Professional Documents
Culture Documents
3GPP2 A.S0007
Ballot Version
Date: June 14, 2001
4 Release 0
5 (Ballot Version)
6
1 Table of Contents
2 Foreword........................................................................................................................................................v
3 1 Introduction .................................................................................................................................. 1-1
4 1.1 Scope ............................................................................................................................................ 1-1
5 1.2 1xEV-DO IOS Architecture Reference Model............................................................................. 1-1
6 1.3 References .................................................................................................................................... 1-2
7 1.4 Terminology ................................................................................................................................. 1-2
8 1.4.1 Acronyms ..................................................................................................................................... 1-2
9 1.4.2 Definitions .................................................................................................................................... 1-3
10 1.5 Document Convention.................................................................................................................. 1-4
11 1.6 Compatibility with IS-2001 Standards ......................................................................................... 1-4
12 1.7 1xEV-DO IOS Assumptions ........................................................................................................ 1-4
13 2 1xEV-DO IOS Call Flows............................................................................................................ 2-1
14 2.1 AT Originates 1xEV-DO Session................................................................................................. 2-1
15 2.1.1 AT Originates 1xEV-DO Session -Successful Authentication..................................................... 2-1
16 2.1.2 AT Originates 1xEV-DO Session - Unsuccessful Authentication ............................................... 2-3
17 2.1.3 AT Originates with a Pre-existing 1xEV-DO Session.................................................................. 2-5
18 2.2 Data Delivery................................................................................................................................ 2-6
19 2.2.1 Data Delivery - AT Terminated.................................................................................................... 2-6
20 2.2.2 Data Delivery - AT Originated..................................................................................................... 2-7
21 2.3 Connection Tear-Down ................................................................................................................ 2-7
22 2.3.1 Connection Tear-Down on 1xEV-DO Network - Initiated by the AT. ........................................ 2-7
23 2.3.2 Connection Tear-Down on 1xEV-DO Network - Initiated by the AN/PCF................................. 2-8
24 2.4 Session Tear-Down....................................................................................................................... 2-9
25 2.4.1 Session Tear-Down - Initiated by the AT.................................................................................... 2-9
26 2.4.2 A10 Tear-Down - Initiated by the PDSN ................................................................................... 2-10
27 2.4.3 Radio Session Tear-Down - Initiated by the AN........................................................................ 2-11
28 2.5 Dormant Handoff of 1xEV-DO AT between ANs - Served by the Same PDSN....................... 2-12
29 2.5.1 AN-AN Dormant Handoff with Successful Retrieval of Session Information........................... 2-12
30 2.5.2 Dormant AN-AN Handoff with Session Information Transfer Failure...................................... 2-14
31 3 1xEV-DO and IS-2000 IOS Transition Call Flows...................................................................... 3-1
32 3.1 Dormant/Idle (Voice or Packet) Cross System Handoff - Served by the Same PDSN. ............... 3-1
33 3.1.1 Dormant/Idle IS-2000 Handoff to Idle 1xEV-DO - Existing Session .......................................... 3-1
34 3.1.2 Dormant/Idle IS-2000 Handoff to Idle 1xEV-DO - New Session................................................ 3-3
35 3.1.3 Idle 1xEV-DO Handoff to Dormant/Idle IS-2000........................................................................ 3-5
36 3.2 AT Terminated Voice Call During Active 1xEV-DO Data Session ............................................ 3-7
i
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 3.2.1 AT Terminated Voice Call During Active 1xEV-DO Data Session (Intra-PDSN/Inter-PCF)..... 3-7
2 3.2.2 MS/AT Terminated Voice Call During Active 1xEV-DO Data Session (Intra-PCF).................. 3-9
3 3.3 AN Change, Active IS-2000 (Packet) to Active 1xEV-DO (Cross System - DO)..................... 3-11
4 3.4 Status Management Supported by Feature Invocation ............................................................... 3-13
5 4 1xEV-DO IOS Interfaces.............................................................................................................. 4-1
6 4.1 A8-A9 (AN - PCF) Interface ........................................................................................................ 4-1
7 4.2 A10-A11 (PCF - PDSN) Interface................................................................................................ 4-1
8 4.3 A12 (AN - AN AAA) Interface.................................................................................................... 4-1
9 4.3.1 PPP Session .................................................................................................................................. 4-2
10 4.3.1.1 Establishment.............................................................................................................. 4-2
11 4.3.1.2 Termination ................................................................................................................ 4-2
12 4.3.1.3 Authentication ............................................................................................................ 4-2
13 4.3.2 RADIUS Support.......................................................................................................................... 4-2
14 4.3.3 Radius Server Requirements ........................................................................................................ 4-3
15 4.4 A13 (AN - AN) Interface.............................................................................................................. 4-4
16 4.4.1 A13 Interface Network/Transport Protocol Specification ............................................................ 4-4
17 4.4.2 A13 Interface Procedures ............................................................................................................. 4-5
18 4.4.2.1 A13-Session Information Request.............................................................................. 4-5
19 4.4.2.1.1 Successful Operation.................................................................................................. 4-5
20 4.4.2.1.2 Failure Operation........................................................................................................ 4-5
21 4.4.2.2 A13-Session Information Response ........................................................................... 4-5
22 4.4.2.2.1 Successful Operation.................................................................................................. 4-5
23 4.4.2.2.2 Failure Operation........................................................................................................ 4-6
24 4.4.2.3 A13-Session Information Confirm ............................................................................. 4-6
25 4.4.2.3.1 Successful Operation.................................................................................................. 4-6
26 4.4.2.3.2 Failure Operation........................................................................................................ 4-6
27 4.4.2.4 A13-Session Information Reject................................................................................. 4-6
28 4.4.2.4.1 Successful Operation.................................................................................................. 4-6
29 4.4.2.4.2 Failure Operation........................................................................................................ 4-6
30 4.4.3 A13 Message Definitions ............................................................................................................. 4-7
31 4.4.3.1 A13-Session Information Request Message ............................................................... 4-7
32 4.4.3.2 A13-Session Information Confirm Message .............................................................. 4-8
33 4.4.3.3 A13-Session Information Reject Message.................................................................. 4-8
34 4.4.3.4 A13-Session Information Response Message............................................................. 4-9
35 4.4.4 A13 Information Element Definitions ........................................................................................ 4-11
36 4.4.4.1 Information Element Identifiers ............................................................................... 4-11
37 4.4.4.2 A13 Message Type ................................................................................................... 4-11
ii
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
18
iii
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 Table of Figures
2 Figure 1.2-1 1xEV-DO IOS Phase 1 Architecture Reference Model ............................................... 1-1
3 Figure 2.1.1-1 Initial AT Origination (with Session Establishment and Key Exchange) .................... 2-1
4 Figure 2.1.2-1 Initial AT Origination (with Session Establishment and Key Exchange) .................... 2-3
5 Figure 2.1.3-1 AT Origination (Session is Already Established) ........................................................ 2-5
6 Figure 2.2.1-1 AT Terminated Data Delivery...................................................................................... 2-6
7 Figure 2.3.1-1 AT Initiated Connection Tear-Down ........................................................................... 2-7
8 Figure 2.3.2-1 AN/PCF Initiated Connection Tear-Down................................................................... 2-8
9 Figure 2.4.1-1 AT Initiated Session Tear-Down.................................................................................. 2-9
10 Figure 2.4.2-1 PDSN Initiated A10 Tear-Down ................................................................................ 2-10
11 Figure 2.4.3-1 AN Initiated Radio Session Tear-Down..................................................................... 2-11
12 Figure 2.5.1-1 Inter-PCF/Intra-PDSN Dormant AN-AN HO - Successful Operation....................... 2-12
13 Figure 2.5.2-1 Inter-PCF/Intra PDSN Dormant AN-AN HO - Session Info Transfer Failure .......... 2-14
14 Figure 3.1.1-1 MS/AT Idle Handoff from IS-2000 to 1xEV-DO - Existing Session .......................... 3-1
15 Figure 3.1.2-1 MS/AT Idle Handoff from IS-2000 to 1xEV-DO - New Session ................................ 3-3
16 Figure 3.1.3-1 MS/AT Idle Handoff from a 1xEV-DO to an IS-2000 System.................................... 3-5
17 Figure 3.2.1-1 Voice Call Termination During Active 1xEV-DO Data Session (Inter-PCF) ............. 3-7
18 Figure 3.2.2-1 Voice Call Termination During Active 1xEV-DO Data Session (Intra-PCF) ............. 3-9
19 Figure 3.3-1 MS/AT Active AN Change from an IS-2000 to a 1xEV-DO System........................ 3-11
20 Figure 3.4-1 Terminal Based Status Management (Using Feature Invocation).............................. 3-13
21 Figure 4.3-1 RADIUS Protocol Reference Model............................................................................ 4-1
22 Figure A.1-1 1xEV-DO IOS Phase 1+ Architecture Reference Model ............................................ A-1
23 Figure D-1 3GPP2 RADIUS Attribute Format.............................................................................. D-1
24
25
26
iv
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 Foreword
2 This 1xEV-DO Inter-Operability Specification (IOS) document is based on TIA/EIA/IS-2001-A, the
3 Inter-Operability Specification (IOS) for CDMA 2000 Access Network Interfaces. This document
4 describes the protocol and some generic procedures to support the following 1xEV-DO IOS features.
5 Conformance to the IOS may be claimed on a feature-by-feature and/or interface-by-interface basis. If
6 conformance on a given interface is claimed for the 1xEV-DO IOS feature, it shall be supported as
7 defined in this standard.
8 Features:
9 Authentication
10 Data delivery
11 Session handoff between ANs.
12
13
v
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 No text.
2
vi
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 1 Introduction
2
3 1.1 Scope
4 This specification provides the 1xEV-DO text and call flows for the following scenarios:
5 N AT originates a 1xEV-DO session (including authentication)
6 N 1xEV-DO data delivery (both AT terminated and AT originated)
7 N 1xEV-DO session tear-down on
8 N Idle handoff of 1xEV-DO AT between ANs
9 N Dormant/Idle (voice or packet) IS-2000 handoff to/from Idle 1xEV-DO (cross system)
10 N Active IS-2000 call (packet), AN change to active call on 1xEV-DO system (cross system, data only)
11 This may happen via a dormant handoff
12 N AT terminated voice call during active 1xEV-DO data session
13 N Status Management
A8 A10
Source Access
PCF PDSN
Network (AN) A9 A11
Target Access
Network (AN)
20
22
1-1
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 1.3 References
2 RFC 1321, MD5 Message-Digest Algorithm, April 1992.
3 RFC 1332, The PPP Internet Protocol Control Protocol (IPCP), May, 1992.
4 RFC 1661, Point-to-Point Protocol, July 1994.
5 RFC 1662, PPP in HDLC-Like Framing, July, 1994.
6 RFC 1750, Randomness Recommendations for Security, December, 1994.
7 RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP), August, 1996.
8 RFC 2486, The Network Access Identifier, January, 1999.
9 RFC 2784, Generic Routing Encapsulation (GRE), March, 2000.
10 RFC 2865, Remote Authentication Dial In User Service (RADIUS), June, 2000.
11 RFC 2866, RADIUS Accounting, June, 2000.
12 TIA/EIA/IS-856, cdma2000 High Rate Packet Data Air Interface Specification, February, 2001.
13 TIA/EIA/IS-2001, Inter-Operability Specification (IOS) for CDMA 2000 Access Network Interfaces,
14 December, 2000.
15 TIA/EIA/IS-2001-A, Inter-Operability Specification (IOS) for CDMA 2000 Access Network Interfaces,
16 May, 2001.
17
18 1.4 Terminology
19
20 1.4.1 Acronyms
1-2
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
2 1.4.2 Definitions
3 Access Stream The IS-856 stream whose end-points are the Access Terminal and the Access Net-
4 work (radio network). This stream is used for access authentication.
5 Access Network The network equipment providing data connectivity between a packet switched data
6 network (typically the Internet) and the access terminals. An access network is equiv-
7 alent to a base station in an IS-2000 systems.
8 Access Terminal A device providing data connectivity to a user. An access terminal may be connected
9 to a computing device such as a laptop personal computer or it may be a self-contain-
10 ed data device such as a personal digital assistant. An access terminal is equivalent to
11 a mobile station in an IS-2000 systems.
12 AN AAA An entity that performs authentication and authorization functions for the Access
13 Network.
14 Connection A connection is a particular state of the air-link in which the access terminal is
15 assigned a Forward Traffic Channel, a Reverse Traffic Channel and associated
16 Medium Access Control (MAC) Channels. During a single session the access
17 terminal and the access network can open and can close a connection multiple times.
18 Hybrid MS/AT A device capable of operating on both IS-2000 and 1xEV-DO access networks.
19 Mobile Station An entity in the (IS-2000) public cellular radio telecommunications service intended
20 to be used while in motion or during halts at unspecified points. Mobile stations
21 include portable units (e.g., hand-held personal units) and units installed in vehicles.
22 Service Stream The IS-856 stream whose end-points are the Access Terminal and the PDSN. This
23 stream is used for packet data exchange.
24 Session A session refers to a shared state between the access terminal and the access network.
25 This shared state stores the protocols and protocol configurations that were
26 negotiated and are used for communications between the access terminal and the
27 access network. Other than to open a session, an access terminal cannot communicate
28 with an access network without having an open session. The 1xEV-DO session and
29 the A10/A11 connection are not associated with each other. The A10/ A11
30 connection may not be established even if the 1xEV-DO session is established. The
31 1xEV-DO session may not be released even if the A10/A11 connection is released.
32
1-3
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
24
1-4
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 Note: Since the AT may have visited an IS-2000 system and established a data session between the
2 time it made an idle handoff from the source AN to target AN, the target AN shall use the PANID
3 given to it by the AT (if any) over the PANID received in the A13-Session Information Accept
4 message from the source AN.
5 N For the instance of Packet Application terminated in the AN, the AT shall support CHAP
6 authentication. In this case, the AT shall send a Network Access Identifier (NAI) of the form
7 specified in RFC 2486.
8 N For the instance of Packet Application terminated in the AN (i.e. AN authentication), the generation
9 of the NAI and password are the responsibility of the service provider. The NAI and password should
10 be chosen and managed using procedures that minimize the likelihood of compromise.
11 N If the AT device authentication feature is used, the AN shall always propose CHAP as a PPP option
12 in an initial Link Control Protocol (LCP) Configure-Request during the PPP establishment.
13 N The MN ID that is used by the AN and the PCF on A8/A9 and A10/A11 messages is determined as
14 follows:
15 S If the 1xEV-DO AN uses the AT device authentication feature, the MN ID field shall be set to the
16 MN ID value returned by the AN-AAA (e.g., IMSI) following successful access authentication.
17 S Otherwise, the AN/PCF shall set the MN ID field to a value that conforms to a valid MN ID
18 format (e.g., IMSI format). In this case, the MN ID is determined by other means.
19 N After the AT indicates it is ready to exchange data on the access stream, the AT and the AN initiate
20 PPP procedures according to RFC 1661.
21 N The AT may support Mobile IP.
22
23
1-5
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 No text.
2
1-6
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
UATI-Request a
UATI-Assignment b
UATI-Complete c
Session Establishment d
AT Ready to Exchange e
Data on Access Stream
A12 Access-Request h
A12 Access-Accept i
AT Ready to Exchange k
Data on Packet Data Stream
A9-Setup-A8 l
A9-Connect-A8 o
7
8
9 Figure 2.1.1-1 Initial AT Origination (with Session Establishment and Key Exchange)
2-1
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 a. The AT sends a UATI-Request message to request that a Unicast Access Terminal Identifier (UATI)
2 be assigned to it by the AN.
3 b. The AN sends a UATI-Assignment message to assign a UATI to the AT.
4 c. The AT sends a UATI-Complete message to notify the AN that it has received the UATI-Assignment
5 message.
6 d. If no session exists between the AT and AN, a session is established where protocols and protocol
7 configurations are negotiated, stored and used for communications between the AT and the AN. Refer
8 to TIA/EIA/IS-856, Section 5, Session Layer.
9 e. The AT indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol
10 for the default packet application bound to the AN is in the open state).
11 f. The AT and the AN initiate Point-to-Point Protocol (PPP) and Link Control Protocol (LCP) negotiat-
12 ions for access authentication. Refer to RFC 1661.
13 g. The AN generates a random challenge and sends it to the AT in a Challenge Handshake Authenticat-
14 ion Protocol (CHAP) Challenge packet in accordance with RFC 1994.
15 h. When the AN receives the CHAP response packet from the AT, it sends a RADIUS Access-Request
16 message packet on the A12 interface to the AN Authentication, Authorization and Accounting (AAA)
17 entity (which acts as a RADIUS server) in accordance with RFC-2865.
18 i. The AN-AAA looks up a password based on the User-name attribute in the A12 Access-Request and
19 if the authentication passes (as specified in RFC-1994 and RFC-2865), the AN AAA sends an
20 Access-Accept packet on the A12 interface. The A12 Access-Accept contains a RADIUS attribute
21 with Type set to 20 (Callback-Id). Refer to Section 4.3.2, RADIUS Support.
22 j. The AN returns an indication of CHAP authentication success, to the AT. Refer to RFC 1994.
23 k. The AT indicates that it is ready to exchange data on the packet data stream. (E.g., the flow control
24 protocol for the default packet application bound to the packet data network is in the open state).
25 l. The AN sends an A9-Setup-A8 message to the Packet Control Function (PCF) and starts timer TA8-
26 setup, to establish the A8-Connection. The A9-Setup-A8 message shall not be sent before the AT indi-
27 cates that it is ready to exchange data on the access stream, as identified in step e.
28 m. The PCF recognizes that no A10 connection associated with the AT is available and selects a PDSN.
29 The PCF sends an A11-Registration Request message to the PDSN which includes the Mobility
30 Event Indicator (MEI) within the Vendor/Organization Specific Extension. The PCF starts timer
31 Tregreq.
32 n. The A11-Registration Request is validated and the PDSN accepts the connection by returning an
33 A11-Registration Reply with an accept indication and Lifetime set to the configured Trp. Both the
34 PDSN and the PCF create a binding record for the A10 connection. The PCF stops timer Tregreq.
35 o. When the AN receives the A9-Connect-A8 message it stops timer TA8-setup.
36 p. PPP connection establishment procedure and optional Mobile IP Registration on the PPP connection
37 are performed between the AT and the PDSN. Refer to RFC 1661.
38 q. At this point the connection is established and packet data can flow between the AT and the PDSN.
39
40
2-2
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
UATI-Request a
UATI-Assignment b
UATI-Complete c
Session Establishment d
AT Ready to Exchange
e
Data on Access Stream
A12 Access-Request h
A12 Access-Reject i
SessionClose k
SessionClose l
5 Figure 2.1.2-1 Initial AT Origination (with Session Establishment and Key Exchange)
6 a. The AT sends a UATI-Request message to request that a UATI be assigned to it by the AN.
7 b. The AN sends a UATI-Assignment message to assign a UATI to the AT.
8 c. The AT sends a UATI-Complete message to notify the AN that it has received the UATI-Assignment
9 message.
10 d. If no session exists between the AT and AN, a session is established where protocols and protocol
11 configurations are negotiated, stored and used for communications between the AT and the AN. Refer
12 to TIA/EIA/IS-856, Section 5, Session Layer.
13 e. The AT indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol
14 for the default packet application bound to the AN is in the open state).
15 f. The AT and the AN initiate PPP and LCP negotiations for access authentication. Refer to RFC 1661.
16 g. The AN generates a random challenge and sends it to the AT in a CHAP Challenge packet in accord-
17 ance with RFC 1994.
18 h. When the AN receives the CHAP response packet from the AT, it sends a RADIUS Access-Request
19 message packet on the A12 interface to the AN AAA (which acts as a RADIUS server) in accordance
20 with RFC-2865.
2-3
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 i. The AN-AAA looks up a password based on the User-name attribute in the A12 Access-Request and
2 if the authentication fails (as specified in RFC-1994 and RFC-2865), the AN AAA sends an Access-
3 Reject packet on the A12 interface.
4 Note: For ANs that perform access authentication, the network requires that no use of a dedicated
5 resource, such as access to a PDSN, be allowed if authentication fails.
6 j. The AN returns an indication of CHAP authentication failure, to the AT. Refer to RFC 1994.
7 k. The AN sends a SessionClose message to the AT, to close the session.
8 l. The AT responds with a SessionClose message.
9
10
2-4
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
Connection Establishment
a
A9-Setup-A8 b
TA8-setup
A9-Connect-A8 c
14
2-5
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
Page Message d
Connection Establishment e
A9-Setup-A8 f
TA8-setup
A9-Connect-A8 g
22
2-6
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
Connection Tear-Down a
(Initiated by the AT)
b
A9-Release-A8
Trel9
c
A9-Release-A8 Complete
18
2-7
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
time
AT AN PCF PDSN
A9-Disconnect-A8
a
Tdiscon9
A9-Release-A8 b
Trel9
c
A9-Release-A8 Complete
Connection Tear-Down
d
(Initiated by the AN)
14
2-8
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
AT AN PCF PDSN
time
Session Tear-Down
a
(Initiated by the AT)
A9-Release-A8 b
A9-Release-A8 Complete e
20
2-9
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
A11-Registration Update a
Tregupd
A11-Registration Acknowledgement b
A9-Disconnect-A8 e
Tdiscon9
A9-Release-A8 f
Trel9
A9-Release-A8 Complete g
18
2-10
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
Session Tear-Down
(Initiated by the AN) a
A9-Release-A8 b
Trel9 Tregreq
A11-Registration Reply (Lifetime=0, accept) d
A9-Release-A8 Complete e
15
2-11
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 2.5 Dormant Handoff of 1xEV-DO AT between ANs - Served by the Same PDSN
2 This section describes the call flows associated with AT dormant handoff between ANs.
UATI-Request a
TA13req
A13-Session Information Response c
UATI-Assignment
d
UATI-Complete
Location Update
e
Procedures
A9-Setup-A8 g
Tregreq
A11-Registration Reply (Lifetime, accept) i
A11-Registration Update j
TA8-setup Tregupd
A11-Registration Acknowledge k
A11-Registration Request l
(Lifetime=0)
Tregreq
A11-Registration Reply
m
(Lifetime=0, accept)
A9-Release-A8-Complete n
2-12
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 e. The Location Update procedures may be used to retrieve the PANID information for sending to the
2 PCF / PDSN.
3 f. The target AN sends an A13-Session Information Confirm to the source AN to indicate that the target
4 AN has received the session information. The target AN stops timer TA13req. Upon receipt of the A13-
5 Session Information Confirm message the source AN deletes the AT session information in question.
6 g. The target AN sends an A9-Setup-A8 message, with Data Ready Indicator set to 0, to the target PCF
7 and starts timer TA8-setup.
8 h. The target PCF selects the PDSN to connect to using the PDSN address provided in the A13-Session
9 Information Response message or using PDSN selection algorithms as specified in TIA/EIA/IS-2001,
10 and sends an A11-Registration Request message to the PDSN. The A11-Registration Request
11 message includes the Mobility Event Indicator (MEI) within the Vendor/Organization Specific Ex-
12 tension. The target PCF starts timer Tregreq. Refer to TIA/EIA/IS-2001-A, Section 2.15.5.8, Inter-PCF
13 Dormant Handoff - Mobile Continues to be Served by the Serving PDSN.
14 i. The A11-Registration Request is validated and the PDSN accepts the connection by returning an
15 A11-Registration Reply with an accept indication and the Lifetime set to the configured Trp value. If
16 the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization
17 Specific Extension. The A10 connection binding information at the PDSN is updated to point to the
18 target PCF. The target PCF stops timer Tregreq.
19 j. The PDSN initiates closure of the A10 connection with the source PCF by sending an A11-Registrat-
20 ion Update message. The PDSN starts timer Tregupd.
21 k. The source PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer
22 Tregupd.
23 l. The source PCF sends an A11-Registration Request message with Lifetime set to zero, to the PDSN.
24 The source AN/PCF starts timer Tregreq.
25 m. The PDSN sends an A11-Registration Reply message to the source PCF. The source PCF closes the
26 A10 connection for the AT and stops timer Tregreq.
27 n. The target PCF responds to the target AN with an A9-Release-A8-complete message. The AN stops
28 timer TA8-setup.
29
30
2-13
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
UATI-Request a
UATI-Assignment
d
UATI-Complete
Location Update
Procedures e
Access Authentication f
A9-Setup-A8 g
A11-Registration Update j
Tregupd
TA8-setup k
A11-Registration Acknowledge
A11-Registration Request
l
(Lifetime=0)
Tregreq
A11-Registration Reply
m
(Lifetime=0, accept)
A9-Release-A8-Complete n
5 Figure 2.5.2-1 Inter-PCF/Intra PDSN Dormant AN-AN HO - Session Info Transfer Failure
6 a. The target AN receives a UATI-Request from the AT.
7 b. The target AN sends an A13-Session Information Request message to the source AN to request the
8 session information for the AT. The A13-Session Information Request message shall include the
9 received UATI and the Security Layer Packet. The target AN starts timer TA13req.
10 c. The source AN cannot validate the A13-Session Information Request or does not have the requested
11 AT session information and sends an A13-Session Information Reject message to the target AN. The
12 target AN stops the timer TA13req.
13 d. The target AN sends a UATI-Assignment to the AT with a new UATI. The AT confirms that it has
14 received the UATI with a UATI-Complete message. This step can occur anytime after receipt of the
15 UATI-Request message.
16 e. The Location Update procedures may be used to retrieve the PANID information for sending to the
17 PCF / PDSN.
2-14
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 f. Since no session exist between the AN and AT, a new session is established. The AT opens an access
2 stream for access authentication. If access authentication is enabled/supported at the target AN, it
3 shall initiate a PPP on the access stream. The AT performs an access authentication via CHAP /
4 RADIUS towards the AN-AAA. The AN shall use the MN ID received from the AN-AAA in the A12
5 Access-Accept, in messages on the A9/A11 interfaces. Refer to Section 4.3, A12 (AN-AN AAA)
6 Interface.
7 g. The target AN transmits an A9-Setup-A8 message to target PCF with Data Ready Indicator set to 0 to
8 establish an A8 connection and starts timer TA8-setup.
9 h. The target PCF selects a PDSN for this call using PDSN selection algorithms as specified in IS-2001.
10 The target PCF sends an A11-Registration Request message to the selected PDSN. The A11-
11 Registration Request includes the Mobility Event Indicator (MEI) within the Vendor/Organization
12 Specific Extension. The PCF starts timer Tregreq. Refer to TIA/EIA/IS-2001-A, Section 2.15.5.8, Inter-
13 PCF Dormant Handoff - Mobile Continues to be Served by the Serving PDSN.
14 i. The A11-Registration Request is validated and the PDSN accepts the connection by returning an
15 A11-Registration Reply with an accept indication and the Lifetime set to the configured Trp value. If
16 the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization
17 Specific Extension . The A10 connection binding information at the PDSN is updated to point to the
18 target PCF. The target PCF stops timer Tregreq.
19 j. The PDSN initiates closure of the A10 connection with the source PCF by sending an A11-Registrat-
20 ion Update message. The PDSN starts timer Tregupd.
21 k. The source PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer
22 Tregupd.
23 l. The source PCF sends an A11-Registration Request message with Lifetime set to zero, to the PDSN.
24 The source AN/PCF starts timer Tregreq.
25 m. The PDSN sends an A11-Registration Reply message to the source PCF. The source PCF closes the
26 A10 connection for the AT and stops timer Tregreq.
27 n. The target PCF responds to the target AN with an A9-Release-A8 Complete message. The AN stops
28 timer TA8-setup.
29
30
2-15
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 No text.
2
2-16
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
4 3.1 Dormant/Idle (Voice or Packet) Cross System Handoff - Served by the Same PDSN.
5 This section describes the call flows for dormant/idle handoffs between 1xEV-DO and TIA/EIA/IS-2000
6 systems.
Location Update a
Procedures
b
A9-Setup-A8
A11-Registration Request (Lifetime, MEI) c
Tregreq
A11-Registration Reply (Lifetime, accept) d
A11-Registration Update e
TA8-setup Tregupd
A11-Registration Acknowledge f
Tregreq
A11-Registration Reply (Lifetime=0, accept) h
A9-Release-A8 i
Complete
15
16
17 Figure 3.1.1-1 MS/AT Idle Handoff from IS-2000 to 1xEV-DO - Existing Session
18 a. The change of AN is indicated by the Location Update procedures as defined in TIA/EIA/IS-856.
19 b. The target AN sends an A9-Setup-A8 message to the target PCF and starts timer TA8-setup.
20 c. The target PCF sends an A11-Registration Request message to the PDSN. The A11-Registration Re-
21 quest message includes the MEI, the PANID of the source PCF and the Current Access Network
22 Identifiers (CANID) of the target PCF, within the Vendor/Organization Specific Extension. The
23 target PCF starts timer Tregreq.
24 d. The A11-Registration Request is validated and the PDSN accepts the connection by returning an
25 A11-Registration Reply with an accept indication and the Lifetime set to the configured Trp value. If
3-1
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization
2 Specific Extension. The A10 connection binding information at the PDSN is updated to point to the
3 target PCF. The target PCF stops timer Tregreq.
4 e. The PDSN initiates closure of the A10 connection with the source BSC/PCF by sending an A11-Reg-
5 istration Update message. The PDSN starts timer Tregupd.
6 f. The source BSC/PCF responds with an A11-Registration Acknowledge message. The PDSN stops
7 timer Tregupd.
8 g. The source BSC/PCF sends an A11-Registration Request message with Lifetime set to zero, to the
9 PDSN. The source BSC/PCF starts timer Tregreq.
10 h. The PDSN sends an A11-Registration Reply message to the source BSC/PCF. The source BSC/PCF
11 closes the A10 connection for the MS/AT and stops timer Tregreq.
12 i. The target PCF sends an A9-Release-A8 Complete message to the target AN. The target AN stops
13 timer TA8-setup.
14
15
3-2
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
UATI-Request a
b
UATI-Assignment
UATI-Complete c
Session Establishment d
AT Ready to Exchange e
Data on Access Stream
A12 Access-Request h
A12 Access-Accept i
AT Ready to Exchange
l
Data on Packet Data Stream
A11-Registration Update o
Tregupd
A11-Registration Acknowledge p
PPP Traffic s
7 Figure 3.1.2-1 MS/AT Idle Handoff from IS-2000 to 1xEV-DO - New Session
8 a. The MS/AT sends a UATI-Request message to request that a UATI be assigned to it by the target
9 AN/PCF.
10 b. The target AN/PCF sends a UATI-Assignment message to assign a UATI to the MS/AT.
11 c. The MS/AT sends a UATI-Complete message to notify the target AN/PCF that it has received the
12 UATI-Assignment message.
3-3
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 d. Since no session exists between the MS/AT and target AN/PCF, a session is established where
2 protocols and protocol configurations are negotiated, stored and used for communications between
3 the MS/AT and the AN. Refer to TIA/EIA/IS-856, Section 5, Session Layer.
4 e. The AT indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol
5 for the default packet application bound to the AN is in the open state).
6 f. After session configuration the MS/AT initiates PPP and LCP negotiations for access authentication.
7 Refer to RFC 1661.
8 g. The target AN/PCF generates a random challenge and sends it to the MS/AT in a CHAP Challenge
9 packet in accordance with RFC 1994.
10 h. When the target AN/PCF receives the CHAP response packet from the MS/AT, it sends a RADIUS
11 Access-Request message packet on the A12 interface to the AN AAA (which acts as a RADIUS
12 server) in accordance with RFC-2865.
13 i. The target AN-AAA looks up a password based on the User-name attribute in the A12 Access-
14 Request and if the authentication passes (as specified in RFC-1994 and RFC-2865), the AN AAA
15 sends an Access-Accept packet on the A12 interface. The A12 Access-Accept contains a RADIUS
16 attribute with Type set to 20 (Callback-Id). Refer to Section 4.3.2, RADIUS Support.
17 j. The target AN/PCF returns an indication of CHAP authentication success, to the MS/AT. Refer to
18 RFC 1994.
19 k. The change of AN is indicated by the Location Update procedures as defined in TIA/EIA/IS-856.
20 l. The AT indicates that it is ready to exchange data on the packet data stream. (E.g., the flow control
21 protocol for the default packet application bound to the packet data network is in the open state).
22 m. The target AN/PCF sends an A11-Registration Request message to the PDSN. The A11-Registration
23 Request message includes the MEI, the PANID of the source and the CANID of the target PCF,
24 within the Vendor/Organization Specific Extension. If PANID is not sent in step l, the AN/PCF sets
25 all of the fields within the PANID and the CANID to zero. The target AN/PCF starts timer Tregreq.
26 n. The A11-Registration Request is validated and the PDSN accepts the connection by returning an
27 A11-Registration Reply with an accept indication and the Lifetime set to the configured Trp value. If
28 the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization
29 Specific Extension. The A10 connection binding information at the PDSN is updated to point to the
30 target AN/PCF. The target AN/PCF stops timer Tregreq.
31 o. The PDSN initiates closure of the A10 connection with the source BSC/PCF by sending an A11-Reg-
32 istration Update message. The PDSN starts timer Tregupd.
33 p. The source BSC/PCF responds with an A11-Registration Acknowledge message. The PDSN stops
34 timer Tregupd.
35 q. The source BSC/PCF sends an A11-Registration Request message with Lifetime set to zero, to the
36 PDSN. The source BSC/PCF starts timer Tregreq.
37 r. The PDSN sends an A11-Registration Reply message to the source BSC/PCF. The source BSC/PCF
38 closes the A10 connection for the MS/AT and stops timer Tregreq.
39 s. PPP traffic flows.
40
41
3-4
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
Target Source
MS/AT MSC PDSN time
BSC/PCF AN/PCF
Origination (DRS='0') a
BS Ack Order b
T303
Assignment Request d
Assignment Failure g
Clear Command h
T20
Clear Complete i
A11-Registration Update j
Tregupd
A11-Registration Acknowledge k
3-5
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 e. The target BSC/PCF sends an A11-Registration Request message to the PDSN. The A11-Registrat-
2 ion Request message includes the MEI, the PANID of the source PCF and the CANID of the target
3 PCF, within the Vendor/Organization Specific Extension. The target BSC/PCF starts timer Tregreq.
4 f. The A11-Registration Request is validated and the PDSN accepts the connection by returning an
5 A11-Registration Reply with an accept indication and the Lifetime set to the configured Trp value. If
6 the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization
7 Specific Extension. The A10 connection binding information at the PDSN is updated to point to the
8 target BSC/PCF. The target BSC/ PCF stops timer Tregreq.
9 If the PDSN responds to the target BSC/PCF with the Data Available Indicator, the target BSC/PCF
10 establishes a traffic channel (IS-2001-A 2.15.5.4-1). In this case the remaining steps in this procedure
11 are omitted.
12 g. The target BSC/PCF sends an Assignment Failure message to the MSC with the cause value indicat-
13 ing Packet Call Going Dormant and starts timer T20. The MSC stops timer T10.
14 h. The MSC sends a Clear Command message to the target with a Cause value Do Not Notify Mobile
15 and starts timer T315. The BSC/PCF stops timer T20 upon receipt of the Clear Command message.
16 i. The target BSC/PCF sends a Clear Complete message to the MSC. The MSC stops timer T315.
17 j. The PDSN initiates closure of the A10 connection with the source AN/PCF by sending an A11-Reg-
18 istration Update message. The PDSN starts timer Tregupd.
19 k. The source AN/PCF responds with an A11-Registration Acknowledge message. The PDSN stops
20 timer Tregupd.
21 l. The source AN/PCF sends an A11-Registration Request message with Lifetime set to zero, to the
22 PDSN. The source AN/PCF starts timer Tregreq.
23 m. The PDSN sends an A11-Registration Reply message to the source AN/PCF. The source AN/PCF
24 closes the A10 connection for the MS/AT and stops timer Tregreq.
25
26
3-6
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
4 3.2.1 AT Terminated Voice Call During Active 1xEV-DO Data Session (Intra-PDSN/Inter-PCF)
5 This section describes the call flow associated with an MS/AT terminated voice call while the MS/AT has
6 an active 1xEV-DO data session. The 1xEV-DO data session is handed off to the IS-2000 system as a
7 concurrent call service if the MS/AT has and selects this capability.
Paging Request a
Page b
Page Response f
Paging Response g
Assignment Request h
Assignment Complete j
A9-Setup-A8 m
T10
A11-Registration Request (Lifetime, MEI) n
TA8-Setup Tregreq
A11-Registration Reply (Lifetime, accept) o
A9-Connect-A8 p
Assignment Complete q
Connect Order s
Connect t
x A9-Release-A8 u
A9-Release-A8 Complete x
9 Figure 3.2.1-1 Voice Call Termination During Active 1xEV-DO Data Session (Inter-PCF)
3-7
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 a. The MSC determines that an incoming call terminates to an MS/AT within its serving region and
2 sends a Paging Request message to the BS to initiate an MS/AT terminated call setup scenario. The
3 MSC starts timer T3113.
4 b. The BS sends a Page Message containing the AT address over the paging channel. The MS/AT may
5 ignore this Page Message to continue the 1xEV-DO session. If the MS/AT ignores the message,
6 following steps are not performed.
7 c. The AN determines that it is not receiving any transmissions from the MS/AT and starts timer Tairdrop.
8 d. The AN sends an A9-AL Disconnected message to PCF2 to stop data flow and starts timer Tald9.
9 e. Upon receipt of the A9-AL Disconnected message, the PCF2 sends an A9-AL Disconnected Ack to
10 the AN. The AN stops timer Tald9.
11 f. The MS/AT sends a Page Response message to the BS. This step can occur any time after step c.
12 g. The BS sends a Paging Response message to the MSC. The MSC stops timer T3113.
13 h. The MSC sends an Assignment Request message to the BS and starts timer T10.
14 i. The BS establishes a traffic channel upon receipt of the Assignment Request message. Refer to
15 TIA/EIA/IS-856, Section 8.4 (8.5), Default Forward (Reverse) Traffic Channel MAC Procedures.
16 j. After the traffic channel setup is complete, the BS sends an Assignment Complete message to the
17 MSC. The MSC stops timer T10.
18 k. The BS sends an Alert with Info message to indicate the MS/AT to ring.
19 l. The MS/AT and the IS-2000 system set up the data session for handoff from 1xEV-DO as a
20 concurrent call service if the MS/AT has concurrent call service capability and selects to handoff the
21 data session from the 1xEV-DO to the IS-2000 system. Refer to TIA/EIA/IS-2001-A, Section
22 2.17.2.1 steps (a) to step (g).
23 m. The BS sends an A9-Setup-A8 message to the PCF1 to establish A8 connection and starts timer TA8-
24 setup.
25 n. PCF1 sends an A11-Registration Request message to the PDSN to establish the A10 connection to
26 handoff from the 1xEV-DO system to the IS-2000 system. PCF1 starts timer Tregreq.
27 o. The A11-Registration Request is validated and the PDSN accepts the connection by returning an
28 A11-Registration Reply with an accept indication. The target PCF1 stops timer Tregreq.
29 p. PCF1 sends an A9-Connect-A8 message after the completion of the A10 connection handoff. The BS
30 stops timer TA8-setup.
31 q. The BS sends an Assignment Complete message to the MSC and stops timer T10 (started during the
32 origination for concurrent service, in step l).
33 r. At this point, the data session is successfully handed off from the 1xEV-DO to the IS-2000 system.
34 s. The MS/AT sends a Connect Order message when the call is answered at the MS/AT.
35 t. The BS sends a Connect message to the MSC.
36 u. Upon not having received any transmissions from the MS/AT prior to timer Tairdrop expiration, the AN
37 sends an A9-Release-A8 message to PCF2 and starts timer Trel9.
38 v. PCF2 sends an A11-Registration Request message with Lifetime set to zero, to the PDSN. PCF2
39 starts timer Tregreq.
40 w. The PDSN sends an A11-Registration Reply message to PCF2. The PCF2 closes the A10 connection
41 for the MS/AT and stops timer Tregreq.
42 x. PCF2 responds to the AN with an A9-Release-A8 Complete message. The AN stops timer Trel9.
43
3-8
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 3.2.2 MS/AT Terminated Voice Call During Active 1xEV-DO Data Session (Intra-PCF)
2 This section describes the call flow associated with an MS/AT terminated voice call while the MS/AT has
3 an active 1xEV-DO data session. The 1xEV-DO data session is handed off to the IS-2000 system as a
4 concurrent call service if the MS/AT has and selects this capability.
Paging Request a
Page b
A9-AL Disconnected d
T3113
Tald9
A9-AL Disconnected Ack-A8 e
Page Response f
Paging Response g
Assignment Request h
TCH Setup T10 i
Assignment Complete j
Alert with Info k
Tairdrop
Origination for Concurrent Service l
A9-Setup-A8 m
A9-Connect-A8 n
Assignment Complete o
Connect Order q
Connect r
x A9-Release-A8 s
A9-Release-A8 Complete t
5
6 Figure 3.2.2-1 Voice Call Termination During Active 1xEV-DO Data Session (Intra-PCF)
7 a. The MSC determines that an incoming call terminates to an MS/AT within its serving region and
8 sends a Paging Request message to the BS to initiate an MS/AT terminated call setup scenario. The
9 MSC starts timer T3113.
10 b. The BS sends a Page Message containing the MS/AT address over the paging channel. The MS/AT
11 may ignore this Page Message to continue the 1xEV-DO session. If the MS/AT ignores the message,
12 following steps are not performed.
13 c. The AN determines that it is not receiving any transmissions from the MS/AT and starts timer Tairdrop.
14 d. The AN sends an A9-AL Disconnected message to the PCF to stop data flow and starts timer Tald9.
15 e. Upon receipt of the A9-AL Disconnected message, the PCF sends an A9-AL Disconnected Ack to the
16 AN. The AN stops timer Tald9.
17 f. The MS/AT sends a Page Response message to the BS. This step can occur any time after step c.
3-9
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 g. The BS sends a Paging Response message to the MSC. The MSC stops timer T3113.
2 h. The MSC sends an Assignment Request message to the BS and starts timer T10.
3 i. The BS establishes a traffic channel upon receipt of the Assignment Request message.
4 j. After the traffic channel setup is complete, the BS sends an Assignment Complete message to the
5 MSC. The MSC stops timer T10. Refer to TIA/EIA/IS-856, Section 8.4 (and 8.5), Default Forward
6 (and Reverse) Traffic Channel MAC Procedures.
7 k. The BS sends an Alert with Info message to indicate the MS/AT to ring.
8 l. The MS/AT and IS-2000 system set up the data session for handoff from 1xEV-DO as a concurrent
9 call service if the MS/AT has concurrent call service capability and selects to handoff the data session
10 from the 1xEV-DO to the IS-2000 system. Refer to TIA/EIA/IS-2001-A, Section 2.17.2.1 steps (a) to
11 step (g).
12 m. The BS sends an A9-Setup-A8 message to the PCF to establish A8 connection and starts timer TA8-
13 setup.
14 n. The PCF sends an A9-Connect-A8 message to the BS. The BS stops timer TA8-setup.
15 o. The BS sends an Assignment Complete message to the MSC and stops timer T10 (started during the
16 origination for concurrent service), in step l.
17 p. At this point, the data session is successfully handed off from the 1xEV-DO system to the IS-2000
18 system.
19 q. The MS/AT sends a Connect Order message when the call is answered at the MS/AT..
20 r. The BS sends a Connect message to the MSC.
21 s. Upon not having received any transmissions from the MS/AT prior to timer Tairdrop expiration, the AN
22 sends an A9-Release-A8 message to the PCF and starts timer Trel9.
23 t. Upon receipt of the A9-Release-A8 message, the PCF sends an A9-Release-A8 Complete message to
24 the AN. The AN stops timer Trel9.
25
26
3-10
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 3.3 AN Change, Active IS-2000 (Packet) to Active 1xEV-DO (Cross System - DO)
2 This section describes the call flow associated with an MS/AT AN change from an IS-2000 to a 1xEV-
3 DO system. The MS/AT determines that an AN change from IS-2000 to 1xEV-DO is required. In this
4 scenario, it is assumed that the MS/AT has already established a session, however it does not have a
5 connection established.
Target Source
MS/AT AN/PCF BSC/PCF MSC PDSN time
Release Order a
Release Order b
Clear Request c
T300
Clear Command d
A11-Registration Update h
T315 Tregupd
A11-Registration Acknowledge i
Clear Complete l
1 AT is ready to exchange data packets. In this case, the AN may take the appropriate action to notify
2 the AT that data packets are available (e.g., by requesting that the Flow Control Protocol transition to
3 the Open state).
4 g. The A11-Registration Request is validated and the PDSN accepts the connection by returning an
5 A11-Registration Reply with an accept indication and the Lifetime set to the configured Trp value. If
6 the PDSN has data to send, it includes the Data Available Indicator within the Vendor/Organization
7 Specific Extension. The A10 connection binding information at the PDSN is updated to point to the
8 target AN/PCF. The target AN/PCF stops timer Tregreq.
9 h. The PDSN initiates closure of the A10 connection with the source BSC/PCF by sending an A11-Reg-
10 istration Update message. The PDSN starts timer Tregupd.
11 i. The source BSC/PCF responds with an A11-Registration Acknowledge message. The PDSN stops
12 timer Tregupd.
13 j. The source BSC/PCF sends an A11-Registration Request message with Lifetime set to zero, to the
14 PDSN. The source BSC/PCF starts timer Tregreq.
15 k. The PDSN sends an A11-Registration Reply message to the source BSC/PCF. The source BSC/PCF
16 closes the A10 connection for the MS/AT and stops timer Tregreq.
17 l. The target BSC/PCF sends a Clear Complete message to the MSC. The MSC stops timer T315.
18 m. Packet data exchange continues between the MS/AT and the PDSN.
19
20
3-12
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
Origination a
(Feature Code)
Mobile Originating Call Setup b
c
MSC Initiated Call Clearing
Origination f
(Feature Code)
Mobile Originating Call Setup g
24
3-13
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 No text.
2
3-14
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
IP IP IP IP IP IP
PL PL PL PL PL PL
4-1
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
2 4.3.1.1 Establishment
3 After the AT indicates it is ready to exchange data on the access stream, the AT and the AN initiate PPP
4 procedures according to RFC 1661.. PPP shall support transparency in accordance with section 4.2 of
5 RFC 1662. The AN and AT shall attempt to negotiate a control character mapping, with the minimum
6 number of escaped characters by proposing an ACCM of 0x00000000. Additionally, if no PPP session is
7 present, the AN may re-authenticate the MS/AT by reinitiating the PPP session.
8 4.3.1.2 Termination
9 The AN may release the PPP connection after the authentication of the AT has been performed. The AN
10 may support a PPP inactivity timer for each PPP session. When the inactivity timer expires, the AN shall
11 terminate the PPP session.
12 4.3.1.3 Authentication
13 The AT and the AN shall support the authentication mechanism CHAP. The AN shall always propose
14 CHAP as a PPP option in an initial LCP Configure-Request during the PPP establishment.
1 The numbers in this list correspond to the RADIUS attribute type defined in RFC 2865.
4-2
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 Callback-Id (20) is populated with the MN ID (i.e., IMSI) and the String field shall be set as
2 follows:
7 6 5 4 3 2 1 0 Octet
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 1
Indicator = [110] (MN ID)
= [1,0]
3 The Odd/Even Indicator (octet 3; bit 3) field is set to 0 for an even number of digits and to 1
4 for an odd number of identity digits.
5 The identity digits (octet 3 etc.) are coded as follows:
6 The International Mobile Subscriber Identifier fields are coded using BCD coding format. If the
7 number of identity digits is even then bits 4 to 7 of the last octet shall be filled with an end mark
8 coded as 1111.
9
22
4-3
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 establishment procedures are used. An existing TCP connection over an interface is released when there
2 are no more signaling messages to be exchanged over the interface. Normal TCP connection release pro-
3 cedures are used. The following TCP and UDP port values are reserved for signaling on the A13 inter-
4 face:
5 A13 (AN-to-AN) 3125/tcp - This is the well-known TCP port number to be used for signaling
6 interconnection to another AN.
7 A13 (AN-to-AN) 3125/udp - This is the well-known UDP port number to be used for signaling
8 interconnection to another AN.
4-5
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
28
4-6
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
6 The following table shows the bitmap layout for the A13-Session Information Request Message
7 6 5 4 3 2 1 0 Octet
A13 Message Type = [01H] 1
UATI: A13 Element Identifier = [01H] 1
Length = [0FH] 2
UATI Type = [01] 3
(MSB) UATI 4
5
OOO OOO
(LSB) N
Security Layer Packet: A13 Element Identifier = [02H] 1
Length = [variable] 2
(MSB) Security Layer Packet 3
4
OOO OOO
(LSB) N
Sector ID: A13 Element Identifier = [03H] 1
Length = [0FH] 2
(MSB) Sector ID 3
4
OOO OOO
(LSB) N
4-7
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
5 The following table shows the bitmap layout for the A13-Session Information Confirm Message
7 6 5 4 3 2 1 0 Octet
A13 Message Type = [02H] 1
UATI: A13 Element Identifier = [01H] 1
Length = [0FH] 2
UATI Type = [01H] 3
(MSB) UATI 4
5
OOO OOO
(LSB) N
10
11 The following table shows the bitmap layout for the A13-Session Information Reject Message
7 6 5 4 3 2 1 0 Octet
A13 Message Type = [03H] 1
UATI: A13 Element Identifier = [01H] 1
Length = [0FH] 2
UATI Type = [01H] 3
(MSB) UATI 4
5
OOO OOO
(LSB) N
-- Continued on next page --
12
4-8
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
7 The following table shows the bitmap layout for the A13-Session Information Response Message
7 6 5 4 3 2 1 0 Octet
A13 Message Type = [04H] 1
UATI: A13 Element Identifier = [01H] 1
Length = [0FH] 2
UATI Type = [01H] 3
(MSB) UATI 4
5
OOO OOO
(LSB) N
-- Continued on next page --
8
4-9
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
4-10
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
7 6 5 4 3 2 1 0 Octet
A13 Element Identifier 1
Length 2
UATI Type = [01H] 3
(MSB) UATI 4
5
OOO OOO
(LSB) N
11 Length This field contains the number of octets in this element following this field as a
12 binary number.
13 UATI Type This field indicates the type of the UATI. The supported values are listed as
14 follows.
4-11
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 UATI This is set to the terminal identifier associated with the MS/AT.
2
7 6 5 4 3 2 1 0 Octet
A13 Element Identifier 1
Length 2
(MSB) Security Layer Packet 3
4
OOO OOO
(LSB) N
5 Length This field contains the number of octets in this element following this field as a
6 binary number.
7 Security Layer Packet This is set to the security layer packet received from the MS/AT.
8
9 4.4.4.5 SectorID
10 The AN shall set this field to the 128-bit address of this sector.
7 6 5 4 3 2 1 0 Octet
A13 Element Identifier 1
Length 2
(MSB) Sector ID 3
4
OOO OOO
(LSB) N
11 Length This field shall be set to the length of this element in octets following the Length
12 Field.
13 Sector ID This is set to the address of the sector.
14
4-12
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 4.4.4.6 Cause
2 This element is used to indicate the reason for occurrence of a particular event and is coded as shown
3 below.
7 6 5 4 3 2 1 0 Octet
A13 Element Identifier 1
Length 2
(MSB) Cause Value (LSB) 3
4 Length This field contains the number of octets in this element following this field as a
5 binary number.
6 Cause Value This field is set to the range of values below:
7
7 6 5 4 3 2 1 0 Octet
A13 Element Identifier 1
Length = 14-15 digits 2
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 3
Indicator = [110] (MN ID)
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4
OOO OOO OOO
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) N
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
11 Length This field contains the number of octets in this element following this field as a
12 binary number.
13
14
4-13
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
7 6 5 4 3 2 1 0 Octet
A1 Element Identifier = [13H] 1
Length 2
(MSB) PDSN IP Address 3
4
5
(LSB) 6
3 Length This field contains the number of octets in this element following this
4 field as a binary number.
5 PDSN IP Address This field is set to the IPv4 address of a PDSN.
6
7 6 5 4 3 2 1 0 Octet
A13 Element Identifier 1
Type = 01H 2
Length 3
Reserved (MSB) SID 4
(LSB) 5
(MSB) NID 6
(LSB) 7
PZID 8
4-14
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
7 6 5 4 3 2 1 0 Octet
A13 Element Identifier 1
Length 2
(MSB) AN State Information Record 3
OOO OOO
(LSB) N
3 Length This field contains the number of octets in this element following
4 this field as a binary number.
5 AN State Information Record This field contains the air interface protocol attributes and
6 associated public data. - The format is as specified in
7 TIA/EIA/IS-856.
8
10
4-15
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 No text.
2
4-16
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
5-1
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 No text.
2
5-2
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
Phase 1
A8 A10
Access
Access Terminal
Network PCF PDSN
(AT)
(AN) A9 A11
Session
Control
A12
A13 Proxy
AN AAA
AN AAA
Session
Control
A8 A10
Access
Access Terminal
Network PCF PDSN
(AT)
(AN) A9 A11
A12
Proxy
AN AAA
AN AAA
Future
A8' A10
Access Terminal Access Network
PCF' PDSN
(AT) (AN')
A9' Session
A11
Control
A12
A8' A10
Access Terminal Access Network
PCF' PDSN
(AT) (AN')
A9' Session
A11
Control
A12
Proxy
AN AAA
AN AAA
A-1
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
A-2
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
Active / Dormant
Connected State
State
Null/Inactive
State
24
1 In 1xEV-DO systems when data is ready to be sent, a ConnectionRequest message is sent on initial call
2 setup to transition from Dormant to Active for the purposes of requesting the establishment of a traffic
3 channel. A UATI assignment is requested when the terminal has detected change of subnet while
4 dormant, to update the network as to its current location.
5 On receipt of an origination with the DRS bit set to 1 or a ConnectionRequest message in a 1xEV-DO
6 system, the BS will initiates the call setup procedure as shown in Section 2.14.7.1, which will normally
7 results in the establishment of a traffic channel and in the A8 and A10 bearer connections being establish-
8 ed.
9 When the BS receives an origination with the DRS bit set to 0 or a request for UATI assignment in a
10 1xEV-DO system, the BS will delays the establishment of a traffic channel until after the A8 and A10
11 bearer connection establishment procedures are complete. During the A8 bearer connection establishment
12 procedure, the BS will indicates to the PCF that a DRS=0 has been received (or there is no indication of
13 data ready to be exchanged, for 1xEV-DO systems) through the use of the Data Ready Indicator element
14 in the A9-Setup-A8 message. If the PCF has data from the network to deliver to the terminal, it will
15 indicates this by setting the Cause element in the A9-Connect-A8 message to the Data Ready to Send
16 value. The BS will then establishes a traffic channel to the terminal and complete a normal call setup
17 procedure as in Section 2.14.7.1.
18 If the PCF does not have data, it indicates that the A8 is not being established by sending the A9-Release-
19 A8 Complete message to the BS. The BS will then returns an Assignment Failure message to the MSC
20 with the Cause value set to Packet Call Going Dormant. Upon receipt of the Assignment Failure message,
21 the MSC returns a Clear Command to the BS with the Cause value set to Do Not Notify Mobile. The BS
22 sends a Clear Complete message to the MSC upon receipt of the Clear Command message.
33 2.14.4.1.1 A9-Setup-A8
34 No changes from TIA/EIA/IS-2001-A text.
B-2
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 The BSC sends the message to the PCF on the A9 interface and starts timer TA8-Ssetup. Upon receiving the
2 message, the PCF initiates the procedure for establishing an A10 connection.
3 After establishing an A10 connection, the PCF sends an A9-Connect-A8 message to the BSC. For the
4 case where the DRS bit received from the mobile is set to 0 or a request for a traffic channel is not
5 received in the 1xEV-DO system, the BSC will awaits the response from the PCF to determine if a traffic
6 channel needs to be established.
7 When the mobile station performs a hard handoff during packet services, the target BSC sends the A9-
8 Setup-A8 message upon receipt of the Handoff Request message from the MSC and starts timer TA8-sSetup.
9 In this case, the BSC sets the Handoff Indicator field of the A9-Setup-A8 message to 1 and Data Ready
10 Indicator is set to 1.
11 In the case of dormant handoff the BSC sends the A9-Setup-A8 message to the PCF upon receipt of the
12 Assignment Request message from the MSC or upon completion of the UATI assignment in 1xEV-DO
13 systems. For this case, it will sets both the Data Ready Indicator and the Handoff Indicator to 0. Please
14 refer to section 6.1.10.1, A9-Setup-A8, for the format and content of this message. Alternatively, if
15 upon receipt of the A9-Setup-A8 message, if the PDSN has no data to send to the MS (in the case of a
16 dormant handoff) or if the PCF could not setup the A8 connection due to PDSN resources being
17 unavailable, the PCF will sends the A9-Release-A8 Complete message. Upon receipt of this message, the
18 BSC stops timer TA8-Ssetup.
19 If the A9-Setup-A8 message contains a DRS IndicatorDRI set to '0' and the PCF does not have data to
20 send, the PCF rejects the attempt to setup the A8 connection by sending an A9-Release- A8-Complete
21 message to the BSC.
29 2.14.4.1.2 A9-Connect-A8
30 No changes from TIA/EIA/IS-2001-A text.
B-3
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
B-4
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
3 2.14.5.3 A9-Release-A8
4 No changes from TIA/EIA/IS-2001-A text.
15 2.14.5.5 A9-Disconnect-A8
16 No changes from TIA/EIA/IS-2001-A text.
21 2.14.5.6 A9-Update-A8
22 This A9 interface message is sent from the BSC to the PCF and is used in several cases. First, it is used to
23 convey accounting information to the PCF if the A8 connection is established before traffic channel
24 establishment (in which case the PCF will resumes data transmission on the A8 connection only after it
25 receives the A9-update-A8 message) or during an active session following accounting parameters changes
26 which need to be conveyed to the PDSN indirectly via the PCF.
27 This A9 interface message can also be used to inform the PCF of an authentication failure at the MSC or
28 AN-AAA for 1xEV-DO systems, following an access attempt by a mobile undergoing dormant handoff.
29 The BSC can also use this message to inform the PCF that a dormant mobile has powered down. In these
30 two cases, the PCF initiates the release of the A10 connection associated with the mobile. This A9
31 message may also be used to indicate to the PCF a successful Short Data Burst delivery.
B-5
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
B-6
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 OOO
2 6.1.10 A9 Interface Message Formats
3 6.1.10.1 A9-Setup-A8
4 This A9 interface message is sent from the BS to the PCF to request the establishment of an A8
5 connection.
Information Element Section Element Direction Type
Reference
A9 Message Type 6.2.2.167 BS -> PCF M
Call Connection Reference 6.2.2.98 BS -> PCF O R
Correlation ID 6.2.2.108 BS -> PCF Oa C
Mobile Identity (IMSI) 6.2.2.16 BS -> PCF Og R
Mobile Identity (ESN) 6.2.2.16 BS -> PCF Ob C
CON_REF 6.2.2.168 BS -> PCF Oh R
Quality of Service Parameters 6.2.2.54 BS -> PCF Oc C
A9 BSC_ID 6.2.2.169 BS -> PCF O R
A8_Traffic_ID 6.2.2.170 BS -> PCF O R
Service Option 6.2.2.66 BS -> PCF Of R
A9 Indicators 6.2.2.171 BS -> PCF O R
User Zone ID 6.2.2.32 BS -> PCF Oi C
IS-2000 Service configuration record 6.2.2.68 BS -> PCF Oe C
Access Network Identifiers 6.2.2.189 BS -> PCF Od C
6 a. If this element is included in this message, its value shall be returned in the corresponding element in
7 the A9-Connect A8 message sent in response to this message.
8 b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS.
9 Use of the ESN in this message is a network operator decision. This information element shall not be
10 included in 1xEV-DO messages.
11 c. This information element is included if information is available at the BS. In this version of this
12 standard, this element is used to carry the current non-assured mode priority of the packet data
13 session. This information element shall not be included in 1xEV-DO messages.
14 d. The Access Node Identifiers (PANID) are included if received from the MS..
15 e. This information element may be omitted if the BS does not possess this information at the time the
16 message if created. This information element shall not be included in 1xEV-DO messages.
17 f. The User Zone ID is included if received from the MS.
18 g. This information element shall be set to the MN ID, associated with the A10 connection, for 1xEV-
19 DO messages.
20 h. The IS-2000 CON_REF field of this information element shall be set to 00H for padding, for 1xEV-
21 DO messages.
22 i. The UZID field of this information element shall be set to 00H for padding, for 1xEV-DO messages.
23
24 The following table shows the bitmap layout for the A9-Setup-A8 message:
B-7
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [01H] 1
Call Connection Reference: A1 Element Identifier = [3FH] 1
Length = [08H] 2
(MSB) Market ID = <any value> 3
(LSB) 4
(MSB) Generating Entity ID = <any value> 5
(LSB) 6
(MSB) 7
Call Connection Reference = <any value> 8
9
(LSB) 10
Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
Mobile Identity (IMSI): A1 Element Identifier = [0DH] 1
Length = [06H-08H] (10-15 digits) 2
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 3
Indicator = [110] (IMSI)
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4
OOO OOO
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
Mobile Identity (ESN): A1 Element Identifier = [0DH] 1
Length = [05H] 2
Identity Digit 1 = [0000] Odd/even Type of Identity 3
Indicator = [101] (ESN)
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
-- Continued on next page --
1
B-8
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
B-9
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
B-10
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 6.1.10.2 A9-Connect-A8
2 This A9 interface message is sent from the PCF to the BS to complete the setup of the A8 connection.
Information Element Section Element Direction Type
Reference
A9 Message Type 6.2.2.167 PCF -> BS M
Call Connection Reference 6.2.2.98 PCF -> BS O R
Correlation ID 6.2.2.108 PCF -> BS Oa C
Mobile Identity (IMSI) 6.2.2.16 PCF -> BS Od R
Mobile Identity (ESN) 6.2.2.16 PCF -> BS Ob C
CON_REF 6.2.2.168 PCF -> BS Oe R
A8_Traffic_ID 6.2.2.170 PCF -> BS O R
Cause 6.2.2.19 PCF -> BS Oc R
PDSN IP Address 6.2.2.30 PCF -> BS O R
3 a. This element shall only be included if it was also included in the A9-Setup-A8 message. This element
4 shall be set to the value received in that message.
5 b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS.
6 Use of the ESN in this message is a network operator decision. This information element shall not be
7 included on 1xEV-DO messages.
8 c. Allowable cause values are: PCF resources not available; Equipment failure; Successful
9 operation, PDSN resources are not available, Data ready to send.
10 d.The PCF transmits its Access Network Identifiers (CANID) to the Base Station.
11 d. This information element shall be set to the MN ID, associated with the A10 connection, for 1xEV-
12 DO messages.
13 e. The IS-2000 CON_REF field of this information element shall be set to 00H for padding, for 1xEV-
14 DO messages.
15
16
B-11
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 The following table shows the bitmap layout for the A9-Connect-A8 message:
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [02H] 1
Call Connection Reference: A1 Element Identifier = [3FH] 1
Length = [08H] 2
(MSB) Market ID = <any value> 3
(LSB) 4
(MSB) Generating Entity ID = <any value> 5
(LSB) 6
(MSB) 7
Call Connection Reference = <any value> 8
9
(LSB) 10
Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
Mobile Identity (IMSI): A1 Element Identifier = [0DH] 1
Length = [06H-08H] (10-15 digits) 2
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 3
Indicator = [110] (IMSI)
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4
OOO OOO
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
Mobile Identity (ESN): A1 Element Identifier = [0DH] 1
Length = [05H] 2
Identity Digit 1 = [0000] Odd/even Type of Identity 3
Indicator = [101] (ESN)
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
-- Continued on next page --
2
B-12
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
B-13
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 6.1.10.3 A9-Disconnect-A8
2 This A9 interface message is sent from the PCF to the BS to release the associated dedicated resource.
Information Element Section Element Direction Type
Reference
A9 Message Type 6.2.2.167 PCF -> BS M
Call Connection Reference 6.2.2.98 PCF -> BS O R
Correlation ID 6.2.2.108 PCF -> BS Oa C
Mobile Identity (IMSI) 6.2.2.16 PCF -> BS Od R
Mobile Identity (ESN) 6.2.2.16 PCF -> BS Ob C
CON_REF 6.2.2.168 PCF -> BS Oe R
A8_Traffic_ID 6.2.2.170 PCF -> BS O R
Cause 6.2.2.19 PCF -> BS Oc R
3 a. If this element is included in this message, its value shall be returned in the corresponding element in
4 the A9-Release-A8 message sent in response to this message.
5 b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS.
6 Use of the ESN in this message is a network operator decision. This information element shall not be
7 included in 1xEV-DO messages.
8 c. Allowable cause values are: Packet call going dormant; Equipment failure; Normal call release.
9 d. This information element shall be set to the MN ID, associated with the A10 connection, for 1xEV-
10 DO messages.
11 e. The IS-2000 CON_REF field of this information element shall be set to 00H for padding, for 1xEV-
12 DO messages.
13
14
B-14
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 The following table shows the bitmap layout for the A9-Disconnect-A8 message:
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [03H] 1
Call Connection Reference: A1 Element Identifier = [3FH] 1
Length = [08H] 2
(MSB) Market ID = <any value> 3
(LSB) 4
(MSB) Generating Entity ID = <any value> 5
(LSB) 6
(MSB) 7
Call Connection Reference = <any value> 8
9
(LSB) 10
Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
Mobile Identity (IMSI): A1 Element Identifier = [0DH] 1
Length = [06H-08H] (10-15 digits) 2
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 3
Indicator = [110] (IMSI)
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4
OOO OOO
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
Mobile Identity (ESN): A1 Element Identifier = [0DH] 1
Length = [05H] 2
Identity Digit 1 = [0000] Odd/even Type of Identity 3
Indicator = [101] (ESN)
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
-- Continued on next page --
2
B-15
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
B-16
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 6.1.10.4 A9-Release-A8
2 This A9 interface message is sent from the BS to the PCF to release the associated dedicated resource.
Information Element Section Element Direction Type
Reference
A9 Message Type 6.2.2.167 BS-> PCF M
Call Connection Reference 6.2.2.98 BS-> PCF O R
Correlation ID 6.2.2.108 BS-> PCF Oa C
Mobile Identity (IMSI) 6.2.2.16 BS-> PCF Oe R
Mobile Identity (ESN) 6.2.2.16 BS-> PCF Ob C
CON_REF 6.2.2.168 BS-> PCF Of R
A8_Traffic_ID 6.2.2.170 BS-> PCF O R
Cause 6.2.2.19 BS-> PCF Oc R
Active Connection Time in Seconds 6.2.2.11 BS-> PCF Od R
4 a. This element shall be included if it was also included in the A9-Disconnect-A8 message. This
5 element shall be set to the value received in that message. If this element was not included in that
6 message, it may be included in this message.
7 b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS.
8 Use of the ESN in this message is a network operator decision. This information element shall not be
9 included in 1xEV-DO messages.
10 c. Allowable cause values are: Packet call going dormant; Equipment failure; Normal call
11 release; "Handoff Successful"; Authentication Failure. Note that Normal Call Release indicates
12 that the service has been released and therefore the A10 resources should be dropped.
13 d. This element shall be included to indicate the active connection time for a traffic channel.
14 e. This information element shall be set to the MN ID, associated with the A10 connection, for 1xEV-
15 DO RAN messages.
16 f. The IS-2000 CON_REF field of this information element shall be set to 00H for padding, for 1xEV-
17 DO messages.
18
19
B-17
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 The following table shows the bitmap layout for the A9-Release-A8 message:
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [04H] 1
Call Connection Reference: A1 Element Identifier = [3FH] 1
Length = [08H] 2
(MSB) Market ID = <any value> 3
(LSB) 4
(MSB) Generating Entity ID = <any value> 5
(LSB) 6
(MSB) 7
Call Connection Reference = <any value> 8
9
(LSB) 10
Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
Mobile Identity (IMSI): A1 Element Identifier = [0DH] 1
Length = [06H-08H] (10-15 digits) 2
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 3
Indicator = [110] (IMSI)
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4
OOO OOO
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
Mobile Identity (ESN): A1 Element Identifier = [0DH] 1
Length = [05H] 2
Identity Digit 1 = [0000] Odd/even Type of Identity 3
Indicator = [101] (ESN)
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
CON_REF: A9 Element Identifier = [01H] 1
Length = [01H] 2
IS-2000 CON_REF = [00H FFH] 3
-- Continued on next page --
2
B-18
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
B-19
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
6 a. If this element is included in this message, its value shall be returned in the corresponding element in
7 the A9-BS Service Response message sent in response to this message.
8 b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS.
9 Use of the ESN in this message is a network operator decision. This information element shall not be
10 included in 1xEV-DO messages.
11 c. This IE may be included by the PCF to indicate to the BS the amount of data remaining at the PCF
12 that is to be transmitted. This information element shall not be included in 1xEV-DO messages.
13 d. This information element shall be is set to the MN ID, associated with the A10 connection, for 1xEV-
14 DO RAN messages.
15
B-20
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 The following table shows the bitmap layout for the A9-BS Service Request message:
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [06H] 1
Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
Mobile Identity (IMSI): A9 Element Identifier = [0DH] 1
Length = [06H-08H] (10-15 digits) 2
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 3
Indicator = [110] (IMSI)
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4
OOO OOO
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
Mobile Identity (ESN): A1 Element Identifier = [0DH] 1
Length = [05H] 2
Identity Digit 1 = [0000] Odd/even Type of Identity 3
Indicator = [101] (ESN)
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
Service Option: A1 Element Identifier = [03H] 1
(MSB) Service Option 2
= [00 21H (3G High Speed Packet Data)] (LSB) 3
Data Count: A9 Element Identifier = [09H] 1
Length = [02H] 2
Count = <any value> 3
4
2
B-21
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
16
B-22
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 The following table shows the bitmap layout for the A9-AL Connected message:
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [08H] 1
Call Connection Reference: A1 Element Identifier = [3FH] 1
Length = [08H] 2
(MSB) Market ID = <any value> 3
(LSB) 4
(MSB) Generating Entity ID = <any value> 5
(LSB) 6
(MSB) 7
Call Connection Reference = <any value> 8
9
(LSB) 10
Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
A8 Traffic ID: A9 Element Identifier = [08H] 1
Length = [0CH] 2
A8 transport protocol stack = [01H] (GRE/IP) 3
(MSB) Protocol Type = [88 81H] (Unstructured byte stream) 4
(LSB) 5
(MSB) 6
Key = <any value> 7
8
(LSB) 9
Address Type = [01H] (IPv4) 10
(MSB) 11
IP Address = <any value> 12
13
(LSB) 14
PDSN IP Address: A1 Element Identifier = [14H] 1
Length = [04H] 2
(MSB) 3
PDSN IP Address = <any value> 4
5
(LSB) 6
-- Continued on next page --
2
B-23
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
B-24
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
4 a. This element shall only be included if it was also included in the A9-AL Connected message. This
5 element shall be set to the value received in that message.
6 b. This IE may be included if the target PCF could not connect to the PDSN designated in the A9-AL
7 Connected message.
8 The following table shows the bitmap layout for the A9-AL Connected Ack message:
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [09H] 1
Call Connection Reference: A1 Element Identifier = [3FH] 1
Length = [08H] 2
(MSB) Market ID = <any value> 3
(LSB) 4
(MSB) Generating Entity ID = <any value> 5
(LSB) 6
(MSB) 7
Call Connection Reference = <any value> 8
9
(LSB) 10
Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
PDSN IP Address: A1 Element Identifier = [14H] 1
Length = [04H] 2
(MSB) 3
PDSN IP Address = <any value> 4
5
(LSB) 6
9
B-25
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
7 a. This element shall only be included if it was also included in the A9-AL Disconnected message. This
8 element shall be set to the value received in that message.
9 The following table shows the bitmap layout for the A9-AL Disconnected Ack message:
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [0BH] 1
Call Connection Reference: A1 Element Identifier = [3FH] 1
Length = [08H] 2
(MSB) Market ID = <any value> 3
(LSB) 4
(MSB) Generating Entity ID = <any value> 5
(LSB) 6
(MSB) 7
Call Connection Reference = <any value> 8
9
(LSB) 10
Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
10
11
12
B-26
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
7 a. If this element is included, its value shall be returned in the corresponding element in the A9-Short
8 Data Ack message from the BS.
9 b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS.
10 Use of the ESN in this message is a network operator decision.
11 c. This element is included in this message when sent from the PCF to the BS and indicates the number
12 of additional bytes of data queued at the PCF and waiting to be sent to a specific mobile.
13 d. Contains the packet data received from the PDSN or an MS in a SDB format as specified in
14 TIA/EIA/IS-707-A-2.
15
16
B-27
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 The following table shows the bitmap layout for the A9-Short Data Delivery message.
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [0CH] 1
Correlation ID: A8/A9 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
Mobile Identity (IMSI): A9 Element Identifier = [0DH] 1
Length = [06H-08H] (10-15 digits) 2
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 3
Indicator = [110] (IMSI)
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4
OOO OOO
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
Mobile Identity (ESN): A1 Element Identifier = [0DH] 1
Length = [05H] 2
Identity Digit 1 = [0000] Odd/even Type of Identity 3
Indicator = [101] (ESN)
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
SR_ID: A9 Element Identifier = [0BH] 1
Length = [01H] 2
Reserved = [0000 0] IS-2000 SR_ID = [001 - 011] 3
Data Count: A9 Element Identifier = [09H] 1
Length = [02H] 2
Count = <any value> 3
4
ADDS User Part: A1 Element Identifier = [3DH] 1
Length = <variable> 2
Reserved = [00] Data Burst Type = 3
[ 06H (Short Data Burst) ]
(MSB) Application Data Message = <any value> 4
OOO OOO
(LSB) n
3
B-28
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
7 a. If this element is included, its value shall be set to the value of the corresponding element in the A9-
8 Short Data Delivery message from the PCF.
9 b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS.
10 Use of the ESN in this message is a network operator decision.
11 c. The cause value indicates to the PCF whether a short data burst is to will be sent to the mobile.
12
13
B-29
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 The following table shows the bitmap layout for the A9-Short Data Ack message.
2
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [0DH] 1
Correlation ID: A8/A9 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
Mobile Identity (IMSI): A9 Element Identifier = [0DH] 1
Length = [06H-08H] (10-15 digits) 2
Identity Digit 1 = [0H-9H] (BCD) Odd/ev Type of Identity 2
en = [110] (IMSI)
Indicat
or
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 3
OOO OOO
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
Mobile Identity (ESN): A1 Element Identifier = [0DH] 1
Length = [05H] 2
Identity Digit 1 = [0000] Odd/ev Type of Identity 3
en = [101] (ESN)
Indicat
or
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
SR_ID: A9 Element Identifier = [0BH] 1
Length = [01H] 2
Reserved = [0000 0] IS-2000 SR_ID = [001 - 011] 3
Cause: A1 Element Identifier = [04H] 1
Length = [01H] 2
ext = Cause Value = 3
[0] [13H (Successful Operation),
16H (Initiate Re-activation of Packet Data call)
B-30
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 6.1.10.14 A9-Update-A8
2 This A9 interface message is sent from the BS to the PCF to indicate a change to the session airlink para-
3 meters.
4
5 a. If this element is included in this message, its value shall be returned in the corresponding element in
6 the A9-Update-A8-Ack message sent in response to this message.
7 b. This second occurrence of the Mobile Identity element, if included, shall contain the ESN of the MS.
8 Use of the ESN in this message is a network operator decision. This information element shall not be
9 included in 1xEV-DO messages.
10 c. These elements are required unless the message is used to indicate Dormant Power down or
11 Authentication Failure.
12 d. This information element shall be set to the MN ID, retrieved from AN-AAA, for 1xEV-DO
13 messages.
14 e. This information element shall not be included in 1xEV-DO messages.
15
16
B-31
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 The following table shows the bitmap layout for the A9-Update-A8 message:
7 6 5 4 3 2 1 0 Octet
A9 Message Type = [03H] 1
Call Connection Reference: A1 Element Identifier = [3FH] 1
Length = [08H] 2
(MSB) Market ID = <any value> 3
(LSB) 4
(MSB) Generating Entity ID = <any value> 5
(LSB) 6
(MSB) 7
Call Connection Reference = <any value> 8
9
(LSB) 10
Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
Mobile Identity (IMSI): A9 Element Identifier = [0DH] 1
Length = [06H-08H] (10-15 digits) 2
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 2
Indicator = [110] (IMSI)
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 3
OOO OOO
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
Mobile Identity (ESN): A1 Element Identifier = [0DH] 1
Length = [05H] 2
Identity Digit 1 = [0000] Odd/even Type of Identity 3
Indicator = [101] (ESN)
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
-- Continued on next page --
2
B-32
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
B-33
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 6.1.10.15 A9-Update-A8-Ack
2 No changes from TIA/EIA/IS-2001-A text.
3
B-34
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
C-1
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 The A10 bearer connection is used for the transport of user data for a packet data session. Link layer /
2 network layer frames are carried between the PCF and the PDSN encapsulated in GRE packets, which in
3 turn are carried over IP. The PCF-Address and the PDSN-Address are used in the source address and
4 destination address fields of the IP header used with the GRE packet. The key field in the GRE header
5 contains the PCF Session Identifier (PSI), and indicates to which packet data bearer connection a partic-
6 ular payload packet belongs to.
7 The A11 A11-Registration Request and A11-Registration Reply messages are defined by RFC 2002 with
8 extension elements defined in Section 6.1.11 of this standard. The A11-Registration Update and A11-
9 Registration Acknowledge messages are also defined in Section 6.1.11 of this standard. The procedures
10 for the use of these messages are defined in Section 2.15.1 of this standard.
C-2
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 Registration Reply message. The address of the alternate proposed PDSN shall be returned in the Home
2 Agent field of the A11-Registration Reply message.
3 On receipt of an A11-Registration Reply with code 88H, the PCF shall either initiate establishment of
4 the A10 connection with the proposed PDSN by sending a new A11-Registration Request message as
5 indicated in this section, or shall use internal algorithms to select a new PDSN.
6 On receipt of an A11-Registration Reply with another result code, depending on the result code, the PCF
7 may attempt to re-try setting up the A10 connection. If the A10 connection can not be established, the
8 PCF indicates this to the AN which releases the call or to the BSC, which returns a failure indication to
9 the MSC, which in-turn releases the call.
10 Reliable message delivery mechanisms are used for setting up the A10 connection between the PCF and
11 the PDSN. As specified in RFC 2002, the A11-Registration Request message may be retransmitted if no
12 A11-Registration Reply is received within a configurable time. A call is considered to have failed if no
13 A11-Registration Reply is received after a configurable number of A11-Registration Request retrans-
14 missions.
22 If some airlink parameters for an active session change, the PCF generates an Active Stop (Y1=3)
23 accounting record followed by an Active Start (Y1=2) accounting record. For successful operation, the
24 PDSN saves the accounting related and other information for further processing, and responds with A11-
25 Registration Reply with an accept indication.
26 See section 6.2.2.166 Vendor/Organization Specific Extension for detailed information on all the airlink
27 record types and the accounting parameters required for each airlink record type. If the accounting
28 parameter specified for an airlink record type is not received at the PDSN, the PDSN shall return an A11-
29 Registration Reply with result code 8DH (Registration Denied - unsupported Vendor ID or unable to
30 interpret data in the CVSE.
31 The following is a description of the accounting events and indicates which airlink record type shall be
32 used for each event. If a specified airlink record type is not received at the PDSN or on receipt of an
33 unspecified airlink record type, the PDSN shall return an A11-Registration Reply with result code 8DH
34 (Registration Denied unsupported Vendor ID or unable to interpret data in the CVSE.
C-4
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
C-5
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 The PCF shall notify the PDSN using A11-Registration Request message containing an Active Stop
2 and an Active Start with the new set of parameters.
Parameter Parameter
b
change change
notification/ notification/
C-6
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 OOO
2 6.2.2.155 Flags
3 No changes from TIA/EIA/IS-2001-A text.
4 6.2.2.156 Lifetime
5 No changes from TIA/EIA/IS-2001-A text.
10 6.2.2.159 Care-of-Address
11 No changes from TIA/EIA/IS-2001-A text.
12 6.2.2.160 Identification
13 No changes from TIA/EIA/IS-2001-A text.
14 6.2.2.161 Code
15 No changes from TIA/EIA/IS-2001-A text.
16 6.2.2.162 Status
17 No changes from TIA/EIA/IS-2001-A text.
0 1 2 3 4 5 6 7 Octet
A11 Element Identifier (Type) 1
Reserved 2
(MSB) 3
Length (LSB) 4
(MSB) 5
3GPP2 Vendor ID 6
7
(LSB) 8
Application Type 9
Application Sub Type 10
(MSB) 11
12
Application Data
(LSB) k
3 Type: 26H
4 Length: This field indicates the number of octets in this element following this
5 field.
6 3GPP2 Vendor ID: 00 00 15 9FH
7 Application Type: This field indicates the type of the application, that the extension relates
8 to. The supported values are:
9 Table 6.2.2.166-1 - Vendor/Organization Specific Extension - Application Type
Hex Value Description
01H Accounting
02H Mobility Event Indicator
03H Data Available Indicator
04H Access Network Identifiers
All other values reserved.
10
11 Application Sub Type: This one octet field indicates the Application sub-type within the
12 Application Type. The supported values are listed in Table 6.2.2.166-2.
13
14
C-8
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
3 Application Data: For Application Type 01H (Accounting), this field contains the account-
4 ing parameters conveyed from the PCF to the PDSN as specified in
5 TIA/EIA/IS-835 (Wireless IP Network Standard). Each of the accounting
6 parameters are structured in the format of RADIUS attributes specified in
7 RFC 2138 2865 and RFC 21392866. This field is used in messages sent
8 from the PCF to the PDSN.
9 For Application Type 02H (Mobility Event Indicator), this field is zero
10 bytes in length. This field is used in messages sent from the PCF to the
11 PDSN.
12 For Application Type 03H (Data Available Indicator), this field is zero
13 bytes in length. This field is used in messages sent from the PDSN to the
14 PCF.
15 For Application Type 04H (Access Network Identifiers), this field con-
16 tains the PANID of the source PCF in octets 11-15 and CANID of the
17 target PCF in octets 16-20. The PANID and CANID are formatted as
18 specified for the Access Network Identifiers element (see section
19 6.2.2.189) from octet 3-7. If PANID or CANID information is not avail-
20 able, it shall be coded as all zeros. The PANID and CANID information
21 is included only in the first A11 Registration Request message following
22 a handoff.
23 For Application Type 01 H (Accounting) all 3GPP2 specific Airlink
24 Record Parameters are coded as follows:
25
C-9
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 2 3 4 5 6 7 8 Octet
Type 1
Length 2
(MSB) 3
4
3GPP2 Vendor-Id 5
(LSB) 6
Vendor-Type 7
Vendor-Length 8
MSB 9
10
3 Type: 1A H
4 Length: Type (1 octet ) + Length (1 octet ) + 3GPP2 Vendor Id (4 octets) + {
5 Vendor-Type (1 octet), Vendor-Length (1 octet), Vendor-Value (variable
6 octets) of the 3GPP2 specific parameter comprising the airlink record
7 being coded.}
8 Vendor ID: 00 00 15 9F H
9 Vendor Type: Sub-Type value from the Airlink Record table below.
10 Vendor-Length: Vendor-Type (1 octet) + Vendor-Length (1 octet) + Payload Length (in
11 octets) from the Airlink Record table below.
12
13 For Application Type 01 H (Accounting) all RADIUS specific Airlink Record Parameters are coded as
14 follows:
1 2 3 4 5 6 7 8 Octet
Type 1
Length 2
MSB 3
4
15
16 Length: Type (1 octet) + Length (1 octet) + Payload Length (in octets) from the
17 Airlink Record table below.
18
C-10
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
2 A number formed from the concatenation of SID+NID+BSC ID, where each item is encoded using four
hexadecimal upper case ASCII characters.
3 If the PCF has not received this information from the AN, the PCF shall set this field to a default value of 0.
C-11
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
4 An example coding of the Active Stop Airlink Record within the Vendor/Organization Specific Extension
5 element is illustrated below:
0 1 2 3 4 5 6 7 Octet
A11 Element Identifier = 26H 1
Reserved 2
(MSB) 3
Length = 30 H (LSB) 4
(MSB) 5
3GPP2 Vendor ID = 00 00 15 9F H 6
7
(LSB) 8
Application Type = 01 H 9
Application Sub Type = 01 H 10
Parameter Name: Airlink Record Type = 3 (Active Stop)
Type = 1A H 11
Length = 0C H 12
(MSB) 13
14
3GPP2 Vendor-Id = 00 00 15 9F H 15
(LSB) 16
Vendor-Type = 28 H 17
Vendor-Length = 06 H 18
MSB 19
20
4 Subtype 31 is for terminating SDB octet count, subtype 32 is for originating SDB octet count.
C-12
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
C-13
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 No text.
2
C-14
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont) | Vendor-type |Vendor-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor-value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
10 1xEV-DO Terminal Authentication: Indicates whether the Access Request is in the context of terminal
11 authentication. This optionally appears in an A12 Access-Request.
12 Vendor-Type = TBD [Editors note: TBD requires resolution]
13 Vendor-Length = 6
14 Vendor-Value = 1 (1xEV-DO Terminal Authentication)
15
16
17
18
D-1
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 No text.
2
D-2
SP-3-0009 (TIA/EIA/IS-878)
June 14, 2001 1xEV-DO IOS Ballot Version
E-1
SP-3-0009 (TIA/EIA/IS-878)
1xEV-DO IOS Ballot Version June 14, 2001
1 No text.
2
E-2