A.S0003-Av2.0 TIA-828-A Abis Published PDF

BTS-BSC Inter-operability (Abis Interface)
A.S0003-Av2.0
(to be published as TIA/EIA-828-A)
3GPP2 A.S0003-A
Version 2.0
Date: July 2001
1
2
3
4
5
6
7
8
9
10

(Post SDO Ballot, Pre-SDO Publication)
11
12
13
14
15
16
17
18
19
20
21
3GPP2 2001
22
23
3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners
24
may copyright and issue documents or standards publications in individual Organizational Partner's name
25
based on this document.
26
Secretariat at secretariat@3gpp2.org.
27
should be directed to that Organizational Partner.
28
Requests for reproduction of this document should be directed to the 3GPP2

Requests to reproduce individual Organizational Partner's documents
See www.3gpp2.org for more information.
A.S0003-Av2.0
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
Table of Contents
1.
2.
Introduction............................................................................................................................................ 2
Objectives................................................................................................................................................ 2
2.1 Scope of the document ......................................................................................................................... 2
2.2 References ............................................................................................................................................ 2
2.2.1
Telecommunications Industry Association (TIA) / Electronics Industry Association (EIA)........... 3
2.2.2
Standards Committee T1................................................................................................................ 3
2.2.3
International Telecommunications Union - Telecommunications Sector (ITU-T) ......................... 3
2.2.4
Other ............................................................................................................................................. 3
3.
Terminology ............................................................................................................................................ 4
3.1 Acronyms ............................................................................................................................................. 4
3.2 Others ................................................................................................................................................... 5
4.
Network Reference Model and Interfaces............................................................................................ 6
4.1 Support of user traffic connections to a frame selector function .......................................................... 9
4.2 Support of paging channel messaging .................................................................................................. 9
4.3 Support of Access channel messaging ................................................................................................ 10
4.4 Support of broadcast system information functions ........................................................................... 10
4.5 Layers 1 & 2 ....................................................................................................................................... 10
4.5.1
Physical Layer Specification (Layer 1) ....................................................................................... 10
4.5.2
Use of ATM (Layer 2) .................................................................................................................. 10
4.5.3
Field of Application..................................................................................................................... 10
4.5.4
ATM Layer................................................................................................................................... 11
4.5.5
ATM Adaptation Layer ................................................................................................................ 11
4.5.6
Network and Transport Protocols ............................................................................................... 11
5.
Call Processing ..................................................................................................................................... 16
5.1 Mobile Originating Call ..................................................................................................................... 16
5.1.1
Abis-ACH Message Transfer ....................................................................................................... 16
5.1.2
Unused Section............................................................................................................................ 17
5.1.3
Abis-BTS Setup............................................................................................................................ 17
5.1.4
Abis-Connect ............................................................................................................................... 17
5.1.5
Abis-Connect Ack ........................................................................................................................ 17
5.1.6
Abis-BTS Setup Ack ..................................................................................................................... 18
5.1.7
Abis-IS-2000 FCH Forward........................................................................................................ 18
5.1.8
Abis-IS-2000 FCH Reverse ......................................................................................................... 19
5.1.9
Abis-PCH Msg Transfer .............................................................................................................. 19
5.1.10
Abis-PCH Msg Transfer Ack.................................................................................................... 20
5.1.11
Abis-Traffic Channel Status ..................................................................................................... 20
5.1.12
Successful Mobile Originating Call......................................................................................... 21
5.2 Mobile Terminated Call...................................................................................................................... 25
5.2.1
Abis-PCH Message Transfer ....................................................................................................... 25
5.2.2
Abis-PCH Message Transfer Ack ................................................................................................ 25
5.2.3
Abis-BTS Setup............................................................................................................................ 25
5.2.4
Abis-Connect ............................................................................................................................... 25
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
A.S0003-Av2.0
Abis-Connect Ack ........................................................................................................................ 25

5.2.5
5.2.6
Abis-BTS Setup Ack ..................................................................................................................... 26
5.2.7
Abis-IS-2000 FCH Forward........................................................................................................ 26
5.2.8
Abis-IS-2000 FCH Reverse ......................................................................................................... 26
5.2.9
Abis-ACH Message Transfer ....................................................................................................... 26
5.2.10
Unused section......................................................................................................................... 26
5.2.11
Abis-Traffic Channel Status ..................................................................................................... 26
5.2.12
Successful Mobile Terminated Call.......................................................................................... 27
5.3 Call Clearing....................................................................................................................................... 31
5.3.1
Call Clearing initiated by MS...................................................................................................... 31
5.3.2
Call Clearing initiated by BS/MSC ............................................................................................. 35
5.3.3
Call Clearing initiated by BTS .................................................................................................... 38
5.3.4
Call Clearing initiated by MS...................................................................................................... 41
5.3.5
Call Clearing initiated by BSC/MSC........................................................................................... 43
5.3.6
Call Clearing initiated by BTS .................................................................................................... 45
5.4 Handoff............................................................................................................................................... 47
5.4.1
Abis-BTS Interface Procedures and Messages ............................................................................ 47
5.4.2
Soft/Softer Handoff addition (Intra-BTS) .................................................................................... 54
5.4.3
Soft/Softer Handoff addition (Inter-BTS)..................................................................................... 56
5.4.4
Soft/Softer Handoff Removal (Inter-BTS) .................................................................................... 58
5.4.5
Hard Handoff (Inter-BTS) ........................................................................................................... 60
5.5 SMS Delivery ..................................................................................................................................... 63
5.5.1
SMS Delivery on the Paging channel.......................................................................................... 63
5.5.2
Call flow example for SMS Delivery on the Paging channel ...................................................... 65
5.5.3
SMS Delivery on the Access channel........................................................................................... 67
5.5.4
SMS Delivery on the Traffic channel to MS................................................................................. 70
5.5.5
SMS Delivery on the Traffic channel from MS ............................................................................ 71
5.6 Traffic Burst Operation....................................................................................................................... 72
5.6.1
Abis-Burst Request ...................................................................................................................... 72
5.6.2
Abis-Burst Response.................................................................................................................... 72
5.6.3
Abis-Burst Commit ...................................................................................................................... 73
5.6.4
High Speed Packet Data.............................................................................................................. 73
5.6.5
Initial Traffic Burst Example Abis Connection Not Yet Established ......................................... 75
5.6.6
Subsequent Traffic Burst Example............................................................................................... 78
5.7 PACA Service ..................................................................................................................................... 80
5.7.1
PACA Updating ........................................................................................................................... 80
5.7.2
Call flow example for PACA Updating........................................................................................ 81
6.
Abis Interface Message ........................................................................................................................ 82
6.1 Abis Interface Message Formats ........................................................................................................ 82
6.1.1
Message Body, Coding, and Ordering of Elements ..................................................................... 82
6.1.2
Message Processing Guidelines .................................................................................................. 84
6.1.3
Message Definition Guidelines.................................................................................................... 85
6.2 Abis interface messages...................................................................................................................... 86
ii
A.S0003-Av2.0
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
Abis-ACH Msg Transfer .............................................................................................................. 86

6.2.1
6.2.2
UNUSED SECTION .................................................................................................................... 89
6.2.3
Abis-PCH Msg Transfer .............................................................................................................. 89
6.2.4
Abis-PCH Msg Transfer Ack ....................................................................................................... 92
6.2.5
Abis-BTS Setup............................................................................................................................ 94
6.2.6
Abis-BTS Setup Ack ................................................................................................................... 101
6.2.7
Abis-BTS Release ...................................................................................................................... 105
6.2.8
Abis-BTS Release Ack................................................................................................................ 107
6.2.9
Abis-Burst Request .................................................................................................................... 108
6.2.10
Abis-Burst Response .............................................................................................................. 113
6.2.11
Abis-Burst Commit................................................................................................................. 117
6.2.12
Abis-Connect.......................................................................................................................... 122
6.2.13
Abis-Connect Ack................................................................................................................... 127
6.2.14
Abis-Remove .......................................................................................................................... 127
6.2.15
Abis-Remove Ack ................................................................................................................... 127
6.2.16
Abis-IS-2000 FCH Fwd ......................................................................................................... 127
6.2.17
Abis-IS-2000 FCH Rvs........................................................................................................... 127
6.2.18
Abis-Traffic Channel Status ................................................................................................... 127
6.2.19
Abis-BTS Release Request ..................................................................................................... 127
6.2.20
Abis-IS-2000 SCH Fwd.......................................................................................................... 129
6.2.21
Abis-IS-2000 SCH Rvs ........................................................................................................... 129
6.2.22
Abis-IS-2000 DCCH Fwd ...................................................................................................... 129
6.2.23
Abis-IS-2000 DCCH Rvs ....................................................................................................... 129
6.2.24
Abis-PACA Update................................................................................................................. 129
7.
Information Element Definitions ...................................................................................................... 131
7.1 Information Element Identifiers ....................................................................................................... 131
7.2 Message Type ................................................................................................................................... 133
7.3 Correlation ID................................................................................................................................... 134
7.4 Mobile Identity ................................................................................................................................. 134
7.5 Cell Identifier ................................................................................................................................... 134
7.6 Air Interface Message....................................................................................................................... 134
7.7 UNUSED SECTION ........................................................................................................................ 135
7.8 Layer 2 Ack Request/Results............................................................................................................ 135
7.9 Cause ................................................................................................................................................ 135
7.10
Call Connection Reference ........................................................................................................... 135
7.11
Band Class .................................................................................................................................... 135
7.12
Privacy Info................................................................................................................................... 135
7.13
Cell Identifier List......................................................................................................................... 135
7.14
SDU ID ......................................................................................................................................... 135
7.15
Physical Channel Info ................................................................................................................... 135
7.16
Cell Information Record ............................................................................................................... 136
7.17
Service Option .............................................................................................................................. 136
7.18
PACA Timestamp.......................................................................................................................... 136
iii
7.19
7.20
7.21
7.22
7.23
7.24
7.25
7.26
7.27
7.28
7.29
7.30
7.31
7.32
7.33
7.34
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
8.
8.1
8.2
8.3
8.4
8.5
8.6
8.7
8.8
A.S0003-Av2.0
Quality of Service Parameters....................................................................................................... 136

Abis Connect Information............................................................................................................. 136
Abis Originating ID ...................................................................................................................... 136
Abis Destination ID ...................................................................................................................... 137
Downlink Radio Environment ...................................................................................................... 137
CDMA Serving One Way Delay ................................................................................................... 137
Forward Burst Radio Info ............................................................................................................. 138
Reverse Burst Radio Info.............................................................................................................. 138
IS-2000 Forward Power Control Mode......................................................................................... 138
IS-2000 FPC Gain Ratio Info ....................................................................................................... 138
BTS L2 Termination ..................................................................................................................... 138
CDMA Target One Way Delay ..................................................................................................... 139
Walsh Code Assignment Reqest ................................................................................................... 139
PACA Order .................................................................................................................................. 139
Authentication Challenge Parameter (RAND).............................................................................. 140
Abis Ack Notify ............................................................................................................................ 141
Timer Definitions ............................................................................................................................... 142
Tconnb :Timer for Abis-Connect message ....................................................................................... 142
Tsetupb : Timer for Abis-BTS Setup message.................................................................................. 142
Tchanstatb : Timer for Abis-Traffic Channel Status message........................................................... 142
Tdisconb : Timer for Abis-Remove Ack message ............................................................................ 143
Tdrptgtb : Timer for Abis-BTS Release Ack message...................................................................... 143
Tbstreqb : Timer for Abis-Burst Response message......................................................................... 143
Tbstcomb : Timer for Abis-BTS Release Ack message.................................................................... 143
Trelreqb : Timer for Abis-BTS Release message.............................................................................. 143
26
27
iv
A.S0003-Av2.0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Table of Figures
FIGURE 4-1 REFERENCE MODEL ......................................................................................................... 6
FIGURE 4-2 RELATIONSHIP BETWEEN AIR INTERFACE AND ABIS INTERFACE (INTRA-BS MODEL) ...... 8
FIGURE 4.5.6.4.1-1 DELIMITING MESSAGES IN AN ABIS APPLICATION TCP BYTE STREAM .............. 14
FIGURE 5.1.12-1 MOBILE ORIGINATING CALL ................................................................................... 21
FIGURE 5.2.12-1 MOBILE TERMINATED CALL ................................................................................... 27
FIGURE 5.3.4-1 CALL CLEARING INITIATED BY MS ........................................................................... 41
FIGURE 5.3.5-1 CALL CLEARING INITIATED BY BSC/MSC ................................................................ 43
FIGURE 5.3.6-1 CALL CLEARING INITIATED BY BTS.......................................................................... 45
FIGURE 5.4.2-1 SOFT/SOFTER HANDOFF ADDITION (INTRA-BTS) ..................................................... 54
FIGURE 5.4.3-1 SOFT/SOFTER HANDOFF ADDITION (INTER-BTS) ..................................................... 56
FIGURE 5.4.4-1 SOFT/SOFTER HANDOFF REMOVAL (INTER-BTS) ..................................................... 58
FIGURE 5.4.5-1 HARD HANDOFF (INTER-BTS).................................................................................. 60
FIGURE 5.5.2-1 SMS DELIVERY ON THE PAGING CHANNEL .............................................................. 65
FIGURE 5.5.3.5-1 SMS DELIVERY ON THE ACCESS CHANNEL ........................................................... 69
FIGURE 5.5.4-1 SMS DELIVERY ON THE TRAFFIC CHANNEL TO MS ................................................. 70
FIGURE 5.5.5-1 SMS DELIVERY ON THE TRAFFIC CHANNEL FROM MS............................................. 71
FIGURE 5.6.5-1 INITIAL TRAFFIC BURST EXAMPLE ........................................................................... 75
FIGURE 5.6.6-1 SUBSEQUENT TRAFFIC BURST EXAMPLE ................................................................. 78
FIGURE 5.7.2-1 PACA UPDATING PROCEDURE .................................................................................. 81
22
23
Table of Tables
24
TABLE 4-1 LAYER 2 TERMINATION TYPE .............................................................................................. 6

TABLE 4-2 ABIS INTERFACE DESCRIPTION............................................................................................ 9
TABLE 6.1.1-1 ELEMENT FLOW DIRECTION INDICATION ............................................................... 82
TABLE 7.1-1 ABIS INFORMATION ELEMENT IDENTIFIERS SORTED BY IDENTIFIER VALUE ............... 131
TABLE 7.2-1 ABIS MESSAGE TYPE VALUES ...................................................................................... 133
TABLE 8-1 TIMER VALUES AND RANGE ............................................................................................ 142
25
26
27
28
29
30
31
1.
2
3
4
A.S0003-Av2.0
Introduction
This document is the specification for the Abis interface (between the Base Transceiver
System (BTS) and Base Station Controller (BSC) for IS-2000 system. The signaling
flows and these signals are described.
5
6
2.
Objectives
The Abis interface specification provides an open and inter-operable system.
2.1
10
11
Scope of the document

This specification defines the interface between BTS and BSC within the BS.
interface between BSs is specified in the TIA/EIA/IS-2001.
The
12
13
14
15
Following features are not specified in this version of the specification.

further study.
They are for
Operations, Administration, Maintenance, and Provisioning (OAM&P)*1
16
Abis Overload control
17
SMS-Broadcast
18
Inter BSC hard/soft handoff *2
19
Flood paging
20
21
22
*1 It is recommended that any OAM&P related information be aligned with the

TIA/EIA-828, Abis interface. .
23
*2 Inter BSC (BS) hard/soft handoff is supported in the TIA/EIA/IS-2001.
24
25
26
The functions supported in TIA/EIA/IS-2001 shall be supported implicitly for the Abis
interface and shall not modify the information transmitted on the radio channels.
27
The conditions for supporting Abis Interface features are equivalent to TIA/EIA/IS-2001.
28
29
2.2
References
30
A.S0003-Av2.0
1
2
Telecommunications Industry Association (TIA) / Electronics Industry

Association (EIA)
3
4
TIA/EIA/IS-2001; Inter-operability Specification (IOS) for CDMA 2000 Access Network

Interfaces (also referenced as 3GPP2 TSG-As A.S0001); December, 2000.
5
6
TIA/EIA/IS-95B; Mobile Station - Base Station Compatibility Standard for Dual-Mode

Wideband Spread Spectrum Cellular Systems; March, 1999
2.2.1
2.2.2
8
9
Standards Committee T1
ANSI T1.627 - 1993, B-ISDN - ATM Layer Functionality and Specification, 1993.
10
International Telecommunications Union - Telecommunications Sector

(ITU-T)
11
12
ITU-T Recommendation I.363.2, B-ISDN ATM Adaptation layer specification: Type 2

AAL; September, 1997.
13
14
ITU-T Recommendation I.363.5, B-ISDN ATM Adaptation Layer specification: Type 5

AAL; August, 1996.
15
16
ITU-T Recommendation I.366.1; Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2; June, 1998.
17
18
19
ITU-T Recommendation Q.2931, Broadband-Integrated Services Digital Network

(B-ISDN) Digital Subscriber Signalling No. 2 (DSS2) User-Network Interface Layer 3
Specification for Basic Call/Connection Control, 1995.
20
2.2.3
2.2.4
Other
21
Internet Engineering Task Force, RFC 791 - Internet Protocol (IP), 1981.
22
Internet Engineering Task Force, RFC 793 - Transmission Control Protocol (TCP), 1981.
23
24
25
3.
Terminology
3.1
Acronyms
A.S0003-Av2.0
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
The following is a list of acronyms that are used in this specification text.
AAL2
AAL5
ADDS
ANSI
ARFCN
ATM
BSC
BSMAP
BTS
CC
CCITT
CDMA
CID
CM
cUDP
FCH
IETF
IMSI
IOS
IP
ISDN
ISLP
ITU
kb
LAC
LSB
MAC
MIN
MS
MSB
MSC
OAM&P
OTD
PACA
ATM Adaptation Layer type 2

ATM Adaptation Layer type 5
Application Data Delivery Service
American National Standards Institute
Absolute Radio Frequency Channel Number
Asynchromous Transfer Mode
Base Station Controller
Base Station Management Application Part
Base Transceiver System
Conference Calling
International Telegraph and Telephone Consultative Committee (See ITU)
Code Division Multiple Access
Circuit IDentifier (used with reference to AAL2)
Connection Management
compressed IP/UDP
Fundamental Channel
Internet Engineering Task Force
International Mobile Subscriber Identity
Interoperability Specification
Internet Protocol
Integrated Services Digital Network
Intersystem Link Protocol
International Telecommunications Union
kilo bits
Location Area Code
Least Significant Bit
Medium Access Control
Mobile Identification Number
Mobile Station
Most Significant Bit
Mobile Switching Center
Operations, Administration, Maintenance, and Provisioning
Orthogonal Transmit Diversity
Priority Access and Channel Assignment
A.S0003-Av2.0
PATE
PCF
PCM
PN
PPP
PSPDN
PSTN
QoS
RAND
RFC
RLP
SCH
SCM
SCTP
SDU
SMS
SMS-MO
SMS-MT
SSCS
SSD
SSSAR
TCP
UDP
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
Packet Arrival Time Error

Packet Control Function
Pulse Code Modulation
Pilot Number
Point to Point Protocol
Packet Switched Public Data Network
Public Switched Telephone Network
Quality of Service
Random Variable
Request for Comment
Radio Link Protocol
Supplemental Channel
Service Connect Message
Stream Control Transmission Protocol
Selection/Distribution Unit function
Short Message Service
SMS Mobile Originated
SMS Mobile Terminated
Service Specific Convergence Sublayer
Shared Secret Data
Service Specific Segmentation and Reassembly
Transmission Control Protocol
User Datagram Protocol
24
25
26
27
28
3.2
Others
1) In this document the term cell is used to refer to a sector with in a cell.
2) The messages indicated with solid lines flow over the Abis interface and the messages
indicated with dashed lines flow over interfaces other than the Abis interface.
4.
A.S0003-Av2.0
Network Reference Model and Interfaces
2
3
Figure 4-1 shows the network reference model that is referred to in this specification.
BS
4
5
6
BSC
SDU Function
7
8
Abis Signaling
Abis Signaling
Abis Interface
10
Abis Traffic
Abis Traffic
11
BTS
12
CH element
BTS
CH element
13
14
15
16
a) Abis interface = Abis signaling + Abis traffic

b) A Selection Distribution Unit (SDU) function is located in the BSC
c) A channel element is located in the BTS
17
18
19
20
21
22
Notes:
The handoff procedure between BTSs within a BSC is defined in this document.
The handoff procedure between the BSs has been defined in TIA/EIA/IS-2001.
23
Figure 4-1 Reference Model
24
25
26
There are 2 architecture for the L2 terminations were considered. They are shown in the following Table
4-1.
27
L
L3
L
2
LAC
MAC
L1
28
29
r-csch(*1)
L3
Authentication
ARQ
Addressing
Utility
SAR
MAC
L1
f-csch(*2)
L3
Type A
Type B
BSC
ARQ
Addressing
Utility
SAR
MAC
L1
BSC
BTS
BTS
Table 4-1 Layer 2 termination type

(*1) r-csch (reverse common signaling logical channel)
30
This logical channel is applied for the case that MS sends message on the ACH and BTS replies on the PCH.
31
In r-csch, LAC sub-layer is composed by Authentication sub-layer, ARQ sub-layer, Addressing sub-layer, Utility
A.S0003-Av2.0
1
2
3
sub-layer and SAR sub-layer.

(*2) f-csch (forward common signaling logical channel)
This logical channel is applied for the case that BTS sends message on the PCH and MS replies on the ACH.
In f-csch, LAC sub-layer is composed ARQ sub-layer, Addressing sub-layer, Utility sub-layer and SAR sub-layer.
In this specification type A is introduced as architecture for initial phase.

type B for the next release.
However we are also introducing
7
8
9
10
11
12
In this release of the Abis specification L2 termination is mandatory to be supported by the BTS. To allow
for a migration to new architectures, a mechanism is provided on the Abis interface whereby the BTS can
specify if L2 termination function will be supported. If the BTS indicates that it does not support L2
termination, then the BSC shall support L2 termination. In this release of the Abis specification the BTS shall
specify to the BSC that it terminates L2 termination.
13
14
15
A.S0003-Av2.0
Figure 4-2 shows the relationship between logical air interface channels and Abis interface signal
Air Interface
MS
Abis traffic
BTS
FCH (f/r-dsch, f/r-dtch)
FCH (Abis-IS-2000 FCH Fwd/Rvs)
SCH (f/r-dtch)
SCH (Abis-IS-2000 SCH Fwd/Rvs)
DCCH (f/r-dsch, f/r-dtch)
BS
Abis Interface
BSC
DCCH (Abis-IS-2000 DCCH Fwd/Rvs)
Abis Signaling
ACH (Abis-ACH Msg Transfer)
ACH (r-csch)
PCH (Abis-PCH Msg Transfer)
PCH (f-csch)
Abis Signaling
OAM Signaling (FFS)
2
3
4
Note:This figure is informative. In this figure, some signals defined in the air interface are omitted for
clarity.
5
6
Figure 4-2 Relationship between Air interface and Abis interface (Intra-BS Model)
7
8
A.S0003-Av2.0
Table 4-2 summaries the details of the Abis interface
2
3
Table 4-2 Abis interface description

Abis function
Transaction
Abis connection - call setup

establish
- Handoff
(BSC invoke)
Abis connection - call release
- Handoff
release
(BSC invoke)
Abis connection
release
(BTS invoke)
PCH transfer
ACH transfer
SCH
transfer
and establish
- SCH setup
Abis Message
- Abis-BTS Setup
- Abis-BTS Setup Ack
- Abis-Connect
- Abis-Connect Ack
- Abis-BTS Release
- Abis-BTS Release Ack
- Abis-Remove
- Abis-Remove Ack
- Abis-BTS Release Request
- Abis-BTS Release
- Abis-BTS Release Ack
- Abis-Remove
- Abis-Remove Ack
- Abis-PCH Msg Transfer
- Abis-PCH Msg Transfer Ack
- Abis-ACH Msg Transfer
- Abis-Burst Request
- Abis-Burst Response
-Abis-Burst Commit
(A7/A3
message
related to Abis)
(A7-HO Req.)
(A7-HO Req. Ack)
(A3-Connect)
(A3-Connect Ack)
(A7-Drop)
(A7-Drop Ack)
(A3-Remove)
(A3-Remove Ack)
(A7-Tgt rm. req.)
(A7-Drop)
(A7-Drop Ack)
(A3-Remove)
(A3-Remove Ack)
(A7-PCH ...)
(A7-PCH ... Ack)
(A7-ACH ...)
(A7-Burst Req.)
(A7-Burst Rsp.)
(A7-Burst Commit)
4.1
6
7
8
9
10
11
12
13
14
15
Support of user traffic connections to a frame selector function

In a CDMA system, the user traffic (voice, data, etc.) of a Mobile Station (MS) may be
connected to the network using one or more connections from MS to BTS(s). If multiple
connections are used for a single flow of user information, the user traffic connection is
said to be in soft handoff. The first step within the network is to carry these multiple
connections back to a single point from which a selection is made of the best frame
received over the radio connections. This implies a connection from each involved BTS
back to a central point where frame selection occurs. This central point is referred to as
the SDU function.
4.2
Support of paging channel messaging
16
17
18
19
When an MS is to be sent a message on a paging channel, the BSC typically formats the
majority of the message and forwards it to the BTS along with various parameters
including the destined cell identifier. The ability to forward such a paging message from
the BSC to the BTS is part of the functionality of the Abis interface.
20
21
An additional requirement of a CDMA system is that such a message may also need to be
forwarded between BSCs to be transmitted on a BTS belonging to a BSC other than the
1
2
3
A.S0003-Av2.0
BSC that originally created the message. This requirement comes through support for
access handoff and other such IS-95 and IS-2000 features. The BSC to BSC signaling
interface to support such forwarding has been defined in the TIA/EIA/IS-2001.
4.3
Support of Access channel messaging
5
6
7
8
When an MS sends a message on an access channel, the BTS will forward that message
to the BSC along with various parameters including the identity of the cell and sector on
which the message was received, etc. The ability to forward such an access message from
BTS to the BSC is part of the functionality of the Abis interface.
9
10
11
12
13
An additional requirement of a CDMA system is that such a message may also need to be
forwarded between BSCs (i.e., to a BSC other than the one that owns the BTS that
originally received the message). This requirement comes through support for access
handoff and other such IS-95 and IS-2000 features. The BSC to BSC signaling interface
to support such forwarding has been defined in the TIA/EIA/IS-2001.
14
15
4.4
16
17
18
19
20
21
Support of broadcast system information functions

In a IS-95 or a IS-2000 system, each BTS broadcasts various pieces of system
information that the MS captures and uses during its interactions with the network. Much
of that system information may be administrated through OAM&P functions. A small
amount of such system information may be placed in BTS and OAM&P control of a BTS
for the same purposes.
4.5
Layers 1 & 2
22
23
4.5.1
24
25
26
27
28
29
The physical layer specification is flexible to deploy the various new technologies.
Vendors shall have flexibility in providing the latest technology. And operators shall
have flexibility in choosing from various options, including T1, E1, 10/100 base T, OC3,
OC12, etc.
4.5.2
30
31
32
33
34
35
36
Physical Layer Specification (Layer 1)
Use of ATM (Layer 2)

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.
4.5.3
Field of Application
Asynchronous Transfer Mode (ATM) is used to transport both signaling and user traffic
(voice/data).
10
A.S0003-Av2.0
4.5.4
ATM Layer
2
3
4
5
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.
6
7
8
9
For this specification only ATM permanent virtual circuits (PVCs) shall be required for
the Abis interface. These virtual circuits shall be configured through administrative
procedures and no special signaling interface procedures, e.g., ATM UNI (Q.2931), shall
be required.
10
4.5.5
ATM Adaptation Layer
11
12
To make use of the basic cell transfer capability of the ATM Transport Layer in specific
uses, various ATM Adaptation Layers (AALs) have been defined.
13
Within this standard, two AALs are used:
14
AAL51 - for the transfer of signaling, and
15
AAL22 - for the transfer of user traffic (voice/data) on Abis traffic sub-channels.
16
17
18
Both AAL5 and AAL2 are used without modification in this standard. The Service
Specific Segmentation and Re-assembly (SSSAR) sub-layer for AAL2, as specified in
ITU-T I.366.1, is used for segmentation and re-assembly of AAL2 SDUs.
19
20
21
In this version of this standard, the functionality of other sub-layers of AAL2 is not
supported. Specifically, Service Specific Transmission Error Detection (SSTED) and
Service Specific Assured Data Transfer (SSADT) are not included.
22
4.5.6
Network and Transport Protocols
4.5.6.1
Signaling Connection Transport Protocol Options
23
24
25
26
27
28
29
Signaling over the Abis interface requires a reliable transport protocol and appropriate
addressing and routing mechanisms to deliver messages from source to destination. The
Abis signaling 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 Abis interface include:
30
31
Abis Interface (signaling connection):
32
IOS Application
TCP
IOS Application
TCP
IOS Application
UDP
IOS Application
SCTP
1 AAL5 is described in ITU-T I.363.5, B-ISDN ATM Adaptation Layer Specification:
Type 5 AAL, August 1996.

2 AAL2 is described in ITU-T Recommendation I.363.2, B-ISDN ATM Adaptation Layer
Type 2 Specification, September 1997.

11
A.S0003-Av2.0
IP
AAL5
IP
Link Layer
IP
Link Layer
IP
Link Layer
ATM
Phys. Lyr.
Phys. Lyr.
Phys. Lyr.
Phys. Lyr.
(Note 1)
(Note 1)
(Note 1)
1
2
3
4
It is mandatory for operators and manufacturers to support ATM based link layer for
signaling over the Abis interface. The other signaling connection may support any of
the protocol stacks above and is left to the discretion of operators and vendors.
5
6
UDP may be used and limited to those cases when reliable delivery is not required : e.g.,
case when BSC sends general page message.
7
8
(Note 1) These protocol stacks shown in the table are examples.
4.5.6.2
User Traffic Connection Transport Protocol Options
10
11
12
13
The protocol stack options for transport of user traffic that are available to operators and
manufacturers include:
Abis Interface (user traffic sub-channel):
14
Abis Traffic
SSSAR
AAL2
ATM
Phys. Layer
Abis Traffic
UDP
IP
Link Layer
Phys. Layer
(Note 1)
Abis Traffic
cUDP
SSCS
AAL2
Abis Traffic
cUDP
PPPmux
Link Layer
ATM
Phys. Layer
(Note 1)
Phys. Layer
(Note 1)
15
16
17
18
It is mandatory for operators and manufacturers to support ATM based transport for user
traffic over the Abis interface. The other signaling connection may support any of the
protocol stacks above and is left to the discretion of operators and vendors.
19
20
(Note 1) These protocol stacks shown in the table are examples.
21
4.5.6.3
22
23
24
TCP Transport Protocol Usage

The standard TCP, as described in RFC 793, shall be used for establishing, using, and
clearing TCP connections.
4.5.6.4
General Use of TCP
25
26
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.
27
28
29
The TCP 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 as follows.
12
A.S0003-Av2.0
1
2
3
4
5
6
7
8
9
10
4.5.6.4.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 4.5.6.4.1-1:
13
A.S0003-Av2.0
1
7
Flag
Flag
Length
(MSB)
Length
(LSB)
First Octet of Abis Application Message
Second Octet of Abis Application Message
Third Octet of Abis Application Message
Msg
...
Last Octet of Abis Application Message
Flag
Flag
Length
(MSB)
Length
(LSB)
Msg
...
Last Octet of Abis Application Message
Flag
Flag
Length
(MSB)
Length
(LSB)
Msg

...
3
4
5
6
Figure 4.5.6.4.1-1 Delimiting Messages in an Abis Application TCP Byte Stream

4.5.6.4.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.
14
A.S0003-Av2.0
4.5.6.4.3
2
3
4
5
TCP Connection Release

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.
4.5.6.4.4
TCP Port Usage
The following TCP port values are reserved for signaling across Abis interfaces:
7
8
Abis: 5604 -- This is the well-known TCP port at a BS used for Abis signaling
interconnection between BTSs and a BSC.
9
10
4.5.6.5
11
12
13
14
15
Use of TCP for the Abis Interface

The standard "Transport Control Protocol (TCP)", as described in RFC 793 and shown in
TIA/EIA/IS-2001 section 5.4.1.
4.5.6.6
IP Network Protocol Usage

The standard IP protocol, as defined in RFC 791 (see TIA/EIA/IS-2001 section 1.5.4),
shall be used for routing Internet Protocol packets.
16
15
A.S0003-Av2.0
5.
Call Processing
5.1
Mobile Originating Call
3
4
5
The following subsections describe the procedure for establishing a call through a mobile
originating action.
Mobile originating call setup involves exchange of the following BSC-BTS messages:
Abis-ACH Msg Transfer
8
9
Abis-BTS Setup
10
Abis-Connect
11
Abis-Connect Ack
12
Abis-BTS Setup Ack
13
Abis-IS-2000 FCH Fwd
14
Abis-IS-2000 FCH Rvs
15
Abis-PCH Msg Transfer
16
Abis-PCH Msg Transfer Ack
17
Abis-Traffic Channel Status
18
19
5.1.1
20
21
22
Abis-ACH Message Transfer

The Abis-Access Channel(ACH) Message Transfer is sent by the BTS to the BSC to
notify the BSC of the reception of an access channel message.
5.1.1.1
23
24
25
Successful Operation
When the BTS receives an access channel message, it shall encapsulate that message in
the Abis-ACH Msg Transfer, forward it to the BSC. The BTS may be responsible for
sending the Data Burst message for such forwarded access channel message.
26
27
28
29
30
Please refer to section 6.2.1, Abis-ACH Msg Transfer, for the format and content of
this message.
5.1.1.2
Failure Operation
None.
31
16
A.S0003-Av2.0
5.1.2
Unused Section
5.1.3
Abis-BTS Setup
2
3
4
5
6
The Abis-BTS Setup message is used by the BSC to request that the BTS allocate
resources in one or more cells for support of a call association.
5.1.3.1
7
8
9
When the BSC decides that one or more cells at the BTS are needed to support one or
more physical channel connections for a call, the BSC sends an Abis-BTS Setup message
to the BTS to indicate the resources required. The BSC then starts timer Tsetupb.
10
11
12
Please refer to section 6.2.5, Abis-BTS Setup, for the format and content of this
message.
5.1.3.2
13
Failure Operation
If timer Tsetupb expires, the BSC may choose to resend the Abis-BTS Setup message.
14
15
5.1.4
16
17
18
Abis-Connect
The Abis-Connect message is sent from the BTS to the BSC to initiate to one or more
Abis traffic connection. The Abis-Connect Ack message is expected in response.
5.1.4.1
19
20
21
22
Upon receiving the Abis Signaling Address information, the BTS begins the process of
establishing the Abis signaling connection with the BSC. The Abis Signaling Address is
used by the BTS to allocate a logical circuit to be used for Abis signaling. The SDU ID
identifies the particular instance of the SDU function.
23
24
25
26
27
Following the establishment of the Abis signaling link, the Abis-Connect message is sent
from the BTS to the BSC. The BTS expects an Abis-Connect Ack message indicating the
result of processing the Abis-Connect message and starts timer Tconnb. When the Abis
traffic connection(s) is established, traffic packets are exchanged to verify that the two
entities can communicate via the Abis traffic connection(s).
28
29
Please refer to section 6.2.12, Abis-Connect, for the format and content of this
message.
30
5.1.4.2
31
Failure Operation
If timer Tconnb expires, the BTS may choose to resend the Abis-Connect message.
32
33
34
35
5.1.5
Abis-Connect Ack
The Abis-Connect Ack message is sent from the BSC to the BTS to indicate the result of
processing the Abis-Connect message.
17
5.1.5.1
A.S0003-Av2.0
2
3
After processing the Abis-Connect message from the BTS, the BSC will indicate
success/failure to the BTS by sending an Abis-Connect Ack message.
4
5
6
7
If the Abis-Connect Ack message indicates that Abis-Traffic Channel Status message are
to be sent, then the BSC starts timer Tchanstatb to await Abis-Traffic Channel Status
message(s) for all new cells on each Abis connection. One instance of this timer is started
for each Abis connection to which one or more cells are being added.
8
9
Please refer to section 6.2.13, Abis-Connect Ack, for the format and content of this
message.
10
5.1.5.2
11
12
13
14
15
Failure Operation
If an instance of timer Tchanstatb expires, the BSC may assume that a failure has
occurred at the BTS during activation of the transmitter(s)/receiver(s) and delete the
unreported cells from the active set attached to the Abis connection. The BSC may then
send an Abis-BTS Release message to the BTS to cleanly remove those cells from the
Abis connection.
16
17
5.1.6
18
19
20
21
Abis-BTS Setup Ack

The Abis-BTS Setup Ack message is used by the BTS to respond to a request that it
allocates resources in one or more cells for support of one or more physical channel
connections for a call association.
5.1.6.1
22
23
24
25
When the BTS receives an Abis-BTS Setup 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 Abis-Connect Ack message(s) has been
received, the BTS responds by sending an Abis-BTS Setup Ack message to the BSC.
26
27
Please refer to section 6.2.6, Abis-BTS Setup Ack, for the format and content of this
message.
28
5.1.6.2
29
Failure Operation
None.
30
31
5.1.7
32
33
34
35
36
37
Abis-IS-2000 FCH Forward

This message is sent from the BSC to the BTS on the Abis traffic subchannel connection
of type IS-2000 FCH (TIA/EIA/IS-2000 Fundamental Channel). It contains the
Forward air-frame for the served MS along with control information for the BTS.
5.1.7.1
This message is sent from the BSC to the BTS on Abis traffic subchannel connections of
type FCH (Fundamental Channel). FCH messages are sent once every 20ms.
18
A.S0003-Av2.0
1
2
3
Please refer to section 6.2.16, Abis-IS-2000 FCH Fwd, for the format and content of
this message.
5.1.7.2
Failure Operation
None.
5
6
5.1.8
7
8
9
10
11
Abis-IS-2000 FCH Reverse

This message is sent from the BTS to the BSC on Abis 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.
5.1.8.1
12
13
14
This message is sent to the BSC on the Abis traffic subchannel connections of type
IS-2000 FCH (TIA/EIA/IS-200 Fundamental Channel) following the decoding of the
Reverse Traffic Channel frame. IS-2000 frames are sent once every 20ms.
15
16
Please refer to section 6.2.17, Abis-IS-2000 FCH Rvs, for the format and content of
this message.
17
5.1.8.2
18
Failure Operation
None.
19
20
5.1.9
21
22

The Abis-Paging Channel (PCH) Msg Transfer is sent by the BSC to request that a
particular message is sent on the specified paging channel(s).
23
24
5.1.9.1
25
26
27
When the BSC wishes to send a message to the mobile station on the paging channel(s) of
the BTS, it encapsulates that message in an Abis-(PCH) Msg Transfer and sends it to the
BTS.
28
29
30
A Layer 2 acknowledgment indication can be requested. If such an acknowledgment is

received from the MS, an Abis-Paging Channel Message Transfer ACK message is used
to convey that information back to the BSC
31
32
Please refer to section 6.2.3, Abis-PCH Msg Transfer for the format and content of this
message.
33
34
5.1.9.2
Failure Operation
None.
35
19
5.1.10
2
3
4
A.S0003-Av2.0

The Abis-PCH Msg Transfer Ack is used to respond to a request for a Layer 2
acknowledgment included in an Abis-PCH Msg Transfer.
5.1.10.1
5
6
7
When the BTS receives the Abis-PCH Msg Transfer including Abis Ack Notify IE, the
BTS sends the Abis-PCH Msg Transfer Ack upon receipt of the Layer 2
acknowledgment.
8
9
Please refer to section 6.2.4, Abis-PCH Msg Transfer Ack for the format and content of
this message.
10
5.1.10.2
11
Failure Operation
None.
12
13
5.1.11
14
15
16
17
18

The Abis-Traffic Channel Status message is used by the BTS to notify the BSC 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
Abis-Connect Ack message indicates that it is requested.
5.1.11.1
19
20
When the BTS needs to notify the BSC of a status change relative to a specific set of cells
on one Abis connection, it sends an Abis-Traffic Channel Status message.
21
22
23
24
25
26
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 Abis-Connect Ack message, the BTS does
not need to send this message if the transmitters(s)/receiver(s) are not turned on at the
BTS (i.e., the radio transmission on the forward link has not begun for the indicated
cells).
27
28
29
30
Multiple instances of this message may be sent relative to a single Abis connection if, for
instance, transmitter(s)/receiver(s) are activated at different times; however, all cells
referenced within a single instance of this message shall be attached to the same Abis
connection.
31
32
33
The BSC stops the instance of timer Tchanstatb for that Abis connection when
Abis-Traffic Channel Status message(s) have been received containing references to all
cells added to the Abis connection by the Abis-Connect message.
34
35
Please refer to section 6.2.18, Abis-Traffic Channel Status, for the format and content
of this message.
36
37
38
5.1.11.2
Failure Operation
None.
39
20
A.S0003-Av2.0
5.1.12
Successful Mobile Originating Call
2
3
This section describes the call flow associated with an MS call origination in the IS-2000
system.
Time Comment
BS
BTS
MS
Origination
BSC
MSC
Abis-ACH Msg. Transfer (ORM)

a
BS Ack Order
Abis-PCH Msg Transfer (BS Ack Order)
b
Complete L3 Info: CM Service Req.
c
T303
Assignment Request
Abis-BTS Setup
e
Tsetupb
Abis-Connect
Tconnb
Abis-Connect Ack
g
Abis-BTS Setup Ack
Null Traffic
Extended
Channel Assignment
Abis-IS-2000 FCH Fwd (Null Data)
Abis-IS-2000 FCH Rvs (Idle)
Abis-PCH Msg. Transfer (ECAM)

k
T10
Traffic Channel Preamble
BS Ack Order
Abis-IS-2000 FCH Rvs (T-CH Preamble)

Abis-IS-2000 FCH Fwd (BS Ack Order)
Idle Tch Data Frames

MS Ack Order
Abis-IS-2000 FCH Rvs (MS Ack Order)
Service Connect
Service Connect Completion
Abis-IS-2000 FCH Fwd (SCM)
Abis-IS-2000 FCH Rvs (SCCM)
q
Assignment Complete
Figure 5.1.12-1 Mobile Originating Call
5
6
7
8
9
10
a.
The MS transmits an Origination Message, with layer 2

acknowledgement required, over the access channel of the air
interface to the BTS. Then the BTS sends an Abis-ACH Msg
Transfer including the Origination message frame in Abis signaling
interface.
21
b.
The BTS may acknowledge the receipt of the Origination Message

with a Base Station Acknowledgment Order to the MS, or will send
this Base Station Acknowledgment Order to the MS encapsulated in
the Abis-Paging Channel Message Transfer from the BSC.
c.
The BSC constructs the CM Service Request message, places it in the

Complete Layer 3 Information message, and sends the message to the
MSC and starts timer T303. If the BSC 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.
d.
The MSC sends an Assignment Request message to the BSC 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 BSC. The MSC then starts timer T10. Upon the receipt
of the Assignment Request message, the BSC stops timer T303.
e.
The BSC sends an Abis-BTS Setup message to the BTS to request

allocation of radio resource at the BTS. The BSC starts timer
Tsetupb. This step can occur any time after receipt of the
Origination message from the BTS.
f.
If resources are available, the BTS responds with an Abis-Connect

message. The BTS starts timer Tconnb.
g.
The BSC sends Abis-Connect Ack message to the BTS. The BTS
stops timer Tconnb.
h.
The BTS sends Abis-BTS Setup Ack to the BSC to acknowledge the
Abis-BTS Setup. If the BSC requested a preferred Walsh code in the
Abis-BTS Setup message and the BTS can support this Walsh code
assignment then the BTS includes this same Walsh code in the
Abis-BTS Setup Ack message. Otherwise the BTS may allocate a
different Walsh code assignment. The BSC stops timer Tsetupb.
i.
The BSC transmits the Abis-IS-2000 FCH Fwd message including

Null Data to let the BTS send Null traffic data toward the MS. Then
the BTS begin sending Null Traffic data for synchronizing between
the BTS and the MS. The BTS may have a function that enables to
send a Null Traffic data for synchronization between the BTS and the
MS. BSC can notify whether the BTS has the function or not by
sending Null Traffic.
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
A.S0003-Av2.0
22
A.S0003-Av2.0
j.
The BTS sends Abis-IS-2000 FCH Rvs message including Idle data
to the BSC.
k.
The BSC sends an Abis-PCH Msg Transfer including Extended

Channel Assignment message to the BTS. The BTS sends an
Extended Channel Assignment message to the MS over the paging
channel of the radio interface (with the MS address) to initiate the
establishment of a radio traffic channel.
l.
The MS begins sending the traffic channel preamble (TCH Preamble)

to the BTS over the designated reverse traffic channel. Then the BTS
transmits this preamble with an Abis-IS-2000 FCH Rvs message.
2
3
4
5
6
7
8
9
10
11
14
m. Once the BSC acquires the reverse traffic channel, it sends an

Abis-IS-2000 FCH Fwd message including a Base Station
Acknowledgement Order with layer 2 acknowledgement required, to
the MS over the forward traffic channel.
15
n.
After receiving a BS Ack Order message, the MS begins sending Idle

TCH Data Frames over the reverse traffic channel. Then the BTS
transmits this frame message with an Abis-IS-2000 FCH Rvs
message.
o.
The MS Ack Order message is sent from the MS, and then the BTS
transmits it to the BSC with an Abis-IS-2000 FCH Rvs message.
p.
The BSC then sends the Abis-IS-2000 FCH Fwd message including
the Service Connect message to the BTS specifying the service
configuration for the call. Then the BTS transmits the Service
Connect message to the MS. The MS begins processing traffic in
accordance with the specified service configuration.
q.
On receipt of the Service Connect message, the MS responds with a

Service Connect Completion message. Then the BTS transmits it
with an Abis-IS-2000 FCH Rvs message.
r.
After the radio traffic channel and circuit have both been established
and fully interconnected, the BSC sends the Assignment Complete
message to the MSC and considers the call to be in conversation
state.
12
13
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
The MSC stops timer T10 upon receipt of the Assignment Complete
message.
35
23
A.S0003-Av2.0
24
A.S0003-Av2.0
5.2
Mobile Terminated Call
2
3
The following subsections describe the procedure for establishing a call through a mobile
terminated action.
Mobile terminated call setup involves exchange of the following BSC-BTS messages:
Abis-PCH Message Transfer
Abis-PCH Message Transfer Ack
Abis-BTS Setup
Abis-Connect
Abis-Connect Ack
10
Abis-BTS Setup Ack
11
12
13
14
Abis-ACH Message Transfer Ack
15
16
17
5.2.1
18
Abis-PCH Message Transfer

See section 5.1.9.
19
20
5.2.2
21
Abis-PCH Message Transfer Ack

See section 5.1.10.
22
23
5.2.3
24
Abis-BTS Setup
See section 5.1.3.
25
26
5.2.4
27
Abis-Connect
See section 5.1.4.
28
29
30
5.2.5
Abis-Connect Ack
See section 5.1.5.
25
A.S0003-Av2.0
1
2
5.2.6
Abis-BTS Setup Ack

See section 5.1.6.
4
5
5.2.7

See section 5.1.7.
7
8
5.2.8

See section 5.1.8.
10
11
5.2.9
12

See section 5.1.1.
13
14
5.2.10
Unused section
5.2.11
15
16
17
18
See section 5.1.11.
19
26
A.S0003-Av2.0
5.2.12
Successful Mobile Terminated Call
This section describes the call flow associated with a mobile station call termination in the
IS-2000 system.
MS
BTS
MSC
BSC
Paging Request
General Page
Abis-PCH Msg. Transfer (GPM)
Page Response
Abis-ACH Msg. Transfer (PRM)
c
d
Complete L3 Info:
Paging Response
T303 Assignment Request
Abis-BTS Setup
Tconnb
f
g
h
Abis-Connect Ack
Abis-BTS Setup Ack

Null Traffic
Abis-IS-2000 FCH Fwd (Null Data)
Extended
Channel Assignment
Abis-PCH Msg. Transfer (ECAM)
TCH Preamble
Abis-IS-2000 FCH Rvs (Preamble)
BS Ack Order
Abis-IS-2000 FCH Fwd (BS Ack)
Idle Tch Data Frames
MS Ack Order
Abis-IS-2000 FCH Rvs (MS Ack)
Service Connect
Abis-IS-2000 FCH Fwd (SCM)
j
k

T10
l
m
n
o
p
q
r
Serv. Con. Completion Abis-IS-2000 FCH Rvs (SCCM)

Assignment Complete
Abis-IS-2000 FCH Fwd (AWIM)
Abis-IS-2000 FCH Rvs (MS Ack)
T301
Connect Order
Abis-IS-2000 FCH Rvs (Connect Order)
BS Ack Order
Abis-IS-2000 FCH Fwd (BS Ack)
Figure 5.2.12-1 Mobile Terminated Call
27
s
t
u
v
w
Connect
Tsetupb
Abis-Connect
MS Ack Order
a
b
BS Ack Order
Alert with Info
Time
x
y
Comment
a.
The MSC sends the Paging Request message to the BSC to initiate a
mobile terminated call setup scenario.
b.
The BSC constructs a General Page Message (GPM), places the

message into an Abis-PCH Msg Transfer Message and sends the
Abis-PCH Msg Transfer Message to the BTS. The BTS sends the
GPM to the MS over the paging channel. The BSC may send this
message to multiple BTSs managed by this BSC. In the following
description, it is assumed that the BSC sends this message to single
BTS.
c.
The MS acknowledges the page by transmitting a Page Response

Message (PRM) to the BTS over the access channel. Upon receipt of
this message, the BTS places this message into an Abis-ACH Msg
Transfer Message and sends it to the BSC.
d.
The BTS acknowledges the receipt of the PRM from the MS by

sending a Base Station Acknowledgement Order to the MS.
e.
The BSC sends the Complete Layer 3 Information message

containing the Paging Response message to the MSC. The BSC starts
timer T303. The BSC may request the MSC to allocate a preferred
terrestrial circuit.
f.
The MSC sends an Assignment Request message to request

assignment of radio resources. The message will also include
terrestrial circuit if one it to be used between the MSC and the BSC.
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
If the BSC 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.
Upon receipt of the Assignment Request message from the MSC, the
BSC stops timer T303.
25
26
27
28
29
30
g.

allocation of radio resources at the BTS. The BSC may allocate a
code channel and include it in the Abis-BTS Setup. The BSC starts
timer Tsetupb.
h.
Upon receipt of Abis-BTS Setup message, the BTS allocates radio

resources and sends Abis-Connect message to initiates an Abis
31
32
33
34
35
A.S0003-Av2.0
28
A.S0003-Av2.0
connection and to report the result of resource allocation. The BTS

starts timer Tconnb.
2
3
i.
The BSC replies with an Abis-Connect Ack message to complete the

Abis connection. The BTS stops timer Tconnb.
j.
The BTS sends Abis-BTS Setup Ack to acknowledge the Abis-BTS

Setup. If the BSC requested a preferred Walsh code in the Abis-BTS
Setup message and the BTS can support this Walsh code assignment
then the BTS includes this same Walsh code in the Abis-BTS Setup
Ack message. Otherwise the BTS may allocate a different Walsh
code assignment. The BSC stops timer Tsetupb.
k.
The BSC sends an Abis-IS-2000 FCH Fwd (Null Traffic Data)

message to the BTS. The BTS starts sending Null Traffic Data to the
mobile station. This allows the mobile station to acquire the FCH
(Fundamental channel). The BTS may have a function that enables to
send a Null Traffic data for synchronization between the BTS and the
MS. BSC can notify whether the BTS has the function or not by
sending Null Traffic..
l.
Upon receiving the first Abis-IS-2000 FCH Fwd (Null Traffic Data)
message, the BTS starts to send Abis-IS-2000 FCH Rvs (Idle frame)
message to the BSC.
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
m. The BSC sends an Extended Channel Assignment message to assign

the FCH.
23
n.
The MS starts to send the Traffic Channel Preamble. Upon receiving

the Traffic Channel Preamble, the BTS stops sending the idle frames
and starts sending the traffic frames containing the Traffic Channel
Preamble.
o.
The BSC sends the BS Ack Order to the MS via the BTS in the
Abis-IS-2000 FCH Fwd message.
p.
The MS stops transmitting the Traffic Channel Preamble and starts to

transmit idle traffic channel data frames upon receipt of the BS Ack
order.
q.
The MS sends the MS Ack Order to acknowledge the BS Ack order.

This is sent by the BTS to the BSC in the Abis-IS-2000 FCH Rvs
message.
24
25
26
27
28
29
30
31
32
33
34
29
r.
The BSC sends the Service Connect Message (SCM) to the MS

specifying the service configuration for the call. This message is sent
by the BSC to the BTS in the Abis-IS-2000 FCH Fwd message. The
MS begins processing traffic in accordance with the specified service
configuration.
s.
Upon receipt of the Service Connect Message (SCM), the MS

responds with a Service Connect Completion Message (SCCM).
Upon receipt of this message, BTS sends an Abis-IS-2000 FCH Rvs
message containing this message to the BSC.
t.
After the radio traffic channel and circuit have both been established,
the BSC sends the Assignment Complete message to the MSC. The
MSC stops timer T10 upon the receipt of the Assignment Complete
message from the BSC and starts timer T301.
u.
The BSC sends Alert with Information Message (AWIM) to the MS

to cause ringing at the MS. This message is sent by the BSC to BTS
in the Abis-IS-2000 FCH Fwd message.
v.
The MS acknowledges the reception of the Alert with Information

Message by transmitting the MS Ack Order.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
A.S0003-Av2.0
20
w. When the call is answered at the MS, a Connect Order, with

acknowledgment required, is transmitted to the BSC via the BTS.
21
x.
The BSC acknowledges the Connect Order with the BS Ack order.
22
y.
The BSC 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 BSC.
23
24
25
26
27
30
A.S0003-Av2.0
5.3
Call Clearing
MS, BTS, BSC or MSC will initiate call clearing procedure.
The Following messages are exchanged between BSC and BTS.
Abis-BTS Release
Abis-BTS Release Ack
Abis-BTS Remove
Abis-BTS Remove Ack
10
11
12
Abis-BTS Release Request
5.3.1
Call Clearing initiated by MS
5.3.1.1
Successful Clear Scenarios
13
14
15
16
17
18
19
20
21
For a normal clearing that is initiated by the MS, the MS will send a Release Order to the
BTS. The BTS shall send an Abis-IS-2000 FCH Rvs message that contains the Release
Order message to the BSC. Then BSC sends Clear Request message to the MSC and
starts 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
23
24
25
In response to the Clear Command message from the MSC, the BSC sends an
Abis-IS-2000 FCH Fwd message containing the Release Order message. The BTS
sends this to the MS on the forward traffic channel to wait for the Abis-Remove Ack
message from the BTS.
26
27
If the BTS receives the Abis-BTS Release message, the BTS starts to releases the radio
resource, sends Abis-Remove message to the BSC and starts timer Tdisconb.
28
29
In response to the Abis-Remove message from the BTS, the BSC sends Abis-Remove
Ack message to the BTS. The BTS will stop timer Tdisconb.
30
31
Then the BTS sends an Abis-BTS Release Ack message to the BSC to acknowledge the
completion of the releasing the radio resources.
32
33
34
35
36
If the BSC receives the Abis-BTS Release Ack message from the BTS, the BSC will stop
timer Tdrptgtb and sends a Clear Complete message to the MSC. Then the BSC
releases the related terrestrial circuit to the BTS, if allocated. The MSC stops timer
T315 upon receipt of the Clear Complete message. The MSC releases the underlying
transport connection.
37
The call flow scenarios are illustrated in section 5.3.4, 5.3.5 and 5.3.6..
31
5.3.1.2
2
3
4
Unsuccessful Call Clearing Procedures

Each node will supervise and detect the unnecessary reserved resource spontaneously,
and release it individually.
5.3.1.3
5
6
A.S0003-Av2.0

See 5.1.8.
5.3.1.3.1
See 5.1.8.1.
8
9
5.3.1.3.2
10
Failure Operation
See 5.1.8.2.
11
12
5.3.1.4
13
14

See 5.1.7.
5.3.1.4.1
15
See 5.1.7.1.
16
17
5.3.1.4.2
18
Failure Operation
See 5.1.7.2.
19
20
5.3.1.5
21
22
23
24
Abis-BTS Release
In response to the Clear Command message from the MSC, the BSC sends an
Abis-IS-2000 FCH Fwd message containing the Release Order message and then the
BSC sends an Abis-BTS Release message to the BTS.
5.3.1.5.1
25
26
The BSC, after sending an Abis-BTS Release message to the BTS and starts timer
Tdrptgtb to wait for the Abis-Release Ack message from the BTS.
27
28
29
Upon receipt of the Abis-BTS Release message, the BTS releases the associated radio
resources. The BTS sends an Abis-BTS Release Ack message to the BSC to acknowledge
the clearing of resources at the BTS.
30
31
32
32
A.S0003-Av2.0
5.3.1.5.2
2
3
Failure Operation
If the BSC fails to receive an Abis-BTS Release Ack message before the expiration of
timer Tdrptgtb, the BSC may resend the Abis-BTS Release message to the BTS.
4
5
5.3.1.6
6
7
8

The Abis-BTS Release Ack message is used by BTS to respond to a request that it
releases the radio resources in the BTS.
5.3.1.6.1
9
10
11
Upon receipt of the Abis-BTS Release message, the BTS releases the associated radio
resources. The BTS sends an Abis-BTS Release Ack message to the BSC to acknowledge
the clearing of resources at the BTS.
12
13
5.3.1.6.2
14
Failure Operation
None
15
16
5.3.1.7
17
18
19
Abis-BTS Remove
In response to the Abis-BTS Release message from the BSC, the BTS sends an Abis-BTS
Remove message to the BSC and starts to releases the radio resource.
5.3.1.7.1
20
21
The BTS, after sending an Abis-BTS Remove message to the BSC and starts timer
Tdisconb to wait for the Abis-Remove Ack message from the BSC.
22
23
Then the BSC sends an Abis-BTS Remove Ack message to the BTS to acknowledge the
receiving of the message.
24
25
5.3.1.7.2
26
27
Failure Operation
If an Abis-BTS Remove Ack message is not received from the BSC while timer Tdisconb
is active, the BTS may choose to resend a Abis-BTS Remove message to the BSC.
28
29
30
31
5.3.1.8
Abis-BTS Remove Ack

The Abis-BTS Remove Ack message is used by BSC to confirm the reception of the
Abis-Remove message in BSC.
33
5.3.1.8.1
2
3
A.S0003-Av2.0
The BSC sends an Abis-BTS Remove Ack message to the BTS to acknowledge the
receiving of Abis-BTS Remove message .
4
5
6
5.3.1.8.2
Failure Operation
None
7
8
34
A.S0003-Av2.0
5.3.2
Call Clearing initiated by BS/MSC
5.3.2.1
2
3
4
If some internal BSC failure occurs, then the BSC will initiate call clearing.
5
6
The BSC sends Clear Request message to the MSC and starts timer T300 to wait for the
Clear Command message from the MSC.
7
8
9
10
The MSC is responsible for clearing any A1, A2, and/or A5 connections associated with
the call. To release all allocated resources, the MSC sends a Clear Command message to
the BSC and starts timer T315. The BSC responds with a Clear Complete message and
stop timer T300.
11
12
13
Then the BSC sends an Abis-IS-2000 FCH Fwd message containing the Release Order
message and the Release Order will be transferred to MS on the IS-2000 FCH Fwd
channel.
14
15
If the BTS receives Release Order from MS, the BTS sends Abis-IS-2000 FCH Rvs
message that contains the Release Order message to the BSC.
16
17
Then the BSC sends an Abis-BTS Release message to the BTS and starts timer Tdrptgtb
to wait for the Abis-Remove Ack message from the BTS.
18
19
If the BTS receives the Abis-BTS Release message, the BTS starts to releases the radio
resource, sends Abis-Remove message to the BSC and starts timer Tdisconb.
20
21
22
23
24
25
26
27
28
releases the related terrestrial circuit to the BTS, if allocated. And the MSC stops timer
29
The call flow scenarios are illustrated in section 5.3.
30
5.3.2.2
31

Each node will detect the unnecessary reserved resource and release it individually.
32
33
5.3.2.3
34
35
36

See 5.1.8.
5.3.2.3.1
See 5.1.8.1
37
35
5.3.2.3.2
A.S0003-Av2.0
Failure Operation
See 5.1.8.2
3
4
5.3.2.4
5
6

See 5.1.7.
5.3.2.4.1
See 5.1.7.1
8
9
5.3.2.4.2
10
Failure Operation
See 5.1.7.2.
11
12
5.3.2.5
13
14
Abis-BTS Release
See 5.3.1.5
5.3.2.5.1
15
See 5.3.1.5.1.
16
17
5.3.2.5.2
18
Failure Operation
See 5.3.1.5.2.
19
20
5.3.2.6
21
22

See 5.3.1.6.
5.3.2.6.1
23
See 5.3.1.6.1
24
25
5.3.2.6.2
26
Failure Operation
None
27
28
29
5.3.2.7
Abis-BTS Remove
See 5.3.1.7.
36
A.S0003-Av2.0
5.3.2.7.1
See 5.3.1.7.1.
3
4
5
5.3.2.7.2
Failure Operation
See 5.3.1.7.1.
6
7
37
A.S0003-Av2.0
5.3.3
Call Clearing initiated by BTS
5.3.3.1
2
3
4
5
6
If the MS is not active (powered off) or if for any reason the radio channel failed between
the MS and the BTS or if some internal BTS failure occurs, then the BTS will initiate call
clearing by sending Abis-BTS Release Request and starts Tdrptgtb.
7
8
9
If the BSC receives Abis-BTS Release Request message, the BSC sends Clear Request
message to the MSC and starts timer T300 to wait for the Clear Command message from
the MSC.
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 sends a Clear Command message to
the BSC and starts timer T315. The BSC stops timer T300.
13
14
15
Then the BSC sends an Abis-IS-2000 FCH Fwd message containing the Release Order
message and the Release Order will be transferred to MS on the IS-2000 FCH Fwd
channel.
16
17
If the BTS receives Release Order from MS, the BTS sends Abis-IS-2000 FCH Rvs
message that contains the Release Order message to the BSC.
18
19
Then the BSC sends an Abis-BTS Release message to the BTS and starts timer Tdrptgtb
to wait for the Abis-Remove Ack message from the BTS.
20
21
22
If the BTS receives the Abis-BTS Release message, the BTS stops timer Tdrptgtb , starts
to releases the radio resource and sends Abis-Remove message to the BSC and starts
timer Tdisconb.
23
24
25
26
27
28
29
30
31
releases the related terrestrial circuit to the BTS, if allocated. And the MSC stops timer
32
The call flow scenarios are illustrated in section 5.3.
33
5.3.3.2
34

Each node will detect the unnecessary reserved resource and release it individually.
35
36
37
38
39
5.3.3.3

If the MS is not active (powered off) or if for any reason the radio channel failed between
the MS and the BTS or if some internal BTS failure occurs, then the BTS will send
Abis-BTS Release Request message to the BSC in order to initiate call clearing.
38
A.S0003-Av2.0
5.3.3.3.1
2
3
The BTS, after sending an Abis-BTS Release Request message to the BSC and starts
timer Trelreqb to wait for the Abis-Release message from the BSC.
4
5
If the BTS receives the Abis-BSC Release message, then the BTS stops Trelreqb and
starts to releases the radio resource.
6
7
5.3.3.3.2
8
9
Failure Operation
If an Abis-BTS Release message is not received from the BSC while timer Trelreqb is
active, the BTS may choose to resend a Abis-BTS Release Request message to the BSC.
10
11
5.3.3.4
12
13

See 5.1.8.
5.3.3.4.1
14
See 5.1.8.1
15
16
5.3.3.4.2
17
Failure Operation
See 5.1.8.2
18
19
5.3.3.5
20
21

See 5.1.7.
5.3.3.5.1
22
See 5.1.7.1
23
24
5.3.3.5.2
25
Failure Operation
See 5.1.7.2
26
27
5.3.3.6
28
29
30
Abis-BTS Release
See 5.3.1.5
5.3.3.6.1
See 5.3.1.5.1.
39
A.S0003-Av2.0
1
2
5.3.3.6.2
Failure Operation
See 5.3.1.5.2.
4
5
5.3.3.7
6
7

See 5.3.1.6.
5.3.3.7.1
See 5.3.1.6.1
9
10
5.3.3.7.2
11
Failure Operation
None
12
13
5.3.3.8
14
15
Abis-BTS Remove
See 5.3.1.7.
5.3.3.8.1
16
See 5.3.1.7.1.
17
18
5.3.3.8.2
19
Failure Operation
See 5.3.1.7.1.
20
21
5.3.3.9
22
23
Abis-BTS Remove Ack

See 5.3.1.8.
5.3.3.9.1
24
See 5.3.1.8.1.
25
26
27
28
5.3.3.9.2
Failure Operation
None
29
40
A.S0003-Av2.0
5.3.4
Call Clearing initiated by MS
This section provides the call flow diagram for a call clearing operation initiated by MS.
3
4
5
BS
MS
BSC
BTS
MSC
Time
6
7
8
Release Order
Clear Request
12
Clear Command
Release Order
Abis-IS-2000 FCH Fwd (Release Order)

Abis-BTS Release
14
c
d
13
Tdrptgtb
15
Abis-Remove
T315
16
17
T300
10
11
Abis-IS-2000 FCH Rvs (Release Order)
Tdisconb
Abis-Remove Ack
f
g
18
19
20
21
22
Clear Complete
Figure 5.3.4-1 Call Clearing initiated by MS

a.
The MS initiates call clearing by transmitting a Release Order over

the reverse traffic channel. In response to the order, BTS sends an
Abis-IS-2000 FCH Rvs message containing the Release Order
message to the BSC.
b.
The BSC then sends the Clear Request message to the MSC to
initiate the call clear transaction. Timer T300 is started by the BSC.
c.
The MSC sends a Clear Command message to the BSC to instruct the
BSC to release the associated dedicated resource (such as terrestrial
circuit) and starts timer T315. The BSC stops timer T300.
d.
In response to the Clear Command message from the MSC, the BSC
sends an Abis-IS-2000 FCH Fwd message containing the Release
Order message. The BTS sends the Release Order message to the MS
over the forward traffic channel
23
24
25
26
27
28
29
30
31
32
33
34
41
e.
The BSC then sends an Abis-BTS Release message to the BTS and
starts Tdrptgtb.
f.
The BTS releases the radio resource and sends Abis Remove message
to the BSC. The BTS starts Tdisconb.
g.
In response to the Abis-Remove message from the BTS, BSC sends

an Abis-Remove Ack message to the BTS. Upon receipt of the
Abis-Remove Ack message the BTS stops timer Tdisconb.
h.
The BTS sends an Abis-BTS Release Ack message to the BSC to

acknowledge the Abis removal. Upon receipt of the Abis-BTS
Release Ack message the BSC stops timer Tdrptgtb.
2
3
4
5
6
7
8
9
10
11
12
13
14
A.S0003-Av2.0
i. The BSC sends a Clear Complete message to the MSC. Then BSC
releases the related terrestrial circuit to the BTS, if allocated. And
the MSC stops timer T315 upon receipt of the Clear Complete
message. The MSC releases the underlying transport connection.
15
16
42
A.S0003-Av2.0
5.3.5
Call Clearing initiated by BSC/MSC
2
3
This section provides the call flow diagram for a call clearing operation initiated by
BSC/MSC.
4
BS
BS
5
BSC
BSC
BTS
BTS
MS
6
7
Time
Clear Request
a
T300
Release Order
8
9
MSC
MSC
Clear Command

c
Release Order
10
T315
Abis-BTS Release
11
Tdrptgtb
Abis-Remove
12
Tdisconb
Abis-Remove Ack
13
Clear Complete
h
i
14
15
16
Figure 5.3.5-1 Call Clearing initiated by BSC/MSC

a.
In the case where the BSC detects some failures related the call, the
BSC sends a Clear Request message to the MSC. The BSC starts
timer T300 and waits for the Clear Command from the MSC (step b).
A Call Clearing flow initiated by BSC starts from this step.
b.
The MSC and sends a Clear Command message to instruct the BSC
to release the associated dedicated resource (such as terrestrial
circuit) and starts timer T315. In the case of a Call Clearing
initiated BS, the BSC stops timer T300. A Call Clearing flow
initiated by MSC starts from this step.
c.
sends Abis-IS-2000 FCH Fwd containing the Release Order message.
17
18
19
20
21
22
23
24
25
26
43
The BTS sends the Release Order message to the MS over the
forward traffic channel.
2
3
d.
The MS replies with a Release Order over the reverse traffic channel.
In response to the order, BTS sends an Abis-IS-2000 FCH Reverse
containing the Release Order message to the BSC.
e.
starts Tdrptgtb.
f.
g.
In response to the Abis Remove message from the BTS, the BSC
sends an Abis Remove Ack message to the BTS. Then the BSC
releases the related terrestrial circuit to the BTS, if allocated. If the
BTS receives the Abis-Remove Ack message, the BTS stops timer
Tdisconb.
h.

acknowledge the Abis removal. If the BSC receives the Abis-Release
Ack message, BSC stops timer Tdrptgtb.
i.
Upon receipt of the Abis BTS Release Ack message, the BSC sends
the 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.
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
A.S0003-Av2.0
22
44
A.S0003-Av2.0
5.3.6
2
3
4
Call Clearing initiated by BTS

This section provides the call flow diagram for a call clearing operation initiated by the
BTS.
5
6
7
BS
MS
9
10
12
BSC
BTS
11
Trelreqb
MSC
Clear Request
T300
Clear Command
Release Order
Time

c
13
14
Release Order
15
T315
16
Abis-BTS Release
17
Abis-Remove
18
19
Tdisconb
Tdrptgtb
Abis-Remove Ack
20
21
Abis-BTS Release ACK
22
Clear Complete
24
26
Figure 5.3.6-1 Call Clearing initiated by BTS

a.
In the case of a radio channel failure between the MS and the BTS, or
if the MS is not active, the BTS sends an Abis-BTS Release Request
message to BSC and the BTS starts timer Trelreqb. In response to
the message the BSC sends a Clear Request message to the MSC.
The BSC starts timer T300 and waits for the Clear Command from
the MSC. A Call Clearing flow initiated by BTS starts from this
step.
b.
The MSC starts timer T315 and sends a Clear Command message to
instruct the BSC to release the associated dedicated resource (such as
terrestrial circuit). The BSC stops timer T300.
c.
sends Abis-IS-2000 FCH Fwd containing the Release Order message.
The BTS sends the Release Order message to the MS over the
forward traffic channel.
27
28
29
30
31
32
33
34
35
36
37
38
39
h
i
23
25
45
d.
The MS replies with a Release Order over the reverse traffic channel.
In response to the order, BTS sends an Abis-IS-2000 FCH Rvs
containing the Release Order message to the BSC.
e.
starts Tdrptgtb. If the BTS receives Abis-BTS Release message from
the BTS, the BTS stops timer Trelreqb.
f.
g.
In response to the Abis Remove message from the BTS and the BSC
sends an Abis Remove Ack message to the BTS and returns a Clear
Complete message to the MSC. Then the BSC releases the related
terrestrial circuit to the BTS, if allocated. If the BTS receives the
Abis-Remove Ack message, the BTS stops timer Tdisconb.
h.

acknowledge the Abis removal. If the BSC receives the Abis-Release
Ack message, the BSC stops timer Tdrptgtb.
i.
Upon receipt of the Abis-BTS Release Ack message, the BSC sends
the 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.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
A.S0003-Av2.0
21
46
A.S0003-Av2.0
5.4
2
3
Handoff
This section describes handoff procedure using Abis interface within the BS.
5.4.1
4
5
6
TIA/EIA/IS-2001
Abis-BTS Interface Procedures and Messages

This section describes the messages and procedures used Abis connection to support
soft/softer handoff, Hard handoff.
5.4.1.1
Abis-BTS Interface Messages
7
8
This section describes the messages and procedures used Abis connection to support BTS
soft/softer handoff.
These messages are:
10
Abis-BTS Setup
11
Abis-BTS Setup Ack
12
Abis-Connect
13
Abis-Connect Ack
14
15
16
Abis-Traffic channel status
17
Abis-BTS-Release
18
Abis-BTS-Release Ack
19
Abis-Remove
20
Abis-Remove Ack
21
22
5.4.1.1.1
23
24
25
26
Abis-BTS Setup
The Abis-BTS Setup message is used by the BSC to request that a target BTS allocate
resources in one or more cells for support of a call association.
5.4.1.1.1.1
27
28
29
When the BSC decides that one or more cells at a target BTS are needed to support one or
more physical channel connections for a call, the BSC sends an Abis-BTS Setup message
to the target BTS to indicate the resources required. The BSC then starts timer Tsetupb.
30
31
32
Please refer to section 6.1.5 Abis-BTS Setup, for the format and content of this
message.
47
5.4.1.1.1.2
2
3
4
Failure Operation
If timer Tsetupb expires, the BSC may choose to resend the Abis-BTS Setup message.
5.4.1.1.2
5
6
7
8
9
A.S0003-Av2.0
Abis-BTS Setup Ack

The Abis-BTS Setup Ack message is used by the target BTS to respond to a request that
it allocates resources in one or more cells for support of one or more physical channel
connections for a call association.
5.4.1.1.2.1
10
11
12
13
14
When the target BTS receives an Abis-BTS Setup 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 Abis-Connect Ack message(s) has been
received, the target BTS responds by sending an Abis-BTS Setup Ack message to the
BSC.
15
16
Please refer to section 6.1.6 Abis-BTS Setup Ack for the format and content of this
message.
17
18
5.4.1.1.2.2
19
20
21
None.
5.4.1.1.3
22
23
24
25
26
Failure Operation
Abis -Connect
The Abis-Connect message is sent from the target BTS to the BSC to initiate or add cells
to one or more Abis user traffic connection. An Abis -Connect Ack message is expected
in response.
5.4.1.1.3.1
27
28
29
30
Upon receiving the Abis Signaling Address information, the receiving BTS begins the
process of establishing the Abis signaling connection with the BSC. The Abis Signaling
Address is used by the target BTS to allocate a logical circuit to be used for Abis
signaling. The SDU ID identifies the particular instance of the SDU function.
31
32
33
34
35
36
Following the establishment of the Abis signaling link, the Abis-Connect message is sent
from the target BTS to the entity at the other end. The target BTS expects an
Abis-Connect Ack message indicating the result of processing the Abis-Connect message
and, therefore, starts timer Tconnb. When the Abis user traffic connection(s) is
established, traffic packets are exchanged to verify that the two entities can communicate
via the Abis user traffic connection(s).
37
Please refer to section 6.1.12 Abis-Connect for the format and content of this message.
38
39
5.4.1.1.3.2
Failure Operation
48
A.S0003-Av2.0
If timer Tconnb expires, the BTS may choose to resend the Abis-Connect message.
2
3
5.4.1.1.4
4
5
6
7
Abis-Connect Ack.
The Abis-Connect Ack message is sent from the BSC to the target BTS to indicate the
result of processing the Abis-Connect message.
5.4.1.1.4.1
8
9
After processing the Abis-Connect message from the requesting BTS, the BSC will
indicate success/failure to the requesting BTS by sending an Abis-Connect Ack message.
10
11
12
13
If the Abis-Connect Ack message indicates that Abis-Traffic Channel Status messages are
to be sent, then the source BSC starts timer Tchanstatb to await Abis-Traffic Channel
Status message(s) for all new cells on each Abis connection. One instance of this timer
is started for each Abis connection to which one or more cells are being added.
14
15
Please refer to section 6.1.13 Abis-Connect Ack or the format and content of this
message.
16
17
5.4.1.1.4.2
18
19
20
21
22
23
If an instance of timer Tchanstatb expires, the BSC may assume that a failure has
occurred at the BTS during activation of the transmitter(s)/receiver(s) and delete the
unreported cells from the active set attached to the Abis connection. The BSC may then
send an Abis-BTS Release message to the target BTS to cleanly remove those cells from
the Abis connection.
5.4.1.1.5
24
25
26
27
28
29
Failure Operation

The Abis-Traffic Channel Status message is used by the target BS to notify the BSC 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
Abis-Connect Ack message indicates that it is requested.
5.4.1.1.5.1
30
31
When the target BS needs to notify the BSC of a status change relative to a specific set of
cells on one Abis connection, it sends an Abis-Traffic Channel Status message.
32
33
34
35
36
37
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 Abis-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).
38
39
Multiple instances of this message may be sent relative to a single Abis connection if, for
instance, transmitter(s)/receiver(s) are activated at different times; however, all cells
49
A.S0003-Av2.0
1
2
referenced within a single instance of this message shall be attached to the same Abis
connection.
3
4
5
The BSC stops the instance of timer Tchanstatb for that Abis connection when
Abis-Traffic Channel Status message(s) have been received containing references to all
cells added to the Abis connection by the Abis-Connect message.
6
7
Please refer to section 6.1.18, Abis-Traffic Channel Status, for the format and content
of this message.
8
9
5.4.1.1.5.2
10
11
12
None.
5.4.1.1.6
13
14
15
16
17
Failure Operation

This message is sent from the BSC to the target BTS on the Abis IS-2000 user traffic
subchannel for subchannel of type FCH (Fundamental Channel). It contains the
Forward airframe for the served MS along with control information for the target BTS.
5.4.1.1.6.1
18
19
20
This message is sent from BSC to the target BTS on Abis IS-2000 user traffic subchannel
connections of type FCH (Fundamental Channel). FCH messages are sent once every
20 ms.
21
22
23
24
25
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 BSC 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 Abis traffic connection of
5ms. However, the delay limits defined above will not be applied to satellite applications.
26
Forward Frame Sequence Number Alignment clarification:
27
28
29
30
The SDU function may use the PATE and Sequence Number information received in the
Abis-IS-2000 FCH Reverse message to ensure that all BTS's involved in soft handoff for
a call will simultaneously transmit identical forward air frames during identical frame
boundaries.
31
32
Please refer to section 6.1.16 Abis-IS-2000 FCH Forward for the format and content of
this message.
33
34
5.4.1.1.6.2
35
36
37
38
39
Failure Operation
None.
5.4.1.1.7

This message is sent from the target BTS to the BSC on Abis IS-2000 user traffic
subchannel connections of type IS-2000 FCH (TIA/EIA/IS-2000 Fundamental Channel).
50
A.S0003-Av2.0
1
2
3
4
It contains the decoded Reverse Traffic Channel frame received from the served MS
along with control information.
5.4.1.1.7.1
5
6
7
This message is sent to the BSC on the Abis 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.
8
9
10
11
12
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 BSC. This assumes a
maximum transmission and queuing delay on the Abis traffic connection of 5 ms.
However, the delay limits defined above will not be applied to satellite applications.
13
Forward Frame Alignment Requirements:
14
15
16
As part of the reverse-link processing, each target BTS channel element shall estimate the
arrival time error for the Abis-IS-2000 FCH Forward message last received and shall set
the PATE field of the next transmitted Abis-IS-2000 FCH Reverse message to this value.
17
18
19
20
21
22
23
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 indicates that the message arrived too
late to be transmitted in the correct airframe. Negative PATE values indicate that the
message arrived too early and therefore shall be buffered before transmission. Zero PATE
value indicates that the message arrived at the optimum time for processing and
transmission.
24
25
Please refer to section 6.1.17 Abis-IS-2000 FCH Reverse for the format and content of
this message.
26
27
5.4.1.1.7.2
28
29
30
None.
5.4.1.1.7
31
32
33
34
35
Failure Operation
Abis-BTS Release
The Abis-BTS Release message is used by the BSC to request that a target BTS
deallocate resources in one or more cells currently being used for support of one or more
physical channel connections for a call association.
5.4.1.1.8.1
36
37
38
39
When the BSC decides that one or more cells at a target BTS are no longer needed to
support one or more physical channel connections for a call association, the BSC sends an
Abis-BTS Release message to the target BS to indicate the resources that are no longer
required. The BSC then starts timer Tdrptgtb.
40
41
Please refer to section 6.1.7, Abis-BTS Release for the format and content of this
message.
51
1
2
5.4.1.1.8.2
A.S0003-Av2.0
Failure Operation
If timer Tdrptgtb expires, the BSC may choose to resend the Abis-BTS Release message.
4
5
5.4.1.1.8
6
7
8
9
10

The Abis-BTS Release Ack message is used by the BSC 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.
5.4.1.1.9.1
11
12
13
When the BTS receives an Abis-BTS Release message, it determines what resources are
no longer needed to support the call association. Once those resources are deallocated,
the BTS responds by sending an Abis-BTS Release Ack message to the BSC.
14
15
Please refer to section 6.1.8, Abis BTS Release Ack, for the format and content of this
message.
16
17
5.4.1.1.9.2
18
19
20
None.
5.4.1.1.9
21
22
23
24
25
26
Failure Operation
Abis-Remove
A target BTS uses the Abis-Remove message to request that the BSC remove the
indicated cells from the indicated Abis connections. This might result in the entire
removal of an Abis traffic subchannel if the last cell on that traffic subchannel is
removed.
5.4.1.1.10.1
27
28
29
30
The BTS sends an Abis-Remove message to the BSC requesting removal of the indicated
cells from one or more Abis connection. The BSC will reply with an Abis-Remove Ack
message. If the last cell is removed from an Abis traffic subchannel, the entire Abis
traffic subchannel is also terminated. The BTS starts timer Tdisconb.
31
32
Please refer to section 6.1.14, Abis-Remove, for the format and content of this
message.
33
34
35
36
37
38
5.4.1.1.10.2
Failure Operation
If the BSC does not recognize an Abis user traffic connection identified in the
Abis-Remove 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
Abis-Remove Ack message.
52
A.S0003-Av2.0
If timer Tdisconb expires, the BTS may resend the Abis-Remove message.
2
3
5.4.1.1.10
4
5
6
7
Abis-Remove Ack
The Abis-Remove Ack message is used by the BSC to notify the target BS that sent the
Abis-Remove message of the outcome of processing the Abis-Remove message.
5.4.1.1.11.1
8
9
10
The BSC sends an Abis-Remove Ack message to the target BTS that sent the
Abis-Remove message to indicate the results of processing the Abis-Remove message.
The Cause List element, when present, indicates any exceptions.
11
12
Please refer to section 6.1.15, Abis-Remove Ack, for the format and content of this
message.
13
14
15
16
5.4.1.1.11.2
Failure Operation
None.
17
53
5.4.2
A.S0003-Av2.0
Soft/Softer Handoff addition (Intra-BTS)
2
Time
MS
BTS
BSC
a
Abis-BTS Setup
Abis-Connect
Tsetupb
Abis-Connect Ack
Tconnb
Abis-BTS Setup Ack
Abis-Traffic channel status
Conditional
Tchanstatb
Extended/General/Universal
Handoff Direction Message
MS Ack Order
g
Handoff Completion Message
h
BS Ack Order
Figure 5.4.2-1 Soft/Softer Handoff addition (Intra-BTS)
4
5
a.

that the specified cells be added from the call. The BSC may allocate
a code channel and include it in the Abis-BTS Setup. The BSC starts
the timer Tsetupb.
b.
The BTS allocates internal resources related to the specified cells.

The BTS sends an Abis-Connect message to the SDU function of the
BSC. The BTS starts the timer Tconnb.
c.
The SDU function replies with an Abis-Connect Ack message and

allocates internal resources. The BTS stops timer Tconnb. If the
BSC has chosen to be notified of the start of transmission and
reception at the target BTS ,the BSC will set Abis-Connect Ack
message indicating that Abis-Traffic Channel Status message is
requested, starts timer Tchanstatb.
d.
The BTS sends Abis-BTS Setup Ack to acknowledge the Abis-BTS

Setup. If the BSC requested a preferred Walsh code in the
6
7
8
9
10
11
12
13
14
15
16
17
18
19
54
A.S0003-Av2.0
different Walsh code assignment. The BSC stops the timer Tsetupb.
2
3
4
5
e.
If the BSC has chosen to be notified of the start of transmission and

reception at the target BTS, when its SDU function and the target
BTS have synchronized with Abis traffic subchannel, the BTS sends
an Abis-Traffic Channel Status message to the BSC. The BSC stops
timer Tchnstatb.
f.
The BSC sends an Extended / General / Universal Handoff Direction

Message to the MS to add the new cell to the active set.
g.
The MS acknowledges receipt of the Extended / General / Universal

Handoff Direction Message with an MS Ack Order.
h.
The MS indicates successful results of processing the Extended /

General / Universal Handoff Direction Message by sending a
Handoff Completion message.
i.
The BSC acknowledges receipt of the Handoff Completion Message

by sending a BS Ack Order.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
55
5.4.3
A.S0003-Av2.0
Soft/Softer Handoff addition (Inter-BTS)
S o urc e
B TS
MS
Tim e
Targ et
B TS
BSC
A b is-B T S S etu p
A b is-C o n n ec t
Tc o n n b
T setu p b
A b is-B T S S etu p A ck
A b is-IS-2 0 0 0 F C H F wd ( F o rwa rd F ram es )

F o rw a rd Fram es
T c h a n sta tb
A b is-IS -2 0 0 0 F C H Rv s( Id le Fram es)
C o n d ition a l
E xten d ed /G en era l/U niv ers al

H a n d o ff Directio n M ess a g e
b
c
A b is-C o n n ect A ck
f
g
A b is-Tra ffic C h a nn el S ta tus
h
A b is-IS-2 0 0 0 F C H F wd
M S A c k O rd er
A b is-IS-2 0 0 0 F C H Rvs
j
H a n d o ff C om pletio n M es sa g e
A b is-IS-2 0 0 0 F C H Rvs
k
B S A ck O rd er
A b is-IS -2 0 0 0 F C H F wd
3
4
Figure 5.4.3-1 Soft/Softer Handoff addition (Inter-BTS)

a.
The BSC decides that one or more cells at the target BTS are needed
to support the call in soft/softer handoff. The BSC sends an
Abis-BTS Setup message to the target BTS to request allocation of
radio resources at the BTS. The BSC may allocate a code channel
and include it in the Abis-BTS Setup. The BSC starts the timer
Tsetupb.
b.
If resources are available, the target BTS responses with

Abis-Connect message. The BTS starts the timer Tconnb.
c.
The BSC replies with an Abis-Connect Ack message to complete the

Abis connection. The BTS stops timer Tconnb. If the BSC has
chosen to be notified of the start of transmission and reception at the
target BTS ,the BSC will set Abis-Connect Ack message indicating
that Abis-Traffic Channel Status message is requested, starts timer
Tchanstatb.
5
6
7
8
9
10
11
12
13
14
15
16
17
18
56
A.S0003-Av2.0
d.
The target BTS sends Abis-BTS Setup Ack to acknowledge the

Abis-BTS Setup. If the BSC requested a preferred Walsh code in the
different Walsh code assignment. The BSC stops the timer Tsetupb.
e.
The BSC begins to send the forward frames to the target BTS.
f.
The target BTS begins to transmit the forward frame as soon as

synchronization has occurred.
g.
The target BTS begins to send reverse idle frames. The reverse
frames contain the timing adjustment information necessary to
achieve synchronization.
h.

BTS have synchronized the Abis traffic sub-channel, the BTS send
an Abis-Traffic Channel Status message to the source BTS.
i.

Message to the MS to add the new cell to the active set.
j.

k.

l.

2
3
4
5
6
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
57
5.4.4
A.S0003-Av2.0
Soft/Softer Handoff Removal (Inter-BTS)
2
Source
BT S
MS
Time
Target
BT S
Extended/General/Universal
BSC
Abis-IS-2000 FCH Fw d
a
MS Ack Order
b
Handoff Com pletion Message
c
BS Ack Order
Abis-IS-2000 FCH Fw d
d
Abis-BTS Release
e
Abis-Rem ove
Tdrptgtb
f
Tdisconb
Abis-Rem ove Ack

Figure 5.4.4-1 Soft/Softer Handoff Removal (Inter-BTS)
4
5
a.

Message to the MS to drop the cell to the active set.
b.

c.

d.

e.
The BSC sends an Abis-BTS-Release message to the target BTS to

request that the specified cells be removed from the call. The BSC
starts timer Tdrptgtb.
6
7
8
9
10
11
12
13
14
15
16
58
g
h
A.S0003-Av2.0
f.
The target BTS, upon receipt of the Abis-BTS-Release message,

deallocates internal resources related to the specified cells. The target
BTS sends an Abis-Remove message to the SDU function of the BSC
and starts timer Tdisconb.
g.
The SDU function of the BSC replies with an Abis-Remove Ack

message and deallocates internal resources. The target BTS stops
timer Tdisconb.
h.
The target BTS sends an Abis-BTS-Release Ack message to the BSC

to acknowledge the removal of the specified cells. The BSC stops
timer Tdrptgtb.
2
3
4
5
6
7
8
9
10
11
59
5.4.5
A.S0003-Av2.0
Hard Handoff (Inter-BTS)
2
Source
BTS
MS
Tim e
Target
BTS
BSC
Abis-BTS Setup
Abis-Connect
Tconnb
Tsetupb
Abis-Connect Ack
c
d
Abis-BTS Setup Ack

Abis-IS-2000 FCH Fwd( Forward Fram es)
Forward Fram es
Abis-IS-2000 FCH Rvs( Idle Fram es)
e
Tchanstat
f
g
Conditional
Extended/G eneral/Universal
MS Ack Order
j
Reverse Fram es
Abis-IS-2000 FCH Rvs( Idle Fram es)
k
Handoff Com pletion Message
l
BS Ack Order
m
Abis-BTS Release
n
Abis-Rem ove
Tdisconb
Tdrptgtb
o
Abis-Rem ove Ack
3
4
a.
The BSC decides that one or more cells at the target BTS are needed
to support the call in hard handoff. The BSC sends an Abis-BTS
Setup to the target BTS to request allocation of radio resources at the
BTS. The BSC starts the timer Tsetupb.
b.
If resources are available, The target BTS responses with an

Abis-Connect message. The target BTS starts the timer Tconnb
6
7
9
10
11
12
13
Figure 5.4.5-1 Hard Handoff (Inter-BTS)
c.
The BSC replies with an Abis-Connect Ack message to complete the Abis connection. The target
BTS stops the timer Tconnb. If the BSC has chosen to be notified of the start of transmission and
reception at the target BTS ,the BSC will set Abis-Connect Ack message indicating that Abis-Traffic
Channel Status message is requested, starts timer Tchanstatb.
60
A.S0003-Av2.0
d.
The target BTS sends an Abis-BTS Setup Ack to acknowledge the

Abis-BTS Setup. The target BTS may allocate a code channel. In this
case, the target BTS includes the allocated code channel in the
Abis-BTS Setup Ack. Unless the target BTS allocates a code channel,
the target BTS includes the code channel that has been indicated by
the Abis-BTS Setup (step a) in the Abis-BTS Setup Ack. The BSC
stops the timer Tsetupb.
e.
The BSC begins to send the forward frames to the target BTS.
2
3
4
5
6
7
8
9
10
11
f.
The target BTS begins to transmit the forward frames as soon as synchronization has
occurred.
g.
The target BTS begins to send the reverse idle frames. The reverse
frames contain the timing adjustment information necessary to
achieve synchronization.
h.

BTS have synchronized Abis traffic subchannel, the BTS send an
Abis-Traffic Channel Status message to the BSC
i.

Message to the MS to change the cell to the active set.
j.

k.
The MS sends reverse traffic channel frames or the traffic channel

preamble to the target BTS.
l.

12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
m. The BSC acknowledges receipt of the Handoff Completion Message

29
n.
The BSC sends an Abis-BTS-Release message to the source BTS to

request that the specified cells be removed from the call. The BSC
starts timer Tdrptgtb.
o.
The source BTS, upon receipt of the Abis-BTS-Release message,

deallocates internal resources related to the specified cells. The
30
31
32
33
61
source BTS sends an Abis-Remove message to the SDU function of

the BSC and starts timer Tdisconb.
2
3
p.
The SDU function of the BSC replies with an Abis-Remove Ack

message and deallocates internal the resources. The target BTS
stops timer Tdisconb.
q.
The target BTS sends an Abis-BTS-Release Ack message to the BSC

to acknowledge the removal of the specified cells. The BSC stops
timer Tdrptgtb.
4
5
6
7
8
A.S0003-Av2.0
62
A.S0003-Av2.0
5.5
2
3
4
SMS Delivery
Delivery of a mobile terminated SMS (SMS-MT) and a mobile originated SMS
(SMS-MO) messages on the control channel is accomplished by the exchange of the
following messages.
Abis-ACH Msg Transfer.
8
9
10
Delivery of a mobile terminated SMS (SMS-MT) and a mobile originated SMS

(SMS-MO) on the traffic channel is accomplished by the exchange of the following
messages.
11
12
13
5.5.1
SMS Delivery on the Paging channel
14
15
5.5.1.1
16
17
18

See section 5.1.9.
5.5.1.1.1
19
20
21
22
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 BSC. MSC waits for the ADDS Page Ack message.
23
24
25
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 BSC.
26
27
28
29
30
31
32
When the BSC receives the ADDS Page message, the BSC sends an Abis-PCH Msg
Transfer to transfer a Data Burst Message to the BTS. The Data Burst Message contains
an SMS message sent from the MSC using the ADDS Page message. If the Tag
information element is included in the ADDS Page message, the BSC requires a Layer 2
acknowledgement from the MS by setting a Layer 2 Ack Request/Results field to 1.
And ARQ fields of the Data Burst Message are also set to values that require the Layer 2
Acknowledgement.
33
34
When the BTS receives the Abis-PCH Msg Transfer message, the BTS sends Data Burst
Message on the Paging channel.
35
36
5.5.1.1.2
Failure Operation
None.
37
63
5.5.1.2
A.S0003-Av2.0

See section 5.1.10.
3
4
5.5.1.2.1
5
6
7
8
9
10
11
12
If the Layer 2 acknowledgement is required, that is to say an Abis Ack Notify element
contained in the Abis-PCH Msg Transfer message is presented, the BTS sends the
Abis-PCH Msg Transfer Ack after the BTS receives an MS Ack Order from the MS. On
receipt of the Abis-PCH Msg Transfer Ack, the BSC will wait for A Abis ACH Message
Transfer carrying an MS Ack Order from the MS. On receipt of the Abis ACH Message
Transfer message the BSC sends a ADDS Page Ack to the MSC.
5.5.1.2.2
13
14
15
Successful Operarion
Failure Operation
None.
5.5.1.3
16

See section 5.1.1.
17
18
5.5.1.3.1
19
20
The BTS without L2 termination simply transfers an MS Ack order to the BSC by
utilizing an Abis-ACH Msg Transfer, when the BTS receives the MS Ack order.
21
22
On receipt of the MS Ack Order transferred by the Abis-ACH Msg Transfer, the BSC
sends the ADDS Page Ack to the MSC.
23
24
25
5.5.1.3.2
Failure Operation
None.
26
27
28
64
A.S0003-Av2.0
5.5.2
Call flow example for SMS Delivery on the Paging channel
This section provides the call flow description for the delivery of an SMS from the MSC to an idle
mobile station on the paging channel.
BS
MS
BTS
BSC
Abis--PCH Msg Transfer
(Data Burst Message)
MSC
ADDS Page

(MS Ack Order)
a
b
Data Burst Message

MS Ack Order
Time Comment
c
T3113
ADDS Page Ack
d
e
5
6
7
8
9
10
11
Figure 5.5.2-1 SMS Delivery on the Paging channel

a.
When the MSC determines that a point-to-point short message should be sent to an idle
MS, the MSC sends an ADDS Page message to the BSC. The ADDS Page message contains the
SMS message in its ADDS User Part information element. If the MSC requires an acknowledgment,
it will include the Tag element in the ADDS Page message. The MSC also starts timer T3113.
b.
The BSC sends the Abis-PCH Msg. Transfer that includes a Data
Burst message. The Data Burst Message contains the short message
in received ADDS Page.
c.
The BTS transfers the Data Burst message that is included in the
Abis-PCH Msg. Transfer message, on a Paging Channel.
d.
In case that the BTS receives the Abis Ack Notify element included
in the Abis-PCH Msg Transfer message, the BTS sends Abis-PCH
Msg Transfer Ack after Layer 2 acknowledgement, i.e. receiving an
MS Ack Order from the MS. The BTS L2 Termination is set to 1 to
indicate that Layer 2 is terminated at the BTS. When the BSC
receives the Abis-PCH Msg Transfer Ack and Layer 2 is terminated
at the BTS,
e.
The BSC sends ADDS PAGE Ack to the MSC when the BSC
receives Abis-PCH Msg Transfer Ack.
12
13
14
15
16
17
18
19
20
21
22
23
24
65
1
2
f.
A.S0003-Av2.0
When the MSC receives the ADDS Page Ack, the MSC stops timer
T3113 if the timer was previously started.
3
4
66
A.S0003-Av2.0
5.5.3
SMS Delivery on the Access channel
5.5.3.1
2
3
4
See section 5.1.1.
5
6
5.5.3.1.1
7
8
9
When the BTS receives the Data Burst Message that contains an SMS message on the
Access channel from the MS, the BTS sends Abis-ACH Msg Transfer to transfer the Data
Burst Message to the BSC.
10
11
12
When the MS requires Layer 2 acknowledgement, the BTS sends the MS Ack Order to
the MS on the Paging channel.
13
The BSC sends the ADDS Transfer that includes the SMS message to the MSC.
14
15
5.5.3.1.2
16
Failure Operation
None
17
18
5.5.3.2
19

See section 5.1.8.
20
21
5.5.3.2.1
22
23
24
When the BTS receives the Abis-PCH Msg Transfer that contains the BS Ack Order, the
BTS sends the BS Ack Order to the MS on the Paging channel and sends the Abis-PCH
Msg Transfer Ack to the BSC.
25
26
5.5.3.2.2
27
Failure Operation
None
28
29
30
5.5.3.3

See section 5.1.10
31
67
5.5.3.4
2
3
4
A.S0003-Av2.0
When the BSC receives the Abis-PCH Msg Transfer Ack from the BTS, the BSC knows
that the BTS received the Abis-PCH Msg Transfer successfully. A BTS L2 Termination
field in the Abis-PCH Msg Transfer Ack is set to 0.
5
6
7
8
5.5.3.4.1
Failure Operation
None
68
A.S0003-Av2.0
5.5.3.5
Call flow example for SMS Delivery on the Access channel
2
3
This section provides the call flow description for the delivery of an SMS from the mobile station to
the MSC on the access channel.
BS
BTS
MS
BSC
MSC
Time Comment
Data Burst Message

a
ADDS Transfer
BS Ack Order
b
c
5
6
7
8
Figure 5.5.3.5-1 SMS Delivery on the Access channel

a.
a.
The MS sends a Data Burst Message on the Access
Channel to transfer the SMS message.
b.
The BTS sends the Abis-ACH Msg Transfer message that contains
the Data Burst Message received on the Access Channel.
9
10
11
12
When the MS requires Layer 2 acknowledgement, the BTS sends the

MS Ack Order to the MS on the Paging channel.
13
14
15
16
c.
The BSC sends the ADDS Transfer message to the MSC that
contains the Data Burst Message received from the MS in the ADDS
User Part element
17
18
69
5.5.4
A.S0003-Av2.0
SMS Delivery on the Traffic channel to MS
This section provides the call flow description for the delivery of an SMS from the MSC to a mobile
station operating on the traffic channel.
BS
MS
BTS
BSC
MSC
ADDS Deliver
Time Comment
a
b
Data Burst Message
MS Ack Order

(MS Ack Order)
e
ADDS Deliver Ack
4
5
6
Figure 5.5.4-1 SMS Delivery on the Traffic channel to MS

a.
When the MSC determines that a point-to-point short message should

be sent to an idle MS, the MSC sends an ADDS Deliver message to
the BSC. The ADDS Deliver message contains the short message in
the ADDS User Part information element.
b.
The BSC sends Abis-IS-2000 FCH Fwd containing the Data Burst
Message
12
c.
The Data Burst Message is sent on the traffic channel.
13
d.
The MS acknowledges the receipt of the Data Burst Message, if it is

required.
e.
The BTS sends Abis-IS-2000 FCH Rvs containing the MS Ack

Order.
f.
The BSC sends ADDS Deliver Ack to acknowledge the ADDS

Deliver.
7
8
9
10
11
14
15
16
17
18
19
20
70
A.S0003-Av2.0
5.5.5
SMS Delivery on the Traffic channel from MS
This section provides the call flow description for the delivery of an SMS from a mobile station
operating on the traffic channel to the MSC.
BS
MS
BTS
Data Burst Message
BSC
A3-IS-2000 FCH Rvs
A3-IS-2000 FCH Fwd
(BS Ack Order)
Time Comment
MSC
a
ADDS Deliver
BS Ack Order
b
c
d
e
5
6
7
Figure 5.5.5-1 SMS Delivery on the Traffic channel from MS

a.
The MS sends a Data Burst Message on the Access Channel to

transfer the SMS message.
b.
The BTS sends Abis-IS-2000 FCH Rvs containing the Data Burst
Message to the BSC.
c.
The BS sends an ADDS Deliver message to the MSC. The ADDS

User Part element contains the SMS message.
d.
The BSC sends Abis-IS-2000 FCH Fwd message including the BS

Ack Order to acknowledge receipt of the Data Burst Message, if it is
required.
e.
The BTS transfer the BS Ack Order.
8
9
10
11
12
13
14
15
16
17
18
71
5.6
2
3
Traffic Burst Operation

This section describes the messages and procedures used between BSC and BTS to
support Traffic Burst Operation. The following messages are used:
Abis-Burst Request
Abis-Burst Response
6
7
Abis-Burst Commit
A.S0003-Av2.0
5.6.1
9
10
Abis-Burst Request
The Abis-Burst Request message is used by the BSC to request that a BTS reserve a set
of radio resources in support of a traffic burst.
11
12
5.6.1.1
13
14
15
16
17
18
19
When the BSC 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
Abis-Burst Request to the BTS. This message requests that the BTS 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
existing traffic burst by specifying the appropriate beginning and duration times. The
BSC then starts timer Tbstreqb.
20
21
Please refer to section 6.1.9, Abis-Burst Request, for the format and content of this
message.
22
23
5.6.1.2
24
25
Failure Operation
If timer Tbstreqb expires, the BSC may choose to resend the Abis-Burst Request
message.
26
27
5.6.2
28
29
Abis-Burst Response
The Abis-Burst Response message is used by the BTS to respond to a request that it
reserve radio resources in one or more cells for support of traffic burst.
30
31
32
33
34
35
5.6.2.1
When the BTS receives an Abis-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
Abis-Burst Request message is received, the BTS shall examine the starting time and
72
A.S0003-Av2.0
1
2
3
4
5
6
7
duration, as well as the set of requested resources to determine if this request extends the
traffic burst. The BTS then creates one or more Abis-Burst Response message(s)
indicating its ability to support the requested traffic burst for each of the cells included in
the Abis-Burst Request message. The BTS starts timer Tbstcomb after each Abis-Burst
Response message. The BSC stops timer Tbstreqb when it receives Abis-Burst
Response message(s) accounting for all cells included in the Abis-Burst Request
message.
8
9
Please refer to section 6.1.10, Abis-Burst Response, for the format and content of this
message.
10
11
5.6.2.2
12
13
Failure Operation
If timer Tbstcomb expires, the BTS may decommit all radio resources committed for the
cell(s) included in this message.
14
15
5.6.3
16
17
Abis-Burst Commit
The Abis-Burst Commit message is used by the BSC to indicate to the BTS the set of
target radio resources that will be used to support a traffic burst.
18
19
5.6.3.1
20
21
22
23
When the BSC has gathered traffic burst commitment information from BTSs and has
prepared the frame selector(s) to support the traffic burst, it sends an Abis-Burst Commit
message to the BTSs to indicate the set of committed target radio resources that will be
used to support the traffic burst.
24
25
26
27
When the BTS 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 BTS. This includes bandwidth and burst duration.
The BTS stops timer Tbstcomb.
28
29
Please refer to section 6.1.11, Abis-Burst Commit, for the format and content of this
message.
30
31
5.6.3.2
32
Failure Operation
None
33
34
35
36
37
38
39
5.6.4
High Speed Packet Data

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 Abis traffic connections during soft/softer
handoff. Setup of an Abis connection for a traffic burst is accomplished using
Abis-Burst Request, Abis-Burst Response, and Abis-Burst Commit messages.
73
1
2
3
A.S0003-Av2.0
Establishment of the Abis connection for the supplemental channel (SCH) is

accomplished via the Abis-BTS Setup, Abis-BTS Setup Ack, Abis-Connect and
Abis-Connect Ack messages.
4
5
6
7
8
9
10
11
12
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 Abis connection for the SCH is established
on the BTS 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 Abis connection. This involves
choosing the traffic circuit to be used and establishing context between the BTS and the
BSC/SDU function. Allocation of radio resources for the SCH is made each time that a
traffic burst is set up.
13
14
15
16
17
18
19
20
21
22
23
When the BSC 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 Abis-Burst Request message to
each BTS to request reservation of specific radio resources. Each BTS responds with an
Abis-Burst Response message to indicate radio resource reservations. Once the BSC has
received all expected Abis-Burst Response messages, it sends an Abis-Burst Commit
message to each BTS to confirm the traffic burst and the set of radio resources to be used.
Each BTS then prepares all indicated cells, connects them to the pre-established Abis
connections, and then participates in the burst. This is shown in the example in section
5.6.5 and 5.6.6.
24
74
A.S0003-Av2.0
5.6.5
Initial Traffic Burst Example Abis Connection Not Yet Established
The example below describes the support of traffic burst operation when the Abis
connection has not yet been established.
3
4
MS
BTS
M SC
BSC
SCRM
(data to be sent)
Abis-BTS Setup
c
d
Abis-BTS Setup Ack
Abis-Burst Request
Abis-Burst Response
Tbstreqb
Abis-Burst Commit
ESCAM
5
6
7
Figure 5.6.5-1 Initial Traffic Burst Example

a.
Either the BSC receives an indication from the MS (via a SCRM

message) or from the network (via data being received from the
PDSN) that data needs to be sent to/from the MS. The BSC decides a
traffic burst on one or more new cells at a BTS 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 BTS.
b.
The BSC assigns an Abis From ID value and sends an Abis BTS
Setup message to the BTS to establish an Abis traffic connection to
support a Supplemental Channel (SCH) for the call. This example
shows only a single Abis connection being established. The BSC is
not required to assign a physical Frame Selector at this time. The
BSC starts timer Tsetupb.
9
10
11
12
13
14
16
17
18
19
20
optional
optional
Forward and/or reverse traffic burst
15
Layer 2 Ack
a
b
Abis-Connect Ack
Tbstcomb
Comment
Tsetupb
Abis-Connect
Tconnb
Time
75
c.
The BTS assigns a traffic circuit and optionally a Channel Element

ID (CE ID) for each Abis traffic connection and sends an
Abis-Connect message to the BSC indicating the Traffic Circuit ID,
optional Abis From ID and CE ID to be associated with the specified
Abis From ID. The BSC and BTS save the association of CE ID,
Traffic Circuit ID, with Cell ID(s). The BSC also saves the Abis
From ID value, to be included in subsequent Abis messages to the
BTS. The BTS starts timer Tconnb. This is only done at the initial
burst.
d.
The BSC responds with an Abis Connect Ack message to complete

the Abis connection. This includes an Abis From ID value assigned
by the BSC, which will be included by the BTS in subsequent Abis
messages to the BSC. The BTS stops timer Tconnb.
e.
The BTS sends Abis-BTS Setup Ack messages to the BSC to

complete the Abis traffic circuit connection setup procedure for the
specified set of cells. This includes an Abis From ID value assigned
by the BTS, which will be included by the BSC in subsequent Abis
messages to the BTS for this call association. The BSC stops timer
Tsetupb.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
When the BSC has knowledge of resources for SCH in the BTS, the
procedure at step f and at step g is not necessary.
21
22
f.
The BSC sends an Abis-Burst Request including the Abis to ID to the

BTS to request the reservation of the needed radio resources for the
supplemental channel. The BSC starts timer Tbstreqb. Note that the
BSC may send an Abis-Burst Request to the BTS at any time after
receiving the Abis-BTS Setup message in step c, and that the set of
cells may be subset of the cells assigned in step a-e.
g.
The BTS determines that it can reserve part or all of the requested
resources and sends Abis-Burst Response message(s) including Abis
From ID to the BSC 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 BTS starts timer Tbstcomb. The BSC stops
timer Tbstreqb.
h.
In the Abis-Burst commit message, Walsh codes are used as obtained

from the Abis-Burst Response message, but the rate could be
downgraded in the Abis-Burst commit message by the BSC. Thus the
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
A.S0003-Av2.0
76
A.S0003-Av2.0
BSC chooses the Walsh code that determines the actual rate for the
traffic burst. However, if the BSC chooses a Walsh code other than
the one allocated by the BTS, it shall do so only to reduce the burst
rate. The new Walsh code in the Burst Commit message shall be
derived from the Walsh code in the Burst Response Message. The
BTS stops timer Tbstcomb. Note that the BSC may allocate the frame
selector any time after step b. Any resources (cells) not included in
the Abis-Burst Commit message may be released by the BTS.
2
3
4
5
6
7
8
9
i.
The BSC commands the MS to prepare for the traffic burst via an
ESCAM message.
j.
The MS acknowledges the command from the BSC with a Layer 2

Ack.
k.
The network and mobile station exchange forward and/or reverse

traffic burst information for the specified duration, or until the BSC
terminates or extends the traffic burst.
10
11
12
13
14
15
16
17
77
5.6.6
A.S0003-Av2.0
Subsequent Traffic Burst Example
2
3
4
The example below describes the support of traffic burst operation when the Abis
connection for the supplemental channel (SCH) has already been established.
MS
BTS
MSC
BSC
SCRM
(data to be sent)
Abis-Burst Request
Comment
a
b
optional
optional
Tbstreqb
Abis-Burst Response
Tbstcomb
Time
Abis-Burst Commit
ESCAM
Layer 2 Ack
Forward and/or reverse traffic burst
5
6
7
Figure 5.6.6-1 Subsequent Traffic Burst Example

a.
8
9
10
When the BSC has knowledge of resources for SCH in the BTS, the
procedure at step b and at step c is not necessary.
11
12
b.
The BSC decides a traffic burst is required on one or more cells for
which an Abis connection already exists in support of a supplemental
channel. The BSC sends an Abis-Burst Request to the BTS to request
the reservation of the needed radio resources for the supplemental
channel. The BSC starts timer Tbstreqb.
c.
The BTS determines that it can reserve part of all of the requested
resources and sends Abis-Burst Response message(s) to the BSC
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
BTS starts timer Tbstcomb. The BSC stops timer Tbstreqb.
d.
In the Abis-Burst commit message, Walsh codes are used as obtained

from the Abis-Burst Response message, but the rate could be
13
14
15
16
17
18
19
20
21
22
23
24
25
Either the BSC receives an indication from the MS (via a SCRM

message) or from the network (via data being received from the
PDSN) that data needs to be sent to/from the MS.
78
A.S0003-Av2.0
downgraded in the Abis-Burst commit message by the BSC. Thus the

BSC chooses the Walsh code that determines the actual rate for the
traffic burst. However, if the BSC chooses a Walsh code other than
the one allocated by the BTS, it shall do so only to reduce the burst
rate. The new Walsh code in the Burst Commit message shall be
derived from the Walsh code in the Burst Response Message.. The
BTS stops timer Tbstcomb. Note that the BSC may allocate the frame
selector any time after step b. Any resources (cells) not included in
the Abis-Burst Commit message may be released by the BTS.
2
3
4
5
6
7
8
9
10
e.
The BSC commands the MS to prepare for the traffic burst via an
ESCAM message.
f.
The MS acknowledges the command from the BSC with a Layer 2

Ack.
g.
The network and the MS exchange forward and/or reverse traffic

burst information for the specified duration, or until the BSC
terminates or extends the traffic burst.
11
12
13
14
15
16
17
79
A.S0003-Av2.0
5.7 PACA Service
PACA queuing processing is performed by following message;
Abis-PACA Update
4
5
5.7.1
PACA Updating
6
7
5.7.1.1 Abis-PACA Update
8
9
10
11
The Abis-PACA Update message is used by the BSC to instruct the BTS to update PACA
related information.
5.7.1.1.1
12
13
14
15
The Abis-PACA Update message is sent by the BSC upon receiving a PACA Update
message from the MSC with an indication to Remove MS from the queue, Remove
MS from the queue and release MS or Update Queue Position and Release MS or if
the BSC autonomously decides to do a cancel a PACA call.
16
17
18
5.7.1.1.2
Failure Operation
None.
19
20
21
22
80
A.S0003-Av2.0
5.7.2
2
3
Call flow example for PACA Updating

This section describes the call flow associated with PACA updating procedure.
BS
BTS
MS
BSC
MSC
Time Comment
PACAUpdate
Abis-PACAUpdate
Tpaca2
PACAUpdate Ack
4
5
6
Figure 5.7.2-1 PACA Updating procedure

a.
When the MSC determines that the PACA control for the BSC is
needed, the MSC sends the PACA Update message and starts the
timer Tpaca2.
b.
Upon receipt of the PACA Update message with an indication to

Remove MS from the queue, Remove MS from the queue and
release MS or Update Queue Position and Release MS, the BSC
sends the Abis-PACA Update message to the BTS. In case of
Remove MS from the queue and release MS or Update Queue
Position and Release MS the BSC sends a message to the MS via
the Abis-IS-2000 FCH Fwd message, and in addition the BSC sends
the Abis-PACA Update message to instruct the BTS to perform the
desired update action.
c.
The BSC sends the PACA Update Ack message to the MSC. The
MSC stops the timer Tpaca2 upon receipt of the PACA Update Ack
message.
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
81
A.S0003-Av2.0
6.
Abis Interface Message
6.1
Abis Interface Message Formats
3
4
5
6
7
For Abis interface messages there are a number of information elements that are
individually defined in section 7.1. Each information element in a given message is
tagged with a reference in section 7.1, a direction indication (i.e., some elements within a
message are bi-directional and others are not), and a Required or Optional type (M/O)
indicator.
The inclusion of information elements in each message is specified as follows:
R - information elements which are required for the message.
10
O - information elements which are optional for the message.
11
12
6.1.1
13
14
15
16
17
18
Message Body, Coding, and Ordering of Elements

For each Abis Interface message there are a number of information elements that are
individually defined in section 7.1. Each information element in a given message is
tagged with a reference in section 7.1, a direction indication (i.e., some elements within a
message are bi-directional and others are not), and a required or optional type.
Information elements that are marked as optional carry an additional explanation of when
they are used. Some information elements are reused in multiple messages.
19
20
21
22
23
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:
24
Table 6.1.1-1 Element Flow DIRECTION Indication

BTS -> BSC
BSC -> BTS
Element flows from BTS to the BSC

Element flows from the BSC to the BTS
25
26
27
The inclusion of information elements in each message is specified as follows:
O - information elements which are optional for the message. The conditions for inclusion of this
element are defined in the operation(s) where the message is used and in footnotes associated with the
table defining the order of information elements in the message.
R - Required in this version of this specification in the message whenever the message is sent.
28
29
30
31
32
Information elements that are required for a given message shall be present, and shall
appear in the order shown in the message definitions in this chapter.
33
82
A.S0003-Av2.0
1
2
3
Information elements that 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
definitions in this chapter.
4
5
6
An information element can very well be required for some messages and optional for
other messages.
7
8
All information elements shall include their Information Element Identifier (IEI) except
for the Message Type IE.
9
10
The bitmap tables in the message subsections of 6.1 are patterned after the format for the
information elements of section 7.1 and use the following conventions:
11
Element Name{<# instances>:
12
13
14
Different elements within a message are separated by

double lines.
15
Fields within elements are separated by single lines.
16
Octets are renumbered at the beginning of every element.
17
18
[<values>]
} Element Name
19
20
Name of information element.
= Set of allowed values.

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:
21
= exactly n occurrences of the element
22
n+
= n or more occurrences of the element
23
1..n = 1 to n inclusive occurrences of the element
24
label {<# instances>:
25
<octet 1>
26
<octet m>
27
} label
28
= Number of instances of the bracketed set of fields where

<# instances> notation indicates:
29
= exactly n occurrences of the field
30
n+
= n or more occurrences of the field
31
1..n = 1 to n inclusive occurrences of the field
32
ssss ssss
33
= Variable length field.
83
A.S0003-Av2.0
ssss ssss
2
3
6.1.2
4
5
6
The following message processing guidelines apply unless overridden by explicit

processing directions in other places within this standard.
1.
If a message is received containing a Message Type value that 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.
2.
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.
3.
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.
4.
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.
5.
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.
6.
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.
7.
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.
8.
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.
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
Message Processing Guidelines
84
A.S0003-Av2.0
1
2
3
4
9.
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.
5
6
6.1.3
Message Definition Guidelines
1.
New messages shall have a Message Type that was never previously used.
2.
Information Element Identifiers may be reused in future revisions only when:
The old use of the element identifier is not used in the new revision, and
10
The new use of the element identifier is used only in new messages that were
11
not defined in previous revisions.
12
The old use of the element identifier shall be supported within the context of
13
the old messages in which it was used.
14
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.
4.
Octets and bits which are undefined or which are defined as reserved may be
used in future revisions.
5.
New Information Elements in a message shall be defined after all previously

defined Information Elements.
21
6.
All new Information Elements shall be defined with a length field.
22
7.
New information may be added to the end of an existing Information Element,

provided that the Information Element is defined with a length field.
15
16
17
18
19
20
23
24
25
26
85
A.S0003-Av2.0
6.2
Abis interface messages
6.2.1
2
3
4
5
6
This Abis interface message is sent from the BTS to the BSC to notify the BSC of the
reception of the contained message or Layer 2 acknowledgment on the specified access
channel.
Information Element
Section
Element Direction
Type
Reference
Message Type
7.2
BTS -> BSC
Correlation ID
7.3
BTS -> BSC
Mobile Identity (IMSI)
7.4
BTS -> BSC
Mobile Identity (ESN)
7.4
BTS -> BSC
Cell Identifier
7.5
BTS -> BSC
BTS L2 Termination
7.30
BTS -> BSC
Air Interface Message
7.6
BTS -> BSC
CDMA Serving One Way Delay
7.24
BTS -> BSC
Authentication Challenge Parameter (RAND)
7.32
BTS -> BSC
a.
This element indicates the cell at the BTS on whose access channel the
air-interface message or Layer 2 acknowledgment was received.
8
9
10
The following table shows the bitmap layout for the Abis-ACH Msg Transfer message:
7
Message Type = [8EH]
Correlation ID:
Octet
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]
86
A.S0003-Av2.0
Identity Digit N+1 = [0H-9H] (BCD)
Identity Digit N = [0H-9H] (BCD)
= [1111] (if even number of digits)
n+1
Mobile Identity (ESN):
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:
A1 Element Identifier = [05H]
Length = [03H]
Cell Identification Discriminator = [02H]
(MSB)
Cell = [001H-FFFH]
(LSB)
Sector = [0H-FH] (0H = Omni)
BTS L2 Termination:
5
1
Abis Element Identifier = [73H]
Length = [01H]
Reserved = [0000 000]
BTS
L2
Term
inati
on
=
[0/1]
Air Interface Message:
Length = <variable>
TIA/EIA-IS-2000 Message Type = <00H to FFH>
Air Interface Message Length = <variable>
(MSB)
5
Air Interface Message = <any value>
(LSB)
CDMA Serving One Way Delay:
A1 Element Identifier = [0CH]
Length = [05H]
Cell Identification
(MSB)
Cell = [001H-FFFH]
87
1
2
Discriminator = [02H]
(LSB)
3
4
5
(MSB)
A.S0003-Av2.0
CDMA Serving One Way Delay = [0000H-FFFFH] (x100ns)
6
(LSB)
Authentication Challenge Parameter: A1 Element Identifier = [41H]

Length
7
1
2
Reserved
Random Number Type
(MSB)
4
RAND Value
5-m
(LSB)
88
m+1
A.S0003-Av2.0
6.2.2
UNUSED SECTION
6.2.3
2
3
4
5
6
This Abis interface message is sent from the BSC to the BTS to request the sending of the
contained message on the specified paging channels to a mobile station.
Information Element
Section
Element Direction
Type
Reference
Message Type
7.2
BSC -> BTS
Correlation ID
7.3
BSC -> BTS
7.4
BSC -> BTS
7.4
BSC -> BTS
Cell Identifier List
7.13
BSC -> BTS
7.6
BSC -> BTS
Layer 2 Ack Request/Results
7.8
BSC -> BTS
7.34
BSC -> BTS
Abis Ack Notify

7
O
O
O
O
O
c
e
b.
This element indicates the cells at the BTS on whose paging channel(s) the
air-interface message is to be sent.
c.
This element is included if the BSC wants a Layer 2 acknowledgment from

the MS.
12
13
If this element is included in this message, the value shall be returned in the
Abis-PCH Msg Transfer Ack message.
10
11
a.
8
9
14
d. Either IMSI or ESN, but not both is included. (Only one instance of Mobile
ID should be allowed)
15
e.
16
17
18
19
The BSC includes this element in this message when it wants to be

informed that a layer 2 ack was received from the MS. The BTS will use the
Abis-PCH Msg Transfer Ack message to notify the BSC that the layer 2 ack
was received. This element should not be included if the Abis Ack
Requested IE is absent.
20
21
89
A.S0003-Av2.0
The following table shows the bitmap layout for the Abis-PCH Msg Transfer
message:
Message Type = [8CH]
Correlation ID:
Octet
Length = [04H]
(MSB)
3
4
5
(LSB)

Odd/even
Indicator
2
Type of Identity
= [110] (IMSI)
= [1,0]
n+1
Length = [05H]
Odd/even
Indicator
Type of Identity
= [101] (ESN)
= [0]
(MSB)
4
ESN = <any value>
5
6
(LSB)
Cell Identifier List:
A1 Element Identifier = [1AH]
7
1
Length = <variable>
Cell Identification {1+:

(MSB)
Cell = [001H-FFFH]
(LSB)
} Cell Identification
90
j
j+1
A.S0003-Av2.0
Air Interface Message:
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:
Length = [01H]
Reserved = [0000 000]
Abis Ack Notify:
Length = [00H]
1
2
91
k
1
2
Layer 2
Ack
= [0/1]
1
2
1
2
3
4
6.2.4
A.S0003-Av2.0
This Abis interface message is sent from the BTS to the BSC to report the results of
sending an air interface message on the specified paging when a layer 2 acknowledgment
had been requested by the BSC.
Information Element
Section
Element Direction
Type
Reference
Message Type
7.2
BTS -> BSC
Correlation ID
7.3
BTS -> BSC
Cause
7.9
BTS -> BSC
BTS L2 Termination
7.30
BTS -> BSC
O
O
a
b
a.
This element is included if the Abis-PCH Msg Transfer contained this element.
It contains the value received on that message.
b.
Inclusion of this element indicates a failure to send the paging channel message
as requested in the Abis-PCH Msg Transfer message. Allowable cause values:
OAM&P intervention, Equipment failure, SMS Message too long for delivery
on the paging channel.
6
7
8
9
10
11
12
13
The following table shows the bitmap layout for the Abis-PCH Msg Transfer Ack
message:
7
Message Type = [8DH]
Correlation ID:
Octet
Length = [04H]
(MSB)
3
4
5
(LSB)
Cause:

Length = [01H]
ext = [0]
Cause Value =
[07H (OAM&P intervention),
20H (equipment failure),
71H (SMS Message too long for delivery on the paging channel)]
92
6
1
2
3
A.S0003-Av2.0
BTS L2 Termination:
Length = [01H]
Reserved = [0000 000]
2
BTS
L2
Termi
natio
n
=
[0/1]
93
A.S0003-Av2.0
1
2
6.2.5
Abis-BTS Setup
3
4
5
This Abis interface message is sent from the BSC to the BTS in order to request the BTS
to assign radio resource, the attributes of which are defined within the message.
Information Element
Section
Element
Type
Reference
Direction
Message Type
7.2
BSC -> BTS
Call Connection Reference
7.10
BSC -> BTS
Band Class
7.11
BSC -> BTS
Privacy Info
7.12
BSC -> BTS
SDU-ID
7.14
BSC -> BTS
7.4
BSC -> BTS
7.4
BSC -> BTS
Physical Channel Info
7.15
BSC -> BTS
Service Option
7.17
BSC -> BTS
Og
PACA Timestamp
7.18
BSC -> BTS
Oa
Quality of Service Parameters
7.19
BSC -> BTS
Ob
Abis Connect Information
7.20
BSC -> BTS
Oc, e
Abis Originating ID
7.21
BSC -> BTS
Od
7.24
BSC -> BTS
CDMA Target One Way Delay
7.30
BSC -> BTS
Walsh Code Assignment Request
7.31
BSC -> BTS
Of
a.
This element may be present only when the call is eligible for PACA service.
b.
This element may be 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.
c.
This element may be used to indicate a code channel that is allocated by the BSC.
It is assumed that the Cell Info Record is used and 0 fills the rest of the fields.
d.
This element is optionally included by the BSC. If included, the value shall be
saved and used by the BTS in subsequent Abis message for this call association.
e.
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
8
9
10
11
12
13
14
15
16
94
A.S0003-Av2.0
ignored in the Cell Information Record: QOF_Mask, PWR_Comb_Ind, Pilot_PN,

Code Channel.
2
3
f.
This element is included when the BSC requests the BTS for assignment of the
Walsh code. If this element is included, Code Channel field of the Abis Connect
Information IE is invalid.
g.
The Service option is set to the service option received in the Origination or
Paging Response message from MS.
4
5
6
7
8
9
95
A.S0003-Av2.0
The following table shows the bitmap layout for the Abis-BTS Setup message:
7
Octet
Message Type = [80H]
Call Connection Reference: A1 Element Identifier = [3FH]
Length = [08H]
(MSB)
Market ID = <any value>
3
(LSB)
(MSB)
Generating Entity ID = <any value>
4
5
(LSB)
(MSB)
6
7
Call Connection Reference = <any value>
8
9
(LSB)
Band Class:

Length = [01H]
Reserved = [000]
Privacy Info:
10
Band Class = [ 00001 (PCS)

00010 (TACS)
00011 (JTACS)
00100 (Korean PCS)
00101 (NMT-450)
00110 (IMT-2000)]
A3/A7 Element Identifier = [1DH]
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
SDU ID: A3/A7 Element Identifier = [4CH]

Length = <variable>
(MSB)
SDU ID = <any value>
(LSB)
96
m
1
A.S0003-Av2.0

Odd/even
Indicator
2
Type of Identity
= [110] (IMSI)
= [1,0]
n+1
Length = [05H]
Odd/even
Indicator
Type of Identity
= [101] (ESN)
= [0]
(MSB)
4
ESN = <any value>
5
6
(LSB)
Physical Channel Info:
A3 Traffic Channel Protocol

Stack = [001]
Length =[05H]
Frame Offset = [00H FFH]
Pilot Gating Rate

= [00, 01, 10]
ARFCN (high part)

= [000-111]
Count of Physical Channels = [01H-02H]
OTD=
[0,1]
Count of Physical Channels =

[001 010]
Service Option:
(MSB)

Service Option
= [0000H - XXXXH]
PACA Timestamp:
2
(LSB)
A1 Element Identifier = [4EH]
Length = [04H]
(MSB)
6
7
Physical Channel 1 =
0H IS-95,
1H FCH,
2H SCH,
3H DCCH
0H N/A,
1H FCH,
2H SCH,
3H DCCH
ARFCN (low part) = [00H-FFH]

Reserved = [0000]
3
1
2
3
97
A.S0003-Av2.0
PACA Queuing Time = <any value>
4
5
(LSB)
Quality of Service Parameters:
Length = [01H]
Reserved = [0000]
Abis Connect Information{1+:
1
2
Packet Priority = [0000 1101]
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),
New A3
Indicator
= [0,1]
(exist,new)
3H Dedicated Control Channel(DCCH)],

Length of Cell Info Record = <variable>
Cell Info Record {1+:

(MSB)
Cell = [001H-FFFH]
(LSB)
Reserved = [000]
j+1
QoF Mask =
[00, 01, 10, 11]
New
Cell
Indicator
PWR_
Comb
_Ind
= [0,1]
= [0,1]
(old, new)
(no,yes)
Pilot_PN = <any value>
j+2
(MSB)
(LSB)
k+1
Code Channel = [00H - FFH]
k+2
Length of Traffic Circuit ID = [05H]
Length of Traffic Circuit Identifier = [02H]
} Cell Info Record

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]
98
A.S0003-Av2.0
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)
Length of A3 Originating ID = [02H]

(MSB)
r+1
A3 Originating ID = <any value>
r+2
(LSB)
Length of A7 Destination ID = [02H]

(MSB)
r+3
r+4
A7 Destination ID = <any value>
r+5
(LSB)
r+6
}Abis Connect Information
Abis Originating ID:
Length of Abis Originating ID = [02H]

(MSB)
Abis Originating ID = <any value>
2
(LSB)
Length = [05H]
Cell Identification
(MSB)
(MSB)
Cell = [001H-FFFH]
99
1
2
Discriminator = [02H]
(LSB)
3
4
5
6
A.S0003-Av2.0
(LSB)
CDMA Target One Way Delay:
Abis Element Identifier = [0BH]
7
1
Length = [02H]
CDMA Target One Way Delay (high part)
CDMA Target One Way Delay (low part)
Walsh Code Assignment Request:

Length = [00H]
1
2
100
1
2
A.S0003-Av2.0
6.2.6
Abis-BTS Setup Ack

This message is sent from BTS to BSC to acknowledge the Abis-BTS Setup.
Information Element
Section
Reference
7.2
BTS -> BSC
7.10
BTS -> BSC
7.20
BTS -> BSC
Abis Originating ID
7.21
BTS -> BSC
Oa
Abis Destination ID
7.22
BTS -> BSC
Ob
Cause
7.9
BTS -> BSC
Oc
a.
This element is optionally included by the BTS. If included, the value

shall be saved and used by the BSC in subsequent Abis message for
this call association.
b.
This element is required if an Abis Originating ID value was included

in the corresponding Abis-BTS Setup message
c.
Inclusion of this element indicates failure of the Abis-BTS Setup

message. Allowable cause values: No radio resource available.
8
9
10
Type
Message Type
Element
Direction
11
12
101
A.S0003-Av2.0
The following table shows the bitmap layout for the Abis-BTS Setup Ack message:
Octet
Length = [08H]
(MSB)
3
(LSB)
(MSB)
4
5
(LSB)
(MSB)
6
7
8
9
(LSB)
Abis Connect Information{1+:
A3/A7 Element Identifier = [1BH]
Length = <variable>
Reserved = [000]
10
1
2

2H Supplemental Channel (SCH),
New A3
Indicator
= [0,1]
(exist,new)
3H Dedicated Control Channel(DCCH)],


(MSB)
Cell = [001H-FFFH]
(LSB)
Reserved = [000]
j+1
QoF Mask =
[00, 01, 10, 11]
New
Cell
Indicator
PWR_
Comb
_Ind
= [0,1]
= [0,1]
(old, new)
(no,yes)
j+2
(MSB)
(LSB)
k+1
k+2
Length of Traffic Circuit ID = [05H]
} Cell Info Record

102
A.S0003-Av2.0
(MSB)
3
(LSB)
(AAL2 CID)

[0H-FH]

[0H-FH]
p+1

[0H-FH]

[0H-FH]
p+2
T_Add (low order)
p+3
= [00-11]
= [0H-FH]
= [0H-FH]
Reserved = [0000]
p+4
p+5
= [0H-FH]
Reserved = [00]
- 11 1111]
p+6
Reserved = [00]
11 1111]
p+7
Reserved = [00]
- 11 1111]
p+8
p+9

(MSB)
q+1
(LSB)
Length of A3 Originating ID = [02H]

(MSB)
r+1
r+2
(LSB)

(MSB)
r+3
r+4
r+5
(LSB)
r+6
}Abis Connect Information
Length of Abis Originating ID = [02H]
103
1
2
(MSB)
A.S0003-Av2.0
Abis Originating ID = <any value>
3
(LSB)
Abis Destination ID:
Length of Abis Destination ID = [02H]

(MSB)
Abis Destination ID = <any value>
3
(LSB)
Cause:

Length = [01H]
Ext = [0]
Cause Value = [21H (No radio resource available)]
1
2
104
4
1
2
3
A.S0003-Av2.0
6.2.7
Abis-BTS Release
2
3
4
This message is sent from BSC to BTS to instruct the BTS to release the associated
dedicated resource.
Information Element
Section
Reference
Element
Direction
Type
Message Type
7.2
BSC -> BTS
7.10
BSC -> BTS
7.5
BSC -> BTS
Correlation ID
7.3
BSC -> BTS
5
6
The following table shows the bitmap layout for the Abis-BTS Release message:
7
Octet
Length = [08H]
(MSB)
3
(LSB)
(MSB)
4
5
(LSB)
(MSB)
6
7
8
9
(LSB)
10
1
Length = <variable>

(MSB)
Cell = [001H-FFFH]
(LSB)
j
j+1
Correlation ID:
Length = [04H]
(MSB)
1
2
3
105
A.S0003-Av2.0
5
(LSB)
1
2
106
A.S0003-Av2.0
6.2.8
This message is sent from the BSC to the BTS to acknowledge the Abis-BTS Release.
Information Element
Section
Reference
Element
Direction
Type
Message Type
7.2
BSC -> BTS
7.10
BSC -> BTS
Correlation ID
7.3
BSC -> BTS
4
5
The following table shows the bitmap layout for the Abis-BTS Release Request Ack message:
Length = [08H]
(MSB)
3
(LSB)
(MSB)
Octet
4
5
(LSB)
(MSB)
6
7
8
9
(LSB)
Correlation ID:
10
1
Length = [04H]
(MSB)
3
4
5
(LSB)
6
7
8
107
6.2.9
2
3
4
Abis-Burst Request
This Abis interface message is sent from the BSC to the BTS to request the reservation of
resources in support of a traffic burst.
Information Element
A.S0003-Av2.0
Section
Reference
Element Direction
Type
Message Type
7.2
BSC -> BTS
7.10
BSC -> BTS
Band Class
7.11
BSC -> BTS
Downlink Radio Environment
7.23
BSC -> BTS
7.24
BSC -> BTS
Privacy Info
7.12
BSC -> BTS
Correlation ID
7.3
BSC -> BTS
SDU ID
7.14
BSC -> BTS
7.4
BSC -> BTS
7.4
BSC -> BTS
7.5
BSC -> BTS
Forward Burst Radio Info
7.25
BSC -> BTS
Reverse Burst Radio Info
7.26
BSC -> BTS
Abis Destination ID
7.22
BSC -> BTS
O
O
O
O
O
O
O
O
f
a
b
b
c
d
e
a.
Optionally included by the BSC. If included, the value shall be saved and
used by the target BS on Abis signaling messages.
b.
This element may be included for OA&M purposes.
c.
The list of cell identifiers shall be assumed by the target BTS to be in priority
order with the highest priority cell listed first.
d.
This element is only included when forward link radio resources are to be
allocated to the burst.
e.
This element is only included when reverse link radio resources are to be
allocated to the burst.
f.
If this element is included in this message, its value shall be returned in the
Abis-Burst Response message and used in the Abis-Burst Commit message.
9
10
11
12
13
14
15
108
A.S0003-Av2.0
g.
2
3
4
This element is required if an Abis Origination ID value was included in an

Abis-BTS Setup Ack message previously received from the BTS for this call
association.
The following table shows the bitmap layout for the Abis-Burst Request message:
7
Octet
Length = [08H]
(MSB)
3
(LSB)
(MSB)
4
5
(LSB)
(MSB)
6
7
8
9
(LSB)
Band Class:

Length = [01H]
Reserved = [000]
Band Class = [00001] (PCS)
Downlink Radio Environment:
10
Length = <variable>
Number of Cells = <variable>
Downlink Radio Environment {1+:

(MSB)
Cell = [001H-FFFH]
(LSB)
Reserved = [00]
Downlink Signal Strength Raw = [000000] (ignored)
(MSB)
j+1
k
k+1
(LSB)
k+2
} Downlink Radio Environment
(MSB)
Length = [08H]
Cell Identification Discriminator = [ 02H]
Cell = [001H-FFFH]
(LSB)
(MSB)
109
4
5
6
A.S0003-Av2.0
(LSB)
Privacy Info:
7
1
A3/A7 Element Identifier = [1DH]
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
Correlation ID:
A3/A7
Element Identifier = [13H]
Length = [04H]
(MSB)
3
4
5
(LSB)

Length = [01H to 06H]
(MSB)
(LSB)

Odd/even
Indicator
M
1
2
Type of Identity
= [110] (IMSI)
= [1,0]
n+1
Length = [05H]
Odd/even
Indicator
1
2
Type of Identity
= [101] (ESN)
= [0]
(MSB)
110
A.S0003-Av2.0
ESN = <any value>
5
6
(LSB)
7
1
Length = <variable>
Cell Identification{1+:
(MSB)
Cell = [001H-FFFH]
(LSB)
j+1
Forward Burst Radio Info:
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:
Length = [04H]
Coding Indicator
7
8
1
2
Reserved = [00 0000]
= [00, 01]
Reserved
Reverse Supplemental Channel Rate
= [0000]
= [0000 1111]
Reverse Supplemental Channel Start Time = [00H FFH]

Reserved
Start Time Unit
Reverse Supplemental Channel Duration
= [0]
= [000 111]
= [0000 1111]

(MSB)
111
4
5
6
1
2
3
A.S0003-Av2.0
(LSB)
1
112
A.S0003-Av2.0
6.2.10
Abis-Burst Response
This Abis interface message is sent from the BTS to the BSC to respond to a request for
reservation of resources to support a traffic burst. Note that one or more Abis-Burst
Response messages may be used to respond to a single Abis-Burst Request message. A
result (committed or uncommitted) shall be provided for all cells in the Abis-Burst
Request message. Each Abis-Burst Response message includes at most one committed
cell.
3
4
5
6
7
8
9
Information Element
10
Section
Element Direction
Reference
Message Type
7.2
BTS -> BSC
7.10
BTS -> BSC
Correlation ID
7.3
BTS -> BSC
Cell Identifier List (Committed)
7.5
BTS -> BSC
Cell Identifier List (Uncommitted)
7.5
BTS -> BSC
7.25
BTS -> BSC
7.26
BTS -> BSC
Abis Destination ID
7.22
BTS -> BSC
O
O
b
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.
d.

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.
18
19
23
c.
17
22

information about forward link radio resources that have been
reserved at the cell indicated in the Cell Identifier List (Committed)
element.
15
21
b.
14
20
If this element was included in the Abis-Burst Request message, the

value shall be returned in this message.
13
16
a.
11
12
Type
113
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.
f.
This element is required if an Abis Origination ID value was included

in an Abis-BTS Setup message previously received from the BSC for
this call association.
2
3
4
5
6
7
8
9
10
A.S0003-Av2.0
11
114
A.S0003-Av2.0
The following table shows the bitmap layout for the Abis-Burst Response message:
Octet
Length = [08H]
(MSB)
3
(LSB)
(MSB)
4
5
(LSB)
(MSB)
6
7
8
9
(LSB)
Correlation ID:
A3/A7
10
1
Length = [04H]
(MSB)
3
4
5
(LSB)
Cell Identifier List (committed):
6
1
Length = <variable>

(MSB)
Cell = [001H-FFFH]
(LSB)
j
j+1
Cell Identifier List (uncommitted):
Length = <variable>
-- Continued on next page -2
115
A.S0003-Av2.0
-- Continued from previous page -Cell Identification {1+:

(MSB)
Cell = [001H-FFFH]
(LSB)
j+1
Length = [06H]
Coding Indicator
Reserved
QOF Mask
= [00, 01]
= [0]
= [00 11]
2
(high part)
= [000 111]
Pilot PN
Code (high
part)
Reserved
= [000]
= [0000 1111]
[0,1]
Reserved
= [000]
= [0 0000 1 1111]
Reserved
Start Time Unit
= [0]
= [000 111]
= [0000 1111]
8
1
Length = [04H]
Coding Indicator
= [00, 01]
Reserved
= [0000]
= [0000 1111]
Reserved
Start Time Unit
= [0]
= [000 111]
= [0000 1111]
3
(LSB)
116
6
1
Length of Abis Destination = [02H]

(MSB)
A.S0003-Av2.0
1
2
6.2.11
Abis-Burst Commit
This Abis interface message is sent from the BSC to the BTS to commit a set of resources
that had been reserved to support a traffic burst.
4
5
Information Element
Section
Element Direction
Reference
Message Type
7.2
BSC -> BTS
7.10
BSC -> BTS
Correlation ID
7.3
BSC -> BTS
Cell Identifier List (Forward)
7.5
BSC -> BTS
Ob
Cell Identifier List (Reverse)
7.5
BSC -> BTS
Ob
7.25
BSC -> BTS
Oc, h
7.26
BSC -> BTS
Od, h
IS-2000 Forward Power Control Mode
7.27
BSC -> BTS
Oe
IS-2000 FPC Gain Ratio Info
7.28
BSC -> BTS
Of
Abis Destination ID
7.22
BSC -> BTS
The length field of this element shall be set to 0 if no resources are

to be allocated in the indicated direction.
c.
This element is only included when forward link radio resources are
to be allocated to the burst.
d.
This element is only included when reverse link radio resources are
to be allocated to the burst.
e.
This element shall be included when supporting a secondary power

control sub-channel. It provides information used for forward gain
equalization for the SCH.
f.
This element shall be included when supporting a secondary power

control sub-channel 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.
13
14
15
16
17
18
19
20
b.
11
12
Optionally included by the BSC. If included, the value shall be

saved and used by the target BTS on Abis signaling messages.
9
10
a.
7
8
Type
117
g.
This element is required if an Abis Originating ID value was included

in an Abis BTS Setup Ack message previously received from the
BTS for this call association.
h.
Walsh code in this IE is used as obtained from the Abis-Burst

Response message, but the rate could be downgraded in this message.
2
3
4
5
A.S0003-Av2.0
6
7
8
9
10
11
12
13
14
Note: In the Abis-Burst commit message, Walsh codes are used as

obtained from the Abis-Burst Response message, but the rate could
be downgraded in the Abis-Burst commit message by the BSC. Thus
the BSC chooses the Walsh code that determines the actual rate for
the traffic burst. However, if the BSC chooses a Walsh code other
than the one allocated by the BTS, it shall do so only to reduce the
burst rate. The new Walsh code in the Burst Commit message shall
be derived from the Walsh code in the Burst Response Message.
15
118
A.S0003-Av2.0
The following table shows the bitmap layout for the Abis-Burst Commit message:
Octet
Length = [08H]
(MSB)
3
(LSB)
(MSB)
4
5
(LSB)
(MSB)
6
7
8
9
(LSB)
Correlation ID:
A3/A7
10
1
Length = [04H]
(MSB)
3
4
5
(LSB)
Cell Identifier List (Forward):
6
1
Length = <variable>

(MSB)
Cell = [001H-FFFH]
(LSB)
j
j+1
Cell Identifier List (Reverse):
Length = <variable>
119
A.S0003-Av2.0
-- Continued from previous page -Cell Identification {1+:

(MSB)
Cell = [001H-FFFH]
(LSB)
j+1
Length = [06H]
Coding Indicator
Reserved
QOF Mask
= [00, 01]
= [0]
= [00 11]
1
2

(high part)
= [000 111]
Pilot PN
Code (high
part)
Reserved
= [000]
= [0000 1111]
[0,1]
Reserved
= [000]
= [0 0000 1 1111]
Reserved
Start Time Unit
= [0]
= [000 111]
= [0000 1111]
Length = [04H]
Coding Indicator
7
8
1
2
= [00, 01]
Reserved
= [0000]
= [0000 1111]

Reserved
Start Time Unit
= [0]
= [000 111]
= [0000 1111]
IS-2000 Forward Power Control Mode:
Length = [02H]
Reserved = [0000 0]
FPC_MODE = [000 011]
IS-2000 FPC Gain Ratio Info:
5
6
1
2
ACTION_TIME = [00H] (ignored)
3
4
1
Length = [08H]
Initial Gain Ratio = [00H FFH]
120
A.S0003-Av2.0
Reser
ved =
[0]
Gain Adjust Step Size = [0H FH]
Count of Gain Ratio Pairs =

[011]
Min Gain Ratio 1 = [00H FFH]
Max Gain Ratio 1 = [00H FFH]
10

(MSB)
3
(LSB)
1
2
3
121
6.2.12
A.S0003-Av2.0
Abis-Connect
2
3
This message uses the same format as the A3-Connect message modified to include
Physical Channel Info IE as shown below.
Information Element
Section
Reference
Element
Direction
Type
Message Type II
6.2.2.5
BTS -> SDU
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
Rc,d
6.2.2.14
BTS -> SDU
a.
If this element is included in this message, it shall be returned in the

A3-Connect Ack message.
b.
If this element was included in the A7-Handoff Request message, it is

required in this message.
c.
At least one instance of this element is required in this message.

Multiple instances of this element may be present in this message.
c.
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.
6
7
8
9
10
11
12
13
14
15
16
The following table shows the bitmap layout for the A3-Connect message modified to include Physical Channel Info IE.
Message Type II = [01H]
Length = [08H]
(MSB)
3
(LSB)
(MSB)
Octet
5
(LSB)
(MSB)
4
6
7
122
A.S0003-Av2.0
8
9
(LSB)
123
10
A.S0003-Av2.0
-- Continued from previous page -
Correlation ID:
Length = [04H]
(MSB)
3
4
5
(LSB)

Length = [01H to 06H]
(MSB)
(LSB)
n
1
A3 Connect Information{1+: A3/A7 Element Identifier = [1BH]

Length = <variable>
Reserved = [000]

2H Supplemental Channel (SCH)
3H Dedicated Control Channel
(DCCH)],
New A3
Indicator
= [0,1]
(exist,new)

(MSB)
Cell = [001H-FFFH]
(LSB)
Reserved = [000]
j+1
QoF Mask =
[00, 01, 10, 11]
New
Cell
Indicator
= [0,1]
= [0,1]
(old, new)
(no,yes)

} Cell Info Record
124
PWR_
Comb
_Ind
j+2
(MSB)
(LSB)
k+1
k+2
A.S0003-Av2.0
-- Continued from previous page -Length of Traffic Circuit ID = [05H]

(MSB)
3
(LSB)
(AAL2 CID)

[0H-FH]

[0H-FH]
p+1

[0H-FH]

[0H-FH]
p+2
T_Add (low order)
p+3
= [00-11]
= [0H-FH]
= [0H-FH]
Reserved = [0000]
p+4
p+5
= [0H-FH]
Reserved = [00]
- 11 1111]
p+6
Reserved = [00]
11 1111]
p+7
Reserved = [00]
- 11 1111]
p+8
p+9

(MSB)
q+1
(LSB)
125
A.S0003-Av2.0
-- Continued from previous page -Length of A3 Originating ID = [02H]

(MSB)
r+1
(LSB)

(MSB)
r+2
s
s+1
(LSB)
s+2
}A3 Connect Information
Physical Channel Info:
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]
0H IS-95,
1H FCH,
2H SCH,
3H DCCH
0H N/A,
1H FCH,
2H SCH,
3H DCCH
2
3
4
126
6
7
A.S0003-Av2.0
6.2.13
Abis-Connect Ack
This message is used in the same format as the A3-Connect Ack message.
Refer to section 6.1.9.2, "A3-Connect Ack", TIA/EIA/IS-2001
4
5
In this case, message type M in A3 message will change to read R, and C to read
O.
6.2.14
Abis-Remove
This message is used in the same format as the A3-Remove message.
Refer to section 6.1.9.3, "A3-Remove", TIA/EIA/IS-2001
9
10
11
O.
6.2.15
Abis-Remove Ack
12
This message is used in the same format as the A3-Remove Ack message.
13
Refer to section 6.1.9.4, "A3-Remove Ack", TIA/EIA/IS-2001
14
15
O.
16
6.2.16
17
This message is used in the same format as the A3-IS-2000 FCH Forward message.
18
Refer to section 6.1.9.9, "Abis-IS-2000 FCH Forward", TIA/EIA/IS-2001
19
20
O.
21
6.2.17
22
This message is used in the same format as the A3-IS-2000 FCH Reverse message.
23
Refer to section 6.1.9.10, "A3-IS-2000 FCH Reverse", TIA/EIA/IS-2001
24
25
O.
26
6.2.18
27
This message is used in the same format as the A3-Traffic Channel Status message.
28
Refer to section 6.1.9.15, "A3-Traffic Channel Status", TIA/EIA/IS-2001
29
30
O.
31
32
6.2.19

This message is sent from the BTS to the BSC to request de-allocation of resources.
127
A.S0003-Av2.0
Information Element
Section
Reference
Element
Direction
Type
Message Type
7.2
BTS -> BSC
7.10
BTS -> BSC
Cause
7.9
BTS -> BSC
Manufacturers Specific Records
7.7
BTS -> BSC
2
3
The following table shows the bitmap layout for the Abis-BTS Release Request message:
Octet
Length = [08H]
(MSB)
3
(LSB)
(MSB)
4
5
(LSB)
(MSB)
6
7
8
9
(LSB)
Cause:

Length = [01H]
ext = [0]
10
1
2
Cause Value =
[07H (OAM&P intervention),

10H (Packet Data Going Dormant),
20H (equipment failure)]
Manufacturers Specific Records:
Length = [variable]
Manufacturer ID = [00H FFH]
Manufacturers specific information
128
A.S0003-Av2.0
6.2.20
Abis-IS-2000 SCH Fwd
This message is used in the same format as the A3-IS-2000 SCH Forward message.
Refer to section 6.1.9.16, "A3-IS-2000 SCH Forward", TIA/EIA/IS-2001.
4
5
O.
6.2.21
Abis-IS-2000 SCH Rvs
This message is used in the same format as the A3-IS-2000 SCH Reverse message.
Refer to section 6.1.9.17, "A3-IS-2000 SCH Forward", TIA/EIA/IS-2001.
9
10
11
O.
6.2.22
Abis-IS-2000 DCCH Fwd
12
This message is used in the same format as the A3-IS-2000 DCCH Forward message.
13
Refer to section 6.1.9.13, "A3-IS-2000 DCCH Forward", TIA/EIA/IS-2001.
14
15
O.
16
6.2.23
Abis-IS-2000 DCCH Rvs
17
This message is used in the same format as the A3-IS-2000 DCCH Reverse message.
18
Refer to section 6.1.9.14, "A3-IS-2000 DCCH Forward", TIA/EIA/IS-2001.
19
20
21
O.
22
23
6.2.24
24
25
Abis-PACA Update
This Abis interface message is sent from the BSC to the BTS to update PACA related
information at the BTS.
26
Information Element
27
28
Section
Reference
Element
Direction
Type
Message Type
7.2
BSC -> BTS
7.10
BSC -> BTS
7.4
BSC -> BTS
BTS PACA Order
7.32
BSC -> BTS
Oa
a.
This element identifies the PACA action to be taken.
The following table shows the bitmap layout for the Abis-PACA Update message:
129
A.S0003-Av2.0
Octet
Message Type = [6EH]
Length = [08H]
(MSB)
3
(LSB)
(MSB)
4
5
(LSB)
(MSB)
6
7
8
9
(LSB)

Odd/even
Indicator
10
1
2
Type of Identity
= [110] (IMSI)
= [1,0]
n+1
BTS PACA Order:
A1 Element Identifier = [5FH]
Length = [02H]
Reserved
2
PACA Action Required
2
3
130
A.S0003-Av2.0
7. Information Element Definitions
7.1
Information Element Identifiers
4
5
6
The following table contains lists of all elements that make up the messages defined in
Chapter 7. The table includes the Information Element Identifier (IEI) coding which
distinguished one element from another.
7
8
Table 7.1-1 Abis Information Element Identifiers Sorted by Identifier value

Element Name
Identifier
(unused value available)
01H-02H
Interface(s)
Reference
Service Option
03H
Abis, A1
7.17
Cause
04H
Abis, A1
7.9
05H
06H
07H
Abis, A1
7.19
Abis Cell Info
08H
Abis
7.16
(Note: This Information Element is same with

A7 Cell Info IE in TIA/EIA/IS-2001.)
09-0AH
0BH
Abis
7.30
0CH
Abis, A1, A7
7.24
Mobile Identity
0DH
Abis, A1, A7
7.4
0E-10H
11H
Abis, A7
7.25
12H
Abis, A7
7.26
Correlation ID
13H
Abis, A3, A7
7.3
IS-2000 Power Control Mode
14H
Abis, A3
7.27
15H
Abis, A7
7.28
Abis, A1, A7
7.13
Abis, A7
7.12
Abis, A7
7.6

Privacy Info
16-19H
1AH
1B-1CH
1DH
1EH-20H
21H
131
A.S0003-Av2.0
22H
23H
24H
29H
2A-3EH
3FH
40H
Authentication Challenge Parameter
41H
4CH
4DH
PACA Timestamp
4EH
Band Class
PACA Order
7.8
Abis, A1, A7
7.23
Abis, A1, A3,

A7
7.10
Abis, A1
7.33
Abis, A3, A7
7.14
Abis, A1
7.18
Abis, A1, A7
7.11
Abis, A1
7.32
42-4BH
SDU ID
Abis, A7
4F-5CH
5DH
5E
5FH
60-70H
Abis From ID
71H
Abis
7.21
Abis To ID
72H
Abis
7.22
BTS L2 Termination
73H
Abis
7.29
Walsh Code Assignment Request
74H
Abis
7.31
Abis Ack Notify
75H
Abis
7.34
All other values are reserved.

1
2
132
A.S0003-Av2.0
7.2
Message Type
2
3
4
The Message Type element is used to indicate the type of a message on the Abis
interfaces.
Element Format:
6
5
Octet
Message Type
6
7
Table 7.2-1 Abis Message Type Values

Message
Type
Value
Interface
Abis-Connect
01H
Abis Signaling
Abis-Connect Ack
02H
Abis Signaling
Abis-Remove
03H
Abis Signaling
Abis-Remove Ack
04H
Abis Signaling
Message Name
Section
Reference
05H-0AH
0BH
Abis Traffic
6.2.16
0CH
Abis Traffic
6.2.17
0DH
Abis Traffic
6.2.18
Abis-IS-2000 DCCH Fwd
0EH
Abis Traffic
6.2.22
Abis-IS-2000 DCCH Rvs
0FH
Abis Traffic
6.2.23
Abis-IS-2000 SCH Fwd
10H
Abis Traffic
6.2.20
Abis-IS-2000 SCH Rvs
11H
Abis Traffic
6.2.21
12H-6DH
Abis-PACA-Update
6EH
6FH-7FH
133
Abis Signaling
6.32
A.S0003-Av2.0
(cont.) - Abis Message Type Values
Message Name
Message
Type
Value
Interface
Section
Reference
Abis-BTS Setup
80H
Abis Signaling
6.2.5
Abis-BTS Setup Ack
81H
Abis Signaling
6.2.6
Abis-BTS Release
82H
Abis Signaling
6.2.7
83H
Abis Signaling
6.2.8
84H
Abis Signaling
6.2.19
85H-8BH
Abis-PCH Msg. Transfer
8CH
Abis Signaling
6.2.3
Abis-PCH Msg. Transfer Ack
8DH
Abis Signaling
6.2.4
Abis-ACH Msg. Transfer
8EH
Abis Signaling
6.2.1
Abis-Burst Request
90H
Abis Signaling
6.2.9
Abis-Burst Response
91H
Abis Signaling
6.2.10
Abis-Burst Commit
92H
Abis Signaling
6.2.11
All other values are reserved.
7.3
Correlation ID
Refer to section 6.2.2.108, Correlation ID, TIA/EIA/IS-2001.
7.4
Refer to section 6.2.2.16, Mobile Identity, TIA/EIA/IS-2001.
7.5
10
11
12
13
Mobile Identity
Cell Identifier
Refer to section 6.2.2.20, Cell Identifier, TIA/EIA/IS-2001.
7.6

Refer to section 6.2.2.152, Air Interface Message, TIA/EIA/IS-2001. ARQ fields
exchanged on an air-interface is not included in this information element.
134
A.S0003-Av2.0
7.7
UNUSED SECTION
7.8
3
4
5
Refer to section 6.2.2.153, Layer 2 Ack Request/Results, TIA/EIA/IS-2001.
7.9
7
8
Refer to section 6.2.2.19, Cause, TIA/EIA/IS-2001.
7.10
10
11
12
7.11
7.12
7.13
23

Refer to section 6.2.2.21, Cell Identifier List, TIA/EIA/IS-2001.
7.14
21
22
Privacy Info
Refer to section 6.2.2.143, Privacy Info, TIA/EIA/IS-2001.
18
19
20
Band Class
Refer to section 6.2.2.106, Band Class, TIA/EIA/IS-2001.
15
16
17

Refer to section 6.2.2.98, Call Connection Reference, TIA/EIA/IS-2001.
13
14
Cause
SDU ID
Refer to section 6.2.2.91, SDU ID, TIA/EIA/IS-2001.
7.15

Refer to section 6.2.2.14, Physical Channel Info, TIA/EIA/IS-2001.
135
7.16
Cell Information Record
2
3
Refer to section 6.2.2.89, Cell Information Record, TIA/EIA/IS-2001.
7.17
Service Option
Refer to section 6.2.2.66, Service Option, TIA/EIA/IS-2001.
7.18
PACA Timestamp
Refer to section 6.2.2.149, PACA Timestamp, TIA/EIA/IS-2001.
7.19
9
10
11
Refer to section 6.2.2.54, Quality of Service Parameters, TIA/EIA/IS-2001.
7.20
12
13
A.S0003-Av2.0
Refer to section 6.2.2.144, A3 Connect Information, TIA/EIA/IS-2001.
7.21
Abis Originating ID
14
This element contains an identifier chosen by the BSC (when the BSC sends an Abis
signaling message to the BTS) or BTS (when the BTS sends an Abis signaling message to
the BSC) for its own use in quickly processing Abis signaling messages received from the
BTS. For example, it may be used to identify the resources supporting the call
association that are internal to the BSC. If an Abis Originating ID is supplied by this BSC,
then the BTS includes this in the Abis Destination ID element in subsequent Abis
messages to this BSC.
15
16
17
18
19
20
21
(MSB)
Octet
Abis Element Identifier
Length
Abis Originating ID
3
(LSB)
136
A.S0003-Av2.0
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 8 octets.
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 8 octets long.
2
3
4
5
6
7
7.22
Abis Destination ID
9
10
11
This element contains an identifier chosen by the BSC (when the BSC sends an Abis
signaling message to the BTS) or BTS (when the BTS sends an Abis signaling message to
the BSC) for its own use in quickly processing Abis signaling messages.
12
13
If an Abis Originating ID was supplied by the BSC, then the BTS includes this value in
the Abis Destination ID element in subsequent Abis messages to the BSC.
14
(MSB)
Length
Abis Destination ID
3
(LSB)
15
This field indicates the number of octets in this element

following the Length field. The maximum value in
this version of this specification is 8 octets.
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 8 octets long.
17
19
20
21
22
7.23
23
24
25
26
Length:
16
18
Octet

Refer to section 6.2.2.25, Downlink Radio Environment, TIA/EIA/IS-2001.
7.24

Refer to section 6.2.2.79, CDMA Serving One Way Delay, TIA/EIA/IS-2001.
27
137
7.25
2
3
7.26

Refer to section 6.2.2.57, Reverse Burst Radio Info, TIA/EIA/IS-2001.
7.27
8
9
10

Refer to section 6.2.2.56, Forward Burst Radio Info, TIA/EIA/IS-2001.
5
6
A.S0003-Av2.0
IS-2000 Forward Power Control Mode

Refer to section 6.2.2.177, IS-2000 Forward Power Control Mode, TIA/EIA/IS-2001.
7.28
11

Refer to section 6.2.2.178, IS-2000 FPC Gain Ratio Info, TIA/EIA/IS-2001.
12
13
7.29
14
15
16
17
BTS L2 Termination
This information element is used to indicate whether the BTS terminates Layer 2 or not.
In this release of the Abis specification L2 termination is mandatory to be supported by
the BTS and may be supported by the BSC. Therefore BTS L2 termination shall be set
1 in this version.
6
5
4
3
2
1
0
Octet
Length
Reserved
18
21
22
Length:
The Length field is a binary value indicating the number of

octets following the Length field.
BTS L2 Termination:
This bit shall be set to 0 when the BTS dose not

terminate Layer 2, and be set to 1 when the BTS
terminates Layer 2.
19
20
BTS L2
Terminat
ion
23
138
A.S0003-Av2.0
7.30
2
3
The BSC uses this IE to send the CDMA Target One Way Delay to each target BTS
involved in soft handoff.
Octet
Length
CDMA Target One Way Delay (high part)
CDMA Target One Way Delay (low part)
5
6
7.31
Walsh Code Assignment Reqest
8
9
This information element indicates the Walsh code in the message that this IE is sent is
invalid.
10
Octet
Length
11
12
Length:
The Length field is set to 0.
13
14
15
7.32
PACA Order
16
The purpose of this element is for the BSC to instruct the BTS to take appropriate action
upon receiving the Abis-PACA Update message.
17
18
Octet
A1 Element Identifier
Length
Reserved
PACA Action Required
19
139
Length
This field shall be set to the length of this element in octets following
the Length field.
2
3
A.S0003-Av2.0
The PACA Action Required field is coded as follows:
4
PACA Action
Required
Description
Value (binary)
000
Reserved
001
Update Queue Position
010
Reserved
011
Remove MS from the queue
100
Reserved
101
Reserved
All other values reserved
5
6
Reserved
This field shall be set to 00000.
7.33
Authentication Challenge Parameter (RAND)
The Authentication Challenge Parameter information element provides a non-predictable

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.
10
11
Octet
A1 Element Identifier
Length
Reserved
Random Number Type
(MSB)
4
RAND Value
5-m
(LSB)
12
Length:
The Length field is a binary value indicating the number

of octets following the Length field.
13
14
m+1
Random Number Type:

Random Number Type
Value
Random Number Type
Random Number
Length
0001
RAND
32 bits
140
A.S0003-Av2.0
1
2
7.34
Abis Ack Notify
4
5
This information element is used to indicate whether the BSC wants to be informed that a
layer 2 ack was received from the MS.
7
8
Length:
Octet
Length
The Length field is a binary value indicating the number of

octets following the Length field.
9
10
141
A.S0003-Av2.0
8. Timer Definitions
Table 8-1 describes the parameters values for each timer. Refer to section 6.3 Timer
Definitions, TIA/EIA/IS-2001, for the MSC timers (T10, T301, T315, T3113).
3
4
Table 8-1 Timer Values and Range

Timer Name
Default Value
(seconds)
Tconnb
0.1
Range of
Values
(seconds)
0 1.0
Tsetupb
0.1
0 0.5
0.1
8.2
BSC
Tchanstatb
0.5
0 1.0
0.1
8.3
BSC
Tdisconb
0.1
0 1.0
0.1
8.4
BTS
Tdrptgtb
0.5
0 1.0
0.1
8.5
BSC
Tbstreqb
0.5
0 1.0
0.1
8.6
BSC
Tbstcomb
0.5
0 1.0
0.1
8.7
BTS
Trelreqb
0.1
0 1.0
0.1
8.8
BTS
Granularity
(seconds)
Section
Reference
Timer Location
0.1
8.1
BTS
5
6
8.1
8
9
Tconnb :Timer for Abis-Connect message

This BTS timer is started when the Abis-Connect message is sent, and stopped when the
Abis-Connect Ack message is received.
10
11
8.2
12
13
Tsetupb : Timer for Abis-BTS Setup message

This BSC timer is started when the Abis-BTS Setup message is sent, and stopped when
the Abis-Connect message is received.
14
15
16
17
18
19
20
8.3
Tchanstatb : Timer for Abis-Traffic Channel Status message

The Tchanstatb timer is used by the BSC to wait for the Abis-Traffic Channel Status
message for all new cells on an Abis connection. This timer is started when the
Abis-Connect Ack message indicating that Abis-Traffic Channel Status messages are
requested is sent and stopped when Abis-Traffic Channel Status message(s) have been
received for all new cells on the Abis connection.
21
142
A.S0003-Av2.0
8.4
2
3
4
Tdisconb : Timer for Abis-Remove Ack message

The Tdisconb timer is used by the BTS to wait for the Abis-Remove Ack message. This
timer starts when the BTS sends Abis-Remove message, and stops when the BTS
receives the Abis-Remove Ack message.
8.5
7
8
9
Tdrptgtb : Timer for Abis-BTS Release Ack message

The Tdrptgtb timer is used by the BSC to wait for Abis-BTS Release Ack message. This
timer starts when the BSC sends the Abis-BTS Release message and stops when the BSC
receives the Abis-BTS Release Ack message.
10
11
8.6
12
13
14
Tbstreqb : Timer for Abis-Burst Response message

The Tbstreqb timer is used by the BSC to wait for Abis-Burst Response message. This
timer starts when the BSC sends the Abis-Burst request message and stops when the BSC
receives the Abis-BTS Release Ack message.
15
16
8.7
17
18
19
Tbstcomb : Timer for Abis-BTS Release Ack message

The Tbstcomb timer is used by the BTS to wait for Abis-Burst Commit message. This
timer starts when the BTS sends the Abis-BTS Release message and stops when the BTS
receives the Abis-Burst Commit message.
20
21
22
23
24
25
8.8
Trelreqb : Timer for Abis-BTS Release message

The Trelreqb timer is used by the BTS to wait for Abis-BTS Release message. This timer
starts when the BTS sends the Abis-BTS Release Request message and stops when the
BTS receives the Abis-BTS Release message.
26
143

A.S0003-Av2.0 TIA-828-A Abis Published PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

A.S0003-Av2.0 TIA-828-A Abis Published PDF

Uploaded by

Copyright:

Available Formats

BTS-BSC Inter-operability (Abis Interface)

BTS-BSC Inter-operability (Abis Interface)

based on this document.

should be directed to that Organizational Partner.

Requests for reproduction of this document should be directed to the 3GPP2

BTS-BSC Inter-operability (Abis Interface)

BTS-BSC Inter-operability (Abis Interface)

Abis-Connect Ack ........................................................................................................................ 25

BTS-BSC Inter-operability (Abis Interface)

Abis-ACH Msg Transfer .............................................................................................................. 86

BTS-BSC Inter-operability (Abis Interface)

Quality of Service Parameters....................................................................................................... 136

BTS-BSC Inter-operability (Abis Interface)

TABLE 4-1 LAYER 2 TERMINATION TYPE .............................................................................................. 6

BTS-BSC Inter-operability (Abis Interface)

Scope of the document

Following features are not specified in this version of the specification.

They are for

Operations, Administration, Maintenance, and Provisioning (OAM&P)*1

Abis Overload control

Inter BSC hard/soft handoff *2

*1 It is recommended that any OAM&P related information be aligned with the

*2 Inter BSC (BS) hard/soft handoff is supported in the TIA/EIA/IS-2001.

Telecommunications Industry Association (TIA) / Electronics Industry

TIA/EIA/IS-2001; Inter-operability Specification (IOS) for CDMA 2000 Access Network

TIA/EIA/IS-95B; Mobile Station - Base Station Compatibility Standard for Dual-Mode

BTS-BSC Inter-operability (Abis Interface)

International Telecommunications Union - Telecommunications Sector

ITU-T Recommendation I.363.2, B-ISDN ATM Adaptation layer specification: Type 2

ITU-T Recommendation I.363.5, B-ISDN ATM Adaptation Layer specification: Type 5

ITU-T Recommendation Q.2931, Broadband-Integrated Services Digital Network

BTS-BSC Inter-operability (Abis Interface)

ATM Adaptation Layer type 2

BTS-BSC Inter-operability (Abis Interface)

Packet Arrival Time Error

BTS-BSC Inter-operability (Abis Interface)

Network Reference Model and Interfaces

a) Abis interface = Abis signaling + Abis traffic

Figure 4-1 Reference Model

Table 4-1 Layer 2 termination type

BTS-BSC Inter-operability (Abis Interface)

sub-layer and SAR sub-layer.

In this specification type A is introduced as architecture for initial phase.

However we are also introducing

BTS-BSC Inter-operability (Abis Interface)

FCH (Abis-IS-2000 FCH Fwd/Rvs)

SCH (Abis-IS-2000 SCH Fwd/Rvs)

DCCH (f/r-dsch, f/r-dtch)

DCCH (Abis-IS-2000 DCCH Fwd/Rvs)

PCH (Abis-PCH Msg Transfer)

BTS-BSC Inter-operability (Abis Interface)

Table 4-2 summaries the details of the Abis interface

Table 4-2 Abis interface description

Abis connection - call setup

Support of user traffic connections to a frame selector function

Support of paging channel messaging

BTS-BSC Inter-operability (Abis Interface)

Support of Access channel messaging

Support of broadcast system information functions

Physical Layer Specification (Layer 1)

Use of ATM (Layer 2)

BTS-BSC Inter-operability (Abis Interface)

ATM Adaptation Layer