TIA/EIA/IS-2001

TIA/EIA
INTERIM STANDARD
Interoperability Specifications (IOS)
For cdma2000 Access Network
Interfaces

TIA/EIA/IS-2001
DECEMBER 2000

TELECOMMUNICATIONS INDUSTRY ASSOCIATION

The Telecommunications Industry Association

represents the communications sector of

NOTICE
TIA/EIA Engineering Standards and Publications are designed to serve the public interest through eliminating
misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of
products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his
particular need. Existence of such Standards and Publications shall not in any respect preclude any member or
nonmember of TIA/EIA from manufacturing or selling products not conforming to such Standards and Publications,
nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TIA/EIA
members, whether the standard is to be used either domestically or internationally.
Standards and Publications are adopted by TIA/EIA in accordance with the American National Standards Institute
(ANSI) patent policy. By such action, TIA/EIA does not assume any liability to any patent owner, nor does it
assume any obligation whatever to parties adopting the Standard or Publication.
TIA/EIA INTERIM STANDARDS
TIA/EIA Interim Standards contain information deemed to be of technical value to the industry, and are published at
the request of the originating Committee without necessarily following the rigorous public review and resolution of
comments which is a procedural part of the development of a TIA/EIA Standard.
TIA/EIA Interim Standards should be reviewed on an annual basis by the formulating Committee and a decision
made on whether to proceed to develop a TIA/EIA Standard on this subject. TIA/EIA Interim Standards must be
cancelled by the Committee and removed from the TIA/EIA Standards Catalog before the end of their third year of
existence.
Publication of this TIA/EIA Interim Standard for trial use and comment has been approved by the
Telecommunications Industry Association. Distribution of this TIA/EIA Interim Standard for comment shall not
continue beyond 36 months from the date of publication. It is expected that following this 36 month period, this
TIA/EIA Interim Standard, revised as necessary, will be submitted to the American National Standards Institute for
approval as an American National Standard. Suggestions for revision should be directed to: Standards &
Technology Department, Telecommunications Industry Association, 2500 Wilson Boulevard, Arlington, VA 22201.
(From Project No. 4545, formulated under the cognizance of the TIA TR-45.4 Subcommittee on Radio to Switching
Technology.)
Published by
TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2000
Standards & Technology Department
2500 Wilson Boulevard
Arlington, VA 22201
PRICE: Please refer to current Catalog of
EIA ELECTRONIC INDUSTRIES ALLIANCE STANDARDS and ENGINEERING PUBLICATIONS or
call Global Engineering Documents, USA and Canada
(1-800-854-7179) International (303-397-7956)

All rights reserved

Printed in U.S.A.

PLEASE!
DON'T VIOLATE
THE
LAW!

This document is copyrighted by the TIA and may not be reproduced without
permission.
Organizations may obtain permission to reproduce a limited number of copies
through entering into a license agreement. For information, contact:

Global Engineering Documents

15 Inverness Way East
Englewood, CO 80112-5704 or call
U.S.A. and Canada 1-800-854-7179, International (303) 397-7956

TIA/EIA/IS-2001

Table of Contents

1
2

FOREWORD............................................................................................................................................................ XXIV

COPYRIGHT INFORMATION............................................................................................................................. XXIX

1.

1.1
PURPOSE ............................................................................................................................................................1
1.2
SCOPE ................................................................................................................................................................3
1.3
ORGANIZATION ...............................................................................................................................................4
1.3.1
Architectures Supported...................................................................................................................... 4
1.3.2
UNUSED SECTION .............................................................................................................................. 4
1.3.3
IOS V4.0 Layout .................................................................................................................................... 4
1.4
DOCUMENTATION CONVENTIONS...............................................................................................................5
1.4.1
Procedural Descriptions..................................................................................................................... 6
1.5
REFERENCES.....................................................................................................................................................7
1.5.1
Telecommunications Industry Association (TIA) / Electronics Industry Association (EIA) . 7
1.5.3
International Telecommunications Union - Telecommunications Sector (ITU-T) ................... 9
1.5.4
Other......................................................................................................................................................10
1.6
TERMINOLOGY ...............................................................................................................................................11
1.6.1
Acronyms ..............................................................................................................................................11
1.6.2
Definitions............................................................................................................................................17
1.7
INTERFACE M ODEL ......................................................................................................................................21
1.7.1
Reference Points A, Ater, and Aquater...................................................................................................21
1.7.2
Interface Reference Model.................................................................................................................22
1.7.3
MSC BS Functional Partitioning.................................................................................................24
1.7.4
Information Flows...............................................................................................................................25
1.7.5
Protocol Reference Model.................................................................................................................26

5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

1.7.5.1 MSC-BS interface Channel Types ..........................................................................................................26

1.7.5.2 Transport Protocols ................................................................................................................................26
1.7.5.3 Layer 3 - A1 Interface: Base Station Application Part ...........................................................................27

26
27
28

1.7.6

29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

FUNCTIONAL OVERVIEW................................................................................................................................. 1

2.

Packet Data Micro-Mobility and Macro-Mobility Concepts ....................................................29

CALL PROCESSING AND SUPPLEMENTARY SERVICES ......................................................................30

2.1
CALL CONTROL .............................................................................................................................................30
2.1.1
Terrestrial Circuit Allocation ..........................................................................................................30
2.1.2
Radio Channel Allocation ................................................................................................................30
2.1.3
Traffic Channel Release.....................................................................................................................30
2.2
A1 INTERFACE CALL SETUP FOR VOICE AND CIRCUIT DATA CALLS ................................................31
2.2.1
Mobile Originated Calls ...................................................................................................................31
2.2.1.1 Connection Management (CM) Service Request ....................................................................................31
2.2.1.2 Complete Layer 3 Information................................................................................................................32
2.2.1.3 UNUSED SECTION (Setup)..................................................................................................................33
2.2.1.4 UNUSED SECTION...............................................................................................................................33
2.2.1.5 Assignment Request................................................................................................................................33
2.2.1.6 Assignment Complete.............................................................................................................................33
2.2.1.7 Assignment Failure..................................................................................................................................33
2.2.1.8 UNUSED SECTION...............................................................................................................................34
2.2.1.9 Progress ...................................................................................................................................................34
2.2.1.10 UNUSED SECTION ...........................................................................................................................34
2.2.1.11 UNUSED SECTION 2.2.1.12 UNUSED SECTION..........................................................................34
2.2.1.13 UNUSED SECTION ...........................................................................................................................34
2.2.1.15 UNUSED SECTION ...........................................................................................................................34

2.2.2

Mobile Origination Examples..........................................................................................................34

2.2.2.1 Mobile Origination ..................................................................................................................................35

i

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

2.2.2.2 Mobile Origination with Access Probe Handoff, Access Handoff and Channel Assignment into
Soft/Softer Handoff...............................................................................................................................................37
2.2.2.3 Mobile Origination with PACA Service..................................................................................................42

2.2.3

Mobile Terminated Voice and Circuit Data Calls .......................................................................48

2.2.3.1 Paging Request.........................................................................................................................................48

2.2.3.2 Paging Response......................................................................................................................................49
2.2.3.3 UNUSED SECTION...............................................................................................................................49
2.2.3.4 UNUSED SECTION...............................................................................................................................49
2.2.3.5 UNUSED SECTION...............................................................................................................................49
2.2.3.6 Assignment Request................................................................................................................................50
2.2.3.7 Assignment Complete.............................................................................................................................50
2.2.3.8 Assignment Failure..................................................................................................................................50
2.2.3.9 UNUSED SECTION h............................................................................................................................50
2.2.3.10 Connect ................................................................................................................................................50
2.2.3.11 UNUSED SECTION ...........................................................................................................................50
2.2.3.12 Alert With Information ........................................................................................................................51

2.2.4

Mobile Termination Examples .........................................................................................................52

2.2.4.1 Mobile Termination.................................................................................................................................52

2.2.4.2 Mobile Termination, Assignment Retry .................................................................................................55

2.2.5
2.2.6
2.2.7
2.2.8

Mobile to Mobile Calls......................................................................................................................58

Emergency Calls .................................................................................................................................58
Test Calls..............................................................................................................................................58
BS Initiated Call Setup ......................................................................................................................58

2.2.8.1 BS Service Request..................................................................................................................................58

2.2.8.2 BS Service Response...............................................................................................................................59
2.2.8.3 BS Initiated Call Setup Example..............................................................................................................59

2.3
A1 INTERFACE CALL CLEARING PROCEDURES........................................................................................61
2.3.1
Call Clearing Initiated by the MS or BS ........................................................................................61
2.3.1.1
2.3.1.2
2.3.1.3
2.3.1.4
2.3.1.5
2.3.1.6
2.3.1.7

2.3.2
2.3.2.1
2.3.2.2
2.3.2.3
2.3.2.4

2.3.3
2.3.4
2.3.5

Successful Clear Scenarios.......................................................................................................................61

Unsuccessful Call Clearing Procedures....................................................................................................61
UNUSED SECTION...............................................................................................................................61
UNUSED SECTION...............................................................................................................................61
Clear Request...........................................................................................................................................61
Clear Command .......................................................................................................................................62
Clear Complete........................................................................................................................................62

Call Clearing Initiated by the MSC ................................................................................................63

Scenario 1 - Clear from the Network.......................................................................................................63
UNUSED SECTION...............................................................................................................................63
Call clearing via Clear Command .............................................................................................................63
Call Clearing when Tones/Announcements are Provided........................................................................64

Call Clearing Collision.....................................................................................................................64

Call Clearing for Handoff .................................................................................................................64
Call Flow Diagrams for Call Clear Operation .............................................................................64

2.3.5.1 Call Clear Initiated by MS.......................................................................................................................64

2.3.5.2 Call Clear Initiated by BS........................................................................................................................66
2.3.5.3 Call Clear Initiated by MSC ....................................................................................................................67

2.4
TRAFFIC CHANNEL RADIO LINK SUPERVISION........................................................................................68
2.5
SUPPORT OF SUPPLEMENTARY SERVICES...............................................................................................68
2.5.1
Support of TIA/EIA 664 Wireless Features.....................................................................................68
2.5.1.1
2.5.1.2
2.5.1.3
2.5.1.4

2.5.2
2.5.3

Flash with Information............................................................................................................................69

Flash with Information Ack ....................................................................................................................69
Feature Notification.................................................................................................................................70
Feature Notification Ack.........................................................................................................................70

DTMF Transmission Using In-band Tones.....................................................................................71

Burst DTMF Transmission.................................................................................................................71
ii

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

2.5.4
2.5.5

UNUSED SECTION ............................................................................................................................71

Supplementary Services Flow Charts.............................................................................................72

2.5.5.1 UNUSED SECTION...............................................................................................................................72

2.5.5.2 Call Waiting.............................................................................................................................................72
2.5.5.3 UNUSED SECTION...............................................................................................................................73
2.5.5.4 UNUSED SECTION...............................................................................................................................73
2.5.5.5 Three-Way Calling (Method 1)............................................................................................................73
2.5.5.6 Three-Way Calling - (Method 2).............................................................................................................74
2.5.5.7 UNUSED SECTION...............................................................................................................................74
2.5.5.8 UNUSED SECTION...............................................................................................................................74
2.5.5.9 Message Waiting Notification on the Paging Channel.............................................................................75
2.5.5.10 Message Waiting Notification on the Traffic Channel.........................................................................76

2.6
SUPPORT OF SHORT M ESSAGE SERVICE ...................................................................................................77
2.6.1
SMS Procedures..................................................................................................................................78
2.6.1.1 SMS - Mobile Originated Point-to-Point ................................................................................................78
2.6.1.2 SMS - Mobile Terminated Point-to-Point ..............................................................................................78
2.6.1.3 SMS - Broadcast......................................................................................................................................78

2.6.2
2.6.2.1
2.6.2.2
2.6.2.3
2.6.2.4

2.6.3

SMS Delivery on the Control Channel ...........................................................................................79

ADDS Page..............................................................................................................................................79
ADDS Transfer .......................................................................................................................................79
ADDS Page Ack......................................................................................................................................81
SMS Message Flow Using ADDS, Control Channel..............................................................................81

SMS Delivery on the Traffic Channel..............................................................................................89

2.6.3.1 ADDS Deliver .........................................................................................................................................89

2.6.3.2 ADDS Deliver Ack..................................................................................................................................89
2.6.3.3 SMS Message Flow Using ADDS, Traffic Channel ...............................................................................90

2.7
SUPPORT OF OVER-THE-A IR SERVICE PROVISIONING (OTASP) AND OVER THE A IR
PARAMETER A DMINISTRATION (OTAPA)............................................................................................................92
2.7.1
OTASP Support ...................................................................................................................................92
2.7.1.1
2.7.1.2
2.7.1.3
2.7.1.4
2.7.1.5
2.7.1.6
2.7.1.7
2.7.1.8
2.7.1.9

OTASP Call Setup ..................................................................................................................................93

OTASP Data Exchanges ..........................................................................................................................93
ADDS Deliver .........................................................................................................................................93
ADDS Deliver ACK................................................................................................................................93
SSD Update procedure............................................................................................................................93
Privacy Mode procedure.........................................................................................................................93
Rejection..................................................................................................................................................93
OTASP Call Clear ...................................................................................................................................93
OTASP Message Flow............................................................................................................................94

2.7.2. OTAPA support .........................................................................................................................................96

2.8
ERROR HANDLING .........................................................................................................................................97
2.8.1
Rejection...............................................................................................................................................97
2.8.1.1 Successful Operation...............................................................................................................................97
2.8.1.2 Failure Operation.....................................................................................................................................97

2.9
UNUSED SECTION.......................................................................................................................................97
2.10 M OBILE ORIGINATED CALLS W ITH PACA SERVICE .............................................................................98
2.10.1
PACA Service Support.......................................................................................................................99
2.10.1.1
2.10.1.2
2.10.1.3
2.10.1.4

PACA Command .................................................................................................................................99

PACA Command Ack..........................................................................................................................99
PACA Update....................................................................................................................................100
PACA Update Ack............................................................................................................................101

2.11 SUPPORT OF POSITION LOCATION SERVICE ..........................................................................................102

2.12 USER ZONES..................................................................................................................................................103
2.12.1
Invoking User Zone at Registration..............................................................................................103
2.12.2
Use of User Zones During Call Setup............................................................................................104
2.12.3
Changing User Zone During a Call..............................................................................................105
iii

TIA/EIA/IS-2001

2.12.3.1 User Zone Change ..............................................................................................................................105

2.13 CIRCUIT DATA CALLS................................................................................................................................106

2.13.1
Asynchronous Data and Group-3 Fax Services..........................................................................106

3
4

2.13.1.1 Data Only...........................................................................................................................................106

2.13.2
A5 Connections for Circuit Data Calls ........................................................................................106
2.13.3
Support for Handoffs of Asynchronous Data and G3 Fax Calls ..............................................107
2.14 PACKET DATA CALLS ................................................................................................................................108
2.14.1
Packet Data Assumptions................................................................................................................109
2.14.2
BS Initiated Call Setup ....................................................................................................................109

6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

2.14.2.1 BS Service Request.............................................................................................................................110

2.14.2.2 BS Service Response..........................................................................................................................110
2.14.2.3 BS Initiated Call Setup Example ........................................................................................................111

2.14.3
2.14.4
2.14.4.1
2.14.4.2
2.14.4.3
2.14.4.4

2.14.5
2.14.5.1
2.14.5.2
2.14.5.3
2.14.5.4
2.14.5.5

2.14.6
2.14.6.1
2.14.6.2
2.14.6.3
2.14.6.4

2.14.7

A8/A9 Interface Procedures............................................................................................................112

A8/A9 Interface Setup Procedures And Messages......................................................................112
A9-Setup-A8......................................................................................................................................112
A9-Connect-A8..................................................................................................................................113
A9-BS Service Request ......................................................................................................................114
A9-BS Service Response....................................................................................................................114

A8/A9 Interface Clearing Procedures and Messages ................................................................115

Successful Clearing Scenarios.............................................................................................................115
Unsuccessful A8 Interface Clearing Procedures.................................................................................116
A9-Release-A8...................................................................................................................................117
A9-Release-A8 Complete..................................................................................................................117
A9-Disconnect-A8.............................................................................................................................118

A8/A9 Interface Handoff Procedures and Messages ..................................................................119

A9-Air Link (AL) Connected.............................................................................................................119
A9-Air Link (AL) Connected Ack.....................................................................................................119
A9-Air Link (AL) Disconnected........................................................................................................120
A9-Air Link (AL) Disconnected Ack ................................................................................................120

A8/A9 Call Flows.............................................................................................................................121

2.14.7.1 Mobile Initiated Initial Call Setup and Mobile IP Registration Successful Operation ...................121
2.14.72 BS Initiated Call Release to Dormant State...........................................................................................123
2.14.7.3 MS Initiated Call Release to Dormant State......................................................................................125
2.14.7.4 MS Power Down ...............................................................................................................................127
2.14.7.5 PDSN Initiated Service Release..........................................................................................................129
2.14.7.6 MS Initiated Call Re-Activation from Dormant State.......................................................................130
2.14.7.7 Network Initiated Call Re-Activation from Dormant State...............................................................130
2.14.7. Mobile Terminated Packet Data Rejection During a Voice Call............................................................133
2.14.7.9 Dormant Handoff (Inter-BSC/Inter_PCF) - Mobile served by same PDSN .....................................134
2.14.7.10 Dormant Handoff (Inter-BSC/Inter_PCF) - Mobile served by a different PDSN.............................136
2.14.7.11 Soft / Softer Handoff..........................................................................................................................137
2.14.7.12 Inter-BS Hard Handoff (within the same PCF) .................................................................................138
2.14.7.13 Inter-PCF Hard Handoff (Within same PDSN).................................................................................141
2.14.7.14 Inter-PCF Hard Handoff (Within same PDSN) With Return On Failure..........................................144

2.15 A10/A11 INTERFACE PROCEDURES..........................................................................................................147

2.15.1
A10 Interface Setup Procedures.....................................................................................................148
2.15.1.1 A10 Connection Establishment..........................................................................................................148

2.15.2

A10 Interface Operational Procedures.........................................................................................150

2.15.2.1 A10 Connection Periodic Re-registration........................................................................................150

2.15.3

A10 Interface Release Procedures.................................................................................................150

2.15.3.1 A10 Connection Release PCF Requested ......................................................................................150

2.15.3.2 A10 Connection Release PDSN Initiated.......................................................................................151

2.15.4
2.15.5

A10 Interface Packet Accounting Procedures ............................................................................152

A10/A11 Interface Call Flows........................................................................................................152

2.15.5.1 Mobile Originated Packet Call Setup Successful Operation...........................................................152

iv

TIA/EIA/IS-2001

2.15.5.2 Mobile Originated Packet Call Setup Failure Operation.................................................................155

2.15.5.3 Mobile Originated Packet Call Setup With registration to alternate PDSN...................................157
2.15.5.4 Packet Data Service Session Clearing-PDSN Initiated.......................................................................160
2.15.5.5 Packet Data Service Session Clearing MSC Initiated......................................................................162
2.15.5.6 Packet Data Service Session Clearing MS Initiated.........................................................................163
2.15.5.7 Packet Data Service Session PDSN Initiated (Crossing A11-Registration Request and A11Registration Update)...........................................................................................................................................164
2.15.5.8 Inter-PCF Dormant Handoff Mobile Continues to be Served by the Serving PDSN.....................166
2.15.5.9 Inter-PCF Dormant Handoff Mobile Served by a New Target PDSN ...........................................170
2.15.5.10 Inter-PCF Hard Handoff Mobile Continues to be Served by the Serving PDSN ...........................174
2.15.5.11 Inter-BS Hard Handoff Mobile Served by a New Target PDSN ....................................................178

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

3.

RADIO RESOURCE MANAGEMENT............................................................................................................182

3.1
RADIO CHANNEL SUPERVISION ................................................................................................................182
3.1.1
Traffic Channel Radio Link Supervision......................................................................................182
3.1.2
Idle Channel Observation...............................................................................................................182
3.2
RADIO CHANNEL M ANAGEMENT ............................................................................................................182
3.2.1
Radio Channel Configuration Management...............................................................................182
3.2.2
Radio Traffic Channel Management.............................................................................................183
3.2.2.1
3.2.2.2
3.2.2.3
3.2.2.4
3.2.2.5

Radio Channel Allocation......................................................................................................................183

Radio Traffic Channel Release...............................................................................................................183
Radio Traffic Channel Power Control...................................................................................................183
UNUSED SECTION.............................................................................................................................183
Channel Encoding and Decoding............................................................................................................183

3.3
HANDOFF VIA MSC.....................................................................................................................................184
3.3.1
Introduction .......................................................................................................................................184
3.3.1.1 Recognition That a Handoff is Required by a BS..................................................................................184
3.3.1.2 Recognition That a Handoff is Required by the MSC ..........................................................................184
3.3.1.3 Concept of Designated Cell ...............................................................................................................184

3.3.2
3.3.2.1
3.3.2.2
3.3.2.3
3.3.2.4
3.3.2.5
3.3.2.6
3.3.2.7

3.3.3

Inter-BS Hard Handoff .....................................................................................................................185

Triggering Phase.....................................................................................................................................185
Target Determination Phase..................................................................................................................185
Resource Establishment.........................................................................................................................186
Execution Phase.....................................................................................................................................187
UNUSED SECTION.............................................................................................................................189
Call Clearing...........................................................................................................................................189
Handoff Failure Handling......................................................................................................................190

Intra-BS Handoff ...............................................................................................................................192

38

3.3.3.1 Handoff Performed................................................................................................................................192

39

3.4
HANDOFF VIA DIRECT BS-T O-BS SIGNALING........................................................................................193
3.4.1
A3 Interface Procedures and Messages........................................................................................193

40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

3.4.1.1 A3 Interface Setup Procedures and Messages.......................................................................................193

3.4.1.2 A3 Interface Operational Procedures and Messages .............................................................................194
3.4.1.3 A3 Interface Clearing Procedures and Messages ...................................................................................201

3.4.2
3.4.3

UNUSED SECTION ..........................................................................................................................203

A7 Interface Procedures and Messages........................................................................................203

3.4.3.1 A7 Interface Messages ..........................................................................................................................203

3.4.4
3.4.5
3.4.6
3.4.7
3.4.8
3.4.9
3.4.10

Soft/Softer Handoff Addition...........................................................................................................211

Soft/softer Handoff Removal............................................................................................................211
Cell Removal by a Target BS..........................................................................................................211
Call Clearing.....................................................................................................................................212
Handoff Performed............................................................................................................................212
Access Handoff and Channel Assignment into Soft Handoff.....................................................212
Soft/Softer Handoff of High Speed Packet Data..........................................................................213

3.4.10.1 Soft/Softer Handoff of Forward Link Bursts of Data........................................................................213

v

TIA/EIA/IS-2001

3.4.10.2 Soft/Softer Handoff of Reverse Link Bursts of Data.........................................................................214

3.5
HANDOFF CALL FLOWS..............................................................................................................................215
3.5.1
UNUSED SECTION ..........................................................................................................................215
3.5.2
Handoff Call Flows...........................................................................................................................215

3
4

3.5.2.1 Hard Handoff (via MSC).......................................................................................................................215

3.5.2.3 Soft/softer Handoff Using Direct BS to BS (A3 and A7) Connections ................................................223

5
6
7

4.

MOBILITY MANAGEMENT, AUTHENTICATION, AND PRIVACY.......................................................233

4.1
M OBILITY M ANAGEMENT ........................................................................................................................233
4.1.1
Paging.................................................................................................................................................233
4.1.2
Registration and Deregistration....................................................................................................233

8
9
10

4.1.2.1
4.1.2.2
4.1.2.3
4.1.2.4
4.1.2.5
4.1.2.6

11
12
13
14
15
16

Network Initiated Registration Procedures ...........................................................................................233

Mobile Initiated Registration.................................................................................................................234
Location Updating Request...................................................................................................................235
Location Updating Accept ....................................................................................................................235
Location Updating Reject ......................................................................................................................236
Power Down Registration at the End of a Call......................................................................................236

4.1.3
UNUSED SECTION ..........................................................................................................................236
4.1.4
UNUSED SECTION ..........................................................................................................................236
4.2
A UTHENTICATION AND PRIVACY ...........................................................................................................237
4.2.1
Shared Secret Data Procedures.....................................................................................................239

17
18
19
20

4.2.1.1
4.2.1.2
4.2.1.3
4.2.1.4
4.2.1.5

21
22
23
24
25

4.2.2

26

SSD Update Procedure - Successful Case.............................................................................................240

SSD Update Request.............................................................................................................................241
Base Station Challenge...........................................................................................................................241
Base Station Challenge Response..........................................................................................................242
SSD Update Response..........................................................................................................................242

Terminal Authentication .................................................................................................................243

4.2.2.1 Authentication Request.........................................................................................................................244

4.2.2.2 Authentication Response......................................................................................................................244

27
28

4.2.3

29

Parameter Update.............................................................................................................................245

4.2.3.1 Parameter Update Request....................................................................................................................245

4.2.3.2 Parameter Update Confirm....................................................................................................................246

30
31

4.2.4
4.2.5

32
33

4.2.5.1
4.2.5.2
4.2.5.3
4.2.5.4

34
35
36
37

Signaling Message Encryption ......................................................................................................247

Voice Privacy.....................................................................................................................................247
Privacy Mode Procedure.......................................................................................................................247
UNUSED SECTION.............................................................................................................................248
Privacy Mode Command.......................................................................................................................248
Privacy Mode Complete.......................................................................................................................249

39

4.3
PACKET DATA SECURITY CONSIDERATIONS ........................................................................................250
4.3.1
PCF-PDSN Security Association ...................................................................................................250

40

4.3.1.1 Computing Registration Authentication Extension Values ...................................................................250

38

41
42
43
44
45
46
47
48
49
50
51
52
53

5.

LAYERS 1 & 2 AND TERRESTRIAL FACILITY MANAGEMENT..........................................................252

5.1
PHYSICAL LAYER SPECIFICATION (LAYER 1) ........................................................................................252
5.2
ANSI SS7 TRANSPORT SPECIFICATION (LAYER 2)...............................................................................252
5.2.1
Field of Application .........................................................................................................................253
5.2.2
Message Transfer Part (MTP) Functions.....................................................................................253
5.2.2.1
5.2.2.2
5.2.2.3
5.2.2.4
5.2.2.5
5.2.2.6
5.2.2.7

5.2.3

General...................................................................................................................................................253
Level 1 (T1.111.2).................................................................................................................................253
Level 2 (T1.111.3).................................................................................................................................254
Level 3 (T1.111.4).................................................................................................................................254
Testing and Maintenance (T1.111.7) ....................................................................................................256
Interface Functions................................................................................................................................256
Overload Control (Message Throughput Congestion)..........................................................................257

SCCP Transport Layer Specification (SCCP Functions) .........................................................258

vi

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

5.2.3.1
5.2.3.2
5.2.3.3
5.2.3.4
5.2.3.5

5.2.4
5.2.4.1
5.2.4.2
5.2.4.3
5.2.4.4
5.2.4.5
5.2.4.6
5.2.4.7

Overview ...............................................................................................................................................258
Primitives (T1.112.1) ............................................................................................................................258
SCCP Messages (T1.112.2) ..................................................................................................................259
SCCP Formats and Codes (T1.112.3)...................................................................................................260
SCCP Procedures (T1.112.4) ................................................................................................................260

Use of the SCCP ................................................................................................................................262

The Direct Transfer Application Part ...................................................................................................262
The BS Management Application Part .................................................................................................262
Connection Establishment .....................................................................................................................262
Connection Release................................................................................................................................266
Abnormal SCCP Release .......................................................................................................................266
SCCP Reference Generation Philosophy ..............................................................................................269
SCCP Transfer of DTAP and BSMAP Messages ................................................................................269

5.3
USE OF ATM (LAYER 2) .............................................................................................................................274
5.3.1
Field of Application .........................................................................................................................274
5.3.2
ATM Layer..........................................................................................................................................274
5.3.3
ATM Adaptation Layer ....................................................................................................................274
5.4
NETWORK AND TRANSPORT PROTOCOLS..............................................................................................275
5.4.1
Signaling Connection Transport Protocol Options ..................................................................275
5.4.2
User Traffic Connection Transport Protocol Options...............................................................277
5.4.3
TCP Transport Protocol Usage......................................................................................................278
5.4.3.1 General Use of TCP ..............................................................................................................................278
5.4.3.2 Use of TCP for the A3 and A7 Interfaces.............................................................................................280
5.4.3.3 Use of TCP for the A9 Interface...........................................................................................................280

5.4.4
5.4.5

IP Network Protocol Usage............................................................................................................281

UDP Transport Protocol Usage.....................................................................................................281

5.4.5.1 UDP Transport Protocol Usage for the A11 Interface .........................................................................281
5.4.5.2 UDP Transport Protocol Usage for the A9 Interface ...........................................................................281

5.4.6

Mobile IP Protocol Usage...............................................................................................................282

30

5.4.6.1 Mobile IP Based Tunneling Protocol ....................................................................................................282

31

5.4.7
GRE Protocol Usage ........................................................................................................................284
5.5
TERRESTRIAL CIRCUIT M ANAGEMENT PROCEDURES .........................................................................286
5.5.1
Terrestrial Circuit Allocation/Deallocation...............................................................................286

32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

5.5.1.1 A2 Terrestrial Circuit Allocation...........................................................................................................286

5.5.1.2 A3 Connection Establishment ...............................................................................................................286

5.5.2

Blocking/Unblocking ......................................................................................................................287

5.5.2.1 A2 Terrestrial Circuit Blocking/Unblocking..........................................................................................287

5.5.3
5.5.3.1
5.5.3.2
5.5.3.3
5.5.3.4

5.5.4
5.5.4.1
5.5.4.2
5.5.4.3
5.5.4.4
5.5.4.5
5.5.4.6
5.5.4.7
5.5.4.8
5.5.4.9

5.5.5

Reset Circuit Procedure ..................................................................................................................290

A1 Reset Circuit (at the BS)..................................................................................................................290
A1 Reset Circuit Acknowledge (from MSC) ........................................................................................291
A1 Reset Circuit (at the MSC)..............................................................................................................292
A1 Reset Circuit Acknowledge (from BS) ............................................................................................292

Global System Reset .........................................................................................................................294

A1 Reset ................................................................................................................................................294
A1 Reset Acknowledge .........................................................................................................................295
A1 Global Reset Examples ....................................................................................................................296
UNUSED SECTION.............................................................................................................................301
UNUSED SECTION.............................................................................................................................301
UNUSED SECTION.............................................................................................................................301
A7-Reset................................................................................................................................................301
A7-Reset Acknowledge .........................................................................................................................301
A7 Global Reset Examples ....................................................................................................................302

Tandem Free Operation...................................................................................................................306

5.5.5.1 Transcoder Control Request..................................................................................................................306

5.5.5.2 Transcoder Control Acknowledge .........................................................................................................307
vii

TIA/EIA/IS-2001

5.5.6

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

6.

UNUSED SECTION ..........................................................................................................................307

MESSAGES, INFORMATION ELEMENTS, AND TIMER DEFINITIONS ..............................................308

6.1
M ESSAGE DEFINITIONS ..............................................................................................................................308
6.1.1
Generic Message Formats...............................................................................................................308
6.1.1.1 A1 Message Header...............................................................................................................................308
6.1.1.2 Message Body, Coding, and Ordering of Elements...............................................................................311
6.1.1.3 Forward Compatibility Guidelines........................................................................................................312

6.1.2

Call Processing Message Formats ................................................................................................316

6.1.2.1 Complete Layer 3 Information..............................................................................................................316

6.1.2.2 CM Service Request..............................................................................................................................317
6.1.2.3 Paging Request.......................................................................................................................................327
6.1.2.4 Paging Response....................................................................................................................................331
6.1.2.5 UNUSED SECTION.............................................................................................................................339
6.1.2.6 UNUSED SECTION.............................................................................................................................339
6.1.2.7 UNUSED SECTION.............................................................................................................................339
6.1.2.8 UNUSED SECTION.............................................................................................................................339
6.1.2.9 UNUSED SECTION.............................................................................................................................339
6.1.2.10 Connect ..............................................................................................................................................340
6.1.2.11 UNUSED SECTION .........................................................................................................................340
6.1.2.12 Progress..............................................................................................................................................341
6.1.2.13 UNUSED SECTION .........................................................................................................................342
6.1.2.14 UNUSED SECTION .........................................................................................................................342
6.1.2.15 Assignment Request...........................................................................................................................343
6.1.2.16 Assignment Complete........................................................................................................................349
6.1.2.17 Assignment Failure.............................................................................................................................351
6.1.2.18 UNUSED SECTION .........................................................................................................................351
6.1.2.19 UNUSED SECTION .........................................................................................................................352
6.1.2.20 Clear Request .....................................................................................................................................353
6.1.2.21 Clear Command..................................................................................................................................355
6.1.2.22 Clear Complete...................................................................................................................................357
6.1.2.23 UNUSED SECTION .........................................................................................................................357
6.1.2.24 Alert With Information ......................................................................................................................358
6.1.2.25 UNUSED SECTION .........................................................................................................................359
6.1.2.26 UNUSED SECTION .........................................................................................................................359
6.1.2.27 UNUSED SECTION .........................................................................................................................359
6.1.2.28 BS Service Request.............................................................................................................................359
6.1.2.29 BS Service Response..........................................................................................................................361

6.1.3

Supplementary Services Message Formats..................................................................................363

6.1.3.1 UNUSED SECTION.............................................................................................................................363

6.1.3.2 UNUSED SECTION.............................................................................................................................363
6.1.3.3 UNUSED SECTION.............................................................................................................................363
6.1.3.4 UNUSED SECTION.............................................................................................................................363
6.1.3.5 UNUSED SECTION.............................................................................................................................363
6.1.3.6 UNUSED SECTION.............................................................................................................................363
6.1.3.7 Flash with Information..........................................................................................................................364
6.1.3.8 Flash with Information Ack ..................................................................................................................367
6.1.3.9 Feature Notification...............................................................................................................................368
6.1.3.10 Feature Notification Ack....................................................................................................................372
6.1.3.11 PACA Command ...............................................................................................................................373
6.1.3.12 PACA Command Ack........................................................................................................................374
6.1.3.13 PACA Update....................................................................................................................................375
6.1.3.14 PACA Update Ack............................................................................................................................378

6.1.4

Mobility Management Message Formats.....................................................................................379

6.1.4.1 Authentication Request.........................................................................................................................379

viii

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

6.1.4.2 Authentication Response......................................................................................................................383

6.1.4.3 User Zone Update................................................................................................................................386
6.1.4.4 SSD Update Request.............................................................................................................................387
6.1.4.5 Base Station Challenge...........................................................................................................................388
6.1.4.6 Base Station Challenge Response..........................................................................................................389
6.1.4.7 SSD Update Response..........................................................................................................................390
6.1.4.8 Location Updating Request...................................................................................................................391
6.1.4.9 Location Updating Accept ....................................................................................................................397
6.1.4.10 Location Updating Reject...................................................................................................................398
6.1.4.11 Parameter Update Request.................................................................................................................399
6.1.4.12 Parameter Update Confirm ................................................................................................................399
6.1.4.13 UNUSED SECTION .........................................................................................................................400
6.1.4.14 UNUSED SECTION .........................................................................................................................400
6.1.4.15 UNUSED SECTION .........................................................................................................................400
6.1.4.16 UNUSED SECTION .........................................................................................................................400
6.1.4.17 UNUSED SECTION .........................................................................................................................400
6.1.4.18 Privacy Mode Command ...................................................................................................................400
6.1.4.19 Privacy Mode Complete....................................................................................................................402

6.1.5

Handoff Message Formats...............................................................................................................403

6.1.5.1 UNUSED SECTION.............................................................................................................................403

6.1.5.2 UNUSED SECTION.............................................................................................................................403
6.1.5.3 UNUSED SECTION.............................................................................................................................403
6.1.5.4 Handoff Required ..................................................................................................................................404
6.1.5.5 Handoff Request....................................................................................................................................414
6.1.5.6 Handoff Request Acknowledge .............................................................................................................425
6.1.5.7 Handoff Failure......................................................................................................................................430
6.1.5.8 Handoff Command ................................................................................................................................431
6.1.5.9 Handoff Required Reject .......................................................................................................................439
6.1.5.10 Handoff Commenced..........................................................................................................................440
6.1.5.11 Handoff Complete..............................................................................................................................441
6.1.5.12 Handoff Performed.............................................................................................................................442
6.1.5.13 UNUSED SECTION .........................................................................................................................443
6.1.5.14 UNUSED SECTION .........................................................................................................................443

6.1.6

Facility Management Message Formats ......................................................................................444

6.1.6.1 UNUSED SECTION.............................................................................................................................444

6.1.6.2 Block......................................................................................................................................................444
6.1.6.3 Block Acknowledge ...............................................................................................................................446
6.1.6.4 Unblock .................................................................................................................................................446
6.1.6.5 Unblock Acknowledge...........................................................................................................................448
6.1.6.6 Reset ......................................................................................................................................................449
6.1.6.7 Reset Acknowledge ...............................................................................................................................450
6.1.6.8 Reset Circuit ..........................................................................................................................................451
6.1.6.9 Reset Circuit Acknowledge ...................................................................................................................453
6.1.6.10 Transcoder Control Request .............................................................................................................454
6.1.6.11 Transcoder Control Acknowledge.....................................................................................................454
6.1.6.12 UNUSED SECTION .........................................................................................................................455
6.1.6.13 UNUSED SECTION .........................................................................................................................455
6.1.6.14 UNUSED SECTION .........................................................................................................................455

6.1.7
6.1.7.1
6.1.7.2
6.1.7.3
6.1.7.4
6.1.7.5

6.1.8

Application Data Delivery Service (ADDS) Message Formats................................................456

ADDS Page............................................................................................................................................456
ADDS Transfer .....................................................................................................................................460
ADDS Deliver .......................................................................................................................................465
ADDS Page Ack....................................................................................................................................468
ADDS Deliver Ack................................................................................................................................471

Error Handling Messages ...............................................................................................................472

ix

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

6.1.8.1 Rejection................................................................................................................................................472

6.1.9

A3 Interface Message Formats .......................................................................................................475

6.1.9.1 A3-Connect ...........................................................................................................................................475

6.1.9.2 A3-Connect Ack....................................................................................................................................479
6.1.9.3 A3-Remove............................................................................................................................................481
6.1.9.4 A3-Remove Ack....................................................................................................................................484
6.1.9.5 A3-Drop ................................................................................................................................................486
6.1.9.6 A3-Propagation Delay Measurement Report .......................................................................................488
6.1.9.7 A3-IS-95 FCH Forward ........................................................................................................................490
6.1.9.8 A3-IS-95 FCH Reverse.........................................................................................................................491
6.1.9.9 A3-IS-2000 FCH Forward ....................................................................................................................492
6.1.9.10 A3-IS-2000 FCH Reverse.................................................................................................................493
6.1.9.11 A3-Physical Transition Directive ......................................................................................................494
6.1.9.12 A3-PhysicalTransition Directive Ack................................................................................................497
6.1.9.13 A3-IS-2000 DCCH Forward..............................................................................................................500
6.1.9.14 A3-IS-2000 DCCH Reverse..............................................................................................................501
6.1.9.15 A3-Traffic Channel Status .................................................................................................................502
6.1.9.16 A3-IS-2000 SCH Forward .................................................................................................................505
6.1.9.17 A3-IS-2000 SCH Reverse.................................................................................................................506

6.1.10

A9 Interface Message Formats .......................................................................................................507

6.1.10.1
6.1.10.2
6.1.10.3
6.1.10.4
6.1.10.5
6.1.10.6
6.1.10.7
6.1.10.8
6.1.10.9
6.1.10.10
6.1.10.11

6.1.11

A11 Interface Message Formats.....................................................................................................530

6.1.11.1
6.1.11.2
6.1.11.3
6.1.11.4

6.1.12

A9-Setup-A8......................................................................................................................................507
A9-Connect-A8..................................................................................................................................511
A9-Disconnect-A8.............................................................................................................................514
A9-Release-A8...................................................................................................................................517
A9-Release-A8 Complete..................................................................................................................520
A9-BS Service Request ......................................................................................................................521
A9-BS Service Response....................................................................................................................523
A9-AL Connected..............................................................................................................................524
A9-AL Connected Ack ......................................................................................................................526
A9-AL Disconnected .........................................................................................................................527
A9-AL Disconnected Ack..................................................................................................................529
A11-Registration Request..................................................................................................................530
A11-Registration Reply .....................................................................................................................534
A11-Registration Update...................................................................................................................538
A11-Registration Acknowledge .........................................................................................................541

A7 Interface Message Formats .......................................................................................................544

6.1.12.1
6.1.12.2
6.1.12.3
6.1.12.4
6.1.12.5
6.1.12.6
6.1.12.7
6.1.12.8
6.1.12.9
6.1.12.10
6.1.12.11
6.1.12.12
6.1.12.13
6.1.12.14
6.1.12.15
6.1.12.16
6.1.12.17
6.1.12.18

A7-Handoff Request..........................................................................................................................544
A7-Handoff Request Ack ..................................................................................................................554
A7-Drop Target .................................................................................................................................559
A7-Drop Target Ack..........................................................................................................................561
A7-Target Removal Request..............................................................................................................563
A7-Target Removal Response...........................................................................................................566
UNUSED SECTION .........................................................................................................................568
UNUSED SECTION .........................................................................................................................568
UNUSED SECTION .........................................................................................................................568
A7- Source Transfer Performed .........................................................................................................569
A7-Reset ............................................................................................................................................571
A7-Reset Acknowledge......................................................................................................................572
A7-Paging Channel Message Transfer ...............................................................................................573
A7-Paging Channel Message Transfer Ack........................................................................................576
A7-Access Channel Message Transfer ..............................................................................................577
A7-Access Channel Message Transfer Ack.......................................................................................579
A7-Burst Request ..............................................................................................................................580
A7-Burst Response............................................................................................................................586
x

TIA/EIA/IS-2001

6.1.12.19 A7-Burst Commit ..............................................................................................................................590

6.2
INFORMATION ELEMENT DEFINITIONS..................................................................................................594
6.2.1
Generic Information Element Encoding.......................................................................................594

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

6.2.1.1
6.2.1.2
6.2.1.3
6.2.1.4
6.2.1.5
6.2.1.6

6.2.2

Conventions...........................................................................................................................................594
Information Element Identifiers.............................................................................................................595
A1 Interface Information Element Types .............................................................................................610
A3 and A7 Interface Information Elements...........................................................................................613
Additional Coding and Interpretation Rules for Information Elements ................................................613
Cross Reference of Information Elements With Messages ...................................................................615

Information Elements .......................................................................................................................636

6.2.2.1 Message Discrimination ........................................................................................................................636

6.2.2.2 Data Link Connection Identifier (DLCI)...............................................................................................637
6.2.2.3 Length Indicator (LI) .............................................................................................................................637
6.2.2.4 Message Type.......................................................................................................................................638
6.2.2.5 Message Type II ...................................................................................................................................642
6.2.2.6 Channel Number....................................................................................................................................644
6.2.2.7 Channel Type........................................................................................................................................645
6.2.2.8 RF Channel Identity..............................................................................................................................647
6.2.2.9 SID.........................................................................................................................................................649
6.2.2.10 IS-95 Channel Identity.......................................................................................................................650
6.2.2.11 UNUSED SECTION .........................................................................................................................651
6.2.2.12 Encryption Information .....................................................................................................................652
6.2.2.13 Voice Privacy Request .......................................................................................................................654
6.2.2.14 Physical Channel Info ........................................................................................................................655
6.2.2.15 Classmark Information Type 2..........................................................................................................657
6.2.2.16 Mobile Identity..................................................................................................................................661
6.2.2.17 Slot Cycle Index.................................................................................................................................664
6.2.2.18 Priority...............................................................................................................................................664
6.2.2.19 Cause..................................................................................................................................................667
6.2.2.20 Cell Identifier......................................................................................................................................671
6.2.2.21 Cell Identifier List ..............................................................................................................................674
6.2.2.22 Circuit Identity Code .........................................................................................................................674
6.2.2.23 Circuit Identity Code Extension.........................................................................................................675
6.2.2.24 Unused ...............................................................................................................................................675
6.2.2.25 Downlink Radio Environment............................................................................................................676
6.2.2.26 Unused ...............................................................................................................................................677
6.2.2.27 Unused ...............................................................................................................................................677
6.2.2.28 Unused ...............................................................................................................................................677
6.2.2.29 Unused ...............................................................................................................................................677
6.2.2.30 PDSN IP Address ..............................................................................................................................678
6.2.2.31 Handoff Power Level .........................................................................................................................679
6.2.2.32 USER Zone ID...................................................................................................................................680
6.2.2.33 Reverse Pilot Gating Rate..................................................................................................................681
6.2.2.34 IS-2000 Channel Identity...................................................................................................................682
6.2.2.35 Response Request..............................................................................................................................684
6.2.2.36 IS-95 MS Measured Channel Identity...............................................................................................684
6.2.2.37 Calling Party ASCII Number ............................................................................................................685
6.2.2.38 Layer 3 Information ...........................................................................................................................688
6.2.2.39 Protocol Discriminator.......................................................................................................................689
6.2.2.40 Reserved-Octet...................................................................................................................................689
6.2.2.41 Location Updating Type....................................................................................................................690
6.2.2.42 Authentication Confirmation Parameter (RANDC) ..........................................................................691
6.2.2.43 Location Area Identification...............................................................................................................692
6.2.2.44 Reject Cause.......................................................................................................................................693
6.2.2.45 Authentication Challenge Parameter (RAND/RANDU/RANDBS/RANDSSD) ..............................694
xi

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

6.2.2.46
6.2.2.47
6.2.2.48
6.2.2.49
6.2.2.50
6.2.2.51
6.2.2.52
6.2.2.53
6.2.2.54
6.2.2.55
6.2.2.56
6.2.2.57
6.2.2.58
6.2.2.59
6.2.2.60
6.2.2.61
6.2.2.62
6.2.2.63
6.2.2.64
6.2.2.65
6.2.2.66
6.2.2.67
6.2.2.68
6.2.2.69
6.2.2.70
6.2.2.71
6.2.2.72
6.2.2.73
6.2.2.74
6.2.2.75
6.2.2.76
6.2.2.77
6.2.2.78
6.2.2.79
6.2.2.80
6.2.2.81
6.2.2.82
6.2.2.83
6.2.2.84
6.2.2.86
6.2.2.87
6.2.2.88
6.2.2.89
6.2.2.90
6.2.2.91
6.2.2.92
6.2.2.93
6.2.2.94
6.2.2.95
6.2.2.96
6.2.2.97
6.2.2.98
6.2.2.99
6.2.2.100
6.2.2.102

Authentication Response Parameter (AUTHR/AUTHU/AUTHBS) ...............................................695

Authentication Parameter COUNT ...................................................................................................696
Message Waiting Indication ...............................................................................................................697
Progress Indicator...............................................................................................................................698
Signal .................................................................................................................................................700
CM Service Type...............................................................................................................................704
Called Party BCD Number ................................................................................................................705
Calling Party BCD Number ...............................................................................................................708
Quality of Service Parameters............................................................................................................710
Cause Layer 3.....................................................................................................................................711
Forward Burst Radio Info..................................................................................................................715
Reverse Burst Radio Info...................................................................................................................717
Transcoder Mode...............................................................................................................................719
UNUSED SECTION .........................................................................................................................719
Power Down Indicator.......................................................................................................................720
Registration Type..............................................................................................................................721
Tag......................................................................................................................................................723
Hard Handoff Parameters...................................................................................................................724
UNUSED SECTION .........................................................................................................................725
Software Version................................................................................................................................726
Service Option....................................................................................................................................727
ADDS User Part ................................................................................................................................728
IS-2000 Service Configuration Record ...............................................................................................729
IS-2000 Non-Negotiable Service Configuration Record.....................................................................730
IS-2000 Mobile Capabilities ..............................................................................................................731
Protocol Type....................................................................................................................................734
MS Information Records....................................................................................................................735
Extended Handoff Direction Parameters............................................................................................736
Forward Layer 3 IS-2000 FCH/DCCH Data.....................................................................................737
Reverse Layer 3 IS-2000 FCH/DCCH Data......................................................................................739
UNUSED SECTION .........................................................................................................................747
Forward Layer 3 IS-2000 SCH Data..................................................................................................748
Reverse Layer 3 IS-2000 SCH Data...................................................................................................750
CDMA Serving One Way Delay .......................................................................................................753
UNUSED SECTION .........................................................................................................................753
UNUSED SECTION .........................................................................................................................753
Radio Environment and Resources.....................................................................................................754
Neighbor List......................................................................................................................................756
UNUSED SECTION .........................................................................................................................756
UNUSED SECTION .........................................................................................................................756
UNUSED SECTION .........................................................................................................................756
UNUSED SECTION .........................................................................................................................757
Cell Information Record.....................................................................................................................757
A3 Signaling Address .........................................................................................................................759
SDU ID ..............................................................................................................................................760
UNUSED SECTION .........................................................................................................................760
UNUSED SECTION .........................................................................................................................760
UNUSED SECTION .........................................................................................................................760
UNUSED SECTION .........................................................................................................................760
A3 Traffic Circuit ID .........................................................................................................................761
A7 Control .........................................................................................................................................762
Call Connection Reference .................................................................................................................763
PMC Cause........................................................................................................................................764
UNUSED SECTION .........................................................................................................................765
UNUSED SECTION .........................................................................................................................766
xii

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

6.2.2.103
6.2.2.104
6.2.2.105
6.2.2.106
6.2.2.107
6.2.2.108
6.2.2.109
6.2.2.110
6.2.2.111
6.2.2.112
6.2.2.113
6.2.2.114
6.2.2.115
6.2.2.116
6.2.2.117
6.2.2.118
6.2.2.119
6.2.2.120
6.2.2.121
6.2.2.122
6.2.2.123
6.2.2.124
6.2.2.125
6.2.2.126
6.2.2.127
6.2.2.128
6.2.2.129
6.2.2.130
6.2.2.131
6.2.2.132
6.2.2.133
6.2.2.134
6.2.2.135
6.2.2.136
6.2.2.137
6.2.2.138
6.2.2.139
6.2.2.140
6.2.2.141
6.2.2.142
6.2.2.143
6.2.2.144
6.2.2.145
6.2.2.146
6.2.2.147
6.2.2.148
6.2.2.149
6.2.2.150
6.2.2.151
6.2.2.152
6.2.2.153
6.2.2.154
6.2.2.155
6.2.2.156
6.2.2.157

UNUSED SECTION .........................................................................................................................766

UNUSED SECTION .........................................................................................................................766
Called Party ASCII Number ..............................................................................................................766
Band Class..........................................................................................................................................767
UNUSED SECTION .........................................................................................................................767
Correlation ID ....................................................................................................................................768
Service Configuration Record.............................................................................................................768
IS-2000 Cause Value .........................................................................................................................769
UNUSED SECTION .........................................................................................................................769
UNUSED SECTION .........................................................................................................................769
UNUSED SECTION .........................................................................................................................769
Authentication Event .........................................................................................................................770
UNUSED SECTION .........................................................................................................................770
UNUSED SECTION .........................................................................................................................770
UNUSED SECTION .........................................................................................................................770
UNUSED SECTION .........................................................................................................................770
One way Propagation Delay Record..................................................................................................771
Forward Layer 3 Data........................................................................................................................772
Reverse Layer 3 Data.........................................................................................................................775
UNUSED SECTION .........................................................................................................................778
UNUSED SECTION .........................................................................................................................778
UNUSED SECTION .........................................................................................................................778
BSC ID...............................................................................................................................................779
UNUSED SECTION .........................................................................................................................779
UNUSED SECTION .........................................................................................................................779
CDMA Long Code Transition Info ...................................................................................................780
UNUSED SECTION .........................................................................................................................780
UNUSED SECTION .........................................................................................................................780
UNUSED SECTION .........................................................................................................................780
Channel Element ID ...........................................................................................................................781
UNUSED SECTION .........................................................................................................................781
Message CRC.....................................................................................................................................782
UNUSED SECTION .........................................................................................................................782
UNUSED SECTION .........................................................................................................................782
Authentication Data...........................................................................................................................783
UNUSED SECTION .........................................................................................................................783
UNUSED SECTION .........................................................................................................................783
UNUSED SECTION .........................................................................................................................783
Channel Element Status......................................................................................................................783
Cause List...........................................................................................................................................784
Privacy Info........................................................................................................................................784
A3 Connect Information ....................................................................................................................786
A3 Connect Ack Information.............................................................................................................790
A3 Remove Information.....................................................................................................................792
A3 Drop Information.........................................................................................................................794
Circuit Group .....................................................................................................................................796
PACA Timestamp .............................................................................................................................798
PACA Order ......................................................................................................................................799
PACA Reorigination Indicator...........................................................................................................800
Air Interface Message ........................................................................................................................801
Layer 2 Ack Request/Results.............................................................................................................802
A11 Message Type............................................................................................................................803
Flags ...................................................................................................................................................803
Lifetime ..............................................................................................................................................804
Home Address....................................................................................................................................804
xiii

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

6.2.2.158
6.2.2.159
6.2.2.160
6.2.2.161
6.2.2.162
6.2.2.163
6.2.2.164
6.2.2.165
6.2.2.166
6.2.2.167
6.2.2.168
6.2.2.169
6.2.2.170
6.2.2.171
6.2.2.172
6.2.2.173
6.2.2.174
6.2.2.175
6.2.2.176
6.2.2.177
6.2.2.178
6.2.2.179
6.2.2.180

Home Agent .......................................................................................................................................805

Care-of-Address.................................................................................................................................805
Identification ......................................................................................................................................806
Code ...................................................................................................................................................807
Status..................................................................................................................................................808
Mobile-Home Authentication Extension ...........................................................................................809
Registration Update Authentication Extension..................................................................................810
Session Specific Extension .................................................................................................................811
Vendor/Organization Specific Extension............................................................................................813
A9 Message Type..............................................................................................................................815
CON_REF..........................................................................................................................................815
A9 BSC_ID........................................................................................................................................816
A8_Traffic_ID ...................................................................................................................................817
A9 Indicators......................................................................................................................................818
A7 Originating ID...............................................................................................................................819
A7 Destination ID..............................................................................................................................820
A3 Originating ID...............................................................................................................................821
A3 Destination ID..............................................................................................................................822
IS-2000 Power Control Info...............................................................................................................823
IS-2000 Forward Power Control Mode.............................................................................................825
IS-2000 FPC Gain Ratio Info.............................................................................................................826
Data Count .........................................................................................................................................828
IS-2000 Mobile Pilot Gain.................................................................................................................828

6.3
TIMER DEFINITIONS ...................................................................................................................................829
6.3.1
Call Processing Timers....................................................................................................................835
6.3.1.1 T10 ........................................................................................................................................................835
6.3.1.2 T20 ........................................................................................................................................................835
6.3.1.3 UNUSED SECTION.............................................................................................................................835
6.3.1.4 UNUSED SECTION.............................................................................................................................835
6.3.1.5 T300 ......................................................................................................................................................835
6.3.1.6 T301 ......................................................................................................................................................835
6.3.1.7 UNUSED SECTION.............................................................................................................................835
6.3.1.8 T303 ......................................................................................................................................................835
6.3.1.9 T306 ......................................................................................................................................................835
6.3.1.10 UNUSED SECTION .........................................................................................................................835
6.3.1.11 UNUSED SECTION .........................................................................................................................836
6.3.1.12 UNUSED SECTION .........................................................................................................................836
6.3.1.13 T311...................................................................................................................................................836
6.3.1.14 UNUSED SECTION .........................................................................................................................836
6.3.1.15 UNUSED SECTION .........................................................................................................................836
6.3.1.16 T315...................................................................................................................................................836
6.3.1.17 UNUSED SECTION .........................................................................................................................836
6.3.1.18 UNUSED SECTION .........................................................................................................................836
6.3.1.19 T3231.................................................................................................................................................836
6.3.1.20 T3113.................................................................................................................................................836
6.3.1.21 T3230.................................................................................................................................................836
6.3.1.22 T3280.................................................................................................................................................837
6.3.1.23 Twaitho..............................................................................................................................................837
6.3.1.24 Trp .....................................................................................................................................................837
6.3.1.25 Tregreq ...............................................................................................................................................837
6.3.1.26 Tregupd..............................................................................................................................................837

6.3.2

Supplementary Services Timers......................................................................................................838

6.3.2.1 UNUSED SECTION.............................................................................................................................838

6.3.2.2 UNUSED SECTION.............................................................................................................................838
6.3.2.3 T62 ........................................................................................................................................................838
xiv

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

6.3.2.4 T63 ........................................................................................................................................................838

6.3.3

Mobility Management Timers.........................................................................................................839

6.3.3.1 T3210 ....................................................................................................................................................839

6.3.3.2 T3220 ....................................................................................................................................................839
This BS timer is started when the Parameter Update Request message is sent, and is stopped when the
Parameter Update Confirm message is received. ................................................................................................839
6.3.3.3 UNUSED SECTION.............................................................................................................................839
6.3.3.4 T3260 ....................................................................................................................................................839
6.3.3.5 T3270 ....................................................................................................................................................839
6.3.3.6 T3271 ....................................................................................................................................................839
6.3.3.7 UNUSED SECTION.............................................................................................................................839

6.3.4

Handoff Timers...................................................................................................................................840

6.3.4.1 T7 ..........................................................................................................................................................840
6.3.4.2 T8 ..........................................................................................................................................................840
6.3.4.3 T9 ..........................................................................................................................................................840
6.3.4.4 T11 ........................................................................................................................................................840
6.3.4.5 UNUSED SECTION.............................................................................................................................840
6.3.4.6 UNUSED SECTION.............................................................................................................................840
6.3.4.7 UNUSED SECTION.............................................................................................................................840
6.3.4.8 UNUSED SECTION.............................................................................................................................840
6.3.4.9 UNUSED SECTION.............................................................................................................................840
6.3.4.10 UNUSED SECTION .........................................................................................................................841
6.3.4.11 UNUSED SECTION .........................................................................................................................841

6.3.5

Facility Management Timers..........................................................................................................842

6.3.5.1 T1 ..........................................................................................................................................................842
6.3.5.2 T2 ..........................................................................................................................................................842
6.3.5.3 T4 ..........................................................................................................................................................842
6.3.5.4 UNUSED SECTION.............................................................................................................................842
6.3.5.5 UNUSED SECTION.............................................................................................................................842
6.3.5.6 T12 ........................................................................................................................................................843
6.3.5.7 T13 ........................................................................................................................................................843
6.3.5.8 T16 ........................................................................................................................................................843
6.3.5.9 T309 ......................................................................................................................................................843
6.3.5.10 UNUSED SECTION .........................................................................................................................843

6.3.6

Timers Used on the A3 and A7 Interfaces.....................................................................................844

6.3.6.1 Tbstact...................................................................................................................................................844
6.3.6.2 Tbstcom.................................................................................................................................................844
6.3.6.3 UNUSED SECTION.............................................................................................................................844
6.3.6.4 UNUSED SECTION.............................................................................................................................844
6.3.6.5 UNUSED SECTION.............................................................................................................................844
6.3.6.6 UNUSED SECTION.............................................................................................................................845
6.3.6.7 UNUSED SECTION.............................................................................................................................845
6.3.6.8 Tconn3...................................................................................................................................................845
6.3.6.9 Tdiscon3................................................................................................................................................845
6.3.6.10 Tdrptgt ...............................................................................................................................................845
6.3.6.11 Thoreq................................................................................................................................................845
6.3.6.12 Ttgtrmv ..............................................................................................................................................845
6.3.6.13 Tchanstat............................................................................................................................................845
6.3.6.14 Tphysical ...........................................................................................................................................845
6.3.6.15 UNUSED SECTION .........................................................................................................................846
6.3.6.16 Tacm...................................................................................................................................................846
6.3.6.17 Tpcm ..................................................................................................................................................846

6.3.7

Timers Used on the A9 Interface.....................................................................................................847

6.3.7.1 TA8-setup .............................................................................................................................................847

6.3.7.2 Tdiscon9................................................................................................................................................847
xv

TIA/EIA/IS-2001

6.3.7.3
6.3.7.4
6.3.7.5
6.3.7.6
6.3.7.7

1
2
3
4
5
6

8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

39
40
41
42
43
44
45
46
47
48
49
50

OPTIONAL FEATURES ANNEX ....................................................................................................................854

B.1

37
38

SUPPLEMENTARY SERVICES ANNEX.......................................................................................................848

A.1
FEATURE A CTIVATION AND DEACTIVATION .......................................................................................848
A.1.1
Feature Activation/Deactivation in Idle Mode...........................................................................848
A.1.2
Feature Activation/Deactivation While in a Call ......................................................................848
A.2
CALL BARRING.............................................................................................................................................849
A.2.1
Call Barring Incoming.....................................................................................................................849
A.2.2
Call Barring Outgoing ....................................................................................................................849
A.3
CALLING NUMBER ID PRESENTATION / RESTRICTION ........................................................................851
A.3.1
CNIP/CNIR for Mobile Terminations............................................................................................851
A.3.2
CNIR on Mobile Originated Calls.................................................................................................851
A.4
VOICE A NSWERING .....................................................................................................................................851
A.6
DISTINCTIVE RINGING................................................................................................................................851
A.7
BASIC REMOTE CALL FORWARDING .......................................................................................................851
A.8
EMERGENCY SERVICE ..................................................................................................................................851
A.9
A UTONOMOUS REGISTRATION.................................................................................................................852
A.10 HOTLINING...................................................................................................................................................852
A.11 CARRIER A CCESS .........................................................................................................................................852
A.12 A UTHORIZED ROAMING ............................................................................................................................852
A.13 13KBPS VOICE SERVICE ..............................................................................................................................852
A.14 CALL FORWARDING....................................................................................................................................852
A.14.1 Call Forwarding Unconditional (CFU) IS53A 5.5 ....................................................................852
A.14.2 Call Forwarding When Busy (CFB) IS53A 5.2 ...........................................................................852
A.14.3 Call Forwarding When No Answer or Not Available (CFNA) IS53A 5.4..............................852
A.14.4 Call Forwarding of Call Waiting IS53A 5.2.4 ............................................................................852
A.15 CALL DELIVERY ..........................................................................................................................................853
A.16 LAWFULLY A UTHORIZED W IRETAP ......................................................................................................853
A.17 E911 PHASE I AND PHASE 2........................................................................................................................853
A.18 A NSWER HOLDING......................................................................................................................................853
A.19 A DVICE OF CHARGE ....................................................................................................................................853
A.20 USER SELECTIVE CALL FORWARDING ....................................................................................................853

36

Trel9 ......................................................................................................................................................847
Talc9......................................................................................................................................................847
Twaitho9 ...............................................................................................................................................847
Tbsreq9..................................................................................................................................................847
Tald9......................................................................................................................................................847

SOURCE TRANSFER NOTIFICATION .........................................................................................................854

CALL DIAGRAMS => SUPPORT OF EVRC ...............................................................................................855

C.1
C.2
C.3
C.4
C.5
C.6
C.7
C.8
C.9
C.10
C.11
C.12

13K REQUESTED 13K GRANTED (ORIGINATION)..............................................................................855

13K (8000H) REQUESTED EVRC GRANTED (ORIGINATION) ............................................................856
EVRC REQUESTED EVRC GRANTED (ORIGINATION) .......................................................................857
EVRC REQUESTED 13K (8000H) GRANTED (ORIGINATION) ............................................................858
13K (8000H) REQUESTED 13K GRANTED (ORIGINATION)................................................................859
13K (8000H) OR EVRC PAGED 13K (8000H) GRANTED (TERMINATION)..........................................860
13K (8000H) PAGED 13K GRANTED (TERMINATION)........................................................................861
13K (8000H) OR EVRC PAGED EVRC GRANTED (TERMINATION)...................................................862
EVRC PAGED EVRC GRANTED (TERMINATION) ................................................................................863
EVRC PAGED 13K (8000H) GRANTED (TERMINATION) ......................................................................864
SERVICE OPTION CHANGE FROM EVRC TO 13K ...................................................................................865
SERVICE OPTION CHANGE FROM 13K TO EVRC...................................................................................866

51

xvi

TIA/EIA/IS-2001

1
2

Table of Figures

FIGURE 1- 1 - DOCUMENT CONVENTION EXAMPLE: CALL CLEAR INITIATED BY MS........................................5

FIGURE 1- 2 - REFERENCE M ODEL FOR DIGITAL A IR INTERFACES .......................................................................23

FIGURE 1- 3 - MSC-BS INTERFACE FUNCTIONAL PLANES ......................................................................................24

FIGURE 1- 4 - A1 INTERFACE SIGNALING PROTOCOL REFERENCE M ODEL .........................................................28

FIGURE 1- 5 HARMONIZED A RCHITECTURE FOR PACKET DATA .......................................................................29

FIGURE 2-1 - M OBILE ORIGINATION............................................................................................................................35

9
10

FIGURE 2-2 - MOBILE ORIGINATION WITH A CCESS PROBE HANDOFF, ACCESS HANDOFF AND CHANNEL
A SSIGNMENT INTO SOFT /SOFTER HANDOFF ...................................................................................................38

11

FIGURE 2-3 - M OBILE ORIGINATION WITH PACA SERVICE ...................................................................................42

12

FIGURE 2-4 - M OBILE ORIGINATION, IDLE HANDOFF WITH PACA A CTIVE .......................................................44

13

FIGURE 2-5 - M OBILE ORIGINATION WITH CONSECUTIVE PACA CALL REQUESTS..........................................45

14

FIGURE 2-6 - PACA CALL CANCELLATION INITIATED BY THE MS.....................................................................46

15

FIGURE 2-7 - PACA CALL CANCELLATION INITIATED BY THE MSC ..................................................................47

16

FIGURE 2-8 - M OBILE TERMINATION ..........................................................................................................................52

17

FIGURE 2-9 - M OBILE TERMINATION: A SSIGNMENT RETRY ..................................................................................55

18

FIGURE 2-10 - M OBILE TERMINATION INITIATED BY THE BS...............................................................................59

19

FIGURE 2-11 - CALL CLEAR INITIATED BY MS .........................................................................................................65

20

FIGURE 2-12 - CALL CLEAR INITIATED BY BS (VIA CLEAR REQUEST ) .................................................................66

21

FIGURE 2-13 - CALL CLEAR INITIATED BY MSC (VIA CLEAR COMMAND) ..........................................................67

22

FIGURE 2-14 - CALL W AITING ......................................................................................................................................72

23

FIGURE 2-15 - THREE-W AY CALLING - (M ETHOD 1)................................................................................................73

24

FIGURE 2-16 - THREE-W AY CALLING - (M ETHOD 2)................................................................................................74

25

FIGURE 2-17 - M ESSAGE W AITING NOTIFICATION ON THE PAGING CHANNEL ..................................................75

26

FIGURE 2-18 - M ESSAGE W AITING NOTIFICATION ON THE TRAFFIC CHANNEL.................................................76

27

FIGURE 2-19 SMS-BROADCAST DELIVERY TO M OBILE STATIONS OVER THE PAGING CHANNEL...............81

28

FIGURE 2-19 - SMS-MT DELIVERY TO A M OBILE STATION ON THE PAGING CHANNEL - EXAMPLE 1 .........83

29

FIGURE 2-20 - SMS-MO DELIVERY ON THE A CCESS CHANNEL .............................................................................84

30

FIGURE 2-21 - SMS-MT DELIVERY TO A M OBILE STATION ON THE PAGING CHANNEL - EXAMPLE 2 .........85

31

FIGURE 2-22 - SMS-MT DELIVERY TO A M OBILE STATION ON THE PAGING CHANNEL - EXAMPLE 3 .........87

32

FIGURE 2-23 - SMS MESSAGE DELIVERY TO A M OBILE STATION ON A TRAFFIC CHANNEL ............................90

33

FIGURE 2-24 - SMS RECEIPT FROM A M OBILE STATION ON A TRAFFIC CHANNEL...........................................91

34

FIGURE 2-25 - OTASP M ESSAGE FLOW : CDMA........................................................................................................94

35

FIGURE 2-26 - LOCATION REGISTRATION USING USER ZONES..............................................................................103

36

FIGURE 2-27 - M OBILE CALL SETUP USING USER ZONE ........................................................................................104

37

FIGURE 2-28 - UPDATING THE USER ZONE DURING A CALL.................................................................................105

xvii

TIA/EIA/IS-2001

FIGURE 2-29 - PACKET DATA SERVICE STATE TRANSITIONS ..............................................................................108

FIGURE 2-30 - M OBILE TERMINATION INITIATED BY THE BS.............................................................................111

3
4

FIGURE 2-31 - M OBILE INITIATED INITIAL CALL SETUP AND M OBILE IP REGISTRATION SUCCESSFUL
OPERATION...........................................................................................................................................................121

FIGURE 2-32 - BS INITIATED CALL RELEASE TO DORMANT STATE ..................................................................123

FIGURE 2-33 - MS INITIATED CALL RELEASE TO DORMANT STATE .................................................................125

FIGURE 2-34 - MS POWER DOWN ...............................................................................................................................127

FIGURE 2-35 - PDSN INITIATED SERVICE RELEASE ................................................................................................129

FIGURE 2-36 - NETWORK INITIATED CALL RE-A CTIVATION FROM DORMANT STATE .................................131

10

FIGURE 2-37 - M OBILE TERMINATED PACKET DATA REJECTION DURING A VOICE CALL ............................133

11

FIGURE 2-38 - DORMANT HANDOFF (INTER-BSC/INTER_PCF) - M OBILE SERVED BY SAME PDSN...............134

12

FIGURE 2-39 - DORMANT HANDOFF (INTER-BSC/INTER_PCF) - M OBILE SERVED BY A DIFFERENT PDSN.136

13

FIGURE 2-40 - INTER-BS HARD HANDOFF (WITHIN THE SAME PCF)...................................................................138

14

FIGURE 2-41 - INTER-PCF HARD HANDOFF (W ITHIN SAME PDSN).....................................................................141

15

FIGURE 2-42 - INTER-PCF HARD HANDOFF (W ITHIN SAME PDSN) W ITH RETURN ON FAILURE .................144

16

FIGURE 2-43 - M OBILE ORIGINATED PACKET CALL SETUP SUCCESSFUL OPERATION ...............................153

17

FIGURE 2-44 - M OBILE ORIGINATED PACKET CALL SETUP FAILURE OPERATION.....................................155

18

FIGURE 2-46 - PACKET DATA SERVICE SESSION CLEARING-PDSN INITIATED .................................................160

19

FIGURE 2-47 - PACKET DATA SERVICE SESSION CLEARING MSC INITIATED ................................................162

20

FIGURE 2-48 - PACKET DATA SERVICE SESSION CLEARING MS INITIATED ...................................................163

21

FIGURE 2-49 - PACKET DATA SERVICE SESSION PDSN INITIATED (CROSSING A11-REGISTRATION
REQUEST AND A11-REGISTRATION UPDATE)................................................................................................164

22

24

FIGURE 2-50 - INTER-PCF DORMANT HANDOFF M OBILE CONTINUES TO BE SERVED BY THE SERVING
PDSN......................................................................................................................................................................167

25

FIGURE 2-52 - INTER-PCF HARD HANDOFF M OBILE CONTINUES TO BE SERVED BY THE SERVING PDSN175

26

FIGURE 2-53 - INTER-BS HARD HANDOFF M OBILE SERVED BY NEW TARGET PDSN ..................................179

27

FIGURE 3- 1 - SUCCESSFUL HARD HANDOFF .............................................................................................................215

28

FIGURE 3- 2 - SUCCESSFUL HARD HANDOFF TO A ANSI/EIA/TIA-553 SYSTEM................................................217

29
30

FIGURE 3- 3 - UNSUCCESSFUL HARD HANDOFF TO ANSI/EIA/TIA-553: ANSI/EIA/TIA-553 ALTERNATIVE

REJECTED ..............................................................................................................................................................219

31

FIGURE 3- 4 HARD HANDOFF W ITH RETURN ON FAILURE ................................................................................221

32

FIGURE 3- 5 - SOFT /SOFTER HANDOFF A DDITION ..................................................................................................223

33

FIGURE 3- 6 - SOFT /SOFTER HANDOFF REMOVAL ...................................................................................................225

34

FIGURE 3- 7 - CELL REMOVAL INITIATED BY THE TARGET BS ...........................................................................227

35

FIGURE 3- 8 - INITIAL TRAFFIC BURST EXAMPLE ...................................................................................................229

36

FIGURE 3- 9 - SUBSEQUENT TRAFFIC BURST EXAMPLE .........................................................................................231

37

FIGURE 4- 1 - LOCATION REGISTRATION - SUCCESSFUL CASE ..............................................................................234

38

FIGURE 4- 2 - SSD UPDATE - SUCCESSFUL CASE .....................................................................................................240

23

xviii

TIA/EIA/IS-2001

FIGURE 4- 3 - TERMINAL A UTHENTICATION ..........................................................................................................243

FIGURE 4-4 - PARAMETER UPDATE ...........................................................................................................................245

FIGURE 4- 5 - PRIVACY M ODE PROCEDURE ..............................................................................................................247

FIGURE 5- 1 - SCCP CONNECTION ESTABLISHMENT ..............................................................................................263

FIGURE 5- 2 - SCCP CONNECTION ESTABLISHMENT REFUSAL .............................................................................264

FIGURE 5- 3 - SCCP CONNECTION ESTABLISHMENT DURING HANDOFF ............................................................264

FIGURE 5- 4 - SCCP CONNECTION REFUSAL DURING HANDOFF...........................................................................265

FIGURE 5- 5 - BS GENERATED SCCP RELEASE : BS HAS LOST A CCESS TO SCCP CONNECTION

INFORMATION ......................................................................................................................................................267

11

FIGURE 5- 6 - MSC GENERATED SCCP RELEASE : MSC HAS LOST A CCESS TO SCCP CONNECTION
INFORMATION ......................................................................................................................................................268

12

FIGURE 5- 7 - SLR/DLR USAGE ....................................................................................................................................269

13

FIGURE 5- 8 - DELIMITING M ESSAGES IN AN IOS A PPLICATION TCP BYTE STREAM.....................................279

14

FIGURE 5- 9 - GRE ENCAPSULATED USER TRAFFIC.................................................................................................284

15

FIGURE 5- 10 - GRE HEADER........................................................................................................................................284

16

FIGURE 5- 11 - BLOCK PROCEDURE ............................................................................................................................288

17

FIGURE 5- 12 - UNBLOCK PROCEDURE .......................................................................................................................290

18

FIGURE 5- 13 A1 RESET CIRCUIT PROCEDURE AT THE BS ................................................................................291

19

FIGURE 5- 14 A1 RESET CIRCUIT PROCEDURE AT THE MSC ............................................................................293

20

FIGURE 5- 15 - RESET CIRCUIT PROCEDURE AT THE MSC WITH BS BLOCK RESPONSE .................................293

21

FIGURE 5- 16 - SUCCESSFUL RESET AT THE MSC....................................................................................................296

22

FIGURE 5- 17 - SUCCESSFUL RESET AT THE BS........................................................................................................297

23

FIGURE 5- 18 - RESET GLARE NOTED AT THE MSC ...............................................................................................298

24

FIGURE 5- 19 - RESET GLARE NOTED AT THE BS ...................................................................................................299

25

FIGURE 5- 20 - RESET GLARE NOTED AT BOTH THE MSC AND THE BS............................................................300

26

FIGURE 5- 21 - SUCCESSFUL A7-RESET AT A BSC ...................................................................................................302

27

FIGURE 5- 22 - A7-RESET GLARE NOTED AT THE FIRST BSC...............................................................................303

28

FIGURE 5- 23 - A7-RESET GLARE NOTED AT BOTH BSCS .....................................................................................304

29

FIGURE 5- 24 - TRANSCODER CONTROL PROCEDURE ..............................................................................................307

30

FIGURE 6-1 - SIGNALING PROTOCOL REFERENCE M ODEL MSC-BS INTERFACE ..............................................308

31

FIGURE 6-2 - STRUCTURE OF A1 LAYER 3 M ESSAGES ............................................................................................310

32

FIGURE 6-3 - A3/A7 INFORMATION ELEMENT GENERIC LAYOUT .......................................................................613

33

FIGURE A- 1 FEATURE A CTIVATION/DEACTIVATION W HILE IN A CALL.........................................................848

34

FIGURE A- 2 TIA/EIA-95 CALL BARRING OUTGOING .............................................................................................850

10

35

xix

TIA/EIA/IS-2001

Table of Tables

TABLE 2- 2 - SUPPORT OF A SYNCHRONOUS DATA/G3 FAX HANDOFFS..............................................................107

TABLE 2- 3 - A CCOUNTING RECORDS GENERATED BY THE PCF.........................................................................152

TABLE 5- 1 - USE OF THE USER DATA FIELD IN SCCP FRAMES ...........................................................................269

TABLE 5- 2 - USE OF SCCP FOR BSMAP AND DTAP M ESSAGES ..........................................................................271

TABLE 6 - 1 - ELEMENT FLOW DIRECTION INDICATION .....................................................................................311

TABLE 6 - 2 - A1 INFORMATION ELEMENT IDENTIFIERS SORTED BY NAME ....................................................596

TABLE 6 - 3 - A1 INFORMATION ELEMENT IDENTIFIERS SORTED BY IDENTIFIER VALUE.............................599

TABLE 6 - 4 - A3/A7 INFORMATION ELEMENT IDENTIFIERS SORTED BY NAME .............................................604

10

TABLE 6 - 5 - A3/A7 INFORMATION ELEMENT IDENTIFIERS SORTED BY NAME (CONT .) ..............................605

11

TABLE 6 - 6 - A3/A7 INFORMATION ELEMENT IDENTIFIERS SORTED BY IDENTIFIER VALUE ......................606

12

TABLE 6 - 7 - A9 INFORMATION ELEMENT IDENTIFIERS SORTED BY IDENTIFIER NAME ..............................608

13

TABLE 6 - 8 - A9 INFORMATION ELEMENT IDENTIFIERS SORTED BY IDENTIFIER VALUE.............................608

14

TABLE 6 - 9 - A11 INFORMATION ELEMENT IDENTIFIERS SORTED BY NAME .................................................609

15

TABLE 6 - 10 - A11 INFORMATION ELEMENT IDENTIFIERS SORTED BY VALUE..............................................609

16

TABLE 6 - 11 - CROSS REFERENCE OF INFORMATION ELEMENTS W ITH M ESSAGES.........................................615

17

TABLE 6 - 12 - BSMAP M ESSAGES .............................................................................................................................638

18

TABLE 6 - 13 - DTAP M ESSAGES.................................................................................................................................641

19

TABLE 6 - 14 - A3 AND A7 M ESSAGE TYPE II VALUES...........................................................................................642

20

TABLE 6 - 15 - CHANNEL TYPE - SPEECH OR DATA INDICATOR VALUES..........................................................645

21

TABLE 6 - 16 - CHANNEL TYPE - CHANNEL RATE AND TYPE VALUES...............................................................646

22

TABLE 6 - 17 - CHANNEL TYPE - OCTET 5 CODING (VOICE /SIGNALING CALL).................................................646

23

TABLE 6 - 18 - CHANNEL TYPE - OCTET 5 CODING (DATA CALL) ......................................................................646

24

TABLE 6 - 19 - RF CHANNEL IDENTITY TIMESLOT NUMBER............................................................................647

25

TABLE 6 - 20 - ENCRYPTION INFORMATION - ENCRYPTION PARAMETER CODING.........................................652

26

TABLE 6 - 21 - ENCRYPTION INFORMATION - ENCRYPTION PARAMETER IDENTIFIER CODING....................653

27

TABLE 6 - 22 - A3 TRAFFIC CHANNEL PROTOCOL STACK ....................................................................................655

28

TABLE 6 - 23 - REVERSE PILOT GATING RATE - PILOT GATING RATE ...............................................................655

29

TABLE 6 - 24 - PHYSICAL CHANNEL INFO - PHYSICAL CHANNEL.........................................................................656

30

TABLE 6 - 25 - CLASSMARK INFORMATION TYPE 2 - RF POWER CAPABILITY..................................................658

31

TABLE 6 - 26 - CLASSMARK INFORMATION TYPE 2 - AIR INTERFACES SUPPORTED (M OBILE P_REV LESS
THAN OR EQUAL TO THREE). ............................................................................................................................660

32

34

TABLE 6 - 27 - CLASSMARK INFORMATION TYPE 2 - AIR INTERFACES SUPPORTED (M OBILE P_REV

GREATER THAN THREE). ....................................................................................................................................660

35

TABLE 6 - 28 - M OBILE IDENTITY - TYPE OF IDENTITY CODING........................................................................662

36

TABLE 6 - 29 - PRIORITY - CALL PRIORITIES ...........................................................................................................665

37

TABLE 6 - 30 - PRIORITY - QUEUING A LLOWED .....................................................................................................666

33

xx

TIA/EIA/IS-2001

TABLE 6 - 31 - PRIORITY - PREEMPTION A LLOWED ..............................................................................................666

TABLE 6 - 32 - CAUSE CLASS VALUES ........................................................................................................................667

TABLE 6 - 33 - CAUSE VALUES ....................................................................................................................................668

TABLE 6 - 35 - CELL IDENTIFIER - CELL IDENTIFICATION DISCRIMINATOR LIST ............................................671

TABLE 6 - 36 - CELL IDENTIFIER - CELL IDENTIFICATION DISCRIMINATOR = 0000 0010.............................672

TABLE 6 - 37 - CELL IDENTIFIER - CELL IDENTIFICATION DISCRIMINATOR = 0000 0101.............................672

TABLE 6 - 38 - CELL IDENTIFIER - CELL IDENTIFICATION DISCRIMINATOR = 0000 0111.............................672

TABLE 6 - 39 - CELL IDENTIFIER - CELL IDENTIFICATION DISCRIMINATOR = 0000 1000.............................673

TABLE 6 - 40 - CIRCUIT IDENTITY CODE EXTENSION - CIRCUIT M ODE FIELD ................................................675

10

TABLE 6 - 41 - REVERSE PILOT GATING RATE - PILOT GATING RATE ...............................................................681

11

TABLE 6 - 42 - IS-2000 CHANNEL IDENTITY - PHYSICAL CHANNEL TYPE........................................................682

12

TABLE 6 - 43 - IS-2000 CHANNEL IDENTITY - PILOT GATING RATE..................................................................683

13

TABLE 6 - 44 - CALLING PARTY ASCII NUMBER - TYPE OF NUMBER VALUES .................................................685

14

TABLE 6 - 45 - CALLING PARTY ASCII NUMBER - NUMBERING PLAN IDENTIFICATION VALUES.................686

15

TABLE 6 - 46 - CALLING PARTY ASCII NUMBER - PRESENTATION INDICATOR ...............................................686

16

TABLE 6 - 47 - CALLING PARTY ASCII NUMBER - SCREENING INDICATOR .......................................................687

17
18

THE MESSAGE CATEGORY OF EACH DTAP MESSAGE MAY BE DETERMINED FROM TABLE 6 - 13 - DTAP
M ESSAGES..............................................................................................................................................................689

19

TABLE 6 - 48 - PROTOCOL DISCRIMINATOR .............................................................................................................689

20

TABLE 6 - 49 - LOCATION UPDATING TYPE.............................................................................................................690

21

TABLE 6 - 50 - REJECT CAUSE VALUE .......................................................................................................................693

22

TABLE 6 - 51 - A UTHENTICATION CHALLENGE PARAMETER - RANDOM NUMBER TYPE..............................694

23

TABLE 6 - 52 - A UTHENTICATION RESPONSE PARAMETER - A UTH SIGNATURE TYPE..................................695

24

TABLE 6 - 53 - PROGRESS INDICATOR - CODING STANDARD .................................................................................698

25

TABLE 6 - 54 - PROGRESS INDICATOR - LOCATION..................................................................................................699

26

TABLE 6 - 55 - PROGRESS INDICATOR - PROGRESS DESCRIPTION..........................................................................699

27

TABLE 6 - 56 - SIGNAL VALUE: TONES ......................................................................................................................700

28

TABLE 6 - 57 - SIGNAL VALUE: TIA/EIA-IS-2000 A LERTING................................................................................700

29

30

TABLE 6 - 58 - SIGNAL - A LERT PITCH VALUES......................................................................................................701

31

TABLE 6 - 59 - SIGNAL - SIGNAL VALUE M APPING: ANSI-41 AND IOS TIA/EIA-IS-2000...........................701

32

TABLE 6 - 60 - CM SERVICE TYPES............................................................................................................................704

33

TABLE 6 - 61 - CALLED PARTY BCD NUMBER - TYPE OF NUMBER VALUES .....................................................706

34

TABLE 6 - 62 - CALLED PARTY BCD NUMBER - NUMBERING PLAN IDENTIFICATION VALUES.....................706

35

TABLE 6 - 63 - CALLED PARTY BCD NUMBER - NUMBER DIGIT VALUES ..........................................................707

36

TABLE 6 - 64 - CALLED PARTY BCD NUMBER - PRESENTATION INDICATOR ...................................................709

37

TABLE 6 - 65 - CALLED PARTY BCD NUMBER - SCREENING INDICATOR ...........................................................709

701

xxi

TIA/EIA/IS-2001

TABLE 6 - 66 - CAUSE LAYER 3 - CODING STANDARD ............................................................................................711

TABLE 6 - 67 - CAUSE LAYER 3 - LOCATION.............................................................................................................711

TABLE 6 - 68 - CAUSE LAYER 3 - CAUSE (CLASS) VALUE........................................................................................712

TABLE 6 - 69 - CAUSE LAYER 3 VALUES....................................................................................................................713

TABLE 6 - 71 - FORWARD BURST RADIO INFO CODING INDICATOR .................................................................715

TABLE 6 - 72 - REVERSE BURST RADIO INFO CODING INDICATOR....................................................................717

TABLE 6 - 73 - LOCATION REGISTRATION TYPE .....................................................................................................721

TABLE 6 - 74 - SERVICE OPTION SERVICE OPTION VALUES..............................................................................727

9
10

TABLE 6 - 75 - REVERSE LAYER 3 IS-2000 FCH/DCCH DATA - TIME SCALE FOR THE PACKET A RRIVAL
TIME ERROR ..........................................................................................................................................................740

11

TABLE 6 - 76 - IS-2000 FRAME CONTENT - SPECIAL FRAME CONTENT PARAMETERS..................................742

12

TABLE 6 - 77 - IS-2000 FRAME CONTENT - FUNDAMENTAL CHANNEL (FCH) FRAME CONTENT

PARAMETERS........................................................................................................................................................743

13
14
15
16
17
18
19
20
21
22
23

TABLE 6 - 78 - IS-2000 FRAME CONTENT - DEDICATED CONTROL CHANNEL (DCCH) FRAME CONTENT
PARAMETERS........................................................................................................................................................744
TABLE 6 - 79 - IS-2000 FRAME CONTENT - SUPPLEMENTAL CHANNEL (SCH) FRAME CONTENT
PARAMETERS FOR 20MS FRAMES ......................................................................................................................745
TABLE 6 - 80 - IS-2000 FRAME CONTENT - SUPPLEMENTAL CHANNEL (SCH) FRAME CONTENT
PARAMETERS FOR 40MS FRAMES* ....................................................................................................................746
TABLE 6 - 81 - IS-2000 FRAME CONTENT - SUPPLEMENTAL CHANNEL (SCH) FRAME CONTENT
PARAMETERS FOR 80MS FRAMES* ....................................................................................................................747
TABLE 6 - 82 - REVERSE LAYER 3 IS-2000 SCH DATA - TIME SCALE FOR THE PACKET A RRIVAL TIME
ERROR.....................................................................................................................................................................751

25

THE CODING OF THE FORWARD, REVERSE , A LLOC AND A VAIL FIELDS IS GIVEN IN TABLE 6 - 93 - RADIO
ENVIRONMENT AND RESOURCES.......................................................................................................................754

26

TABLE 6 - 83 - RADIO ENVIRONMENT AND RESOURCES.........................................................................................755

27

TABLE 6 - 84 - A3 A DDRESS IDENTIFIER TYPE........................................................................................................759

28

TABLE 6 - 85 - PMC CAUSE VALUES ..........................................................................................................................765

29

THE CODING OF THE BAND CLASS FIELD IS SPECIFIED IN TABLE 6 - 86 - BAND CLASS ...................................767

30

TABLE 6 - 86 - BAND CLASS .........................................................................................................................................767

31

TABLE 6 - 87 - FORWARD LAYER 3 DATA - RATE SET INDICATOR .....................................................................773

32

TABLE 6 - 88 - FORWARD LAYER 3 DATA - FORWARD TRAFFIC CHANNEL RATE ............................................773

33

TABLE 6 - 89 - FORWARD LAYER 3 DATA - FORWARD TRAFFIC CHANNEL INFORMATION ............................774

34

TABLE 6 - 90 - FORWARD LAYER 3 DATA - LAYER 3 FILL.....................................................................................774

35

TABLE 6 - 91 - REVERSE LAYER 3 DATA - VALUE OF ..........................................................................................776

36

TABLE 6 - 92 - REVERSE LAYER 3 DATA - TIME SCALE FOR THE PACKET A RRIVAL TIME ERROR ...............776

37

TABLE 6 - 93 - REVERSE LAYER 3 DATA - RATE SET INDICATOR........................................................................776

38

TABLE 6 - 94 - REVERSE LAYER 3 DATA - REVERSE TRAFFIC CHANNEL RATE .................................................777

39

TABLE 6 - 95 - REVERSE LAYER 3 DATA - REVERSE TRAFFIC CHANNEL INFORMATION BITS........................777

40

TABLE 6 - 96 - REVERSE LAYER 3 DATA - LAYER 3 FILL BITS..............................................................................778

24

xxii

TIA/EIA/IS-2001

TABLE 6 - 97 - BSC IDENTIFIER FORMAT .................................................................................................................779

TABLE 6 - 98 - PRIVACY INFO - PRIVACY M ASK TYPE............................................................................................785

TABLE 6 - 99 - PACA ORDER - PACA A CTION REQUIRED ...................................................................................799

TABLE 6 - 100 - A11 INTERFACE M ESSAGE TYPES..................................................................................................803

TABLE 6 - 101 - SETTING OF A11 REGISTRATION REQUEST M ESSAGE FLAGS...................................................803

TABLE 6 - 102 - SETTING OF HOME A DDRESS FIELD..............................................................................................804

TABLE 6 - 103 - A11 CODE VALUES...........................................................................................................................807

TABLE 6 - 104 - A11 STATUS VALUES .......................................................................................................................808

TABLE 6 - 105 - A11 PROTOCOL TYPE VALUES.......................................................................................................812

10

TABLE 6 - 106 - VENDOR/ORGANIZATION SPECIFIC EXTENSION - A PPLICATION TYPE.................................814

11

TABLE 6 - 108 - A PPLICATION SUB TYPE ................................................................................................................814

12

TABLE 6 - 109 - A8_TRAFFIC_ID - A8 TRANSPORT PROTOCOL STACK..............................................................817

13

TABLE 6 - 110 - A8_TRAFFIC_ID - A DDRESS TYPE .................................................................................................818

14

TABLE 6 - 111 - TIMER VALUES AND RANGES SORTED BY NAME........................................................................829

15

TABLE 6 - 112 - TIMER VALUES AND RANGES SORTED BY CLASSIFICATION .....................................................832

16

xxiii

TIA/EIA/IS-2001

2
3
4
5
6
7
8

Foreword
This Inter-Operability Specification (IOS) is based on TIA/EIA/634 -B, "MSC-BS
Interface for Public Wireless Communications Systems " and CDG IOS v3.1.0 MSC to
BS Interface Inter-Operability Specification (IOS).
Some sections are marked as UNUSED SECTION. These are IS-634 Rev A sections
that had been marked Not required in CDG IOS v3.1.0. This was done to preserve
section numbering. Also in Tables 6-2 through 6-5 some Information Element Identifier
values are marked as unused value for the same reason.

12

This document includes a description of the protocol and some generic procedures to
support the following features and functions. Conformance to this standard may be
claimed on a feature by feature and/or interface by interface basis. If conformance on a
given interface is claimed for a feature, it must be supported as defined in this standard.

13

FEATURES

14

Authentication

15

Authorized Roaming

16

Basic 911

17

Call Barring (Incoming and Outgoing)

18

Call Delivery

19

Call Forwarding:
Basic Remote Call Forwarding,
Call Forwarding Unconditional (CFU),
Call Forwarding When Busy (CFB),
Call Forwarding When No Answer or Not Available (CFNA),
Call Forwarding of Call Waiting

9
10
11

20
21
22
23
24
25

User Selective Call Forwarding

26

Calling Line ID

27

Calling Number ID Presentation (CNIP) on Mobile Terminations

28

Calling Number ID Restriction (CNIR) on Originations and Terminations

29

Call Transfer

30

Call Waiting

31

Carrier Access

32

Distinctive Ringing

33

E911 Phase 1 and Phase 2

34

Emergency Service (Basic) via specific dialed number (e.g., 911)

35

High Speed (144 kbps) Packet Data Services

36

Hotlining

37

Lawfully Authorized Wiretap

38

Message Waiting Notification

39

Over the Air Service Provisioning (OTASP)

xxiv

TIA/EIA/IS-2001

Over the Air Parameter Administration (OTAPA)

Priority Access and Channel Assignment (PACA) SMS MO and MT

SMS Broadcast and Broadcast Teleservice Transport Capability

Three-Way Calling

User Zone

Voice Answering

Voice/Data Privacy

Answer Holding

FUNCTIONS

10

13k Vocoder Support

11

Autonomous Registration

12
13

EVRC Support including downward and upward service negotiation between the BS
and the MS

14

Feature Activation/Deactivation: Idle and In-Call

15

Active Handoff: the following types of handoffs are supported

Voice
calls

Async Data
and G3 Fax

Packet Data
Calls (up to
144 kbps)

Intra-BS, Intra-MSC Soft Handoff

Yes

Yes

Yes

* Intra-BS, Intra-MSC Hard Handoff

Yes

Yes

Yes

Inter-BS, Intra-MSC Soft Handoff

Yes a

Yes

Yes

* Inter-BS, Intra-MSC Hard Handoff

Yes

Yes

Yes a

Inter-BS, Inter-MSC Soft Handoff

Yes a

Yes

Yes

* Inter-BS, Inter-MSC Hard Handoff

Yes

No

Yes b

Type of Handoff

16

Hard handoff does not apply to supplemental channels

a.

Inter-BS, Intra-MSC Hard Handoff may result in handoff across PDSN

boundaries.

b.

Inter-BS, Inter-MSC Hard Handoff may result in handoff across PDSN

boundaries. In addition, this requires extensions to ANSI-41 for packet data
services.

17
18
19
20
21
22

xxv

TIA/EIA/IS-2001

1
2

Soft Handoff enhancements, as specified in TIA/EIA IS-95B are supported by this

specification.

Access Handoff, Access Probe Handoff and CDMA Channel Assignment into Soft
Handoff and Access Entry Handoff as specified in TIA/EIA-95-B are supported in this
specification.

Access Entry Handoff is transparent to this standard.

Mobile-Assisted CDMA-to-CDMA Inter-Frequency

supported as specified in TIA/EIA-95-B.

3
4

8
9
10

xxvi

Handoff

Enhancement

is

TIA/EIA/IS-2001

Circuit mode voice service assumptions:

2
3

The following assumptions are made:

All mobiles will be capable of executing a service option change and a hard handoff
simultaneously. That is, the Action Time for both of these activities may be the
same.

For inter-vendor hard handoff, the source BS knows the service option capabilities
of the target BS.

For inter-vendor soft handoff, all target BS channel elements are capable of
supporting both the 13K and EVRC service options (i.e., rate set 1 and rate set 2).

The source BS may assume that sufficient resources will be available at the target
BS for the requested service option.

13

A default service configuration shall be used at all target BSs for hard handoff.

14

The MSC is aware of the service options supported by each of the BSs attached to
it.

Hard handoff from 13K to EVRC is disallowed for IS-95B mobiles. For IS-2000
mobiles, if the target BS does not have 13K available, the target BS may send a new
service option to the source BS.

Currently, only 13K (8000H and 0011H) and EVRC voice service options are
supported.

21

The default service option for IOS networks is 13K voice (SO=8000H).

22

All mobile stations capable of supporting EVRC can also support 13K (8000H)
service options.

24

The service negotiation will be between the Base Station and the Mobile Station.

25

The service negotiation will only depend on the capabilities of the Base Station and
of the Mobile Station.

5
6
7
8
9
10
11
12

15
16
17
18
19
20

23

26
27
28
29
30
31
32

Based on these assumptions, a source BS will always know what vocoder types (EVRC
/ 13K) are available at the target BS, and what service configuration is to be used at the
target BS. If a change of vocoder type is necessary, the source BS can accomplish it by
commanding the MS to execute a service option change and a hard handoff
simultaneously. Thus, service negotiation messaging is not needed on either the A1 or
A3 interfaces.

33

xxvii

TIA/EIA/IS-2001

The following procedures are to be followed:

If the BS receives a Paging Request from the MSC specifying a service option valid
for this version of the IOS but not supported by the BS, the BS will page the mobile
with the service option in the Paging Request message.

If the BS receives an Origination Message / Paging Response Message from a

mobile station specifying a voice service option not valid for this standard, the BS
will deny the request. In the case of an originating call, the BS will order the mobile
station to generate a local Reorder signal.

Otherwise, if the BS receives an Origination Message / Paging Response Message

from a mobile station specifying a supported service option (i.e., rate set 1 or rate
set 2), that is not supported on the particular BS, the BS shall send a CM Service
Request message / Paging Response message to the MSC containing the service
option received from the mobile station.

The MSC will send the service option that was received in the CM Service Request
/ Paging Response message in the Assignment Request message.

16

Otherwise, the call is handled using the call setup procedures of this specification.

17

In all cases, if a call is successfully set up, the BS shall inform the MSC of the
agreed service option in the Assignment Complete message.

In the intra-MSC hard handoff scenario, if the source BS asks for a service option
not supported by the target BS, then the MSC may reject the handoff request.

3
4
5
6
7
8
9
10
11
12
13
14
15

18
19
20

xxviii

TIA/EIA/IS-2001

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

Copyright Information
This standard contains significant portions of material copied from ETSI GSM 04.08
(Phase 1) and ETSI GSM 08.08 (Phase 1) which has been modified to comply with the
domestic specifications of the U.S.A. The specific modifications are in the following
areas:
Many of the messages, information elements, and timers contained in GSM 04.08 (Phase
1) and GSM 08.08 (Phase 1) have been copied and adapted.
The message procedural descriptions can be found in sections 2, 3, 4, and 5 of this
specification. These message procedural descriptions have been copied and adapted.
The message definitions can be found in section 6.1. These message definitions have
been copied and adapted.
The information element definitions can be found in section 6.2. These information
element definitions have been copied and adapted.
The timer definitions can be found in section 6.3. These timer definitions have been
copied and adapted.
The copyrights on these ETSI documents are owned by the European
Telecommunications Standards Institute (ETSI), which has granted a license for
reproduction for use by TIA and its Engineering Committees and Subcommittees. Any
copies of the above mentioned ETSI documents required for other purposes should be
purchased directly from ETSI or other organizations with a sales agreement covering
ETSI publications.

22
23
24
25

xxix

TIA/EIA/IS-2001

1.

This standard describes the overall system functions, including services and features
required for interfacing a Base Station (BS) with the Mobile Switching Center, with other
Base Stations, and with the Packet Control Function (PCF); and for interfacing the PCF
with the Packet Data Service Node (PDSN).

2
3
4
5

This standard is intended to provide sufficient specification of a set of interfaces in

order to support the interoperability of one vendor's equipment with that of another.
Which, interface(s) a vendor chooses to implement is dependent on business decisions,
and is up to each vendor. However conformance to any given interface specified within
this standard requires all of the messages and procedures for supported features on
that interface, to be supported as specified within this standard. Establishing standard
interfaces allows the BS, PCF, PDSN, and MSC equipment to evolve independently and
to be provided by multiple vendors.

6
7
8
9
10
11
12
13

14

15

Functional Overview

1.1

Purpose
The purpose is to provide the standard for:

16

interfacing of an MSC with one or more BSs,

17

interfacing a BS with one or more BSs,

18

interfacing of a PCF with one or more BSs,

19

Interfacing PDSNs with PCFs..

20
21
22
23
24
25
26
27
28
29
30
31

This document defines the functional capabilities, including services and features, of
the defined interfaces. These services and features are the defining characteristics that
are the basis for the overall system standard.
The MSC-BS Interface is defined as the interface that provides telecommunications
services access between a Base Station and a Mobile Switching Center. It specifically
represents the demarcation point between the BS and the MSC which coincides with
the Reference Point "A" as depicted in the Telecommunications Industry Association
(TIA) TR45 Network Reference Model (NRM), see TSB-100. This point establishes the
technical interface and designates the test points and operational division of
responsibility between the BS and the MSC.
This standard fulfills the following criteria:
supports future MSC and BS implementations;

32

supports current TIA/EIA/IS-2000 and TIA/EIA/IS-95air interfaces;

33

makes maximum use of existing standards from the Telecommunications

Industry Association (TIA) and other sources;

promotes reliability enhancement, technical innovation, network product

availability, and economic competition;

37

allows connection of various manufacturers BSs to the same MSC;

38

allows the separate evolution of MSC and BS technology.

34
35
36

39
40
41
42
43

The Source BS -Target BS interface is defined as the interface which provides for interBS soft/softer handoffs. It specifically represents the demarcation point between two
Base Stations which coincides with the Reference Point A ter. This point establishes
the technical interface and designates the test points and operational division of
responsibility between the Source BS and Target BS. The Source BS and Target BS

TIA/EIA/IS-2001

1
2

3
4
5
6
7
8
9
10

interface is defined as the A3/A7 interface shown in Figure 1-2 Reference Model for
Digital Air Interfaces.
The PCF-PDSN interface is defined as the interface that provides access between a
Packet Control Function and a Packet Data Serving Node for high speed packet data
services. It specifically represents the demarcation point between the PCF and the
PDSN which coincides with the Reference Point "A quater". This point establishes the
technical interface and designates the test points and operational division of
responsibility between the PCF and the PDSN. The PCF-PDSN interface is defined as
the A10/A11 interface shown in Figure 1-2 Reference Model for Digital Air Interfaces.
The PCF-PDSN interface definition fulfills the following criteria:

11

supports future PCF and PDSN implementations;

12

allows connection of various manufacturers PCFs to the same PDSN and vice
versa;

13
14
15
16
17

makes maximum use of existing standards from the Internet Engineering Task Force
(IETF) and other sources;
promotes quality of service and accounting information exchange between the
PCFs and the PDSNs

19

promotes reliability enhancement, technical innovation, network product

availability, and economic competition;

20

allows the separate evolution of PCF and PDSN technologies.

18

TIA/EIA/IS-2001

2
3
4
5
6

1.2

Scope
This standard provides the specification for the Interfaces which coincides with the
Reference Point "A", "Ater" and "Aquater" defined in the TR45 Network Reference
Model shown in TSB-100.
The scope of this standard includes the following topics:
MSC-BS and BS-BS interfaces:

Descriptions of the specified functional capabilities that provide wireless

telecommunications services across the MSC-BS and BS-BS Interface as
defined in the TR45 Network Reference Model;

Descriptions of the division of responsibility of the functions provided

between the BS and the MSC, and between the source BS and the target BS,
without prescribing specific implementations;

15

Descriptions of the MSC-BS Interface and the BS-BS interface standards that
support the functional capabilities of the following air interface signaling
protocols:

16

ANSI/EIA/TIA-553 (only to support hard handoffs to AMPS)

17

TIA/EIA IS-2000

18

TIA/EIA IS-637-A;

19

PCF-PDSN interfaces:

20

Descriptions of the specified functional capabilities that provide packet

data services across the PCF-PDSN interface;

Descriptions of the division of responsibility of the functions provided

between the PCF and the PDSN without prescribing specific
implementations.

7
8
9
10
11
12
13
14

21

22
23
24
25
26

The interfaces defined in this standard are specified by a set of characteristics,

including:

27

Physical and electromagnetic parameters.

28

Channel structures.

29

Message types and contents.

30

Network operating procedures.

31

User data framing and transport.

TIA/EIA/IS-2001

1.3

Organization
This specification describes the protocol necessary to provide to wireless radio
telephone subscribers certain services requiring interaction between the Mobile
Switching Center (MSC), the Packet Control Function (PCF), the Packet Data Service
Node (PDSN), and the Base Station (BS), and is based on:

2
3
4
5
6

ANSI/TIA/EIA/634-B, MSC-BS Interface for Public Wireless Communications

Systems , and

CDG IOS version 3.1.0, CDMA Development Group MSC to BS Interface

Inter-Operability Specification.

TIA/EIA/IS-835, Wireless IP Network Architecture based on IETF Protocols.

7
8
9
10

11

1.3.1

The basic architecture for this interoperability specification

Selection/Distribution Unit (SDU) with the source Base Station (BS).

12
13

14

Architectures Supported

1.3.2

UNUSED SECTION

1.3.3

IOS V4.0 Layout

includes

the

15

16

17

This specification is organized into six sections.

18

Section 1

contains all global references, definitions, and terminology, as well as

purpose, scope, organization and conventions.

Section 2

contains the procedures required for call setup, call clearing, high
speed packet data services, and supplementary services.

22

Section 3

contains the procedures required for handoff operations.

23

Section 4

contains the procedures required for authentication, registration,

privacy, and mobile inquiry operations.

Section 5

contains the specifications for the layers for the interfaces in this
specification.

Section 6

contains the message and element layouts and timer definitions for
the interfaces in this specification.

19
20
21

24
25
26
27
28
29

TIA/EIA/IS-2001

1.4

Documentation Conventions

The scenarios and examples in this specification are not meant to be exhaustive, but
are only used to help explain some of the important procedures of the protocol.

Figure 1-1is provided as an example of the conventions used in this specification.

Several points within the diagram are worthy of note. The circled numbers in the
following figure correspond to the numbered items below.

1. Horizontal dotted lines are used to indicate messaging that is not part of defined
interfaces specified in this specification. Not all air interface messages are shown,
and names may be generic. For example, such as Handoff Direction Message are
meant to include EHDM, GHDM, and UHDM.

7
8
9
10

2. Vertical dotted lines are used to indicate the span of timers. The timer name is
placed as close as possible to the line. Timer names begin with a capital T
followed by digits or alphabetic characters. A list of timers is given in section 6.3.

11
12
13

3. Horizontal solid lines are used to indicate messaging that is part of theinterfaces
specified in this standard.

14
15

4. Lower case letters are associated with individual messaging instances in the diagram
in alphabetical order arranged vertically. These letters correlate the text below the
diagram with portions of the diagram.

16
17
18

5. Procedures that may involve the exchange of several messages are shown as an
open block arrow with the name of the procedure inside.

19
20

6. Comments related to parts of the diagram are located in a comment column on the
right side of the diagram.

21
22
23

time
MS

BS
Order
1

a
Message

comment

MSC

Tx

4
b

Message

Order
Ty
5

Procedure

Message

Comments

24
25

Figure 1- 1 - Document Convention Example: Call Clear Initiated by MS

TIA/EIA/IS-2001

a.

The mobile station transmits an Order over the reverse link.

b.

The BS sends a message to the MSC. Timer Tx is started by the BS.

c.

The MSC sends a message to the BS and starts timer Ty. The BS stops timer
Tx.

d.

The BS acknowledges the MS message by returning an Order over the forward

link.

e.

The BS and MSC execute the procedure.

f.

The BS then returns a message to the MSC. The MSC stops timer Ty.

1
2

5
6
7

10

11
12
13
14
15
16
17
18
19
20
21
22

1.4.1

Procedural Descriptions
The procedural descriptions are broken into sections where each section describes one
of the messages in the procedure. The description for each procedure is written to flow
through each section devoted to the messages that make up the procedure. Each of
these sections will have the following subsection breakdowns (as appropriate):
1. Successful Operation: this section is used to describe what the message is for,
why the sender is sending it, and what the receiver is expected to do with the
message. It may also provide a brief tutorial on the overall impact of this
message regarding the particular procedure. It includes invocation of any
pertinent timers or discussion of timing constraints. It may also provide
subsections that describe the uses of the elements within the message,
particularly if they are not obvious.
2.

Failure Operation: if applicable, this section is used to describe the actions of

the sender if the expected response is not received by the sender. This
includes treatment of timer expiration or receipt of failure messages stemming
from the message that was sent.

3.

Abnormal Operation: if applicable, this section is used to describe out of

sequence events that could possibly occur and the treatment by the receiver
of the message.

23
24
25
26
27
28

TIA/EIA/IS-2001

1.5

References

1.5.1

Telecommunications Industry Association (TIA) /

Electronics Industry Association (EIA)

3
4

5
6

ANSI/EIA/TIA - 553, Mobile Station - Land Station Compatibility Specification;

September, 1989.

7
8
9

ANSI TIA/EIA 41-D, Cellular Radio-Telecommunications Intersystem Operations;

1997.

11

TIA/EIA/IS-52, Uniform Dialing Procedures and Call Processing Treatment for

Cellular Radio Telecommunications; November, 1989.

12

TIA/EIA/664, Cellular Features Description Rev A; published December 1999

13

TIA/EIA/IS-95-B; TIA/EIA/IS-95-A, Mobile Station - Base Station Compatibility

Standard for Dual-Mode Wideband Spread Spectrum Cellular System; May, 1995.

10

14
15
16
17
18
19
20
21
22

TIA/EIA/IS-124 Rev B, Intersystem Non-signaling Data Communications; November,

1993.
TIA/EIA/TSB-29-A, International Implementation of Cellular Radiotelephone Systems
Compliant with ANSI/EIA/TIA 553; September, 1992.
TIA/EIA/TSB58, Administration of Parameter Value Assignments for TIA/EIA Spread
Spectrum Standards; December 1999.
TIA/EIA/IS-637, Short Message Services for Wideband Spread Spectrum Cellular
Systems, 1995.

23
24

IS-707-A, Data Services Option Standard for Spread Spectrum, April 1999.

25

TIA/EIA/IS-728, Inter-System Link Protocol, 1997.

26

TIA/EIA/IS-725-A, Over-the-Air Service Provisioning of Mobile Stations in Wideband

Spread Spectrum Systems, July, 1999.

27
28
29

TIA/EIA/IS-634 Revision A, MSC-BS Interface for Public Communications Networks,

July 1998.

31

ANSI/TIA/EIA-634 Revision B, MSC-BS Interface for Public Communications

Networks, March 1999.

32

TIA/EIA/IS-2000, cdma2000 Standards for Spread Spectrum Systems, August, 1999.

33

TIA/TIA/IS-835 Wireless IP Network Architecture Based on IETF Protocols, May,

2000>.

30

34

TIA/EIA/IS-2001

1.5.2

ANSI T1.101-1987, Synchronization Interface Standards for Digital Networks, 1987.

ANSI T1.102-1987, Digital Hierarchy - Electrical Characteristics; 1987.

ANSI T1.107-1988, Digital Hierarchy - Formats Specifications; 1988.

ANSI T1.110-1992, Signaling System No. 7 (SS7) General Information, June, 1992,.

ANSI T1.111-1992, Signaling System No. 7 (SS7) - Message Transfer Part (MTP), June,
1992.

7
8
9

Standards Committee T1

ANSI T1.112-1992, Signaling System No. 7 (SS7) - Signaling Connection Control Part
(SCCP), October, 1992,.

10

ANSI T1.403-1995, Network-to-Customer Installation - DS1 Metallic Interface, 1995.

11

ANSI T1.627 - 1993, B-ISDN - ATM Layer Functionality and Specification, 1993.

12

ANSI T1.635 - 1994, Broadband ISDN - ATM Adaptation Layer Type 5 Common Part
Functions and Specification, 1994.

13
14
15
16
17

ANSI T1.646 - 1995, Broadband ISDN - Physical Layer Specification for UserNetwork-Interface Including DS1/ATM, 1995.
ANSI T1.105 - 1995, Synchronous Optical Network (SONET) Basic Description
Including Multiplex Structure, Rates and Formats, 1995.

TIA/EIA/IS-2001

International Telecommunications Union - Telecommunications

Sector (ITU-T)

ITU-T Recommendation I.361, B-ISDN ATM Layer Specification.

ITU-T Recommendation I.363, B-ISDN ATM Adaptation Layer Specification.

5
6

ITU-T DRAFT Recommendation I.363.2, B-ISDN ATM Adaptation Layer Type 2

Specification, September 1997.

ITU-T Recommendation I.366.1

ITU-T Recommendation I.432, B-ISDN User-Network Interface - Physical Layer

Specification.

9
10
11
12
13
14
15
16

1.5.3

ITU-T Recommendation G.704, Synchronous Frame Structure Used at 1544, 6312,

2048, 8488, and 44,736 kbit/s Hierarchical Levels.
ITU-T Recommendation Q.2110, B-ISDN ATM Adaptation Layer Service Specific
Connection Oriented Protocol (SSCOP), July 1994.
ITU-T Recommendation Q.2140, B-ISDN ATM Adaptation Layer Service Specific
Coordination Function For Signalling At The Network Node Interface (SSCF at
NNI), February 1995.

19

ITU-T Recommendation Q.2931, Broadband-Integrated Services Digital Network (BISDN) Digital Subscriber Signalling No. 2 (DSS2) User-Network Interface Layer 3
Specification for Basic Call/Connection Control, 1995.

20

ITU-T Recommendation E.212, Identification Plan for Land Mobile Stations, 1993.

21

ITU-T Recommendation G.702, General Aspects of Digital Transmission Systems Terminal Equipments - Digital Hierarchy Bit Rates, 1993.

17
18

22

TIA/EIA/IS-2001

1.5.4

Other

Internet Engineering Task Force, RFC 768 User Datagram Protocol (UDP), 1980.

Internet Engineering Task Force, RFC 791 - Internet Protocol (IP), 1981.

Internet Engineering Task Force, RFC 793 - Transmission Control Protocol (TCP),
1981.

Internet Engineering Task Force, RFC 1321 The MD5 Message-Digest Algorithm,
1992.

Internet Engineering Task Force, RFC 1577 - Classical IP and ARP over ATM, 1994.

9
10

Internet Engineering Task Force, RFC 1661 The Point-to-Point Protocol (PPP),
1994.

11

Internet Engineering Task Force, RFC 1662 PPP in HDLC-like Framing, 1994.

12

Internet Engineering Task Force, RFC 1701 Generic Routing Encapsulation, 1994.

13
14

Internet Engineering Task Force, RFC 1883 - Internet Protocol, Version 5 (IPv6)
Specification, 1996.

15

Internet Engineering Task Force, RFC 2002 IP Mobility Support Specification, 1996.

16
17

Internet Engineering Task Force, RFC 2138 Remote Authentication Dial In User
Services (RADIUS), 1997.

18

Internet Engineering Task Force, RFC 2139 RADIUS Accounting, 1997.

19

Internet Engineering Task Force, RFC 2344 Reverse Tunneling for Mobile IP, 1998.

20

10

TIA/EIA/IS-2001

1.6

Terminology

1.6.1

Acronyms

3WC

Three Way Calling

AAA

Authentication, Authorization and Accounting

AAL2

ATM Adaptation Layer type 2

AAL5

ATM Adaptation Layer type 5

AC

Authentication Center

ADDS

Application Data Delivery Service

ADPCM

Adaptive Differential Pulse Code Modulation

AL

Air Link

AMPS

Advanced Mobile Phone System

ANP

AAL2 Negotiation Procedures

ANSI

American National Standards Institute

ARFCN

Absolute Radio Frequency Channel Number

AS

Antenna System

ATM

Asynchronous Transfer Mode

AUTHR

Authentication Response

AUTHU

Unique Challenge Authentication Response

BCD

Binary Coded Decimal

BS

Base Station

BSAP

Base Station Application Part

BSC

Base Station Controller

BSMAP

Base Station Management Application Part

BTS

Base Transceiver System

CC

Conference Calling

CCITT

International Telegraph and Telephone Consultative

Committee (See ITU)

CD

Call Delivery

CDG

CDMA Development Group

CDMA

Code Division Multiple Access

CFB

Call Forwarding - Busy

CFD

Call Forwarding - Default

CFNA

Call Forwarding - No Answer

CFU

Call Forwarding - Unconditional

11

TIA/EIA/IS-2001

CID

Circuit IDentifier (used with reference to AAL2)

CLID

Calling Line Identifier

CM

Connection Management

CNIP

Calling Number Identification Presentation

CNIR

Calling Number Identification Restriction

COUNT

Call History Count

CT

Call Transfer

CW

Call Waiting

DCCH

Dedicated Control Channel

DCE

Data Communications Equipment

DLCI

Data Link Connection Identifier

DLR

Destination Local Reference

DMH

Data Message Handler

DND

Do Not Disturb

DPC

Destination Point Code

DRS

Data Ready to Send

DS0

Digital Signal Level 0

DS1

Digital Signal Level 1

DS3

Digital Signal Level 3

DSAT

Digital Supervisory Audio Tone

DSS1

Digital Subscriber Signaling System Number 1

DTAP

Direct Transfer Application Part

DTMF

Dual Tone Multi-Frequency

DTX

Discontinuous Transmission

EIA

Electronics Industry Association

EIB

Erasure Indicator Bit

EIR

Equipment Identity Register

ESN

Electronic Serial Number

EVRC

Enhanced Variable Rate Codec

FA

Foreign Agent

FCH

Fundamental Channel

FPC

Forward Power Control

FQI

Frame Quality Indicator

FS

Frame Selector/Selection

FSN

Frame Sequence Number

GR

Gain Ratio

GRE

Generic Routing Extension

HA

Home Agent

12

TIA/EIA/IS-2001

HLR

Home Location Register

ICGI

ANSI TIA/EIA 41 Whole Cell Global Identification

IETF

Internet Engineering Task Force

IMSI

International Mobile Subscriber Identity

IOS

Interoperability Specification

IP

Internet Protocol

ISDN

Integrated Services Digital Network

ISLP

Intersystem Link Protocol

ITU

International Telecommunications Union (See CCITT)

IWF

Interworking Function

kb

kilo bits

LAC

Location Area Code

LAI

Location Area Identifier

LR

Location Register

LSB

Least Significant Bit

MAC

Medium Access Control

MAH

Mobile Access Hunting

MAHO

Mobile Assisted Handoff

MC

Message Center, (alternatively: Mobile Client)

MIN

Mobile Identification Number

MIP

Mobile IP

MS

Mobile Station

MSB

Most Significant Bit

MSC

Mobile Switching Center

MSI

Mobile Session Identifier

MT0

Mobile Termination 0

MT1

Mobile Termination 1

MT2

Mobile Termination 2

MTP

Message Transfer Part

MTP1

Message Transfer Part Layer 1

MTP2

Message Transfer Part Layer 2

MTP3

Message Transfer Part Layer 3

MWN

Message Waiting Notification

N-AMPS

Narrow band AMPS

NDSS

Network Directed System Selection

NRM

Network Reference Model

13

TIA/EIA/IS-2001

OAM&P

Operations, Administration, Maintenance, and

Provisioning

OLT

Outer Loop Threshold

OS

Operations System

OTASP

Over The Air Service Provisioning

OTD

Orthogonal Transmit Diversity

PACA

Priority Access and Channel Assignment

PATE

Packet Arrival Time Error

PCA

Password Call Acceptance

PCF

Packet Control Function

PCM

Pulse Code Modulation

PDE

Position Determining Entity

PDSN

Packet Data Serving Node

PIN

Personal Identification Number

PL

Preferred Language

PLD

Position Location Data

PLMN

Public Land Mobile Network

PMC

Packet Mode Channel

PMM

Personal Mobility Management

PN

Pilot Number

PPP

Point to Point Protocol

PSPDN

Packet Switched Public Data Network

PSTN

Public Switched Telephone Network

QCELP

Q Code Excited Linear Prediction

QIB

Quality Indication Bit

QOF

Quasi Orthogonal Function

QoS

Quality of Service

QPCH

Quick Paging Channel

RAND

Random Variable

RANDC

Random Confirmation

RANDSSD

Random SSD

RANDU

Random Variable - Unique Challenge

RC

Radio Configuration, Radio Class

RF

Radio Frequency

RFC

Remote Feature Control

RLC

Release Complete (SCCP)

RLP

Radio Link Protocol

14

TIA/EIA/IS-2001

RLSD

Release (SCCP)

R-OLT

Reverse Outer Loop Threshold

RPC

Reverse Power Control

SAT

Supervisory Audio Tone

SCA

Selective Call Acceptance

SCCP

Signaling Connection Control Part

SCH

Supplemental Channel

SDU

Selection/Distribution Unit

SLR

Source Local Reference

SLS

Signaling Link Selection

SME

Signaling Message Encryption

SMS

Short Message Service

SMS-MO

SMS Mobile Originated

SMS-MT

SMS Mobile Terminated

SNR

Signal to Noise Ratio

SP

Signaling Point

SPI

Security Parameter Index

SPINA

Subscriber PIN Access

SPINI

Subscriber PIN Intercept

SSCF

Service Specific Convergence Function

SSCOP

Service Specific Connection Oriented Protocol

SSD

Shared Secret Data

SSI

Signal Strength Indicator

STP

Signal Transfer Point

TA

Terminal Adapter

TAm

Mobile Terminal Adapter

TBD

To Be Determined

TCP

Transmission Control Protocol

TDMA

Time Division Multiple Access

TE1

Terminal Equipment 1

TE2

Terminal Equipment 2

TIA

Telecommunications Industry Association

TMSI

Temporary Mobile Station Identity

TSB

Telecommunications Systems Bulletin

TTA

Telecommunications Technology Association

TTC

Telecommunication Technology Committee

UDP

User Datagram Protocol

15

TIA/EIA/IS-2001

VLR

Visitor Location Register

VMR

Voice Message Retrieval

VP

Voice Privacy

WNE

Wireless Network Entity

16

TIA/EIA/IS-2001

1.6.2

Definitions
Base Station

An entity in the public radio telecommunications system used for

radio telecommunications with mobile stations.

Base Station Controller

The control portion of the base station that includes call control
logic and interconnections to the MSC, the BTSs that are part of
the BS, other BSCs, and BTSs of neighboring BSs for purposes
of soft/softer handoff.

Base Transceiver Station

A component of a base station that includes radio equipment. A

BTS is sometimes equated with the physical cell site of a wireless
network.

11

Bearer Connection

A connection intended to provide a path for user traffic.

12

Call Association

The totality of the active communication between the mobile

station and the network, including all signaling and transfer of
user information.

Cell

The unit of a base station having the ability to radiate in a given

geographic area; a sector or face of a physical radio
equipment implementation.

18

Downlink

The direction of MSC to BS.

19

Handoff

Handoff is the process by which an air interface circuit between a

mobile station and a base station is transferred from the current
base station equipment and air interface channel to either a
different base station equipment and air interface channel or a
different air interface channel on the current base station. The
following types of handoff are supported:

2
3
4
5
6
7
8
9
10

13
14
15
16
17

20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

1. Hard Handoff: A handoff that requires the mobile station to

tune its radio equipment or to reestablish synchronization.
2. Soft Handoff: A handoff that does not require the mobile
station to tune its radio equipment or to reestablish
synchronization and that uses the same frame selection function
(and voice transcoding function, if this is a voice call) in the
network for both the old and new air interface channels.
3. Soft Handoff with Pre-Selection: The configuration achieved
when a BS internally splits a single forward flow of coded user
information from the frame selector to send it to two or more cells
controlled by that BS. In the reverse direction, the BS joins the
flows of coded user information frames from those cells, selects
the best quality frame (preselection), and forwards only that
selected frame to the frame selector.
4. Softer Handoff: A handoff involving two or more traffic
channels on a call such that in the forward direction the BS splits
a single flow of traffic channel frames into two or more forward
flows to be sent to the mobile station with the power control
combined bit set to indicate that the same reverse power control
information is to be used. In the reverse direction the BS
combines the traffic channel frames that are received from two or
more cells/sectors and forms a single reverse flow from this
combination.
17

TIA/EIA/IS-2001

Interworking Function

The Interworking Function (IWF), used in the context of the this

standard, provides a translation of the user traffic on a data call
between the fixed network and the air interface.

Logical Channel

A logical path that can carry signaling, user traffic, or a

combination of the two between two entities such as the network
and the mobile station. A logical channel can be instantiated
over one or more physical channels. Logical channels may also
share physical channels.

Mobile Switching Center

The MSC switches MS-originated or MS-terminated traffic. An

MSC is usually connected to at least one base station. It may
connect to other public networks PSTN, ISDN, etc., other MSCs
in the same network, or MSCs in different networks. (It has been
referred to as Mobile Telephone Switching Office, MTSO.) It
provides the interface for user traffic between the wireless
network and other public switched networks, or other MSCs.

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Mobility Security Association

A collection of security contexts, between a pair of nodes, which
may be applied to Mobile IP protocol messages exchanged
between them. Each context indicates an authentication algorithm
and mode, a secret (a shared key, or appropriate public/private
key pair), and a style of replay protection in use.

17
18
19
20
21
22

Packet Data Session

PDSN Routes MS originated or MS terminated packet data

traffic. A PDSN establishes, maintains and terminates link layer
sessions to mobile stations. An instance of use of packet data
service by a mobile user. A packet data session begins when the
user invokes packet data service. A packet data session ends
when the user or the network terminates packet data service.
During a particular packet data session, the user may change
locations but the same IP address is maintained.

Physical Channel

A physical path between the SDU function and the mobile

station that consists of any connecting A3 traffic channel(s) and
radio channel(s). Depending on the radio technology in use, a
physical channel may be in soft handoff between the mobile
station and the SDU function.

SDU Function

The SDU function (Selection/Distribution Unit function) includes

the following functions:

23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

Traffic Handler: This function exchanges traffic bits with the

associated vocoder or CDMA RLP function, or is directly
connected to the A5 interface.
Signaling Layer 2:
This function performs the layer 2
functionality of the air interface signaling protocol and is
responsible for the reliable delivery of layer 3 signaling messages
between the base station and the mobile station.
Multiplex Sublayer: This function multiplexes and demultiplexes
user traffic and signaling traffic for the air interface.

46

18

TIA/EIA/IS-2001

Power Control: This function administrates the forward and

reverse link power control in a CDMA system. This function and
the channel element provide the power control function for the
CDMA operation. As part of this function, it generates or
utilizes relevant power control information that is exchanged over
the air interface or with the channel element.

2
3
4
5
6
7

Frame Selection/Distribution: This function is responsible for

selecting the best incoming air interface reverse link frame from
the channel elements involved in the soft handoff. It also
distributes forward air interface frames to all channel elements
involved in a call.

8
9
10
11
12

Backhaul Frame Handler: This function demultiplexes the control

information and the air interface reverse frame from the frame
received over the backhaul network. It also multiplexes the
control information and the air interface frames in the forward
direction.

13
14
15
16
17

External Frame Handler: This function exchanges backhaul

frames with channel elements which are remote from the Selector.

18
19

21

Intra-BS Frame Handler: This function exchanges backhaul

frames with channel elements involved in intra-BS soft handoff.

22

Control: This function provides control functions.

20

Security Parameter Index

Security Parameter Index (SPI) is an index identifying a security

context between a pair of nodes among the contexts available in
the Mobility Security Association. SPI values 0 through 255
are reserved and are not used in any Mobility Security
Association.

Service Instance

An instance of a higher level communication service between the

mobile station user and various other endpoints.

Service Provider Network

A network operated by either the home service provider or the

visited service provider. The home service provider maintains
the customer business relationship with the user. The visited
service provider provides access services through the
establishment of a service agreement with the home service
provider.

36

Serving Network

The network that provides access services to the user.

37

Signaling Connection

A connection intended to provide a path for signaling traffic.

23
24
25
26
27
28
29
30
31
32
33
34
35

19

TIA/EIA/IS-2001

Source Base Station

The BS that is in control of the call is designated the source BS

and remains the source BS until it is removed from control of the
call.

Target Base Station

Any BS that supports the call other than the source BS is

designated as a target BS.

Transcoder

A device that transforms signals from one type of digital

representation to another.

Uplink

The direction of BS to MSC.

2
3
4
5
6
7
8

20

TIA/EIA/IS-2001

1.7

Interface Model
The 3GPP2 Network Reference Model is a logical reference model as shown below in
TSB-100.

2
3
4

6
7
8
9
10
11
12
13

1.7.1

Reference Points A, Ater, and Aquater

The TIA TR45 Network Reference Model contains reference points A, A ter, and A quater
that are implemented by the protocols and interfaces of this standard. The A interface
is implemented by the interfaces indicated below:
A1, A2, A5
The A ter reference point is implemented by:
A3 and A7.
The A quater reference point is implemented by:
A10 and A11.

21

TIA/EIA/IS-2001

2
3
4
5
6

1.7.2

Interface Reference Model

The interfaces defined in this standard are described below.
A1
The A1 interface carries signaling information between the Call Control
(CC) and Mobility Management (MM) functions of the MSC and the call
control component of the BS (BSC).
A2

The A2 interface carries 64/56 kbits/sec PCM information (voice/data)

between the Switch component of the MSC and one of the following:
the channel element component of the BS (in the case of an analog air
interface), and

8
9

the Selection/Distribution Unit (SDU) function (in the case of a voice call
over a digital air interface),

10
11

A3

The A3 interface carries coded user information (voice/data) and signaling

information between the SDU function and the channel element
component of the BS (BTS). This is a logical description of the endpoints
of the A3 interface. The physical endpoints are beyond the scope of this
specification. The A3 interface is composed of two parts: signaling and
user traffic. The signaling information is carried across a separate logical
channel from the user traffic channel, and controls the allocation and use
of channels for transporting user traffic.

A5

The A5 interface carries a full duplex stream of bytes between the

Interworking Function (IWF) and the SDU function.

A7

The A7 interface carries signaling information between a source BS and a

target BS.

24

A8

The A8 interface carries user traffic between the BS and the PCF.

25

A9

The A9 interface carries signaling information between the BS and the

PCF.

27

A10

The A10 interface carries user traffic between the PCF and the PDSN.

28

A11

The A11 interface carries signaling information between the PCF and the
PDSN.

12
13
14
15
16
17
18
19
20
21
22
23

26

29

22

TIA/EIA/IS-2001

1
2
3

This is a logical architecture that does not imply any particular physical implementation. Figure
1-2 shows the relationship among network components in support of mobile originations, mobile
terminations, and direct BS-to-BS soft/softer handoff operations.

MSC

Call Control,
Mobility

IWF

Switch

Management.

(This interface is not included

in this specification.)

A1

A2

A5

Source BS

Target BS
A3(user traffic)
BSC
A3(signaling)

BSC

A8 (user traffic)

SDU

A9 (signaling)

A10 (user traffic)

PCF

A11 (signaling)

PDSN

Function
A7 (signaling)

BTS

BTS

Aquater Reference
Point

Ater Reference
Point

5
6
7

Figure 1- 2 - Reference Model for Digital Air Interfaces

The A3 interface is used for inter-BS soft/softer handoff when a target BS is attached to
the frame selection function within the source BS.

9
10
11
12
13
14
15
16
17
18
19

The A5 interface is used to provide a path for user traffic for circuit-oriented data calls
between the source BS and the MSC.
The A7 interface is used between the source BS and the target BS for inter-BS
soft/softer handoff.
The A8 interface is used to provide a path for user traffic between source BSC and PCF
for packet data services.
The A9 interface is used to provide a signaling connection between source BSC and
PCF for packet data services.
The A10 interface is used to provide a path for user traffic between a PCF and a PDSN
for packet data services.

21

The A11 interface is used to provide a signaling connection between a PCF and a PDSN
for packet data services.

22

For this standard, the circuit-oriented data IWF is considered to be located at the MSC.

20

23

TIA/EIA/IS-2001

1.7.3

MSC BS Functional Partitioning

The functions provided by the network elements on either side of the MSC-BS Interface
define the functions that the MSC-BS Interface supports. Figure 1- 3 below depicts a
model of the MSC-BS Interface functional planes. The four functional planes embody all
of the functions that the MSC-BS Interface supports.

2
3
4
5

Call
Processing
&
Supp.
Services

Radio
Resources
Mngmnt.

Mobility
Mngmnt.

Call
Processing
&
Supp.
Services

Trans.
Facilities
Mngmnt.

Transport
Protocols

Radio
Resources
Mngmnt.

Mobility
Mngmnt.

Trans.
Facilities
Mngmnt.

Transport
Protocols

Physical Facilities
6
7

Figure 1- 3 - MSC-BS Interface Functional Planes

The transmission facilities management plane is the basis for the MSC-BS Interface
telecommunications services. It manages the transmission means for the communication
needs of the subscribers as well as the required information transfer between the BS
and MSC. The radio resource management plane manages stable links between the MSs
and the MSC and supports the movement of subscribers during calls (i.e., handoff
control). The mobility management plane manages subscriber databases and subscriber
location data. The call processing plane manages call control and telecommunications
services for the subscribers.

9
10
11
12
13
14
15

24

TIA/EIA/IS-2001

1.7.4

Information Flows
The interfaces defined in this standard provide:

bearer (user traffic) connections (A2, A3(traffic), A5, A8, and A10),

a signaling connection between the channel element component of the BS and

the SDU function (A3signaling),

a direct BS to BS signaling connection (A7),

a signaling connection between the BS and the MSC (A1),

a signaling connection between the BS and PCF (A9),

a signaling connection between a PCF and PDSN pair (A11). A11 signaling
messages are also used for passing accounting related and other information
from the PCF to the PDSN,

10
11
12
13
14

In general, the functions specified on the interfaces are based on the premise that the
interfaces carry signaling information that traverses the following logical paths:
between the BS and MSC only (e.g., BS management information);

between the MS and the MSC via the BS (e.g., the BS maps air interface
messages to the MSC-BS Interface);

between the BS and other network elements via the MSC (e.g., mobility
management messages to the HLR);

19

between the source BS and the target BS;

20

between the BS and the PCF; and

21

between the PCF and the PDSN.

22

between the MS and the PDSN (e.g., Authorization information and MIP
signaling).

15
16
17
18

23

24
25
26
27

These logical paths define all of the traffic that can exist on the defined interfaces. To
support these logical paths, the interfaces of this standard can be described by the
following characteristics:
physical and electromagnetic parameters;

28

channel structures; and

29

message types and contents.

25

TIA/EIA/IS-2001

1.7.5

Protocol Reference Model

1.7.5.1

MSC-BS interface Channel Types

The MSC-BS interface consists of user traffic channels and signaling channels. In
general, user traffic channels are independent of signaling channels. Different paths
and different underlying transport technologies can be employed for each.

4
5
6

1.7.5.2

The MSC-BS interface referred to within this specification is designed to support a wide
range of implementations.

8
9

10

1.7.5.2.1

1.7.5.2.2

14

16
17
18
19
20
21

Layer 2 - Transport Protocols

This standard specifies multiple protocols for the transport of signaling and user
information. See section 5.

13

15

Layer 1
The physical interface is based on the layer 1 interfaces defined in section 5.

11

12

Transport Protocols

1.7.5.2.2.1

SS7 Signaling Transport

When SS7 is used to provide signaling transport, the underlying transport mechanism
defined to carry signaling information between the BS and the MSC is the Message
Transfer Part (MTP), and the Signaling Connection Control Part (SCCP) of Signaling
System No. 7 (SS7).
The MTP and SCCP are used to transport the application layer signaling protocol which
is defined as the BS Application Part (BSAP).

26

TIA/EIA/IS-2001

1.7.5.2.2.2

ATM Transport

When ATM is used to provide signaling transport, the AAL5 protocol is employed.

When ATM is used to provide user traffic transport, the AAL2 protocol is used. The
procedures defined in section 3 determine the allocation and use of the logical channels,
i.e., the connection identifiers (CIDs) that AAL2 provides over an ATM virtual circuit.

4
5

Each BS has two or more ATM virtual circuits that connect it to other BSs (regardless
of whether switched or permanent virtual circuits are used). These virtual circuits are
comprised of one or more virtual circuits using the AAL5 protocol for signaling, and
one or more virtual circuits using AAL2 for the user traffic connections.

6
7
8
9

10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

1.7.5.3

Layer 3 - A1 Interface: Base Station Application Part

The Base Station Application Part (BSAP) is the application layer signaling protocol
that provides messaging to accomplish the functions of the A1 Interface component of
the MSC - BS Interface. BSAP is split into two sub-application parts; the BS
Management Application Part (BSMAP), and the Direct Transfer Application Part
(DTAP). Please refer to Figure 1-4 A1 Interface Signaling Protocol Reference Model
for an illustration of this structure.
The BS Management Application Part (BSMAP) supports all Radio Resource
Management and Facility Management procedures between the MSC and the BS, or to
a cell(s) within the BS. BSMAP messages are not passed to the MS, but are used only
to perform functions at the MSC or the BS. A BSMAP message (Complete Layer 3
Information) is also used together with a DTAP message to establish a connection for a
MS between the BS and the MSC, in response to the first layer 3 air interface message
sent by the MS to the BS for each MS system request. The description of the layer 3
protocol for the BSMAP information exchange is contained within this specification.
The Direct Transfer Application Part (DTAP) messages are used to transfer call
processing and mobility management messages between the MSC and BS. DTAP
messages carry information that is primarily used by the MS. The BS shall map the
DTAP messages going to and coming from the MSC from/into the appropriate air
interface signaling protocol.
In section 6.2.2.4, Table 6-8 lists the BSMAP messages and Table 6-9 lists the DTAP
messages.

BS side

A Interface

BSAP
DTAP

MSC side
BSAP

BSMAP

DTAP

Transport
Protocol(s)

BSMAP

Transport
Protocol(s)
Physical Layer

32

27

TIA/EIA/IS-2001

1
2

Figure 1- 4 - A1 Interface Signaling Protocol Reference Model

Abbreviations used in Figure 1-4:

BS

Base Station

BSAP

Base Station Application Part

BSMAP Base Station Management Application Part

DTAP

Direct Transfer Application Part

MSC

Mobile Switching Center

28

TIA/EIA/IS-2001

1.7.6

Packet Data Micro-Mobility and Macro-Mobility Concepts

The figure below provides a conceptual view of levels of packet data mobility.

The figure below provides a conceptual view of levels of packet data mobility.
Home Agent
Mobility between PDSNs
(Mobile IP)
PDSN

PDSN

Mobility between PCFs

(A10/A11 Interfaces)
PCF

PCF

PCF
Mobility between BSCs
(A8/A9 Interfaces)

BSC

BSC

BSC

BSC
Mobility between BTSs
(Intra-BS Hard Handoff)

BTS
4

BTS

BTS

BTS

BTS

BTS

BTS

5
6
7

Figure 1- 5 Harmonized Architecture for Packet Data

The A8/A9 interfaces support mobility between BSCs under the same PCF.

The A10/A11 interfaces support mobility between PCFs under the same PDSN.

10

Mobile IP supports mobility between PDSN/FA under the same Home Agent.

11

Hard handoff and soft handoff procedures realize the mobility between BTSs

12
13
14
15
16
17
18

29

TIA/EIA/IS-2001

2.

In some of the call processing and services functions described below, it is possible
that an inter-BS hard handoff may occur during the process. In such an event, the target
BS (i.e., the BS to which the MS has been handed off) shall assume responsibility for
functionality ascribed to the BS as defined herein. For example, if an inter-BS hard
handoff occurs during a mobile terminated call setup while the MS is in the Waiting for
Answer state, the new serving BS shall send a Connect message to the MSC upon
receipt of the Connect Order message on the air interface even though that BS was not
involved with previous portions of the call setup process.

3
4
5
6
7
8
9
10

11

2.1

Call Control
Call control shall be primarily the responsibility of the MSC. The BS provides message
transmission and inter-working between the particular air interface and the MSC.

12
13

14

Call Processing and Supplementary

Services

2.1.1

Terrestrial Circuit Allocation

15

Terrestrial Circuit allocation will be handled in the following manner:

16

The MSC will consider the interface to the BS as a route of n circuits. The MSC shall
therefore ensure that the terrestrial circuit chosen is able to support the type of call
involved.

17
18

The BS may suggest a preferred terrestrial circuit to the MSC; however, the MSC shall
choose the terrestrial circuit to be used.

19
20

The terrestrial Circuit allocation procedure is further described in section 2.2.1.5,

Assignment Request.

21
22

23

2.1.2

The BS may choose the radio channel to be used on the appropriate cell in the case of
multi-cell BSs. This may be based on information received from the MSC.

24
25

26

27
28

Radio Channel Allocation

2.1.3

Traffic Channel Release

The release of a dedicated resource is primarily controlled by the MSC. However, for
radio propagation reasons, the BS can request that the MSC release a call.

30

TIA/EIA/IS--2001

2.2

Procedures for setup of mobile originated and terminated voice and circuit data calls are
described in this section. Call setup is a process where a sequence of messages is used
to advance the call to a stable condition where the parties involved may communicate.
A1 procedures for packet data calls are specified in sections 2.14 and 2.15 of this
document.

3
4
5
6
7

The individual messages used in these procedures have their type (DTAP or BSMAP)
defined and their formats shown in section 6.1, Message Definitions. Definitions of
the elements comprising these messages are contained in section 6.2, Information
Element Definitions. Details of the usage of each message are contained in the
following subsections.

8
9
10
11
12

For details on call clearing procedures please refer to section 2.3, A1Interface Call
Clearing Procedures. For definitions of timers listed in this section, please refer to
section 6.3, Timer Definitions.

13
14
15

16

A1 Interface Call Setup for Voice and Circuit Data

Calls

2.2.1

Mobile Originated Calls

The following subsections describe the procedure for establishing a call through a
mobile originated action. The call setup may be a normal call setup, emergency call
setup, PACA call setup, packet data call setup, or supplementary service invocation.

17
18
19

25

If PACA service is requested during call origination the base station can use either a
queuing approach or a channel reservation approach for allocating radio resources (see
TIA/EIA-664). The mechanism to reserve channels using the channel reservation
approach is not specified in this standard. The procedure for call origination with PACA
service using a queuing approach is specified in section 2.2.2.1 and 2.2.2.3. PACA
related messages are described in section 2.11.

26

Mobile originated call setup involves exchange of the following MSC-BS messages:

20
21
22
23
24

27

Complete Layer 3 Information with Connection Management (CM) Service Request

28

Assignment Request

29

Assignment Failure

30

Assignment Complete

31

Progress

32

PACA Command

33

PACA Command Ack

34

PACA Update
PACA Update Ack

35

The CM Service Request message to the MSC is used to initiate a mobile originated call
setup. Please refer to section 2.5, Support of Supplementary Services for details.

36
37

38
39
40
41

2.2.1.1

Connection Management (CM) Service Request

When the mobiles originating access attempt is received by the BS, the BS constructs
the CM Service Request DTAP message, places it in the Complete Layer 3 Information
message, and sends the message to the MSC.
31

TIA/EIA/IS-2001

2.2.1.1.1

In a mobile origination scenario, the BS starts timer T303. The BS transfers a CM Service
Request message to the MSC. The Complete Layer 3 Information message and the MSC
response are also used for connection establishment

2
3
4

In the Access Probe Handoff scenario, the source BS (the BS on which the first access
probe was sent), upon receiving an origination request for the same mobile and the
same call forwarded via an A7 connection from another BS, may choose to send a
second CM Service Request to the MSC. The MSC shall be able to handle a CM
Service Request for a mobile that is already engaged in an origination attempt by
sending a Clear Command message to the BS containing a cause value of Do not
notify MS.

5
6
7
8
9
10
11

The base station may select an available channel based on the mobiles capabilities, and
assign the MS to that channel at any time following the receipt of the mobiles
originating access.

12
13
14

For information on the Authentication and Privacy procedures refer to section 4.2,
Authentication and Privacy.

15
16

Please refer to section 6.1.2.2, CM Service Request for the format and content of this
message.

17
18

19

2.2.1.1.2

21
22
23
24
25

2.2.1.1.3

28

2.2.1.2

31
32

2.2.1.2.1

35

37
38
39
40
41

Successful Operation
Please refer to section 6.1.2.1, Complete Layer 3 Information, for the format and
content of this message.

34

36

Complete Layer 3 Information

The Complete Layer 3 Information message is a BSMAP message that contains the CM
Service Request message, the Paging Response message, or the Location Updating
Request message.

30

33

Abnormal Operation
If the MSC wishes to clear the call in response to the CM Service Request, it may refuse
the connection request via the primitive appropriate to the underlying transport layer.

27

29

Failure Operation
If the BS fails to receive an Assignment Request message, PACA Command message
(e.g., if the call is eligible for PACA service), or Clear Command message in response to
the CM Service Request message prior to expiration of timer T303, then it may send a
Reorder or Release message to the MS, and shall initiate call clearing by sending a Clear
Request message to the MSC with the cause value set to Timer expired if an
underlying transport connection exists.

20

26

Successful Operation

2.2.1.2.2

Failure Operation
Please refer to section 2.2.1.1.2, Failure Operation, when this message is used in
conjunction with the CM Service Request message. Please refer to section 2.2.3.2.2
when this message is used in conjunction with the Paging Response message. Please
refer to section 4.1.2.3.2 when this message is used in conjunction with the Location
Updating Request message.

32

TIA/EIA/IS--2001

2.2.1.3

UNUSED SECTION (Setup)

2.2.1.4

UNUSED SECTION

2.2.1.5

Assignment Request

3
4

This BSMAP message is sent from the MSC to the BS to request assignment of radio
resources.

6
7

2.2.1.5.1

After sending this message to the BS, the MSC starts timer T10 and waits for the
Assignment Complete message from the BS.

9
10

The BS stops timer T303 upon receipt of the Assignment Request message, selects a
traffic channel, sends the Channel Assignment Message to the MS, and waits for the
confirmation from the MS that the MS reached the assigned traffic channel.

11
12
13

Please refer to section 6.1.2.15, Assignment Request for the format and content of this
message.

14
15

16

2.2.1.5.2

18

2.2.1.6

21
22
23

2.2.1.6.1

26

When the MSC receives this message, it stops timer T10. At this point the MSC
considers the call in conversation state.

27
28

Please refer to section 6.1.2.16, Assignment Complete, for the format and content of
this message.

29
30

2.2.1.6.2

34
35

Failure Operation
None.

32

33

Successful Operation
When the MS has successfully reached the assigned traffic channel, the BS sends this
message to the MSC. At this point the BS considers the call in conversation state.

25

31

Assignment Complete
This BSMAP message indicates that the requested assignment has been completed
correctly. The sending of the Assignment Complete message also indicates to the MSC
that it will henceforth be responsible for providing in-band treatment of the call if
required.

20

24

Failure Operation
If the MSC fails to receive an Assignment Complete message, or an Assignment Failure
message before the expiration of timer T10, then it shall initiate call clearing.

17

19

Successful Operation

2.2.1.7

Assignment Failure
This BSMAP message is sent from the BS to the MSC to indicate that the requested
assignment procedure could not be successfully completed.

33

TIA/EIA/IS-2001

2.2.1.7.1

Upon recognizing that the assignment can not be completed, the BS sends the
Assignment Failure message, starts timer T20 and waits for the MSC to respond with an
Assignment Request message or a Clear Command message.

2
3
4

Please refer to section 6.1.2.17, Assignment Failure, for the format and content of this
message.

5
6

2.2.1.7.2

Failure Operation
If timer T20 expires, the BS shall send a Clear Request message to the MSC.

Successful Operation

2.2.1.8

UNUSED SECTION

2.2.1.9

Progress

10

11

This DTAP message may be sent by the MSC during any Call Control session to
specify local tone generation or removal.

12
13

14

2.2.1.9.1

Successful Operation
When the BS receives the Progress message from the MSC it takes the appropriate
action to request the MS to generate the tone as indicated.

15
16

19

The MSC should delay sending any call clearing message after a Progress message to
allow the local tone generation at the MS. In addition, the BS may need to be aware of
the time needed by the MS to generate the local tone.

20

Please refer to section 6.1.2.12, Progress, for the format and content of this message.

17
18

21

2.2.1.9.2

None.

22

23

Failure Operation

2.2.1.10

UNUSED SECTION

2.2.1.11

UNUSED SECTION 2.2.1.12

2.2.1.13

UNUSED SECTION

24

25

UNUSED SECTION

26

27
28

2.2.1.14 UNUSED SECTION

29

30

2.2.1.15

UNUSED SECTION

2.2.2

Mobile Origination Examples

31

32

33

34

TIA/EIA/IS--2001

2.2.2.1

Mobile Origination
This section describes the call flow associated with a mobile station call origination in
the system.

2
3

time
MS

BS

comment

MSC

Origination Message
a
Base Station Ack Order

b
Complete L3 Info: CM Service Request
T303

Assignment Request
d

Channel Assignment Message

e
Tch Preamble
f
BS Ack Order
g
MS Ack Order
h
Service Connect Message

i
T10

Service Connect Completion

j
Assignment Complete
Ringback Tone

k
l

Transparent to
signaling

4
5
6
7

Figure 2-1 - Mobile Origination

a.

The MS transmits an Origination Message, with layer 2 acknowledgment

required, over the access channel of the air interface to the BS to request
service.

b.

The BS acknowledges the receipt of the Origination Message with a Base

Station Acknowledgment Order to the MS.

8
9
10
11
12
13
14

If the BS can determine that resources, e.g., a traffic channel, are not available,
the BS may perform the PACA procedure described in section 2.2.2.3.1.
Otherwise, the call is allowed to proceed.

35

TIA/EIA/IS-2001

c.

2
3
4

If the global challenge is used, the MSC will continue the call setup process
while waiting for an authentication confirmation. If an authentication failure
indication is received at the MSC, it may clear the call. Some in-band treatment
may be provided on discretion of the MSC manufacturer, e.g., tone or
announcement, assuming the BSC has already done channel assignment.

5
6
7
8
9
10

d.

11
12
13

15
16
17

If the Include Priority bit of the Radio Environment and Resources element
was set to 1 in the CM Service Request message to indicate that no lower
priority channels are available (e.g., when a PACA channel reservation scheme
is used) the MSC shall include the actual call priority.

18
19
20
21

Upon receipt of the Assignment Request message from the MSC, the BS stops
timer T303.

22
23

e.

25
26
27

29
30
31
32
33
34

When a traffic channel becomes available, the BS will instruct the MS to reoriginate the call by sending a PACA Message.

35
36

f.

The MS begins sending the traffic channel preamble (TCH Preamble) over the
designated reverse traffic channel.

g.

Once the BS acquires the reverse traffic channel, it sends the Base Station
Acknowledgment Order, with layer 2 acknowledgment required, to the MS over
the forward traffic channel.

h.

The MS acknowledges the reception of the BS Ack Order by transmitting the

Mobile Station Acknowledgment Order and by sending null traffic channel
data (Null TCH Data) over the reverse traffic channel.

i.

The BS then sends the Service Connect Message / Service Option Response
Order to the MS specifying the service configuration for the call. The MS
begins processing traffic in accordance with the specified service
configuration.

38
39
40
41
42
43
44
45
46
47
48

If a traffic channel is available for the call, the BS sends a Channel Assignment
Message over the paging channel of the radio interface (with the MS address)
to initiate the establishment of a radio traffic channel, if the MS is not already
on a traffic channel.
If for any reason the BS is unable to assign resources (e.g., a traffic channel)
for this call and the call is given PACA service, the BS will queue the request
and will notify the MS of the reason and the current queue position (see
section 2.2.2.3.1). The BS will then send an Assignment Failure message to the
MSC with the Cause field set to PACA Call Queued. The MSC initiates
normal call clearing procedure as described in section 2.3 to release the
underlying transport connection.

28

37

The MSC sends an Assignment Request message to the BS to request

assignment of radio resources. This message will include information on the
terrestrial circuit, if one is to be used between the MSC and the BS. The MSC
then starts timer T10.
If the BS requested a preferred terrestrial circuit in the CM Service Request
message and the MSC can support that terrestrial circuit, the MSC shall use
the same terrestrial circuit in the Assignment Request message. Otherwise, the
MSC may assign a different terrestrial circuit.

14

24

The BS constructs the CM Service Request message, places it in the Complete

Layer 3 Information message, sends the message to the MSC, and starts timer
T303. For circuit switched calls, the BS may request the MSC to allocate a
preferred terrestrial circuit.

36

TIA/EIA/IS--2001

j.

On receipt of the Service Connect Message, the MS responds with a Service

Connect Completion Message.

k.

After the radio traffic channel and circuit have both been established and fully
interconnected, the BS sends the Assignment Complete message to the MSC
and considers the call to be in conversation state.

The MSC stops timer T10 upon receipt of the Assignment Complete message.

1
2
3
4

l.

7
8

9
10
11
12
13
14

15
16
17
18
19
20

2.2.2.2

As call progress tone is applied in-band in this case, ringback tone will be
available on the audio circuit path towards the MS.

Mobile Origination with Access Probe Handoff, Access Handoff and Channel
Assignment into Soft/Softer Handoff
This section describes the call flow associated with the mobile origination with the
Access Probe Handoff, Access Handoff and Channel Assignment into Soft Handoff
using the source BS (the base station on which the first probe was sent). The same
technique applies to the mobile termination case.
The access handoff, access probe handoff, and channel assignment into soft handoff
functions shown in the following diagram are not all necessarily required for each call
setup. The diagram gives an example of a call where all three are used, but that will not
be the case for all calls. In this section, A3-CEData Forward/Reverse messages
represent A3-IS-95 FCH Forward/Reverse, A3-IS-2000 FCH Forward/Reverse, or
A3-IS-2000 DCCH Forward/Reverse messages.

37

TIA/EIA/IS-2001

Source
BS

MS

Target
BS-1

Target
BS-2

time

Target
BS-3

comment

MSC

Origination Message (I)

x
Origination Message (II)

a
b

Base Station Ack Order

Source BS was
attempted first
Access probe handoff
to target BS-1

x
A7-Access Channel Message Transfer

Tacm

A7-Access Channel Message Transfer Ack

Complete L3 Info: CM Service Request

A7-Handoff Request
g
T303
A3-Connect

These messages are

used to set up soft
handoff legs for
channel assignment
into soft handoff.

h
Tconn3

A3-Connect Ack

i
Thoreq

A3-CEData Forward
j

Tchanstat

A3-CEData Reverse
k
A3-Traffic Channel Status
l
A7-Handoff Request Ack
m

Origination Message (III)

Base Station Ack Order

A7-Access Channel Message Transfer

Tacm

A7-Access Channel Message Transfer Ack

Access probe handoff

to target BS-2
Access probe
handoff ends

Assignment Request

A7-Paging Channel Message Transfer

s

x
x

Extended Channel Assignment Message

t
Pilot Preamble

Access handoff to
target BS-3

T10
u
SCENARIO CONTINUES
NEXT PAGE

1
2
3

Figure 2-2 - Mobile Origination with Access Probe Handoff, Access Handoff and
Channel Assignment into Soft/Softer Handoff

38

TIA/EIA/IS--2001

MS

Source
BS

Target
BS-1

Target
BS-2

time

Target
BS-3

comment

MSC

Base Station Ack Order

MS Ack Order

SCENARIO CONTINUED
FROM PREVIOUS PAGE

w
T10

Service Connect Message

Service Connect Completion Message

x
y

Assignment Complete

1
2
3
4
5
6
7
8
9
10
11
12

Figure 2-2 (continued) Mobile Origination with Access Probe Handoff, Access
Handoff and Channel Assignment into Soft/Softer Handoff
a. The MS transmits an Origination Message (Origination (I)), with layer 2
acknowledgment required, over the access channel of the air interface to the
source BS to request service. Because this BS is the first to which the MS
sends an access probe, it becomes by definition the source BS for this call
setup attempt. In this message the mobile station reports the pilot strength of
all the pilots in the mobile stations Paging Channel Active Set. It also reports
other pilots using the ACCESS_HO_LIST and the OTHER_REPORTED_LIST
(see TIA/EIA/IS-2000). This message is not received by the source BS.
b.

The MS performs an access probe handoff and sends a second Origination

Message (Origination (II)), with layer 2 acknowledgment required, over the
access channel of the air interface to the target BS-1 to request service. Note
that the target BS-1 may not have been in the ACCESS_HO_LIST in step a.

c.

The target BS-1 acknowledges the receipt of the Origination message with a
Base Station Acknowledge Order to the MS. The BS Ack Order is not received
by the MS.

d.

The target BS-1 recognizes that it is not the first accessed BS and encapsulates
the Origination message received from the MS in the A7-Access Channel
Message Transfer message and forwards it to the source BS instead of
sending the CM Service Request message to the MSC. The target BS-1 starts
timer Tacm.

e.

The source BS acknowledges the A7-Access Channel Message Transfer

message by sending an A7-Access Channel Message Transfer Ack message
to the target BS-1. The target BS-1 stops timer Tacm.

f.

The source BS constructs the CM Service Request message, places it in the

Complete Layer 3 Information message, sends the message to the MSC, and
starts timer T303. The BS may request the MSC to allocate a preferred
terrestrial circuit.

13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

39

TIA/EIA/IS-2001

g.

Since the Origination message to the source BS carries the pilot report of other
strong pilots, the source BS initiates the inter-BS soft handoff setup procedure
by sending the A7-Handoff Request message to one or more target BSs. (In
this example scenario, the source BS chooses Target BS-1 Target BS-2 and
Target BS-3). The Source BS starts an instance of timer Thoreq for each A7
Handoff Request message sent. Alternatively the initiation of soft handoff
may be performed after receiving the Assignment Request message from the
MSC.

h.

The target BSs initiate A3 connections by sending A3-Connect messages to

the specified address. Each target BS starts an instance of timer Tconn3.

i.

The source BS replies with A3-Connect Ack messages to complete the A3

connections. Target BSs stop timer Tconn3. The Source BS starts an instance
of timer Tchanstat for each A3 Connect Ack message sent if the source BS
wishes to receive A3-Traffic Channel Status messages from the target BSs..

15

j.

The source BS begins to send idle forward frames to the target BSs.

16

k.

The target BSs begin to send reverse idle frames as soon as the first forward
frame is received from the source BS. The reverse frames contain the timing
adjustment information necessary to achieve synchronization.

l.

If the source BS has chosen to be notified of the start of transmission and

reception at the target BSs, when its SDU function and the target BSs have
synchronized the A3 traffic subchannel, the target BS replies with an A3Traffic Channel Status message. See section 3.4.1.1.2. Note that this step can
occur any time after step (i). The source BS stops Tchanstat timers.

1
2
3
4
5
6
7
8
9
10
11
12
13
14

17
18
19
20
21
22
23

27

m. Target BS-1, target BS-2 and target BS-3 send A7-Handoff Request Ack
messages to the source BS to complete the soft handoff setup procedure.
Note that this message can be sent at any time following the receipt of the A3Connect Ack messages at each target BS. The Source BS stops Thoreq timers.

28

n.

24
25
26

29
30
31
32

Note that the ACCESS_HO_LIST identifies the source BS as the first

attempted, and that target BS-1 and target BS-2, which may not have been
included in the ACCESS_HO_LIST in step a, are included in the
ACCESS_HO_LIST in this step.

33
34
35
36
37

o.

Target BS-2 responds with a Base Station Ack Order to the MS. The MS
receives the Base Station Ack Order, which successfully completes the access
attempt.

p.

The target BS-2 recognizes that it is not the first accessed BS (i.e., the source
BS) and encapsulates the Origination message received from the MS in the A7Access Channel Message Transfer message and forwards it to the source BS
instead of sending the CM Service Request message to the MSC. The target
BS-2 starts timer Tacm.

38
39
40
41
42
43
44

The MS did not receive the layer 2 acknowledgment in response to the

Origination message at step c; therefore, it performs an access probe handoff
to target BS-2, and sends a third Origination message (Origination (III)) with
the first accessed base station identified and with layer 2 acknowledgment
required.

40

TIA/EIA/IS--2001

q.

2
3

The source BS upon receiving the Origination Message from the target- BS-2
for the same MS and the same call may send a second CM Service Request to
the MSC, though this option is not shown in this example. Upon receipt of the
A7-Access Channel Message Transfer Ack message the target BS-2 stops
timer Tacm.

4
5
6
7
8
9

r.

The MSC sends an Assignment Request message to the source BS to request

assignment of radio resources. This message will include information on the
terrestrial circuit, if one is to be used between the MSC and the BS. The MSC
then starts timer T10. Upon receipt of the Assignment Request message from
the MSC, the BS stops timer T303. This step may occur any time after step f.

s.

After receiving the Assignment Request message from the MSC and
optionally receiving A3-Connect messages from the potential target BSs, the
source BS constructs an air-interface Extended Channel Assignment message
and forwards it in the A7-Paging Channel Message Transfer message to one or
more base stations, usually chosen from those that are in the
ACCESS_HO_LIST and OTHER_REPORTED_LIST (which may not be the
same BSs set up in soft handoff). The A7-Paging Channel Message Transfer
message may be sent any time after the A3 Connections are completed.

t.

The source BS and target BSs send the appropriate channel assignment
message over the air to the MS. The probability of the MS receiving this
message is substantially increased by sending this message from multiple base
stations. In the meantime, the MS has performed an access handoff to target
BS-3. Since the MS is listening to the paging channel of only one base station,
it does not receive the Extended Channel Assignment Message from any other
BSs than target BS-3. At any time after sending/receiving the A7-Paging
Channel Message Transfer message, all soft handoff legs on the source BS
and target BS begin sending null forward traffic frames to the MS.

u.

After receiving the Extended Channel Assignment Message from the target
BS-3 and the forward traffic frames from one or more base stations, the MS
starts sending the traffic frames or preambles.

10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

In steps v through y, the full activity of the messaging between the source BS
and the MS via the target BSs using A3-CEData Forward and A3-CEData
Reverse messages and transmission and reception of messages to and from
the MS by the target BSs is not shown for simplicity in the diagram.

34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49

The source BS acknowledges the A7-Access Channel Message Transfer

message by sending an A7-Access Channel Message Transfer Ack message
to the target BS-2.

v.

If a target BS detects reverse preamble, it sends it to the source BS in an A3CEData Reverse message.Once the source BS acquires the reverse traffic
channel, it sends the Base Station Acknowledgment Order, with layer 2
acknowledgment required, to the MS over the forward traffic channel. The
source BS also informs the target BSs that the reverse traffic channel was
acquired by starting to send non-idle frame content type in the A3-CEData
Forward messages. Upon receiving non-idle frame content in the A3-CEData
Forward messages, the target BS terminates any attempts to send the channel
assignment message to the MS.

w. The MS acknowledges the reception of the BS Ack Order by transmitting the

Mobile Station Acknowledgment Order and by sending null traffic channel
data (Null TCH Data) over the reverse traffic channel.

41

TIA/EIA/IS-2001

x.

The source BS then sends the Service Connect Message / Service Option
Response Order to the MS specifying the service configuration for the call.
The MS begins processing traffic in accordance with the specified service
configuration.

y.

On receipt of the Service Connect Message, the MS responds with a Service

Connect Completion Message.

z.

The source BS sends the Assignment Complete message to the MSC. At this
time, the MS is on the traffic channel and the call setup into soft/softer handoff
is completed successfully. MSC stops timer T10. At this time, the MS is setup
directly in soft/softer handoff with one or more base stations.

2
3
4
5
6
7
8
9
10

11

2.2.2.3

Two conditions may occur on a call origination with PACA service. In the first
condition, the BS can not determine that radio resources are not available for a call
before sending the CM Service Request message to the MSC. In this case the
origination procedure shown in section 2.2.2.1 is followed. In the second case, the BS
determines that radio resources are not available for a call before sending the CM
Service Request message. In this second case, the origination procedure shown in
section 2.2.2.3.1 below is followed.

12
13
14
15
16
17
18

19
20
21

Mobile Origination with PACA Service

2.2.2.3.1

Mobile Origination with PACA Service

This section describes the call flow associated with a mobile station call origination
with PACA service in the system.
time
MS

BS

MSC

Origination Message

Base Station Ack Order

Complete L3 Info: CM Service Request

T303

PACA Command
PACA Command Ack

c
d

Tpaca1
e

PACA Message
f
PACA Message

PACA Message

22
23

Figure 2-3 - Mobile Origination with PACA Service

42

comment

TIA/EIA/IS--2001

a.

The MS transmits an Origination, with layer 2 acknowledgment required, over

the access channel of the air interface to the BS to request service. The MS
sets the PACA_REORIG field to 0 to indicate a user-directed origination.

b.

The BS acknowledges the receipt of the Origination Message with a Base

Station Acknowledgment Order to the MS.

c.

The BS constructs the CM Service Request message, places it in the Complete

Layer 3 Information message, sends the message to the MSC, and starts timer
T303. The BS includes the Radio Environment and Resources elements in the
CM Service Request message. The Avail bit of the Radio Environment and
Resources element is set to 0 to indicate that resources at the BS are not
available. The PSI field in the Classmark Information Type 2 IE should be set to
1.

2
3
4
5
6
7
8
9
10
11
12

The MSC receives the call origination and dialed digits in the CM Service
Request message and determines that the call is eligible for PACA service.

13
14
15

d.

The MSC sends a PACA Command message to inform the BS that PACA
service shall be applied to this call. The PACA Command message includes the
Priority and the PACA Time Stamp information elements to provide
information to the BS for PACA queuing. The MSC starts timer Tpaca1. Upon
receipt of the PACA Command message the BS stops timer T303.

e.

Based on the information received in the PACA Command message the BS

queues the call. The BS sends a PACA Command Ack message to the MSC.
The MSC stops timer Tpaca1 after receiving the acknowledgment.

f.

The BS sends a PACA Message to the MS to indicate that the service request
has been queued and includes the queue position.

g.

The BS may optionally send additional PACA messages over the paging
channel to update the MS on its PACA queue position. The BS may resend
this message as needed until radio resources become available.

h.

When radio resources become available, the BS sends a PACA Message to

instruct the MS to re-originate the call. In this case, the PURPOSE field is set to
0010 to request PACA re-origination. The normal Origination procedure (see
section 2.2.2.1) will process the re-origination request.

16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

43

TIA/EIA/IS-2001

2.2.2.3.2

Mobile Origination, Idle Handoff with PACA Active

This section describes the call flow associated with mobile station call origination with
PACA active in the system while idle handoff occurs.

2
3

time
MS

New BS

comment

MSC

Old BS

Origination Procedure with PACA

Service Involving the Old BS

Origination Procedure with PACA

Service Involving the New BS

PACA Update
PACA Update Ack

Tpaca2
d

4
5
6

Figure 2-4 - Mobile Origination, Idle Handoff with PACA Active

a.

The MS previously attempted a call origination and the call has been queued
as in steps a through f of Figure 2-3.

b.

While approaching the boundary of the cell, the MS detects an adequately

strong pilot signal transmitted by one of the neighboring cells (new BS). The
MS performs an idle handoff and starts monitoring the new paging channel.
The MS then transmits an Origination Message, with layer 2 ack required, over
the access channel of the air interface to the new BS to request service. In this
case, the PACA_REORIG field received in the Origination Message is set to
1. The normal Origination procedure (see section 2.2.2.1) will process the reorigination request.

c.

The MSC sends a PACA Update message to instruct the old BS to remove the
service request from its PACA queue. The MSC can send the PACA Update
message anytime after receiving the CM Service Request message from the
new base station. The MSC starts timer Tpaca2.

d.

The BS sends a PACA Update Ack message to the MSC to confirm that
appropriate action has been taken by the BS and that its PACA information
has been updated. Upon receipt of the PACA Update Ack message the MSC
stops timer Tpaca2.

7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

44

TIA/EIA/IS--2001

2.2.2.3.3

Mobile Origination with PACA Active, Consecutive PACA Calls

This section describes the call flow associated with a successful mobile station call
origination with consecutive service requests in the system. In this scenario the MS
originates a call to another number while the first call request is in a PACA queue.

2
3
4

time
MS

BS

comment

MSC

Origination Procedure
with PACA Service

Origination Procedure
with PACA Service

PACA Update
PACA Update Ack

Tpaca2
d

5
6
7

Figure 2-5 - Mobile Origination with Consecutive PACA Call Requests

a.

The MS previously attempted a call origination and the call has been queued
as in steps a through f of Figure 2-3.

b.

While the first call request is pending, the MS sends an Origination Message,
with layer 2 ack required, over the access channel of the air interface to the BS
to request service using a different called party number. In this case, the
PACA_REORIG field received in the Origination Message is set to 0. The
normal Origination procedure (see section 2.2.2.1) will process the reorigination request.

c.

The MSC sends a PACA Update message to the BS with the PACA Order
indicating Remove MS from the queue. The MSC can send the PACA
Update message anytime after receiving the second CM Service Request
message. The MSC starts timer Tpaca2.

d.

The BS sends a PACA Update Ack message to the MSC to confirm that
appropriate action has been taken by the BS and that its PACA information
has been updated. Upon receipt of the PACA Update Ack message the MSC
stops timer Tpaca2.

8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

45

TIA/EIA/IS-2001

2.2.2.3.4

PACA Call Cancellation Initiated by the MS

This section describes the call flow associated with cancellation of a PACA queued call
in the system. In this scenario the cancellation is initiated by the MS.

2
3

time
MS

BS

comment

MSC

Origination Procedure
with PACA Service

PACA Cancel

BS Ack Order

c
PACA Update
d

Tpaca2

PACA Update Ack

4
5
6

Figure 2-6 - PACA Call Cancellation Initiated by the MS

a.

The MS previously attempted a call origination and the call has been queued
as in steps a through f of Figure 2-3.

b.

The MS sends a PACA Cancel Message, with layer 2 ack required, over the
access channel of the air interface to the BS to request the call be canceled.

c.

The BS acknowledges the receipt of the PACA Cancel Message with a Base
Station Acknowledgment Order to the MS.

d.

The BS cancels the call and removes the request from its PACA queue. The BS
then sends a PACA Update message to the MSC to indicate that the call has
been canceled. The BS starts timer Tpaca2.

e.

The MSC sends a PACA Update Ack message to the BS to confirm the receipt
of the PACA Update message. Upon receipt of the PACA Update Ack
message the BS stops timer Tpaca2.

7
8
9
10
11
12
13
14
15
16
17

46

TIA/EIA/IS--2001

2.2.2.3.5

PACA Call Cancellation Initiated by either MSC or BS

This section describes the call flow associated with cancellation of a PACA call in the
system. In this example scenario the cancellation is initiated by the MSC. The BSinitiated PACA call cancellation is identical except the BS sends the PACA Update
message to the MSC.

2
3
4
5

time
MS

BS

comment

MSC

Origination Procedure
with PACA Service

PACA Update

PACA Message

MSC decides to
cancel the
queued PACA
call.

c
Tpaca2

MS Ack Order

d
PACA Update Ack

6
7
8

Figure 2-7 - PACA Call Cancellation Initiated by the MSC

a.

The MS previously attempted a call origination and the call has been queued
as in steps a through f of Figure 2-3.

b.

The MSC sends a PACA Update message to the BS with the PACA Order
indicating Remove MS from the queue and release MS. The MSC starts timer
Tpaca2.

c.

The BS cancels the call and removes the request from its PACA queue. The BS
then sends a PACA Message (PURPOSE=0011) to the MS to indicate that
the PACA call has been canceled.

17

d.

The MS sends an MS Ack order to the BS to acknowledge PACA cancellation.

18

e.

The BS sends a PACA Update Ack message to the MSC to confirm that
appropriate action has been taken by the BS and that its PACA information
has been updated. Upon receipt of the PACA Update Ack message the MSC
stops timer Tpaca2.

9
10
11
12
13
14
15
16

19
20
21

47

TIA/EIA/IS-2001

2.2.3

Mobile Terminated Voice and Circuit Data Calls

The following subsections describe the procedure for establishing a voice or circuit
data call through a mobile terminated action. Mobile terminated packet data delivery is
specified in sections 2.14 and 2.15 of this document.

Mobile terminated call setup involves exchange of the following MSC-BS messages:

2
3

Paging Request

Complete Layer 3 Information with Paging Response

Assignment Request

Assignment Complete

10

Assignment Failure

11

Alert with Information

12

Connect

13

2.2.3.1

This BSMAP message is sent from the MSC to the BS to initiate a mobile terminated call
setup scenario. This message may also be sent for location purposes.

14
15

16

2.2.3.1.1

18
19
20

When the BS receives the Paging Request message from the MSC, it determines from
which cell(s) to broadcast the page request. The page messages are then distributed to
the appropriate cell(s), which then broadcast the page message over their paging
channels. Where necessary, the page message is inserted into the computed paging
channel slot.

21
22
23
24
25

Please refer to section 6.1.2.3, Paging Request, for the format and content of this
message.

26
27

29
30
31

Successful Operation
The MSC determines that an incoming call (either land or mobile originated) terminates
to a MS within its serving region and initiates the paging procedure. It starts timer
T3113, sends the Paging Request message to the BS, and waits for the Complete Layer 3
information containing Paging Response message.

17

28

Paging Request

2.2.3.1.2

Failure Operation
If a Complete Layer 3 Information message containing a Paging Response message has
not been received by the MSC before timer T3113 expires, the MSC may repeat the
Paging Request message and restart timer T3113.

48

TIA/EIA/IS--2001

2.2.3.2

This DTAP message is sent from the BS to the MSC, after receipt of a Page Response
Message from the MS, in response to a Paging Request message. The Paging Response
and the subsequent MSC response are used for connection establishment.

2
3
4

2.2.3.2.1

Successful Operation
When the MS recognizes a page message containing its identity, it will send a response
message to the BS. The BS will construct the Paging Response message using the
information received from the MS, append it to the Complete Layer 3 Information
message (please refer to section 6.1.2.1, Complete Layer 3 Information), and send this
combined message to the MSC. The BS will start timer T303 and await reception of the
Assignment Request message. The MSC stops timer T3113 upon receiving the Paging
Response message.

6
7
8
9
10
11
12

In the Access Probe Handoff scenario, the source BS (the BS on which the first access
probe was sent), upon receiving a page response for the same mobile and the same call
forwarded via an A7 connection from another BS, may choose to send a second Paging
Response to the MSC. The MSC shall be able to handle a Paging Response for a mobile
that is already engaged in a termination attempt by sending a Clear Command message to
the BS containing a cause value of Do not notify MS.

13
14
15
16
17
18

The base station may select an available channel based on the mobile's capabilities, and
assign the MS to that channel at any time following the receipt of a Page Response
Message from the MS.

19
20
21

Please refer to section 6.1.2.4, Paging Response, for the format and content of this
message.

22
23

24

Paging Response

2.2.3.2.2

Failure Operation

25

No action is taken at the BS on failure to receive a Paging Response from the MS.

26

If the BS fails to receive an Assignment Request message or Clear Command message in

response to the Paging Response message prior to expiration of timer T303, then it may
send a Reorder or Release message to the MS, and clear all associated resources.

27
28

29

2.2.3.2.3

If a Paging Response is received by the MSC for a call that is no longer active, the MSC
may clear the call.

30
31

32

Abnormal Operation

2.2.3.3

UNUSED SECTION

2.2.3.4

UNUSED SECTION

2.2.3.5

UNUSED SECTION

33

34
35

36
37

49

TIA/EIA/IS-2001

2.2.3.6

See section 2.2.1.5.

Assignment Request

2.2.3.7

Assignment Complete

See section 2.2.1.6.

Note that for mobile terminated calls, the BS (MSC) considers the call stable and in the
conversation state after sending (receiving) the Connect message.

2.2.3.8

See section 2.2.1.7.

Assignment Failure

2.2.3.9

UNUSED SECTION h

2.2.3.10

Connect

10

11

This DTAP message informs the MSC that the called MS has answered (gone offhook).

12
13

14

2.2.3.10.1

Successful Operation
When the BS receives the indication that the called MS has answered, it sends the
Connect message to the MSC.

15
16

18

Upon receiving the Connect message, the MSC connects both parties, and stops timer
T301.

19

Please refer to section 6.1.2.10, Connect, for the format and content of this message.

17

20

2.2.3.10.2

If the MSC fails to receive the Connect message prior to expiration of timer T301 then it
performs exception handling (e.g., announcement, forwarding). The specific actions are
the MSC manufacturers concern.

21
22
23

24

Failure Operation

2.2.3.11

UNUSED SECTION

25

50

TIA/EIA/IS--2001

2.2.3.12

This DTAP message is sent from the MSC to the BS. Upon receipt of this message, the
BS shall send an Alert With Information Message on the air interface.

2
3

2.2.3.12.1

6
7
8
9

Please refer to section 6.1.2.24, Alert With Information, for the format and content of
this message.

10
11

13

Successful Operation
The MSC sends this message to the BS to request that the BS send an Alert With
Information Message on the air interface. This message may be sent by the MSC for
other mobile control purposes. For example, this message may be used by the MSC to
cause the MS to do audible alerting when it had been previously doing silent alerting
during a mobile termination call setup.

12

Alert With Information

2.2.3.12.2

Failure Operation
None.

51

TIA/EIA/IS-2001

2.2.4

Mobile Termination Examples

2.2.4.1

Mobile Termination

This section describes the call flow associated with a mobile station call termination in
the system.

4
5

time
MS

BS

comment

MSC
Paging Request

Page Message
T3113

Page Response Message

b
c

Complete L3 Info: Paging Response

Base Station Ack Order

T303

d
e

Assignment Request
f
Channel Assignment Message
g
Tch Preamble

T10

BS Ack Order

h
i

MS Ack Order

j
Service Connect Message
k
Service Connect Completion
l
Assignment Complete
m
Alert with Info
n

MS Ack Order

Connect Order
T301

BS Ack Order

p
q

Connect

6
7
8
9

Figure 2-8 - Mobile Termination

a.

The MSC determines that an incoming call terminates to a mobile within its
serving region and sends the Paging Request message to the BS to initiate a
mobile terminated call setup scenario. The MSC then starts timer T3113.

b.

The BS issues a Page Message containing the MS address over the paging
channel.

c.

The MS acknowledges the page by transmitting a page response message

over the access channel

10
11
12
13
14
15

52

TIA/EIA/IS--2001

d.

2
3

The MSC stops timer T3113 upon receipt of the Paging Response message
from the BS.

4
5
6

e.

The BS acknowledges the receipt of the Page Response Message from the MS
with a Base Station Acknowledgment Order to the MS.

f.

The MSC sends an Assignment Request message to the BS to request

assignment of radio resources. This message will also include terrestrial circuit
if one is to be used between the MSC and the BS. The MSC then starts timer
T10.

7
8
9
10
11

If the BS requested a preferred terrestrial circuit in the Paging Response

message and the MSC can support that terrestrial circuit, the MSC shall use
the same terrestrial circuit in the Assignment Request message. Otherwise, the
MSC may assign a different terrestrial circuit.

12
13
14
15

Upon receipt of the Assignment Request message from the MSC, the BS stops
timer T303.

16
17
18

g.

The BS sends a Channel Assignment Message over the control channel of the
radio interface (with the MS address) to initiate the establishment of a radio
traffic channel, if the MS is not already on a traffic channel.

h.

The MS begins sending the traffic channel preamble (TCH Preamble) over the
designated reverse traffic channel.

i.

Once the BS acquires the reverse traffic channel, it sends the Base Station
Acknowledgment Order, with layer 2 acknowledgment required, to the MS over
the forward traffic channel.

j.

The MS acknowledges the reception of the BS order by transmitting the

Mobile Station Acknowledgment Order.

k.

The BS then sends the Service Connect Message / Service Option Response
Order to the MS specifying the service configuration for the call. The MS
begins processing traffic in accordance with the specified service
configuration.

l.

On receipt of the Service Connect Message, the MS responds with a Service

Connect Completion Message.

19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

m. After the radio traffic channel and circuit have both been established, the BS
sends the Assignment Complete message to the MSC.
The MSC stops timer T10 upon receipt of the Assignment Complete message
from the BS, and starts timer T301.

36
37
38

n.

The BS sends the Alert with Information Message to the MS to cause ringing
at the MS.

o.

The MS acknowledges the reception of the Alert with Information Message by

transmitting the Mobile Station Acknowledgment Order.

39
40
41

The BS constructs the Paging Response message, places it in the Complete

Layer 3 Information message, sends the message to the MSC, and starts timer
T303. The BS may request the MSC to allocate a preferred terrestrial circuit.

53

TIA/EIA/IS-2001

p.

When the call is answered at the MS, a Connect Order, with acknowledgment
required, is transmitted to the BS.

q.

The BS acknowledges the Connect Order with the Base Station

Acknowledgment Order over the forward traffic channel.

r.

The BS sends a Connect message to the MSC to indicate that the call has been
answered at the MS. At this point, the call is considered stable and in the
conversation state.

The MSC stops timer T301 upon receipt of the Connect message from the BS.

1
2
3
4
5
6

54

TIA/EIA/IS--2001

2.2.4.2

Mobile Termination, Assignment Retry

This section describes the call flow diagram when channel assignment is retried
between the BS and MSC interface for a mobile terminated call.

2
3

time
MS

comment

MSC

BS

Paging Request
Page Message
T3113

Page Response Message

a
b
c

Complete L3 Info: Paging Response

d
Base Station Ack Order

T303

Assignment Request
f
Assignment Failure

T20

T10
g

Assignment Request

Channel Assignment Message

i
T10

Tch Preamble

BS Ack Order

k
MS Ack Order
l
Service Connect Message

Service Connect Completion

n
Assignment Complete

Alert with Info

p

MS Ack Order

q
Connect Order
T301

BS Ack Order

r
s

Connect

4
5
6
7

Figure 2-9 - Mobile Termination: Assignment Retry

a

The MSC determines that an incoming call terminates to a mobile within its
serving region and sends the Paging Request message to the BS to initiate a
mobile terminated call setup scenario. The MSC starts timer T3113.

b.

The BS issues a Page Message containing the MS address over the paging
channel.

8
9
10
11

55

TIA/EIA/IS-2001

c.

The MS acknowledges the page by transmitting a Page Response Message

over the access channel.

d.

The BS constructs the Paging Response message, places it in the Complete

Layer 3 Information message, sends the message to the MSC, and starts timer
T303. The BS may request the MSC to allocate a preferred terrestrial circuit.

2
3
4
5

The MSC stops timer T3113 upon receipt of the Paging Response message
from the BS.

6
7
8

e.

The BS acknowledges the receipt of the Page Response Message from the MS
with a Base Station Acknowledgment Order over the air interface.

f.

The MSC sends an Assignment Request message to the BS to request

assignment of radio resources. This message will also include terrestrial circuit,
if one is to be used, between the MSC and the BS. The MSC then starts timer
T10.

9
10
11
12
13

17

If the BS requested a preferred terrestrial circuit in the Paging Response

message and the MSC can support that terrestrial circuit, the MSC shall use
the same terrestrial circuit in the Assignment Request message. Otherwise, the
MSC may assign a different terrestrial circuit.

18

The BS stops timer T303 upon receipt of the Assignment Request message.

14
15
16

19

g.

20
21

The MSC stops timer T10 upon receipt of the Assignment Failure message
from the BS.

22
23
24

h.

25
26
27

29
30
31

i.

The BS sends a Channel Assignment Message over the paging channel of the
radio interface (with the MS address) to initiate the establishment of a radio
traffic channel, if the MS is not already on a traffic channel.

j.

The MS begins sending the traffic channel preamble (TCH Preamble) over the
designated reverse traffic channel.

k.

Once the BS acquires the reverse traffic channel, it sends the Base Station
Acknowledgment Order, with layer 2 acknowledgment required, to the MS over
the forward traffic channel.

l.

The MS acknowledges the reception of the Base Station Acknowledgment

Order by transmitting the Mobile Station Acknowledgment Order.

33
34
35
36
37
38
39
40
41

The MSC retries by sending an Assignment Request message to the BS to

request assignment of radio resources. This message will also include a
different terrestrial circuit to be used between the MSC and the BS, if one is
needed for the call. The MSC restarts timer T10.
Upon receipt of the retry of the Assignment Request message, the BS stops
timer T20. In this example, it is assumed that this second Assignment Request
message is acceptable to the BS. The BS connects the traffic channel to the
designated terrestrial circuit.

28

32

In this example, the BS recognizes that the assignment cannot be completed,

(e.g., the requested terrestrial circuit is not available) and sends the
Assignment Failure message to the MSC. The BS then starts timer T20.

56

TIA/EIA/IS--2001

m. The BS then sends the Service Connect Message / Service Option Response
Order to the MS specifying the service configuration for the call. The MS
begins processing traffic in accordance with the specified service
configuration.

n.

On receipt of the Service Connect Message, the MS responds with a Service

Connect Completion Message.

o.

After the radio traffic channel and circuit have both been established, the BS
sends the Assignment Complete message to the MSC

1
2
3

6
7
8

Upon receipt of the Assignment Complete message, the MSC stops timer T10,
and starts timer T301.

9
10

p.

The BS sends the Alert with Information Message to the MS to cause ringing
at the MS.

q.

The MS acknowledges the reception of the Alert with Information Message by

transmitting the Mobile Station Acknowledgment Order.

r.

When the call is answered at the MS, a Connect Order, with acknowledgment
required, is transmitted to the BS.

s.

The BS acknowledges the Connect Order with the Base Station

Acknowledgment Order over the forward traffic channel.

t.

20

The BS sends a Connect message to the MSC to indicate that the call has been
answered at the MS.

21

Upon receipt of the Connect message from the BS, the MSC stops timer T301.

11
12
13
14
15
16
17
18
19

57

TIA/EIA/IS-2001

2.2.5

Mobile to mobile calls are handled as a combination of mobile originated and mobile
terminated calls. This version of the specification does not specify procedures (such as
Tandem Free Operation) for mobile to mobile calls.

2
3
4

Mobile to Mobile Calls

2.2.6

Emergency Calls

For E911 Phase 2, also see section 2.12.

Emergency calls are handled as regular calls by the BS. There is no impact to the A
interface. A specific digit string (e.g. 911) constitute the dialed digits.

2.2.7

Test Calls
The purpose of test calls is to generate test data (e.g., frame error rate (FER), forward
and reverse link capacity estimates, etc.) for performance analysis. These calls may not
require any trunks (DS0 circuits). A test call can be initiated by the mobile station or the
MSC. Test calls initiated by the mobile station use the procedures described in
sections 2.2.1 and 2.2.2. Test calls initiated by the MSC use the procedures described in
sections 2.2.3 and 2.2.4.

10
11
12
13
14
15

18

When the test call uses a Markov or loopback operation, reception of any
supplementary service messages or inter-BS hard handoff requests may be considered
unexpected and may be ignored.

19

Hard handoff is not supported for Markov and loopback test calls.

16
17

20

2.2.8

Upon request from the PDSN (through the PCF), the BS may initiate a Packet Data call
by sending the BS Service Request message to the MSC. The MSC acknowledges the
request by sending the BS Service Response message to the BS and initiates a normal
call termination procedure as shown in Figure 2-10. The following sections describe
this procedure.

21
22
23
24
25

26

2.2.8.1

2.2.8.1.1

30
31

Please refer to section 6.1.2.28, BS Service Request, for the format and content of this
message.

32
33

2.2.8.1.2

36

38
39

Failure Operation
If a BS Service Response message is not received at the BS before the expiration of
timer T311, then the BS may resend the BS Service Request message.

35

37

Successful Operation
In order to initiate a call setup, the BS sends a BS Service Request message to the MSC
containing the identity of the mobile station that needs to be paged. The BS starts timer
T311 and awaits the reception of the BS Service Response message.

29

34

BS Service Request
This BSMAP message is sent from the BS to the MSC to begin a BS initiated call setup.

27

28

BS Initiated Call Setup

2.2.8.2

BS Service Response
This BSMAP message is sent from the MSC to the BS in response to a BS Service
Request.
58

TIA/EIA/IS--2001

2.2.8.2.1

The MSC shall send a BS Service Response message to the BS originating the BS
Service Request message. That BS, on receiving a BS Service Response message stops
timer T311.

2
3
4

Please refer to section 6.1.2.29, BS Service Response, for the format and content of
this message.

5
6

2.2.8.2.2

2.2.8.3

BS Initiated Call Setup Example

The sections below provide success and failure cases for BS initiated call setup.

10

11

Failure Operation
None.

Successful Operation

2.2.8.3.1

Mobile Termination Initiated by the BS: Successful Case

This section describes the call flow associated with a BS initiated call setup in a
TIA/EIA/IS-2000 system.

12
13

time
BS

MS

comment

MSC

BS Service Request
a
T311

BS Service Response
b

Mobile Terminated Call Setup

See section 2.2.4.1

14
15

Figure 2-10 - Mobile Termination Initiated by the BS

16

a.

The BS, in order to put a specific mobile on a traffic channel, sends a BS Service
Request to the MSC.

b.

The MSC acknowledges the call setup request by sending a BS Service Response
message to the BS that sent the BS Service Request message.

c.

The MSC sends a Paging Request message to establish a mobile terminated call as
illustrated in section 2.2.4.1, Mobile Termination.

17
18
19
20
21

22
23
24
25

2.2.8.3.2

Mobile Termination Initiated by the BS: Failure Case

When the MSC cannot accept the request from the BS, the call flow in Figure 2-10 will
be terminated in step (b). The MSC shall include a cause value in the BS Service
Response message indicating the reason for refusing the call setup request from the BS.

26

59

TIA/EIA/IS-2001

2.3

Call clearing may be initiated by either the Base Station, the Mobile Station, the
PDSN/PCF, or the MSC.

2
3

2.3.1

2.3.1.1

8
9
10
11
12

The MSC is responsible for clearing any A1, A2, and/or A5 connections associated
with the call. To release all allocated resources, the MSC shall send a Clear Command
message to the BS. The BS will respond with a Clear Complete message and stop timer
T300. The call flow scenarios are illustrated in section 2.3.5.

13
14
15
16

If the MS is not active (powered off) or if for any reason the radio channel failed
between the MS and the BS or if some internal BS failure occurs, then the BS will initiate
call clearing. The BS sends a Clear Request message to the MSC. The MSC responds
with a Clear Command message to the BS and waits for a Clear Complete message from
the BS. The scenario is illustrated in section 2.3.5.2.

17
18
19
20
21

2.3.1.2

Unsuccessful Call Clearing Procedures

See sections 2.3.1.5.2 and 2.3.1.6.2 for unsuccessful call clearing procedures related to
the Clear Request and Clear Command messages.

23
24

25

Successful Clear Scenarios

For a normal clearing that is initiated by the MS, the MS will send a Release Order to the
BS. The BS shall send a Clear Request message to the MSC and start timer T300 to wait
for the Clear Command message from the MSC. For packet data calls, call clearing does
not normally clear the service session. The service session will be cleared using
procedures in this section for conditions such as MS power down, termination of the
PPP session by the mobile or the network, etc.

22

Call Clearing Initiated by the MS or BS

Call clearing may be initiated by packet data procedures; see sections 2.14 and 2.15.

A1 Interface Call Clearing Procedures

2.3.1.3

UNUSED SECTION

2.3.1.4

UNUSED SECTION

2.3.1.5

Clear Request

26

27
28

29

Upon failure of a radio channel, or when the MS sends a Release Order to clear the call,
the BS shall send a Clear Request message to the MSC.

30
31

32
33
34
35
36
37
38

2.3.1.5.1

Successful Operation
The BS, after sending the Clear Request message, sets timer T300 and waits for a Clear
Command message from the MSC. Upon receiving the Clear Request message from the
BS, the MSC sends a Clear Command message to the BS and waits for a Clear Complete
message.
Please refer to section 6.1.2.20, Clear Request, for the format and content of this
message.

60

TIA/EIA/IS--2001

2.3.1.5.2

If a Clear Command message is not received from the MSC while timer T300 is active,
the BS may resend a Clear Request message to the MSC and restart timer T300. If the
Clear Command message is not received from the MSC before timer T300 expires a
second time or if the BS chooses to not resend the Clear Request message, the BS shall
cease further supervision of this call connection, release all dedicated resources, and
shall release the connection.

2
3
4
5
6
7

2.3.1.6

2.3.1.6.1

13

When the BS receives a Clear Command message, it stops timer T300 if it is active,
performs the appropriate procedure to release the MS and clears associated dedicated
resources.

14
15
16

If the Clear Command message contains a cause value of Do not notify MS, the BS
shall release terrestrial and radio resources and send no further messages to the MS.

17
18

Please refer to section 6.1.2.21, Clear Command, for the format and content of this
message.

19
20

2.3.1.6.2

23
24
25

2.3.1.7

28

2.3.1.7.1

31

Please refer to section 6.1.2.22, Clear Complete, for the format and content of this
message.

32
33

35

Successful Operation
Upon receipt of the Clear Complete message from BS, the MSC stops timer T315 and
releases the transport connection being used for the call.

30

34

Clear Complete
Upon receipt of the Clear Command the BS sends a Clear Complete message to the
MSC.

27

29

Failure Operation
If the MSC fails to receive the Clear Complete message before the expiration of timer
T315, the MSC may resend the Clear Command message and restart timer T315. If the
MSC does not receive the Clear Complete message the second time, the MSC shall
release the underlying transport connection to clear the MSC-BS signaling connection.

22

26

Successful Operation
After sending the Clear Command to the BS, the MSC starts timer T315 and waits for the
Clear Complete message from the BS.

12

21

Clear Command
Upon receipt of the Clear Request message, the MSC sends a Clear Command message
to the BS to instruct the BS to release the associated dedicated resources.

9
10

11

Failure Operation

2.3.1.7.2

Failure Operation
None.

61

TIA/EIA/IS-2001

2.3.2

When the MSC chooses to deny call set up initiated by the reception of a CM Service
Request or Paging Response message contained in a SCCP Connection Request, the
MSC may send a SCCP Connection Refused containing no user data.

2
3
4

2.3.2.1

Scenario 1 - Clear from the Network

Upon receiving a clear indication from the network the MSC shall send a Clear
Command message to the BS and wait for a Clear Complete message from the BS. This
normal call clearing scenario is illustrated in section 2.3.5.3.2.

6
7
8

Call Clearing Initiated by the MSC

2.3.2.1.1

UNUSED SECTION

2.3.2.1.2

UNUSED SECTION

2.3.2.1.3

Clear Command

10

11
12

13

Please refer to section 2.3.1.6.

14

15

2.3.2.1.4

The function and purpose of this message is exactly the same as described in section
2.3.1.7.

16
17

18

Clear Complete

2.3.2.2

UNUSED SECTION

2.3.2.3

Call clearing via Clear Command

19

20

If call clearing is initiated by the MSC, the MSC shall send a Clear Command message to
the BS, start timer T315, and wait for a Clear Complete message from the BS. Timer T315
will be stopped when the Clear Complete message is received. This normal call clearing
scenario is illustrated in section 2.3.5.3.2.

21
22
23
24

25

2.3.2.3.1

Upon receiving a clear indication from the network, the MSC shall send the Clear
Command message to the BS to clear the call.

26
27

28

2.3.2.3.1.1

30
31
32

Please refer to section 6.1.2.21, Clear Command, for the format and content of this
message.

33
34

36

Successful Operation
After sending the Clear Command to the BS, the MSC starts timer T315 and waits for the
Clear Complete message from the BS. This operation is considered to be successful if
the Clear Complete message is received by MSC. The MSC will stop timer T315 upon
receipt of the Clear Complete message.

29

35

Clear Command

2.3.2.3.1.2

Failure Operation
Please refer to section 2.3.1.6.2.
62

TIA/EIA/IS--2001

2.3.2.3.2

The function and purpose of this message is exactly the same as described in section
2.3.1.7.

2
3

2.3.2.4

2.3.3

9
10
11

2.3.4

2.3.5

2.3.5.1

Call Clear Initiated by MS

This section provides the call flow diagrams for a call clearing operation initiated by the
mobile station.

17
18

19

Call Flow Diagrams for Call Clear Operation

The following subsections provide the call flow diagrams for call clearing operations.

15

16

Call Clearing for Handoff

Please refer to section 3.3.2.6.

13

14

Call Clearing Collision

Call clearing collision occurs when the BS sends a Clear Request message and the MSC
simultaneously sends a Clear Command message. When the MSC receives the Clear
Request message, it shall note it and continue to wait for the Clear Complete message.
When the BS receives the Clear Command message, it shall complete the call clearing.

12

Call Clearing when Tones/Announcements are Provided

Call clearing messages are not affected if the network provides either tones or
announcements immediately before clearing a call.

Clear Complete

2.3.5.1.1

UNUSED SECTION

20

63

TIA/EIA/IS-2001

2.3.5.1.2

Call Clear via Clear Request

In this example, when the MS initiates call clearing by sending a Release Order to the
BS, the BS sends a Clear Request message to the MSC and waits to receive a Clear
Command message.

2
3
4

time
BS

MS

comment

MSC

Release Order

a
Clear Request
b
T300

Clear Command

Release Order
T315

Clear Complete
e
5
6
7
8

Figure 2-11 - Call Clear Initiated by MS

a.

The mobile station initiates call clearing by transmitting a Release Order over
the reverse traffic channel.

b.

The BS then sends the Clear Request message to the MSC to initiate the call
clear transaction. Timer T300 is started by the BS.

c.

The MSC starts timer T315 and sends a Clear Command message to the BS to
instruct the BS to release the associated dedicated resource (such as terrestrial
circuit). The BS stops timer T300.

d.

In response to the Clear Command message, the BS releases the terrestrial

circuit, if allocated. The BS then acknowledges the MS by sending it a Release
Order over the forward traffic channel and releases the radio resource.

e.

The BS then returns a Clear Complete message to the MSC. The MSC stops
timer T315 upon receipt of the Clear Complete message. The MSC releases the
underlying transport connection.

9
10
11
12
13
14
15
16
17
18
19
20

64

TIA/EIA/IS--2001

2.3.5.2

This section provides the call flow diagram for a call clearing operation initiated by the
base station.

2
3

Call Clear Initiated by BS

2.3.5.2.1

UNUSED SECTION

2.3.5.2.2

Call Clear via Clear Request

In this example, when there is a radio channel failure or the MS is not active, the BS
initiates call clearing by sending a Clear Request message to the MSC.

7
8

time
MS

BS

comment

MSC

Clear Request
T300

a
Clear Command
T315

Clear Complete

b
c

9
10
11
12

Figure 2-12 - Call Clear Initiated by BS (via Clear Request)

a.

In this case of a radio channel failure between the MS and the BS, or if the MS
is not active, the BS sends a Clear Request message to the MSC. The BS starts
timer T300 and waits for the Clear Command from the MSC (step b).

b.

The MSC starts timer T315 and sends a Clear Command message to instruct
the BS to release the associated dedicated resource (such as terrestrial circuit).
The BS stops timer T300.

c.

The BS then returns a Clear Complete message.

13
14
15
16
17
18
19
20

The MSC stops timer T315 upon receipt of the Clear Complete message and
releases the underlying transport connection.

65

TIA/EIA/IS-2001

2.3.5.3

This section provides the call flow diagram for a call clearing operation initiated by the
MSC when an underlying transport connection exists.

2
3

Call Clear Initiated by MSC

2.3.5.3.1

UNUSED SECTION

2.3.5.3.2

Call Clear via Clear Command

6
7
8

In this example, the MSC initiates call clearing by using the Clear procedure (Clear
Command and Clear Complete messages).
time
MS

BS

comment

MSC
Clear Command

Release Order
b
Release Order

T315
Clear Complete

c
d

9
10
11
12

Figure 2-13 - Call Clear Initiated by MSC (via Clear Command)

a.

The MSC starts timer T315 and sends a Clear Command message to the BS to
instruct the BS to release the associated dedicated resource and initiate call
clearing over the air.

b.

The BS initiates call clearing over the air interface by transmitting a Release
Order over the forward traffic channel.

c.

The MS acknowledges the Release Order by returning a Release Order over

the reverse traffic channel.

d.

The BS then returns a Clear Complete message. The MSC stops timer T315
upon receipt of the Clear Complete message and releases the underlying
transport connection.

13
14
15
16
17
18
19
20
21

66

TIA/EIA/IS--2001

2.4

Radio link supervision of dedicated radio resources shall be the responsibility of the BS.
If communication with the mobile is lost then the BS can request that the call be cleared.

2
3

2.5

6
7
8
9
10
11
12
13
14
15
16

18
19
20

Support of Supplementary Services

The receipt at the network of a hook flash or Origination message from the MS during a
particular call state is interpreted by the network as the invocation of a supplementary
service. The activation, deactivation, registration, and erasure of a supplementary
service by a mobile subscriber is accomplished by the subscriber entering a digit string
at the MS. The MS will send the digit string to the network in an Origination message.
The MSC will perform digit analysis on the dialed digits to determine that the subscriber
wishes to perform a supplementary service operation, will process the request, and will
give the MS an indication of the acceptance or rejection of the request using normal call
setup and call clearing procedures. No special action is required at the BS to process
supplementary service requests using this method. Please refer to the message flow
diagrams for the mobile originated call setup procedures (section 2.2.1 and 2.2.2) for an
illustration of this message handling.

17

Traffic Channel Radio Link Supervision

2.5.1

Support of TIA/EIA 664 Wireless Features

The features defined in TIA/EIA 664 generally involve transactions between the MSC
and the MS. The required information is passed through the BS using the following
messages:

21

Flash with Information

22

Flash with Information Ack

23

Feature Notification

24

Feature Notification Ack

25

This section contains the above messages to support supplementary services.

67

TIA/EIA/IS-2001

2.5.1.1

The Flash with Information message may be sent from the MSC to the BS to convey
supplementary services information which is to be sent to the MS. This message may
also be sent by the BS to convey supplementary service information.

2
3
4

2.5.1.1.1

To send supplementary service information to the MS on a traffic channel, the MSC

shall include the information in a Flash with Information message. For example, to
perform the Message Waiting Indication feature, the MSC shall send a Flash with
Information message including a Message Waiting Indication element. If a Tag element
is included in the Flash with Information message, the BS will request the MS to
acknowledge the corresponding air interface message.
Upon receipt of this
acknowledgment, the BS shall send a Flash with Information Ack message to the MSC.

8
9
10
11
12
13
14

If a Flash with Information Ack message is expected by the MSC, then it shall start timer
T62.

15
16

During call setup, the MSC shall queue any Flash with Information message until the
Assignment Complete message is received for mobile originations or until a Connect
Message is received for mobile terminations (i.e., conversation sub-state). In the event
that the call is cleared prior to reaching the conversation sub-state, a Feature
Notification message may be sent by the MSC.

17
18
19
20
21

Please refer to section 6.1.3.7, Flash with Information, for the format and content of
this message.

22
23

2.5.1.1.2

26

2.5.1.2

29

2.5.1.2.1

32
33
34

Please refer to section 6.1.3.8, Flash with Information Ack, for the format and content
of this message.

35
36

38

Successful Operation
This DTAP message is sent from the BS to the MSC. If the MSC had included a Tag
element in the Flash with Information message, then upon receiving a Layer 2 Ack for
the Flash with Information message from the MS, the BS sends this message to the
MSC. The MSC stops timer T62.

31

37

Flash with Information Ack

The BS uses this message to send the acknowledgment of the Flash with Information
message to the MSC.

28

30

Failure Operation
In the MSC to BS direction, if timer T62 expires before the receipt of Flash with
Information Ack, the MSC may resend the Flash with Information message.

25

27

Successful Operation
This message is sent by the BS to the MSC when the BS receives a Flash with
Information Message sent by the MS.

24

Flash with Information

2.5.1.2.2

Failure Operation
None.

68

TIA/EIA/IS--2001

2.5.1.3

This message is sent by the MSC to initiate sending of the feature indication
information to the MS.

2
3

2.5.1.3.1

6
7
8
9
10
11
12
13

Please refer to section 6.1.3.9, Feature Notification, for the format and content of this
message.

14
15

2.5.1.3.2

2.5.1.4

20

2.5.1.4.1

23
24

Please refer to section 6.1.3.10, Feature Notification Ack, for the format and content of
this message.

25
26

28

Successful Operation
This BSMAP message is sent from the BS to the MSC. Upon receiving a Layer 2 Ack
from the MS for the Feature Notification message, the BS sends this message to the
MSC.

22

27

Feature Notification Ack

The BS uses this message to send the acknowledgment of the Feature Notification to
the MSC.

19

21

Failure Operation
The MSC may send the Feature Notification message again after timer T63 expires.

17

18

Successful Operation
If the MSC determines that it needs to deliver some feature indication information to the
MS, it sends this BSMAP message to the BS and starts timer T63. Then the MSC waits
for the BS to send the Feature Notification Ack message back. When the BS receives
the Feature Notification message, it will send an Order or Feature Notification message
(depending upon the applicable air interface protocol) to the MS on a Paging channel. If
the MSC needs an acknowledgment to the Feature Notification message, it indicates
that by including a Tag element in the Feature Notification message. The MSC then
expects that a Feature Notification Ack message, including this Tag element, will be
sent back when the BS receives a layer 2 acknowledgment from the MS.

16

Feature Notification

2.5.1.4.2

Failure Operation
None.

69

TIA/EIA/IS-2001

2.5.2

DTMF digit transmission can be sent using in-band tones between the MS and MSC
once a call is in conversation state. No action is required by the BS for transmission of
in-band DTMF signals.

2
3
4

DTMF Transmission Using In-band Tones

2.5.3

Burst DTMF Transmission

10

The TIA/EIA/IS-2000 specification does not detail the functional split (i.e., which entity
generates the tones) but this standard assumes that the MSC will generate the tones for
DTMF signals sent in the network to MS direction. This standard further assumes for
the DTMF signals in the MS to network direction that the MSC will inject DTMF tones
into the 64 kbps/sec PCM stream or the BS will cause the SDU to generate tones.

11

DTMF tone generation at the BS is required in the MS to network direction.

6
7
8
9

12

13

2.5.4

UNUSED SECTION

14

70

TIA/EIA/IS--2001

2.5.5

Supplementary Services Flow Charts

2.5.5.1

UNUSED SECTION

2.5.5.2

Call Waiting

3
4

5
6

This section provides the call flow description for the call waiting feature.
time
MS

BS

comment

MSC
Flash with Information

Flash with Information

a
b

Flash with Information

c
Flash with Information
d
Flash with Information
e
Flash with Information

7
8
9

Figure 2-14 - Call Waiting

a.

The MSC sends a Flash with Information message to the BS to alert the MS
that there is a call waiting.

b.

The BS takes the information from the MSC and sends a Flash with
Information message to the MS.

c.

The MS sends the Flash with Information message to the BS to indicate the
acceptance of the second call.

d.

The BS sends a Flash with Information message to the MSC. The MSC then
places the original call on hold and connects the second call to the MS.

e.

To toggle between the two callers, the MS sends the Flash with Information
message to the BS.

f.

The BS sends a Flash with Information message to the MSC. The MSC then
places the second call on hold and reconnects the original call to the MS.

10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

The MSC may optionally apply an inband tone to alert the user of a waiting call. Such
an action would take the place of or supplement steps (a) and (b) above.
If an MS releases an active call after receiving call waiting notification, and while a call
is waiting, the active call is cleared using normal call release procedures as described in
Section 2.3.1.1, and the waiting call is offered using normal mobile termination
procedures, as described in Section 2.2.4.1.
If an MS releases the active call while another call is held (by the Call Waiting feature),
the active call is cleared using normal call release procedures as described in Section
2.3.1.1, and the held call is offered using normal mobile termination procedures, as
described in Section 2.2.4.1.

71

TIA/EIA/IS-2001

2.5.5.3

UNUSED SECTION

2.5.5.4

UNUSED SECTION

2.5.5.5

Three-Way Calling (Method 1)

3
4

5
6
7

This section provides the call flow description for the Three-Way Calling feature
(Method 1).
time
MS

BS

comment

MSC

Flash with Information

a
Flash with Information
b
Flash with Information (2nd party called address)
c
Flash with Information
d
Flash with Information
e
Flash with Information
f
Flash with Information
g
Flash with Information
h
8
9
10

Figure 2-15 - Three-Way Calling - (Method 1)

a.

To initiate Three-Way Calling while a call is in progress, the MS sends a Flash

with Information to the BS to request the original call to be placed on hold.

b.

The BS sends the Flash with Information message from the MS to the MSC.
The MSC places the original call on hold.

c.

The MS sends a Flash with Information message to the BS containing the

dialed digits of the second party.

d.

The BS sends the Flash with Information message to the MSC with the dialed
digits of the second party. Once the second party answers, it is connected to
the MS.

e.

The MS sends a Flash with Information Message to the BS to request

connection of all three parties.

f.

The BS sends the Flash with Information to the MSC. The MSC places all three
parties in a conference call.

g.

To disconnect the second party, the MS sends a Flash with Information to the
BS.

h.

The BS sends a Flash with Information message to the MSC, which

disconnects the second call.

11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

72

TIA/EIA/IS--2001

2.5.5.6

Three-Way Calling - (Method 2)

This section provides the call flow description for the Three-Way Calling feature
(Method 2). In Method 2, the called address information of the second call is sent
during the first hook flash indication from the MS.

2
3
4

time
MS

BS

comment

MSC

Flash with Information (2nd party called address)

a
Flash with Information
b
Flash with Information
c
Flash with Information
d
Flash with Information
e
Flash with Information
f
5

Figure 2-16 - Three-Way Calling - (Method 2)

6
7

a.

To initiate Three-Way Calling while a call is in progress, the MS sends a Flash

with Information containing the dialed digits of the second call to the BS.

b.

The BS sends a Flash with Information message to the MSC along with the
dialed digits of the second party. The MSC places the original call on hold and
starts call setup procedures for the second party. Once the second party
answers, it is connected to the MS.

c.

The MS sends a Flash with Information message to the BS to request

connection of all three parties.

d.

The BS sends the Flash with Information message to the MSC. The MSC
places all three parties in a conference call.

e.

To disconnect the second party, the MS sends a Flash with Information

message to the BS.

f.

The BS sends a Flash with Information message to the MSC, which

disconnects the second call.

8
9
10
11
12
13
14
15
16
17
18
19
20

21

2.5.5.7

UNUSED SECTION

2.5.5.8

UNUSED SECTION

22

23
24

73

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9

2.5.5.9

Message Waiting Notification on the Paging Channel

The Feature Notification message is used to deliver a Message Waiting Indication
(MWI) to the MS while it is idle. There is a possible race condition when the Feature
Notification message is sent while a MS is originating a call on a BS. If this occurs, the
message waiting indication may not be successfully delivered. It is recommended that
the MSC request an acknowledgment with the Feature Notification, and resend the
MWI information on the traffic channel, if necessary.
The following example demonstrates the delivery of a Message Waiting Indication via
the Feature Notification message over the control channel.
time
MS

BS

comment

MSC
Feature Notification

MWI Order / Feature

Notification
T63

Layer 2 Ack

a
b
c

Feature Notification Ack

d
10
11
12
13

Figure 2-17 - Message Waiting Notification on the Paging Channel

a.

MSC sends a Feature Notification message containing message waiting

information and starts timer T63.

b.

The BS sends an appropriate message to the mobile depending upon the air
interface protocol.

c.

The MS acknowledges the receipt of the message by a Layer 2

acknowledgment.

d.

BS sends the Feature Notification Ack message to the MSC. The MSC stops
timer T63.

14
15
16
17
18
19
20

74

TIA/EIA/IS--2001

1
2
3
4
5
6

2.5.5.10

Message Waiting Notification on the Traffic Channel

The Flash with Information message is used to deliver a Message Waiting Indication
while the MS is on a traffic channel, i.e., after an Assignment Complete message has
been received at the MSC. The following example shows the delivery of a Message
Waiting Indication to the MS while on a traffic channel via the Flash with Information
message.
time
MS

BS

comment

MSC
Flash with Information

Flash with Information

T62

Layer 2 Ack

b
c

Flash with Information Ack

7
8
9
10

Figure 2-18 - Message Waiting Notification on the Traffic Channel

a.

When the MS is on traffic channel, the MSC may include message waiting
information in the Flash with Information message to inform the MS that there
are zero or more messages waiting. In this scenario, it is assumed that the MSC
also includes the Tag element in the Flash with Information message to request
that the BS notify the MSC when a Layer 2 acknowledgment is received from
the MS. The MSC starts timer T62.

b.

The BS will send the information in the Flash with Information air interface
message.

c.

Once the MS has received the Flash with Information message, it will respond
with a Layer 2 Ack message.

d.

The BS will send the Flash with Information Ack message to the MSC
including the Tag element included by the MSC in the Flash with Information
message. The MSC stops timer T62.

11
12
13
14
15
16
17
18
19
20
21
22

23

75

TIA/EIA/IS-2001

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

2.6

Support of Short Message Service

The Short Message Service (SMS) provides for the transfer of short messages between
an application residing on a mobile station and an application within the network, e.g.,
at a Message Center (MC). The MSC and BS provide a conduit for short messages
between the application in the network, e.g., at the MC, and the application in the MS.
Other network procedures carried out by entities providing a Short Message Service
(SMS), are beyond the scope of this standard (see TIA/EIA-41).
Three types of basic short messaging are supported: mobile originated point-to-point,
mobile terminated point-to-point, and broadcast. Both mobile originated and mobile
terminated point-to-point short messaging may require that messages be exchanged in
both directions on the air interface.
Short messages can be exchanged between the MS and BS on both the control and
traffic channels. Thus, an active mobile station is able to send and receive short
messages at any time. The maximum number of short message characters that can be
handled varies with the air interface and teleservice type employed. Each short message
shall be carried within a single message on the MSC-BS Interface: no provision is made
for segmentation and reassembly of short messages.
The short message service is divided into a number of protocol layers: the SMS
teleservice layer, the SMS transport layer, and the SMS relay layer (see IS-637). The
relay layer may sit on top of other air interface layers. Not all air interfaces may support
the full range of SMS capabilities and layers. All of these layers are transparent to the
MSC-BS Interface, and are carried as part of the SMS user part element in the MSC-BS
Interface messages.
For point to point delivery the MSC can request that the BS report that a Layer 2
acknowledgment was received from the MS. This indicates that the MS received the
short message. In addition, both the transport and teleservice layers may generate
acknowledgments (see IS-637) but these acknowledgments are transparent to the MSCBS Interface.
The scope of the requirements and specifications outlined in this document are limited
to the MSC-BS Interface, as defined in the Network Reference Model. Descriptions of
operations at other interfaces are included for information only.

76

TIA/EIA-2001

2.6.1

SMS Procedures

The subsections below contain descriptions of the following procedures:

SMS Mobile Originated Point-to-Point

SMS Mobile Terminated Point-to-Point

SMS Broadcast

2.6.1.1

This section describes the procedure for sending an SMS message which is mobile
originated.

7
8

A mobile originated SMS (SMS-MO) message may be sent from the MS to the BS on
either a control (access) or traffic channel.

9
10

An MS already on a traffic channel will use that traffic channel to send an SMS-MO
message. An idle MS may use either an access channel, or in some air interfaces, may
request a traffic channel for delivery of an SMS-MO message. If an idle CDMA MS
wants to use a traffic channel to send an SMS-MO message, it will send an Origination
Message with the short message service option number in the service option field. The
call origination procedures described in section 2.2.1 will then be used. If the access
channel is used for SMS-MO message transmission from the MS to the BS, then no call
establishment is performed. The transport of the SMS-MO message on the MSC-BS
Interface is accomplished by sending an Application Data Delivery Service (ADDS)
Transfer message from the BS to the MSC.

11
12
13
14
15
16
17
18
19
20

When the SMS-MO message is transmitted from the MS to the BS on a traffic channel,
the transport of SMS-MO message on the MSC-BS Interface is accomplished by
sending the ADDS Deliver message from the BS to the MSC.

21
22
23

24

2.6.1.2

26

An SMS Mobile Terminated (SMS-MT) message can be transmitted from the BS to the
MS on either a control (paging) or traffic channel. An SMS-MT message to an MS
already on a traffic channel is sent on the traffic channel.

27
28
29

When the SMS-MT message is sent to the MS on a traffic channel, the transport of the
SMS-MT message on the MSC-BS Interface is accomplished by sending the ADDS
Deliver message from the MSC to the BS.

30
31
32

When the SMS-MT message is sent to the MS on a control channel, the transport of
the SMS-MT message on the MSC-BS Interface is accomplished by sending the ADDS
Page message from the MSC to the BS.

33
34
35

37
38
39
40

SMS - Mobile Terminated Point-to-Point

This section describes the procedure for sending an SMS message which is mobile
terminated.

25

36

SMS - Mobile Originated Point-to-Point

2.6.1.3

SMS - Broadcast
SMS Broadcast is a mobile terminated short message that is sent to all mobile stations
operating within the BS serving region.
When the MSC sends an SMS Broadcast message to idle mobile stations, the MSC
uses the ADDS Page message.

77

TIA/EIA/IS-2001

2.6.2

The delivery of SMS-MT, SMS-MO, and SMS-Broadcast messages on the control

channel is accomplished by the exchange of ADDS Page, ADDS Page Ack, and ADDS
Transfer messages.

2
3
4

The ADDS Page is sent from the MSC to the BS and is used for SMS-MT and SMSBroadcast messages. It is acknowledged with the ADDS Page Ack message.

5
6

The ADDS Transfer message is sent from the BS to the MSC when the BS receives a
Data Burst message on the access channel.

7
8

2.6.2.1

11
12
13

2.6.2.1.1

16
17
18

When the MSC determines that it needs to deliver an SMS message to a specific idle
mobile station, and the MSC does not require a Layer 2 acknowledgment notification,
the MSC sends the ADDS Page message, without a Tag information element, to the BS.

19
20
21

The Tag information element, when present, indicates to the BS that a Layer 2
acknowledgment is required from the MS. It can be used by the MSC to uniquely
identify the ADDS Page message. If the Tag information element is present in the
ADDS Page message, then the BS shall save it and return the same value in the Tag
information element of the ADDS Page Ack message.

22
23
24
25
26

When the MSC determines that it needs to deliver an SMS Broadcast message, and the
MSC desires a response from the BS, the MSC starts timer T3113, sends the ADDS
Page message containing a Tag element to the BS, and waits for the ADDS Page Ack
message. The Tag information element, when present indicates to the BS that an ADDS
Page Ack response message is requested. However, the BS is not required to solicit
Layer 2 Acknowledgements from the mobile stations. If the Tag element is present,
than the BS shall save it and return the saved value in the Tag information element of
the ADDS Page Ack message.

27
28
29
30
31
32
33
34

Please refer to section 6.1.7.1, ADDS Page, for the format and content of this
message.

35
36

38
39
40

Successful Operation
When the MSC determines that it needs to deliver an SMS message to a specific idle
mobile station, and a Layer 2 acknowledgment notification, is required from the MS the
MSC starts timer T3113, sends the ADDS Page message containing a Tag information
element to the BS, and waits for the ADDS Page Ack message.

15

37

ADDS Page
This BSMAP message is sent from the MSC to the BS to transport an application data
message. For the purposes of the Short Message Service, the ADDS Page message is
used to transport the Short Message from the MSC to the BS to be delivered on the
paging channel(s).

10

14

SMS Delivery on the Control Channel

2.6.2.1.2

Failure Operation
If the Tag information element was included in the ADDS Page message, and the ADDS
Page Ack message has not been received at the MSC before timer T3113 expires, the
MSC may resend the ADDS Page message and restart timer T3113.

78

TIA/EIA-2001

2.6.2.2

This BSMAP message is sent from the MS to the MSC to deliver an application data
message. In the case of the Short Message Service, the ADDS Transfer message is
used to transfer Short Messages from the BS to the MSC.

2
3
4

2.6.2.2.1

Please refer to section 6.1.7.2, ADDS Transfer, for the format and content of this
message.

8
9

11

Successful Operation
When the BS receives an application data message from the MS on the access channel,
it sends it to the MSC in an ADDS Transfer message.

10

ADDS Transfer

2.6.2.2.2

Failure Operation
None.

79

TIA/EIA/IS-2001

2.6.2.3

This BSMAP message is sent from the BS to the MSC when the BS receives a Layer 2
acknowledgment from an MS for an ADDS Page message directed to a specific MS that
contains a Tag element, or when the BS successfully processes an ADDS Page
message containing both Mobile Identity set to "Broadcast Address" and a Tag
element, or when theBS wishes to indicate an error situation resulting from an ADDS
Page message that contains a Tag element.

2
3
4
5
6
7

ADDS Page Ack

2.6.2.3.1

Successful Operation
For messages to a specific MS, if the MSC included the Tag element in the ADDS Page
message, the BS sends this message when it receives a Layer 2 acknowledgment from
the MS.

9
10
11

For SMS Broadcast messages, if the MSC included the Tag element in the ADDS Page
message, the BS sends this message to indicate that it has processed the ADDS Page
message. The BS is not required to solicit Layer 2 Acknowledgements from the mobile
stations.

12
13
14
15
16

Please refer to section 6.1.7.4, ADDS Page Ack, for the format and content of this
message.

17
18

19

2.6.2.3.2.

None.

20

21

2.6.2.4

SMS Message Flow Using ADDS, Control Channel

This section contains examples of SMS delivery on the control channel.

22

23

Failure Operation

2.6.2.4.1

SMS Broadcast Delivery over the Paging Channel

24
25
26

This section provides the call flow description for SMS Broadcast delivery over the
Paging channel.

27

time
MS

BS

comment

MSC
ADDS Page

a
T3113
ADDS Page Ack
Paging Channel SMS Broadcast
Delivery

b
c

28
29
30
31

Figure 2-19 SMS-Broadcast Delivery to Mobile Stations over the Paging Channel.
a.

The MSC receives SMS Broadcast information for delivery to idle mobile
stations.

80

TIA/EIA-2001

The MSC sends an ADDS Page message to the BS. The ADDS Page contains
the SMS Broadcast message in its ADDS User Part information element.

1
2

If the MSC requires an acknowledgment to the ADDS Page message, the Tag
element shall be included in the ADDS Page message. The MSC shall then also
set timer T3113.

3
4
5
6

b.

If the MSC requested an acknowledgment from the BS by including the Tag

element in the ADDS Page message, the BS replies with an ADDS Page Ack
message including the Tag element set to the same value as received from the
MSC. The MSC cancels timer T3113.

c.

The BS sends the SMS Broadcast information to the appropriate mobile stations
over the Paging channel. Layer2 acks are not requested by the BS from the mobile
stations receiving the SMS broadcast message.

7
8
9
10
11
12

13

81

TIA/EIA/IS-2001

1
2
3
4

2.6.2.4.2
Example 1

SMS Delivery to a Mobile Station on the Paging Channel -

This section provides the call flow description for the delivery of an SMS-MT message
on the paging channel.
time
MS

BS

comment

MSC
ADDS Page
a

Paging Channel SMS Delivery

T3113

Layer 2 Ack
c
ADDS Page Ack
d
5
6
7
8

Figure 2-19 - SMS-MT Delivery to a Mobile Station on the Paging Channel - Example
1
a.

The MSC sends an ADDS Page message to the BS. The ADDS Page contains
the short message in its ADDS User Part information element.

10
11

If the MSC requires an acknowledgment, it will include the Tag information

element in the ADDS Page message. It will also start timer T3113.

12
13
14

b.

The BS sends the short message to the MS on the paging channel. Before
sending the short message, the BS may perform vendor specific procedures
such as paging the MS to determine the cell in which the MS is located.

c.

If a Layer 2 Ack was solicited, the MS acknowledges the receipt of the

message by a Layer 2 Ack.

d.

If the MSC requested an acknowledgment by including the Tag information

element in the ADDS Page message, the BS replies with an ADDS Page Ack
message including the Tag information element set identical to the value sent
by the MSC. If timer T3113 was previously started, it will now be stopped.

15
16
17
18
19
20
21
22

The MSC determines that a point-to-point short message is to be sent to an

idle mobile station.

82

TIA/EIA-2001

1
2
3

2.6.2.4.3

SMS Receipt from a Mobile Station on the Access Channel

This section provides the call flow description for the receipt of an SMS-MO message
on the access channel.

MS

BS

MSC

Time

Access Channel SMS Delivery

a

Layer 2 Ack
b

ADDS Transfer
c
4
5
6
7

Figure 2-20 - SMS-MO Delivery on the Access Channel

a.

The MS sends a point-to-point SMS message to the network on the access

channel.

b.

If the MS had requested a Layer 2 Ack, the BS acknowledges the short

message received on the access channel by sending a Layer 2 Ack on the
paging channel.

c.

The BS sends an ADDS Transfer message to the MSC containing the SMS
message received from the MS in the ADDS User Part element.

8
9
10
11
12
13

83

TIA/EIA/IS-2001

1
2
3
4
5
6

2.6.2.4.4

SMS Delivery to a Mobile Station on the Paging Channel - Example 2

without Early Traffic Channel Assignment
This section provides an example call flow description for the delivery of an SMS-MT
message on the Paging Channel without early traffic channel assignment by the BS. In
this example, the mobile station is held on the control channel until the SMS messages are
delivered. After delivery, the mobile station is released.
time
MS

BS

comment

MSC
Paging Request
a

Page Message

T3113

Page Response Message

c
Complete L3 Info: Paging Response
d
Base Station Ack Order

T303

ADDS Page
f
Paging Channel SMS Delivery

T3113

Layer 2 Ack
h

Optional

Optional

ADDS Page Ack

(MSC releases underlying transport connection)

Release Order
k
Release Order
l
7
8
9

Figure 2-21 - SMS-MT Delivery to a Mobile Station on the Paging Channel - Example
2

10

a.

The MSC sends a Paging Request message to the BS and starts timer T3113.

11

b.

The BS sends a Page Message on the paging channel.

12

c.

The MS responds with a Page Response Message.

13

d.

The BS sends a Complete Layer 3 Information message containing a Paging

Response message to the MSC. The MSC stops timer T3113.

e.

The BS sends a Base Station Ack Order to acknowledge the Page Response
Message from the MS.

f.

If the Radio Environment and Resources element in the Page Response

message indicates no early traffic channel assignment by the BS, the MSC
sends an ADDS Page message to the BS. The ADDS Page contains the short
message in its ADDS User Part information element.

14
15
16
17
18
19
20
21
22

If the MSC requires an acknowledgment, it will include the Tag information

element in the ADDS Page message. It will also start timer T3113.

84

TIA/EIA-2001

g.

The BS sends the short message to the MS. Before sending the short message,
the BS may perform vendor specific procedures such as paging the MS to
determine the cell in which the MS is located.

h.

The MS acknowledges the receipt of the message by a Layer 2 Ack.

i.

If the MSC requested an acknowledgment by including the Tag information

element in the ADDS Page message, the BS replies with an ADDS Page Ack
message including the Tag information element set identical to the value sent
by the MSC. If timer T3113 was previously started, it will now be stopped.

j.

The MSC releases the underlying transport connection to clear the pending
page response.

k.

The BS, upon the release of the underlying transport connection, sends a
Release Order to the MS.

l.

The MS sends a Release Order to the BS to acknowledge the release.

1
2
3

6
7
8
9
10
11
12
13

85

TIA/EIA/IS-2001

2
3
4
5

2.6.2.4.5

SMS Delivery to a Mobile Station on the Paging Channel - Example 3 with

Early Traffic Channel Assignment
This section provides an example call flow description for the delivery of an SMS-MT
message on the Paging Channel with early traffic channel assignment by the BS.
time
MS

BS

comment

MSC
Paging Request
a

Page Message

T3113

Page Response Message

c
Complete L3 Info: Paging Response
d
Base Station Ack Order

T303

(MSC releases underlying transport connection)

Release Order

f
g

Release Order
ADDS Page

h
i

Paging Channel SMS Delivery

T3113

Layer 2 Ack
ADDS Page Ack

Optional

Optional

6
7
8
9

Figure 2-22 - SMS-MT Delivery to a Mobile Station on the Paging Channel - Example
3

10

a.

The MSC sends a Paging Request message to the BS and starts timer T3113.

11

b.

The BS sends a Page Message on the paging channel.

12

c.

The MS responds with a Page Response Message.

13

d.

The BS sends a Complete Layer 3 Information message containing a Paging

Response message to the MSC. The MSC stops timer T3113.

e.

The BS sends a Base Station Ack Order to acknowledge the Page Response
Message from the MS.

f.

The Radio Environment and Resources element in the Page Response message
indicates early traffic channel assignment by the BS, the MSC shall release the
underlying transport connection to clear the pending page response

g.

The BS, upon the release of the underlying transport connection, sends a
Release Order to the MS.

22

h.

The MS sends a Release Order to the BS to acknowledge the release.

23

i.

The MSC sends an ADDS Page message to the BS. The ADDS Page contains
the short message in its ADDS User Part information element.

14
15
16
17
18
19
20
21

24

86

TIA/EIA-2001

If the MSC requires an acknowledgment, it will include the Tag information

element in the ADDS Page message. It will also start timer T3113.

1
2

j.

The BS sends the short message to the MS. Before sending the short message,
the BS may perform vendor specific procedures such as paging the MS to
determine the cell in which the MS is located.

k.

The MS acknowledges the receipt of the message by a Layer 2 Ack.

l.

If the MSC requested an acknowledgment by including the Tag information

element in the ADDS Page message, the BS replies with an ADDS Page Ack
message including the Tag information element set identical to the value sent
by the MSC. If timer T3113 was previously started, it will now be stopped.

3
4
5

8
9
10

87

TIA/EIA/IS-2001

2.6.3

SMS Delivery on the Traffic Channel

This section describes the delivery of SMS messages on the traffic channel.

The delivery of Short Messages on the traffic channel is accomplished with the ADDS
Deliver and ADDS Deliver Ack messages on the MSC-BS Interface.

2.6.3.1

This DTAP message is sent from the MSC to the BS or from the BS to the MSC for
transferring an application data message exchanged over the traffic channel.

6
7

2.6.3.1.1

11

In the MSC to BS direction, the Tag information element, when present, indicates to the
BS that a Layer 2 acknowledgment is required from the MS. It can be used by the MSC
to uniquely identify the ADDS Deliver message. If the Tag information element is
present in the ADDS Deliver message, then the BS shall save it and return the same
value in the Tag information element of the ADDS Deliver Ack message.

12
13
14
15
16

Please refer to section 6.1.7.3, ADDS Deliver, for the format and content of this
message.

17
18

2.6.3.1.2

2.6.3.2

23
24

2.6.3.2.1

27
28

Please refer to section 6.1.7.5, ADDS Deliver Ack, for the format and content of this
message.

29
30

32

Successful Operation
The BS sends this message when it receives a Layer 2 acknowledgment from the MS
and the corresponding ADDS Deliver message received from the MSC contained a Tag
information element.

26

31

ADDS Deliver Ack

This DTAP message is sent from the BS to the MSC when the BS receives a Layer 2
acknowledgment from the MS for an ADDS Deliver message that contains a Tag
information element.

22

25

Failure Operation
If a Layer 2 Ack is not received from the mobile station, the BS shall initiate call clearing.

20

21

Successful Operation
When the MSC or BS needs to deliver an application data message while a traffic
channel exists, the sender will include that application data message in an ADDS
Deliver message and send it across the A1 interface.

9
10

19

ADDS Deliver

2.6.3.2.2

Failure Operation
None.

88

TIA/EIA-2001

2.6.3.3

This section contains examples of SMS Delivery Services on the traffic channel.

3
4
5

SMS Message Flow Using ADDS, Traffic Channel

2.6.3.3.1

SMS Delivery to a Mobile Station on a Traffic Channel

This section provides the call flow description for delivery of an SMS-MT short
message on a traffic channel.
MS

BS

MSC

Time

Comment

ADDS Deliver
a

Traffic Channel SMS Delivery

b

Layer 2 Ack
c

ADDS Deliver Ack

d
6
7
8
9

Figure 2-23 - SMS message delivery to a Mobile Station on a Traffic Channel

a.

The MSC determines that a short message is to be sent to the MS while it is on

the traffic channel.

b.

The MSC sends an ADDS Deliver message to the BS. The ADDS Deliver
message contains the short message in the ADDS User Part element.The BS
transmits the Short Message over the forward traffic channel. If the BS does
not receive an acknowledgment after transmitting the CDMA Data Burst
message, it shall retransmit the message. The BS shall not exceed a maximum
number of retransmissions, to be selected by the BS manufacturer. When the
BS reaches the maximumnumber of retransmissions, it shall declare a Layer 2
Ack failure. If the BS declares a Layer 2 Ack failure as a result of a ADDS
deliver message that contained a Tag element, then the BS may send an ADDS
Deliver Ack message back to the MSC with the appropriate cause value.

c.

The MS acknowledges delivery of the short message on the traffic channel

with a Layer 2 Ack.

d.

If the MSC has requested a response by including the tag element in the
ADDS Deliver message, the BS replies with an ADDS Deliver Ack message
when it has received acknowledgment from the MS that the message was
delivered. If a Tag element was included in the ADDS Deliver message, the BS
shall include the Tag element in the ADDS Deliver Ack message, and set it to
the same value as that received inthe ADDS Deliver message.

10
11
12
13
14
15
16
17
18
19
20
21
22

23
24
25
26
27
28

89

TIA/EIA/IS-2001

1
2
3

2.6.3.3.2

SMS Receipt from a Mobile Station on a Traffic Channel

This section provides the call flow description for the receipt of an SMS-MO message
on a traffic channel.

MS

BS

MSC

Time

Traffic Channel SMS Delivery

a

Layer 2 Ack
b

ADDS Deliver
c
4
5
6
7

Figure 2-24 - SMS Receipt from a Mobile Station on a Traffic Channel

a.

The BS receives a Traffic Channel SMS Delivery message from an MS on the

traffic channel with a burst type indicating SMS.

b.

If a Layer 2 Ack was requested by the MS, the BS sends a Layer 2 Ack to the
MS on the traffic channel.

c.

The BS sends an ADDS Deliver message to the MSC. The ADDS User Part
element contains the Short Message which was received from the MS.

8
9
10
11
12

90

TIA/EIA-2001

2.7

2
3

This section describes the messages and procedures to support the OTASP and
OTAPA features over the open A-Interface. These features are fully specified in IS-683.

4
5

7
8
9
10
11
12
13

Support of Over-The-Air Service Provisioning

(OTASP) and Over The Air Parameter
Administration (OTAPA)

2.7.1

OTASP Support
This section describes the messages and procedures to support OTASP calls. This
includes a mechanism for transporting OTASP data messages, as defined in IS-683
section 3.5 Reverse Link Message Formats and section 4.5 Forward Link Message
Formats over the MSC-BS interface. The processing of OTASP forward and reverse
data messages at the MSC or BS is the responsibility of the vendors. The air interface
between the BS and MS is described in IS-683 and the MSC interface to the network is
addressed inEIA/TIA/IS-725.

15

Successful OTASP processing involves hfollowing procedures and exchange of some

MSC-BS interface messages:

16

1)

OTASP Call Setup procedure

17

2)

OTASP Data Exchange procedure which includes exchange of following

messages:

14

18
19

- ADDS Deliver

20

- ADDS Deliver Ack

Some existing procedures may also be applied as sub-procedures:

21
22

- SSD update procedure

23

- Privacy Mode request procedure

24

3)

OTASP Call Clearing procedure

91

TIA/EIA/IS-2001

2.7.1.1

Normal call setup procedures are used to establish the OTASP call.

2.7.1.2

5
6
7

2.7.1.3

11

2.7.1.4

14
15

2.7.1.5

18
19

2.7.1.6

22
23

A Privacy Mode procedure may be applied after an SSD Update procedure has been
successfully completed.

24
25

2.7.1.7

28
29

31

Rejection
When the BS receives a rejection indication (e.g., a mobile station Reject Order), it
sends the Rejection message to the MSC. No response is expected from the MSC. See
section 2.9.1.

27

30

Privacy Mode procedure

The Privacy Mode procedure will include the processes to: pre-load the BS with
parameters for signaling message encryption (SME) or privacy, enable and disable SME
or privacy.

21

26

SSD Update procedure

After the A-Key has been derived at the MS as a result of receiving appropriate
information via an ADDS Deliver message, an SSD Update procedure over the traffic
channel may also be used.

17

20

ADDS Deliver ACK

This message is sent from the BS to the MSC to report that an acknowledgment or a
rejection from the MS has been received at the BS for an OTASP application data
delivery. See section 2.7.3.2 for details of this message.

13

16

ADDS Deliver
This message is sent from the MSC to the BS or from the BS to the MSC to encapsulate
and transfer OTASP data on a traffic channel. See section 2.7.3.1 for details of this
message.

9
10

12

OTASP Data Exchanges

After a voice path is set up, the ADDS Deliver message will be used in both directions
to support exchange of OTASP data. In addition, the SSD update procedure and the
Privacy Mode procedure over the traffic channel may also be utilized. Please see section
2.8.4 for the call flows.

OTASP Call Setup

2.7.1.8

OTASP Call Clear

Normal call clearing procedures are utilized to clear OTASP calls.

92

TIA/EIA-2001

1
2
3

2.7.1.9

OTASP Message Flow

This section describes the message transactions between an MSC and BS to support
OTASP message transfer for the mobile.

time
MS

BS

comment

MSC

Origination Message
a
Normal Call Setup
ADDS Deliver
Data Burst (OTA)

c
d

L2 Ack/Reject Order with L2 Ack

ADDS Deliver Ack

Reject Order

f
g

Rejection

Data Burst (OTA)

L2 Ack

j
ADDS Deliver

If a Rejection
message is
received, the
remainder of this
scenario may be
omitted.

SSD Update

Optional

Terminal Re-Authentication

Optional

Privacy Mode Request

Optional

Repeat Steps c through k

Optional

Normal Call Clearing

5
6

Figure 2-25 - OTASP Message Flow: CDMA

93

TIA/EIA/IS-2001

a.

The MS transmits an Origination Message over the access channel of the air
interface to the BS to initiate the OTASP process.

b.

The MSC and the BS will utilize normal call setup procedures to establish the
OTASP call.

c.

Upon request from the Over the Air Function (OTAF), the MSC encapsulates
an OTASP data message within an ADDS Deliver message and sends it to the
BS.

d.

The BS extracts the OTASP data message and places it in the CDMA Data
Burst Message and transmits it over the traffic channel to the MS.

e.

The MS may respond with a Layer 2 Ack or a Reject Order containing a Layer 2
Ack acknowledging the Data Burst Message.

f.

When the BS receives a Layer 2 Ack or a Reject Order containing a Layer 2

Ack acknowledging the Data Burst Message from the MS response to an
ADDS Deliver message that contained a Tag information element, it sends an
ADDS Deliver Ack message to the MSC with the corresponding Tag value.

16

g.

The MS may return a Reject Order.

17

h.

The BS will send a Rejection message to the MSC to convey the information
contained in the Reject Order.

i.

The OTASP application in the MS responds by sending an OTASP data

message. The MS places the OTASP data message in the CDMA Data Burst
Message and transmits it over the traffic channel to the BS.

j.

Upon reception of the CDMA Data Burst Message, the BS responds with a
Layer 2 Ack.

k.

The BS extracts the OTASP data message and places it in the ADDS Deliver
message to the MSC.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

18
19
20
21
22
23
24
25
26

Steps (l) through (o) are optional.

27

l.

28
29
30

After the A-Key has been derived from information transferred via ADDS
Deliver messages, an SSD Update procedure over the traffic channel may also
be utilized to exchange authentication information (RANDSSD, RANDBS,
AUTHBS).

33

m. After an SSD Update procedure, Terminal Re-Authentication (see TIA/EIA/IS683-A) needs to be performed to generate the cipher key that will be used for
Privacy.

34

n.

After Terminal Re-Authentication, Privacy Mode procedures over the traffic

channel may also be applied to specify the use of either Signaling Message
Encryption (SME) or Privacy for the call.

o.

Multiple forward and reverse OTASP messages can be sent between the
OTASP endpoint in the network and the MS. The MSC and the BS will transfer
the messages whenever they are received.

p.

Once the OTASP service programming has been successful, the call can be
cleared using a regular Call Clear procedure.

31
32

35
36
37
38
39
40
41

94

TIA/EIA-2001

2.7.2. OTAPA support

3
4
5
6
7
8
9
10

Support of OTAPA is supported in this specification by the ADDS Deliver/Ack set of

messages. A specific Service Option (18 or 19) is required to set up the call. No specific
messages or information areas required beyond the messages required to set up a
Mobile Terminated call and to transfer ADDS messages. The only requirement for the
BS is to provide interworking between the air interface and the A1 interface for these
messages. The use of these messages by the Mobile Station and the MSC is beyond
the scope of this specification.

11

95

TIA/EIA/IS-2001

2.8

This section contains error handling guidelines and procedures. The contents of this
section do not override specific error handling in the other parts of this standard.

2
3

2.8.1

Rejection
The Rejection message is used by the BS to indicate to the MSC that the mobile station
has indicated rejection of a command/message. This is coded as a BSMAP message
when triggered by a Mobile Station Reject Order on the access channel and a DTAP
message otherwise.

5
6
7
8

Error Handling

2.8.1.1

Successful Operation
When the BS receives a rejection indication (e.g., a Mobile Station Reject Order) it shall
send the Rejection message to the MSC only in the cases listed below. No response is
expected from the MSC.

10
11
12

15

The Rejection message shall only be used in conjunction with a Mobile Station Reject
Order received as a response to an ADDS Page or ADDS Deliver operation (i.e., Data
Burst).

16

Please refer to section 6.1.8.1, Rejection, for the format and content of this message.

13
14

17

2.8.1.2

None.

18

19

Failure Operation

2.9

UNUSED SECTION

20

96

TIA/EIA-2001

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

2.10

Mobile Originated Calls With PACA Service

PACA (Priority Access Channel Assignment) allows a user to have priority access to
traffic channels on call origination. When the traffic channel is not available, the base
station can queue the mobile and update the queue position subsequently. When a
traffic channel becomes available, the BS serves the MS based on first come first served
within a priority.
The subscriber has two options for invocation of PACA: Permanent or Demand (see
TIA/EIA-664). In the permanent option, the feature is always available and is used
automatically whenever the user attempts to originate a call. In the demand option, the
feature is available only on request via dialing the feature code before the phone
number at the time of origination for that specific call.
In systems, by sending the PACA Message over the air-interface, the base station can
notify the user that the call is queued, the queue position is updated, or the PACA call
should be re-originated. When the PACA call is enabled, the MS shall operate in nonslotted mode. If the MS is directed by the user to cancel the queued PACA call, the MS
shall send the PACA Cancel Message.
Two conditions may occur on a call origination with PACA service. In the first
condition, the BS can not determine the availability of radio resources before sending
the CM Service Request to the MSC. Thus, the BS sends the CM Service Request to
the MSC which will not include any information about the availability of its radio
resources. In this case, the origination procedure shown in 2.2.2.1 is followed.
In the second case, the BS determines that radio resources are not available before
sending the CM Service Request. The BS sends an indication in the CM Service
Request message to notify the MSC that the radio resources are unavailable. In this
case, the origination procedure shown in 2.2.2.3.1 is followed.
The above procedures are defined based on the following principles:
The PACA queue is maintained and managed at the BS.

28

The timestamp is managed at the MSC.

29

The MSC assigns the priority level and time of a PACA eligible call and
informs the BS in the Assignment Request or PACA Command message.

The MSC maintains the timestamp information for the PACA call and assists in
maintaining the priority while the MS is roaming within the system by passing
the timestamp information to the new BS in the Assignment Request or PACA
Update message.

35

The BS may keep the MS informed of updated queue position.

36

The BS informs the MSC in case of re-origination of PACA call in the CM

Service Request message.

The PACA call can be canceled implicitly or explicitly by the MS, the BS or the
MSC.

30
31
32
33
34

37
38
39

97

TIA/EIA/IS-2001

2.10.1

PACA Service Support

Support of the PACA service in this standard involves the following messages:
1. PACA Command

2
3
4

2.

PACA Command Ack

3.

PACA Update

4.

PACA Update Ack

5.

CM Service Request

6.

Assignment Request

7.

Assignment Failure

10

2.10.1.1

This BSMAP message is sent by the MSC to inform the BS that PACA service is to be
applied to the call.

11
12

13

2.10.1.1.1

15
16

After sending the PACA Command message to the BS, the MSC starts timer Tpaca1
and waits for the PACA Command Ack message from the BS. When the BS receives
the PACA Command message, it will queue the call for PACA service and may send the
air interface PACA Message to notify the MS that the call was queued and to provide
the queue position. See sections 2.2.2.1 and 2.2.2.3.

17
18
19
20
21

Please refer to section 6.1.3.11, PACA Command, for the format and content of this
message.

22
23

2.10.1.1.2

26

2.10.1.2

29

2.10.1.2.1

32
33

Please refer to section 6.1.3.12, PACA Command Ack, for the format and content of
this message.

34
35

37

Successful Operation
Upon receipt of the PACA Command message from the MSC, if radio resources are not
available for the call the BS will queue the request and send the PACA Command Ack
message to notify the MSC that the call has been queued.

31

36

PACA Command Ack

This BSMAP message is sent by the BS to the MSC to acknowledge that the PACA
request has been queued successfully.

28

30

Failure Operation
If timer Tpaca1 expires before the MSC receives the PACA Command Ack message the
MSC may resend the PACA Command to the BS.

25

27

Successful Operation
Upon receipt of the CM Service Request message from the BS, if the MSC determines
that it needs to queue the call for PACA service, it will send this message to the BS
containing priority level and time stamp information for the call.

14

24

PACA Command

2.10.1.2.2

Failure Operation
None.

98

TIA/EIA-2001

2.10.1.3

This BSMAP message is sent, from either the BS or the MSC, to indicate that the BS or
MSC intends to modify the queued call.

2
3

PACA Update

2.10.1.3.1

Successful Operation

10

The PACA Update message is sent by the MSC or the BS to indicate to the receiving
entity (the BS or the MSC) that it shall take an appropriate action as specified by the
PACA Order information element in this message. After sending the PACA Update
message, the sending entity starts timer Tpaca2 and waits to receive a PACA Update
Ack message from the other entity. See sections 2.2.2.3.2 through 2.2.2.3.5 for example
scenarios.

11

The PACA Update message is used in the following cases:

5
6
7
8
9

12

When idle handoff occurs the MSC sends this message to instruct the old BS
to remove the request from its PACA queue.

In the case of consecutive PACA calls the MSC sends this message to instruct
the BS to remove the previous request (the call associated with the first called
number) from its PACA queue.

The MSC may send this message to request the BS to update its PACA queue.
If the MSC doesnt receive any response from the BS within a certain period of
time the MSC may clear all resources associated with the call.

The MSC may send this message to indicate to the BS that the call has been
canceled. The BS shall remove the request from its PACA queue and clear any
resources allocated for the call. In this case, the BS shall notify the MS that the
call has been canceled.

The BS may send this message to the MSC either autonomously, if it wants to
cancel the call, or upon the receipt of the PACA Cancel Message from the MS.

13
14
15
16
17
18
19
20
21
22
23
24
25

Please refer to section 6.1.3.13, PACA Update, for the format and content of this
message.

26
27

28
29
30

2.10.1.3.2

Failure Operation
If timer Tpaca2 expires before the sender (MSC or BS) receives the PACA Update Ack
message, then it may re-send the PACA Update message again.

99

TIA/EIA/IS-2001

2.10.1.4

This BSMAP message is sent by the BS or MSC to the MSC or BS to acknowledge that
an appropriate action has been taken by the BS or MSC and that its PACA information
has been updated.

2
3
4

2.10.1.4.1

Please refer to section 6.1.3.14, PACA Update Ack, for the format and content of this
message.

8
9

11

Successful Operation
The MSC (BS) sends the PACA Update Ack message to inform the MSC (BS) of the
result of the action taken in response to the PACA Update.

10

PACA Update Ack

2.10.1.4.2

Failure Operation
None.

100

TIA/EIA-2001

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

2.11

Support of Position Location Service

The Position Location Service provides for the transfer of Position Location Data
between an application residing on a mobile station and an application within the
network (i.e. Position Determining Entity (PDE)). Support of the TIA/EIA 801 messages
using the ADDS message across the "A" interface is mandatory. Other network
procedures carried out by entities providing Position Location Data (PLD) are beyond
the scope of this standard.
Position Location Data is transferred between MSC and BS using ADDS procedures on
both the control and traffic channels. Normally the ADDS messages are used to carry
application data between the mobile station and the MSC which is transparent to the
base station, however, for PLD applications a base station may trigger the position
determination process. Thus, an active mobile station is able to send and receive
Position Location Data messages at any time. The Position Location Data and
associated messaging is defined in TIA/EIA 801. This is transparent to the MSC-BS
Interface, and is carried as part of the ADDS User Part element in the MSC-BS A1
Interface messages.
When transferring Position Location Data between Mobile Station and MSC/BS across
the control channel the following message will be used: ADDS Page, ADDS Page Ack.,
and ADDS Transfer. When transferring Position Location Data between Mobile Station
and MSC/BS across the traffic channel the following message will be used: ADDS
Deliver and ADDS Deliver Ack.

101

TIA/EIA/IS-2001

2.12

User Zones (UZ) are geographic areas. Based on the identified User Zone, the network
provides the MS a set of services and features. This section describes the messages
and procedures to support User Zones. Included are the mechanisms used to set up a
User Zone for an MS.

2
3
4
5

Location Updating Request, CM Service Request, and Paging Response, messages are
sent by the BS to indicate the MS's active User Zone. The Flash with Info message is
sent from the MS to the BS during the call to change the user zone. Flash with
Information and the Feature Notification messages are sent by the MSC to the BS to
reject or change the MS's active User Zone.

6
7
8
9
10

11

12
13
14
15
16
17

User Zones

2.12.1

Invoking User Zone at Registration

When the MSs registration message is received by the BS, it constructs the Location
Updating Request message and sends the message to the MSC. If the MSC is
successful in processing the message, it sends a Location Updating Accept Message
to the BS. If the MSC rejects the MS's User Zone the MSC sends a Feature Notification.
This message will include the rejection action indicator value, indicating that the User
Zone was rejected. The MSC may also send an alternate User Zone for the MS to use.
time
MS

BS

Registration Message

a
Location Updating Request
Location Updating Accept

Feature Notification

comment

MSC

Feature Notification

b
c
d
e

18

Steps d and e
are used by the
MSC for User
Zone rejection.

19

Figure 2-26 - Location Registration using User Zones

20

a.

The MS initiates registration operation by sending the Registration Message to

the BS.

b.

On reception of the Registration Message the BS constructs the Location

Updating Request message, including the MS's User Zone and places it in a
Complete Layer 3 Information message, and sends it to the MSC.

c.

The MSC sends the Location Updating Accept message to the BS to indicate
that the Location Updating Request message has been processed.

21
22
23
24
25
26

28

The following two steps are only used when the MSC rejects the User Zone requested
by the MS.

29

d.

The MSC will send a Feature Notification message to reject the User Zone. If the
MSC rejects the MS User Zone the MSC will send a rejection indication to the
mobile and may send an alternate User Zone for the mobile to use.

e.

The BS sends the Feature Notification message to the MS with the information it
received from the MSC

27

30
31
32
33

102

TIA/EIA-2001

2.12.2

Use of User Zones During Call Setup

The User Zone is broadcast on the paging channel. If the MS rejects the User Zone
sent by the MSC, the MS may choose a preferred User Zone and send the preferred
User Zone in the page response message to the network.

2
3
4

For an originating call the MS sends its User Zone in the Origination message which the
BS uses to create the CM Service Request message. The BS sends the CM Service
Request message to the MSC. The MSC responds to the CM Service Request with an
Assignment Request message to the BS to request assignment of radio resources. If the
MSC rejects the MS User Zone the MSC may send an alternate User Zone for the
mobile to use.

5
6
7
8
9
10

time
MS

BS

comment

MSC

Complete L3 Info: CM Service Request/Paging Response

Assignment Request

Flash with Information

.
.
.
Assignment Complete
.
.
.
.
Flash with information
.

d
e

Steps d and e
are used by the
MSC for User
Zone rejection.

11
12
13

Figure 2-27 - Mobile Call setup Using User Zone

a.

The BS constructs the CM Service Request message or paging response

message, including the User Zone the MS transmitted and send it to the MSC.

The MSC sends an Assignment Request message to the BS to request

assignment of radio resources.

18

The BS sends an Assignment Complete message to the MSC.

19

The MSC will send a Flash with Information message to reject the MS's
preferred User Zone. If the MSC rejects the MS preferred User Zone the MSC
may send a rejection indication and may send an alternate User Zone for the
mobile to use, in the Flash with Information message.

The BS sends the Flash with Information message to the MS with the
information it received from the MSC.

14
15
16
17

20
21
22
23
24

103

TIA/EIA/IS-2001

2.12.3

It is possible to change the User Zone for an MS while a call is in progress. (i.e. after a
hard handoff.) The MS sends a Flash with Information message to the BS to change its
User Zone during a Call. The Flash with Information message is used from the MSC and
the BS to accomplish this.

2
3
4
5

6
7
8
9
10
11
12

Changing User Zone During a Call

2.12.3.1

User Zone Change

If the MS wishes to change User Zone during a call, it sends the Flash with Information
message (including a User Zone Update Request information record) to the BS. The BS
then sends the Flash with Information message to the MSC. If the MSC wants to
change the User Zone being used by a MS or to reject a User Zone requested by the
MS, the MSC may send a Flash with Informationmessage to the BS indicating the new
User Zone.
time
MS

BS

comment

MSC

Flash with Information

a
Flash with Information

Flash with Information

c
Flash with Information

13
14
15
16

Figure 2-28 - Updating the User Zone During a Call

a.

The MS transmits a Flash with Information Message, over the reverse

traffic channel of the air interface to the BS to request service. Included in
this message is the User Zone the MS prefers contained in the User Zone
Update Request information record.

b.

The BS sends a Flash with Information message to the MSC. Included is

the preferred User Zone the MS transmitted.

c.

If the MSC rejects the MS preferred User Zone the MSC sends a Flash
with Information with an IS-95 Information Records element including an
indication of the rejection and optionally, an alternate User Zone for the
mobile to use. Note, this message is sent only if the MSC rejects the MS
preferred User Zone.

d.

The BS sends a Flash with Information message to the MS. Included is the
User Zone information the MSC transmitted.

17
18
19
20
21
22
23
24
25
26
27
28

29

104

TIA/EIA-2001

2.13

Data services are grouped into two categories: circuit-oriented (includes Asynchronous
Data and Group-3 Fax services) and packet. Procedures applicable to circuit-oriented
data calls are described in this section.

2
3
4

For all calls supporting circuit-oriented data services, an Interworking Function (IWF)
exists that interfaces between the transmission of the data in the fixed network and the
transmission of the data over the air interface. For this standard, the IWF for circuitoriented data calls is considered to be located at the MSC. See section 6.2.2.66 for
information on valid service options.

5
6
7
8
9

Once an IWF has been allocated for a circuit-oriented data call, it shall remain anchored
for the duration of the call.

10
11

12

Circuit Data Calls

2.13.1

Asynchronous Data and Group-3 Fax Services

15

This service allows the MS to send and receive asynchronous data. The procedures
and interfaces are specified by TIA/EIA/IS-707 which specifies compliance with other
TIA data standards and ITU recommendations (e.g., EIA/TIA-602, V.32 bis, V.42).

16

Both mobile origination and mobile termination of this service shall be Data Only.

13
14

17

2.13.1.1

For circuit oriented data only calls, normal call origination, call termination, and call
clearing procedures apply. These procedures are described in section 2.2.1, 2.2.2, and
2.3 respectively.

18
19
20

21

22
23
24
25
26
27
28
29

Data Only

2.13.2

A5 Connections for Circuit Data Calls

The A5 interface connects the SDU to the IWF when those entities are located in
different pieces of equipment. The A5 interface carries a duplex stream of user traffic
between the IWF and SDU.
For TIA/EIA/IS-707 the RLP is terminated in the SDU. The A5 interface in this case
carries the output of the RLP function specified in TIA/EIA/IS-707 from the SDU
function to the IWF.
The protocol currently defined in this standard for the A5 interface is ISLP. See
TIA/EIA/IS-728.

105

TIA/EIA/IS-2001

2.13.3

Support for Handoffs of Asynchronous Data and G3 Fax Calls

This standard supports Handoffs for Asynchronous Data and Group 3 fax calls as
indicated in table 2-2.

Table 2- 2 - Support of Asynchronous Data/G3 Fax Handoffs

Type of Handoff

Supported for Asynchronous Data

and G3 Fax

Intra-BS, Intra-MSC Soft Handoff

Yes

Intra-BS, Intra-MSC Hard Handoff

Yes

Inter-BS, Intra-MSC Soft Handoff

Yes

Inter-BS, Intra-MSC Hard Handoff

Yes

Inter-BS, Inter-MSC Soft Handoff

Yes

Inter-BS, Inter-MSC Hard Handoff

No

106

TIA/EIA-2001

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

2.14

Packet Data Calls

Data services are grouped into two categories: circuit-oriented (includes Asynchronous
Data and Group-3 Fax services) and packet. Procedures applicable to packet data calls
are described in this section. See Section 6.2.2.66 for valid service options.
For all calls supporting packet data services, a Packet Data Serving Node (PDSN) exists
that interfaces between the transmission of the data in the fixed network and the
transmission of the data over the air interface. The PDSN interfaces to the BS through a
Packet Control Function (PCF), which may or may not be co-located with the BS.
For purposes of the protocol of this standard, there are three packet data service states:
Active/Connected, Dormant, and Null/Inactive. In the Active/Connected State, a
physical traffic channel exists between the mobile station and the base station, and
either side may send data. In the Dormant State, no physical traffic channel exists
between the mobile station and the base station, but the PPP link between the mobile
station and the PDSN is maintained. In the Null/Inactive State, there is no traffic channel
between the mobile station and the base station and no PPP link between the mobile
station and the PDSN.

17

Active /
Connected
State

Dormant
State

Null/Inactive
State
18
19

Figure 2-29 - Packet Data Service State Transitions

20

A1 and A8 connections are maintained during the Active / Connected State and
released during transition to Dormant or Null/Inactive State. Tthe A10 connection is
maintained during the Active/Connected and the Dormant State.

21
22
23
24
25
26
27
28
29
30

As part of the support for the Dormant State, the cdma2000 air interface supports a Data
Ready to Send indicator that is used on Origination. When a mobile terminal sends an
origination request with a packet data service option specified, it will include the Data
Ready to Send (DRS) bit. This indicator will be set to 1 on initial call setup and when the
terminal wishes to transition from Dormant to Active because it has data to send and is
requesting the establishment of a traffic channel. The DRS bit will be set to 0 to indicate
that the terminal has transitioned a Packet Zone boundary while dormant, and is
sending the origination request to update the network as to its current location.

31
32
33
34

On receipt of an origination with the DRS bit set to 1, the BS will initiate the call setup
procedure as shown in Section 2.14.8.1, which will normally result in the establishment
of a traffic channel and in the A8 and A10 bearer connections being established.

35
36
37

When the BS receives an origination with the DRS bit set to 0, the BS will delay the
establishment of a traffic channel until after the A8 and A10 bearer connection
107

TIA/EIA/IS-2001

establishment procedures are complete. During the A8 bearer connection establishment

procedure, the BS will indicate to the PCF that a DRS=0 has been received through the
use of the Data Ready Indicator element in the A9-Setup-A8 message. If the PCF has
data from the network to deliver to the terminal, it will indicate this by setting the Cause
element in theA9-Connect-A8 message to the Data Ready to Send value. The BS will
then establish a traffic channel to the terminal and complete a normal call setup
procedure as in Section 2.14.8.1.

1
2
3
4
5
6
7
8

If the PCF does not have data, it indicates that the A8 is not being established by
sending the A9-Release-A8 Complete message to the BS. The BS will then return an
Assignment Failure message to the MSC with the Cause value set to Packet Call Going
Dormant. Upon receipt of the Assignment Failure message, the MSC returns a Clear
Command to the BS with the Cause value set to Do Not Notify Mobile. The BS sends a
Clear Complete message to the MSC upon receipt of the Clear Command message.

9
10
11
12
13
14
15
16
17

18

2.14.1

Packet Data Assumptions

The following assumptions are made regarding packet data.

19

1.

Each PCF corresponds to a packet zone. Location update is performed when

the mobile roams into a new PCF area. No dormancy knowledge is required by
the PDSN.

23

2.

The set of PDSNs that a PCF may connect to is known at the PCF.

24

3.

While a call is active, handoff will normally result in connection to the same
PDSN to the new PCF.

4.

When connecting to a PDSN during an active session handoff or during

dormant handoff, if the target PDSN recognizes the terminal and the session,
and itdoes not require a restart of PPP.

5.

Links between PCFs and PDSNs support both the signaling and traffic
channels.

6.

The signaling channels support call connects, disconnects, as well as

signaling for QoS, accounting information etc.

33

7.

The traffic channels support in-sequence delivery of data payload.

34

8.

A PCF initiates an A10 connection, but either the PCF or the PDSN may drop
it.

9.

The A10/A11 interfaces are assumed to be supported on a private IP network

for security considerations.

20
21
22

25
26
27
28
29
30
31
32

35
36
37

10. When IP is used as the network layer for the A10 bearer, standard IP QoS
mechanisms may be employed.

38
39

40

41
42
43
44

2.14.2

BS Initiated Call Setup

The BS can initiate a call by sending the BS Service Request message to the MSC. The
MSC acknowledges the request by sending the BS Service Response message to the
BS and initiates a normal call termination procedure as shown in Figure 2-10 below.
The following sections describe this procedure.
108

TIA/EIA-2001

2.14.2.1

This BSMAP message is sent from the BS to the MSC to begin a BS initiated call setup.

2.14.2.1.1

5
6

Please refer to section 6.1.2.28, BS Service Request, for the format and content of this
message.

7
8

2.14.2.1.2

11

2.14.2.2

14

2.14.2.2.1

17
18

Please refer to section 6.1.2.29, BS Service Response, for the format and content of
this message.

19
20

22

Successful Operation
The MSC shall send a BS Service Response message to the BS originating the BS
Service Request message. That BS, on receiving a BS Service Response message stops
timer T311.

16

21

BS Service Response
This BSMAP message is sent from the MSC to the BS in response to a BS Service
Request.

13

15

Failure Operation
If a BS Service Response message is not received at the BS before the expiration of
timer T311, then the BS may resend the BS Service Request message.

10

12

Successful Operation
In order to initiate a call setup, the BS sends a BS Service Request message to the MSC
containing the identity of the mobile station that needs to be paged. The BS starts timer
T311 and awaits the reception of the BS Service Response message.

BS Service Request

2.14.2.2.2

Failure Operation
None.

109

TIA/EIA/IS-2001

2.14.2.3

The sections below provide success and failure cases for BS initiated call setup.

BS Initiated Call Setup Example

2.14.2.3.1

Mobile Termination Initiated by the BS: Successful Case

This section describes the call flow associated with a BS initiated call setup.

time
BS

MS

comment

MSC

BS Service Request
a
T311

BS Service Response
b

Mobile Terminated Call Setup

See section 2.2.4.1

5
6

Figure 2-30 - Mobile Termination Initiated by the BS

a.

The BS, in order to put a specific mobile on a traffic channel, sends a BS Service
Request to the MSC and starts timer T311.

b.

The MSC acknowledges the call setup request by sending a BS Service Response
message to the BS that sent the BS Service Request message. The BS stops timer
T311 upon receipt of the BS Service Response message.

c.

The MSC sends a Paging Request message to establish a mobile terminated call as
illustrated in section 2.2.4.1, Mobile Termination.

8
9
10
11
12
13

14
15
16
17

2.14.2.3.2

Mobile Termination Initiated by the BS: Failure Case

When the MSC cannot accept the request from the BS, the call flow in Figure 2-30 will
be terminated in step (b). The MSC shall include a cause value in the BS Service
Response message indicating the reason for refusing the call setup request from the BS.

18

110

TIA/EIA-2001

2.14.3

A8/A9 Interface Procedures

The following sections describe the messages and procedures for the
A8/A9 interfaces. The sections are as follows:A8/A9 Interface Setup
Procedures and Messages,

A8/A9 Interface Clearing Procedures and Messages,

A8/A9 Interface Handoff Procedures and Messages,

Packet Data State Transitions, and

A8/A9 Interface Call Flows.

3
4
5

10

2.14.4

This section contains the messages used to set up an A8 connection.

11

12

2.14.4.1

14

16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

A9-Setup-A8
This message is sent from the BSC to the PCF on the A9 interface to establish an A8
connection

13

15

A8/A9 Interface Setup Procedures And Messages

2.14.4.1.1

Successful Operation
When the BSC receives an Assignment Request from the MSC, as a result of sending a
CM Service Request (in response to an Origination message from the mobile with a
Service Option that requests packet data service and with the DRS bit set to 1), or as a
result of sending a Page Response, it initiates the procedure for establishing radio
traffic channels. After establishing traffic channels, the BSC determines the
characteristics for an A8 connection such as QoS and generates an A9-Setup-A8
message indicating the normal call setup (i.e., the handoff indicator field of the A9Setup-A8 message is set to 0). The BSC sends the message to the PCF on the A9
interface and starts timer TA8-Setup. Upon receiving the message, the PCF initiates the
procedure for establishing an A10 connection.
After establishing an A10 connection, the PCF sends an A9-Connect-A8 message to
the BSC. For the case where the DRS bit is set to 0, the BSC will await the response from
the PCF to determine if a traffic channel needs to be established.
When the mobile station performs hard handoff during packet services, the target BSC
sends the A9-Setup-A8 message upon receipt of the Handoff Request from the MSC
and starts timer TA8-Setup. In this case, the BSC sets the Handoff Indicator field of the
A9-Setup-A8 message to 1 and Data Ready Indicator is set to 1.
In the case of dormant handoff the BSC sends the A9-setup-A8 message to the PCF
upon receipt of the Assignment Request from the MSC. For this case, it will set both
the DRS Indicator and the Handoff Indicator to 0. Please refer to section 6.1.10.1, A9Setup-A8, for the format and content of this message.

111

TIA/EIA/IS-2001

2.14.4.1.2

Failure Operation
If the BSC fails to receive an A9-Connect-A8, that is to say, the timer TA8-setup has
expired before receiving an A9-Connect-A8 message, the BSC sends an Assignment
Failure message or a Handoff Failure message, as appropriate, to the MSC.

2
3
4
5

2.14.4.2

This A9 message is used to respond to an A9-Setup-A8 message.

2.14.4.2.1

11
12
13
14
15

Then the BSC sends an Assignment Complete message or a Handoff Request Ack
message to the MSC to indicates all the resources for requested connection has been
allocated successfully.

16
17
18

Please refer to section 6.1.10.2, A9-Connect-A8, for the format and content of this
message.

19
20

22
23
24
25
26

Successful Operation
The PCF sends an A9-Connect-A8 message to the BSC in response to an A9-Setup-A8
message. If establishment of an A10/A11 connection is needed (e.g., during normal call
setup), this message shall be sent after the connection establishment is successful. If
the handoff indicator field of the A9-Setup-A8 message is set to 1, the PCF starts timer
Twaitho9. Twaitho9 is stopped by the PCF upon receipt of the A9-AL(Air Link)
Connected message. Upon receiving the A8-Connnect message, the BSC stops the
timer TA8-setup.

9
10

21

A9-Connect-A8

2.14.4.2.2

Failure Operation
If the A10/A11 connection establishment procedure is required but fails , the PCF
should send A9-Release-A8 Complete message with Cause value set to PDSN
resources not available (0x79)".
If the timer Twaitho9 expires, the PCF should initiate clearing of the A8 connection as
shown in Figure 2-36 steps b through d.

112

TIA/EIA-2001

2.14.4.3

This A9 interface message is sent from the PCF to the BSC to begin a BS initiated call
setup.

2
3

2.14.4.3.1

6
7

Please refer to section 6.1.10.6, A9-BS Service Request, for the format and content of
this message.

8
9

2.14.4.3.2

12

2.14.4.4

15

2.14.4.4.1

18
19

Please refer to section 6.1.10.7, A9-BS Service Response, for the format and content
of this message.

20
21

23

Successful Operation
The BSC shall send an A9-BS Service Response message to the PCF originating the A9BS Service Request message. Upon receiving the A9-BS Service Response Message,
the PCF stops timer Tbsreq9.

17

22

A9-BS Service Response

This A9 interface message is sent from the BSC to the PCF in response to an A9-BS
Service Request.

14

16

Failure Operation
If an A9-BS Service Response message is not received at the PCF before the expiration
of timer Tbsreq9, then the PCF may resend the A9-BS Service Request message.

11

13

Successful Operation
In order to initiate a call setup, the PCF sends an A9-BS Service Request message to the
BSC containing the identity of the mobile station that needs to be paged. The PCF
starts timer Tbsreq9 and awaits the reception of the A9-BS Service Response message.

10

A9-BS Service Request

2.14.4.4.2

Failure Operation
None.

113

TIA/EIA/IS-2001

2.14.5

Procedures for clearing the A8 connection are described in this section. An A8

connectionclearing is initiated whenever the state of the packet service changes from
the active state to the dormant/null state. Clearing the A8 connection and the traffic
channel does not necessarily correspond to clearing of the packet data service session.

2
3
4
5

A8/A9 Interface Clearing Procedures and Messages

2.14.5.1

Successful Clearing Scenarios

An A8 connection clearing occurs:

when a packet data inactivity timer in the BSC expires. The BSC, after sending the
Clear Request message, sets timer T300 and waits for a Clear Command message
from the MSC. To release all allocated resources, the MSC shall send a Clear
Command message to the BSC, start timer T315, and wait for the Clear Complete
message from the BSC. After stopping timer T300 and releasing the air resources,
the BSC sends an A9-Release-A8 message to the PCF and starts timer Trel9. The
PCF responds with an A9-Release-A8 Complete message. Then the BSC sends a
Clear Complete message and stops timer Trel9. The call flow scenario is illustrated
in section 2.14.7.2 "BS Initiated Call Release to Dormant State."

when the packet data inactivity timer in the MS expires. When the BS receives a
Release Order requesting the transition to dormant, the BSC shall send a Clear
Request message to the MSC. The rest of the procedure is same as the BSC
initiated scenario. The call flow scenario is illustrated in section 2.14.7.3 "MS
Initiated Call Release to Dormant State."

when the MS releases the call. When the BSC receives a Release Order, the BSC
shall send a Clear Request message to the MSC and start timer T300. To release all
allocated resources, the MSC shall send a Clear Command message to the BSC,
start timer T315, and wait for the Clear Complete message from the BSC. After
stopping timer T300 and releasing the air resources with the Release Order, the BSC
sends an A9-Release-A8 message to the PCF and starts timer Trel9. The PCF
responds with an A9-Release-A8 Complete message. Not that in this situation, the
A10/A11 connection is not released. Then the BSC sends a Clear Complete
message and stops timer Trel9. The call flow scenario is illustrated in section
2.14.7.4 "MS Power Down."

9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

114

TIA/EIA-2001

1
2
3
4
5
6
7
8
9
10
11
12

13
14
15
16

2.14.5.2

when the A10/A11 connection is released by the PDSN. When the PCF detects that
the A10/A11 connection is released, the PCF sends an A9-Disconnect-A8 message
to the BSC and starts timer Tdiscon9. Then the BSC initiates the release of the A8
connection by sending an A 9-Release-A8 message and starts timer Trel9. The PCF
responds with an A9-Release-A8 Complete message and stops timer Tdiscon9. The
BSC, after sending the Clear Request message and stopping timer Trel9, sets timer
T300 and waits for a Clear Command message from the MSC. To release all
allocated resources, the MSC shall send a Clear Command message to the BSC,
start timer T315, and wait for the Clear Complete message from the BSC. Then the
BSC stops timer T300, releases the air resources, and responds with a Clear
Complete message. The call flow scenario is illustrated in section 2.14.7.5 PDSN
Initiated Service Release."

Unsuccessful A8 Interface Clearing Procedures

See sections 2.14.5.3.2, 2.14.5.4.2, and 2.14.5.5.2 for unsuccessful call clearing
procedures related to the A9-Release-A8, A9-Release-A8 Complete and A9-DisconnectA8 messages.

115

TIA/EIA/IS-2001

2.14.5.3

This A9 interface message is sent from the BSC to the PCF to request the release of the
associated dedicated resource.

2
3

2.14.5.3.1

6
7

When the PCF receives the A9-Release-A8 message, it stops timer Tdiscon9 if it is
active and performs the appropriate procedure to release the associated dedicated
resources. For the handoff case, Twaitho9 timer will be stopped.

8
9
10

Please refer to section 6.1.10.4, A9-Release-A8, for the format and content of this
message.

11
12

2.14.5.3.2

15
16
17
18
19

2.14.5.4

22

2.14.5.4.1

25
26

Please refer to section 6.1.10.5, A9-Release-A8 Complete, for the format and content
of this message.

27
28

30

Successful Operation
Upon receipt of the A9-Release-A8 message from the BSC, the PCF closes the A8
connection and sends an A9-Release-A8 Complete to notify the BSC of the outcome.
The BSC stops timer Trel9 upon receipt of this message.

24

29

A9-Release -A8 Complete

This A9 interface message is sent from the PCF to the BSC to acknowledge completion
of the request to release the A8 connection.

21

23

Failure Operation
If an A9-Release-A8 Complete message is not received from the PCF while timer Trel9 is
active, the BSC may resend the A9-Release-A8 message to the PCF and restart timer
Trel9. If the A9-Release-A8 Complete message is not received from the PCF before timer
Trel9 expires a second time or if the BSC chooses to not resend the A9-Release-A8
message, the BSC shall cease further supervision of this call connection, release all
dedicated resources, air and terrestrial, and shall release the connection.

14

20

Successful Operation
When the BSC needs to release an A8 connection, it sends an A9-Release-A8 message
to the PCF. The BSC starts timer Trel9 and waits for the A9-Release-A8 Complete
message from the PCF.

13

A9-Release -A8

2.14.5.4.2

Failure Operation
None.

116

TIA/EIA-2001

2.14.5.5

This A9 interface message is sent from the PCF to the BSC to request to release the
associated dedicated resource.

2
3

2.14.5.5.1

Please refer to section 6.1.10.3, A9-Disconnect-A8, for the format and content of this
message.

7
8

10
11
12
13
14
15

Successful Operation
When the PCF needs to release an A8 connection, it sends an A9-Disconnect-A8
message to the BSC. The PCF starts timer Tdiscon9.

A9-Disconnect-A8

2.14.5.5.2

Failure Operation
If an A9-Release-A8 message is not received from the BSC while timer Tdiscon9 is
active, the PCF may resend an A9-Disconnect-A8 message to the BSC and restart timer
Tdiscon9. If the A9-Release-A8 message is not received from the BSC before timer
Tdiscon9 expires a second time or if the PCF chooses to not resend the A9-DisconnectA8 message, the PCF shall cease further supervision of this call connection, shall send
the A9-Release-A8 Complete message, and release its resources.

117

TIA/EIA/IS-2001

2.14.6

This section contains the messages used during handoff procedure.

2.14.6.1

5
6
7
8
9

2.14.6.1.1

12
13

Upon the receipt of the A9-AL Connected message, the PCF updates its routing table to
route packet data sent from PDSN to the (target) BSC managing the active air link. The
PCF performs A10/A11 connection establishment if the A10/A11 connection has not
been established yet.

14
15
16
17

Please refer to section 6.1.10.8, A9-AL Connected, for the format and content of this
message.

18
19

2.14.6.1.2

2.14.6.2

24

2.14.6.2.1

27
28

Please refer to section 6.1.10.9, A9-AL Connected Ack, for the format and content of
this message.

29
30

32

Successful Operation
Upon receipt of an A9-AL Connected message from the (target) BSC, the PCF shall
transmit an A9-AL Connected Ack message to the target BSC to indicate the outcome
of processing the received message. The (target) BSC shall stop timer Talc9.

26

31

A9-Air Link (AL) Connected Ack

The A9-AL Connected Ack message is sent from the (target) PCF to the (target) BSC to
indicate the result of processing the A9-AL Connected message.

23

25

Failure Operation
If timer Talc9 expires, the message may be resent.

21

22

Successful Operation
After the mobile station performs (inter-PCF) hard handoff including the case of return
on failure, the (target) BSC managing active air link sends the A9-AL Connected
message to the (target) PCF and starts timer Talc9.

11

20

A9-Air Link (AL) Connected

After the mobile station performs (inter-PCF) hard handoff, the A9-AL Connected
message is sent from the target) BSC managing the active air link to the (target) PCF.
This message is employed in order to notify the (target) PCF ( that handoff is
successfully completed and) that the air link has been established and that the PCF can
send packets on the new A8 connection. An A9-AL Connected Ack message is
expected in response.

10

A8/A9 Interface Handoff Procedures and Messages

2.14.6.2.2

Failure Operation
None.

118

TIA/EIA-2001

2.14.6.3

When the mobile station performs hard handoff, the A9-AL Disconnected message is
sent from the source BSC to the source PCF. This message is employed in order to
notify the source PCF that the air link is temporarily disconnected. An A9-AL
Disconnected Ack message is expected in response.

2
3
4
5

2.14.6.3.1

8
9

Upon receipt of an A9-AL Disconnected message from the source BSC, the PCF shall
stop transmitting packet data and starts buffering packets from the PDSN.

10
11

Please refer to section 6.1.10.10, A9-AL Disconnected, for the format and content of
this message.

12
13

2.14.6.3.2

2.14.6.4

A9-Air Link (AL) Disconnected Ack

The A9-AL Disconnected Ack message is sent from the PCF to the BSC to indicate the
result of processing the A9-AL Disconnected message.

17
18

19

Failure Operation
If timer Tald9 expires, the message may be resent.

15

16

Successful Operation
When the source BSC receives the Handoff Command message which instructs it to
perform hard handoff, the source BSC shall send an A9-AL Disconnected message to
the PCF and start timer Tald9.

14

A9-Air Link (AL) Disconnected

2.14.6.4.1

Successful Operation
Upon receipt of an A9-AL Disconnected message from the BSC, the PCF shall transmit
an A9-AL Disconnected Ack message to the BSC to indicate the outcome of processing
the received message. The source BSC shall stop timer Tald9 upon receipt of the A9-AL
Disconnected Ack message.

20
21
22
23

Please refer to section 6.1.10.11, A9-AL Disconnected Ack, for the format and
content of this message.

24
25
26

27
28

2.14.6.4.2

Failure Operation
None.

119

TIA/EIA/IS-2001

2.14.7

A8/A9 Call Flows

2.14.7.1

Mobile Initiated Initial Call Setup and Mobile IP Registration Successful

Operation

4
5

When an MS initiates a call and Mobile IP Registration has not initiated yet, Mobile IP
Registration is performed before transmitting packet data.

6
7

MS

BSC

MSC

PCF

PDSN

Origination

a
BS ACK Order

b
CM Service Request

c
T303

Assignment Request

d
IS-2000
TCH
Establishment
procedure

T10

e
A9-Setup-A8

f
TA8-Setup
A9-Connect-A8

A10/A11
Connection
Establishment
procedure

g
h

Assignment Complete

i
Establishing PPP connection, Mobile IP Registration

Transmitting packet data

8
9
10
11
12

Figure 2-31 - Mobile Initiated Initial Call Setup and Mobile IP Registration
Successful Operation
a.

The MS transmits an Origination Message (DRS=1), with layer 2

acknowledgment required, over the access channel of the air interface to the
BSC to request packet data service.

b.

The BSC acknowledges the receipt of the Origination Message with a Base
Station Acknowledgment Order to the MS.

13
14
15
16

120

TIA/EIA-2001

c.

The BSC constructs the CM Service Request message, places it in the

Complete Layer 3 Information message, sends the message to the MSC, and
starts timer T303.

d.

The MSC sends an Assignment Request message to the BSC to request

assignment of radio resources and starts timer T10. For packet data service
terrestrial circuit between the MSC and the BSC is not required.

e.

The BSC and the MS initiate the establishment of a radio traffic channel.

f.

The BSC transmits an A9-Setup-A8 message to PCF with Data Ready

Indicator set to 1 to establish an A8 connection and starts timer TA8-setup.

10

g.

Procedure for establishing A10/A11 connection is performed.

11

h.

Upon establishment of the A10/A11 connection, the PCF establishes A8

connection and transmits an A9-Connect-A8 Message.i.
Upon receiving
an A9-Connect-A8 message, the BSC stops the timer TA8-setup and transmits
Assignment Complete message. The MSC stops timer T10. This step may
occur any time after radio link establishment.

j.

PPP connection establishment procedure and Mobile IP Registration on the

PPP connection are performed between the MS and PDSN.

1
2
3
4
5
6

12
13
14
15
16
17

18
19

121

TIA/EIA/IS-2001

2.14.72

BS Initiated Call Release to Dormant State

This section describes the call flow associated with a BSC initiated packet service
deactivation (active-to-dormant state transition). In order to simplify the diagram, it is
assumed that for purposes of this example, the packet call is not in inter-BSC soft/softer
handoff prior to the deactivation.

2
3
4
5

MS

MSC/VLR

BS

PCF

PDSN

Active/PPP connected

Comment

Clear Request

T300
Clear Command
TCH
Release
Procedure

Time

c
d

T315

A9-Release-A8

Trel9

A9-Release-A8 Complete

Clear Complete

Dormant/PPP connected

6
7
8

Figure 2-32 - BS Initiated Call Release to Dormant State

a.

While the packet data service option is connected, the BSC should maintain a
packet data inactivity timer. The timer should be reset whenever non-idle RLP
data frames are sent or received.

b.

If the packet data inactivity timer expires, the BSC should release the Traffic
Channel. The BSC sends a Clear Request message to the MSC to initiate the
call clear transaction, and starts timer T300.

c.

The MSC starts timer T315 and sends a Clear Command message to the BSC to
instruct the BSC to release the associated dedicated resources. The BSC stops
timer T300.

18

d.

BS initiates traffic channel release using existing procedures.

19

e.

The

9
10
11
12
13
14
15
16
17

MS

acknowledges

122

the

Release

message.

TIA/EIA-2001

f.
The BSC then sends an A9-Release-A8 message, with a
Cause value set to Packet call going Dormant, to the PCF to instruct the PCF
to release the associated dedicated resources, and starts timer Trel9. . Note
that in this scenario the A10/A11 connection is not released.

1
2
3
4
5

g.

The PCF acknowledges the A9-Release-A8 message by returning an A9Release-A8 Complete message. The BSC stops timer Trel9.

h.

The BSC then returns a Clear Complete message to the MSC. The MSC stops
timer T315 and releases the underlying transport connection. Clear Complete
may occur any time after the traffic channel is released.

i.

The MS goes to the dormant state.

6
7
8
9
10

123

TIA/EIA/IS-2001

2.14.7.3

MS Initiated Call Release to Dormant State

This section describes the call flow associated with a mobile station deactivation
(active-to-dormant state transition) initiated by MS. In order to simplify the diagram, it is
assumed that for purposes of this example, the packet call is not in inter-BS soft/softer
handoff prior to the deactivation.

2
3
4
5

MS

BSC

MSC/VLR

PCF

Active / PPP connected

PDSN

Time

Comment

Release Order

b
Clear Request
T300

Clear Command

d
TCH

Release
Procedure

T315

f
A9-Release-A8
Trel9

A9-Release-A8 Complete
Clear Complete

g
h
i

Dormant / PPP connected

6
7
8
9

Figure 2-33 - MS Initiated Call Release to Dormant State

a.

The mobile maintains a packet data inactivity timer. The timer is reset whenever
a non-idle RLP data frame is sent or received.

b.

If the packet data inactivity timer expires, the mobile requests the BSC to
disconnect the traffic channel. The mobile station sends a Release Order with
ORDQ = 00000000,to the BSC to request a transition to the dormant state.

c.

The BSC then sends a Clear Request message to the MSC to initiate the call
clear transaction, and start timer T300.

d.

The MSC starts timer T315 and sends a Clear Command message to the BSC to
instruct the BSC to release the associated dedicated resources. The BSC stops
timer T300.

10
11
12
13
14
15
16
17
18

124

TIA/EIA-2001

e.

BS initiates traffic channel release using existing procedures.

f.

The MS acknowledges the Release message. g.

The BSC then sends an
A9-Release-A8 message, with a Cause value set to Packet call going
Dormant, to the PCF to instruct the PCF to release the associated dedicated
resources, and starts timer Trel9. Note that in this scenario the A10/A11
connection is not released.

h.

The PCF acknowledges the A9-Release-A8 message by returning an A9Release-A8 Complete. The BSC stops timer Trel9

i.

The BSC then returns a Clear Complete message to the MSC. The MSC
releases the underlying transport connection and stops timer T315. Clear
Complete may occur any time after the traffic channel is released.

j.

The MS goes to the dormant state.

3
4
5
6
7
8
9
10
11
12

125

TIA/EIA/IS-2001

1
2
3

2.14.7.4

MS Power Down

This section describes the call flow associated with a packet call release initiated by an MS power
down

MS

BS

MSC/VLR

PCF

PDSN

Release Order

Time

Comment

a
Clear Request

b
T300

Clear Command

c
Release Order

T315

A9-Release-A8

e
A10/A11 Connection
Release Procedure

Trel9

A9-Release-A8 Complete

g
Clear Complete

4
5
6
7

Figure 2-34 - MS Power Down

a.

The MS powers down causing a packet data session to terminate. It sends a

Release Order to the BSC with a power down indication.

b.

The BSC then sends a Clear Request message to the MSC to initiate the call
clear transaction, and starts timer T300.

c.

The MSC starts timer T315 and sends a Clear Command message to the BSC to
instruct the BSC to release the associated dedicated resources. The BSC stops
timer T300.

d.

In response to the Clear Command message, the BSC acknowledges the MS by

sending it a Release Order and releases the radio resource.

e.

The BSC then sends an A9-Release-A8 message with a Cause value set to
Normal Call Release, to the PCF to instruct the PCF to release the associated
dedicated resource, and release the associated A10 connection. The BSC
starts timer Trel9.

f.

The PCF initiates the procedure for releasing the A10/A11 connection. See
Section 2.15.5.6 for details.

g.

The PCF then sends an A9-Release-A8 Complete message to the BS. The BSC
stops timer Trel9. See Section 2.15.5.6 for details.

8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

126

TIA/EIA-2001

1
2
3

h.

The BSC return a Clear Complete message to the MSC. The MSC releases the
underlying transport connection and stops timer T315. Clear Complete may
occur any time after the traffic channel is released.

127

TIA/EIA/IS-2001

2.14.7.5

PDSN Initiated Service Release

This section describes the call flow associated with a packet service release initiated by
PDSN.

2
3

MS

BS

MSC/VLR

PCF

PDSN

A10/A11 Connection
Release Procedure

Time

Comment

A9-Disconnect-A8

b
Tdiscon9

A9-Release-A8

c
Trel9

A9-Release-A8 Complete

Clear Request

e
T300

Clear Command

f
g

TCH
Release

T315

h
Clear Complete

4
5

Figure 2-35 - PDSN Initiated Service Release

a.

When the packet service is released by the PDSN (e.g., because of PPP
termination), the A10/A11 connection is released.

b.

When the PCF recognizes that the A10/A11 connection is released, the PCF
sends an A 9-Disconnect-A8 message to the BSC and starts timer Tdiscon9.

c.

The BSC initiates release of the A8 connection by transmitting an A9-ReleaseA8 message and starts timer Trel9. The PCF stops timer Tdiscon9.

d.

The PCF acknowledges the A9-Release-A8 message by returning an A9Release-A8 Complete. The BSC stops timer Trel9.

e.

The BSC the sends a Clear Request message to the MSC to initiate call clearing
transaction, and starts timer T300.

f.

The MSC starts timer T315 and sends a Clear Command message to the BSC to
instruct the BSC to release the associated dedicated resources. The BSC stops
timer T300.

g.

In response to the Clear Command message, the BSC initiates call clearing over
the air interface by transmitting a Release Order.

21

h.

The MS acknowledges the Release Order by returning a Release Order.

22

i.

The BSC then returns a Clear Complete message to the MSC. The MSC stops
timer T315 and releases the underlying transport connection. Clear Complete
may occur any time after the traffic channel is released.

6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

23
24

128

TIA/EIA-2001

2.14.7.6

MS Initiated Call Re-Activation from Dormant State

Once in the dormant state, a packet data call is reconnected by the MS by including a
packet data call specific service option in an Origination Message with DRS bit set to
1. The PPP and MIP sessions need not be re-established. That is, the A10/A11
connection need not be re-established. In all other respects, this call is no different
than a normal A8 connection setup procedure.

2
3
4
5
6
7

8
9
10
11
12
13
14

2.14.7.7

Network Initiated Call Re-Activation from Dormant State

Once in the dormant state, a packet data call is reconnected by the PCF by sending an
A9-BS Service Request message containing a packet data call specific service option to
the BS. The BS acknowledges the request by sending the A9-BS Service Response
message to the PCF and initiates a normal BS initiated call setup.
This section describes the call flow example associated with the establishment of an A8
connection upon dormant state to active state transition. In this scenario:

16

1) the MS has already performed MIP registration and established a PPP

connection with the PDSN.

17

2) the A8 (User Traffic) connection between the PCF and the BSCdoes not exist.

15

18

129

TIA/EIA/IS-2001

The PDSN sends data packets to the PCF on an existing A10 connection. The following
call flow diagram provides an illustration for a successful packet termination procedure.

1
2
3

MS

PCF

MSC / VLR

BS

PDSN

Time

Dormant, PPP connection is maintained

Packet Data
Traffic

A9-BS Service Request

BS Service Request
T311

Tbsreq9

BS Service Response

Paging Request

Page Response Message

BS Ack Order

c
d

A9-BS Service Response

Page Message

e
f
g

T3113

Complete L3 info:
Paging Response

i
j

T303

Assignment Request

T10
IS-2000 Tch
Setup

l
A9-Setup-A8

TA8-Setup

A9-Connect-A8
Assignment Complete

Active Packet Data Session

4
5
6

Figure 2-36 - Network Initiated Call Re-Activation from Dormant State

130

Comment

TIA/EIA-2001

a.

The PDSN sends data packets to the BSC on an existing PPP connection and
A10/A11 connection associated with a specific mobile for packet service.

b.

The PCF sends an A9-BS Service Request message to the BSC in order to
request packet service, and starts timer Tbsreq9.

c.

The BSC sends a BS Service Request message to the MSC, and starts timer
T311, in order to reconnect the call.

d.

The MSC acknowledges the call setup request by sending a BS Service

Response message to the BS. Upon receipt of the BS Service Response
message from the MSC, the BS stops timer T311.

e.

The BSC responds with A9-BS Service Response. The PCF stops timer
Tbsreq9 upon receipt of the A9-BS Service Response message.

f.

The MSC sends a Paging Request message to establish a mobile terminated

packet data call, and starts timer T3113.

g.

The BS issues a Page message containing the MS address over the paging
channel.

h.

The MS acknowledges the page by transmitting a Page Response message

over the access channel.

i.

The BS constructs the Paging Response message, place it in Complete Layer 3

Information message, sends the message to the MSC, and starts timer T303.
The MSC stops timer T3113 upon receipt of the Paging Response message
from the BS.

j.

The BS acknowledges the receipt of the Page Response message with a BS

Ack order to the MS.

k.

The MSC sends an Assignment Request message to the BS to request

assignment of radio resources and the A8 (User Traffic) connection between
the BSC and the PCF. The MSC then starts timer T10.

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

Upon receipt of the Assignment Request message from the MSC, the BSC
stops timer T303.

27
28
29

l.

30

32

m. The BSC sends A9-Setup-A8 message to the PCF to establish A8 (User

Traffic) connection between the BSC and the PCF, over the A9 (Signaling)
connection. The BSC then starts timer TA8-Setup.

33

n.

The PCF responds with A9-Connect-A8 message to complete the setup of A8

(User Traffic) connection for this packet service request. Upon receipt of the
A9-Connect-A8 message from the PCF, the BSC stops timer TA8-Setup.

o.

After the radio link and the A8 connection have been established, the BS
sends an Assignment Complete message to the MSC. The MSC stops timer
T10.

31

34
35
36
37
38

The BSC and the MS perform radio resources setup procedure.

39

131

TIA/EIA/IS-2001

2.14.7.

Mobile Terminated Packet Data Rejection During a Voice Call

The following call flow diagram provides an illustration for rejection of packet data
termination during a voice call.

2
3
4

MS

BSC

MSC / VLR

PDSN

PCF

Time Comment

Dormant, PPP connection is maintained

voice call
Packet Data
Traffic

A9-BS Service Request

T311

BS Service Request

b
Tbsreq9

BS Service Response

c
d

A9-BS Service Response(Cause: MS Busy)

voice call

Dormant

5
6
7

Figure 2-37 - Mobile Terminated Packet Data Rejection During a Voice Call
a.

It is assumed that the MS has performed MIP registration and established a

PPP connection.,

10

b.

It is assumed that a voice call is currently active.

11

c.

The PDSN sends data packets to the PCF on an existing PPP connection and
A10/A11 connection associated with a specific mobile for packet service.

b.

The PCF sends A9-BS Service Request message to the BSC in order to request
packet service, and starts timer Tbsreq9.

c.

The BS sends a BS Service Request message to the MSC, and starts timer
T311, in order to establish the call.

d.

The MSC sends a BS Service Response message with cause value MS Busy
to the BS. The BS stops timer T311 upon receipt of the BS Service Response
message.

e.

The BSC sends an A9-BS Service Response message to the PCF containing a
the cause value MS Busy. The PCF stops timer Tbsreq9 upon receipt of the
A9-BSC Service Response message and should wait to resend A9-BS Service
Request message. The amount of time to wait to resend is an implementation
issue.

8
9

12
13
14
15
16
17
18
19
20
21
22
23
24

132

TIA/EIA-2001

133

TIA/EIA/IS-2001

1
2
3
4
5
6

2.14.7.9

Dormant Handoff (Inter-BSC/Inter_PCF) - Mobile served by same PDSN

The following call flow diagram provides an illustration for a successful handoff during
Dormant state from source PCF to target PCF. It is assumed that the PCF has only one
Packet Zone ID. The BS will not establish a traffic channel when it receives an
origination with DRS set to 0; a traffic channel may be established after the completion
of setup of the A8 and A10 bearer connections.

7
8

Source
BS

MS

Target
BS

Source
PCF

MSC

Target
PCF

Time
PDSN

Dormant, PPP connection is maintained

Origination Message

BS Ack Order

c
CM Service Req
T303

d
e

Assignment Req
A9-Setup-A8

TA8-setup

T10
PDSN Dormant HO
Procedures 2.16.5.8
A9-Release-A8 Complete

Assignment Failure
T20

h
i

Clear Command

T315

Clear Complete

k
Dormant Packet Data Session

9
10
11
12

Figure 2-38 - Dormant Handoff (Inter-BSC/Inter_PCF) - Mobile served by same PDSN

a.

It is assumed that the MS has performed a MIP registration and

established a PPP connection with PDSN but is now dormant.

b.

The dormant mobile detects a change of Packet Zone ID while monitoring

the broadcast channel and initiates an origination with the DRS bit set to
0.

c.

Target BSC acknowledges the receipt of the Origination message with a

Base Station Ack Order to the MS.

13
14
15
16
17
18

134

Comment

TIA/EIA-2001

d.

Target BSC constructs the CM Service Request message, places it in the

Complete Layer 3 Information message, sends message to the MSC and
starts timer T303.

e.

The MSC sends an Assignment Request message to target BSC to

request assignment of radio resources and starts timer T10. On receipt of
the Assignment Request message, the BSC stops timer T303.

f.

The target BSC sends A9-Setup-A8 message, with Data Ready Indicator
set to 0, to the target PCF and starts timer TA8-setup.

g.

The target PCF establishes the A10/A11 link and the PDSN disconnects
the old A10/A11 link (see procedure in 2.15.5.8). (If the PDSN has data for
the mobile, it responds to the PCF with a Registration Reply message with
the Data Available Indicator in the Vendor/Organization Specific
Extension.)

h.

The PCF responds to the BSC with an A9-Release A8 Complete message.

The BSC stops timer TA8-setup.

2
3
4
5
6
7
8
9
10
11
12
13
14
15

If the PDSN responds to the PCF with a Data Available Indicator, the PCF
responds to the BSC with an A9-Connect-A8 message with Cause element
set to Data Ready to Send. In this case, the BS will establish a traffic
channel and continue as in steps g-j in Figure 2-40. In this case, the
remaining steps in this procedure are omitted.

16
17
18
19
20

i.

The BSC sends the Assignment Failure message to the MSC with Cause
value indicating Packet Call Going Dormant and starts timer T20. The MSC
stops timer T10.

j.

The MSC sends Clear Command to BS with Cause value Do Not Notify
Mobile and starts timer T315. Upon receipt of the Clear Command, the BS
stops timer T20. The BS sends a Clear Complete message to the MSC.

27

k.

The MSC stops timer T315 upon receipt of the Clear Complete message.

28

l.

The packet data session remains dormant

21
22
23
24
25
26

29

30

135

TIA/EIA/IS-2001

2.14.7.10

Dormant Handoff (Inter-BSC/Inter_PCF) - Mobile served by a different PDSN

When an MS in dormant state moves into a different packet zone and ends up being
connected to a different PDSN, Mobile IP Registration is performed.

3
4

MS

BSC

MSC

PCF

PDSN

Origination

BS ACK Order

b
CM Service Request
T303

Assignment Request

d
T10
A9-Setup-A8

TA8-Setup
A9 -Connect-A8

A10/A11
Connection
Establishment
procedure

f
g

Assignment Complete

h
TCH
Establishment
procedure

Establishing PPP connection, Mobile IP Registration

5
6
7
8

Figure 2-39 - Dormant Handoff (Inter-BSC/Inter_PCF) - Mobile served by a different

PDSN

9
10

a.

The dormant mobile detects a change of Packet Zone ID while monitoring the
broadcast channel and initiates an origination with the DRS bit set to 0.

b.

The BSC acknowledges the receipt of the Origination Message with a Base
Station Acknowledgment Order to the MS.

c.

The BSC constructs the CM Service Request message, places it in the

Complete Layer 3 Information message, sends the message to the MSC, and
starts timer T303.

d.

The MSC sends an Assignment Request message to the BSC to request

assignment of radio resources and starts timer T10. For packet data service

11
12
13
14
15
16
17
18

136

TIA/EIA-2001

terrestrial circuit between the MSC and the BSC is not required. The BSC
stops timer T303.

1
2

e.

The BSC transmits an A9-Setup-A8 message to PCF, with DRS=0, to establish

an A8 connection and starts timer TA8-setup.

f.

Procedure for establishing A10/A11 connection is performed.

g.

The BSC initiates the establishment of a radio traffic channel.

h.

Upon establishment of the A10 connection, the PCF establishes A8

connection and transmits an A9-Connect-A8 Message with Traffic Channel
Required indicator set.

i.

Upon receiving an A9-Connect-A8 message, the BSC stops the timer TA8setup. After the radio link is established, the BS sends an Assignment
Complete message to the MSC. The MSC stops timer T10. This step may occur
any time after radio link establishment.

j.

PPP connection establishment procedure and Mobile IP Registration on the

PPP connection are performed between the MS and PDSN.

3
4

8
9
10
11
12
13
14
15
16
17

18
19
20

2.14.7.11

Soft / Softer Handoff

Same procedure as the voice call is applied in this scenario. Please refer to section
3.5.2.3, Soft/softer Handoff Using Direct BS to BS (A3 and A7) Connections.

137

TIA/EIA/IS-2001

2.14.7.12

Inter-BS Hard Handoff (within the same PCF)

The following call flow diagram provides an illustration for a successful hard handoff
event system during packet data services. In order to simplify the diagram, it is assumed
that for purposes of this example, the packet call is not in inter-BS soft/softer handoff
prior to the deactivation, and no other service options are connected.

2
3
4
5

MS

Source BSC

PCF

Target BSC

MSC

Handoff Required

Handoff Request

T7
A9-Setup-A8
TA8-Setup

PDSN Time

A9-Connect-A8

Handoff Request Ack

e
Handoff Command

A9-AL Disconnected
Tald9
GHDM / UHDM

T9

MS Ack Order
x

A9-AL Disconnected Ack

h
i

Twaitho9

Twaitho
Handoff Commenced

Handoff Completion

BS Ack Order

m
A9-AL Connected
T306

Talc9 A9-AL Connected Ack

Handoff Complete

Clear Command

A9-Release-A8
Tre19

T315

A9-Release Complete-A8

r
s

Clear Complete
t
6
7

Figure 2-40 - Inter-BS Hard Handoff (within the same PCF)

138

Comment

TIA/EIA-2001

a.

Based on an MS report that it crossed a network specified threshold for signal

strength or for other reasons, the source BS recommends cdma2000 to
cdma2000 hard handoff to one or more cells in the domain of the target BS. The
source BS sends a Handoff Required message with the list of cells to the MSC
and starts timer T7.

b.

The MSC sends a Handoff Request message to the target BS with hard
handoff indicator.

c.

The target BSC sends an A9-Setup-A8 message to the PCF and starts timer
TA8-Setup, in order to establish the A8-Connection. In this case, the handoff
indicator field of the A9-Setup-A8 message is set to 1 (during handoff).

d.

Upon receipt of the A9-Setup-A8 message from the target BS, the PCF
establishes the A8 connection. At this point of time, the PCF continues to
forward packet data received from PDSN to the source BSC (i.e., The target
BSC doesnt receive packet data from the PCF.). Then the PCF sends the A9Connect-A8 message and starts timer Twaitho9. When the target BSC receives
the A9-Connect-A8 message it stops timer TA8-Setup.

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

The establishment of the A10/A11 connection is not performed because the

handoff indicator field of the A9-Setup-A8 message is set to 1 (during
handoff).

17
18
19
20

e.

The target BSC sends a Handoff Request Acknowledgment message to the

MSC. The target BSC starts timer T9 to wait for arrival of the MS on its radio
channel.

f.

The MSC prepares to switch from the source BSC to the target BSC and sends
a Handoff Command to the source BS. The source BSC stops timer T7.

g.

The PCF stops packet transmission to the source BSC upon receipt of A9AL(Air Link) Disconnected from source BS. At this point in time, the source
BSC starts timer Tald9.

h.

The PCF sends A9-AL(Air Link) Disconnected Ack message in response to

the A9-AL Disconnected message. The BSC stops timer Tald9.

i.

The source BSC sends the General Handoff Direction Message or Universal
Handoff Direction Message to the mobile station across the air interface. If the
MS is allowed to return to the source BS, then timer Twaitho is started by the
source BS.

j.

The MS may acknowledge the General Handoff Direction Message or

Universal Handoff Direction Message by sending a MS Ack Order to the
source BS.

21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

If the General Handoff Direction Message or Universal Handoff Direction

Message is sent using quick repeats, the source BSC might not request an
acknowledgment from theMS .

37
38
39
40

k.

The source BSC sends a Handoff Commenced message to the MSC to notify it
that the MS has been ordered to move to the target BSC channel. The source
BSC starts timer T306 to await the Clear Command message from the MSC. If
timer Twaitho has been started, the source BSC shall wait for that timer to
expire before sending the Handoff Commenced message.

l.

The MS sends a Handoff Completion message to the target BS.

41
42
43
44
45

139

TIA/EIA/IS-2001

m. The target BSC sends the BSC Ack Order to the MS over the air interface.

n.

Upon the receipt of the Handoff Completion message from MS, the target BSC
sends A9-AL(Air Link) Connected message to the PCF and starts timer Talc9.
Then the PCF stops timer Twaitho9, updates its routing table to route packet
data sent from PDSN to the target BSC and restarts packet data transmission to
the target BS. In this case, PCF does not perform the A10/A11 connection
establishment procedure because the A10/A11 connection has already been
established.

o.

The PCF sends the A9-AL(Air Link) Connected Ack as the response of the
A9-AL(Air Link) Connected message and stops timer Talc9. If timer Talc9 is
expired, the target BSC may resend the A9-AL Connect message. However, if
timer T9 had expired before the BSC receives the A9-AL Connect Ack
message, the BSC shall send Handoff Failure message to the MSC. Please refer
to section 3.3.2.7.2, Handoff Failure, for detailed procedure.

p.

The target BSC sends a Handoff Complete message to the MSC to notify it
that the MS has successfully completed the hard handoff. The target BSC
stops timer T9.

q.

The MSC sends a Clear Command to the source BS. The source BSC stops
timer T306. The MSC starts timer T315.

r.

The source BSC sends an A9-Release-A8 message to the PCF in order to

release the A8-Connection and starts timer Tre19.

s.

Upon the receipt of the A9-Release-A8 message from the source BS, the
source PCF releases the A8-Connection and responds with an A9-Release-A8
Complete message. Upon receiving A9-Release-A8 message the source BS
stops timer Tre19.

t.

The source BS sends a Clear Complete message to the MSC to notify it that
clearing has been accomplished. The MSC stops timer T315. Clear Complete
may occur any time after the traffic channel is released.

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

29

140

TIA/EIA-2001

2.14.7.13

Inter-PCF Hard Handoff (Within same PDSN)

The following call flow diagram provides an illustration for a successful hard handoff
event from a cdma2000 system to another cdma2000 system during packet data services.
In order to simplify the diagram, it is assumed that for purposes of this example, the
packet call is not in inter-BS soft/softer handoff prior to the deactivation, and no other
service options are connected.

2
3
4
5
6

MS

Source
PCF

Source BSC

Target
PCF

Target BSC

MSC

PDSN Time

Handoff Required

a
Handoff Request

T7
A9-Setup-A8
TA8-Setup

b
c

A9-Connect-A8

Handoff Request Ack

Handoff Command

A9-AL Disconnected

Tald9 A9-AL Disconnected Ack

GHDM / UHDM

T9

MS Ack Order

Twaitho
Handoff Commenced

Twaitho9

Handoff Completion

BS Ack Order

m
A9-AL Connected
Talc9

PDSN Dormant HO
Procedures 2.15.5.15

T306

A9-AL Connected Ack

Handoff Complete

A9-Release-A8
T315

A9-Release-A8 Complete

s
t

Clear Complete

7
8
9

Clear Command

Tre19

Figure 2-41 - Inter-PCF Hard Handoff (Within same PDSN)

141

Comment

TIA/EIA/IS-2001

a.

Based on an MS report that it crossed a network specified threshold for signal

strength or for other reasons, the source BSC recommends cdma2000 to
cdma2000 hard handoff to one or more cells in the domain of the target BSC.
The source BSC sends a Handoff Required message with the list of cells to the
MSC and starts timer T7.

b.

The MSC sends a Handoff Request message to the target BSC with hard
handoff indicator (e.g., Handoff Type element in the message indicating hard
handoff).

c.

The target BSC sends an A9-Setup-A8 message to the target PCF in order to
establish the A8-Connection and sets timer TA8-Setup. In this case, the
handoff indicator field of the A9-Setup-A8 message is set to 1 (during
handoff).

d.

Upon receipt of the A9-Setup-A8 message from the target BSC, the target PCF
establishes the A8-Connection. At this point of time, PDSN continues to
forward packet data to the source BSC via source PCF. (I.e., The target BSC
and target PCF dont receive packet data from the PDSN.). Then the target PCF
sends the A9-Connect-A8 message and starts timer Twaitho9. When the
source BSC receives the A9-Connect-A8 message it stops timer TA8-Setup.

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

The establishment of the A10/A11 connection is not performed because the

handoff indicator field of the A9-Setup-A8 message is set to 1 (during
handoff).

19
20
21
22

e.

The target BSC sends a Handoff Request Acknowledgment message to the

MSC. The target BSC starts timer T9 to wait for arrival of the MS on its radio
channel.

f.

The MSC prepares to switch from the source BSC to the target BSC and sends
a Handoff Command to the source BSC. The source BSC stops timer T7.

g.

The PCF stops packet transmission to the source BSC upon receipt of A9AL(Air Link) Disconnected from the source BSC. At this point of time, the
source BSC starts timer Tald9.

h.

The PCF sends A9-AL Disconnected Ack message as response of A9-AL(Air

Link) Disconnected message. The BSC stops timer Tald9.

i.

The source BSC sends the General Handoff Direction Message or Universal
Handoff Direction Message to the mobile station across the air interface. If the
MS is allowed to return to the source BSC, then timer Twaitho is started by the
source BSC.

j.

The MS may acknowledge the General Handoff Direction Message or

Universal Handoff Direction Message by sending a MS Ack Order to the
source BSC.
If the General Handoff Direction Message or Universal
Handoff Direction Message is sent using quick repeats, the source BSC might
not request an acknowledgment from the MS .

k.

The source BSC sends a Handoff Commenced message to the MSC to notify it
that the MS has been ordered to move to the target BSC channel. The source
BSC starts timer T306 to await the Clear Command message from the MSC. If
timer Twaitho has been started, the source BSC shall wait for that timer to
expire before sending the Handoff Commenced message.

l.

The MS sends a Handoff Completion Message to the target BSC.

23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

142

TIA/EIA-2001

m. The target BSC sends the BSC Ack Order to the MS over the air interface.

n.

Upon the receipt of the Handoff Completion message from the MS, the target
BSC sends A9-AL(Air Link) Connected message to the target PCF and starts
timer Talc9. The target PCF stops timer Twaitho9.

o.

The target PCF establishes the A10/A11 link and the PDSN disconnects the
old A10/A11 link (see procedure in . 2.15.5.10).

p.

The target PCF sends the A9-AL(Air Link)Connected Ack as the response of
the A9-AL(Air Link) Connected message and stops timer Talc9. If timer Talc9
is expired, the target BSC may resend the A9-AL Connect message. However,
if timer T9 had expired before the BSC receives the A9-AL Connect Ack
message, the BSC shall send Handoff Failure message to the MSC. Please refer
to section 3.3.2.7.2, Handoff Failure, for detail procedure.

q.

The target BSC sends a Handoff Complete message to the MSC to notify it
that the MS has successfully completed the hard handoff. The target BSC
stops timer T9.

r.

The MSC sends a Clear Command to the source BSC. The source BSC stops
timer T306. The MSC starts timer T315.

s.

The source BSC sends a A9-Release-A8 message to the source PCF in order to
release the A8-Connection and starts timer Tre19.

t.

Upon the receipt of the A9-Release-A8 message from the source BSC, the
source PCF releases the A8-Connection and responds with a A9-Release-A8
Complete message. When the source BSC receives the A9-Release-A8
Complete message it stops timer Tre19.

u.

The source BSC sends a Clear Complete message to the MSC to notify it that
clearing has been accomplished. The MSC stops timer T315. Clear Complete
may occur any time after the traffic channel is released.

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

143

TIA/EIA/IS-2001

2.14.7.14

Inter-PCF Hard Handoff (Within same PDSN) With Return On Failure

The following call flow diagram provides an illustration for a hard handoff event from a
cdma2000 system to another cdma2000 system. In this scenario, the mobile station
successfully returns to the source BSC after hard handoff fails. It is assumed that the
call is not in inter-BSC soft/softer handoff prior to the hard handoff, and thus no interBSC connections need to be removed.

2
3
4
5
6

MS

Source
PCF

Source BS

Target
PCF

Target BS

MSC

Handoff Required
T7
A 9-Setup-A8
TA8-Setup

A9-Connect-A8
Handoff Request Ack

Handoff Command

b
c
d
e
f

A9-AL Disconnected

Tald9 A9-AL Disconnected Ack

GHDM / UHDM

h
T9

Twaitho9

MS Ack Order

i
j

Twaitho
k
A9-AL Connected

Talc9

Comment

a
Handoff Request

CF Search Report
Message

P D S N Time

A9-AL Connected Ack

Handoff Failure

n
Clear Command
A 9-Release-A8
Tre19

T315
A9-Release-A8 Complete

o
p
q

Clear Complete

7
8
9

Figure 2-42 - Inter-PCF Hard Handoff (Within same PDSN) With Return On Failure

144

TIA/EIA-2001

a.

Based on an MS report that it crossed a network specified threshold for signal

strength or for other reasons, the source BSC recommends cdma2000 to
cdma2000 hard handoff to one or more cells in the domain of the target BSC.
The source BSC sends a Handoff Required message with the list of cells to the
MSC and starts timer T7.

b.

The MSC sends a Handoff Request message to the target BSC with hard
handoff indicator (e.g., Handoff Type element in the message indicating hard
handoff).

c.

The target BSC sends an A9-Setup-A8 message to the target PCF in order to
establish the A8-Connection and sets timer TA8-Setup. In this case, the
handoff indicator field of the A9-Setup-A8 message is set to 1 (during
handoff).

d.

Upon receipt of the A9-Setup-A8 message from the target BSC, the target PCF
establishes the A8-Connection. At this point of time, PDSN continues to
forward packet data to the source BSC via source PCF. (I.e., The target BSC
and target PCF dont receive packet data from the PDSN.). Then the target PCF
sends the A9-Connect-A8 message. When the target BSC receives the A9Connect-A8 message it stops timer TA8-Setup.

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

The establishment of the A10/A11 connection is not performed because the

handoff indicator field of the A9-Setup-A8 message is set to 1 (during
handoff).

19
20
21
22

e.

The target BSC sends a Handoff Request Acknowledgment message to the

MSC. The target BSC starts timer T9 to wait for arrival of the MS on its radio
channel.

f.

The MSC prepares to switch from the source BSC to the target BSC and sends
a Handoff Command to the source BSC. The source BSC stops timer T7.

g.

Upon receipt of the Handoff Command message, the source BSC sends an A9AL(Air Link) Disconnected message to the source PCF and starts timer Tald9.
The source PCF stops packet data transmission to the source BSC upon
receipt of the A9-AL(Air Link) Disconnected from the source BSC.

h.

The PCF sends the A9-AL(Air Link) Disconnected Ack message as response
of the A9-AL(Air Link) Disconnected message. Upon receipt of this message,
the source BSC stops timer Tald9.

i.

The source BSC sends the General Handoff Direction Message or Universal
Handoff Direction Message to the mobile station across the air interface. If the
MS is allowed to return to the source BSC, then timer Twaitho is started by the
source BSC.

j.

The MS may acknowledge the General Handoff Direction Message or

Universal Handoff Direction Message by sending a MS Ack Order to the
source BSC.

23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

If the General Handoff Direction Message or Universal Handoff Direction

Message is sent using quick repeats, the source BSC might not request an
acknowledgment from theMS.

41
42
43
44

k.

The MS sends a Candidate Frequency (CF) Search Report Message to the

source BSC after handoff to the target has failed.

l.

If the handoff fails (i.e., when the BSC receives the CF Search Report
Message), the source BSC sends the A9-AL(Air Link) Connected message to
the source PCF and starts timer Talc9.

45
46
47
48

145

TIA/EIA/IS-2001

m. The source PCF restarts packet data transmission upon receipt of the A9AL(Air Link) Connected message from the source BSC. The source BSC stops
timer Talc9.

n.

Upon receipt of the CF Search Report Message from the MS the source BSC
detects that the MS has never accessed the target BSC cell and sends a
Handoff Failure message to the MSC indicating the unsuccessful access by
the MS.

o.

The MSC sends a Clear Command to the target BSC. The target BSC stops
timer T9. The MSC starts timer T315.

p.

The BSC sends an A9-Release-A8 message to the target PCF in order to

instruct it to release the associated dedicated resources and starts timer Tre19.

q.

Upon the receipt of the A9-Release-A8 message from the target BSC, the target
PCF releases resources and responds with an A9-Release-A8 Complete
message. When the target BSC receives the A9-Release-A8 Complete message
it stops timer Tre19.

r.

Upon receipt of the Clear Command message from the MSC, the target BSC
releases and deallocates radio and terrestrial resources.

s.

The target BSC then sends a Clear Complete message to the MSC. The MSC
stops timer T315.

1
2

5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

146

TIA/EIA-2001

2
3
4

2.15

A10/A11 Interface Procedures

A10/A11 interface uses Mobile IP messages for managing the A10 connections. The
following sections describe the messages and procedures for the A10/A11 interfaces.
The sections are as follows;

A10 Connection Setup Procedures,

A10 Connection Re-Registration Procedures,

A10 Connection Release Procedures,

A10 Connection Accounting Procedures, and

A10/A11 Interface Call Flows

10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

The mobile subscriber initiates a packet data call by sending an IS-2000 Origination
Message. Normal voice service authentication procedures are followed for the
subscriber, and then a traffic channel is established with the mobile. After connection of
a packet data service option, RLP synchronization between the mobile station and the
BS proceeds. The BS/PCF initiates setup of an A10 connection with the PDSN by
sending a Registration Request message on the A11 interface. The PDSN may accept or
reject the connection setup request. If the connection setup request is acceptable, the
PDSN returns a Registration Reply message with an accept indication, and the packet
data call is connected through the just established A10 connection.
With the A10 connection in place, link layer/network layer frames pass over this
connection in both directions via GRE framing. The PDSN accepts these frames, strips
the GRE, and processes them as normal incoming frames for the appropriate interface
and protocol. The other direction behaves analogously, with the PDSN encapsulating
the link layer/network layer frames in GRE, and the PCF stripping the GRE before
passing the frames over to the upper layer. At this point, there is a point-to-point link
layer/network layer connection between the mobile user and the PDSN.
In order to setup an A10 connection, the PCF assigns a PCF Session Identifier (PSI) to
the packet data bearer. The Mobile PCF Session Identifier (PSI) is unique only within
the PCF entity. The PCF will also use the MN Session Reference ID (MN-SRID) which is
passed from the mobile on each origination and which, together with the Mobile
Identifier, can be used to identify a packet data service session for a specific mobile
across PCFs and PDSNs. In the Registration Request message, the PCF sets the Home
Address field to zeros. The IP source address (IP header) and the Care-of-Address field
of the Registration Request message are set to the IP address of the PCF. The IP
destination address in the IP header and the Home Agent field in the Registration
Request are set to the address of the PDSN designated for the call. The PCF Session
Identifier (PSI), link layer/network layer protocol type identifier, MN Session Reference
ID and IMSI address of the mobile subscriber are set in the Session Specific Extension
of the Registration Request message.
The A10 bearer connection is used for the transport of user data for a packet data
session. Link layer/network layer frames are carried between the PCF and the PDSN
encapsulated in GRE packets, which in turn are carried over IP. The PCF-Address and
the PDSN-Address are used in the source address and destination address fields of the
IP header used with the GRE packet. The Key field in the GRE header contains the PCF
Session Identifier (PSI), and indicates which packet data bearer connection a particular
payload packet belongs to.
The A11 signaling messages Registration Request and Registration Reply are defined
by RFC 2002 with extension elements defined in this standard. The Registration Update

147

TIA/EIA/IS-2001

and Registration Acknowledge messages are defined in this standard. The procedures
for the use of these messages are defined in this standard.

1
2
3

2.15.1

A10 Interface Setup Procedures

2.15.1.1

A10 Connection Establishment

The A11 Registration Request message is sent from the PCF to the PDSN for setting up
an A10 connection.

7
8

2.15.1.1.1

Successful Operation
When the BS receives an Assignment Request with a Service Option that requests
packet data service from the MSC, it initiates the procedure for establishing radio traffic
channels. After traffic channels are established, the BS/PCF initiates procedures for
establishing an A10 connection.

10
11
12
13

The PCF initiates setup of an A10 connection by sending a Registration Request

message to the PDSN and starts timer Tregreq. The Registration Request message is
structured as specified in RFC 2002 and contains the extensions specified in this
standard. The Registration Request message may be retransmitted a configurable
number of times as specified in RFC 2002. If the connection setup request is acceptable,
the PDSN updates its binding record for the A10 connection by creating an association
between the IMSI address and the PCF Session Identifier, PCF-Address and PDSNAddress information. It then returns a Registration Reply with an accept indication,
including the configured Lifetime (Trp) for the A10 connection. The packet data call is
connected through the just established A10 connection.

14
15
16
17
18
19
20
21
22
23

The PCF and the PDSN use the PCF-IP-Address and the PDSN-IP-Address returned in
the Registration Reply message as the A10 connection for the transport of user traffic.
The PCF-IP-Address and the PDSN-IP-Address form the unique link layer ID for each
A10 connection. The PCF and the PDSN maintain an association of the mobiles IMSI
address with the A10 connection.

24
25
26
27
28

The PCF and the PDSN use the PCF-Address and the PDSN-Address returned in the
Registration Reply message as the A10 connection for the transport of user traffic. The
PSI, PCF-Address and the PDSN-Address form the unique link layer ID for each A10
connection. The PCF and the PDSN maintain an association of the mobiles IMSI
address with link layer ID over the A10 connection.

29
30
31
32
33

Please refer to RFC 2002 and section 6.1.11.1 Registration Request for the format and
content of the Registration Request message.

34
35
36

37
38
39
40
41
42
43
44
45

2.15.1.1.2

Failure Operation
The PCF initiates setup of an A10 connection by sending an A11-Registration Request
message to a selected PDSN. If the selected PDSN does not accept the connection, it
returns an A11-Registration Reply with a reject result code.
The PDSN may return an A11-Registration Reply message with result code 88H
(Registration Denied unknown PDSN address). When code 88H is used, an alternate
PDSN address is included in the A11-Registration Reply message. The address of the
alternate proposed PDSN shall be returned in the Home Agent field of the A11Registration Reply message.
148

TIA/EIA-2001

1
2
3
4
5
6
7
8
9
10
11
12
13

On receipt of a A11-Registration Reply with code 136, the PCF shall either initiate
establishment of the A10 connection with the proposed PDSN by sending a new A11Registration Request message as indicated in this section, or shall use internal
algorithms to select a new PDSN.
On receipt of a A11-Registration Reply with another result code, depending on the
result code, the PCF may attempt to re-try setting up the A10 connection. If the A10
connection can not be established, the PCF indicates this to the BSC, which returns a
failure indication to the MSC, which in-turn releases the call.
Reliable message delivery mechanisms are used for setting up the A10 connection
between the PCF and the PDSN. As specified in RFC 2002, the A11-Registration
Request message may be retransmitted if no A11-Registration Reply is received within a
configurable time. A call is considered to have failed if no A11-Registration Reply is
received after a configurable number of A11-Registration Request retransmissions.

149

TIA/EIA/IS-2001

2.15.2

A10 Interface Operational Procedures

2.15.2.1

A10 Connection Periodic Re-registration

The PCF periodically refreshes the A10 connection with the PDSN by sending a A11Registration Request message.

4
5

Please refer to Section 6.1.11.1, A11-Registration Request, for the format and content
of this message.

6
7

2.15.2.1.1

The PCF periodically refreshes the A10 connection with the PDSN by sending a A11Registration Request message before A10 connection registration Lifetime (Trp) expires,
as per procedures specified in RFC 2002. The PDSN returns A11-Registration Reply
with an accept indication, including the refreshed Lifetime timer value for the A10
connection.

9
10
11
12
13

14

Successful Operation

2.15.2.1.2

Failure Operation
Reliable message delivery mechanisms are used for setting up the A10 connection
between the PCF and the PDSN. As specified in RFC 2002, the A11-Registration Request
message may be retransmitted if no A11-Registration Reply is received within a
configurable time. A call is considered.failed if no A11-Registration Reply is received after
a configurable number of A11-Registration Request retransmissions. If the authentication
failed at registration reply during re-registration, the A10 connection is released at the
complete expiration of the lifetime.

15
16
17
18
19
20
21

If identification mismatch is detected in the registration reply at re-registration, the A10

connection is released at the complete expiration of the lifetime.

22
23
24

25

2.15.3

The release of an A10 connection is controlled by the PCF. For PDSN initiated A10
connection release, the PDSN requests that the PCF release the connection. The BSC
would release the traffic channel(s) accordingly.

26
27
28

29

2.15.3.1

31

Please refer to Section 6.1.11.1, A11-Registration Request, for the format and content
of this message.

32
33

35
36
37
38
39
40
41

A10 Connection Release PCF Requested

The PCF may initiate release of the A10 connection by sending a A11-Registration
Request message to the PDSN with Lifetime field set to zero.

30

34

A10 Interface Release Procedures

2.15.3.1.1

Successful Operation
The PCF may initiate release of the A10 connection by sending a A11-Registration
Request message to the PDSN with Lifetime field set to zero. The PCF includes the
accounting related and other information also in the A11-Registration Request. For
successful operation, the PDSN removes the binding information for the A10
connection, saves the accounting related and other information for further processing,
and returns a A11-Registration Reply with accept indication. On receipt of the A11Registration Reply, the PCF also removes binding information for the A10 connection.
150

TIA/EIA-2001

151

TIA/EIA/IS-2001

2.15.3.1.2

Failure Operation
On failure to receive A11-Registration Reply in response to a configurable number of
A11-Registration Request retransmissions, the PCF removes the binding information for
the A10 connection.

2
3
4
5

When the PDSN receives a A11-Registration Request with a Vendor/Organization

Specific Extension and recognizes it, but the extension contains an
unknown/unsupported Vendor ID or or the PDSN does not know how to interpret the
Application Group, Application Sub Type or Application Data, a A11-Registration
Reply is sent with the reject error code 8DH (Registration Denied unsupported
Vendor ID or unable to interpret the data) indicating that the registration was rejected.

6
7
8
9
10
11

Please refer to Section 6.1.11.2, A11-Registration Reply, for the format and content of
this message.

12
13

14

2.15.3.2

The PDSN may initiate release of an A10 connection by sending a A11-Registration

Update message to the PCF.

15
16

In the case of a PDSN initiated release of the A10 connection, the PCF indicates this to
the BSC, in this release, which returns an indication to the MSC .

17
18

Please refer to Section 6.1.11.3, A11-Registration Update, for the format and content
of this message.

19
20

21

2.15.3.2.1

23
24
25
26
27
28
29
30
31
32
33

35
36
37
38
39
40
41
42
43

Successful Operation
The PDSN may initiate release of an A10 connection by sending a A11-Registration
Update message to the PCF. The Home Agent field in the A11-Registration Update is
the PDSN-Address and the Home Address is set to zeros. Care-of-Address field
contains the PCF-Address. The PCF Session Identifier and other session specific
information is sent within the Session Specific extension. . For successful operation, the
PCF returns a A11-Registration Acknowledge with an accept indication. The PCF then
sends the accounting related and other information to the PDSN within the
Vendor/Organization Specific Extension in a A11-Registration Request message with
Lifetime set to zero (0). The PDSN responds with A11-Registration Reply with an accept
indication and saves the accounting related and other information for further
processing. At this time, both the PCF and the PDSN remove the binding information
for the A10 connection.

22

34

A10 Connection Release PDSN Initiated

2.15.3.2.2

Failure Operation
On failure to receive a A11-Registration Acknowledge or a A11-Registration Request
(with accounting related information and Lifetime set to zero) in response to a
configurable number of A11-Registration Update retransmissions or on receiving a A11
registration acknowledge with an update denied status, the PDSN removes the binding
information for the A10 connection.
When PCF returns Registration denied, the PDSN may send a new registration update
at a configurable number of time.
On the release of the A10 connection, the PCF indicates this to the BSC, which returns
an indication to the MSC (if required), which in-turn initiates release of the call.

152

TIA/EIA-2001

1
2

Please refer to Section 6.1.11.4, A11-Registration Acknowledge, for the format and
content of this message.

153

TIA/EIA/IS-2001

2.15.4

A10 Interface Packet Accounting Procedures

The PCF uses the A11-Registration Request message to send accounting related and
other information to the PDSN. The accounting related information is accumulated at
the PCF and sent to the PDSN on occurrence of pre-defined triggers, which are listed in
Table 2-3 below. The occurrence of these predefined triggers is fully specified in
TIA/EIA/IS-835.The A10 connection binding information at the PDSN and the PCF may
also be updated appropriately depending on the setting of the Lifetime field.

Table 2- 3 - Accounting Records Generated By The PCF

2
3
4
5
6

Airlink
Record ID
Y1=1

Connection Setup: Setup of A10 connection initiated.

Y1=2

Active Start: Mobile comes on the traffic channel(s).

Y1=3

Active Stop: Mobile has stopped use of traffic channel(s).

Y1=4

A forward or reverse short data burst (SDB) was exchanged

with the mobile.

If some airlink parameters for an active session change, the PCF generates an Active
Stop (Y1=34) accounting record followed by an Active Start (Y1=2) accounting
record. For successful operation, the PDSN saves the accounting related and other
information for further processing, and responds with A11-Registration Reply with an
accept indication.

9
10
11
12
13

14

Accounting Records Generated By The PCF

2.15.5

A10/A11 Interface Call Flows

2.15.5.1

Mobile Originated Packet Call Setup Successful Operation

15

16
17
18
19
20
21
22
23
24
25

In order to obtain packet data services, the mobile performs registration with the serving
wireless network and then with the packet network. The mobile sends an Origination
Message to the BS that includes the packet data service option. It results in assignment
of the traffic channel, establishment of the A10 connection, establishment of the link
layer (PPP) and for the case where Mobile IP is used by the terminal, Mobile IP
registration with the serving packet network.
User data traffic can now be passed over the A10 connection encapsulated within GRE
frames. The PCF periodically re-registers with the selected PDSN by the use of A11Registration Request message before the A10 connection Lifetime expires.

26
27

154

TIA/EIA-2001

time
MS

BSC/PCF

MSC

Origination
Message
Base Station Ack Order

a
b

Complete L3 Info: CM Service Request

T303

comment

PDSN

Assignment Request

T10

TCH Setup

Tregreq

A11-Registration Request (Lifetime)

A11-Registration Reply (Lifetime, Accept)

Assignment Complete

Establish PPP Connection

Mobile IP Registration

Trp

User Data Transmission

A11-Registration Request (Lifetime, Accounting Data)

Tregreq

A11-Registration Reply (Lifetime, accept)

k
l

1
2

Figure 2-43 - Mobile Originated Packet Call Setup Successful Operation

155

TIA/EIA/IS-2001

Note: The following descriptions assume that the PCF is capable of determining
whether one or more PDSNs is reachableon the A10/A11 Network. Based on
internal algorithms, the PCF selects a PDSN best suited for handling this call.

a.

In order to perform registration for packet data services, the mobile sends an
Origination Message with Layer2 Ack required indication over the Access
Channel to the BS. The Origination Message includes a packet data service
option.

b.

The BS acknowledges the receipt of the Origination Message with a Base

Station Ack Order to the mobile.

c.

The BS constructs a CM Service Request message, places it in the Complete

Layer 3 Information message, sends the message to the MSC, and starts timer
T303.

d.

The MSC sends an Assignment Request message to the BS requesting

assignment of radio resources and starts timer T10. No terrestrial circuit
between the MSC and the BS is assigned to the packet data call.

e.

On receipt of the Assignment Request message, the BS stops timer T303. The
BS and the mobile perform radio resources setup procedures if the mobile is
not already on a traffic channel

f.

The PCF recognizes that no A10 connection associated with this mobile is
available and selects a PDSN for this call. The PCF sends a A11-Registration
Request message to the selected PDSN. The PCF starts timer Tregreq.

g.

The A11-Registration Request is validated and the PDSN accepts the

connection by returning a A11-Registration Reply message with an accept
indication and the Lifetime set to the configured Trp value. Both the PDSN and
the PCF create a binding record for the A10 connection. The PCF stops timer
Tregreq.

h.

After the radio link and A10connection are setup, the BS sends Assignment
Complete message to the MSC. The MSC stops timer T10 upon receipt of the
Assignment Complete message from the BS.

i.

The mobile and the PDSN establish the link layer (PPP) connection and then
perform the MIP registration procedures over the link layer (PPP) connection,
thereby creating a Layer3 Visitor List binding for the mobile.

j.

After completion of MIP registration, the mobile can send/receive data via GRE
framing over the A10 connection.

k.

The PCF sends A11-Registration Request message before expiry of

registration Lifetime timer (Trp) for refreshing registration for the A10
connection. A11-Registration Request message may also be used to send
accounting related and other information to the PDSN. The accounting related
and other information is sent at system defined trigger points. The PCF starts
timer Tregreq.

l.

For a validated A11-Registration Request, the PDSN returns a A11Registration Reply message with an accept indication and a configured
Lifetime value. Both the PDSN and the PCF update the A10 connection
binding record. The PDSN stores the accounting related and other information
(if received) for further processing, before returning the A11-Registration
Reply. The PCF stops timer Tregreq.

1
2

5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

156

TIA/EIA-2001

2.15.5.2

Mobile Originated Packet Call Setup Failure Operation

In order to obtain packet data services, the mobile performs registration with the serving
wireless network and then with the packet network. The mobile sends an Origination
Message to the BSC that includes the packet data service option. It results in
assignment of the traffic channel. The PCF initiates establishment of the A10
connection with the PDSN by sending a A11-Registration Request to the PDSN. If the
connection setup request is not acceptable, the PDSN returns a A11-Registration Reply
with a reject code. Based on the reject code, the PCF may attempt to re-try setting up
the A10 connection. If the A10 connection is not able to be established, the PCF
indicates this to the BSC which returns a failure indication to the MSC, which in-turn
releases the call.

2
3
4
5
6
7
8
9
10
11

time
MS

BSC/PCF

MSC

PDSN

Origination
Message
Base Station Ack Order

a
b

Complete L3 Info: CM Service Request

T303

Assignment Request
T10

TCH Setup
A11-Registration Request (Lifetime)
Tregreq

A11-Registration Reply (Lifetime, reject)

c
d
e
f
g
h

Assignment Failure
Clear Command
Release Order

i
j

Clear Complete

12
13
14

Figure 2-44 - Mobile Originated Packet Call Setup Failure Operation

157

comment

TIA/EIA/IS-2001

Note: The following descriptions assume that the PCF is capable of determining
reachability to one or more PDSNs on the A10/A11 Network. Based on internal
algorithms, the PCF selects a PDSN best suited for handling this call.

a.

In order to perform A11-Registration for packet data services, the mobile sends
an Origination Message with Layer2 Ack required indication over the Access
Channel to the BS. The Origination Message includes a packet data service
option.

b.

The BS acknowledges the receipt of the Origination Message with a Base

Station Ack Order to the mobile.

c.

The BS constructs a CM Service Request message, places it in the Complete

Layer 3 Information message, sends the message to the MSC, and starts timer
T303.

d.

The MSC sends an Assignment Request message to the BS requesting

assignment of radio resources and starts timer T10. No terrestrial circuit
between the MSC and the BS is assigned to the packet data call.

e.

On receipt of the Assignment Request message, the BS stops timer T303. The
BS and the mobile perform radio resources setup procedures if the mobile is
not already on a traffic channel at end of line.

f.

The PCF recognizes that no A10 connection associated with this mobile is
available and selects a PDSN for this call. The PCF sends a A11-Registration
Request message to the selected PDSN. The PCF starts timer Tregreq.

g.

The PDSN does not accept the A11-Registration Request and fails A10
connection setup by returning a A11-Registration Reply message with a reject
code. The PCF stops timer Tregreq.

h.

Based on the reject code, the PCF may attempt to re-try setting up the A10
connection. If the A10 connection can not be established, the BSC returns an
Assignment Failure with cause PDSN resource unavailable to the MSC.

i.

The MSC sends a Clear Command message to the BS, instructing the BS to
release the associated resources, including the radio resources.

j.

The BS sends a Release Order to the mobile instructing the mobile to release
the radio resources.

k.

The BS returns a Clear Complete message to the MSC.

1
2

5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

Note: If the BSC has already returned an Assignment Complete message to the
MSC prior to receiving a A11-Registration Reply with a reject code from the
PDSN, the BSC initiates release of the call by sending a Clear Request with
Cause (PDSN Resource Unavailable) to the MSC.

38
39

158

TIA/EIA-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14

2.15.5.3

Mobile Originated Packet Call Setup With registration to alternate PDSN

In order to obtain packet data services, the mobile performs registration with the serving
wireless network and then with the packet network. The mobile sends an Origination
Message to the BSC that includes the packet data service option. It results in
assignment of the traffic channel. The PCF initiates establishment of the A10
connection with the selected PDSN by sending a A11-A11-Registration Request
message. If the PDSN does not accept the connection and wants to propose another
PDSN, it returns A11-Registration Reply message with code 88H (Registration Denied
unknown PDSN address). The address of the alternate PDSN is also returned in the
Home Agent field of the A11-Registration Reply message. The PCF may initiate setup of
the A10 connection with the alternate PDSN by sending another A11-Registration
Request message, or may use internal algorithms to select a new PDSN.The PCF
initiates establishment of the A10 connection with the selected PDSN by sending a
A11-Registration Request messageor may use internal algorithms to select a new PDSN.

time
MS

BSC/PCF

MSC

PDSN-1

PDSN-2

Origination Message
a
Base Station Ack Order

Complete L3 Info: CM Service Request

T303

Assignment Request

TCH Setup

T10

e
A11-Registration Request (Lifetime)

A11-Registration Reply (Cause=Denied)

Treqreq

A11-Registration Request (Lifetime)

A11-Registration
Reply
(LifeTime,
Accept)
A11-Registration Reply
(Lifetime,
Reject)

i
j

Assignment Complete

Establish PPP Connection

Mobile IP Registration

User Data Transmission

Trp

A11-Registration Request (Lifetime, Accounting Data)

Tregreq

A11-Registration Reply (LifeTime, Accept)

15
16
17
18

Figure 2-45 - Mobile Originated Packet Call Setup With registration to alternate
PDSNNote: The following descriptions assume that the PCF is capable of determining

159

comment

TIA/EIA/IS-2001

1
2
3

reachability to one or more PDSNs on the A10/A11 Network. Based on internal

algorithms, the PCF selects a PDSN best suited for handling this call.
a.

In order to perform registration for packet data services, the mobile sends an
Origination Message with Layer2 Ack required indication over the Access
Channel to the BS. The Origination Message includes a packet data service
option.

b.

The BS acknowledges the receipt of the Origination Message with a Base

Station Ack Order to the mobile.

4
5
6
7
8

11

sc. The BS constructs a CM Service Request message, places it in the Complete

Layer 3 Information message, sends the message to the MSC, and starts timer
T303.

12

d.

The MSC sends an Assignment Request message to the BS requesting

assignment of radio resources and starts timer T10. No terrestrial circuit
between the MSC and the BS is assigned to the packet data call.

e.

On receipt of the Assignment Request message, the BS stops timer T303. The
BS and the mobile perform radio resources setup procedures if the mobile is
not already on a traffic channel at end of line.

f.

The PCF recognizes that no A10 connection associated with this mobile is
available and selects a PDSN (PDSN-1) for this call. The PCF sends a A11Registration Request message to the selected PDSN-1. The PCF starts timer
Tregreq.

g.

The A11-Registration Request is validated and the PDSN-1 rejects the

connection and may proposes another PDSN (PDSN-T). The PDSN-1 returns a
A11-Registration Reply message with a reject code of 88H(Registration
Denied unknown PDSN address) and the address of the alternate PDSN
(PDSN-2) in the Home Agent address field of the A11-Registration Reply
message. The PCF stops timer Tregreq.

h.

The PCF initiates establishment of the A10 connection with the PDSN-T by
sending a A11-Registration Request message. The PCF starts timer Tregreq.

i.

The A11-Registration Request is validated and the PDSN-T accepts the

connection by returning a A11-Registration Reply message with an accept
indication and the Lifetime set to the configured Trp value. Both the PDSN-T
and the PCF create a binding record for the A10 connection. The PCF stops
timer Tregreq.

j.

After the radio link and the A10 connection have been established, the BS
sends an Assignment Complete message to the MSC. The MSC stops timer
T10. This step may occur any time after radio link establishment.

k.

The mobile and the PDSN-T establish the link layer (PPP) connection and then
perform the MIP registration procedures over the link layer (PPP) connection,
thereby creating a Layer3 Visitor List binding for the mobile.

l.

After completion of MIP registration, the mobile can send/receive data via GRE
frames over the A10 connection.

9
10

13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

m. The PCF sends A11-Registration Request message before expiry of

registration Lifetime timer (Trp) for refreshing registration for the A10
connection with PDSN-T.An A11-Registration Request message is also used
to send accounting related and other information to PDSN T . The accounting
related and other information is sent at system defined trigger points. The PCF
starts timer Tregreq.
160

TIA/EIA-2001

1
2
3
4
5
6

7
8
9

n.

For a validated A11-Registration Request, the PDSN-T returns a A11Registration Reply message with an accept indication and a configured
Lifetime value. Both the PDSN-T and the PCF update the A10 connection
binding record. The PDSN-T stores the accounting related and other
information (if received) for further processing, before returning the A11Registration Reply. The PCF stops timer Tregreq.

Note: The PCF continues to perform re-registration of the A10 connection with the PDSN-T by the
exchange of A11-Registration Request and A11-Registration Reply messages before expiry of Lifetime
timer
Trp.

161

TIA/EIA/IS-2001

2
3
4
5
6
7
8

2.15.5.4

Packet Data Service Session Clearing-PDSN Initiated

User data traffic is passed over the A10 connection, encapsulated within GRE frames.
An event occurs at the PDSN that requires closing of the packet data session. The
PDSN initiates closure of the A10 connection with the PCF. If the mobile is on a traffic
channel, other resources assigned to the call are also released.
PDSN initiated service session clearing may occur, for example due to PPP timeout. For
such cases a traffic channel may not exist, and this scenario terminates at step d.

9
10

time
MS

BSC/PCF

MSC

PDSN

A11-Registration Update
a
A11-Registration Acknowledgement

Tregupd
b

A11-Registration Request (lifetime=0,Accounting Data)

c
Tregreq

A11-Registration Reply (Lifetime=0, accept)

d
Clear Request

T300

Clear Command

TCH Release

f
T315

Clear Complete

g
h

11
12
13

Figure 2-46 - Packet Data Service Session Clearing-PDSN Initiated

14
15

a.

An event occurs at the PDSN that requires closure of the packet data session.
The PDSN initiates closure of the A10 connection by sending a A11Registration Update message to the PCF. The PCF starts timer Tregupd.

b.

The PCF responds with a A11-Registration Acknowledge message. Steps c

through d may occur in parallel with steps e through g. The PCF stops
timer Tregupd.

c.

The PCF sends a A11-Registration Request message with Lifetime set to zero,
and accounting related information. The PCF starts timer Tregreq.

16
17
18
19
20
21
22

162

comment

TIA/EIA-2001

d.

The PDSN stores the accounting related information for further processing
before returning A11-Registration Reply message and closes the A10
connection for the mobile. The PCF also closes the A10 connection. The PCF
stops timer Tregreq.

e.

The BS sends a Clear Request message to the MSC to initiate clearing of the
radio and other resources assigned to the call and starts timer T300.

f.

The MSC sends a Clear Command message to the BS, instructing the BS to
release the associated resources, including the radio resources and starts timer
T315. The BS stops timer T300 upon receiving the Clear Command.

g.

The BS sends a Release Order to the mobile instructing the mobile to close the
packet data session. The BS releases the radio resources and closes the packet
data session for the mobile. The mobile acknowledges the Release Order by
returning a Release Order to the BS and closes the packet data session

h.

The BS returns a Clear Complete message to the MSC. The MSC stops timer
T315.

2
3
4
5
6
7
8
9
10
11
12
13
14
15

163

TIA/EIA/IS-2001

1
2
3
4
5
6

2.15.5.5

Packet Data Service Session Clearing MSC Initiated

User data traffic is now being passed over the A10 connection encapsulated within GRE
frames. An event occurs at the MSC that requires closing of the packet data session
and release of radio and other resources for the call. The MSC initiates closure of the
A10 connection with the PDSN. Traffic channel and other resources assigned to the call
are also released.

7
8
9

MS

MSC

BSC/PCF

time comment
PDSN

User Data Session

Clear Command

a
T315

TCH Release

b
A11 Registration Request (Lifetime=0, Accounting data)

Tregreq A11 Registration Reply (Lifetime=0, Accept) d

Clear Complete

10
11
12

Figure 2-47 - Packet Data Service Session Clearing MSC Initiated

13
14

a.

An event occurs at the MSC that requires closure of the packet data session.
The MSC sends a Clear Command message to the BS, instructing the BS to
release the call and associated resources, including the radio resources. Steps
c and d may occur in parallel with step b.

b.

The BS and the mobile release the traffic channel and other radio resource.

15
16
17
18

19
20
21
22
23
24

The PCF sends a A11-Registration Request message to the PDSN with a Lifetime timer value of zero to
close the A10 connection. Accounting data is also included in the A11-Registration Request message.
The PCF starts timer Tregreq
c.

The PDSN stores the accounting data for further processing and responds
with a Registration Reply to complete the release of the A10 connection. The
PCF stops timer Tregreq.

25
26
27

d. The BS sends a Clear Complete message to the MSC. The MSC stops timer
T315.

164

TIA/EIA-2001

2.15.5.6

Packet Data Service Session Clearing MS Initiated

The example below shows the termination of a packet data call as a result of a power
down operation by the MS.

2
3
4

MSC

BS/PCF

MS

PDSN

Release Order
(Power Down Indication)

TCH Release

Clear Command
T315

A11 Registration Request (Lifetime=0, Accounting data)

Tregreq

comment

Clear Request
T300

time

c
d
e

A11 Registration Reply (Lifetime=0, Accept)

f
Clear Complete

5
6

Figure 2-48 - Packet Data Service Session Clearing MS Initiated

a.

The MS powers down resulting in termination of the packet data session. It

sends a Release Order to the BS with a power down indication.

b.

The BS sends a Clear Request to the MSC. The BS starts timer T300.

10

c.

The MSC responds with a Clear Command. The BS stops timer T300. The
MSC starts timer T315.

d.

The BS responds to the MS with a Release Order and the traffic channel and
other radio resources are released. Step d may occur in parallel with steps e
and f.

7
8

11
12
13
14
15

16

e.

The BS sends a A11-Registration Request message to the PDSN with a

Lifetime timer value of zero to close the A10 connection. Accounting data is
included in the message. The PCF starts timer Tregreq.

f.

The PDSN stores the accounting data for further processing and responds
with a A11-Registration Reply to complete the release of the A10 connection.
The PCF stops timer Tregreq.

g.

The BS sends a Clear Complete message to the MSC. The MSC stops timer
T315.

17
18
19
20
21
22
23
24

165

TIA/EIA/IS-2001

2.15.5.7

Packet Data Service Session PDSN Initiated (Crossing A11-Registration

Request and A11-Registration Update)
User data traffic is passed over the A10 connection, encapsulated within GRE frames.
An event occurs at the PDSN that requires closing of the packet data session. The
PDSN initiates closure of the A10 connection with the PCF. At the same time, PCF
sends a A11-Registration Request message to the PDSN to perform periodic reregistration of the A10 connection. Release of the A10 connection initiated by the
PDSN takes precedence. Traffic channel and other resources assigned to the call are
also released.

3
4
5
6
7
8
9
10

time
MS

BS/PCF

MSC

comment

PDSN

a
A11-Registration Request (lifetime, Accounting Data)
A11-Registration Update
UpdateUpdate

Tregreq

Tregupd

A11-Registration Reply (Lifetime=0, accept)

A11-Registration Acknowledge

A11-Registration Request (lifetime= 0,Accounting Data)

Tregreq A11-Registration Reply (Lifetime=0, accept)

f
Clear Request
g
T300

Clear Command

T315

TCH Release
Clear Complete

i
j

11
12
13
14

Figure 2-49 - Packet Data Service Session PDSN Initiated (Crossing A11Registration Request and A11-Registration Update)
166

TIA/EIA-2001

1
2

a.

The PCF sends A11-Registration Request message before expiry of

registration Lifetime timer (Trp) for refreshing registration for the A10
connection, and starts timer Tregreq. Accounting related and other information
may also be included in the A11-Registration Request message.

b.

An event occurs at the PDSN that requires closure of the packet data session.
The PDSN initiates closure of the A10 connection by sending a A11Registration Update message to the PCF, and starts timer Tregupd.

c.

On receipt of A11-Registration Request message while timer Tregupd is

running, the PDSN returns a A11-Registration Reply with lifetime set to zero
(0). The PDSN, however stores the accounting related and other information (if
received) for further processing, before returning the A11-Registration Reply.
The PCF stops timer Tregreq.

d.

On receipt of A11-Registration Update message, irrespective of timer Tregreq

condition, the PCF responds with a A11-Registration Acknowledge message.
Steps e through f may occur in parallel with steps g through i. The PDSN
stops timer Tregupd.

e.

The PCF sends a A11-Registration Request message with Lifetime set to zero,
and accounting related information to the PDSN. The PCF starts timer Tregreq.

f.

The PDSN stores the accounting related information for further processing
before returning A11-Registration Reply message and closes the A10
connection for the mobile. The PCF also closes the A10 connection. The PCF
stops timer Tregreq.

g.

The BS sends a Clear Request message to the MSC to initiate clearing of the
radio and other resources assigned to the call. The BS starts timer T300.

h.

The MSC sends a Clear Command message to the BS, instructing the BS to
release the associated resources, including the radio resources. The MSC
starts timer T315. Upon receiving the Clear Command, the BS stops timer T300.

i.

The BS and the MS release traffic channel and other the radio resources.

j.

The BS returns a Clear Complete message to the MSC. The MSC stops timer
T315.

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

33

167

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

2.15.5.8

Inter-PCF Dormant Handoff Mobile Continues to be Served by the Serving

PDSN
In order to obtain packet data services, the mobile performed registration with the
packet network. The packet data session transitioned to dormant mode. Both the A10
connection and the link layer (PPP) connection are maintained. The source PCF
continues to perform re-registrations for the A10 connection with the PDSN by the
exchange of A11-Registration Request and A11-Registration Reply messages before
expiry of A10 connection Lifetime timer Trp.
While in the dormant mode, the mobile detects a change of Packet Zone ID. On
detection of a new Packet Zone ID, the mobile sends an Origination Message to the
target BS that includes the packet data service option and the DRS bit set to 0. The
target PCF establishes an A10 connection with the PDSN. If the the PDSN has data, the
PDSN returns the Data Available Indicator in the Vendor/Organization Specific
Extension within the Registration Reply to the BS/PCF resulting in establishment of the
traffic channel. The source PDSN releases the A10 connection with the PCF-S. The
target PCF periodically re-registers with the source PDSN by the use of A11Registration Request message before the A10 connection Lifetime expires.

168

TIA/EIA-2001

MS

Source
BS/PCF

Target
BS/PCF

MSC

PDSN

Origination

time

comment

BaseStation AckOrder

Complete L3 Info: CM Service Request

T303

Assignment Request

T10

A11-Registration Request (Lifetime, MEI)

Tregreq

A11-Registration Reply (Lifetime, Accept)

Assignment Failure

Clear Command
T20

Clear Complete
i

T_rp

A11-Registration Update
A11-Registration Acknowledge

j
Tregupd

A11-Registration Request(Lifetime=0, Accounting data)

Tregreq

A11-Registration Reply (Lifetime=0, accept)

A11-Registration Request(Lifetime, Accounting data)
Tregreq

A11-Registration Reply (Lifetime, accept)

k
l
m

o
p

2
3
4

Figure 2-50 - Inter-PCF Dormant Handoff Mobile Continues to be Served by the

Serving PDSN

169

TIA/EIA/IS-2001

1
2

a.

On detection of a new Packet Zone ID, the mobile sends an Origination

Message with DRS set to 0 to the target BS.

b.

The target BS acknowledges the receipt of the Origination Message with a BS

Ack Order to the mobile.

c.

The target BS constructs a CM Service Request message, places it in the

Complete Layer 3 Information message, and sends the message to the MSC,
and starts timer T303.

d.

The MSC sends an Assignment Request message to the target BS requesting

assignment of radio resources and starts timer T10.. On receipt of the
Assignment Request the BS stops timer T303.

e.

The target PCF sends an A11-Registration Request message to the PDSN..

The Registration Request message includes the Mobility Event Indicator
within the Vendor/Organization Specific Extension. The PCF starts timer
Tregreq.

f.

The A11-Registration Request is validated and the PDSN accepts the

connection by returning a A11-Registration Reply with an accept indication. If
the PDSN has data to send, it includes the Data Available Indicator within the
Vendor/Organization Specific Extension. The A10 connection binding
information at the PDSN is updated to point to target PCF. The PCF stops timer
Tregreq.

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

If the PDSN responds to the PCF with the Data Available Indicator, the BS will
establish traffic channels as in step g in Figure 2-53. In this case the remaining
steps in this procedure are omitted.

22
23
24

g.

The BS sends the Assignment failure message to the MSC with the cause
value indicating Packet Call Going Dormant and starts timer T20. The MSC
stops timer T10

h.

MSC sends Clear Command to BS with Cause value Do Not Notify Mobile and
starts timer T315. BS stops timer T20 upon receipt of the Clear Command
message.

i.

BS send a Clear Complete message to the MSC. MSC stops timer T315 upon
receipt of the Clear Complete.

34

j.

35

k.

The PDSN initiates closure of the A10 connection with the source PCF by
sending a A11-Registration Update message. The PDSN starts timer Tregupd.

l.

The source PCF responds with a A11-Registration Acknowledge message. The

PDSN stops timer Tregupd.

25
26
27
28
29
30
31
32
33

36
37
38

40

m. The source PCF sends a A11-Registration Request message with Lifetime set
to zero, and accounting related to the PDSN. The PCF starts timer Tregreq.

41

n.

The PDSN sends the A11-Registration Reply message to the source PCF. The
source PCF closes the A10 connection for the mobile. The PCF stops timer
Tregreq.

o.

The target PCF sends A11-Registration Request message before expiry of

registration Lifetime timer (Trp) for refreshing registration for the A10
connection with the PDSN. The A11-Registration Request message is also

39

42
43
44
45
46

170

TIA/EIA-2001

used to send accounting related and other information to the PDSN. The
accounting related and other information is sent at system defined trigger
points. The PCF starts timer Tregreq.

1
2
3
4
5
6
7
8

p.

For a validated A11-Registration Request, the PDSN returns a A11Registration Reply message with an accept indication and a configured
Lifetime value. The PDSN stores the accounting data (if received) for further
processing, before returning the A11-Registration Reply. The PCF stops timer
Tregreq.

171

TIA/EIA/IS-2001

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

2.15.5.9

Inter-PCF Dormant Handoff Mobile Served by a New Target PDSN

In order to obtain packet data services, the mobile performed registration with the
packet network. The packet data session transitioned to dormant mode. Both the A10
connection and the link layer (PPP) connection are maintained. The sourcePCF
continues to perform re-registrations for the A10 connection with the sourcePDSN by
the exchange of A11-Registration Request and A11-Registration Reply messages before
expiry of A10 connection Lifetime timer Trp.
While the packet data session is in dormant mode, the mobile detects a change of
Packet Zone ID. On detection of a new Packet Zone ID, the mobile sends an Origination
Message to the BS-T that includes the packet data service option and the DRS bit set to
0. The target PCF establishes an A10 connection with the target PDSN-T.
Since the BS will normally not establish a traffic channel when it receives an origination
with DRS set to 0, a traffic channel will be established, after the BS/PCF receives a
Registration Reply message from the PDSN containing Data Available Indicator. Link
layer (PPP) re-establishment between the mobile and the target PDSN-Tand Mobile IP
re-registration between the mobile and the packet network are then performed. If user
data is available, it is exchanged between the mobile and the corresponding node over
the new A10 connection, encapsulated within GRE frames. The source PDSN releases
the A10 connection with the source PCF on expiry of MIP registration timer or Trp timer.
The target PCF periodically re-registers with the PDSN-Tby the use of A11-Registration
Request message before the A10 connection Lifetime expires.

23

172

TIA/EIA-2001

MS

Source
BS/PCF

Target
BS/PCF

MSC

Source
PDSN

Target
PDSN

Origination

time

Base Station Ack Order

Complete L3 Info: CM Service Request

T303

Assignment Request

T10

e
A11-Registration Request (Lifetime, MEI)

Tregreq

A11-Registration Reply (Lifetime, Accept, Data Available Indicator)

f
g

TCH Release
Assignment Complete

T_rp

A11-Registration Update
A11-Registration Acknowledge

Tregupd

A11-Registration Request(Lifetime=0, Accounting data)

k
Tregreq

A11-Registration Reply (Lifetime=0, accept)

A11-Registration Request(Lifetime, Accounting data)

Tregreq

A11-Registration Reply (Lifetime, accept)

l
m
n

1
2

Figure 2-51 - Inter-PCF Dormant Handoff Mobile Served by a New Target PDSN

173

comment

TIA/EIA/IS-2001

a.

On detection of a new Packet Zone ID, the mobile sends an Origination

Message with DRS set to 0 to the target target BS.

b.

The target BS acknowledges the receipt of the Origination Message with a BS

Ack Order to the mobile.

c.

The target BS constructs a CM Service Request message, places it in the

Complete Layer 3 Information message, and sends the message to the MSC,
and starts timer T303.

d.

The MSC sends an Assignment Request message to the target BS requesting

assignment of radio resources and starts timer T10. On receipt of the
Assignment Request the BS stops timer T303.

e.

The target PCF initiates establishment of the A10 connection by sending a

A11-Registration Request message to the target PDSN-T. The Registration
Request message includes the Mobility Event Indicator within the
Vendor/Organization Specific Extension. The PCF starts timer Tregreq.

f.

The A11-Registration Request is validated and the target PDSN-T accepts the
connection by returning a A11-Registration Reply with an accept indication
and Data Available Indicator within the Vendor/Organization Specific
Extension. The PCF stops timer Tregreq.

g.

On receipt of Registration Reply with Data Availability Indicator, the BS

initiates setup of the traffic channel with the MS.

h.

The BSC sends the Assignment Complete message to the MSC. The MSC
stops timer T10.

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

PDSN-T

25

i.

On expiry of the MIP registration timer the source PDSN initiates closure of the
A10 connection with the source PCF by sending a Registration Update
message. The PDSN starts timer Tregupd.

j.

The source PCF responds with a A11-Registration Acknowledge message. The

source PDSN stops timer Tregupd.

k.

The source PCF sends a A11-Registration Request message with Lifetime set
to zero, and accounting related information (inclusing connection release
airlink record) to the source PDSN. The source PCF starts timer Tregreq.

l.

The source PDSN stores the accounting related information for further
processing before returning A11-Registration Reply message. The source PCF
closes the A10 connection for the mobile. The source PCF stops timer Tregreq.

26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41

m. The target PCF sends A11-Registration Request message before expiry of

registration Lifetime timer (Trp) for refreshing registration for the A10
connection with the target PDSN. A11-Registration Request message is also
used to send accounting related and other information to the target PDSN. The
accounting related and other information is sent at system defined trigger
points. The target PCF starts timer Tregreq.

174

TIA/EIA-2001

2
3
4
5
6

n.

For a validated A11-Registration Request, the target PDSNreturns a A11Registration Reply message with an accept indication and a configured
Lifetime value. The target PDSN stores the accounting related and other
information (if received) for further processing, before returning the A11Registration Reply. The targetPCF stops timer Tregreq.

175

TIA/EIA/IS-2001

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

2.15.5.10

Inter-PCF Hard Handoff Mobile Continues to be Served by the Serving

PDSN
In order to obtain packet data services, the mobile performed registration with the
packet network. The traffic channel is assigned and an A10 connection established
between the source PCF and the source PDSN. It results in establishment of the link
layer (PPP) connection and Mobile IP registration with the serving packet network. The
source PCF continues to perform re-registrations for the A10 connection with the
PDSN-S by the exchange of A11-Registration Request and A11-Registration Reply
messages before expiry of A10 connection Lifetime timer Trp.
The mobile roams into the coverage area of a target BS resulting in a hard handoff. After
exchange of appropriate messages between the MSC and the source BS and the target
BS, the mobile is acquired by the target BS. The target PCF establishes an A10
connection with the PDSN. User data is exchanged between the mobile and the
correspondent node over the new A10 connection, encapsulated within GRE frames.
The PDSN releases the A10 connection with the source PCF. The target PCF
periodically re-registers with the PDSN by the use of A11-Registration Request
message before the A10 connection Lifetime expires.

19

176

TIA/EIA-2001

MS

Source
BS/PCF

Target
BS/PCF

MSC

PDSN

Handoff Required
T7

time

comment

Handoff Request

Null forward traffic channels Frames

c
Handoff Request Ack
d
Handoff Command
e
Extended/General Handoff Direction
T9

MS Ack Order

Twaitho

Handoff Commenced

Reverse Traffic Channel Preamble or Data

Handoff Completion

BS Ack

k
A11-Registration Request (Lifetime, MEI)
l

Tregreq

T306

A11-Registration Reply (Lifetime, Accept)

m
Handoff Complete

User Data Transmission

Trp
Clear Command
Clear Complete

p
T315

A11-Registration Update
A11-Registration Update Acknowledge

r
Tregupd

A11-Registration Request (lifetime=0, Accounting Data)

Tregreq

A11-Registration Reply (Lifetime=0, accept)

s
t
u

A11-Registration Request (lifetime, Accounting Data)

v
Tregreq

A11-Registration Reply (Lifetime, accept)

w

1
2
3

Figure 2-52 - Inter-PCF Hard Handoff Mobile Continues to be Served by the Serving
PDSN

177

TIA/EIA/IS-2001

2
3

a.

On detection of a condition that a hard handoff is required, the source BS

sends a Handoff Required message to the MSC with a preferred list of target
cells, and starts timer T7.

b.

The MSC tries each of the elements in the preferred cell list until one cell is
found that has an available radio channel. The MSC sends a Handoff Request
message to the target target BS.

c.

Upon receipt of the Handoff Request message, target BS allocates suitable idle
(radio) resources. The target BS starts transmitting null TCH data on the
forward traffic channel for the mobile.

d.

The target BS returns a Handoff Request Ack message to the MSC with
appropriate RF channel information to allow the mobile to be instructed to tune
to the new RF channel, and starts timer T9 to wait for the mobile to arrive on
the radio channel.

e.

Upon receipt of the Handoff Request Ack message from target BS, the MSC
prepares to switch the call from source BS to target BS. The MSC sends a
Handoff Command message to source BS containing appropriate RF channel
information received from target BS.

f.

Upon receipt of the Handoff Command message, the source BS stops timer T7,
instructs the mobile to handoff by sending the Handoff Direction message. If
the MS is allowed to return to the source BS, then timer Twaitho is started by
the source BS.

g.

The mobile acknowledges receipt of the Handoff Direction message by

sending an MS Ack Order message to source BS.

h.

Upon receipt of confirmation from the mobile, the source BS sends a Handoff
Commenced message to the MSC. The source BS starts timer T306 to await the
Clear Command message from the MSC. If timer Twaitho has been started, the
source BS shall wait for that timer to expire before sending the Handoff
Commenced message.

i.

The mobile starts sending reverse TCH frames or preamble data to the target
BS.

j.

Upon synchronization of the traffic channel, the mobile sends a Handoff

Completion Message to the target BS.

k.

The target BS acknowledges receipt of the Handoff Completion Message by

sending a BS Ack Order to the mobile.

l.

The target PCF A11-Registration Request message with Mobility Event

Indicator within Vendor/Organization Specific Extension to the PDSN. The
PCF starts timer Tregreq.

4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

178

TIA/EIA-2001

m. The A11-Registration Request is validated and PDSN accepts the connection

by returning a A11-Registration Reply with an accept indication. The A10
connection binding information at the PDSN is updated to point to target PCF.
The target PCF stops timer Tregreq.

n.

The BS-T detects that the mobile has successfully accessed the target and
stops timer T9. BS-T then sends a Handoff Complete message to the MSC
indicating successful completion of hard handoff.

o.

User data is exchanged between the mobile and the correspondent node over
this A10 connection.

p.

Upon receipt of Handoff Complete, the MSC initiates release of the MSC
resources used in the handoff. MSC then sends a Clear Command message to
source BS, informing it of the success of the hard handoff. The source BS
stops timer T306. The MSC starts timer T315 also.

q.

The source BS sends a Clear Complete message to the MSC acknowledging

success of the handoff. MSC stops timer T315 on receipt of the Clear Complete
message.

r.

The PDSN initiates closure of the A10 connection with the source PCF by
sending a A11-Registration Update message. The PDSN starts timer Tregupd.

s.

The source PCF responds with a A11-Registration Acknowledge message. The

PDSN stops timer Tregupd.

t.

The source PCF sends a Registration Request message with Lifetime set to
zero, and accounting related information to the PDSN. The PCF starts timer
Tregreq.

u.

The PDSN stores the accounting related information for further processing
before returning Registration Reply message. The source PCF closes the A10
connection for the mobile. The source PCF stops timer Tregreq

v.

The target PCF sends A11-Registration Request message before expiry of

registration Lifetime timer (Trp) for refreshing registration for the A10
connection with the PDSN. A11-Registration Request message is also used to
send accounting related and other information to the PDSN. The accounting
related and other information is sent at system defined trigger points. The PCF
starts timer Tregreq.

1
2
3

6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

w. For a validated A11-Registration Request, the PDSN returns a A11Registration Reply message with an accept indication and a configured
Lifetime value. The PDSN stores the accounting related and other information
(if received) for further processing, before returning the A11-Registration
Reply. The PCF stops timer Tregreq.

179

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

2.15.5.11

Inter-BS Hard Handoff Mobile Served by a New Target PDSN

In order to obtain packet data services, the mobile performed registration with the
packet network. The traffic channel is assigned and an A10 connection established
between the serving source PCF and the source PDSN on behalf of the mobile. It results
in establishment of the link layer (PPP) connection and Mobile IP registration with the
serving packet network. The source PCF continues to perform re-registrations for the
A10 connection with the source PDSN by the exchange of A11-Registration Request
and A11-Registration Reply messages before expiry of A10 connection Lifetime timer
Trp.
The mobile roams into the coverage area of a target BS resulting in a hard handoff. After
exchange of appropriate messages between the MSC and the source BS , the mobile is
acquired by the target BS. The target PCF establishes an A10 connection with the target
PDSN. Link layer (PPP) establishment between the mobile and target PDSN and Mobile
IP re-registration between the mobile and the packet network may then be performed.
User data is exchanged between the mobile and the correspondent node over the new
A10 connection, encapsulated within GRE frames. The source PDSN releases the A10
connection with the source PCF on expiry of MIP registration timer. The target
PCFperiodically re-registers with the target PDSN by the use of A11-Registration
Request message before the A10 connection Lifetime expires.

180

TIA/EIA-2001

1
2

MS

Source
BS/PCF

Target
BS/PCF

MSC

PDSN-S

PDSN-T

Handoff Required
T7

time

Handoff Request

Null forward traffic channels Frames

c
Handoff Request Ack

Handoff Command
e
Extended/General Handoff Direction
f

T9

MS Ack Order
Twaitho

Handoff Commenced

x
Reverse Traffic Channel Preamble or Data

h
i

Handoff Completion

BS Ack
Order

A11-Registration Request (Lifetime, MEI)

T306

k
l

Tregreq

A11-Registration Reply (Lifetime, Accept)

Handoff Complete

User Data Transmission

Clear Command
Clear Complete

p
T315

A11-Registration Update
A11-Registration Acknowledge

r
Tregupd

A11-Registration Request (lifetime=0, Accounting Data)

Tregreq

A11-Registration Reply (Lifetime=0, accept)

A11-Registration Request (lifetime, Accounting Data)
Tregreq

A11-Registration Reply (Lifetime, accept)

s
t
u
v
w

3
4

Figure 2-53 - Inter-BS Hard Handoff Mobile Served by New Target PDSN
181

comment

TIA/EIA/IS-2001

1
2

a.

On detection of a condition that a hard handoff is required, the sourceBS

sends a Handoff Required message to the MSC with a preferred list of target
cells, and starts timer T7.

b.

The MSC tries each of the elements in the preferred cell list until one cell is
found that has an available radio channel. The MSC sends a Handoff Request
message to the target BS.

c.

Upon receipt of the Handoff Request message, target BS allocates suitable idle
(radio) resources. The BS starts transmitting null TCH data on the forward
traffic channel for the mobile.

d.

The target BS returns a Handoff Request Ack message to the MSC with
appropriate RF channel information to allow the mobile to be instructed to tune
to the new RF channel, and starts timer T9 to wait for the mobile to arrive on
the radio channel.

e.

Upon receipt of the Handoff Request Ack message from target BS, the MSC
prepares to switch the call from source BS to target BS. The MSC sends a
Handoff Command message to source BS containing appropriate RF channel
information received from the target BS..

f.

Upon receipt of the Handoff Command message, the source BS stops timer T7,
instructs the mobile to handoff by sending HDM/EHDM/GHDM message. If
the MS is allowed to return to the source BS, then timer Twaitho is started by
the source BS."

g.

The mobile acknowledges receipt of HDM/GHDM/EHDM by sending an MS

Ack Order message to source BS.

h.

Upon receipt of confirmation from the mobile, the source BS sends a Handoff
Commenced message to the MSC. The source BS starts timer T306 to await the
Clear Command message from the MSC. If timer Twaitho has been started, the
source BS shall wait for that timer to expire before sending the Handoff
Commenced message.

i.

The mobile starts sending reverse TCH frames or preamble data to the target
BS.

j.

Upon synchronization of the traffic channel, the mobile sends a Handoff

Completion Message to the target BS.

k.

The target BS acknowledges receipt of the Handoff Completion Message by

sending a BS Ack Order to the mobile.

l.

The target PCF selects target PDSN for this call and an A11-Registration
Request message with Mobility Event Indicator within the
Vendor/Organization Specific Extension to the target PDSN. The target PCF
starts timer Tregreq.

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

43

m. The A11-Registration Request is validated and target PDSN accepts the

connection by returning a A11-Registration Reply with an accept indication.
The target PCF stops timer Tregreq.

44

n.

41
42

45
46

The target BS detects that the mobile has successfully accessed the target and
stops timer T9. The target BS then sends a Handoff Complete message to the
MSC indicating successful completion of hard handoff.

182

TIA/EIA-2001

o.

The link layer (PPP) connection between the mobile and the PDSN-T is
established and the mobile performs MIP registration with the packet network.
User data is exchanged between the mobile and the correspondent node over
this A10 connection.

p.

Upon receipt of Handoff Complete, the MSC initiates release of the MSC
resources used in the handoff. MSC then sends a Clear Command message to
the source BS, informing it of the success of the hard handoff. The source BS
stops timer T306. The MSC starts timer T315.

q.

The source BS sends a Clear Complete message to the MSC acknowledging

success of the handoff. MSC stops timer T315 on receipt of the Clear Complete
message.

r.

On expiry of MIP registration timer the source PDSN initiates closure of the
A10 connection with the PCF by sending a A11-Registration Update message.
The source PDSN starts timer Tregupd.

s.

The source PCF responds with a A11-Registration Acknowledge message. The

source PDSN stops timer Tregupd.

t.

The source PCF sends a A11-Registration Request message with Lifetime set
to zero, and accounting related information to the source PDSN. The source
PCF starts timer Tregreq.

u.

The serving PDSN stores the accounting related information for further
processing before returning A11-Registration Reply message. The source PCF
closes the A10 connection for the mobile. The source PCF stops timer Tregreq.

v.

The target PCF sends A11-Registration Request message before expiry of

registration Lifetime timer (Trp) for refreshing registration for the A10
connection with the target PDSN. A11-Registration Request message is also
used to send accounting related and other information to the target PDSN. The
accounting related and other information is sent at system defined trigger
points. The target PCF starts timer Tregreq

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

w. For a validated A11-Registration Request, the target PDSN returns a A11Registration Reply message with an accept indication and a configured
Lifetime value.

32

183

TIA/EIA/IS-2001

3.

Radio Resource Management

3.1

Radio Channel Supervision

3.1.1

Traffic Channel Radio Link Supervision

Radio link supervision of dedicated radio resources shall be the responsibility of the BS.
If communication with the mobile is lost then the BS can request that the call be cleared.

6
7

3.1.2

The quality of idle radio channels may be measured by the BS.

10

Idle Channel Observation

3.2

Radio Channel Management

3.2.1

Radio Channel Configuration Management

11

12

13
14
15

The channel configuration management shall be controlled between the BS and the
Operations System (OS) over the O Interface. The BS shall be able to support one cell or
multiple cells. The O Interface is beyond the scope of this specification.

184

TIA/EIA/IS-2001

3.2.2

Radio Traffic Channel Management

3.2.2.1

Radio Channel Allocation

The BS shall always choose the radio channel to be used.

3.2.2.2

The release of a dedicated radio resource is primarily controlled by the MSC. However,
for radio propagation reasons the BS can request of the MSC that a call be released.

6
7

3.2.2.3

Radio Traffic Channel Power Control

All power control functions shall be performed between the MS and the BS.

10

Radio Traffic Channel Release

3.2.2.4

UNUSED SECTION

3.2.2.5

Channel Encoding and Decoding

11

12
13
14
15

The radio channel encoding and decoding, and interleaving shall be performed by the
BS. The type of radio channel coding and interleaving is derived from the information in
the Assignment Request message from the MSC.

185

TIA/EIA/IS-2001

3.3

Handoff via MSC

3.3.1

Introduction

Handoffs (both Intra-BS and Inter-BS) can occur for one of several reasons including
radio propagation, traffic distribution, OAM&P activity, and equipment failure. See also
sections 2.14.3, 2.14.5, and 2.15.5 for packet data scenarios.

4
5
6

Inter-BS Handoff: An Inter-BS handoff is attempted whenever a potential target may

be outside of the domain of the source BS. The MSC may optionally use inter-BS hard
handoff procedures to perform handoffs where the source BS and target BS are the
same. Hard handoff includes inter-MSC hard handoff in which the source BS and the
target BS are controlled by different MSCs.

7
8
9
10
11

Intra-BS Handoff: An intra-BS handoff is a handoff performed under the domain of one
BS. As such, the MSC is not involved in the execution of the handoff. Once an intra-BS
hard handoff is successfully completed, the BS shall inform the MSC if the old cell is no
longer involved in the call. Once an intra-BS soft/softer handoff is successfully
completed, the BS shall inform the MSC unless the designated cell concept is used, see
section 3.3.1.3 (Concept of Designated Cell).

12
13
14
15
16
17

18

3.3.1.1

The BS shall be able to generate an indication that a hard handoff may be required to
the MSC using the protocols defined.

19
20

No additional guidance is given within this specification concerning the algorithm

within the BS that generates either an Intra-BS handoff, or an indication to the MSC that
an Inter-BS hard handoff is required.

21
22
23

24

3.3.1.2

27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

Recognition That a Handoff is Required by the MSC

For this version of the standard, the MSC may not autonomously precipitate a handoff.

25

26

Recognition That a Handoff is Required by a BS

3.3.1.3

Concept of Designated Cell

A designated cell is a cell identifier (cell + sector) that is chosen by the BS to
represent the mobile stations location. The initial cell identifier associated with the
mobile stations activity (origination, termination, etc.) is by definition the first
designated cell. When the air interface only supports connection of the mobile
station to a single sector at a time, the designated cell is the currently connected
sector. When the air interface supports connection of a mobile station to multiple
sectors (possibly on different cells) simultaneously, e.g., CDMA soft/softer handoff, a
single designated cell is to be identified to the MSC.
As long as the original cell identifier that was provided to the MSC to identify the initial
designated cell remains on the call, it may remain the designated cell. When the
sector identified as the designated cell is removed from the call, the BS currently
serving as the source BS for the call chooses a new designated cell from the set of
sectors serving the call and shall provide the appropriate cell identifier to the MSC. The
source BS may choose a new designated cell at any time from the set of cells
currently serving the call. The technique for choice of a designated cell is an
operator/manufacturer concern.

186

TIA/EIA/IS-2001

The notification to the MSC can be implicit through the use of the inter-BS handoff
procedure (Handoff Required, Handoff Request, Handoff Request Acknowledge,
Handoff Command messages), or explicit through the use of the Handoff Performed
message. The implicit notification occurs when the handoff type is a hard handoff.

1
2
3
4

3.3.2

This section discusses the protocol to support hard handoff transitions where the
source and target cells are under the domain of different BSs. For this version of the
standard, it is assumed that the only CDMA traffic channels that may be transferred via
inter-BS hard handoff are the Fundamental and Dedicated Control Channels (FCH and
DCCH, resp.). Hard handoff of the Supplemental Channel is not supported in this
version of the standard.

6
7
8
9
10
11

For a MS operating on the CDMA traffic channel, an inter-BS hard handoff may occur
while the MS is in the Conversation State, or Waiting for Answer State.

12
13

14

3.3.2.1

Triggering Phase
Hard handoff triggering is initiated by the MS or the source BS.

15

16

Inter-BS Hard Handoff

3.3.2.1.1

UNUSED SECTION

3.3.2.1.2

UNUSED SECTION

3.3.2.1.3

UNUSED SECTION

3.3.2.2

Target Determination Phase

17

18
19

20
21

22

Having received an indication from a BS that an Inter-BS hard handoff is required, the
decision of when and whether an Inter-BS hard handoff is to take place shall be made
by the MSC. Inter-BS soft/softer handoff decisions can be made by the source and
target BSs involved, see section 3.4 (Handoff via Direct BS-to-BS Signaling).

23
24
25
26

Procedures for inter-BS hard handoffs are discussed in section 3.3.2 (Inter-BS Hard
Handoff), and the procedures for intra-BS handoffs are discussed in section 3.3.3 (IntraBS Handoff). Procedures for inter-BS soft/softer handoff are discussed in section 3.4
(Handoff via Direct BS-to-BS Signaling). Message Transaction diagrams for each of
these procedures can be found in section 3.5 (Handoff Call Flows). Message formats to
support the procedures are found in section 6.1 (Message Definitions). Definitions of
timers within this chapter can be found in section 6.3 (Timer Definitions).

27
28
29
30
31
32
33

34
35
36
37
38
39
40

3.3.2.2.1

Handoff Required
This message allows the source BS to initiate a handoff. This message provides the
MSC with a list of target candidate cells or optional measurement information for the
MSC to use in order to determine a target with an available radio channel.
Upon receiving a Handoff Required message, the MSC may construct a candidate target
list, modify the existing one, or use the existing list as received. Alternatively, the MSC
may unilaterally determine a candidate target cell list. Once the MSC has established a

187

TIA/EIA/IS-2001

candidate target cell list, the handoff processing continues with resource establishment.
See section 3.3.2.3 (Resource Establishment).

1
2

3.3.2.2.1.1

When a source BS has sufficient information to initiate a handoff, it shall determine if

one or more target cells are outside the current BS domain. If one or more candidate
targets are outside its domain or if all handoffs are handled by the MSC, then the source
BS shall generate a Handoff Required message requesting the MSC to find a target with
available resources.

4
5
6
7
8

Absence of the IS-95 Channel Identity or IS-2000 Channel Identity element indicates
that the type of handoff being requested is a CDMA to AMPS hard handoff.

9
10

If timer T7 has not been started for this handoff attempt prior to this time, it shall now be
started. This implies that the Handoff Required message shall be repeated by the BS
with a periodicity no smaller than T7 between messages.

11
12
13

Please refer to section 6.1.5.4, Handoff Required, for the format and content of this
message.

14
15

16

3.3.2.2.1.2

Failure Operation
If a Handoff Command message is not received prior to expiration of timer T7, then the
source BS may resend the Handoff Required message.

17
18

The MSC shall always respond to the Handoff Required message. The BS may resend
the Handoff Required message only after timer T7 expires or a Handoff Required Reject
message is received.

19
20
21

22

Successful Operation

3.3.2.3

Resource Establishment

3.3.2.3.1

Handoff Request

23

24

This BSMAP message allows the MSC to make specific requests of potential targets to
provide radio resources for a handoff of an existing mobile connection.

25
26

27
28
29
30
31
32
33
34
35
36
37
38
39
40

3.3.2.3.1.1

Successful Operation
This message is sent by the MSC to candidate target cell(s). Using the candidate target
cell list generated per section 3.3.2.2.1 (Handoff Required), the MSC will determine a
target cell that has available resources that match the mobiles permitted channel type.
More than one candidate target cell under the domain of the same BS may be specified
for simultaneous inclusion in the handoff. To accomplish a handoff for any supported
signaling type, a Handoff Request message is constructed and sent to the necessary
BS(s). Information may be included in the request that instructs the BS on specific
information on the type of radio channel required, and other miscellaneous parameters.
This information can be extracted from the Handoff Required message elements. The
MSC starts timer T11.
See section 3.3.2.2.1.1 for the use of IS-95 Channel Identity elements to indicate hard
handoff for TIA/EIA-95 systems and the use of IS-2000 Channel Identity elements to
indicate handoff for TIA/EIA/IS-2000 systems.

188

TIA/EIA/IS-2001

Upon receipt of this message, the candidate target BS shall choose suitable idle radio
resources. If available, the BS will respond to the MSC with a Handoff Request
Acknowledge message containing the appropriate channel and other pertinent
information to allow the MS to be instructed to tune to the new channel.

1
2
3
4

Please refer to section 6.1.5.5, Handoff Request, for the format and content of this
message.

5
6

3.3.2.3.1.2

Receipt of a Handoff Failure message at the MSC or expiration of T11 signals the failure
of the target BS to allocate resources for a handoff request. On receipt of a Handoff
Failure message or upon expiration of T11, the MSC shall terminate the handoff
procedure and release all references and resources associated with the target. The MSC
may continue with additional target cell candidates or send a Handoff Required Reject
message to the source BS with the appropriate cause value. Please refer to section
3.3.2.7.1 (Handoff Required Reject) and section 3.3.2.7.2, (Handoff Failure) for more
information.

8
9
10
11
12
13
14
15

16

3.3.2.3.2

18
19

3.3.2.3.2.1

22
23
24
25
26

Concurrent with the sending of the Handoff Request Acknowledge message, the target
BS shall start timer T9.

27
28

Please refer to section 6.1.5.6, Handoff Request Acknowledge for the format and
content of this message.

29
30

3.3.2.3.2.2

Failure Operation
See section 3.3.2.7.2 (Handoff Failure) for actions to be taken upon the expiration of
timer T9.

32
33

34

Successful Operation
This acknowledgment to the Handoff Request message indicates that cell(s) under this
BSs domain can qualify as the target for the handoff. The target BS indicates that the
appropriate radio and land resources have been allocated and set up for the requested
handoff. The MSC will use information provided in this message to create a Handoff
Command message to be sent to the source BS to execute the handoff. The MSC stops
timer T11.

21

31

Handoff Request Acknowledge

This BSMAP message allows the target BS to respond to the MSC concerning the
Handoff Request message. This message is generated when the target BS determines
that appropriate resources are allocated to service the needs of the incoming handoff.

17

20

Failure Operation

3.3.2.4

Execution Phase

3.3.2.4.1

Handoff Command

35

36
37
38

This BSMAP message allows the MSC to signal to the source BS that a target channel
has been allocated for handoff.

189

TIA/EIA/IS-2001

3.3.2.4.1.1

Essentially, the Handoff Command message is used to convey information about the
target BS to the source BS (and on to the mobile station) regarding layer 1 access
information at the target.

2
3
4

If the source BS elects not to honor the Handoff Command message, a Handoff Failure
message with a cause value of Alternate signaling type reject shall be sent to the MSC
so that the reserved target resources are released.

5
6
7

The source BS will transmit the handoff instructions to the mobile to execute a handoff
and will start timer T8 if an acknowledgment is requested.

8
9

The source BS will typically receive confirmation that the mobile has received the
command and is acting accordingly. Timer T8 is canceled when this confirmation is
received if timer T8 is running. The source BS may optionally send the handoff direction

10
11
12

message1 to the MS using quick repeats and may not request an acknoledgement from
the mobile. In this case, the source BS shall not start timer T8.

13
14

If the source BS indicates in a handoff direction message that the MS is allowed to

return to the source BS if it cannot acquire the target BS, the source BS will start timer
Twaitho.

15
16
17

Information contained in the elements of this message are identical to the information
contained in the corresponding elements of the Handoff Request Acknowledge (See
section 3.3.2.3.2).

18
19
20

Please refer to section 6.1.5.8, Handoff Command for the format and content of this
message.

21
22

23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

Successful Operation

3.3.2.4.1.2

Failure Operation
If the mobile station fails to acknowledge the handoff instruction (i.e., timer T8 expires)
and the mobile remains on the old channel, then a Handoff Failure message (See section
3.3.2.7.2, Handoff Failure) is sent to the MSC with the cause field set to Reversion To
Old Channel. The procedure at the target BS is terminated by the MSC using a call
clearing sequence. See section 3.3.2.6, Call Clearing for additional call clearing
requirements
If timer T8 expires and the source BS cannot detect the presence of the radio link to the
mobile, then the source BS will send a Clear Request message (See section 6.1.2.20,
Clear Request) to the MSC regarding the source channel with the cause field set to
Radio Interface failure. The channel and terrestrial resource will be released after a
Clear Command is received from the MSC.
If timer Twaitho expires, the source BS will consider this a normal event and will send a
Handoff Commenced message to the MSC. See section 3.3.2.4.2 (Handoff Commenced)
below.
If the source BS has allowed an MS to return if it cannot acquire the target BS and the
MS returns before timer Twaitho expires, the source BS shall resume servicing the MS
and send a Handoff Failure to the MSC with cause value Reversion to old channel.

1 This may be a Handoff Direction Message, a General Handoff Direction Message, an

Extended Handoff Direction Message, or a Universal Handoff Direction Message as

appropriate.

190

TIA/EIA/IS-2001

3.3.2.4.2

The Handoff Commenced message is used for ANSI/EIA/TIA-553, TIA/EIA-95, and for
TIA/EIA/IS-2000 hard handoffs. It is sent by the source BS to the MSC to indicate that
the handoff command has been sent to the mobile station, and that the mobile station is
not expected to return to the source BS.

2
3
4
5

The MSC may send a Clear Command to the source BS upon receipt of the Handoff
Commenced Message.

6
7

3.3.2.4.2.1

11
12
13
14
15
16
17

Please refer to section 6.1.5.10, Handoff Commenced for the format and content of this
message.

18
19

3.3.2.4.2.2

22

3.3.2.4.3

25

3.3.2.4.3.1

28
29
30

Please refer to section 6.1.5.11, Handoff Complete for the format and content of this
message.

31
32

3.3.2.4.3.2

3.3.2.4.4

Handoff Performed
This message is not used in the case of inter-BS hard handoff. See also sections 3.3.1
and 3.3.1.3.

36
37

38

Failure Operation
None.

34

35

Successful Operation
In the successful scenario, the MSC receives the Handoff Complete message from the
target BS. The MSC shall send a Clear Command (See section 2.3.1.6) to the source. If
the Handoff Complete is the result of a hard handoff then any terrestrial circuit to the
source BS shall also be cleared via an MSC initiated clearing sequence.

27

33

Handoff Complete
The Handoff Complete message allows the target BS to signal to the MSC that a mobile
station has successfully accessed the target cell.

24

26

Failure Operation
If timer T306 expires, then the BS follows the call clearing procedures defined in section
2.3.1.5 (i.e., send a Clear Request message to the MSC).

21

23

Successful Operation
When the source BS does not expect the MS to return, it starts timer T306 once the
Handoff Commenced message is sent to the MSC. If the handoff direction message is
sent using quick repeats, the source BS might not request an acknowledgment from the
mobile. In this case, the source BS will send the Handoff Commenced message after all
the quick repeats have been transmitted to the mobile station unless the MS has been
allowed to return if it cannot acquire the target BS. In the case that the MS has been
allowed to return, timer Twaitho will have been started and the source BS must wait
until timer Twaitho expires before sending the Handoff Commenced message to the
MSC.

9
10

20

Handoff Commenced

3.3.2.5

UNUSED SECTION

39

191

TIA/EIA/IS-2001

3.3.2.6

The call clearing procedure is described in section 2. It is used in hard handoff

scenarios to release the source RF channel and terrestrial resource after either the
mobile has been acquired by the target BS or the call is dropped.

2
3
4

The MSC may use call clearing to tear down either the source channel, the target
channel, or both in the event of a failure in the handoff process. The call clearing
messages are only used to clear full-rate circuits.

5
6
7

The Clear Command message shall contain a cause field to inform the source or target
cell of the success or failure of the handoff procedure. This indication can be used for
statistics purposes.

8
9
10

11

Call Clearing

3.3.2.7

Handoff Failure Handling

There are two messages that indicate a failure in the handoff process; the Handoff
Required Reject and the Handoff Failure messages. These messages are discussed in
this section. Also, refer to section 3.5.2.1.4 (Hard Handoff With Return On Failure).

12
13
14

16

When a traffic channel is not available at the target BS, several options are
available:

17

Option 1 - Target can allocate AMPS channel

18

Option 2 - Target indicates failure to MSC, MSC attempts to allocate AMPS

channel.

15

19

21

Option 3 - Target indicates failure then MSC passes it along to the source BS
and lets the source BS decide.

22

Options 3 shall be supported.

20

NOTE: This standard does not specify the messaging required for Option 1. Support
and implementation of this option is a vendor concern.

23
24

25

3.3.2.7.1

This message is sent from the MSC to the source BS to deny the request contained in a
Handoff Required message.

26
27

28

3.3.2.7.1.1

30
31
32

If a Handoff Required Reject message is received, then the source BS shall stop timer T7
and a new handoff procedure may be initiated if the condition of the call connection
warrants immediate action (e.g., emergency handoff). Such a procedure is implemented
at the discretion of the manufacturer and system operator.

33
34
35
36

Please refer to section 6.1.5.9, Handoff Required Reject, for the format and content of
this message.

37
38

40

Successful Operation
If the source BS requested a response by including the Response Request element in
the Handoff Required message, and the handoff cannot be accomplished, a Handoff
Required Reject message may be sent to the source BS indicating that the handoff
cannot be accomplished at this time.

29

39

Handoff Required Reject

3.3.2.7.1.2

Failure Operation
None.

192

TIA/EIA/IS-2001

3.3.2.7.2

The Handoff Failure message is sent from either the target BS or the source BS to the
MSC to indicate that there has been a failure in either the resource allocation process or
the execution of an inter-BS handoff and that the handoff has been aborted.

2
3
4

3.3.2.7.2.1

7
8

In the event that timer T9 expires and no mobile station is detected by the target BS, a
Handoff Failure message (See section 3.3.2.6.2, Handoff Failure) shall be sent to the
MSC with the appropriate cause field set.

9
10
11

If the source BS has indicated in a handoff direction message2 that the MS is allowed to
return if it cannot acquire the target BS, the possibility exists that the MS will return to
the source BS. If this happens prior to the expiry of timer Twaitho, the source BS will
send a Handoff Failure message to the MSC indicating the return of the MS.

12
13
14
15

Please refer to section 6.1.5.7, Handoff Failure, for the format and content of this
message.

16
17

19

Successful Operation
After receiving a Handoff Failure message the MSC will send a Clear Command (See
section 6.1.2.21 Clear Command) to the target BS, which shall then deallocate radio
and terrestrial resources.

18

Handoff Failure

3.3.2.7.2.2

Failure Operation
None.

2 This may be a Handoff Direction Message, a General Handoff Direction Message, an

Extended Handoff Direction Message, or a Universal Handoff Direction Message as

appropriate

193

TIA/EIA/IS-2001

3.3.3

Intra-BS Handoff

3.3.3.1

Handoff Performed

The BS uses the Handoff Performed message to inform the MSC of handoff operations.

3.3.3.1.1

An intra-BS handoff is a handoff performed under the domain of one BS. As such, the
MSC is not involved in the execution of the handoff. Once an intra-BS handoff is
successfully completed, the BS may inform the MSC via a Handoff Performed message.

6
7
8

When the sector identified as the designated cell is removed from the call, the BS
currently serving as the source BS for the call chooses a new designated cell from the
set of sectors serving the call and shall provide the appropriate cell identifier to the
MSC.

9
10
11
12

Please refer to section 6.1.5.12, Handoff Performed, for the format and content of this
message.

13
14

15
16

Successful Operation

3.3.3.1.2

Failure Operation
None.

194

TIA/EIA/IS-2001

3.4

Efficient inter-BS soft handoff is supported via direct BS to BS signaling and traffic
connections between base stations. The A3 and A7 interfaces are used to support this
form of inter-BS soft handoff which is based on packet technologies.

2
3
4

The A3 interface, composed of signaling and user traffic subchannels, provides the
ability to establish and remove A3 traffic connections. The A3 interface also provides
support for operational procedures, such as turning on/off voice privacy or changing
the service configuration of a call.

5
6
7
8

The A7 interface provides direct BS to BS signaling for the support of efficient soft
handoff.

9
10

11

Handoff via Direct BS-to-BS Signaling

3.4.1

A3 Interface Procedures and Messages

This section contains the procedure definitions and message overviews for the A3
interface. It is organized into four subsections:

12
13
14

A3 Interface Setup Procedures and Messages,

15

A3 Interface Operational Procedures and Messages,

16

A3 Interface Clearing Procedures and Messages, and

17

A3 Interface Scenarios.

18

3.4.1.1

This section contains the messages used to set up an A3 connection.

19

20

3.4.1.1.1

22
23

25
26
27
28
29
30
31
32
33
34
35
36

A3-Connect
The A3-Connect message is sent from the target BS to the source BS to initiate or add
cells to one or more A3 user traffic connection. An A3-Connect Ack message is
expected in response.

21

24

A3 Interface Setup Procedures and Messages

3.4.1.1.1.1

Successful Operation
Upon receiving the A3 Signaling Address information, the receiving BS begins the
process of establishing the A3 signaling connection with the source BS. The A3
Signaling Address is used by the target BS to allocate a logical circuit to be used for A3
signaling. The SDU ID identifies the particular instance of the SDU function.
Following the establishment of the A3 signaling link, the A3-Connect message is sent
from the target BS to the entity at the other end. The target BS expects an A3-Connect
Ack message indicating the result of processing the A3-Connect message and,
therefore, starts timer Tconn3. When the A3 user traffic connection(s) is established,
traffic packets are exchanged to verify that the two entities can communicate via the A3
user traffic connection(s).
Please refer to section 6.1.9.1, A3-Connect, for the format and content of this
message.

195

TIA/EIA/IS-2001

3.4.1.1.1.2

If timer Tconn3 expires, the target BS shall include all new cells that would have been
added by the A3-Connect message to the list of non-committed cells in the A7-Handoff
Request Ack message.

2
3
4

3.4.1.1.2

3.4.1.1.2.1

If the A3-Connect Ack message indicates that A3-Traffic Channel Status messages are
to be sent, then the source BS starts timer Tchanstat to await A3-Traffic Channel Status
message(s) for all new cells on each A3 connection. One instance of this timer is
started for each A3 connection to which one or more cells are being added.

11
12
13
14

Please refer to section 6.1.9.2, A3-Connect Ack, for the format and content of this
message.

15
16

3.4.1.1.2.2

19
20
21
22

3.4.1.2

3.4.1.2.1

27
28

3.4.1.2.1.1

31

If a change to an allocated physical channel is already pending at the target BS, the
reception of this message replaces the pending operation and the pending action time.
The new transition may place the BS into the same state it already is supporting, thus
effectively canceling the previously pending transition.

32
33
34
35

Please refer to section 6.1.9.11, A3-Physical Transition Directive, for the format and
content of this message.

36
37

39

Successful Operation
When an allocated physical channel is to be changed for a call, the source BS shall
transmit an A3-Physical Transition Directive to a target BS and start timer Tphysical.

30

38

A3-Physical Transition Directive

This message is sent from the source BS to the target BS over the A3 interface. It
conveys a change to an allocated physical channel at the target BS as well as the
expected time of execution for the change.

26

29

A3 Interface Operational Procedures and Messages

This section contains messages used on the A3 connection to support an A3 call leg.

24

25

Failure Operation
If an instance of timer Tchanstat expires, the source BS may assume that a failure has
occurred at the BS during activation of the transmitter(s)/receiver(s) and delete the
unreported cells from the active set attached to the A3 connection. The source BS may
then send an A7- Drop Target message to the target BS to cleanly remove those cells
from the A3 connection.

18

23

Successful Operation
After processing the A3-Connect message from the requesting BS, the source BS will
indicate success/failure to the requesting BS by sending an A3-Connect Ack message.

9
10

17

A3-Connect Ack
The A3-Connect Ack message is sent from the source BS to the target BS to indicate
the result of processing the A3-Connect message.

Failure Operation

3.4.1.2.1.2

Failure Operation
If timer Tphysical expires, the message may be resent.

196

TIA/EIA/IS-2001

3.4.1.2.2

This A3 message is sent from the target BS to the source BS over the A3 signaling
interface to convey the outcome of processing an A3-Physical Transition Directive
message.

2
3
4

3.4.1.2.2.1

7
8
9

Please refer to section 6.1.9.12, A3-Physical Transition Directive Ack, for the format
and content of this message.

10
11

3.4.1.2.2.2

Failure Operation
None.

13

14

Successful Operation
Upon receipt of an A3-Physical Transition Directive from the source BS, the target BS
shall transmit an A3-Physical Transition Directive Ack message to the source BS to
indicate the outcome of processing the received message. The source BS shall stop
timer Tphysical upon receipt of the A3-Physical Transition Directive Ack message.

12

A3-Physical Transition Directive Ack

3.4.1.2.3

UNUSED SECTION

3.4.1.2.4

UNUSED SECTION

3.4.1.2.5

A3-Propagation Delay Measurement Report

15

16
17

18

This message is sent from the reporting BS to the source BS over the A3 signaling
interface. It contains the CDMA serving one way delay measured at the reporting BS.

19
20

21

3.4.1.2.5.1

This message is sent from the reporting BS to the source BS over the A3 signaling
interface immediately following the acquisition of the mobile and subsequently
whenever the propagation delay changes by two or more PN chips.

22
23
24

Please refer to section 6.1.9.6, A3-Propagation Delay Measurement Report, for the
format and content of this message.

25
26

27

3.4.1.2.5.2

3.4.1.2.6

31
32
33

35
36
37

A3-IS-95 FCH Forward

This message is sent from the source BS to the receiving BS on the A3 user traffic
subchannel for subchannels of type IS-95 FCH (TIA/EIA/IS-95 Fundamental
Channel). It contains the Forward Traffic Channel frame for the served MS along with
control information for the receiving BS.

30

34

Failure Operation
None.

28

29

Successful Operation

3.4.1.2.6.1

Successful Operation
This message is sent from source BS to the receiving BS on A3 user traffic subchannel
connections of type IS-95 FCH (TIA/EIA/IS-95 Fundamental Channel) once every 20
msec.

197

TIA/EIA/IS-2001

The forward path delay shall be no more than 50 ms measured from the time the first bit
of the frame is transmitted from the source BS to the time the first bit of the frame is
transmitted over the air interface at the channel element for any soft handoff leg. This
assumes a maximum delay on the A3 traffic connection of 5 ms.

However, the delay limits defined above will not be applied to satellite applications.

Forward Frame Sequence Number Alignment clarification:

The SDU function may use the PATE (Packet Arrival Time Error) and Sequence Number
information received in the A3- IS-95 FCH Reverse message to ensure that all target
BS's involved in soft handoff for a call will simultaneously transmit identical forward air
frames during identical 20 millisecond frame boundaries.

1
2
3

8
9
10

Please refer to section 6.1.9.7, A3- IS-95 FCH Forward, for the format and content of
this message.

11
12

13

3.4.1.2.6.2

None.

14

15

3.4.1.2.7

17
18
19

21
22
23

A3- IS-95 FCH Reverse

This message is sent to the source BS on A3 user traffic subchannel connections of
type IS-95 FCH (Fundamental Channel) once every 20 msec. It contains the decoded
Reverse Traffic Channel frame received from the served MS along with control
information.

16

20

Failure Operation

3.4.1.2.7.1

Successful Operation
This message is sent to the source BS on the A3 user traffic subchannel connections of
type IS-95 FCH (Fundamental Channel) once every 20 msec following the decoding
of the Reverse Traffic Channel frame.

27

The reverse speech path delay shall be no more than 60 ms measured from the time the
last bit of the frame is received on the air interface at the channel element of any soft
handoff leg to the time the last bit of the frame is received at the source BS. This
assumes a maximum delay on the A3 traffic connection of 5 ms.

28

However, the delay limits defined above will not be applied to satellite applications.

29

Forward Frame Alignment Requirements:

30

As part of the reverse-link processing, each target BTS channel element shall estimate
the arrival time error for the A3- IS-95 FCH Forward message last received and shall set
the PATE field of the next transmitted A3- IS-95 FCH Reverse message to this value.

24
25
26

31
32
33
34
35
36
37
38
39
40
41

In the case when no forward data has been received for an interval of time exceeding the
maximum range of the PATE, the PATE value shall saturate (i.e., not rollover) at the
maximum positive value. Positive PATE values indicate that the message arrived too
late to be transmitted in the correct air frame. Negative PATE values indicate that the
message arrived too early and therefore must be buffered before transmission. Zero
PATE value indicates that the message arrived at the optimum time for processing and
transmission.
Please refer to section 6.1.9.8, A3- IS-95 FCH Reverse, for the format and content of
this message.

198

TIA/EIA/IS-2001

3.4.1.2.7.2

None.

3.4.1.2.8

5
6
7

3.4.1.2.8.1

11

This message can be used to note that the indicated set of cells has begun radio
transmission on the forward link and that the corresponding receivers have been
activated. When this message is used in response to an A3-Connect Ack message, the
target BS does not need to send this message if the transmitters(s)/receiver(s) are not
turned on at the target BS (i.e., the radio transmission on the forward link has not begun
for the indicated cells).

12
13
14
15
16
17

Multiple instances of this message may be sent relative to a single A3 connection if, for
instance, transmitter(s)/receiver(s) are activated at different times; however, all cells
referenced within a single instance of this message must be attached to the same A3
connection.

18
19
20
21

The source BS stops the instance of timer Tchanstat for that A3 connection when A3Traffic Channel Status message(s) have been received containing references to all cells
added to the A3 connection by the A3-Connect message.

22
23
24

Please refer to section 6.1.9.15, A3-Traffic Channel Status, for the format and content
of this message.

25
26

3.4.1.2.8.2

3.4.1.2.9

31
32

34
35
36
37
38
39
40
41
42

A3-IS-2000 FCH Forward

This message is sent from the source BS to the target BS on the A3 IS-2000 user traffic
subchannel for subchannel of type FCH (Fundamental Channel). It contains the
Forward air-frame for the served MS along with control information for the target BS.

30

33

Failure Operation
None.

28

29

Successful Operation
When the target BS needs to notify the source BS of a status change relative to a
specific set of cells on one A3 connection, it sends a A3-Traffic Channel Status
message.

9
10

27

A3-Traffic Channel Status

The A3-Traffic Channel Status message is used by the target BS to notify the source BS
that radio transmission on the forward link has begun for the indicated cells, and that
the corresponding receivers have been activated. This message is sent when the A3Connect Ack message indicates that it is requested.

Failure Operation

3.4.1.2.9.1

Successful Operation
This message is sent from source BS to the target BS on A3 IS-2000 user traffic
subchannel connections of type FCH (Fundamental Channel). FCH messages are
sent once every 20 ms.
The forward path message delay shall be no more than 50ms measured from the time the
first bit of the frame is transmitted from the source BS to the time the first bit of the
frame is transmitted over the air interface at the channel element for any soft handoff
leg. This assumes a maximum transmission and queuing delay on the A3 traffic
connection of 5ms. However, the delay limits defined above will not be applied to
satellite applications.

199

TIA/EIA/IS-2001

Forward Frame Sequence Number Alignment clarification:

The SDU function may use the PATE and Sequence Number information received
in the A3-IS-2000 FCH Reverse message to ensure that all BS's involved in soft
handoff for a call will simultaneously transmit identical forward air frames during
identical frame boundaries.

2
3
4
5

Please refer to section 6.1.9.9, A3-IS-2000 FCH Forward, for the format and content of
this message.

6
7

3.4.1.2.9.2

None.

10

3.4.1.2.10

A3-IS-2000 FCH Reverse

This message is sent from the target to the source BS on A3 IS-2000 user traffic
subchannel connections of type IS-2000 FCH (TIA/EIA/IS-2000 Fundamental
Channel). It contains the decoded Reverse Traffic Channel frame received from the
served MS along with control information.

11
12
13
14

15

Failure Operation

3.4.1.2.10.1

Successful Operation
This message is sent to the source BS on the A3 IS-2000 user traffic subchannel
connections of type IS-2000 FCH (TIA/EIA/IS-2000 Fundamental Channel) following
the decoding of the Reverse Traffic Channel frame. IS-2000 FCH frames are sent once
every 20 ms.

16
17
18
19

24

The reverse path message delay shall be no more than 60 ms measured from the time the
last bit of the frame is received on the air interface at the channel element of any soft
handoff leg to the time the last bit of the frame is received at the source BS. This
assumes a maximum transmission and queuing delay on the A3 traffic connection of 5
ms. However, the delay limits defined above will not be applied to satellite applications.

25

Forward Frame Alignment Requirements:

20
21
22
23

As part of the reverse-link processing, each target BTS channel element shall
estimate the arrival time error for the A3-IS-2000 FCH Forward message last
received and shall set the PATE field of the next transmitted A3-IS-2000 FCH
Reverse message to this value.

26
27
28
29

In the case when no forward data has been received for an interval of time
exceeding the maximum range of the PATE, the PATE value shall saturate (i.e., not
rollover) at the maximum positive value. Positive PATE values indicate that the
message arrived too late to be transmitted in the correct air frame. Negative PATE
values indicate that the message arrived too early and therefore must be buffered
before transmission. Zero PATE value indicates that the message arrived at the
optimum time for processing and transmission.

30
31
32
33
34
35
36

Please refer to section 6.1.9.10, A3-IS-2000 FCH Reverse, for the format and content
of this message.

37
38

39
40

3.4.1.2.10.2

Failure Operation
None.

200

TIA/EIA/IS-2001

3.4.1.2.11

This message is sent from the source BS to the target BS on the A3 IS-2000 user traffic
subchannel for subchannels of type IS-2000 DCCH (TIA/EIA/IS-2000 Dedicated
Control Channel). It contains the Forward air-frame for the served MS along with
control information for the target BS.

2
3
4
5

A3-IS-2000 DCCH Forward

3.4.1.2.11.1

Successful Operation
This message is sent from source BS to the target BS on A3 IS-2000 user traffic
subchannel connections of type IS-2000 DCCH (TIA/EIA/IS-2000 Dedicated Control
Channel). IS-2000 DCCH frames are sent once every 20 ms.

7
8
9

15

The forward path message delay shall be no more than 50ms measured from the time the
first bit of the frame is transmitted from the source BS to the time the first bit of the
frame is transmitted over the air interface at the channel element for any soft handoff
leg. This assumes a maximum transmission and queuing delay on the A3 traffic
connection of 5ms. However, the delay limits defined above will not be applied to
satellite applications.

16

Forward Frame Sequence Number Alignment clarification:

10
11
12
13
14

The SDU function may use the PATE (Packet Arrival Time Error) and Sequence
Number information received in the A3-IS-2000 DCCH Reverse message to ensure
that all BS's involved in soft handoff for a call will simultaneously transmit identical
forward air frames during identical frame boundaries.

17
18
19
20

Please refer to section 6.1.9.13, A3-IS-2000 DCCH Forward, for the format and
content of this message.

21
22

23

3.4.1.2.11.2

None.

24

25

3.4.1.2.12

27
28
29

31
32
33
34

A3-IS-2000 DCCH Reverse

This message is sent from the target to the source BS on A3 IS-2000 user traffic
subchannel connections of type IS-2000 DCCH (TIA/EIA/IS-2000 Dedicated Control
Channel). It contains the decoded Reverse Traffic Channel frame received from the
served MS along with control information.

26

30

Failure Operation

3.4.1.2.12.1

Successful Operation
This message is sent to the source BS on the A3 IS-2000 user traffic subchannel
connections of type IS-2000 DCCH (TIA/EIA/IS-2000 Dedicated Control Channel)
following the decoding of the Reverse Traffic Channel frame. IS-2000 DCCH frames are
sent once every 20 ms.

39

The reverse path message delay shall be no more than 60 ms measured from the time the
last bit of the frame is received on the air interface at the channel element of any soft
handoff leg to the time the last bit of the frame is received at the source BS. This
assumes a maximum transmission and queuing delay on the A3 traffic connection of 5
ms. However, the delay limits defined above will not be applied to satellite applications.

40

Forward Frame Alignment Requirements:

35
36
37
38

41
42

As part of the reverse-link processing, each target BTS channel element shall
estimate the arrival time error for the A3-IS-2000 DCCH Forward message last

201

TIA/EIA/IS-2001

received and shall set the PATE field of the next transmitted A3-IS-2000 DCCH
Reverse message to this value.

1
2

In the case when no forward data has been received for an interval of time
exceeding the maximum range of the PATE, the PATE value shall saturate (i.e., not
rollover) at the maximum positive value. Positive PATE values indicate that the
message arrived too late to be transmitted in the correct air frame. Negative PATE
values indicate that the message arrived too early and therefore must be buffered
before transmission. Zero PATE value indicates that the message arrived at the
optimum time for processing and transmission.

3
4
5
6
7
8
9

Please refer to section 6.1.9.14, A3-IS-2000 DCCH Reverse, for the format and content
of this message.

10
11

12

3.4.1.2.12.2

None.

13

14

3.4.1.2.13

A3-IS-2000 SCH Forward

This message is sent from the source BS to the target BS on the A3 IS-2000 user traffic
subchannel for subchannels of type IS-2000 SCH (TIA/EIA/IS-2000 Supplemental
Channel). It contains the Forward Traffic Channel frame for the served MS along with
control information for the target BS.

15
16
17
18

19

Failure Operation

3.4.1.2.13.1

Successful Operation
This message is sent from source BS to the target BS on A3 IS-2000 user traffic
subchannel connections of type IS-2000 SCH (TIA/EIA/IS-2000 Supplemental
Channel). SCH frames are sent once every 20 ms. Furthermore, IS-2000 SCH messages
containing Null frame content may be suppressed (i.e., not transmitted) on the A3
connection according to the restrictions outlined in the message format definition.

20
21
22
23
24

30

The forward path message delay shall be no more than 55ms measured from the time the
first bit of the frame is transmitted from the source BS to the time the first bit of the
frame is transmitted over the air interface at the channel element for any soft handoff
leg. This assumes a maximum transmission and queuing delay on the A3 traffic
connection of 10 ms. However, the delay limits defined above will not be applied to
satellite applications.

31

Forward Frame Sequence Number Alignment clarification:

25
26
27
28
29

The SDU function may use the PATE (Packet Arrival Time Error) and Sequence
Number information received in the A3-IS-2000 SCH Reverse message to ensure
that all BS's involved in soft handoff for a call will simultaneously transmit identical
forward air frames during identical 20 millisecond frame boundaries.

32
33
34
35

Please refer to section 6.1.9.16, A3-IS-2000 SCH Forward, for the format and content
of this message.

36
37

38

3.4.1.2.13.2

None.

39

40
41
42

Failure Operation

3.4.1.2.14

A3-IS-2000 SCH Reverse

This message is sent to the source BS on A3 IS-2000 user traffic subchannel
connections of type IS-2000 SCH (TIA/EIA/IS-2000 Supplemental Channel). It

202

TIA/EIA/IS-2001

contains the decoded Reverse Traffic Channel frame received from the served MS along
with control information.

1
2

3.4.1.2.14.1

Successful Operation
This message is sent to the source BS on the A3 IS-2000 user traffic subchannel
connections of type IS-2000 SCH (TIA/EIA/IS-2000 Supplemental Channel) following
the decoding of the Reverse Traffic Channel frame. IS-2000 SCH frames are sent once
every 20 ms. Furthermore, IS-2000 SCH messages containing Null frame content may be
suppressed (i.e., not transmitted) on the A3 connection according to the restrictions
outlined in the message format definition.

4
5
6
7
8
9

15

The reverse path message delay shall be no more than 65 ms measured from the time the
last bit of the frame is received on the air interface at the channel element of any soft
handoff leg to the time the last bit of the frame is received at the source BS. This
assumes a maximum transmission and queuing delay on the A3 traffic connection of
10ms. However, the delay limits defined above will not be applied to satellite
applications.

16

Forward Frame Alignment Requirements:

10
11
12
13
14

As part of the reverse-link processing, each target BTS channel element shall
estimate the arrival time error for the A3-IS-2000 SCH Forward message last
received and shall set the PATE field of the next transmitted A3-IS-2000 SCH
Reverse message to this value.

17
18
19
20

In the case when no forward data has been received for an interval of time
exceeding the maximum range of the PATE, the PATE value shall saturate (i.e., not
rollover) at the maximum positive value. Positive PATE values indicate that the
message arrived too late to be transmitted in the correct air frame. Negative PATE
values indicate that the message arrived too early and therefore must be buffered
before transmission. Zero PATE value indicates that the message arrived at the
optimum time for processing and transmission.

21
22
23
24
25
26
27

Please refer to section 6.1.9.17, A3-IS-2000 SCH Reverse, for the format and content
of this message.

28
29

30

3.4.1.2.14.2

None.

31

32

3.4.1.3

3.4.1.3.1

36
37

39
40
41
42

A3-Remove
A target BS uses the A3-Remove message to request that the source BS remove the
indicated cells from the indicated A3 connections. This might result in the entire
removal of an A3 traffic subchannel if the last cell on that traffic subchannel is removed.

35

38

A3 Interface Clearing Procedures and Messages

This section contains messages used to clear an A3 connection.

33

34

Failure Operation

3.4.1.3.1.1

Successful Operation
The target BS sends an A3-Remove message to the source BS requesting removal of
the indicated cells from one or more A3 connection. The source BS will reply with an
A3-Remove Ack message. If the last cell is removed from an A3 traffic subchannel, the
entire A3 traffic subchannel is also terminated. The target BS starts timer Tdiscon3.

203

TIA/EIA/IS-2001

Please refer to section 6.1.9.3, A3-Remove, for the format and content of this message.

3.4.1.3.1.2

Failure Operation

If the source BS does not recognize an A3 user traffic connection identified in the A3Remove message as being associated with the Call Connection Reference value
included in this message, it shall send an appropriate cause for the failure in the A3Remove Ack message.

If timer Tdiscon3 expires, the target BS may resend the A3-Remove message.

3
4
5

3.4.1.3.2

The A3-Remove Ack message is used by the source BS to notify the target BS that sent
the A3-Remove message of the outcome of processing the A3-Remove message.

9
10

11

3.4.1.3.2.1

13
14

Please refer to section 6.1.9.4, A3-Remove Ack, for the format and content of this
message.

15
16

3.4.1.3.2.2

3.4.1.3.3

A3-Drop
The purpose of the A3-Drop message is to indicate that the source BS is removing the
indicated A3 traffic subchannel, e.g., as a result of OAM&P intervention.

20
21

22

Failure Operation
None.

18

19

Successful Operation
The source BS sends an A3-Remove Ack message to the target BS that sent the A3Remove message to indicate the results of processing the A3-Remove message. The
Cause List element, when present, indicates any exceptions.

12

17

A3-Remove Ack

3.4.1.3.3.1

Successful Operation

25

The source BS may send an A3-Drop message to indicate that the A3 traffic subchannel
between the receiving BS and the source BS is about to be terminated. This is a
unilateral action taken by the source BS. An appropriate cause value shall be included.

26

Please refer to section 6.1.9.5, A3-Drop, for the format and content of this message.

23
24

27
28

3.4.1.3.3.2

Failure Operation
None.

204

TIA/EIA/IS-2001

3.4.2

UNUSED SECTION

3.4.3

A7 Interface Procedures and Messages

This section describes the messages and procedures used between base stations on an
A7 connection to support direct BS to BS soft/softer handoff, access handoff, access
probe handoff, and channel assignment into soft/softer handoff.

4
5
6

3.4.3.1

A7 Interface Messages

10

This section describes the messages and procedures used between base stations on an
A7 connection to support direct BS to BS soft/softer handoff, access handoff, access
probe handoff, and channel assignment into soft/softer handoff. These messages are:

11

A7-Handoff Request

12

A7-Handoff Request Ack

13

A7-Drop Target

14

A7-Drop Target Ack

15

A7-Target Removal Request

16

A7-Target Removal Response

17

A7-Paging Channel Message Transfer

18

A7-Paging Channel Message Transfer Ack

19

A7-Access Channel Message Transfer

20

A7-Access Channel Message Transfer Ack

21

A7-Burst Request

22

A7-Burst Response

23

A7-Burst Commit

24
25

The following A7 interface message may be received by any target BS if requested via
the A7-Handoff Request Ack message using the A7-Control element:

26

A7-Source Transfer Performed

27

The A7-Source Transfer Performed message is used as part of an optional feature. This
feature may only be needed for an IOS compliant BS that is integrated into a system that
includes equipment that does internal source transfers, i.e., transfers of the control of a
call from one source BS to another source BS. The source transfer procedure is not part
of the IOS. See informative annex B for more information.

8
9

28
29
30
31

32

3.4.3.1.1

The A7-Handoff Request message is used by the source BS to request that a target BS
allocate resources in one or more cells for support of a call association.

33
34

35
36
37

A7-Handoff Request

3.4.3.1.1.1

Successful Operation
When the source BS decides that one or more cells at a target BS are needed to support
one or more physical channel connections for a call, the source BS sends an A7-

205

TIA/EIA/IS-2001

Handoff Request message to the target BS to indicate the resources required. The
source BS then starts timer Thoreq.

1
2

Please refer to section 6.1.12.1, A7-Handoff Request, for the format and content of
this message.

3
4

3.4.3.1.1.2

If timer Thoreq expires, the source BS may choose to resend the A7-Handoff Request
message.

6
7

3.4.3.1.2

A7-Handoff Request Ack

The A7-Handoff Request Ack message is used by the target BS to respond to a request
that it allocate resources in one or more cells for support of one or more physical
channel connections for a call association.

9
10
11

12

Failure Operation

3.4.3.1.2.1

Successful Operation
When the target BS receives an A7-Handoff Request message, it determines what
internal resources are needed to support the requested physical channels for the call
association. Once those resources are allocated and the A3-Connect Ack message(s)
has been received, the target BS responds by sending an A7-Handoff Request Ack
message to the source BS.

13
14
15
16
17

NOTE: An implementation that internally transfers the control of a call from

one BSC to another may send an A7-Handoff Request message on one A7
connection, and then send an A7-Drop Target message on a different A7
connection. If a target BS chooses to be aware of the current source BS for a
call, it may indicate that using the A7-Control element on this message. See
informative annex B for more information.

18
19
20
21
22
23

Please refer to section 6.1.12.2, A7-Handoff Request Ack, for the format and content
of this message.

24
25

26

3.4.3.1.2.2

None.

27

28

3.4.3.1.3

30
31

33
34
35
36
37
38

A7-Drop Target
The A7-Drop Target message is used by the source BS to request that a target BS
deallocate resources in one or more cells currently being used for support of one or
more physical channel connections for a call association.

29

32

Failure Operation

3.4.3.1.3.1

Successful Operation
When the source BS decides that one or more cells at a target BS are no longer needed
to support one or more physical channel connections for a call association, the source
BS sends an A7-Drop Target message to the target BS to indicate the resources that are
no longer required. The source BS then starts timer Tdrptgt.
Please refer to section 6.1.12.3, A7-Drop Target, for the format and content of this
message.

206

TIA/EIA/IS-2001

3.4.3.1.3.2

If timer Tdrptgt expires, the source BS may choose to resend the A7-Drop Target
message.

2
3

3.4.3.1.4

6
7

3.4.3.1.4.1

11
12

Please refer to section 6.1.12.4, A7-Drop Target Ack, for the format and content of
this message.

13
14

3.4.3.1.4.2

3.4.3.1.5

19
20

3.4.3.1.5.1

23
24
25

The target BS shall indicate in this message on a cell by cell basis whether its request
may be denied by the source BS.

26
27

Please refer to section 6.1.12.5, A7-Target Removal Request, for the format and
content of this message.

28
29

3.4.3.1.5.2

32

34
35
36
37

Failure Operation
If timer Ttgtrmv expires, the target BS may choose to resend the A7-Target Removal
Request message.

31

33

Successful Operation
When the target BS decides that one or more cells can no longer be provided to support
for a call association, the target BS sends an A7-Target Removal Request message to
the source BS to indicate the resources that can no longer be provided. The target BS
then starts timer Ttgtrmv.

22

30

A7-Target Removal Request

The A7-Target Removal Request message is used by the target BS to request that a
source BS remove one or more cells currently being used for support of one or more
physical channel connections for a call association.

18

21

Failure Operation
None.

16

17

Successful Operation
When the target BS receives an A7-Drop Target message, it determines what resources
are no longer needed to support the call association. Once those resources are
deallocated, the target BS responds by sending an A7-Drop Target Ack message to the
source BS.

9
10

15

A7-Drop Target Ack

The A7-Drop Target Ack message is used by the target BS to respond to a request that
it deallocate resources in one or more cells currently being used for support of one or
more physical channel connections for a call association.

Failure Operation

3.4.3.1.6

A7-Target Removal Response

The A7-Target Removal Response message is used by the source BS to respond to a
request that it deallocate resources in one or more cells currently being used for support
of a call association. This message can be used by the source BS to either accept or
deny the request by the target BS that the cells be removed from the call association.

207

TIA/EIA/IS-2001

3.4.3.1.6.1

When the source BS receives an A7-Target Removal Request message, it determines

whether to remove the indicated cells from support of the call association. Once the
decision has been made and the MS has been instructed to remove appropriate entries
from its active set, the source BS responds by sending an A7-Target Removal
Response message to the target BS. The target BS stops timer Ttgtrmv.

2
3
4
5
6

Please refer to section 6.1.12.6, A7-Target Removal Response, for the format and
content of this message.

7
8

3.4.3.1.6.2

Failure Operation
None.

10

11

Successful Operation

3.4.3.1.7

UNUSED SECTION

3.4.3.1.8

UNUSED SECTION

3.4.3.1.9

UNUSED SECTION

3.4.3.1.10

A7-Source Transfer Performed

12

13
14

15
16

17

The A7-Source Transfer Performed message is used as part of an optional feature. This
feature may only be needed for an IOS compliant BS that is integrated into a system that
includes equipment that does internal source transfers, i.e., transfers of the control of a
call from one source BS to another source BS. The source transfer procedure is not part
of the IOS. See informative annex B for more information.

18
19
20
21
22

The A7-Source Transfer Performed message is sent by the old source BS to notify a
target BS that a source transfer procedure has occurred.

23
24

25

3.4.3.1.10.1

After a source transfer procedure has successfully completed, it is the responsibility of

the old source BS to notify all target BSs that request such notification of the identity of
the new source BS. This is accomplished by sending an A7-Source Transfer Performed
message to each target BS that expects such notification indicating the call connection
reference value and the identities of the old and new source BSs. No response is
expected.

26
27
28
29
30
31

When a target BS receives this message, it shall note the identity of the new source BS
for the call.

32
33

Please refer to section 6.1.12.10, A7-Source Transfer Performed, for the format and
content of this message.

34
35

36
37

Successful Operation

3.4.3.1.10.2

Failure Operation
None.

208

TIA/EIA/IS-2001

3.4.3.1.11

The A7-Paging Channel Message Transfer message is sent by a source BS to request

that a particular message be sent on the specified paging channel(s).

2
3

3.4.3.1.11.1

6
7

A Layer 2 acknowledgment indication can be requested. If such an acknowledgment is

received from the MS, an A7-Paging Channel Message Transfer ACK message is used
to convey that information back to the source BS. If a Layer 2 acknowledgment
indication is requested by the source BS, it starts timer Tpcm.

8
9
10
11

When a BS receives this message, it shall complete any final formatting of the contained
message and then send the message to the MS on the specified paging channel(s). If a
Layer 2 acknowledgment is requested by the source BS, the message sent to the MS
shall request a Layer 2 acknowledgment from the MS.

12
13
14
15

Please refer to section 6.1.12.13, A7-Paging Channel Message Transfer for the format
and content of this message.

16
17

3.4.3.1.11.2

20

3.4.3.1.12

23
24

3.4.3.1.12.1

27
28
29

When a Layer 2 acknowledgment arrives from the MS, the BS sends the A7-Paging
Channel Message Transfer Ack message to convey that information to the BS that had
requested the Layer 2 acknowledgment. If the internal Layer 2 timer at the BS expires,
this message is also sent conveying the fact that the Layer 2 acknowledgment timeout
has occurred.

30
31
32
33
34

Please refer to section 6.1.12.14, A7-Paging Channel Message Transfer Ack for the
format and content of this message.

35
36

38

Successful Operation
When an A7-Paging Channel Message Transfer message containing a request for a
Layer 2 acknowledgment is received by a BS, the BS transmits the paging channel
message to the MS with a Layer 2 acknowledgment request included and starts its
internal timer to await the Layer 2 acknowledgment.

26

37

A7-Paging Channel Message Transfer Ack

The A7-Paging Channel Message Transfer Ack message is used to respond to a
request for a Layer 2 acknowledgment included in an A7-Paging Channel Message
Transfer message.

22

25

Failure Operation
If timer Tpcm expires, the source BS may choose to send this message again, or may
initiate failure handling.

19

21

Successful Operation
When a source BS wishes to send a message to a mobile station on the paging
channel(s) of another BS, it encapsulates that message in an A7-Paging Channel
Message Transfer message and sends it to the other BS.

18

A7-Paging Channel Message Transfer

3.4.3.1.12.2

Failure Operation
None.

209

TIA/EIA/IS-2001

3.4.3.1.13

The A7-Access Channel Message Transfer message is sent by a target BS to the

source BS to notify the source BS of the reception of an access channel message when
the access channel message contains an access handoff list that indicates that the
receiving BS is not the first accessed BS.

2
3
4
5

3.4.3.1.13.1

8
9
10
11
12

The source BS will send an acknowledgment for this message to the target BS using the
A7-Access Channel Message Transfer Ack message.

13
14

Please refer to section 6.1.12.15, A7-Access Channel Message Transfer, for the format
and content of this message.

15
16

3.4.3.1.13.2

3.4.3.1.14

21
22

3.4.3.1.14.1

25
26
27

Please refer to section 6.1.12.16, A7-Access Channel Message Transfer Ack, for the
format and content of this message.

28
29

3.4.3.1.14.2

3.4.3.1.15

34

36
37
38
39
40

A7-Burst Request
The A7-Burst Request message is used by the source BS to request that a target BS
reserve a set of radio resources in support of a traffic burst.

33

35

Failure Operation
None.

31

32

Successful Operation
When the source BS receives the A7-Access Channel Message Transfer message from
the target BS, it shall send an acknowledgment for this message to the target BS using
the A7-Access Channel Message Transfer Ack message. The target BS stops timer
Tacm.

24

30

A7-Access Channel Message Transfer Ack

The A7-Access Channel Message Transfer Ack message is sent by the source BS to
acknowledge the A7-Access Channel Message Transfer message received from the
target BS.

20

23

Failure Operation
If timer Tacm expires, the target BS may resend this message.

18

19

Successful Operation
When a BS (target BS) receives an access channel message containing an access
handoff list that indicates that the receiving BS is not the first attempted BS (i.e., is not
the source BS), it shall encapsulate that message in the A7-Access Channel Message
Transfer message, forward it to the source BS, and start timer Tacm. The target BS is
responsible for sending the Layer 2 acknowledgment for such forwarded access
channel messages.

17

A7-Access Channel Message Transfer

3.4.3.1.15.1

Successful Operation
When the source BS determines that a traffic burst is required in support of a particular
service instance, it determines the cells needed to support the traffic burst and sends an
A7-Burst Request to the target BS. This message requests that the target BS reserve
the indicated radio resources for a traffic burst beginning at a particular time and for a
particular duration. This message may also be used to request an extension of an

210

TIA/EIA/IS-2001

existing traffic burst by specifying the appropriate beginning and duration times. The
source BS then starts timer Tbstreq.

1
2

Please refer to section 6.1.12.17, A7-Burst Request, for the format and content of this
message.

3
4

3.4.3.1.15.2

If timer Tbstreq expires, the source BS may choose to resend the A7-Burst Request
message.

6
7

3.4.3.1.16

3.4.3.1.16.1

13
14
15
16
17
18
19
20
21
22

Please refer to section 6.1.12.18, A7-Burst Response, for the format and content of
this message.

23
24

3.4.3.1.16.2

27

3.4.3.1.17

30

32
33
34
35
36
37
38
39
40
41

A7-Burst Commit
The A7-Burst Commit message is used by the source BS to indicate to the target BS the
set of target radio resources that will be used to support a traffic burst.

29

31

Failure Operation
If timer Tbstcom expires, the target BS may decommit all radio resources committed for
the cell(s) included in this message.

26

28

Successful Operation
When the target BS receives an A7-Burst Request message, it determines whether it can
provide the requested radio resources in support of the traffic burst. If a traffic burst for
the same service instance was already committed (and possibly active) at the time the
A7-Burst Request message is received, the target BS shall examine the starting time and
duration, as well as the set of requested resources to determine if this request extends
the traffic burst. The target BS then creates one or more A7-Burst Response
message(s) indicating its ability to support the requested traffic burst for each of the
cells included in the A7-Burst Request message. The target BS starts timer Tbstcom
after each A7-Burst Response message. The source BS stops timer Tbstreq when it
receives A7-Burst Response message(s) accounting for all cells included in the A7Burst Request message.

12

25

A7-Burst Response
The A7-Burst Response message is used by the target BS to respond to a request that
it reserve radio resources in one or more cells for support of a traffic burst.

9
10

11

Failure Operation

3.4.3.1.17.1

Successful Operation
When the source BS has gathered traffic burst commitment information from target BSs
and has prepared the frame selector(s) to support the traffic burst, it sends an A7-Burst
Commit message to the target BSs to indicate the set of committed target radio
resources that will be used to support the traffic burst.
When the target BS receives this message, it shall prepare all indicated resources for
support of the traffic burst. Any resources that were reserved but are not included in
this message may be decommitted by the target BS. This includes bandwidth and burst
duration. The target BS stops timer Tbstcom.
Please refer to section 6.1.12.19, A7-Burst Commit, for the format and content of this
message.

211

TIA/EIA/IS-2001

1
2

3.4.3.1.17.2

Failure Operation
None

212

TIA/EIA/IS-2001

3.4.4

The source BS decides what cells are to be added to a call in soft/softer handoff. An
A7-Handoff Request message is sent directly to the target BS across the A7 connection
between the source and target BSs to request the addition of those cells to the call. The
target BS allocates and connects the appropriate resources and responds directly to the
source BS using an A7-Handoff Request Ack message once all expected A3-Connect
Ack messages have been received.

2
3
4
5
6
7

The A3-Connect message is used by the target BS to both create new A3 connections
for a call, and to add cells to existing A3 connections. In either case, information on all
cells attached to the A3 connection shall be included in the A3 Connect Information
element, and there shall be an indication as to which cells were already existing and
which cells were newly associated with the A3 connection.

8
9
10
11
12

The A3-Connect message can be used to establish multiple A3 connections. To

support this capability, multiple sets of cell information may be included. A single A3Connect Ack message is used to respond to an A3-Connect message, regardless of the
number of A3 connections being established via the A3-Connect message. The A3Connect Ack message is returned to the address from which the A3-Connect message
was sent.

13
14
15
16
17
18

In response to an A7 Handoff Request message that includes multiple cells to be added

to the call association in soft or softer handoff, the target BS may send a single A3Connect message including information for multiple connections, or it may send
multiple A3-Connect messages where each message includes information for a single
connection only. However, the target BS shall not send multiple A3-Connect messages
that each include multiple connection information, nor any combination of such
messages and A3-Connect messages that include information for a single connection.
The requirements of this paragraph may be relaxed in a future revision of this standard.

19
20
21
22
23
24
25
26

The A3-Connect Ack and A3-Traffic Channel Status messages support the ability of
the source BS to request that the target BS send a notification that the target BS
transmitter(s) and receiver(s) are turned on.

27
28
29

30

3.4.5

32
33
34
35

37
38
39
40
41
42
43
44

Soft/softer Handoff Removal

Removal of cells in soft/softer handoff involves the sending by the source BS of an A7Drop Target message to the target BS. The target BS removes the indicated cells and
responds with an A7-Drop Target Ack message. If the last cell(s) attached to a
particular A3 connection are removed, the target BS will initiate removal of that A3
connection also.

31

36

Soft/Softer Handoff Addition

3.4.6

Cell Removal by a Target BS

For a variety of reasons, a target BS may need to request that one or more of its cells be
removed from a call. This request can be for reasons of internal resource management,
OA&M, internal BS error situations, etc. The target BS, in these cases, sends an A7Target Removal Request message to the source BS with appropriate information to
indicate what cells need to be removed from the call, and for what reason(s). The
source BS takes appropriate actions and responds with an A7-Target Removal
Response message. It may be possible that the source BS would indicate to the target
BS that the target cell(s) must remain in the call.

213

TIA/EIA/IS-2001

3.4.7

Call clearing for calls using packet based soft/softer handoff is always accomplished via
the source BS. If the call clearing is initiated by either the MS or source BS, a Clear
Request message will be sent to the MSC to request call clearing. If the MSC initiates
the call clearing, it sends a Clear Command message to the source BS. Clear Command
messages are not sent to target BSs involved in the call. Instead, the source BS is
responsible for using the A7 interface drop target procedure to remove all target BSs
from the call prior to sending the Clear Complete message to the MSC.

2
3
4
5
6
7
8

3.4.8

11

See also sections 3.3.1.3 Concept of Designated Cell and 3.3.3.1 Handoff
Performed.

12
13

15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

Handoff Performed
The source BS is responsible for sending Handoff Performed messages to the MSC to
keep it informed of the identity of the cells currently involved in supporting the call.

10

14

Call Clearing

3.4.9

Access Handoff and Channel Assignment into Soft Handoff

In addition to setting up soft handoff legs during a call, the soft handoff legs can also
be setup during the establishment of the call. This procedure is required to support the
access probe handoff, access handoff, and channel assignment into soft/softer handoff.
The source BS decides what cells are to be setup in soft/softer handoff during the
establishment of the call and the A7-Handoff Request procedure is used. That is, an
A7-Handoff Request message is sent directly to the target BS across the A7 connection
between the source and target BSs to request the setup of those cells to the call. The
target BS allocates and connects the appropriate resources and responds directly to the
source BS using an A7-Handoff Request Ack message once all expected A3-Connect
Ack messages have been received.
Cells that are likely candidates for access probe handoff and access handoff by the MS
are included in the ACCESS_HO_LIST.
For each message received on one of its access channels, the BS shall analyze the
PILOT_RECORD if such a record is included in the message. If the BS does not
correspond to the first attempted pilot in the record (i.e., is not the source BS), then it
shall forward the access channel message on an inter-BS (i.e., A7) link corresponding to
the first attempted pilot in the record. If the access channel message is an Origination
or Page Response, the BS shall forward the message as indicated above and shall not
send the corresponding CM Service Request message or Paging Response message to
the MSC.
The source BS sends A7-Paging Channel Message Transfer messages carrying an
appropriate channel assignment information to selected BSs, usually chosen from those
contained in the ACCESS_HO_LIST and OTHER_REPORTED_LIST, requesting that
they send the channel assignment message on specific cells. The channel assignment
message is used to assign the forward channel(s) to the MS.
The set of BSs to which the source BS sends the A7 Paging Channel Message Transfer
message may be different from the set of BSs that are set up in soft handoff.
See section 2.2.2.2 for an example scenario showing access probe handoff, access
handoff and channel assignment into soft/softer handoff.

214

TIA/EIA/IS-2001

1
2
3

See also sections 3.4.3.1.11 through 3.4.3.1.14 for information on the A7-Paging Channel
Message Transfer, A7-Paging Channel Message Transfer Ack, A7-Access Channel
Message Transfer, and A7-Access Channel Message Transfer Ack messages.

215

TIA/EIA/IS-2001

3.4.10

Support of high speed packet data (i.e., speeds greater than 14.4 kbps) may be
accomplished through the use of multiple physical channels. These physical channels are
supported in the infrastructure using A3 traffic connections during soft/softer handoff.
Setup of an A3 connection for a traffic burst is accomplished using A7-Burst Request,
A7-Burst Response, and A7-Burst Commit messages. Establishment of the A3 connection
for the supplemental channel (SCH) is accomplished via the A7-Handoff Request,
A7Handoff Request Ack, A3-Connect and A3-Connect Ack messages.

2
3
4
5
6
7
8

In this version of this standard, it is assumed that any leg for a supplemental channel will
be established on a cell that already supports a leg for the fundamental channel (FCH) or
the dedicated control channel (DCCH) for the same mobile station. To minimize the time
required to establish a traffic burst, the A3 connection for the SCH is established on the
target BS at the transmission of the first data burst. When a leg is established for a SCH,
only the terrestrial resources are allocated, i.e., the A3 connection. This involves
choosing the traffic circuit to be used and establishing context between the target BS and
the source BS/SDU function. Allocation of radio resources for the SCH is made each time
that a traffic burst is set up.

9
10
11
12
13
14
15
16
17

When the source BS realizes that it is necessary to allocate radio resources for a traffic
burst in either the forward or reverse direction or both, it sends an A7-Burst Request
message to each target BS to request reservation of specific radio resources. Each target
BS responds with an A7-Burst Response message to indicate radio resource reservations.
Once the source BS has received all expected A7-Burst Response messages, it sends an
A7-Burst Commit message to each target BS to confirm the traffic burst and the set of
radio resources to be used. Each target BS then prepares all indicated cells, connects
them to the pre-established A3 connections, and then participates in the burst. This is
shown in the example in section 3.5.2.3.

18
19
20
21
22
23
24
25
26

27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

Soft/Softer Handoff of High Speed Packet Data

3.4.10.1

Soft/Softer Handoff of Forward Link Bursts of Data

When a traffic burst is scheduled to begin, the SDU function begins to transmit forward
link frames carrying user traffic on the A3 connection for the SCH. At the termination of a
traffic burst in the forward direction, the SDU function ceases transmitting frames on the
SCH A3 connection. The SDU function may begin to send idle frames on the forward A3
connection prior to the beginning of the burst to allow synchronization of the A3
connection. If the target BS receives forward idle frames and is not receiving reverse
frames from the MS, it shall send reverse idle frames to the SDU function to allow packet
arrival time error adjustments to occur.
When a new traffic burst is initiated on an A3 connection for a SCH, the target BS shall
wait for the first forward link frame before transmitting any reverse link frames. If the
target BS receives a forward link Idle Frame, it shall calculate the packet arrival time error
and transmit that information on the reverse link in an Idle Frame if it has no user traffic to
transmit in a non-idle frame. The target BS shall not transmit any air interface frame when
receiving a forward link Idle Frame. In this way, the SDU function can control precisely
the beginning of forward link traffic bursts on physical channels.
The source BS may suppress (i.e., not transmit) an A3-IS-2000 SCH Forward message
with Forward Layer 3 Data elements containing Null or Idle frame contents. See section
6.2.2.76 (IS-2000 Frame Content) for Source and Target operations with Null and Idle
frames.

216

TIA/EIA/IS-2001

The target BS may suppress (i.e., not transmit) an A3-IS-2000 SCH Reverse message with
Reverse Layer 3 Data information elements containing Null or Idle frame contents if, and
only if, an A3-IS-2000 SCH Forward message was not received in the previous air-frame
period. See section 6.2.2.76 (IS-2000 Frame Content) for Source and Target operations
with Null and Idle frames.

1
2
3
4
5

6
7
8
9
10
11
12
13
14

3.4.10.2

Soft/Softer Handoff of Reverse Link Bursts of Data

When a traffic burst is expected by a target BS, the target BS shall wait as indicated
above for the first forward link frame so that the packet arrival time error can be correctly
calculated. Following reception of the first forward link frame at the target BS, the target
BS shall begin transmitting reverse link frames which may be frames containing user
traffic (i.e., packet data), Idle Frames, Null Frames, or Erasure Frames. The SDU
function, being aware of the specified beginning and end times for each traffic burst
from the mobile station, can properly decide whether Erasure Frames should be
considered as Idle Frames.

217

TIA/EIA/IS-2001

3.5

Handoff Call Flows

3.5.1

UNUSED SECTION

3.5.2

Handoff Call Flows

3.5.2.1

Hard Handoff (via MSC)

3.5.2.1.1

Successful Hard Handoff

3
4

7
8

The following call flow diagram provides an illustration for a successful hard handoff
event. It is assumed that the call is not in inter-BS soft/softer handoff prior to the hard
handoff, and thus no A3 connections need to be removed.

10
11
12

MS

Source BS

MSC

Target BS

Handoff Required

Time

a
Handoff Request

T7

b
Null forward traffic channel frames

T711
c

Handoff Request Ack

Handoff Command

d
e

Handoff Direction Message

f
MS Ack Order

T9

Twaitho
x Handoff Commenced

g
h

Reverse Traffic Channel Frames or Traffic Channel Preamble

Handoff Completion Message

j

BS Ack Order

k
Handoff Complete

T306
Clear Command
Clear Complete

T315

13
14

Figure 3- 1 - Successful Hard Handoff

218

l
m
n

Comment

TIA/EIA/IS-2001

a.

Based on an MS report that it crossed a network specified threshold for signal

strength or for other reasons, the source BS recommends a hard handoff to one or
more cells in the domain of the target BS. The source BS sends a Handoff Required
message with the list of cells to the MSC and starts timer T7.

b.

The MSC sends a Handoff Request message to the target BS with the TIA/EIA-95
Channel Identity element present since the hard handoff bit was set and/or the
Handoff Type element in the Handoff Required message indicated hard handoff. The
MSC starts timer T11.

2
3
4
5
6
7
8

In the case of hard handoff for an async data/fax call, the Circuit Identity Code
Extension element in the Handoff Request message indicates the Circuit Identity
Code of the circuit to be connected to the SDU function at the target BS to support
the A5 connection to the IWF.

9
10
11
12
13

c.

Upon receipt of the Handoff Request message from the MSC, the target BS allocates
appropriate radio resources as specified in the message and connects the call. The
target BS sends null forward traffic channel frames to the MS.

d.

The target BS sends a Handoff Request Acknowledge message to the MSC. The
target BS starts timer T9 to wait for arrival of the MS on its radio channel.

14
15
16
17

If the service option received in the Handoff Request message is not available at the
target BS and the target BS selected a different service option for the handoff then
the target BS shall include the service option it selected in the Service Configuration
Record IE.

18
19
20
21
22

e.

Upon receipt of the Handoff Request Acknowledge message the MSC stops timer
T11. The MSC prepares to switch from the source BS to the target BS and sends a
Handoff Command to the source BS. The source BS stops timer T7. The MSC shall
include the service option it received from the Handoff Request Acknowledgement
message in the Handoff Command message.

f.

The source BS sends the handoff direction message3 to the MS across the air
interface. If the MS is allowed to return to the source BS, then timer Twaitho is also
started by the source BS.

g.

The MS may acknowledge the handoff direction message by sending a MS Ack

Order to the source BS.

23
24
25
26

27
28
29
30
31

If the handoff direction message is sent using quick repeats, the source BS might not
request an acknowledgment from the.

32
33
34

h.

The source BS sends a Handoff Commenced message to the MSC to notify it that
the MS has been ordered to move to the target BS channel. The source BS starts
timer T306 to await the Clear Command message from the MSC. If timer Twaitho has
been started, the source BS shall wait for that timer to expire before sending the
Handoff Commenced message.

i.

The MS sends reverse traffic channel frames or the traffic channel preamble to the
target BS.

35
36
37
38
39
40

3 This may be a Handoff Direction Message, a General Handoff Direction Message, an

Extended Handoff Direction Message, or a Universal Handoff Direction Message as

appropriate.

219

TIA/EIA/IS-2001

j.

The MS sends a Handoff Completion Message to the target BS.

k.

The target BS sends the BS Ack Order to the MS over the air interface.

l.

The target BS sends a Handoff Complete message to the MSC to notify it that the
MS has successfully completed the hard handoff. The target BS stops timer T9.

m.

The MSC sends a Clear Command to the source BS. The source BS stops timer
T306. The MSC starts timer T315.

4
5
6

In the case of hard handoff for an async data/fax call, clearing of all resources
including the A5 connection at the old BS is accomplished via the Clear Command
message.

7
8
9

n.

10
11

12

3.5.2.1.2

The source BS sends a Clear Complete message to the MSC to notify it that clearing
has been accomplished. The MSC stops timer T315.

Successful Hard Handoff to ANSI/EIA/TIA-553 Systems

For the purpose of this specification, the single MSC in the following figure represents
the source and the target MSC connected by TIA/EIA IS-41. The message flows
between the target MSC and the target BS in the figure are not required.

13
14
15

The following call flow diagram provides an illustration for a successful hard handoff
event to a ANSI/EIA/TIA-553 system.

16
17

Source
BS

MS

Target
BS

MSC

Handoff Required

a
Handoff Request

T7

time

T11
Handoff Request Ack
Handoff Command
T9

Analog Handoff Direction Msg

Acknowledge Order

b
c
d
e
f

Handoff Commenced
g
Transponded SAT
h

T306

Handoff Complete
Clear Command

Clear Complete

i
j

T315
k

18
19
20

Figure 3- 2 - Successful Hard Handoff to a ANSI/EIA/TIA-553 System

220

comment

TIA/EIA/IS-2001

Based on an MS report that it has crossed a network specified threshold for signal
strength, the source BS recommends a hard handoff to one or more cells in the
domain of the target BS. The source BS sends a Handoff Required message with the
Cell Identifier List to the MSC to find a target with available resources. The source
BS indicates a response requirement by including the Response Request element.

The source BS then starts timer T7.

a.

2
3
4

b.

The MSC sends a Handoff Request message to the target BS with the neither the IS95 nor IS-2000 Channel Identity element present since this is a CDMA to Analog
hard handoff request. The MSC starts timer T11.

c.

11

The target BS determines that appropriate resources are available and returns a
Handoff Request Acknowledge message to the MSC.

12

The target BS then starts timer T9.

7
8
9
10

15

Upon receipt of the Handoff Request Acknowledge message from the target BS, the
MSC stops T11 and sends a Handoff Command message to the source BS to convey
information from the target BS to the source BS.

16

Timer T7 is stopped when a Handoff Command message is received.

13

d.

14

17

e.

Upon receipt of the Handoff Command message from the MSC, the source BS
transmits the Analog Handoff Direction Message to the MS requesting Layer 2
acknowledgment.

f.

The MS returns an MS Ack Order to the source BS to confirm receipt of the Analog
Handoff Direction Message.

g.

The source BS sends a Handoff Commenced message to the MSC to notify it that
the MS has been ordered to move to the target BS channel. The source BS starts
timer T306 to await the Clear Command from the MSC.

h.

The MS tunes to the target BS SAT and initiates transmission of transponded SAT.

18
19
20
21
22
23
24
25

The target BS stops timer T9.

26
27

i.

Upon reception of the correct MS transponded SAT, the target BS sends a Handoff
Complete message to the MSC to indicate that the MS has successfully accessed
the target BS.

j.

The MSC releases the source BSs terrestrial circuit and instructs the source BS to
release its radio resources by sending a Clear Command message to the source BS
with the Cause element set to Handoff successful. The MSC starts timer T315.
The source BS stops timer T306 when the Clear Command message is received.

k.

The source BS releases its source channel, clears any terrestrial resources, and then
returns a Clear Complete message to the MSC to indicate that the transition is
complete. The MSC stops timer T315 when the Clear Complete message is received.

28
29
30
31
32
33
34
35
36

221

TIA/EIA/IS-2001

2
3
4
5
6
7
8
9
10

3.5.2.1.3

Unsuccessful Hard Handoff to ANSI/EIA/TIA-553: ANSI/EIA/TIA-553

Alternative Rejected
For the purpose of this specification, the single MSC in the following figure represents
the source and the target MSC connected by TIA/EIA IS-41. The message flows
between the target MSC and the target BS in the figure are informative and are not
required.
The following call flow diagram provides an illustration of an unsuccessful Hard
Handoff. In this example, the source BS determines that an ANSI/EIA/TIA-553
alternative is not acceptable, rejects the Handoff Command and maintains the mobile.
MS

Source
BS

MSC

Target
BS

Handoff Required

T11
Handoff Request Ack

Handoff Command
Handoff Failure

b
c
d

T9
e
Clear Command

T315

comment

a
Handoff Request

T7

time

Clear Complete

f
g

11

13

Figure 3- 3 - Unsuccessful Hard Handoff to ANSI/EIA/TIA-553: ANSI/EIA/TIA-553

Alternative Rejected

14

a.

12

18

Based on an MS report that it has crossed a network specified threshold for signal
strength, the source BS recommends a hard handoff to one or more cells in the
domain of the target BS. The source BS sends a Handoff Required message with the
Cell Identifier List to the MSC to find a target with available resources. The source
BS indicates a response requirement by including the Response Request element.

19

The source BS then starts timer T7.

15
16
17

20

b.

The MSC constructs a preferred list of targets for polling and sends a Handoff
Request message to the target BS with neither the IS-95 nor the IS-2000 Channel
Identity element present since the hard handoff bit is set. The MSC starts timer T11.

c.

The target BS determines that a channel resource is not available and reserves or
allocates an ANSI/EIA/TIA-553 channel. The target BS then sends a Handoff
Request Acknowledge message to the MSC informing it of the availability of the
ANSI/EIA/TIA-553 channel. The target BS then starts timer T9.

21
22
23
24
25
26

222

TIA/EIA/IS-2001

d.

2
3
4

Upon receipt of the Handoff Request Acknowledge message from the target BS, the
MSC stops T11 and sends a Handoff Command message to the source BS to convey
information from the target BS to the source BS. In the Handoff Command, the
Handoff Type element, if present, shall be set to CDMA-Analog Hard HO.
Timer T7 is stopped at the source BS when a Handoff Command message is
received, or a Reset message is received.

5
6

e.

Upon receipt of the Handoff Command message from the MSC, the source BS
recognizes that an ANSI/EIA/TIA-553 channel has been supplied and decides to
reject the assignment. The source BS keeps the MS and sends a Handoff Failure
message to the MSC with the Cause element set to Alternate signaling type reject.

f.

13

The MSC releases the target BSs terrestrial circuit and instructs the target BS to
release its radio resources by sending a Clear Command message to the target BS
and starts timer T315.

14

The target BS stops timer T9.

7
8
9
10
11
12

15
16
17
18

g.

Upon receipt of the Clear Command message from the MSC, the target BS releases
its radio resource. The target BS then returns a Clear Complete message to the MSC
to indicate that the resource release operation is complete. The MSC stops timer
T315 when the Clear Complete message is received.

223

TIA/EIA/IS-2001

3.5.2.1.4

Hard Handoff With Return On Failure

The following call flow diagram provides an illustration for a hard handoff event. In this
scenario the mobile station successfully returns to the source BS after hard handoff
fails. It is assumed that the call is not in inter-BS soft/softer handoff prior to the hard
handoff, and thus no inter-BS connections need to be removed.

2
3
4
5

MS

Source BS

MSC

Target BS

Handoff Required

Time

Comment

a
Handoff Request

T7

b
T11
7
Handoff Request Ack

Null forward traffic channel frames

Handoff Command

c
d
e

hHandoff Ddirection mMessage

f
T8

MS Ack Order
CF Search Report Message

T9

Twaitho

g
h

Handoff Failure
i
Clear Command
T315

Clear Complete

j
k

6
7

Figure 3- 4 Hard Handoff With Return On Failure

a.

Based on an MS report that it crossed a network specified threshold for signal

strength or for other reasons, the source BS recommends a hard handoff to one or
more cells in the domain of the target BS. The source BS sends a Handoff Required
message with the list of cells to the MSC and starts timer T7.

b.

The MSC sends a Handoff Request message to the target BS with the IS-95 Channel
Identity element present since the hard handoff bit was set and/or the Handoff Type
element in the Handoff Required message indicated hard handoff. The MSC starts
timer T11.

9
10
11
12
13
14
15

In the case of hard handoff for an async data/fax call, the Circuit Identity Code
Extension element in the Handoff Request message indicates the Circuit Identity
Code of the circuit to be connected to the SDU function at the target BS to support
the A5 connection to the IWF.

16
17
18
19
20
21
22

c.

Upon receipt of the Handoff Request message from the MSC, the target BS allocates
appropriate radio resources, as specified in the message, and connects it to the
terrestrial circuit. The target BS sends null forward traffic channel frames to the MS.

224

TIA/EIA/IS-2001

d.

The target BS sends a Handoff Request Acknowledgment message to the MSC. The
target BS starts timer T9 to wait for arrival of the MS on its radio channel.

e.

Upon receipt of the Handoff Request Acknowledge message the MSC stops timer
T11. The MSC prepares to switch from the source BS to the target BS and sends a
Handoff Command to the source BS. The source BS stops timer T7.

f.

The source BS sends the handoff direction message 4 to the MS across the air
interface. The source BS indicates in the message that the MS is permitted to return
to the source BS if handoff to the target fails. The source BS starts timer Twaitho.

g.

The MS may acknowledge the handoff direction message by sending a MS Ack

Order to the source BS.

2
3
4
5

6
7
8
9
10

If the handoff direction message is sent using quick repeats, the source BS might not
request an acknowledgment from the MS.

11
12
13

h.

The MS sends a Candidate Frequency (CF) Search Report Message to the source BS
after handoff to the target has failed. The source BS stops timer Twaitho.

i.

Upon receipt of the CF Search Report Message from the MS the source BS detects
that the MS has never accessed the target BS cell and sends a Handoff Failure
message to the MSC with the Cause element set to Reversion to old channel.

j.

The MSC sends a Clear Command to the target BS. The target BS stops timer T9.
The MSC starts timer T315.

k.

Upon receipt of the Clear Command message from the MSC, the target BS releases
and deallocates radio and terrestrial resources.

14
15
16
17
18
19
20
21
22
23

The target BS then sends a Clear Complete message to the MSC. The MSC stops
timer T315.

4 This may be a Handoff Direction Message, a General Handoff Direction Message, an

Extended Handoff Direction Message, or a Universal Handoff Direction Message as

appropriate.

225

TIA/EIA/IS-2001

3.5.2.3

Soft/softer Handoff Using Direct BS to BS (A3 and A7) Connections

3.5.2.3.1

Soft/softer Handoff Addition

Soft/softer handoff addition occurs as shown in the following diagram. Soft/softer

handoff addition includes both the creation of new A3 connections, as well as the
addition of cells to existing A3 connections. In this section, A3-CEData
Forward/Reverse messages represent A3-IS-95 FCH Forward/Reverse, A3-IS-2000
FCH Forward/Reverse, or A3-IS-2000 DCCH Forward/Reverse messages. For SCH
soft/softer handoff addition, see Sections 3.5.2.3.6 and 3.5.2.3.7.

4
5
6
7
8
9

MS

Source BS

MSC

Target BS

Time

Comment

A7- Handoff Request

a
A3-Connect

Thoreq

b
Tconn3

A3-Connect Ack

c
A3-CEData Forward (Forward Frames)
Forward Frames

d
e

A3-CEData Reverse (Idle Frames)

A7- Handoff Request Ack

g
A3-Traffic Channel Status
h
Hhandoff Ddirection Mmessage
i

Conditional:
(See IS-634.1
section
3.4.1.1.2)

MS Ack Order
j
Handoff Completion Message
k
BS Ack Order
l
Handoff Performed
m
10
11

Figure 3- 5 - Soft/softer Handoff Addition

226

Conditional:
(See IS-634.1
section
3.3.1.3)

TIA/EIA/IS-2001

a.

The source BS decides that one or more cells at the target BS are needed to
support the call in soft/softer handoff. The source BS sends an A7-Handoff
Request to the target BS and starts timer Thoreq.

b.

The target BS initiates an A3 connection by sending an A3-Connect message

to the specified address. Note that a single A7-Handoff Request message may
result in multiple A3 connections being established, each using a separate A3Connect message. This example shows only a single A3 connection being
established.

c.

The source BS replies with a A3-Connect Ack message to complete the A3

connection or to acknowledge the addition of cells to an existing A3
connection.

12

d.

The source BS begins to send forward frames to the target BS.

13

e.

The target BS begins to transmit the forward frames as soon as

synchronization has occurred.

f.

The target BS begins to send reverse idle frames as soon as the first forward
frame is received from the source BS. The reverse frames contain the timing
adjustment information necessary to achieve synchronization.

g.

The target BS sends an A7-Handoff Request Ack message to the source BS to

indicate the success of the cell addition(s). The source BS stops timer Thoreq.

h.

If the source BS has chosen to be notified of the start of transmission and

reception at the target BS, when its SDU function and the target BS have
synchronized the A3 traffic subchannel, the target BS replies with an A3Traffic Channel Status message. See also section 3.4.1.1.2 A3-Connect Ack.
Note that this step may occur any time after step (d).

i.

The source BS sends a handoff direction message5 to the mobile station to

add the new cell(s) to the active set.

j.

The mobile station acknowledges receipt of the handoff direction message

with an MS Ack Order.

k.

The mobile station indicates successful results of processing the handoff

direction message by sending a Handoff Completion Message.

l.

The source BS acknowledges receipt of the Handoff Completion Message by

sending a BS Ack Order.

1
2
3
4
5
6
7
8
9
10
11

14
15
16
17
18
19
20
21
22
23
24

25
26
27
28
29
30
31
32

m. The source BS may send a Handoff Performed message to the MSC. See
section 3.3.1.3 Concept of A Designated Cell. The Handoff Performed
message may be sent any time after the Handoff Completion Message is
received by the BS.

33
34
35
36

37

3.5.2.3.2

UNUSED SECTION

38

5 This may be a Handoff Direction Message, a General Handoff Direction Message, an

Extended Handoff Direction Message, or a Universal Handoff Direction Message as

appropriate.

227

TIA/EIA/IS-2001

3.5.2.3.3

Soft/softer Handoff Removal

Soft/softer handoff removal occurs as shown in the following diagram. In this section,
A3-CEData Forward/Reverse messages represent A3-IS-95 FCH Forward/Reverse,
A3-IS-2000 FCH Forward/Reverse, or A3-IS-2000 DCCH Forward/Reverse
messages.

2
3
4
5

MS

Source BS

MSC

Target BS

Time

Comment

A3-CEData Forward (HO Dir. Msg.)

a
Handoff Direction Message
b
MS Ack Order
c
A3-CEData Reverse (MS Ack Order)
d
Handoff Completion Message

BS Ack Order

f
A7-Drop Target
g
A3-Remove
h

Tdrptgt

Tdiscon3

A3-Remove Ack

i
A7-Drop Target Ack

Handoff Performed
k

Conditional:
(See 3.3.1.3)

6
7

Figure 3- 6 - Soft/softer Handoff Removal

a.

The source BS sends a handoff direction message6 in an A3-CEData Forward

message to the target BS to be sent to the mobile station to drop one or more
cell(s) from the active set.

b.

The source BS and target BS transmit the handoff direction message to the
mobile station.

c.

The mobile station acknowledges receipt of the handoff direction message

with an MS Ack Order transmitted to both the source and target BSs.

d.

The target BS relays the MS Ack Order to the source BS in an A3-CEData

Reverse message.

e.

The mobile station indicates successful results of processing the handoff

direction message by sending a Handoff Completion Message.

9
10
11
12
13
14
15
16
17
18

6 This may be a Handoff Direction Message, a General Handoff Direction Message, an

Extended Handoff Direction Message, or a Universal Handoff Direction Message as

appropriate.

228

TIA/EIA/IS-2001

f.

The source BS acknowledges receipt of the Handoff Completion Message by

sending a BS Ack Order.

g.

The source BS sends an A7-Drop Target message to the target BS to request

that the specified cells be removed from the call. The source BS starts timer
Tdrptgt.

h.

The target BS, upon receipt of the A7-Drop Target message, deallocates
internal resources related to the specified cells. The target BS sends an A3Remove message to the SDU function of the source BS and starts timer
Tdiscon3.

i.

The SDU function of the source BS replies with an A3-Remove Ack message
and deallocates internal resources. The target BS stop timer Tdiscon3.

j.

The target BS sends an A7-Drop Target Ack message to the source BS to

acknowledge the removal of the specified cells. The source BS stops timer
Tdrptgt.

k.

The source BS may send a Handoff Performed message to the MSC. See
section 3.3.1.3 Concept of A Designated Cell. The Handoff Performed
message may be sent any time after the Handoff Completion Message is
received by the BS.

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

19

3.5.2.3.4

UNUSED SECTION

20

229

TIA/EIA/IS-2001

3.5.2.3.5

Cell Removal by a Target BS

The example below shows a Target Removal initiated by a target BS, where the last cell
attached to an A3 call leg is removed, thus causing the A3 call leg connections to be
torn down. As can be seen in the example, the A7-Target Removal Request message
initiates normal call leg removal, that is, between the A7-Target Removal Request and
A7-Target Removal Response messages will be found the normal A7 interface call leg
removal procedure.

2
3
4
5
6
7

MS

Source BS

MSC

Target BS

A7-Target Removal Request

Time

Comment

Extended Handoff Direction Message

b
MS Ack Order
Ttgtrmv

Handoff Completion Message

d
BS Ack Order
e
A7-Drop Target
f
Tdrptgt

A3-Remove
g
A3-Remove Ack

Tdiscon3
h
A7-Drop Target Ack

Handoff Performed
j
A7-Target Removal Response
k
8
9
10

Figure 3- 7 - Cell Removal Initiated by the Target BS

230

Conditional:
(See 3.3.1.3)

TIA/EIA/IS-2001

a.

The target BS decides that one or more of its cells can no longer be involved in the
soft/softer handoff and sends an A7-Target Removal Request message to the source
BS. The target BS starts timer Ttgtrmv.

b.

The source BS sends a handoff direction message7 to the mobile station to drop the
cell(s) from the active set.

c.

The mobile station acknowledges receipt of the handoff direction message with an
MS Ack Order.

d.

The mobile station indicates successful results of processing the handoff direction
message by sending a Handoff Completion Message.

e.

The source BS acknowledges receipt of the Handoff Completion Message by

sending a BS Ack Order.

f.

The source BS sends an A7-Drop Target message to the target BS to request that
the specified cells be removed from the call. The source BS starts timer Tdrptgt.

g.

The target BS, upon receipt of the A7-Drop Target message, deallocates internal
resources related to the specified cells. In this example, it is assumed that all cells
attached to an A3 connection are removed from the call. The target BS sends an A3Remove message to the SDU function of the source BS and starts timer Tdiscon3.

h.

The SDU function of the source BS replies with an A3-Remove Ack message and
deallocates internal resources. The target BS stop timer Tdiscon3.

i.

The target BS sends an A7-Drop Target Ack message to the source BS to

acknowledge the removal of the specified cells. The source BS stops timer Tdrptgt.

j.

The source BS may send a Handoff Performed message to the MSC. See section
3.3.1.3 Concept of A Designated Cell. The Handoff Performed message may be
sent any time after the Handoff Completion Message is received by the BS.

k.

The source BS responds to the target BS with an A7-Target Removal Response

message. The target BS stops timer Ttgtrmv.

2
3

4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

7 This may be a Handoff Direction Message, a General Handoff Direction Message, an

Extended Handoff Direction Message, or a Universal Handoff Direction Message as

appropriate.

231

TIA/EIA/IS-2001

3.5.2.3.6

Initial Traffic Burst Example A3 Connection Not Yet Established

The example below describes the support of an initial traffic burst when the A3
connection has not yet been established.
In this version of this standard, it is assumed that any leg for a supplemental channel will
be established on a cell that also supports a leg for the fundamental channel (FCH) or the
dedicated control channel (DCCH) for the same mobile station. To minimize the time
required to establish a traffic burst, the A3 connection for the SCH is established on the
target BS at the transmission of the first data burst. When a leg is established for a SCH,
only the terrestrial resources are allocated, i.e., the A3 connection. This involves
choosing the traffic circuit to be used and establishing context between the target BS and
the source BS/SDU function. Allocation of radio resources for the SCH is made each time
that a traffic burst is set up.

2
3
4
5
6
7
8
9
10
11
12

MS

Source BS

SCRM Msg

PDSN

Target BS

(data to be sent)

Time

Comment

A7- Handoff Request

Thoreq

A3-Connect
c
Tconn3

A3-Connect Ack

d
A7- Handoff Request Ack

A7- Burst Request

Tbstreq

e
f

A7 Burst Response
Tbstcom

A7Burst Commit

g
h

ESCAM
message
Layer 2 Ack

i
j
Forward and/or reverse traffic burst

13
14
15

Figure 3- 8 - Initial Traffic Burst Example

16

a.

Either the source BS receives an indication from the MS (via a Supplemental Channel
Request Message (SCRM)) or from the network (via data being received from the
PDSN) that data needs to be sent to/from the MS. The source BS decides a traffic
burst on one or more new cells at a target BS is required in support of a service
instance in soft/softer handoff. This example assumes that a Fundamental Channel
(FCH) or Dedicated Control Channel (DCCH) leg already exists on the selected cell(s)
at the target BS.

b.

The Source BS assigns an A7 From ID value and sends a A7 Handoff Request to the
target BS to establish an A3 traffic connection to support a Supplemental Channel
(SCH) for the call. This example shows only a single A3 connection being

17
18
19
20
21
22
23
24
25

232

TIA/EIA/IS-2001

established. The Source BS is not required to assign a physical Frame Selector at

this time.

1
2

c.

The target BS assigns a traffic circuit and optionally a Channel Element ID (CE ID)
for each A3 traffic connection and sends an A3-Connect message to the source BS
indicating the Traffic Circuit ID, optional A3 From ID and CE ID to be associated
with the specified A3 From ID. The source BS and target BS save the association of
CE ID, Traffic Circuit ID, with Cell ID(s). The source BS also saves the A3 From ID
value, to be included in subsequent A3 messages to the target BS. The target BS
starts timer Tconn3. This is only done at the initial burst.

d.

The source BS responds with an A3 Connect Ack message to complete the A3

connection. This includes an A3 From ID value assigned by the source BS, which
will be included by the target BS in subsequent A3 messages to the source BS. The
target BS stops timer Tconn3.

e.

The Target BS sends A7-Handoff Request Ack messages to the source BS to

complete the A3 traffic circuit connection setup procedure for the specified set of
cells. This includes an A7 From ID value assigned by the target BS, which will be
included by the source BS in subsequent A7 messages to the target BS for this call
association.

f.

The source BS sends an A7-Burst Request including the A7 From ID to the target
BS to request the reservation of the needed radio resources for the supplemental
channel. The source BS starts timer Tbstreq. Note that the source BS may send an
A7-Burst Request to the target BS at any time after receiving the A3-Connect
message in step c, and that the set of cells may be a subset of the cells assigned in
steps a-e.

g.

The target BS determines that it can reserve part or all of the requested resources
and sends A7-Burst Response message(s) including the A7 From ID to the source
BS indicating the resources that have been reserved and committed to the traffic
burst, and the cause value for any uncommitted cells. Each reservation includes a
physical Channel Element. Note that the physical Channel Element may be allocated
any time after step (b). The target BS starts timer Tbstcom. The source BS stops
timer Tbstreq.

h.

The source BS makes a final decision on the resources using the A7-Burst Response
information from the target BSs, associates a frame selector with the physical
channel, and sends an A7-Burst Commit message to each target BS indicating the
set of committed resources that will actually be used for the traffic burst. The target
BS stops time Tbstcom. Note that the source BS may allocate the frame selector any
time after step (b). Any resources (cells) not included in the A7-Burst Commit
message may be freed by the target BS.

i.

The source BS commands the MS to prepare for the traffic burst via an Extended
Supplemental Channel Assignment Message (ESCAM).

41

j.

The MS acknowledges the command from the source BS with a Layer 2 Ack.

42

k.

The network and mobile station exchange forward and/or reverse traffic burst
information for the specified duration, or until the source BS terminates or extends
the traffic burst.

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

43
44

233

TIA/EIA/IS-2001

3.5.2.3.7

Subsequent Traffic Burst Example

The example below describes the support of a traffic burst when the A3 connection for
the supplemental channel (SCH) has already been established. Note that this could be
the initial data burst if the A3 connection for the SCH was established previously via
the A7-Handoff Request procedure.

2
3
4
5

MS

Source BS

SCRM Msg

PDSN

Target BS

(data to be sent)

Time

Comment

A7- Burst Request

b
A7- Burst Response

Tbstreq

c
Tbstcom

A7- Burst Commit

d
ESCAM
message
Layer 2 Ack

e
f

Forward and/or reverse traffic burst

6
7

Figure 3- 9 - Subsequent Traffic Burst Example

a.

Either the source BS receives an indication from the MS (via a Supplemental Channel
Request Message (SCRM)) or from the network (via data being received from the
PDSN) that data needs to be sent to/from the MS.

b.

The source BS decides a traffic burst is required on one or more cells for which an
A3 connection already exists in support of a supplemental channel. The source BS
sends an A7-Burst Request to the target BS to request the reservation of the needed
radio resources for the supplemental channel. The source BS starts timer Tbstreq.

c.

The target BS determines that it can reserve part or all of the requested resources
and sends A7-Burst Response message(s) to the source BS indicating the resources
that have been reserved and committed to the traffic burst, and the cause value for
any uncommitted cells. Each reservation includes a physical Channel Element. Note
that the physical Channel Element may be allocated any time after step (b). The
target BS starts timer Tbstcom. The source BS stops timer Tbstreq.

d.

The source BS makes a final decision on the resources using the A7-Burst Response
information from the target BSs, associates a frame selector with the physical
channel, and sends A7-Burst Commit messages to all target BSs indicating the set of
committed resources that will actually be used for the traffic burst. The target BS
stops time Tbstcom. Note that the source BS may allocate the frame selector any
time after step (b). Any resources (cells) not included in the A7-Burst Commit
message may be freed by the target BS.

9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

234

TIA/EIA/IS-2001

e.

The source BS commands the MS to prepare for the traffic burst via an Extended
Supplemental Channel Assignment Message (ESCAM).

f.

The MS acknowledges the command from the source BS with a Layer 2 Ack.

g.

The network and mobile station exchange forward and/or reverse traffic burst
information for the specified duration, or until the source BS terminates or extends
the traffic burst.

1
2

5
6

235

TIA/EIA/IS-2001

4.

Mobility Management, Authentication,

and Privacy
This chapter discusses the protocol support for Mobility Management procedures
between the MSC and the BS. The mobility management procedures encompass mobile
registration, authentication, and control of signaling message encryption and voice
privacy. Privacy procedures are described in detail in section 2 Call Processing and
Supplementary Services.

4
5
6
7
8

The BS is responsible for translating the Mobility Management messages from the MSC
towards the MS into the correct air interface messages. Likewise, the BS is responsible
for translating the Mobility Management air interface messages into the appropriate
MSC-BS Interface messages for the MSC.

9
10
11
12

13

4.1

Mobility Management

14

4.1.1

Paging
Please refer to section 2 Call Processing and Supplementary Services.

15

16

4.1.2

Mobile registration is a process where mobile characteristics such as location or status

are provided to the network. Registration may be initiated by the mobile station, by the
network, or implied during a mobile station access. Deregistration processes for the
MSC-BS Interface are initiated by the MS.

17
18
19
20

21
22

Registration and Deregistration

4.1.2.1

Network Initiated Registration Procedures

The following functions are not supported in this version of the specification:

23

The ability to allow the MSC to order an idle MS to perform a registration;

24

Traffic channel registration - where the MSC may notify an MS that it is

registered while the MS occupies a traffic channel.

25
26
27
28

The MSC may infer registration information based on a mobiles system access. This
form of registration is transparent to the BS and the MS, and requires no additional
message passing over the MSC-BS interface.

236

TIA/EIA/IS-2001

4.1.2.2

Mobile Initiated Registration

The MS may initiate registration for a number of reasons. The types of registration
performed are enabled and controlled through parameters transmitted by the BS on the
forward (downlink) control channels. Selection of control channel parameters and
enabling of specific registration types are beyond the scope of this document, and will
not be discussed further.

2
3
4
5
6

Successful location registration requests involve the exchange of the following MSCBS messages:

Complete Layer 3 Information with Location Updating Request

10

Authentication Request / Authentication Response (optional)

11

Location Updating Accept

12

The message diagrams for the location update request procedure are illustrated in
Figure 4-1.

13

When authentication is supported by the BS/MSC, a challenge RAND is broadcast on

the control channel. RAND is specified in section 6.2.2.45 and utilized for the process of
registration, call origination and call termination. The MS utilizes the broadcast RAND
to compute the Authentication Response AUTHR specified in 6.2.2.46..

14
15
16
17

The Location Updating Request message is sent by the BS to notify the MSC of a
registration attempt by the MS.

18
19

20

4.1.2.2.1

UNUSED SECTION

4.1.2.2.2

Location Registration - Successful Case

21

22
23
24
25

The call flow diagram in Figure 4-1 provides an illustration of a successful Location
Registration procedure initiated by the MS.
time
MS

BS

MSC

Registration Message

a
Location Updating Request

T3210

Location Updating Accept

c

Registration Accepted Order

26
27

Figure 4- 1 - Location Registration - Successful Case

237

comment

TIA/EIA/IS-2001

a.

The MS initiates registration operation by sending the Registration Message to

the BS.

b.

On reception of the Registration Message the BS constructs the Location

Updating Request message, places it in the Complete Layer 3 Information
message, and sends it to the MSC. The BS then starts timer T3210.

c.

The MSC sends the Location Updating Accept message to the BS to indicate
that the Location Updating Request message has been processed.

2
3
4
5
6
7

Upon receipt of the Location Updating Accept message, the BS stops timer
T3210.

8
9

d.

10
11

12

4.1.2.3

Location Updating Request

When the mobiles registration message is received by the BS, it constructs the
Location Updating Request message, places it in the Complete Layer 3 Information
message, and sends the message to the MSC.

13
14
15

16

The BS may transmit a Registration Accepted Order to the MS to indicate

successful location registration operation.

4.1.2.3.1

Successful Operation

19

When the mobiles registration message is received by the BS, it constructs the
Location Updating Request message, places it in the Complete Layer 3 Information
message, starts timer T3210, and sends the message to the MSC.

20

The MSC responds with a Location Updating Accept message.

21

Please refer to section 2.2.1.2 for details of the Complete Layer 3 Information message.

22

Please refer to section 6.1.4.8, Location Updating Request, for the format and content
of this message.

17
18

23

24

4.1.2.3.2

If timer T3210 expires before the receipt of a Location Updating Accept message or a
Location Updating Reject message the BS may re-send the Location Updating Request
message. The total number of retransmissions is operator determined.

25
26
27

28

4.1.2.4

30

4.1.2.4.1

33
34
35

Please refer to section 6.1.4.9, Location Updating Accept, to for the format and
content of this message.

36
37

39

Successful Operation
The MSC will send a Location Updating Accept message to the BS when a location
registration procedure has been successfully completed at the MSC. Upon receipt of
this message, the BS cancels timer T3210 and may send the appropriate response (a
Registration Accepted order) over the control channel in use.

32

38

Location Updating Accept

This DTAP message is sent from the MSC to the BS to indicate that the Location
Updating Request has been successfully processed.

29

31

Failure Operation

4.1.2.4.2

Failure Operation
None.

238

TIA/EIA/IS-2001

4.1.2.5

This DTAP message is sent from the MSC to the BS to indicate that the Location
Updating Request message was rejected.

2
3

4.1.2.5.1

6
7
8
9

Please refer to section 6.1.4.10, Location Updating Reject, for the format and content
of this message.

10
11

4.1.2.5.2

4.1.2.6

Power Down Registration at the End of a Call

The MS may send a power down indication in a Release Order when clearing a call. The
BS shall forward a power down indication to the MSC by including the Power Down
Indicator element in the Clear Complete message. Please refer to section 2.3.1.7 Clear
Complete for more information.

15
16
17
18

19

Failure Operation
None.

13

14

Successful Operation
The MSC may send a Location Updating Reject message to the BS when a registration
procedure yields a rejection. The Location Updating Reject message contains a
mandatory cause element containing the reason for rejection. Upon receipt of this
message, the BS clears timer T3210 and may send the appropriate response to the MS (a
Registration Reject Order) over the control channel in use.

12

Location Updating Reject

4.1.3

UNUSED SECTION

4.1.4

UNUSED SECTION

20

21

22

239

TIA/EIA/IS-2001

4.2

Authentication and Privacy

When applicable, authentication is carried out at the mobile and at the HLR/AC.

The following table indicates the requirements for Authentication and Privacy while the
MS is idle, during registration, during origination, during termination, and during a call.
The table further illustrates whether the authentication is required for the
Paging/Access Channel and/or the Traffic Channel.

4
5
6

240

TIA/EIA/IS-2001

Table 4- 1 Authentication and Voice Privacy Requirements

STATE

On PAGING/ACCESS

On TRAFFIC

Global Challenge

N/A

N/A

Unique Challenge

Required

N/A

SSD Update

Not Required

N/A

Parameter Update (Count)

N/A

N/A

Voice Privacy On/Off

N/A

N/A

Data Privacy On/Off

Required

N/A

Global Challenge

Required

N/A

Unique Challenge

Not Required

N/A

SSD Update

N/A

N/A

Parameter Update (Count)

N/A

N/A

Voice Privacy On/Off

N/A

N/A

Data Privacy On/Off

N/A

N/A

Global Challenge

Required

N/A

Unique Challenge

N/A

(See: During Call)

SSD Update

N/A

(See: During Call)

Parameter Update (Count)

N/A

(See: During Call)

Voice Privacy On/Off

N/A

Required

Data Privacy On/Off

N/A

Required

Global Challenge

Required

N/A

Unique Challenge

N/A

(See: During Call)

SSD Update

N/A

(See: During Call)

Parameter Update (Count)

N/A

(See: During Call)

Voice Privacy On/Off

N/A

Required

Data Privacy On/Off

N/A

Required

Global Challenge

N/A

N/A

Unique Challenge

N/A

Required

SSD Update

N/A

Required

Parameter Update (Count)

N/A

Not Required

Voice Privacy On/Off

N/A

Required

Data Privacy On/Off

N/A

Required

While IDLE

During REGISTRATION

During ORIGINATION

During TERMINATION

During CALL

241

TIA/EIA/IS-2001

The assumptions in this specification are:

1
2

the BS shall be able to generate the RAND parameter

the MSC shall support BS generated RAND authentication

6
7
8
9
10
11
12
13
14
15

4.2.1

Shared Secret Data Procedures

Shared Secret Data (SSD) is a 128-bit pattern stored in the MS and readily available to
the network. This Shared Secret Data is not passed across the air interface between the
MS and the network or across the MSC-BS interface. The first 64 bits of the SSD is
defined as SSD-A that is used to support the authentication procedures. The last 64
bits of the SSD is defined as SSD-B that is used to support voice privacy and signaling
message encryption. Air interface procedures are defined to update SSD at the mobile
station. New Shared Secret Data is generated at the HLR/AC, which initiates the SSD
update procedure. Invocation of the SSD update procedure is an HLR/AC or OAM&P
concern. The SSD update procedure can take place on traffic channels for mobiles
capable of authentication and the related security procedures.

18

Usually, the entity controlling the authentication in the network will initiate the Unique
Challenge procedure as specified in the section 4.2.2 Terminal Authentication after an
SSD update procedure is completed.

19

The SSD update procedure involves exchange of the following MSC-BS messages:

20

SSD Update Request

21

Base Station Challenge

22

Base Station Challenge Response

23

SSD Update Response

16
17

242

TIA/EIA/IS-2001

4.2.1.1

SSD Update Procedure - Successful Case

The call flow diagram in Figure 4- 2 provides an illustration of a Shared Secret Data
(SSD) Update procedure.

2
3

time
MS

BS

comment

MSC
SSD Update Request

SSD Update Message

T3270

a
b

Base Station Challenge Order

c
Base Station Challenge
d
Base Station Challenge Response
Base Station Challenge Confirmation Order

e
f

T3271

SSD Update Confirmation Order

g
SSD Update Response
h
4
5

Figure 4- 2 - SSD Update - Successful Case

a.

The MSC sends an SSD Update Request message to the BS to indicate that the
Shared Secret Data at the MS needs updating. The update information is in the
form of a random number (RANDSSD) that will be used by the MS to calculate
the new SSD. The MSC starts timer T3270.

b.

Based on the SSD Update Request message from the MSC, the BS sends the
SSD Update message to indicate to the MS that it should update its SSD.

c.

Upon receipt of the SSD Update message from the BS, the MS uses the
RANDSSD as input to the algorithm to generate the new SSD. The MS then
selects a 32 bit random number (RANDBS) and sends it to the BS in a Base
Station Challenge Order message.

d.

The BS forwards the Base Station Challenge message to the MSC to verify the
new SSD calculated at the MS is the same as the number in the network. The
MSC stops timer T3270.

e.

On reception of the Base Station Challenge message, the MSC uses the new SSD
as input to the algorithm to generate the authentication response signature
(AUTHBS). The MSC then sends the authentication response signature
(AUTHBS) to the BS in the Base Station Challenge Response message. The
MSC starts timer T3271.

7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

243

TIA/EIA/IS-2001

f.

Upon receipt of the Base Station Challenge Response message from the MSC,
the BS transmits this information in a Base Station Challenge Confirmation Order
message to the MS.

g.

If AUTHBS from the MSC is valid, the MS will return an SSD Update
Confirmation Order message to the BS.

2
3
4
5

If AUTHBS from the MSC is invalid, the MS will return an SSD Update Rejection
Order message to the BS.

6
7

h.

8
9

10

4.2.1.2

12
13

4.2.1.2.1

16

When the MS receives the SSD Update Message, it uses the RANDSSD as input to the
algorithm to generate the new SSD. The MS will then select a 32 bit random number
(RANDBS) and shall send it to the BS in a Base Station Challenge Order message.

17
18
19

Please refer to section 6.1.4.4, SSD Update Request, for the format and content of this
message.

20
21

4.2.1.2.2

24

4.2.1.3

27
28

4.2.1.3.1

31
32
33

When the HLR/AC receives the Base Station Challenge message it uses the MS
generated RANDBS and the new SSD as input to the algorithm to generate the
response.

34
35
36

Please refer to section 6.1.4.5, Base Station Challenge, for the format and content of
this message.

37
38

40

Successful Operation
The MS selects a 32 bit random number (RANDBS) and sends it to the BS in a Base
Station Challenge Order. When a BS receives a Base Station Challenge Order, it
forwards this MS generated RANDBS in the Base Station Challenge message to the
MSC. The MSC stops timer T3270.

30

39

Base Station Challenge

The Base Station Challenge message is sent from the BS to the MSC to verify the new
SSD that was calculated at the MS. This is a DTAP message when used to perform the
SSD update on a traffic channel.

26

29

Failure Operation
If timer T3270 expires prior to receipt of a BS Challenge message, the MSC may choose
to retransmit this message.

23

25

Successful Operation
The MSC sends an SSD Update Request message to the BS and starts timer T3270.
When the BS receives this message it forwards an SSD Update Message to the MS.

15

22

SSD Update Request

The SSD Update Request message is sent from the MSC to the BS to indicate that the
MS should update its Shared Secret Data. This is a DTAP message used to perform
SSD update on a traffic channel.

11

14

The BS forwards the information in the SSD Update Response message to the
MSC. The MSC stops timer T3271.

4.2.1.3.2

Failure Operation
None.

244

TIA/EIA/IS-2001

4.2.1.4

This message is sent from the MSC to the BS in response to the Base Station Challenge
message. This is a DTAP message when used to perform the SSD update on a traffic
channel.

2
3
4

4.2.1.4.1

7
8
9
10

Please refer to section 6.1.4.6, Base Station Challenge Response, for the format and
content of this message.

11
12

4.2.1.4.2

15

4.2.1.5

18
19
20

4.2.1.5.1

23
24
25
26
27

The MS will not update the SSD if the AUTHBS value is not considered valid. Further
error handling at the HLR/AC is an HLR/AC matter and will not be detailed in this
specification.

28
29
30

Please refer to section 6.1.4.7, SSD Update Response, for the format and content of
this message.

31
32

34

Successful Operation
When the MS receives the Base Station Challenge Confirmation Order message from
the BS, it checks the validity of the response and returns an SSD Update
Confirmation/Rejection Order to the BS to indicate whether the procedure was
successfully performed. The BS uses the SSD Update Confirmation/Rejection Order to
create the SSD Update Response message which it sends to the MSC. The MSC stops
timer T3271.

22

33

SSD Update Response

This message is sent from the BS to the MSC to indicate whether the MS has
successfully updated its SSD. It is sent by the BS only upon receipt of the SSD Update
Confirmation/Rejection Order from the MS. This is a DTAP message when used to
perform SSD updates on a traffic channel.

17

21

Failure Operation
If timer T3271 expires prior to receipt of a SSD Update Response message, the MSC
may declare failure of the SSD Update procedure.

14

16

Successful Operation
The MSC sends a Base Station Challenge Response message to the BS and starts timer
T3271. When the BS receives the Base Station Challenge Response message from the
MSC it sends the Base Station Challenge Confirmation Order message to the MS. The
MS checks the validity of the response and sends an SSD Update
Confirmation/Rejection Order to the BS.

13

Base Station Challenge Response

4.2.1.5.2

Failure Operation
None.

245

TIA/EIA/IS-2001

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

4.2.2

Terminal Authentication
Authentication is a method of verifying the authenticity of a mobile station, permitting
denial of service to invalid mobiles and thereby deterring fraud. The method involves a
common algorithm in the network and MS, and a parameter unique to each MS, and
known only to the MS and the network, called the A-Key. Furthermore, a second level
of security is established called the Shared Secret Data (SSD). The SSD is derived from
the A-Key and a random challenge (RANDSSD) as described in section 4.2.1. The AKey and the SSD are never broadcast across the air interface. Instead, a publicly
available random number (RAND) is sent to the MS. The RAND and SSD are used as
input to the authentication algorithm at both the MS and the network. The
authentication result (referred to as AUTHR) is computed by the MS and returned to
the network. It is compared to the networks computed result AUTHR. If the results
match, the authentication procedure was successful. If authentication procedures fail,
the MSC may initiate call clearing per section 2.3.3.3
Two forms of authentication are available for use with mobiles capable of authentication
and the related security procedures. In the first form, the RAND value is broadcast on
the forward control/paging channel and common to all mobiles accessing the cell. The
mobile computes AUTHR using this RAND, and provides it in its initial access
message, which may be a location registration, origination, or page response. Please
refer to section 2 for details on use of this form of authentication for mobile origination
and page responses. Please also refer to section 4.1.2, Registration and
Deregistration.
In the second form of authentication, the MSC initiates an explicit authentication
procedure, with messaging separate from those used for call setup and registration. The
MSC issues a challenge to the MS containing a specific (unique) RANDU value, and
the MS responds with its computed AUTHU value. This is referred to as the unique
challenge/response procedure, and is described in this section. This procedure is
always initiated and controlled by the MSC. The MSC may initiate this procedure at
any time on either control or traffic channels.
time
MS

BS

MSC

Authentication Request
Authentication Challenge
T3260
Authentication Challenge Response

b
c

Authentication Response
30
31
32

Figure 4- 3 - Terminal Authentication

246

comment

TIA/EIA/IS-2001

a.

The MSC sends the Authentication Request to the BS and starts timer T3260.

b.

The BS forwards the information (RANDU) to the MS in an Authentication

Challenge Message over the air interface.

c.

The MS computes the result AUTHU based on the specified RANDU and the
MSs SSD. It then returns an Authentication Challenge Response Message to
the BS, with the enclosed AUTHU.

d.

The BS forwards the AUTHU information to the MSC using the Authentication
Response message.

3
4
5
6
7
8

Upon receipt of the Authentication Response message from the BS, the MSC
stops timer T3260.

9
10

11

4.2.2.1

The Authentication Request message is sent from the MSC to the BS to initiate an
authentication check on a specified MS. This is a DTAP message when used to perform
authentication on a traffic channel and a BSMAP message otherwise.

12
13
14

15

4.2.2.1.1

17
18

When the MS receives the Authentication Challenge message it uses the RANDU as
input to the algorithm to generate the response parameter (AUTHU).

19
20

Please refer to section 6.1.4.1, Authentication Request, for the format and content of
this message.

21
22

4.2.2.1.2

25
26

4.2.2.2

29
30

4.2.2.2.1

33

Please refer to section 6.1.4.2, Authentication Response, for the format and content of
this message.

34
35

37

Successful Operation
When a BS receives an Authentication Challenge Response message from the MS it
sends the Authentication Response message to the MSC. The MSC stops timer T3260.

32

36

Authentication Response
This message is sent from the BS to the MSC in response to the Authentication
Request message. This is a DTAP message when used to perform authentication on a
traffic and a BSMAP message otherwise.

28

31

Failure Operation
If timer T3260 expires, the MSC may resend the Authentication Request message to the
BS, may initiate call clearing, or may invoke other failure processing as determined by
the network operator.

24

27

Successful Operation
The MSC sends an Authentication Request message to the BS and starts timer T3260.
When the BS receives this message it forwards an Authentication Challenge message
to the MS.

16

23

Authentication Request

4.2.2.2.2

Failure Operation
None.

247

TIA/EIA/IS-2001

4.2.3

Parameter Update
This procedure is performed when the MSC is instructed to update the call history
count at the MS.

2
3

The MSC sends a Parameter Update Request message to the BS and starts timer T3220.
Upon receiving this message, the BS shall instruct the MS to update its count by
sending the Parameter Update Order on a traffic channel. When the MS receives this
order, it increments its call history count and responds by sending a Parameter Update
Confirmation Order message to the BS. Upon receiving the Parameter Update
Confirmation Order message from the MS, the BS shallsend the Parameter Update
Confirm message to the MSC. Upon receipt of this message, the MSC shall update the
call history count and stops timer T3220.

4
5
6
7
8
9
10
11
12

Time Comment
MS

BS

MSC
Parameter Update Request
a

Parameter Update Order

T3220

Parameter Update Confirmation Order

c
Parameter Update Confirm
d

13
14
15

Figure 4-4 - Parameter Update

16

a.

When the BS receives the Parameter Update Request from the MSC, it orders the
MS to update its call history count. The MSC starts timer T3220.

b.

When the Parameter Update Order is received by the MS, it increments its call
history count.

20

c.

MS acknowledges that the call history count has been successfully updated.

21

d.

The BS sends the Parameter Update Confirm to the MSC indicating that the MS
incremented its call history count. Upon receipt of this message, the MSC
updates the call history count. The MSC stops timer T3220.

17
18
19

22
23

24

4.2.3.1

This DTAP message is sent from the MSC to the BS to increment the call history count
in the mobile station.

25
26

27
28
29

Parameter Update Request

4.2.3.1.1

Successful Operation
The MSC sends Parameter Update Request to the BS and starts timer T3220. When the
BS receives this message, it shall send the Parameter Update Order message to the MS.

248

TIA/EIA/IS-2001

Please refer to section 6.1.4.11, Parameter Update Request to view the format of this
message.

1
2

4.2.3.1.2

If timer T3220 expires without receiving a response from the BS, the MSC shall not
increment the call history count and may re-send this message.

4
5

4.2.3.2

8
9

4.2.3.2.1

12
13
14

16
17

Successful Operation
When the BS receives the Parameter Update Confirmation Order from the MS, it shall
send the Parameter Update Confirm to the MSC. The MSC shall increment the call
history count and stop timer T3220. Please refer to section 6.1.4.12, Parameter Update
Confirm to view the format of this message.

11

15

Parameter Update Confirm

This DTAP message is sent from the BS to the MSC in response to a Parameter Update
Request message. This message is sent when the BS receives a positive indication from
the MS that it incremented its call history count.

10

Failure Operation

4.2.3.2.2

Failure Operation
If the BS fails to receive a response from the MS indicating that the call history count
has been successfully incremented in the MS, the BS shall do nothing.

249

TIA/EIA/IS-2001

4.2.4

If provided by the air interface, protection of fields within signaling messages between
the base and the mobile station can take place. In order to provide this protection, the
relevant device used for the signaling message needs to be loaded with the appropriate
key. This is supplied by the MSC over the MSC-BS Interface. See section 6.2.2.12,
Encryption Information. Signaling Message Encryption cannot be invoked unless
broadcast authentication is activated in the system.

2
3
4
5
6
7

4.2.5

Voice Privacy
If provided by the air interface, voice privacy between the base and the mobile station
can take place. In order to provide this protection, the relevant device used for the voice
privacy needs to be loaded with the appropriate key. This is supplied by the MSC over
the MSC-BS interface. See section 6.2.2.12, Encryption Information. Voice Privacy
cannot be invoked unless broadcast authentication is activated in the system.

9
10
11
12
13

14

Signaling Message Encryption

4.2.5.1

Privacy Mode Procedure

15

This section describes the call flow associated with voice privacy activation.

16

If broadcast challenge is not active in the system, then voice privacy cannot be
invoked.

17

19

The privacy mode procedure should be completed either before handoff is initiated or
after a handoff operation is complete.

20

Voice Privacy is shown here being invoked during an established call.

18

time
MS

BS

MSC
Privacy Mode Command
a

Mobile Order

b
T3280

Mobile Response
Privacy Mode Complete

21
22

Figure 4- 5 - Privacy Mode Procedure

250

c
d

comment

TIA/EIA/IS-2001

a.

The MSC at any point during the call following the receipt of the Assignment
Complete message may send the Privacy Mode Command message to the BS
to specify that privacy is to be provided for traffic information. The MSC then
starts timer T3280.

b.

After the radio traffic channel has been acquired, voice privacy can be
established when the BS transmits a voice privacy request order to the MS.

c.

The MS performs the required privacy mode procedures and acknowledges the
BS with a voice privacy response order.

d.

The BS returns the Privacy Mode Complete message to the MSC to indicate
successful receipt of the Privacy Mode Command message.

2
3
4
5
6
7
8
9
10

The MSC stops timer T3280 upon receipt of the Privacy Mode Complete
message.

11
12

13

4.2.5.2

UNUSED SECTION

4.2.5.3

Privacy Mode Command

14

15

This optional BSMAP message may be sent by the MSC to the BS after receipt of the
Assignment Complete message while the call is in conversation state. Its typical use is
to specify the use of encryption/privacy parameters for the call. It may be sent to enable
or disable the use of encryption/privacy during conversation.

16
17
18
19

The pre-loading of the BS with parameters allows initiation of SME during assignment
to traffic channels when appropriate, and allows the BS to immediately initiate privacy
upon request by the mobile user or immediately following assignment to a traffic
channel.

20
21
22
23

The MSC may place the information in the Assignment Request message, if available.
Please refer to section 6.1.2.15, Assignment Request for details on inclusion of the
Encryption Information element in this message.

24
25
26

If signaling encryption is not available at the time the Assignment Request message is
sent, the MSC shall wait until after the Assignment Complete message to send the
Privacy Mode Command message.

27
28
29

The Privacy Mode procedure may be invoked by the MSC during conversation state to
enable or disable the use of encryption/privacy. This may be initiated by the MSC, or
sent in response to a request for privacy by the mobile user. Use in the latter case is
only necessary where the privacy parameters are not pre-loaded by the MSC.

30
31
32
33

34
35
36
37
38
39

4.2.5.3.1

Successful Operation
The MSC starts timer T3280 upon sending this message. When the BS receives the
Privacy Mode Command message it responds to the MSC with the Privacy Mode
Complete message.
Please refer to section 6.1.4.18, Privacy Mode Command, for the format and content of
this message.

251

TIA/EIA/IS-2001

4.2.5.3.2

In the case where the MSC initiated the Privacy Mode procedure, if the MSC does not
receive the Privacy Mode Complete message before T3280 expires, then the MSC will
initiate call clearing.

2
3
4

Failure Operation

4.2.5.4

Privacy Mode Complete

This optional BSMAP message is sent from the BS to the MSC autonomously, or in
response to the Privacy Mode Command message. It is used in the following cases:

6
7
8

During conversation, to acknowledge the Privacy Mode Command and

indicate current encryption parameter settings.

During conversation, to indicate a change in the privacy status, where the

privacy mode was changed to on or off at the request of the mobile user.

During conversation, to indicate that the mobile user has requested privacy
but the BS is unable to provide it.

9
10
11
12
13

14

4.2.5.4.1

When the MSC receives this message from the BS in response to the Privacy Mode
Command message or autonomously, it stops timer T3280.

15
16

When the MSC receives this message autonomously indicating that the MS has
requested Privacy, it may respond with the Privacy Mode Command message
containing the necessary Privacy parameters, or indicate that Privacy is not available.

17
18
19

Please refer to section 6.1.4.19, Privacy Mode Complete, for the format and content of
this message.

20
21

22
23

Successful Operation

4.2.5.4.2

Failure Operation
None.

252

TIA/EIA/IS-2001

4.3

The PCF-PDSN interface is designed for use over a protected, private network between
the PCFs and the PDSNs. Pre-arranged security associations, in the style of IP
Mobility Support for IPv4 (RFC 2002) exist among every PCF and PDSN pair that
forms an RP connection.

2
3
4
5

Several potential vulnerabilities exist in the absence of such security associations. If an

A10 connection is accessible to an attacker, the GRE encapsulated user traffic may be
intercepted and/or spoofed if end-to-end security mechanisms are not in place. Such
end-to-end security issues are outside the scope of this standard. However, all A11
signaling messages are authenticated to prevent an A10 connection setup and tear
down by an unauthorized node. Mobile-Home Authentication Extension and
Registration Update Authentication Extension provide a means of protecting the A11
signaling messages. If registration messages are not authenticated, a denial-of-service
attack is possible. If a PCF sends a Registration Request to the PDSN with a spoofed
Session Specific Extension, the PDSN would then send an explicit tunnel tear down to
the previous PCF, causing user traffic to be misdirected to the new PCF. This would
cause a loss of service and possibly interception of traffic, depending on what other
security measures are in place.

6
7
8
9
10
11
12
13
14
15
16
17
18

The A8/A9 interfaces are assumed to be supported on a private IP network for security
considerations.

19
20

21

Packet Data Security Considerations

4.3.1

PCF-PDSN Security Association

24

Security contexts are configurable between every PCF and PDSN pair on the packet
data network. Each security context indicates an authentication algorithm and mode, a
secret (a shared key, or appropriate public/private key pair), and a style of replay

25

protection in use.8

22
23

An index identifying a security context between a pair of PCF and PDSN is called
Security Parameter Index (SPI). SPI values 0 through 255 are reserved, hence not
used in any PCF-PDSN security association.

26
27
28

29
30
31
32
33
34

4.3.1.1

Computing Registration Authentication Extension Values

The Mobile-Home Authentication Extension and Registration Update
Authentication Extension provide a means for authenticating the registration
messages on the Aquater interface. The Authenticator value in the Mobile-Home
Authentication Extension and Registration Update Authentication Extension
protects the following fields:

35

the UDP payload of registration messages

36

all prior extensions in their entirety, and

37

the Type, Length and SPI fields of the extension

38
39
40
41

The authentication algorithm uses the default keyed-MD5 (RFC 1321) in the prefixsuffix mode to compute a 128-bit message digest of the registration message. The
Authenticator value is a 128-bit value computed as the MD5 checksum over the
following stream of bytes:

8 See RFC 2002 for details.

253

TIA/EIA/IS-2001

the shared secret defined by the mobility security association between the
PCF and the PDSN and by the SPI value specified in the authentication
extension, followed by

the protected fields from the registration message, in the order specified
above, followed by

the shared secret again

2
3
4
5
6
7
8
9
10
11
12

The Authenticator field itself and the UDP header are NOT included in the computation
of the Authenticator value. The receiver uses the SPI value within an authentication
extension to determine the security context, and compute the Authenticator value. A
mismatch in the Authenticator values results in rejection of the registration message
with error code 131 (sending node failed authentication). See section 3.5, RFC 2002 for
implementation details.

13

254

TIA/EIA/IS-2001

5.

Layers 1 & 2 and Terrestrial Facility

Management

5.1

Physical Layer Specification (Layer 1)

The A1, A2, A3, A5, and A7 interfaces are based on the use of:

T1 digital transmission system interfaces. Each 1.544 Mbits/s interface provides

24*56 kbits/s or 24*64 kbits/s channels which can be used for traffic or signaling as
the operator requires. Common physical interface standards are found in ANSI
T1.101 and related references. For a list of references, refer to section 1.5.

E1 digital transmission interfaces consisting of 30*64 kbits/s user channels can

also be used for traffic or signaling as the operator requires, and as applicable to
the network.

7
8
9
10
11
12

As a BS/MSC agreed option, dedicated DS0 signaling link[s] may be used instead
of the T1/E1 interface.

13
14
15

T3 digital transmission interfaces supporting transmission rates of 43.232

Mbits/sec.

OC3 digital transmission interfaces supporting transmission rates of 155.52

Mbits/sec.

16
17
18

The A8, A9, A10, and A11 interfaces are based on the use of the Internet Protocol (IP).
IP can operate across various physical layer media. The specific layer 1 media and layer
2 link protocols to be used for these interfaces are not specified in this standard.

19
20
21

22

5.2

ANSI SS7 Transport Specification (Layer 2)

23

Information for this section was excerpted from ANSI T1.111 and ANSI T1.112.

24

This section is divided into two parts. Section 5.2.2 deals with the Message Transfer
Part (MTP). Section 5.2.3 deals with the Signaling Connection Control Part (SCCP) and
its use.

25
26
27
28
29
30
31
32
33

The MTP provides a mechanism giving reliable transfer of signaling messages. Section
5.2.2 deals with the subset of the MTP that can be used between a Base Station (BS)
and a Mobile Switching Center (MSC), which is compatible with a full MTP.
The SCCP is used to provide a referencing mechanism to identify a particular
transaction relating to, for instance, a particular call. Section 5.2.3 identifies the SCCP
subset that shall be used between a BS and an MSC. The SCCP can also be used to
enhance the message routing for operations and maintenance information.

255

TIA/EIA/IS-2001

5.2.1

Field of Application
This section is applicable to the signaling between BSs and MSCs in Public Land
Mobile Networks (PLMNs). It provides a minimum set of MTP requirements that may be
implemented at a BS or MSC, while maintaining compatibility with the implementation of
a full specification of the MTP.

2
3
4
5

This section defines the interfaces at the 56 or 64 Kbits/s boundary to the BS or MSC
and applies primarily to digital access arrangements. The use of analog arrangements is
not supported.

6
7
8

12

The reliability of signaling links is an administrative concern. It is recommended that in

the case where more than one multiplex system is required and reliability reasons dictate
the use of a multiple link sets, then each signaling link should be assigned in a different
multiplex system.

13

Only the associated mode of signaling will be applicable to the BS.

14

The ANSI recommendations concerning MTP shall be taken as being requirements

unless covered by a statement in this section.

9
10
11

15

16

5.2.2

Message Transfer Part (MTP) Functions

5.2.2.1

General

17

18

The MTP functions as specified in ANSI T1.111 [Reference 5] are applicable. However,
the following exceptions and modifications to those recommendations may be applied
for the MSC to BS signaling. See section 5.2.2.2 through section 5.2.2.4.

19
20
21

22

5.2.2.2

Level 1 (T1.111.2)

23
24

T1.111.2 Figure 2

25
26

These figures are for information only. For the MSC-BS Interface, interface point C is
appropriate.

27

T1.111.2 Section 1.4 Analog Signaling Link

28

The use of analog signaling links is not an available option.

29

T1.111.2 Section 2 General

30

A signaling rate of 56/64 kbits/s is assumed.

31

T1.111.2 Section 3 Error Characteristics and Availability

32
33

Error characteristics and availability are an operator concern. Excessive errors could
lead to inefficient use of the signaling links.

34

T1.111.2 Section 5 Digital Signaling Link

35
36

The standard arrangement will be to derive the signaling link from a T1/E1 digital path
but dedicated DS0 signaling link[s] may be used as a BS/MSC agreed option.

37

T1.111.2 Section 6 Analog Signaling Data Link

38

Only digital signaling data links are supported.

256

TIA/EIA/IS-2001

5.2.2.3

Level 2 (T1.111.3)

T1.111.3 Section 1.4 Signal Unit Error Correction

Only the basic error correction protocol is required.

T1.111.3 Section 7 Signaling Link Initial Alignment Procedure

In the initial alignment procedure specified in Recommendation T1.111.3, only the

emergency proving is applicable for the BS. Thus, in states 02 and 03 of the initial
alignment procedure status indication "N" is not sent from the BS. The BS should be
capable of recognizing status indication "N" if received in order for the alignment
procedure to complete.

6
7
8
9

10

5.2.2.4

Level 3 (T1.111.4)

11

T1.111.4 Section 1.1.2 End Point of a Signaling Link

12
13

The BS is only implemented as the end point of a signaling link. There will be no
Signaling Transfer Point (STP) network management features in the BS.

14

T1.111.4 Section 2

15

Since STP working is not required for the discrimination and routing functions of the
MTP used for MSC-BS can be significantly simplified.

16

19

Since the implementation of this interface is intended only for point to point application
the routing function within the MTP will be preset to select the point code appropriate
to the parent MSC.

20

T1.111.4 Section 2.2 Routing Label

21
22

Load sharing will be performed on the BS with more than one signaling link by means of
the Signaling Link Selection field (SLS).

23

T1.111.4 Section 2.3 Message Routing Function

24
25

Load sharing between link sets is not required since there will only be one link set
between the BS and MSC.

26

T1.111.4 Section 2.3.5 Handling of Messages under Signaling Link Congestion

27

The procedures for handling message congestion priority levels as defined for U. S.
Signaling Networks in T1.111.4 Section 2.3.5.2 shall be followed. The message priorities
given in Appendix B of T1.111.5 for SCCP and MTP messages shall be used. The
remaining message priorities for BSMAP and DTAP messages are provided in Tables 611 and 6-12 in section 6.2.2.4 of this specification.

17
18

28
29
30
31

257

TIA/EIA/IS-2001

T1.111.4 Section 2.4 Message Discrimination

At the BS only messages with a correct Destination Point Code (DPC) will be accepted.
Other messages will be discarded. It is recommended that discarding a message because
of an incorrectly set point code should cause an incident report to be generated.

3
4

10

At an MSC (which has the capability of acting as an STP) an administration may decide
that each message received from a BS signaling link is passed through a screening
function that checks that the DPC of the message is the same as the Signaling Point
(SP) code of the exchange. If that is the case, the message is sent to the normal MTP
message handling functions. Otherwise, the message is discarded and an incident
report is made.

11

T1.111.4 Section 3 Signaling Network Management

12

15

Since the MSC-BS Interface utilizes point to point signaling between the BS and the
MSC, the Signaling Route Management procedures, including the status of signaling
routes, signaling route restricted, signaling route unavailability and availability, are not
required.

16

T1.111.4 Section 3.8 Signaling Network Congestion

17
18

The procedures defined for U. S. Networks shall be followed for handling congestion on
signaling links.

19

T1.111.4 Section 4 Signaling Traffic Management

20

22

Since the MSC-BS Interface utilizes point to point signaling, the Traffic Management
procedures supporting signaling routes, including signaling route restricted, signaling
route unavailability and availability, are not required.

23

T1.111.4 Section 4.2

24

27

The normal routing situation will be that there are one or more signaling links available
between the BS and MSC, and these will constitute a link set. They will be run in a load
sharing mode and changeover and change back procedures will be supported between
these signaling links.

28

T1.111.4 Section 4.3.3

29

There will be no alternative link set.

30

T1.111.4 Section 5 Changeover

31

Changeover between link sets is not applicable.

32

T1.111.4 Section 6 Change back

33

Change back between link sets is not applicable.

34

T1.111.4 Section 7 Forced Rerouting

35

Forced rerouting is not applicable since there is only one signaling route existing
between the BS and the MSC.

5
6
7
8
9

13
14

21

25
26

36

258

TIA/EIA/IS-2001

T1.111.4 Section 8 Controlled Rerouting

2
3

Controlled rerouting is not applicable since there is only one signaling route existing
between the BS and the MSC.

T1.111.4 Section 9 MTP Restart

The MTP Restart procedure is not required.

T1.111.4 Section 11 Signaling Traffic Flow Control

The Signaling Route Management procedures supporting signaling traffic flow control
including signaling route unavailability and signaling route set congestion are not
applicable for the MSC-BS Interface.

8
9
10

T1.111.4 Section 12 Signaling Link Management

11

Only basic link management procedures are applicable.

12

T1.111.4 Section 13 Signaling Link Management

13

16

Signaling Route Management procedure is not applicable for the MSC-BS Interface
since it is a point to point connection. No action is required upon reception of a TFP,
TFR, TFA, Signaling Route Set Test, Signaling Route Set Congestion Test, or Transfer
Control message.

17

T1.111.4 Section 14.2.1

18
19

Since all messages are passed using the SCCP, the service indicator will be: D=0, C=0,
B=1, A=1.

20

T1.111.4 Section 14.2.2

21
22

The sub service field will always be set to indicate a national network as follows: D=1,
C=0.

23

T1.111.4 Section 15

24

The formats and codes listed are only relevant to the messages that are required.

14
15

25

5.2.2.5

Testing and Maintenance (T1.111.7)

26

T1.111.7 Section 2.1 Signaling Data Link Test

27

The Signaling Data Link Test procedure is not required for the MSC-BS Interface.

28

T1.111.7 Section 2.2

29

The generation of a Signaling Link Test Message (SLTM) is not applicable at the BS,
however the BS shall be capable of responding with an acknowledgment message to a
SLTM.

30
31

32

5.2.2.6

Interface Functions

34

The method of interfacing to the higher layers will be by the primitives defined in
T1.111.1.

35

The primitives defined are:

33

36

MTP Pause indication

37

MTP Resume indication

38

MTP Status indication

259

TIA/EIA/IS-2001

MTP Transfer request

MTP Transfer indication

5.2.2.7

Overload Control (Message Throughput Congestion)

MTP overload control is not required.

260

TIA/EIA/IS-2001

5.2.3

SCCP Transport Layer Specification (SCCP Functions)

5.2.3.1

Overview

The purpose of this section is to identify the subset of the SCCP functions that are
necessary to achieve the management of the MS transactions in the MSC-BS interface,
and to provide addressing facilities. If this subset of SCCP functions is implemented,
compatibility with a full ANSI SCCP shall be maintained. Only the needs of the BSAP
are taken into account in this section.

4
5
6
7
8

The following simplifications are applicable to the signaling between BS and MSC in
PLMNs:

9
10
11

In order to limit the complexity of the procedures, a BS exchanges signaling

messages only with its MSC, where a protocol conversion may be needed in
some cases. Therefore, no SCCP translation function is required in the MSC
between the national and the local SCCP and MTP within the MSC area.

Several functions of the SCCP are not used on the MSC-BS interface: error
detection, receipt confirmation, and flow control.

The segmenting/reassembling function shall be used if the total message

length exceeds the maximum allowed message length that can be carried by the
MTP.

T1.112.1 through T1.112.4 are considered as the basis for elaboration of this
document.

12
13
14
15
16
17
18
19
20
21

22

5.2.3.2

Primitives (T1.112.1)

23

T1.112.1 Table 1

24

Two primitives of the table are not used:

25

N-INFORM DATA

26

N-RESET

27

T1.112.1 Table 2

28

The following parameters of the N-CONNECT primitive are not used:

29

Responding address

30

Receipt confirmation selection

31

Expedited data selection

32

T1.112.1 Table 3

33

The following parameter of the N-DATA primitive is not used:

34

Confirmation request

35

T1.112.1 Table 6

36

The following parameter of the N-DISCONNECT primitive is not used:

37

Responding address

38

T1.112.1 Section 2.1.2

261

TIA/EIA/IS-2001

Permanent signaling connections are not applicable.

T1.112.1 Table 8

The primitive N-NOTICE is not used.

T1.112.1 Table 8A

The following parameter of the N-UNITDATA is not used:

Return option

T1.112.1 Section 4.1.2

Functions for permanent signaling connections are not applicable.

5.2.3.3

SCCP Messages (T1.112.2)

10

T1.112.2 Section 2.4

11

The Data Acknowledgment (AK) message is not used.

12

T1.112.2 Section 2.6

13

The Data Form 2 (DT2) message is not used.

14

T1.112.2 Section 2.7

15

The Expedited Data (ED) message is not used.

16

T1.112.2 Section 2.8

17

The Expedited Data Acknowledgment (EA) message is not used.

18

T1.112.2 Section 2.10

19
20

The Protocol Data Unit Error (ERR) message is not used; the inconsistent messages of
the SCCP protocol are discarded.

21

T1.112.2 Section 2.13

22

The Reset Confirm (RSC) message is not used.

23

T1.112.2 Section 2.14

24

The Reset Request (RSR) message is not used.

25

T1.112.2 Section 3.5

26

The Subsystem-Out-Of-Service-Grant (SOG) message is not used.

27

T1.112.2 Section 3.4

28

The Subsystem-Out-Of-Service (SOR) message is not used.

29

T1.112.2 Section 2.16

30

The Unitdata Service (UDTS) message is not used.

31

T1.112.2 Section 4.2

32
33

The credit parameter field is not used for protocol class 2. However, the parameter
shall still be included in the IT message for syntax reasons.

34

T1.112.2 Section 4.6

35

The error cause parameter field is not used.

36

T1.112.2 Section 4.10

262

TIA/EIA/IS-2001

The receive sequence number parameter is not used.

T1.112.2 Section 4.13

The reset cause parameter field shall not be used.

T1.112.2 Section 4.16

The sequencing/segmenting parameter field is not used for protocol class 2.

However, the parameter shall still be included in the IT message for syntax reasons.

5.2.3.4

SCCP Formats and Codes (T1.112.3)

T1.112.3 Section 3.4

9
10

For point-to-point network structures (i.e., direct connections between the MSC and
BS) the called party address may consist of the single element:

11

subsystem number

12

14

No global title is used. The signaling point code which is coded in the MTP routing
label and the Subsystem Number (SSN) in the called party address allow the routing of
the message.

15

T1.112.3 Section 3.4.2.2

16

SSN Values: BSAP = 11111100, (252)

17

Use of alternative values is an administrative concern.

18

20

BSAP SSN value of 11111101 (253) is the SSN for GSM. In CDG IOS V2.0.0 it was
determined that the IOS Open A-Interface should use its own SSN value and this was
selected as BSAP = 11111100 (252).

21

T1.112.3 Section 3.4.2.3

22

Global title: refer to T1.112.3 Section 3.4

23

T1.112.3 Section 3.6

24

Protocol Class: the classes 1 and 3 are not used.

25

T1.112.3 Sections 3.8, 3.9, 3.10, 3.13, 3.14

26

Parameters are not used.

27

T1.112.3 Sections 4.8, 4.9, 4.11, 4.12, 4.13, 4.14, 4.15, 4.16

28

Messages are not used.

29

T1.112.3 Section 5.1.1

30

SOR and SOG are not needed.

13

19

31

5.2.3.5

SCCP Procedures (T1.112.4)

32

T1.112.4 Sections 1.1.2.2, 1.1.2.4

33

Protocol classes 1 and 3 are not used.

34

T1.112.4 Section 1.1.3

35

A signaling connection consists of a single connection section. No intermediate nodes

are defined in the MSC-BS Interface.

36

263

TIA/EIA/IS-2001

The use of multiple connections sections is an administrative concern.

T1.112.4 Section 1.2.1 (b)

Not applicable for single connections.

T1.112.4 Section 2.1 (1.)

Global title not used for single connections.

T1.112.4 Section 2.2.1

7
8

Subsystem Number (SSN) is only present in the called party address for single
connections.

T1.112.4 Section 2.2.2

11

The addressing information may take the following form in the N-CONNECT request
primitive: DPC+SSN (for single connections).

12

T1.112.4 Section 2.2.2.2

13

No SCCP translation function is required for single connections.

14

T1.112.4 Section 2.3.1 (3)

15

Not applicable for single connections.

16

T1.112.4 Section 2.3.2 (4)

17

Not applicable for single connections.

18

T1.112.4 Section 3.1.3

19

Not applicable: no protocol class and flow control negotiations.

20

T1.112.4 Section 3.1.5

21

Not applicable.

22

T1.112.4 Section 3.2.2

23

Not applicable.

24

T1.112.4 Section 3.3.4

25

Not applicable.

26

T1.112.4 Section 3.5.1.2

27

Not applicable.

28

T1.112.4 Section 3.5.2

29

Not applicable.

30

T1.112.4 Sections 3.6, 3.7, 3.9, 3.10

31

Not applicable.

32

T1.112.4 Section 4.2

33

Message return is not applicable.

34

T1.112.4 Section 5

35

Only those messages and procedures relating to non-replicated subsystems or nodes

are required. At the BS the concerned point will be the parent MSC. The subsystem
involved is the BSAP.

10

36
37

264

TIA/EIA/IS-2001

5.2.4

The MTP and the SCCP are used to support signaling messages between the MSC and
the BS. One user function of the SCCP, called Base Station Application Part (BSAP) is
defined. The BSAP uses one signaling connection for the transfer of layer 3 messages
per active Mobile Station (MS) having one or more active transactions (see section
5.2.4.3). The BSAP user function is further subdivided into two separate functions
called DTAP (Direct Transfer Application Part) and BSMAP (BS Management
Application Part).

2
3
4
5
6
7
8

Both connectionless (Class 0) and connection-oriented (Class 2) procedures are used to

support the BSMAP. The procedure descriptions in this specification explain whether
connection or connectionless services are to be used for each layer 3 procedure.

9
10
11

A distribution function located in BSAP, which is reflected in the protocol specification

by the layer 3 header defined in section 6.1.1.1, performs the discrimination between the
data related to those two subparts.

12
13
14

This section describes the use of an SCCP connection for an MS transaction. Section
5.2.4.1 identifies the Direct Transfer Application Part. Section 5.2.4.2 identifies the BS
Management Application Part. Section 5.2.4.3 describes the connection establishment
procedures. Section 5.2.4.4 describes the connection release procedures. Section 6.1.1.1
describes the distribution between BSMAP and DTAP messages and the data transfer
over an SCCP connection.

15
16
17
18
19
20

21

5.2.4.1

23
24
25
26
27
28

5.2.4.2

The BS Management Application Part

The BS Management Application Part (BSMAP) supports other procedures between
the MSC and the BS related to the MS, or to a cell within the BS, or to the whole BS.
The description of the layer 3 protocol for the BSMAP information exchange is
contained within this standard.

30
31
32
33

34

The Direct Transfer Application Part

The Direct Transfer Application Part (DTAP) is used to transfer call control and
mobility management messages to and from the MS. This layer 3 MSC-BS protocol in
support of the MS-MSC call control and mobile management information exchange is
referred to within this standard. The messages that transfer these information elements
are also defined within this standard. Those messages that are considered DTAP are
distinguished from BSMAP messages and are listed in Table 6-9, DTAP Messages, in
section 6.2.2.4.

22

29

Use of the SCCP

5.2.4.3

Connection Establishment

39

The initial messages exchanged in call setup are used to establish an SCCP connection
for subsequent signaling communications relating to the call. A new connection is
established when individual information related to an MS transaction has to be
exchanged between a BS and an MSC, and no such transaction exists between the MSC
and that BS.

40

Two connection establishment cases have to be distinguished:

35
36
37
38

41
42
43
44

Case 1.

A new transaction (e.g., Location updating - section 4; incoming or

outgoing call - section 2) is initiated on the radio path. Following an
Access Request made by the MS on the Random Access Channel,
the connection establishment is then initiated by the BS.

265

TIA/EIA/IS-2001

Case 2.

1
2

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

5.2.4.3.1

The MSC decides to perform an inter-BS Handoff (See section 3.3.2).

The connection establishment is then initiated by the MSC.

Establishment Procedure - case 1

In this case, the connection establishment is initiated at the reception by the BS of the
first layer 3 message from the MS. Generally, such a message contains the Mobile
Identity parameter (ESN, or IMSI). The BS then constructs the first MSC-BS Interface
BSMAP message (Complete Layer 3 Information) which includes one of the appropriate
DTAP messages (Location Updating Request, CM Service Request, or Paging
Response) depending on whether the mobile station is accessing the network for the
purpose of registration, call origination, or termination. The Complete Layer 3
Information message is sent to the MSC in the user data field of the SCCP Connection
Request message (see Figure 6-2 Structure of Layer 3 Message User Data Fields, in
section 6). The Complete Layer 3 Information message includes the cell identity and the
layer 3 message that was received from the mobile. The exact coding of the BSMAP
message is specified in section 6.
At the reception of the SCCP Connection Request message, the MSC may check, based
on the received identity, whether another association already exists for the same MS. If
it is the case, the connection establishment is refused. Otherwise, an SCCP Connection
Confirm message is sent back to the BS. This message may optionally contain a
BSMAP or DTAP message in the user data field.
The diagram in Figure 5-1 shows a successful SCCP connection establishment
procedure.
Time
BS

Comment

MSC

SCCP Connection Request: Complete Layer 3 Info

a
T3230

SCCP Connection Confirm

b

23
24

Figure 5- 1 - SCCP Connection Establishment

25

a.

The BS sends an SCCP Connection Request message, including a user data

field, to the MSC. The BS then starts timer T3230.

b.

Upon receipt an SCCP Connection Confirm message, which shall contain a

Layer 3 application message, the BS stops timer T3230 and establishes the
connection.

26
27
28
29

30

The procedures in case of connection establishment refusal are shown in Figure 5-2.
Time
BS

MSC

SCCP Connection Request: Complete Layer 3 Info

a
T3230

SCCP Connection Refused

b

31

266

Comment

TIA/EIA/IS-2001

Figure 5- 2 - SCCP Connection Establishment Refusal

1
2

a.

The BS sends an SCCP Connection Request message, including a user data

field, to the MSC. The BS then starts timer T3230.

b.

The MSC responds with an SCCP Connection Refused message. The BS

stops timer T3230.

3
4
5

If the user data field of the SCCP Connection Request message contains a Complete
Layer 3 Info message with a Location Updating Request application message, the MSC
shall respond with a SCCP Connection Refused message with a Location Updating
Accept or Location Updating Reject message in the user data field.

6
7
8
9

10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

5.2.4.3.2

Establishment Procedure - case 2

In this case, the connection establishment is undertaken by the MSC as soon as the
MSC decides to perform an inter-BS Handoff.
An SCCP Connection Request message is sent to the BS. The user data field of this
message shall contain the BSMAP Handoff Request message (see Figure 6-1,
Structure Of Layer 3 Message User Data Fields in section 6.1.1.1). The layer 3
messages shall be transferred in the user data field of the SCCP Connection Request in
order to complete the establishment of the relation between the radio channel requested
and the SCCP connection as soon as possible. The exact structure of the user data field
is explained in section 6.1.1.1.
When receiving the SCCP Connection Request message, the BS performs the necessary
checking and reserves, in the successful case, a radio channel for the requested
handoff. An SCCP Connection Confirm message is also returned to the MSC and shall
contain the BSMAP Handoff Request Acknowledge message in the user data field.
The diagram in Figure 5-3 shows a successful SCCP connection establishment
procedure during handoff.

Time
BS

Comment

MSC
SCCP Connection Request: Handoff Request
a
SCCP Connection Confirm

T3231
b

26
27
28

Figure 5- 3 - SCCP Connection Establishment During Handoff

a.

The MSC sends an SCCP Connection Request message, including a user data
field that contains a Handoff Request application message, to the BS. The
MSC starts timer T3231.

b.

Upon receipt, an SCCP Connection Confirm message, which shall contain the
Layer 3 application message Handoff Request Acknowledge, is returned to the
MSC. The MSC stops timer T3231.

29
30
31
32
33

34

The diagram in Figure 5-4 shows an SCCP connection refusal during handoff.

267

TIA/EIA/IS-2001

Time
BS

Comment

MSC
SCCP Connection Request: Handoff Request
a
SCCP Connection Refused

T3231
b

1
2
3
4

Figure 5- 4 - SCCP Connection Refusal During Handoff

a.

The MSC sends an SCCP Connection Request message, including a user data
field that contains a Handoff Request application message, to the BS. The
MSC starts timer T3231.

b.

Upon receipt, an SCCP Connection Refused message, which contains the

Layer 3 application message Handoff Failure, is returned to the MSC. The MSC
stops timer T3231.

5
6
7
8
9

268

TIA/EIA/IS-2001

5.2.4.4

Connection Release
This procedure is normally initiated at the MSC side but in the case of abnormal SCCP
connection release (see 5.2.4.5), the BS may initiate connection clearing.

2
3

The MSC initiates this procedure with respect to the source BS in normal conditions for
all calls supported by A1 connections.

4
5

A connection is released when a given signaling connection is no longer required. This

may occur in normal cases:

6
7
8

at the end of a transaction (call, location updating);

after completion of a successful external Handoff: the connection with the old
BS is released.

10

The MSC/BS sends a SCCP RLSD message. The user data field of this message is
optional and may contain a transparent layer 3 message (e.g., DTAP) or be empty. The
structure of the user data field, if any, is explained in section 6.1.1.1 A1 Message
Header.

11
12
13
14

When receiving this message, the BS/MSC releases all the radio resources allocated to
the relevant MS, if there are still any left, and sends a SCCP RLC back to the MSC/BS.

15
16

For abnormal cases a connection failure may be detected by the connection supervision
service provided by SCCP. If so, the Reset Circuit procedure described in section 5.5.3
Reset Circuit Procedure is used. For other abnormal SCCP connection releases, refer
to section 5.2.4.5 Abnormal SCCP Release.

17
18
19
20

21
22
23
24
25
26
27

5.2.4.5

Abnormal SCCP Release

The normal release of SCCP A1 connections is initiated by the MSC. Under abnormal
conditions, such an SCCP connection may be released by the BS in order to clear
resources.
Whenever a SCCP connection is abnormally released, all resources associated with that
connection shall be cleared. Abnormal release could result from, for example, resource
failure, protocol error, or unexpected receipt of the SCCP RLSD or SCCP RLC command.

269

TIA/EIA/IS-2001

1
2
3
4
5

5.2.4.5.1

SCCP Release by BS: Loss of SCCP Connection Information

The example below demonstrates release of an SCCP connection by the BS due to loss
of SCCP connection information. Note that when a circuit(s) is associated with the call
at the MSC, Reset Circuit/Reset Circuit Ack messages need to be exchanged between
the MSC and BS to guarantee release of the circuit by both the MSC and BS.
time
BS

comment

MSC
SCCP RLSD

SCCP RLC
b
Reset Circuit

Reset Circuit Ack

Conditional

T12
Conditional
d

6
7
8
9

Figure 5- 5 - BS Generated SCCP Release: BS Has Lost Access to SCCP Connection

Information
a.

An unexpected SCCP RLSD (under abnormal termination) is received by the

MSC from the BS.

b.

The MSC sends an SCCP RLC message to the BS to indicate that the SCCP
RLSD message has been received and that the appropriate procedures have
been completed.

c.

If a circuit was involved with the call at the MSC, the MSC starts timer T12 and
sends a Reset Circuit message to inform the BS that had sent the SCCP RLSD
to clear its call data. The Reset Circuit message carries the CIC of the trunk
whose corrupted connection was released.

d.

The Reset Circuit Ack message informs the MSC that the Reset Circuit has
been received and acted upon. The MSC stops timer T12.

10
11
12
13
14
15
16
17
18
19

270

TIA/EIA/IS-2001

1
2
3
4
5

5.2.4.5.2

SCCP Release by MSC: Loss of SCCP Connection Information

The example below demonstrates release of an SCCP connection by the MSC due to
loss of SCCP connection information. Note that when a circuit(s) is associated with the
call at the BS, Reset Circuit/Reset Circuit Ack messages need to be exchanged between
the MSC and BS to guarantee release of the circuit by both the MSC and BS.
time
BS

comment

MSC
SCCP RLSD

SCCP RLC
b
Reset Circuit
T12

Reset Circuit Ack

d

Condition
al
Condition
al

6
7
8
9

Figure 5- 6 - MSC Generated SCCP Release: MSC Has Lost Access to SCCP
Connection Information
a.

An unexpected SCCP RLSD (under abnormal termination) is received by the BS

from the MSC.

b.

The BS sends an SCCP RLC message to the MSC to indicate that the SCCP
RLSD message has been received and that the appropriate procedures have
been completed.

c.

If a circuit was involved with the call at the BS, the BS starts timer T12 and
sends a Reset Circuit message to inform the MSC which had sent the SCCP
RLSD to clear its call data. The Reset Circuit message carries the CIC of the
trunk whose corrupted connection was released.

d.

The Reset Circuit Ack message informs the BS that the Reset Circuit has been
received and acted upon. The BS stops timer T12.

10
11
12
13
14
15
16
17
18
19

271

TIA/EIA/IS-2001

5.2.4.6

SCCP Reference Generation Philosophy

Referring to Figure 5-7 SLR DLR Usage, the SCCP local reference number
(source/destination) is a three byte element internally chosen by the MSC or BS to
uniquely identify a signaling connection. In the direction MSC to BS, the source local
reference is chosen by the MSC and the destination local reference is chosen by the BS.
In the direction BS to MSC, the source local reference is chosen by the BS and the
destination local reference is chosen by the MSC. In the direction MSC to BS, the MSC
always echoes the BS SLR in the DLR field. In the direction BS to MSC, the BS always
echoes the MSC SLR in the DLR field. Note that it is the responsibility of the BS and
MSC to insure that no two calls have identical SCCP local reference numbers.

2
3
4
5
6
7
8
9
10

SLR (MSC), DLR (BS)

MSC

SLR (BS), DLR (MSC)

BS

SLR = Source Local Reference

DLR = Destination Local Reference
11
12

Figure 5- 7 - SLR/DLR Usage

13

MSC generation of SCCP local reference numbers shall conform to ANSI T1.112.4,
Section 3.1.2.

14

15

5.2.4.7

SCCP Transfer of DTAP and BSMAP Messages

18

The DTAP and BSMAP messages on the A1 interface are contained in the user data
field of the exchanged SCCP frames. Table 5-1 below summarizes the use of the User
Data Field in SCCP frames.

19

Table 5- 1 - Use of the User Data Field in SCCP Frames

16
17

SCCP Frame

User Data Field

(BSMAP/DTAP)

Connection Oriented (CO) Protocol Class 2

SCCP Connection Request (CR)

Optional

SCCP Connection Confirm (CC)

Optional

SCCP Connection Refused (CREF)

Optional

SCCP Released (RLSD)

Optional

SCCP Release Complete (RLC)

Not Applicable

SCCP Data Transfer 1 (DT1)

Mandatory

Connectionless (CL) Protocol Class 0

SCCP Unit Data (UDT)

Mandatory

20

272

TIA/EIA/IS-2001

1
2

For connection oriented transactions, a connection is requested, obtained or refused

using the following SCCP messages (protocol class 2):

SCCP Connection Request (CR)

SCCP Connection Confirm (CC)

SCCP Connection Refused (CREF)

SCCP Released (RLSD) and SCCP Release Complete (RLC) messages are used
to break a connection.

7
8
9
10
11
12
13
14
15
16
17

The use of the User Data Field in SCCP frames in the various establishment and release
cases is described in section 5.2.4.3 Connection Establishment and section 5.2.4.4
Connection Release.
For connection oriented transactions, once the signaling connection is confirmed
between the MSC and the BS, all A1 interface messages are transported in the SCCP
Data Transfer 1 (DT1) message until the connection is to be dropped.
For Connectionless (protocol class 0) transactions, where there is no SCCP connection,
A1 interface messages are transported in the SCCP Unit Data (UDT) message.
Table 5- 2 below indicates which SCCP messages shall be used to transport each of the
application messages on the A1 interface.

273

TIA/EIA/IS-2001

Table 5- 2 - Use of SCCP for BSMAP and DTAP Messages

Message

SCCP

Section

Discriminator

Message

Complete Layer 3 Information

6.1.2.1

BSMAP

CRa

CM Service Request

6.1.2.2

DTAP

CRa,g

Paging Request

6.1.2.3

BSMAP

UDTa

Paging Response

6.1.2.4

DTAP

CRa,g

Connect

6.1.2.10

DTAP

DT1

Progress

6.1.2.12

DTAP

DT1

Assignment Request

6.1.2.15

BSMAP

CCb , DT1

Assignment Complete

6.1.2.16

BSMAP

DT1

Assignment Failure

6.1.2.17

BSMAP

DT1

Clear Request

6.1.2.20

BSMAP

DT1

Clear Command

6.1.2.21

BSMAP

DT1

Clear Complete

6.1.2.22

BSMAP

DT1

Alert With Information

6.1.2.24

DTAP

DT1

BS Service Request

6.1.2.28

BSMAP

UDT

BS Service Response

6.1.2.29

BSMAP

UDT

Flash with Information

6.1.3.7

DTAP

DT1

Flash with Information Ack

6.1.3.8

DTAP

DT1

Feature Notification

6.1.3.9

BSMAP

UDTa

Feature Notification Ack

6.1.3.10

BSMAP

UDTa

Authentication Request

6.1.4.1

DTAP/BSMAP

DT1/UDTc

Authentication Response

6.1.4.2

DTAP/BSMAP

DT1/UDTc

SSD Update Request

6.1.4.4

DTAP/BSMAP

DT1

Base Station Challenge

6.1.4.5

DTAP/BSMAP

DT1

Base Station Challenge Response

6.1.4.6

DTAP/BSMAP

DT1

SSD Update Response

6.1.4.7

DTAP/BSMAP

DT1

Location Updating Request

6.1.4.8

DTAP

CRa,g

Location Updating Accept

6.1.4.9

DTAP

CREF

Location Updating Reject

6.1.4.10

DTAP

CREF

Privacy Mode Command

6.1.4.18

BSMAP

DT1

Application Message
Call Processing Messages

Supplementary Services Messages

Mobility Management Messages

274

TIA/EIA/IS-2001

Message

SCCP

Application Message

Section

Discriminator

Message

Privacy Mode Complete

6.1.4.19

BSMAP

DT1

275

TIA/EIA/IS-2001

Table 5 - 2 - Use of SCCP for BSMAP and DTAP Messages - continued

Message

SCCP

Section

Discriminator

Message

Handoff Required

6.1.5.4

BSMAP

DT1

Handoff Request

6.1.5.5

BSMAP

CRd

Handoff Request Acknowledge

6.1.5.6

BSMAP

CCd

Handoff Failure

6.1.5.7

BSMAP

DT1f, CREFe

Handoff Command

6.1.5.8

BSMAP

DT1

Handoff Required Reject

6.1.5.9

BSMAP

DT1

Handoff Commenced

6.1.5.10

BSMAP

DT1

Handoff Complete

6.1.5.11

BSMAP

DT1

Handoff Performed

6.1.5.12

BSMAP

DT1

Block

6.1.6.2

BSMAP

UDT

Block Acknowledge

6.1.6.3

BSMAP

UDT

Unblock

6.1.6.4

BSMAP

UDT

Unblock Acknowledge

6.1.6.5

BSMAP

UDT

Reset

6.1.6.6

BSMAP

UDT

Reset Acknowledge

6.1.6.7

BSMAP

UDT

Reset Circuit

6.1.6.8

BSMAP

UDT

Reset Circuit Acknowledge

6.1.6.9

BSMAP

UDT

Application Message
Handoff Messages

Facilities Management Messages

Application Data Delivery Service (ADDS) Messages

ADDS Page

6.1.7.1

BSMAP

UDT

ADDS Transfer

6.1.7.2

BSMAP

UDT

ADDS Deliver

6.1.7.3

DTAP

DT1

ADDS Page Ack

6.1.7.4

BSMAP

UDT

ADDS Deliver Ack

6.1.7.5

DTAP

DT1

6.1.8.1

DTAP/BSMAP

DT1/UDTc

Error Handling Messages

Rejection
2

276

TIA/EIA/IS-2001

Following are the footnotes referred to in table 5-2.

2
3

a.

Required, SCCP DT1 is not an option.

b.

May use in response to CM Service Request or Paging Response.

c.

Use only when procedure is being done on a paging channel.

d.

Required only for hard handoffs.

e.

May be used if responding to an SCCP Connection Request/Handoff Request.

f.

May be used after an SCCP connection has been established.

g.

Sent within Complete Layer 3 Information, which is a BSMAP message.

277

TIA/EIA/IS-2001

5.3

Asynchronous Transfer Mode (ATM) is a suite of protocols that allow fast, efficient
delivery of user traffic in a packet environment. ATM, for the purposes of this
standard, consists of two main layers: the ATM Layer that uses the physical layer, and
the ATM Adaptation Layer that adapts the basic ATM layer to specific usage.

2
3
4
5

5.3.1

5.3.2

ATM Layer
The ATM Layer uses a basic 53 octet cell consisting of a 5 octet header and 48 octet
payload. This standard uses the ATM Layer as specified in ANSI T1.627-1993
Telecommunications Broadband ISDN - ATM Layer Functionality and Specification
without modification.

10
11
12
13

For this specification only ATM permanent virtual circuits (PVCs) shall be required for
the A3 and A7 interfaces. These virtual circuits shall be configured through
administrative procedures and no special signaling interface procedures, e.g., ATM UNI
(Q.2931), shall be required.

14
15
16
17

18

Field of Application
Asynchronous Transfer Mode (ATM) is used to transport both signaling and user
traffic (voice/data).

Use of ATM (Layer 2)

5.3.3

ATM Adaptation Layer

20

To make use of the basic cell transfer capability of the ATM Transport Layer in specific
usages, various ATM Adaptation Layers (AALs) have been defined.

21

Within this standard, two AALs are used:

22

AAL59 - for the transfer of signaling, and

23

AAL210 - for the transfer of user traffic (voice/data) on A3 traffic subchannels.

19

24
25
26
27
28
29

Both AAL5 and AAL2 will be used without modification in this standard. The Service
Specific Segmentation and Reassembly (SSSAR) sublayer for AAL2, as specified in
ITU-T I.366.1, is used for segmentation and reassembly of AAL2 SDUs.
In this version of this standard, the functionality of other sublayers of AAL2 are not
supported. Specifically, Service Specific Transmission Error Detection (SSTED) and
Service Specific Assured Data Transfer (SSADT) are not included.

9 AAL5 is described in ITU-T I.363.5, B-ISDN ATM Adaption Layer Specification:

Type 5 AAL, August 1996.

10 AAL2 is described in ITU-T Recommendation I.363.2, B-ISDN ATM Adaptation

Layer Type 2 Specification, September 1997.

278

TIA/EIA/IS-2001

5.4

Network and Transport Protocols

5.4.1

Signaling Connection Transport Protocol Options

4
5
6
7
8
9
10

Signaling over the A1, A3 and A7 interfaces requires a reliable transport protocol and
appropriate addressing and routing mechanisms to deliver messages from source to
destination. The IOS application is independent of the underlying transport, which is
left to the discretion of operators and manufacturers. The signaling protocol stack
options available to operators and manufacturers for the A1, A3 and A7 interfaces
include:
A1 Interface:

11

IOS Application
SCCP
MTP3
MTP2
MTP1
Phys. Lyr.
12
13

A3 Interface (signaling connection):

14

IOS Application
TCP
IP
AAL5
ATM
Phys. Lyr.
15
16

A7 Interface (signaling connection):

17

IOS Application
TCP
IP
AAL5
ATM
Phys. Lyr.
18

279

TIA/EIA/IS-2001

A9 Interface (signaling connection):

A9 Signaling
TCP/UDP
IP
Link Layer
Phys. Lyr.
3
4

A11 Interface (signaling connection):

A11 Signaling
UDP
IP
Link Layer
Phys. Lyr.
6

280

TIA/EIA/IS-2001

5.4.2

User Traffic Connection Transport Protocol Options

The protocol stack options for transport of user traffic that are available to operators
and manufacturers include:

A2 Interface:

56/64 kbits/sec PCM

DS0
6
7

A3 Interface (user traffic subchannel):

User Traffic Frame

SSSAR
AAL2
ATM
Phys. Layer
9
10

A5 Interface:

11

Data Octet Stream

ISLP
DS0
12
13

A8 Interface:

14

GRE
IP
Link Layer
Phys. Layer
15
16

A10 Interface:

17

GRE
IP
Link Layer
Phys. Layer
18

281

TIA/EIA/IS-2001

5.4.3

The standard TCP protocol, as described in reference 3, section 1.5.4, shall be used for
establishing, using, and clearing TCP connections.

2
3

5.4.3.1

The TCP protocol provides a reliable byte stream transfer. Therefore, a means needs to
be provided for two application entities to delimit the messages sent between them.
The technique for such delimitation is given below.

7
8
9

11
12
13
14
15
16
17
18

General Use of TCP

TCP connections for signaling may be set up on a per-call basis or signaling messages
for multiple calls may be multiplexed on a single TCP connection.

10

TCP Transport Protocol Usage

5.4.3.1.1

Message Delimiting in TCP

TCP provides a reliable byte stream between two application entities. Because the
protocol in this standard uses messages to communicate, these messages shall be
delimited in the TCP byte stream. Such delimitation shall be done by means of a two
byte flag field and a two byte length field inserted at the beginning of each message
sent over a TCP connection. The flag field shall contain the hex value F634. The
purpose of the flag field is to facilitate verification of message boundaries, and fast
reestablishment of synchronization if synchronization of message boundaries is lost.
See Figure 5-8 below.

282

TIA/EIA/IS-2001

Flag

Flag

Length

(MSB)

Length

(LSB)
First Octet of IOS Application Message
Second Octet of IOS Application Message

Msg

Third Octet of IOS Application Message

...
Last Octet of IOS Application Message

Flag

Flag

Length

(MSB)

Length

(LSB)
First Octet of IOS Application Message
Second Octet of IOS Application Message

Msg

Third Octet of IOS Application Message

...
Last Octet of IOS Application Message

Flag

Flag

Length

(MSB)

Length

(LSB)
First Octet of IOS Application Message
Second Octet of IOS Application Message

Msg

Third Octet of IOS Application Message

...

Figure 5- 8 - Delimiting Messages in an IOS Application TCP Byte Stream

3
4
5
6

5.4.3.1.2

TCP Connection Establishment

A new TCP connection is established when a signaling message related to a call has to
be exchanged over an interface, and no such connection exists over the particular
interface. Normal TCP connection establishment procedures are used.

283

TIA/EIA/IS-2001

5.4.3.1.3

An existing TCP connection over an interface is released when there are no more
signaling messages to be exchanged over the interface. Normal TCP connection release
procedures are used.

2
3
4

TCP Connection Release

5.4.3.1.4

TCP Port Usage

The following TCP port values are reserved for signaling across A interfaces:

A7: (BS-to-BS) 5602 -- This is the well-known TCP port at a BS used for signaling
interconnection to another BS.

A9: (BS-to-PCF) 5603 -- This is the well-known TCP/UDP port at a BS used for signaling
interconnection to a PCF.

9
10

11

5.4.3.2

The standard "Transmission Control Protocol (TCP)", as described in RFC793 and

shown in section 5.4.1 shall be used on the A3 (signaling subchannel) and A7
interfaces.

12
13
14

15
16
17
18

Use of TCP for the A3 and A7 Interfaces

5.4.3.3

Use of TCP for the A9 Interface

When TCP is used for transferring the A9 interface messages, the standard
"Transmission Control Protocol (TCP)", as described in RFC793 and shown in section
5.4.1, shall be used.

284

TIA/EIA/IS-2001

5.4.4

IP Network Protocol Usage

The standard IP protocol, as defined in RFC 791 (see section 1.5.4), shall be used for
routing Internet Protocol packets. When IP is used as the network layer for the A10
bearer, standard IP QoS mechanisms may be employed.

2
3
4

5.4.5

UDP Transport Protocol Usage

5.4.5.1

UDP Transport Protocol Usage for the A11 Interface

The use of UDP over the A11 interface conforms to the use of UDP for Mobile IP, as
specified in RFC 2002.

7
8

5.4.5.2

UDP Transport Protocol Usage for the A9 Interface

11

When UDP is used for transferring the A9 interface messages, the standard "User
Datagram Protocol (UDP)", as described in RFC768, shall be used.

12

The following UDP port value is reserved for signaling across A9 interface:

13

A9: (BS-to-PCF) 5603 -- This is the well-known UDP port at a BS used for signaling
interconnection to a PCF.

10

14
15
16
17
18
19
20

The initiator of an A9_Link (BS) would pick an available source UDP port, and send an
A9-Setup-A8 message to the destination ( PCF) at port 5603. The PCF will respond with
an A9-Connect-A8 message to the initiator's (BS) UDP port that initiated the A9-SetupA8 message.
The UDP protocol provides a transfer mechanism between the BS and the PCF with a
minimum of overhead.

21

285

TIA/EIA/IS-2001

5.4.6

Mobile IP Protocol Usage

Mobile IP based messages are used for A11 interface call control signaling and for
passing accounting related and other information from the PCF to the PDSN. The A11
interface messages use Mobile IP well-known port (434). Each control message is
transported within a UDP datagram. The initiator of the A10 connection (PCF) picks an
available source UDP port, and sends a connection request message to the selected
PDSN at UDP port 434. The recipient (PDSN) sends a reply message to the initiators
(PCF) UDP port that initiated the connection request.

2
3
4
5
6
7
8
9

10

5.4.6.1

Mobile IP Based Tunneling Protocol

5.4.6.1.1

Mobile IP Extensions

11

12

This section describes extensions to the Mobile IP protocol for the Aquater interface
within the TIA/EIA/IS-2000 network.

13
14

15

5.4.6.1.1.1

In a cdma2000 network, the Mobile Station initiates a connection by sending a call

setup indication to the BS/PCF across the radio network. When this indication is
received by a BS/PCF, a Registration Request will be sent from the BS/PCF to the PDSN
to setup a new A10 connection.

16
17
18
19

The BS/PCF sends a Registration Request with the GRE encapsulation and the reverse
tunneling bit set. The Home Address field is set to zero. The Home Agent field will be
assigned to the IP address of the PDSN and the Care-of Address field will be assigned
to the IP address of the BS/PCF.

20
21
22
23

When a Registration Request is received by a PDSN, the information from the Session
Specific Extension will be used to identify a packet data session. When a registration is
accepted, a GRE tunnel will be created for this Mobile Station.

24
25
26

27

5.4.6.1.1.2

29
30
31

33
34

Registration Reply
The Registration Reply will be sent by a PDSN following the procedure as described in
[RFC 2002]. The Home Address field will be the same value as the Home Address field
from the corresponding Registration Request message received by the PDSN. The
Session Specific Extension MUST be included in the message.

28

32

Registration Request

5.4.6.1.1.3

Registration Update/Acknowledge
Two new messages are defined to support PDSN initiated A10/A11 connection tear
down and to speed up resource reclamation on the BS/PCF.

37

The Registration Update message is used for notification of the change of the
registration associated with a call. It shall be sent by the PDSN to the previous BS/PCF
when a BS/PCF to BS/PCF handoff occurs.

38

Both messages are sent with UDP using well-known port number 434.

35
36

286

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11

5.4.6.1.1.4

Registration Update Authentication Extension

The Registration Update Authentication extension is used to authenticate the
Registration Update and Registration Acknowledge messages. It has the same format
and default algorithm support requirements as the authentication extension defined for
the Mobile IP protocol [RFC 2002], but with a different type (40). The authenticator
value is computed from the stream of bytes including the shared secret, the UDP
payload, all prior extensions in their entirety, and the type and length of this extension,
but not including the authenticator field itself nor the UDP header. The secret used for
computing the authenticator field is shared between the BS/PCF and PDSN. This
extension is required in both Registration Update and Registration Acknowledge
messages.

287

TIA/EIA/IS-2001

5.4.7

GRE Protocol Usage

The upper layer for the A8 and A10 interfaces is the Generic Routing Encapsulation
protocol (GRE) as defined in RFC 1701.

GRE encapsulates user traffic as shown below.

GRE Header

User Traffic

5
6

Figure 5- 9 - GRE Encapsulated User Traffic

Figure 5- 10 shows the structure of the GRE header.

0
1
2
3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 9 0 1 2
C R K S s

Recur

Flags

Bit Num.

Protocol Type

Ver

Octet: 5-8

Key
Sequence Number (optional)

10

Figure 5- 10 - GRE Header

The flags and other fields in the GRE header are encoded as follows:

11

C (Checksum Present)

12

R (Routing Present)

13

K (Key Present)

14

S (Sequence Number Present)

0/1

15

s (Strict Source Route Present)

16

Recur (Recursion Control)

0s

17

Flags

0s

18

Ver (Version Number)

0s

19

Protocol Type

Hex 88 0B for PPP

Hex 88 81 for Unstructured Byte
Stream

20
21

288

Octet: 1-4

Octet: 9-12

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10

The BS/PCF and the PDSN set the Key field in the GRE header to the PCF Session
Identifier (PSI) for the call. If the link layer/network layer protocol requires that the
packets be delivered in sequence, the sequence number field is used. The Sequence
Numbers are per packet sequence numbers. Both the BS/PCF and the PDSN set the
Sequence Number to zero at packet session startup. Each packet sent for a given
session is assigned the next consecutive sequence number. Roll-overs of the sequence
numbers are handled appropriately. For protocols such as PPP and Async PPP, that
require in-sequence receipt of packets, if the packets arriving at the BS/PCF or the
PDSN lose their sequencing across the A10/A11 interface, the receiving entity may
attempt to resequence the packets before delivering to the PPP layer.

289

TIA/EIA/IS-2001

5.5

The following sections describe those procedures involved with the management of
terrestrial circuits. Terrestrial circuits in the context of this section are those DS0
facilities that are used to carry traffic (voice or data) (A2) and signaling information (A1)
between the MSC and the BS. Also included are ATM virtual circuits (A3) that are used
to carry traffic (voice or data) and signaling information between the SDU and the BTS,
and A7 signaling information between the source BS and the target BS. Section 5.5.1
describes circuit allocation and deallocation. Section 5.5.2 describes blocking and
unblocking of terrestrial circuits. Section 5.5.3 describes resetting of circuits.

2
3
4
5
6
7
8
9

The terrestrial circuit management message structures and the information elements in
these messages are described in section 6.1.6.

10
11

The following definitions are to be used when considering the condition of a terrestrial
circuit:

12
13

available - The condition of a terrestrial circuit (A2) that is available for selection by the
MSC, or of a virtual circuit connection (A3) that is available for selection by the BTS.

14
15

blocked - The condition of a terrestrial circuit (A2) which the BS has identified as out of
service, and is therefore not available for selection by the MSC, or of a virtual circuit
connection (A3) which the SDU has identified as out of service, and is therefore not
available for selection by the BTS.

16
17
18
19

idle - The condition of a terrestrial circuit (A2) that is not carrying traffic, or of a virtual
circuit connection (A3) that is not carrying traffic. The idle condition does not imply
availability.

20
21
22

23

5.5.1

Terrestrial Circuit Allocation/Deallocation

This section describes Terrestrial Circuit Allocation.

24

25

Terrestrial Circuit Management Procedures

5.5.1.1

A2 Terrestrial Circuit Allocation

26

The MSC will choose the terrestrial circuit to be used.

27
28

The Terrestrial Circuit allocation procedure has been described in section 2.2.1.7
Assignment Request.

29

NOTE: There will be at least one single logical trunk group serving the BS.

30
31
32
33
34

5.5.1.2

A3 Connection Establishment
The BS will consider the interface to the SDU as a route of n virtual circuits. The BS
chooses the virtual circuit to be used.
The A3 connection establishment procedures have been described in section 3.4.1 A3
Interface Procedures and Messages .

290

TIA/EIA/IS-2001

5.5.2

Blocking will be handled in the following ways for each type of sub-interface.

5.5.2.1

5
6
7
8
9
10

The following sections describe the operation of and messages involved in the blocking
and unblocking procedures.

11
12

5.5.2.1.1

Block
The Block message is sent from the BS to the MSC to indicate that one or more
terrestrial circuits shall be blocked at the MSC and therefore cannot be used for traffic.

14
15

16

A2 Terrestrial Circuit Blocking/Unblocking

The MSC needs to be informed of any MSC-BS A2 terrestrial circuits that are out of
service or that return to service at the BS. The Block or Unblock message is sent by the
BS as a connectionless mode message for terrestrial circuits that are out of service or
that return to service. Upon receiving a Block or Unblock message, the MSC takes
appropriate action and acknowledges the action to the BS. The MSC may locally block a
circuit by not choosing it. No information flow across the interface concerning this type
of blocking is needed.

13

Blocking/Unblocking

5.5.2.1.1.1

Successful Operation
The BS sends a Block Message to the MSC and starts timer T1. The value of T1 shall be
set to a value to allow sufficient time for the MSC to block all circuits indicated in this
message. The message identifies at least one circuit (Circuit Identity Code) to be
blocked and the reason (Cause) of the blocking. The only way a terrestrial circuit may
become unblocked after it has been blocked is through a reset circuit procedure (from
the BS) (section 5.5.3), a global reset from either the MSC or BS, or an unblock
procedure (from the BS) (section 5.5.2.3). More than one circuit may be blocked using a
single Block message.

17
18
19
20
21
22
23
24

30

The MSC sends a Block Acknowledge message in response to the Block message after
taking appropriate action. A call that is already in progress on the specified circuit is not
affected by the Block message. The block becomes effective after the completion of the
call in progress. The MSC does not delay sending the Block Acknowledge message if a
call is in progress. If a circuit is already marked as blocked in the MSC, it remains
blocked and the MSC sends the Block Acknowledge message.

31

Please refer to section 6.1.6.2, Block, for the format and content of this message.

25
26
27
28
29

32
33
34
35
36
37
38
39

5.5.2.1.1.2

Failure Operation
If the BS does not receive a Block Acknowledge message before the expiration of timer
T1, then the BS shall send the Block message a second and final time and shall mark the
indicated circuit(s) as blocked.
If an Assignment Request message is received for a circuit which is marked at the BS as
blocked then the BS shall send an Assignment Failure message with a cause value of
Terrestrial resource is not available followed by a Block message with a cause value
of No radio resource available. Please refer to Figure 5-9.

291

TIA/EIA/IS-2001

5.5.2.1.2

The MSC sends this message to the BS to acknowledge receipt of the Block message
and to indicate that appropriate action has been taken.

2
3

5.5.2.1.2.1

6
7
8
9
10

If multiple circuits were indicated in the Block message, the response applies to all of
those circuits.

11
12

Please refer to section 6.1.6.3, Block Acknowledge, for the format and content of this
message.

13
14

5.5.2.1.2.2

18

Failure Operation
None.

16

17

Successful Operation
After the MSC blocks all of the circuits specified in the Block message, the MSC sends
a Block Acknowledge message to the BS. The Block Acknowledge message indicates to
the BS that the necessary action has been taken. The circuits involved are assumed to
be blocked by the MSC until a Reset message or an Unblock message relevant to the
circuits is received from the BS. The Block Acknowledge message returns the Circuit
Identity Code(s) of the corresponding Block message.

15

Block Acknowledge

5.5.2.1.2.3

Scenario Diagram
Figure 5-11 below shows the Block procedure.
Time
BS

Comment

MSC

Block
a
T1

Block Acknowledge

19
20
21
22

Figure 5- 11 - Block Procedure

a.

The BS sends the Block message to the MSC with information on the circuits
to be blocked. Timer T1 is started by the BS.

b.

In response to the Block message, the MSC returns a Block Acknowledge

message, indicating the involved circuit have been blocked. Timer T1 is
stopped by the BS.

23
24
25
26

292

TIA/EIA/IS-2001

5.5.2.1.3

This BSMAP message is used by the BS to notify the MSC that the specified circuits
are available for use.

2
3

Unblock

5.5.2.1.3.1

Successful Operation
If the BS wishes to unblock blocked circuits, an Unblock message is sent to the MSC.
The BS sends the Unblock message, marks all circuits included in the Unblock message
as unblocked, and starts timer T1. The value of T1 shall be set to a value to allow
sufficient time for the MSC to unblock all circuits indicated in this message. Upon
receipt of the Unblock message from the BS, the MSC marks the circuit as available at
the BS and sends an Unblock Acknowledge message to the BS. The Unblock
Acknowledge message returns the Circuit Identity Code of the corresponding Unblock
message. If a circuit is already marked as unblocked in the MSC, it remains unblocked
and the MSC sends the Unblock Acknowledge message.

5
6
7
8
9
10
11
12
13

15

If multiple circuits were indicated in the Unblock message, the response applies to all of
those circuits.

16

Please refer to section 6.1.6.4, Unblock, for the format and content of this message.

14

17

5.5.2.1.3.2

If the BS does not receive the Unblock Acknowledge message before the expiration of
timer T1, then the BS shall send the Unblock message a second and final time. If timer
T1 expires on the second attempt, the BS shall mark the indicated circuit(s) as
unblocked.

18
19
20
21

22

5.5.2.1.4

Unblock Acknowledge
The MSC responds to the BS request to unblock circuits by sending an Unblock
Acknowledge message. The MSC marks such circuits as available at the BS before it
sends the Unblock Acknowledge message to the BS.

23
24
25

26

Failure Operation

5.5.2.1.4.1

Successful Operation

27

Please refer to Section 5.5.2.1.3.1.

28

Please refer to section 6.1.6.5, Unblock Acknowledge, for the format and content of
this message.

29

30
31

5.5.2.1.4.2

Failure Operation
None.

293

TIA/EIA/IS-2001

5.5.2.1.4.3

Scenario Diagram
The diagram in Figure 5-12 shows the Unblock procedure.

Time
BS

Comment

MSC

Unblock
a
T1

Unblock Acknowledge

3
4

Figure 5- 12 - Unblock Procedure

5
6

a.

The BS sends the Unblock message to the MSC in a request to unblock

blocked circuits. Timer T1 is started by the BS.

b.

The MSC marks the circuits as available and sends the Unblock Acknowledge
message to the BS. Timer T1 is stopped by the BS.

7
8
9

10

5.5.3

The reset circuit procedure is needed to initialize information in the MSC/BS when a
failure has occurred affecting only a small part of the equipment and in which the SCCP
connection has been released. If the MSC/BS detects that one or more circuits have to
be idled due to abnormal SCCP connection release, a Reset Circuit message is sent.
Upon receipt of the Reset Circuit message, the receiver idles the indicated circuits and
returns an acknowledgment.

11
12
13
14
15
16

The following sections describe the operation of and messages involved in the reset
circuit procedure.

17
18

19

5.5.3.1

21
22

24
25
26
27
28
29
30

A1 Reset Circuit (at the BS)

If the BS detects that one or more circuits have to be idled due to abnormal SCCPconnection release, it sends a Reset Circuit message to the MSC indicating the Circuit
Identity Code(s) which the MSC is to idle and the reason (Cause) of the circuit reset.

20

23

Reset Circuit Procedure

5.5.3.1.1

Successful Operation
The BS sends a Reset Circuit message and starts timer T12. The value of T12 shall be
set to a value to allow sufficient time for the MSC to reset all circuits indicated in this
message. When the MSC receives the Reset Circuit message, it clears the possible
calls, marks the indicated circuits as idle, and returns a Reset Circuit Acknowledge
message to the BS.
Please refer to section 6.1.6.8, Reset Circuit, for the format and content of this
message.

294

TIA/EIA/IS-2001

5.5.3.1.2

If the BS does not receive or recognize the Reset Circuit Acknowledge message before
the expiration of timer T12, the Reset Circuit message is repeated. The Reset Circuit
message shall be sent no more than three times.

2
3
4

If the Reset Circuit Acknowledge message is never received or recognized by the BS,
then the situation (i.e., possibly incompatible device states between the BS and MSC)
shall be resolved internally in the BS or by OAM&P procedures.

5
6
7

5.5.3.2

A1 Reset Circuit Acknowledge (from MSC)

The Reset Circuit Acknowledge message is sent from the MSC to the BS to
acknowledge that the MSC has reset (idled) the circuits indicated in the corresponding
Reset Circuit message.

9
10
11

12

Failure Operation

5.5.3.2.1

Successful Operation

14

When the MSC receives a Reset Circuit message, it idles the circuits and sends a Reset
Circuit Acknowledge message to the BS.

15

Upon receipt of the Reset Circuit Acknowledge message, the BS stops timer T12.

16

Please refer to section 6.1.6.9, Reset Circuit Acknowledge, for the format and content
of this message.

13

17

18

5.5.3.2.2

None.

19

20
21

Failure Operation

5.5.3.2.3

Scenario Diagram
The diagram in Figure 5-13 shows the Reset Circuit procedure.
Time
BS

Comment

MSC
Reset Circuit
a
T12

Reset Circuit Acknowledge

22
23
24
25

Figure 5- 13 A1 Reset Circuit Procedure at the BS

a.

Once the BS detects that one or more circuits have to be idled, it sends a Reset
Circuit message to the MSC with information on the circuit identities and the
cause of the reset. Timer T12 is started by the BS after sending of the Reset
Circuit message.

b.

Upon receipt of the Reset Circuit message, the MSC returns a Reset Circuit
Acknowledge message to indicate that the circuits have been reset. Timer T12
is stopped by the BS.

26
27
28
29
30
31

295

TIA/EIA/IS-2001

5.5.3.3

If the MSC detects that one or more circuits have to be put to idle due to abnormal
SCCP connection release or OAM&P intervention, it sends a Reset Circuit message to
the BS indicating the circuits which the BS is to idle and the cause of the circuit reset.

2
3
4

5.5.3.3.1

7
8
9
10
11
12
13
14
15
16

Please refer to section 6.1.6.8, Reset Circuit, for the format and content of this
message.

17
18

5.5.3.3.2

21
22

5.5.3.4

25
26

5.5.3.4.1

29

Please refer to section 6.1.6.9, Reset Circuit Acknowledge, for the format and content
of this message.

30
31

5.5.3.4.2

5.5.3.4.3

36

38

Scenario Diagrams
The two diagrams in the subsections below show the use of the Reset Circuit procedure
at the MSC.

35

37

Failure Operation
None.

33

34

Successful Operation
Upon receipt of the Reset Circuit Acknowledge or Block message from the BS, the MSC
stops timer T12.

28

32

A1 Reset Circuit Acknowledge (from BS)

The Reset Circuit Acknowledge message is sent from the BS to the MSC to
acknowledge that the BS has reset (idled) the circuits indicated in the corresponding
Reset Circuit message.

24

27

Failure Operation
If the MSC does not receive the Reset Circuit Acknowledge message or a Block
message before the expiration of timer T12, the Reset Circuit message is sent a second
and final time.

20

23

Successful Operation
To idle circuits, the MSC sends a Reset Circuit message to the BS and starts timer T12.
The value of T12 shall be set to a value to allow sufficient time for the BS to reset all
circuits indicated in this message. When the BS receives a Reset Circuit message, it
shall respond with a Reset Circuit Acknowledge message in the case that all of the
circuit(s) can be put to idle. If all of the circuits are blocked at the BS at reception of the
Reset Circuit message, a Block message will be returned to the MSC instead of the
Reset Circuit Acknowledge message. If some of the circuits are blocked at the BS at
reception of the Reset Circuit message, a Block message will be returned to the MSC
indicating those blocked circuits. The MSC responds with a Block Acknowledge
message to any Block message it receives if it successfully blocks all of the circuits
specified in the Block message.

19

A1 Reset Circuit (at the MSC)

5.5.3.4.3.1

A1 Reset Circuit Procedure at the MSC

The diagram in Figure 5-14 shows a simple reset circuit procedure initiated by the MSC.

296

TIA/EIA/IS-2001

Time
BS

Comment

MSC

Reset Circuit
a
Reset Circuit Acknowledge

T12
b

1
2

Figure 5- 14 A1 Reset Circuit Procedure at the MSC

3
4

a.

Once the MSC detects that one or more circuits have to be put to idle, it sends
a Reset Circuit message to the BS with information on the circuits and the
cause of the reset. Timer T12 is started by the MSC.

b.

Upon receipt of the Reset Circuit message, the BS returns a Reset Circuit
Acknowledge message to indicate that the circuits have been reset. Timer T12
is stopped by the MSC.

5
6
7
8
9

10
11
12

5.5.3.4.3.2

A1 Reset Circuit Procedure at the MSC with BS Block Response

The diagram in Figure 5-15 shows a reset circuit procedure initiated by the MSC that is
responded to from the BS by a Block message.
Time
BS

Comment

MSC

Reset Circuit
a
Block

T12
b

T1

Block Acknowledge

13
14
15
16

Figure 5- 15 - Reset Circuit Procedure at the MSC with BS Block Response

a.

Once the MSC detects that one or more circuits have to be put to idle, it sends
a Reset Circuit message to the BS with information on the circuit identities and
the cause of the reset. Timer T12 is started by the MSC.

b.

If the BS cannot set a circuit to idle it sends the Block message to the MSC
with information on the circuit identities to be blocked and the cause of the
blocking. Timer T1 is started by the BS. In this example, it is assumed that all of
the circuits indicated in the Reset Circuit message need to be blocked. The
MSC stops Timer T12 upon receipt of the Block message.

c.

In response to the Block message, the MSC returns a Block Acknowledge

message, indicating the involved circuit have been blocked. Timer T1 is
stopped by the BS upon receipt of the Block Acknowledge message.

17
18
19
20
21
22
23
24
25
26

297

TIA/EIA/IS-2001

5.5.4

The purpose of the global system reset procedure is to cause the initialization of the
MSC or BSC in the event of a global failure by its counterpart. Since the type of failure
is global, the messages of the procedure are sent as connectionless messages on the
A1 interface. The A7 procedure uses connection-oriented messages on the underlying
transport connection.

2
3
4
5
6

Upon detection of a global failure or as a result of an initialization, the BSC or MSC

sends an A1/A7 global reset message to its counterpart. The counterpart then performs
all necessary initialization functions such as: releasing of affected calls and references,
idling of circuits, blocking of circuits, and ensuring as necessary that all MSs
previously involved in a call are no longer transmitting. After a guard period sufficient
to allow all necessary initialization to occur, the counterpart acknowledges the A1/A7
global reset message.

7
8
9
10
11
12
13

The following sections describe the operation of and messages involved in the reset
procedures. The message structures and the information elements in these messages
are described in sections 6.1.6.6, 6.1.6.7, 6.1.12.11, and 6.1.12.12.

14
15
16

17

5.5.4.1

19
20

22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

A1 Reset
In the event of a failure or initialization at the BS or MSC that has resulted in the loss of
transaction reference information, a Reset message is sent on the A1 interface to the
counterpart of the equipment that is resetting to indicate the reason for the reset.

18

21

Global System Reset

5.5.4.1.1

Successful Operation
Reset sent by the BS:
Upon initialization, the BS shall send a Reset message to the MSC and start timer
T4.
Upon receipt of the Reset message from the BS, the MSC releases affected calls
and erases all affected references, and puts all circuits associated with the BS into
the idle state and shall mark all circuits as unblocked. During reinitialization, the BS
may use the blocking procedure to mark circuits as blocked. After a guard period
of T2 seconds a Reset Acknowledge message is returned to the BS indicating that
all references have been cleared.
If timer T16 is running at the MSC when the Reset message is received from the BS,
the MSC shall stop timer T16, start timer T2, complete initialization, and then return
a Reset Acknowledge message to the BS after timer T2 expires.
Reset sent by the MSC:
Upon initialization, the MSC shall send a Reset message to each affected BS and
start timer T16.
Upon receipt of a Reset message from the MSC, the BS shall release all affected
calls and erase all affected references. The BS may use the blocking procedure to
mark circuits as blocked as described in section 5.5.2 and shall idle all others. After
a guard period of T13 seconds a Reset Acknowledge message is returned to the
MSC, indicating that all MSs that were involved in a call are no longer transmitting
and that all references at the BS have been cleared.
If timer T4 is running at the BS when the Reset message is received from the MSC,
the BS shall stop timer T4, start timer T13, complete initialization, and then return a
Reset Acknowledge to the MSC after timer T13 expires.

298

TIA/EIA/IS-2001

Please refer to section 6.1.6.6, Reset, for the format and content of this message.

5.5.4.1.2

If the BS sends a Reset message to the MSC and receives no Reset Acknowledge
message within period T4, then it shall repeat the entire reset procedure.

3
4

If the MSC sends a Reset message to the BS and receives no Reset Acknowledge
message within period T16 then it shall repeat the reset procedure with respect to that
BS.

5
6
7

If a Reset message is received that contains a protocol version less than the protocol
version of the receiver but unknown to the receiver, then the receiver may raise an
OA&M flag and choose not to respond to the sender.

8
9
10

11

5.5.4.2

5.5.4.2.1

15
16
17
18

When the BS has received a Reset message from the MSC, the BS sends a Reset
Acknowledge message after a guard period of T13 seconds to the MSC to indicate that
the Reset message was received and that all references have been cleared. When the
MSC receives the Reset Acknowledge message, it stops timer T16 if it is running and
begins normal operation.

19
20
21
22
23

Please refer to section 6.1.6.7, Reset Acknowledge, for the format and content of this
message.

24
25

27

Successful Operation
When the MSC has received a Reset message from a BS, the MSC, after a guard period
of T2 seconds, sends a Reset Acknowledge message to the BS to indicate that the
Reset message is received and that all references have been cleared. When the BS
receives the Reset Acknowledge message, it stops timer T4 if it is running and begins
normal operation.

14

26

A1 Reset Acknowledge
The Reset Acknowledge message is sent in response to a Reset message.

12

13

Failure Operation

5.5.4.2.2

Failure Operation
None.

299

TIA/EIA/IS-2001

5.5.4.3

This section contains examples of the Reset procedure, including glare situations.

3
4

A1 Global Reset Examples

5.5.4.3.1

Successful Rese t at the MSC

This example shows a successful reset procedure when the MSC (re-)initializes.
Time
BS

Comment

MSC
Reset
a
T13

T16

BS blocks circuits as necessary

using the blocking procedure.

Reset Acknowledge
c

5
6

Figure 5- 16 - Successful Reset at the MSC

a.

As the MSC (re-)initializes, it sends a Reset message to the BS to notify the BS of

the reset procedure it is undertaking. The MSC starts timer T16. The BS starts timer
T13.

b.

The BS may use the circuit blocking procedure to block circuits, as necessary,
between itself and the MSC.

c.

Upon expiration of timer T13, the BS returns a Reset Acknowledge message. The
MSC stops timer T16. Both the MSC and BS begin normal operations relative to
each other.

8
9
10
11
12
13
14

300

TIA/EIA/IS-2001

1
2

5.5.4.3.2

Successful Reset at the BS

This example shows a successful reset procedure when the BS (re-)initializes.
Time
BS

Comment

MSC

Reset
a
T4

T2

BS blocks circuits as necessary

using the blocking procedure.

Reset Acknowledge

3
4

Figure 5- 17 - Successful Reset at the BS

a.

As the BS (re-)initializes, it sends a Reset message to the MSC to notify the MSC of
the reset procedure it is undertaking. The MSC starts timer T2. The BS starts timer
T4.

b.

The BS may use the circuit blocking procedure to block circuits, as necessary,
between itself and the MSC.

c.

Upon expiration of timer T2, the MSC returns a Reset Acknowledge message. Timer
T4 is stopped by the BS. Both the MSC and BS begin normal operations relative to
each other.

6
7
8
9
10
11
12

301

TIA/EIA/IS-2001

1
2
3
4
5
6

5.5.4.3.3

Reset Glare Noted at the MSC

This example shows parallel reset procedures at the BS and MSC. In this case, the MSC
notes that a timing condition has occurred since the Reset message from the BS arrives
after the Reset message is sent from the MSC. The MSC shall assume that the Reset
message it has sent has been lost. As a result, the MSC shall act as though it is not
also performing a reset procedure.
Time
BS

Comment

MSC

Reset
a
T16
Reset
b
T4

T2

BS blocks circuits as necessary

using the blocking procedure.

Reset Acknowledge

7
8

Figure 5- 18 - Reset Glare Noted at the MSC

a.

As the MSC (re-) initializes, it sends a Reset message to the BS to notify the BS of
the reset procedure it is undertaking. The MSC starts timer T16. In this example, the
Reset message is lost or cannot be successfully processed by the BS.

b.

As the BS (re-) initializes, it sends a Reset message to the MSC to notify the MSC of
the reset procedure it is undertaking. The MSC stops timer T16 and starts timer T2.
The BS starts timer T4.

c.

The BS may use the circuit blocking procedure to block circuits, as necessary,
between itself and the MSC.

d.

Upon expiration of timer T2, the MSC returns a Reset Acknowledge message. Timer
T4 is stopped by the BS. Both the MSC and BS begin normal operations relative to
each other.

10
11
12
13
14
15
16
17
18
19

302

TIA/EIA/IS-2001

1
2
3
4
5
6

5.5.4.3.4

Reset Glare Noted at the BS

This example shows parallel reset procedures at the BS and MSC. In this case, the BS
notes that a timing condition has occurred since the Reset message from the MSC
arrives after the Reset message is sent from the BS. The BS shall assume that the Reset
message it has sent has been lost. As a result, the BS shall act as though it is not also
performing a reset procedure.
Time
BS

Comment

MSC

Reset
a
T4

Reset
b
T13

T16

BS blocks circuits as necessary

using the blocking procedure.

Reset Acknowledge
d

7
8

Figure 5- 19 - Reset Glare Noted at the BS

a.

As the BS (re-) initializes, it sends a Reset message to the MSC to notify the MSC of
the reset procedure it is undertaking. The BS starts timer T4. In this example, the
Reset message is lost or cannot be successfully processed by the MSC.

b.

As the MSC (re-) initializes, it sends a Reset message to the BS to notify the BS of
the reset procedure it is undertaking. The BS stops timer T4 and starts timer T16.
The BS starts timer T13.

c.

The BS uses the circuit blocking procedure to block circuits, as necessary, between
itself and the MSC.

d.

Upon expiration of timer T13, the BS returns a Reset Acknowledge message. Timer
T16 is stopped by the MSC. Both the MSC and BS begin normal operations relative
to each other.

10
11
12
13
14
15
16
17
18
19

303

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10

5.5.4.3.5

Reset Glare Noted at Both the MSC and the BS

This example shows parallel reset procedures at the BS and MSC. In this case, the
Reset messages pass each other enroute and are both received. The BS notes that a
timing condition has occurred since the Reset message from the MSC arrives after the
Reset message is sent from the BS. The BS shall assume that the Reset message it has
sent has been lost. As a result, the BS shall act as though it is not also performing a
reset procedure. Similarly, the MSC notes that a timing condition has occurred since
the Reset message from the BS arrives after the Reset message is sent from the MSC.
The MSC shall assume that the Reset message it has sent has been lost. As a result,
the MSC shall act as though it is not also performing a reset procedure.
Time
BS

Comment

MSC

Reset

Reset

T4

T16
b
T13

T2

BS blocks circuits as necessary

using the blocking procedure.

Reset Acknowledge
d
Reset Acknowledge

11
12

13

Figure 5- 20 - Reset Glare Noted at Both the MSC and the BS

a.

As the BS (re-) initializes, it sends a Reset message to the MSC to notify the MSC of
the reset procedure it is undertaking. The BS starts timer T4. In this example, the
MSC also sends a Reset message due to (re-) initialization and starts timer T16.

b.

When the BS receives the Reset message, it stops timer T4 and starts timer T13.
When the MSC receives the Reset message, it stops timer T16 and starts timer T2.

c.

The BS uses the circuit blocking procedure to block circuits, as necessary, between
itself and the MSC.

d.

Upon expiration of timer T13, the BS returns a Reset Acknowledge message. The
MSC discards the message as an unexpected message. The BS begins normal
operations relative to the MSC.

e.

Upon expiration of timer T2, the MSC returns a Reset Acknowledge message. The
BS discards the message as an unexpected message. The MSC begins normal
operations relative to the BS.

14
15
16
17
18
19
20
21
22
23
24
25
26

NOTE: Steps (d) and (e) could occur in the reverse order.

304

TIA/EIA/IS-2001

5.5.4.4

UNUSED SECTION

5.5.4.5

UNUSED SECTION

5.5.4.6

UNUSED SECTION

5.5.4.7

A7-Reset

3
4

5
6

In the event of a failure or initialization at a BSC that has resulted in the loss of
transaction reference information, an A7-Reset message is sent to other known BSCs to
indicate the reason for the reset.

8
9
10

11

5.5.4.7.1

Successful Operation
Upon initialization, a (first) BSC shall send an A7-Reset message to other known BSCs
and start timer T4.

12
13

Upon receipt of the A7-Reset message from a BSC, the receiving (second) BSC releases
affected virtual calls and erases all affected references. After a guard period of T2
seconds an A7-Reset Acknowledge message is returned to the first BSC indicating that
all references have been cleared.

14
15
16
17

20

If timer T4 is running at the second BSC when the A7-Reset message is received from
the first BSC, the second BSC shall stop timer T4, start timer T2, complete initialization,
and return an A7-Reset Acknowledge message to the first BSC when timer T2 expires.

21

Please refer to section 6.1.12.11, A7-Reset, for the format and content of this message.

18
19

22

5.5.4.7.2

If a BSC sends an A7-Reset message to another BSC and receives no A7-Reset

Acknowledge message within period T4, then it shall repeat the entire reset procedure
with respect to that other BSC. It is not necessary to repeat the reset procedure with
respect to the MSC or to other BSCs.

23
24
25
26

If an A7-Reset message is received that contains a protocol version less than the
protocol version of the receiver but unknown to the receiver, then the receiver may raise
an OA&M flag and choose not to respond to the sender.

27
28
29

30
31

Failure Operation

5.5.4.8

A7-Reset Acknowledge
The A7-Reset Acknowledge message is sent in response to an A7-Reset message.

305

TIA/EIA/IS-2001

5.5.4.8.1

When a (second) BSC has received an A7-Reset message from another (first) BSC, the
second BSC sends an A7-Reset Acknowledge message to the first BSC after a guard
period of T2 seconds to indicate that the A7-Reset message was received and that all
references have been cleared. When the first BSC receives the A7-Reset Acknowledge
message, it stops timer T4 if it is running and begins normal operation.

2
3
4
5
6

Please refer to section 6.1.12.12, A7-Reset Acknowledge, for the format and content
of this message.

7
8

5.5.4.8.2

5.5.4.9

14

A7 Global Reset Examples

This section contains examples of the A7-Reset procedure, including glare situations.

12

13

Failure Operation
None.

10

11

Successful Operation

5.5.4.9.1

Successful Reset at a BSC

This example shows a successful A7-Reset procedure when a BSC (re)-initializes.
Second
BSC

First
BSC
A7-Reset
T2

A7-Reset Acknowledge

Time

Comment

T4

15
16
17

Figure 5- 21 - Successful A7-Reset at a BSC

18

a.

As the first BSC (re-) initializes, it sends an A7-Reset message to another (second)
BSC to notify the second BSC of the reset procedure it is undertaking. The second
BSC starts timer T2. The first BSC starts timer T4.

b.

Upon expiration of timer T2, the second BSC returns an A7-Reset Acknowledge
message. The first BSC stops timer T4. Both BSCs begin normal operations relative
to each other.

19
20
21
22
23

306

TIA/EIA/IS-2001

1
2
3
4
5
6

5.5.4.9.2

A7-Reset Glare Noted at the First BSC

This example shows parallel reset procedures at two BSCs. In this case, the first BSC
notes that a timing condition has occurred since the A7-Reset message from the other
(second) BSC arrives after the A7-Reset message is sent from the first BSC. The first
BSC shall assume that the A7-Reset message it has sent has been lost. As a result, the
first BSC shall act as though it is not also performing an A7-Reset procedure.

First
BSC

Second
BSC

Time

Comment

A7-Reset
a
T4

A7-Reset
b

T2

T4

A7-Reset Acknowledge

7
8

Figure 5- 22 - A7-Reset Glare Noted at the First BSC

a.

As a (first) BSC (re-) initializes, it sends an A7-Reset message to another (second)

BSC to notify the second BSC of the A7-Reset procedure it is undertaking. The first
BSC starts timer T4. In this example, the A7-Reset message is lost or cannot be
successfully processed by the second BSC, which is itself (re)-initializing.

b.

As the second BSC (re-) initializes, it sends an A7-Reset message to the first BSC to
notify the first BSC of the A7-Reset procedure it is undertaking. The first BSC stops
timer T4 and starts timer T2. The second BSC starts timer T4.

c.

Upon expiration of timer T2, the first BSC returns an A7-Reset Acknowledge
message. Timer T4 is stopped by the second BSC. Both the first BSC and second
BSC begin normal operations relative to each other.

10
11
12
13
14
15
16
17
18

307

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11

5.5.4.9.3

A7-Reset Glare Noted at Both BSCs

This example shows parallel A7 reset procedures at two BSCs. In this case, the A7Reset messages pass each other enroute and are both received. The first BSC notes
that a timing condition has occurred since the A7-Reset message from the second BSC
arrives after the A7-Reset message is sent from the first BSC. The first BSC shall
assume that the A7-Reset message it has sent has been lost. As a result, the first BSC
shall act as though it is not also performing a reset procedure. Similarly, the second
BSC notes that a timing condition has occurred since the A7-Reset message from the
first BSC arrives after the A7-Reset message is sent from the second BSC. The second
BSC shall assume that the A7-Reset message it has sent has been lost. As a result, the
second BSC shall act as though it is not also performing a reset procedure.

Second
BSC

First
BSC
A7-Reset

A7-Reset

T4

Time

T4
b
T2

T2

A7-Reset Acknowledge
c
A7-Reset Acknowledge

12
13

Figure 5- 23 - A7-Reset Glare Noted at Both BSCs

308

Comment

TIA/EIA/IS-2001

a.

As the first BSC (re-) initializes, it sends an A7-Reset message to the second BSC to
notify the second BSC of the reset procedure it is undertaking. The first BSC starts
timer T4. In this example, the second BSC also sends an A7-Reset message due to
(re-) initialization and starts timer T4.

b.

When the first BSC receives the A7-Reset message, it stops timer T4 and starts timer
T2. When the second BSC receives the A7-Reset message, it stops timer T4 and
starts timer T2.

c.

Upon expiration of timer T2, the first BSC returns an A7-Reset Acknowledge
message. The second BSC discards the message as an unexpected message. The
first BSC begins normal operations relative to the second BSC.

d.

Upon expiration of timer T2, the second BSC returns an A7-Reset Acknowledge
message. The first BSC discards the message as an unexpected message. The
second BSC begins normal operations relative to the first BSC.

2
3
4
5
6
7
8
9
10
11
12
13
14

NOTE: Steps (c) and (d) could occur in the reverse order.

309

TIA/EIA/IS-2001

5.5.5

Tandem Free Operation

It is generally known that tandeming of vocoders will result in noticeable audio
degradation. Although some vocoders handle tandeming better than others, all suffer
from this effect. Such tandeming would occur in a mobile-to-mobile digital call.

2
3
4

For a mobile to mobile digital call, vocoding currently takes place at both the originating
and terminating SDUs. Encoded audio received at the SDU is decoded and
subsequently routed to the mate SDU via the MSC(s). At the mate SDU, the decoded
voice is encoded again prior to transmission over the air. This tandem vocoding
results in an audio quality degradation and increased throughput delay compared to a
mobile-to-land or land-to-mobile call.

5
6
7
8
9
10

The TFO feature will enhance current operation by bypassing the vocoding process at
the SDU(s) for mobile to mobile calls. If both mobile parties are using the same voice
service option, the encoded voice received from the BTS is not decoded at the SDU.
Instead the encoded voice is converted to the appropriate MSC/BS signaling format
(e.g., rate adapted to a 64K DS0 timeslot, but not decoded) for transmission through the
MSC network. The mate MSC in turn routes the encoded speech to the appropriate
SDU where it is converted back to the appropriate signaling format for routing to the
BTS.

11
12
13
14
15
16
17
18

TFO setup operation relies on inband signaling exchange between the SDUs. The
SDUs use inband signaling to determine when it is appropriate to establish TFO
operation. Refer to the TFO standard (3GPP2 TFO specification) for complete details
regarding the inband signaling protocol.

19
20
21
22

30

The TFO feature also provides the capability of controlling TFO operation via out-ofband signaling. Specifically, the Transcoder Control Request and Transcoder Control
Acknowledge messages could be used over the A1 interface to disable/enable the
inband signaling mechanism at the SDUs. Disabling the inband signaling mechanism,
forces the call to revert to tandem vocoding mode. These same messages can also be
used to re-start/enable the inband signaling protocol at the SDUs. This capability is
beneficial for supplementary feature interaction scenarios (such as, Answer Hold and
Three Party Conferencing).

31

The following sections highlight specific details regarding these two messages.

23
24
25
26
27
28
29

32

5.5.5.1

The BSMAP Transcoder Control Request message is sent from the MSC to the BS to
request a change in the current state of the inband signaling mechanism.

33
34

35

Transcoder Control Request

5.5.5.1.1

Successful Operation

36

The MSC sends the Transcoder Control Request to the BS and starts timer T309.

37

When the BS receives this message with an attempt TFO directive, the inband
signaling mechanism at the SDU is enabled (or reset if already enabled and not in the
TFO Operation state) and the BS responds with a Transcoder Control Acknowledge if
tandem free operation is successful.

38
39
40
41
42
43
44

When the BS receives this message with a tandem mode directive, it disables the
inband signaling mechanism and reverts to tandem vocoding mode. The Transcoder
Control Acknowledge message is returned upon successful transition to tandem
vocoding mode.

310

TIA/EIA/IS-2001

Please refer to section 6.1.6.10, Transcoder Control Request, for the format and
content of this message.

1
2

5.5.5.1.2

Failure Operation
If the request failed or the Transcoder Control Acknowledge message was not received
before timer T309 expired, then the MSC invokes appropriate follow-up processing.
MSC may peg the error counters associated with the TFO feature and the call.

4
5
6

5.5.5.2

Transcoder Control Acknowledge

This BSMAP message is sent from the BS to the MSC to indicate the success or failure
of enabling or disabling tandem free operation.

8
9

10

5.5.5.2.1

Successful Operation
When the MSC receives this message, it cancels timer T309 and examines the message
to determine whether its request was successful.

11
12

Please refer to section 6.1.6.11, Transcoder Control Acknowledge, for the format and
content of this message.

13
14

15

5.5.5.2.2

Failure Operation
When timer T309 expired in the MSC, see 5.5.5.1.2.

16

17

5.5.5.2.3

Scenario Diagram
The diagram in Figure 5-14 shows the Transcoder Control procedure.

18

Time
BS

Comment

MSC

Transcoder Control Request

a
T309

Transcoder Control Acknowledge

b
19
20

Figure 5- 24 - Transcoder Control Procedure

21

a.

The MSC sends a Transcoder Control Request message to enable or disable the
inband signaling mechanism at the BS. If the inband signaling mechanism is already
enabled and the call is not in the TFO Operation state, an enable directive simply
resets the inband signaling state machine logic. Timer T309 is started by the MSC.

b.

Upon receipt of the Transcoder Control Request message, the BS sets the inband
signaling mechanism to the appropriate state and returns a success Transcoder
Control Acknowledge message if TFO operation was successfully
enabled/disabled. A failure acknowledgement is sent if the BS is unable to honor
the Transcoder Control Request. Timer T309 is stopped by the MSC.

22
23
24
25
26
27
28
29

30

5.5.6

UNUSED SECTION

31

311

TIA/EIA/IS-2001

1
2

6.

Messages, Information Elements, and Timer Definitions

6.1

Message Definitions

6.1.1

Generic Message Formats

6.1.1.1

A1 Message Header

5
6
7
8
9

Each message transferred between the BS and MSC is classified either as a DTAP or
a BSMAP message. The BS performs protocol conversion between the DTAP/BSMAP
messages and the specific air interface signaling system in use.

10
11
12

In order to distinguish between the DTAP messages and BSMAP messages, a header
is prefixed on each A1 interface message transferred between the BS and MSC. See
Figure 6-1.

BS side
BSAP
DTAP

A Interface

MSC side
BSAP
DTAP

BSMAP

Transport
Protocol(s)

BSMAP

Transport
Protocol(s)
Physical Layer

13
14

Figure 6-1 - Signaling Protocol Reference Model MSC-BS Interface

15
16
17
18
19

BS
BSAP
BSMAP
DTAP
MSC

Base Station
Base Station Application Part
Base Station Management Application Part
Direct Transfer Application Part
Mobile Switching Center

313

TIA/EIA/IS-2001

1
2

6.1.1.1.1

3
4
5

Transfer of DTAP and BSMAP Messages

See section 5.2.4.7 for information on the transfer of DTAP and BSMAP messages on
the A1 interface.

6.1.1.1.1.1

Distribution Function

6
7
8
9

The distribution of messages between the BSMAP and DTAP functions and the
distribution or multiplexing of DTAP messages to or from the various radio link layer
2 access points are performed in an intermediate layer of protocol between the
transport layer and Layer 3 referred to as the distribution sub-layer.

10
11
12
13
14
15
16

The protocol for this sub-layer simply consists of the management of a one or two
octet Distribution Data Unit as a header, followed by the actual layer 3 BSMAP or
DTAP message. This is shown in Figure 6-2, Structure Of A1 Layer 3 Messages.
The user data field contains a Distribution Data Unit, a Length Indicator, and the
actual layer 3 message. The Distribution Data Unit consists of one or two octets
depending on whether the message is DTAP or BSMAP. The first octet, Message
Discrimination, differentiates the message between these two types.

17

6.1.1.1.1.2

Transfer of DTAP Messages

18
19
20
21
22

For DTAP messages, the Distribution Data Unit consists of two parameters: the
Message Discrimination parameter and the Data Link Connection Identifier (DLCI)
parameter. Please refer to section 6.2.2.1, Message Discrimination and section
6.2.2.2, Data Link Connection Identifier (DLCI) for details on the coding of these
parameters.

23
24

In the Message Discrimination parameter the discrimination bit D is set to the value 1
to indicate DTAP.

25
26

The DLCI parameter is used for MSC to BS and BS to MSC messages to indicate the
type and treatment of the message being transmitted.

27
28

The length indicator (see section 6.2.2.3) is coded in one octet, and is the binary
representation of the number of octets of the subsequent layer 3 message parameter.

29
30
31
32

The coding of the DTAP layer 3 messages is specified in this chapter starting in
section 6.1.1.2, Message Body, Coding, and Ordering of Elements. Those that are
actually DTAP messages are distinguished from those that are BSMAP in section 6.0
in the description of Message Type (section 6.2.2.4).

314

TIA/EIA/IS-2001

6.1.1.1.1.3

Transfer of BSMAP Messages

2
3
4

The transfer of BSMAP messages over a specific transport connection allows the
BSMAP functions in both the MSC and the BS to identify to which particular Mobile
Station association the exchanged message (e.g., assign, handoff request, etc.) applies.

5
6
7

The structure of the user data field is given in Figure 6-2, Structure Of A1 Layer 3
Messages. The user data field contains a Distribution Data Unit, a Length Indicator,
and the actual layer 3 message.

8
9
10

The Distribution Data Unit only consists of the Message Discrimination parameter,
and is coded on one octet. The discrimination bit D is set to the value 0 to indicate
BSMAP.

11
12

The Length Indicator (see section 6.2.2.3) is coded in one octet, and is the binary
representation of the number of octets of the subsequent layer 3 message parameter.

13
14

The coding of the BSMAP layer 3 messages is specified in this chapter starting in
section 6.1.1.3.

15
BSMAP Message Header

DTAP Message Header

Message Discrimination

octet 1

DLCI (Always set to 0)

octet 2

Length Indicator

octet 3

APPLICATION

Message Discrimination

Length Indicator

octet 2

Layer 3
Message
Length

APPLICATION
octets 4 to
k+1

octets 3 to k

MESSAGE

MESSAGE

16
17
18

octet 1

BSAP
Message
Header

Figure 6-2 - Structure of A1 Layer 3 Messages

315

Layer 3
Message

TIA/EIA/IS-2001

6.1.1.2

Message Body, Coding, and Ordering of Elements

2
3
4
5
6
7
8

For each A1 (BSAP), A3, A7, A9, and A11 Interface message there are a number of
information elements that are individually defined in section 6.2. Each information
element in a given message is tagged with a reference in section 6.2, a direction
indication (i.e., some elements within a message are bi-directional and others are not),
and a mandatory/optional type (M/O) indicator. Information elements that are marked
as optional carry an additional indication of being either required (R) or conditional
(C). (See below.) Some information elements are reused in multiple messages.

9
10
11
12

The DIRECTION indication associated with each message element pertains to the use
of that particular message element when used with the particular message (i.e., use of
the message element may be different in other messages). The format of the
DIRECTION indication is as follows:

13

Table 6 - 1 - Element Flow DIRECTION Indication

14

BS -> MSC

Element flows from BS to the MSC

MSC -> BS

Element flows from the MSC to the BS

BS <-> MSC

Element flows both ways to/from the MSC and BS

BTS -> SDU

Element flows from the BTS to the SDU

SDU -> BTS

Element flows from the SDU to the BTS

Source BS -> Target BS

Element flows from the Source BS to the Target

BS

Target BS -> Source BS

Element flows from the Target BS to the Source

BS

PCF -> PDSN

Element flows from the PCF to the PDSN

PDSN -> PCF

Element flows from the PDSN to the PCF

BS -> PCF

Element flows from the BS to the PCF

PCF->BS

Element flows from the PCF to the BS

The inclusion of information elements in each message is specified as follows:

15

M - information elements which are mandatory for the message.

16

O - information elements which are optional for the message.

17

Required in the message whenever the message is sent.

18
19
20
21

Conditionally required. The conditions for inclusion of this

element are defined in the operation(s) where the message is
used (see sections 2 - 5) and in footnotes associated with the
table defining the order of information elements in the message.

22
23

Information elements which are mandatory for a given message shall be present, and
appear in the order shown in the message definitions in this chapter.

24
25
26

Information elements which are optional for a given message are included as needed
for specific conditions. When included, they shall appear in the order shown in the
message definition given in this chapter.

316

TIA/EIA/IS-2001

1
2

An information element can very well be mandatory for some messages and optional
for other messages.

3
4

The bitmap tables in the message subsections of 6.1 are patterned after the format for
the information elements of section 6.2 and use the following conventions:
Element Name{<# instances>:

5
6

= Name of information element.

7
8

Different elements within a message are separated by

double lines.

Fields within elements are separated by single lines.

10
11

Octets are renumbered at the beginning of every

element.

12

[<values>]

= Set of allowed values.

13
14
15
16

} Element Name

The number of instances of an element is 1 by default.

If the Element Name{<# instances }Element
Name notation is used, the <# instances> notation
indicates:

17

= exactly n occurrences of the element

18

n+

= n or more occurrences of the element

19

1..n = 1 to n inclusive occurrences of the element

20

label {<# instances>:

21

<octet 1>

22

<octet m>

23
24

} label

= Number of instances of the bracketed set of fields

where <# instances> notation indicates:

25

= exactly n occurrences of the field

26

n+

= n or more occurrences of the field

27

1..n = 1 to n inclusive occurrences of the field

28

ssss ssss

29

30

ssss ssss

31

6.1.1.3

= Variable length field.

Forward Compatibility Guidelines

32
33
34
35
36

This standard will evolve to accommodate new features and capabilities. To ensure
that equipment implemented to one revision level will inter-operate with equipment
implemented to later revision levels the following guidelines are defined for the
processing of messages and for the development of messages in future revisions of this
standard.

37
38
39

Unexpected signaling information may be received at an entity due to differing levels

of signaling protocol at different entities within a network: an entity using a more
enhanced version of the protocol may send (unless overridden by section 6.1.1.3.3)

317

TIA/EIA/IS-2001

1
2

information to an entity implemented at a lower level of the protocol which is outside

the protocol definition supported at that receiving entity.

3
4
5
6
7

It may happen that an entity receives unrecognized signaling information, i.e.,

messages, element types or element values. This can typically be caused by the
upgrading of the protocol version used by other entities in the network. In these cases
the following message processing guidelines are invoked (unless overridden by section
6.1.1.3.3) to ensure predictable network behavior.

8
9
10
11

If the receiving entity is implemented to version 4.0 of the IOS or greater, then the
sending entity shall send messages that are correctly formatted for the version of the
IOS declared to be implemented by the sending entity, (unless overridden by section
6.1.1.3.3).

12
13
14
15

If the receiving entity is implemented to a CDG IOS version less than 3.1.0, then if
the sending entity is at an equal or greater version than the receiver, the sending entity
shall format messages according to the version of the protocol implemented at the
receiving entity.

16
17
18
19

For example, a CDG IOS version 3.1.0 entity by using the following guidelines
(unless overridden by section 6.1.1.3.3) may be capable of ignoring additional new
elements or fields within elements sent by an entity implemented to an IOS version
higher than 3.1.0.

20

6.1.1.3.1

Message Processing Guidelines

21
22

The following message processing guidelines apply unless overridden by explicit

processing directions in other places within this standard.

23
24
25

In the guidelines in this section, optional includes both optional conditional and
optional required information elements as indicated in the message tables in
sections 6.1.2 through 6.1.12.

26
27
28
29

1.

If a message is received containing a Message Type value which is

not defined for the revision level implemented then the message
shall be discarded and ignored. There shall be no change in state
or in timers due to receipt of an unknown message.

30
31
32
33

2.

If a message is received without an expected mandatory

information element for the revision level implemented then the
message shall be discarded and ignored. There shall be no change
in state or in timers due to receipt of the message.

34
35
36
37
38
39
40
41

3.

If a message is received that contains an information element

which is defined for the revision level implemented but contains
invalid values in some fields, these fields shall be ignored and the
remainder of the information element processed to the extent
possible. The message and all other information elements shall be
processed to the extent possible. Failure handling may be
initiated if call processing cannot continue. See also message
processing guidelines 9 and 10 below.

42
43
44
45
46

4.

If a message is received that contains an Information Element

Identifier which is not defined for the revision level implemented
then that element shall be discarded and ignored. The message
shall be processed to the extent possible. Failure handling may be
initiated if call processing cannot continue.

318

TIA/EIA/IS-2001

1
2
3

5.

If a known but unexpected optional information element is

received, that information element shall be ignored. The message
and all other information elements shall be processed.

4
5
6
7

6.

If a message is received without an expected optional information

element the message shall be processed to the extent possible.
Failure handling may be initiated if call processing cannot
continue.

8
9
10
11
12
13
14
15

7.

No value of an information element that is indicated as reserved

for the revision level implemented shall be sent. If a valid
information element contains a value which is specified as
reserved or is otherwise not defined in the revision level
implemented then this field shall be ignored and the remainder of
the information element processed to the extent possible. The
message and all other information elements shall be processed to
the extent possible.

16
17
18

8.

Octets and bits designated as Reserved or which are undefined

for the revision implemented shall be set to zero by a sending
entity and ignored by a receiving entity.

19
20
21
22
23

9.

If an element is received containing a field that is larger than

expected, i.e., is indicated as having more bits/octets than
expected, then the expected bits/octets of that field shall be
processed to the extent possible and the additional bits/octets shall
be ignored.

24
25
26
27
28
29

10. If an element is received containing a field that is smaller than

expected, i.e., is indicated as having fewer bits/octets than
expected, then the length field or other indicator will be
considered correct and the bits/octets actually present in the
element shall be processed to the extent possible. Failure handling
may be initiated if call processing cannot continue.

30

6.1.1.3.2

Message Definition Guidelines

31

1.

New messages shall have a Message Type that was never previously used.

32
33

2.

Information Element Identifiers may be reused in future revisions only

when:

34
35

The old use of the element identifier is not used in the new
revision, and

36
37

the new use of the element identifier is used only in new messages
which were not defined in previous revisions.

38
39

The old use of the element identifier shall be supported within the
context of the old messages in which it was used.

40
41
42

3.

Defined valid values of Information Elements may be changed in future

revisions. The new version shall define the error handling when previously
valid values are received.

43
44

4.

Octets and bits which are undefined or which are defined as reserved may
be used in future revisions.

45
46

5.

The Mandatory/Optional designation of Information Elements within a

message shall not change.

319

TIA/EIA/IS-2001

1
2

6.

Mandatory Information elements shall be sent in the order specified in

section 6.1.

3
4

7.

New optional Information Elements in a message shall be defined after all

previously defined optional Information Elements.

8.

All new Information Elements shall be defined with a length field.

6
7
8

9.

New information may be added to the end of an existing Information

Element, provided that the Information Element is defined with a length
field.

6.1.1.3.3

IOS Upgrade Guidelines

10

For supporting backward compatibility on the A1 interface:

11
12
13
14
15
16
17
18
19
20

When two nodes communicate on the A1 interface no element shall be sent which is
larger or smaller in length, or have values other than expected as per the protocol
version of the node running on the lower protocol version. If an information element
is sent in a manner that violates the above principle, or if an unexpected or unknown
element is sent in the middle of a message, or if an element that was required to be
sent for successful message processing as per the protocol revision of the node
running at the lower version is not sent, then failure handling may be invoked by the
receiving node. If the receiving node determines that failure handling does not need to
be applied, then processing may continue with the receiving entity generating any
OA&M logs as required.

21
22
23
24
25
26

Any new elements may be sent to the node running the lower protocol version if the
position of those elements is beyond the end of the elements expected by the lower
protocol revision. Elements that were defined at the lower protocol revision but
marked as not required and that become used at the higher protocol revision and
appear before the end of the elements expected by the lower protocol revision shall
not be sent to the node running the lower protocol revision.

27
28

If both the nodes are running the same protocol version then the above rules still
apply.

320

TIA/EIA/IS-2001

6.1.2

Call Processing Message Formats

6.1.2.1

Complete Layer 3 Information

3
4
5

This BSMAP message is sent from the BS to the MSC upon receipt of the first
message from the mobile station. This message contains a CM Service Request
message, a Paging Response message, or a Location Updating Request message.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Cell Identifier

6.2.2.20

BS -> MSC

Ma

Layer 3 Information

6.2.2.38

BS -> MSC

6
7
8
9

a.

10
11
12

This element identifies the cell where the service request was
received from the MS. Discriminator type0000 0010 (Cell ID)
may be used in the complete Layer 3 Information message. For
more information, refer to section 6.2.2.20.

The bitmap below is included for information only. It is already included in the
bitmaps for the CM Service Request, Paging Response and Location Updating Request
messages.
7

(MSB)

Octet

Message Type = [57H]

Cell Identifier: A1 Element Identifier = [05H]

Length = [03H,H]

Cell Identification Discriminator = [02H]

Cell = [001H-FFFH]
(LSB)

Layer 3 Information:

Sector = [0H-FH] (0H = Omni)

A1 Element Identifier = [17H]

Length = <variable>

4
5
1
2

(# of bytes included in the following message)

Contents of Layer 3 Message:

CM Service Request, Paging Response or Location Updating Request

321

TIA/EIA/IS-2001

6.1.2.2

2
3
4

CM Service Request
This DTAP message is sent from the BS to the MSC to request a service for the
connection management sub-layer entities, e.g., circuit switched connection
establishment and activation of supplementary services.

Information Element

Section
Reference

Protocol Discriminator

6.2.2.39

BS -> MSC

Mm

Reserved - Octet

6.2.2.40

BS -> MSC

Message Type

6.2.2.4

BS -> MSC

CM Service Type

6.2.2.51

BS -> MSC

Mm

Classmark Information Type 2

6.2.2.15

BS -> MSC

Ma, m

Mobile Identity (IMSI)

6.2.2.16

BS -> MSC

Mm

Called Party BCD Number

6.2.2.52

BS -> MSC

Ob

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Om

Slot Cycle Index

6.2.2.17

BS -> MSC

Oc

Authentication Response Parameter (AUTHR)

6.2.2.46

BS -> MSC

Od

Authentication Confirmation Parameter (RANDC)

6.2.2.42

BS -> MSC

Oe

Authentication Parameter COUNT

6.2.2.47

BS -> MSC

Authentication Challenge Parameter (RAND)

6.2.2.45

BS -> MSC

Of

Service Option

6.2.2.66

BS -> MSC

Og, m

Voice Privacy Request

6.2.2.13

BS -> MSC

Radio Environment and Resources

6.2.2.82

BS -> MSC

Oh

Called Party ASCII Number

6.2.2.105

BS -> MSC

Oi

Circuit Identity Code

6.2.2.22

BS -> MSC

Oj

Authentication Event

6.2.2.114

BS -> MSC

Ok

Authentication Data

6.2.2.137

BS -> MSC

Ol

PACA Reorigination Indicator

6.2.2.151

BS -> MSC

On

User Zone ID

6.2.2.32

BS -> MSC

IS-2000 Mobile Capabilities

6.2.2.70

BS -> MSC

Oo

CDMA Serving One Way Delay

6.2.2.79

BS->MSC

Op

322

Element
Direction

Type

TIA/EIA/IS-2001

1
2
3

a.

If an MS is capable of multiple band classes, this shall be

indicated in the band class entry field as shown in section
6.2.2.15.

4
5

b.

This element is included when Digit_Mode=0, i.e. BCD digits are

received by the BS from the mobile.

6
7
8
9
10
11
12

c.

This optional element applies only to TIA/EIA-IS-2000 mobiles

operating in slotted mode (discontinuous reception). It contains
an index value used in paging channel slot computation. The Slot
Cycle Index shall be stored by the MSC, and returned to the BS
for call termination to the MS to ensure that the Paging Message
is broadcast in the TIA/EIA-IS-2000 paging channel slots
monitored by the MS.

13
14
15

d.

This optional element contains the authentication response

signature (AUTHR) received from an authentication capable
mobile station when broadcast authentication is active.

16
17

e.

This optional element contains the RANDC received from the

MS.

18
19

RANDC shall be included whenever it is received from the MS

and authentication is enabled.

20
21
22
23
24

f.

Included where broadcast authentication is performed, and

contains the random number (RAND) value used when the BS is
responsible for RAND assignment and can correlate this
parameter with the RAND used by the MS in its authentication
computation.

25
26

g.

If no service option is received from the mobile, the Service

Option element is set to 0001H (8K speech).

27
28
29
30

h.

If the MS has been or is being placed on a radio traffic channel

prior to the Assignment Request message, the BS shall set the
Alloc field to Resources are allocated and the Avail field shall
be set to Resources are available.

31
32
33
34
35
36
37
38

i.

This element contains information on the called party number

coded as an ASCII string. This element is included when
Digit_Mode of value = 1, i.e. ASCII digit is received by the BS
from the mobile. Either this element or the Called Party BCD
Number element shall be present in this message, but not both
simultaneously. If both this element and the Called Party BCD
Number element are missing, or both are present, the MSC may
initiate call failure handling.

39
40

j.

Included when the BS wishes to request a preferred terrestrial

circuit.

41
42
43

k.

Present when an authentication enabled BS does not receive the

authentication parameters (AUTHR, RANDC and COUNT) from
the MS, or when a RAND/RANDC mismatch has occurred

323

TIA/EIA/IS-2001

1
2
3
4
5

l.

This optional information element is required when the service

option is Async Data or Group 3 Fax. It may be optionally
included for other calls. If this element is absent and the Service
Option element indicates an Async Data or Group 3 Fax call, then
the MSC may initiate call failure handling.

6
7

m. If any of these elements are not correctly present, call failure

handling may be initiated by the MSC.

8
9

n.

This element is included if the air interface Origination message

indicated PACA reorigination.

10
11

o.

This element is only included when the mobile station operates at

revision level 6 or greater as defined by TIA/EIA/IS-2000.

12
13

p.

This IE is included if applicable to the geo-location technology

and if this technology is supported at the base station.

324

TIA/EIA/IS-2001

1
2

The following message layout contains the Complete Layer 3 Info message
encapsulating the CM Service Request Message.
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

1
2

Message Type = [57H]

Cell Identifier: A1 Element Identifier = [05H]

Length = [03H]

Cell Identification Discriminator = [02H]

(MSB)

Cell = [001H-FFFH]
(LSB)

Octet

Layer 3 Information:

Sector = [0H-FH] (0H = Omni)

A1 Element Identifier = [17H]

Length = <variable>

4
5
1
2

(# of bytes included in the following message)

Reserved = [0000]

Protocol Discriminator = [0011]

(Call Processing & Supplementary Services)

Reserved - Octet = [00H]

Message Type = [24H]

Service Type = [0001]

CM Service Type:

(Mobile Originating Call)

A1 Element Identifier = [1001]

-- Continued on next page --

325

TIA/EIA/IS-2001

1
-- Continued from previous page -

Classmark Information Type 2: Length = <variable>

Mobile P_REV
= [000 111]

Reserved
= [0]

See List
of
Entries =
[0,1]

RF Power Capability = [000]

(Class 1, vehicle & portable)

Reserved = [00H]

NAR_A
N_CAP

IS-95

Slotted

= [1]

= [0,1]

Reserved = [00]

3
DTX
= [0,1]

Mobile
Term

Reserved

= [0]

= [0,1]

= [0,1]
Reserved = [00H]

Reserved = [000000]

Mobile
Term

PSI

= [0,1]

= [0,1]
SCM Length = [01H 05H]

Station Class Mark = [00H FFH]

Count of Band Class Entries = [01H-20H]

Band Class Entry Length = [03H]

10

Mobile Band Class Capability Entry {1+:

Reserved = [000]

Band Class n = [00000-11111]

Reserved = [000]

Band Class n Air Interfaces Supported =

[00000-11111]

k+1

Band Class n MS Protocol Level = [00H-FFH]

} Mobile Band Class Capability Entry
-- Continued on next page --

326

k+2

TIA/EIA/IS-2001

1
-- Continued from previous page -

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Type of Identity

Odd/even
Indicator

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Called Party BCD Number:

A1 Element Identifier = [5EH]

Length = [00H-11H]
= [1]

Type of Number

Number Plan Identification

= [000-111]

= [0000-1111]

Number Digit/End Mark 2 = [0000-1111]

Number Digit/End Mark 1 = [0000-1111]

Number Digit/End Mark 4 = [0000-1111]

Number Digit/End Mark 3 = [0000-1111]

Number Digit/End Mark m+1 = [0000-1111]

Number Digit/End Mark m = [0000-1111]

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

2
Type of Identity

Odd/even
Indicator

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Slot Cycle Index:

A1 Element Identifier = [35H]

Reserved = [00000]
Authentication Response Parameter (AUTHR):

Slot Cycle Index = [000-111]

A1 Element Identifier = [42H]

Length = [04H]
Reserved = [0000]
[0]

[0]

[0]

Auth Signature Type = [0001] (AUTHR)

[0]

[0]

[0]

(MSB)

5
(LSB)

327

3
4

Auth Signature = <any value>

-- Continued on next page --

TIA/EIA/IS-2001

1
-- Continued from previous page - Authentication Confirmation Parameter (RANDC): A1 Element Identifier = [28H]

RANDC = [00H-FFH]

Authentication Parameter COUNT:

Reserved = [00]

A1 Element Identifier = [40H]

Count = [000000-111111]

Authentication Challenge Parameter (RAND):

A1 Element Identifier = [41H]

Length = [05H]
Reserved = [0000]

1
2

Random Number Type = [0001] (RAND)

(MSB)

3
4

RAND = <any value>

5
6
(LSB)

Service Option: A1 Element Identifier = [03H]

(MSB)

Service Option = <any value>

2
(LSB)

Reserv
ed =
[0]

Include
Priority
= [0,1]

Forward = [00]

A1 Element Identifier = [1DH]

Reverse = [00]

Called Party ASCII Number:

Alloc =
[0,1]

Avail =
[0,1]

A1 Element Identifier = [5BH]

Length = <variable>
ext = [1]

Numbering Plan Identification = [0000-1111]

(as in T1,607 sec 4.5.9)

(as in T1,607 sec 4.5.9)

1
3
4

ASCII character 2

ASCII character n

A1 Element Identifier = [01H]

PCM Multiplexer = <any value>

(LSB)

ASCII character 1

Circuit Identity Code:

(MSB)

Type of Number = [000-111]

3
1

Voice Privacy Request: A1 Element Identifier = [A1H]

Radio Environment and Resources:

Authentication Event:

1
2

Timeslot = [00000-11111]

A1 Element Identifier = [4AH]

Length = [01H]

Event = [01H,02H]

(Parameters not received, RANDC/RAND mismatch)

-- Continued on next page --

328

TIA/EIA/IS-2001

1
-- Continued from previous page -

Authentication Data:

A1 Element Identifier = [59H]

Length = [03H]

(MSB)

3
Auth-Data = <any value>

4
(LSB)

PACA Reorigination Indicator: A1 Element Identifier = [60H]

Length = [01H]

Reserved [0000 000]

User Zone ID:

PRI =
[0,1]

UZID = <any value>

3
(LSB)

IS-2000 Mobile Capabilities:

A1 Element Identifier = [11H]

Length = <variable>
Reserved
= [ 000 ]

OTD
FCH
DCCH
Supported Supported Supported
= [0,1]
= [0,1]
= [0,1]
-- Continued on next page --

329

3
1

A1 Element Identifier = [02H]

Length = [02H]
(MSB)

4
1
2

QPCH
Enhanced
RC CFG Supported
Supported = [0,1]
= [0,1]

TIA/EIA/IS-2001

1
-- Continued from previous page -FCH Information: Bit-Exact Length Octet Count
= [00H to FFH]
Reserved
= [0]

Geo Location Type = [000, 001,

010, 011]

FCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

Geo
Location
Included
= [0,1]

(MSB)

6
FCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

DCCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

k+1

DCCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

k+2

k+3
DCCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

-- Continued on next page --

330

...
Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

1
-- Continued from previous page -

CDMA Serving One Way Delay: A1 Element Identifier = [0CH]

Length = [06H, 09H]

Cell Identification Discriminator = [02H,07H]

IF (Discriminator = 02H), Cell Identification {1:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification
(MSB)

CDMA Serving One Way Delay = [0000H-FFFFH]

k
(LSB)

Reserved = [0000 00]

Resolution = [00, 01,

10]

331

k+1
k+2

TIA/EIA/IS-2001

6.1.2.3

2
3
4

Paging Request
This BSMAP message is sent from MSC to BS and contains sufficient information to
allow the paging to be transmitted by the correct cells, in the correct format at the
correct time.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Mobile Identity (IMSI)

6.2.2.16

MSC -> BS

Ma

Tag

6.2.2.62

MSC -> BS

Cell Identifier List

6.2.2.21

MSC -> BS

Ob

Slot Cycle Index

6.2.2.17

MSC -> BS

Oc

Service Option

6.2.2.66

MSC -> BS

Od

IS-2000 Mobile Capabilities

6.2.2.70

MSC -> BS

Oe

a.

This element shall be set to IMSI.

6
7
8
9
10

b.

Only required for multi-cell BS. More than one cell identifier element
may be included to allow the paging request of several cells within a
BS on receipt of a single paging request message from the MSC.
When absent, paging request at all cells controlled by the BS is
assumed.

11
12
13
14
15

c.

This optional element is included where slotted paging is performed

on the paging channels. It is used by the BS to compute the correct
paging channel slot on each paging channelTIA/EIA-IS-2000 if this
element is absent, then it is assumed that the MS is operating in nonslotted mode.

16
17

d.

The MSC may decide to page the mobile with the preferred service
option selected from the subscribed service option record.

18
19

e.

This element is only included when the MSC has previously been
given this information by a BS.

332

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Paging Request message:
7

BSMAP Header:

Octet
1

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Message Type = [52H]

1
1

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

2
Type of Identity

Odd/even
Indicator

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Tag:

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

Cell Identifier List:

5
1

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [02H,05H]

IF (Discriminator = 02H), Cell Identification {1+:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 05H), Cell Identification {1+:

(MSB)

LAC = [0001H-FFFFH]

j
(LSB)

j+1

} Cell Identification

Slot Cycle Index:

A1 Element Identifier = [35H]

Reserved = [00000]

Slot Cycle Index = [000-111]

-- Continued on next page --

333

1
2

TIA/EIA/IS-2001

1
-- Continued from previous page -

Service Option: A1 Element Identifier = [03H]

(MSB)

Service Option

2
(LSB)

= [8000H (13K speech),

0011H (13K high rate voice service),

0003H (EVRC),
801FH (13K Markov),
0009H (13K Loopback),
0004H (Async Data Rate Set 1),
000CH (Async Data Rate Set 2),
0005H (G3 Fax Rate Set 1),
000DH (G3 Fax Rate Set 2),
0006H (SMS Rate Set 1),
000EH (SMS Rate Set 2)
0021H (Packet Data)
0012H (OTAPA Rate Set 1),
0013H (OTAPA Rate Set 2)]

IS-2000 Mobile Capabilities:

A1 Element Identifier = [11H]

Length = <variable>
Reserved
= [ 000 ]

OTD
FCH
DCCH
Supported Supported Supported
= [0,1]
= [0,1]
= [0,1]
-- Continued on next page --

334

1
2

QPCH
Enhanced
RC CFG Supported
Supported = [0,1]
= [0,1]

TIA/EIA/IS-2001

1
-- Continued from previous page -FCH Information: Bit-Exact Length Octet Count
= [00H to FFH]
Reserved
= [0]

Geo Location Type = <any

value> (ignored)

FCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

Geo
Location
Included
= <any
value>
(ignored)

(MSB)

6
FCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

DCCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

k+1

DCCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

k+2

k+3
DCCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

335

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

6.1.2.4

2
3

Paging Response
This DTAP message is sent from the BS to the MSC when the BS receives a page
response message from an MS

Information Element

Section
Reference

Protocol Discriminator

6.2.2.39

BS -> MSC

Mj

Reserved - Octet

6.2.2.40

BS -> MSC

Message Type

6.2.2.4

BS -> MSC

Classmark Information Type 2

6.2.2.15

BS -> MSC

Ma, j

Mobile Identity (IMSI)

6.2.2.16

BS -> MSC

Mj

Tag

6.2.2.62

BS -> MSC

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Ok

Slot Cycle Index

6.2.2.17

BS -> MSC

Ob

Authentication Response Parameter (AUTHR)

6.2.2.46

BS -> MSC

Oc

Authentication Confirmation Parameter (RANDC)

6.2.2.42

BS -> MSC

Od

Authentication Parameter COUNT

6.2.2.47

BS -> MSC

Authentication Challenge Parameter (RAND)

6.2.2.45

BS -> MSC

Oe

Service Option

6.2.2.66

BS -> MSC

Of, j

Voice Privacy Request

6.2.2.13

BS -> MSC

Circuit Identity Code

6.2.2.22

BS -> MSC

Og

Authentication Event

6.2.2.114

BS -> MSC

Oh

Radio Environment and Resources

6.2.2.82

BS -> MSC

Oi

User Zone ID

6.2.2.32

BS -> MSC

IS-2000 Mobile Capabilities

6.2.2.70

BS -> MSC

Ok

CDMA Serving One Way Delay

6.2.2.79

Ol

336

Element
Direction

BS->MSC

Type

TIA/EIA/IS-2001

1
2

a.

If an MS is capable of supporting multiple band classes, this shall indicated

in the Band Class Entry field as shown in section 6.2.2.15.

3
4
5
6
7
8

b.

This optional element applies only to TIA/EIA-IS-2000 mobiles operating in

slotted mode (discontinuous reception). It contains an index value used in
paging channel slot computation. The Slot Cycle Index shall be stored by the
MSC, and returned to the BS for call termination to the MS to ensure that the
paging message is broadcast in the TIA/EIA-IS-2000 paging channel slots
monitored by the MS.

9
10
11

c.

This optional element contains the authentication response signature

(AUTHR) received from an authentication capable mobile station when
broadcast authentication is active.

12
13

d.

Contains the RANDC received from the MS. RANDC shall be included
whenever it is received from the MS and authentication is enabled.

14
15
16
17

e.

Included where broadcast authentication is performed, and contains the

random number (RAND) value used when the BS is responsible for RAND
assignment and can correlate this parameter with the RAND used by the MS
in its authentication computation.

18
19

f.

If no service option is received from the mobile, the Service Option

element is set to 0001H (8K speech).

20

g.

Included when the BS wishes to request a preferred terrestrial circuit.

21
22
23

h.

Present when an authentication enabled BS does not receive the

authentication parameters (AUTHR, RANDC and COUNT) from the MS, or
when a RAND/RANDC mismatch has occurred.

24
25
26

i.

If the MS has been or is being placed on a radio traffic channel prior to the
Assignment Request message, the BS shall set the Alloc field to Resources
are allocated and the Avail field shall be set to Resources are available.

27
28

j.

If any of these elements are not correctly present, call failure handling may
be initiated by the MSC.

29
30

k.

This element is only included when the mobile station operates at revision
level 6 or greater as defined by TIA/EIA/IS-2000.

31
32

l.

This IE is included if applicable to the geo-location technology and if this

technology is supported at the base station

337

TIA/EIA/IS-2001

1
2

The following message layout contains the Complete Layer 3 Info message
encapsulating the Paging Response Message.
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Message Type = [57H]

Cell Identifier: A1 Element Identifier = [03H]

Length = [03H]

Cell Identification Discriminator = [02H]

(MSB)

Cell = [001H-FFFH]
(LSB)

Octet

Layer 3 Information:

Sector = [0H-FH] (0H = Omni)

5
1

A1 Element Identifier = [17H]

Length = <variable>

(# of bytes included in the following message)

Reserved = [0000]

Protocol Discriminator = [0011]

(Call Processing & Supplementary Services)

Reserved - Octet = [00H]

Message Type = [27H]

Classmark Information Type 2: Length = <variable>

Mobile P_REV
= [000 111]

Reserved
= [0]

RF Power Capability = [000]

See List
of
Entries =
[1]

(Class 1, vehicle & portable)

Reserved = [00H]
NAR_

IS-95

Slotted

AN_

= [1]

= [0,1]

Reserved = [00]

DTX
= [0,1]

Mobile
Term

Reserved

= [0]

= [0,1]

CAP
= [0,1]
Reserved = [00H]
Reserved = [0000 00]

5
Mobile
Term

PSI

= [0,1]

= [0,1]
SCM Length = [01H - 05H]

Station Class Mark = [00H FFH]

Count of Band Class Entries = [01H-20H]

Band Class Entry Length = [03H]

10

-- Continued on next page --

338

TIA/EIA/IS-2001

1
-- Continued from previous page -Mobile Band Class Capability Entry {1+:
Reserved = [000]

Band Class n = [00000-11111]

Reserved = [000]

Band Class n Air Interfaces Supported =

[00000-11111]

k+1

Band Class n MS Protocol Level = [00H-FFH]

k+2

} Mobile Band Class Capability Entry

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/eve
n
Indicator

Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Tag:

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Slot Cycle Index:

A1 Element Identifier = [35H]

Reserved = [00000]

Slot Cycle Index = [000-111]

-- Continued on next page --

339

7
1
2

TIA/EIA/IS-2001

1
-- Continued from previous page -

Authentication Response Parameter (AUTHR):

A1 Element Identifier = [42H]

Length = [04H]
Reserved = [0000]
= [0]

= [0]

= [0]

= [0]

Auth Signature Type = [0001] (AUTHR)

= [0]

= [0]

(MSB)

Auth Signature = <any value>

5
(LSB)

6
1

Authentication Confirmation Parameter (RANDC):

A1 Element Identifier = [28H]
RANDC = [00H-FFH]

Reserved
= [00]

Authentication Parameter COUNT:

A1 Element Identifier = [40H]

Count = [000000-111111]

Include
Priority
= [0,1]

Authentication Challenge Parameter (RAND):

A1 Element Identifier = [41H]

Length = [05H]
Reserved = [0000]

1
2

Random Number Type = [0001] (RAND)

(MSB)

3
4

RAND Value = <any value>

5
6
(LSB)

Service Option: A1 Element Identifier = [03H]

(MSB)

Service Option = <any value>

2
(LSB)

Voice Privacy Request: A1 Element Identifier = [A1H]

Circuit Identity Code:

(MSB)

A1 Element Identifier = [01H]

PCM Multiplexer = <any value>

(LSB)

Authentication Event:

Timeslot = [00000-11111]

A1 Element Identifier = [4AH]

Length = [01H]

Event = [01H,02H]

(Parameters not received, RANDC/RAND mismatch)

-- Continued on next page --

340

TIA/EIA/IS-2001

1
-- Continued from previous page -

Radio Environment and Resources:

Reserved = [00]

Forward = [00]

User Zone ID:

A1 Element Identifier = [1DH]

Reverse = [00]

Alloc =
[0,1]

Avail =
[0,1]

UZID = <any value>

3
(LSB)

IS-2000 Mobile Capabilities:

A1 Element Identifier = [11H]

Length = <variable>
Reserved
= [ 000 ]

OTD
FCH
DCCH
Supported Supported Supported
= [0,1]
= [0,1]
= [0,1]

Geo Location Type = [000, 001,

010, 011]

Geo
Location
Included
= [0,1]

-- Continued on next page --

341

4
1
2

QPCH
Enhanced
RC CFG Supported
Supported = [0,1]
= [0,1]

FCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0]

2
1

A1 Element Identifier = [02H]

Length = [02H]
(MSB)

FCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

4
5

TIA/EIA/IS-2001

1
-- Continued from previous page -(MSB)

6
FCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

DCCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

k+1

DCCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

k+2

k+3
DCCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

-- Continued on next page --

342

...
Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

1
-- Continued from previous page -

CDMA Serving One Way Delay: A1 Element Identifier = [0CH]

Length = [06H, 09H]

Cell Identification Discriminator = [02H,07H]

IF (Discriminator = 02H), Cell Identification {1:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification
(MSB)

CDMA Serving One Way Delay = [0000H-FFFFH]

k
(LSB)

Reserved = [0000 00]

Resolution = [00, 01,

10]

343

k+1
k+2

TIA/EIA/IS-2001

6.1.2.5

UNUSED SECTION

6.1.2.6

UNUSED SECTION

6.1.2.7

UNUSED SECTION

6.1.2.8

UNUSED SECTION

6.1.2.9

UNUSED SECTION

2
3
4
5
6
7
8
9
10

344

TIA/EIA/IS-2001

6.1.2.10

Connect

2
3

This DTAP message is sent by the called BS to the MSC for mobile termination to
indicate that the call has been accepted by the called user.
Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

BS -> MSC

Reserved - Octet

6.2.2.40

BS -> MSC

Message Type

6.2.2.4

BS -> MSC

4
5

The following table shows the bitmap layout for the Connect message:
7

Octet
1

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [03H]

Protocol Discriminator = [0011]

Reserved - Octet = [00H]

Message Type = [07H]

6
6.1.2.11

DTAP Header: Message Discrimination = [01H]

Reserved = [0000]

UNUSED SECTION

345

TIA/EIA/IS-2001

6.1.2.12

2
3
4

Progress
This DTAP message is sent from the MSC to the BS to indicate the progress of a call
in the event of interworking or in connection with the provision of in-band
information/patterns.

Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

MSC -> BS

Reserved - octet

6.2.2.40

MSC -> BS

Message Type

6.2.2.4

MSC -> BS

Signal

6.2.2.50

MSC -> BS

Ob

MS Information Records

6.2.2.72

MSC -> BS

Oa,b

5
6

a.

This optional element carries the MS Information Records. This

element shall carry only signal information.

7
8
9

b.

Either the Signal element or the MS Information Records element

may be present in this message, but both shall not be present
simultaneously.

10
11
12

The Signal element will be retained in this message in this

version of the standards for the purpose of backward compatibility
with CDG IOSv2.x,y.

346

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Progress message:
7

Octet
1

DTAP Header: Message Discrimination = [01H]

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = <variable>

Reserved = [0000]

Reserved - Octet = [00H]

Message Type = [03H]

Signal: A1 Element Identifier = [34H]

Protocol Discriminator = [0011]

Signal value = [63H (abbrev intercept),

65H (abbrev reorder),
02H (intercept),
03H (reorder)]
Reserved = [000000]

Alert Pitch =
[00,01,10]

(med, high, low)

MS Information Records:

A1 Element Identifier = [15H]

Length = [01H-FFH]

Information Record Type = [00H-FFH]

Information Record Length = <variable>

j+1

Information Record Content

j+2

Information Record: {1+:

(MSB)

(LSB)

} Information Record
2
3

6.1.2.13

UNUSED SECTION

6.1.2.14

UNUSED SECTION

4
5
6

347

TIA/EIA/IS-2001

6.1.2.15

2
3
4
5
6

Assignment Request
This BSMAP message is sent from the MSC to the BS in order to request the BS to
assign radio resource, the attributes of which are defined within the message. The
message may include the terrestrial circuit to be used if one is needed for the
call/activity. The message includes the necessary information for providing PACA
service if the call is eligible for such service.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Channel Type

6.2.2.7

MSC -> BS

Ma

Circuit Identity Code

6.2.2.22

MSC -> BS

Ob

Encryption Information

6.2.2.12

MSC -> BS

Oc

Service Option

6.2.2.66

MSC -> BS

Od

Signal

6.2.2.50

MSC -> BS

Oe, g

Calling Party ASCII Number

6.2.2.37

MSC -> BS

Of, g

MS Information Records

6.2.2.72

MSC -> BS

Oh

Priority

6.2.2.18

MSC -> BS

Ok

PACA Timestamp

6.2.2.149

MSC -> BS

Oi

Quality of Service Parameters

6.2.2.54

MSC -> BS

Oj

348

TIA/EIA/IS-2001

1
2

a.

Channel Type is being included for historical reasons and is hard coded as
shown. The BS should examine the Service Option element instead.

3
4
5
6

b.

This element is not included when a terrestrial resource is not required.

When the Service Option element indicates one of the following {Markov,
loopback, packet data, OTAPA, short message}, this element is not included
in the message.

7
8

c.

This optional element is present when encryption is requested and the MSC
has the keys available at the time this message is sent.

9
10

d.

The MSC shall send to the BS the same service option received on the CM
Service Request or Paging Response message.

11
12
13
14
15

e.

Carries instructions for generation of audible tones or alerting patterns. For

mobile terminated calls to anTIA/EIA-IS-2000 mobile, it can be used to
specify a distinctive alerting pattern. This element is not used for mobile
originated calls. This element may be set to Alerting Off if included when
used for setting up an SMS delivery on the traffic channel.

16

f.

This optional element is not used for mobile originating calls.

17
18
19

g.

The Signal and Calling Party ASCII Number elements will be retained in
this message for the purpose of backward compatibility with CDG IOS
V2.x,y.

20
21
22

h.

This optional element carries the MS Information Records. It shall not

redundantly carry information present in other elements such as Signal,
Calling Party ASCII Number.

23
24
25
26

The Signal information record may be set to Alerting Off if included when
used for setting up an SMS delivery on the traffic channel. The Signal and
Calling Party ASCII Number information records are not included for mobile
originated calls.

27

i.

This element is present only when the call is eligible for PACA service.

28
29
30

j.

This element is only used for packet data calls. In this version of this
standard, this element is used to carry a Packet Priority field coded on 4 bits.
Values 1110 and 1111 are reserved.

31
32
33
34

k.

If the Include Priority bit of the Radio Environment and Resources element
was set to 1 in the CM Service Request message to indicate that no lower
priority channels are available (e.g., when a PACA channel reservation
scheme is used) the MSC shall include the actual call priority.

349

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Assignment Request message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [01H]

Channel Type: A1 Element Identifier = [0BH]

Length = [03H]

Speech or Data Indicator =[01H] (speech)

Channel Rate and Type = [08H] (Full Rate)

Speech Encoding Algorithm/data rate + Transparency Indicator = [05H]

(13 kb/s vocoder - speech)

Circuit Identity Code:

(MSB)

A1 Element Identifier = [01H]

PCM Multiplexer = <any value>

(LSB)

Encryption Information:

Timeslot = [00000-11111]

A1 Element Identifier = [0AH]

Length = [08H,0AH,12H]

Encryption Info {1..2:

IF (Encryption Parameter Identifier = 00001) {1:
ext = [1]

Encryption Parameter Identifier = [00001] (SME)

Status

Available

= [0,1]

= [0]

Encryption Parameter Length = [08H]

j
j+1

(MSB)

j+2
j+3
j+4
Encryption Parameter value (SME)

j+5
j+6
j+7
j+8
(LSB)

-- Continued on next page --

350

j+9

TIA/EIA/IS-2001

1
-- Continued from previous page -} OR IF (Encryption Parameter Identifier = 00100) {1:
ext = [1]

Encryption Parameter Identifier = [00100]

Status

Available

(Private Longcode)

= [0,1]

= [0,1]

Encryption Parameter Length = [06H]

Unused = [000000]

j
j+1

(MSB)

j+2
j+3

Encryption Parameter value (Private Long Code)

j+4
j+5
j+6
(LSB)

j+7

} Encryption Info

Service Option: A1 Element Identifier = [03H]

(MSB)

Service Option
= [8000H (13K speech),
0011H (13K high rate voice service),
0001 8K Speech,
0003H (EVRC),
801FH (13K Markov),
0009H (13K Loopback),
0004H (Async Data Rate Set 1),
0005H (G3 Fax Rate Set 1),
000CH (Async Data Rate Set 2),
000DH (G3 Fax Rate Set 2),
0006H (SMS Rate Set 1),
000EH (SMS Rate Set 2)
0021H (Packet Data)
0012H (OTAPA Rate Set 1),
0013H (OTAPA Rate Set 2)]
-- Continued on next page --

351

2
(LSB)

TIA/EIA/IS-2001

1
-- Continued from previous page -

Signal: A1 Element Identifier = [34H]

Signal value = [40H (normal),

41H (inter-group),
42H (special/priority),
44H (ping ring),
4FH (alerting off),
81H (long),
82H (short-short),
83H (short-short-long),
84H (short-short-2),
85H (short-long-short),
86H (short-short-short-short),
87H (PBX long),
88H (PBX short-short),
89H (PBX short-short-long),
8AH (PBX short-long-short),
8BH (PBX short-short-short-short)]
Reserved = [000000]

Alert Pitch =
[00,01,10]

(med, high, low)

Calling Party ASCII Number:

A1 Element Identifier = [4BH]

Length = [01H-FFH]
ext = [0]

1
2

Type of Number

Numbering Plan Identification

= [as in T1.607 Sec 4.5.9

= [as in T1.607 Sec 4.5.9]

except 5 and 7]
ext = [1]

Reserved = [000]

Presentation
Indicator

Screening Indicator

= [as in T1.607 Sec

4.5.9]

= [as in T1.607 Sec

4.5.9]
Printable ASCII Character 1 =[00H-FFH]

Printable ASCII Character 2

Printable ASCII Character m

-- Continued on next page --

352

TIA/EIA/IS-2001

1
-- Continued from previous page -

MS Information Records:

A1 Element Identifier = [15H]

Length = [01H-FFH]

Information Record Type = [00H-FFH]

Information Record Length = <variable>

j+1

Information Record: {1+:

(MSB)

Information Record Content = <any value>

j+2

(LSB)

} Information Record

Priority:

A1 Element Identifier = [06H]

Length = [01H]

Reserved = [00]

Call Priority = [0000 1111]

PACA Timestamp:

Queuing
Allowed
= [0,1]

Preemption
Allowed

= [0,1]
1

A1 Element Identifier = [4EH]

Length = [04H]

(MSB)

3
PACA Queuing Time = <any value>

4
5
(LSB)

Quality of Service Parameters:

A1 Element Identifier = [07H]

Length = [01H]
Reserved = [0000]

1
2

Packet Priority = [0000 1101]

353

TIA/EIA/IS-2001

6.1.2.16

2
3

Assignment Complete
This BSMAP message is sent from the BS to the MSC and indicates that the
requested assignment has been completed.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Channel Number

6.2.2.6

BS -> MSC

Mc

Encryption Information

6.2.2.12

BS -> MSC

Oa

Service Option

6.2.2.66

BS -> MSC

Ob

4
5
6
7
8

a.

Present when either VP or SME parameters were provided by the

MSC in the Privacy Mode Command or Assignment Request
messages. It contains the Algorithm Info which indicates current
settings of Voice Privacy (VP) and Signaling Message Encryption
(SME) and no keys are included in this case.

9
10
11
12

b.

If the service option value included in the Assignment Request

message was 8000H, 0011H, or 0003H (13K speech, 13K
high rate speech, or EVRC), then the only allowable values that
may be sent on this message are those same three service options.

13
14
15

If the service option value included in the Assignment Request

message indicated a fax call, then the only allowable values that
may be sent on this message are fax service options.

16
17
18

If the service option value included in the Assignment Request

message indicated a data call, then the only allowable values that
may be sent on this message are data service options.

19
20
21

If the service option value included in the Assignment Request

message indicated an SMS call, then the only allowable values
that may be sent on this message are SMS service options.

22
23
24
25

If the service option value included in the Assignment Request

message indicated either Markov or loopback procedures, then the
only allowable values that may be sent on this message are values
that indicate Markov or loopback procedures.

26
27

If any of the above rules are violated, the MSC may initiate failure
handling.

28
29

c.

If this element is not correctly present, call failure handling may

be initiated by the MSC.

354

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Assignment Complete message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

(MSB)

Message Type = [02H]

Channel Number: A1 Element Identifier = [23H]

Channel Number = [0000H-FFFFH]

2
(LSB)

Octet

Encryption Information:

3
1

A1 Element Identifier = [0AH]

Length = [02H,04H]

Encryption Info {1..2:

ext = [1]

Encryption Parameter Identifier = [00001, 00100]

Status

Available

(SME, Private Longcode)

= [0,1]

= [0,1]

Encryption Parameter Length = [00H]

j
j+1

} Encryption Info

Service Option: A1 Element Identifier = [03H]

(MSB)

Service Option
= [8000H (13K speech),
0011H (13K high rate voice service),
0003H (EVRC),
801FH (13K Markov),
0009H (13K Loopback),
0004H (Async Data Rate Set 1),
0005H (G3 Fax Rate Set 1),
000CH (Async Data Rate Set 2),
000DH (G3 Fax Rate Set 2),
0006H (SMS Rate Set 1),
000EH (SMS Rate Set 2)
0021H (Packet Data),
0012H (OTAPA Rate Set 1),
0013H (OTAPA Rate Set 2) ]

355

2
(LSB)

TIA/EIA/IS-2001

6.1.2.17

Assignment Failure

2
3

This BSMAP message is sent from the BS to the MSC and indicates that the
requested assignment could not be completed.
Information Element

Section
Reference

Element
Direction

Message Type

6.2.2.4

BS -> MSC

Cause

6.2.2.19

BS -> MSC

Ma

4
5
6
7
8
9
10
11

a.

12

Allowable values: radio interface message failure, radio interface

failure, OAM&P intervention, equipment failure, no radio
resource available, requested terrestrial resource unavailable, BS
not equipped, requested transcoding/rate adaptation unavailable,
terrestrial circuit already allocated, protocol error between BS and
MSC, Mobile Station not equipped (or incapable), PACA call
queued, lower priority radio resources not available, packet call
going dormant.

The following table shows the bitmap layout for the Assignment Failure message:
7

BSMAP Header:

Message Discrimination = [00H]

Octet
1
2

Message Type = [03H]

Cause: A1 Element Identifier = [04H]

ext = [0]

Cause Value =
[00H (radio interface message failure),
01H (radio interface failure),
07H (OAM&P intervention),
10H (packet call going dormant),
20H (equipment failure),
21H (no radio resource available),
22H (requested terrestrial resource unavailable),
25H (BS not equipped),
26H (Mobile Station not equipped (or incapable),
29H (PACA call queued),
30H (requested transcoding/rate adaptation unavailable),
31H (lower priority radio resources not available),
50H (terrestrial circuit already allocated),
60H (protocol error between BS and MSC)]

6.1.2.18

Length Indicator (LI) = [04H]

Length = [01H]

13

Type

UNUSED SECTION

14

356

2
3

TIA/EIA/IS-2001

6.1.2.19

UNUSED SECTION

357

TIA/EIA/IS-2001

6.1.2.20

2
3
4

Clear Request
The BS sends this BSMAP message to the MSC to indicate that the BS wishes to
release the associated dedicated resource. This message is sent via the BSMAP SCCP
connection associated with the dedicated resource.

Information Element

5
6
7
8
9
10
11
12
13
14

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Cause

6.2.2.19

BS -> MSC

Ma

Cause Layer 3

6.2.2.55

BS -> MSC

Ob

a.

15
16
17
18
19
20

Section
Reference

Allowable values: radio interface message failure, OAM&P

intervention, equipment failure, protocol error between BS and MSC,
radio interface failure, call processing, packet call going dormant,
timer expired, MS-to-IWF TCP connection failure, ATH0 (Modem
hang up) Command, +FSH/+FHNG (Fax session ended) Command,
no carrier, PPP protocol failure, PPP session closed by the MS. When
the MS sends a Release Order to the BS to clear the call, the cause
value in this message shall be set to call processing,, and the real
reason for sending the Clear Request message is specified in the Cause
Layer 3 information element.
Since the purpose of this message is to release the call, call release
should proceed even if the Cause element is missing from this
message.

b.

This optional information element contains the reason for sending the
Clear Request message from the BS to the MSC when the MS has sent
a Release Order to the BS to clear the call.

358

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Clear Request message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = [04H,08H]

Octet
1
2

Message Type = [22H]

Cause: A1 Element Identifier = [04H]

Length = [01H]
ext = [0]

2
3

Cause Value =
[00H (radio interface message failure),
01H (radio interface failure),
07H (OAM&P intervention),
09H (call processing),
10H (packet call going dormant),
0DH (timer expired),
20H (equipment failure),
60H (protocol error between BS and MSC),
72H (MS-to-IWF TCP connection failure),
73H (ATH0 (Modem hang up) Command),
74H (+FSH/+FHNG (Fax session ended) Command),
75H (No carrier),
76H (PPP protocol failure),
77H (PPP session closed by the MS) ]

Cause Layer 3: A1 Element Identifier = [08H]

Length = [02H]

ext = [1]
ext = [1]

Coding Standard

Reserved

Location = [0100]

= [00] (Q.931)

= [0]

(Public network serving the remote user)

Cause Value =

[10H (normal clearing),

1FH (normal unspecified)]

359

1
3
4

TIA/EIA/IS-2001

6.1.2.21

2
3
4

Clear Command
This BSMAP message is sent from MSC to BS to instruct the BS to release the
associated dedicated resource. This message is sent via the BSMAP SCCP connection
associated with the dedicated resource.

Information Element

5
6
7
8
9

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Cause

6.2.2.19

MSC -> BS

Ma

Cause Layer 3

6.2.2.55

MSC -> BS

Ob

a.

10
11
12
13
14
15
16
17

Section
Reference

This mandatory element indicates the reason for sending the Clear
Command message to the BS. Allowable values: call processing,
OAM&P intervention, equipment failure, handoff successful, protocol
error between BS and MSC, reversion to old channel, do not notify
MS.
If the Clear Command message is being sent in response to a Clear
Request message that contained a cause value of call processing,
then this element shall be set to call processing.

b.

This element is only used when the MSC initiates call clearing. The
Cause Layer 3 element shall be present only when the Cause element
contains a value of "Call processing." Allowable Cause Layer 3 values
are: Normal clearing, User busy, User alerting no answer, and Normal
unspecified.

360

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Clear Command message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = [04H,08H]

Octet
1
2

Message Type = [20H]

Cause: A1 Element Identifier = [04H]

Length = [01H]
ext = [0]

2
3

Cause Value =
[07H (OAM&P intervention),
09H (call processing),
0AH (reversion to old channel),
0BH (handoff successful),
20H (equipment failure),
60H (protocol error between BS and MSC),
78H (Do not notify MS)]

Cause Layer 3: A1 Element Identifier = [08H]

Length = [02H]

ext = [1]
ext = [1]

Coding Standard

Reserved

Location = [0100]

= [00] (Q.931)

= [0]

(Public network serving the remote user)

Cause Value =

[10H (normal clearing),

11H (user busy),
13H (user alerting - no answer),
1FH (normal unspecified)]

361

1
3
4

TIA/EIA/IS-2001

6.1.2.22

2
3

Clear Complete
The BS sends this BSMAP message to the MSC to inform the MSC that the
associated dedicated resource has been successfully cleared.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Power Down Indicator

6.2.2.60

BS -> MSC

Oa

a.

Used to indicate that the mobile powered down at the end of the call.

The following table shows the bitmap layout for the Clear Complete message:
7

BSMAP Header: Message Discrimination = [00H]

Length Indicator (LI) = [01H,02H]

Octet
1
2

(depending on the presence of the Power Down Indicator)

[1]

[0]

Message Type = [21H]

[1]

[0]

Power Down Indicator:

A1 Element Identifier = [0010]

6
7

6.1.2.23

UNUSED SECTION

362

TIA/EIA/IS-2001

6.1.2.24

Alert With Information

2
3

This DTAP message is sent from the MSC to the BS. It directs the BS to send an
Alert with Information Message on the air interface to the MS.
Information Element

Section
Reference

Protocol Discriminator

6.2.2.39

MSC -> BS

Reserved Octet

6.2.2.40

MSC -> BS

Message Type

6.2.2.4

MSC -> BS

MS Information Records

6.2.2.72

MSC -> BS

a.

Element
Direction

Type

This optional element carries the MS Information Records.

5
6

The following table shows the bitmap layout for the Alert with Information message:
7

Octet
1

DTAP Header: Message Discrimination = [01H]

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = <variable>

Reserved = [0000]

Protocol Discriminator = [0011]

Reserved - Octet = [00H]

Message Type = [26H]

MS Information Records:

A1 Element Identifier = [15H]

Length = <variable>

Information Record Type = [01H-FFH]

Information Record Length = <variable>

j+1

Information Record Content

j+2

Information Record: {1+:

(MSB)

(LSB)

} Information Record
7

363

variable

TIA/EIA/IS-2001

6.1.2.25

UNUSED SECTION

6.1.2.26

UNUSED SECTION

6.1.2.27

UNUSED SECTION

6.1.2.28

BS Service Request

2
3
4
5
6
7
8
9

This BSMAP message is sent from the BS to the MSC to request a BS initiated mobile
terminated call setup.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Mobile Identity (IMSI)

6.2.2.16

BS -> MSC

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Service Option

6.2.2.66

BS -> MSC

Tag

6.2.2.62

BS -> MSC

10

a.

This element is present when the ESN is available at the BS.

11

b.

This element indicates the service option requested by the BS.

12
13
14

c.

If this element is present in the message, the value shall be saved

at the BS to be included in a BS Service Response message if one
is sent in response to this message.

364

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the BS Service Request message:
7

BSMAP Header: Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [09H]

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Service Option: A1 Element Identifier = [03H]

(MSB)

Service Option =

[ 00 21H (Packet Data Service Option, 144 kbps) ]

(LSB)

Tag:

3
1

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

365

TIA/EIA/IS-2001

6.1.2.29

2
3

BS Service Response
This BSMAP message is sent from the MSC to the originating BS to convey the
outcome of processing the BS Service Request message.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Mobile Identity (IMSI)

6.2.2.16

MSC -> BS

Mobile Identity (ESN)

6.2.2.16

MSC -> BS

Tag

6.2.2.62

MSC -> BS

Cause

6.2.2.19

MSC -> BS

4
5

a.

This element is present when the ESN value is available at the

MSC.

6
7
8

b.

This element shall only be included if the MSC does not grant the
BS service request. The allowable cause values are Service
option not available, MS busy, and No response from MS.

9
10
11
12

c.

If a Tag element is included in a BS Service Request message sent

from the BS to the MSC, then the MSC must send a BS Service
Response message to the BS. The Tag value sent by the BS must
be used in the Tag element in this message.

13

366

TIA/EIA/IS-2001

The following table shows the bitmap layout for the BS Service Response message:
7

BSMAP Header: Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [0AH]

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Tag:

7
1

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

Cause: A1 Element Identifier = [04H]

Length = [01H]

ext = [0]

Cause Value =
[ 08H (MS busy),
0CH (No response from MS)
11H (Service option not available) ]

367

5
1
2
3

TIA/EIA/IS-2001

6.1.3

Supplementary Services Message Formats

6.1.3.1

UNUSED SECTION

6.1.3.2

UNUSED SECTION

6.1.3.3

UNUSED SECTION

6.1.3.4

UNUSED SECTION

6.1.3.5

UNUSED SECTION

6.1.3.6

UNUSED SECTION

2
3
4
5
6
7
8
9
10
11
12
13
14

368

TIA/EIA/IS-2001

6.1.3.7

2
3
4

Flash with Information

This DTAP message is sent from the BS to the MSC to indicate that a hook-flash
has been received from the MS. This message may be sent from the MSC to the BS for
features associated with TIA/EIA-95.

Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

BS <-> MSC

Reserved - Octet

6.2.2.40

BS <-> MSC

Message Type

6.2.2.4

BS <-> MSC

Called Party BCD Number

6.2.2.52

BS <-> MSC

Oa

Signal

6.2.2.50

MSC -> BS

Ob

Message Waiting Indication

6.2.2.48

MSC -> BS

Oc, b

Calling Party ASCII Number

6.2.2.37

MSC -> BS

Ob

Tag

6.2.2.62

MSC -> BS

MS Information Records

6.2.2.72

MSC <-> BS

Od

5
6

a.

Contains the digits received by the BS from the mobile station.

These digits may or may not be valid dialed digits.

7
8
9
10
11
12
13

b.

The Signal, Message Waiting Indication and Calling Party ASCII

Number elements will only be retained in this message in this
version of this standard for the purpose of backward compatibility
with CDG IOSv2.x. They will not be supported in future IOS
versions. The Signal, Message Waiting Indication and Calling
Party ASCII Number elements shall only be sent to an IOS v2.x
BS.

14
15

c.

Contains a count of the number of messages waiting at the

Message Center. All values, including zero, are valid.

16
17
18
19

d.

This optional element carries the MS Information Records. It

shall not redundantly carry information present in other elements
such as Signal, Message Waiting Indication, and Calling Party
ASCII Number.

369

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Flash with Information message:
7

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = <variable>

Protocol Discriminator = [0011]

Reserved - Octet = [00H]

Message Type = [10H]

Called Party BCD Number:

A1 Element Identifier = [5EH]

Length = [00H-11H]
= [1]

Octet
1

DTAP Header: Message Discrimination = [01H]

Reserved = [0000]

1
2

Type of Number

Number Plan Identification

= [000-111]

= [0000-1111]

Number Digit/End Mark 2 = [0000-1111]

Number Digit/End Mark 1 = [0000-1111]

Number Digit/End Mark 4 = [0000-1111]

Number Digit/End Mark 3 = [0000-1111]

Number Digit/End Mark m+1 = [0000-1111]

Number Digit/End Mark m = [0000-1111]

Signal: A1 Element Identifier = [34H]

Signal value = [00H-FFH] (see 6.2.2.50)

Reserved = [000000]

2
Alert Pitch =
[00,01,10]

(med, high, low)

Message Waiting Indication:

A1 Element Identifier = [38H]

Number of Messages = [00H-FFH]

Calling Party ASCII Number:

A1 Element Identifier = [4BH]

Length = [01H-FFH]
ext = [0]

1
2

Type of Number

Numbering Plan Identification

= [as in T1.607 Sec 4.5.9

= [as in T1.607 Sec 4.5.9]

except 5 and 7]
ext = [1]

Reserved = [000]

Presentation
Indicator

Screening Indicator

= [as in T1.607 Sec

4.5.9]

= [as in T1.607 Sec

4.5.9]
Printable ASCII Character 1 =[00H-FFH]

Printable ASCII Character 2

Printable ASCII Character m

-- Continued on next page --

370

TIA/EIA/IS-2001

1
-- Continued from previous page -

Tag:

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

MS Information Records:

5
1

A1 Element Identifier = [15H]

Length = [01H-FFH]

Information Record Type = [00H-FFH]

Information Record Length = <variable>

j+1

Information Record: {1+:

(MSB)

Information Record Content = <any value>

j+2

(LSB)

} Information Record

371

TIA/EIA/IS-2001

6.1.3.8

Flash with Information Ack

2
3

This DTAP message is sent from the BS to the MSC to indicate that a layer 2
acknowledgment to a Flash with Information message has been received from the MS.
Information Element

Section
Reference

Protocol Discriminator

6.2.2.39

BS -> MSC

Reserved - Octet

6.2.2.40

BS -> MSC

Message Type

6.2.2.4

BS -> MSC

Tag

6.2.2.62

BS -> MSC

4
5
6
7
8

a.

9
10

Element
Direction

Type

Oa

If a Tag element is included in a Flash with Information message sent from the
MSC to the BS, then the BS must send a Flash with Information Ack message to
the MSC when it receives a Layer 2 acknowledgment from the MS to the Flash
with Information air interface message. The Tag value sent by the MSC must be
used in the Tag element in this message.

The following table shows the bitmap layout for the Flash with Information Ack
message:
7

Octet
1

DTAP Header: Message Discrimination = [01H]

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [08H]

Reserved = [0000]

Tag:

Protocol Discriminator = [0011]

Reserved - Octet = [00H]

Message Type = [50H]

1
1

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

372

TIA/EIA/IS-2001

6.1.3.9

2
3

Feature Notification
This BSMAP message is sent from the MSC to the BS and currently is used for
message waiting indication.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Mobile Identity (IMSI)

6.2.2.16

MSC -> BS

Ma

Tag

6.2.2.62

MSC -> BS

Cell Identifier List

6.2.2.21

MSC -> BS

Ob

Slot Cycle Index

6.2.2.17

MSC -> BS

Oc

Signal

6.2.2.50

MSC -> BS

Od

Message Waiting Indication

6.2.2.48

MSC -> BS

Oe, d

Calling Party ASCII Number

6.2.2.37

MSC -> BS

Od

MS Information Records

6.2.2.72

MSC -> BS

Of

IS-2000 Mobile Capabilities

6.2.2.70

MSC -> BS

Og

4
5

a.

This element will contain an IMSI.

6
7
8

b.

Uniquely identifies cells within a BS, therefore it is a variable

length element dependent on the number of cells that need to be
identified. This element is only useful for multi-cell BSs.

9
10
11
12
13

c.

This optional element is included where slotted paging is

performed on the paging channels. It is used by the BS to
compute the correct paging channel slot on each paging
channelTIA/EIA-IS-2000 in the systems, if this element is absent,
then it is assumed that the MS is operating in non-slotted mode.

14
15
16
17
18
19
20

d.

The Signal, Message Waiting Indication and Calling Party ASCII

Number elements will only be retained in this message in this
version of this standard for the purpose of backward compatibility
with CDG IOS v2.x. They will not be supported in future IOS
versions. The Signal, Message Waiting Indication and Calling
Party ASCII Number elements shall only be sent to an IOS v2.x
BS.

21
22
23

e.

Used by the MSC to send message waiting information. It

specifies the number of messages waiting for the mobile. All
values, including zero, are valid.

24
25
26
27

f.

This optional element carries MS Information Records. It shall

not redundantly carry information present in other elements such
as Signal, Message Waiting Indication, and Calling Party ASCII
Number.

28
29

g.

This element is only included when the MSC has previously been
given this information by a BS.

373

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Feature Notification message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [60H]

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

2
Type of Identity

Odd/even
Indicator

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Tag:

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

Cell Identifier List:

5
1

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [02H,05H]

IF (Discriminator = 02H), Cell Identification {1+:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 05H), Cell Identification {1+:

(MSB)

LAC = [0001H-FFFFH]

j
(LSB)

j+1

} Cell Identification

Slot Cycle Index:

A1 Element Identifier = [35H]

Reserved = [00000]

Slot Cycle Index = [000-111]

Signal value = [00H-FFH] (see 6.2.2.50)

2
Alert Pitch =
[00,01,10]
(med, high, low)

-- Continued on next page --

374

2
1

Signal: A1 Element Identifier = [34H]

Reserved = [000000]

TIA/EIA/IS-2001

1
-- Continued from previous page -

Message Waiting Indication:

A1 Element Identifier = [38H]

Number of Messages = [00H-FFH]

Calling Party ASCII Number:

2
1

A1 Element Identifier = [4BH]

Length = [01H-FFH]
ext = [0]

Type of Number

Numbering Plan Identification

= [000,001,010,011,100]

=
[0000,0001,0011,0100,1000,1001]

ext = [1]

Presentation
Indicator

Reserved = [000]

=
[00,01,10,11]

= [00,01,10]

Screening Indicator

Printable ASCII Character 1 =[00H-FFH]

Printable ASCII Character 2

Printable ASCII Character m

MS Information Records:

A1 Element Identifier = [15H]

Length = [01H-FFH]

Information Record Type = [00H-FFH]

Information Record Length = <variable>

j+1

Information Record: {1+:

(MSB)

Information Record Content = <any value>

j+2

(LSB)

} Information Record

IS-2000 Mobile Capabilities:

A1 Element Identifier = [11H]

Length = <variable>
Reserved
= [ 000 ]

DCCH
Supported
= [0,1]

QPCH
Enhanced
OTD
FCH
Supported Supported RC CFG Supported
Supported = [0,1]
= [0,1]
= [0,1]
= [0,1]

-- Continued on next page --

375

1
2
3

TIA/EIA/IS-2001

1
2
-- Continued from previous page -FCH Information: Bit-Exact Length Octet Count
= [00H to FFH]
Reserved
= [0]

Geo Location Type = <any

value> (ignored)

FCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

Geo
Location
Included
= <any
value>
(ignored)

(MSB)

6
FCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

DCCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

k+1

DCCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

k+2

k+3
DCCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

3
4

376

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

6.1.3.10

Feature Notification Ack

2
3

This BSMAP message is sent from the BS to the MSC in response to Feature
Notification message.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Mobile Identity (IMSI)

6.2.2.16

BS -> MSC

Ma

Tag

6.2.2.62

BS -> MSC

4
5

a.

6
7

This element will contain an IMSI.

The following table shows the bitmap layout for the Feature Notification Ack
message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [61H]

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

2
Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Tag:

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

377

TIA/EIA/IS-2001

6.1.3.11

PACA Command

2
3
4
5

This BSMAP message is sent from the MSC to the BS. This message is used to
indicate that the BS is to apply PACA service to the call. The MSC sends this
message to convey the PACA information (e.g., priority and PACA time stamp) to the
BS.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Priority

6.2.2.18

MSC -> BS

PACA Timestamp

6.2.2.149

MSC -> BS

6
7

The following table shows the bitmap layout for the PACA Command message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = [0AH]

Message Type = [6CH]

Priority:

A1 Element Identifier = [06H]

Length = [01H]

Reserved = [00]

Octet

Call Priority = [0000 1111]

PACA Timestamp:

2
Queuing
Allowed
= [0,1]

Preemption
Allowed

= [0,1]
1

A1 Element Identifier = [4EH]

Length = [04H]

(MSB)

3
PACA Queuing Time = <any value>

4
5
(LSB)

378

TIA/EIA/IS-2001

6.1.3.12

PACA Command Ack

2
3

This BSMAP message is sent from the BS to the MSC to acknowledge that the PACA
Command message was received and appropriate action was taken by the BS.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Cause

6.2.2.19

MSC -> BS

4
5

The following table shows the bitmap layout for the PACA Command Ack message:
7

BSMAP Header:

Message Discrimination = [00H]

Octet
1

Length Indicator (LI) = [01H]

Message Type = [6DH]

Cause: A1 Element Identifier = [04H]

Length = [01H]
ext = [0]

Cause Value =
2DH (PACA queue overflow),

379

2
3

TIA/EIA/IS-2001

6.1.3.13

2
3
4
5
6
7
8
9

PACA Update
This BSMAP message is sent, from either the BS or the MSC, to indicate that the BS
(MSC) intends to modify the queued call. The MSC sends this message to cancel the
call, to remove the previous request (the request associated with the first called
number when the MS makes consecutive PACA calls) or to instruct the old BS (cell)
to remove the request from its PACA queue when an idle handoff has occurred. The
BS sends this message to the MSC to cancel the call. The BS can either send this
message autonomously or send it when it receives a PACA cancellation request from
the MS.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS <-> MSC

Mobile Identity (IMSI)

6.2.2.16

BS <-> MSC

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Oa

PACA Order

6.2.2.150

BS <-> MSC

Priority

6.2.2.18

BS <- MSC

Ob

Authentication Response Parameter (AUTHR)

6.2.2.46

BS -> MSC

Oc

Authentication Confirmation Parameter (RANDC)

6.2.2.42

BS -> MSC

Oc

Authentication Parameter COUNT

6.2.2.47

BS -> MSC

Oc

Authentication Challenge Parameter (RAND)

6.2.2.45

BS -> MSC

Od

Authentication Event

6.2.2.114

BS -> MSC

Oe

10
11
12

a.

This element is included in the message if it is received from the

MS and is not included in the first instance of the Mobile Identity
element.

13
14

b.

This element is included in the message if the MSC wishes to

modify the priority of a queued call.

15
16

c.

This element is included in the message if it is received from the

MS.

17
18
19
20
21

d.

Included where broadcast authentication is performed, and

contains the random number (RAND) value used when the BS is
responsible for RAND assignment and can correlate this
parameter with the RAND used by the MS in its authentication
computation.

22
23
24

e.

Present when an authentication enabled BS does not receive the

authentication parameters (AUTHR, RANDC and COUNT) from
the MS, or when a RAND/RANDC mismatch has occurred

25
26

380

TIA/EIA/IS-2001

The following table shows the bitmap layout for the PACA Update message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [6EH]

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

2
Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/eve
n
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

PACA Order:

A1 Element Identifier = [5FH]

Length = [01H]
Reserved = [0000 0]

Priority:

2
PACA Action Required
= [000 101]

Call Priority = [0000 1111]

-- Continued on next page --

381

3
1

A1 Element Identifier = [06H]

Length = [01H]

Reserved = [00]

2
Queuing
Allowed
= [0,1]

Preemption
Allowed

= [0,1]

TIA/EIA/IS-2001

1
-- Continued from previous page -

Authentication Response Parameter (AUTHR):

A1 Element Identifier = [42H]

Length = [04H]
Reserved = [0000]
= [0]

= [0]

= [0]

= [0]

Auth Signature Type = [0001] (AUTHR)

= [0]

= [0]

(MSB)

Auth Signature = <any value>

5
(LSB)

Authentication Confirmation Parameter (RANDC):

6
1

A1 Element Identifier = [28H]

RANDC = [00H-FFH]

Authentication Parameter COUNT:

Reserved = [00]

A1 Element Identifier = [40H]

Count = [000000-111111]

382

2
1
2

TIA/EIA/IS-2001

1
2
3
4

6.1.3.14

PACA Update Ack

This BSMAP message is sent from the BS(MSC) to the MSC (BS) to acknowledge
that the PACA Update message was received and appropriate action was taken by the
BS (MSC).
Information Element
Section
Element
Type
Reference
Direction
Message Type

6.2.2.4

BS <-> MSC

Mobile Identity (IMSI)

6.2.2.16

BS <-> MSC

Priority

6.2.2.18

BS <- MSC

Oa

Cause

6.2.2.19

BS <-> MSC

Ob

5
6

a.

Indicates the new priority to be applied to the queued call if the

priority is to be changed.

7
8

b.

Allowable cause values are: PACA Cancel Request Rejected,

No Response from the MS, PACA Queue Overflow.

The following table shows the bitmap layout for the PACA Update Ack message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [6FH]

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

2
Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Priority:

A1 Element Identifier = [06H]

Length = [01H]

Reserved = [00]

Call Priority = [0000 1111]

Cause: A1 Element Identifier = [04H]

Length = [01H]

ext = [0]

Cause Value =
[0CH (No response from MS),
2DH (PACA queue overflow),
2EH (PACA cancel request rejected)]

383

2
Queuing
Allowed
= [0,1]

Preemption
Allowed

= [0,1]
1
2
3

TIA/EIA/IS-2001

6.1.4

Mobility Management Message Formats

6.1.4.1

Authentication Request

2
3
4
5
6
7
8

This message is sent from the MSC to the BS and it is used to make an authentication
check on the mobile station. This is a DTAP message when used to perform
authentication on a voice/traffic channel and a BSMAP message otherwise. The
RANDU information element of this message is used by the MS to generate the
AUTHU.
Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

MSC -> BS

Ma

Reserved - Octet

6.2.2.40

MSC -> BS

Ma

Message Type

6.2.2.4

MSC -> BS

Authentication Challenge Parameter (RANDU)

6.2.2.45

MSC -> BS

Mobile Identity (IMSI)

6.2.2.16

MSC -> BS

Ob,c

Tag

6.2.2.62

MSC -> BS

Oc,d

Cell Identifier List

6.2.2.21

MSC -> BS

Oc,e

Slot Cycle Index

6.2.2.17

MSC -> BS

Oc,f

IS-2000 Mobile Capabilities

6.2.2.70

MSC -> BS

Og

9
10

a.

Not used when the Authentication Request message is sent as a

BSMAP message.

11
12
13
14

b.

This element contains the identity of the MS to which the

Authentication Challenge order is to be sent. It shall be included
when the Authentication Challenge is to be sent on the paging
channel(s). This element will contain an IMSI.

15
16

c.

Not used when the Authentication Request message is sent as a

DTAP message.

17
18
19

d.

If this element is present in this message, the value shall be saved

at the BS to be included in an Authentication Response message if
one is sent in response to this message.

20
21
22
23
24
25

e.

This element uniquely identifies cells within a BS from which the

Authentication Challenge is to be sent on paging channels. It is a
variable length element dependent on the number of cells that
need to be identified. This element is only included when the
Authentication Challenge is to be sent on paging channel(s) and is
only required when a subset of the BSs cells shall be identified.

26
27
28
29
30

f.

This optional element is included where slotted paging is

performed on TIA/EIA-IS-2000 paging channels. It is used by the
BS to compute the correct paging channel slot on each paging
channel. In TIA/EIA-IS-2000 systems, if this element is absent,
then it is assumed that the MS is operating in non-slotted mode.

384

TIA/EIA/IS-2001

1
2

g.

3
4

This element is only included when the MSC has previously been
given this information by a BS.

When the Authentication Request message is sent as a BSMAP message, the

following format applies.

5
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [45H]

Authentication Challenge Parameter (RANDU): A1 Element Identifier = [41H]

Length = [04H]
Reserved = [0000]

Random Number Type = [0010] (RANDU)

(MSB)

3
4

RANDU Value = <any value>

5
(LSB)

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

2
Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Tag:

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

Cell Identifier List:

A1 Element Identifier = [1AH]

5
1

Length = <variable>

Cell Identification Discriminator = [02H,05H]

IF (Discriminator = 02H), Cell Identification {1+:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

-- Continued on next page --

385

j
j+1

TIA/EIA/IS-2001

1
-- Continued from previous page -} OR IF (Discriminator = 05H), Cell Identification {1+:
(MSB)

LAC = [0001H-FFFFH]

j
(LSB)

j+1

} Cell Identification

Slot Cycle Index:

A1 Element Identifier = [35H]

Reserved = [00000]

Slot Cycle Index = [000-111]

2
3
4

When the Authentication Request message is sent as a DTAP message, the following
format applies.

5
7

Octet
1

DTAP Header: Message Discrimination = [01H]

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [08H]

Reserved = [0000]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [45H]

Authentication Challenge Parameter (RANDU): Length = [04H]

Reserved = [0000]

Random Number Type = [0010] (RANDU)

(MSB)

2
3

RANDU Value = <any value>

4
(LSB)

IS-2000 Mobile Capabilities:

A1 Element Identifier = [11H]

Length = <variable>
Reserved
= [ 000 ]

DCCH
Supported
= [0,1]

Enhanced
OTD
FCH
Supported Supported RC CFG
= [0,1] Supported
= [0,1]
= [0,1]

-- Continued on next page --

386

5
1
2

QPCH
Supported
= [0,1]

TIA/EIA/IS-2001

1
-- Continued from previous page -FCH Information: Bit-Exact Length Octet Count
= [00H to FFH]
Reserved
= [0000 0]

FCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

6
FCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

DCCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

k+1

DCCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

k+2

k+3
DCCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

387

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

6.1.4.2

2
3
4
5
6

Authentication Response
This message is in response to the Authentication Request message and it is sent from
the BS to the MSC. This is a DTAP message when used to perform authentication on
a voice/traffic channel and a BSMAP message otherwise. The AUTHU is generated by
the MS using an algorithm and the RANDU which was sent through the
Authentication Request message.

Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

BS -> MSC

Ma

Reserved - Octet

6.2.2.40

BS -> MSC

Ma

Message Type

6.2.2.4

BS -> MSC

Authentication Response Parameter (AUTHU)

6.2.2.46

BS -> MSC

Mobile Identity (IMSI)

6.2.2.16

BS -> MSC

Ob,c

Tag

6.2.2.62

BS -> MSC

Oc

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Oc

7
8

a.

Not used when the Authentication Response message is sent as a

BSMAP message.

9
10
11
12

b.

This element contains the identity of the MS that sent the

Authentication Challenge Response. It shall be included when the
Authentication Challenge Response was received on an access
channel. This element will contain an IMSI.

13
14

c.

Not used when the Authentication Response message is sent as a

DTAP message.

15

388

TIA/EIA/IS-2001

1
2

When the Authentication Response message is sent as a BSMAP message, the

following format applies.

3
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

2
1

Message Type = [46H]

Authentication Response Parameter (AUTHU):

A1 Element Identifier = [42H]

Length = [04H]
Reserved = [0000]
[0]

[0]

[0]

[0]

[0]

(MSB)

5
(LSB)

Length = [06H-08H] (10-15 digits)

Odd/even
Indicator

6
1

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Identity Digit 1 = [0H-9H] (BCD)

3
4

Auth Signature = <any value>

1
2

Auth Signature Type = [0010] (AUTHU)

[0]

Octet

2
Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Tag:

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

389

TIA/EIA/IS-2001

1
2

When the Authentication Response message is sent as a DTAP message, the following
format applies.

3
7

Octet
1
2

Length Indicator (LI) = [08H]

Protocol Discriminator = [0101]

Message Type = [46H]

Reserved = [0000]
[0]

Reserved - Octet = [00H]

Authentication Response Parameter (AUTHU):

[0]

Data Link Connection Identifier (DLCI) = [00H]

[0]

DTAP Header: Message Discrimination = [01H]

Reserved = [0000]

Length = [04H]

Auth Signature Type = [0010] (AUTHU)

[0]

[0]

[0]

(MSB)

Auth Signature = <any value>

4
(LSB)

390

TIA/EIA/IS-2001

6.1.4.3

User Zone Update

This BSMAP message is sent by the BS to the MSC to request a User Zone update.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC <-> BS

User Zone ID

6.2.2.32

MSC <-> BS

3
4

The following table shows the bitmap layout for the User Zone Update:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = [05H]

Message Type = [04H]

User Zone ID:

A1 Element Identifier = [02H]

Length = [02H]
(MSB)

Octet

UZID = <any value>

3
(LSB)

391

TIA/EIA/IS-2001

6.1.4.4

SSD Update Request

2
3
4
5
6

This message is sent from the MSC to the BS and is used to initiate the Shared Secret
Data update procedure at the MS. This is a DTAP message when used to perform the
SSD Update on a voice/traffic channel. The Authentication Challenge Parameter
(RANDSSD) information element of this message is used to generate the new SSD at
the MS.
Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

MSC -> BS

Reserved - Octet

6.2.2.40

MSC -> BS

Message Type

6.2.2.4

MSC -> BS

Authentication Challenge Parameter (RANDSSD)

6.2.2.45

MSC -> BS

7
8

The following table shows the bitmap layout for the SSD Update Request message:
7

Octet
1

DTAP Header: Message Discrimination = [01H]

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [0CH]

Reserved = [0000]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [47H]

Authentication Challenge Parameter (RANDSSD):

Reserved = [0000]

Length = [08H]

Random Number Type = [0100]

(RANDSSD)

(MSB)

1
2
3
4
5

RANDSSD Value = <any value>

6
7
8
(LSB)

392

TIA/EIA/IS-2001

6.1.4.5

Base Station Challenge

2
3
4
5
6

This message is in response to the SSD Update Request message and is sent from the
BS to the MSC. This is a DTAP message when used to perform the SSD Update on a
voice/traffic channel. The authentication parameter RANDBS information element of
this message contains the RANDBS and will be used by the HLR/AC as input to the
authentication algorithm to verify the new Shared Secret Data.
Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

BS -> MSC

Reserved - Octet

6.2.2.40

BS -> MSC

Message Type

6.2.2.4

BS -> MSC

Authentication Challenge Parameter (RANDBS)

6.2.2.45

BS -> MSC

7
8

The following table shows the bitmap layout for the Base Station Challenge message:
7

Octet
1

DTAP Header: Message Discrimination = [01H]

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [09H]

Reserved = [0000]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [48H]

Authentication Challenge Parameter (RANDBS): Length = [05H]

Reserved = [0000]

Random Number Type = [1000] (RANDBS)

(MSB)

2
3

RANDBS Value = <any value>

(LSB)

393

TIA/EIA/IS-2001

6.1.4.6

Base Station Challenge Response

2
3
4
5
6

This message is in response to the Base Station Challenge message and is sent from
the MSC to the BS. This is a DTAP message when used to perform the SSD Update
on a voice/traffic channel. The AUTHBS is generated using an authentication
algorithm, the new SSD, and RANDBS, which was sent in the Base Station Challenge
message.
Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

MSC -> BS

Reserved - Octet

6.2.2.40

MSC -> BS

Message Type

6.2.2.4

MSC -> BS

Authentication Response Parameter (AUTHBS)

6.2.2.46

MSC -> BS

7
8
9
10

The following table shows the bitmap layout for the Base Station Challenge Response
message:
7

Octet
1

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [08H]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [49H]

Authentication Response Parameter (AUTHBS): Length = [04H]

Reserved = [0000]
[0]

DTAP Header: Message Discrimination = [01H]

Reserved = [0000]

[0]

[0]

Auth Signature Type = [0011] (AUTHBS)

[0]

[0]

[0]

(MSB)

Auth Signature = <any value>

4
(LSB)

394

TIA/EIA/IS-2001

6.1.4.7

SSD Update Response

2
3
4
5

This message is used to terminate the SSD Update procedure and is sent in response
to the Base Station Challenge Response message. This message is sent from the BS to
the MSC. This is a DTAP message when used to perform the SSD Update on a
voice/traffic channel.
Information Element

Section
Reference

Protocol Discriminator

6.2.2.39

BS -> MSC

Reserved - Octet

6.2.2.40

BS -> MSC

Message Type

6.2.2.4

BS -> MSC

Cause Layer 3

6.2.2.55

BS -> MSC

Oa

6
7
8
9
10
11

a.

Element
Direction

Type

This element indicates the failure of the SSD update operation at

the MS. Absence of this element indicates success of the SSD
update operation at the MS. Allowable cause values are:
Procedure failed, SSD update rejected. If the BS receives an SSD
Update Reject Order from the mobile, the BS shall set the Cause
Layer 3 value to SSD update rejected.

12
13

The following table shows the bitmap layout for the SSD Update Response message:
7

DTAP Header: Message Discrimination = [01H]

Length Indicator (LI) = [03H,07H]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [4AH]

Cause Layer 3: A1 Element Identifier = [08H]

Length = [02H]

ext = [1]

1
2

ext = [1]

Octet

Data Link Connection Identifier (DLCI) = [00H]

Reserved = [0000]

Coding Standard

Reserved

Location = [0100]

= [00] (Q.931)

= [0]

(Public network serving the remote user)

Cause Value =

[0FH (procedure failed),

3BH (SSD Update Rejected)]
14

395

3
4

TIA/EIA/IS-2001

6.1.4.8

2
3
4

Location Updating Request

This DTAP message is sent by the BS to the MSC to request an update to the MSs
location area (registration) when the mobile moved to a new location from its previous
location.

Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

BS -> MSC

Mi

Reserved - Octet

6.2.2.40

BS -> MSC

Message Type

6.2.2.4

BS -> MSC

Mobile Identity (IMSI)

6.2.2.16

BS -> MSC

Ma, i

Location Area Identification

6.2.2.43

BS -> MSC

Classmark Information Type 2

6.2.2.15

BS -> MSC

Ob, i

Registration Type

6.2.2.61

BS -> MSC

Oi

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Oc, i

Slot Cycle Index

6.2.2.17

BS -> MSC

Od

Authentication Response Parameter (AUTHR)

6.2.2.46

BS -> MSC

Oe

Authentication Confirmation Parameter (RANDC)

6.2.2.42

BS -> MSC

Of

Authentication Parameter COUNT

6.2.2.47

BS -> MSC

Authentication Challenge Parameter (RAND)

6.2.2.45

BS -> MSC

Og

Authentication Event

6.2.2.114

BS -> MSC

Oh

User Zone ID

6.2.2.32

BS -> MSC

IS-2000 Mobile Capabilities

6.2.2.70

BS -> MSC

Oj

a.

This element will contain an IMSI.

6
7

b.

If an MS is capable of supporting multiple band classes, this shall be

indicated in the Band Class Entry field as shown in section 6.2.2.15.

8
9

c.

Present in TIA/EIA-IS-2000 systems when the serial number is received

from the MS.

10

d.

The slot cycle index is included when provided by the MS.

11
12
13

e.

This optional element contains the authentication response signature

(AUTHR) received from an authentication capable mobile station when
broadcast authentication is active.

14
15
16

f.

This optional element contains the RANDC received from the MS.
RANDC shall be included whenever it is received from the MS and
authentication is enabled.

396

TIA/EIA/IS-2001

1
2
3
4

g.

Included where broadcast authentication is performed, and contains the

random number (RAND) value used when the BS is responsible for
RAND assignment and can correlate this parameter with the RAND used
by the MS in its authentication computation.

5
6
7

h.

Present when an authentication enabled BS does not receive the

authentication parameters (AUTHR, RANDC and COUNT) from the
MS, or when a RAND/RANDC mismatch has occurred.

8
9

i.

If any of these elements are not correctly present, call failure

handling may be initiated by the MSC.

10
11

j.

This element is only included when the mobile station operates at

revision level 6 or greater as defined by TIA/EIA/IS-2000.

12
13

The following message layout contains the Complete Layer 3 Info message
encapsulating the Location Updating Request Message.
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

1
2

Message Type = [57H]

Cell Identifier: A1 Element Identifier = [05H]

Length = [03H]

Cell Identification Discriminator = [02H]

(MSB)

Cell = [001H-FFFH]
(LSB)

Octet

Layer 3 Information:

Sector = [0H-FH] (0H = Omni)

A1 Element Identifier = [17H]

Length = <variable>

4
5
1
2

(# of bytes included in the following message)

Reserved = [0000]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [08H]

-- Continued on next page --

397

TIA/EIA/IS-2001

1
-- Continued from previous page -

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Type of Identity

Odd/even
Indicator

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Location Area Identification:

A1 Element Identifier = [13H]

MCC Digit 2 = [0H-FH]

MCC Digit 1 = [0H-FH]

MNC Digit 3 = [0H-FH]

MCC Digit 3 = [0H-FH]

MNC Digit 2 = [0H-FH]

MNC Digit 1 = [0H-FH]

(MSB)

LAC = [0001H-FFFFH]

5
(LSB)

Classmark Information Type 2: A1 Element Identifier = [12H]

Length = <variable>

Mobile P_REV
= [000 111]

Reserved
= [0]

See List
of
Entries =
[1]

2
RF Power Capability = [000]

IS-95

Slotted

AN_

= [1]

= [0,1]

Reserved = [00]

(Class 1, vehicle & portable)

Reserved = [00H]
NAR_

4
DTX
= [0]

Mobile
Term

Reserved

= [0]

= [0,1]

CAP
= [0,1]
Reserved = [00H]

Reserved = [0000 00]

Mobile
Term

PSI

= [0,1]

= [0,1]
SCM Length = [01H 05H]

Station Class Mark = [00H FFH]

Count of Band Class Entries = [01H-20H]

10

Band Class Entry Length = [03H]

11

-- Continued on next page --

398

TIA/EIA/IS-2001

1
-- Continued from previous page -Mobile Band Class Capability Entry {1+:
Reserved = [000]

Band Class n = [00000-11111]

Reserved = [000]

Band Class n Air Interfaces Supported =

[00000-11111]

k+1

Band Class n MS Protocol Level = [00H-FFH]

k+2

} Mobile Band Class Capability Entry

Registration Type:

A1 Element Identifier = [1FH]

Location Registration Type =

[00H (timer-based),
01H (power-up),
02H (zone-based),
03H (power-down),
04H (parameter change),
06H (distance-based)]

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

2
Type of Identity

Odd/eve
n
Indicator

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Slot Cycle Index:

A1 Element Identifier = [35H]

Reserved = [00000]
Authentication Response Parameter (AUTHR):

Slot Cycle Index = [000-111]

A1 Element Identifier = [42H]

Length = [04H]
Reserved = [0000]
[0]

[0]

[0]

Auth Signature Type = [0001] (AUTHR)

[0]

[0]

[0]

(MSB)

5
(LSB)

-- Continued on next page --

3
4

Auth Signature = <any value>

399

TIA/EIA/IS-2001

1
-- Continued from previous page -

Authentication Confirmation Parameter (RANDC):

A1 Element Identifier = [28H]
RANDC = [00H-FFH]

Authentication Parameter COUNT:

Reserved = [00]

A1 Element Identifier = [40H]

Count = [000000-111111]

Authentication Challenge Parameter (RAND):

A1 Element Identifier = [41H]

Length = [05H]
Reserved = [0000]

1
2

Random Number Type = [0001] (RAND)

(MSB)

3
4

RAND = <any value>

5
6
(LSB)

Authentication Event:

7
1

A1 Element Identifier = [4AH]

Length = [01H]

Event = [01H (Parameters not received),

02H (RANDC/RAND mismatch)]

User Zone ID:

A1 Element Identifier = [02H]

Length = [02H]
(MSB)

UZID = <any value>

3
(LSB)

-- Continued on next page --

400

TIA/EIA/IS-2001

1
-- Continued from previous page -

IS-2000 Mobile Capabilities:

A1 Element Identifier = [11H]

Length = <variable>

2
QPCH
Enhanced
RC CFG Supported
Supported = [0,1]
= [0,1]

OTD
FCH
DCCH
Supported Supported Supported
= [0,1]
= [0,1]
= [0,1]

Reserved
= [ 000 ]

FCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0]

Geo Location Type = [000, 001,

010, 011]

FCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

Geo
Location
Included
= [0,1]

(MSB)

6
FCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

DCCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

k+1

DCCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

k+2

k+3
DCCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

401

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

6.1.4.9

Location Updating Accept

2
3

This DTAP message is sent from MSC to BS to acknowledge that the MSC received
and accepted the location registration request from the BS.
Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

MSC -> BS

Reserved - Octet

6.2.2.40

MSC -> BS

Message Type

6.2.2.4

MSC -> BS

Location Area Identification

6.2.2.43

MSC -> BS

4
5
6

The following table shows the bitmap layout for the Location Updating Accept
message:
7

Octet
1

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [03H or 09H]

(MSB)

DTAP Header: Message Discrimination = [01H]

Reserved = [0000]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [02H]

A1 Element Identifier = [13H]

MCC Digit 2 = [0H-FH]

MCC Digit 1 = [0H-FH]

MNC Digit 3 = [0H-FH]

MCC Digit 3 = [0H-FH]

MNC Digit 2 = [0H-FH]

MNC Digit 1 = [0H-FH]

Location Area Identification:

LAC = [0001H-FFFFH]

5
(LSB)

402

TIA/EIA/IS-2001

6.1.4.10

Location Updating Reject

2
3

This DTAP message is sent by the MSC to the BS to indicate that updating has failed.
This message is optional.
Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

MSC -> BS

Reserved - Octet

6.2.2.40

MSC -> BS

Message Type

6.2.2.4

MSC -> BS

Reject Cause

6.2.2.44

MSC -> BS

Ma

4
5

a.

Valid reject cause reasons are: Roaming not allowed, Network

failure, Congestion, Illegal MS.

6
7
8

The following table shows the bitmap layout for the Location Updating Reject
message:
7

DTAP Header: Message Discrimination = [01H]

Octet
1

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [04H]

Reserved = [0000]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [04H]

Reject Cause =

[03H (illegal MS),

0BH (roaming not allowed),
51H (network failure),
56H (congestion)]

403

TIA/EIA/IS-2001

1
2
3

6.1.4.11
Parameter Update Request
This DTAP message is sent from the MSC to the BS to increment the call history count in the MS. Upon
sending this message, the MSC starts timer T3220.

4
Information Element

Reference

Direction

TYPE

Protocol Discriminator

6.2.2.39

MSC-> BS

Reserved - Octet

6.2.2.40

MSC-> BS

Message Type

6.2.2.4

MSC-> BS

5
6

The following table shows the bitmap layout for the Parameter Update Request
message:
7

Octet
1

DTAP Header: Message Discrimination = [01H]

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [03H]

Reserved = [0000]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [2CH]

7
8
9
10
11

6.1.4.12
Parameter Update Confirm
This DTAP message is sent from the BS to the MSC in response to a Parameter Update Request message.
This message is sent when the BS receives a positive indication from the MS that it incremented its call
history count.

12
Information Element

Reference

Direction

TYPE

Protocol Discriminator

6.2.2.39

BS-> MSC

Reserved - Octet

6.2.2.40

BS-> MSC

Message Type

6.2.2.4

BS-> MSC

13
14
15

The following table shows the bitmap layout for the Base Parameter Update Confirm
message:
7

DTAP Header: Message Discrimination = [01H]

Octet
1

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [03H]

Reserved = [0000]

Protocol Discriminator = [0101]

Reserved - Octet = [00H]

Message Type = [2BH]

404

TIA/EIA/IS-2001

1
2
3

6.1.4.13

UNUSED SECTION

6.1.4.14

UNUSED SECTION

6.1.4.15

UNUSED SECTION

6.1.4.16

UNUSED SECTION

6.1.4.17

UNUSED SECTION

6.1.4.18

Privacy Mode Command

4
5
6
7
8
9
10
11
12
13
14
15

This BSMAP message is sent from the MSC to the BS to enable or disable signaling
message encryption or Voice Privacy mode.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Encryption Information

6.2.2.12

MSC -> BS

16

405

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the Privacy Mode Command
message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

2
1

Message Type = [53H]

Encryption Information:

Octet

A1 Element Identifier = [0AH]

Length = [08H,0AH,12H]

Encryption Info {1..2:

IF (Encryption Parameter Identifier = 00001), Encryption Info {1:
ext = [1]

Encryption Parameter Identifier = [00001] (SME)

Status

Available

= [0,1]

= [0]

Encryption Parameter Length = [08H]

j
j+1

(MSB)

j+2
j+3
j+4
Encryption Parameter value

j+5
j+6
j+7
j+8
(LSB)

j+9

} OR IF (Encryption Parameter Identifier = 00100), Encryption Info {1:

ext = [1]

Encryption Parameter Identifier = [00100]

Status

Available

(Private Longcode)

= [0,1]

= [0]

Encryption Parameter Length = [06H]

Unused = [000000]

j+1
(MSB)

j+2
j+3

Encryption Parameter value

j+4
j+5
j+6
(LSB)

}
} Encryption Info

406

j+7

TIA/EIA/IS-2001

6.1.4.19

Privacy Mode Complete

2
3
4

This BSMAP message is sent from the BS to the MSC to acknowledge the Privacy
Mode Command, to indicate a change in the Voice Privacy mode setting, or to
indicate that the MS has requested Voice Privacy.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Encryption Information

6.2.2.12

BS -> MSC

Oa

Voice Privacy Request

6.2.2.13

BS -> MSC

Ob

5
6

a.

Used to indicate Voice Privacy mode changes when this message

is sent autonomously by the BS.

7
8

b.

Used to indicate that Voice Privacy was requested by the MS, but
could not be provided by the BS.

9
10
11
12

Note: Encryption Information and voice privacy elements are mutually

exclusive. The Encryption Information element is used to indicate
a change in Encryption Information at the BS. The Voice Privacy
Request element is used by the BS to request the encryption keys.

13
14

The following table shows the bitmap layout for the Privacy Mode Complete message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

2
1

Message Type = [55H]

Encryption Information:

Octet

A1 Element Identifier = [0AH]

Length = [02H,04H]

Encryption Info {1..2:

ext = [1]

Encryption Parameter Identifier = [00001,00100]

Status

Available

(SME, Private Longcode)

= [0,1]

= [0,1]

Encryption Parameter Length = [00H]

j
j+1

} Encryption Info

Voice Privacy Request: A1 Element Identifier = [A1H]

407

TIA/EIA/IS-2001

6.1.5

2
3
4
5
6
7

Handoff Message Formats

Within this section where a Cell Identifier List element is contained in a handoff
message, care shall be taken in selection of the type of Cell Identifier Discriminator
used. Only one discriminator type can be used in a single occurrence of the Cell
Identifier List element, and all cells appearing in the list shall follow that format. For
details see Sections 6.2.2.21, Cell Identifier List and 6.2.2.20, Cell Identifier.

6.1.5.1

UNUSED SECTION

6.1.5.2

UNUSED SECTION

6.1.5.3

UNUSED SECTION

8
9
10
11
12

408

TIA/EIA/IS-2001

6.1.5.4

2
3
4

Handoff Required
This BSMAP message is sent from the BS to the MSC to indicate that for a given MS
which already has a dedicated radio resource assigned, a handoff is required for the
reason given by the cause element.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Cause

6.2.2.19

BS -> MSC

Ma

Cell Identifier List (Target)

6.2.2.21

BS -> MSC

Mb

Classmark Information Type 2

6.2.2.15

BS -> MSC

Oc, i

Response Request

6.2.2.35

BS -> MSC

Encryption Information

6.2.2.12

BS -> MSC

Od

IS-95 Channel Identity

6.2.2.10

BS -> MSC

Oe, j

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Of

Downlink Radio Environment

6.2.2.25

BS -> MSC

Og, j

Service Option

6.2.2.66

BS -> MSC

CDMA Serving One Way Delay

6.2.2.79

BS -> MSC

Oj

IS-95 MS Measured Channel Identity

6.2.2.36

BS -> MSC

Ok

IS-2000 Channel Identity

6.2.2.34

BS -> MSC

Oj,l

Quality of Service Parameters

6.2.2.54

BS -> MSC

Om

IS-2000 Mobile Capabilities

6.2.2.70

BS -> MSC

IS-2000 Service Configuration Record

6.2.2.68

BS -> MSC

PDSN IP Address

6.2.2.30

BS -> MSC

On

Protocol Type

6.2.2.71

BS -> MSC

Oo

409

TIA/EIA/IS-2001

1
2

a.

Allowable cause values are: Interference; Better cell (i.e., Power

budget).

3
4

b.

This element contains the preferred list of target cells in order of

predicted best performance.

5
6

c.

This element indicates the signaling modes and band classes the
mobile is capable of operating in.

7
8
9

d.

Conveys current Voice/Data Privacy and Signaling Message

Encryption modes, as well as the Voice/Data Privacy and
Signaling Message Encryption Keys, if applicable.

10
11
12
13
14
15
16
17
18

e.

Specifies current TIA/EIA-95 channel for CDMA to CDMA

handoff requests only. This element shall contain only a single
instance of octets 4 to 7 when sent by an entity compliant with this
version of the standard. For backward compatibility with older
IOS versions, an entity compliant with this version of the standard
shall be prepared to receive multiple instances of octets 4 to 7, but
may ignore all additional instances, since the ARFCN value is
already contained in the first instance. This element is not present
if the IS-2000 Channel Identity element is present.

19
20
21

f.

This element is required for TIA/EIA-95 and TIA/EIA-IS-2000

handoff and must contain the mobiles ESN, so that the target BS
can calculate the Public Long Code Mask.

22
23

g.

This element provides information for each cell in the Cell

Identifier List element.

24

h.

Not applicable

25
26
27

i.

The fields in octets 4 and 5 shall be coded as shown in the bitmap

below. The MSC shall ignore all fields except IS-95, Slotted, and
Mobile_Term.

28

j.

These elements are not required for a CDMA to AMPS handoff.

29
30
31

k.

This element specifies the target IS-95 Channel for CDMA to

CDMA Hard Handoff based on the MS measurement. It is
required if the value is provided by the MS.

32
33
34

l.

This element specifies the current IS-2000 channel for CDMA to

CDMA hard handoff requests only. This element is not present if
the IS-95 Channel Identity element is present.

35
36
37

m. This element is only used for packet data calls. In this version of
this standard, this element is used to carry a Packet Priority field
coded on 4 bits. Values 1110 and 1111 are reserved.

38
39
40

n.

This element is only used for packet data calls in case of an InterPCF hard handoff. It carries the IP Address of the PDSN
currently connected to the PCF.

41
42
43

o.

This element is only used for packet data calls in case of an InterPCF hard handoff. It identifies the Link Layer protocol used at
the Mobile Node and at the PDSN.

410

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Handoff Required message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [11H]

Cause: A1 Element Identifier = [04H]

ext = [0]

Length = [01H]

Cause Value = [0EH,0FH]

(better cell, interference)

Cell Identifier List (Target):

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [02H,07H]

IF (Discriminator = 02H), Cell Identification {1+:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification

Classmark Information Type 2: A1 Element Identifier = [12H]

Length = <variable>

Mobile P_REV
= [000 111]

Reserved
= [0]

2
RF Power Capability = [000]

See List
of
Entries =
[1]

(Class 1, vehicle & portable)

Reserved = [00H]
NAR_

IS-95

Slotted

AN_

= [1]

= [0,1]

Reserved = [00]

DTX
= [0,1]

Mobile
Term
= [0,1]

CAP
= [0,1]
-- Continued on next page --

411

Reserved
= [0]

TIA/EIA/IS-2001

1
-- Continued from previous page -Reserved = [00H]

Reserved = [0000 00]

Mobile
Term

PSI

= [0,1]

= [0,1]
SCM Length = [01H 05H]

Station Class Mark = [00H FFH]

Count of Band Class Entries = [01H-20H]

Band Class Entry Length = [03H]

11

Mobile Band Class Capability Entry {1+:

Reserved = [000]

Band Class n = [00000-11111]

Reserved = [000]

Band Class n Air Interfaces Supported =

[00000-11111]

k+1

Band Class n MS Protocol Level = [00H-FFH]

k+2

} Mobile Band Class Capability Entry

Response Request:
Encryption Information:

A1 Element Identifier = [1BH]

A1 Element Identifier = [0AH]

Length = <variable>

Encryption Info {0..4:

IF (Encryption Parameter Identifier = 00001, 00101, or 00110) {1:
ext = [1]

Encryption Parameter Identifier =

Status

Available

[00001 (SME),

= [0,1]

= [0,1]

00101 (Datakey (ORYX)),

00110 (Initial RAND)]
Encryption Parameter Length = <variable>

j+1

(MSB)

j+2
Encryption Parameter value = <any value>

(LSB)

-- Continued on next page --

412

TIA/EIA/IS-2001

1
-- Continued from previous page -} OR IF (Encryption Parameter Identifier = 00100) {1:
ext = [1]

Encryption Parameter Identifier = [00100]

Status

Available

(Private Longcode)

= [0,1]

= [0,1]

Encryption Parameter Length = [06H]

m
m+1

Unused = [000000]

(MSB)

m+2
m+3

Encryption Parameter value = <any value>

m+4
m+5
m+6
(LSB)

m+7

}
} Encryption Info

IS-95 Channel Identity: A1 Element Identifier = [22H]

Length = <variable> (see footnote e above)

Hard
Handoff =
[1]

Number of Channels to Add

= [001]

Frame Offset = [0H-FH]

(see footnote e above) {1+:

Walsh Code Channel Index = <any value> (ignored)

Pilot PN Code (low part) = <any value> (ignored)

Reserved = [00]

Power
Pilot PN
Combined
Code
(high part)
= [0]
= [0,1]

Freq.
included

ARFCN (high part)

= [000-111]

= [1]
ARFCN (low part) = [00H-FFH]

}( see footnote e above)

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

-- Continued on next page --

413

TIA/EIA/IS-2001

1
-- Continued from previous page -

Downlink Radio Environment:

A1 Element Identifier = [29H]

Length = <variable>

Number of Cells = <variable>

Cell Identification Discriminator = [02H,07H]

Downlink Radio Environment {1+:

IF (Discriminator = 02H), Cell Identification {1
(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification
Reserved = [00]

Downlink Signal Strength Raw = [000000-111111]

(MSB)

CDMA Target One Way Delay = [0000H-FFFFH] (x100ns)

k+1
(LSB)

k+2

} Downlink Radio Environment

Service Option: A1 Element Identifier = [03H]

(MSB)

Service Option
= [8000H (13K speech),
0011H (13K high rate voice service),
0003H (EVRC),
801FH (13K Markov),
0009H (13K Loopback),
0004H (Async Data Rate Set 1),
0005H (G3 Fax Rate Set 1),
000CH (Async Data Rate Set 2),
000DH (G3 Fax Rate Set 2),
0006H (SMS Rate Set 1),
000EH (SMS Rate Set 2)
0021H (Packet Data),
0012H (OTAPA Rate Set 1),
0013H (OTAPA Rate Set 2) ]
-- Continued on next page --

414

2
(LSB)

TIA/EIA/IS-2001

1
-- Continued from previous page -

CDMA Serving One Way Delay: A1 Element Identifier = [0CH]

Length = [06H, 09H]

Cell Identification Discriminator = [02H,07H]

IF (Discriminator = 02H), Cell Identification {1:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification
(MSB)

CDMA Serving One Way Delay = [0000H-FFFFH]

k
(LSB)

Reserved = [0000 00]

Resolution = [00, 01,

10]

IS-95 MS Measured Channel Identity:

A1 Element Identifier = [64H]

Length = [02H]

k+1
k+2
1
2

Band Class = [00000 11111]

ARFCN (high part)

= [000-111]
ARFCN (low part) = [00H FFH]

IS-2000 Channel Identity:

A1 Element Identifier = [09H]

Length = <variable>
OTD
= [0]
(ignor
ed) ]

Channel Count = [000-111]

4
1
2

Frame Offset = [0H-FH]

Channel Information {1+:

4n

Physical Channel Type =

[ 01H (Fundamental Channel FCH IS-2000),
02H (Dedicated Control Channel DCCH IS-2000)]
Reserved
= [0]

Pilot Gating Rate

= [00, 01, 10]

QOF Mask
= <any value>
Ignored

Walsh Code Channel Index (high

part) = <any value> (ignored)

Walsh Code Channel Index (low part) = <any value> (ignored)

-- Continued on next page --

415

4n+1

4n+2

TIA/EIA/IS-2001

1
-- Continued from previous page -Pilot PN Code (low part) = <any value> (ignored)
Reserved = [000]

Pilot PN
Code
(high part)

ARFCN (high part)

Freq.
included

4n+3
6

= [000-111]

= [1]

= [0,1]
ARFCN (low part) = [00H-FFH]

} Channel Information

Quality of Service Parameters:

A1 Element Identifier = [07H]

Length = [01H]
Reserved = [0000]

2
Packet Priority = [0000 1101]

IS-2000 Mobile Capabilities:

A1 Element Identifier = [11H]

Length = <variable>
Reserved
= [ 000 ]

OTD
FCH
DCCH
Supported Supported Supported
= [0,1]
= [0,1]
= [0,1]

Geo Location Type = <any

value> (ignored)

Geo
Location
Included
= <any
value>
(ignored)

-- Continued on next page --

416

3
1
2

QPCH
Enhanced
RC CFG Supported
Supported = [0,1]
= [0,1]

FCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0]

FCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

4
5

TIA/EIA/IS-2001

1
-- Continued from previous page -(MSB)

6
FCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

DCCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

k+1

DCCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

k+2

k+3
DCCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

IS-2000 Service Configuration Record:

...

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

A1 Element Identifier = [0EH]

Bit-Exact Length Octet Count = <variable>

Reserved
= [ 0000 0 ]

1
2

Bit-Exact Length Fill Bits

= [ 000 111 ]

(MSB)

3
4

IS-2000 Service Configuration Record Content = <any value>

Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

-- Continued on next page --

417

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

1
-- Continued from previous page -

PDSN IP Address:

A1 Element Identifier = [14H]

Length = [04H]

(MSB)

3
PDSN IP Address = <any value>

4
5
(LSB)

Protocol Type: A1 Element Identifier = [18H]

Length = [02H]

(MSB)

Protocol Type = [88 0BH] (PPP)

3
(LSB)

418

TIA/EIA/IS-2001

6.1.5.5

2
3
4

Handoff Request
The BSMAP Handoff Request message is sent from the MSC to the BS to indicate
that a mobile is to be handed over to that BS. This message is only required for interBS handoffs.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Channel Type

6.2.2.7

MSC -> BS

Encryption Information

6.2.2.12

MSC -> BS

Ma

Classmark Information Type 2

6.2.2.15

MSC -> BS

Mb

Cell Identifier List (Target)

6.2.2.21

MSC -> BS

Mc

Circuit Identity Code Extension

6.2.2.23

MSC -> BS

Cd

IS-95 Channel Identity

6.2.2.10

MSC -> BS

Oe

Mobile Identity (IMSI)

6.2.2.16

MSC -> BS

Of

Mobile Identity (ESN)

6.2.2.16

MSC -> BS

Of

Downlink Radio Environment

6.2.2.25

MSC -> BS

Service Option

6.2.2.66

MSC -> BS

CDMA Serving One Way Delay

6.2.2.79

MSC -> BS

IS-95 MS Measured Channel Identity

6.2.2.36

MSC -> BS

IS-2000 Channel Identity

6.2.2.34

MSC -> BS

Quality of Service Parameters

6.2.2.54

MSC -> BS

IS-2000 Mobile Capabilities

6.2.2.70

IS-2000 Service Configuration Record

MSC -> BS

6.2.2.68

MSC -> BS

PDSN IP Address

6.2.2.30

MSC -> BS

Ol

Protocol Type

6.2.2.71

MSC -> BS

Om

419

O
O

TIA/EIA/IS-2001

1
2
3

a.

4
5
6

Conveys current Voice/Data Privacy Signaling Message

Encryption mode, as well as the Voice/Data Privacy and/or
Signaling Message Encryption Keys, if applicable.
Whatever encryption information is received from the source BS
on the Handoff Required message is sent to the target BS on the
Handoff Request message.

7
8

b.

This element provides the signaling types and band classes that
the mobile is permitted to use. More than one is permitted.

9
10
11

c.

If more than one cell is specified, then they shall be in order of

selection preference. Only discriminator types 0000 0010 and
0000 0111 are used.

12
13

d.

This element contains the full-rate circuit identifier allocated by

the MSC.

14
15
16

In the case of hard handoff for an async data/fax call, this element
indicates the Circuit Identity Code of the circuit to be connected to
the target BS to support the A5 connection to the IWF.

17
18
19

In the case of hard handoff for a voice call, this element indicates
the Circuit Identity Code of the circuit to be connected to the
Target BS to support the A2 connection.

20
21
22

In the case of hard handoff for a packet data call, SMS delivery on
a traffic channel (SMS service option in use), or OTAPA delivery
on a traffic channel, this element shall not be included.

23
24
25
26
27
28
29
30
31

e.

Specifies current TIA/EIA-95 channel for CDMA to CDMA

handoff requests only. This element shall contain only a single
instance of octets 4 to 7 when sent by an IOS v3.1.0 compliant
entity. For backward compatibility with older IOS versions, an
IOS v3.1.0 compliant entity shall be prepared to receive multiple
instances of octets 4 to 7, but may ignore all additional instances,
since the ARFCN value is already contained in the first instance.
This element is not present if the IS-2000 Channel Identity
element is present.

32
33
34
35

f.

This element is required for CDMA to CDMA handoffs. The first

instance shall contain the IMSI, and the second shall contain the
mobile's ESN, so that the target BS can calculate the Public Long
Code Mask.

36
37

g.

This element provides information for each cell in the Cell

Identifier List (target) element.

38
39
40

h.

If the IS-95 MS Measured Channel Identity element was included

in the Handoff Required message, this element is required in this
message.

41
42
43

i.

This element specifies the current IS-2000 channel for CDMA to

CDMA hard handoff requests only. This element is not present if
the IS-95 Channel Identity element is present.

420

TIA/EIA/IS-2001

1
2
3

j.

This element is only used for packet data calls. In this version of
this standard, this element is used to carry a Packet Priority field
coded on 4 bits. Values 1110 and 1111 are reserved.

k.

Not applicable.

5
6
7

l.

This element is only used for packet data calls in case of an InterPCF hard handoff. It carries the IP Address of the PDSN
currently connected to the PCF.

8
9
10

m. This element is only used for packet data calls in case of an InterPCF hard handoff. It identifies the Link Layer protocol used at
the Mobile Node and at the PDSN.

421

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Handoff Request message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [10H]

Channel Type: A1 Element Identifier = [0BH]

Length = [03H]

Speech or Data Indicator =[01H] (speech)

Channel Rate and Type = [08H] (Full Rate)

Speech Encoding Algorithm/data rate + Transparency Indicator =

[05H (13 kb/s vocoder - speech),

40H (non-transparent mode data) ]

Encryption Information:

A1 Element Identifier = [0AH]

Length = <variable>

Encryption Info {0..4:

IF (Encryption Parameter Identifier = 00001, 00101, or 00110) {1:
ext = [1]

Encryption Parameter Identifier =

Status

Available

[00001] (SME),

= [0,1]

= [0]

00101 (Datakey (ORYX)),

00110 (Initial RAND)]
Encryption Parameter Length = <variable>

j+1

(MSB)

j+2
Encryption Parameter value = <any value>

(LSB)

-- Continued on next page --

422

TIA/EIA/IS-2001

1
-- Continued from previous page -} OR IF (Encryption Parameter Identifier = 00100) {1:
ext = [1]

Encryption Parameter Identifier = [00100]

Status

(Private Longcode)

= [0,1]

Availabl
e

= [0]
Encryption Parameter Length = [06H]
Unused = [000000]

m+1
(MSB)

m+2
m+3

Encryption Parameter value = <any value>

m+4
m+5
m+6
(LSB)

m+7

}
} Encryption Info

Classmark Information Type 2: A1 Element Identifier = [12H]

Length = <variable>

Mobile P_REV
=[000 111]

Reserved
= [0]

2
RF Power Capability = [000]

See List
of
Entries =
[1]

(Class 1, vehicle & portable)

Reserved = [00H]
NAR_

IS-95

Slotted

AN_

= [1]

= [0,1]

Reserved = [00]

DTX
= [0,1]

Mobile
Term

Reserved

= [0]

= [1]

CAP
= [0,1]
Reserved = [00H]
Reserved = [0000 00]

6
Mobile
Term

PSI

= [0,1]

= [0,1]
SCM Length = [01H 05H]

Station Class Mark = [00H FFH]

Count of Band Class Entries = [01H-20H]

10

Band Class Entry Length = [03H]

11

-- Continued on next page --

423

TIA/EIA/IS-2001

1
-- Continued from previous page -Mobile Band Class Capability Entry {1+:
Reserved = [000]

Band Class n = [00000-11111]

Reserved = [000]

Band Class n Air Interfaces Supported =

[00000-11111]

k+1

Band Class n MS Protocol Level = [00H-FFH]

k+2

} Mobile Band Class Capability Entry

Cell Identifier List (Target):

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [ 03H, 06H]

IF (Discriminator = 02H), Cell Identification {1+:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+2
j+3
j+4

} Cell Identification

Circuit Identity Code Extension: A1 Element Identifier = [24H]

Length = [03H]

(MSB)

PCM Multiplexer = <any value>

(LSB)

Timeslot = [00000-11111]

Reserved = [0H]

Circuit Mode = [0H] (Full-rate)

IS-95 Channel Identity: A1 Element Identifier = [22H]

Length = <variable> (see footnote e above)

Hard
Handoff =
[1]

Number of Channels to Add

= [001]

Frame Offset = [0H-FH]

-- Continued on next page --

424

1
3
4
5
1
2
3

TIA/EIA/IS-2001

1
-- Continued from previous page -(see footnote e above) {1+:
Walsh Code Channel Index = <any value> (ignored)

4n

Pilot PN Code (low part) = <any value> (ignored)

4n+1

Reserved = [00]

4n+2

Power
Pilot PN
Combined
Code
(high part)
= [0]
(ignored)

Freq.
included

ARFCN (high part)

= [000-111]

= [1]
ARFCN (low part) = [00H-FFH]

}( see footnote e above)

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

2
Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Downlink Radio Environment:

A1 Element Identifier = [29H]

7
1

Length = <variable>

Number of Cells = <variable>

Cell Identification Discriminator = [ 03H, 06H]

Downlink Radio Environment {1+:

IF (Discriminator = 02H), Cell Identification {1:
(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

-- Continued on next page --

425

j
j+1

TIA/EIA/IS-2001

1
-- Continued from previous page -} OR IF (Discriminator = 07H), Cell Identification {1:
(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification
Reserved = [00]

Downlink Signal Strength Raw = [000000-111111]

(MSB)

CDMA Target One Way Delay = [0000H-FFFFH] (x100ns)

k+1
(LSB)

k+2

} Downlink Radio Environment

Service Option: A1 Element Identifier = [03H]

(MSB)

Service Option

2
(LSB)

= [8000H (13K speech),

0011H (13K high rate voice service),

0003H (EVRC),
0004H (Async Data Rate Set 1),
0005H (G3 Fax Rate Set 1),
000CH (Async Data Rate Set 2),
000DH (G3 Fax Rate Set 2),
0006H (SMS Rate Set 1),
000EH (SMS Rate Set 2)
0021H (Packet Data),
0012H (OTAPA Rate Set 1),
0013H (OTAPA Rate Set 2) ]

CDMA Serving One Way Delay: A1 Element Identifier = [0CH]

Length = [06H,09H]

Cell Identification Discriminator = [02H,07H]

IF (Discriminator = 02H), Cell Identification {1:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

-- Continued on next page --

426

j
j+1

TIA/EIA/IS-2001

1
-- Continued from previous page -} OR IF (Discriminator = 07H), Cell Identification {1:
(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification
(MSB)

CDMA Serving One Way Delay = [0000H-FFFFH]

k
(LSB)

Reserved = [0000 00]

Resolution = [00, 01,

10]

IS-95 MS Measured Channel Identity:

A1 Element Identifier = [64H]

Length = [02H]

k+1
k+2
1
2

Band Class = [00000 11111]

ARFCN (high part)

= [000-111]
ARFCN (low part) = [00H FFH]

IS-2000 Channel Identity:

A1 Element Identifier = [09H]

Length = <variable>
OTD
= [0]
(ignor
ed)

Channel Count = [000-111]

1
2

Frame Offset = [0H-FH]

Channel Information {1+:

4n

Physical Channel Type =

[ 01H (Fundamental Channel FCH IS-2000),
02H (Dedicated Control Channel DCCH IS-2000)]]
Reserved
= [0]

Pilot PN
Code
(high part)

Pilot Gating Rate

= [00, 01, 10]

QOF Mask
= <any value>
Ignored

Walsh Code Channel Index (high

part) = <any value>ignored)

4n+1

Walsh Code Channel Index (low part) = <any value> (ignored)

4n+2

Pilot PN Code (low part) = <any value> (ignored)

4n+3

Reserved = [000]

Freq.
included

ARFCN (high part)

= [000-111]

= [1]

= [0,1]
ARFCN (low part) = [00H-FFH]
} Channel Information
-- Continued on next page --

427

TIA/EIA/IS-2001

1
-- Continued from previous page -

Quality of Service Parameters:

A1 Element Identifier = [07H]

Length = [01H]
Reserved = [0000]

2
Packet Priority = [0000 1101]

IS-2000 Mobile Capabilities:

A1 Element Identifier = [11H]

Length = <variable>

2
QPCH
Enhanced
RC CFG Supported
Supported = [0,1]
= [0,1]

OTD
FCH
DCCH
Supported Supported Supported
= [0,1]
= [0,1]
= [0,1]

Reserved
= [ 000 ]

FCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0]

Geo Location Type = <any

value> (ignored)

FCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

Geo
Location
Included
= <any
value>
(ignored)

(MSB)

6
FCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

-- Continued on next page --

428

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

1
-- Continued from previous page -DCCH Information: Bit-Exact Length Octet Count
= [00H to FFH]
Reserved
= [0000 0]

k+1

DCCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

k+3
DCCH Information Content
= <any value>
Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

k+2

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

IS-2000 Service Configuration Record:

...

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

A1 Element Identifier = [0EH]

Bit-Exact Length Octet Count = <variable>

Reserved
= [ 0000 0 ]

1
2

Bit-Exact Length Fill Bits

= [ 000 111 ]

(MSB)

3
4

IS-2000 Service Configuration Record Content = <any value>

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

PDSN IP Address:

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

A1 Element Identifier = [14H]

Length = [04H]

(MSB)

3
PDSN IP Address = <any value>

4
5
(LSB)

Protocol Type: A1 Element Identifier = [18H]

Length = [02H]

(MSB)

Protocol Type = [88 0BH] (PPP)

3
(LSB)

429

TIA/EIA/IS-2001

6.1.5.6

2
3
4
5

Handoff Request Acknowledge

This BSMAP message is sent from the BS to the MSC to indicate that a target
channel has been allocated for handoff as requested. This is in response to the
Handoff Request message. This message is only used for CDMA-CDMA hard
handoff.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

IS-95 Channel Identity

6.2.2.10

BS -> MSC

Oa

Cell Identifier List

6.2.2.21

BS -> MSC

Extended Handoff Direction Parameters

6.2.2.73

BS -> MSC

Hard Handoff Parameters

6.2.2.63

BS -> MSC

IS-2000 Channel Identity

6.2.2.34

BS -> MSC

Oc

IS-2000 Service Configuration Record

6.2.2.68

BS -> MSC

Od

IS-2000 Non-Negotiable Service Configuration

Record

6.2.2.69

BS -> MSC

Oe

6
7
8
9

a.

Included if the air interface channel allocated by the target is

TIA/EIA-95. It lists TIA/EIA-95 channels that have been allocated
by the target BS. This element is not present if the IS-2000
Channel Identity element is present.

10

b.

Not Used

11
12
13
14

c.

Included if the air interface channel allocated by the target is

TIA/EIA-IS-2000. It lists TIA/EIA-IS-2000 channels that have
been allocated by the target BS. This element is not present if
the IS-95 Channel Identity element is present.

15
16
17

d.

This element is included if the target BS wishes to indicate a

desired configuration different from that currently being used at
the source BS.

18
19
20
21
22
23
24
25
26
27

e.

This element contains the TIA/EIA/IS-2000 non-negotiable service

configuration record to support the transport of information
related to IS-2000 logical to physical mapping (LPM) tables, and
if needed, FPC power control information. It is included if the
target BS wishes to provide the source BS with non-negotiable
service configuration parameter values that may be sent to the
mobile station. It is up to the source BS to decide whether or not
to include the received non-negotiable service configuration
record in the Universal Handoff Direction Message / General
Handoff Direction Message sent to the mobile station.

430

TIA/EIA/IS-2001

1
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Message Type = [12H]

IS-95 Channel Identity: A1 Element Identifier = [22H]

Length = <variable>
Hard
Handoff =
[1]

Octet

Number of Channels to Add

= [001]

2
Frame Offset = [0H-FH]

{1:
Walsh Code Channel Index = [00H-3FH]

Pilot PN Code (low part) = [00H-FFH]

Freq.
included

Power
Pilot PN
Combined
Code
(high part)
= [0]
= [0,1]

Reserved = [00]

ARFCN (high part)

= [000-111]

= [1]
ARFCN (low part) = [00H-FFH]

Cell Identifier List:

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [02H,07H]

IF (Discriminator = 02H) {1:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

} Cell Identification
-- Continued on next page --

431

j+2
j+3
j+4

TIA/EIA/IS-2001

1
-- Continued from previous page -

Extended Handoff Direction Parameters:

A1 Element Identifier = [10H]

Length = [09H]

1
2

Search Window A Size (Srch_Win_A) =

[0H-FH]

Search Window N Size (Srch_Win_N) =

[0H-FH]

Search Window R Size (Srch_Win_R) =

[0H-FH]

Add Pilot Threshold (T_Add) high order

= [0H-FH]

T_Add (low order)

Drop Pilot Threshold (T_Drop) = [000000-111111]

= [00-11]
Compare Threshold (T_Comp)

Drop Timer Value (T_TDrop)

= [0H-FH]

= [0H-FH]

Neighbor Max Age (Nghbor_Max_AGE)

Reserved = [0000]

6
7

= [0H-FH]
Reserved = [00]

SOFT_SLOPE = [00 0000 - 11 1111]

Reserved = [00]

ADD_INTERCEPT = [00 0000 - 11 1111]

Reserved = [00]

DROP_INTERCEPT = [00 0000 - 11 1111]

10

Target BS P_REV = [00H FFH]

Hard Handoff Parameters:

Reserved = [000]

11
1

A1 Element Identifier = [16H]

Band Class = [00000-11111]

Number of Preamble Frames

Reset L2

Reset FPC

Encryption Mode

= [000-111]

= [0,1]

= [0,1]

= [00,01]

2
Private
LCM

= [0,1]
Reserved = [000]

Nom_Pwr = [0000-1111]

Nom_Pwr
_Ext

= [0,1]
Reserved = [00]

FPC Subchannel Information

= <any value>

Reserved = [0000]

Power Control Step

= <any value>

-- Continued on next page --

432

FPC
SubChan
Info
Included
= [0,1]

Power
Control
Step
Included
= [0,1]

TIA/EIA/IS-2001

1
-- Continued from previous page -

IS-2000 Channel Identity:

A1 Element Identifier = [09H]

Length = <variable>
OTD
=
[0,1]

Channel Count = [000-111]

2
Frame Offset = [0H-FH]

Channel Information {1+:

4n

Physical Channel Type =

[ 01H (Fundamental Channel FCH IS-2000),
02H (Dedicated Control Channel DCCH IS-2000)]
Reserved
= [0]

Pilot PN
Code
(high part)

Pilot Gating Rate

= [00, 01, 10]

QOF Mask
= [00,01,10,11]

Walsh Code Channel Index (high

part) = <any value>

4n+1

Walsh Code Channel Index (low part) = <any value>

4n+2

Pilot PN Code (low part) = <any value>

4n+3

Reserved = [000]

ARFCN (high part)

Freq.
included

= [000-111]

= [1]

= [0,1]
ARFCN (low part) = [00H-FFH]

} Channel Information

IS-2000 Service Configuration Record:

A1 Element Identifier = [0EH]

Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

1
2

Bit-Exact Length Fill Bits

= [000 to 111]

(MSB)

3
4

IS-2000 Service Configuration Record Content

= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

-- Continued on next page --

433

...
Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

1
-- Continued from previous page -

IS-2000 Non-negotiable Service Configuration Record:

= [0FH]

A1 Element Identifier

Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

1
2

Bit-Exact Length Fill Bits

= [000 to 111]

(MSB)

3
4

IS-2000 Non-Negotiable Service Configuration Record Content

= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

434

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

6.1.5.7

Handoff Failure

2
3
4

This BSMAP message is sent from the BS to the MSC. It indicates to the MSC that
there has been a failure in the resource allocation process on an inter-BS handoff, and
that the handoff has been aborted.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Cause

6.2.2.19

BS -> MSC

Ma

5
6
7
8
9
10
11

a.

Allowable Values: Alternate signaling type reject; Handoff

procedure time-out; OAM&P intervention; Equipment failure; No
radio resource available; BS not equipped; Requested
transcoding/rate adaptation unavailable; Requested terrestrial
resource unavailable; Reversion to old channel; Radio interface
failure; Mobile station not equipped (or incapable); Terrestrial
circuit already allocated.

12
13

The following table shows the bitmap layout for the Handoff Failure message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = [04H]

Message Type = [16H]

Cause: A1 Element Identifier = [04H]

Length = [01H]
ext = [0]

Octet

Cause Value =
[01H (radio interface failure),
07H (OAM&P intervention),
0AH (reversion to old channel),
20H (equipment failure),
21H (no radio resource available),
22H (requested terrestrial resource unavailable),
25H (BS not equipped),
26H (MS not equipped),
2BH (Alternate signaling type reject),
30H (Requested transcoding/rate adaptation unavailable),
50H (terrestrial circuit already allocated)
7FH (handoff procedure timeout)]

435

2
3

TIA/EIA/IS-2001

6.1.5.8

2
3

Handoff Command
This BSMAP message is sent from the MSC to the source BS to commence source cell
handoff procedures. This message is in response to the Handoff Required message.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

RF Channel Identity

6.2.2.8

MSC -> BS

Oa

IS-95 Channel Identity

6.2.2.10

MSC -> BS

Ob

Cell Identifier List

6.2.2.21

MSC -> BS

Handoff Power Level

6.2.2.31

MSC -> BS

Oa

SID

6.2.2.9

MSC -> BS

Oa,d

Extended Handoff Direction Parameters

6.2.2.73

MSC -> BS

Oe

Hard Handoff Parameters

6.2.2.63

MSC -> BS

Oc

IS-2000 Channel Identity

6.2.2.34

MSC -> BS

IS-2000 Service Configuration Record

6.2.2.68

MSC -> BS

IS-2000 Non-negotiable Service Configuration

Record

6.2.2.69

MSC -> BS

O
O
O

4
5

a.

Included if the air interface channel allocated by the target is

ANSI/EIA/TIA-553.

6
7
8
9

b.

Included if the air interface channel allocated by the target is

TIA/EIA-95. It lists TIA/EIA-95 channels that have been allocated
by the target BS. This element is not present if the IS-2000
Channel Identity element is present.

10
11

c.

Included if the air interface channel allocated by the target is

TIA/EIA-95 or TIA/EIA/IS-2000.

12
13
14
15
16
17

d.

This element is only provided for ANSI/EIA/TIA-553 handoffs. In

the event that an TIA/EIA-IS-2000 channel cannot be allocated but
an ANSI/EIA/TIA-553 channel is allocated and identified in the
RF Channel Identity element, then this element provides the SID
of the target. The SID is sent to the MS in the Analog Handoff
Direction message from the source BS.

436

TIA/EIA/IS-2001

1
2
3

e.

4
5
6
7

The MSC, for intra-MSC handoffs, should use the Extended

Handoff Direction Parameters element supplied in the Handoff
Request Acknowledge message
Since TIA/EIA-41 only supports Search Window A, for interMSC handoffs, the source BS shall ignore all fields of the
Extended Handoff Direction Parameters element, except for
Search Window A.

8
9
10
11

f.

Included if the air interface channel allocated by the target is

TIA/EIA-IS-2000. It lists TIA/EIA-IS-2000 channels that have
been allocated by the target BS.. This element is not present if the
IS-95 Channel Identity element is present.

12
13

g.

This element is included if the MSC receives this element from

the target BS in the Handoff Request Acknowledge message.

14
15
16
17
18
19
20
21
22
23

h.

This element contains the TIA/EIA/IS-2000 non-negotiable

Service configuration record to support the transport of
information related to IS-2000 logical to physical mapping (LPM)
tables, and if needed, FPC power control information. It is
included if the target BS wishes to provide the source BS with
non-negotiable service configuration parameter values that may be
sent to the mobile station. It is up to the source BS to decide
whether or not to include the received non negotiable service
configuration record in the Universal Handoff Direction Message /
General Handoff Direction Message sent to the mobile station.

437

TIA/EIA/IS-2001

1
2

The coding of the Handoff Command for CDMA CDMA hard handoff is as
follows:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Message Type = [13H]

IS-95 Channel Identity: A1 Element Identifier = [22H]

Length = <variable>
Hard
Handoff =
[1]

Octet

Number of Channels to Add

= [001]

2
Frame Offset = [0H-FH]

(the following 4 octets are repeated once for each entry in the Cell Identifier List) {1+:
Walsh Code Channel Index = [00H-3FH]

Pilot PN Code (low part) = [00H-FFH]

Freq.
included

Power
Pilot PN
Combined
Code
(high part)
= [0]
= [0,1]

Reserved = [00]

ARFCN (high part)

= [000-111]

= [1]
ARFCN (low part) = [00H-FFH]

}(the above 4 octets are repeated once for each entry in the Cell Identifier List)

Cell Identifier List:

A1 Element Identifier = [1AH]

Length = [03H,06H]

Cell Identification Discriminator = [02H, 07H]

IF (Discriminator = 02H) , Cell Identification {1:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

} Cell Identification
-- Continued on next page --

438

j+2
j+3
j+4

TIA/EIA/IS-2001

1
-- Continued from previous page -
Reserved
= [0]

SID:

(MSB)

SID (high order) = [000-111]

SID (low order) = [00H-FFH]

A1 Element Identifier = [32H]

Extended Handoff Direction Parameters:

2
(LSB)

A1 Element Identifier = [10H]

Length = [09H]

Search Window A Size (Srch_Win_A) =

[0H-FH]

Search Window N Size (Srch_Win_N)

(ignored)

Search Window R Size (Srch_Win_R)

(ignored)

Add Pilot Threshold (T_Add) high order

(ignored)

T_Add (low order)

Drop Pilot Threshold (T_Drop)

(ignored)

(ignored)

Compare Threshold (T_Comp)

Drop Timer Value (T_TDrop)

(ignored)

(ignored)

Neighbor Max Age (Nghbor_Max_AGE)

Reserved = [0000]

6
7

(ignored)
Reserved = [00]

SOFT_SLOPE = [00 0000 - 11 1111]

Reserved = [00]

ADD_INTERCEPT = [00 0000 - 11 1111]

Reserved = [00]

DROP_INTERCEPT = [00 0000 - 11 1111]

10

Target BS P_REV = [00H FFH]

Hard Handoff Parameters:

Reserved = [000]
Number of Preamble Frames
= [000-111]
Reserved = [000]

Reserved = [00]

11
1

A1 Element Identifier = [16H]

Band Class = [00000-11111]
Private LCM
Reset FPC
Encryption Mode
= [0,1]
= [1]
= [00,01]
Nom_Pwr = [0000-1111]

Reset L2
= [1]
Nom_Pwr
_Ext
= [0,1]
FPC Subchannel Information
= <any value>

Reserved = [0000]

Power Control Step

= <any value>

-- Continued on next page --

439

2
3
4

FPC
SubChan
Info
Included
= [0,1]

Power
Control
Step
Included
= [0,1]

TIA/EIA/IS-2001

1
-- Continued from previous page -

IS-2000 Channel Identity:

A1 Element Identifier = [09H]

Length = <variable>
OTD =
[0,1]

Channel Count = [00001111]

2
Frame Offset = [0H-FH]

Channel Information {1+:

4n

Physical Channel Type =

[ 01H (Fundamental Channel FCH IS-2000),
02H (Dedicated Control Channel DCCH IS-2000)],
Reserved
= [0]

Pilot PN
Code
(high part)

Pilot Gating Rate

= [00, 01, 10]

QOF Mask
= [00,01,10,11]

Walsh Code Channel Index (high

part) = <any value>

4n+1

Walsh Code Channel Index (low part) = <any value>

4n+2

Pilot PN Code (low part) = <any value>

4n+3

Reserved = [000]

ARFCN (high part)

Freq.
included

= [000-111]

= [1]

= [0,1]
ARFCN (low part) = [00H-FFH]

} Channel Information

IS-2000 Service Configuration Record:

A1 Element Identifier = [0EH]

Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

1
2

Bit-Exact Length Fill Bits

= [000 to 111]

(MSB)

3
4

IS-2000 Service Configuration Record Content

= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

-- Continued on next page --

440

...
Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

1
-- Continued from previous page -

IS-2000 Non-negotiable Service Configuration Record:

= [0FH]

A1 Element Identifier

Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

1
2

Bit-Exact Length Fill Bits

= [000 to 111]

(MSB)

3
4

IS-2000 Non-Negotiable Service Configuration Record Content

= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

441

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

1
2

The coding of the Handoff Command for CDMA AMPS hard handoff is as
follows:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

2
1

Message Type = [13H]

RF Channel Identity:

Octet

A1 Element Identifier = [21H]

Color Code = [00H-FFH]

Reserved = [0000 00]

N-AMPS ANSI/EIA
/TIA-553
= [0,1]

= [0,1]

Reserved = [000000]

Timeslot Number

= [00-11]
Reserved = [00000]

ARFCN (high part) = [000-111]

ARFCN (low part) = [00H-FFH]

Handoff Power Level:

6
1

A1 Element Identifier = [26H]

Length = [06H]

Number of Cells = [01H]

Reserved ID Type = [00,01,10]

= [0]
(Discriminator 1,7,8)
(MSB)

Handoff Power Level = [00000-11111]

LAC = [0001H-FFFFH]

5
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Reserved
= [0]

(MSB)

SID:

Sector = [0H-FH] (0H = Omni)

SID (high order) = [000-111]

-- Continued on next page --

442

8
1

A1 Element Identifier = [32H]

SID (low order) = [00H-FFH]

2
(LSB)

TIA/EIA/IS-2001

1
-- Continued from previous page -

Hard Handoff Parameters:

Reserved = [000]

A1 Element Identifier = [16H]

Band Class = [00000-11111]

(ignored)
Number of Preamble Frames

Reset L2

Reset FPC

Encryption Mode

= [000-111]

= [0,1]

= [0,1]

= [00,01]

(ignored)

(ignored)

(ignored)

Private
LCM

= [0,1]
(ignored)

Reserved = [000]
(ignored)

Nom_Pwr = [0000-1111]

Nom_Pwr
_Ext

(ignored)

= [0,1]
(ignored)
Reserved = [00]

FPC Subchannel Information

= <any value>
(ignored)

Reserved = [0000]

Power Control Step

= <any value>
(ignored)

443

FPC
SubChan
Info
Included
= [0,1]
(ignored)

Power
Control
Step
Included
= [0,1]
(ignored)

TIA/EIA/IS-2001

6.1.5.9

Handoff Required Reject

2
3

This BSMAP message is sent from the MSC to the BS. It indicates to the BS that it
was not possible to execute a handoff as requested.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Cause

6.2.2.19

MSC -> BS

Ma

4
5
6
7

a.

Allowable Cause Values: OAM&P Intervention; Equipment

failure; No radio resource available; Requested terrestrial resource
unavailable; Requested transcoding/rate adaptation unavailable;
Handoff blocked; Handoff procedure timeout, BS not equipped.

8
9
10

The following table shows the bitmap layout for the Handoff Required Reject
message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = [04H]

Message Type = [1AH]

Cause: A1 Element Identifier = [04H]

Length = [01H]
ext = [0]

Octet

Cause Value =
[07H (OAM&P intervention),
20H (equipment failure),
21H (no radio resource available),
22H (requested terrestrial resource unavailable),
25H (BS not equipped),
2AH (handoff blocked),
30H (Requested transcoding/rate adaptation unavailable),
7FH (handoff procedure timeout)]

444

2
3

TIA/EIA/IS-2001

6.1.5.10

Handoff Commenced

2
3
4
5
6
7
8

This BSMAP message is used for TIA/EIA-IS-2000 hard handoffs. It is sent by the
source BS to the MSC to indicate that the handoff command has been sent to the
mobile station, and that an acknowledgment has been received from the mobile
station. For TIA/EIA-95, if the handoff command is sent using quick repeats, the
source BS may not request an acknowledgment from the mobile. In this case, the
source BS will send the Handoff Commenced after all the quick repeats have been
transmitted to the mobile station.
Information Element

Section
Reference

Message Type

6.2.2.4

Element
Direction

Type

BS -> MSC

9
10

The following table shows the bitmap layout for the Handoff Commenced message:
7

BSMAP Header:

Message Discrimination = [00H]

Octet
1

Length Indicator (LI) = [01H]

Message Type = [15H]

445

TIA/EIA/IS-2001

6.1.5.11

Handoff Complete

2
3
4

This BSMAP message is sent from the target BS to the MSC to inform the MSC that
the mobile station has arrived on the new channel and has completed all (if any)
required connection procedures.
Information Element

Section
Reference

Message Type

6.2.2.4

Element
Direction

Type

BS -> MSC

5
6

The following table shows the bitmap layout for the Handoff Complete message:
7

BSMAP Header:

Message Discrimination = [00H]

Octet
1

Length Indicator (LI) = [01H]

Message Type = [14H]

446

TIA/EIA/IS-2001

6.1.5.12

Handoff Performed

2
3
4
5

This BSMAP message is sent from the BS to the MSC in order to indicate that the BS
has performed an internal handoff. The handoff may have been internal or in
conjunction with another BS. The purpose of this message is to update the call
configuration for the MSC. The Cell Identifier List is included for billing, trace, etc.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Cause

6.2.2.19

BS -> MSC

Ma

Cell Identifier List

6.2.2.21

BS -> MSC

Ob

6
7
8
9
10

a.

Allowable cause values are: Uplink quality, Uplink strength,

Downlink quality, Downlink strength, Distance, Interference,
Better cell (i.e., Power budget), OAM&P intervention. For
TIA/EIA-IS-2000 soft handoff procedures: Inter-BS soft handoff
drop target; Intra-BS soft handoff drop target.

11
12

b.

The MSC shall consider the first cell in the Cell Identifier List to
be the designated cell.

13

The following table shows the bitmap layout for the Handoff Performed message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
1
2

Message Type = [17H]

Cause: A1 Element Identifier = [04H]

Length = [01H]
ext = [0]

Cause Value =
[02H (uplink quality),
03H (uplink strength),
04H (downlink quality),
05H (downlink strength),
06H (distance),
07H (OAM&P intervention),
1BH (inter-BS soft handoff drop target),
0EH (better cell),
0FH (interference),
1DH (intra-BS soft handoff drop target)]
-- Continued on next page --

447

2
3

TIA/EIA/IS-2001

1
-- Continued from previous page -

Cell Identifier List:

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [02H,07H]

IF (Discriminator = 02H), Cell Identification {1+:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H) ), Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

} Cell Identification
2
3

6.1.5.13

UNUSED SECTION

6.1.5.14

UNUSED SECTION

4
5
6

448

j+2
j+3
j+4

TIA/EIA/IS-2001

6.1.6

Facility Management Message Formats

6.1.6.1

UNUSED SECTION

6.1.6.2

Block

2
3
4
5
6
7
8

This BSMAP message is sent from the BS to the MSC to indicate that one or more
terrestrial circuits shall be blocked at the MSC, and cannot therefore be used for
traffic.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Circuit Identity Code

6.2.2.22

BS -> MSC

Cause

6.2.2.19

BS -> MSC

Circuit Group

6.2.2.148

BS -> MSC

b,c

9
10
11

a.

This cause value applies to all circuits identified in this message.

Allowable cause values: OAM&P intervention, Equipment failure,
No radio resource available.

12
13
14

b.

If this element is presentit shall include the value found within the
Circuit Identity Code element as the first value represented within
its range of circuit identity code values.

15
16

c.

This element shall not be sent to implementations of the CDG IOS

earlier than IOS v3.1.0.

449

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the Block message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

(MSB)

2
1

Message Type = [40H]

Circuit Identity Code:

A1 Element Identifier = [01H]

PCM Multiplexer = <any value>

(LSB)

Timeslot = [00000-11111]

3
1

Cause: A1 Element Identifier = [04H]

Length = [01H]

ext =
[0]

Octet

2
3

Cause Value =
[07H (OAM&P intervention),
20H (equipment failure),
21H (no radio resource available)]

Circuit Group : A1 Element Identifier = [19H]

Length = <variable>

Reserved = [000000]

All
Circuits
= [0,1]

Inclusiv
e=
[0,1]

Count = [01H to FFH]

(MSB)
(first
unused
bit - if
any)

4
5

First CIC: PCM Multiplexer = <any value>

(LSB)
(second
unused
bit - if
any)

Timeslot = [00000-11111]

(third
unused
bit - if
any)

(fourth
unused
bit - if
any)

(fifth
unused
bit - if
any)

(sixth
unused
bit - if
any)

(seventh
unused
bit - if
any)

Circuit Bitmap = <any value>

(corresp
to value
in First
CIC
field)

450

TIA/EIA/IS-2001

6.1.6.3

Block Acknowledge

2
3
4

The MSC sends this BSMAP message to BS to acknowledge the receipt of an earlier
block message, and to indicate that the circuits concerned have been removed from
service.
Information Element

Section
Reference

Element
Direction

Message Type

6.2.2.4

MSC -> BS

Circuit Identity Code

6.2.2.22

MSC -> BS

5
6

Type
M
a

This element is the same as the one received in the Block message. The following
table shows the bitmap layout for the Block Acknowledge message:
7

BSMAP Header:

Octet
1

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

6.1.6.4

8
9
10

A1 Element Identifier = [01H]

PCM Multiplexer = <any value>

(LSB)

Message Type = [41H]

Circuit Identity Code:

(MSB)

Timeslot = [00000-11111]

Unblock
This BSMAP message is sent from the BS to the MSC to indicate that one or more
terrestrial resources may be returned to service at the MSC, and can therefore be used
for traffic.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Circuit Identity Code

6.2.2.22

BS -> MSC

Circuit Group

6.2.2.148

BS -> MSC

a,b

11
12
13

a.

If this element is presentit shall include the value found within the
Circuit Identity Code element as the first value represented within
its range of circuit identity code values.

14
15

b.

This element shall not be sent to implementations of the CDG IOS

earlier than IOS v3.1.0.

451

TIA/EIA/IS-2001

The following table shows the bitmap layout for the Unblock message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

(MSB)

2
1

Message Type = [42H]

Circuit Identity Code:

A1 Element Identifier = [01H]

PCM Multiplexer = <any value>

(LSB)

Timeslot = [00000-11111]

3
1

Circuit Group: A1 Element Identifier = [19H]

Length = <variable>

Reserved = [000000]

All
Circuits
= [0,1]

Inclusive
= [0,1]

Count = [01H to FFH]

(MSB)
(first
unused
bit - if
any)

(second
unused
bit - if
any)

Timeslot = [00000-11111]

(third
unused
bit - if
any)

(fourth
unused
bit - if
any)

(fifth
unused
bit - if
any)

First CIC: PCM Multiplexer = <any value>

(LSB)

Octet

(sixth
unused
bit - if
any)

(seventh
unused
bit - if
any)

Circuit Bitmap = <any value>

(corresp
to value
in First
CIC
field)

452

TIA/EIA/IS-2001

6.1.6.5

Unblock Acknowledge

2
3
4

The MSC sends this BSMAP message to BS to acknowledge the receipt of an earlier
Unblock message, and to indicate that the circuits concerned have been returned to
service.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Circuit Identity Code

6.2.2.22

MSC -> BS

The following table shows the bitmap layout for the Unblock Acknowledge message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Message Type = [43H]

Circuit Identity Code:

(MSB)

A1 Element Identifier = [01H]

PCM Multiplexer = <any value>

(LSB)

Timeslot = [00000-11111]

453

Octet
1
2
1
1
2
3

TIA/EIA/IS-2001

6.1.6.6

Reset

2
3
4

This BSMAP message can be sent either from the BS to the MSC or from the MSC to
the BS. It indicates to the receiving entity that the transmitting entity has failed and
has lost memory of the calls in progress, calls set up, and associated references.

This message is sent as a connectionless message.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS <-> MSC

Cause

6.2.2.19

BS <-> MSC

Ma

Software Version

6.2.2.65

BS <-> MSC

Ob

a.

Allowable cause values: OAM&P intervention, Equipment failure.

b.

This element shall not be sent to an entity operating with V2.x.y.

8
9

The following table shows the bitmap layout for the Reset message:
7

BSMAP Header:

Message Discrimination = [00H]

Octet
1

Length Indicator (LI) = [04H]

Message Type = [30H]

Cause: A1 Element Identifier = [04H]

Length = [01H]
ext = [0]

Cause Value =

2
3

[07H (OAM&P intervention),

20H (equipment failure)]

Software Version:

A1 Element Identifier = [31H]

Length = <variable>

IOS Major Revision Level (X) = [04H]

IOS Minor Revision Level (Y) = [00H]

IOS Point Release Level (Z) = [00H]

Manufacturer/Carrier Software Information = <printable ASCII character>

Manufacturer/Carrier Software Information = <printable ASCII character>

454

TIA/EIA/IS-2001

6.1.6.7

Reset Acknowledge

2
3
4
5

This BSMAP message can be sent either from the BS to the MSC, or from the MSC to
the BS. It indicates to the receiving entity that the transmitting entity has cleared all
calls and reset all references, and is ready to resume service. If sent by the MSC, it
also indicates that all MSC-BS terrestrial circuits have been idled.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS <-> MSC

Software Version

6.2.2.65

BS <-> MSC

Oa

6
7

a.

The following table shows the bitmap layout for the Reset Acknowledge message:
7

This element shall not be sent to an entity implemented to a prior version of this
specification.

BSMAP Header:

Message Discrimination = [00H]

Octet
1

Length Indicator (LI) = [01H]

Message Type = [31H]

Software Version:

A1 Element Identifier = [31H]

Length = <variable>

IOS Major Revision Level (X) = [04H]

IOS Minor Revision Level (Y) = [00H]

IOS Point Release Level (Z) = [00H]

Manufacturer/Carrier Software Information = <printable ASCII character>

Manufacturer/Carrier Software Information = <printable ASCII character>

455

TIA/EIA/IS-2001

6.1.6.8

Reset Circuit

2
3
4

This BSMAP message can be sent either from the BS to the MSC or from the MSC to
the BS. It indicates to the receiving entity that the state of the circuits indicated in the
message is unknown.

This message is sent as a connectionless message.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS <-> MSC

Circuit Identity Code

6.2.2.22

BS <-> MSC

Cause

6.2.2.19

BS <-> MSC

Circuit Group

6.2.2.148

BS <-> MSC

b,c

6
7
8

a.

This cause value applies to all circuits identified in this message.

Allowable cause values: OAM&P intervention, Call Processing,
Equipment failure.

9
10
11

b.

If this element is presentit shall include the value found within the
Circuit Identity Code element as the first value represented within
its range of circuit identity code values.

12
13

c.

This element shall not be sent to implementations of the CDG IOS

earlier than IOS v3.1.0.

456

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the Reset Circuit message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

(MSB)

2
1

Message Type = [34H]

Circuit Identity Code:

A1 Element Identifier = [01H]

PCM Multiplexer = <any value>

(LSB)

Timeslot = [00000-11111]

3
1

Cause: A1 Element Identifier = [04H]

Length = [01H]

ext =
[0]

Octet

2
3

Cause Value =
[07H (OAM&P intervention),
09H (Call Processing),
20H (equipment failure)]

Circuit Group: A1 Element Identifier = [19H]

Length = <variable>

Reserved = [000000]

All
Circuits
= [0,1]

Inclusive
= [0,1]

Count = [01H to FFH]

(MSB)
(first
unused
bit - if
any)

4
5

First CIC: PCM Multiplexer = <any value>

(LSB)
(second
unused
bit - if
any)

Timeslot = [00000-11111]

(third
unused
bit - if
any)

(fourth
unused
bit - if
any)

(fifth
unused
bit - if
any)

(sixth
unused
bit - if
any)

(seventh
unused
bit - if
any)

Circuit Bitmap = <any value>

(corresp
to value
in First
CIC
field)

457

TIA/EIA/IS-2001

6.1.6.9

Reset Circuit Acknowledge

2
3
4

This BSMAP message can be sent either from the BS to the MSC, or from the MSC to
the BS. It indicates to the receiving entity that the transmitting entity has cleared any
possible calls using the specified circuits (i.e., the circuits are idled).
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS <-> MSC

Circuit Identity Code

6.2.2.22

BS <-> MSC

5
6

The following table shows the bitmap layout for the Reset Circuit Acknowledge
message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Message Type = [35H]

Circuit Identity Code:

(MSB)

A1 Element Identifier = [01H]

PCM Multiplexer = <any value>

(LSB)

Timeslot = [00000-11111]

458

Octet
1
2
1
1
2
3

TIA/EIA/IS-2001

1
2

6.1.6.10

Transcoder Control Request

3
4
5

This BSMAP message is sent from the MSC to the BS to change the state of the
inband signaling mechanism at the BS. A disable directive will also result in the BS
reverting to tandem vocoding mode if already in tandem free mode.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC->BS

Transcoder Mode

6.2.2.58

MSC->BS

6
7

The following table shows the bitmap layout for the Transcoder Control Request
message:
7

BSMAP Header:

Octet
1

Message Discrimination = [00H]

Length Indicator (LI) = [04H]

2
1

Message Type = [0CH]

Transcoder Mode:

A1 Element Identifier = [1CH]

Length = [01H]

Reserved = [0000 000]

TFO
Mode
=[0,1]

8
9

6.1.6.11

Transcoder Control Acknowledge

10
11
12

This BSMAP message is sent from the BS to the MSC to acknowledge whether
tandem free operation was successfully enabled or disabled in response to the MSCs
mode setting request.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS->MSC

Cause

6.2.2.19

BS->MSC

Oa

13
14
15
16
17

a. If this element is not present, then tandem free operation was either
successfully established or disabled (depending on the directive from the
MSC). If the element is present, its only allowable value is TFO Control
Request Failed. This value is used when the MSC directive received in
the Transcoder Control Request could not be honored.

18
19

The following table shows the bitmap layout for the Transcoder Control Request
message:
7

5
BSMAP Header:

Message Discrimination = [00H]

459

Octet
1

TIA/EIA/IS-2001

Length Indicator (LI) = [04H]

Message Type = [0BH]

Cause: A1 Element Identifier = [04H]

Length = [01H]
ext =
[0]

Cause Value = 33H (TFO Control Request Failed)

1
2
3

6.1.6.12

UNUSED SECTION

6.1.6.13

UNUSED SECTION

6.1.6.14

UNUSED SECTION

4
5
6
7

460

2
3

TIA/EIA/IS-2001

6.1.7

Application Data Delivery Service (ADDS) Message Formats

6.1.7.1

ADDS Page

2
3
4
5

This BSMAP message is sent from the MSC to the BS to request delivery of an
application data message on the paging channel.
Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

MSC -> BS

Mobile Identity (IMSI/Broadcast Address)

6.2.2.16

MSC -> BS

Ma

ADDS User Part

6.2.2.67

MSC -> BS

Mb

Tag

6.2.2.62

MSC -> BS

Oc

Cell Identifier List

6.2.2.21

MSC -> BS

Od

Slot Cycle Index

6.2.2.17

MSC -> BS

Oe

IS-2000 Mobile Capabilities

6.2.2.70

MSC -> BS

Of

a.

This element will contain IMSI or Broadcast Address.

7
8
9
10
11
12
13

b.

Contains the application data information to be sent to the mobile

user, encoded using the syntax appropriate for the current radio
channel and service type. In the case of the Short Message
Service, the ADDS User Part contains an application type field
indicating Short Message Service. In the case of the Position
Location Data, the ADDS User Part contains an application type
field indicating Position Location Data.

14
15
16

c.

If this element is present in this message, the value shall be saved

at the BS to be included if an ADDS Page Ack message is sent in
response to this message.

17
18
19
20

d.

The cell identifiers indicate the cells and location areas in which
the BS is to attempt delivery of the message. When the Cell
Identifier information element is absent, the BS shall attempt
delivery in all cells controlled by the BS.

21
22
23
24
25
26
27
28

e.

This optional element is included where slotted paging is

performed on TIA/EIA-IS-2000 paging channels. It is used by the
BS to compute the correct paging channel slot on each paging
channel. In TIA/EIA-IS-2000 systems, if this element is absent,
then it is assumed that the MS is operating in non-slotted mode.
Note: For SMS Broadcast, the presence or absence of this element
does not indicate the slotted/non-slotted operating mode of the
MS.

29
30

f.

This element is only included when the MSC has previously been
given this information by a BS.

31

461

TIA/EIA/IS-2001

The following table shows the bitmap layout for the ADDS Page message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [65H]

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

IF (Type of Identity in octet 3 = 110), Mobile Identity {1:

Identity Digit 1 = [0H-9H] (BCD)

Type of Identity =
[ 110 (IMSI) ]

Odd/even
Indicator

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

} OR IF (Type of Identity in octet 3 = 010), Mobile Identity {1:

Reserved = [0000 0]

Type of Identity =
[010 Broadcast Identifier]

Priority = [00 11]

Message ID = [00 0000 11 1111]

Zone ID = [00H FFH]

(MSB)

Service = [0000H FFFFH]

6
(LSB)

Language = [00H FFH]

7
8

} Mobile Identity

ADDS User Part:

A1 Element Identifier = [3DH]

Length = <variable>
Reserved = [00]

(MSB)

2
3

Data Burst Type =

[ 03H (SMS),
04H (OTA),
05H (PLD) ]
Application Data Message = <any value>

(LSB)

-- Continued on next page --

462

TIA/EIA/IS-2001

1
-- Continued from previous page -

Tag:

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

Cell Identifier List:

5
1

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [02H,05H]

IF (Discriminator = 02H), Cell Identification {1+:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 05H), Cell Identification {1+:

(MSB)

LAC = [0001H-FFFFH]

j
(LSB)

j+1

} Cell Identification

Slot Cycle Index:

A1 Element Identifier = [35H]

Reserved = [00000]

Slot Cycle Index = [000-111]

IS-2000 Mobile Capabilities:

A1 Element Identifier = [11H]

Length = <variable>
Reserved
= [ 000 ]

FCH
DCCH
Supported Supported
= [0,1]
= [0,1]

Geo Location Type = <any

value> (ignored)

OTD
Supported
= [0,1]

Geo
Location
Included
= <any
value>
(ignored)

-- Continued on next page --

463

2
1
2

Enhanced QPCH
RC CFG Supported
Supported = [0,1]
= [0,1]

FCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0]

FCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

4
5

TIA/EIA/IS-2001

1
-- Continued from previous page -(MSB)

6
FCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

DCCH Information: Bit-Exact Length Octet Count

= [00H to FFH]
Reserved
= [0000 0]

k+1

DCCH Information:
Bit-Exact Length Fill Bits
= [000 to 111]

(MSB)

k+2

k+3
DCCH Information Content
= <any value>
Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

464

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

6.1.7.2

2
3

ADDS Transfer
This BSMAP message is sent from the BS to the MSC whenever an application data
message is received from the MS on the access channel.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Mobile Identity (IMSI)

6.2.2.16

BS -> MSC

ADDS User Part

6.2.2.67

BS -> MSC

Ma

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Ob

Authentication Response Parameter AUTHR

6.2.2.46

BS -> MSC

Oc

Authentication Confirmation Parameter RANDC

6.2.2.42

BS -> MSC

Od

Authentication Parameter COUNT

6.2.2.47

BS -> MSC

Oe

Authentication Challenge Parameter RAND

6.2.2.45

BS -> MSC

Of

Authentication Event

6.2.2.114

BS -> MSC

Og

Cell Identifier

6.2.2.20

BS -> MSC

Oh

CDMA Serving One Way Delay

6.2.2.79

BS->MSC

Oi

4
5
6
7
8
9

a.

Contains the application data information that was received from the
MS. In the case of the Short Message Service, the application data
information the Short Message. In the case of the Position Location
Data, the application data information is the Position Location Data.
An application type field in this element is used to distinguish the
application, e.g., Short Message" or "Position Location Data.

10
11

b.

The second occurrence of the Mobile Identity element contains the

ESN.

12
13
14

c.

Included where broadcast authentication is performed, and contains

the Authentication Response Parameter, AUTHR, as computed by the
MS.

15
16
17

d.

This optional element contains the RANDC received from the MS.
RANDC shall be included whenever it is received from the MS and
authentication is enabled.

18
19

e.

Included where broadcast authentication is performed, and contains

the mobiles call history count for authentication operations.

20
21
22
23

f.

Included where broadcast authentication is performed, and contains

the random number (RAND) value used when the BS is responsible
for RAND assignment and can correlate this parameter with RAND
used by the MS in its authentication computation.

24
25
26

g.

Present when an authentication enabled BS does not receive the

authentication parameters (AUTHR, RANDC and COUNT) from the
MS, or when a RAND/RANDC mismatch has occurred.

465

TIA/EIA/IS-2001

1
2
3
4

h.

Identifies the cell where the application data (e.g., SMS-MO) was
received from the MS. Discriminator type0000 0010 (Cell ID) may
be used in the ADDS Transfer message. For more information, refer
to section 6.2.2.20.

5
6
7

i.

This IE is included if the data burst type = PLD (05H), if applicable

to the geo-location technology, and if this technology is supported at
the base station.

466

TIA/EIA/IS-2001

The following table shows the bitmap layout for the ADDS Transfer message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [67H]

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

2
Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

ADDS User Part:

A1 Element Identifier = [3DH]

Length = <variable>
Reserved = [00]

(MSB)

2
3

Data Burst Type =

[ 03H (SMS),
04H (OTA),
05H (PLD) ]
Application Data Message = <any value>

(LSB)

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

-- Continued on next page --

467

TIA/EIA/IS-2001

1
-- Continued from previous page -

Authentication Response Parameter (AUTHR):

A1 Element Identifier = [42H]

Length = [04H]
Reserved = [0000]
[0]

[0]

[0]

Auth Signature Type = [0001] (AUTHR)

[0]

[0]

[0]

(MSB)

5
(LSB)

Authentication Confirmation Parameter (RANDC): A1 Element Identifier =

[28H]
RANDC = [00H-FFH]

Authentication Parameter COUNT:

Reserved = [00]

Count = [000000-111111]

1
2

A1 Element Identifier = [41H]

Length = [05H]
Reserved = [0000]

A1 Element Identifier = [40H]

Authentication Challenge Parameter (RAND):

3
4

Auth Signature = <any value>

1
2

Random Number Type = [0001] (RAND)

(MSB)

3
4

RAND = <any value>

5
6
(LSB)

Authentication Event:

A1 Element Identifier = [4AH]

7
1

Length = [01H]

Event = [01H,02H]

(Parameters not received, RANDC/RAND mismatch)

Cell Identifier: A1 Element Identifier = [05H]

Length = [03H]

Cell Identification Discriminator = [02H]

IF (Discriminator = 02H) , Cell Identification {1:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

} Cell Identification
-- Continued on next page --

468

j
j+1

TIA/EIA/IS-2001

1
-- Continued from previous page -

CDMA Serving One Way Delay: A1 Element Identifier = [0CH]

Length = [06H, 09H]

Cell Identification Discriminator = [02H,07H]

IF (Discriminator = 02H), Cell Identification {1:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification
(MSB)

CDMA Serving One Way Delay = [0000H-FFFFH]

k
(LSB)

Reserved = [0000 00]

Resolution = [00, 01,

10]

469

k+1
k+2

TIA/EIA/IS-2001

6.1.7.3

2
3
4
5

ADDS Deliver
This DTAP message is sent from the MSC to the BS to request delivery of an
application data message to an MS on a traffic channel. This message can also be sent
from the BS to the MSC to deliver an application data message received on the traffic
channel.

Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

MSC <-> BS

Reserved Octet

6.2.2.40

MSC <-> BS

Message Type

6.2.2.4

MSC <-> BS

ADDS User Part

6.2.2.67

MSC <-> BS

Ma

Tag

6.2.2.62

MSC -> BS

Ob

CDMA Serving One Way Delay

6.2.2.79

BS->MSC

Oc

6
7
8
9
10
11
12

a.

Contains the application data information that was received from

the MS. In the case of the Short Message Service, the application
data information is the Short Message. In the case of the Position
Location Data, the application data information is the Position
Location Data. An application type field in this element is used to
distinguish the application, e.g., Short Message" or "Position
Location Data.

13
14

b.

This element is optional in this message. If used in this message,

it shall be returned to the MSC in the ADDS Deliver Ack.

15
16
17

c.

This IE is included if the data burst type = PLD (05H), if

applicable to the geo-location technology, and if this technology is
supported at the base station.

470

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the ADDS Deliver message:
7

Octet
1

DTAP Header: Message Discrimination = [01H]

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = <variable>

Reserved = [0000]

Protocol Discriminator = [0011]

Reserved - Octet = [00H]

Message Type = [53H]

ADDS User Part:

Length = <variable>

Reserved = [00]

Data Burst Type =

[ 03H (SMS),
04H (OTA),
05H (PLD) ]

(MSB)

Application Data Message = <any value>

(LSB)

Tag:

n
1

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

-- Continued on next page --

471

TIA/EIA/IS-2001

1
-- Continued from previous page -

CDMA Serving One Way Delay: A1 Element Identifier = [0CH]

Length = [06H, 09H]

Cell Identification Discriminator = [02H,07H]

IF (Discriminator = 02H), Cell Identification {1:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 07H), Cell Identification {1:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification
(MSB)

CDMA Serving One Way Delay = [0000H-FFFFH]

k
(LSB)

Reserved = [0000 00]

Resolution = [00, 01,

10]

472

k+1
k+2

TIA/EIA/IS-2001

6.1.7.4

2
3
4
5
6
7

ADDS Page Ack

This BSMAP message is sent from the BS to the MSC to indicate that the BS received
a Layer 2 acknowledgment from the MS indicating that the point-to-point application
data message was successfully delivered, or that the BS received the ADDS Page
message to send an SMS broadcast message, or that the ADDS message was too long
for delivery on the Paging channel, or that an internal BS failure has occurred with
respect to the ability to complete an ADDS Page activity.

Information Element

Section
Reference

Element
Direction

Type

Message Type

6.2.2.4

BS -> MSC

Mobile Identity (IMSI/Broadcast Address)

6.2.2.16

BS -> MSC

Ma

Tag

6.2.2.62

BS -> MSC

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Ob

Cause

6.2.2.19

BS -> MSC

Oc

Cell Identifier

6.2.2.20

BS -> MSC

Od

a.

This element will contain an IMSI.

9
10

b.

The second occurrence of the Mobile Identity element contains the

ESN.

11
12
13
14
15
16
17

c.

Used to indicate an error situation. In particular, this element can

be used to carry information to the MSC that the ADDS User Part
element contained in the ADDS Page message is too long to be
carried on the paging channel. Allowable cause values are: ADDS
message too long for delivery on the paging channel, equipment
failure. This element is required if the ESN is received from the
MS.

18
19
20

d.

Identifies the cell where the air interface acknowledgement was

received corresponding to the paging channel message sent as a
result of an ADDS Page message.

21

473

TIA/EIA/IS-2001

The following table shows the bitmap layout for the ADDS Page Ack message:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [66H]

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

IF (Type of Identity in octet 3 = 110), Mobile Identity {1:

Identity Digit 1 = [0H-9H] (BCD)

Type of Identity

Odd/even
Indicator

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

} OR IF {Type of Identity in octet 3 = 010), Mobile Identity {1:

Reserved = [0000 0]

Type 0f Identity = [010

(Broadcast Identifier)]

Priority = [0011]

Message ID=[00 0000 - 11 1111]

Zone ID = [00H FFH]

(MSB)

Service = [00 00H FF FFH]

6
(LSB)

} Mobile Identity

Tag:

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

-- Continued on next page --

474

TIA/EIA/IS-2001

1
-- Continued from previous page -

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Cause: A1 Element Identifier = [04H]

Length = [01H]

ext = [0]

7
1
2

Cause Value =

[20H (equipment failure),

71H (ADDS message too long for delivery on paging channel)]

(MSB)

Cell Identifier: A1 Element Identifier = [05H]

Length = [03H]

Cell Identification Discriminator = [02H]

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

475

4
5

TIA/EIA/IS-2001

6.1.7.5

ADDS Deliver Ack

2
3
4

This DTAP message shall be sent from the BS to the MSC when a Layer 2
acknowledgment from the MS has been received at the BS for an ADDS Deliver
message that contains a Tag element.

5
6
7
8

(Note: If the BS does not receive an acknowledgment after transmitting the CDMA
Data Burst message, it shall retransmit the message. The BS shall not exceed a
maximum number of re-transmissions, to be selected by the BS manufacturer. When
the BS reaches the maximum number of re-transmissions, it shall clear the call.)
Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

BS -> MSC

Reserved Octet

6.2.2.40

BS -> MSC

Message Type

6.2.2.4

BS -> MSC

Tag

6.2.2.62

BS -> MSC

Cause

6.2.2.19

BS -> MSC

Oa

9
10

a.

Used to indicate an error situation. Allowable cause value: Reject

Indication from Mobile Station.

11
12

The following table shows the bitmap layout for the ADDS Deliver Ack message:
7

Octet
1

DTAP Header: Message Discrimination = [01H]

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = <variable>

Reserved = [0000]

Tag:

Protocol Discriminator = [0011]

Reserved - Octet = [00H]

Message Type = [54H]

1
1

A1 Element Identifier = [33H]

(MSB)

2
Tag Value = <any value>

3
4
(LSB)

Cause: A1 Element Identifier = [04H]

Length = [01H]

ext = [0]

Cause Value =
[70H (rejection indication from mobile station)]

476

5
1
2
3

TIA/EIA/IS-2001

6.1.8

2
3

Error Handling Messages

This section contains messages used for general error handling.

6.1.8.1

4
5
6
7

Rejection
The Rejection message is used by the BS to indicate to the MSC that the mobile
station has indicated rejection of a command/message. This is coded as a BSMAP
message when triggered by a Mobile Station Reject Order on the access channel and a
DTAP message otherwise.

Information Element

Section
Reference

Element
Direction

Type

Protocol Discriminator

6.2.2.39

BS -> MSC

Ma

Reserved - Octet

6.2.2.40

BS -> MSC

Ma

Message Type

6.2.2.4

BS -> MSC

Mobile Identity (IMSI)

6.2.2.16

BS -> MSC

Ob, c

Mobile Identity (ESN)

6.2.2.16

BS -> MSC

Ob, d

IS-2000 Cause Value

6.2.2.110

BS -> MSC

Oe

8
9

a.

These elements are not used in BSMAP messages and shall be

included in DTAP messages.

10
11

b.

These elements are not used in DTAP messages and shall be

included in BSMAP messages.

12

c.

This element shall be set to IMSI.

13
14

d.

The second occurrence of the Mobile Identity element contains the

ESN.

15
16

e.

Contains the cause indication sent by an TIA/EIA-IS-2000 mobile

station in an TIA/EIA-IS-2000 Mobile Station Reject Order.

477

TIA/EIA/IS-2001

1
2

When the Rejection message is sent as a BSMAP message, the following format
applies:
7

BSMAP Header:

Message Discrimination = [00H]

Length Indicator (LI) = <variable>

Octet
2

Message Type = [56H]

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

2
Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

IS-95 Cause Value:

A1 Element Identifier = [62H]

7
1

Length = [01H]

IS-95 Cause Information = <any value>

478

TIA/EIA/IS-2001

1
2

When the Rejection message is sent as a DTAP message, the following format
applies:
7

DTAP Header: Message Discrimination = [01H]

Octet
1

Data Link Connection Identifier (DLCI) = [00H]

Length Indicator (LI) = [06H]

Reserved = [0000]

Protocol Discriminator = [0011]

Reserved - Octet = [00H]

Message Type = [56H]

IS-95 Cause Value:

A1 Element Identifier = [62H]

Length = [01H]

IS-95 Cause Information = <any value>

479

TIA/EIA/IS-2001

6.1.9

A3 Interface Message Formats

6.1.9.1

A3-Connect

3
4

This A3 message is sent from the target BS to the source BS to initiate or add cells to
one or more A3 user traffic connections.
Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

BTS -> SDU

Call Connection Reference

6.2.2.98

BTS -> SDU

Correlation ID

6.2.2.108

BTS -> SDU

Oa

SDU ID

6.2.2.91

BTS -> SDU

Ob

A3 Connect Information

6.2.2.144

BTS -> SDU

Oc,d

5
6

a.

If this element is included in this message, it shall be returned in

the A3-Connect Ack message.

7
8

b.

If this element was included in the A7-Handoff Request message,

it is required in this message.

9
10

c.

At least one instance of this element is required in this message.

Multiple instances of this element may be present in this message.

11
12
13
14

d.

If the physical channel type is SCH, then the Extended Handoff

Direction Parameters Field Length shall be set to 0 and the
following fields shall be ignored in the Cell Information Record:
QOF_Mask, PWR_Comb_Ind, Pilot_PN, and Code_Chan.

15

The following table shows the bitmap layout for the A3-Connect message:
7

Message Type II = [01H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

-- Continued on next page --

480

10

TIA/EIA/IS-2001

1
-- Continued from previous page -

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

SDU ID:

A3/A7 Element Identifier = [4CH]

Length = [01H to 06H]

(MSB)

SDU ID = <any value>

(LSB)

A3 Connect Information{1+:

n
1

A3/A7 Element Identifier = [1BH]

Length = <variable>
Reserved = [000]

Physical Channel Type

= [0H - IS-95 Fundamental Channel,
1H Fundamental Channel (FCH),
2H Supplemental Channel (SCH)
3H Dedicated Control Channel
(DCCH)],

New A3
Indicator

= [0,1]
(exist,new)

Length of Cell Info Record = <variable>

Cell Identification Discriminator = [07H]

Cell Info Record {1+:

(MSB)

j+1
MSCID = <any value>

j+2
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)
Reserved = [000]

j+4

Sector = [0H-FH] (0H = Omni)

QoF Mask =
[00, 01, 10, 11]

New
Cell
Indicator

PWR_
Comb
_Ind

= [0,1]

= [0,1]

(old, new)

(no,yes)

Pilot_PN = <any value>

Code Channel = [00H - FFH]
} Cell Info Record
-- Continued on next page --

481

j+3
j+5

(MSB)

(LSB)

k+1
k+2

TIA/EIA/IS-2001

1
-- Continued from previous page -Length of Traffic Circuit ID = [05H]

Length of Traffic Circuit Identifier = [02H]

Traffic Circuit ID {1:

(MSB)

Traffic Circuit Identifier = <any value>

3
(LSB)

Length of Traffic Connection Identifier = [01H]

Traffic Connection Identifier = [00H-FFH]

(AAL2 CID)
} Traffic Circuit ID
Extended Handoff Direction Parameters Field Length = [09H]

Extended Handoff Direction Parameters {1+:

Search Window A Size (Srch_Win_A) =
[0H-FH]

Search Window N Size (Srch_Win_N) =

[0H-FH]

p+1

Search Window R Size (Srch_Win_R) =

[0H-FH]

Add Pilot Threshold (T_Add) high order

= [0H-FH]

p+2

T_Add (low order)

Drop Pilot Threshold (T_Drop) = [000000-111111]

p+3

= [00-11]
Compare Threshold (T_Comp)

Drop Timer Value (T_TDrop)

= [0H-FH]

= [0H-FH]

Neighbor Max Age (Nghbor_Max_AGE)

Reserved = [0000]

p+4
p+5

= [0H-FH]
Reserved = [00]

SOFT_SLOPE = [00 0000 - 11 1111]

p+6

Reserved = [00]

ADD_INTERCEPT = [00 0000 - 11 1111]

p+7

Reserved = [00]

DROP_INTERCEPT = [00 0000 - 11 1111]

p+8

Target BS P_REV = [00H FFH]

p+9

} Extended Handoff Direction Parameters

Length of Channel Element ID = <variable>
(MSB)

Channel Element ID = <any value>

q+1

(LSB)

(MSB)

-- Continued on next page --

482

TIA/EIA/IS-2001

1
-- Continued from previous page -Length of A3 Destination ID = [02H]
(MSB)

A3 Destination ID = <any value>

r+1
(LSB)

Length of A7 Destination ID = [02H]

(MSB)

A7 Destination ID = <any value>

s+1
(LSB)

}A3 Connect Information

483

r+2

s+2

TIA/EIA/IS-2001

6.1.9.2

A3-Connect Ack

2
3

This A3 channel message is sent from the source BS to the target BS to indicate the
result of processing the A3-Connect message.
Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

SDU -> BTS

Call Connection Reference

6.2.2.98

SDU -> BTS

Correlation ID

6.2.2.108

SDU -> BTS

Oa

A3 Connect Ack Information

6.2.2.145

SDU -> BTS

Ob

4
5

a.

If this element was included in the A3-Connect message, the

value shall be returned in this message.

6
7
8

b.

One instance of this element shall appear in this message for each
corresponding A3 Connect Information element in the A3Connect message that is being responded to.

The following table shows the bitmap layout for the A3-Connect Ack message:
7

Message Type II = [02H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

-- Continued on next page --

484

TIA/EIA/IS-2001

1
-- Continued from previous page -

A3 Connect Ack Information{1+:A3/A7 Element Identifier = [1CH]

Length = <variable>

Reserved = [00]

Soft Handoff Leg #

= [0000 to 1111]

2
PMC
Cause
Present
= [1]
(yes)

xmit
notify

(send A3TCH
Status)
= [0,1]
(no, yes)

Length of Traffic Circuit ID = [05H]

Length of Traffic Circuit Identifier = [02H]

Traffic Circuit ID {1:

(MSB)

Traffic Circuit Identifier = <any value>

6
(LSB)

Length of Traffic Connection Identifier = [01H]

Traffic Connection Identifier = [00H-FFH]

(AAL2 CID)
} Traffic Circuit ID
Length of Channel Element ID = <variable>
(MSB)

Channel Element ID = <any value>

j+1

(LSB)

k
k+1

PMC Cause =
[00H (No Error),
02H (already connected),
03H (illegal A3 Connect),
0AH (no resources available)]
Length of A3 Originating ID = [02H]
(MSB)

A3 Originating ID = <any value>

p+1
(LSB)

Length of A3 Destination ID = [02H]

(MSB)

A3 Destination ID = <any value>

q+1
(LSB)

}A3 Connect Ack Information

485

p+2

q+2

TIA/EIA/IS-2001

6.1.9.3

A3-Remove

2
3

This A3 message is sent from the target BS to the source BS to request that cells be
removed from the A3 connections identified in this message.
Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

BTS -> SDU

Call Connection Reference

6.2.2.98

BTS -> SDU

Correlation ID

6.2.2.108

BTS -> SDU

Oa

SDU ID

6.2.2.91

BTS -> SDU

Ob

A3 Remove Information

6.2.2.146

BTS -> SDU

Oc

4
5

a.

If this element is included in this message, the value shall be

returned in the A3-Remove Ack message.

6
7

b.

If this element was included in the A7-Handoff Request message,

it is required in this message.

8
9

c.

At least one instance of this element is required in this message.

Multiple instances of this element may be present in this message.

10
11

The following table shows the bitmap layout for the A3-Remove message:
7

Message Type II = [03H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

-- Continued on next page --

486

TIA/EIA/IS-2001

1
-- Continued from previous page -

SDU ID:

A3/A7 Element Identifier = [4CH]

Length = [01H to 06H]

(MSB)

SDU ID = <any value>

(LSB)

n
1

A3 Remove Information{1+: A3/A7 Element Identifier = [1EH]

Length = <variable>

Length of Traffic Circuit ID = [05H]

Length of Traffic Circuit Identifier = [02H]

Traffic Circuit ID {1:

(MSB)

Traffic Circuit Identifier = <any value>

5
(LSB)

Length of Traffic Connection Identifier = [01H]

Traffic Connection Identifier = [00H-FFH]

(AAL2 CID)
} Traffic Circuit ID
Number of Cells to be Removed = <variable>

Cell Identification Discriminator = [07H]

10

Cell Identifier {1+:

(MSB)

11
MSCID = <any value>

12
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

} Cell Identifier
-- Continued on next page --

487

13
14
15

TIA/EIA/IS-2001

1
-- Continued from previous page --

Length of A3 Destination ID = [02H]

(MSB)

A3 Destination ID = <any value>

q+1
(LSB)

Length of A7 Destination ID = [02H]

(MSB)

A7 Destination ID = <any value>

s+1
(LSB)

}A3 Remove Information

2

488

q+2

s+2

TIA/EIA/IS-2001

6.1.9.4

2
3

A3-Remove Ack
This A3 message is sent from the source BS to the target BS to acknowledge
completion of the request to remove cells from A3 connections.

Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

SDU -> BTS

Call Connection Reference

6.2.2.98

SDU -> BTS

Correlation ID

6.2.2.108

SDU -> BTS

Oa

A3 Destination ID

6.2.2.175

SDU -> BTS

Ob

4
5

a.

If this element was included in the A3-Remove message, the value

shall be returned in this message.

6
7
8
9
10

b.

If the A3 Originating ID field was included in the corresponding

A3 Connect Information element of an A3-Connect message that
established the traffic connection for these cells, then the A3
Destination ID element shall contain this information and be
included in this message.

489

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the A3-Remove Ack message:
7

Message Type II = [04H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

A3 Destination ID: A3/A7 Element Identifier = [55H]

A3 Destination ID = [02H]

(MSB)

A3 Destination ID = <any value>

3
(LSB)

490

TIA/EIA/IS-2001

6.1.9.5

A3-Drop

2
3

This optional A3 message is sent to notify a target base station (BS) that the A3 traffic
subchannel is about to be dropped.
Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

SDU -> BTS

Call Connection Reference

6.2.2.98

SDU -> BTS

A3 Drop Information

6.2.2.147

SDU -> BTS

Oa

Cause List

6.2.2.142

SDU -> BTS

Ob

4
5

a.

One instance of this element shall appear in this message for each
A3 connection that is being dropped by the SDU function.

6
7
8
9

b.

The items in this list shall be in the same order and shall be in one
to one correspondence with the occurrences of the A3 Drop
Information element. Each entry indicates the reason for dropping
the associated A3 connection.

10
11

Allowable cause values are: OAM&P intervention; Invalid Call;

Equipment failure.

12

The following table shows the bitmap layout for the A3-Drop message:
7

Message Type II = [05H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

-- Continued on next page --

491

10

TIA/EIA/IS-2001

1
-- Continued from previous page -

A3 Drop Information:

A3/A7 Element Identifier = [1EH]

Length = <variable>

Length of Traffic Circuit ID = [05H]

Length of Traffic Circuit Identifier = [02H]

Traffic Circuit ID {1:

(MSB)

Traffic Circuit Identifier = <any value>

5
(LSB)

Length of Traffic Connection Identifier = [01H]

Traffic Connection Identifier = [00H-FFH]

(AAL2 CID)
} Traffic Circuit ID
Length of Channel Element ID = <variable>
(MSB)

Channel Element ID = <any value>

10

(LSB)

Length of A3 Destination ID = [02H]

(MSB)

p+3

A3 Destination ID = <any value>

p+4
(LSB)

Cause List:

A3/A7 Element Identifier = [19H]

Length = <variable>

p+5
1
2

Cause Value {1+:

Reserved
= [0]

Cause Value =
[07H (OAM&P intervention),
12H (invalid call),
20H(equipment failure)]

} Cause Value
2

492

TIA/EIA/IS-2001

6.1.9.6

2
3
4

A3-Propagation Delay Measurement Report

This A3 message is sent from the target BS to the source BS immediately following
the acquisition of the mobile and subsequently whenever the delay changes by two or
more PN chips.

Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

BTS -> SDU

Call Connection Reference

6.2.2.98

BTS -> SDU

One way Propagation Delay Record

6.2.2.119

BTS -> SDU

SDU ID

6.2.2.91

BTS -> SDU

Oa

A3 Destination ID

6.2.2.175

BTS -> SDU

Ob

A7 Destination ID

6.2.2.173

BTS -> SDU

Oc

5
6
7

a.

If this element was included in the A7-Handoff Request message,

it is required in this message.

8
9
10
11
12

b.

If the A3 Originating ID field was included in the corresponding

A3 Connect Ack Information element of an A3-Connect Ack
message that established the traffic connection for the cell, then
the A3 Destination ID element shall contain this information and
be included in this message.

13
14
15
16
17

c.

If the A7 Originating ID element was included in the

corresponding A7-Handoff Request message, and the A3 Flag
field was set to '1', then the A7 Destination ID element shall be
included in this message and contain the value of the A7
Originating ID.

18

493

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the A3-Propagation Delay
Measurement Report message:
7

Message Type II = [06H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

One Way Propagation Delay Record:

A3/A7 Element Identifier = [09H]

10
1

Length = [06H]

Cell Identification Discriminator = [07H]

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

(MSB)

j+3

Sector = [0H-FH] (0H = Omni)

CDMA Serving One Way Delay = [0000H-FFFFH] (x100ns)

SDU ID:

SDU ID = <any value>

(LSB)

A3 Destination ID = <any value>

3
(LSB)

A7 Destination ID: A3/A7 Element Identifier = [2DH]

494

A3 Destination ID: A3/A7 Element Identifier = [55H]

Length of A3 Destination ID = [02H]

(MSB)

k+1
1

A3/A7 Element Identifier = [4CH]

Length = [01H to 06H]

(MSB)

j+4
k

(LSB)

j+2

4
1

TIA/EIA/IS-2001

Length of A7 Destination ID = [02H]

(MSB)

A7 Destination ID = <any value>

3
(LSB)

1
2

A3-IS-95 FCH Forward

6.1.9.7

3
4
5
6
7

This A3 message is sent from the source BS to the target BS over A3 IS-95 user traffic
subchannels of type IS-95 FCH (TIA/EIA/IS-95 Fundamental Channel). It is used to
send a Forward Traffic Channel frame to the target BS for transmission to the MS.
This message includes the entire Forward Traffic Channel frame and some control
information.

8
9

Note: This is the same as A3-CEData Forward message in previous revisionsof this
standard.
Information Element

Section
Reference

Message Type II

Element
Direction

Type

6.2.2.5

SDU -> BTS

Forward Layer 3 Data

6.2.2.120

SDU -> BTS

Message CRC

6.2.2.134

SDU -> BTS

10
11

The following table shows the bitmap layout for the A3-IS-95 FCH Forward message:
7

Octet
1

Message Type II = [07H]

Forward Layer 3 Data {1:

Reserved = [0000]

(MSB)

Sequence Number = [0000-1111]

Forward Traffic Channel Gain = [00H-80H]

Reverse Traffic Channel Ew/Nt = [00H-0FFH]

Rate Set Indicator = [0H,1H]

Forward Traffic Channel Rate = [0H-3H]

Reserved = [0000]

Power Control Subchannel Count = [1H-6H]

Forward Traffic Channel Information + Layer 3 Fill = <any value>

(LSB)

} Forward Layer 3 Data

(MSB)

Message CRC = [0000H-FFFFH]

(LSB)

12

495

m+1

TIA/EIA/IS-2001

A3-IS-95 FCH Reverse

6.1.9.8

2
3
4
5

This A3 message is sent from the target BS to the source BS over A3 user traffic
subchannels of type IS-95 FCH (TIA/EIA/IS-95 Fundamental Channel). It is used
by the target BS to send a decoded Reverse Traffic Channel Frame and control
information.

6
7

Note: This is the same as A3-CEData Reverse message in previous revisions of this
standard.
Information Element

Section
Reference

Message Type II

Element
Direction

Type

6.2.2.5

BTS -> SDU

Reverse Layer 3 Data

6.2.2.121

BTS -> SDU

Message CRC

6.2.2.134

BTS -> SDU

8
9

The following table shows the bitmap layout for the A3-FCH Reverse message:
7

Octet
1

Message Type II = [08H]

Reverse Layer 3 Data {1:

Sequence Number = [0000-1111]

Soft Handoff Leg #

= [0000 - 1111]
Reverse Traffic Channel Quality = [00H-FFH]
Scaling = [00-11]

Packet Arrival Time Error = [000000-111111]

Rate Set Indicator = [0H,1H]

Reverse Traffic Channel Rate = [0H-6H]

EIB =
[0,1]

Reserved = [0000]
(MSB)

Reverse Traffic Channel Information + Layer 3 Fill = <any value>

(LSB)

}Reverse Layer 3 Data

(MSB)

Message CRC = [0000H-FFFFH]

(LSB)

10

496

m+1

TIA/EIA/IS-2001

A3-IS-2000 FCH Forward

6.1.9.9

2
3
4
5
6
7

This A3 message is sent from the source BS to the target BS over A3 IS-2000 user
traffic subchannel of type IS-2000 FCH (TIA/EIA/IS-2000 Fundamental Channel).
It is used to send a Forward Link air-frame to the target BS for transmission to the
MS. This message includes the entire Forward Link air-frame data and some control
information. FCH Forward messages are not to be suppressed due to streaming gainsettings required for EIB-based power control.
Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

SDU -> BTS

Forward Layer 3 IS-2000 FCH/DCCH Data

6.2.2.74

SDU -> BTS

Message CRC

6.2.2.134

SDU -> BTS

8
9

The following table shows the bitmap layout for the A3-IS-2000 FCH Forward messages:
7

Octet
1

Message Type II = [0BH]

Forward Layer 3 IS-2000 FCH/DCCH Data {1:

FPC: SLC = [ 0001 to 0110 ]

FSN = [ 0000 to 1111 ]

FPC: GR = [00H - FFH ]

RPC: OLT = [00H - FFH ]

IS-2000 Frame Content = [00H-08H, 0AH-12H ]

(MSB)

5
Forward Link Information = <variable>

(LSB)

} Forward Layer 3 IS-2000 FCH/DCCH Data

(MSB)

Message CRC = [0000H-FFFFH]

(LSB)

10

497

TIA/EIA/IS-2001

A3-IS-2000 FCH Reverse

6.1.9.10

2
3
4
5
6

This A3 message is sent from the target BS to the source BS over A3 IS-2000 user
traffic subchannel of type IS-2000 FCH (TIA/EIA/IS-2000 Fundamental Channel). It
is used by the target BS to send a decoded Reverse Link air-frame and control
information to the source BS. IS-2000 FCH Reverse messages are not be suppressed
due to streaming feedback required for EIB-based power control.
Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

SDU <- BTS

Reverse Layer 3 IS-2000 FCH/DCCH Data

6.2.2.75

SDU <- BTS

Message CRC

6.2.2.134

SDU <- BTS

7
8

The following table shows the bitmap layout for the A3-IS-2000 FCH Reverse message:
7

Octet
1

Message Type II = [0CH]

Reverse Layer 3 IS-2000 FCH/DCCH Data {1:

Soft Handoff Leg #
= [0000 - 1111]

FSN = [ 0000 to 1111 ]

FQI
= [0,1]

Reverse Link Quality

= [000 0000 111 1111 ]

Scaling
= [ 00 11 ]

Packet Arrival Time Error

= [00 0000 11 1111 ]

IS-2000 Frame Content = [00H-08H, 0AH-12H, 7DH, 7EH ]

FPC: S = [0000 000 1111 111 ]

4
EIB
= [0,1]

(MSB)

5
6

Reverse Link Information = <variable>

(LSB)

}Reverse Layer 3 IS-2000 FCH/DCCH Data

(MSB)

Message CRC = [0000H-FFFFH]

(LSB)

9
10

498

TIA/EIA/IS-2001

6.1.9.11

2
3
4

A3-Physical Transition Directive

This A3 message is sent from the source BS to the target BS over the A3 interface. It
conveys a change to an allocated physical channel at the target BS as well as the time
of execution for the change.

Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

SDU -> BTS

Call Connection Reference

6.2.2.98

SDU -> BTS

CDMA Long Code Transition Info

6.2.2.128

SDU -> BTS

Oc

Channel Element ID

6.2.2.132

SDU -> BTS

Oa

Privacy Info

6.2.2.143

SDU -> BTS

Oh

A3 Traffic Circuit ID

6.2.2.96

SDU -> BTS

Ob

Reverse Pilot Gating Rate

6.2.2.33

SDU -> BTS

Od

IS-2000 Forward Power Control Mode

6.2.2.177

SDU -> BTS

Oe

IS-2000 Mobile Pilot Gain

6.2.2.180

SDU -> BTS

Of

A3 Destination ID

6.2.2.175

SDU -> BTS

Og

5
6

a.

If this element was included in the A3-Connect message, its value

shall be included in this element.

7
8
9

b.

This element shall be included when the Channel Element ID

element is not used in this message. It shall not be included when
the Channel Element ID element is included.

10
11
12
13
14

c.

This element shall be included when the purpose of this message

is to cause a change to the long code key in use for encrypting the
physical channel. If the Privacy Info element is not present, then
the Private Long Code Mask value most recently received in A7Handoff Request shall apply.

15
16
17

d.

This element shall be included when the purpose of this message

is to cause a change in the pilot gating rate of the physical
channel.

18
19
20
21

e.

This element shall be included when the purpose of this message

is to cause a change in the forward power control mode. This
message shall be sent once for each A3 traffic connection for the
same mobile station.

22
23
24
25

f.

One or more instances of this element shall be included when the

purpose of this message is to cause a change in the Mobile Pilot
Gain. This element only applies to the physical channel measured
for reverse power control (either FCH or DCCH).

26
27
28

g.

If the A3 Originating ID field was included in the corresponding

A3 Connect Information element of an A3-Connect message that
established the traffic connection, then the A3 Destination ID

499

TIA/EIA/IS-2001

1
2

element shall contain this information and be included in this

message.

3
4

h.

5
6

This element shall be included when the source BS wishes to

inform the target BS of a new Private Long Code Mask value.

The following table shows the bitmap layout for the A3-Physical Transition Directive
message:
7

Message Type II = [09H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

CDMA Long Code Transition Info:

A3/A7 Element Identifier = [0EH]

Length = [02H]

10
1
2

LCM_TYP
E = [0,1]

Reserved = [0000000]

(public,
private)
ACTION_TIME = [00H-FFH]

Channel Element ID:

4
1

A3/A7 Element Identifier = [17H]

Length = <variable>
(MSB)

Channel Element ID = <any value>

(LSB)

Reserved =
[0]

Privacy Info: A3/A7 Element Identifer = [1AH]

Length = <variable>

Privacy Mask Type = [00010] (private)

Status
= [0,1]

Available
= [0,1]

Privacy Mask Length = [06H]

(MSB)

3
4

Privacy Mask = <any value>

(LSB)

-- Continued on next page --

500

10

TIA/EIA/IS-2001

1
-- Continued from previous page -

Traffic Circuit ID:

(MSB)

A3/A7 Element Identifier = [03H]

Length = [05H]

Length of Traffic Circuit Identifier = [02H]

Traffic Circuit Identifier = <any value>

(LSB)

Length of Traffic Connection Identifier = [01H]

Traffic Connection Identifier = [00H-FFH]

(AAL2 CID)

Reverse Pilot Gating Rate:

A3/A7 Element Identifier = [06H]

Length = [02H]

Reserved = [0000 00]

Pilot Gating Rate

= [00, 01, 10]

ACTION_TIME = [00H FFH]

IS-2000 Forward Power Control Mode:

A3/A7 Element Identifier = [14H]

Length = [02H]
Reserved = [0000 0]

FPC_MODE = [000 011]

IS-2000 Mobile Pilot Gain:

3
4
1

A3/A7 Element Identifier = [01H]

Length = [02H]

Mobile Pilot Gain = [00H FFH]

ACTION_TIME = [00H FFH]

A3 Destination ID: A3/A7 Element Identifier = [55H]

Length of A3 Destination ID = [02H]

(MSB)

1
2

ACTION_TIME = [00H FFH]

A3 Destination ID = <any value>

3
(LSB)

501

TIA/EIA/IS-2001

6.1.9.12

2
3

A3-PhysicalTransition Directive Ack

This A3 message is sent from the target BS to the source BS over the A3 signaling
interface to convey the outcome of processing A3-Physical Transition Directive.

Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

BTS -> SDU

Call Connection Reference

6.2.2.98

BTS -> SDU

Cell Information Record (Committed)

6.2.2.89

BTS -> SDU

Od

SDU ID

6.2.2.91

BTS -> SDU

Oa

PMC Cause

6.2.2.99

BTS -> SDU

Ob

Cell Information Record (Uncommitted)

6.2.2.89

BTS -> SDU

Oc,d

A3 Destination ID

6.2.2.175

BTS -> SDU

Oe

A7 Destination ID

6.2.2.173

BTS -> SDU

Of

4
5
6

a.

If this element was included in the A7-Handoff Request message,

it is required in this message.

7
8
9

b.

Allowable PMC Cause values are: Private long code not available
or not supported, Requested Reverse Pilot Gating Rate not
supported.

10
11

c.

This element shall be included when the PMC Cause element is

present.

12
13
14

d.

The New Cell Indicator field of this element shall be set to zero in
this message, since no new cells are being added to an A3 traffic
connection by this operation.

15
16
17
18
19

e.

If the A3 Originating ID field was included in the corresponding

A3 Connect Ack Information element of an A3-Connect Ack
message that established the traffic connection for these cells, then
the A3 Destination ID element shall contain this information and
be included in this message.

20
21
22
23
24

f.

If the A7 Originating ID element was included in the

corresponding A7-Handoff Request message, and the A3 Flag
field was set to '1', then the A7 Destination ID element shall be
included in this message and contain the value of the A7
Originating ID.

25

502

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the A3-Physical Transition Directive
Ack message:
7

Message Type II = [0AH]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

Cell Information Record (Committed):

A3/A7 Element Identifier = [02H]

10
1

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Information {1+:

(MSB)

j+1
MSCID = <any value>

(MSB)

(LSB)

Cell = [001H-FFFH]
(LSB)
Reserved = [000]

j+3

Sector = [0H-FH] (0H = Omni)

QOF_Mask =
[00, 01, 10, 11]

j+2

New
Cell
Indicator

PWR_
Comb
_Ind

= [0,1]

= [0,1]

(old, new)

(no,yes)

Pilot_PN = <any value>

j+4

(MSB)

(LSB)

k+1

Code Channel = [00H FFH]

k+2

} Cell Information

SDU ID:

A3/A7 Element Identifier = [4CH]

Length = [01H to 06H]

(MSB)

SDU ID = <any value>

(LSB)

-- Continued on next page --

503

TIA/EIA/IS-2001

1
-- Continued from previous page -

PMC Cause:

A3/A7 Element Identifier = [05H]

Length = [01H]

PMC Cause Value =

[05H (Requested Reverse Pilot Gating Rate not supported),

0DH (Private long code not available or not supported),
0FH (Requested privacy configuration unavailable) ]

Cell Information Record (Uncommitted): A3/A7 Element Identifier = [02H]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Information {1+:

(MSB)

j+1
MSCID = <any value>

(MSB)

(LSB)

Cell = [001H-FFFH]
(LSB)
Reserved = [000]

j+3

Sector = [0H-FH] (0H = Omni)

QOF_Mask =
[00, 01, 10, 11]

j+2

New
Cell
Indicator

PWR_
Comb
_Ind

= [0]

= [0,1]

(old)

(no,yes)

Pilot_PN = <any value>

j+4

(MSB)

(LSB)

k+1

Code Channel = [00H FFH]

k+2

} Cell Information

A3 Destination ID: A3/A7 Element Identifier = [55H]

Length of A3 Destination ID = [02H]

(MSB)

A3 Destination ID = <any value>

3
(LSB)

A7 Destination ID: A3/A7 Element Identifier = [2DH]

Length of A7 Destination ID = [02H]

(MSB)

A7 Destination ID = <any value>

3
(LSB)

504

TIA/EIA/IS-2001

A3-IS-2000 DCCH Forward

6.1.9.13

2
3
4
5
6
7

These A3 messages are sent from the source BS to the target BS over A3 IS-2000 user
traffic subchannels of type IS-2000 DCCH (TIA/EIA/IS-2000 Dedicated Control
Channel).They are used to send a Forward Link air-frame to the target BS for
transmission to the MS. These messages include the entire Forward Link air-frame
data and some control information. IS-2000 DCCH Forward messages are not be
suppressed due to streaming gain-settings required for EIB-based power control.
Information Element

8
9

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

SDU -> BTS

Forward Layer 3 IS-2000 FCH/DCCH Data

6.2.2.74

SDU -> BTS

Message CRC

6.2.2.134

SDU -> BTS

The following table shows the bitmap layout for the A3-IS-2000 DCCH Forward messages:
7

Octet
1

Message Type II = [0EH]

Forward Layer 3 IS-2000 FCH/DCCH Data {1:

FPC: SLC = [ 0001 to 0110 ]

FSN = [ 0000 to 1111 ]

FPC: GR = [00H - FFH ]

RPC: OLT = [00H - FFH ]

IS-2000 Frame Content = [00H, 20H, 21H, 7FH ]

(MSB)

5
Forward Link Information = <variable>

(LSB)

} Forward Layer 3 IS-2000 FCH/DCCH Data

(MSB)

Message CRC = [0000H-FFFFH]

(LSB)

10

505

TIA/EIA/IS-2001

A3-IS-2000 DCCH Reverse

6.1.9.14

2
3
4
5
6

This A3 message is sent from the target BS to the source BS over A3 IS-2000 user
traffic subchannel of type IS-2000 DCCH (TIA/EIA/IS-2000 Dedicated Control
Channel). It is used by the target BS to send a decoded Reverse Link air-frame and
control information to the source BS. IS-2000 DCCH Reverse messages are not be
suppressed due to streaming feedback required for EIB-based power control.
Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

SDU <- BTS

Reverse Layer 3 IS-2000 FCH/DCCH Data

6.2.2.75

SDU <- BTS

Message CRC

6.2.2.134

SDU <- BTS

7
8

The following table shows the bitmap layout for the A3-IS-2000 DCCH Reverse message:
7

Octet
1

Message Type II = [0FH]

Reverse Layer 3 IS-2000 FCH/DCCH Data {1:

Soft Handoff Leg #
= [0000 - 1111]

FSN = [ 0000 to 1111 ]

FQI
= [0,1]

Reverse Link Quality

= [ 000 0000 111 1111 ]

Scaling
= [ 00 11 ]

Packet Arrival Time Error

= [00 0000 11 1111]

IS-2000 Frame Content = [00H, 20H, 21H, 7EH, 7FH ]

FPC: S = [0000 000 1111 111 ]

4
EIB
= [0,1]

(MSB)

5
6

Reverse Link Information = <variable>

(LSB)

}Reverse Layer 3 IS-2000 FCH/DCCH Data

(MSB)

Message CRC = [0000H-FFFFH]

(LSB)

506

TIA/EIA/IS-2001

6.1.9.15

2
3

A3-Traffic Channel Status

This A3 message is sent from the target BS to the source BS to provide status
information with respect to one or more cells on an A3 connection.

Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

BTS -> SDU

Call Connection Reference

6.2.2.98

BTS -> SDU

Cell Identifier List

6.2.2.21

BTS -> SDU

Channel Element Status

6.2.2.141

BTS -> SDU

SDU ID

6.2.2.91

BTS -> SDU

Oa

A3 Destination ID

6.2.2.175

BTS -> SDU

Ob

A7 Destination ID

6.2.2.173

BTS -> SDU

Oc

4
5
6

a.

If this element was included in the A7-Handoff Request message,

it is required in this message.

7
8
9
10
11

b.

If the A3 Originating ID field was included in the corresponding

A3 Connect Ack Information element of an A3-Connect Ack
message that established the traffic connection for these cells, then
the A3 Destination ID element shall contain this information and
be included in this message.

12
13
14
15
16

c.

If the A7 Originating ID element was included in the

corresponding A7-Handoff Request message, and the A3 Flag
field was set to '1', then the A7 Destination ID element shall be
included in this message and contain the value of the A7
Originating ID.

507

TIA/EIA/IS-2001

1
2
3

The following table shows the bitmap layout for the A3-Traffic Channel Status
message:
7

Message Type II = [0DH]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

Cell Identifier List:

10
1

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification

Channel Element Status:

A3/A7 Element Identifier = [18H]

Length = [01H]
Reserved = [0000000]

2
Xmit On
= [0,1]

(Off, On)

SDU ID:

A3/A7 Element Identifier = [4CH]

Length = [01H to 06H]

(MSB)

SDU ID = <any value>

(LSB)

508

TIA/EIA/IS-2001

1
-- Continued from previous page -

A3 Destination ID: A3/A7 Element Identifier = [55H]

Length of A3 Destination ID = [02H]

(MSB)

A3 Destination ID = <any value>

3
(LSB)

A7 Destination ID: A3/A7 Element Identifier = [2DH]

Length of A7 Destination ID = [02H]

(MSB)

A7 Destination ID = <any value>

3
(LSB)

509

TIA/EIA/IS-2001

A3-IS-2000 SCH Forward

6.1.9.16

2
3
4
5
6

This A3 message is sent from the source BS to the target BS over A3 IS-2000 user
traffic subchannels of type IS-2000 SCH (TIA/EIA/IS-2000 Supplemental Channel).
It is used to send a Forward Link air-frame to the target BS for transmission to the
MS. This message includes the entire Forward Link air-frame and some control
information.
Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

SDU -> BTS

Forward Layer 3 IS-2000 SCH Data

6.2.2.77

SDU -> BTS

Message CRC

6.2.2.134

SDU -> BTS

7
8

The following table shows the bitmap layout for the A3-IS-2000 SCH Forward message:
7

Octet
1

Message Type II = [10H]

Forward Layer 3 IS-2000 SCH Data {1:

FPC: SLC = [ 0001 to 0110 ]

FSN = [ 0000 to 1111 ]

FPC: GR = [ 00H FFH ]

IS-2000 Frame Content = [00H, 32H-39H, 3DH-43H, 7FH]

(MSB)

4
Forward Link Information = <variable>

(LSB)

} Forward Layer 3 IS-2000 SCH Data

(MSB)

Message CRC = [0000H-FFFFH]

(LSB)

510

TIA/EIA/IS-2001

A3-IS-2000 SCH Reverse

6.1.9.17

2
3
4
5
6

This A3 message is sent from the target BS to the source BS over A3 IS-2000 user
traffic subchannels of type IS-2000 SCH (TIA/EIA/IS-2000 Supplemental Channel).
It is used by the target BS to send a decoded Reverse Link air-frame and control
information. The target BS may use the A3-IS-2000 SCH Reverse Message to send
Idle frames to the source BS for the purpose of synchronization of the A3 link.
Information Element

Section
Reference

Element
Direction

Type

Message Type II

6.2.2.5

BTS -> SDU

Reverse Layer 3 IS-2000 SCH Data

6.2.2.78

BTS -> SDU

Message CRC

6.2.2.134

BTS -> SDU

7
8

The following table shows the bitmap layout for the A3-IS-2000 SCH Reverse message:
7

Octet
1

Message Type II = [11H]

Reverse Layer 3 IS-2000 SCH Data {1:

Soft Handoff Leg #
= [0000 - 1111]

FSN = [ 0000 to 1111 ]

FQI
= [0,1]

Reverse Link Quality

= [ 000 0000 111 1111 ]

Scaling
= [ 00 11 ]

Packet Arrival Time Error

= [ 00 0000 11 1111 ]

IS-2000 Frame Content = [00H, 32H 39H, 3DH 43H, 7EH, 7FH ]

(MSB)

5
Reverse Link Information = <variable>

(LSB)

}Reverse Layer 3 IS-2000 SCH Data

(MSB)

Message CRC = [0000H-FFFFH]

(LSB)

511

TIA/EIA/IS-2001

6.1.10

A9 Interface Message Formats

6.1.10.1

A9-Setup-A8

2
3
4
5

This A9 interface message is sent from the BS to the PCF to request the establishment
of an A8 connection.
Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

BS -> PCF

Call Connection Reference

6.2.2.98

BS -> PCF

Correlation ID

6.2.2.108

BS -> PCF

Oa

Mobile Identity (IMSI)

6.2.2.16

BS -> PCF

Mobile Identity (ESN)

6.2.2.16

BS -> PCF

Ob

CON_REF

6.2.2.168

BS -> PCF

Quality of Service Parameters

6.2.2.54

BS -> PCF

Oc

A9 BSC_ID

6.2.2.169

BS -> PCF

A8_Traffic_ID

6.2.2.170

BS -> PCF

Service Option

6.2.2.66

BS -> PCF

A9 Indicators

6.2.2.171

BS -> PCF

User Zone ID

6.2.2.32

BS -> PCF

6
7
8

a.

If this element is included in this message, its value shall be

returned in the corresponding element in the A9-Connect A8
message sent in response to this message.

9
10
11

b.

This second occurrence of the Mobile Identity element, if

included, shall contain the ESN of the MS. Use of the ESN in
this message is a network operator decision.

12
13

c.

This information element is included if information is available at

the BS.

512

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A9-Setup-A8 message:
7

A9 Message Type = [01H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

-- Continued on next page --

513

TIA/EIA/IS-2001

1
-- Continued from previous page -

CON_REF:

A9 Element Identifier = [01H]

Length = [01H]

IS-2000 CON_REF = [00H FFH]

Quality of Service Parameters:

A9 Element Identifier = [07H]

Length = [01H]
Reserved = [0000]

2
Packet Priority = [0000 1101]

A9 BSC_ID:

A9 Element Identifier = [06H]

Length = [01H 06H]

(MSB)

BSC Identifier = <any value>

(LSB)

(MSB)

M
1

A8 Traffic ID: A9 Element Identifier = [08H]

Length = [0CH]

A8 transport protocol stack = [01H] (GRE/IP)

Protocol Type = [88 0BH] (PPP)

4
(LSB)

(MSB)

5
6

Key = <any value>

7
8
(LSB)

Address Type = [01H] (IPv4)

9
10

(MSB)

11
IP Address = <any value>

12
13
(LSB)

(MSB)

Service Option: A1 Element Identifier = [03H]

Service Option

= [ 00 21H (High Speed Packet Data, 144 kbps) ]

(LSB)

Length = [01H]

2
Data
Ready
Indicator
= [0,1]

-- Continued on next page --

514

3
1

A9 Indicators: A9 Element Identifier = [05H]

Reserved = [0000 000]

14

Handoff
indicator
= [0, 1]

TIA/EIA/IS-2001

1
-- Continued from previous page -

User Zone ID:

A1 Element Identifier = [02H]

Length = [02H]
(MSB)

UZID = <any value>

3
(LSB)

515

TIA/EIA/IS-2001

1
2

6.1.10.2

3
4

A9-Connect-A8
This A9 interface message is sent from the PCF to the BS to complete the setup of the
A8 connection.

Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

PCF -> BS

Call Connection Reference

6.2.2.98

PCF -> BS

Correlation ID

6.2.2.108

PCF -> BS

Oa

Mobile Identity (IMSI)

6.2.2.16

PCF -> BS

Mobile Identity (ESN)

6.2.2.16

PCF -> BS

Ob

CON_REF

6.2.2.168

PCF -> BS

A8_Traffic_ID

6.2.2.170

PCF -> BS

Cause

6.2.2.19

PCF -> BS

Oc

PDSN IP Address

6.2.2.30

PCF -> BS

5
6
7

a.

This element shall only be included if it was also included in the

A9-Setup-A8 message. This element shall be set to the value
received in that message.

8
9
10

b.

This second occurrence of the Mobile Identity element, if

included, shall contain the ESN of the MS. Use of the ESN in
this message is a network operator decision.

11
12
13

c.

Allowable cause values are: PCF resources not available;

Equipment failure; Successful operation, PDSN resources
are not available, Data ready to send.

516

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A9-Connect-A8 message:
7

A9 Message Type = [02H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

-- Continued on next page --

517

TIA/EIA/IS-2001

1
-- Continued from previous page -

CON_REF:

A9 Element Identifier = [01H]

Length = [01H]

IS-2000 CON_REF = [00H FFH]

3
1

A8 Traffic ID: A9 Element Identifier = [08H]

Length = [0CH]

A8 transport protocol stack = [01H] (GRE/IP)

Protocol Type = [88 0BH] (PPP)

(MSB)

(LSB)
(MSB)

5
6

Key = <any value>

7
8
(LSB)

Address Type = [01H] (IPv4)

9
10

(MSB)

11
IP Address = <any value>

12
13
(LSB)

Cause: A9 Element Identifier = [04H]

Length = [01H]

ext = [0]

14

2
3

Cause Value =
[13H (Successful operation),
20H (Equipment failure),
32H (PCF resources not available),
79H (PDSN resources are not available),
7AH (Data Ready to Send) ]

PDSN IP Address: A1 Element Identifier = [14H]

Length = [04H]

(MSB)

3
PDSN IP Address = <any value>

4
5
(LSB)

518

TIA/EIA/IS-2001

6.1.10.3

2
3

A9-Disconnect-A8
This A9 interface message is sent from the PCF to the BS to release the associated
dedicated resource.

Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

PCF -> BS

Call Connection Reference

6.2.2.98

PCF -> BS

Correlation ID

6.2.2.108

PCF -> BS

Oa

Mobile Identity (IMSI)

6.2.2.16

PCF -> BS

Mobile Identity (ESN)

6.2.2.16

PCF -> BS

Ob

CON_REF

6.2.2.168

PCF -> BS

A8_Traffic_ID

6.2.2.170

PCF -> BS

Cause

6.2.2.19

PCF -> BS

Oc

4
5
6

a.

If this element is included in this message, its value shall be

returned in the corresponding element in the A9-Release-A8
message sent in response to this message.

7
8
9

b.

This second occurrence of the Mobile Identity element, if

included, shall contain the ESN of the MS. Use of the ESN in
this message is a network operator decision.

10
11

c.

Allowable cause values are: Packet call going dormant;

Equipment failure; Normal call release.

519

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A9-Disconnect-A8 message:
7

A9 Message Type = [03H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

-- Continued on next page --

520

TIA/EIA/IS-2001

1
-- Continued from previous page -

CON_REF:

A9 Element Identifier = [01H]

Length = [01H]

IS-2000 CON_REF = [00H FFH]

3
1

A8 Traffic ID: A9 Element Identifier = [08H]

Length = [0CH]

A8 transport protocol stack = [01H] (GRE/IP)

Protocol Type = [88 0BH] (PPP)

(MSB)

(LSB)
(MSB)

5
6

Key = <any value>

7
8
(LSB)

Address Type = [01H] (IPv4)

9
10

(MSB)

11
IP Address = <any value>

12
13
(LSB)

Cause: A9 Element Identifier = [04H]

Length = [01H]

ext = [0]

Cause Value =
[10H (Packet call going dormant),
14H (Normal call release),
20H (Equipment failure) ]

521

14
1
2
3

TIA/EIA/IS-2001

6.1.10.4

2
3

A9-Release-A8
This A9 interface message is sent from the BS to the PCF to release the associated
dedicated resource

Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

BS-> PCF

Call Connection Reference

6.2.2.98

BS-> PCF

Correlation ID

6.2.2.108

BS-> PCF

Oa

Mobile Identity (IMSI)

6.2.2.16

BS-> PCF

Mobile Identity (ESN)

6.2.2.16

BS-> PCF

Ob

CON_REF

6.2.2.168

BS-> PCF

A8_Traffic_ID

6.2.2.170

BS-> PCF

Cause

6.2.2.19

BS-> PCF

Oc

4
5
6
7

a.

This element shall be included if it was also included in the A9Disconnect-A8 message. This element shall be set to the value
received in that message. If this element was not included in that
message, it may be included in this message.

8
9
10

b.

This second occurrence of the Mobile Identity element, if

included, shall contain the ESN of the MS. Use of the ESN in
this message is a network operator decision.

11
12
13
14

d.

Allowable cause values are: Packet call going dormant;

Equipment failure; Normal call release. Note that Normal
Call Release indicates that the service has been released and
therefore the A10 resources should be dropped.

522

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A9-Release-A8 message:
7

A9 Message Type = [04H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

-- Continued on next page --

523

TIA/EIA/IS-2001

1
-- Continued from previous page -

CON_REF:

A9 Element Identifier = [01H]

Length = [01H]

IS-2000 CON_REF = [00H FFH]

3
1

A8 Traffic ID: A9 Element Identifier = [08H]

Length = [0CH]

A8 transport protocol stack = [01H] (GRE/IP)

Protocol Type = [88 0BH] (PPP)

(MSB)

(LSB)
(MSB)

5
6

Key = <any value>

7
8
(LSB)

Address Type = [01H] (IPv4)

9
10

(MSB)

11
IP Address = <any value>

12
13
(LSB)

Cause: A9 Element Identifier = [04H]

Length = [01H]

ext = [0]

Cause Value =
[10H (Packet call going dormant),
14H (Normal call release),
20H (Equipment failure) ]

524

14
1
2
3

TIA/EIA/IS-2001

6.1.10.5

A9-Release-A8 Complete

2
3

This A9 interface message is sent from the PCF to the BS to acknowledge completion
of the request to release the connection.
Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

PCF -> BS

Call Connection Reference

6.2.2.98

PCF -> BS

Correlation ID

6.2.2.108

PCF -> BS

Oa

4
5
6

a.

7
8

This element shall only be included if it was also included in the

A9-Release-A8 message. This element shall be set to the value
received in that message.

The following table shows the bitmap layout for the A9-Release-A8 Complete
message:
7

A9 Message Type = [05H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

525

TIA/EIA/IS-2001

6.1.10.6

A9-BS Service Request

2
3

This A9 interface message is sent from the PCF to the BS to request re-activation of a
packet data service in Dormant state.
Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

PCF -> BS

Correlation ID

6.2.2.108

PCF -> BS

Oa

Mobile Identity (IMSI)

6.2.2.16

PCF -> BS

Mobile Identity (ESN)

6.2.2.16

PCF -> BS

Ob

Service Option

6.2.2.66

PCF -> BS

Data Count

6.2.2.179

PCF -> BS

4
5
6

a.

If this element is included in this message, its value shall be

returned in the corresponding element in the A9-BS Service
Response message sent in response to this message.

7
8
9

b.

This second occurrence of the Mobile Identity element, if

included, shall contain the ESN of the MS. Use of the ESN in
this message is a network operator decision.

10

The following table shows the bitmap layout for the A9-BS Service Request message:
7

Octet

A9 Message Type = [06H]

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Mobile Identity (IMSI): Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

Type of Identity

6
1
2

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

-- Continued on next page --

526

TIA/EIA/IS-2001

1
-- Continued from previous page -

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

2
Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Service Option: A1 Element Identifier = [03H]

(MSB)

Service Option
= [00 21H (High Speed Packet Data, 144 kbps)]

Data Count:

A3/A7 Element Identifier = [09H]

Count = [00H-FFH]

527

2
(LSB)

3
1
2

TIA/EIA/IS-2001

6.1.10.7

2
3

A9-BS Service Response

This A9 interface message is sent from the BS to the PCF to acknowledge the call
setup.

Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

BS -> PCF

Correlation ID

6.2.2.108

BS -> PCF

Oa

Cause

6.2.2.19

BS -> PCF

Ob

4
5
6

a.

This element shall only be included if it was also included in the

A9-BS Service Request message. This element shall be set to the
value received in that message.

7
8

b.

This element shall only be included if the BS does not grant the
A9-BS Service Request. The allowable cause value is MS busy.

9
10

The following table shows the bitmap layout for the A9-BS Service Response
message:
7

Octet

A9 Message Type = [07H]

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Cause: A9 Element Identifier = [04H]

Length = [01H]

ext = [0]

Cause Value = [ 08H (MS busy),

11H (Service option not available)]

528

6
1
2
3

TIA/EIA/IS-2001

6.1.10.8

A9-AL Connected

2
3

This A9 interface message is sent from the BS to the PCF to notify that the traffic
channel is established when the MS performed Hard Handoff.
Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

BS -> PCF

Call Connection Reference

6.2.2.98

BS -> PCF

Correlation ID

6.2.2.108

BS -> PCF

Oa

A8_Traffic_ID

6.2.2.170

BS -> PCF

PDSN IP Address

6.2.2.30

PCF -> BS

4
5
6

a.

If this element is included in this message, its value shall be

returned in the corresponding element in the A9-AL Connected
Ack message sent in response to this message.

The following table shows the bitmap layout for the A9-AL Connected message:
7

A9 Message Type = [08H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

-- Continued on next page --

529

TIA/EIA/IS-2001

1
-- Continued from previous page -

(MSB)

A8 Traffic ID: A9 Element Identifier = [08H]

Length = [0CH]

A8 transport protocol stack = [01H] (GRE/IP)

Protocol Type = [88 0BH] (PPP)

4
(LSB)

(MSB)

5
6

Key = <any value>

7
8
(LSB)

Address Type = [01H] (IPv4)

9
10

(MSB)

11
IP Address = <any value>

12
13
(LSB)

14
1

PDSN IP Address: A1 Element Identifier = [14H]

Length = [04H]

(MSB)

3
PDSN IP Address = <any value>

4
5
(LSB)

530

TIA/EIA/IS-2001

6.1.10.9

A9-AL Connected Ack

2
3

This A9 interface message is sent from the PCF to the BS to acknowledge completion
of the Al connection request.
Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

PCF -> BS

Call Connection Reference

6.2.2.98

PCF -> BS

Correlation ID

6.2.2.108

PCF -> BS

Oa

4
5
6

a.

This element shall only be included if it was also included in the

A9-AL Connected message. This element shall be set to the value
received in that message.

The following table shows the bitmap layout for the A9-AL Connected Ack message:
7

A9 Message Type = [09H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

531

TIA/EIA/IS-2001

6.1.10.10

A9-AL Disconnected

2
3

This A9 interface message is sent from the BS to the PCF to notify that the traffic
channel is to be released when the MS performed Hard Handoff.
Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

BS -> PCF

Call Connection Reference

6.2.2.98

BS -> PCF

Correlation ID

6.2.2.108

BS -> PCF

Oa

A8_Traffic_ID

6.2.2.170

BS -> PCF

4
5
6

a.

If this element is included in this message, its value shall be

returned in the corresponding element in the A9-AL Disconnected
Ack message sent in response to this message.

The following table shows the bitmap layout for the A9-AL Disconnected message:
7

A9 Message Type = [0AH]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

-- Continued on next page --

532

TIA/EIA/IS-2001

1
-- Continued from previous page -

(MSB)

A8 Traffic ID: A9 Element Identifier = [08H]

Length = [0CH]

A8 transport protocol stack = [01H] (GRE/IP)

Protocol Type = [88 0BH] (PPP)

4
(LSB)

(MSB)

5
6

Key = <any value>

7
8
(LSB)

Address Type = [01H] (IPv4)

9
10

(MSB)

11
IP Address = <any value>

12
13
(LSB)

533

14

TIA/EIA/IS-2001

6.1.10.11

A9-AL Disconnected Ack

2
3

This A9 interface message is sent from the PCF to the BS to acknowledge completion
of the Al disconnected request.
Information Element

Section
Reference

Element Direction

Type

A9 Message Type

6.2.2.167

PCF -> BS

Call Connection Reference

6.2.2.98

PCF -> BS

Correlation ID

6.2.2.108

PCF -> BS

Oa

4
5
6

a.

7
8

This element shall only be included if it was also included in the

A9-AL Disconnected message. This element shall be set to the
value received in that message.

The following table shows the bitmap layout for the A9-AL Disconnected Ack
message:
7

A9 Message Type = [0BH]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

9
10

534

TIA/EIA/IS-2001

6.1.11

A11 Interface Message Formats

6.1.11.1

A11-Registration Request

This A11 interface message is sent from the PCF to the PDSN for:

establishing an A10 connection;

periodic re-registration of an A10 connection;

clearing an A10 connection;

passing accounting related information.

Information Element

Section
Reference

Element Direction

Type

A11 Message Type

6.2.2.154

PCF -> PDSN

Flags

6.2.2.155

PCF -> PDSN

Lifetime

6.2.2.156

PCF -> PDSN

Home Address

6.2.2.157

PCF -> PDSN

Home Agent

6.2.2.158

PCF -> PDSN

Care-of-Address

6.2.2.159

PCF -> PDSN

Identification

6.2.2.160

PCF -> PDSN

Session Specific Extension

6.2.2.165

PCF -> PDSN

Vendor/Organization Specific Extension(s)

6.2.2.166

PCF -> PDSN

Oa

Mobile-Home Authentication Extension

6.2.2.163

PCF -> PDSN

8
9

a.

One or more instances of this element may be included in the A11Registration Request message.

10
11
12

The following table shows the bitmap layout for the A11-Registration Request
message:
0

MSB

Octet

A11 Message Type = [01H]

Flags = [0AH]

Lifetime = [00 00H to FF FFH]

1
LSB

MSB

2
1

Home Address = [00 00 00 00 H]

2
3
LSB

-- Continued on next page --

535

TIA/EIA/IS-2001

1
-- Continued from previous page -MSB

1
Home Agent = <any value>

2
3
LSB

MSB

4
1

Care-of-Address = <any value>

2
3
LSB

MSB

4
1
2
3

Identification = <any value>

4
5
6
7
LSB

MSB

Session Specific Extension: = [27H]

Length = [13H15H]

2
3

Protocol Type = [ 88 0BH, 88 81H ]

LSB

MSB

4
5
6

Key (PCF Session Identifier) = <any value>

7
LSB

8
9

Reserved = [00 00H]

10
MSB

11

MN Session Reference Id = <any value>

LSB

MSB

13

MN ID Type = [00 06 H] (IMSI)

LSB
-- Continued on next page --

536

12
14

TIA/EIA/IS-2001

1
-- Continued from previous page -15

MN ID Length = [06-08H] (10-15 digits)

Identity Digit 1 = [0H, 9H] (BCD)

Odd/Even Indicator = [0000, 0001]

16

Identity Digit 3 = [0H, 9H] (BCD)

Identity Digit 2 = [0H, 9H] (BCD)

17

Identity Digit N = [0H, 9H] (BCD)

21-23

If (Odd/Even Indicator = 0000 (even))

{Identity Digit N+1 = [FH] (BCD)}
Else If (Odd/Even Indicator = 0001 (odd))
{Identity Digit N+1 = [0H, 9H]
(BCD)}

Vendor/Organization Specific Extension: Type = [ 26H]

Reserved = [0000 0000]

MSB

3
Length = <variable>

LSB

MSB

4
5

3GPP2 Vendor ID = 00 00 15 9FH

6
7
LSB

Application Type = [01 H, 02H]

8
9

IF (Application Type = 01H (Accounting) {1:

Application Sub Type = [01 H]

10

MSB

11
12
Application Data (contains accounting information)

LSB

Variable

} Application Type = 01H; ELSE IF (Application Type = 02H (Mobility Event Indicator) {1:
Application Sub Type = [01H]

Mobile-Home Authentication Extension: Type = [20H]

Length = [14 H ]

} Application Type = 02H.

MSB

3
4

SPI = [00 00 01 00H to FF FF FF FF H]

5
LSB
-- Continued on next page --

537

TIA/EIA/IS-2001

1
-- Continued from previous page -MSB

7
8
9
10

Authenticator = <any value > (keyed-MD-5 authentication)

11

21
LSB
2

538

22

TIA/EIA/IS-2001

1
2

6.1.11.2

3
4

A11-Registration Reply
This A11 interface message is sent from the PDSN to the PCF in response to an A11
Registration Request message.

Information Element

Section
Reference

Element Direction

Type

A11 Message Type

6.2.2.154

PDSN -> PCF

Code

6.2.2.161

PDSN -> PCF

Lifetime

6.2.2.156

PDSN -> PCF

Home Address

6.2.2.157

PDSN -> PCF

Home Agent

6.2.2.158

PDSN -> PCF

Ma

Identification

6.2.2.160

PDSN -> PCF

Session Specific Extension

6.2.2.165

PDSN -> PCF

Vendor/Organization Specific Extension

6.2.2.166

PDSN -> PCF

Ob

Mobile-Home Authentication Extension

6.2.2.163

PDSN -> PCF

5
6

a.

This element can also be used to identify the IPv4 address of an

alternative PDSN.

7
8

b.

One or more instances of this element may be included in the A11Registration Reply message.

539

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A11-Registration Reply message
0

[ 00H

Octet

A11 Message Type = [03H]

Code =

(Registration Accepted),

80H (Registration Denied reason unspecified)

81H (Registration Denied -- administratively prohibited)
82H (Registration Denied insufficient resources)
83H (Registration Denied mobile node failed authentication)
85H (Registration Denied identification mismatch)
86H (Registration Denied poorly formed request)
88H

(Registration Denied unknown PDSN address)

89H

(Registration Denied requested reverse tunnel unavailable)

8AH

(Registration Denied reverse tunnel is mandatory and T bit not set)

8DH (Registration Denied unsupported vendor ID or unable to interpret data in the

CVSE) ]
MSB

Lifetime = [00 00 H to FF FF H]

1
LSB

MSB

2
1

Home Address = [00 00 00 00 H]

2
3
LSB

MSB

4
1

Home Agent = <any value>

2
3
LSB

MSB

4
1
2
3

Identification = <any value>

4
5
6
7
LSB

-- Continued on next page --

540

TIA/EIA/IS-2001

1
-- Continued from previous page - Session Specific Extension: Type = [27H]

Length = [13H 15H]

MSB

Protocol Type = [ 88 0BH, 88 81H ]

LSB

MSB

4
5
6

Key (PCF Session Identifier) = <any value>

7
LSB

8
9

Reserved = [00 00 H]

10
MSB

11

MN Session Reference Id = <any value>

LSB

MSB

12
13

MN ID Type = [00 06 H] (IMSI)

LSB

14
15

MN ID Length = [06-08H] (10-15 digits)

Identity Digit 1 = [0H, 9H] (BCD)

Odd/Even Indicator = [0000, 0001]

16

Identity Digit 3 = [0H, 9H] (BCD)

Identity Digit 2 = [0H, 9H] (BCD)

17

Identity Digit N = [0H, 9H] (BCD)

21-23

If (Odd/Even Indicator = 0000 (even))

{Identity Digit N+1 = [FH] (BCD)}
Else If (Odd/Even Indicator = 0001 (odd))
{Identity Digit N+1 = [0H, 9H]
(BCD)}

Vendor/Organization Specific Extension: Type = [ 26H]

Reserved = [0000 0000]

(MSB)

3
Length = 00 05H

(LSB)

(MSB)

4
5

3GPP2 Vendor ID = 00 00 15 9FH

6
7
(LSB)

Application Type = [03H]

Application Sub Type = [01 H]
-- Continued on next page --

541

8
9
10

TIA/EIA/IS-2001

1
-- Continued from previous page - Mobile-Home Authentication Extension: Type = [20H]

Length = [ 14H ]

2
3

MSB
4

SPI = [00 00 01 00H to FF FF FF FF H]

5
LSB
MSB

6
7
8
9
10

Authenticator = <any value > (keyed-MD-5 authentication)

11

21
LSB

542

22

TIA/EIA/IS-2001

6.1.11.3

2
3

A11-Registration Update
This A11 interface message is sent from the PDSN to the PCF to update the status of
an A10 connection.

Information Element

Section
Reference

Element Direction

Type

A11 Message Type

6.2.2.154

PDSN -> PCF

Reserved <3 octets>

None

PDSN -> PCF

Ma

Home Address

6.2.2.157

PDSN -> PCF

Home Agent

6.2.2.158

PDSN -> PCF

Identification

6.2.2.160

PDSN -> PCF

Session Specific Extension

6.2.2.165

PDSN -> PCF

Registration Update Authentication

Extension

6.2.2.164

PDSN -> PCF

a.

This field is set to zero by the PDSN and ignored by the PCF.

5
6
7

The following table shows the bitmap layout for the A11-Registration Update
message.

8
0

Message Type = [14H]

Octet
1
1

Reserved = [00 00 00 H]

2
3

MSB

1
Home Address = [00 00 00 00 H]

2
3
LSB

MSB

4
1

Home Agent = <any value>

2
3
LSB

-- Continued on next page --

543

TIA/EIA/IS-2001

1
-- Continued from previous page -MSB

1
2
3
Identification = <any value>

4
5
6
7
LSB

Session Specific Extension: Type = [27H]

Length = [13H 15H]

Protocol Type = [ 88 0BH, 88 81H]

MSB

LSB
MSB

4
5

Key (PCF Session Identifier) = <any value>

6
7
LSB

8
9

Reserved = [00 00 H]

10
MSB

MN Session Reference Id = <any value>

11
LSB

MSB

MN ID Type = [00 06 H] (IMSI)

12
13

LSB
MN ID Length = [06-08H] (10-15 digits)

14
15

Identity Digit 1 = [0H, 9H] (BCD)

Odd/Even Indicator = [0000, 0001]

16

Identity Digit 3 = [0H, 9H] (BCD)

Identity Digit 2 = [0H, 9H] (BCD)

17

Identity Digit N = [0H, 9H] (BCD)

21-23

If (Odd/Even Indicator = 0000 (even))

{Identity Digit N+1 = [FH] (BCD)}
ELSE (If Odd/Even Indicator = 0001 (odd))
{Identity Digit N+1 = [0H, 9H] (BCD)}

-- Continued on next page --

544

TIA/EIA/IS-2001

1
-- Continued from previous page - Registration Update Authentication Extension: Type = [28H]

Length = [14H ]

(MSB)

3
SPI = [00 00 01 00H to FF FF FF FF H]

4
5
(LSB)

(MSB)

6
7
8
9
10

Authenticator = <any value > (keyed-MD-5 authentication)

11

21
(LSB)

545

22

TIA/EIA/IS-2001

6.1.11.4

A11-Registration Acknowledge

2
3

This A11 interface message is sent from the PCF to the PDSN in response to a A11Registration Update message.
Information Element

Section
Reference

A11 Message Type

Element Direction

Type

6.2.2.154

PCF -> PDSN

None

PCF -> PDSN

Ma

Status

6.2.2.162

PCF->PDSN

Home Address

6.2.2.157

PCF -> PDSN

Care-of-Address

6.2.2.159

PCF -> PDSN

Identification

6.2.2.160

PCF -> PDSN

Session Specific Extension

6.2.2.165

PCF -> PDSN

Registration Update Authentication

Extension

6.2.2.164

PCF -> PDSN

Reserved <2 octets>

a.

This field is set to zero by the PCF and ignored by the PDSN.

5
6
7

The following table shows the bitmap layout for the A11-Registration Acknowledge
message.
0

Octet

Message Type = [15H]

Reserved = <00 00 H>

1
2

Status =

[ 00H (Update Accepted)

80H (Update Denied reason unspecified)
81H (Update Denied -- administratively prohibited
83H (Update Denied sending node failed authentication)
85H (Update Denied identification mismatch)
86H (Registration Denied poorly formed registration update) ]
MSB

1
Home Address = [00 00 00 00 H]

2
3
LSB

-- Continued on next page --

546

TIA/EIA/IS-2001

1
-- Continued from previous page -MSB

1
Care-of-Address = <any value>

2
3
LSB

MSB

4
1
2
3

Identification = <any value>

4
5
6
7
LSB

Session Specific Extension: Type = [27H]

Length = [13H 15H]

Protocol Type = [ 88 0BH, 88 81H]

MSB

LSB
MSB

4
5

Key (PCF Session Identifier) = <any value>

6
7
LSB

Reserved = [00 00 H]

8
9
10

MSB

MN Session Reference Id = <any value>

11
LSB

MSB

MN ID Type = [00 06 H] (IMSI)

12
13

LSB
MN ID Length = [06-08H] (10-15 digits)

14
15

Identity Digit 1 = [0H, 9H] (BCD)

Odd/Even Indicator = [0000, 0001]

16

Identity Digit 3 = [0H, 9H] (BCD)

Identity Digit 2 = [0H, 9H] (BCD)

17

Identity Digit N = [0H, 9H] (BCD)

21-23

If (Odd/Even Indicator = 0000 (even))

{Identity Digit N+1 = [FH] (BCD)}
Else If (Odd/Even Indicator = 0001 (odd))
{Identity Digit N+1 = [0H, 9H]
(BCD)}

-- Continued on next page --

547

TIA/EIA/IS-2001

1
-- Continued from previous page - Registration Update Authentication Extension: Type = [28H]

Length = [14H ]

MSB

3
4

SPI = [00 00 01 00H to FF FF FF FF H]

5
LSB
(MS)B

6
7
8
9
10

Authenticator = <any value > (keyed-MD-5 authentication)

11

21
(LSB)
2

548

22

TIA/EIA/IS-2001

6.1.12

A7 Interface Message Formats

6.1.12.1

A7-Handoff Request

3
4

This A7 interface message is sent from the source BS to the target BS to request
allocation of resources to support soft/softer handoff for a call.
Information Element

Section
Reference

Element Direction

Type

Message Type II

6.2.2.5

Source BS -> Target BS

Call Connection Reference

6.2.2.98

Source BS -> Target BS

Cell Identifier List

6.2.2.21

Source BS -> Target BS

Oa,f,m

IS-95 Channel Identity

6.2.2.10

Source BS -> Target BS

Ob,f

Band Class

6.2.2.106

Source BS -> Target BS

Downlink Radio Environment

6.2.2.25

Source BS -> Target BS

CDMA Serving One Way Delay

6.2.2.79

Source BS -> Target BS

Service Configuration Record

6.2.2.109

Source BS -> Target BS

On

Privacy Info

6.2.2.143

Source BS -> Target BS

Oo

A3 Signaling Address

6.2.2.90

Source BS -> Target BS

Ok

Correlation ID

6.2.2.108

Source BS -> Target BS

Ok

SDU-ID

6.2.2.91

Source BS -> Target BS

Od

Mobile Identity (IMSI)

6.2.2.16

Source BS -> Target BS

Oe

Mobile Identity (ESN)

6.2.2.16

Source BS -> Target BS

Oe

Physical Channel Info

6.2.2.14

Source BS -> Target BS

Of,l

Quality of Service Parameters

6.2.2.54

Source BS -> Target BS

Og,f

IS-2000 Power Control Info

6.2.2.176

Source BS -> Target BS

Oh,f

IS-2000 Forward Power Control Mode

6.2.2.177

Source BS -> Target BS

Oi,f

IS-2000 FPC Gain Ratio Info

6.2.2.178

Source BS -> Target BS

Oj,f

A7 Originating ID

6.2.2.172

Source BS -> Target BS

m,f

IS-2000 Service Configuration Record

6.2.2.68

Source BS ->Target
BS

549

n,f

TIA/EIA/IS-2001

1
2

a.

The list of cell identifiers shall be assumed by the target BS to be in priority

order with the highest priority cell listed first.

3
4
5

b.

The target BS shall consider only the following fields valid in this element: A1
Element ID, Length, Number of Channels to Add, Frame Offset, Freq. Included
and ARFCN. All other fields shall be ignored by the target BS.

6
7

c.

If this element is omitted, the target BS shall send all A3 signaling messages
related to the call to the same address as is used to reply to this A7 message.

8
9

d.

Optionally included by the source BS. If included, the value shall be saved and
used by the target BS on A3 signaling messages.

10

e.

This element shall be included for OA&M purposes.

11
12
13
14
15
16
17
18
19
20
21

f.

Either the { IS-95 Channel Identity, Service Configuration Record} elements as

a set, or the { Physical Channel Info, Quality of Service, IS-2000 Power
Control Info, IS-2000 Forward Power Control Mode, IS-2000 FPC Gain Ratio,
A7 Originating ID, and IS-2000 Service Configuration Record } elements as a
set shall be present in this message, but elements from both sets shall not be
present simultaneously. The IS-95 Channel Identity element is being kept in
this revision of this specification for backward compatibility, and is expected to
be removed from the next revision of this specification. For backward
compatibility, the { IS-95 Channel Identity, Service Configuration Record} set
of elements shall be sent to BSs implemented to V3.x.y of the CDG IOS
specifications.

22
23

g.

The BS shall send the Quality of Service Parameters information element only
for a packet data call when it is received from the MSC.

24
25
26
27
28

h.

This element shall be included when the physical channel (FCH or DCCH)
measured by the primary power control subchannel is included in the Frame
Selector Info Information Element. It provides information about power
control for the call. (Note: information for the secondary power control
subchannel is sent in the A7-Burst Commit message.)

29
30
31
32

i.

This element shall be included when the physical channel (FCH or DCCH)
measured by the primary power control subchannel is included in the Frame
Selector Info Information Element. (Note: information for the secondary power
control subchannel is sent in the A7-Burst Commit message.)

33
34
35
36
37
38

j.

This element shall be included when the physical channel (FCH or DCCH)
measured by the primary power control subchannel is included in the Frame
Selector Info Information Element. It provides information used for forward
gain equalization for the primary power control subchannel.
(Note:
information for the secondary power control subchannel is sent in the A7-Burst
Commit message.)

39
40

k.

If this element is included in this message, it shall be returned in the A7Handoff Request Ack message.

41
42

l.

A maximum of one supplemental channel (SCH) is supported by this version of

this specification.

550

TIA/EIA/IS-2001

1
2
3
4

m. This element is optionally included by the source BS. If included, the value
shall be saved and used by the target BS in subsequent A7 messages for this
call association. If the A3 Flag field is set to '1', then the value shall also be
used by the target BS in all subsequent A3 messages.

5
6

n.

Either the Service Configuration Record or the IS-2000 Service Configuration

Record is included in this message, but not both.

o.

This element is included if the Privacy Mask is available.

551

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A7-Handoff Request message:
7

Message Type II = [80H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

Cell Identifier List:

10
1

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification) {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification

IS-95 Channel Identity: A1 Element Identifier = [22H]

Length = [05H]

Hard
Handoff =
[0]
(ignored)

Power
Pilot PN
Combined
Code
(high part)
= [0]
= [0]
(ignored)

2
Frame Offset = [0H-FH]

Number of Channels to Add

= [000]

1
3

(ignored)
Walsh Code Channel Index = [00H] (ignored)

Pilot PN Code (low part) = [00H] (ignored)

Reserved = [00]

Freq.
included

ARFCN (high part)

= [000-111]

= [1]

(ignored)
ARFCN (low part) = [00H-FFH]
-- Continued on next page --

552

TIA/EIA/IS-2001

1
-- Continued from previous page -

Band Class:

A1 Element Identifier = [5DH]

Length = [01H]

Reserved = [000]

Band Class = [00001] (PCS)

Downlink Radio Environment:

3
1

A1 Element Identifier = [29H]

Length = <variable>

Number of Cells = <variable>

Cell Identification Discriminator = [07H]

Downlink Radio Environment {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Reserved = [00]

j+3

Sector = [0H-FH] (0H = Omni)

Downlink Signal Strength Raw = [000000] (ignored)

(MSB)

j+2
j+4
k

CDMA Target One Way Delay

k+1
(LSB)

k+2

} Downlink Radio Environment

CDMA Serving One Way Delay: A1 Element Identifier = [0CH]

Length = [09H]

Cell Identification Discriminator = [ 07H]

(MSB)

4
MSCID = <any value>

5
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

(MSB)

Sector = [0H-FH] (0H = Omni)

CDMA Serving One Way Delay = [0000H-FFFFH]

Resolution = [00, 01,

10]

Service Configuration Record:

10
11
1

A7 Element Identifier = [10H]

Length = <variable>
(MSB)

8
9

(LSB)
Reserved = [0000 00]

Service Configuration Record = <any value>

(LSB)

-- Continued on next page --

553

TIA/EIA/IS-2001

1
-- Continued from previous page -

Privacy Info:

A3/A7 Element Identifier = [1AH]

Length = <variable>

Privacy Mask Information {1+:

Reserved

Privacy Mask Type = [00001,00010]

Status

Available

= [0]

(public, private)

= [0,1]

= [0,1]

Privacy Mask Length = <variable>

(MSB)

j
j+1

Privacy Mask = <any value>

j+2

(LSB)

} Privacy Mask Information

A3 Signaling Address:

A1 Element Identifier = [49H]

Length = [07H]

Address Type = [01H] (IPv4)

(MSB)

TCP Port

4
(LSB)

(MSB)

5
6

A3 Address = <any value>

7
8
(LSB)

9
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

SDU ID:

A1 Element Identifier = [4CH]

Length = [01H to 06H]

(MSB)

SDU ID = <any value>

(LSB)

-- Continued on next page --

554

TIA/EIA/IS-2001

1
-- Continued from previous page -

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

2
Type of Identity

Odd/even
Indicator

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

2
Type of Identity

Odd/even
Indicator

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Physical Channel Info: A3/A7 Element Identifier = [07H]

7
1

Length =[05H]

Frame Offset = [00H FFH]

A3 Traffic Channel Protocol

Stack = [001]

Pilot Gating Rate

= [00, 01, 10]

ARFCN (high part)

= [000-111]

ARFCN (low part) = [00H-FFH]

Count of Physical Channels = [01H-02H]

Reserved = [0000]

OTD=
[0,1]

Count of Physical Channels

= [001 010]
Physical Channel 1 =
0H IS-95,
1H FCH,
2H SCH,
3H DCCH

Physical Channel 2 =
0H N/A,
1H FCH,
2H SCH,
3H DCCH

-- Continued on next page --

555

6
7

TIA/EIA/IS-2001

1
-- Continued from previous page --

Quality of Service Parameters:

A7 Element Identifier = [0FH]

Length = [01H]
Reserved = [0000]

A3/A7 Element Identifier = [0BH]

3
1

Length = [05H]

Mobile Pilot Gain = [00H FFH]

Reserved = [0000]

FPC_
PRI_
CHAN =
[0,1]

2
Packet Priority = [0000 1101]

IS-2000 Power Control Info:

Count of Subchan Gains =

[011]

Reserved = [000]

FPC_SUBCHAN_GAIN 1 = [0 0000 1 1111]

Reserved = [000]

FPC_SUBCHAN_GAIN 2 = [0 0000 1 1111]

Reserved = [000]

FPC_SUBCHAN_GAIN 3 = [0 0000 1 1111]

IS-2000 Forward Power Control Mode:

A3/A7 Element Identifier = [14H]

Length = [02H]
Reserved = [0000 0]

2
FPC_MODE = [000 011]

ACTION_TIME = [00H] (ignored)

-- Continued on next page --

556

1
3
4

TIA/EIA/IS-2001

1
-- Continued from previous page -

IS-2000 FPC Gain Ratio Info:

Reserved
= [0]

Length = [08H]

Initial Gain Ratio = [00H FFH]

Gain Adjust Step Size = [0H FH]

A3/A7 Element Identifier = [15H]

Count of Gain Ratio Pairs =

[011]

Min Gain Ratio 1 = [00H FFH]

Max Gain Ratio 1 = [00H FFH]

Min Gain Ratio 2 = [00H FFH]

Max Gain Ratio 2 = [00H FFH]

Min Gain Ratio 3 = [00H FFH]

Max Gain Ratio 3 = [00H FFH]

10

A7 Originating ID:

A3/A7 Element Identifier = [2CH]

Length = [03H]
Reserved = [0000 000]
(MSB)

2
A3 Flag
= [0,1]

A7 Originating ID = <any value>

4
(LSB)

-- Continued on next page --

557

TIA/EIA/IS-2001

1
-- Continued from previous page -

IS-2000 Service Configuration Record:

A1 Element Identifier = [0EH]

Bit-Exact Length Octet Count = <variable>

Reserved
= [ 0000 0 ]

1
2

Bit-Exact Length Fill Bits

= [ 000 111 ]

(MSB)

3
4

IS-2000 Service Configuration Record Content = <any value>

Seventh
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Sixth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fifth Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

Fourth
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

558

Third
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

Second
Fill Bit
if needed
= [0 (if
used as a
fill bit)]

...
First Fill
Bit if
needed
= [0 (if
used as a
fill bit)]

TIA/EIA/IS-2001

6.1.12.2

2
3

A7-Handoff Request Ack

This A7 interface message is sent from the target BS to the source BS to respond to a
request for allocation of resources to support soft/softer handoff for a call.

Information Element

Section
Reference

Element Direction

Message Type II

6.2.2.5

Target BS -> Source BS

Call Connection Reference

6.2.2.98

Target BS -> Source BS

Cell Identifier List (committed)

6.2.2.21

Target BS -> Source BS

Correlation ID

6.2.2.108

Target BS -> Source BS

Neighbor List

6.2.2.83

Target BS -> Source BS

Cell Identifier List (uncommitted)

6.2.2.21

Target BS -> Source BS

Cause List

6.2.2.142

Target BS -> Source BS

A7 Control

6.2.2.97

Target BS -> Source BS

A7 Originating ID

6.2.2.172

Target BS -> Source BS

A7 Destination ID

6.2.2.173

Target BS -> Source BS

Type
M
O

a,g

c,g

d,g

e,g

O
O
O

O
O

4
5

a.

If there are no committed cells, the length field of this element shall be set
to zero.

6
7

b.

This field is required if a Correlation ID value was included on the A7Handoff Request message to which this message is a response.

8
9
10
11

c.

There may be multiple instances of the Neighbor List element. The

number and order of instances of the Neighbor List element shall match
the number and order of cell identifiers in the Cell Identifier List
(committed) element.

12
13
14
15

d.

If one or more cells that were requested are not being committed to the call
association by the target BS, then this element is required when the
receiver of this message is implemented to V3.x.y of the CDG IOS
specification. It shall contain the cell identifiers of all uncommitted cells.

16
17
18
19
20
21
22
23
24
25
26

e.

If one or more cells that were requested are not being committed to the call
association by the target BS, then this element is required to indicate the
reasons on a cell by cell basis when the receiver of this message is
implemented V3.x.y of the CDG IOS specification. The number and order
of the cause values in this list shall match the number and order of cell
identifiers in the Cell Identifier List (uncommitted) element. The
allowable cause values are: OAM&P intervention, Service option not
available, Equipment failure, No radio resource available, BS not
equipped, Ciphering algorithm not supported, Private Long Code not
available or not supported, Requested MUX option or rates not available,
Requested privacy configuration unavailable.

559

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9

f.

If this element is not present, the source BS shall act as though the element
had been received with the Send Source Transfer Report field set to 0. If
this element is not used to request the A7-Source Transfer Performed
message from equipment capable of internally transferring call control
from one BSC to another, then the target BS shall be prepared to
potentially receive an A7-Handoff Request message from one BSC to set up
a soft/softer handoff, and an A7-Drop Target message from a different
BSC to remove cells from that soft/softer handoff. See informative annex
B for more information.

10
11
12

g.

Any cell must being committed for this call association must be committed for
all physical channels that were listed in the corresponding A7-Handoff Request
message.

13
14
15

h.

This element is optionally included by the target BS. If included, the value
shall be saved and used by the source BS in subsequent A7 messages for this
call association.

16
17

i.

This element is required if an A7 Originating ID value was included in the

corresponding A7-Handoff Request message.

18

560

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the A7-Handoff Request Ack
message:
7

Message Type II = [81H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Cell Identifier List (committed): A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

-- Continued on next page --

561

TIA/EIA/IS-2001

1
-- Continued from previous page -

Neighbor List: A1 Element Identifier = [48H]

Length = <variable>

Number of Neighbors = [00H-FFH]

Pilot PN Code (low part) = [00H-FFH]

Neighbor Info {1+:

Short Cell Identification Discriminator = [000 0111]

Pilot PN
Code
(high part)

k+1

(Discriminator Type = 7)

= [0,1]
(MSB)

k+2
MSCID = <any value>

k+3
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

k+4
k+5

Sector = [0H-FH] (0H = Omni)

k+6

} Neighbor Info

Cell Identifier List (uncommitted):

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

} Cell Identification
-- Continued on next page --

562

j+2
j+3
j+4

TIA/EIA/IS-2001

1
-- Continued from previous page -

Cause List:

A3/A7 Element Identifier = [19H]

Length = <variable>

Cause Value {1+:

Reserved
= [0]

Cause Value =
= [07H (OAM&P intervention),
11H (service option not available),
20H ( equipment failure),
21H (no radio resource available),
40H (ciphering algorithm not supported)
41H (Private Long Code not available or not supported),
42H (Requested MUX option or rates not available),
43H (Requested Privacy Configuration unavailable)]

} Cause Value

A7 Control:

A3/A7 Element Identifier = [1FH]

Length = [01H]

Reserved = [0000 000]

A7 Originating ID:

2
Send
Source
Transfer
Report =
[1]

A3/A7 Element Identifier = [2CH]

Length = [03H]
Reserved = [0000 000]
(MSB)

2
A3 Flag
= [0,1]

A7 Originating ID = <any value>

A7 Destination ID:

A7 Destination ID = <any value>

3
(LSB)

563

5
1

A3/A7 Element Identifier = [2DH]

Length = [02H]
(MSB)

3
4

(LSB)

TIA/EIA/IS-2001

6.1.12.3

2
3

A7-Drop Target
This A7 interface message is sent from the source BS to the target BS to request
deallocation of resources being used to support soft/softer handoff for a call.

Information Element

Section
Reference

Element Direction

Type

Message Type II

6.2.2.5

Source BS -> Target BS

Call Connection Reference

6.2.2.98

Source BS -> Target BS

Cell Identifier List

6.2.2.21

Source BS -> Target BS

Ob

Correlation ID

6.2.2.108

Source BS -> Target BS

Oa

A7 Destination ID

6.2.2.173

Source BS -> Target BS

4
5

a.

If this element is included in this message, then the target BS

shall include the value in the A7-Drop Target Ack message.

6
7
8

b. This element is required if an A7 Originating ID value was included

in an A7-Handoff Request Ack message previously received from
the target BS for this call association.

564

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the A7-Drop Target message:
7

Message Type II = [82H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

Cell Identifier List:

10
1

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

A7 Destination ID:

A3/A7 Element Identifier = [2DH]

Length = [02H]
(MSB)

A7 Destination ID = <any value>

3
(LSB)

565

TIA/EIA/IS-2001

6.1.12.4

2
3
4

A7-Drop Target Ack

This A7 interface message is sent from the target BS to the source BS to respond to a
request for deallocation of resources being used to support soft/softer handoff for a
call.

Information Element

Section
Reference

Element Direction

Type

Message Type II

6.2.2.5

Target BS -> Source BS

Call Connection Reference

6.2.2.98

Target BS -> Source BS

Correlation ID

6.2.2.108

Target BS -> Source BS

A7 Destination ID

6.2.2.173

Target BS -> Source BS

O
O

5
6

a.

This field is required if a Correlation ID value was included on the A7Drop Target message to which this message is a response.

7
8
9

b.

This element is required if an A7 Originating ID value was included in an

A7-Handoff Request message previously received from the source BS for
this call association.

566

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A7-Drop Target Ack message:
7

Message Type II = [83H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

A7 Destination ID:

A3/A7 Element Identifier = [2DH]

Length = [02H]
(MSB)

A7 Destination ID = <any value>

3
(LSB)

567

TIA/EIA/IS-2001

6.1.12.5

2
3

A7-Target Removal Request

This A7 interface message is sent from the target BS to the source BS to request
deallocation of resources being used to support soft/softer handoff for a call.

Information Element

Section
Reference

Element Direction

Type

Message Type II

6.2.2.5

Target BS -> Source BS

Call Connection Reference

6.2.2.98

Target BS -> Source BS

Cell Identifier List (target)

6.2.2.21

Target BS -> Source BS

Cause List

6.2.2.142

Target BS -> Source BS

a,b,d

Correlation ID

6.2.2.108

Target BS -> Source BS

A7 Destination ID

6.2.2.173

Target BS -> Source BS

O
O

O
O

4
5

a.

The number and order of entries in the Cell Identifier list (target) element
shall match the number and order of entries in the Cause List element.

6
7
8
9

b.

The allowable cause values are broken into two categories, those which
indicate that the source BS has a choice of honoring this removal request,
and those that indicate that the source BS has no choice and the removal
must take place.

10
11

Cause values indicating that the source BS has a choice are: OAM&P
intervention.

12
13

Cause values indicating that the source BS has no choice are: Equipment
failure.

14
15

c.

If this element is included in this message, the value shall be returned in

the A7-Target Removal Response message.

16
17
18

d.

This element is required if an A7 Originating ID value was included in an

A7-Handoff Request message previously received from the source BS for
this call association.

568

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the A7-Target Removal Request
message:
7

Message Type II = [84H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

Cell Identifier List (target):

10
1

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+2
j+3
j+4

} Cell Identification

Cause List:

A3/A7 Element Identifier = [19H]

Length = <variable>

1
2

Cause Value {1+:

Reserved
= [0]

Cause Value =
= [07H (OAM&P intervention),
20H ( equipment failure)]

} Cause Value
-- Continued on next page --

569

TIA/EIA/IS-2001

1
-- Continued from previous page -

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

A7 Destination ID:

A3/A7 Element Identifier = [2DH]

Length = [02H]
(MSB)

A7 Destination ID = <any value>

3
(LSB)

570

TIA/EIA/IS-2001

1
2

6.1.12.6

3
4
5

A7-Target Removal Response

This A7 interface message is sent from the source BS to the target BS to respond to a
request for deallocation of resources being used to support soft/softer handoff for a
call.

Information Element

Section
Reference

Element Direction

Type

Message Type II

6.2.2.5

Source BS -> Target BS

Call Connection Reference

6.2.2.98

Source BS -> Target BS

Correlation ID

6.2.2.108

Source BS -> Target BS

Cause List

6.2.2.142

Source BS -> Target BS

Cell Identifier List (not removed)

6.2.2.21

Source BS -> Target BS

A7 Destination ID

6.2.2.173

Source BS -> Target BS

b,c

c,

O
O

O
O

6
7

a.

This field is required if a Correlation ID value was included on the A7Target Removal Request message to which this message is a response.

8
9
10
11

b.

Included by the source BS only if one or more cells are not to be removed
from the soft/softer handoff as requested by the target BS. Allowable cause
values are: Uplink quality, Uplink strength, Downlink quality, Downlink
strength.

12
13
14

c.

If the Cause List element is included in this message, then the instances of
cause value in that element shall match the number and order of cell
identifiers in this list.

15
16
17

d.

This element is required if an A7 Originating ID value was included in an

A7-Handoff Request Ack message previously received from the target BS
for this call association.

571

TIA/EIA/IS-2001

1
2

The following table shows the bitmap layout for the A7-Target Removal Response
message:
7

Message Type II = [85H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Cause List:

A3/A7 Element Identifier = [19H]

Length = <variable>

6
1
2

Cause Value {1+:

Reserved
= [0]

Cause Value =
= [02H (uplink quality),
03H (uplink strength),
04H (downlink quality),
05H (downlink strength)]

} Cause Value
-- Continued on next page --

572

TIA/EIA/IS-2001

1
-- Continued from previous page -

Cell Identifier List (not removed):

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification

A7 Destination ID:

A3/A7 Element Identifier = [2DH]

Length = [02H]
(MSB)

A7 Destination ID = <any value>

3
(LSB)

2
3

6.1.12.7

UNUSED SECTION

6.1.12.8

UNUSED SECTION

6.1.12.9

UNUSED SECTION

4
5
6
7
8

573

TIA/EIA/IS-2001

6.1.12.10

2
3
4
5
6

A7- Source Transfer Performed

This message is used by the old source BSC to notify all target BSs of the successful
completion of a source transfer procedure. This message is only used when the target
BS has indicated on the A7-Handoff Request Ack message that it wishes to be
informed if control of the call is passed to another BSC. See informative annex B for
more information.

Information Element

Element Direction

Type

Message Type II

6.2.2.5

old Source BS -> Target BS

Call Connection Reference

6.2.2.98

old Source BS -> Target BS

BSC ID (old source)

6.2.2.125

old Source BS -> Target BS

BSC ID (new source)

6.2.2.125

old Source BS -> Target BS

A7 Destination ID
7
8
9

Section
Reference

a.

6.2.2.173

old Source BS -> Target BS

This element is required if an A7 Originating ID value was included in an

A7-Handoff Request message previously received from the target BS for
this call association.

574

TIA/EIA/IS-2001

1
2
3

The following table shows the bitmap layout for the A7-Target Source Transfer
Performed message:
7

Message Type II = [89H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

BSC ID (old source):

10
1

A3/A7 Element Identifier = [04H]

Length = [05H]

Type = [02H] (IPv4)

(MSB)

4
BSC Identifier = <any value> (IP v4 address)

5
6
(LSB)

BSC ID (new source):

7
1

A3/A7 Element Identifier = [04H]

Length = [05H]

Type = [02H] (IPv4)

(MSB)

4
BSC Identifier = <any value> (IP v4 address)

5
6
(LSB)

A7 Destination ID:

A3/A7 Element Identifier = [2DH]

Length = [02H]
(MSB)

A7 Destination ID = <any value>

3
(LSB)

575

TIA/EIA/IS-2001

6.1.12.11

A7-Reset

2
3
4

This A7 message can be sent between two BSs. It indicates to the receiving entity that
the transmitting entity has failed and has lost memory of the connections in progress,
connections set up, and associated references.
Information Element

Section
Reference

Element Direction

Message Type II

6.2.2.5

First BS <-> Second BS

Cause

6.2.2.19

First BS <-> Second BS

Software Version

6.2.2.65

First BS <-> Second BS

a.

Type
M
a

R
R

Allowable cause values: OAM&P intervention, Equipment failure.

6
7

The following table shows the bitmap layout for the A7-Reset message:
7

Octet

Message Type II = [8AH]

Cause: A7 Element Identifier = [08H]

Length = [01H]
ext =
[0]

Cause Value =

2
3

[07H (OAM&P intervention),

20H (equipment failure)]

Software Version:

A1 Element Identifier = [31H]

Length = <variable>

IOS Major Revision Level (X) = [04H]

IOS Minor Revision Level (Y) = [00H]

IOS Point Release Level (Z) = [00H]

Manufacturer/Carrier Software Information = <printable ASCII character>

Manufacturer/Carrier Software Information = <printable ASCII character>

576

TIA/EIA/IS-2001

6.1.12.12

2
3
4

A7-Reset Acknowledge
This A7 message can be sent between two BSs. It indicates to the receiving entity that
the transmitting entity has cleared all calls and reset all references, and is ready to
resume service.

Information Element

Section
Reference

Element Direction

Type

Message Type II

6.2.2.5

First BS <-> Second BS

Software Version

6.2.2.65

First BS <-> Second BS

5
6

The following table shows the bitmap layout for the A7-Reset Acknowledge message:
7

Message Type II = [8BH]

Software Version:

A1 Element Identifier = [31H]

Octet
1
1

Length = <variable>

IOS Major Revision Level (X) = [04H]

IOS Minor Revision Level (Y) = [00H]

IOS Point Release Level (Z) = [00H]

Manufacturer/Carrier Software Information = <printable ASCII character>

Manufacturer/Carrier Software Information = <printable ASCII character>

577

TIA/EIA/IS-2001

1
2
3
4

6.1.12.13

A7-Paging Channel Message Transfer

This A7 interface message is sent from the source BS to the target BS to request the
sending of the contained message on the specified paging channels to a mobile
station.

Information Element

Section
Reference

Message Type II

Element Direction

6.2.2.5

Source BS -> Target BS

Correlation ID

6.2.2.108

Source BS -> Target BS

Mobile Identity (IMSI)

6.2.2.16

Source BS -> Target BS

Cell Identifier List

6.2.2.21

Source BS -> Target BS

Air Interface Message

6.2.2.152

Source BS -> Target BS

Layer 2 Ack Request/Results

6.2.2.153

Source BS -> Target BS

Type
M
a

O
O
O

O
d

R
C

5
6

a.

If this element is included in this message, the value shall be returned in

the A7-Paging Channel Message Transfer Ack message.

b.

This element shall contain the IMSI sent by the MS..

8
9

c.

This element indicates the cells at the target BS on whose paging

channel(s) the air-interface message is to be sent.

10
11

d.

This element is included if the source BS wants a Layer 2

acknowledgment from the MS.

578

TIA/EIA/IS-2001

1
2
3

The following table shows the bitmap layout for the A7-Paging Channel Message
Transfer message:
7

Octet

Message Type II = [8CH]

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

6
1
2

Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

-- Continued on next page --

579

TIA/EIA/IS-2001

1
-- Continued from previous page -

Cell Identifier List:

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [02H,05H]

IF (Discriminator = 02H), Cell Identification {1+:

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

j+1

} OR IF (Discriminator = 05H), Cell Identification {1+:

(MSB)

LAC = [0001H-FFFFH]

j
(LSB)

j+1

} Cell Identification

Air Interface Message: A3/A7 Element Identifier = [21H]

Length = <variable>

TIA/EIA-IS-2000 Message Type = <00H to FFH>

Air Interface Message Length = <variable>

(MSB)

5
Air Interface Message = <any value>

(LSB)

Layer 2 Ack Request/Results:

A3/A7 Element Identifier = [23H]

Length = [01H]
Reserved = [0000 000]

580

k
1
2

Layer 2
Ack
= [0/1]

TIA/EIA/IS-2001

6.1.12.14

A7-Paging Channel Message Transfer Ack

2
3
4

This A7 interface message is sent from the target BS to the source BS to report the
results of sending an air interface message on the specified paging when a layer 2
acknowledgment had been requested by the source BS.
Information Element

Section
Reference

Message Type II

Element Direction

Type

6.2.2.5

Target BS -> Source BS

Correlation ID

6.2.2.108

Target BS -> Source BS

Layer 2 Ack Request/Results

6.2.2.153

Target BS -> Source BS

Cause

6.2.2.19

Target BS -> Source BS

M
a

O
O
O

5
6

a.

This element is included if the A7-Paging Channel Message Transfer

contained this element. It contains the value received on that message.

7
8

b.

This element is included to indicate success or failure in receiving a Layer 2

acknowledgment from the MS.

9
10
11

c.

Inclusion of this element indicates a failure to send the paging channel

message as requested in the A7-Paging Channel Message Transfer message.
Allowable cause values: OAM&P intervention, Equipment failure.

12
13
14

The following table shows the bitmap layout for the A7-Paging Channel Message
Transfer Ack message:
7

Octet

Message Type II = [8DH]

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Layer 2 Ack Request/Results:

A3/A7 Element Identifier = [23H]

Length = [01H]
Reserved = [0000 000]

Cause: A7 Element Identifier = [08H]

Length = [01H]

ext = [0]

Cause Value =
[07H (OAM&P intervention),
20H (equipment failure)]

581

6
1
2

Layer 2
Ack
= [0/1]

1
2
3

TIA/EIA/IS-2001

6.1.12.15

A7-Access Channel Message Transfer

2
3
4

This A7 interface message is sent from the target BS to the source BS to notify the
source BS of the reception of the contained message or Layer 2 acknowledgment on
the specified access channel.
Information Element

Section
Reference

Message Type II

Element Direction

6.2.2.5

Target BS -> Source BS

Correlation ID

6.2.2.108

Target BS -> Source BS

Mobile Identity (IMSI)

6.2.2.16

Target BS -> Source BS

Cell Identifier

6.2.2.20

Target BS -> Source BS

Air Interface Message

6.2.2.152

Target BS -> Source BS

Type
M
a

O
O
O

5
6

a.

If this element is included in this message, then the value shall be

returned in the A7-Access Channel Message Transfer Ack message.

b.

This element shall contain the IMSI sent by the MS.

8
9

c.

This element indicates the cell at the target BS on whose access channel
the air-interface message or Layer 2 acknowledgment was received.

10
11
12

The following table shows the bitmap layout for the A7-Access Channel Message
Transfer message:
7

Octet

Message Type II = [8EH]

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Length = [06H-08H] (10-15 digits)

Identity Digit 1 = [0H-9H] (BCD)

Odd/even
Indicator

6
1
2

Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

-- Continued on next page --

582

TIA/EIA/IS-2001

1
-- Continued from previous page -

Cell Identifier: A7 Element Identifier = [0AH]

Length = [06H]

Cell Identification Discriminator = [07H]

(MSB)

4
MSCID = <any value>

5
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

6
7

Sector = [0H-FH] (0H = Omni)

8
1

Air Interface Message: A3/A7 Element Identifier = [21H]

Length = <variable>

TIA/EIA-IS-2000 Message Type = <00H to FFH>

Air Interface Message Length = <variable>

(MSB)

5
Air Interface Message = <any value>

(LSB)

583

TIA/EIA/IS-2001

6.1.12.16

A7-Access Channel Message Transfer Ack

2
3

This A7 interface message is sent from the source BS to the target BS to acknowledge
the receipt of the A7-Access Channel Message Transfer message.
Information Element

Section
Reference

Message Type II
Correlation ID
4
5
6

a.

Element Direction

6.2.2.5

Source BS -> Target BS

6.2.2.108

Source BS -> Target BS

Type
M
a

This field is required if a Correlation ID value was included on the A7Access Channel Message Transfer message to which this message is a
response.

7
8
9

The following table shows the bitmap layout for the A7-Access Channel Message
Transfer Ack message:
7

Octet

Message Type II = [8FH]

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

10

584

TIA/EIA/IS-2001

6.1.12.17

2
3

A7-Burst Request
This A7 interface message is sent from the source BS to the target BS to request the
reservation of resources in support of a traffic burst.

Information Element

Section
Reference

Element Direction

Type

Message Type II

6.2.2.5

Source BS -> Target BS

Call Connection Reference

6.2.2.98

Source BS -> Target BS

Band Class

6.2.2.106

Source BS -> Target BS

Downlink Radio Environment

6.2.2.25

Source BS -> Target BS

CDMA Serving One Way Delay

6.2.2.79

Source BS -> Target BS

Privacy Info

6.2.2.143

Source BS -> Target BS

A3 Signaling Address

6.2.2.90

Source BS -> Target BS

Correlation ID

6.2.2.108

Source BS -> Target BS

SDU ID

6.2.2.91

Source BS -> Target BS

Mobile Identity (IMSI)

6.2.2.16

Source BS -> Target BS

Mobile Identity (ESN)

6.2.2.16

Source BS -> Target BS

Cell Identifier List

6.2.2.21

Source BS -> Target BS

Forward Burst Radio Info

6.2.2.56

Source BS -> Target BS

Reverse Burst Radio Info

6.2.2.57

Source BS -> Target BS

A7 Destination ID

6.2.2.173

Source BS -> Target BS

O
O
O
O
O
O
O
O
O

4
5
6

a.

If this element is omitted, the target BS shall send all A3 signaling

messages related to the call to the same address as is used to reply to this
A7 message.

7
8

b.

Optionally included by the source BS. If included, the value shall be saved
and used by the target BS on A3 signaling messages.

c.

This element may be included for OA&M purposes.

10
11

d.

The list of cell identifiers shall be assumed by the target BS to be in

priority order with the highest priority cell listed first.

12
13

e.

This element is only included when forward link radio resources are to be
allocated to the burst.

14
15

f.

This element is only included when reverse link radio resources are to be
allocated to the burst.

16
17

g.

If this element is included in this message, its value shall be returned in the
A7-Burst Response message and used in the A7-Burst Commit message.

18
19
20

h.

This element is required if an A7 Originating ID value was included in an

A7-Handoff Request Ack message previously received from the target BS
for this call association.

585

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A7-Burst Request message:
7

Message Type II = [90H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

Band Class:

A1 Element Identifier = [5DH]

Length = [01H]

Reserved = [000]

Band Class = [00001] (PCS)

Downlink Radio Environment:

10

3
1

A1 Element Identifier = [29H]

Length = <variable>

Number of Cells = <variable>

Cell Identification Discriminator = [07H]

Downlink Radio Environment {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Reserved = [00]

j+3

Sector = [0H-FH] (0H = Omni)

Downlink Signal Strength Raw = [000000] (ignored)

(MSB)

k+1
(LSB)

-- Continued on next page --

586

j+4
k

CDMA Target One Way Delay

} Downlink Radio Environment

j+2

k+2

TIA/EIA/IS-2001

1
-- Continued from previous page -

CDMA Serving One Way Delay: A1 Element Identifier = [0CH]

Length = [09H]

Cell Identification Discriminator = [ 07H]

(MSB)

4
MSCID = <any value>

5
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

(MSB)

Sector = [0H-FH] (0H = Omni)

CDMA Serving One Way Delay = [0000H-FFFFH]

Privacy Info:

8
9

(LSB)
Reserved = [0000 00]

Resolution = [00, 01,

10]

10
11
1

A3/A7 Element Identifier = [1AH]

Length = <variable>

Privacy Mask Information {1+:

Reserved

Privacy Mask Type = [00001,00010]

Status

Available

= [0]

(public, private)

= [0,1]

= [0,1]

Privacy Mask Length = <variable>

(MSB)

j
j+1

Privacy Mask = <any value>

j+2

(LSB)

} Privacy Mask Information

(MSB)

A3 Signaling Address:

A1 Element Identifier = [49H]

Length = [07H]

Address Type = [01H] (IPv4)

TCP Port

4
(LSB)

(MSB)

5
6

A3 Address = <any value>

7
8
(LSB)

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

9
1
2
3

Correlation Value = <any value>

4
5

587

TIA/EIA/IS-2001

-- Continued on next page --

588

TIA/EIA/IS-2001

1
-- Continued from previous page -(LSB)

SDU ID:

A1 Element Identifier = [4CH]

Length = [01H to 06H]

(MSB)

SDU ID = <any value>

(LSB)

Length = [06H-08H] (10-15 digits)

Odd/even
Indicator

m
1

Mobile Identity (IMSI): A1 Element Identifier = [0DH]

Identity Digit 1 = [0H-9H] (BCD)

2
Type of Identity

= [110] (IMSI)

= [1,0]
Identity Digit 3 = [0H-9H] (BCD)

Identity Digit 2 = [0H-9H] (BCD)

Identity Digit N+1 = [0H-9H] (BCD)

Identity Digit N = [0H-9H] (BCD)

= [1111] (if even number of digits)

Identity Digit N+2 = [0H-9H] (BCD)

n+1

Mobile Identity (ESN): A1 Element Identifier = [0DH]

Length = [05H]

Identity Digit 1 = [0000]

Odd/even
Indicator

Type of Identity

= [101] (ESN)

= [0]
(MSB)

4
ESN = <any value>

5
6
(LSB)

Cell Identifier List:

7
1

A1 Element Identifier = [071AH]

Length = <variable>

Cell Discriminator Type = [07H]

Cell Identification{1+:
(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

} Cell Identification
-- Continued on next page --

589

j+2
j+3
j+4

TIA/EIA/IS-2001

1
-- Continued from previous page -

Forward Burst Radio Info:

A3/A7 Element Identifier = [11H]

Length = [06H]
Coding Indicator

Reserved

QOF Mask

= [00, 01]

= [0]

= [00 11]

2
Forward Code Channel Index
(high part)

= [000 111]
Forward Code Channel Index (low part) = [00H FFH]

Pilot PN Code (low part) = [00H FFH]

Pilot PN
Code (high
part)

Reserved

Forward Supplemental Channel Rate

= [000]

= [0000 1111]

[0,1]
Reserved

Forward Supplemental Channel Start Time

= [000]

= [0 0000 1 1111]

Reserved

Start Time Unit

Forward Supplemental Channel Duration

= [0]

= [000 111]

= [0000 1111]

Reverse Burst Radio Info:

Reserved = [00]

Reverse Supplemental Channel Rate

= [00, 01]

= [0000 1111]
Reverse Supplemental Channel Start Time = [00H FFH]

Rev
Walsh
ID

8
1

A3/A7 Element Identifier = [12H]

Length = [04H]
Coding Indicator

Start Time Unit

Reverse Supplemental Channel Duration

= [000 111]

= [0000 1111]

= <any
value>
(ignored)

A7 Destination ID:

A3/A7 Element Identifier = [2DH]

Length = [02H]
(MSB)

A7 Destination ID = <any value>

3
(LSB)

590

TIA/EIA/IS-2001

6.1.12.18

2
3
4
5
6
7

A7-Burst Response
This A7 interface message is sent from the target BS to the source BS to respond to a
request for reservation of resources to support a traffic burst. Note that one or more
A7-Burst Response messages may be used to respond to a single A7-Burst Request
message. A result (committed or uncommitted) must be provided for all cells in the
A7-Burst Request message. Each A7-Burst Response message includes at most one
committed cell.

Information Element

Section
Element Direction
Reference

Type

Message Type II

6.2.2.5

Target BS -> Source BS

Call Connection Reference

6.2.2.98

Target BS -> Source BS

Correlation ID

6.2.2.108

Target BS -> Source BS

Cell Identifier List (Committed)

6.2.2.21

Target BS -> Source BS

Cell Identifier List (Uncommitted)

6.2.2.21

Target BS -> Source BS

Forward Burst Radio Info

6.2.2.56

Target BS -> Source BS

Reverse Burst Radio Info

6.2.2.57

Target BS -> Source BS

A7 Destination ID

6.2.2.173

Target BS -> Source BS

O
O
O

O
O
O

8
9

a.

If this element was included in the A7-Burst Request message, the

value shall be returned in this message.

10
11
12
13

b.

This element is only included when this message includes

information about forward link radio resources that have been
reserved at the cell indicated in the Cell Identifier List
(Committed) element.

14
15
16
17

c.

This element is only included when this message includes

information about reverse link radio resources that have been
reserved at the cell indicated in the Cell Identifier List
(Committed) element.

18
19
20
21

d.

This element is only included when this message includes

information about a cell with radio resources reserved for the
forward and/or reverse burst indicated in the Forward and/or
Reverse Burst Radio Info element.

22
23
24
25
26
27
28

e.

This element is only included when this message includes one or

more requested cells that are not being reserved. The allowable
cause values are: OAM&P intervention, Equipment failure, No
radio resource available, BS not equipped, Ciphering algorithm
not supported, Private Long Code not available or not supported,
Requested MUX option or rates not available, Requested privacy
configuration not available.

29
30
31

f.

This element is required if an A7 Originating ID value was

included in an A7-Handoff Request message previously received
from the source BS for this call association.

591

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A7-Burst Response message:
7

Message Type II = [91H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

6
1

Cell Identifier List (committed): A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

} Cell Identification
-- Continued on next page --

592

j+2
j+3
j+4

TIA/EIA/IS-2001

1
-- Continued from previous page -

Cell Identifier List (uncommitted):

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification

Forward Burst Radio Info:

A3/A7 Element Identifier = [11H]

Length = [06H]
Coding Indicator

Reserved

QOF Mask

= [00, 01]

= [0]

= [00 11]

1
2

Forward Code Channel Index

(high part)

= [000 111]
Forward Code Channel Index (low part) = [00H FFH]

Pilot PN Code (low part) = [00H FFH]

Pilot PN
Code (high
part)

Reserved

Forward Supplemental Channel Rate

= [000]

= [0000 1111]

[0,1]
Reserved

Forward Supplemental Channel Start Time

= [000]

= [0 0000 1 1111]

Reserved

Start Time Unit

Forward Supplemental Channel Duration

= [0]

= [000 111]

= [0000 1111]

Reverse Burst Radio Info:

A3/A7 Element Identifier = [12H]

Length = [04H]
Coding Indicator

Reserved = [00]

= [0000 1111]
Reverse Supplemental Channel Start Time = [00H FFH]

Rev
Walsh
ID

Reverse Supplemental Channel Rate

= [00, 01]

Start Time Unit

Reverse Supplemental Channel Duration

= [000 111]

= [0000 1111]

= [0,1]
-- Continued on next page --

593

4
5

TIA/EIA/IS-2001

1
-- Continued from previous page -

A7 Destination ID:

A3/A7 Element Identifier = [2DH]

Length = [02H]
(MSB)

A7 Destination ID = <any value>

3
(LSB)

594

TIA/EIA/IS-2001

6.1.12.19

2
3

A7-Burst Commit
This A7 interface message is sent from the source BS to the target BS to commit a set
of resources that had been reserved to support a traffic burst.

Information Element

Section
Element Direction
Reference

Type

Message Type II

6.2.2.5

Source BS -> Target BS

Call Connection Reference

6.2.2.98

Source BS -> Target BS

Correlation ID

6.2.2.108

Source BS -> Target BS

Cell Identifier List (Forward)

6.2.2.21

Cell Identifier List (Reverse)

Source BS -> Target BS

Ob

6.2.2.21

Source BS -> Target BS

Ob

Forward Burst Radio Info

6.2.2.56

Source BS -> Target BS

Oc

Reverse Burst Radio Info

6.2.2.57

Source BS -> Target BS

Od

IS-2000 Forward Power Control Mode

6.2.2.177

Source BS -> Target BS

Oe

IS-2000 FPC Gain Ratio Info

6.2.2.178

Source BS -> Target BS

Of

A7 Destination ID

6.2.2.173

Source BS -> Target BS

4
5

a.

Optionally included by the source BS. If included, the value shall

be saved and used by the target BS on A3 signaling messages.

6
7

b.

The length field of this element shall be set to 0 if no resources

are to be allocated in the indicated direction.

8
9

c.

This element is only included when forward link radio resources

are to be allocated to the burst.

10
11

d.

This element is only included when reverse link radio resources

are to be allocated to the burst.

12
13
14

f.

This element shall be included when supporting a secondary

power control subchannel. It provides information used for
forward gain equalization for the SCH.

15
16
17
18
19

e.

This element shall be included when supporting a secondary

power control subchannel for the SCH. The FPC_MODE value
shall go into effect at the earlier of the burst start times indicated
in the Forward Burst Radio Info and/or Reverse Burst Radio Info
element.

20
21
22

g.

This element is required if an A7 Originating ID value was

included in an A7-Handoff Request Ack message previously
received from the target BS for this call association.

595

TIA/EIA/IS-2001

The following table shows the bitmap layout for the A7-Burst Commit message:
7

Message Type II = [92H]

Call Connection Reference:

A1 Element Identifier = [3FH]

Length = [08H]
(MSB)

Market ID = <any value>

3
(LSB)

(MSB)

Octet

Generating Entity ID = <any value>

4
5

(LSB)
(MSB)

6
7

Call Connection Reference = <any value>

8
9
(LSB)

10
1

Correlation ID: A3/A7 Element Identifier = [13H]

Length = [04H]

(MSB)

3
Correlation Value = <any value>

4
5
(LSB)

Cell Identifier List (Forward):

6
1

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

Sector = [0H-FH] (0H = Omni)

} Cell Identification
-- Continued on next page --

596

j+2
j+3
j+4

TIA/EIA/IS-2001

1
-- Continued from previous page -

Cell Identifier List (Reverse):

A1 Element Identifier = [1AH]

Length = <variable>

Cell Identification Discriminator = [07H]

Cell Identification {1+:

(MSB)

j
MSCID = <any value>

j+1
(LSB)

(MSB)

Cell = [001H-FFFH]
(LSB)

j+2
j+3

Sector = [0H-FH] (0H = Omni)

j+4

} Cell Identification

Forward Burst Radio Info:

A3/A7 Element Identifier = [11H]

Length = [06H]
Coding Indicator

Reserved

QOF Mask

= [00, 01]

= [0]

= [00 11]

1
2

Forward Code Channel Index

(high part)

= [000 111]
Forward Code Channel Index (low part) = [00H FFH]

Pilot PN Code (low part) = [00H FFH]

Pilot PN
Code (high
part)

Reserved

Forward Supplemental Channel Rate

= [000]

= [0000 1111]

[0,1]
Reserved

Forward Supplemental Channel Start Time

= [000]

= [0 0000 1 1111]

Reserved

Start Time Unit

Forward Supplemental Channel Duration

= [0]

= [000 111]

= [0000 1111]

Reverse Burst Radio Info:

A3/A7 Element Identifier = [12H]

Length = [04H]
Coding Indicator

Reserved = [00]

= [0000 1111]
Reverse Supplemental Channel Start Time = [00H FFH]

Rev
Walsh
ID

Reverse Supplemental Channel Rate

= [00, 01]

Start Time Unit

Reverse Supplemental Channel Duration

= [000 111]

= [0000 1111]

= [0,1]
-- Continued on next page --

597

4
5

TIA/EIA/IS-2001

1
-- Continued from previous page -

IS-2000 Forward Power Control Mode:

A3/A7 Element Identifier = [14H]

Length = [02H]

Reserved = [0000 0]

FPC_MODE = [000 011]

ACTION_TIME = [00H] (ignored)

IS-2000 FPC Gain Ratio Info:

Length = [08H]

Initial Gain Ratio = [00H FFH]

Count of Gain Ratio Pairs =

[011]

Min Gain Ratio 1 = [00H FFH]

Max Gain Ratio 1 = [00H FFH]

Min Gain Ratio 2 = [00H FFH]

Max Gain Ratio 2 = [00H FFH]

Min Gain Ratio 3 = [00H FFH]

Max Gain Ratio 3 = [00H FFH]

10

A7 Destination ID:

A3/A7 Element Identifier = [2DH]

Length = [02H]
(MSB)

3
4

A3/A7 Element Identifier = [15H]

Gain Adjust Step Size = [0H FH]

Reser
ved =
[0]

A7 Destination ID = <any value>

3
(LSB)

598

TIA/EIA/IS-2001

6.2

Information Element Definitions

2
3

This chapter contains the coding of the signaling elements used in the messages
defined in Chapter 6.

4
5
6
7

The definitions in the following subsections are for informational purposes only.
Parameter usage may vary per message in that only a subset of the defined values may
be applicable in a particular message. Therefore, the allowed values are specified per
message in the subsections of section 6.1.

6.2.1

Generic Information Element Encoding

6.2.1.1

Conventions

10
11

The following conventions are assumed for the sequence of transmission of bits and
bytes:

12
13
14

Each bit position is marked as 0 to 7. Bit 0 is the least significant bit and is
transmitted first. However, for the A10/A11 interface, bit 0 is the most
significant bit and is transmitted first.

15
16

In a message, octets are identified by number. Octet 1 is transmitted first, then

octet 2, etc.

17
18

For variable length elements, a length indicator is included. This indicates the number of
octets following in the element.

19
20

The definition of whether an information element is mandatory or optional is specified in

Chapter 6.1.

21
22
23
24
25
26

All information elements of BSMAP messages shall include their information element
identifier (IEI). Mandatory information elements of DTAP messages, except as noted for
Type 1 elements (see 6.2.1.3), shall not include their IEI. Optional information elements
of DTAP messages shall include their IEI. Exceptions are explicitly identified in the
message definitions. In all other cases of signaling messages on the A1, A3, A7, A9
and A11. Interfaces, the Information Element Identifier is included.

27

All spare and reserved bits are set to 0, unless otherwise indicated.

28
29

For future expansion purposes, some of these information elements have fields within
them that have been reserved.

30
31
32
33

The extensions for the A11 interface messages are defined in the TLV (Type-LengthValue) format. The Type field indicates the type of the extension. Length field indicates
the length (in octets) of the extension, not including the Type and Length fields. The
value field contains the information specific to the Type of the extension.

600

TIA/EIA/IS-2001

6.2.1.2

Information Element Identifiers

2
3
4
5

The following tables contain lists of all elements that make up the messages defined in
Chapter 6. The tables include the Information Element Identifier (IEI) coding which
distinguishes one element from another. The tables also include a section and page
reference where the element coding can be found.

6
7
8
9

A11 interface information elements, other than the extensions, are position specific,
hence do not include the Information Element Identifier (IEI). The A11 interface
extensions are, however, identified by a Type field, which distinguishes one extension
from the others.

10
11

Elements used in messages on the A1 interface are contained in Table 6-2 sorted by
name and in Table 6-3 sorted by identifier value.

12
13
14
15
16

Elements used in messages on the A3 and A7 interfaces are contained Table 6-4 sorted
by element name and in Table 6-5 sorted by identifier value. These two tables contain a
column indicating on which interface(s) the element is used. Where an element is used
on the A1 interface as well as one or both of the A3 interface, the element identifier
value is identical for all usage of the same element.

17
18

Elements used on messages on the A11 interface are contained in Table 6-7, sorted by
name.

19
20
21

All elements that are used on the A1 interface are chosen from the A1 Information
Element Identifier range of values represented in Table 6-3 even if that same element is
also used on another interface.

22
23
24
25
26

All elements that are used on interfaces other than the A1 interface, and are not used in
any message on the A1 interface are chosen from the A3/A7 Information Element
Identifier range of values represented in Table 6 - 1 - A3/A7 Information Element
Identifiers Sorted by Name and Table 6 - 2 - A3/A7 Information Element Identifiers
Sorted by Identifier value.

27
28
29
30

If an element is used on another interface in addition to the A1 interface, a copy of the

A1 Information Element Identifier value is placed in Table 6 - 3 - A3/A7 Information
Element Identifiers Sorted by Name and Table 6 - 4 - A3/A7 Information Element
Identifiers Sorted by Identifier value.

31

601

TIA/EIA/IS-2001

Table 6 - 2 - A1 Information Element Identifiers Sorted by Name

Element Name

Identifier
(Hex)

Identifier
(Binary)

Reference

ADDS User Part

3DH

0011 1101

6.2.2.67

Authentication Challenge Parameter

41H

0100 0001

6.2.2.45

28H

0010 1000

6.2.2.42

Authentication Data

59H

0101 1001

6.2.2.137

Authentication Event

4AH

0100 1010

6.2.2.114

Authentication Parameter COUNT

40H

0100 0000

6.2.2.47

Authentication Response Parameter

42H

0100 0010

6.2.2.46

Called Party ASCII Number

5BH

0101 1011

6.2.2.105

Called Party BCD Number

5EH

0101 1110

6.2.2.52

Calling Party ASCII Number

4BH

0100 1011

6.2.2.37

Cause

04H

0000 0100

6.2.2.19

Cause Layer 3

08H

0000 1000

6.2.2.55

CDMA Serving One Way Delay

0CH

0000 1100

6.2.2.79

Cell Identifier

05H

0000 0101

6.2.2.20

Cell Identifier List

1AH

0001 1010

6.2.2.21

Channel Number

23H

0010 0011

6.2.2.6

Channel Type

0BH

0000 1011

6.2.2.7

Circuit Group

19H

0001 1001

6.2.2.148

Circuit Identity Code

01H

0000 0001

6.2.2.22

Circuit Identity Code Extension

24H

0010 0100

6.2.2.23

Classmark Information Type 2

12H

0001 0010

6.2.2.15

CM Service Type

9XHa

1001 xxxxa

6.2.2.51

Data Link Connection Identifier (DLCI)

none b

none b

6.2.2.2

Downlink Radio Environment

29H

0010 1001

6.2.2.25

Encryption Information

0AH

0000 1010

6.2.2.12

Extended Handoff Direction Parameters

10H

0001 0000

6.2.2.73

Authentication
(RANDC)

Confirmation

Parameter

602

TIA/EIA/IS-2001

(cont.) - A1 Information Element Identifiers Sorted by Name

Element Name

Identifier
(Hex)

Identifier
(Binary)

Reference

Handoff Power Level

26H

0010 0110

6.2.2.31

Hard Handoff Parameters

16H

0001 0110

6.2.2.63

IS-2000 Channel Identity

09H

0000 1001

6.2.2.34

IS-2000 Mobile Capabilities

11H

0001 0001

6.2.2.70

IS-2000 Non-Negotiable Service Configuration

Record

0FH

0000 1111

6.2.2.69

IS-2000 Service Configuration Record

0EH

0000 1110

6.2.2.68

IS-2000 Cause Value

62H

0110 0010

6.2.2.110

IS-95 Channel Identity

22H

0010 0010

6.2.2.10

IS-95 MS Measured Channel Identity

64H

0110 0100

6.2.2.36

Layer 3 Information

17H

0001 0111

6.2.2.38

Location Area Identification

13H

0001 0011

6.2.2.43

Message Discrimination

none

none

6.2.2.1

Message Type

none

none

6.2.2.4

Message Waiting Indication

38H

0011 1000

6.2.2.48

Mobile Identity

0DH

0000 1101

6.2.2.16

MS Information Records

15H

0001 0101

6.2.2.72

PACA Order

5FH

0101 1111

6.2.2.150

PACA Reorigination Indicator

60H

0110 000

6.2.2.151

PACA Timestamp

4EH

0100 1110

6.2.2.149

PDSN IP Address

14H

0001 0100

6.2.2.30

Power Down Indicator

A2H

1010 0010

6.2.2.60

Priority

06H

0000 0110

6.2.2.18

none b

none b

6.2.2.39

Protocol Type

18H

0001 1000

6.2.2.71

Quality of Service Parameters

07H

0000 0111

6.2.2.54

Radio Environment and Resources

1DH

0001 1101

6.2.2.82

Registration Type

1FH

0001 1111

6.2.2.61

Reject Cause

44H

0100 0100

6.2.2.44

none b

none b

6.2.2.40

Response Request

1BH

0001 1011

6.2.2.35

RF Channel Identity

21H

0010 0001

6.2.2.8

Service Option

03H

0000 0011

6.2.2.66

Protocol Discriminator

Reserved - Octet

603

TIA/EIA/IS-2001

(cont.) - A1 Information Element Identifiers Sorted by Name

Element Name

Identifier
(Hex)

Identifier
(Binary)

Reference

SID

32H

0011 0010

6.2.2.9

Signal

34H

0011 0100

6.2.2.50

Slot Cycle Index

35H

0011 0101

6.2.2.17

Software Version

31H

0011 0001

6.2.2.65

Tag

33H

0011 0011

6.2.2.62

Transcoder Mode

1CH

0001 1100

6.2.2.58

User Zone ID

02H

0000 0010

6.2.2.32

Voice Privacy Request

A1H

1010 0001

6.2.2.13

2
3

a.

This is a type 1 information element (see section 6.2.1.3). The xxxx (X under
the hex identifier column) is data.

4
5

b.

This is a type 3 information element (see section 6.2.1.3) that is contained

as a mandatory element in a DTAP message.

604

TIA/EIA/IS-2001

Table 6 - 3 - A1 Information Element Identifiers Sorted by Identifier Value

Element Name

Identifier
(Hex)

Identifier
(Binary)

Reference

Circuit Identity Code

01H

0000 0001

6.2.2.22

User Zone ID

02H

0000 0010

6.2.2.32

Service Option

03H

0000 0011

6.2.2.66

Cause

04H

0000 0100

6.2.2.19

Cell Identifier

05H

0000 0101

6.2.2.20

Priority

06H

0000 0110

6.2.2.18

Quality of Service Parameters

07H

0000 0111

6.2.2.54

Cause Layer 3

08H

0000 1000

6.2.2.55

IS-2000 Channel Identity

09H

0000 1001

6.2.2.34

Encryption Information

0AH

0000 1010

6.2.2.12

Channel Type

0BH

0000 1011

6.2.2.7

CDMA Serving One Way Delay

0CH

0000 1100

6.2.2.79

Mobile Identity

0DH

0000 1101

6.2.2.16

IS-2000 Service Configuration Record

0EH

0000 1110

6.2.2.68

IS-2000 Non-Negotiable Service Configuration

Record

0FH

0000 1111

6.2.2.69

Extended Handoff Direction Parameters

10H

0001 0000

6.2.2.73

IS-2000 Mobile Capabilities

11H

0001 0001

6.2.2.70

Classmark Information Type 2

12H

0001 0010

6.2.2.15

Location Area Identification

13H

0001 0011

6.2.2.43

PDSN IP Address

14H

0001 0100

6.2.2.30

MS Information Records

15H

0001 0101

6.2.2.72

Hard Handoff Parameters

16H

0001 0110

6.2.2.63

Layer 3 Information

17H

0001 0111

6.2.2.38

Protocol Type

18H

0001 1000

6.2.2.71

Circuit Group

19H

0001 1001

6.2.2.148

Cell Identifier List

1AH

0001 1010

6.2.2.21

Response Request

1BH

0001 1011

6.2.2.35

605

TIA/EIA/IS-2001

(cont.) - A1 Information Element Identifiers Sorted by Identifier Value

Element Name

Identifier
(Hex)

Identifier
(Binary)

Reference

Transcoder Mode

1CH

0001 1100

6.2.2.58

Radio Environment and Resources

1DH

0001 1101

6.2.2.82

(unused available element identifier value)

1EH

0001 1110

Registration Type

1FH

0001 1111

(unused available element identifier value)

20H

0010 0000

RF Channel Identity

21H

0010 0001

6.2.2.8

IS-95 Channel Identity

22H

0010 0010

6.2.2.10

Channel Number

23H

0010 0011

6.2.2.6

Circuit Identity Code Extension

24H

0010 0100

6.2.2.23

(unused available element identifier value)

25H

0010 0101

Handoff Power Level

26H

0010 0110

(unused available element identifier value)

27H

0010 0111

Authentication
(RANDC)

28H

0010 1000

6.2.2.42

29H

0010 1001

6.2.2.25

2AH 30H

0010 1010 -

Confirmation

Parameter

Downlink Radio Environment

(unused available element identifier values)

6.2.2.61

6.2.2.31

0011 0000
Software Version

31H

0011 0001

6.2.2.65

SID

32H

0011 0010

6.2.2.9

Tag

33H

0011 0011

6.2.2.62

Signal

34H

0011 0100

6.2.2.50

Slot Cycle Index

35H

0011 0101

6.2.2.17

606

TIA/EIA/IS-2001

(cont.) - A1 Information Element Identifiers Sorted by Identifier Value

Element Name

Identifier
(Hex)

Identifier
(Binary)

(unused available element identifier value)

36H 37H

0011 0110 -

Reference

0011 0111
Message Waiting Indication
(unused available element identifier values)

38H

0011 1000

39H 3CH

0011 1001 -

6.2.2.48

0011 1100
ADDS User Part

3DH

0011 1101

(unused available element identifier value)

3EH

0011 1110

(unused available element identifier value)

3FH

0011 1111

Authentication Parameter COUNT

40H

0100 0000

6.2.2.47

Authentication Challenge Parameter

41H

0100 0001

6.2.2.45

Authentication Response Parameter

42H

0100 0010

6.2.2.46

(unused - available element identifier value)

43H

0100 0011

Reject Cause

44H

0100 0100

45H 47H

0100 0101 -

(unused - available element identifier value)

6.2.2.67

6.2.2.44

0100 0111
(unused available element identifier value)

48H

0100 1000

(unused available element identifier value)

49H

0100 1001

Authentication Event

4AH

0100 1010

6.2.2.114

Calling Party ASCII Number

4BH

0100 1011

6.2.2.37

(unused available element identifier value)

4CH

0100 1100

(unused - available element identifier value)

4DH

0100 1101

PACA Timestamp

4EH

0100 1110

4FH 58H

0100 1111 -

(unused - available element identifier values)

0101 1000

607

6.2.2.149

TIA/EIA/IS-2001

(cont.) - A1 Information Element Identifiers Sorted by Identifier Value

Element Name

Identifier
(Hex)

Identifier
(Binary)

Reference

Authentication Data

59H

0101 1001

(unused - available element identifier value)

5AH

0101 1010

Called Party ASCII Number

5BH

0101 1011

(unused - available element identifier value)

5CH

0101 1100

(unused available element identifier value)

5DH

0101 1101

Called Party BCD Number

5EH

0101 1110

6.2.2.52

PACA Order

5FH

0101 1111

6.2.2.150

PACA Reorigination Indicator

60H

0110 0000

(unused available element identifier value)

61H

0110 0001

IS-2000 Cause Value

62H

0110 0010

(unused available element identifier value)

63H

0110 0011

IS-95 MS Measured Channel Identity

64H

0110 0100

65H 7FH

0110 0101 0111 1111

(unused available element identifier values)

608

6.2.2.137

6.2.2.105

6.2.2.151

6.2.2.110

6.2.2.36

TIA/EIA/IS-2001

(cont.) - A1 Information Element Identifiers Sorted by Identifier Value

Element Name

Identifier
(Hex)

Identifier
(Binary)

Reference

(unused - available element identifier value)

8XHa

1000 xxxxa

CM Service Type

9XHa

1001 xxxxa

(unused - available element identifier value)

A0H

1010 0000

Voice Privacy Request

A1H

1010 0001

6.2.2.13

Power Down Indicator

A2H

1010 0010

6.2.2.60

A3H - AFH

1010 0011 -

Type 1 Information Elements

6.2.2.51

Type 2 Information Elements

(unused - available type 2 element identifier

values)

1101 1111

Additional Type 1 Information Elements

(unused - available type 1 element identifier
value)

EXHa FXHa

1110 xxxxa -

Message Discrimination

none

none

6.2.2.1

Message Type

none

none

6.2.2.4

Data Link Connection Identifier (DLCI)

none b

none b

6.2.2.2

Protocol Discriminator

none b

none b

6.2.2.39

Reserved - Octet

none b

none b

6.2.2.40

1111 xxxxa

Information Elements without Identifiers

2
3
4
5

a.
b.

This is a type 1 information element (see section 6.2.1.3). The xxxx (X under
the hex identifier column) is data.
This is a type 3 information element (see section 6.2.1.3) that is contained
as a mandatory element in a DTAP message.

609

TIA/EIA/IS-2001

Table 6 - 4 - A3/A7 Information Element Identifiers Sorted by Name

Element Name

Identifier

Interface(s)

A3 Connect Ack Information

1CH

A3

6.2.2.145

A3 Connect Information

1BH

A3

6.2.2.144

A3 Destination ID

55H

A3

6.2.2.175

A3 Drop Information

1EH

A3

6.2.2.147

A3 Originating ID

3EH

A3

6.2.2.174

A3 Remove Information

20H

A3

6.2.2.146

A3 Signaling Address

49H

A7

6.2.2.90

A3 Traffic Circuit ID

03H

A3

6.2.2.96

A7 Control

1FH

A7

6.2.2.97

A7 Destination ID

2DH

A7

6.2.2.173

A7 Originating ID

2CH

A7

6.2.2.172

Air Interface Message

21H

A7

6.2.2.152

Band Class

5DH

A1, A7

6.2.2.106

BSC ID

04H

A7

6.2.2.125

Call Connection Reference

3FH

A1, A3, A7

6.2.2.98

Cause

08H

A1, A7, A9

6.2.2.19

Cause List

19H

A3, A7

6.2.2.142

CDMA Long Code Transition Info

0EH

A3

6.2.2.128

CDMA Serving One-Way Delay

0CH

A1, A7

6.2.2.79

Cell Identifier

0AH

A7

6.2.2.20

Cell Identifier List

1AH

A1, A3, A7

6.2.2.21

Cell Information Record

02H

A3

6.2.2.89

Channel Element ID

17H

A3

6.2.2.132

Channel Element Status

18H

A3

6.2.2.141

Correlation ID

13H

A3, A7, A9

6.2.2.108

Downlink Radio Environment

29H

A1, A7

6.2.2.25

Forward Burst Radio Info

11H

A7

6.2.2.56

IS-2000 FPC Gain Ratio Info

15H

A7

6.2.2.178

IS-2000 Mobile Pilot Gain

01H

A3

6.2.2.180

IS-2000 Power Control Info

0BH

A7

6.2.2.176

IS-2000 Forward Power Control Mode

14H

A7

6.2.2.177

IS-2000 Service Configuration Record

10H

A1,A7

6.2.2.68

IS-95 Channel Identity

22H

A1, A7

6.2.2.10

Layer 2 Ack Request/Results

23H

A7

6.2.2.153

610

Reference

TIA/EIA/IS-2001

Table 6 - 5 - A3/A7 Information Element Identifiers Sorted by Name (cont.)

2
Mobile Identity

0DH

A1, A7

6.2.2.16

Neighbor List

48H

A7

6.2.2.83

One Way Propagation Delay Record

09H

A3

6.2.2.119

Physical Channel Info

07H

A7

6.2.2.14

PMC Cause

05H

A3

6.2.2.99

Privacy Info

1DH

A7

6.2.2.143

Quality of Service Parameters

0FH

A1, A7, A9

6.2.2.54

Reverse Burst Radio Info

12H

A7

6.2.2.57

Reverse Pilot Gating Rate

06H

A3

6.2.2.33

SDU ID

4CH

A3, A7

6.2.2.91

Service Configuration Record

61H

A7

6.2.2.109

Software Version

31H

A7

All other values are reserved.

3

611

6.2.2.65

TIA/EIA/IS-2001

Table 6 - 6 - A3/A7 Information Element Identifiers Sorted by Identifier value

Element Name

Identifier

Interface(s)

IS-2000 Mobile Pilot Gain

01H

A3

6.2.2.180

Cell Information Record

02H

A3

6.2.2.89

A3 Traffic Circuit ID

03H

A3

6.2.2.96

BSC ID

04H

A7

6.2.2.125

PMC Cause

05H

A3

6.2.2.99

Reverse Pilot Gating Rate

06H

A3

6.2.2.33

Physical Channel Info

07H

A7

6.2.2.14

Cause

08H

A1, A7, A9

6.2.2.19

One Way Propagation Delay Record

09H

A3

6.2.2.119

Cell Identifier

0AH

A1, A7

6.2.2.20

IS-2000 Power Control Info

0BH

A7

6.2.2.14

CDMA Serving One-Way Delay

0CH

A1, A7

6.2.2.79

Mobile Identity

0DH

A1, A7

6.2.2.16

CDMA Long Code Transition Info

0EH

A3

6.2.2.128

Quality of Service Parameters

0FH

A1, A7, A9

6.2.2.54

IS-2000 Service Configuration Record

10H

A1, A7

6.2.2.68

Forward Burst Radio Info

11H

A7

6.2.2.56

Reverse Burst Radio Info

12H

A7

6.2.2.57

Correlation ID

13H

A3, A7

6.2.2.108

IS-2000 Power Control Mode

14H

A3

6.2.2.64

IS-2000 FPC Gain Ratio Info

15H

A7

6.2.2.178

Channel Element ID

17H

A3

6.2.2.132

Channel Element Status

18H

A3

6.2.2.141

Cause List

19H

A3, A7

6.2.2.142

612

Reference

TIA/EIA/IS-2001

Table 6 - 6 (cont.) - A3/A7 Information Element Identifiers Sorted by Identifier value

Element Name

Identifier

Interface(s)

Cell Identifier List

1AH

A1, A7

6.2.2.21

A3 Connect Information

1BH

A3

6.2.2.144

A3 Connect Ack Information

1CH

A3

6.2.2.145

Privacy Info

1DH

A7

6.2.2.143

A3 Drop Information

1EH

A3

6.2.2.147

A7 Control

1FH

A7

6.2.2.97

A3 Remove Information

20H

A3

6.2.2.146

Air Interface Message

21H

A7

6.2.2.152

IS-95 Channel Identity

22H

A1, A7

6.2.2.10

Layer 2 Ack Request/Results

23H

A7

6.2.2.153

(unused - available element identifier value)

24H

Downlink Radio Environment

29H

A1, A7

6.2.2.25

A7 Originating ID

2CH

A7

6.2.2.172

A7 Destination ID

2DH

A7

6.2.2.173

Software Version

31H

A7

6.2.2.65

A3 Originating ID

3EH

A3

6.2.2.174

A3 Destination ID

55H

A3

6.2.2.175

Call Connection Reference

3FH

A1, A3, A7

6.2.2.98

Neighbor List

48H

A7

6.2.2.83

A3 Signaling Address

49H

A7

6.2.2.90

SDU ID

4CH

A3, A7

6.2.2.91

Band Class

5DH

A1, A7

6.2.2.106

Service Configuration Record

61H

A1, A7

6.2.2.109

All other values are reserved.

613

Reference

TIA/EIA/IS-2001

Table 6 - 7 - A9 Information Element Identifiers Sorted by Identifier Name

Element Name

Identifier

Interface(s)

Reference

A8 Traffic ID

08H

A9

6.2.2.170

A9 BSC_ID

06H

A9

6.2.2.169

A9 Indicators

05H

A9

6.2.2.171

Call Connection Reference

3FH

A3, A7, A9

6.2.2.98

Cause

04H

A1, A7, A9

6.2.2.19

CON_REF

01H

A9

6.2.2.168

Correlation ID

13H

A3, A7, A9

6.2.2.108

Data Count

09H

A9

6.2.2.179

Mobile Identity

0DH

A1, A7, A9

6.2.2.16

Quality of Service Parameters

07H

A1, A7, A9

6.2.2.54

PDSN IP Address

14H

A1, A9

6.2.2.30

Service Option

03H

A1, A9

6.2.2.66

User Zone ID

02H

A1, A9

6.2.2.32

2
3

Table 6 - 8 - A9 Information Element Identifiers Sorted by Identifier Value

Element Name

Identifier

Interface(s)

CON_REF

01H

A9

6.2.2.168

User Zone ID

02H

A1, A9

6.2.2.66

Service Option

03H

A1, A9

6.2.2.66

Cause

04H

A1, A9

6.2.2.19

A9 Indicators

05H

A9

6.2.2.171

A9 BSC_ID

06H

A9

6.2.2.169

Quality of Service Parameters

07H

A1, A9

6.2.2.54

A8 Traffic ID

08H

A9

6.2.2.170

Data Count

09H

A9

6.2.2.179

Mobile Identity

0DH

A1, A7, A9

6.2.2.16

Correlation ID

13H

A3, A7, A9

6.2.2.108

PDSN IP Address

14H

A1, A9

6.2.2.30

Call Connection Reference

3FH

A3, A7, A9

6.2.2.98

614

Reference

TIA/EIA/IS-2001

Table 6 - 9 - A11 Information Element Identifiers Sorted by Name

Element Name

Identifier

Interface(s)

A11 Message Type

None

A11

6.2.2.154

Care-of-Address

None

A11

6.2.2.159

Code

None

A11

6.2.2.161

Flags

None

A11

6.2.2.155

Home Address

None

A11

6.2.2.157

Home Agent

None

A11

6.2.2.158

Identification

None

A11

6.2.2.160

Lifetime

None

A11

6.2.2.156

Mobile-Home Authentication Extension

20 H

A11

6.2.2.163

Registration Update Authentication Extension

28 H

A11

6.2.2.164

Session Specific Extension

27H

A11

6.2.2.165

None

A11

6.2.2.162

26H

A11

6.2.2.166

Status
Vendor/Organization Specific Extension

Reference

All other values are reserved.

2
3

Table 6 - 10 - A11 Information Element Identifiers Sorted by Value

Element Name

Identifier

Interface(s)

A11 Message Type

None

A11

6.2.2.154

Care-of-Address

None

A11

6.2.2.159

Code

None

A11

6.2.2.161

Flags

None

A11

6.2.2.155

Home Address

None

A11

6.2.2.157

Home Agent

None

A11

6.2.2.158

Identification

None

A11

6.2.2.160

Lifetime

None

A11

6.2.2.156

Status

None

A11

6.2.2.162

Mobile-Home Authentication Extension

20 H

A11

6.2.2.163

Vendor/Organization Specific Extension

26H

A11

6.2.2.166

Session Specific Extension

27H

A11

6.2.2.165

Registration Update Authentication Extension

28 H

A11

6.2.2.164

All other values are reserved.

4

615

Reference

TIA/EIA/IS-2001

6.2.1.3

A1 Interface Information Element Types

This section describes the four information element types used on the A1 Interface.

Two main categories of information elements are defined:

Information elements with fixed length;

Information elements with variable length

6
7

The number of octets in fixed length elements is previously defined: a fixed value is
associated with the element identifier.

8
9
10

Variable length elements shall include the length field immediately following the element
identifier when present. When the element identifier is absent, the length field occupies
the first octet of the message.

11

Four types of information elements are defined:

12

Information elements with 1/2 octet of content (Type 1);

13

Information elements with 0 octets of content (Type 2);

14
15

Information elements with fixed length and at least one octet of

content (Type 3);

16

Information elements with variable length (Type 4).

17
18

Information element Response Request (1BH) is an exception to the rules specified in

this section.

616

TIA/EIA/IS-2001

Type 1 Information Element

2
3
4
5
6

Type 1 information elements provide the information element identifier in bit positions 6,
5, 4. The value 0 1 0 in these bit positions is reserved for Type 2 information elements
which together with this provide the information element identifier in bit positions
3,2,1,0. Type 3 and 4 information elements provide the information element identifier in
the first octet.

7
8

These information elements are shown in the figures below for both the case where the
information element is optional in a message and mandatory in a message.

9
10
11

In the figures below, IEI is used as an abbreviation for Information Element Identifier.
CIE as an abbreviation for Content of Information Element and LI as an abbreviation for
Length Indicator

12

Type 1 information elements with 1/2 octet of content:

7

IEI

CIE

Octet
1

13
14
15
16

Type 1 information elements may be either optional or mandatory in a BSMAP or a

DTAP message. When a Type 1 element is included as a mandatory information element
in a DTAP message, the information element identifier field shall be coded appropriately
by the sender, but may be ignored by the receiver.

17

Type 2 Information Element

18

Type 2 information elements with fixed length and zero octets of content

19

IEI

Note: A Type 2 information element cannot be mandatory in a DTAP message.

617

Octet
1

TIA/EIA/IS-2001

Type 3 Information Element

2
3
4

Type 3 information elements with fixed length and at least one octet of content are
shown below. The first instance includes the information element identifier (IEI). The
second excludes the IEI to demonstrate the coding for a mandatory DTAP element.
7

IEI

Octet
1

CIE

CIE

5
7

Octet

CIE

CIE

CIE

6
7

Type 4 Information Element

8
9
10

Type 4 information elements with variable length are shown below. The first instance
includes the information element identifier (IEI). The second excludes the IEI to
demonstrate the coding for a mandatory DTAP element.
7

IEI

Octet
1

LI

CIE

CIE

11
7

Octet

LI

CIE

CIE

12

618

TIA/EIA/IS-2001

6.2.1.4

2
3
4

A3 and A7 Interface Information Elements

All information elements carried exclusively on the A3 and A7 Interfaces in signaling
messages shall be coded with an Information Element Identifier, a Length field, and a
value part as shown in the figure below.

Information Element Identifier

Length

Value

5
6

Figure 6-3 - A3/A7 Information Element Generic Layout

7
8

The value component of the information element may be composed of one or more
fields of varying sizes.

6.2.1.5

Additional Coding and Interpretation Rules for Information Elements

10
11
12
13

Information elements shall always use the same Information Element Identifier for all
occurrences on a specific An Interface. Insofar as possible, the same Information
Element Identifier shall be used for a given information element when it is used on more
than one of the A n Interfaces.

14
15

The order of appearance for each information element which is mandatory or optional in
a message is laid down in the definition of the message.

16
17
18

Where the description of the information element in this standard contains spare bits,
these bits are indicated as being set to 0. In order to allow compatibility with future
implementation, messages shall not be rejected simply because a spare bit is set to 1.

19
20
21
22

An optional variable length information element may be present, but empty. For
example, a Setup message may contain a Called Party BCD Number information element,
the content of which is zero length. This shall be interpreted by the receiver as
equivalent to that information element being absent.

619

TIA/EIA/IS-2001

On the A1 interface, all new information elements shall be defined with a length field.

2
3
4
5
6
7

Some existing elements make use of an extension bit mechanism that allows the size of
the information element to be increased. This mechanism consists of the use of the
high order bit (bit 7) of an octet as an extension bit. When an octet within an
information element has bit 7 defined as an extension bit, then the value 0 in that bit
position indicates that the following octet is an extension of the current octet. When
the value is 1, there is no extension.

8
9
10
11

An example of the use of the extension bit mechanism is found in octets 3 and 3a of the
Calling Party BCD Number element (section 6.2.2.53). Octet 3 can be extended by
setting bit 7 to 0 and including octet 3a. This would allow the transmission of the
presentation indicator and screening indicator values as part of this element.

12
13
14

On the A3 and A7 Interfaces, length fields shall be employed instead of the extension
bit mechanism as a means of indicating the limits of a particular field.

620

TIA/EIA/IS-2001

6.2.1.6

Cross Reference of Information Elements With Messages

2
3

The following table provides a cross reference between the elements defined in this
specification and the messages defined herein.

Table 6 - 11 - Cross Reference of Information Elements With Messages

Information Element

Used in These Messages

A3 Connect Ack Information

6.2.2.145

A3-Connect Ack

6.1.9.2

A3 Connect Information

6.2.2.144

A3-Connect

6.1.9.1

A3 Destination ID

6.2.2.175

A3-Remove Ack

6.1.9.4

A3-Propagation Delay
Measurement Report

6.1.9.6

A3-Physical Transition Directive

6.1.9.11

A3-Physical Transition Directive

Ack

6.1.9.12

A3-Traffic Channel Status

6.1.9.15

A3 Drop Information

6.2.2.147

A3-Drop

6.1.9.5

A3 Remove Information

6.2.2.146

A3-Remove

6.1.9.3

A3 Signaling Address

6.2.2.90

A7-Handoff Request

6.1.12.1

A7-Burst Request

6.1.12.17

A3 Traffic Circuit ID

6.2.2.96

A3- Physical Transition Directive

6.1.9.11

A7 Destination ID

6.2.2.173

A3-Propagation Delay
Measurement Report

6.1.9.6

A3-Physical Transition Directive

Ack

6.1.9.12

A3-Traffic Channel Status

6.1.9.15

A7-Handoff Request Ack

6.1.12.2

A7-Drop Target

6.1.12.3

A7-Drop Target Ack

6.1.12.4

A7-Target Removal Request

6.1.12.5

A7- Target Removal Response

6.1.12.6

A7-Source Transfer Performed

6.1.12.10

A7-Burst Request

6.1.12.17

A7-Burst Response

6.1.12.18

A7-Burst Commit

6.1.12.19

A7-Handoff Request

6.1.12.1

A7-Handoff Request Ack

6.1.12.2

A7 Originating ID

6.2.2.172

A7 Control

6.2.2.97

A7-Handoff Request Ack

6.1.12.2

A8 Traffic_ID

6.2.2.170

A9-Setup-A8

6.1.10.1

621

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
A8 Traffic_ID

Used in These Messages

6.2.2.170

(continued from previous page)

A9-AL Connected

6.1.10.8

A9-AL Disconnected

6.1.10.9

A9-Connect-A8

6.1.10.2

A9-Disconnect-A8

6.1.10.3

A9-Release-A8

6.1.10.4

A9 BSC_ID

6.2.2.169

A9-Setup-A8

6.1.10.1

A9 Indicators

6.2.2.171

A9-Setup-A8

6.1.10.1

A9 Message Type

6.2.2.167

A9-Setup-A8

6.1.10.1

A9-AL Connected

6.1.10.8

A9-AL Connected Ack

6.1.10.9

A9-AL Disconnected

6.1.10.10

A9-AL Disconnected Ack

6.1.10.11

A9-BS Service Request

6.1.10.6

A9-BS Service Response

6.1.10.7

A9-Connect-A8

6.1.10.2

A9-Disconnect-A8

6.1.10.3

A9-Release-A8

6.1.10.4

A9-Release-A8 Complete

6.1.10.5

A11-Registration Request

6.1.11.1

A11-Registration Reply

6.1.11.2

A11-Registration Update

6.1.11.3

A11-Registration Acknowledge

6.1.11.4

ADDS Deliver

6.1.7.3

ADDS Page

6.1.7.1

ADDS Transfer

6.1.7.2

A7-Access Channel Message

Transfer

6.1.12.15

A7-Paging Channel Message

Transfer

6.1.12.13

CM Service Request

6.1.2.2

Location Updating Request

6.1.4.8

Paging Response

6.1.2.4

Base Station Challenge

6.1.4.5

A11 Message Type

ADDS User Part

Air Interface Message

Authentication Challenge Parameter

(RAND/RANDU/RANDBS/RANDSSD)

6.2.2.154

6.2.2.67

6.2.2.152

6.2.2.45

622

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
Authentication Challenge Parameter
(RAND/RANDU/RANDBS/RANDSSD)

Used in These Messages

6.2.2.45

(continued from previous page)

Authentication Confirmation Parameter

(RANDC)

6.2.2.42

PACA Update

6.1.3.13

SSD Update Request

6.1.4.4

Authentication Request

6.1.4.1

ADDS Transfer

6.1.7.2

CM Service Request

6.1.2.2

Location Updating Request

6.1.4.8

Paging Response

6.1.2.4

PACA Update

6.1.3.13

ADDS Transfer

6.1.7.2

Authentication Data

6.2.2.137

CM Service Request

6.1.2.2

Authentication Event

6.2.2.114

ADDS Transfer

6.1.7.2

CM Service Request

6.1.2.2

Location Updating Request

6.1.4.8

Paging Response

6.1.2.4

PACA Update

6.1.3.13

ADDS Transfer

6.1.7.2

CM Service Request

6.1.2.2

Location Updating Request

6.1.4.8

PACA Update

6.1.3.13

Paging Response

6.1.2.4

Base Station Challenge Response

6.1.4.6

CM Service Request

6.1.2.2

Paging Response

6.1.2.4

Location Updating Request

6.1.4.8

Authentication Response

6.1.4.2

PACA Update

6.1.3.13

ADDS Transfer

6.1.7.2

A7-Handoff Request

6.1.12.1

A7-Burst Request

6.1.12.17

A7- Source Transfer Performed

6.1.12.10

Authentication Parameter COUNT

Authentication Response Parameter

(AUTHBS/AUTHR/AUTHU)

Band Class

BSC ID

6.2.2.47

6.2.2.46

6.2.2.106

6.2.2.125

623

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
Call Connection Reference

Used in These Messages

6.2.2.98

A3- Physical Transition Directive

6.1.9.11

A3- Physical Transition Directive

Ack

6.1.9.12

A3-Connect

6.1.9.1

A3-Connect Ack

6.1.9.2

A3-Drop

6.1.9.5

A3-Propagation Delay
Measurement Report

6.1.9.6

A3-Remove

6.1.9.3

A3-Remove Ack

6.1.9.4

A3-Traffic Channel Status

6.1.9.15

A7- Source Transfer Performed

6.1.12.10

A7-Burst Request

6.1.12.17

A7-Drop Target

6.1.12.3

A7-Drop Target Ack

6.1.12.4

A7-Handoff Request

6.1.12.1

A7-Handoff Request Ack

6.1.12.2

A7-Target Removal Request

6.1.12.5

A7-Target Removal Response

6.1.12.6

A9-AL Connected

6.1.10.8

A9-AL Connected Ack

6.1.10.9

A9-AL Disconnected

6.1.10.10

A9-AL Disconnected Ack

6.1.10.11

A9-Connect-A8

6.1.10.2

A9-Disconnect-A8

6.1.10.3

A9-Setup-A8

6.1.10.1

A9-Release-A8

6.1.10.4

A9-Release-A8 Complete

6.1.10.5

Called Party ASCII Number

6.2.2.105

CM Service Request

6.1.2.2

Care-of-Address

6.2.2.159

A11-Registration Request

6.1.11.1

A11-Registration Acknowledge

6.1.11.4

CM Service Request

6.1.2.2

Flash with Information

6.1.3.7

Called Party BCD Number

6.2.2.52

624

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
Calling Party ASCII Number

Cause

Cause Layer 3

Cause List

CDMA Long Code Transition Info

Used in These Messages

6.2.2.37

6.2.2.19

6.2.2.55

6.2.2.142

6.2.2.128

625

Assignment Request

6.1.2.15

Flash with Information

6.1.3.7

Feature Notification

6.1.3.9

A7-Paging Channel Message

Transfer Ack

6.1.12.14

A7-Reset

6.1.12.11

A9-Connect-A8

6.1.10.2

A9-Disconnect-A8

6.1.10.3

A9-Release-A8

6.1.10.4

A9-BS Service Response

6.1.10.7

ADDS Deliver Ack

6.1.7.5

ADDS Page Ack

6.1.7.4

Assignment Failure

6.1.2.17

Block

6.1.6.2

BS Service Response

6.1.2.29

Clear Command

6.1.2.21

Clear Request

6.1.2.20

Handoff Failure

6.1.5.7

Handoff Performed

6.1.5.12

Handoff Required

6.1.5.4

Handoff Required Reject

6.1.5.9

PACA Command Ack

6.1.3.12

PACA Update Ack

6.1.3.14

Reset

6.1.6.6

Reset Circuit

6.1.6.8

Clear Command

6.1.2.21

Clear Request

6.1.2.20

SSD Update Response

6.1.4.7

A3-Drop

6.1.9.5

A7-Handoff Request Ack

6.1.12.2

A7-Target Removal Request

6.1.12.5

A7-Target Removal Response

6.1.12.6

A3- Physical Transition Directive

6.1.9.11

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
CDMA Serving One Way Delay

Cell Identifier

Cell Identifier List

Used in These Messages

6.2.2.79

6.2.2.20

6.2.2.21

626

A7-Handoff Request

6.1.12.1

A7-Burst Request

6.1.12.17

ADDS Deliver

6.1.7.3

ADDS Transfer

6.1.7.2

CM Service Request

6.1.2.2

Handoff Required

6.1.5.4

Handoff Request

6.1.5.5

Paging Response

6.1.2.4

A7-Access Channel Message

Transfer

6.1.12.15

ADDS Page Ack

6.1.7.4

ADDS Transfer

6.1.7.2

Complete Layer 3 Information

6.1.2.1

A3-Traffic Channel Status

6.1.9.15

A7-Drop Target

6.1.12.3

A7-Handoff Request

6.1.12.1

A7-Paging Channel Message

Transfer

6.1.12.13

ADDS Page

6.1.7.1

Authentication Request

6.1.4.1

Feature Notification

6.1.3.9

Handoff Command

6.1.5.8

Handoff Performed

6.1.5.12

Handoff Request Acknowledge

6.1.5.6

Paging Request

6.1.2.3

A7-Target Removal Response

6.1.12.6

A7-Target Removal Request

6.1.12.5

Handoff Request

6.1.5.5

Handoff Required

6.1.5.4

A7-Burst Request

6.1.12.17

A7-Burst Response

6.1.12.18

A7-Burst Commit

6.1.12.19

A7-Handoff Request Ack

6.1.12.2

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element

Used in These Messages

Cell Information Record

6.2.2.89

A3- Physical Transition Directive

Ack

6.1.9.12

Channel Element ID

6.2.2.132

A3- Physical Transition Directive

6.1.9.11

Channel Element Status

6.2.2.141

A3-Traffic Channel Status

6.1.9.15

Channel Number

6.2.2.6

Assignment Complete

6.1.2.16

Channel Type

6.2.2.7

Assignment Request

6.1.2.15

Handoff Request

6.1.5.5

Block

6.1.6.2

Reset Circuit

6.1.6.8

Unblock

6.1.6.4

Assignment Request

6.1.2.15

Block

6.1.6.2

Block Acknowledge

6.1.6.3

CM Service Request

6.1.2.2

Paging Response

6.1.2.4

Reset Circuit

6.1.6.8

Reset Circuit Acknowledge

6.1.6.9

Unblock

6.1.6.4

Unblock Acknowledge

6.1.6.5

Circuit Group

Circuit Identity Code

6.2.2.148

6.2.2.22

Circuit Identity Code Extension

6.2.2.23

Handoff Request

6.1.5.5

Classmark Information Type 2

6.2.2.15

CM Service Request

6.1.2.2

Handoff Request

6.1.5.5

Handoff Required

6.1.5.4

Location Updating Request

6.1.4.8

Paging Response

6.1.2.4

CM Service Type

6.2.2.51

CM Service Request

6.1.2.2

Code

6.2.2.161

A11-Registration Reply

6.1.11.2

627

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
CON_REF

Correlation ID

Used in These Messages

6.2.2.168

6.2.2.108

628

A9-Setup-A8

6.1.10.1

A9-Connect-A8

6.1.10.2

A9-Disconnect-A8

6.1.10.3

A9-Release-A8

6.1.10.4

A3-Connect

6.1.9.1

A3-Connect Ack

6.1.9.2

A3-Remove

6.1.9.3

A3-Remove Ack

6.1.9.4

A7-Access Channel Message

Transfer

6.1.12.15

A7-Access Channel Message

Transfer Ack

6.1.12.16

A7-Burst Request

6.1.12.17

A7-Burst Response

6.1.12.18

A7-Burst Commit

6.1.12.19

A7-Drop Target

6.1.12.3

A7-Drop Target Ack

6.1.12.4

A7-Handoff Request

6.1.12.1

A7-Handoff Request Ack

6.1.12.2

A7-Paging Channel Message

Transfer

6.1.12.13

A7-Paging Channel Message

Transfer Ack

6.1.12.14

A7-Target Removal Request

6.1.12.5

A7-Target Removal Response

6.1.12.6

A9-Setup-A8

6.1.10.1

A9-Connect-A8

6.1.10.2

A9-Disconnect-A8

6.1.10.3

A9-Release-A8

6.1.10.4

A9-Release-A8 Complete

6.1.10.5

A9-BS Service Request

6.1.10.6

A9-BS Service Response

6.1.10.7

A9-AL Connected

6.1.10.8

A9-AL Connected Ack

6.1.10.9

A9-AL Dis connected

6.1.10.10

TIA/EIA/IS-2001

A9-AL Dis connected Ack

629

6.1.10.11

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element

Used in These Messages

Data Count

6.2.2.179

A9-BS Service Request

6.1.10.6

Downlink Radio Environment

6.2.2.25

A7-Handoff Request

6.1.12.1

A7-Burst Request

6.1.12.17

Handoff Request

6.1.5.5

Handoff Required

6.1.5.4

Assignment Complete

6.1.2.16

Assignment Request

6.1.2.15

Handoff Request

6.1.5.5

Handoff Required

6.1.5.4

Privacy Mode Command

6.1.4.18

Privacy Mode Complete

6.1.4.19

Handoff Command

6.1.5.8

Handoff Request Acknowledge

6.1.5.6

Encryption Information

Extended Handoff Direction Parameters

6.2.2.12

6.2.2.73

Flags

6.2.2.155

A11-Registration Request

6.1.11.1

Forward Burst Radio Info

6.2.2.56

A7- Burst Request

6.1.12.17

A7-Burst Response

6.1.12.18

A7-Burst Commit

6.1.12.19

Forward Layer 3 Data

6.2.2.120

A3-IS-95 FCH Forward

6.1.9.7

Forward Layer 3 IS-2000 FCH/DCCH

Data

6.2.2.74

A3-IS-2000 FCH Forward

6.1.9.9

A3-IS-2000 DCCH Forward

6.1.9.13

Forward Layer 3 IS-2000 SCH Data

6.2.2.77

A3-IS-2000 SCH Forward

6.1.9.16

Handoff Power Level

6.2.2.31

Handoff Command

6.1.5.8

Hard Handoff Parameters

6.2.2.63

Handoff Command

6.1.5.8

Handoff Request Acknowledge

6.1.5.6

A11-Registration Request

6.1.11.1

A11-Registration Reply

6.1.11.2

A11-Registration Update

6.1.11.3

A11-Registration Acknowledge

6.1.11.4

A11-Registration Request

6.1.11.1

A11-Registration Reply

6.1.11.2

A11-Registration Update

6.1.11.3

Home Address

Home Agent

6.2.2.157

6.2.2.158

630

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
Identification

IS-2000 Channel Identity

IS-2000 Forward Power Control Mode

IS-2000 FPC Gain Ratio Info

IS-2000 Mobile Capabilities

Used in These Messages

6.2.2.160

6.2.2.34

6.2.2.177

6.2.2.178

6.2.2.70

A11-Registration Request

6.1.11.1

A11-Registration Reply

6.1.11.2

A11-Registration Update

6.1.11.3

A11-Registration Acknowledge

6.1.11.4

Handoff Command

6.1.5.8

Handoff Request

6.1.5.5

Handoff Request Acknowledge

6.1.5.6

Handoff Required

6.1.5.4

A3- Physical Transition Directive

6.1.9.11

A7-Handoff Request

6.1.12.1

A7-Burst Commit

6.1.12.19

A7-Handoff Request

6.1.12.1

A7-Burst Commit

6.1.12.19

CM Service Request

6.1.2.2

Paging Request

6.1.2.3

Paging Response

6.1.2.4

Feature Notification

6.1.3.9

Authentication Request

6.1.4.1

Location Updating Request

6.1.4.8

Handoff Required

6.1.5.4

Handoff Request

6.1.5.5

ADDS Page

6.1.7.1

IS-2000 Mobile Pilot Gain

6.2.2.180

A3- Physical Transition Directive

6.1.9.11

IS-2000 Non-Negotiable Service

Configuration Record

6.2.2.69

Handoff Request Acknowledge

6.1.5.6

Handoff Command

6.1.5.8

IS-2000 Power Control Info

6.2.2.176

A7-Handoff Request

6.1.12.1

IS-2000 Service Configuration Record

6.2.2.68

Handoff Required

6.1.5.4

Handoff Request

6.1.5.5

Handoff Request Acknowledge

6.1.5.6

Handoff Command

6.1.5.8

A7-Handoff Request

6.1.12.1

Rejection

6.1.8.1

IS-2000 Cause Value

6.2.2.110

631

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
IS-95 Channel Identity

IS-95 MS Measured Channel Identity

Layer 2 Ack Request/Results

Used in These Messages

6.2.2.10

6.2.2.36

6.2.2.153

A7-Handoff Request

6.1.12.1

Handoff Command

6.1.5.8

Handoff Request

6.1.5.5

Handoff Request Acknowledge

6.1.5.6

Handoff Required

6.1.5.4

Handoff Request

6.1.5.5

Handoff Required

6.1.5.4

A7-Paging Channel Message

Transfer

6.1.12.13

A7-Paging Channel Message

Transfer Ack

6.1.12.14

Layer 3 Information

6.2.2.38

Complete Layer 3 Information

6.1.2.1

Lifetime

6.2.2.156

A11-Registration Request

6.1.11.1

A11-Registration Reply

6.1.11.2

Location Updating Accept

6.1.4.9

Location Updating Request

6.1.4.8

A3-IS-95 FCH Forward

6.1.9.7

A3-IS-95 FCH Reverse

6.1.9.8

A3-IS-2000 DCCH Forward

6.1.9.13

A3-IS-2000 DCCH Reverse

6.1.9.14

A3-IS-2000 FCH Forward

6.1.9.9

A3-IS-2000 FCH Reverse

6.1.9.10

A3-IS-2000 SCH Forward

6.1.9.16

A3-IS-2000 SCH Reverse

6.1.9.17

ADDS Deliver

6.1.7.3

ADDS Deliver Ack

6.1.7.5

ADDS Page

6.1.7.1

ADDS Page Ack

6.1.7.4

ADDS Transfer

6.1.7.2

Location Area Identification

Message CRC

Message Type

6.2.2.43

6.2.2.134

6.2.2.4

632

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
Message Type

Used in These Messages

6.2.2.4

(continued from previous page)

Message Type

6.2.2.4

(continued from the previous page)

633

Alert With Information

6.1.2.24

Assignment Complete

6.1.2.16

Assignment Failure

6.1.2.17

Assignment Request

6.1.2.15

Authentication Request

6.1.4.1

Authentication Response

6.1.4.2

Base Station Challenge

6.1.4.5

Base Station Challenge Response

6.1.4.6

Block

6.1.6.2

Block Acknowledge

6.1.6.3

BS Service Response

6.1.2.29

BS Service Request

6.1.2.28

Clear Command

6.1.2.21

Clear Complete

6.1.2.22

Clear Request

6.1.2.20

CM Service Request

6.1.2.2

Complete Layer 3 Information

6.1.2.1

Connect

6.1.2.10

Feature Notification

6.1.3.9

Feature Notification Ack

6.1.3.10

Flash with Information

6.1.3.7

Flash with Information Ack

6.1.3.8

Handoff Command

6.1.5.8

Handoff Commenced

6.1.5.10

Handoff Complete

6.1.5.11

Handoff Failure

6.1.5.7

Handoff Performed

6.1.5.12

Handoff Request

6.1.5.5

Handoff Request Acknowledge

6.1.5.6

Handoff Required

6.1.5.4

Handoff Required Reject

6.1.5.9

Location Updating Accept

6.1.4.9

Location Updating Reject

6.1.4.10

Location Updating Request

6.1.4.8

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element

Message Type

Used in These Messages

6.2.2.4

(continued from the previous page)

Message Type II

6.2.2.5

634

PACA Command

6.1.3.11

PACA Command Ack

6.1.3.12

PACA Update

6.1.3.13

PACA Update Ack

6.1.3.14

Paging Request

6.1.2.3

Paging Response

6.1.2.4

Parameter Update Confirm

6.1.4.12

Parameter Update Request

6.1.4.11

Privacy Mode Command

6.1.4.18

Privacy Mode Complete

6.1.4.19

Progress

6.1.2.12

Rejection

6.1.8.1

Reset

6.1.6.6

Reset Acknowledge

6.1.6.7

Reset Circuit

6.1.6.8

Reset Circuit Acknowledge

6.1.6.9

SSD Update Request

6.1.4.4

SSD Update Response

6.1.4.7

Unblock

6.1.6.4

Unblock Acknowledge

6.1.6.5

User Zone Update

6.1.4.3

A3- Physical Transition Directive

6.1.9.11

A3- Physical Transition Directive

Ack

6.1.9.12

A3 IS-2000 DCCH Forward

6.1.9.13

A3 IS-2000 DCCH Reverse

6.1.9.14

A3-IS-95 FCH Forward

6.1.9.7

A3-IS-95 FCH Reverse

6.1.9.8

A3-Connect

6.1.9.1

A3-Connect Ack

6.1.9.2

A3-Drop

6.1.9.5

A3 IS-2000 FCH Forward

6.1.9.9

A3 IS-2000 FCH Reverse

6.1.9.9

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element

Message Type II

Used in These Messages

6.2.2.5

(continued from the previous page)

Mobile-Home Authentication Extension

Message Waiting Indication

6.2.2.163

6.2.2.48

635

A3-Propagation Delay
Measurement Report

6.1.9.6

A3-Remove

6.1.9.3

A3-Remove Ack

6.1.9.4

A3 IS-2000 SCH Forward

6.1.9.16

A3 IS-2000 SCH Reverse

6.1.9.17

A3-Traffic Channel Status

6.1.9.15

A7- Source Transfer Performed

6.1.12.10

A7-Access Channel Message

Transfer

6.1.12.15

A7-Access Channel Message

Transfer Ack

6.1.12.16

A7-Burst Commit

6.1.12.19

A7-Burst Request

6.1.12.17

A7-Burst Response

6.1.12.18

A7-Drop Target

6.1.12.3

A7-Drop Target Ack

6.1.12.4

A7-Handoff Request

6.1.12.1

A7-Handoff Request Ack

6.1.12.2

A7-Paging Channel Message

Transfer

6.1.12.13

A7-Paging Channel Message

Transfer Ack

6.1.12.14

A7-Reset

6.1.12.11

A7-Reset Acknowledge

6.1.12.12

A7-Target Removal Request

6.1.12.5

A7-Target Removal Response

6.1.12.6

A11-Registration Request

6.1.11.1

A11-Registration Reply

6.1.11.2

Flash with Information

6.1.3.7

Feature Notification

6.1.3.9

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
Mobile Identity

Used in These Messages

6.2.2.16

636

ADDS Transfer

6.1.7.2

CM Service Request

6.1.2.2

Paging Response

6.1.2.4

ADDS Page

6.1.7.1

A7 Burst Request

6.1.12.17

BS Service Request

6.1.2.28

BS Service Response

6.1.2.29

PACA Update

6.1.3.13

PACA Update Ack

6.1.3.14

Handoff Request

6.1.5.5

Handoff Required

6.1.5.4

A9-Setup A8

6.1.10.1

Paging Request

6.1.2.3

A9-Connect-A8

6.1.10.2

A7-Handoff Request

6.1.12.1

Authentication Request

6.1.4.1

Authentication Response

6.1.4.2

Location Updating Request

6.1.4.8

A7-Access Channel Message

Transfer

6.1.12.15

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
Mobile Identity

Used in These Messages

6.2.2.16

(continued from the previous page)

MS Information Records

6.2.2.72

A7-Paging Channel Message

Transfer

6.1.12.13

ADDS Page Ack

6.1.7.4

Feature Notification

6.1.3.9

Feature Notification Ack

6.1.3.10

Paging Request

6.1.2.3

Rejection

6.1.8.1

A9-Disconnect-A8

6.1.10.3

A9-Release-A8

6.1.10.4

A9-BS Service Request

6.1.10.6

Progress

6.1.2.12

Assignment Request

6.1.2.15

Alert With Information

6.1.2.24

Flash With Information

6.1.3.7

Feature Notification

6.1.3.9

Neighbor List

6.2.2.83

A7-Handoff Request Ack

6.1.12.2

One way Propagation Delay Record

6.2.2.119

A3-Propagation Delay
Measurement Report

6.1.9.6

PACA Order

6.2.2.150

PACA Update

6.1.3.13

PACA Reorigination Indicator

6.2.2.151

CM Service Request

6.1.2.2

PACA Timestamp

6.2.2.149

Assignment Request

6.1.2.15

PACA Command

6.1.3.11

Handoff Required

6.1.5.4

Handoff Request

6.1.5.5

A9-Connect-A8

6.1.10.2

A9-AL Connected

6.1.10.8

PDSN IP Address

6.2.2.30

Physical Channel Info

6.2.2.14

A7-Handoff Request

6.1.12.1

PMC Cause

6.2.2.99

A3- Physical Transition Directive

Ack

6.1.9.12

Power Down Indicator

6.2.2.60

Clear Complete

6.1.2.22

Priority

6.2.2.18

Assignment Request

6.1.2.15

PACA Command

6.1.3.11

PACA Update

6.1.3.13

PACA Update Ack

6.1.3.14

637

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
Privacy Info

Protocol Discriminator

Protocol Type

Quality of Service Parameters

Radio Environment and Resources

Used in These Messages

6.2.2.143

6.2.2.39

6.2.2.71

6.2.2.54

6.2.2.82

638

A7-Handoff Request

6.1.12.1

A7-Burst Request

6.1.12.7

A3-Physical Transition Directive

6.1.9.11

ADDS Deliver

6.1.7.3

ADDS Deliver Ack

6.1.7.5

Alert With Information

6.1.2.24

Authentication Request

6.1.4.1

Authentication Response

6.1.4.2

Base Station Challenge

6.1.4.5

Base Station Challenge Response

6.1.4.6

CM Service Request

6.1.2.2

Connect

6.1.2.10

Flash with Information

6.1.3.7

Flash with Information Ack

6.1.3.8

Location Updating Accept

6.1.4.9

Location Updating Reject

6.1.4.10

Location Updating Request

6.1.4.8

Paging Response

6.1.2.4

Parameter Update Confirm

6.1.4.12

Parameter Update Request

6.1.4.11

Progress

6.1.2.12

Rejection

6.1.8.1

SSD Update Request

6.1.4.4

SSD Update Response

6.1.4.7

Handoff Required

6.1.5.4

Handoff Request

6.1.5.5

Assignment Request

6.1.2.15

Handoff Request

6.1.5.5

A9-Setup-A8

6.1.10.1

A7-Handoff Request

6.1.12.1

Handoff Required

6.1.5.4

CM Service Request

6.1.2.2

Paging Response

6.1.2.4

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element

Used in These Messages

Registration Type

6.2.2.61

Location Updating Request

6.1.4.8

Registration Update Authentication

Extension

6.2.2.164

A11-Registration Update

6.1.11.3

A11-Registration Acknowledge

6.1.11.4

Reject Cause

6.2.2.44

Location Updating Reject

6.1.4.10

Reserved - Octet

6.2.2.40

Paging Response

6.1.2.4

Authentication Request

6.1.4.1

Authentication Response

6.1.4.2

Base Station Challenge

6.1.4.5

Base Station Challenge Response

6.1.4.6

CM Service Request

6.1.2.2

Connect

6.1.2.10

Flash with Information

6.1.3.7

Flash with Information Ack

6.1.3.8

Location Updating Accept

6.1.4.9

Location Updating Reject

6.1.4.10

Location Updating Request

6.1.4.8

Parameter Update Confirm

6.1.4.12

Parameter Update Request

6.1.4.11

Progress

6.1.2.12

Rejection

6.1.8.1

SSD Update Request

6.1.4.4

SSD Update Response

6.1.4.7

ADDS Deliver

6.1.7.3

ADDS Deliver Ack

6.1.7.5

Alert With Information

6.1.2.24

Response Request

6.2.2.35

Handoff Required

6.1.5.4

Reverse Burst Radio Info

6.2.2.57

A7-Burst Request

6.1.12.17

A7-Burst Response

6.1.12.18

A7-Burst Commit

6.1.12.19

Reverse Layer 3 Data

6.2.2.121

A3-IS-95 FCH Reverse

6.1.9.8

Reverse Layer 3 IS-2000 FCH/DCCH

Data

6.2.2.75

A3-IS-2000 FCH Reverse

6.1.9.10

A3-IS-2000 DCCH Reverse

6.1.9.14

639

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element

Used in These Messages

Reverse Layer 3 IS-2000 SCH Data

6.2.2.78

A3-IS-2000 SCH Reverse

6.1.9.17

Reverse Pilot Gating Rate

6.2.2.33

A3-Physical Transition Directive

6.1.9.11

RF Channel Identity

6.2.2.8

Handoff Command

6.1.5.8

SDU ID

6.2.2.91

A3- Physical Transition Directive

Ack

6.1.9.12

A3-Connect

6.1.9.1

A3-Propagation Delay
Measurement Report

6.1.9.6

A3-Remove

6.1.9.3

A3-Traffic Channel Status

6.1.9.15

A7-Handoff Request

6.1.12.1

A7-Burst Request

6.1.12.17

Service Configuration Record

6.2.2.109

A7-Handoff Request

6.1.12.1

Service Option

6.2.2.66

Assignment Complete

6.1.2.16

Assignment Request

6.1.2.15

CM Service Request

6.1.2.2

Handoff Request

6.1.5.5

Handoff Required

6.1.5.4

A9-BS Service Request

6.1.10.6

A9-Setup-A8

6.1.10.1

Paging Request

6.1.2.3

Paging Response

6.1.2.4

BS Service Request

6.1.2.28

A11-Registration Request

6.1.11.1

A11-Registration Reply

6.1.11.2

A11-Registration Update

6.1.11.3

A11-Registration Acknowledge

6.1.11.4

Session Specific Extension

6.2.2.165

SID

6.2.2.9

Handoff Command

6.1.5.8

Signal

6.2.2.50

Assignment Request

6.1.2.15

Feature Notification

6.1.3.9

Flash with Information

6.1.3.7

Progress

6.1.2.12

640

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

2
Information Element
Slot Cycle Index

Software Version

Used in These Messages

6.2.2.17

6.2.2.65

ADDS Page

6.1.7.1

Authentication Request

6.1.4.1

CM Service Request

6.1.2.2

Feature Notification

6.1.3.9

Location Updating Request

6.1.4.8

Paging Request

6.1.2.3

Paging Response

6.1.2.4

A7-Reset

6.1.12.11

A7-Reset Acknowledge

6.1.12.12

Reset

6.1.6.6

Reset Acknowledge

6.1.6.7

Status

6.2.2.162

A11-Registration Acknowledge

6.1.11.4

Tag

6.2.2.62

ADDS Deliver

6.1.7.3

ADDS Deliver Ack

6.1.7.5

ADDS Page

6.1.7.1

ADDS Page Ack

6.1.7.4

Authentication Request

6.1.4.1

Authentication Response

6.1.4.2

BS Service Request

6.1.2.28

BS Service Response

6.1.2.29

Feature Notification

6.1.3.9

Feature Notification Ack

6.1.3.10

Flash with Information

6.1.3.7

Flash with Information Ack

6.1.3.8

Paging Request

6.1.2.3

Paging Response

6.1.2.4

Transcoder Mode

6.2.2.58

Transcoder Control Request

6.1.6.10

User Zone ID

6.2.2.32

CM Service Request

6.1.2.2

Paging Response

6.1.2.4

User Zone Update

6.1.4.3

A9-Setup-A8

6.1.10.1

Location Updating Request

6.1.4.8

A11-Registration Request

6.1.11.1

A11-Registration Reply

6.1.11.2

Vendor/Organization Specific Extension

6.2.2.166

641

TIA/EIA/IS-2001

Table 6 - 11 - (cont.) Cross Reference of Information Elements With Messages

Information Element

Voice Privacy Request

Used in These Messages

6.2.2.13

642

CM Service Request

6.1.2.2

Paging Response

6.1.2.4

Privacy Mode Complete

6.1.4.19

TIA/EIA/IS-2001

6.2.2

Information Elements

6.2.2.1

Message Discrimination

3
4
5

6
7
8

A 1 octet field is used in all messages to discriminate between DTAP and BSMAP
messages. See Section 6.1.1 for details on use of this element in the header of all
messages.
7

Octet

D-bit

The D-bit is set to 1 to indicate that the message is a DTAP messages. All other
messages shall have the D-bit set to 0. See Section 6.1.1.1.1 for an indication of when
the D-bit is set (i.e., DTAP or BSMAP message).

643

TIA/EIA/IS-2001

6.2.2.2

Data Link Connection Identifier (DLCI)

2
3
4
5
6
7

The DLCI is one of the parameters for the distribution data unit which is part of the user
data field of every DTAP message. See Section 6.1.1.1.1.2 for details on use of this
element in the header of all DTAP messages. The DLCI parameter is used for MSC to BS
messages to indicate the type of data link connection to be used over the radio
interface. In the direction BS to MSC the DLCI parameter is used to indicate the type of
originating data parameter is coded in one octet, as follows:
7

C2

C1

Reserved

Octet

S3

S2

S1

8
9

C2 and C1 are defined as:

C2

C1

Description
Represents the default for TIA/EIA-IS-2000

All other
values
10
11
12

Reserved

Bits S3, S2, and S1 represent the SAPI (Signaling Access Point Identifier) value used on
the radio link. The SAPI shall be set to zero for TIA/EIA-IS-2000 systems.
6.2.2.3

Length Indicator (LI)

13
14

The length indicator is coded in one octet, and is the binary representation of the
number of octets following the length indicator.
7

Length Indicator
15

644

Octet
1

TIA/EIA/IS-2001

6.2.2.4

Message Type

Element Format:
7

Message Type

3
4

Table 6 - 12 - BSMAP Messages

BSMAP Message Name
ADDS Page

Message
Type
Message Category
Value
65H
Supplementary Services

Section
Reference
6.1.7.1

ADDS Page Ack

66H

Supplementary Services

6.1.7.4

ADDS Transfer

67H

Supplementary Services

6.1.7.2

Assignment Complete

02H

Call Processing

6.1.2.16

Assignment Failure

03H

Call Processing

6.1.2.17

Assignment Request

01H

Call Processing

6.1.2.15

Authentication Request

45H

Mobility Management

6.1.4.1

Authentication Response

46H

Mobility Management

6.1.4.2

Base Station Challenge

48H

Mobility Management

6.1.4.5

Base Station Challenge Response

49H

Mobility Management

6.1.4.6

Block

40H

Facilities Management

6.1.6.2

Block Acknowledge

41H

Facilities Management

6.1.6.3

BS Service Request

09H

Call Processing

6.1.2.28

BS Service Response

0AH

Call Processing

6.1.2.29

Clear Command

20H

Call Processing

6.1.2.21

Clear Complete

21H

Call Processing

6.1.2.22

645

Octet

TIA/EIA/IS-2001

Table 6 - 12 (cont.) - BSMAP Messages

BSMAP Message Name
Clear Request

Message
Type
Message Category
Value
22H
Call Processing

Section
Reference
6.1.2.20

Complete Layer 3 Information

57H

Call Processing

6.1.2.1

Feature Notification

60H

Supplementary Services

6.1.3.9

Feature Notification Ack

61H

Supplementary Services

6.1.3.10

Handoff Command

13H

Radio Resource Mgmt.

6.1.5.8

Handoff Commenced

15H

Radio Resource Mgmt.

6.1.5.10

Handoff Complete

14H

Radio Resource Mgmt.

6.1.5.11

Handoff Failure

16H

Radio Resource Mgmt.

6.1.5.7

Handoff Performed

17H

Radio Resource Mgmt.

6.1.5.12

Handoff Request

10H

Radio Resource Mgmt.

6.1.5.5

Handoff Request Acknowledge

12H

Radio Resource Mgmt.

6.1.5.6

Handoff Required

11H

Radio Resource Mgmt.

6.1.5.4

Handoff Required Reject

1AH

Radio Resource Mgmt.

6.1.5.9

PACA Command

6CH

Supplementary Services

6.1.3.11

PACA Command Ack

6DH

Supplementary Services

6.1.3.12

PACA Update

6EH

Supplementary Services

6.1.3.13

PACA Update Ack

6FH

Supplementary Services

6.1.3.14

Paging Request

52H

Call Processing

6.1.2.3

Privacy Mode Command

53H

Call Processing

6.1.4.18

Privacy Mode Complete

55H

Call Processing

6.1.4.19

646

TIA/EIA/IS-2001

Table 6 - 12 (cont.) - BSMAP Messages

BSMAP Message Name
Rejection

Message
Type
Message Category
Value
56H
Call Processing

Section
Reference
6.1.8.1

Reset

30H

Facilities Management

6.1.6.6

Reset Acknowledge

31H

Facilities Management

6.1.6.7

Reset Circuit

34H

Facilities Management

6.1.6.8

Reset Circuit Acknowledge

35H

Facilities Management

6.1.6.9

SSD Update Request

47H

Mobility Management

6.1.4.4

SSD Update Response

4AH

Mobility Management

6.1.4.7

Transcoder Control Acknowledge

0BH

Facilities Management

6.1.6.11

Transcoder Control Request

0CH

Facilities Management

6.1.6.10

Unblock

42H

Facilities Management

6.1.6.4

Unblock Acknowledge

43H

Facilities Management

6.1.6.5

User Zone Update

04H

Mobility Management

6.1.4.3

647

TIA/EIA/IS-2001

Table 6 - 13 - DTAP Messages

DTAP Message Name
ADDS Deliver

Message
Value Message Category
Type
53H
Supplementary Services

Section
Reference
6.1.7.3

ADDS Deliver Ack

54H

Supplementary Services

6.1.7.5

Alert With Information

26H

Call Processing

6.1.2.24

Authentication Request

45H

Mobility Management

6.1.4.1

Authentication Response

46H

Mobility Management

6.1.4.2

Base Station Challenge

48H

Mobility Management

6.1.4.5

Base Station Challenge Response

49H

Mobility Management

6.1.4.6

CM Service Request

24H

Call Processing

6.1.2.2

Connect

07H

Call Processing

6.1.2.10

Flash with Information

10H

Supplementary Services

6.1.3.7

Flash with Information Ack

50H

Supplementary Services

6.1.3.8

Location Updating Accept

02H

Mobility Management

6.1.4.9

Location Updating Reject

04H

Mobility Management

6.1.4.10

Location Updating Request

08H

Mobility Management

6.1.4.8

Paging Response

27H

Call Processing

6.1.2.4

Parameter Update Confirm

2BH

Mobility Management

6.1.4.12

Parameter Update Request

2CH

Mobility Management

6.1.4.11

Rejection

56H

Call Processing

6.1.8.1

648

TIA/EIA/IS-2001

6.2.2.5

Message Type II

2
3

The Message Type II element is used to indicate the type of a message on the A3 and
A7 interfaces.

Element Format:
7

Octet

Message Type II

5
6

Table 6 - 14 - A3 and A7 Message Type II Values

Message
Type II
Value

Interface

A3-Connect

01H

A3

6.1.9.1

A3-Connect Ack

02H

A3

6.1.9.2

A3-Remove

03H

A3

6.1.9.3

A3-Remove Ack

04H

A3

6.1.9.4

A3-Drop

05H

A3

6.1.9.5

A3-Propagation Delay Measurement Report

06H

A3

6.1.9.6

A3-IS-95 FCH Forward

07H

A3

6.1.9.7

A3-IS-95 FCH Reverse

08H

A3

6.1.9.8

A3-Physical Transition Directive

09H

A3

6.1.9.11

A3-Physical Transition Directive Ack

0AH

A3

6.1.9.12

A3-IS-2000 FCH Forward

0BH

A3

6.1.9.13

A3-IS-2000 FCH Reverse

0CH

A3

6.1.9.14

A3-Traffic Channel Status

0DH

A3

6.1.9.15

A3-IS-2000 DCCH Forward

0EH

A3

6.1.9.16

A3-IS-2000 DCCH Reverse

0FH

A3

6.1.9.17

A3-IS-2000 SCH Forward

10H

A3

6.1.9.18

A3-IS-2000 SCH Reverse

11H

A3

6.1.9.19

Message Name

649

Section
Reference

TIA/EIA/IS-2001

Table 6 - 14 (cont.) - A3 and A7 Message Type II Values

Message
Type II
Value

Interface

Section
Reference

A7-Handoff Request

80H

A7

6.1.12.1

A7-Handoff Request Ack

81H

A7

6.1.12.2

A7-Drop Target

82H

A7

6.1.12.3

A7-Drop Target Ack

83H

A7

6.1.12.4

A7- Target Removal Request

84H

A7

6.1.12.5

A7- Target Removal Response

85H

A7

6.1.12.6

(unused value available)

86H

A7

6.1.12.7

(unused value available)

87H

A7

6.1.12.8

(unused value available)

88H

A7

6.1.12.9

A7-Source Transfer Performed

89H

A7

6.1.12.10

A7-Reset

8AH

A7

6.1.12.11

A7-Reset Acknowledge

8BH

A7

6.1.12.12

A7-Paging Channel Message Transfer

8CH

A7

6.1.12.13

A7-Paging Channel Message Transfer Ack

8DH

A7

6.1.12.14

A7-Access Channel Message Transfer

8EH

A7

6.1.12.15

A7- Access Channel Message Transfer Ack

8FH

A7

6.1.12.16

A7-Burst Request

90H

A7

6.1.12.17

A7-Burst Response

91H

A7

6.1.12.18

A7-Burst Commit

92H

A7

6.1.12.19

Message Name

All other values are reserved.

650

TIA/EIA/IS-2001

6.2.2.6

Channel Number

2
3

This element contains a logical channel number assigned to the equipment providing a
traffic channel.

4
5

This element is being kept in this revision of this standard for backward compatibility
with TSB80. It is likely to be removed from a future revision of this standard.
7

Octet

A1 Element Identifier

Channel Number

Channel Number

A default value of zero may be used by manufacturers.

651

TIA/EIA/IS-2001

6.2.2.7

2
3

Channel Type
This element contains information that Call Processing may use to determine the radio
resource that is required and is coded as follows:

Octet

A1 Element Identifier

Length

Speech or Data Indicator

Channel Rate and Type

Speech Encoding Algorithm/data rate + Transparency Indicator

The Length field is defined as the number of octets following the Length field.

The Speech or Data Indicator octet is coded as follows:

Table 6 - 15 - Channel Type - Speech or Data Indicator Values

7

Speech
setting

or

No Alert

Speecha

Dataa

Signalingb

a.

A dedicated terrestrial resource is also required

b.

A dedicated terrestrial resource is not required

652

Data

Indicator

TIA/EIA/IS-2001

The Channel Rate and Type is coded as follows:

Table 6 - 16 - Channel Type - Channel Rate and Type Values

7

Channel Rate and Type

Reserved (invalid)

DCCH

Reserved for future use (invalid)

Full rate TCH channel Bm

Half rate TCH channel Lm

3
4
5

If octet 3 indicates that the call is a speech call or signaling (e.g., DCCH) then octet 5 is
coded as follows:

Table 6 - 17 - Channel Type - Octet 5 Coding (Voice/Signaling Call)

7

Octet 5 coding if speech call or signaling

No Resources Required (invalid)

Reserved

Reserved

TIA/EIA-IS-2000 8 kb/s vocoder

8 kb/s enhanced vocoder (EVRC)

13 kb/s vocoder

ADPCM

All other values are reserved

7
8

If octet 3 indicates that the call is a data call then octet 5 shall be coded as follows:

Table 6 - 18 - Channel Type - Octet 5 Coding (Data Call)

7

ext.a

T/ NTb

3
Reserved

2
c

10

a.

reserved for extension.

11

b.

0-Transparent service, 1-Non-Transparent service.

12

c.

Currently unused and is encoded as 000000

653

TIA/EIA/IS-2001

6.2.2.8

RF Channel Identity
This element specifies the identity of an ANSI/EIA/TIA-553 radio channel.

Octet

A1 Element Identifier

Color Code

Reserved

N-AMPS

Reserved

ANSI
EIA/TIA553

(Timeslot Number)

Reserved

ARFCN (high part)

ARFCN (low part)

4
5
6

3
4
5
6

The Color Code field in octet 2 identifies the unique code used by ANSI/EIA/TIA-553
signaling system to distinguish the serving cell RF channels from cells reusing this RF
channel. For ANSI/EIA/TIA-553 cells, this color code corresponds to the 3 possible
Supervisory Audio Tones (SAT) used to distinguish this cells radio channels.

7
8
9
10
11
12

Octet 3 indicates a single signaling type allocated by a target BS in a hard handoff

procedure. The allocated signaling type is indicated when the corresponding bit is set
to 1. When the indicated signaling type is narrow band analog technology (N-AMPS),
then the Timeslot Number field represents the C12 and C13 narrow band bits which are
defined as the narrow band channel offset from the center frequency of the overlaid
channel N. It is coded as follows:

13

Table 6 - 19 - RF Channel Identity Timeslot Number

Value

14
15
16
17
18
19
20

Description

00

Centered on N

01

Channel below N

10

Channel above N

11

Reserved

The ARFCN (Absolute RF Channel Number) field in octets 5 and 6 may, depending on
the message in which it is included, identify the channel being used in the current
mobile connection; for example, to allow a remote sites scan receiver to measure the
uplink signal strength relative to the remote site. Alternatively, depending on the
message which it is included, this element may identify a target set channel for a
handoff. This ARFCN has a range of 0-2047 to accommodate the Frequency Bands of
each signaling system. The frequency bands are shown below for clarification.

654

TIA/EIA/IS-2001

1
2

The frequency bands reserved for ANSI/EIA/TIA-553 signaling systems are covered
with the following channel numbering schemes:

3
4
5

initial allocation of 20 MHz for both band A and B representing 1666 signaling and voice channels and numbered 1-333 for the A
band, and 334-666 for the B band.

6
7
8
9

extended allocation (ANSI/EIA/TIA-553) of 5 MHz for A, B, and

A bands representing 166 voice channels and numbered 667-716
for the A band, 717-799 for the B band, and 991-1023 for the A
band.

655

TIA/EIA/IS-2001

6.2.2.9

2
3

SID
This element provides the System Identification used by mobiles to determine
home/roam status. It is coded as follows:

A1 Element Identifier
Reserved

(MSB)

SID (high order)

SID (low order)

2
(LSB)

The SID is a 15 bit unique number assigned to each wireless system coverage area.

656

Octet

TIA/EIA/IS-2001

6.2.2.10

IS-95 Channel Identity

This element specifies identity information for one or more TIA/EIA-95 radio channels.

Hard
Handoff

Freq.
included

Octet

A1 Element Identifier

Length

Number of Channels to Add

Pilot PN
Power
Code (high Combined
part)

Frame Offset

Walsh Code Channel Index

4n

Pilot PN Code (low part)

4n+1

Reserved

ARFCN (low part)

ARFCN (high part)

4n+2

4n+3

3
4
5
6

Length is the number of octets that follow this octet. The length of this element is
variable because more than one target cell may be requested in a TIA/EIA-95 handoff.
Therefore, this element provides the flexibility to specify multiple TIA/EIA-950 channels
that the target BS can accommodate.

7
8
9
10
11

The Hard Handoff field, when set to 1, indicates that a hard handoff is required rather
than a soft/softer handoff. This field may be set in a handoff request or response. It
shall be set appropriately by the responding target BS to correspond to the action
committed by the target. If the Handoff Type element is also present in the same
message, the value of Handoff Type shall agree with the setting of this bit.

657

TIA/EIA/IS-2001

In this version of the standard, the Number of Channels field shall be set to 001.

2
3
4
5

The Frame Offset field will contain the number of 1.25 ms intervals relative to system
time that the forward and reverse traffic channels are delayed by the source. If this
element is returned to the source with the hard handoff indicator bit set, this field will
contain the frame offset delay required by the target.

6
7

The Walsh Code Channel Index specifies one of 64 possible Walsh Codes used to
channelize the downlink RF bit stream in a TIA/EIA-95 call.

8
9

Octets 4n+1 and 4n+2 contain the Pilot PN Code. The Pilot PN Code is one of 511
unique values for the Pilot Channel offset. The offsets are in increments of 64 PN chips.

10
11
12
13
14
15
16

The Power Combined field is a flag that, when set to 1, indicates diversity combining
of the power control sub-channel of this TIA/EIA-95 code channel with the previous
TIA/EIA-95 code channel listed in this element. In other words, if this is the second
replication of octets 4n through 4n+3, then the power control sub-channel of this
TIA/EIA-95 code channel is diversity combined with power control sub-channel of the
previous replication of octets 4n through 4n+3. The first occurrence of this field in the
IS-95 Channel Identity element is set to zero.

17
18
19
20
21

Frequency Included is a flag indicating whether the frequency assignment is included.

A 0 indicates no frequency assignment is present, a 1 indicates a frequency
assignment is present and is specified in the ARFCN field of this element. For code
channel assignments that are on the same TIA/EIA-95 channel frequency, this field shall
be set to 0.

22
23
24
25
26

The ARFCN (Absolute RF Channel Number) in octets 4n+2 and 4n+3 identifies the
TIA/EIA-IS-95 frequency being used in the current mobile connection. This ARFCN has
a range of 0-2047 to accommodate the various frequency bands. The frequency bands
are shown below for clarification. When the Frequency Included flag is set to zero, the
ARFCN field shall be set to all binary zeros.

27
28

The Frequency Bands reserved for TIA/EIA-95 signaling system in the North American
cellular band class are covered with the following channel numbering scheme:

29
30

A band allocation of 311 channels and numbered for TIA/EIA95TIA/EIA-IS-2000 as 1-311.

31
32

B band allocation of 289 channels and numbered for TIA/EIA95TIA/EIA-IS-2000 as 356-644.

33
34

A band allocation of 6 channels and numbered for TIA/EIA95TIA/EIA-IS-2000 as 689-694.

35
36

B band allocation of 39 channels and numbered for TIA/EIA95TIA/EIA-IS-2000 as 739-777.

37
38

A band allocation of 11 channels and numbered for TIA/EIA95TIA/EIA-IS-2000 as 1013-1023.

39
40

The Frequency Bands reserved in the North American PCS band class are covered with
the following channel numbering scheme:

41
42

6.2.2.11

A-F band allocation of channels numbered from 25-1175.

UNUSED SECTION

43

658

TIA/EIA/IS-2001

6.2.2.12

2
3

Encryption Information
This is a variable length element. It contains necessary information to control
encryption devices. This element is used during call setup and handoff.

Octet

A1 Element Identifier

Length

Encryption Info - 1

3-n

Encryption Info - 2

n+1 - m

...
Encryption Info - k

p-q

4
5
6
7

The Length field (octet 2) is a binary number indicating the absolute length of the
contents after the Length octet. Multiple instances of the Encryption Info field may
occur within this element. If no Encryption Info information is available, the Length
indicator shall be set to 0000 0000

The Encryption Info field is coded as follows:

Table 6 - 20 - Encryption Information - Encryption Parameter Coding

7
ext=1

Encryption Parameter Identifier

Octet

Status

Available

Encryption Parameter Length

(MSB)

Encryption Parameter value - octet 1

...

...

Encryption Parameter value - octet m

(LSB)

variable

10

Encryption Parameter Coding - Octet 1:

11
12
13
14
15

Bit 0 indicates if the encryption algorithm is available (supported). The BS sets this bit
appropriately when this element is included in a message being sent by a BS. The MSC
always sets this bit to 0 and the BS always ignores it when this element is included in
a message being sent by the MSC. Available is coded 1, and not available is coded
0.

16

The Status indication, bit 1, is coded 1 to indicate active and 0 to indicate inactive.

17

Bits 2 through 6 contain the Encryption Parameter Identifier; see the table below.

18

Bit 7 is an extension bit.

659

TIA/EIA/IS-2001

Table 6 - 21 - Encryption Information - Encryption Parameter Identifier Coding

Encryption
Parameter
Identifier Value

Encryption Parameter

00000

Not Used - Invalid value.

00001

SME Key: Signaling Message Encryption Key

00010

Reserved (VPM: Voice Privacy Mask)

00011

Reserved

00100

Private Longcode

00101

Data Key (ORYX)

00110

Initial RAND

All other values

Reserved

2
3
4

A brief description of the parameters and their typical usage is given below for
information only, and is not intended to limit the scope of application.

5
6

SME Key: Signaling Message Encryption Key, used for encryption of some signaling
messages in IS-95, IS-95A, TIA/EIA-IS-2000. Key length is 8 octets.

7
8
9

Private Longcode:
Encryption parameter for IS-95, IS-95A, , TIA/EIA-IS-2000.
Key length is 42 bits, encoded in 6 octets, such that the 6 unused bits are set equal to
'0', and occupy the high-order positions of the most significant octet.

10
11

Data Key (ORYX):

Parameter intended for encryption of user data in
TIA/EIA/IS-707. Key length is 4 octets.

12
13
14

Initial RAND:
Parameter used for data encryption in TIA/EIA/IS-707. When data
encryption is enabled, this parameter shall be passed to the target BS from the source
BS so that the same value of RAND can be used. The key length is 4 octets.

15

Encryption Parameter Coding - Octets 2 and 3 - n:

16
17
18

The second octet indicates the length of the parameter as a binary number. Octets 3
through n contain the parameter value. The length of the parameter may be zero in
which case octet 2 is set to a binary value of zero.

660

TIA/EIA/IS-2001

6.2.2.13

2
3
4

Voice Privacy Request

This is a fixed length element with zero octets of content. Only the element identifier is
included (type 2). When present, it indicates that the MS has requested Voice Privacy.
TIA/EIA-IS-2000

Element Identifier

661

Octet
1

TIA/EIA/IS-2001

6.2.2.14

2
3

Physical Channel Info

This element provides information about a set of physical channels for a call
association.

Octet

A3/A7 Element Identifier

Length

Frame Offset

A3 Traffic Channel
Protocol Stack
ARFCN

Pilot Gating
Rate

Reserved

(MSB)

OTD

Physical Channel 2

4
(LSB)

Count of Physical Channels

Physical Channel 1

4
5

Length:

This field indicates the number of octets in this element following the
Length field.

Frame Offset:

This field indicates the frame offset for the given physical channel..

7
8
9
10
11

A3 Traffic Channel Protocol Stack:

This field indicates the protocol stack to be used with A3 traffic
channels attached to the given physical channels. Valid values are
shown below.
Table 6 - 22 - A3 Traffic Channel Protocol Stack
Value
001
All other values

12
13
14
15
16
17

Pilot Gating Rate

Protocol Stack
AAL2 / ATM / Physical Layer
Reserved

The actual Reverse Pilot Gating Rate. This field is used to indicate
the gating rate for the Reverse Pilot channel as shown in Table 6 - 23 Reverse Pilot Gating Rate - Pilot Gating Rate below
This field is used for the DCCH. If the FCH is being used, then this
field is set to 00, i.e., there is no pilot gating on the FCH.

Table 6 - 23 - Reverse Pilot Gating Rate - Pilot Gating Rate

Binary Values

Meaning

00

Gating rate 1

01

Gating rate 1/2

10

Gating rate 1/4

11

Reserved

18

662

TIA/EIA/IS-2001

1
2

ARFCN:

This field indicates the Absolute Radio Frequency Channel Number

relative to the band class for the call association.

3
4
5

NOTE: The Frame Offset, A3 Traffic Channel Protocol Stack, Pilot Gating Rate and ARFCN are
the same for ALL physical channels of a call association.

6
7
8

OTD:

This bit shall be set to 1 to indicate that the mobile will be using
OTD. It is set to 0 otherwise.

9
10
11
12

Count of Physical Channels:

The number of physical channels represented in this element. In this
version of the standard the value shall be 1H or 2H. If the value is 1H,
then Physical Channel 2 shall be coded as '0000'.

13
14
15
16
17
18
19
20

Physical Channel n:

21

These fields contain the binary values used to indicate the type of
physical channel associated with the indicated cells. Valid values are
shown below. In this version of the standard, a maximum of one
physical channel of each type is allowed per call association. A call
association is not allowed to have TIA/EIA/IS-95 and TIA/EIA/IS2000 physical channel types simultaneously; nor is it allowed to
request FCH, SCH, and DCCH simultaneously.
Table 6 - 24 - Physical Channel Info - Physical Channel
Value (hex)

Physical Channel Type

0H

IS-95 Fundamental Channel TIA/EIA/IS-95

1H

Fundamental Channel (FCH) TIA/EIA/IS-2000

2H

Supplemental Channel (SCH) TIA/EIA/IS-2000

3H

Dedicated Control Channel (DCCH) TIA/EIA/IS-2000

All other values

Reserved

22

Valid combinations are the following:

23

Count

Physical Channel 2

Physical Channel 1

24
25
26
27

0H (N/A)

0H (IS-9)5, or
1H (FCH), or
2H (SCH), or
3H (DCCH)

28
29
30
31

2H (SCH)
1H (FCH)
3H (DCCH)
2H (SCH)

1H (FCH), or
2H (SCH), or
2H (SCH), or
3H (DCCH)

663

TIA/EIA/IS-2001

6.2.2.15

Classmark Information Type 2

2
3
4

The Classmark Information Type 2 defines certain attributes of the mobile station
equipment in use on a particular transaction, thus giving specific information about the
mobile station. It is coded as follows:
7

Mobile P_REV

A1 Element Identifier

Length

Reserved

See List
of Entries

RF Power Capability

Reserved
NAR_

IS-95

Octet

Slotted

Reserved

AN_

DTX

Mobile
Term

Reserved

CAP
Reserved

Reserved

Mobile
Term

PSI

SCM Length

Station Class Mark

Count of Band Class Entries

10

Band Class Entry Length

11

Reserved

Band Class 1

12

Reserved

Band Class 1 Air Interfaces Supported

13

Band Class 1 MS Protocol Level

14

...

...

Reserved

Band Class n

Reserved

Band Class n Air Interfaces Supported

m+1

Band Class n MS Protocol Level

5

The Length field is defined as the number of octets following the Length field.

664

m+2

TIA/EIA/IS-2001

1
2

The RF Power Capability field is coded as follows:

Table 6 - 25 - Classmark Information Type 2 - RF Power Capability

Binary Values

Meaning

ANSI/EIA/
TIA-553

TIA/EIAIS-2000

000

Class 1, vehicle and portable

4W

1.25 W

001

Class 2, portable

1.6 W

0.5 W

010

Class 3, handheld

0.6 W

0.2 W

011

Class 4, handheld

100

Class 5, handheld

101

Class 6, handheld

110

Class 7, handheld

111

Class 8, handheld

Unused

4
5
6

Each mobile has an assigned power class capability that needs to be known in order to
regulate uplink power control. Each power class is unique to the specific signaling
system. Power classes can range from 1 to 8. All other values are reserved.

7
8
9
10
11
12
13
14
15
16

The See List of Entries field is an escape mechanism that allows octets 3 through 6 to be
ignored by the receiver. When set to 1, the receiver shall ignore the contents of
octets 3 through 6 and shall instead use the contents of octets 7 through the end of the
element to derive the valid class mark information. When this field is set to 0, the
receiver shall process the contents of octets 3 through 6 and ignore any additional data
that may be present after these octets. A BS shall be required to populate both portions
of this element, i.e. octets 3-6 and 7 through the end-of-element, in order to provide
backward compatibility with CDG IOS V3.x.y. The information contained in the first
band class entry set in octets 12-14 shall be applicable to the current band class of the
mobile.

17
18
19
20
21
22

The Mobile P_REV field in octet 3, and the Band Class 1 MS Protocol Level in octet 14,
contain the current mobile station protocol revision level as defined in TIA/EIA-IS-2000.
The Mobile P_REV field in octet 3 contains the low order 3 bits of the 8-bit MS Protocol
Level. The source BS shall always set this field when sending this element to the MSC
on a message. The MSC shall transparently transfer this value when forwarding this
element to the target BS. The target BS may choose to ignore the value.

665

TIA/EIA/IS-2001

1
2
3
4

The Mobile Term field in bit 1 of octet 5 and bit 1 of octet 7 is set to 1 for TIA/EIA-IS2000 mobiles currently capable of receiving incoming calls, and is set to 1 for all other
mobile types. It is set to 0 for TIA/EIA-IS-2000 mobiles incapable of receiving
incoming calls.

5
6
7

The DTX field in bit 2 of octet 5 indicates whether or not the mobile is capable of
discontinuous transmission. It is set to 1 if the mobile is capable of DTX, otherwise it
is set to 0.

8
9

The Slotted field in bit 5 of octet 5 indicates that the mobile is operating in slotted
paging request mode when set to 1 (TIA/EIA-IS-2000 only).

10
11

The IS-95 field in bit 6 of octet 5 indicates that the MS is capable of supporting the
TIA/EIA-IS-2000 air interface.

12
13

The NAR_AN_CAP field in bit 7 of octet 5 is set to 1 for an MS that is capable of

supporting narrow band analog technology (N-AMPS), and is set to 0 otherwise.

14
15
16

The PACA Supported Indicator (PSI) field in bit 0 of octet 7 indicates the mobile
stations capability to support PACA. This field is set to 1 if the mobile station
supports PACA; otherwise it is set to 0.

17
18

The SCM Length field indicates the length of the Station Class Mark field in the
following octet(s).

19

The Station Class Mark field shall be coded as specified in TIA/EIA-IS-2000.

20
21
22
23
24
25

The Count of Entries field indicates the number of band class information entries that
follow. These entries each contain information on the air interface capabilities and
protocol level information of the MS with respect to a specific band class. At least one
entry for the mobiles current band class is required. The current band class information
shall be included in the first band class entry information set. Data pertaining to other
band classes supported by the mobile may also be included.

666

TIA/EIA/IS-2001

1
2
3

The Band Class Entry Length field indicates the length of the set of parameters
associated with each band class entry set. The length of each band class entry set
included in this element shall be the same.

The Band Class n field shall be a binary value coded as shown in section 6.2.2.106.

5
6
7
8
9

The Band Class n Air Interface Standard field shall be a binary value coded as defined
in the TIA/EIA-IS-2000 Operating Mode Information record. A copy of this bit-map
table is included here for reference. Note: In the event of a discrepancy between the
table as it appears here and in TIA/EIA-IS-2000, the TIA/EIA-IS-2000 table shall take
precedence.

10
11

Table 6 - 26 - Classmark Information Type 2 - Air Interfaces Supported (Mobile

P_REV less than or equal to three).
Binary Values

Meaning

0000 0000

TIA/EIA-95 CDMA mode in Band Class 0

0000 0001

TIA/EIA-95 CDMA mode in Band Class 0

0000 0010

TIA/EIA-95 analog mode

0000 0011

TIA/EIA/IS-91 wide analog mode

0000 0100

TIA/EIA/IS-91 narrow analog mode

All other
values

Reserved

12
13
14

Table 6 - 27 - Classmark Information Type 2 - Air Interfaces Supported (Mobile

P_REV greater than three).
Binary Values

Standards for Band Class 0 and

Band Class 1

Meaning

0000 0000 or
0000 0001

TIA/EIA-95

CDMA Mode

0000 0010

TIA/EIA-95

Analog Mode

0000 0011

TIA/EIA/IS-91

Wide Analog Mode

0000 0100

TIA/EIA/IS-91

Narrow
Mode

Analog

All other values reserved.

15
16
17
18
19
20

The Band Class n MS Protocol Level field contains the mobile station protocol revision
level as defined in TIA/EIA-IS-2000. The source BS shall always set this field when
sending this element to the MSC on a message. The MSC shall transparently transfer
this value when forwarding this element to the target BS. The target BS may choose to
ignore the value.

667

TIA/EIA/IS-2001

1
2

6.2.2.16

Mobile Identity

3
4
5

The purpose of the mobile identity information element is to provide the mobile station
Electronic Serial Number (ESN), the International Mobile Subscriber Identity (IMSI), or
the Broadcast Address.

6
7
8
9
10

The International Mobile Subscriber Identifier (IMSI) does not exceed 15 digits and the
ESN is a 32 bit field separated into a Manufacturer code, the Serial Number and a
Reserved field. The Broadcast Address is used to deliver Short Messages to groups of
subscribers and has the format specified in section 3.4.3.2 of IS-637A and is mapped to
the Mobile Identity element as shown below.

11

The following is the Mobile Identity element coding: TIA/EIA-IS-2000.

12
13
14

Warning: The length limit for this information element was 10 octets in IOS v2.0a, IOS
v2.1, and IOS v3.0.0.
Care needs to be exercised for interoperability with
implementations based on the previous standard.
7

Identity Digit 1

A1 Element Identifier

Length

Odd/even
Indicator

Identity Digit 3

Type of Identity
Identity Digit 2

3
4

...
Identity Digit N+1

Identity Digit N

15
16

Octet

The Length field is defined as the number of octets following the Length field.

668

variab
le

TIA/EIA/IS-2001

The Type of Identity is defined as follows:

Table 6 - 28 - Mobile Identity - Type of Identity Coding

Binary Values

Meaning

000

No Identity Code
TIA/EIA-IS-2000

010

Broadcast Address

101

ESN

110

IMSI

3
4

The Odd/Even Indicator (octet 3; bit 3) field is set to 0 for an even number of digits
and to 1 for an odd number of identity digits.

The identity digits (octet 3 etc.) are coded as follows:

6
7
8

The International Mobile Subscriber Identifier fields are coded using BCD coding
format. If the number of identity digits is even then bits 4 to 7 of the last octet shall be
filled with an end mark coded as 1111.

9
10

The ESN is not separated into digits, and occupies octets 4-7 with the most significant
bit in octet 4 bit 7. Identity Digit 1 in octet 3 is unused and coded as 0000.

11
12

For Broadcast Address (type 010), the Mobile Identity is encoded as specified below
based on IS-637A.
7

A1 Element Identifier

Length

Reserved

Type of Identity

Priority

Message ID

Zone ID
(MSB)

Octet

Service

6
(LSB)

Language

7
8

13
14

Length:

This field indicates the number of octets in this element following the
Length field.

15

Type of Identity: This field is defined as shown above.

16
17

Priority:

This field indicates the priority level of this broadcast message to the
MS.

18
19
20
21

Message ID:

This field contains a value used by the MS to distinguish between

different messages from the same broadcast service transmitted
within the time period established for broadcast duplicate detection in
the mobile station.

669

TIA/EIA/IS-2001

1
2
3

Zone ID:

This field contains a value used by the MS to distinguish between

messages from the same broadcast service transmitted in different
geographic regions.

4
5
6
7

Service:

This field contains the service category. The mobile station should
receive and process the broadcast message or page if the Service field
contains a service category that the mobile station has been
configured to receive.

8
9

Language:

This field contains a value used by the MS to distinguish the

language used in the content of the broadcast message.

670

TIA/EIA/IS-2001

6.2.2.17

2
3
4

Slot Cycle Index

The Slot Cycle Index element is unique to TIA/EIA-IS-2000 mobiles. It contains a
parameter used in computation of the paging timeslot, allowing discontinuous reception
in the mobile station. It is coded as follows:

A1 Element Identifier

Reserved
5
6
7

6.2.2.18

Priority
This element indicates the priority of the call and is coded as follows:

Reserved

10
11

Slot Cycle Index

Note that the Classmark Information Type 2 element contains an indication of whether
the MS is operating in slotted or non-slotted mode. See also section 6.2.2.15.

Octet

Octet

A1 Element Identifier

Length

Call Priority

Queuing
Allowed

Preemption
Allowed

The Length field is defined as the number of octets following the Length field.
In octet 3, the priority field allows prioritizing of requests for mobile connections. The
priorities are ordered from 0000 (highest priority) to 1111 (lowest priority).

671

TIA/EIA/IS-2001

1
2

The meaning of the priorities are as follows:

Table 6 - 29 - Priority - Call Priorities

Binary Values
bits 5-4-3-2

Meaning

0000

Priority Level 0 (highest)

0001

Priority Level 1

0010

Priority Level 2

0011

Priority Level 3

0100

Priority Level 4

0101

Priority Level 5

0110

Priority Level 6

0111

Priority Level 7

1000

Priority Level 8

1001

Priority Level 9

1010

Priority Level 10

1011

Priority Level 11

1100

Priority Level 12

1101

Priority Level 13

1110

Priority Level 14

1111

Priority Level 15 (lowest)

672

TIA/EIA/IS-2001

Table 6 - 30 - Priority - Queuing Allowed

Binary Values
bit 1

Meaning

queuing not allowed

queuing allowed

2
3

Table 6 - 31 - Priority - Preemption Allowed

Binary Values
bit 0

Meaning

preemption not allowed

preemption allowed

4
5

673

TIA/EIA/IS-2001

6.2.2.19

Cause

2
3

This element is used to indicate the reason for occurrence of a particular event and is
coded as shown below.
7

Octet

Element Identifier

Length

0/1

Cause Value

4
5
6
7

This information element is used on multiple interfaces. When the information element
is included in a message that is sent on the A1 or A9 interface, the Element Identifier
field is coded as 04H. When the information element is included in a message sent on
the A7 interface, the Element Identifier field is coded as 08H.

The Length field is defined as the number of octets following the Length field.

9
10
11
12

The Cause Value field is a single octet field if the extension bit (bit 7) is set to 0. If bit 7
of octet 3 is set to 1 then the Cause Value is a two octet field. If the value of the first
octet of the cause field is 1XXX 0000 then the second octet is reserved for national
applications, where XXX indicates the Cause Class as indicated in the table below.

13

Table 6 - 32 - Cause Class Values

Binary Values

Meaning

000

Normal Event

001

Normal Event

010

Resource Unavailable

011

Service or option not available

100

Service or option not implemented

101

Invalid message (e.g., parameter out of range)

110

Protocol error

111

Interworking

674

TIA/EIA/IS-2001

Table 6 - 33 - Cause Values

6

HEX
VALUE

CAUSE

Normal Event Class (000 xxxx and 001 xxxx)

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1

0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
0
0
0
0
0
1
1

0
0
0
0
1
1
1
1
0
0
0
0
1
1
1
1
0
0
0
0
1
0
1

0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
0
1
1
0
1
0

0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
1

0
0
0
0
0

1
1
1
1
1

0
0
0
0
0

0
0
0
0
0

0
0
0
1
1

0
0
1
0
1

0
1
0
1
0

00
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
11
12
13
14
1B
1D

Radio interface message failure

Radio interface failure
Uplink Quality
Uplink strength
Downlink quality
Downlink strength
Distance
OAM&P intervention
MS busy
Call processing
Reversion to old channel
Handoff successful
No response from MS
Timer expired
Better cell (power budget) (Handoff Required msg.)
Interference (Handoff Required msg.)
Packet call going dormant
Service option not available
Invalid Call
Successful operation
Normal call release
Inter-BS Soft Handoff Drop Target
Intra-BS Soft Handoff Drop Target

Resource Unavailable Class (010 xxxx)

20
21
22
25
26

Equipment failure
No radio resource available
Requested terrestrial resource unavailable
BS not equipped
MS not equipped (or incapable)

675

TIA/EIA/IS-2001

Table 6 - 34 (cont.) - Cause Values

6

0
0
0
0

1
1
1
1

0
0
0
0

1
1
1
1

0
0
1
1

0
0
0

1
1
1

1
1
1

0
0
0

0
0
0

1
1
1
1
1

0
0
0
0
0

0
0
0
0
0

0
0
0
0
1

0
0
0
0
1

Hex Value

Cause

0
1
29
PACA Call Queued
1
1
2B
Alternate signaling type reject (Handoff Failure msg.)
0
1
2D
PACA Queue Overflow
1
0
2E
PACA Cancel Request Rejected
Service or Option Not Available Class (011 xxxx)
0
0
30
Requested transcoding/rate adaptation unavailable
0
1
31
Lower priority radio resources not available
1
0
32
PCF resources not available
1
1
33
TFO Control request Failed
Service or Option Not Implemented Class (100 xxxx)
0
0
40
Ciphering algorithm not supported
0
1
41
Private Long Code not available or not supported.
1
0
42
Requested MUX option or rates not available.
1
1
43
Requested Privacy Configuration unavailable
a
1
1
4F
Terrestrial circuit already allocated.

1
1

0
0

1
1

0
1

0
1

0
1

Invalid Message Class (101 xxxx)

0
50
Terrestrial circuit already allocated
a
1
5F
Protocol Error between BS and MSC.

1
1
1
1
1
1
1
1
1
1

1
1
1
1
1
1
1
1
1
1

1
1
1
1
1
1
1
1
1
1

0
0
0
0
0
0
1
1
1
1

0
0
1
1
1
1
0
0
0
1

1
1
0
0
1
1
0
0
1
1

0
1
0
1
0
1
0
1
0
1

Protocol Error (110 xxxx)

60
Protocol Error between BS and MSC
Interworking (111 xxxx)
71
ADDS message too long for delivery on the paging
channel
72
MS-to-IWF TCP connection failure
73
ATH0 (Modem hang up) Command
74
+FSH/+FHNG (Fax session ended) Command
75
No carrier
76
PPP protocol failure
77
PPP session closed by the MS
78
Do not notify MS
79
PDSN resources are not available
7A
Data ready to send
7F
Handoff procedure time-out (HO Failure message)

All other values

2

Reserved for future use.

a.

Used prior to version 3.0.0 of this specification only.

676

TIA/EIA/IS-2001

1
2

If The MSC uses a CIC value that is unknown to the BS, the cause value used shall be
25H (BS not equipped) in the appropriate message.

3
4

Unused cause values found in this table will be removed in a future version of this
standard.

677

TIA/EIA/IS-2001

6.2.2.20

2
3

Cell Identifier
This element uniquely identifies a particular cell and is of variable length depending on
how the cell is identified. The fields of this element are shown below:

Octet

Element Identifier

Length

Cell Identification Discriminator

Cell Identification

variable

4
5
6
7

This information element is used on multiple interfaces. When the information element
is included in a message that is sent on the A1 interface, the Element Identifier field is
coded as 05H. When the information element is included in a message sent on the A3 or
A7 interface, the Element Identifier field is coded as 08H.

8
9

The Length field is defined as the number of octets following the Length field. The
length depends on the Cell Identification Discriminator (octet 3).

10
11
12
13

The Cell Identification Discriminator is a binary number indicating if the whole or a part
of Cell Global Identification (e.g., one or more of the following: MCC, MNC, LAC,
MSCID, CI) is used for cell identification in octets 4 through n. The Cell Identification
Discriminator is coded as follows:

14

Table 6 - 35 - Cell Identifier - Cell Identification Discriminator List

Binary Values

15
16

Meaning

0000 0010

Cell Identity (CI) is used to identify the cell.

0000 0101

Location Area Code (LAC) is used to identify all cells within a location area.

0000 0111a

IS-41 whole Cell Global Identification (ICGI) is used to identify the cell.
a.

When the Cell Identifier is used to identify a cell controlled by

another MSC, type 0000 0111 will be used..

678

TIA/EIA/IS-2001

1
2
3

Table 6 - 36 - Cell Identifier - Cell Identification Discriminator = 0000 0010

7

Octet

CI value

CI value cont.

4
5

Table 6 - 37 - Cell Identifier - Cell Identification Discriminator = 0000 0101

7

Octet

LAC

LAC cont.

7
8

Table 6 - 38 - Cell Identifier - Cell Identification Discriminator = 0000 0111

7

Octet

MSCID

MSCID continued

MSCID continued

CI value

CI value continued

MSCID, MSC Identifier (octets 4 through 6):

10

The MSCID is coded as defined in IS-41-C, Section 6.5.2.82.

11
12

MSCID is 3 octets long where the first two octets (octets 4 and 5) represent Market ID
and the last octet represents the Switch Number.

13
14

In the MSCID field, bit 7 of octet 4 is the most significant bit and bit 0 of octet 5 is the
least significant bit of the Market ID field.

15

In the MSCID field bit 7 of octet 6 is the most significant bit of the Switch Number field.

16

CI, Cell Identity value (octets 7 and 8):

17
18

In the CI value field bit 7 of octet 7 is the most significant bit and bit 0 of octet 8 is the
least significant bit. Bits 3 to 0 of octet 8 contain the sector number (0H = omni).

19

679

TIA/EIA/IS-2001

Table 6 - 39 - Cell Identifier - Cell Identification Discriminator = 0000 1000

7

Octet

MCC digit2

MCC digit1

MNC digit3

MCC digit 3

MNC digit2

MNC digit1

LAC

LAC cont.

CI value

CI value cont.

10

MCC, Mobile Country Code (octets 4 and 5):

The MCC field is coded as in ITU Rec. E212, Annex A.

MNC, Mobile Network Code (octets 5 and 6):

5
6
7
8
9

The coding of this field is the responsibility of each administration but BCD
coding shall be used. If an administration decides to include only one digit in the
MNC then bits 4-7 of octet 6 and bits 4-7 of octet 5 are coded as 1111. If an
administration decides to include only two digits in the MNC then bits 4-7 of
octet 5 are coded as 1111.

10

LAC, Location Area Code (octets 7 and 8):

11
12

In the LAC field bit 7 of octet 7 is the most significant bit and bit 0 of octet 8 is
the least significant bit.

13

The coding of the location area code is the responsibility of each administration.

14

CI, Cell Identity value (octets 9 and 10):

15
16

In the CI value field bit 7 of octet 9 is the most significant bit and bit 0 of octet 10
the least significant bit.

17
18
19

The coding of the cell identity is the responsibility of each administration.

Coding using full hexadecimal representation may be used. The cell identity
consists of 2 octets maximum.

20
21

If an administration has chosen N bits for the cell identity where N <16 then the
additional bits up to 16 are coded with a 0 in each in the following way:

22

If 8 <N<16 the bits N-8 through 7 of octet 9 are coded with a 0 in each.

23

If N=8 then octet 9 is coded with a 0 in each bit.

24
25

If N<8 then octet 9 is coded with a 0 in each bit and bits N through 7 of octet 3
are coded with a 0 in each.

26
27
28
29

Location Area Code (LAC) is an operator defined identifier for a set of cells. LAC is not
defined by the IOS for features. In this IOS document the LAC field is supported ;
however, it may be ignored or filled with zeros at the suppliers option , and must not
cause a protocol error.

30

The Cell Identifier within an MSC is unique.

680

TIA/EIA/IS-2001

1
2

6.2.2.21

3
4

Cell Identifier List

This element uniquely identifies cells and is of variable length containing the following
fields:

A1 Element Identifier

Length

Cell Identification Discriminator

Cell Identification 1

...

Cell Identification n
5
6

Octet

variable

The Length field is a binary value indicating the number of octets following the Length
field.

7
8

6.2.2.22

9
10
11
12

Circuit Identity Code

This element defines the terrestrial channel over which the call will pass. It contains the
5 least significant bits of a binary representation of the timeslot assigned to the circuit.
The remaining bits in the CIC are used where necessary, to identify one among several
systems interconnecting an originating and destination point.

A1 Element Identifier

Octet
1

13

Bits a-k define the PCM multiplexer in use.

14

Bits xxxxx define the actual timeslot in use.

15
16
17

The Circuit Identity Code defines the PCM multiplex and timeslot in use at the MSC. In
cases where re-multiplexing takes place between the MSC and BS a translation may be
necessary at the BS.

681

TIA/EIA/IS-2001

6.2.2.23

Circuit Identity Code Extension

This variable length element defines a full rate terrestrial channel.

7

(MSB)

Octet

A1 Element Identifier

Length

Circuit Identity Code

Circuit Identity Code (cont.)

Reserved

(LSB)
Circuit Mode

4
5

The Length field is defined as the number of octets following the Length field.

The Circuit Identity Code field is coded as specified in octets 2-3 of section 6.2.2.22.

5
6

The Circuit Mode field informs the MSC about the use of this element, and is encoded
as follows:

Table 6 - 40 - Circuit Identity Code Extension - Circuit Mode Field

Binary
Value

Name

0000

Full-rate

Meaning
Full-rate circuit operation.

All other values reserved

8
9

6.2.2.24

Unused

682

TIA/EIA/IS-2001

1
2

6.2.2.25

Downlink Radio Environment

3
4

This element includes signal strength measurement information that was made by the
mobile. It is of variable length and is coded as follows:
7

Reserved

Reserved

Octet

A1 Element Identifier

Length

Number of cells

Cell Identification Discriminator

Cell Identification 1

5-var

Downlink Signal Strength Raw

CDMA Target One Way Delay (high part)

k+1

CDMA Target One Way Delay (low part)

k+2

...

...

Cell Identification n

m-var

Downlink Signal Strength Raw

n+1

CDMA Target One Way Delay (high part)

n+2

CDMA Target One Way Delay (low part)

n+3

The Length field is defined as the number of octets following the Length field.

6
7
8

Octet 3 indicates the number of cells represented by this element. For each cell, the Cell
Identification, Downlink Signal Strength Raw, and CDMA Target One Way Delay fields
are replicated.

9
10

In octet 4, the Cell Identification Discriminator is coded per section 6.2.2.20. It applies to
all Cell Identification fields present in this element.

11
12
13

The Cell Identification is coded as per the equivalent octets described in section
6.2.2.20, and shall uniquely identify one cell. Only one cell can be indicated per
replication.

14
15
16
17

Downlink Signal Measurement Raw is an average signal level measured by the mobile
for the specified cell. The method of measurement is unique to the signaling system.
The signal level is the last measurement average received from the mobile in its raw, not
normalized format.

18

The range of values for this field is 0 to 63 where the units are defined by

19

2 10 log10 PS

20
21
22
23

where PS is the strength of this pilot measured as the sum of ratios of received pilot
energy per chip to the total received spectral density (noise and signals) of at most k
usable multi-path components, where k is the number of demodulating elements
supported by the mobile station.

683

TIA/EIA/IS-2001

684

TIA/EIA/IS-2001

1
2

The CDMA Target One Way Delay field shall contain the estimated one-way delay from
the MS to the associated target cell, according to the information reported by the MS.

The CDMA Target One Way Delay is specified in units of 100 ns.

The BS calculates the value of the CDMA Target One Way Delay as follows:
(Target PN phase measured by the MS - Target pilot offset index 64 +
Serving one way delay in PN chips) / 0.12288

5
6
7

The target PN phase is reported by the MS in the Pilot Strength Measurement Message.

8
9

The target pilot offset index is derived by the BS from information in the Pilot Strength
Measurement Message.

10
11

The serving one way delay is maintained in information known to the BS.
6.2.2.26

Unused

6.2.2.27

Unused

6.2.2.28

Unused

6.2.2.29

Unused

12
13
14
15
16
17
18
19

685

TIA/EIA/IS-2001

6.2.2.30

PDSN IP Address

2
7

Octet

A1 Element Identifier

Length

(MSB)

3
PDSN IP Address

4
5
(LSB)

3
4

Length

5
6

PDSN IP Address

This field contains the number of octets in this element following this
field as a binary number.
This field contains an IPv4 address for a PDSN.

686

TIA/EIA/IS-2001

6.2.2.31

2
3

Handoff Power Level

This element contains the desired Handoff Power Level of the MS. This element is not
applicable to CDMA.

Reserved

Octet

A1 Element Identifier

Length

Number of Cells

ID Type

Handoff Power Level

Cell Identification 1

Reserved

Handoff Power Level

4
5-8
9

Cell Identification 2

10-11

...

...

Reserved

Handoff Power Level

Cell Identification n

variable
variable

The Length field is defined as the number of octets following the Length field.

5
6

Octet 3 indicates the number of cells represented by this element. For each cell, the
Handoff Power Level and Cell Identification fields are replicated.

7
8

The Handoff Power Level element provides a recommendation of the uplink power level
that the mobile should use when accessing the target on handoff.

9
10
11

The ID Type field in octet 4 specifies the type of Cell Identification If the ID Type field
is set to 01, Cell Identification shall be formatted according to Cell Identification
Discriminator 0000 0111.. All other ID Type value are reserved.

12
13
14
15
16

The Cell Identification field is coded as per the Cell Identification field described in
section 6.2.2.20. The first instance of the Cell Identification field in this element shall be
formatted according to Cell Identification Discriminator Cell Identification Discriminator
0000 0111. Subsequent instances shall be formatted according to Cell Identification
Discriminator 0000 0010.

687

TIA/EIA/IS-2001

6.2.2.32

USER Zone ID

This element uniquely identifies a particular User Zone

7

(MSB)

Octet

A1 Element Identifier

Length

UZID

3
(LSB)

3
4
5

Length

The length field contains the binary value that indicates the number
of octets in the element following the Length field.]

UZID:

This field contains a User Zone ID value as sent by the MSC or MS.
The MSC is responsible for any mapping of this 16-bit value to the
24-bit value defined in ANSI/TIA/EIA-41.

6
7
8
9
10
11

688

TIA/EIA/IS-2001

6.2.2.33

Reverse Pilot Gating Rate

2
3
4

This element indicates the Reverse Pilot Gating Rate to be used by the mobile as well as
the explicit time of transition to the new gating rate. The BTS uses this information to
process inner loop power control.
7

Octet

A3/A7 Element Identifier

Length

Reserved

Pilot Gating Rate

ACTION_TIME

3
4

5
6
7

Length

The length field contains the binary value that indicates the number
of octets in the element following the Length field.

Reserved

All reserved bits shall be set to 0.

Pilot Gating Rate

The actual Reverse Pilot Gating Rate. This field is used to indicate
the gating rate for the Reverse Pilot channel as shown in below. This
field is used for the DCCH. If the FCH is being used, then this field is
set to 00, i.e., there is no pilot gating on the FCH.

9
10
11
12
13

Table 6 - 41 - Reverse Pilot Gating Rate - Pilot Gating Rate

Binary Values

Meaning

00

No Gating

01

Gating rate 1/2

10

Gating rate 1/4

11

Reserved

14
15
16
17
18
19
20
21
22
23

ACTION_TIME

This field shall be set by the BSC to the CDMA System Time (see
TIA/EIA/IS-2000) in units of 80 ms (modulo 64) at which the transition
to the new reverse pilot gating rate is to take effect. This field shall
have the same setting as was conveyed to the MS in a Resource
Allocation Message, Resource Allocation Mini-Message, Universal
Direction Handoff Message, Extended Release Message, or Extended
Release Mini-Message on the forward traffic channel (see TIA/EIA/IS2000.5). The action time value conveyed to the mobile station is
derived by taking the least significant 6 bits of this 8-bit field.

689

TIA/EIA/IS-2001

6.2.2.34

IS-2000 Channel Identity

2
3

This element specifies identity information for one or more

channels.
7

OTD

TIA/EIA-IS-2000 radio

A1 Element Identifier

Length

2
Frame Offset

Channel Count

Physical Channel Type

Reserved

Pilot Gating Rate

Pilot PN
Code
(high part)

QOF Mask

3
4n

Walsh Code Channel Index

(high part)

4n+1

Walsh Code Channel Index (low part)

4n+2

Pilot PN Code (low part)

4n+3

Reserved

Freq.
Included

ARFCN (high part)

ARFCN (low part)

4
5
6
7
8

Octet

4n+4

4n+5

Length:

is the number of octets that follow this octet. The length of this
element is variable because more than one target cell may be
requested in a hard handoff. Therefore, this element provides the
flexibility to specify multiple channels that the target BS can
accommodate.

9
10

OTD:

This bit shall be set to 1 to indicate that the mobile will be using
OTD. It is set to 0 otherwise.

11

Channel Count

Number of the channels specified in this element.

12
13
14

Frame Offset:

This field will contain the number of 1.25 ms intervals relative to

system time that the forward and reverse traffic channels are delayed
by the source.

15
16
17

Physical Channel Type:

18

This field contains the binary value used to indicate the type of
physical channel. Valid values are shown below.
Table 6 - 42 - IS-2000 Channel Identity - Physical Channel Type
Hex Values

Meaning

01H

Fundamental Channel (FCH) TIA/EIA/IS-2000

02H

Dedicated Control Channel (DCCH)

TIA/EIA/IS-2000

03H

Supplemental Channel (SCH) TIA/EIA/IS-2000

80H to 9FH
All other values

Reserved for UMTS

Reserved

19

690

TIA/EIA/IS-2001

1
2
3

Pilot Gating Rate:

The actual Reverse Pilot Gating Rate. This field is used to indicate
the gating rate for the Reverse Pilot channel as shown in Table 6 - 43 IS-2000 Channel Identity - Pilot Gating Rate

4
5

Table 6 - 43 - IS-2000 Channel Identity - Pilot Gating Rate

Binary Values

Meaning

00

Gating rate 1

01

Gating rate 1/2

10

Gating rate 1/4

11

Reserved

6
7
8

QOF Mask:

This field contains the QOF (Quasi-Orthogonal Function) mask index

as specified in TIA/EIA/IS-2000.2.

9
10
11
12

Walsh Code Channel Index:

This field specifies one of 256 possible Walsh Codes used to
channelize the downlink RF bit stream in a TIA/EIA/IS-2000 call. The
high order 3 bits are reserved for future expansion.

13
14

Pilot PN Code:

The Pilot PN Code is one of 511 unique values for the Pilot Channel
offset. The offsets are in increments of 64 PN chips.

15
16
17
18
19
20

Freq. Included:

The Frequency Included field is a flag indicating whether the

frequency assignment is included. A 0 indicates no frequency
assignment is present, a 1 indicates a frequency assignment is
present and is specified in the ARFCN field of this element. For code
channel assignments that are on the same channel frequency, this
field shall be set to 0.

21
22
23

ARFCN:

This field (Absolute RF Channel Number) identifies the Absolute

Radio Frequency Channel Number relative to the band class for the
call association.

691

TIA/EIA/IS-2001

6.2.2.35

2
3
4

Response Request
The presence of this element indicates that a response is required by the sender. The
element has a fixed length of one octet. Each procedure that uses this element shall
specify the appropriate responses.

A1 Element Identifier

Octet
1

5
6

6.2.2.36

7
8

IS-95 MS Measured Channel Identity

This element indicates the band class and frequency that has been measured by the MS
in preparation for a hard handoff.

Octet

A1 Element Identifier

Length

Band Class

(MSB)
ARFCN

3
(LSB)

9
10

Length:

This field indicates the number of octets in this element following the
Length field.

11
12
13
14
15

Band Class:

The BS shall copy the band class from the Candidate Frequency
Search Report message received from the MS into this field when this
element is included in the Handoff Required message. The MSC shall
copy this value to the corresponding field in this same element in the
Handoff Request message.

16
17
18
19

ARFCN:

(Actual Radio Frequency Channel Number) The BS shall set this

field to the CDMA channel number in the specified CDMA band
class corresponding to the CDMA frequency assignment for the
candidate frequency.

20

692

TIA/EIA/IS-2001

6.2.2.37

Calling Party ASCII Number

This element identifies the origin of a call. It is coded as shown below.

7

ext = 0/1
ext = 1

Octet

A1 Element Identifier

Length

Type of Number
Presentation
Indicator

Numbering Plan Identification

0

0
Reserved

Screening Indicator

3
3a

Printable ASCII Character 1

Printable ASCII Character 2

...

Printable ASCII character m-2

3
4
5

Note: The characters that are transferred in this element shall be taken from the set of
ASCII characters commonly referred to as printable. Allowable characters are those
specified in section 7.8 of TIA/EIA 664.

The Length in octet 2 indicates the number of octets following the Length field.

See section 6.2.1.5 for the coding of extension bits (bit 7 in octets 3 and 3a).

The Type of Number field in octet 3 is coded as follows:

Table 6 - 44 - Calling Party ASCII Number - Type of Number Values

Binary Values

Meaning

000

Unknown a

001

International number b, d

010

National number b

011

Network specific number c

100

Dedicated PAD access, short code

101

Reserved

110

Reserved

111

Reserved for extension

10
11
12
13
14

a.

The Type of Number unknown is used when the user of the

network has no knowledge of the Type of Number, e.g.,
international number, national number, etc. In this case, the number
digits/end marks field is organized according to the network dialing
plan (e.g., prefix or escape digits might be present).

15

b.

Prefix or escape digits shall not be included.

693

TIA/EIA/IS-2001

1
2
3

c.

The Type of Number network specific number is used to indicate

administration/service number specific to the serving network (e.g.,
used to access an operator).

4
5

d.

The international format shall also be accepted by the MSC when

the call is destined to the same country as the MSC.

The Numbering Plan Identification field is coded as follows:

Table 6 - 45 - Calling Party ASCII Number - Numbering Plan Identification Values

Binary Values
0000

unknown a

0001

ISDN/telephony number plan (ITU recommendation E.164/E.163)

0011

data number plan (ITU recommendation X.121)

0100

telex numbering plan (ITU recommendation F.69)

1000

national numbering plan

1001

private numbering plan

0111

reserved for extension

All other values

8
9
10
11

Meaning

a.

Reserved.

The numbering plan unknown is used when the user or network

has no knowledge of the numbering plan. In this case, the number
digits/end marks field is organized according to the network dialing
plan (e.g., prefix or escape digits might be present).

12
13

The coding of the Presentation Indicator field is shown below (extension bit in octet 3 is
set to 0).

14

Table 6 - 46 - Calling Party ASCII Number - Presentation Indicator

Binary Values

15
16
17
18
19
20

Meaning

00

Presentation allowed

01

Presentation restricted

10

Number not available due to interworking

11

Reserved

Note: In the mobile originating case, the Presentation Indicator value is used for
indicating the intention of the calling mobile station for the presentation of the calling
party number to the called user. This may also be requested on a subscription basis. If
octet 3a is omitted (extension bit set to 1 in octet 3), and the network does not support
subscription information for the calling party number information restrictions, the value
00 - Presentation allowed is assumed.

694

TIA/EIA/IS-2001

1
2

The coding of Screening Indicator field is shown below (extension bit in octet 3 set to
0).

Table 6 - 47 - Calling Party ASCII Number - Screening Indicator

Binary Values

Meaning

00

User-provided, not screened

01

User-provided, verified and paused

10

User-provided, verified and failed

11

Network provided

Note: If octet 3a is omitted, 00 - User provided, not screened is assumed.

695

TIA/EIA/IS-2001

6.2.2.38

2
3
4

Layer 3 Information
This element is included in the Complete Layer 3 Information message. It contains either
Location Updating Request message, CM Service Request message or Paging
Response message.

Octet

A1 Element Identifier

Length

Layer 3 Information

3-n

The Length field indicates the number of octets following the Length field.

6
7
8
9

The coding of the Layer 3 Information in octets 3 through n follows the DTAP message
encoding rules, and accordingly the Protocol Discriminator, Reserved Octet and
Message Type elements in octets 3, 4, and 5, respectively do not include an Element
Identifier.

696

TIA/EIA/IS-2001

6.2.2.39

Protocol Discriminator

This element distinguishes the messages belonging to the following procedures:

1.

Call Processing and Call Related Supplementary Services

2.

Mobility Management

3.

Radio Resource Management

4.

Facilities Management

5.

Other Signaling Procedures

8
9

The message category of each DTAP message may be determined from Table 6 - 13 DTAP Messages

10

, DTAP Messages.
7

Reserved

Protocol Discriminator

11

The coding of the Protocol Discriminator field is shown below.

12

Table 6 - 48 - Protocol Discriminator

Octet
1

Description

Call Processing and call related Supplementary Services

Mobility Management

Radio Resource Management

Facility Management

Other Signaling Procedures

reserved for test procedures

All other values Reserved

13
14

6.2.2.40

Reserved-Octet

15
16

This element, used in DTAP messages, does not have an element identifier. It uses a
single octet and is always coded as zero.
7

Octet

17

697

TIA/EIA/IS-2001

6.2.2.41

Location Updating Type

2
3

This element indicates whether a normal or a periodic location updating is required. This
is a type 1 information element.
7
1

IEI

reserved

reserved

Location Updating
Type

Octet
1

4
5

The Location Updating Type is a two bit field and it is coded as shown below. TIA/EIAIS-2000

Table 6 - 49 - Location Updating Type

Location Updating Type
(bits 1 and 0)

Use

00

Normal Location Updating

01

Periodic Updating

10

Reserved

11

Reserved

698

TIA/EIA/IS-2001

6.2.2.42

Authentication Confirmation Parameter (RANDC)

2
3

This element contains the Authentication Confirmation Parameter (RANDC) received

from the MS. The RANDC is included for the use of the network.
7

Octet

A1 Element Identifier

RANDC

699

TIA/EIA/IS-2001

6.2.2.43

Location Area Identification

2
3

The Location Area Identification provides a unique identification for each specified
area.
7

A1 Element Identifier

(MSB)

Octet
1

MCC digit 2

MCC digit 1

MNC digit 3

MCC digit 3

MNC digit 2

MNC digit 1

LAC

5
(LSB)

4
5
6
7
8

The MCC in octets 2 and 3 is coded as in CCITT Rec. E212, Annex A. The value of the
MNC is the operators responsibility and BCD coding shall be used. If the operator
decides to use only one digit for MNC, then bits 4 through 7 of octet 4 and bits 4
through 7 of octet 3 are coded as 1111. If the operator decides to use only two digit
for MNC, then bits 4 through 7 of octet 3 are coded as 1111.

9
10

The Location Area Code (LAC) field is 16 bits. The most significant bit is bit 7 of octet
5 of this element.

11
12
13
14

MCC is the mobile country code. MNC is the mobile network code. If MNC is unused,
all bits in the MNC digit 1 and MNC digit 2 fields will be set to 0 and all bits in the
MNC digit 3 field will be set to 1. The LAC field may be used to indicate a paging area.
If the LAC field is unused, all bits in the LAC field will be set to 0.

15
16
17
18
19

Location Area Code (LAC) is an operator defined identifier for a set of cells. LAC is not
defined by CDG IOS for features. However, this field is currently used by at least one
supplier to identify cells. In this IOS document the LAC field is supported; however, it
may be ignored or filled with zeros at the suppliers option, and must not cause a
protocol error.

700

TIA/EIA/IS-2001

6.2.2.44

Reject Cause

This element indicates the reason for rejecting an MS request by the network.
7

Octet

A1 Element Identifier

Reject Cause Value

The Reject Cause value in octet 2 is coded as follows:

Table 6 - 50 - Reject Cause Value

Bit Positions

Hex

Value

01

Reserved

02

MIN/IMSI unknown in HLR

03

Illegal MS

04

TMSI/IMSI/MIN unknown in VLR

05

Reserved

0B

Roaming not allowed

0C

Location area not allowed

20

Service option not supported

21

Requested service option not subscribed

22

Service option temporarily out of order

26

Call cannot be identified

51

Network failure

56

Congestion

62

Message type non-existent or not implemented

63

Information element
implemented

64

Invalid information element contents

65

Message not compatible with the call state

66

Protocol error, unspecified

6E

Invalid message, unspecified

6F

Mandatory information element error

All other values

Reject Cause

Reserved.

701

non-existent

or

not

TIA/EIA/IS-2001

6.2.2.45

Authentication Challenge Parameter (RAND/RANDU/RANDBS/RANDSSD)

2
3
4

The Authentication Challenge Parameter information element provides a nonpredictable number which is used for authentication/SSD update. Bit 7 of octet 2 is the
most significant bit, while bit 0 of the highest numbered octet is the least significant bit.
7

Octet

A1 Element Identifier

Length

Reserved

Random Number Type

(MSB)

4
RAND/RANDU/RANDBS/RANDSSD Value

5-m
(LSB)

5
6

Length:

The Length field is a binary value indicating the

number of octets following the Length field.

Random Number Type:

Table 6 - 51 - Authentication Challenge Parameter - Random Number Type

Random Number
Type Value

Random Number
Type

Random Number
Length

0001

RAND

32 bits

0010

RANDU

24 bits

0100

RANDSSD

56 bits

1000

RANDBS

32 bits

All other values are reserved.

9

702

m+1

TIA/EIA/IS-2001

6.2.2.46

Authentication Response Parameter (AUTHR/AUTHU/AUTHBS)

2
3

This element provides the authentication response signature calculated by the MS or

the network as appropriate.

4
5

In TIA/EIA-IS-2000 systems the authentication response may be the AUTHR, AUTHU,

or AUTHBS.

6
7
8

AUTHU and AUTHR are used in messages which are transmitted from the MS/BS to
the HLR/AC. AUTHBS is used in messages which are transmitted from the HLR/AC to
the MS/BS.
7

Octet

A1 Element Identifier

Length

Reserved
0

Auth Signature Type

0

(MSB)

Auth Signature

5
(LSB)

9
10

Length:

The Length field is a binary value indicating the

number of octets following the Length field.

11
12

Auth Signature Type:

This field identifies the type of authentication signature

included in this element and shall be set as follows:

13

Table 6 - 52 - Authentication Response Parameter - Auth Signature Type

Auth Signature Type Value

Auth Signature Type

0001

AUTHR

0010

AUTHU

0100

AUTHBS
All other values are reserved.

14
15
16
17
18
19
20

Auth Signature:

This field occupies the lower 18 bits in octets four through

six. The higher order bits in octet four are set to 0. Bit
seven of octet four is the most significant bit, while bit zero
of octet six is the least significant bit. This field contains the
authentication signature (AUTHR/AUTHU/AUTHBS).

703

TIA/EIA/IS-2001

6.2.2.47

Authentication Parameter COUNT

This element provides the HLR/AC with the mobile stations call history parameter.
7

A1 Element Identifier
Reserved

Count

704

Octet
1
2

TIA/EIA/IS-2001

6.2.2.48

Message Waiting Indication

This element is used by the MSC to specify the number of messages waiting.
7

Octet

A1 Element Identifier

Number of Messages

705

TIA/EIA/IS-2001

6.2.2.49

Progress Indicator

2
3
4
5
6

The Progress Indicator information element describes an event which has occurred
during the life of a call. The Progress Description field setting specified in this element
is to be retained until overridden by the next setting specified in a subsequent message.
Prior to receipt of a Progress Description setting by the MSC, the BS assumes that call
progress information will be provided in-band by the MSC/network.
7

ext=1

Coding Standard

A1 Element Identifier

Length

Reserved

ext=1

Location

Progress Description

7
8

Table 6 - 53 - Progress Indicator - Coding Standard

Binary Values

Octet

Meaning

00

Standardized coding as described in CCITT Recommendation Q. 931

01

Reserved for other international standards

10

National standard

11

Reserved for other international standards

706

3
4

TIA/EIA/IS-2001

1
2

Table 6 - 54 - Progress Indicator - Location

Binary Values

Meaning

0000

User

0001

Private network serving the local user

0010

Public network serving the local user

0100

Public network serving the remote user

0101

Private network serving the remote user

1010

Network beyond interworking point

All other values Reserved

3
4

Note: Depending on the location of the users, the local public network and remote
public network may be the same network.

Table 6 - 55 - Progress Indicator - Progress Description

Binary Values

Meaning

000 0001

Call is not end-to-end PLMN/ISDN and further call progress

information may be available in-band.

000 0010

Destination address in non-PLMN/ISDN

000 0011

Origination address in non-PLMN/ISDN

000 0100

Call has returned to the PLMN/ISDN

000 1000

In-band information or appropriate pattern now available

000 1010

Delay encountered at the terminating switch

All other values Reserved

6
7

Note: Progress Description value 000 0100 specifies that tones are to be locally
generated at the BS. The other values specify in-band tones generated by the network.

707

TIA/EIA/IS-2001

6.2.2.50

Signal

2
3
4
5
6

This element is used by the MSC to transfer the information required for creating the
tone or the alerting signals to the BS for transmission in appropriate messages to the
MS. This information element may be repeated in a message. It is the responsibility of
the MSC to map any signal values received via ANSI TIA/EIA 41 or other protocol into
the values given below.
7

Signal value

2
Alert Pitch

Meaning

0000 0000

Dial tone on

0000 0001

Ring back tone on

0000 0010

Intercept tone on

0000 0011

Network congestion (reorder) tone on

0000 0100

Busy tone on

0000 0101

Confirm tone on

0000 0110

Answer tone on

0000 0111

Call waiting tone on

0000 1000

Off-hook warning tone on

0011 1111

Tones off

8
9

Table 6 - 57 - Signal Value: TIA/EIA-IS-2000 Alerting

Binary
Values

Octet
1

Table 6 - 56 - Signal Value: Tones

Binary
Values

A1 Element Identifier

Reserved
7

Meaning

0100 0000

Normal Alerting

0100 0001

Inter-group Alerting

0100 0010

Special/Priority Alerting

0100 0011

Reserved (ISDN Alerting pattern 3)

0100 0100

Ping Ring (abbreviated alert)

0100 0101

Reserved (ISDN Alerting pattern 5)

0100 0110

Reserved (ISDN Alerting pattern 6)

0100 0111

Reserved (ISDN Alerting pattern 7)

0110 0011

Abbreviated intercept

0110 0101

Abbreviated reorder

0100 1111

Alerting off

708

TIA/EIA/IS-2001

1
2

3
4

Table 6 - 58 - Signal - Alert Pitch Values

Binary
Values

Meaning

00

Medium pitch (standard alert)

01

High pitch

10

Low pitch

11

Reserved

5
6
7

The table below provides a mapping between signal values in TIA/EIA-41, TIA/EIA-IS2000-B, and this specification.

Table 6 - 59 - Signal - Signal Value Mapping: ANSI-41 and IOS TIA/EIA-IS-2000

Tone & Reference
Reference

TONES (Signal Type = 00)

TIA/EIA-IS-2000-B

TIA/EIA-41.5 Table 125

Table 7.7.5.5.3

Announcement Code

IOS
Table 6-56

Value
SIGNAL_T
YPE

SIGNAL
field

Dial Tone

00

000000

00000000

00000000

Ring Back

00

000001

00000001

00000001

Intercept

00

000010

00000010

00000010

Abbreviated Intercept

00

000011

11000001

01100011

Network Congestion

00

000100

00000011

00000011

Abbreviated Network
Congestion

00

000101

11000010

01100101

Busy

00

000110

00000100

00000100

Confirm

00

000111

00000101

00000101

Answer

00

001000

00000110

00000110

Call Waiting

00

001001

00000111

00000111

Tones Off

00

111111

00111111

00111111

709

TIA/EIA/IS-2001

(continued) - Signal - Signal Value Mapping: TIA/EIA-41 IOS TIA/EIA-IS-2000

Alert Type & Reference
Reference

Alerting (Signal Type = 10)

TIA/EIA-IS-2000-B

TIA/EIA-41.5 Table 123,

Cadence Octet of

Table 7.7.5.5.3

IOS

Alert Code
SIGNAL_T
YPE

SIGNAL
field

No Tone (off)

10

000000

000000

10000000

Long (standard alert)

10

000001

000001

10000001

Short-Short

10

000010

000010

10000010

Short-Short-Long

10

000011

000011

10000011

Short-Short2

10

000100

000100

10000100

Short-Long-Short

10

000101

000101

10000101

Short-Short-Short-Short

10

000110

000110

10000110

PBX Long

10

000111

000111

10000111

PBX Short-Short

10

001000

001000

10001000

PBX Short-Short-Long

10

001001

001001

10001001

PBX Short-Long-Short

10

001010

001010

10001010

PBX Short-Short-ShortShort

10

001011

001011

10001011

710

TIA/EIA/IS-2001

(continued) - Signal - Signal Value Mapping: TIA/EIA-41 IOS TIA/EIA-IS-2000

Alert Type & Reference

Reference

Alerting (Signal Type = 01)

TIA/EAI-95-B

TIA/EIA-41.5 Table 123,

Cadence Octet of

Table 7.7.5.5.3

IOS

Alert Code
SIGNAL_T
YPE

SIGNAL
field

Normal Alerting

01

000000

000001

01000000

Intergroup Alerting

01

000001

NA 1

01000001

Special/Priority Alerting

01

000010

NA

01000010

Rsvd (pattern 3)

01

000011

NA

01000011

Ping-ring

01

000100

NA

01000100

Rsvd (pattern 5)

01

000101

NA

01000101

Rsvd (pattern 6)

01

000110

NA

01000110

Rsvd (pattern 7)

01

000111

NA

01000111

Alerting Off

01

001111

000000

01001111

IS-41C does not support the Alert Codes marked NA.

711

TIA/EIA/IS-2001

6.2.2.51

CM Service Type

This element specifies the type of service requested from the network.

3
4

The CM Service Type information element is coded as shown below. It is a type 1

information element.
7

A1 Element Identifier

Service Type

5
6

Table 6 - 60 - CM Service Types

Binary Values

Meaning

0001

Mobile originating call establishment

0010

Emergency call establishment

0100

Short Message transfer

1000

Supplementary service activation

All other values

Reserved

712

Octet
1

TIA/EIA/IS-2001

6.2.2.52

Called Party BCD Number

2
3

The purpose of the Called Party BCD Number information element is to identify the
called party.

4
5
6

The Called Party BCD Number information element is coded as shown below. It is a type
4 information element with 19 octets length maximal. The maximum number of number
digit(s)/end mark(s) is 32.
7

Octet

A1 Element Identifier

Length

Type of Number

Numbering Plan Identification

Number Digit/End Mark 2

Number Digit/End Mark 1

Number Digit/End Mark 4

Number Digit/End Mark 3

...
Number Digit/End Mark m+1

Number Digit/End Mark m

The Length field in octet 2 indicates the number of octets following the Length field.

8
9

If the Called Party BCD Number information element is included in a Setup message for
emergency call establishment, the Length field may be set to 0.

10
11

If the Called Party BCD Number element contains an odd number of digits/end marks,
bits 4 to 7 of the last octet shall be set to 1111.

713

TIA/EIA/IS-2001

The Type of Number field in octet 3 is coded as follows:

Table 6 - 61 - Called Party BCD Number - Type of Number Values

Binary Values

Meaning

000

Unknown a

001

International number b, d

010

National number b

011

Network specific number c

100

Dedicated PAD access, short code

101

Reserved

110

Reserved

111

Reserved for extension

3
4
5
6
7

a.

The Type of Number unknown is used when the user of the

network has no knowledge of the Type of Number, e.g.,
international number, national number, etc. In this case, the number
digits/end marks field is organized according to the network dialing
plan (e.g., prefix or escape digits might be present).

b.

Prefix or escape digits shall not be included.

9
10
11

c.

The Type of Number network specific number is used to indicate

administration/service number specific to the serving network (e.g.,
used to access an operator).

12
13

d.

The international format shall also be accepted by the MSC when

the call is destined to the same country as the MSC.

14

The Numbering Plan Identification field is coded as follows:

15

Table 6 - 62 - Called Party BCD Number - Numbering Plan Identification Values

Binary Values Meaning
0000

unknown a

0001

ISDN/telephony number plan (ITU recommendation E.164/E.163)

0011

data number plan (ITU recommendation X.121)

0100

telex numbering plan (ITU recommendation F.69)

1000

national numbering plan

1001

private numbering plan

0111

reserved for extension

All other
values
16
17
18
19

a.

Reserved.
The numbering plan unknown is used when the user or network
has no knowledge of the numbering plan. In this case, the number
digits/end marks field is organized according to the network dialing
plan (e.g., prefix or escape digits might be present).

714

TIA/EIA/IS-2001

The Number Digits/End Marks in octets 4 through n are coded as follows:

Table 6 - 63 - Called Party BCD Number - Number Digit Values

Binary Values

Meaning

0000

0001

0010

0011

0100

0101

0110

0111

1000

1001

1010

1011

1100

1101

1110

1111

used as end
mark in case of
odd number
information

715

TIA/EIA/IS-2001

6.2.2.53

Calling Party BCD Number

2
3
4

This element identifies the origin of a call. It is coded as shown below. It is a type 4
information element with 14 octets length maximal. The maximum number of number
digit(s)/end mark(s) is 20.
7

ext=0/1
ext=1

A1 Element Identifier

Length

Type of Number
Presentation
Indicator

Numbering Plan Identification

0

0
Reserved

Screening Indicator

3
3a

Number Digit/End Mark 2

Number Digit/End Mark 1

Number Digit/End Mark 4

Number Digit/End Mark 3

...
Number Digit/End Mark m + 1
5

Octet

Number Digit/End Mark m

The Length in octet 2 indicates the number of octets following the Length field.

716

TIA/EIA/IS-2001

Note 1: The contents of octets 3, 4 through n are coded as described in section 6.2.2.52

2
3

Note 2: If the Calling Party BCD Number contains an odd number of digits/end marks,
bits 4 to 7 of the last octet shall be set to 1111.

The coding of Presentation Indicator is shown below (extension bit in octet 3 set to 0).

Table 6 - 64 - Called Party BCD Number - Presentation Indicator

Binary Values

Meaning

00

Presentation allowed

01

Presentation restricted

10

Number not available due to interworking

11

Reserved

6
7
8
9
10
11

Note: In the mobile origination case, the Presentation Indicator field is used for
indicating the intention of the calling mobile station for the presentation of the calling
party number to the called user. This may also be requested on a subscription basis. If
octet 3a is omitted (extension bit set to 1 in octet 3), and the network does not support
subscription information for the calling party number information restrictions, the
Presentation Indicator value 00 - Presentation allowed is assumed.

12
13

The coding of Screening Indicator field is shown below (extension bit in octet 3 set to
0).

14

Table 6 - 65 - Called Party BCD Number - Screening Indicator

Binary Values

15
16

Meaning

00

User-provided, not screened

01

User-provided, verified and paused

10

User-provided, verified and failed

11

Network provided

Note: If octet 3a is omitted, Screening Indicator value 00 - User provided, not

screened is assumed.

717

TIA/EIA/IS-2001

6.2.2.54

Quality of Service Parameters

2
3

This element identifies the Quality of Service to apply to a given packet data session.
In this version of this standard the only information carried is a 4-bit priority value.
7

Octet

Element Identifier

Length

Reserved
4
5
6
7
8

Packet Priority

Element Identifier:

This information element is used on multiple interfaces. When the

information element is included in a message that is sent on the A1 or
A9 interface, the Element Identifier field is coded as 07H. When the
information element is included in a message sent on the A7 interface,
the Element Identifier field is coded as 0FH.

9
10

Length:

This field indicates the number of octets in this element following the
Length field.

11
12
13

Packet Priority:

This field indicates the priority of a packet data call as a binary value.
Value 0000 is the lowest priority. Value 1111 is the highest priority.
Values 1110 and 1111 are reserved.

14

718

TIA/EIA/IS-2001

6.2.2.55

Cause Layer 3

2
3
4

This element is included to provide the reason for generating certain messages, to
provide diagnostic information in the event of procedural errors and to indicate the
location of the cause originator.

The Cause Layer 3 is a type 4 information element.

7

ext=1

Coding Standard

Octet

A1 Element Identifier

Length

Reserved

ext=1

Location
Cause Value

3
4

6
7

Table 6 - 66 - Cause Layer 3 - Coding Standard

Binary Values

Meaning

00

Standard as described in ITU Recommendation. Q. 931

01

Reserved for other international standards

10

National standard

11

Reserved for other international standards

8
9

Table 6 - 67 - Cause Layer 3 - Location

Binary Values
0000

User

0001

Private network serving the local user

0010

Public network serving the local user

0011

Transit network

0100

Public network serving the remote user

0101

Private network serving the remote user

0111

International network

1010

Network beyond interworking point

All other values

10
11

Meaning

Reserved

The Cause Value field is divided into two subfields: a Class (bits 4 through 6) and a
value within the Class (bits 0 through 3).

719

TIA/EIA/IS-2001

The class indicates the general nature of the event.

Table 6 - 68 - Cause Layer 3 - Cause (Class) Value

Binary Values

Meaning

Class (000)

normal event

Class(001)

normal event

Class (010)

resource unavailable

Class (011)

service or option not available

Class (100)

service or option not implemented

Class (101)

invalid message (e.g., parameter out of range)

Class (110)

protocol error (e.g., unknown message)

Class (111)

interworking

720

TIA/EIA/IS-2001

Table 6 - 69 - Cause Layer 3 Values

Binary Cause
Values

Hex Cause
Values
Cause Diagnostic Remarks
Class (000) and Class (001) - Normal Event

000 0001

01

Unassigned (unallocated) number

000 0011

03

No route to destination

000 0110

06

Channel unacceptable

000 1111

0F

Procedure failed

001 0000

10

Normal Clearing

001 0001

11

User busy

001 0010

12

No user responding

001 0011

13

User alerting, no answer

001 0101

15

Call rejected

001 0110

16

Number changed New destinationa

001 1010

1A

Non selected user clearing

001 1011

1B

Destination out of order

001 1100

1C

Invalid number format (incomplete number)

001 1101

1D

Facility rejected

001 1111

1F

Normal, unspecified
Class (010) - Resource Unavailable

010 0010

22

No circuit/channel available

010 0110

26

Network out of order

010 1001

29

Temporary failure

010 1010

2A

Switching equipment congestion

010 1011

2B

Access information discarded information element ids

010 1100

2C

requested circuit/channel not available

010 1111

2F

Resources unavailable, unspecified

Class (011) - Service or Option Not Available

011 0001

31

Quality of service unavailable

011 0010

32

Requested facility not subscribed

011 0011

33

Request MUX option or rates unavailable

011 1001

39

Bearer capability not authorizedc

011 1010

3A

Bearer capability not presently available c

011 1011

3B

SSD Update Rejected

011 1111

3F

Service or option not available, unspecified

721

TIA/EIA/IS-2001

Table 6 - 70 (cont.) - Cause Layer 3 Values

Binary Cause
Values

Cause
Number

Cause Diagnostic Remarks

Class (100) - Service or Option Not Implemented

100 0001

41

Bearer service not implementedc

100 0101

45

Requested facility not implement

100 0110

46

Only restricted digital information bearer capability is available c

100 1111

4F

Service or option not implemented, unspecified

Class (101) - Invalid Message

101 0001

51

Reserved

101 1000

58

Incompatible destination incompatible parameterb

101 1011

5B

Invalid transit network selection

101 1111

5F

Invalid message, unspecified

Class (110) - Protocol Error

110 0000

60

Mandatory information element error information element identifier(s)

110 0001

61

Message type nonexistent or not implemented message type

110 0010

62

Message not compatible with control state message type or message

type nonexistent or not implemented

110 0100

64

Invalid information element contents Information element Identifier(s)

110 0101

65

Message not compatible with call state message type

110 1111

6F

Protocol error, unspecified

Class (111) - Interworking

111 1111

7F

All other values

Interworking, unspecified
Reserved

2
3

a.

New destination is formatted as the called party number information

element, including information element identifier.

4
5

b.

Incompatible parameter is composed of incompatible information

element identifier.

c.

This value is being kept for backward compatibility to TSB-80.

722

TIA/EIA/IS-2001

6.2.2.56

Forward Burst Radio Info

2
3

This element contains information on the radio resources requested/committed by the

source/target BS for a Forward link traffic burst.
7

Coding Indicator

Octet
1

Length

QOF Mask

Forward Code Channel Index

(high part)

Pilot PN Code (low part)

Reserved

Forward Supplemental Channel Rate

Forward Supplemental Channel Start Time

Start Time Unit

Forward Supplemental Channel Duration

4
5

Length:

This field indicates the number of octets in this

element following the Length field.

6
7
8

Coding Indicator:

This field indicates the type of channel coding to be

applied to the supplemental channel (SCH) during the
duration of the traffic burst.

Forward Code Channel Index (low part)

Reserved
Reserved

A3/A7 Element Identifier

Reserved

Pilot PN
Code (high
part)

7
8

Table 6 - 71 - Forward Burst Radio Info Coding Indicator

Value

Privacy Mask Type

00

Convolutional Coding

01

Turbo Coding

All other values

Reserved

10
11

QOF Mask:

This field contains the QOF (Quasi Orthogonal Function)

mask index, as indexed in TIA/EIA/IS-2000-2.

12
13
14
15

Forward Code Channel Index:

This field specifies one of 256 possible Walsh Codes used to
channelize the downlink RF bit stream in an TIA/EIA/IS-2000
call.

16
17

Pilot PN Code:

The Pilot PN Code is one of 511 unique values for the Pilot
Channel offset. The offsets are in increments of 64 PN chips.

723

TIA/EIA/IS-2001

1
2
3
4
5

Forward Supplemental Channel Rate:

This field indicates the bandwidth on the forward SCH to be
used for the traffic burst. The field shall be coded as in the
Extended Supplemental Channel Assignment Message
(ESCAM) in TIA/EIA/IS-2000-5.

6
7
8
9

Forward Supplemental Channel Start Time:

This field indicates the System Time, in Burst Action Time
Units, specified by the Start Time Unit field (modulo 64), at
which the burst is to start.

10
11
12
13

Start Time Unit:

This field indicates the units of Forward Supplemental

Channel Start Time. This field shall be set to one less than
the number of 20 ms frames that determines the Start Time
Unit.

14
15
16
17
18
19
20
21
22

Forward Supplemental Channel Duration:

This field contains a binary value indicating the duration of a
burst in number of 20 ms frames. This field shall be set to
0000 to indicate that the burst in effect at the time this
message is received is to stop at the Burst Action Time. The
field shall be coded to 1111 to indicate a burst of infinite
duration starting at Burst Action Time. Other values for this
field will be set according to Table 3.7.3.3.2.37-3 of
TIA/EIA/IS-2000-5.

724

TIA/EIA/IS-2001

6.2.2.57

Reverse Burst Radio Info

2
3

This element contains information on the radio resources requested/committed by the

source/target BS for a Reverse link traffic burst.
7

Coding Indicator

Octet

A3/A7 Element Identifier

Length

Reserved

Reserved
Rev Walsh
ID

Reverse Supplemental Channel Rate

Reverse Supplemental Channel Start Time

Start Time Unit

Reverse Supplemental Channel Duration

4
5

4
5

Length:

This field indicates the number of octets in this element

following the Length field.

6
7
8

Coding Indicator:

This field indicates the type of channel coding to be applied

to the supplemental channel (SCH) during the duration of
the traffic burst.

Table 6 - 72 - Reverse Burst Radio Info Coding Indicator

Value

Privacy Mask Type

00

Convolutional Coding

01

Turbo Coding

All other values

Reserved

10
11
12
13
14

Reverse Supplemental Channel Rate:

This field indicates the bandwidth on the Reverse SCH to be
used for the traffic burst. The field shall be coded as in the
Extended Supplemental Channel Assignment Message
(ESCAM) in TIA/EIA/IS-2000-5.

15
16
17
18

Reverse Supplemental Channel Start Time:

This field indicates the System Time, in Burst Action Time
Units, specified by the Start Time Unit field (modulo 64), at
which the burst is to start.

19
20
21
22
23

Rev Walsh ID:

This field shall be coded as in the Extended Supplemental

Channel Assignment Message (ESCAM) in TIA/EIA/IS2000-5, to indicate the Walsh cover ID that the mobile
station is to use when transmitting on the Reverse
Supplemental Channel

725

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13

Start Time Unit:

This field indicates the units of Reverse Supplemental

Channel Start Time. This field shall be set to one less than
the number of 20 ms frames that determines the Start Time
Unit.

Reverse Supplemental Channel Duration:

This field contains a binary value indicating the duration of a
burst in number of 20 ms frames. This field shall be set to
0000 to indicate that the burst is to stop at the Burst Action
Time. The field shall be coded to 1111 to indicate a burst of
infinite duration starting at Burst Action Time. Other values
for this field will be set according to Table 3.7.3.3.2.37-3 of
TIA/EIA/IS-2000-5.

14

726

TIA/EIA/IS-2001

6.2.2.58

Transcoder Mode

This element specifies the settings of the transcoder in the BS, for one party of the call.
7

Octet

A1 Element Identifier

Length = [01H]

Reserved
3
4
5
6

TFO
Mode

Bit 0 of octet 3 specifies whether the transcoder should disable the inband signaling
mechanism and employ the speech coding algorithm appropriate to the channel type
(e.g., QCELP for IS-95) or enable the inband signaling mechanism and attempt tandem
free operation. Thebit is set to 0 for tandem mode, 1 for TFO.
6.2.2.59

UNUSED SECTION

727

TIA/EIA/IS-2001

6.2.2.60

Power Down Indicator

2
3

The presence of this type 2 element in a message indicates to the MSC that the MS has
powered down at the end of a call.
7

A1 Element Identifier

728

Octet
1

TIA/EIA/IS-2001

6.2.2.61

Registration Type

2
3
4
5
6

This information element indicates the type of registration requested by an MS. A

mobile station registering on an access channel may initiate any of the following six
types of registration, when enabled. This element shall not be included if the BS cannot
determine the registration type, and shall always be present in the case of power down
registration.
7

Octet

A1 Element Identifier

Location Registration Type

The Location Registration Type field in octet 2 is coded as follows:

Table 6 - 73 - Location Registration Type

Binary Values

Meaning

0000 0000

Timer-based

0000 0001

Power-up

0000 0010

Zone-based

0000 0011

Power-down

0000 0100

Parameter-change

0000 0101

Ordered

0000 0110

Distance-based

All other values

Reserved

729

TIA/EIA/IS-2001

Timer Based Registration

2
3
4

Timer based registration is performed when a timer expires in the mobile station. This
causes the mobile station to register at regular intervals, allowing deregistration of
inactive mobiles by the network.

Power Up Registration

6
7

Power up registration is performed when power is applied to the mobile station. This is
used to notify the network that the mobile unit is now active.

Zone Based Registration

9
10
11
12
13
14

A mobile service area may be partitioned into smaller regions, called Zones, which is a
group of one or more cells. The mobile station identifies the current zone via parameters
on the forward control channel, which are specific to the air interface type. When the
mobile station enters a zone in which it is not registered, it may initiate zone based
registration. Zone based registration allows the network to limit paging to only the
zone(s) in which the mobile station is registered.

15

Power Down Registration

16
17
18
19
20

Power down registration may be performed when the mobile station is switched off.
Power down registration may occur as an independent procedure on the control
channel, or an indication of the power down may accompany a release operation on the
traffic channel for a call in progress. This latter form of power down registration is
described in section 4.1.2.3.

21

Parameter Change Registration

22
23

Parameter change registration may be performed when specific operating parameters in

the mobile station are modified.

24

Distance Based Registration

25
26
27

When the distance (computed via control channel parameters) between the current cell
and the cell where the mobile last registered is exceeded by a threshold, distance based
registration may be performed by the mobile station.

730

TIA/EIA/IS-2001

6.2.2.62

Tag

2
3
4
5
6
7
8
9
10
11

This element provides a reference for correlating a response to the original request. If
the sender desires a response, then this element is included in the request message. If
this element is received, the response message shall contain this element set to the
received Tag value. Use of this element allows multiple instances of a request to be
outstanding simultaneously. When the Tag element is used by the MSC on a message
that causes interaction with the MS on a traffic channel, the MSC shall be prepared to
handle call clearing. If call clearing occurs, the MSC must be aware that the MS may not
have received the information contained in that message. Unless the call is cleared, the
BS shall respond with the appropriate response message when the Tag element is
included in the request message.
7

12
13

Octet

A1 Element Identifier

Tag Value

2-5

The Tag Value is a 32 bit fixed length field (octets 2 through 5). The value of this field is
a manufacturers concern.

731

TIA/EIA/IS-2001

6.2.2.63

Hard Handoff Parameters

2
3

This element is used to deliver information needed by the source BS to perform hard
handoff.
7

A1 Element Identifier
Reserved

1
Band Class

Number of Preamble Frames

Reset L2

Reserved

Nom_
Pwr_Ext

Reserved

Reset
FPC

Encryption Mode

2
Private
LCM

Nom_ Pwr

FPC Subchannel Information

Reserved

Octet

Power Control Step

3
4

FPC
SubChan
Info
Included

Power
Control
Step
Included

4
5

The Band Class field corresponds to the CDMA frequency assignment for the CDMA
channel. The coding of this field is specified in TSB58.

6
7
8

The Number of Preamble Frames is the number of traffic channel preamble frames that
the mobile has to send when performing a Hard Handoff. All values 000 through 111
are valid.

9
10

The Private LCM is the Private Long Code Mask Indicator used to change the long
code mask after a Hard Handoff is performed. The coding of this field is as follows:

11

0 Do not use Private Long Code Mask

12

1 Use Private Long Code Mask

13
14
15

The Encryption Mode indicates whether encryption will be used for the messages on
the CDMA forward and reverse traffic channels. The encoding of this field is as follows:
00 Encryption disabled

16
17
18
19
20
21

01 Encryption enabled
The Reset FPC (Reset Forward Traffic Power Control) field indicates whether the
forward traffic channel counters are to be maintained or initialized after a Hard Handoff
is performed. The coding of this field is as follows:
0 Do not reset counters
1 Reset counters

732

TIA/EIA/IS-2001

1
2
3
4

The Reset L2 (Reset Layer 2 Acknowledgment) field indicates whether the layer 2
acknowledgment sequence number is to be maintained or initialized after a Hard
Handoff is performed. The coding of this field is as follows:
0 Do not reset Layer 2 Acknowledgment

1 Reset Layer 2 Acknowledgment

The Nom_Pwr_Ext field is coded per TIA/EIA-IS-2000.

The Nom_Pwr field is coded per TIA/EIA-IS-2000.

8
9
10
11

FPC Subchannel Information contains the forward power control (FPC) subchannel gain
information and is coded per TIA/EIA/IS-2000 section 3.7.3.3.2.36. This field shall only
be valid when the call is operating per TIA/EIA/IS-2000. Otherwise, this field shall be
set to 00000.

12
13

FPC SubChan Info Included indicates whether the FPC Subchannel Information field
contains valid information.

14
15
16

Power Control Step is coded per TIA/EIA/IS-2000 3.7.3.3.2.36. This field shall only be
included when the call is operating per TIA/EIA/IS-2000. Otherwise, this field shall be
set to 000.

17
18

Power Control Step Included indicates whether the Power Control Step field contains
valid information.

19
20

6.2.2.64

UNUSED SECTION

21

733

TIA/EIA/IS-2001

6.2.2.65

Software Version

2
3

This element provides software version information about the sub-system originating
the message. Its definition is a BS and MSC manufacturer concern.
7

Octet

A1 Element Identifier

Length

IOS Major Revision Level (X)

IOS Minor Revision Level (Y)

IOS Point Release Level (Z)

Manufacturer/Carrier Software Information

6-n

4
5
6
7

Each version of the this standard is published with a version number in the
form X.Y.Z. These three values shall be placed in octets 3, 4, and 5
respectively as binary values.

8
9
10
11
12

Each separate software load from a manufacturer shall have some software
load identity. In addition, the carrier may wish to exchange specific
information between entities in their network. This information shall be
placed in octets 6-n in ASCII format as agreed between the carrier and
the manufacturer.

734

TIA/EIA/IS-2001

6.2.2.66

Service Option

2
3

This element indicates the service option requested by the MS, or by the network. It is
coded as follows:
7

Octet

A1 Element Identifier
(MSB)

Service Option

2
(LSB)

4
5

For signaling type TIA/EIA-IS-2000, the Service Option field in octets 2 and 3 is coded
as defined in TSB-58.

The service options supported are given in Table 6 - 74 below.

Table 6 - 74 - Service Option Service Option Values

Service Option
Value (hex)

Description

8000H

(13K speech)

0011H

(13K high rate voice service)

0003H

(EVRC)

801FH

(13K Markov)

0004H

(Asynchronous Data rate set 1)

0005H

(Group 3 Fax rate set 1)

0009H

(13K loopback)

000CH

(Asynchronous Data rate set 2)

000DH

(Group 3 Fax rate set 2)

0006H

(SMS rate set 1)

000EH

(SMS rate set 2)

0012H

(OTAPA Rate Set 1)

0013H

(OTAPA Rate Set 2)

0016H

High Speed Packet Data Service:

Internet or ISO Protocol Stack (RS1 forward, RS1 reverse)
Use of this value is outside the scope of this version of this standard.

0017H

High Speed Packet Data Service:

Internet or ISO Protocol Stack (RS1 forward, RS2 reverse)
Use of this value is outside the scope of this version of this standard.

0018H

High Speed Packet Data Service:

Internet or ISO Protocol Stack (RS2 forward, RS1 reverse)
Use of this value is outside the scope of this version of this standard.

0019H

High Speed Packet Data Service:

Internet or ISO Protocol Stack (RS2 forward, RS2 reverse)
Use of this value is outside the scope of this version of this standard.

735

TIA/EIA/IS-2001

0021H

(High Speed Packet Data, 144 kbps)

1
2

6.2.2.67

ADDS User Part

3
4

This element contains the user information portion of an ADDS message. That is, it
carries the application data message.
7

Octet

A1 Element Identifier

Length

Application Type

Application Data Message

4-n

5
6

The Length field is defined as the number of octets following the Length field and has a
value greater than zero.

The Application Type field is coded as follows:

8
9

For CDMA: the 6-bit Data Burst Type defined in TIA/EIA-IS-2000 is contained in
bits 5 through 0, with bits 6 and 7 set to zero.

10

The Application Data Message field has variable length and is encoded as follows:

11
12

For CDMA SMS Services, the Application Data Message is the CDMA SMS Transport
Layer Message defined in IS-637.

13

For CDMA PLD Services, the Application Data Message is defined in TIA/EIA-801.

14
15
16
17
18
19
20
21
22

For AMPS Extended Protocol Enhanced Services, the Application Data Message field
consists of the IS-91 message fields. If necessary, padding bits with a value of 0 are
added at the end to make an integral number of octets. For the specific instance of the
CLI Order, the Application Data Message is the 4-bit DIGIT fields. No padding bits are
used. For the specific instance of the Short Message, the Application Data Message is
the 6-bit CHAR fields. If necessary, padding bits are added to make an integer number
of octets. For the specific instance of the Voice Mail Message, the Application Data
Message is the 6-bit CHAR fields. If necessary, padding bits are added to make an
integer number of octets.

23
24
25

For Alert with Information SMS Services, the Application Data Message is the
Teleservice Identifier followed by one or more Teleservice Sub-parameters (see 4.3.1.4.2
of IS-637).

26

736

TIA/EIA/IS-2001

6.2.2.68

IS-2000 Service Configuration Record

2
3

This information element contains the service configuration record as defined in

TIA/EIA/IS-2000-5.
7

Element Identifier

Bit-Exact Length Octet Count

Reserved

Bit-Exact Length Fill Bits

(MSB)

3
4

IS-2000 Service Configuration Record Content

Seventh
Fill Bit
if needed
4
5
6
7
8
9

Octet

Sixth Fill
Bit if
needed

Element Identifier:

Fifth Fill
Bit if
needed

Fourth
Fill Bit
if needed

Third Fill
Bit if
needed

...
Second
Fill Bit
if needed

First Fill
Bit if
needed

This information element is used on multiple interfaces.

When the information element is included in a message that
is sent on the A1 interface, the Element Identifier field is
coded as 0EH. When the information element is included in a
message sent on the A7 interface, the Element Identifier field
is coded as 10H.

10
11
12

Bit-Exact Length Octet Count:

This field contains the total number of octets in this element
following the Length field represented as a binary value.

13
14
15
16
17
18

Bit-Exact Length Fill Bits:

This field contains a binary value indicating the number of
fill bits contained in the last octet of this element. If this field
contains a non-zero value, the indicated number of fill bits
are set to 0 and occupy the low order bit positions of the
last octet of this element.

19
20
21
22
23
24
25
26

IS-2000 Service Configuration Record Content:

This field contains a Service Configuration Record coded
according to TIA/EIA/IS-2000-5. The value begins in the
high order bit position of octet 4 of this element and extends
into the last octet of this element. Bit positions in the last
octet that are not used, if any, are considered fill bits, are set
to 0, and occupy the low order bit positions of the last
octet.

27

737

TIA/EIA/IS-2001

6.2.2.69

IS-2000 Non-Negotiable Service Configuration Record

2
3

This information element contains the non-negotiable service configuration record as

defined in TIA/EIA/IS-2000-5.
7

Octet

A1 Element Identifier

Bit-Exact Length Octet Count

Reserved

Bit-Exact Length Fill Bits

(MSB)

3
4

IS-2000 Non-Negotiable Service Configuration Record Content

Seventh
Fill Bit
if needed

Sixth Fill
Bit if
needed

Fifth Fill
Bit if
needed

Fourth
Fill Bit
if needed

Third Fill
Bit if
needed

Second
Fill Bit
if needed

...
First Fill
Bit if
needed

4
5
6

Bit-Exact Length Octet Count:

This field contains the total number of octets in this element
following this field represented as a binary value.

7
8
9
10
11
12

Bit-Exact Length Fill Bits:

This field contains a binary value indicating the number of
fill bits contained in the last octet of this element. If this field
contains a non-zero value, the indicated number of fill bits
are set to 0 and occupy the low order bit positions of the
last octet of this element.

13
14
15
16
17
18
19
20

IS-2000 Non-Negotiable Service Configuration Record Content:

This field contains a Non-Negotiable Service Configuration
Record coded according to TIA/EIA/IS-2000-5. The value
begins in the high order bit position of octet 4 of this
element and extends into the last octet of this element. Bit
positions in the last octet that are not used, if any, are
considered fill bits, are set to 0, and occupy the low order
bit positions of the last octet.

738

TIA/EIA/IS-2001

6.2.2.70

IS-2000 Mobile Capabilities

This element contains information about the IS-2000-specific capabilities of the mobile.

3
7

Reserved

A1 Element Identifier

Length

DCCH
FCH
OTD
Enhanced
QPCH
Supported Supported Supported RC CFG Supported
Supported

FCH Information: Bit-Exact Length Octet Count

Reserved

Octet

Geo Location Type

Geo
Location
Included

FCH Information:
Bit-Exact Length Fill Bits

(MSB)

6
FCH Information Content
Seventh
Fill Bit
if needed

Sixth Fill
Bit if
needed

Fifth Fill
Bit if
needed

Fourth
Fill Bit
if needed

...
Third Fill
Bit if
needed

Second
Fill Bit
if needed

First Fill
Bit if
needed

DCCH Information: Bit-Exact Length Octet Count

Reserved

k+1

DCCH Information:
Bit-Exact Length Fill Bits

(MSB)

k+2
k+3

DCCH Information Content

Seventh
Fill Bit
if needed

Sixth Fill
Bit if
needed

Fifth Fill
Bit if
needed

Fourth
Fill Bit
if needed

...
Third Fill
Bit if
needed

Second
Fill Bit
if needed

First Fill
Bit if
needed

4
5

Length:

This field contains the total number of octets in this element

following the Length field represented as a binary value.

6
7

DCCH Supported:

This field is set to 1 if mobile indicated that it supports the

IS-2000 DCCH, otherwise it is set to 0.

8
9

FCH Supported:

This field is set to 1 if mobile indicated that it supports the

IS-2000 FCH, otherwise it is set to 0.

10
11

OTD Supported:

This field has a value of 1 if the mobile supports

Orthogonal Transmit Diversity and a value of 0 otherwise.

739

TIA/EIA/IS-2001

1
2
3
4
5

Enhanced RC CFG Supported:

This field indicates whether the MS supports any radio
configuration in radio class 2. A value of 1 indicates
support, and a value of 0 indicates no support.

6
7
8

QPCH Supported:

This field indicates whether the MS supports the IS-2000

Quick Paging Channel (QPCH). A value of 1 indicates
support, and a value of 0 indicates no support.

9
10
11
12

FCH Information: Bit-Exact Length Octet Count:

This field contains the total number of octets in the FCH
Information Content field represented as a binary value.

13
14
15
16
17
18
19

FCH Information: Bit-Exact Length Fill Bits

This field contains a binary value indicating the number of
fill bits contained in the last octet of the FCH Information
Content field. If this field contains a non-zero value, the
indicated number of fill bits are set to 0 and occupy the low
order bit positions of the last octet of the FCH Information
Content field.

20
21
22
23

Geo_Location_Included

This field is set to 1 if geo-location capabilities about the

mobile are included. This field is set to 0 if no geo-location
capabilities are included and the MSC shall ignore the
contents of the Geo_Location_Type field.

24
25

Geo_Location_Type

If Geo_Location_Included is set to 1 this field is included

and set as follows:

26
27

000

No mobile assisted geo-location capabilities

28
29

001

IS801
capable
(Advanced
Triangulation only (AFLT))

30
31

010

IS801
capable
(Advanced
Forward
Link
Triangulation and Global Positioning Systems

32

011

Global Positioning Systems Only

Forward

Link

33
34

All Other values reserved.

35
36
37

If Geo_Location_Included is set to 0 this field is included

and set to 000 .

38
39
40
41

FCH Information Content:

42
43
44

DCCH Information: Bit-Exact Length Octet Count:

This field contains the total number of octets in the DCCH
Information Content field represented as a binary value.

The FCH Capabilities Information field is coded per

TIA/EIA/IS-2000-5 section 2.7.4.27.1.

740

TIA/EIA/IS-2001

1
2
3
4
5
6
7

DCCH Information: Bit-Exact Length Fill Bits

This field contains a binary value indicating the number of
fill bits contained in the last octet of the DCCH Information
Content field. If this field contains a non-zero value, the
indicated number of fill bits are set to 0 and occupy the low
order bit positions of the last octet of the DCCH Information
Content field.

8
9
10

DCCH Information Content:

The DCCH Capabilities Information field is coded per
TIA/EIA/IS-2000-5 section 2.7.4.27.2.

741

TIA/EIA/IS-2001

6.2.2.71

Protocol Type

2
3

This information element contains the Link Layer / Network Layer Protocol Type used
by the PDSN.
7

(MSB)

Octet

A1 Element Identifier

Length

Protocol Type

3
(LSB)

4
5

Length

This field contains the number of bytes in this element following this
field as a binary number.

6
7
8
9

Protocol Type

This field indicates the protocol type in use at a PDSN for an existing
packet connection. This field provides the ability for a target BS/PCF
to properly accept a hard handoff of a packet data call. The value is
as defined in section 6.2.2.165.

742

TIA/EIA/IS-2001

6.2.2.72

MS Information Records

2
3
4

This information element contains a list of TIA/EIA-IS-2000 Information Records.

Examples of such information records are: call mode, terminal information, roaming
information, security status, mobile identity, etc.
7

Octet

A1 Element Identifier

Length

Information Record Type - 1

Information Record Length - 1

(MSB)

5
Information Record Content - 1

...
(LSB)

Information Record Type - 2

J+1

Information Record Length - 2

j+2

(MSB)

J+3
Information Record Content - 2

(LSB)

...

Information Record Type - n

Information Record Length - n

m+1

(MSB)

m+2
Information Record Content - n

(LSB)

5
6
7

For coding of the Information Record Type field and Information Record Content field
refer to TIA/EIA-IS-2000. The Information Record Length field indicates the number of
octets in the immediately following Information Record Content field in this element.

8
9

The BS shall transparently transmit the contents from octet 3 to the end of this element
without verifying or modifying them.

10
11

This information element was referred to as IS-95 Information Records in previous

versions of this standard.

743

TIA/EIA/IS-2001

6.2.2.73

Extended Handoff Direction Parameters

2
3
4
5
6

This element is used by a target BS to provide information to the source BS for two
purposes. The first purpose is to create the Extended Handoff Direction Message,
General Handoff Direction Message or Universal Direction Message to be sent to the
MS. The second purpose is to create the TIA/EIA-IS-2000 In-Traffic System Parameters
message.
7

A1 Element Identifier

Length

Search Window A Size (Srch_Win_A)

Search Window N Size (Srch_Win_N)

Search Window R Size (Srch_Win_R)

Add Pilot Threshold (T_Add) high order bits

T_Add low order bits

Drop Pilot Threshold (T_Drop)

Compare Threshold (T_Comp)

Drop Timer Value (T_TDrop)

Neighbor Max Age (Nghbor_Max_AGE)

reserved

Reserved

SOFT_SLOPE

Reserved

ADD_INTERCEPT

Reserved

DROP_INTERCEPT

10

Target BS P_REV
7

Octet

For coding of the parameters listed in this element, refer to TIA/EIA-IS-2000.

744

11

TIA/EIA/IS-2001

6.2.2.74

2
3

Forward Layer 3 IS-2000 FCH/DCCH Data

This element contains the CDMA Forward Fundamental and Dedicated Control Channel
Frame and control information for packets flowing in the SDU to BTS direction.

FPC: SLC

4
5
6
7
8
9
10
11
12
13

Octet

FSN

FPC: GR

RPC: OLT

IS-2000 Frame Content

Forward Link Information

variable

Frame Sequence Number (FSN):

The SDU shall set this field to CDMA System Time in frames, modulo 16
(see 1.2 of TIA/EIA-IS-2000) corresponding to the transmission time of
the frame over the air in the forward direction.
Forward Link Power Control: Sector Link Count (FPC: SLC):
This parameter indicates the number of legs (also known as.
independent power control subchannels) involved in soft handoff.
Multiple sectors in softer handoff with each other are counted as a
single leg. This is useful for forward link gain equalization.
Forward Link Power Control: Gain Ratio (FPC: GR):

14
15
16

This parameter is required for EIB (50Hz) power control. It is also useful
during transitions of: soft handoff states, transmission rates, and FER
target values.

17

The SDU shall set this field to the binary value of

18
19
20
21
22

Min((At / Ap ) 128 , 255 )

where At is the full-rate Forward Link gain, and Ap is the smallest Pilot
Channel gain. The SDU shall set the FPC: GR field in the range of 0
through 255.
Reverse Link Power Control: Outer-loop Threshold (RPC: OLT):

23
24
25

The source BS shall set this field to the desired Reverse Link Eb/Nt,
where Eb/Nt is the ratio of the demodulated 9600 bps information bit
energy to the total received power spectral density on the RF channel.

26
27

The source BS shall set the RPC:OLT field in the range of 0 through 255
corresponding to 0dB to 31.875dB in units of 0.125dB.

28

745

TIA/EIA/IS-2001

1
2

IS-2000 Frame Content

3
4
5
6
7
8

This parameter is an index value from the IS-2000 Frame Contents

information element, with the specific value taken from Table 6 - 72 - IS2000 Frame Content - Supplemental Channel (SCH) Frame Content
Parameters for 40ms Frames, or Table 6 - 73 - IS-2000 Frame Content Supplemental Channel (SCH) Frame Content Parameters for 80ms
Frames*

9
10

The IS-2000 Frame Content parameter uniquely identifies the symbol

repetition rate and number of information bits.

11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

Forward Link Information:

The SDU shall set this field to the Forward Link Information that the
BTS is to send to the MS. The SDU shall include the number of bits in
the Information column of Table 6 - 1, Table 6 - 71 - IS-2000 Frame
Content - Supplemental Channel (SCH) Frame Content Parameters for
20ms Frames, Table 6 - 72 - IS-2000 Frame Content - Supplemental
Channel (SCH) Frame Content Parameters for 40ms Frames, or Table 6 73 - IS-2000 Frame Content - Supplemental Channel (SCH) Frame
Content Parameters for 80ms Frames corresponding to the transmission
rate of the Forward Link frame. The SDU shall set the Information Bits
to the information bits supplied by the Multiplex Option Sublayer. The
bit order shall be as specified in TIA/EIA IS-2000-1.
Layer 3 Fill:
The SDU shall include the number of bits in the Layer 3 Fill column of
Table 6 - 2, Table 6 - 71 - IS-2000 Frame Content - Supplemental
Channel (SCH) Frame Content Parameters for 20ms Frames, Table 6 - 72 IS-2000 Frame Content - Supplemental Channel (SCH) Frame Content
Parameters for 40ms Frames, or Table 6 - 73 - IS-2000 Frame Content Supplemental Channel (SCH) Frame Content Parameters for 80ms
Frames corresponding to the transmission rate of the Traffic Channel
frame. The Layer 3 Fill bits shall be set to 0. The fill bits are added at
the end of the frame in the lower order bit positions after the Forward
Link Information.

746

TIA/EIA/IS-2001

6.2.2.75

Reverse Layer 3 IS-2000 FCH/DCCH Data

2
3

This element contains the CDMA Reverse Fundamental and Dedicated Control Channel
frame and control information for packets flowing in the BTS to SDU direction.
7

Soft Handoff Leg #

FQI

Octet

FSN

Reverse Link Quality

Scaling

Packet Arrival Time Error

IS-2000 Frame Content

FPC: S

4
EIB

Reverse Link Information

5
Variable

4
5
6
7
8

Soft Handoff Leg #:

This field is used to carry the soft handoff leg number as indicated by
the source BS on the A3-Connect Ack message. The target BS shall set
this field to the value contained in the Soft Handoff Leg # field in the A3
Connect Ack Information element of the A3-Connect Ack message.

Frame Sequence Number (FSN):

10
11
12

The BTS shall set this field to CDMA System Time in frames, modulo 16
(see section 1.2 of TIA/EIA-IS-2000) corresponding to the receive time
of the air interface frame in the reverse direction.

13
14
15
16

Frame Quality Indicator (FQI):

If the traffic frame contains Reverse Link Information, then the BTS shall
set the FQI (Frame Quality Indicator) field to 1 if the Reverse Traffic
Frame CRC passes, and 0 if the CRC fails.

17
18
19
20

If there is no reverse traffic frame 2, the BTS shall (using an

implementation specific algorithm) set the FQI field to 1 if it can
determine that a reverse traffic frame CRC would have passed, and 0
otherwise.

21

Reverse Link Quality:

22
23
24
25

If the reverse traffic frame contains Reverse Link Information, then the
BTS shall set the Reverse Link Quality field to the Inverted Re-Encoded
Symbol Error Rate or equivalent metric. The Inverted Re-Encoded SER is
the binary value of:
127 - (Min[Re-Encoded Symbol Error Rate , 255]) / 2

26
27
28
29

where the value of a is used to normalize the number of symbols to the

1x repetition rate as listed in the IS-2000 Frame Content element.
(Reference: IS-2000-2, Table 2.1.3.1.5-1 Code Symbol Repetition)

There is no Reverse Traffic Frame when only a reverse pilot channel exists. For
example, this occurs during call setup before the BTS has acquired the reverse traffic
channel, and it occurs when the DCCH is in DTX mode.

747

TIA/EIA/IS-2001

1
2
3
4
5
6
7

The Inverted Re-Encoded Symbol Error Rate is the number of errors

found when comparing the received symbols at the input of the channel
decoder and the re-encoded symbols at the output of the channel
decoder. The Inverted Re-Encoded Symbol Error Rate computation shall
include the erasure indicator bit (E), if applicable; the information bits;
the frame quality indicator (F), if applicable; and the encoder tail bits (T),
if applicable.

8
9

If there is no reverse traffic frame 3, or if a frame erasure is detected by

the BTS, the Reverse Link Quality field shall be set to 000 0000.

10
11

Scaling:

12
13

The BTS shall set this field to the time scale for the Packet Arrival Time
Error (PATE) field. Values are indicated in the table below.

14
15
16

Table 6 - 75 - Reverse Layer 3 IS-2000 FCH/DCCH Data - Time Scale for the Packet
Arrival Time Error

17

18

Scaling Field Value

Time Units

PATE Range

00

0.125 ms

3.875ms

01

1.0 ms

31.0 ms

10

1.25 ms

38.75 ms

11

5.0 ms

155 ms

Packet Arrival Timer Error (PATE):

19
20
21
22
23
24

The BTS shall set this field to the time difference between the time at
which the A3-Forward Layer 3 Data message arrives at the BTS minus
the expected arrival time in units specified by the Scaling field. This
value is expressed in 2s complement format. It has a value in the range
31 time units, as determined by the Scaling field.
Forward Power Control- Signal to Noise Ratio (FPC: S)

25

The BTS shall set this field to the current S:

26

S= SIR + RSSI in dB

27
28

The SIR shall be calculated by accumulating filtered rake finger energy

values.

29
30
31

The RSSI is the BTS received signal strength indication updated every
frame. The RSSI can be obtained by filtering the baseband front end
signal samples over some time period (e.g., 2 seconds).

There is no Reverse Traffic Frame when only a reverse pilot channel exists. For
example, this occurs during call setup before the BTS has acquired the reverse traffic
channel, and it occurs when the DCCH is in DTX mode.

748

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

Note: Signal to Interference ratio (SIR) can be estimated from the reverse
pilot (TIA/EIA/IS-2000) or winning Walsh symbol energy (TAI/EIA/IS95A,B) and is therefore proportional to Ew/Nt or pilot Ec/Nt
respectively. The result is really signal to noise plus interference ratio
which is called SIR because the noise term is treated as being
insignificant compared to the interference power.
EIB (Erasure Indicator Bit):
When FPC_MODE is not equal to 011, then the BTS shall set this field
to 0. When FPC_MODE is equal to 011, then the BTS shall set this
field to 1 if the EIB received from the MS is 1; otherwise, the BTS
shall set this field to 0'. Furthermore, FPC_MODE equal to 011 implies
that a Reverse Layer 3 DCCH Data frame will be generated at least once
per 20 ms in order to convey EIB status.
IS-2000 Frame Content
This parameter is an index value from the IS-2000 Frame Contents information
element, with the specific value taken from one of the following: Table 6 - 79 IS-2000 Frame Content - Fundamental Channel (FCH) Frame Content
Parameters or Table 6 - 80 - IS-2000 Frame Content - Dedicated Control
Channel (DCCH) Frame Content Parameters. The IS-2000 Frame Content
parameter uniquely identifies the symbol repetition rate and number of
information bits.
Reverse Link Information:
The BTS shall set this field to the Reverse Link Information that the BTS
received from the MS. The BTS shall include the number of bits in the
Information column of Table 6 - 76 - IS-2000 Frame Content Fundamental Channel (FCH) Frame Content Parameters or Table 6 - 82 IS-2000 Frame Content - Dedicated Control Channel (DCCH) Frame
Content Parameters corresponding to the transmission rate of the
Reverse Link frame. The BTS shall set the Information Bits to the
information bits received from the MS which correspond to the
Multiplex Sublayer in use (see TIA/EIA/IS-2000). The BTS shall use the
bit order specified in TIA/EIA/IS-2000.Layer 3 Fill:
The SDU shall
include the number of bits in the Layer 3 Fill column of Table 6 - 77 - IS2000 Frame Content - Fundamental Channel (FCH) Frame Content
Parameters or Table 6 - 78 - IS-2000 Frame Content - Dedicated Control
Channel (DCCH) Frame Content Parameters corresponding to the
transmission rate of the Traffic Channel frame. The Layer 3 Fill bits shall
be set to 0. The fill bits are added at the end of the frame in the lower
order bit positions after the Reverse Link Information.
IS-2000 Frame Content:
The IS-2000 Frame Content field is used to indicate the code symbol repetition
rate and number of information bits contained in the information element.
Special Frame Content parameters are defined to facilitate "in-band" signaling
between the Source BS and Target BS's. These parameters are defined as
follows:

749

TIA/EIA/IS-2001

1
2

Table 6 - 76 - IS-2000 Frame Content - Special Frame Content Parameters

IS-2000
Frame
Content
(hex)

Name

00

Idle 1

7D

Description
Forward

Reverse

May be used for synchronization

when air interface resources are
not allocated. See section 3.4.10.1.

Used for synchronization when

the BTS has not yet acquired the
traffic channel, or when air
interface resources are not
allocated.

Full Rate
Likely

Not Applicable

Radio Configuration 1, Full Rate

Likely

7E

Erasure 1

Not Applicable.

Insufficient Physical Layer Frame

Quality

7F

Null1

Used during DTX mode (when Used during DTX mode (when
transmitting Null traffic frames to there is only a pilot channel and
the MS).
no frames are being received on
Note: This not applicable for the the traffic channel).
IS-2000 FCH.

1.

Note: This not applicable for the

IS-2000 FCH.

The number of Information Bits for these frame content types is 0.

750

TIA/EIA/IS-2001

1
2
3

Table 6 - 77 - IS-2000 Frame Content - Fundamental Channel (FCH) Frame Content

Parameters

4
Frame
Content
(hex)

Radio
Configuration

Data Rate
(bps)

Code Symbol
Repetition ()
For the Reverse
Link

01

Forward: 1

9600

172

02

and

4800

80

03

Reverse: 1

2400

0
0

1200

16

04

Number of
Information
Bits

40

05

Forward: 2

14400

267

06

and

7200

125

07

Reverse: 2

3600

55

1800

21

9600 (5ms)*

24

0A

Forward:
3,4,6,7

9600 (20ms)

172

0B

and

4800

80

0C

Reverse: 3,5

2700

40

1500

16

16

08
09

0D
0E

Number of
Pad Bits

9600

24

0F

Forward:
5,8,9

14400

267

10

and

7200

125

11

Reverse:

3600

55

12

4,6

1800

16

21

*-Note that 5ms frames are not supported in this version of this standard.

751

TIA/EIA/IS-2001

1
2
3

Table 6 - 78 - IS-2000 Frame Content - Dedicated Control Channel (DCCH) Frame

Content Parameters
Frame
Content (hex)

Radio
Configuration

Data Rate
(bps)

Code Symbol
Repetition ()

Number of
Pad Bits

20

Forward:
3,4,6,7

Number of
Information Bits

9600

14400

267

9600 (5ms)*

24

172

Reverse:
3,5
21

Forward:
5,8,9
Reverse:
4,6

22

Forward:
5,8,9
Reverse:
4,6

752

TIA/EIA/IS-2001

1
2
3

Table 6 - 79 - IS-2000 Frame Content - Supplemental Channel (SCH) Frame Content

Parameters for 20ms Frames

(bps)

Code Symbol
Repetition ()

Number of
Pad Bits

Number of
Information Bits

614400*

12264

307200*

6120

153600

3084

Frame
Content (hex)

Radio
Configuration

Data Rate

30

Reverse: 5
Forward: 7

31

Reverse: 3

32
33

Forward:

76800

1512

34

3,4,6

38400

744

35

19200

360

36

9600

172

37

4800

80

38

2700

40

39

1500

16

16

3A

Reverse: 6

1036800*

20712

3B

Forward: 9

460800*

9192

3C

Reverse: 4

230400*

4584

115200

2280

3D

4
5

3E

Forward:

57600

1128

3F

5,8

28800

552

40

14400

267

41

7200

125

42

3600

55

43

1800

16

21

*-Note that data rates above 153600 Kbps and 5ms frames are not supported in this
version of this standard.

753

TIA/EIA/IS-2001

1
2
3

Table 6 - 80 - IS-2000 Frame Content - Supplemental Channel (SCH) Frame Content

Parameters for 40ms Frames*
Frame
Content

Radio
Configuration

Data Rate
(bps)

Code Symbol
Repetition ()

Number of
Pad Bits

Number of Info.
Bits

50

Reverse: 5
Forward: 7

307200

12264

51

Reverse: 3

153600

6120

76800

3048

52
53

Forward:

38400

1512

54

3,4,6

19200

744

55

9600

360

56

4800

172

57

2400

80

58

1350

40

59

Reverse: 6

518400

20712

5A

Forward: 9

230400

9192

5B

Reverse: 4

115200

4584

57600

2280

5C

5D

Forward:

28800

1128

5E

5,8

14400

552

5F

7200

267

60

3600

125

61

1800

55

*- Note that 40ms Frames are not supported in this version of this standard.

754

TIA/EIA/IS-2001

1
2
3

Table 6 - 81 - IS-2000 Frame Content - Supplemental Channel (SCH) Frame Content

Parameters for 80ms Frames*
Frame
Content

Radio
Configuration

Data Rate
(bps)

Code Symbol
Repetition ()

Number of
Pad Bits

Number of Info.
Bits

62

Reverse: 5
Forward: 7

153600

12264

63

Reverse: 3

7680
0

6120

38400

3048

19200

1512

9600

744

67

4800

360

68

2400

172

69

1200

80

64
65
66

Forward:
3,4,6

6A

Reverse: 6

259200

20712

6B

Forward: 9

115200

9192

6C

Reverse: 4

57600

4584

28800

2280

6D
6E

Forward:

14400

1128

6F

5,8

7200

552

70

3600

267

71

1800

125

4
5

*- Note that 80ms frames are not supported in this version of this standard.
6.2.2.76

UNUSED SECTION

755

TIA/EIA/IS-2001

6.2.2.77

2
3
4
5
6
7
8
9
10
11

Forward Layer 3 IS-2000 SCH Data

This element contains the CDMA Forward Supplemental Link Frame and control
information for packets flowing in the source BS (SDU) to target BS (BTS) direction.
The frame content parameter is optionally set to Null for soft handoff legs incurring the
greatest transmission loss. This can be determined by the reverse link signal to noise
ratio (S). The signal to noise ratio can be obtained from the Reverse Layer 3 FCH/DCCH
Data element Signal to Noise Ratio parameter. A threshold, driven by the Service Option
and/or QoS, can be used for transmission selection. Depending on the threshold, either
the best forward link or a best subset of the forward links is selected for transmission on
the A3 interface, and subsequently on the air interface. Note that appropriate actiontime coordinated signaling with the mobile station is required to exercise this option.

FPC: SLC

12
13
14
15
16
17
18
19
20
21

Octet

FSN

FPC: GR

IS-2000 Frame Content

Forward Link Information

variable

Forward Link Power Control: Sector Link Count (FPC: SLC):

This parameter indicates the number of legs (also known as
independent power control subchannels) involved in soft handoff.
Multiple sectors in softer handoff with each other are counted as a
single leg. This is useful for forward link gain equalization.
Frame Sequence Number (FSN):
The SDU shall set this field to CDMA System Time in frames, modulo 16
(see 1.2 of TIA/EIA-IS-2000) corresponding to the transmission time of
the frame over the air in the forward direction.
Forward Link Power Control: Gain Ratio (FPC: GR):

22
23
24

This parameter is required for EIB (50Hz) power control. It is also useful
during transitions of: soft handoff states, transmission rates, and FER
target values.

25

The SDU shall set this field to the binary value of

26

Min([(A d /A p )*SQRT( 9600 /Rate )] 128 , 255 )

27
28

where Ad is the Forward Link SCH gain, and Ap is the smallest common
Pilot Channel gain. (IS-2000 supports multiple pilots.)

29

Note: The BTS determines the Forward Link SCH gain as follows:

30
31
32
33
34
35
36
37

Ad = FPC:GR*Ap*SQRT(Rate/9600)/128
IS-2000 Frame Content
This parameter is an index value from the IS-2000 Frame Contents
information element, with the specific value taken from Table 6 - 82 - IS2000 Frame Content - Supplemental Channel (SCH) Frame Content
Parameters for 20ms Frames. The IS-2000 Frame Content parameter
uniquely identifies the
symbol repetition rate and number of
information bits.

756

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Forward Link Information:

The SDU shall set this field to the Forward Link Information that the
BTS is to send to the MS. The SDU shall include the number of bits in
the Information column of Table 6 - 83 - IS-2000 Frame Content Supplemental Channel (SCH) Frame Content Parameters for 20ms
Frames corresponding to the transmission rate of the Forward Link
frame. The SDU shall set the Information Bits to the information bits
supplied by the Multiplex Option Sublayer. The bit order shall be as
specified in TIA/EIA IS-2000-1.
Layer 3 Fill:
The SDU shall include the number of bits in the Layer 3 Fill column of
Table 6 - 84 - IS-2000 Frame Content - Supplemental Channel (SCH)
Frame Content Parameters for 20ms Frames corresponding to the
transmission rate of the Traffic Channel frame. The Layer 3 Fill bits shall
be set to 0. The fill bits are added at the end of the frame in the lower
order bit positions after the Forward Link Information.

757

TIA/EIA/IS-2001

1
2

6.2.2.78

Reverse Layer 3 IS-2000 SCH Data

3
4

This element contains the CDMA Reverse Supplemental Link frame and control
information for packets flowing in the BTS to SDU direction.
7

Soft Handoff Leg #

1
2
3

IS-2000 Frame Content

Reverse Link Information

variable

Soft Handoff Leg #:

This field is used to carry the soft handoff leg number as indicated by
the source BS on the A3-Connect Ack message. The target BS shall set
this field to the value contained in the Soft Handoff Leg # field in the A3
Connect Ack Information element of the A3-Connect Ack message.
Frame Sequence Number (FSN):
The BTS shall set this field to CDMA System Time in frames, modulo 64
(see section 1.2 of TIA/EIA-IS-2000) corresponding to the receive time
of the air interface frame in the reverse direction.
Frame Quality Indicator (FQI):

15
16
17
18
19

Octet

Packet Arrival Time Error

11
12
13
14

Reverse Link Quality

Scaling

10

1
FSN

FQI

5
6
7
8
9

If the traffic frame contains Reverse Link Information, then the BTS shall
set the FQI (Frame Quality Indicator) field to 1 if the Reverse Traffic
Frame CRC passes. Otherwise, the BTS shall set this field to 0 if the
CRC fails or if there is no Reverse Link Information4.
Reverse Link Quality:

20
21
22
23

If the reverse traffic frame contains Reverse Link Information, then the
BTS shall set this field to the Inverted Re-Encoded Symbol Error Rate
(SER) or equivalent metric. The Inverted Re-Encoded SER is the binary
value of:

24

127 - (Min[Re-Encoded Symbol Error Rate , 255]) / 2

25
26
27
28

where the value of is used to normalize the number of symbols to the

1x repetition rate as listed in the IS-2000 Frame Content information
element in Table 6 - 85 - IS-2000 Frame Content - Supplemental Channel
(SCH) Frame Content Parameters for 20ms Frames.

There is no Reverse Link Information when only a reverse pilot channel exists. For
example, this occurs during call setup before the BTS has acquired the reverse traffic
channel, and it occurs when the SCH is in DTX mode.

758

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8

The Inverted Re-Encoded Symbol Error Rate is the number of errors

found when comparing the received symbols at the input of the channel
decoder and the re-encoded symbols at the output of the channel
decoder. The Inverted Re-Encoded Symbol Error Rate computation shall
include the erasure indicator bit (E), if applicable; the information bits;
the frame quality indicator (F), if applicable; and the encoder tail bits (T),
if applicable.

9
10

If there is no reverse traffic frame 5, or if a frame erasure is detected by

the BTS, the Reverse Link Quality field shall be set to 000 0000

11

Scaling:

12
13
14
15
16

The BTS shall set this field to the time scale for the Packet Arrival Time
Error (PATE) field. Values are indicated in the table below.

Table 6 - 82 - Reverse Layer 3 IS-2000 SCH Data - Time Scale for the Packet Arrival
Time Error
Field Value

Time Units

PATE Range

00

0.125 ms

3.875ms

01

1.0 ms

31.0 ms

10

1.25 ms

38.75 ms

11

5.0 ms

155 ms

17
18

Packet Arrival Timer Error (PATE):

19
20
21
22
23
24

The BTS shall set this field to the time difference between the time at
which the A3-Forward Layer 3 Data message arrives at the BTS minus
the expected arrival time in units specified by the Scaling field. This
value is expressed in 2s complement format. It has a value in the range
31 time units, as determined by the Scaling field.
IS-2000 Frame Content

25
26
27
28

This parameter is an index value from the IS-2000 Frame Contents

information element, with the specific value taken from Table 6 - 83 - IS2000 Frame Content - Supplemental Channel (SCH) Frame Content
Parameters for 20ms Frames

29
30

The Frame Content parameter uniquely identifies the symbol repetition

rate and number of information bits.

There is no Reverse Traffic Frame when only a reverse pilot channel exists. For
example, this occurs when the SCH is in DTX mode.

759

TIA/EIA/IS-2001

1
2

Reverse Link Information:

3
4
5
6
7
8
9
10
11

The BTS shall set this field to the Reverse Link Information that the BTS
received from the MS. The BTS shall include the number of bits in the
Information column Table 6 - 84 - IS-2000 Frame Content - Supplemental
Channel (SCH) Frame Content Parameters for 20ms Frames
corresponding to the transmission rate of the Reverse Link frame. The
BTS shall set the Information Bits to the information bits received from
the MS which correspond to the Multiplex Sublayer in use (see
TIA/EIA/IS-2000). The BTS shall use the bit order specified in
TIA/EIA/IS-2000.

12
13
14
15
16
17
18

Layer 3 Fill:
The SDU shall include the number of bits in the Layer
3 Fill column of Table 6 - 85 - IS-2000 Frame Content - Supplemental
Channel (SCH) Frame Content Parameters for 20ms Frames
corresponding to the transmission rate of the Traffic Channel frame.
The Layer 3 Fill bits shall be set to 0. The fill bits are added at the end
of the frame in the lower order bit positions after the Reverse Link
Information.

760

TIA/EIA/IS-2001

6.2.2.79

CDMA Serving One Way Delay

2
3

This element specifies the estimated one-way delay from the MS to the cell associated
with the REF_PN (see TIA/EIA-IS-2000). It is coded as follows:
7

(MSB)

Octet

A1 Element Identifier

Length

Cell Identifier

3-var

CDMA Serving One Way Delay

CDMA Serving One Way Delay
Reserved

m
(LSB)
Resolution

m+1
m+2

4
5
6

The Length field contains the number of octets in this element following the Length
field.

7
8
9
10

The Cell Identifier field identifies the reference cell. This field is comprised of a Cell
Identification Discriminator and a Cell Identification and shall be formatted according to
octets 3 through the end of the Cell Identifier element defined in section 6.2.2.20. The
allowable cell discriminator values are 0000 0010, and 0000 0111.

11
12

The CDMA Serving One Way Delay field is the one-way delay from the MS to the cell
associated with the REF_PN (see TIA/EIA-IS-2000) as estimated by the BS.

13
14

The Resolution field indicates the units used to calculate the CDMA Serving One way
Delay. The allowable values are:

15

00 100 nsec

16

01 50 nsec

17

10 1/16 TIA/EIA-95 PN Chip

18

11 - reserved

19
20

6.2.2.80

UNUSED SECTION

6.2.2.81

UNUSED SECTION

21
22

761

TIA/EIA/IS-2001

1
2

6.2.2.82

Radio Environment and Resources

3
4
5
6

This element indicates the environment and availability of resources for a new call
establishment. Four inter-related factors are included: availability of radio resources,
pre-allocation of radio resources by the BS, and an evaluation of the forward and
reverse radio environments by the BS (interference, power level, etc.)

7
8

The BS evaluation of the radio environment is manufacturer-specific, but can be

generalized to: acceptable / marginally acceptable / poor.
7

A1 Element Identifier
Reserved

Include
Priority

Forward

Reverse

Octet
1

Alloc

Avail

9
10
11
12
13
14

The Include Priority field indicate whether the actual priority of the call is required. This
bit is set to 1 to request the MSC to include the actual priority in the Assignment
Request message. Otherwise, it is set to 0 . This field is not used in IOS v4.0.0 and
shall be set to 0. The setting {Alloc=0, Avail=1} is used when the BS does not do early
traffic channel assignment and it either has resources or does not know whether it has
resources.

15
16
17

Note - The BS should include this field to indicate to the MSC that no lower priority
channels are available when PACA service is requested and a channel reservation
method is used to support the call.

18
19

The coding of the Forward, Reverse, Alloc and Avail fields is given in Table 6 - 93 Radio Environment and Resources

20

The Alloc field indicates that radio resources have been allocated for the call

21

The Avail field indicates that resources are available and can be allocated for this call.

762

TIA/EIA/IS-2001

1
2

Table 6 - 83 - Radio Environment and Resources

FIELD VALUES

DESCRIPTION

Forward
00

Not reported.

01

Forward radio environment is acceptable.

10

Forward radio environment is marginally acceptable.

11

Forward radio environment is poor.

Reverse
00

Not reported.

01

Reverse radio environment is acceptable.

10

Reverse radio environment is marginally acceptable.

11

Reverse radio environment is poor.

Resources are not allocated.

Alloc
a

Resources are allocated.

0a

Resources are not available.

Resources are available.

Avail

3
4

a.

It is an illegal (and illogical) combination to have the Alloc field set to 1

and the Avail field set to 0.

763

TIA/EIA/IS-2001

1
2

6.2.2.83

Neighbor List

3
4

This element contains a list of the target BS neighbor cells. This list may be used by the
source BS to update the MS neighbor list.
7

Octet
1

Length

Number of Neighbors

3
(LSB)

Short Cell Identification Discriminator 1 = [07H]

Cell Identification 1

variable

...

PILOT_PN n
PILOT_PN
n
(MSB)

A1 Element Identifier

PILOT_PN 1

PILOT_PN
1
(MSB)

(LSB)

Short Cell Identification Discriminator n = [07H]

Cell Identification n

k
k+1

variable

5
6
7

The Length field is a binary value indicating the number of octets following the Length
field.

8
9

The Number of Neighbors field contains the number of neighboring cells included in
this element.

10

There is one instance of the next three fields for each cell in the neighbor list.

11
12

The PILOT PN Code is one of the 511 unique values for the pilot PN sequence offset
index. The offsets are in increments of 64 PN chips.

13
14
15

The Short Cell Identification Discriminator field is identical to Cell Identification

Discriminator field specified in section 6.2.2.20 except that only the least significant
seven bits of the eight bits of the Cell Identification Discriminator value are used.

16
17

The Cell Identification field is identical to Cell Identification field specified in section
6.2.2.20.

18

6.2.2.84

UNUSED SECTION

6.2.2.86

UNUSED SECTION

19
20
21

764

TIA/EIA/IS-2001

6.2.2.87

UNUSED SECTION

6.2.2.88

UNUSED SECTION

6.2.2.89

Cell Information Record

2
3
4
5
6
7

The Cell Information Record contains the TIA/EIA-IS-2000 air interface channel
information for the cells attached to a call leg.
7

Reserved

Octet

A3/A7 Element Identifier

Length

Cell Identification Discriminator 1

Cell Identification 1

variable

QOF_Mask 1

New Cell
Indicator

PWR_
Comb_Ind

Pilot_PN 1

Reserved

j
(MSB)
(LSB)

j+1

Code_Chan 1

j+2

...

Cell Identification Discriminator n

Cell Identification n

variable

QOF_Mask n

New Cell
Indicator

PWR_
Comb_Ind

Pilot_PN n

l
(MSB)
(LSB)

Code_Chan n
8
9

Length

The Length field contains the number of octets in this element

following the Length field.

10
11
12
13

Cell Identification Discriminator

This field uses the Cell Identification Discriminator values used
with the Cell Identifier element (see section 6.2.2.20) to describe
the format of the immediately following Cell Identification.

14
15
16
17

Cell Identification

This field contains the Cell Identification of a cell associated

with this A3 connection. It shall be formatted according to
octets 4 through the end of the Cell Identifier element defined
in section 6.2.2.20.

18

Reserved

This field is spare and shall be set to 000

19
20
21

QOF_Mask

This field contains QOF(Quasi Orthogonal Function) mask

index. This QoF mask index coincides with the QoF mask index
of air interface air message

22
23

The BTS shall set this field to the QOF mask in the range 00
to 11 inclusive that is used with the code channel index.

765

l+1
l+2

TIA/EIA/IS-2001

1
2
3
4
5
6
7

New Cell Indicator:

This field indicates whether the corresponding cell is being

newly added to an A3 traffic connection by the current
procedure or was already existing on this A3 traffic
connection.
0 = an existing cell
1 = a newly added cell

PWR_Comb_Ind

Power Control symbol combining indicator.

9
10
11
12
13
14
15
16

If the Forward Traffic Channel associated with this pilot will

carry the same closed loop power control subchannel bits as
that of the previous pilot in this message, the BTS shall set this
field to 1. Otherwise, the BTS shall set this field to 0. For
the first occurrence of this record in the element, the BTS shall
set this field to 0.
Pilot_PN

17
18
19
20
21
22
23
24
25

This field contains the pilot PN sequence offset index for the
associated cell.
The BTS shall set this field to the pilot PN sequence offset for
this pilot in units of 64 PN chips.

Code_Chan

This field contains the code channel index for the associated
cell.
The BTS shall set this field to the code channel index (see
TIA/EIA-IS-2000) in the range 00H to FFH inclusive that is to
be used on the Forward Traffic Channel associated with this
pilot.

766

TIA/EIA/IS-2001

1
2

6.2.2.90

A3 Signaling Address

3
4
5
6
7

This information element identifies the network node that contains the instance of the
SDU in use for the call. The target BS is responsible for checking whether a connection
with the same destination address exists. If such a connection does exist, that existing
connection shall be used to carry A3 signaling messages sent and received by the
target BS.
7

(MSB)

A1 Element Identifier

Length

Address Type

TCP Port

4
(LSB)

(MSB)

5
6

A3 Address

(LSB)

8
9

Octet

variable

Length:

The Length field contains the number of octets in this

element following the Length field.

10
11

Address Type:

This field indicates the type and format of the A3 Address

that follows.

12
13

TCP Port:

This field contains the TCP Port address for the A3 signaling
connection.

14
15
16

A3 Address:

This field has a variable length that is dependent on the

Type field. The internal format of this field may be specified
via the Type field.

17

Table 6 - 84 - A3 Address Identifier Type

Type

Format of the A3 Address

Length of A3 Address

Internet Protocol IPv4

4 octets

Internet Protocol IPv6

variable

All other values

Reserved

18

767

TIA/EIA/IS-2001

1
2

6.2.2.91

SDU ID

This information element identifies a particular SDU instance within an SDU Node.
7

Octet

A1 Element Identifier

Length

(MSB)

3
SDU Identifier

(LSB)

variable

4
5

Length:

The Length field contains the number of octets in this

element following the Length field.

6
7
8
9

SDU Identifier:

This field has a variable length. The actual length is

indicated in the Length field and is dependent upon the
particular implementation. In this version of this standard,
this value shall be no more than 6 octets long.

10

6.2.2.92

UNUSED SECTION

6.2.2.93

UNUSED SECTION

6.2.2.94

UNUSED SECTION

6.2.2.95

UNUSED SECTION

11
12
13
14
15
16

768

TIA/EIA/IS-2001

1
2

6.2.2.96

A3 Traffic Circuit ID

3
4
5
6

This information element is used to identify a particular circuit (virtual/physical)

between a BTS and a source BS/SDU. It is useful particularly when multiple circuits
supporting A3 user traffic connections may exist between the BTS and the source
BS/SDU, e.g., multiple ATM virtual circuits running the AAL2 protocol.
7

A3/A7 Element Identifier

Length

Length of Traffic Circuit Identifier

(MSB)

4
Traffic Circuit Identifier

(LSB)

Length of Traffic Connection Identifier

n
n+1

(MSB)

n+2
Traffic Connection Identifier

(LSB)

7
8

Octet

Length:

This field indicates the number of octets in this element

following the Length field.

9
10
11

Length of Traffic Circuit Identifier:

This field indicates the length in octets of the Traffic Circuit
Identifier.

12
13

The Traffic Circuit Identifier field shall be exactly two octets

in length.

14
15
16
17
18

Traffic Circuit Identifier:

The value contained within this field is configured for a

particular circuit (virtual/physical) by agreements between
the network operator and the manufacturers involved. This
field is regarded as the VCCI (Virtual Channel Connection
Identifier).

19
20
21

Length of Traffic Connection Identifier:

This field indicates the length in octets of the Traffic
Connection Identifier.

22
23
24
25
26
27

Traffic Connection Identifier:

This field contains a value that is unique within the traffic
circuit and identifies a single logical connection within that
traffic circuit. This field is regarded as the CID of an AAL2
virtual circuit. If this field is omitted, all circuits within the
specified VCCI are indicated.

769

TIA/EIA/IS-2001

1
2

6.2.2.97

A7 Control

3
4

This information element is used to control various aspects of the A7 connection

between two BSs.
7

7
8
9
10
11
12

Octet

A3/A7 Element Identifier

Length

Reserved

5
6

Send
Source
Transfer
Report

Length:

The Length field contains the number of octets in this

element following the Length field.

Send Source Transfer Report:

This field is used by a target BS to indicate that it requires

the source BS to send an A7 Source Transfer Performed
message in the event that a source transfer procedure is
executed. This field is always coded as 1. A value of 1
indicates that A7-Source Transfer Performed message shall
be sent.

770

TIA/EIA/IS-2001

1
2

6.2.2.98

Call Connection Reference

This information element contains a globally unique identification for a call connection.
7

Octet

A1 Element Identifier

Length

(MSB)

Market ID
Market ID (continued)

(MSB)

3
(LSB)

Generating Entity ID
Generating Entity ID (continued)

4
5

(LSB)

(MSB)

6
7

Call Connection Reference Value

8
9
(LSB)

10

4
5

Length:

The Length field contains the number of octets in this

element following the Length field.

6
7

Market ID:

This field represents a unique market ID that is specified by

the service provider (see TIA/EIA/TSB29).

8
9
10

Generating Entity ID:

This two octet field represents a unique code assigned by

the operator to the entity that generates this Call Connection
Reference value.

11
12
13

Call Connection Reference Value:

This four octet field may contain any value. It is assigned

by the generating entity whose responsibility it is to
guarantee its uniqueness.

771

TIA/EIA/IS-2001

1
2

6.2.2.99

PMC Cause

3
4

This element is used to indicate the outcome of processing an A3 or A7 interface

message.
7

Octet

A3/A7 Element Identifier

Length

PMC Cause Value

772

TIA/EIA/IS-2001

The PMC Cause Value field is coded as follows:

Table 6 - 85 - PMC Cause Values

PMC Cause Value
(Hex)

Description

00H

No Error

01H

Awaiting Connect

02H

Already connected

03H

Illegal A3 Connect

04H

Illegal A3 Remove

05H

Requested Reverse Pilot Gating Rate not supported

06H

DTMF continuous tone generation not active

07H

Unrecognized message

08H

Reserved (available value)

09H

Invalid State

0AH

No Resources Available

0BH

Reserved (available value)

0CH

Illegal Operation

0DH

Private long code not available or not supported

0EH

Requested MUX option or rates not available

0FH

Requested privacy configuration unavailable

All Other Values

Reserved

3
4

6.2.2.100

UNUSED SECTION

773

TIA/EIA/IS-2001

1
2
3

6.2.2.102

UNUSED SECTION

6.2.2.103

UNUSED SECTION

6.2.2.104

UNUSED SECTION

6.2.2.105

Called Party ASCII Number

4
5
6
7
8
9
10
11

This element contains the called party number in ASCII format. It is coded as shown
below.
7

ext = 1

Octet

A1 Element Identifier

Length

Type of Number

Numbering Plan Identification

ASCII character 1

ASCII character 2

...

ASCII character n

12
13

The Length field contains the number of octets in this element following the Length
field.

14
15

For the coding of the Type of Number and Numbering Plan Identification fields refer to
section 6.2.2.52.

774

TIA/EIA/IS-2001

1
2

6.2.2.106

Band Class

This information element specifies the frequency band.

7

Octet

A1 Element Identifier

Length

Reserved

Band Class

4
5

The Length field contains the number of octets in this element following the Length
field.

The coding of the Band Class field is specified in Table 6 - 86 - Band Class

7
8

below. This table contains band class values defined in TSB58. If there are any
discrepancies between this table and TSB58, the latter shall be considered correct.

Table 6 - 86 - Band Class

Binary Values

Meaning

0 0000

800 MHz Cellular System

0 0001

1.850 to 1.990 GHz Broadband PCS

0 0010

872 to 960 MHz TACS band

0 0011

832 to 925 MHz JTACS band

0 0100

1.750 to 1.870 GHz Korean PCS band

All other values

Reserved

10
11

6.2.2.107

UNUSED SECTION

775

TIA/EIA/IS-2001

1
2

6.2.2.108

Correlation ID

This information element is used to correlate request and response messages.

7

Octet

A3/A7 Element Identifier

Length

(MSB)

3
Correlation Value

...
(LSB)

4
5

Length:

The Length field contains the number of octets in this

element following the Length field.

6
7
8
9

Correlation Value:

This field contains a value that allows the network entity to

correlate a request-response pair of messages. The value is
a manufacturer concern. In this revision of this standard,
this value shall be exactly 4 octets in length

10

6.2.2.109

Service Configuration Record

11
12

This information element identifies common attributes used by the MS and the BS to
build and interpret traffic channel frames.
7

Octet

A1 Element Identifier

Length

Service Configuration Record

variable

13
14

The Length field contains the number of octets in this element following the Length
field.

15
16

The encoding of the Service Configuration Record field is the same as that of the
Service Configuration Record in TIA/EIA-IS-2000.

776

TIA/EIA/IS-2001

1
2

6.2.2.110

IS-2000 Cause Value

3
4

This information element contains the cause indication sent by an TIA/EIA-IS-2000

mobile station.
7

A1 Element Identifier

Length

IS-95 Cause Information

variable

5
6

The Length field contains the number of octets in this element

following the Length field.

7
8
9

The content, values and format of the IS-95 Cause Information field
are as specified for the ORDQ field of the Reject Order in TIA/EIAIS-2000.

10
11

This information element is referred to as IS-95 Cause Value in

previous versions of this standard.

12
13

6.2.2.111

UNUSED SECTION

6.2.2.112

UNUSED SECTION

6.2.2.113

UNUSED SECTION

14
15
16
17

Octet

777

TIA/EIA/IS-2001

1
2

6.2.2.114

3
4

Authentication Event
This information element is included by the BS to provide information to the MSC only
when an unexpected authentication event occurs.

5
6

Length:

A1 Element Identifier

Length

Event

This field indicates the number of octets in this element

following this Length field.

The coding of Event is as follows

8
9
10

01H

The BS is operating in authentication required mode, but

authentication parameters (AUTHR, RANDC and COUNT)
were NOT received from the MS.

11
12
13

02H

The BS is operating in authentication required mode, but the

MS provided RANDC did not match the BS provided
RAND(s).

14

All other values reserved.

15

6.2.2.115

UNUSED SECTION

6.2.2.116

UNUSED SECTION

6.2.2.117

UNUSED SECTION

6.2.2.118

UNUSED SECTION

16
17
18
19
20
21

Octet

778

TIA/EIA/IS-2001

1
2

6.2.2.119

3
4

One way Propagation Delay Record

This element contains the CDMA serving one-way propagation delay and the Cell
Identification.

(MSB)

Octet

A3/A7 Element Identifier

Length

Cell Identification Discriminator

Cell Identification
Cell Identification

(MSB)

4
(LSB)

CDMA Serving One way Delay

CDMA Serving One way Delay

m
m+1

(LSB)

5
6
7

Length:

This field indicates the number of octets in this element following the
Length field.

8
9
10
11
12

Cell Identification Discriminator:

This field uses the Cell Identification Discriminator values used with
the Cell Identifier element (see section 6.2.2.20) to describe the format
of the immediately following Cell_ID. Cell discriminator types 0000
0010 and 0000 0111 are used.

13
14
15
16

Cell Identification:

17
18

CDMA Serving One way Delay:

This is the CDMA serving one-way delay in units of 100 ns.

This is the cell identification as described in section 6.2.2.20 for which

the propagation delay measurement is included in this record. It shall
be formatted according to octets 4 through the end of the Cell
Identifier element defined in section 6.2.2.20.

779

TIA/EIA/IS-2001

1
2

6.2.2.120

3
4

Forward Layer 3 Data

This element contains the CDMA Forward Traffic Channel Frame and control
information for packets flowing in the SDU to BTS direction.

Reserved

Octet

Sequence Number

Forward Traffic Channel Gain

Reverse Traffic Channel

Ew NT

Rate Set Indicator

Forward Traffic Channel Rate

Reserved

Power Control Subchannel Count

Forward Traffic Channel Information +Layer 3 Fill

5

Reserved:

variable

The SDU shall set this field to 0000.

6
7
8
9
10

Sequence Number:
The SDU shall set this field to CDMA System Time in frames,
modulo 16 (see 1.2 of TIA/EIA-IS-2000) corresponding to the
transmission time of the frame over the air in the forward
direction.

11

Forward Traffic Channel Gain:

12

The SDU shall set this field to the binary value of

13

Min((A t / A p ) 128, 255)

14
15

where A t is the full-rate Forward Traffic Channel gain, and Ap is the

Pilot Channel gain.

16

Reverse Traffic Channel

Ew NT

17
18
19
20

The SDU shall set this field to the desired Reverse Traffic Channel
Ew/Nt , where Ew/Nt is the ratio of the total demodulated Walsh
symbol energy to total received power spectral density on the RF
channel. The Ew/Nt is thus a composite value.

21
22
23

The SDU shall set the Reverse Traffic Channel Ew/Nt field in the
range of 0 through 255 in units of 0.125dB. This provides a Reverse
Traffic Channel Ew/Nt in the range of 0 through 31.875 dB.

780

TIA/EIA/IS-2001

1
2

Rate Set Indicator:

3
4
5

The SDU shall set this field to correspond to the Rate Set of the traffic
channel frame as follows.
Table 6 - 87 - Forward Layer 3 Data - Rate Set Indicator
Field Value

Meaning

0000

Rate Set 1

0001

Rate Set 2
All other values are reserved

Forward Traffic Channel Rate:

7
8

The SDU shall set the field to the rate at which the BTS is to send the
Forward Traffic Channel Information to the MS.

9
10
11
12

13

The SDU shall set this field as follows:

14

If this field indicates Idle Frame, then the BTS shall not
transmit an air interface frame, but shall ignore all but the
Sequence Number and Frame Type fields and shall use this frame
to adjust the frame arrival time.

Table 6 - 88 - Forward Layer 3 Data - Forward Traffic Channel Rate

Field Value

Rate Set 1 Transmission

Rate

Rate Set 2 Transmission Rate

0000

9600 bps (Full Rate)

14400 bps (Full Rate)

0001

4800 bps (Half Rate)

7200 bps (Half Rate)

0010

2400 bps (Quarter Rate)

3600 bps (Quarter Rate)

0011

1200 bps (Eighth Rate)

1800 bps (Eighth Rate)

0100

Idle Frame

Idle Frame

All other values are reserved.

15

Reserved: This field shall be set to 0000.

16

Power Control Subchannel Count:

17
18
19
20
21
22
23
24
25
26
27

The SDU shall set this field to the number of independent

power control subchannels involved in soft handoff.
Forward Traffic Channel Information:
The SDU shall set this field to the Forward Traffic Channel
Information that the BTS is to send to the MS. The SDU shall
include the number of bits in the Information column
corresponding to the transmission rate of the Forward Traffic
Channel frame. The SDU shall set the Information Bits to the
information bits supplied by the Multiplex Option Sublayer in
use (see TIA/EIA-IS-2000). The bit order shall be as specified
in TIA/EIA-IS-2000.

781

TIA/EIA/IS-2001

1
2

Table 6 - 89 - Forward Layer 3 Data - Forward Traffic Channel Information

Rate
Set

Transmission
Rate (bps)

Number of Information Bits per

Frame

9600

172

4800

80

2400

40

1200

16

14400

267

7200

125

3600

55

1800

21

3
4

Layer 3 Fill:

5
6
7
8
9
10

The SDU shall include the number of bits in the Layer 3 Fill
column corresponding to the transmission rate of the Traffic
Channel frame. The SDU shall set the Layer 3 Fill bits to 0.
The fill bits are added at the end of the frame in the lower order
bit positions per the bit ordering specified in this standard.
Table 6 - 90 - Forward Layer 3 Data - Layer 3 Fill
Class

Transmission
Rate (bps)

Number of Layer 3 Fill Bits

per Frame

Rate Set 1

9600

4800

2400

1200

14400

7200

3600

1800

Rate Set 2

11

782

TIA/EIA/IS-2001

6.2.2.121

Reverse Layer 3 Data

2
3

This element contains the CDMA Reverse Traffic Channel frame and control
information for packets flowing in the BTS to SDU direction.
7

Octet

Sequence Number

Soft Handoff Leg #

Reverse Traffic Channel Quality
Scaling

Packet Arrival Time Error

Rate Set Indicator

Reverse Traffic Channel Rate

Reserved

4
EIB

Reverse Traffic Channel Information + Layer 3 Fill

5
variable

4
5
6
7
8

Soft Handoff Leg #:

This field is used to carry the soft handoff leg number as

indicated by the source BS on the A3-Connect Ack message.
The target BS shall set this field to the value contained in the
Soft Handoff Leg # field in the A3-Connect Ack Information
element of the A3-Connect Ack message.

9
10
11
12

Sequence Number:

The BTS shall set this field to CDMA System Time in frames,
modulo 16 (see section 1.2 of TIA/EIA-IS-2000) corresponding
to the receive time of the air interface frame in the reverse
direction.

13

Reverse Traffic Channel Quality:

14
15

The Reverse Traffic Channel Quality shall consist of a one bit CRC
field and a seven bit Symbol Error Rate field.

16
17
18
19

If the Reverse Traffic Frame CRC passes, the BTS shall set the most
significant bit to 1. Otherwise, the BTS shall set this bit to 0. If the
Reverse Traffic Channel frame does not have a CRC, the BTS shall set
this bit to 0.

20
21
22

The BTS shall set the 7 least significant bits of this parameter to the
inverted Re-Encoded Symbol Error Rate or equivalent metric,. The
inverted Re-Encoded Symbol Error Rate is the binary value of

23
24
25

127 - (Min[Re-Encoded Symbol Error Rate , 255]) / 2

where the value of is determined according to the Reverse Traffic
Channel Rate as shown in the following table.

26
27
28
29
30

If the most recently received forward frame received by the BTS from
the SDU was an Idle Frame, then the BTS shall set the Reverse Traffic
Channel Quality field to a value of 00H and shall send an Idle Frame
to the SDU. The SDU shall ignore the value of this field in Idle
Frames.

783

TIA/EIA/IS-2001

Table 6 - 91 - Reverse Layer 3 Data - Value of

Value ()

Rate Set 1 Transmission Rate

Rate Set 2 Transmission Rate

9600 bps (Full Rate)

14400 bps (Full Rate)

4800 bps (Half Rate)

7200 bps (Half Rate)

2400 bps (Quarter Rate)

3600 bps (Quarter Rate)

1200 bps (Eighth Rate)

1800 bps (Eighth Rate)

Idle Frame

Idle Frame

2
3
4
5

The Re-Encoded Symbol Error Rate is the number of errors found

when comparing the received symbols at the input of the
convolutional code decoder and the re-encoded symbols at the
output of the convolutional code decoder.

6
7
8

The Re-encoded Symbol Error Rate computation shall include the

erasure indicator bit (E), if applicable; the information bits; the Frame
Quality Indicator (F), if applicable; and the Encoder Tail Bits (T).

9
10
11
12

13

Scaling:

The BTS shall set this field to the time scale for the Packet
Arrival Time Error (PATE) field. Values are indicated in the
table below.

Table 6 - 92 - Reverse Layer 3 Data - Time Scale for the Packet Arrival Time Error
Field Value

Time Units

PATE Range

00

125 s

3.875 ms

01

1.0 ms

31.0 ms

10

1.25 ms

38.75 ms

Packet Arrival Timer Error (PATE):

14
15
16
17
18
19
20
21
22

The BTS shall set this field to the time difference between the time at
which the A3-IS-95 Forward message arrives at the BTS minus the
expected arrival time in units specified by the Scaling field. This value
is expressed in 2s complement format. It has a value in the range 31
time units, as determined by the Scaling field.
Rate Set Indicator:

The BTS shall set this field to correspond to the Rate Set of the traffic
channel frame as follows. If the BTS is sending an Idle Frame to the
SDU, the SDU shall ignore the contents of this field.

Table 6 - 93 - Reverse Layer 3 Data - Rate Set Indicator

Field Value

Meaning

0000

Rate Set 1

0001

Rate Set 2
All other values are reserved

23

784

TIA/EIA/IS-2001

1
2
3
4

Reverse Traffic Channel Rate:

The BTS shall set the field values as shown in the following table. The BTS
shall set the field value to 0101, idle, if it has not acquired the MS.
Table 6 - 94 - Reverse Layer 3 Data - Reverse Traffic Channel Rate
Field Value

Rate Set 1 Transmission

Rate

Rate Set 2 Transmission Rate

0000

9600 bps (Full Rate)

14400 bps (Full Rate)

0001

4800 bps (Half Rate)

7200 bps (Half Rate)

0010

2400 bps (Quarter Rate)

3600 bps (Quarter Rate)

0011

1200 bps (Eighth Rate)

1800 bps (Eighth Rate)

0100

Erasure

Erasure

0101

Idle

Idle

0110

Rate Set 1 Full Rate Likely

Reserved

All other values are reserved

5

Reverse Traffic Channel Information:

6
7
8
9
10
11
12
13
14

The BTS shall set this field to the Reverse Traffic Channel
Information that the BTS received from the MS. The BTS shall
include the number of bits in the Information column
corresponding to the transmission rate of the Reverse Traffic
Channel frame. The BTS shall set the Information Bits to the
information bits received from the MS which correspond to the
Multiplex Sublayer in use (see TIA/EIA-IS-2000). The BTS
shall use the bit order specified in TIA/EIA-IS-2000.
Table 6 - 95 - Reverse Layer 3 Data - Reverse Traffic Channel Information Bits
Class

Transmission
Rate (bps)

Number of Information Bits per

Frame

Rate Set 1

9600

172

4800

80

2400

40

1200

16

14400

267

7200

125

3600

55

1800

21

Erasure

Idle

Rate Set 2

Other

15

785

TIA/EIA/IS-2001

EIB (Erasure Indicator Bit):

2
3
4
5

When Rate Set 1 is being used, the BTS shall set this bit to 0.
When Rate Set 2 is being used, the BTS shall set this bit to 1
if the EIB received from the MS is a 1; otherwise, the BTS
shall set this bit to 0.

Reserved:

The BTS shall set this field to 0000000.

7
8
9
10
11

Layer 3 Fill:

The BTS shall include the number of bits in the Layer 3 Fill column
corresponding to the transmission rate of the Reverse Traffic Channel
frame. The BTS shall set the Layer 3 Fill bits to 0. The fill bits are
added at the end of the frame in the lower order bit positions per the
bit ordering specified in this standard.

12

Table 6 - 96 - Reverse Layer 3 Data - Layer 3 Fill Bits

Class

Transmission
Rate (bps)

Number of Layer 3 Fill Bits per

Frame

Rate Set 1

9600

4800

2400

1200

14400

7200

3600

1800

Erasure

Idle

Rate Set 2

Other

13
14

6.2.2.122

UNUSED SECTION

6.2.2.123

UNUSED SECTION

6.2.2.124

UNUSED SECTION

15
16
17
18
19

786

TIA/EIA/IS-2001

6.2.2.125

BSC ID

This element specifies the identifier of a particular BSC.

7

Octet

A3/A7 Element Identifier

Length

Type

(MSB)

4
BSC Identifier

(LSB)

variable

Length:

4
5

This field indicates the number of octets in this element following the Length
field.

Type:

This field indicates the type and format of the BSC Identifier that follows.

Table 6 - 97 - BSC Identifier Format

Type

Format of the BSC Identifier

Length of BSC Identifier

No format is specified.

Variable

Internet Protocol IPv4

4 octets

Internet Protocol IPv6

variable

All other values are reserved.

9
10

BSC Identifier:

11
12

This field has a variable length that is dependent on the Type field. The internal format
of this field may be specified via the Type field. See Table 6 - 97 - BSC Identifier Format

13

above.

14
15

6.2.2.126

UNUSED SECTION

6.2.2.127

UNUSED SECTION

16
17
18

787

TIA/EIA/IS-2001

6.2.2.128

2
3

CDMA Long Code Transition Info

This element provides the encryption mask type (public or private long code mask) to
be used by the BTS as well as the explicit time of transition to the new long code mask.

Octet

A3/A7 Element Identifier

LENGTH

2
LCM_TYPE

Reserved
ACTION_TIME

3
4

4
5

LENGTH

This field shall be set to the length of this element in octets following
the LENGTH field.

Reserved:

All reserved bits shall be set to 0.

LCM_TYPE

Long code mask type.

Use Public long code mask.

Use Private long code mask.

10
11
12
13
14
15
16
17

ACTION_TIME

The field shall be set by the BSC to the CDMA System Time (see
TIA/EIA-IS-2000), in units of 80 ms (modulo 64) at which the
transition to the new long code mask is to take effect. This field shall
have the same setting as was conveyed to the MS in a Long Code
Transition Request Order on the Forward Traffic Channel (see
TIA/EIA-IS-2000). The Action Time value conveyed to the mobile
station is derived by taking the least significant 6 bits of this 8-bit
field.

18
19

6.2.2.129

UNUSED SECTION

6.2.2.130

UNUSED SECTION

6.2.2.131

UNUSED SECTION

20
21
22
23
24

788

TIA/EIA/IS-2001

6.2.2.132

2
3

Channel Element ID
This information element identifies a particular channel element instance within a target
BS.

Octet

A3/A7 Element Identifier

Length

(MSB)

CE ID - octet 1

...

CE ID - octet m

(LSB)

m+2

4
5
6
7

Length:

This field indicates the number of octets in this element

following the Length field. The value in this field shall be in
the range 1 through 6.

8
9

CE ID:

This field contains a value that the target BS uses to identify

internal resources.

10

6.2.2.133

UNUSED SECTION

11

789

TIA/EIA/IS-2001

6.2.2.134

Message CRC

2
3
4

This is a standard 16-bit message CRC computed over the Message Type II and the
Forward Layer 3 Data (or Reverse Layer 3 Data) information elements. It is based on the
standard CRC-CCITT generator polynomial g(x) = x16 +x12+x5+1.
7

(MSB)

CRC

1
(LSB)

5
6
7

6.2.2.135

UNUSED SECTION

6.2.2.136

UNUSED SECTION

8
9
10

790

Octet

TIA/EIA/IS-2001

6.2.2.137

Authentication Data

2
3

This element contains the authentication data used as input to the authentication
algorithm.
7

Octet

A1 Element Identifier

Length

(MSB)

3
Auth-Data

4
(LSB)

4
5

Length:

The Length field contains the number of octets in this

element following the Length field.

6
7
8
9

Auth-Data:

The value of this field is derived from the last six

digits or characters sent by the MS as described in
the Authentication of Mobile Station Origination
section of TIA/EIA-IS-2000.

10

6.2.2.138

UNUSED SECTION

6.2.2.139

UNUSED SECTION

6.2.2.140

UNUSED SECTION

6.2.2.141

Channel Element Status

11
12
13
14
15
16
17

This element contains the status of a set of channel elements at a target BS.
7

Octet

A3/A7 Element Identifier

Length

Reserved

Xmit On

18
19
20

Length:

This field indicates the number of octets in this

element following the Length field.

21
22
23

Xmit On:

This field indicates whether the cells indicated in the

accompanying Cell Identifier List element currently
have their transmitters and receivers turned on.

24

0 = transmitter(s) and receiver(s) is(are) off.

25

1 = transmitter(s) and receiver(s) is(are) on.

791

TIA/EIA/IS-2001

6.2.2.142

Cause List
This element contains a list of cause values that can be correlated to a list of cells.

Octet

A3/A7 Element Identifier

Length

Reserved

Cause Value 1

...
Reserved

Cause Value n

n+2

3
4
5

Length:

This field indicates the number of octets in this

element following the Length field.

6
7

Cause Value:

This field contains one of the cause values listed in

section 6.2.2.19.

6.2.2.143

Privacy Info
This element contains the CDMA long code masks (public and private).

(MSB)

A3/A7 Element Identifier

Length

Privacy Mask Information - 1, first octet

...

...

Privacy Mask Information - 1, last octet

(MSB)

(LSB)

Privacy Mask Information - 2, first octet

j
j+1

...

...

Privacy Mask Information - 2, last octet

(LSB)

...
(MSB)

Octet

...

Privacy Mask Information - n, first octet

...

...

Privacy Mask Information - n, last octet

(LSB)

10
11
12

Length:

This field indicates the number of octets in this

element following the Length field.

792

TIA/EIA/IS-2001

The Privacy Mask Information field is coded as follows:

7

Reserved

Privacy Mask Type

Octet

Status

Available

Privacy Mask Length

(MSB)

Privacy Mask - octet 1

...

...

Privacy Mask - octet m

2
3
4
5
6
7
8

Octet 1:

(LSB)

m+2

Bit 0 indicates if the algorithm is available

(supported). The BS sets this bit appropriately when
this element is included in a message being sent by a
BS. The MSC always sets this bit to 0 and the BS
always ignores it when this element is included in a
message being sent by the MSC. Available is coded
1, and not available is coded 0.

9
10

Bit 1, the status indication, is coded 1 to indicate

active and 0 to indicate inactive.

11
12

Bits 2 through 6 contain the Privacy Mask Type; see

the table below.

13

Bit 7 is reserved.

14
15
16

Octet 2:

Contains a value indicating the number of octets in

the following Privacy Mask field.

Table 6 - 98 - Privacy Info - Privacy Mask Type

Value

Privacy Mask Type

00000

Not Used - Invalid value.

00001

Public Long Code Mask

00010

Private Long Code Mask

All other values

Reserved

17
18
19
20

Public Long Code Mask:

Encryption parameter for TIA/EIA-IS-2000. Key length is 42 bits,
encoded in 6 octets, such that the 6 unused bits are set equal to '0',
and occupy the high-order positions of the most significant octet.

21
22
23
24

Private Long Code Mask:

Encryption parameter for TIA/EIA-IS-2000. Key length is 42 bits,
encoded in 6 octets, such that the 6 unused bits are set equal to '0',
and occupy the high-order positions of the most significant octet.

793

TIA/EIA/IS-2001

6.2.2.144

2
3

A3 Connect Information
This element contains information on one or more cells to be added to a single new or
existing A3 connection.

(MSB)

A3/A7 Element Identifier

Length

Length of Cell Info Record

Cell Info Record - first octet

Cell Info Record - second octet

Cell Info Record - last octet

Length of Traffic Circuit ID

j+1

Traffic Circuit ID

j+2

(LSB)

(MSB)

k+1

Extended Handoff Direction Parameters - 1st cell, 1st octet

k+2

Extended Handoff Direction Parameters - 1st cell, last octet

Extended Handoff Direction Parameters - last cell, 1st octet

Extended Handoff Direction Parameters - last cell, last octet

Length of Channel Element ID

n+1

Channel Element ID - first octet

n+2

Channel Element ID - last octet

(LSB)

Length of A3 Originating ID

p+1

A3 Originating ID

p+2
(LSB)

Length of A7 Destination ID
(MSB)

Extended Handoff Direction Parameters Field Length

(MSB)

Octet

A7 Destination ID

q+1
(LSB)

794

p+3

q+2

TIA/EIA/IS-2001

1
2

Length:

This field indicates the number of octets in this element following the
Length field.

New A3 Indicator:

This field indicates whether a new A3 connection is to be created.

4
5

0 = a new A3 connections is NOT to be created - this element refers

to an existing A3 connection.

6
7

1 = a new A3 connections IS to be created - this element refers to a

new A3 connection.

8
9
10

L Physical Channel Type:

This field contains the binary value used to indicate a type of
physical channel associated with the indicated traffic connection. Valid
values are shown below.

11
Value (hex)

Physical Channel Type

0H

IS-95 Fundamental Channel TIA/EIA/IS-95

1H

Fundamental Channel (FCH) TIA/EIA/IS-2000

2H

Supplemental Channel (SCH) TIA/EIA/IS-2000

3H

Dedicated Control Channel (DCCH) TIA/EIA/IS-2000

All other values

Reserved

12
13
14
15

length of Cell Info Record:

This field indicates the number of immediately following octets that
contain the Cell Info Record.

16
17
18
19
20
21
22
23

Cell Info Record:

This field is formatted exactly the same as the Cell Information Record
element from octet 3 to the end. It contains information on all cells
attached to this A3 connection, whether they are being newly
attached to this A3 connection by the current operation or they were
previously attached by an earlier operation. If, after power combining
is applied in the reverse direction, multiple frames exist at the BS, preselection is applied to these frames and a single frame is sent in the
reverse direction on the A3 traffic connection.

24
25

For Supplemental Channel, the code channel field in this Cell Info
Record (see section 6.2.2.89) is ignored.

26
27
28

Length of Traffic Circuit ID:

This field indicates the number of immediately following octets that
contain the A3 Traffic Circuit ID value for this A3 connection.

29
30

Traffic Circuit ID:

31
32
33

Extended Handoff Direction Parameters Field Length:

This field indicates the number of octets contained in each
occurrence of the Extended Handoff Direction Parameters field.

34
35
36
37

Extended Handoff Direction Parameters:

This field is formatted exactly the same as the Extended Handoff
Direction Parameters element (see section 6.2.2.73) from octet 3 to the
end, and is repeated for each cell attached to this A3 connection in a

This field is formatted exactly the same as the A3 Traffic Circuit ID

element from octet 3 to the end.(see section 6.2.2.89).

795

TIA/EIA/IS-2001

1
2

one-to-one correspondence with the cells listed in the Cell Info

Record field.

3
4
5
6
7

Length of Channel Element ID:

This field indicates the number of immediately following octets that
contain the Channel Element ID value for this A3 connection. This
field shall be set to 0000 0000 if no Channel Element ID value is
included in this element.

8
9
10
11
12
13

Channel Element ID:

This field is formatted exactly the same as the Channel Element ID

element (section 6.2.2.132) from octet 3 to the end. If a value is
included in this field, i.e., if the Length of Channel Element ID field
contains a value other than 0000 0000, this value shall be saved and
sent by the SDU function to the target BS in all subsequent A3
signaling messages.

14
15
16

Length of A3 Originating ID: This field indicates the number of octets in this element
following the Length field. The maximum value in this version of this
specification is 2 octets.

17
18
19
20
21
22
23

A3 Originating ID:

24
25
26
27

Length of A7 Destination ID: This field indicates the number of octets in this element
following the Length field. The maximum value in this version of this
specification is 2 octets. This field shall be set to 0000 0000 if no A7
Destination ID value is included in this element.

28
29
30
31
32

A7 Destination ID:

This field is formatted exactly the same as the A3 Originating ID

element (section 6.2.2.174) from octet 3 to the end. If a value is
included in this field, i.e., if the Length of A3 Originating ID field
contains a value other than 0000 0000, this value shall be saved and
sent by the SDU function to the target BS as the A3 Destination ID in
all subsequent A3 signaling messages that are related to the traffic
connection.

This field is formatted exactly the same as the A3 Destination ID

element (section 6.2.2.173) from octet 3 to the end. If the A7
Originating ID was included in the associated A7-Handoff Request
message and the A3 Flag was set to '1', then this field should be set to
the value of the A7 Originating ID.

33

796

TIA/EIA/IS-2001

6.2.2.145

2
3
4

A3 Connect Ack Information

This element contains information on a new or existing A3 connection referenced in a
corresponding A3 Connect Information element from the A3-Connect message that is
being responded to.

Reserved

A3/A7 Element Identifier

Length

Soft Handoff Leg #

PMC
Cause
Present

Xmit
Notify

Length of Traffic Circuit ID

(MSB)

Traffic Circuit ID - first octet

Traffic Circuit ID - last octet

(LSB)

Length of Channel Element ID

Channel Element ID - first octet

m+2

Channel Element ID - last octet

(LSB)

PMC Cause

n+1

Length of A3 Originating ID

A3 Originating ID

p+1
(LSB)

Length of A3 Destination ID
(MSB)

m
m+1

(MSB)

(MSB)

Octet

A3 Destination ID

q+1
(LSB)

5
6

Length:

This field indicates the number of octets in this element following the
Length field.

7
8
9

Xmit Notify:

This field indicates whether the target BS shall send a A3-Traffic

Channel Status message indicating that the transmitter and receiver of
the cell(s) at the target BS have been activated.

10
11

0 = Target BS shall not send a A3-Traffic Channel Status message

upon activation of the transmitter(s) and receiver(s).

12
13

1 = Target BS shall send a A3-Traffic Channel Status message upon

activation of the transmitter(s) and receiver(s).

14
15
16
17
18
19

PMC Cause Present:

This field indicates whether a single octet is present following the

Length of Channel Element ID field (and the Channel Element ID field
is the first of these fields is non-zero) containing a PMC Cause value.
This field is always coded as 1 for backward compatibility with
previous versions of the IOS.
1 = A PMC Cause value IS present.

797

TIA/EIA/IS-2001

1
2
3
4

Soft Handoff Leg #:

This field is used to carry the soft handoff leg number as determined
by the source BS. The value in this field shall be transferred to the
Soft Handoff Leg # field of the Reverse Layer 3 Data element in the
A3-FCH/DCCH/SCH Reverse messages sent to the source BS.

5
6
7
8
9

Length of Traffic Circuit ID:

This field indicates the number of immediately following octets that
contain the A3 Traffic Circuit ID value for this A3 connection. This
field shall be set to 0000 0000 if no A3 Traffic Circuit ID value is
included in this element.

10
11
12

Traffic Circuit ID:

This field is formatted exactly the same as the A3 Traffic Circuit ID

element from octet 3 to the end. This field is optional if the Channel
Element ID field of this element contains a value.

13
14
15
16
17

Length of Channel Element ID:

This field indicates the number of immediately following octets that
contain the Channel Element ID value for this A3 connection. This
field shall be set to 0000 0000 if no Channel Element ID value is
included in this element.

18
19
20
21
22

Channel Element ID:

This field is formatted exactly the same as the Channel Element ID

element (section 6.2.2.132) from octet 3 to the end. If a value was
included in the Channel Element ID field of the corresponding A3
Connect Information element, this field shall be set to the value that
was saved from that element.

23
24
25
26
27
28
29

PMC Cause:

This field is formatted exactly the same as octet 3 of the PMC Cause
element. If no error has occurred in processing the corresponding
Connect Information element from the A3 Connect message, then this
field shall contain a value of No Error. If an error has occurred in
processing the corresponding A3 Connect Information element from
the A3-Connect message, this field shall contain an appropriate PMC
Cause Value as found in 6.2.2.99.

30
31
32
33

Length of A3 Originating ID: This field indicates the number of octets in this element
following the Length field. The maximum value in this version of this
specification is 2 octets.

34
35
36
37
38
39

A3 Originating ID:

40
41
42
43

Length of A3 Destination ID: This field indicates the number of octets in this element
following the Length field. The maximum value in this version of this
specification is 2 octets. This field shall be set to 0000 0000 if no A3
Destination ID value is included in this element.

44
45
46
47
48

A3 Destination ID:

This field is formatted exactly the same as the A3 Originating ID

element (section 6.2.2.174) from octet 3 to the end. If a value is
included in this field, i.e., if the Length of A3 Originating ID field
contains a value other than 0000 0000, this value shall be saved and
sent by the target BS to the source BS as the A3 Destination ID in all
subsequent A3 signaling messages related to the traffic connection.

This field is formatted exactly the same as the A3 Destination ID

element (section 6.2.2.175) from octet 3 to the end If a value was
included in the A3 Originating ID field of the corresponding A3
Connect Information element, this field shall be set to the value that
was saved from that element.

798

TIA/EIA/IS-2001

6.2.2.146

2
3

A3 Remove Information
This element contains information on one or more cells to be removed from a single
existing A3 connection.

799

Octet

TIA/EIA/IS-2001

A3/A7 Element Identifier

Length

Length of Traffic Circuit ID

(MSB)

4
Traffic Circuit ID

(LSB)

Number of Cells To Be Removed

j+1

Cell Identification Discriminator 1

j+2

(MSB)

j+3
Cell Identification 1

(LSB)

Cell Identification Discriminator n

(MSB)

m+1
Cell Identification n

(LSB)

(MSB)

Length of A3 Destination ID
(MSB)

A3 Destination ID

q+1
(LSB)

Length of A7 Destination ID
(MSB)

A7 Destination ID

r+1
(LSB)

r+2

1
2
3

Length:

4
5
6

Length of Traffic Circuit ID:

This field indicates the number of immediately following octets that
contain the A3 Traffic Circuit ID value for this A3 connection.

7
8

Traffic Circuit ID:

9
10
11

This field indicates the number of octets in this element following the
Length field.

This field is formatted exactly the same as the A3 Traffic Circuit ID

element from octet 3 to the end.

Number of Cells To Be Removed:

This field contains a count of the number of Removed Cell
Identification Discriminator/Cell Identification pairs that follow.

800

TIA/EIA/IS-2001

1
2
3
4
5
6

Cell Identification Discriminator:

This field uses the Cell Identification Discriminator values used with
the Cell Identifier element (see section 6.2.2.20) to describe the format
of the immediately following Cell Identification field.
Cell
Identification Discriminator values 0000 0010 and 0000 0111 are
allowed.

7
8
9

Cell Identification:

This field contains the Cell Identification of a cell associated with this
A3 connection. This field is formatted according to octets 4 through
the end of the Cell Identifier element as defined in section 6.2.2.20.

10
11
12
13

Length of A3 Destination ID: This field indicates the number of octets in this element
following the Length field. The maximum value in this version of this
specification is 2 octets. This field shall be set to 0000 0000 if no A3
Destination ID value is included in this element.

14
15
16
17
18

A3 Destination ID:

19
20
21
22

Length of A7 Destination ID: This field indicates the number of octets in this element
following the Length field. The maximum value in this version of this
specification is 2 octets. This field shall be set to 0000 0000 if no A7
Destination ID value is included in this element.

23
24
25
26
27

A7 Destination ID:

This field is formatted exactly the same as the A3 Destination ID

element (section 6.2.2.175) from octet 3 to the end. If a value was
included in the A3 Originating ID field of the corresponding A3
Connect Information element, this field shall be set to the value that
was saved from that element.

This field is formatted exactly the same as the A3 Destination ID

element (section 6.2.2.173) from octet 3 to the end. If the A7
Originating ID was included in the associated A7-Handoff request
message and the A3 Flag was set to '1', then this field should be set to
the value of the A7 Originating ID.

28

801

TIA/EIA/IS-2001

6.2.2.147

A3 Drop Information
This element indicates an A3 connection that is being removed in its entirety.

(MSB)

A3/A7 Element Identifier

Length

Length of Traffic Circuit ID

Traffic Circuit ID

(LSB)

Length of Channel Element ID

(MSB)

m
m+1

Channel Element ID - first octet

m+2

Channel Element ID - last octet

(LSB)

Length of A3 Destination ID
(MSB)

Octet

A3 Destination ID

q+1
(LSB)

802

TIA/EIA/IS-2001

1
2

Length:

This field indicates the number of octets in this element following the
Length field.

3
4
5
6
7

Length of Traffic Circuit ID:

This field indicates the number of immediately following octets that
contain the A3 Traffic Circuit ID value for this A3 connection. This
field shall be set to 0000 0000 if no A3 Traffic Circuit ID value is
included in this element.

8
9
10

Traffic Circuit ID:

This field is formatted exactly the same as the A3 Traffic Circuit ID

element from octet 3 to the end. This field is optional if the Channel
Element ID field of this element contains a value.

11
12
13
14
15

Length of Channel Element ID:

This field indicates the number of immediately following octets that
contain the Channel Element ID value for this A3 connection. This
field shall be set to 0000 0000 if no Channel Element ID value is
included in this element.

16
17
18
19
20

Channel Element ID:

21
22
23
24

Length of A3 Destination ID: This field indicates the number of octets in this element
following the Length field. The maximum value in this version of this
specification is 2 octets. This field shall be set to 0000 0000 if no A3
Destination ID value is included in this element.

25
26
27
28
29

A3 Destination ID:

This field is formatted exactly the same as the Channel Element ID

element from octet 3 to the end. If a value was included in the
Channel Element ID field of the corresponding A3 Connect
Information element, this field shall be set to the value that was saved
from that element.

This field is formatted exactly the same as the A3 Destination ID

element (section 6.2.2.175) from octet 3 to the end If a value was
included in the A3 Originating ID field of the corresponding A3
Connect Ack Information element, this field shall be set to the value
that was saved from that element.

803

TIA/EIA/IS-2001

6.2.2.148

Circuit Group

2
3

This element contains a list of circuit identities represented by a beginning circuit

identity code value, a count, and an optional bitmap. Please see the details below.
7

A1 Element Identifier

Length

Reserved

All
Circuits

Inclusive

Count
(MSB)

First CIC (most significant bits)

(second
unused
bit - if
any)

(third
unused
bit - if
any)

(fourth
unused
bit - if
any)

3
4
5

First CIC (least significant bits)

(first
unused
bit - if
any)

Octet

(fifth
unused
bit - if
any)

(LSB)
(sixth
unused
bit - if
any)

(seventh
unused
bit - if
any)

Circuit Bitmap

(corresp.
to value
in First
CIC field)
4
5

Length:

The Length field contains the number of octets in this element

following the Length field.

6
7
8
9
10
11
12

All Circuits:

This field is used to indicate that all circuits between the MSC and BS
are to be affected by the operation specified by the message when
this field is set to 1. In this case, only a single instance of this
element may be present in the message and only the first three octets
of this element are used. If this field is set to 0, the remaining fields
of this element specify the affected circuits and multiple instances of
this element may exist in the message.

13
14
15
16
17
18
19

Inclusive:

This field is used to indicate whether all circuits with identifiers in the
range [First CIC, First CIC + Count - 1] are represented by this
element. If this field is set to 1, then all circuits with identifiers in the
range are included and there is no Circuit Bitmap field included in this
element. If this field is set to 0, then not all circuits with identifiers in
the range are included. In this case, the Circuit Bitmap field identifies
the circuits that are included.

20
21
22
23
24

NOTE: When this element is used in a message that has a preceding

mandatory Circuit Identity Code element, the first value in the range
of circuits identified by the first occurrence of this element in the
message shall be the value contained within the Circuit Identity Code
element.

804

TIA/EIA/IS-2001

1
2
3

Count:

This is a binary encoded field that represents a count of the number

of circuits represented by this element including the given Circuit
Identity Code value in octets 5 and 6.

4
5

First CIC:

This field contains a Circuit Identity Code value formatted as shown

in octets 2 and 3 of 6.2.2.22.

6
7
8

Circuit Bitmap:

This variable sized field contains an integral number of octets

sufficiently large to contain (Count) bits. That is, the number of
octets in this field is equal to:

(Count ) / 8

10
11
12
13
14

Any unused bits occur in octet 7, beginning in bit position 7, and are
set to 0. Bit 0 in the highest numbered octet in the Circuit Bitmap
field corresponds to the circuit represented by the value in the First
CIC field. Bit 1 in that octet corresponds to the circuit represented by
the (value in the First CIC field) + 1, etc.

15
16
17
18

A bit in the Circuit Bitmap field that has a value of 1 indicates that
the corresponding circuit is included in the set of circuits referenced
by this element. A value of 0 indicates that the corresponding
circuit is not included in the set of circuits referenced by this element.

805

TIA/EIA/IS-2001

6.2.2.149

PACA Timestamp

PACA Timestamp indicates the time when the PACA call was originally queued.
7

Octet

A1 Element Identifier

Length

(MSB)

3
PACA Queuing Time

4
5
(LSB)

3
4

Length

5
6

PACA Queuing Time

A binary value representing the time of the service
request. The lower the binary value the earlier the time.

This field shall be set to the length of this element in octets following
the Length field.

806

TIA/EIA/IS-2001

6.2.2.150

PACA Order

2
3

The purpose of this element is the sender to instruct the receiver to take appropriate
action upon receiving the PACA Update message.
7

A1 Element Identifier

Length

Reserved

PACA Action Required

4
5

Length

The PACA Action Required field is coded as follows:

Table 6 - 99 - PACA Order - PACA Action Required

Description

Value (binary)
000

Reserved

001

Update Queue Position and notify MS

010

Remove MS from the queue and release MS

011

Remove MS from the queue

100

MS Requested PACA Cancel

101

BS Requested PACA Cancel

All other values

Reserved

8
Reserved

This field shall be set to the length of this element in octets following
the Length field.

PACA Action
Required

Octet

This field shall be set to 00000.

10

807

TIA/EIA/IS-2001

6.2.2.151

PACA Reorigination Indicator

2
3
4

This element indicates whether the access attempt is a user directed origination or a
PACA re-origination. This element is present only when the MS sends a priority service
request.
7

Octet

A1 Element Identifier

Length

Reserved

PRI

5
6

Length

This field shall be set to the length of this element in octets

following the Length field.

7
8
9

PRI

(PACA Reorigination Indicator) This field is set to 1 to

indicate that this is a PACA reorigination; otherwise it is set to
0.

Reserved

This field shall be set to 0000000.

10
11
12

808

TIA/EIA/IS-2001

6.2.2.152

Air Interface Message

2
3

This information element is used to contain an air-interface message or Layer 2acknowledgement received/to be sent on a control channel(s) by a target BS.
7

A3/A7 Element Identifier

Length

TIA/EIA-IS-2000 Message Type

Air Interface Message Length

(MSB)

5
Air Interface Message

(LSB)

4
5

Octet

Length:

The Length field is a binary value indicating the

number of octets following the Length field.

6
7
8
9
10

TIA/EIA-IS-2000 Message Type:

This field contains the type of the message contained
in the following Air Interface Message field. It is
provided to allow simpler recognition and handling by
the BS.

11
12
13
14

Air Interface Message Length:

This field contains a binary value indicating the
number of octets in the following Air Interface
Message field.

15
16

Air Interface Message:

This field contains the air-interface message

received/to be sent on a control channel(s).

17

809

TIA/EIA/IS-2001

6.2.2.153

Layer 2 Ack Request/Results

2
3

This information element is used to contain a Layer 2-acknowledgement request or

results received/to be sent on a control channel(s) by a target BS.
7

Octet

A3/A7 Element Identifier

Length

Reserved

Layer 2
Ack

4
5

Length:

The Length field is a binary value indicating the number of

octets following the Length field.

6
7
8
9

Layer 2 Ack:

When this element is included in the A7-Paging

Channel Message Transfer message, this bit shall be
set to 1 to indicate that a Layer 2 acknowledgment is
requested by the source BS.

10
11
12
13
14
15

When this element is included in the A7-Paging

Channel Message Transfer Ack message this bit is
set to 0 by the target BS to indicate failure to receive
a Layer 2 acknowledgment, and is set to 1 by the
target BS to indicate that a Layer 2 acknowledgment
was received from the MS.

16

810

TIA/EIA/IS-2001

6.2.2.154

A11 Message Type

2
3

This one octet element identifies the type of the A11 interface message. The structure
of the element conforms to as specified in RFC 2002, and is shown below.
0

Octet

A11 Message Type

4
5

The A11 interface message types are listed in Table 6 - 100. These values shall remain
coordinated with the values assigned by the IETF for the Mobile IP protocol.

Table 6 - 100 - A11 Interface Message Types

A11 Message
Type Value

Section
Reference

A11-Registration Request

01H

6.1.11.1

A11-Registration Reply

03H

6.1.11.2

A11-Registration Update

14H

6.1.11.3

A11-Registration Acknowledge

15H

6.1.11.4

A11 Interface Message Name

7
8

6.2.2.155

Flags

9
10
11

The structure of this element is as specified in RFC 2002, and is shown below. The
setting of the Flags bits determines how an A11 interface message is interpreted by the
receiving entity, and the characteristics of the A10 connection also.
0

Octet

Reserved

12
13

For the A11 Registration Request message, the Flag bits are set as specified in Table 6 101.

14

Table 6 - 101 - Setting of A11 Registration Request Message Flags

7

RES

Bit Position
Bit Identifier
Simultaneous Bindings

Broadcast Datagrams
0

Decapsulation by mobile node

0

Minimal Encapsulation
1

GRE Encapsulation
0

V.J. Compression
1

Reverse Tunneling
0

15

811

Reserved Bit

TIA/EIA/IS-2001

812

TIA/EIA/IS-2001

6.2.2.156

Lifetime

2
3
4

This two octet element indicates the number of seconds remaining before registration
for an A10 connection is considered expired. The structure of the element conforms to
RFC 2002 and is shown below.
0

(MSB)

Lifetime

Octet
1

(LSB)

5
6
7

6.2.2.157

Home Address

8
9
10

This four octet element identifies the IPv4 address of the entity for which the A10
connection is established. The structure of the element conforms to as specified in RFC
2002, and is shown below.
0

(MSB)

Octet
1

Home Address

2
3
(LSB)

11
12

Table 6 - 102 shows the setting of the Home Address field for various A11 interface
messages.

13

Table 6 - 102 - Setting of Home Address Field

Home Address

A11 Interface Message

A11-Registration Request

00 00 00 00 H

A11-Registration Reply

00 00 00 00 H

A11-Registration Update

00 00 00 00 H

A11-Registration Acknowledge

00 00 00 00 H

14

813

TIA/EIA/IS-2001

1
2

6.2.2.158

Home Agent

3
4

This element identifies the IPv4 address of the PDSN that terminates the A10
connection. The structure of the element conforms to RFC 2002 and is shown below.
0

(MSB)

Octet
1

Home Agent

2
3
(LSB)

5
6
7

6.2.2.159

Care-of-Address

8
9

This element identifies the IPv4 address of the PCF that terminates the A10 connection.
The structure of the element conforms to RFC 2002 and is shown below.
0

(MSB)

Octet
1

Care-of-Address

2
3
(LSB)

10

814

TIA/EIA/IS-2001

1
2

6.2.2.160

Identification

3
4
5
6

This element is used by the PCF and the PDSN for matching the A11-Registration
Requests with A11-Registration Replies, and A11-Registration Updates with A11Registration Acknowledge messages. It also protects against replay attacks (section
5.6, RFC 2002). The structure of the element conforms to RFC 2002 and is shown below.
0

(MSB)

Octet
1
2

Identification

3
4
5
6
7
(LSB)

815

TIA/EIA/IS-2001

1
2

6.2.2.161

Code

3
4

This element identifies the result of processing an A11-Registration Request message.

The structure of the element conforms to RFC 2002 and is shown below.
0

Code
The supported Code values are listed in Table 6 - 103.

Table 6 - 103 - A11 CODE Values

Decimal
Value

00H
80H
81H
82H
83H
85H
86H
88H
89H
8AH
8DH

0
128
129
130
131
133
134
136
137
138
141

All other values

Octet
1

Hex
Value

CODE
Registration Accepted
Registration Denied reason unspecified
Registration Denied administratively prohibited
Registration Denied insufficient resources
Registration Denied mobile node failed authentication
Registration Denied identification mismatch
Registration Denied poorly formed request
Registration Denied unknown PDSN address
Registration Denied requested reverse tunnel unavailable
Registration Denied reverse tunnel is mandatory and T bit not set
Registration Denied unsupported Vendor ID or unable to interpret data
in the CVSE
Reserved

7
8

816

TIA/EIA/IS-2001

6.2.2.162

Status

This element identifies the result of processing an A11-Registration Update message.

0

Status
The supported Status values are listed in Table 6 - 104.

Table 6 - 104 - A11 Status Values

Decimal
Value

0
0
80H
128
81H
129
83H
131
85H
133
86H
134
All other values

Octet
1

Hex
Value

A11 STATUS
Update Accepted
Update Denied reason unspecified
Update Denied administratively prohibited
Update Denied sending node failed authentication
Update Denied identification mismatch
Update Denied poorly formed Registration Update
Reserved

5
6

817

TIA/EIA/IS-2001

6.2.2.163

Mobile-Home Authentication Extension

2
3
4

This element is present in all A11-Registration Request and A11-Registration Reply

messages. This element marks the end of the authenticated data in these messages.
The structure of the extension conforms to RFC 2002 and is shown below.
0

Octet

A11 Element Identifier (Type)

Length

(MSB)

3
SPI

4
5
(LSB)

(MSB)

6
7

Authenticator

(LSB)

22

Type

20H. (Section 3.5.2, RFC 2002)

Length

This field is set to 4 plus the number of bytes in the authenticator.

SPI

This four octet field is set to the Security Parameter Index,

as described in section 1.6, RFC 2002.

Authenticator

For keyed-MD-5 authentication, the Authenticator field is

set to the 128-bit message digest value obtained by applying the
keyed-MD-5 algorithm in the prefix+suffix mode on the protected
fields. See section 3.5.1, RFC 2002 for details.

7
8
9
10
11
12
13
14

818

TIA/EIA/IS-2001

1
2

6.2.2.164

Registration Update Authentication Extension

3
4
5

This element is present in all A11-Registration Update and A11-Registration

Acknowledge messages. This element marks the end of the authenticated data in these
messages.

6
0

Octet

A11 Element Identifier (Type)

Length

(MSB)

3
SPI

4
5
(LSB)

(MSB)

6
7

Authenticator

(LSB)

22

7
8

Type

28H

Length

This field is set to 4 plus the number of bytes in the authenticator.

11
12

SPI

This four octet field is set to the Security Parameter Index,

as described in section 1.6, RFC 2002.

13

Authenticator

10

14
15
16
17

For keyed-MD-5 authentication, the Authenticator field is set to the

128-bit message digest value obtained by applying the keyed-MD-5
algorithm in the prefix+suffix mode on the protected fields. See
section 3.5.1, RFC 2002 for details.

18
19

819

TIA/EIA/IS-2001

6.2.2.165

Session Specific Extension

2
3
4

This element is present in all A11-Registration Request, A11-Registration Reply, A11Registration Update and A11-Registration Acknowledge messages. This element
includes the mobile identity and session specific information.
0

Octet

A11 Element Identifier (Type)

Length

(MSB)

3
Protocol Type

(LSB)

(MSB)

4
5

Key

6
7
(LSB)

Reserved

Reserved

10

(MSB)

11
MN Session Reference Id

(LSB)

(MSB)

12
13

MN ID Type

(LSB)

MN ID Length

14
15

Identity Digit 1

Odd/Even Indicator

16

Identity Digit 3

Identity Digit 2

17

Identity Digit N+1

Identity Digit N

Variable

5
6

Type

27H

820

TIA/EIA/IS-2001

1
2

Length

This one octet field indicates the length (in bytes) of the extension,
NOT including the Type and Length fields.

3
4
5

Protocol Type

This two octet field identifies the type of the link layer protocol
/network layer protocol in use at the mobile node. The supported
Protocol Type values are listed below:

Table 6 - 105 - A11 Protocol Type Values

Protocol Type

Value

PPP

88 0BH

Unstructured Byte
Stream

88 81H

7
8
9
10
11
12
13

Key

This field, along with the PCF-Address and the PDSN-Address,

identifies the A10 bearer connection on behalf of a packet data
session. This field is set to the PCF Session Identifier (PSI) assigned
to a packet data session by the PCF. This value is only unique within
a single PCF. This Key value is also inserted in the Key field of every
GRE frame containing user data sent over the A10 connection.

14
15

Reserved

This field is not used at present. It is set to zero by the sending entity
and ignored by the receiving entity.

16
17
18
19
20
21

MN Session ReferenceID This field is used to differentiate multiple packet data service sessions
in the mobile. In the future releases, the MN Session Reference ID
will be passed to the PCF from the mobile on each origination. Note
that for this release, only a single session is supported and therefore
the MN Session Reference ID is not passed to the PCF, and the PCF
should set the value of this element to 1 (one).

22

23
24
25

MN ID Type

This field indicates the type of the address used by the mobile node.
The supported MN ID Type values are listed in Table 6-26. Note only
the least significant bits are shown, all other bits are set to zero

26
27

MN ID Length

This one octet field identifies the number of octets following the MN
ID Length field.

28
29

Odd/Even Indicator

This field is set to 0000 for an even number of identity digits and to
0001 for an odd number of identity digits.

30

Identity Digits:

The identity digits are coded as follows:

31
32
33

The International Mobile Subscriber Identifier fields are coded using

BCD coding format. If the number of identity digits is even then bits 0
to 3 of the last octet shall be filled with an end mark coded as 1111.

34

The Broadcast Address is encoded as specified in TIA/EIA/IS-637.

35

821

TIA/EIA/IS-2001

6.2.2.166

Vendor/Organization Specific Extension

2
3
4
5

This element may be present in the A11-Registration Request message to convey the
accounting information from the PCF to the PDSN. This element may also be present in
the A11-Registration Request message to convey the Mobility Event Indicator) from
the PCF to the PDSN during dormant handoffs and active/hard handoffs.

6
7
8
9

When used to convey the accounting information, the accounting records are
contained within the Application Data field of this element. The accounting records
conveyed from the PCF to the PDSN conform to the specifications in TIA/EIA IS-835
(Wireless IP Network Standard).

10
0

Octet

A11 Element Identifier (Type)

Reserved

(MSB)

3
Length

(LSB)

(MSB)

4
5

3GPP2 Vendor ID

6
7
(LSB)

Application Type

Application Sub Type

10

(MSB)

11
12
Application Data

(LSB)

Variable

11
12

Type

26H

13
14
15

Length

This field indicates the number of octets in this element following this
field.

16

3GPP2 Vendor ID

00 00 15 9FH

Application Type

This field indicates the type of the application, that the extension
relates to. The supported values are:

17
18
19

822

TIA/EIA/IS-2001

Table 6 - 106 - Vendor/Organization Specific Extension - Application Type

Hex Value

Description

01 H

Accounting

02H

Mobility Event Indicator

03H

Data Available Indicator

All Others

Reserved Available for future use

2
3
4
5

Application Sub Type

This one octet field indicates the Application sub-type within the
Application Type. The supported values are listed in Table 6 - 107 Application Sub Type.

6
7

Table 6 - 108 - Application Sub Type

Application Type

Application Sub Type

Application Type
Name

HEX Value

Application Sub
Type Name

HEX Value

Accounting

01 H

RADIUS

01H

DIAMETER

02H

All other values are reserved

Mobility Event
Indicator

02H

Mobility

01H

All other values are reserved

Data Available
Indicator

03H

Data Ready to Send

01H

All other values are reserved

8
9

Application Data

10
11
12
13
14
15
16

For Application Type 01H (Accounting), this field contains the

accounting parameters conveyed from the PCF to the PDSN as
specified in TIA/EIA IS-835 (Wireless IP Network Standard). Each of
the accounting parameters is structured in the format of RADIUS
attributes specified in RFC 2138 and RFC 2139 and in P.S001 (Wireless
IP Network Standard). This field is used in messages sent from the
PCF to the PDSN.

17
18
19

For Application Type 02H (Mobility Event Indicator), this field is zero
bytes in length. This field is used in messages sent from the PCF to
the PDSN.

20
21
22

For Application Type 03H (Data Availabile Indicator), this field is zero
bytes in length. This field is used in messages sent from the PDSN to
the PCF.

23

823

TIA/EIA/IS-2001

1
2

6.2.2.167

A9 Message Type

3
4

The A9 Message Type element is used to indicate the type of a message on the A9
interface.
A9 Message Name

A9 Message

Section

Type

Reference

A9-Setup-A8

01H

6.1.10.1

A9-Connect-A8

02H

6.1.10.2

A9-Disconnect-A8

03H

6.1.10.3

A9-Release-A8

04H

6.1.10.4

A9-Release-A8 Complete

05H

6.1.10.5

A9-BS Service Request

06H

6.1.10.6

A9-BS Service Response

07H

6.1.10.7

A9-AL Connected

08H

6.1.10.8

A9-AL Connected Ack

09H

6.1.10.9

A9-AL Disconnected

0AH

6.1.10.10

A9-AL Disconnected Ack

0BH

6.1.10.11

5
6

6.2.2.168

CON_REF

7
8

This information element identifies connection instance between the MS and the source
BS.
7

Octet

A9 Element Identifier

Length

IS-2000 CON_REF

9
10

Length

This field shall be set to the length of this element in octets following
the Length field.

11
12

IS-2000 CON_REF

This field contains the connection reference value defined in

TIA/EIA/IS-2000.

824

TIA/EIA/IS-2001

1
2

6.2.2.169

A9 BSC_ID

This information element specifies the identifier of a particular BS.

7

Octet

A9 Element Identifier

Length

(MSB)

3
BSC Identifier

(LSB)

4
5

Length

This field shall be set to the length of this element in octets following
the Length field.

6
7

BSC Identifier

This field is used to identify the BSC connected to the PCF on an A8

connection. This field shall be no more than 6 octets in length.

825

Variable

TIA/EIA/IS-2001

1
2

6.2.2.170

A8_Traffic_ID

This information element identifies the connection used by the MS for packet service.
7

Octet

A9 Element Identifier

Length

A8 transport protocol stack

Protocol Type

(MSB)

(LSB)
(MSB)

5
6

Key

7
8
(LSB)

Address Type

10

(MSB)

11
IP Address

...
(LSB)

4
5

Length

6
7
8

A8 transport protocol stack

This field is used to identify the A8 transport protocol stack to be
used for the A8 connection.

This field shall be set to the length of this element in octets following
the Length field.

Table 6 - 109 - A8_Traffic_ID - A8 Transport Protocol Stack

Values
01H
All Others

Meaning
GRE/IP
Reserved

10
11
12

Protocol Type

This field is used to indicate the protocol type to be tunneled across

the A8 interface. It is same as the Protocol Type field in the GRE
header. This field is set to 0x880B (PPP).

13
14
15

Key

This is a four octet field. This field is used to indicate the A8

connection identification. It is same as the Key field in the GRE
header.

826

variable

TIA/EIA/IS-2001

1
2

Address Type

This field indicates the type and format of the IP Address that
follows.

Table 6 - 110 - A8_Traffic_ID - Address Type

Value

Address Type

Length of IP Address

01H

Internet Protocol IPv4

4 octets

02H

Internet Protocol IPv6

variable

All other values

Reserved

4
5
6
7
8
9

IP Address

This field has a variable length that is dependent on the Type field.
This field is used to indicate the IP address of the A8 bearer port on
the sending entity. That is, when the BSC sends the A9-Setup-A8
message containing this element, this field contains the IP address at
the BSC where the A8 user traffic connection will terminate.

10
11

6.2.2.171

A9 Indicators

12
13
14

This information element indicates whether an A9-Setup-A8 message is being sent by

the source BS as a result of an initial connection, or by the target BS as a result of a
handoff operation.
7

Octet

A9 Element Identifier

Length

Reserved

Data
Ready
Indicator

Handoff
Indicator

15
16

Length

This field shall be set to the length of this element in octets following
the Length field.

17
18
19
20
21

Handoff indicator

This field indicates whether Handoff was performed or not. If this

field is set 0, the Setup message indicates a normal call setup. If this
field is set 1, the Setup message indicates a Hard Handoff is to be
performed and it is not necessary to establish the A10/A11
connection immediately.

22
23
24
25
26

Data Ready Indicator

This field indicates whether there is data ready to be sent from the
mobile to the network. It reflects the value of the DRS bit of the air
interface. If this field is set to 0, it indicates that data is not ready to
be sent and the A9-Setup-A8 message is reporting a mobility event.
Otherwise (set to 1) it indicates that data is ready to be sent.

827

TIA/EIA/IS-2001

6.2.2.172

2
3
4
5
6
7

A7 Originating ID
This element contains an identifier chosen by this (the near end) BS for its own use in
quickly processing A7 signaling messages received from the far end BS. For example, it
may be used to identify the resources supporting the call association that are internal to
this BS. If an A7 Originating ID is supplied by this BS, then the far end BS includes this
in the A7 Destination ID element in subsequent A7 messages to this BS for this call
association.

Octet

A3/A7 Element Identifier

Length

Reserved
(MSB)

A3 Flag

A7 Originating ID

3
4

(LSB)

8
9
10

Length:

This field indicates the number of octets in this

element following the Length field. The maximum
value in this version of this specification is 2 octets.

11
12
13
14
15

A3 Flag:

If this field is set to '1' in the A7-Handoff Request

message, then the value of the A7 Originating ID
should be returned in the A7 Destination ID
parameter in all A3 messages sent from the Target BS
to the Source BS.

16
17
18
19
20

A7 Originating ID:

This field has variable length. The actual length is

indicated in the Length field and is dependent upon
the particular implementation. In this version of this
standard, this value shall be no more than 2 octets
long.

828

TIA/EIA/IS-2001

6.2.2.173

2
3

This element contains an identifier chosen by the far end BS for its own use in quickly processing
A7signaling messages.

4
5

If an A7 Originating ID was supplied by the far end BS, then the near end BS includes this value in the A7
Destination ID element in subsequent A7 messages to the far end BS for this call association.
7

A7 Destination ID

(MSB)

A3/A7 Element Identifier

Length

A7 Destination ID

3
(LSB)

6
7
8
9
10
11
12
13

Octet

Length:

This field indicates the number of octets in this

element following the Length field. The maximum
value in this version of this specification is 2 octets.

A7 Destination ID:

This field has variable length. The actual length is

indicated in the Length field and is dependent upon
the particular implementation. In this version of this
standard, this value shall be no more than 2 octets
long.

829

TIA/EIA/IS-2001

6.2.2.174

2
3
4
5
6

This element contains an identifier chosen by this (the near end) BS for its own use in quickly processing
A3 signaling messages received from the far end BS. For example, it may be used to identify a particular
leg of a particular call, or it may identify the resources supporting that leg that are internal to this BS. If an
A7 Originating ID is supplied by this BS, then the far end BS includes this in the A3 Destination ID
element in subsequent A3 messages to this BS related to the traffic connection.
7

A3 Originating ID

(MSB)

A3/A7 Element Identifier

Length

A3 Originating ID

3
(LSB)

7
8
9
10
11
12
13
14

Octet

Length:

This field indicates the number of octets in this

element following the Length field. The maximum
value in this version of this specification is 2 octets.

A3 Originating ID:

This field has variable length. The actual length is

indicated in the Length field and is dependent upon
the particular implementation. In this version of this
standard, this value shall be no more than 2 octets
long.

830

TIA/EIA/IS-2001

6.2.2.175

2
3

This element contains an identifier chosen by the far end BS for its own use in quickly processing A3
signaling messages.

4
5

If an A3 Originating ID was supplied by the far end BS, then the near end BS includes this value in the A3
Destination ID element in subsequent A3 messages to the far end BS related to the traffic connection.
7

A3 Destination ID

(MSB)

A3/A7 Element Identifier

Length

A3 Destination ID

3
(LSB)

6
7
8
9
10
11
12
13

Octet

Length:

This field indicates the number of octets in this

element following the Length field. The maximum
value is 2 octets.

A3 Destination ID:

This field has variable length. The actual length is

indicated in the Length field and is dependent upon
the particular implementation. In this version of this
standard, this value shall be no more than n octets
long.

831

TIA/EIA/IS-2001

6.2.2.176

2
3
4

IS-2000 Power Control Info

This element provides information about power control for IS-2000 channels, including
information used for forward gain equalization for a given IS-2000 power control
subchannel.

FPC_
PRI_
CHAN

5
6
7
8
9

Octet

Element Identifier

Length

Mobile Pilot Gain

Reserved

Count of Subchan Gains

Reserved

FPC_SUBCHAN_GAIN 1

Reserved

FPC_SUBCHAN_GAIN 2

Reserved

FPC_SUBCHAN_GAIN 3

Element Identifier:

This information element is used on multiple interfaces. When the

information element is included in a message that is sent on the A1
interface, the Element Identifier field is coded as 0EH. When the
information element is included in a message sent on the A7 interface,
the Element Identifier field is coded as 10H.

10
11

Length:

This field indicates the number of octets in this element following the
Length field.

12
13
14
15
16
17
18
19
20
21
22

Mobile Pilot Gain:

This field specifies the ratio of the mobile's pilot channel power gain
to the primary reverse traffic channel power gain, where the primary
reverse traffic channel is defined to be the channel on which the
reverse outer loop is run. The primary reverse traffic channel shall be
the Fundamental Channel (FCH) if it exists, and the Dedicated Control
Channel (DCCH) otherwise. The mobile pilot gain, together with
information specific to the targets ASIC, is used by the target BS to
convert the reverse Eb/Nt received in the forward traffic frame to a
reverse outer loop threshold (reverse pilot setpoint). The range of
values for this field is 0 to 255, which corresponds to 31.875 dB to 0
dB in 0.125 dB increments.

23
24

FPC_PRI_CHAN:

This field indicates which forward link physical channel supports the
power control channel. (0 = forward FCH, 1 = DCCH).

25
26
27
28
29
30
31
32
33

Count of Subchan Gains:

This field indicates the number of fields immediately following that
represent the FPC_SUBCHAN_GAIN value that applies to the call
depending on the number of independent soft handoff legs. In this
version of the IOS, the value of this field is 3. The number of
independent soft handoff legs is sent in the A3 traffic frame. When
determining the number of independent soft handoff legs, a set of
legs in softer handoff are counted as a single leg. These values
represent the following table:

832

TIA/EIA/IS-2001

Count of Independent Soft

Handoff Legs

1
2
3
4
5
6

FPC_SUBCHAN_GAIN

1 leg

FPC_SUBCHAN_GAIN 1

2 legs

FPC_SUBCHAN_GAIN 2

3 legs

FPC_SUBCHAN_GAIN 3

FPC_SUBCHAN_GAIN n:
This field specifies the power gain level of the forward link power
control subchannel on the F-FCH or F-DCCH that the forward power
control subchannel is punctured on, for a given number of
independent soft handoff legs as indicated in the previous table. The
resolution is 0.25 dB. (Defined in TIA/EIA/IS-2000-5 3.7.3.3.2.31)

833

TIA/EIA/IS-2001

6.2.2.177

IS-2000 Forward Power Control Mode

This element specifies the forward power control mode for IS-2000 channels.

3
7

Octet

A3/A7 Element Identifier

Length

Reserved

FPC_MODE
ACTION_TIME

3
4

4
5

Length:

This field indicates the number of octets in this element following the
Length field.

6
7
8

FPC_MODE:

This field specifies the forward power control operating mode. This
indicates the power control subchannel configuration on the reverse
pilot channel. (Defined in TIA/EIA/IS-2000-2 Table 2.1.3.1.10.1-1.)

ACTION_TIME:

This field shall be set to the CDMA System Time (see TIA/EIA/IS2000) in units of 80 ms (modulo 64) at which the values specified in
the fields of this element take effect.

9
10
11
12

834

TIA/EIA/IS-2001

6.2.2.178

2
3

IS-2000 FPC Gain Ratio Info

This element provides information used for forward gain equalization for a given IS2000 power control subchannel.

Reserved

Octet

A3/A7 Element Identifier

Length

Initial Gain Ratio

Gain Adjust Step Size

Count of Gain Ratio Pairs

Min Gain Ratio 1

Max Gain Ratio 1

10

Min Gain Ratio 2

11

Max Gain Ratio 2

12

Min Gain Ratio 3

13

Max Gain Ratio 3

14

4
5
6
7

[NOTE: These fields apply either to the primary power control subchannel or to the secondary
power control subchannel, depending on what message this
information element is included in.]

8
9
10
11
12

Gain Adjust Step Size:

13
14
15
16

Initial Gain Ratio:

This field indicates the amount of forward channel gain change to be

used by the target BS when making gain adjustments on the physical
channel measured by the power control subchannel. The resolution is
0.25 dB.
This field indicates the initial forward link gain for the physical
channel measured by the power control subchannel. It is to be used
at the cell when adding a given soft handoff leg.

17

This field is ignored if the forward power control mode is 50 Hz (EIB).

18
19
20

The initial gain ratio is expressed according to the formula given for
the Forward Link Power Control: Gain Ratio (FPC: GR) in the A3 traffic
frame format for the corresponding physical channel.

21
22
23
24
25
26
27
28
29
30

Count of Gain Ratio Pairs:

This field indicates the number of pairs of octets immediately
following that represent the Min Gain Ratio and Max Gain Ratio
values that apply to the call depending on the number of independent
soft handoff legs. In this version of the IOS, the value of this field is
3. The number of independent soft handoff legs is sent in the A3
traffic frame of the corresponding physical channel.
When
determining the number of independent soft handoff legs, a set of
legs in softer handoff are counted as a single leg. These values
represent the following table:

835

TIA/EIA/IS-2001

1
Count of Independent Soft
Handoff Legs

Minimum
Gain Ratio

Maximum
Gain Ratio

1 leg

Min Gain Ratio 1

Max Gain Ratio 1

2 legs

Min Gain Ratio 2

Max Gain Ratio 2

3 legs

Min Gain Ratio 3

Max Gain Ratio 3

2
3
4
5

Min Gain Ratio:

This field indicates the minimum allowed forward link gain for the
physical channel measured by the power control subchannel.

6
7
8
9
10
11
12
13
14

The minimum gain ratio is expressed according to the formula given

for the Forward Link Power Control: Gain Ratio (FPC: GR) in the A3
traffic frame format for the corresponding physical channel.
Max Gain Ratio:
This field indicates the maximum allowed forward link gain for the
physical channel measured by the power control subchannel.
The maximum gain ratio is expressed according to the formula given
for the Forward Link Power Control: Gain Ratio (FPC: GR) in the A3
traffic frame format for the corresponding physical channel.

15

836

TIA/EIA/IS-2001

6.2.2.179

Data Count

This element contains a count the number of bytes to be transmitted.

7

3
4
5

Count

6.2.2.180

Octet

A3/A7 Element Identifier

Count

This element indicates the number of bytes remaining in the PCF. The
value FF FFH means that the number of bytes remaining is greater
than or equal to FF FFH bytes (64 kB).
IS-2000 Mobile Pilot Gain
This element provides information for reverse power control for IS-2000 channels.

8
9

Octet

A3/A7 Element Identifier

Length

Mobile Pilot Gain

ACTION_TIME

Length:

This field indicates the number of octets in this element following the
Length field.

10
11
12
13
14
15
16
17
18
19
20

Mobile Pilot Gain:

This field specifies the ratio of the mobile's pilot channel power gain
to the primary reverse traffic channel power gain, where the primary
reverse traffic channel is defined to be the channel on which the
reverse outer loop is run. The primary reverse traffic channel shall be
the Fundamental Channel (FCH) if it exists, and the Dedicated Control
Channel (DCCH) otherwise. The mobile pilot gain, together with
information specific to the targets ASIC, is used by the target BS to
convert the reverse Eb/Nt received in the forward traffic frame to a
reverse outer loop threshold (reverse pilot setpoint). The range of
values for this field is 0 to 255, which corresponds to 31.875 dB to 0
dB in 0.125 dB increments.

21
22
23

Action Time:

This field shall be set to the CDMA System Time (see TIA/EIA/IS2000) in units of 80 ms (modulo 64) at which the values specified in
the fields of this element take effect.

24

837

TIA/EIA/IS-2001

6.3

Timer Definitions

The following tables are in units of seconds unless otherwise noted.

Table 6 - 111 - Timer Values and Ranges Sorted by Name

Timer Name

Default
Value
(seconds)

Range of
Values
(seconds)

Granularity
(seconds)

T1

55

0 - 255

6.3.5.1

Facilities Management

T2

60

0 - 255

6.3.5.2

Facilities Management

T4

60

0 - 255

6.3.5.3

Facilities Management

T5

60

0 - 255

6.3.5.4

Facilities Management

T6

75

0 - 255

6.3.5.5

Facilities Management

T7

10

0 - 255

6.3.4.1

Handoff

6.3.4.2

Handoff

T8

See section 6.3.4.2.

Section
Reference

Classification

T9

10

0 - 255

6.3.4.3

Handoff

T10

0 - 99

6.3.1.1

Call Processing

T11

0 - 99

6.3.4.4

Handoff

T12

60

0 - 255

6.3.5.6

Facilities Management

T13

55

0 - 255

6.3.5.7

Facilities Management

T16

60

0 - 255

6.3.5.8

Facilities Management

T20

0 - 99

6.3.1.2

Call Processing

T30

0 - 99

6.3.1.3

Call Processing

T40

0 - 99

6.3.1.4

Call Processing

T50

60

0 - 255

6.3.4.4

Handoff

T52

90

0 - 255

6.3.4.5

Handoff

T60

0 - 99

6.3.2.1

Supplementary Services

T61

0 - 99

6.3.2.2

Supplementary Services

T62

0 - 99

6.3.2.3

Supplementary Services

T63

0 - 99

6.3.2.4

Supplementary Services

T300

1.5

0 - 99

0.1

6.3.1.5

Call Processing

T301

30

0 - 60

6.3.1.6

Call Processing

838

TIA/EIA/IS-2001

(cont.) Timer Values and Ranges Sorted by Name

Timer Name

Default
Value
(seconds)

Range of
Values
(seconds)

Granularity
(seconds)

T302

0 - 99

6.3.1.7

Call Processing

T303

0 - 99

6.3.1.8

Call Processing

T306

0 - 99

6.3.1.9

Call Processing

T307

0 - 99

6.3.1.10

Call Processing

T308

0 - 99

6.3.1.11

Call Processing

T309

0 - 90

6.3.5.9

Facilities Management

T311

0-5

0.1

6.3.1.13

Call Processing

T312

0 - 99

6.3.1.14

Call Processing

T313

0 - 99

6.3.1.14

Call Processing

T315

0 - 99

6.3.1.16

Call Processing

T316

0 - 99

6.3.1.17

Call Processing

T3231

0-99

6.3.1.19

Call Processing

T325

0 - 99

6.3.1.18

Call Processing

T326

0 - 99

6.3.1.19

Call Processing

T777

90

0 - 255

6.3.4.6

Handoff

T778

15

0 - 255

6.3.4.7

Handoff

T787

90

0 - 255

6.3.4.8

Handoff

T789

10

0 - 60

6.3.4.10

Handoff

T790

10

0 - 60

6.3.4.11

Handoff

T3113

0 - 99

6.3.1.20

Call Processing

T3210

30

0 - 99

6.3.3.1

Mobility Management

T3220

10

0 - 99

6.3.3.2

Mobility Management

T3230

0 - 99

6.3.1.21

Call Processing

T3240

0 - 99

6.3.3.3

Mobility Management

T3260

30

0 - 99

6.3.3.4

Mobility Management

T3270

0 - 99

6.3.3.5

Mobility Management

T3271

15

0 - 99

6.3.3.6

Mobility Management

T3272

0 - 99

6.3.3.7

Mobility Management

T3280

15

0 - 99

6.3.1.22

Call Processing

TA8-Setup

0-99

6.3.7.1

A8,A9 Interfaces

839

Section
Reference

Classification

TIA/EIA/IS-2001

(cont.) Timer Values and Ranges Sorted by Name

Timer Name

Default
Value
(seconds)

Range of
Values
(seconds)

Granularity
(seconds)

Tacm

0.5

0 - 1.0

0.1

6.3.6.16

A3, A7 Interfaces

Talc9

0.5

0 1.0

0.1

6.3.7.4

A8, A9 Interfaces

Tald9

0.5

0 1.0

0.1

6.3.7.7

A8, A9 Interfaces

Tbsreq9

1.5

0 5

0.1

6.3.7.6

A8, A9 Interfaces

Tbstact

0.6

0 1.0

0.1

6.3.6.1

A3, A7 Interfaces

Tbstcom

0.1

0 1.0

0.1

6.3.6.2

A3, A7 Interfaces

Tchanstat

0.5

0 - 1.0

0.1

6.3.6.13

A3, A7 Interfaces

Tchngserv

0 - 10

6.3.6.15

A3, A7 Interfaces

Tconn3

0.5

0 - 1.0

0.1

6.3.6.8

A3, A7 Interfaces

Tconn4

1 - 10

6.3.6.4

A3, A7 Interfaces

Tdiscon3

0.5

0 - 1.0

0.1

6.3.6.9

A3, A7 Interfaces

Tdiscon4

1 - 10

6.3.6.5

A3, A7 Interfaces

Tdiscon9

0-5

0.1

6.3.7.2

A8,A9 Interfaces

Tdrptgt

1 - 10

6.3.6.10

A3, A7 Interfaces

Ttgtrmv

1 - 10

6.3.6.12

A3, A7 Interfaces

Thoreq

0-5

0.1

6.3.6.11

A3, A7 Interfaces

Tpaca1

0 - 99

6.3.1.24

Call Processing

Tpaca2

0 - 99

6.3.1.25

Call Processing

Tpcm

0-2

0.1

6.3.6.17

A3, A7 Interfaces

Tphysical

0 - 10

6.3.6.14

A3, A7 Interfaces

Tregreq

05

0.1

6.3.1.25

A10, A11 Interfaces

Tregupd

05

0.1

6.3.1.26

A10, A11 Interfaces

Trel9

0-5

0.1

6.3.7.3

A8,A9 Interfaces

1800

0 65,535

60

6.3.1.24

A10, A11 Interfaces

Tservchange

0-5

6.3.6.9

A3, A7 Interfaces

Tsrcxfer

0.1

0 - 1.0

0.1

6.3.6.3

A3, A7 Interfaces

Trp

Section
Reference

Classification

Twaitho

See section 6.3.4.23.

6.3.4.23

Handoff

Twaitho9

See section 6.3.7.5

6.3.7.5

A8,A9 Interfaces

6.3.6.6

A3, A7 Interfaces

Txferabort

0.1

0 - 1.0

0.1

840

TIA/EIA/IS-2001

Table 6 - 112 - Timer Values and Ranges Sorted by Classification

Timer Name

Default
Value
(seconds)

Range of
Values
(seconds)

Granularity
(seconds)

T10

0 - 99

6.3.1.1

Call Processing

T20

0 - 99

6.3.1.2

Call Processing

T30

0 - 99

6.3.1.3

Call Processing

T300

1.5

0 - 99

0.1

6.3.1.5

Call Processing

T301

30

0 - 60

6.3.1.6

Call Processing

T302

0 - 99

6.3.1.7

Call Processing

T303

0 - 99

6.3.1.8

Call Processing

T306

0 - 99

6.3.1.9

Call Processing

T307

0 - 99

6.3.1.10

Call Processing

T308

0 - 99

6.3.1.11

Call Processing

T311

0-5

0.1

6.3.1.13

Call Processing

T312

0 - 99

6.3.1.14

Call Processing

T313

0 - 99

6.3.1.15

Call Processing

T315

0 - 99

6.3.1.16

Call Processing

T316

0 - 99

6.3.1.17

Call Processing

T325

0 - 99

6.3.1.18

Call Processing

T326

0 - 99

6.3.1.19

Call Processing

T3113

0 - 99

6.3.1.208

Call Processing

T3230

0 - 99

6.3.1.21

Call Processing

T3231

0-99

6.3.1.19

Call Processing

T3280

15

0 - 99

6.3.1.22

Call Processing

T40

0 - 99

6.3.1.4

Call Processing

Tpaca1

0 - 99

6.3.1.24

Call Processing

Tpaca2

0 - 99

6.3.1.25

Call Processing

T1

60

0 - 255

6.3.5.1

Facilities Management

T2

55

0 - 255

6.3.5.2

Facilities Management

T4

60

0 - 255

6.3.5.3

Facilities Management

T5

60

0 - 255

6.3.5.4

Facilities Management

T6

75

0 - 255

6.3.5.5

Facilities Management

T12

60

0 - 255

6.3.5.6

Facilities Management

841

Section
Reference

Classification

TIA/EIA/IS-2001

(cont.) - Timer Values and Ranges Sorted by Classification

Timer Name

Default
Value
(seconds)

Range of
Values
(seconds)

Granularity
(seconds)

T13

55

0 - 255

6.3.5.7

Facilities Management

T16

60

0 - 255

6.3.5.8

Facilities Management

T309

0 - 90

6.3.5.9

Facilities Management

T7

10

0 - 255

6.3.4.1

Handoff

6.3.4.2

Handoff

T8

See section 6.3.4.2.

Section
Reference

Classification

T9

10

0 - 255

6.3.4.3

Handoff

T11

0 - 99

6.3.4.4

Handoff

T50

60

0 - 255

6.3.4.4

Handoff

T52

90

0 - 255

6.3.4.5

Handoff

T777

90

0 - 255

6.3.4.6

Handoff

T778

15

0 - 255

6.3.4.7

Handoff

T787

90

0 - 255

6.3.4.8

Handoff

T789

10

0 - 60

6.3.4.10

Handoff

T790

10

0 - 60

6.3.4.11

Handoff

6.3.4.23

Handoff

Twaitho

See section 6.3.4.23.

T3210

30

0 - 99

6.3.3.1

Mobility Management

T3220

10

0 - 99

6.3.3.2

Mobility Management

T3240

0 - 99

6.3.3.3

Mobility Management

T3260

30

0 - 99

6.3.3.4

Mobility Management

T3270

0 - 99

6.3.3.5

Mobility Management

T3271

15

0 - 99

6.3.3.6

Mobility Management

T3272

0 - 99

6.3.3.7

Mobility Management

Tacm

0.5

0 - 1.0

0.1

6.3.6.16

A3, A7 Interfaces

Tdrptgt

1 - 10

6.3.6.10

A3, A7 Interfaces

Thoreq

0-5

0.1

6.3.6.11

A3, A7 Interfaces

Ttgtrmv

1 - 10

6.3.6.12

A3, A7 Interfaces

842

TIA/EIA/IS-2001

(cont.) - Timer Values and Ranges Sorted by Classification

Timer Name

Default
Value
(seconds)

Range of
Values
(seconds)

Granularity
(seconds)

Tbstact

0.6

0 1.0

0.1

6.3.6.1

A3, A7 Interfaces

Tbstcom

0.1

0 1.0

0.1

6.3.6.2

A3, A7 Interfaces

Tchanstat

0.5

0 - 1.0

0.1

6.3.6.13

A3, A7 Interfaces

Tchngserv

0 - 10

6.3.6.15

A3, A7 Interfaces

Tconn3

0.5

0 - 1.0

0.1

6.3.6.8

A3, A7 Interfaces

Tconn4

1 - 10

6.3.6.4

A3, A7 Interfaces

Tdiscon3

0.5

0 - 1.0

0.1

6.3.6.9

A3, A7 Interfaces

Tdiscon4

1 - 10

6.3.6.5

A3, A7 Interfaces

Tpcm

0-2

0.1

6.3.6.17

A3, A7 Interfaces

Tphysical

0 - 10

6.3.6.14

A3, A7 Interfaces

Tservchange

0-5

6.3.6.7

A3, A7 Interfaces

Tsrcxfer

0.1

0 - 1.0

0.1

6.3.6.3

A3, A7 Interfaces

Txferabort

0.1

0 - 1.0

0.1

6.3.6.6

TA8-Setup

0-99

6.3.7.1

A3, A7 Interfaces
A8,A9 Interfaces

Talc9

0.5

0 1.0

0.1

6.3.7.4

Tald9

0.5

0 1.0

0.1

6.3.7.7

Tbsreq9

1.5

0 5

0.1

6.3.7.6

Tdiscon9

0-5

0.1

6.3.7.2

Trel9

0-5

0.1

6.3.7.3

Twaitho9

See section 6.3.7.5

Section
Reference

6.3.7.5

Classification

A8, A9 Interfaces
A8, A9 Interfaces
A8, A9 Interfaces
A8,A9 Interfaces
A8,A9 Interfaces
A8,A9 Interfaces

Tregreq

05

0.1

6.3.1.25

A10, A11 Interfaces

Tregupd

05

0.1

6.3.1.26

A10, A11 Interfaces

Trp

1800

0 65,535

60

6.3.1.24

A10, A11 Interfaces

T60

0 - 99

6.3.2.1

Supplementary Services

T61

0 - 99

6.3.2.2

Supplementary Services

T62

0 - 99

6.3.2.3

Supplementary Services

T63

0 - 99

6.3.2.4

Supplementary Services

843

TIA/EIA/IS-2001

6.3.1

Call Processing Timers

6.3.1.1

T10

3
4
5

This MSC timer is started when the Assignment Request message is sent, and stopped
when the Assignment Complete message, or Assignment Failure message is received.
6.3.1.2

6
7
8
9

T20
This BS timer is started when the Assignment Failure message is sent, and stopped
when the Assignment Request message (retry) is received or when the MSC initiates
call clearing.

6.3.1.3

UNUSED SECTION

6.3.1.4

UNUSED SECTION

6.3.1.5

T300

10
11
12
13
14
15
16

This BS timer is started when a Clear Request message is sent. It is stopped when a
Clear Command message is received.
6.3.1.6

17
18
19

T301
This MSC timer is started when the Assignment Complete message is received, and
stopped when the Connect message is received (ring time-out, max. 60 seconds).

6.3.1.7

UNUSED SECTION

6.3.1.8

T303

20
21
22
23
24
25
26
27

BS timer T303 for MS origination is started when the CM Service Request message is
sent. For MS termination, the timer is started when the Paging Response message is
sent. In both cases, the timer is stopped when the Assignment Request message or a
Clear Command message is received, or the SCCP connection is refused or released by
the MSC.
6.3.1.9

28
29
30

T306
BS timer T306 is started when the Handoff Commenced message is sent and stopped
when the Clear Command message is received.

6.3.1.10

UNUSED SECTION

31

844

TIA/EIA/IS-2001

6.3.1.11

UNUSED SECTION

6.3.1.12

UNUSED SECTION

6.3.1.13

T311

2
3
4
5
6
7
8

This BS timer is started when the BS Service Request message is sent, and stopped
when the BS Service Response message is received.
6.3.1.14

UNUSED SECTION

6.3.1.15

UNUSED SECTION

6.3.1.16

T315

9
10
11
12
13
14
15

This MSC timer is started when the Clear Command message is sent, and stopped when
the Clear Complete message is received.
6.3.1.17

UNUSED SECTION

6.3.1.18

UNUSED SECTION

6.3.1.19

T3231

16
17
18
19
20
21
22
23

This MSC timer is started the SCCP Connection Request primitive is sent, and is
stopped when an SCCP Connection Confirm primitive or an SCCP Connection Refused
primitive is received.
6.3.1.20

T3113

24
25
26

This MSC timer is started when the Paging Request message or an ADDS Page
message is sent, and is stopped when the Page Response message or an ADDS Page
Ack message is received.

27
28

The value for this timer can be calculated for a MS in slotted mode by the following
formula:

29

T3113 = 4.72 + (1.28 * 2Slot Cycle Index )

30
31
32
33

6.3.1.21

T3230
This BS timer is started when any message contained in the Complete Layer 3
information message is sent, and is stopped when an SCCP Connection Confirm
primitive or an SCCP Connection Refused primitive is received.

845

TIA/EIA/IS-2001

6.3.1.22

2
3
4

T3280
This MSC timer is started when the Privacy Mode Command message is sent, and
stopped when the Privacy Mode Complete message is received.

6.3.1.23

5
6
7
8
9
10
11

Twaitho
This is a TIA/EIA-IS-2000 timer that is shown in this standard for descriptive purposes
only. It is started when the source BS sends a General Handoff Direction Message to
the MS with an indication that the MS is allowed to return to the source BS if it cannot
acquire the target BS. This timer is stopped if the source BS receives a Candidate
Frequency (CF) Search Report Message, or upon receipt of a Clear Command message
from the MSC. The source BS must wait until this timer expires (if the timer is started)
before sending the Handoff Commenced message to the MSC.

12
13
14
15
16
17

6.3.1.24

Trp
This is the A10 connection registration Lifetime timer. This timer is started at the time of
establishment of an A10 connection and updated during periodic re-registrations of the
A10 connection. The A10 connection is cleared on expiry of this timer. A Trp value of
FF FF H (two octets, all bits set to 1) indicates infinite Lifetime. A value of 00 00 H
(two octets, all bits set to 0) indicates that the A10 connection is to be released.

18

6.3.1.25

Tregreq

19
20
21
22
23

The PCF timer Tregreq is started when the Registration Request message is sent, and
stopped when the Registration Reply message is received.
6.3.1.26

Tregupd
The PDSN timer Tregupd is started when the Registration Update message is sent, and
stopped when the Registration Acknowledge message is received.

846

TIA/EIA/IS-2001

1
2

6.3.2

Supplementary Services Timers

6.3.2.1

UNUSED SECTION

6.3.2.2

UNUSED SECTION

6.3.2.3

T62

4
5
6
7
8
9
10

MSC timer T62 is started when the Flash with Information message is sent and stopped
when the Flash with Information Ack message is received.
6.3.2.4

T63

11
12

MSC timer T63 is started when the a Feature Notification message is sent containing a
Tag element and stopped when the Feature Notification Ack message is received.

13
14

The value for this timer can be calculated for a MS in slotted mode by the following
formula:

15

T63 = 4.72 + (1.28 * 2Slot Cycle Index )

847

TIA/EIA/IS-2001

6.3.3

Mobility Management Timers

6.3.3.1

T3210

3
4
5
6

This BS timer is started when the Location Updating Request message is sent, and is
stopped when a Location Updating Accept message, or a Location Updating Reject
message is received.
6.3.3.2

7
8

T3220
This BS timer is started when the Parameter Update Request message is sent, and is
stopped when the Parameter Update Confirm message is received.

9
10

6.3.3.3

UNUSED SECTION

6.3.3.4

T3260

11
12
13
14
15

This MSC timer is started when the Authentication Request message is sent, and is
stopped when the Authentication Response message is received.
6.3.3.5

16
17
18

This MSC timer is started when the SSD Update Request message is sent, and is
stopped when the Base Station Challenge message is received.
6.3.3.6

19
20
21

T3270

T3271
This MSC timer is started when the Base Station Challenge Response message is sent,
and is stopped when the SSD Update Response message is received.

6.3.3.7

UNUSED SECTION

22

848

TIA/EIA/IS-2001

6.3.4

Handoff Timers

6.3.4.1

T7

3
4
5
6
7
8
9
10
11
12

The source BS starts this timer when sending the Handoff Required message to the
MSC. If strength measurements are being performed, then the timer is started at the time
that the Strength Measurement Request message is sent to the MSC. Therefore, the
timer represents the time between successive handoff attempts for the same mobile
connection. It is recommended that this timer value be long enough to cover all
message exchanges with potential targets as well as the maximum time to transmit all
transmissions of the Handoff Command message (see T8), and handoff queuing time, if
supported. Timer T7 is stopped when a Handoff Command message or a Handoff
Required Reject message is received.
6.3.4.2

T8

13
14
15
16

The source BS starts this timer when sending the handoff instruction to the MS. It is
recommended that this timer value include all the time necessary to successfully
complete handoff execution (i.e., time to send all transmissions of a handoff instruction
plus the time to access the target or detect that the mobile has not left the source BS).

17
18

For further information and an explicit definition of this timer see the appropriate air
interface standard, e.g., TIA/EIA-IS-2000-A.

19

6.3.4.3

20
21
22
23
24

The target BS starts this timer when sending the Handoff Request Acknowledge
message to the MSC. It is stopped when the mobile station is acquired. It represents
the time to reserve the target channel while waiting for the mobile to arrive on the target
channel. This should be at least as long as T8.
6.3.4.4

25
26
27
28

T9

T11
This MSC timer is started when the Handoff Request message is send to the BS and is
stopped when the Handoff Request Acknowledge message is received or the SCCP
connection is refused or released by the BS.

6.3.4.5

UNUSED SECTION

6.3.4.6

UNUSED SECTION

6.3.4.7

UNUSED SECTION

6.3.4.8

UNUSED SECTION

6.3.4.9

UNUSED SECTION

29
30
31
32
33
34
35
36
37

849

TIA/EIA/IS-2001

6.3.4.10

UNUSED SECTION

6.3.4.11

UNUSED SECTION

2
3

850

TIA/EIA/IS-2001

1
2

6.3.5

Facility Management Timers

6.3.5.1

T1

4
5

The BS starts this timer when the Block or Unblock message is sent and stops it when
the Block Acknowledge or Unblock Acknowledge message is received.

6
7
8

The source BS/SDU starts this timer when the A3-Block or A3-Unblock message is sent
and stops it when the A3-Block Acknowledge or A3-Unblock Acknowledge message is
received.

6.3.5.2

T2

10
11
12

Timer T2 represents the Reset guard period in the MSC. To avoid a deadly embrace
situation during a BS triggered global reset procedure, timer T2 (MSC) should always be
less than timer T4 (BS).

13
14
15

Timer T2 also represents the A7-Reset guard period in the BSC that receives the A7Reset message. To avoid a deadly embrace situation during an A7-Reset procedure,
timer T2 (second BSC) should always be less than timer T4 (first BSC).

16

6.3.5.3

T4

17
18
19
20
21

The BS starts this timer when the Reset message is sent and stops it when the Reset
Acknowledge message is received. If timer T4 expires without receiving a Reset
Acknowledge message, the BS repeats the Reset procedure. To avoid a deadly
embrace situation during a BS triggered global reset procedure, timer T2 (MSC) should
always be less than timer T4 (BS).

22
23
24
25
26

The first BSC starts this timer when the A7-Reset message is sent and stops it when the
A7-Reset Acknowledge message is received. If timer T4 expires without receiving a A7Reset Acknowledge message, the first BSC repeats the A7-Reset procedure. To avoid a
deadly embrace situation during a first BSC triggered global reset procedure, timer T2
(second BSC) should always be less than timer T4 (first BSC).

27

6.3.5.4

UNUSED SECTION

6.3.5.5

UNUSED SECTION

28
29
30

851

TIA/EIA/IS-2001

6.3.5.6

2
3
4
5

This MSC or BS timer is started when a Reset Circuit message is sent and stopped when
a Reset Acknowledge message is received. At the MSC, this timer is also stopped
when a Block message is received from the BS.
6.3.5.7

6
7
8
9

6.3.5.8

T16
The MSC starts this timer when a Reset message is sent and stops it when a Reset
Acknowledge message is received. If timer T16 expires without receiving a Reset
Acknowledge message, the MSC repeats the Reset procedure. To avoid a deadly
embrace situation during a MSC triggered global reset procedure, timer T13 (BS)
should always be less than timer T16 (MSC).

6.3.5.9

16
17
18

T13
Timer T13 represents a Reset guard period at the BS. To avoid a deadly embrace
situation during a MSC triggered global reset procedure, timer T13 (BS) should always
be less than timer T16 (MSC).

10
11
12
13
14
15

T12

T309
The MSC starts this timer when the Transcoder Control Request message is sent, and
stops it when the Transcoder Control Acknowledge message is received.

6.3.5.10

UNUSED SECTION

852

TIA/EIA/IS-2001

1
2

6.3.6

Timers Used on the A3 and A7 Interfaces

6.3.6.1

Tbstact

4
5
6
7
8

The Tbstact timer is used by the source BS to wait for the A7-Burst Activate Ack
message A7-Burst Activate Ack. This timer is started when the A7-Burst Activate
message is sent and stopped when A7-Burst Activate Ack message has been received
by the source BS.
6.3.6.2

9
10
11
12

Tbstcom
The Tbstcom timer is used by the target BS to wait for the A7-Burst Activate message
from the source BS. This timer is started when the A7-Burst Response message is sent
and stopped when A7-Burst Activate message has been received.

6.3.6.3

UNUSED SECTION

6.3.6.4

UNUSED SECTION

6.3.6.5

UNUSED SECTION

13
14
15
16
17

853

TIA/EIA/IS-2001

6.3.6.6

UNUSED SECTION

6.3.6.7

UNUSED SECTION

6.3.6.8

Tconn3

2
3
4
5
6
7
8
9

The Tconn3 timer is used by the target BS to wait for the A3-Connect Ack message.
This timer is started when the A3-Connect message is sent and stopped when the A3Connect Ack message is received.
6.3.6.9

10
11
12
13

The Tdiscon3 timer is used by the target BS to wait for the A3-Remove Ack message.
This timer is started when the A3-Remove message is sent and stopped when the A3Remove Ack message is received.
6.3.6.10

14
15
16
17

6.3.6.11

6.3.6.12

32
33
34
35

Ttgtrmv
The Ttgtrmv timer is used by the target BS to wait for the A7-Target Removal Ack
message. This timer is started when the A7-Target Removal message is sent and
stopped when the A7-Target Removal Ack message is received.

6.3.6.13

26
27
28
29
30
31

Thoreq
The Thoreq timer is used by the source BS to wait for the A7-Handoff Request Ack
message. This timer is started when the A7-Handoff Request message is sent and
stopped when the A7-Handoff Request Ack message is received.

22
23
24
25

Tdrptgt
The Tdrptgt timer is used by the source BS to wait for the A7-Drop Target Ack
message. This timer is started when the A7-Drop Target message is sent and stopped
when the A7-Drop Target Ack message is received.

18
19
20
21

Tdiscon3

Tchanstat
The Tchanstat timer is used by the source BS/SDU to wait for the A3-Traffic Channel
Status messages for all new cells on an A3 connection. This timer is started when the
A3-Connect Ack message indicating that A3-Traffic Channel Status messages are
requested is sent and stopped when A3-Traffic Channel Status message(s) have been
received for all new cells on the A3 connection.

6.3.6.14

Tphysical
The Tphysical timer is used by the source BS/SDU to wait for the A3-Physical
Transition Directive Ack message for an A3 connection. This timer is started when the
A3-Physical Transition Directive message is sent and stopped when A3-Physical
Transition Directive Ack message has been received.

854

TIA/EIA/IS-2001

6.3.6.15

UNUSED SECTION

6.3.6.16

Tacm

2
3
4
5
6
7
8
9
10

This is a BS timer. The timer is started when an A7-Access Channel Message Transfer
message is sent and stopped when an A7-Access Channel Message Transfer Ack
message is received.
6.3.6.17

Tpcm
This is a BS timer. The timer is started when an A7-Paging Channel Message Transfer
message is sent and stopped when an A7-Paging Channel Message Transfer Ack
message is received.

855

TIA/EIA/IS-2001

1
2

6.3.7

Timers Used on the A9 Interface

6.3.7.1

TA8-setup

4
5
6

This is a BS timer. The timer is started when an A9-Setup-A8 message is sent and
stopped when an A9-Connect-A8 message is received.
6.3.7.2

7
8
9

This is a PCF timer. The timer is started when an A9-Disconnect-A8 message is sent
and stopped when an A9-Release A8message is received.
6.3.7.3

10
11
12

6.3.7.4

6.3.7.5

23
24

Twaitho9
This is a PCF timer. The timer is started when an A9-Connect-A8 message is sent and
stopped when an A9-AL Connected message is received. The value of this timer shall
be greater than that of the timer Twaitho.

6.3.7.6

20
21
22

Talc9
This is a BS timer. The timer is started when an A9-AL Connected message is sent and
stopped when an A9-AL Connected Ack message is received.

16
17
18
19

Trel9
This is a BS timer. The timer is started when an A9-Release-A8 message is sent and
stopped when an A9-Release-A8 Complete message is received.

13
14
15

Tdiscon9

Tbsreq9
This is a PCF timer. The timer is started when an A9-BS Service Request message is
sent and stopped when an A9-BS Service Response message is received.

6.3.7.7

Tald9
This is a BS timer. The timer is started when an A9-AL Disconnected message is sent
and stopped when an A9-AL Disconnected Ack message is received.

25

856

TIA/EIA/IS-2001

This informative annex contains brief descriptions and procedures for supplementary
services.

2
3

A.1

A.1.1

9
10
11
12
13

15
16
17
18
19
20
21

Feature Activation/Deactivation in Idle Mode

Feature activation/deactivation in idle mode is accomplished by the sending of a string
of digits and end marks (*, #) that identify the feature to be activated/deactivated, along
with any additional PIN information, etc. in a mobile origination. The MSC, after
doing digit analysis, determines that the request is for feature activation/deactivation.
After taking appropriate action (e.g., setting up a call and playing a tone or
announcement), the MSC or MS may initiate call clearing.

14

Feature Activation and Deactivation

The sections below indicate the procedures used to handle feature activation and
deactivation both when the MS is idle and is in a call.

Supplementary Services Annex

A.1.2

Feature Activation/Deactivation While in a Call

Feature activation/deactivation while in a call is accomplished by sending a string of
digits and end marks (*, #) that identify the feature to be activated/deactivated, along
with any additional PIN information, etc. in an air interface Flash with Information
message from the MS to the BS and in an MSC-BS Interface Flash with Information
message from the BS to the MSC. Any response by the MSC to the BS is via in-band
signals provided by the MSC. Such actions are treated as activities that are
independent of the Flash with Information messages going in the other direction.
time
MS

BS

comment

MSC

Flash with Information

a
Flash with Information
b

In-Band information

22
23
24

Figure A- 1 Feature Activation/Deactivation While in a Call

a.

The MS sends a Flash with Information message to the BS to pass a

string of digits and end marks to request feature activation/deactivation.

b.

The BS places the string of digits and end marks in a Flash with
Information message and sends it to the MSC.

c.

The MSC generates in-band tones or announcements.

25
26
27
28

857

TIA/EIA/IS-2001

A.2

Call Barring

A.2.1

Call Barring Incoming

No impact.

4
5
6
7
8
9

A.2.2

Call Barring Outgoing

Call Barring Outgoing requires the MSC to assign a channel to the originating mobile,
apply call treatment (e.g. announcement to mobile subscriber on the traffic channel)
and then clear the call after treatment has been applied. Note that the subscriber may
also initiate call clearing upon hearing the announcement or other appropriate
treatment (e.g., tones).

858

TIA/EIA/IS-2001

Time
MS

BS

MSC

Origination Message
a
Base Station Ack Order
b
Complete L3 Info: CM Service Request
c
T3230
SCCP Connection
d
e

T303

f
Assignment Request
g
Channel Assignment Message
h
T10

Tch Preamble

i
Base Station Acknowledgement Order
j
Mobile Station Acknowledgement Order
k
Service Connect Message
l
Assignment Complete
m

Switch determines call

Clear Command
should be blocked,
applies treatment
T315
Clear Complete
(announcement).
Initiates MSC call
See IOS V3
clearing.
2.3.5.3 MSC
Call Clearing

n
o
p
q

2
3

Figure A- 2 TIA/EIA-95 Call Barring Outgoing

859

TIA/EIA/IS-2001

A.3

Calling Number ID Presentation / Restriction

The following subsections describe the support for:

Calling Number Identification Presentation (CNIP)

Calling Number Identification Restriction (CNIR)

A.3.1

CNIP/CNIR for Mobile Terminations

There are two types of CNIP/CNIR supported:

1.

If the mobile station is idle, for mobile terminated calls, the CNIP/CNIR
information is sent in the Assignment Request message.

2.

If the mobile station user subscribes to the Call Waiting (CW) feature and is
engaged in a call, the CNIP/CNIR information is sent in the Flash with
Information message.

8
9
10
11

The MSC will code the presentation restriction information as presentation allowed
when providing text, e.g., Unknown Number or Private Number, corresponding to
the cases when the number is not available or is presentation restricted. When the
screening indicator is not provided or can not be determined, a default value of
network provided is recommended.

12
13
14
15
16

17

A.3.2

For CNIR, the calling party can request CNIR on a per call basis by including the
feature code preceding the Called Party Number digits in the Called Party BCD
Number in the CM Service Request message.

18
19
20

21

A.4
A.6

25
26

A.7

30
31

Basic Remote Call Forwarding

This feature is transparent to the IOS interfaces.

28

29

Distinctive Ringing
The A1 interface uses the Signal element (see section 6.2.2.50) or the IS-95
Information Records element (see section 6.2.2.72) to carry information to the MS
concerning the specific ringing pattern to be used.

24

27

Voice Answering
Transparent to the IOS interfaces

22

23

CNIR on Mobile Originated Calls

A.8

Emergency service
Emergency calls are setup as normal calls with specific dialed digits (e.g. 911) as the
called party number.

860

TIA/EIA/IS-2001

A.9

See section 4.1.2.

A.10
A.11

7
8

A.12
A.13

13Kbps Voice Service

Supported by this standard.

12

13

Authorized Roaming
This feature is transparent to the IOS interfaces.

10

11

Carrier Access
This feature uses carrier access codes as prefixes to the called party number to set up
an origination call. It is supported transparently by the IOS interfaces (IOS allows up
to a total of 32 digits in the origination messages).

Hotlining
This feature is transparent to the IOS interface.

Autonomous Registration

A.14

Call Forwarding

A.14.1

Call Forwarding Unconditional (CFU) IS53A 5.5

14

15
16

1.

Feature activation: Feature codes are sent in the Called Party BCD Number
parameter of the CM Service Request message (see section 2.5.5.0 for the
supporting procedures and section 2.5.1.1 for message descriptions) when
subscriber initiates actions (eg. to activate or deactivate Call Forwarding.).

2.

Feature operation - Incoming calls are forwarded by the MSC; this is transparent
to the IOS interfaces.

17
18
19
20
21

22

A.14.2

Call Forwarding When Busy (CFB) IS53A 5.2

Transparent to IOS interfaces.

23

25

Call Forwarding When No Answer or Not Available (CFNA)

IS53A 5.4

26

Same as Call Forwarding Unconditional (CFU).

24

27
28

A.14.3

A.14.4

Call Forwarding of Call Waiting IS53A 5.2.4

This feature is transparent to the IOS interfaces.

861

TIA/EIA/IS-2001

A.15

This feature is transparent to the MSC-BS Interfaces.

Call Delivery

A.16

Lawfully Authorized Wiretap

Location support for wiretap is not required, however, location of the wiretap subject
may be provided using the most recent Cell ID parameter provided to the MSC via one
of the following messages:

1.

CM Service Request (see section 2.2.1.1)

2.

Page Response (See section 2.2.2.2)

3.

Handoff Request Ack (See section 3.3.2.3.2)

10

4.

Handoff Performed Message (See section 3.3.3.1)

11

5.

ADDS Page Ack (See section 2.7.2.3)

12

6.

ADD Transfer (See section 2.7.2.2)

4
5

13

A.17

For E911 phase 1, the CM service request provides the location of the E911 MS and
also provides the MSID (IMSI) of the MS to be used for the callback number.

14
15

For E911 phase 2, this standard supports delivery of the mobile location from the
network to a Position Determining Entity (PDE) on the Base Station to Switch
interface. Procedures and protocols used on the interface between the PDE and other
Network Entities are outside the scope of this standard. Further this standard assumes
that all involved elements (i.e. mobile station, Base Station, MSC and PDE) conform to
TIA/EIA IS-801. The PDE can either be supported at the Base Station or centrally at
the MSC, but the information is always transferred to the MSC.

16
17
18
19
20
21
22

Call back feature is transparently supported by the normal call establishment

procedures.

23
24

25

A.18

27
28
29

A.19

Advice of Charge
This feature is supported transparently to the A-Interface signaling.

31

32

Answer Holding
This feature is supported transparently to the A-Interface signaling. The Flash with
Information message is used to invoke Answer Holding in the Alerting and Call
Waiting state. The Flash with Information message is also used to toggle between two
calls, one of which in Answer Holding state, while in Call Waiting state.

26

30

E911 phase I and phase 2

A.20

User Selective Call Forwarding

33

This feature is supported transparently to the A-Interface signaling.

34
35

Forward To Number registration is handled by regular Feature Activation procedures

as described in section.

36

Invocation is handled by using the Flash with Information message.

862

TIA/EIA/IS-2001

This informative annex contains descriptions of optional features.

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

Optional Features Annex

B.1

Source Transfer Notification

When building a network based on this specification, the network operator should be
aware that it is possible for a manufacturer to support a proprietary procedure referred
to as Source Transfer. Source Transfer is the procedure by which call control is
passed from one BS to a second BS such that the second BS becomes the source BS
in control of the call.
When the equipment from such a manufacturer includes more than one BSC,
proprietary source transfer operations from equipment connected to one BSC to
equipment connected to a second BSC may be visible to other base stations involved in
soft handoff as target BSs. This visibility takes the form of the reception of A7
messages across an A7 connection different than the A7 connection used to setup the
soft handoff with the target BS. For instance, a target BS could receive an A7-Handoff
Request message across a first A7 connection, and then receive an A7-Drop Target
message across a second A7 connection for the same call.
This specification provides a means of interoperability with equipment that supports
proprietary source transfer procedures that may be visible to target BSs. The decision
to be made by a network operator is whether the network configuration includes the
possibility of source transfer procedures being visible to other base stations. If only a
single BSC capable of source transfer procedures is included in the network, then this
optional feature is not required for the network. If multiple source transfer capable
BSCs are included in the network, then other base station manufacturers need to
determine whether or not the reception of A7 messages on an A7 connection different
than the connection used to setup the soft handoff is of concern to their equipment. If
their equipment requires that the manufacturers base station be notified that such
reception will occur, this specification provides a means of requesting such
notification.
The means of requesting the notification is to include the A7 Control element (section
6.2.2.97) on the A7-Handoff Request Ack message (sections 3.4.3.1.2 and 6.1.12.2).
The notification is the A7-Source Transfer Performed message (sections 3.4.3.1.10 and
6.1.12.10). The A7-Source Transfer Performed message is sent by the old source BSC
to the target BSC to inform the target BSC of the identity of the new source BSC in
control of the call as the result of a source transfer procedure.

863

TIA/EIA/IS-2001

These scenarios are not comprehensive and are for information only.

Call Diagrams => Support of EVRC

C.1

13K Requested 13K Granted (Origination)

4
5
6
7
8
9
10
11
12

In this scenario the mobile station is either 13K (8000h) only or is EVRC capable, but
programmed to prefer 13K (8000h). The BS is capable of 13K (8000h) only. When the
mobile station places a call, the 13K (8000h) service option will be sent to the base
station in the Origination message. The base station passes the 13K(8000h) service
option to the MSC in the CM Service Request message. The MSC will send an
Assignment Request message with the same service option that was received in the
CM Service Request message. The mobile will connect with a 13K (8000h) service
option. The Assignment Complete message will contain a 13K (8000h) service option.

13

MS
(13K only or
13K Preferred)

13K Only
BS

MSC

Origination ( SO=13K )

Base Station Ack Order

Complete L3 Info: CM Service Request

(SO=13K )
T303
Assignment Request ( SO=13K )

Channel Assignment Message

Tch Preamble
BS Ack Order
T10

MS Ack Order

Service Connect Message

Service Connect Completion

Assignment Complete ( SO=13K )

Ringback Tone

864

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10

C.2

13K (8000h) Requested EVRC Granted (Origination)

In this scenario the mobile station is capable of 13K (8000h) or EVRC, but the mobile
is programmed to prefer 13K (8000h). The BS is capable of 13K (8000h) or EVRC.
When the mobile station places a call, the 13K (8000h) service option will be sent to
the base station in the Origination message. The base station will pass the 13K (8000h)
service option in the CM Service Request message. The MSC will send an
Assignment Request message with the same service option that was received in the
CM Service Request message. The base station will negotiate with the mobile station
an EVRC service option. The base station will send the MSC an EVRC service option
to the MSC in the Assignment Complete message.

11
12

EVRC MS
(13K Preferred)

EVRC + 13K
BS

MSC

Origination ( SO=13K )

Base Station Ack Order

Complete L3 Info: CM Service Request

(SO=13K )
T303
Assignment Request ( SO=13K )

Channel Assignment Message

Tch Preamble
BS Ack Order
T10

MS Ack Order

Service Negotiation

Service Connect Message

Service Connect Completion
Assignment Complete (
Ringback Tone

13
14

865

SO=EVRC)

TIA/EIA/IS-2001

C.3

EVRC Requested EVRC Granted (Origination)

In this scenario the mobile station is capable of 13K (8000h) or EVRC, and the mobile
is programmed to prefer EVRC. The BS is capable of 13K (8000h) or EVRC. When
the mobile station places a call, the EVRC service option will be sent to the base
station in the Origination message. The base station will pass the EVRC service option
to the MSC in the CM Service Request message. The MSC will send an Assignment
Request message with the same service option that was received in the CM Service
Request message. The mobile will connect with an EVRC service option. The base
station will send the MSC an EVRC service option in the Assignment Complete
message.

2
3
4
5
6
7
8
9
10
11

EVRC MS
(EVRC
Preferred)

EVRC + 13K
BS

MSC

Origination ( SO=EVRC)

Base Station Ack Order

Complete L3 Info: CM Service Request

(SO=EVRC)
T303
Assignment Request ( SO=EVRC)

Channel Assignment Message

Tch Preamble
BS Ack Order
T10

MS Ack Order

Service Connect Message

Service Connect Completion

Assignment Complete ( SO=EVRC)

Ringback Tone

12

866

TIA/EIA/IS-2001

C.4

EVRC Requested 13K (8000h) Granted (Origination)

In this scenario the mobile station is capable of 13K (8000h) or EVRC, and the mobile
is programmed to prefer EVRC. The BS is capable of 13K (8000h) only. When the
mobile station places a call, the EVRC service option will be sent to the base station in
the Origination message. The base station will pass the EVRC service option to the
MSC in the CM Service Request message. The MSC will send an Assignment Request
message with the same service option that was received in the CM Service Request
message. The BS will then negotiate with the mobile station to a 13K (8000h) service
option. The base station will send the MSC a 13K (8000h) service option in the
Assignment Complete message.

2
3
4
5
6
7
8
9
10
11

EVRC MS
(EVRC
Preferred)

13K BS

MSC

Origination ( SO=EVRC )

Base Station Ack Order

Complete L3 Info: CM Service Request

(SO=EVRC )
T303
Assignment Request ( SO=EVRC )

Channel Assignment Message

Tch Preamble
BS Ack Order
T10

MS Ack Order
Service Negotiation

Service Connect Message

Service Connect Completion

Assignment Complete (
Ringback Tone

12

867

SO=13K)

TIA/EIA/IS-2001

C.5

13K (8000h) Requested 13K Granted (Origination)

In this scenario the mobile station is capable of 13K (8000h) only. The BS is capable
of 13K (8000h) or EVRC. When the mobile station places a call, the 13K (8000h)
service option will be sent to the base station in the Origination message. The base
station will pass the 13K (8000h) service option to the MSC in the CM Service
Request message. The MSC will send an Assignment Request message with the same
service option that was received in the CM Service Request message. The base station
will attempt to negotiate with the mobile station to an EVRC service option. The MS
will respond with a 13K option. The base station will send the MSC a 13K service
option in the Assignment Complete message.

2
3
4
5
6
7
8
9
10
11

13K MS

EVRC + 13K
BS

MSC

Origination ( SO=13K)
Base Station Ack Order

Complete L3 Info: CM Service Request

(SO=13K)
T303
Assignment Request ( SO=13K )

Channel Assignment Message

Tch Preamble
BS Ack Order
T10

MS Ack Order

Service Negotiation

Service Connect Message

Service Connect Completion
Assignment Complete ( SO=13K)
Ringback Tone

12
13

868

TIA/EIA/IS-2001

C.6

13K (8000h) or EVRC Paged 13K (8000h) Granted

(Termination)

In this scenario the mobile station is capable of 13K (8000h) only. The BS is capable
of 13K (8000h) or EVRC. The MSC can page the mobile station with either a 13K
(8000h) or EVRC service option specified in the Paging Request message. The base
station will page the mobile station with the service option received in Paging Request
message. The MS will respond with 13K (8000h) in the Page Response message. The
MSC will send an Assignment Request message with the same service option that was
received in the Paging Response message. The base station will attempt to negotiate
with the mobile station an EVRC service option. The MS will respond with a 13K
(8000h) service option. The base station will send the MSC a 13K (8000h) service
option in the Assignment Complete message.

3
4
5
6
7
8
9
10
11
12

13K MS

EVRC + 13K
BS

MSC

Paging Request (SO=13K or EVRC)

Page Message (SO=13K or EVRC)
T3113

Page Response Message

(SO=13K)
Base Station Ack Order

Complete L3 Info: Paging Response

(SO=13K)

T303
Channel Assignment Message

Assignment Request ( SO=13K)

Tch Preamble
BS Ack Order
MS Ack Order
T10
Service Negotiation

Service Connect Message

Service Connect Completion
Assignment Complete ( SO=13K)
Alert with Info
MS Ack Order
Connect Order

T301

BS Ack Order
Connect

13

869

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11

C.7

13K (8000h) Paged 13K Granted (Termination)

In this scenario the mobile station either is capable of 13K (8000h) or EVRC and the
mobile is programmed to prefer 13K (8000h), or the MS is 13K (8000h) capable only.
The BS is capable of 13K (8000h) only. When the MSC pages the mobile station, the
13K (8000h) service option will be sent in the Paging Request message. The base
station will page the mobile station with a 13K (8000h) service option. The MS will
respond with 13K (8000h) in the Page Response message. The MSC will send an
Assignment Request message with the same service option that was received in the
Paging Response message. The mobile will connect with a 13K (8000h) service option.
The base station will send the MSC a 13K service option in the Assignment Complete
message.
EVRC MS
(13K preferred)
or 13K MS only

MSC

13K BS

Paging Request (SO=13K)

Page Message ( SO=13K)
T3113

Page Response Message

(SO=13K)
Base Station Ack Order

Complete L3 Info: Paging Response

(SO=13K)

T303
Channel Assignment Message

Assignment Request ( SO=13K)

Tch Preamble
BS Ack Order
MS Ack Order
T10
Service Connect Message
Service Connect Completion

Assignment Complete ( SO=13K)

Alert with Info
MS Ack Order
Connect Order

T301

BS Ack Order
Connect

12

870

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11
12

C.8

13K (8000h) or EVRC Paged EVRC Granted

(Termination)
In this scenario the mobile station is capable of 13K (8000h) or EVRC and the mobile
is programmed to prefer 13K (8000h). The BS is capable of 13K (8000h) or EVRC.
The MSC can page the mobile station with either a 13K (8000h) or EVRC service
option specified in the Paging Request message. The base station will page the mobile
station with the service option received in Paging Request message. The MS will
respond with 13K (8000h) in the Page Response message. The MSC will send an
Assignment Request message with the same service option that was received in the
Paging Response message. The base station will attempt to negotiate with the mobile
station an EVRC service option. The base station will send the MSC an EVRC service
option in the Assignment Complete message.

EVRC MS
(13K preferred)

EVRC + 13K
BS

MSC

Paging Request ( SO=13K or EVRC)

Page Message ( SO=13K or EVRC)
T3113

Page Response Message

(SO=13K)
Base Station Ack Order

Complete L3 Info: Paging Response

(SO=13K)

T303
Assignment Request ( SO=13K)

Channel Assignment Message

Tch Preamble
BS Ack Order
MS Ack Order

T10
Service Negotiation

Service Connect Message

Service Connect Completion
Assignment Complete ( SO=EVRC)
Alert with Info
MS Ack Order
Connect Order

T301

BS Ack Order
Connect

871

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9

C.9

EVRC Paged EVRC Granted (Termination)

In this scenario the mobile station is capable of 13K (8000h) or EVRC. The BS is
capable of 13K (8000h) or EVRC. When the MSC pages the mobile station, the
EVRC service option will be sent in the Paging Request message. The base station
will page the mobile station with an EVRC service option. The MSC will send an
Assignment Request message with the same service option that was received in the
Page Response message. The mobile will connect with an EVRC service option. The
base station will send the MSC an EVRC service option in the Assignment Complete
message.

10

EVRC +
13K MS

EVRC + 13K
BS

MSC

Paging Request (SO=EVRC)

Page Message (SO=EVRC)
T3113

Page Response Message

(SO=EVRC)

Complete L3 Info: Paging Response

(SO=EVRC)

Base Station Ack Order

T303
Channel Assignment Message

Assignment Request (SO=EVRC)

Tch Preamble
BS Ack Order
MS Ack Order
T10
Service Connect Message
Service Connect Completion

Assignment Complete S
( O=EVRC)
Alert with Info
MS Ack Order
Connect Order

T301

BS Ack Order
Connect

11

872

TIA/EIA/IS-2001

1
2
3
4
5
6
7
8
9
10
11

C.10

EVRC Paged 13K (8000h) Granted (Termination)

In this scenario the mobile station is capable of 13K (8000h) or EVRC. The BS is
capable of 13K (8000h) only. The MSC pages the mobile station with an EVRC
service option specified in the Paging Request message. The base station will page the
mobile station with the service option received in Paging Request message. The MS
will respond with EVRC service option in the Page Response message. The MSC will
send an Assignment Request message with the same service option that was received
in the Paging Response message. The base station will attempt to negotiate with the
mobile station a 13K (8000h) service option. The MS will respond with a 13K (8000h)
service option. The base station will send the MSC a 13K (8000h) service option in the
Assignment Complete message.

12

EVRC
MS

MSC

13K BS

Paging Request (SO=EVRC)

Page Message(SO=EVRC)
T3113

Page Response Message

(SO=EVRC)

Complete L3 Info: Paging Response

(SO=EVRC)

Base Station Ack Order

T303
Channel Assignment Message

Assignment Request (SO=EVRC)

Tch Preamble
BS Ack Order
MS Ack Order
T10
Service Negotiation

Service Connect Message

Service Connect Completion
Assignment Complete (SO=13K)
Alert with Info
MS Ack Order
Connect Order

T301

BS Ack Order
Connect

13

873

TIA/EIA/IS-2001

C.11

Service Option Change From EVRC to 13K

In this scenario the mobile station is setup with EVRC but is changed to 13K during
hard handoff. The target BS is capable of 13K (8000H) only. The source BS include a
13K service option in the Handoff Required message sent to the MSC because the
target BS is not capable of EVRC. The action time is the same in both Service
Connect and Extended Handoff Direction Messages. This scenario only applies to IS95A. mobiles. For IS-95B mobiles service option is allowed in the Extended Handoff
Direction Message and a separate Service Connect Message is not required. It is
assumed that the TIA/EIA-95A call is not in inter-BS soft/softer handoff prior to the
hard handoff, and thus no A3 connections need to be removed.

2
3
4
5
6
7
8
9
10
11

MS

Source BS

MSC

Target BS

Handoff Required (SO=13K)

Handoff Request (SO=13K)

T7

Null forward traffic channel frames

Service Connect Message
Handoff Command
(SO=13K,action time=?)
Extended/General Handoff Direction Message
(action time=?)
T8
MS Ack Order
Twaitho

Handoff Request Ack

T9

x Handoff Commenced
Reverse Traffic Channel Frames or Traffic Channel Preamble
Handoff Completion Message
Service Connect Completion Message

BS Ack Order
Handoff Complete

T306
Clear Command
Clear Complete
12
13

874

T315

TIA/EIA/IS-2001

3
4
5
6
7
8
9
10
11

C.12

Service Option Change From 13K to EVRC

In this scenario the mobile station is setup with 13K but is changed to EVRC during
hard handoff. The target BS is capable of EVRC (8000H) only. The source BS include
an EVRC service option in the Handoff Required message sent to the MSC because the
target BS is not capable of 13K. The action time is the same in both Service Connect
and Extended Handoff Direction Messages. This scenario only applies to IS-95A.
mobiles. For IS-95B mobiles service option is allowed in the Extended Handoff
Direction Message and a separate Service Connect Message is not required. It is
assumed that the TIA/EIA-95A call is not in inter-BS soft/softer handoff prior to the
hard handoff, and thus no A3 connections need to be removed.

12

MS

Source BS

MSC

Target BS

Handoff Required (SO=EVRC)

Handoff Request (SO=EVRC)
T7
Null forward traffic channel frames
Service Connect Message
Handoff Command
(SO=EVRC,action time=?)
Extended/General Handoff Direction Message
(action time=?)
T8
MS Ack Order
Twaitho

Handoff Request Ack

T9

x Handoff Commenced
Reverse Traffic Channel Frames or Traffic Channel Preamble
Handoff Completion Message
Service Connect Completion Message

BS Ack Order
Handoff Complete

T306
Clear Command
Clear Complete
13
14
15

875

T315