Abis Interface

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
2
3
9 BTS-BSC Inter-operability (Abis Interface)

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. Requests for reproduction of this document should be directed to the 3GPP2
26 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's documents
27 should be directed to that Organizational Partner. See www.3gpp2.org for more information.
28
A.S0003-Av2.0 BTS-BSC Inter-operability (Abis Interface)
1 Table of Contents
2 1. Introduction............................................................................................................................................ 2
3 2. Objectives................................................................................................................................................ 2
4 2.1 Scope of the document ......................................................................................................................... 2
5 2.2 References ............................................................................................................................................ 2
6 2.2.1 Telecommunications Industry Association (TIA) / Electronics Industry Association (EIA)........... 3
7 2.2.2 Standards Committee T1................................................................................................................ 3
8 2.2.3 International Telecommunications Union - Telecommunications Sector (ITU-T) ......................... 3
9 2.2.4 Other ............................................................................................................................................. 3
10 3. Terminology ............................................................................................................................................ 4
11 3.1 Acronyms ............................................................................................................................................. 4
12 3.2 Others ................................................................................................................................................... 5
13 4. Network Reference Model and Interfaces............................................................................................ 6
14 4.1 Support of user traffic connections to a frame selector function .......................................................... 9
15 4.2 Support of paging channel messaging .................................................................................................. 9
16 4.3 Support of Access channel messaging ................................................................................................ 10
17 4.4 Support of broadcast system information functions ........................................................................... 10
18 4.5 Layers 1 & 2 ....................................................................................................................................... 10
19 4.5.1 Physical Layer Specification (Layer 1) ....................................................................................... 10
20 4.5.2 Use of ATM (Layer 2) .................................................................................................................. 10
21 4.5.3 Field of Application..................................................................................................................... 10
22 4.5.4 ATM Layer................................................................................................................................... 11
23 4.5.5 ATM Adaptation Layer ................................................................................................................ 11
24 4.5.6 Network and Transport Protocols ............................................................................................... 11
25 5. Call Processing ..................................................................................................................................... 16
26 5.1 Mobile Originating Call ..................................................................................................................... 16
27 5.1.1 Abis-ACH Message Transfer ....................................................................................................... 16
28 5.1.2 Unused Section............................................................................................................................ 17
29 5.1.3 Abis-BTS Setup............................................................................................................................ 17
30 5.1.4 Abis-Connect ............................................................................................................................... 17
31 5.1.5 Abis-Connect Ack ........................................................................................................................ 17
32 5.1.6 Abis-BTS Setup Ack ..................................................................................................................... 18
33 5.1.7 Abis-IS-2000 FCH Forward........................................................................................................ 18
34 5.1.8 Abis-IS-2000 FCH Reverse ......................................................................................................... 19
35 5.1.9 Abis-PCH Msg Transfer .............................................................................................................. 19
36 5.1.10 Abis-PCH Msg Transfer Ack.................................................................................................... 20
37 5.1.11 Abis-Traffic Channel Status ..................................................................................................... 20
38 5.1.12 Successful Mobile Originating Call......................................................................................... 21
39 5.2 Mobile Terminated Call...................................................................................................................... 25
40 5.2.1 Abis-PCH Message Transfer ....................................................................................................... 25
41 5.2.2 Abis-PCH Message Transfer Ack ................................................................................................ 25
42 5.2.3 Abis-BTS Setup............................................................................................................................ 25
43 5.2.4 Abis-Connect ............................................................................................................................... 25
i
BTS-BSC Inter-operability (Abis Interface) A.S0003-Av2.0
1 5.2.5 Abis-Connect Ack ........................................................................................................................ 25

2 5.2.6 Abis-BTS Setup Ack ..................................................................................................................... 26
3 5.2.7 Abis-IS-2000 FCH Forward........................................................................................................ 26
4 5.2.8 Abis-IS-2000 FCH Reverse ......................................................................................................... 26
5 5.2.9 Abis-ACH Message Transfer ....................................................................................................... 26
6 5.2.10 Unused section......................................................................................................................... 26
7 5.2.11 Abis-Traffic Channel Status ..................................................................................................... 26
8 5.2.12 Successful Mobile Terminated Call.......................................................................................... 27
9 5.3 Call Clearing....................................................................................................................................... 31
10 5.3.1 Call Clearing initiated by MS...................................................................................................... 31
11 5.3.2 Call Clearing initiated by BS/MSC ............................................................................................. 35
12 5.3.3 Call Clearing initiated by BTS .................................................................................................... 38
13 5.3.4 Call Clearing initiated by MS...................................................................................................... 41
14 5.3.5 Call Clearing initiated by BSC/MSC........................................................................................... 43
15 5.3.6 Call Clearing initiated by BTS .................................................................................................... 45
16 5.4 Handoff............................................................................................................................................... 47
17 5.4.1 Abis-BTS Interface Procedures and Messages ............................................................................ 47
18 5.4.2 Soft/Softer Handoff addition (Intra-BTS) .................................................................................... 54
19 5.4.3 Soft/Softer Handoff addition (Inter-BTS)..................................................................................... 56
20 5.4.4 Soft/Softer Handoff Removal (Inter-BTS) .................................................................................... 58
21 5.4.5 Hard Handoff (Inter-BTS) ........................................................................................................... 60
22 5.5 SMS Delivery ..................................................................................................................................... 63
23 5.5.1 SMS Delivery on the Paging channel.......................................................................................... 63
24 5.5.2 Call flow example for SMS Delivery on the Paging channel ...................................................... 65
25 5.5.3 SMS Delivery on the Access channel........................................................................................... 67
26 5.5.4 SMS Delivery on the Traffic channel to MS................................................................................. 70
27 5.5.5 SMS Delivery on the Traffic channel from MS ............................................................................ 71
28 5.6 Traffic Burst Operation....................................................................................................................... 72
29 5.6.1 Abis-Burst Request ...................................................................................................................... 72
30 5.6.2 Abis-Burst Response.................................................................................................................... 72
31 5.6.3 Abis-Burst Commit ...................................................................................................................... 73
32 5.6.4 High Speed Packet Data.............................................................................................................. 73
33 5.6.5 Initial Traffic Burst Example – Abis Connection Not Yet Established ......................................... 75
34 5.6.6 Subsequent Traffic Burst Example............................................................................................... 78
35 5.7 PACA Service ..................................................................................................................................... 80
36 5.7.1 PACA Updating ........................................................................................................................... 80
37 5.7.2 Call flow example for PACA Updating........................................................................................ 81
38 6. Abis Interface Message ........................................................................................................................ 82
39 6.1 Abis Interface Message Formats ........................................................................................................ 82
40 6.1.1 Message Body, Coding, and Ordering of Elements ..................................................................... 82
41 6.1.2 Message Processing Guidelines .................................................................................................. 84
42 6.1.3 Message Definition Guidelines.................................................................................................... 85
43 6.2 Abis interface messages...................................................................................................................... 86
ii
1 6.2.1 Abis-ACH Msg Transfer .............................................................................................................. 86

2 6.2.2 UNUSED SECTION .................................................................................................................... 89
3 6.2.3 Abis-PCH Msg Transfer .............................................................................................................. 89
4 6.2.4 Abis-PCH Msg Transfer Ack ....................................................................................................... 92
5 6.2.5 Abis-BTS Setup............................................................................................................................ 94
6 6.2.6 Abis-BTS Setup Ack ................................................................................................................... 101
7 6.2.7 Abis-BTS Release ...................................................................................................................... 105
8 6.2.8 Abis-BTS Release Ack................................................................................................................ 107
9 6.2.9 Abis-Burst Request .................................................................................................................... 108
10 6.2.10 Abis-Burst Response .............................................................................................................. 113
11 6.2.11 Abis-Burst Commit................................................................................................................. 117
12 6.2.12 Abis-Connect.......................................................................................................................... 122
13 6.2.13 Abis-Connect Ack................................................................................................................... 127
14 6.2.14 Abis-Remove .......................................................................................................................... 127
15 6.2.15 Abis-Remove Ack ................................................................................................................... 127
16 6.2.16 Abis-IS-2000 FCH Fwd ......................................................................................................... 127
17 6.2.17 Abis-IS-2000 FCH Rvs........................................................................................................... 127
18 6.2.18 Abis-Traffic Channel Status ................................................................................................... 127
19 6.2.19 Abis-BTS Release Request ..................................................................................................... 127
20 6.2.20 Abis-IS-2000 SCH Fwd.......................................................................................................... 129
21 6.2.21 Abis-IS-2000 SCH Rvs ........................................................................................................... 129
22 6.2.22 Abis-IS-2000 DCCH Fwd ...................................................................................................... 129
23 6.2.23 Abis-IS-2000 DCCH Rvs ....................................................................................................... 129
24 6.2.24 Abis-PACA Update................................................................................................................. 129
25 7. Information Element Definitions ...................................................................................................... 131
26 7.1 Information Element Identifiers ....................................................................................................... 131
27 7.2 Message Type ................................................................................................................................... 133
28 7.3 Correlation ID................................................................................................................................... 134
29 7.4 Mobile Identity ................................................................................................................................. 134
30 7.5 Cell Identifier ................................................................................................................................... 134
31 7.6 Air Interface Message....................................................................................................................... 134
32 7.7 UNUSED SECTION ........................................................................................................................ 135
33 7.8 Layer 2 Ack Request/Results............................................................................................................ 135
34 7.9 Cause ................................................................................................................................................ 135
35 7.10 Call Connection Reference ........................................................................................................... 135
36 7.11 Band Class .................................................................................................................................... 135
37 7.12 Privacy Info................................................................................................................................... 135
38 7.13 Cell Identifier List......................................................................................................................... 135
39 7.14 SDU ID ......................................................................................................................................... 135
40 7.15 Physical Channel Info ................................................................................................................... 135
41 7.16 Cell Information Record ............................................................................................................... 136
42 7.17 Service Option .............................................................................................................................. 136
43 7.18 PACA Timestamp.......................................................................................................................... 136
iii
1 7.19 Quality of Service Parameters....................................................................................................... 136

2 7.20 Abis Connect Information............................................................................................................. 136
3 7.21 Abis Originating ID ...................................................................................................................... 136
4 7.22 Abis Destination ID ...................................................................................................................... 137
5 7.23 Downlink Radio Environment ...................................................................................................... 137
6 7.24 CDMA Serving One Way Delay ................................................................................................... 137
7 7.25 Forward Burst Radio Info ............................................................................................................. 138
8 7.26 Reverse Burst Radio Info.............................................................................................................. 138
9 7.27 IS-2000 Forward Power Control Mode......................................................................................... 138
10 7.28 IS-2000 FPC Gain Ratio Info ....................................................................................................... 138
11 7.29 BTS L2 Termination ..................................................................................................................... 138
12 7.30 CDMA Target One Way Delay ..................................................................................................... 139
13 7.31 Walsh Code Assignment Reqest ................................................................................................... 139
14 7.32 PACA Order .................................................................................................................................. 139
15 7.33 Authentication Challenge Parameter (RAND).............................................................................. 140
16 7.34 Abis Ack Notify ............................................................................................................................ 141
17 8. Timer Definitions ............................................................................................................................... 142
18 8.1 Tconnb :Timer for Abis-Connect message ....................................................................................... 142
19 8.2 Tsetupb : Timer for Abis-BTS Setup message.................................................................................. 142
20 8.3 Tchanstatb : Timer for Abis-Traffic Channel Status message........................................................... 142
21 8.4 Tdisconb : Timer for Abis-Remove Ack message ............................................................................ 143
22 8.5 Tdrptgtb : Timer for Abis-BTS Release Ack message...................................................................... 143
23 8.6 Tbstreqb : Timer for Abis-Burst Response message......................................................................... 143
24 8.7 Tbstcomb : Timer for Abis-BTS Release Ack message.................................................................... 143
25 8.8 Trelreqb : Timer for Abis-BTS Release message.............................................................................. 143
26
27
iv
1 Table of Figures
2 FIGURE 4-1 REFERENCE MODEL ......................................................................................................... 6
3 FIGURE 4-2 RELATIONSHIP BETWEEN AIR INTERFACE AND ABIS INTERFACE (INTRA-BS MODEL) ...... 8
4 FIGURE 4.5.6.4.1-1 DELIMITING MESSAGES IN AN ABIS APPLICATION TCP BYTE STREAM .............. 14
5 FIGURE 5.1.12-1 MOBILE ORIGINATING CALL ................................................................................... 21
6 FIGURE 5.2.12-1 MOBILE TERMINATED CALL ................................................................................... 27
7 FIGURE 5.3.4-1 CALL CLEARING INITIATED BY MS ........................................................................... 41
8 FIGURE 5.3.5-1 CALL CLEARING INITIATED BY BSC/MSC ................................................................ 43
9 FIGURE 5.3.6-1 CALL CLEARING INITIATED BY BTS.......................................................................... 45
10 FIGURE 5.4.2-1 SOFT/SOFTER HANDOFF ADDITION (INTRA-BTS) ..................................................... 54
11 FIGURE 5.4.3-1 SOFT/SOFTER HANDOFF ADDITION (INTER-BTS) ..................................................... 56
12 FIGURE 5.4.4-1 SOFT/SOFTER HANDOFF REMOVAL (INTER-BTS) ..................................................... 58
13 FIGURE 5.4.5-1 HARD HANDOFF (INTER-BTS).................................................................................. 60
14 FIGURE 5.5.2-1 SMS DELIVERY ON THE PAGING CHANNEL .............................................................. 65
15 FIGURE 5.5.3.5-1 SMS DELIVERY ON THE ACCESS CHANNEL ........................................................... 69
16 FIGURE 5.5.4-1 SMS DELIVERY ON THE TRAFFIC CHANNEL TO MS ................................................. 70
17 FIGURE 5.5.5-1 SMS DELIVERY ON THE TRAFFIC CHANNEL FROM MS............................................. 71
18 FIGURE 5.6.5-1 INITIAL TRAFFIC BURST EXAMPLE ........................................................................... 75
19 FIGURE 5.6.6-1 SUBSEQUENT TRAFFIC BURST EXAMPLE ................................................................. 78
20 FIGURE 5.7.2-1 PACA UPDATING PROCEDURE .................................................................................. 81
21
22
23 Table of Tables
24 TABLE 4-1 LAYER 2 TERMINATION TYPE .............................................................................................. 6
25 TABLE 4-2 ABIS INTERFACE DESCRIPTION............................................................................................ 9
26 TABLE 6.1.1-1 ELEMENT FLOW DIRECTION INDICATION ............................................................... 82
27 TABLE 7.1-1 ABIS INFORMATION ELEMENT IDENTIFIERS SORTED BY IDENTIFIER VALUE ............... 131
28 TABLE 7.2-1 ABIS MESSAGE TYPE VALUES ...................................................................................... 133
29 TABLE 8-1 TIMER VALUES AND RANGE ............................................................................................ 142
30
31
v
1 1. Introduction
2 This document is the specification for the Abis interface (between the Base Transceiver
3 System (BTS) and Base Station Controller (BSC) for IS-2000 system. The signaling
4 flows and these signals are described.
5
6 2. Objectives
7 The Abis interface specification provides an open and inter-operable system.
8
9 2.1 Scope of the document

10 This specification defines the interface between BTS and BSC within the BS. The
11 interface between BSs is specified in the TIA/EIA/IS-2001.
12
13 Following features are not specified in this version of the specification. They are for
14 further study.
15 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 *1 It is recommended that any OAM&P related information be aligned with the
22 TIA/EIA-828, Abis interface. .
23 *2 Inter BSC (BS) hard/soft handoff is supported in the TIA/EIA/IS-2001.
24
25 The functions supported in TIA/EIA/IS-2001 shall be supported implicitly for the Abis
26 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
2
1 2.2.1 Telecommunications Industry Association (TIA) / Electronics Industry

2 Association (EIA)
3 TIA/EIA/IS-2001; Inter-operability Specification (IOS) for CDMA 2000 Access Network
4 Interfaces (also referenced as 3GPP2 TSG-A’s A.S0001); December, 2000.
5 TIA/EIA/IS-95B; Mobile Station - Base Station Compatibility Standard for Dual-Mode

6 Wideband Spread Spectrum Cellular Systems; March, 1999
7 2.2.2 Standards Committee T1

8 ANSI T1.627 - 1993, B-ISDN - ATM Layer Functionality and Specification, 1993.
9 2.2.3 International Telecommunications Union - Telecommunications Sector

10 (ITU-T)
11 ITU-T Recommendation I.363.2, B-ISDN ATM Adaptation layer specification: Type 2
12 AAL; September, 1997.
13 ITU-T Recommendation I.363.5, B-ISDN ATM Adaptation Layer specification: Type 5
14 AAL; August, 1996.
15 ITU-T Recommendation I.366.1; Segmentation and Reassembly Service Specific Con-
16 vergence Sublayer for the AAL type 2; June, 1998.
17 ITU-T Recommendation Q.2931, Broadband-Integrated Services Digital Network
18 (B-ISDN) Digital Subscriber Signalling No. 2 (DSS2) User-Network Interface Layer 3
19 Specification for Basic Call/Connection Control, 1995.
20 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
1 3. Terminology
2
3 3.1 Acronyms
4 The following is a list of acronyms that are used in this specification text.
5
6 AAL2 ATM Adaptation Layer type 2
7 AAL5 ATM Adaptation Layer type 5
8 ADDS Application Data Delivery Service
9 ANSI American National Standards Institute
10 ARFCN Absolute Radio Frequency Channel Number
11 ATM Asynchromous Transfer Mode
12 BSC Base Station Controller
13 BSMAP Base Station Management Application Part
14 BTS Base Transceiver System
15 CC Conference Calling
16 CCITT International Telegraph and Telephone Consultative Committee (See ITU)
17 CDMA Code Division Multiple Access
18 CID Circuit IDentifier (used with reference to AAL2)
19 CM Connection Management
20 cUDP compressed IP/UDP
21 FCH Fundamental Channel
22 IETF Internet Engineering Task Force
23 IMSI International Mobile Subscriber Identity
24 IOS Interoperability Specification
25 IP Internet Protocol
26 ISDN Integrated Services Digital Network
27 ISLP Intersystem Link Protocol
28 ITU International Telecommunications Union
29 kb kilo bits
30 LAC Location Area Code
31 LSB Least Significant Bit
32 MAC Medium Access Control
33 MIN Mobile Identification Number
34 MS Mobile Station
35 MSB Most Significant Bit
36 MSC Mobile Switching Center
37 OAM&P Operations, Administration, Maintenance, and Provisioning
38 OTD Orthogonal Transmit Diversity
39 PACA Priority Access and Channel Assignment
4
1 PATE Packet Arrival Time Error

2 PCF Packet Control Function
3 PCM Pulse Code Modulation
4 PN Pilot Number
5 PPP Point to Point Protocol
6 PSPDN Packet Switched Public Data Network
7 PSTN Public Switched Telephone Network
8 QoS Quality of Service
9 RAND Random Variable
10 RFC Request for Comment
11 RLP Radio Link Protocol
12 SCH Supplemental Channel
13 SCM Service Connect Message
14 SCTP Stream Control Transmission Protocol
15 SDU Selection/Distribution Unit function
16 SMS Short Message Service
17 SMS-MO SMS Mobile Originated
18 SMS-MT SMS Mobile Terminated
19 SSCS Service Specific Convergence Sublayer
20 SSD Shared Secret Data
21 SSSAR Service Specific Segmentation and Reassembly
22 TCP Transmission Control Protocol
23 UDP User Datagram Protocol
24
25 3.2 Others
26 1) In this document the term “cell” is used to refer to a sector with in a cell.
27 2) The messages indicated with solid lines flow over the Abis interface and the messages
28 indicated with dashed lines flow over interfaces other than the Abis interface.
5
1 4. Network Reference Model and Interfaces

2 Figure 4-1 shows the network reference model that is referred to in this specification.
3
4 BS
5
6 BSC SDU Function
7
8 Abis Signaling Abis Signaling
9 Abis Interface
10 Abis Traffic Abis Traffic
11
BTS BTS CH element
12 CH element
13
14
15
16 a) Abis interface = Abis signaling + Abis traffic
17 b) A Selection Distribution Unit (SDU) function is located in the BSC
18 c) A channel element is located in the BTS
19
20 Notes: The handoff procedure between BTSs within a BSC is defined in this document.
21 The handoff procedure between the BSs has been defined in TIA/EIA/IS-2001.
22
23 Figure 4-1 Reference Model
24
25 There are 2 architecture for the L2 terminations were considered. They are shown in the following Table
26 4-1.
27
L r-csch(*1) f-csch(*2) Type A Type B
L3 L3 L3
BSC
Authentication
ARQ ARQ
L LAC Addressing Addressing BSC
2 Utility Utility
BTS
SAR SAR
MAC MAC MAC
L1 L1 L1 BTS
28 Table 4-1 Layer 2 termination type
29 (*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
6
1 sub-layer and SAR sub-layer.

2 (*2) f-csch (forward common signaling logical channel)
3 This logical channel is applied for the case that BTS sends message on the PCH and MS replies on the ACH.
4 In f-csch, LAC sub-layer is composed ARQ sub-layer, Addressing sub-layer, Utility sub-layer and SAR sub-layer.
5 In this specification type A is introduced as architecture for initial phase. However we are also introducing
6 type B for the next release.
7
8 In this release of the Abis specification L2 termination is mandatory to be supported by the BTS. To allow
9 for a migration to new architectures, a mechanism is provided on the Abis interface whereby the BTS can
10 specify if L2 termination function will be supported. If the BTS indicates that it does not support L2
11 termination, then the BSC shall support L2 termination. In this release of the Abis specification the BTS shall
12 specify to the BSC that it terminates L2 termination.
13
14
15
7
1 Figure 4-2 shows the relationship between logical air interface channels and Abis interface signal
Air Interface Abis Interface

BS
MS BTS Abis traffic BSC
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) DCCH (Abis-IS-2000 DCCH Fwd/Rvs)
Abis Signaling
ACH (r-csch) ACH (Abis-ACH Msg Transfer)

PCH (f-csch) PCH (Abis-PCH Msg Transfer)
Abis Signaling
OAM Signaling (FFS)
2
3 Note:This figure is informative. In this figure, some signals defined in the air interface are omitted for
4 clarity.
5
6 Figure 4-2 Relationship between Air interface and Abis interface (Intra-BS Model)
7
8
8
1 Table 4-2 summaries the details of the Abis interface

2
3 Table 4-2 Abis interface description

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

6 In a CDMA system, the user traffic (voice, data, etc.) of a Mobile Station (MS) may be
7 connected to the network using one or more connections from MS to BTS(s). If multiple
8 connections are used for a single flow of user information, the user traffic connection is
9 said to be in soft handoff. The first step within the network is to carry these multiple
10 connections back to a single point from which a selection is made of the “best” frame
11 received over the radio connections. This implies a connection from each involved BTS
12 back to a central point where frame selection occurs. This central point is referred to as
13 the “SDU function.”
14
15 4.2 Support of paging channel messaging

16 When an MS is to be sent a message on a paging channel, the BSC typically formats the
17 majority of the message and forwards it to the BTS along with various parameters
18 including the destined cell identifier. The ability to forward such a paging message from
19 the BSC to the BTS is part of the functionality of the Abis interface.
20 An additional requirement of a CDMA system is that such a message may also need to be
21 forwarded between BSCs to be transmitted on a BTS belonging to a BSC other than the
9
1 BSC that originally created the message. This requirement comes through support for
2 access handoff and other such IS-95 and IS-2000 features. The BSC to BSC signaling
3 interface to support such forwarding has been defined in the TIA/EIA/IS-2001.
4 4.3 Support of Access channel messaging

5 When an MS sends a message on an access channel, the BTS will forward that message
6 to the BSC along with various parameters including the identity of the cell and sector on
7 which the message was received, etc. The ability to forward such an access message from
8 BTS to the BSC is part of the functionality of the Abis interface.
9 An additional requirement of a CDMA system is that such a message may also need to be
10 forwarded between BSCs (i.e., to a BSC other than the one that owns the BTS that
11 originally received the message). This requirement comes through support for access
12 handoff and other such IS-95 and IS-2000 features. The BSC to BSC signaling interface
13 to support such forwarding has been defined in the TIA/EIA/IS-2001.
14
15 4.4 Support of broadcast system information functions

16 In a IS-95 or a IS-2000 system, each BTS broadcasts various pieces of system
17 information that the MS captures and uses during its interactions with the network. Much
18 of that system information may be administrated through OAM&P functions. A small
19 amount of such system information may be placed in BTS and OAM&P control of a BTS
20 for the same purposes.
21 4.5 Layers 1 & 2

22
23 4.5.1 Physical Layer Specification (Layer 1)

24 The physical layer specification is flexible to deploy the various new technologies.
25 Vendors shall have flexibility in providing the latest technology. And operators shall
26 have flexibility in choosing from various options, including T1, E1, 10/100 base T, OC3,
27 OC12, etc.
28
29 4.5.2 Use of ATM (Layer 2)

30 Asynchronous Transfer Mode (ATM) is a suite of protocols that allow fast, efficient
31 delivery of user traffic in a packet environment. ATM, for the purposes of this standard,
32 consists of two main layers: the ATM Layer that uses the physical layer, and the ATM
33 Adaptation Layer that adapts the basic ATM layer to specific usage.
34 4.5.3 Field of Application

35 Asynchronous Transfer Mode (ATM) is used to transport both signaling and user traffic
36 (voice/data).
10
1 4.5.4 ATM Layer

2 The ATM Layer uses a basic 53-octet cell consisting of a 5-octet header and 48-octet
3 payload. This standard uses the ATM Layer as specified in ANSI T1.627-1993
4 Telecommunications Broadband ISDN - ATM Layer Functionality and Specification
5 without modification.
6 For this specification only ATM permanent virtual circuits (PVC’s) shall be required for
7 the Abis interface. These virtual circuits shall be configured through administrative
8 procedures and no special signaling interface procedures, e.g., ATM UNI (Q.2931), shall
9 be required.
10 4.5.5 ATM Adaptation Layer

11 To make use of the basic cell transfer capability of the ATM Transport Layer in specific
12 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 Both AAL5 and AAL2 are used without modification in this standard. The Service
17 Specific Segmentation and Re-assembly (SSSAR) sub-layer for AAL2, as specified in
18 ITU-T I.366.1, is used for segmentation and re-assembly of AAL2 SDUs.
19 In this version of this standard, the functionality of other sub-layers of AAL2 is not
20 supported. Specifically, Service Specific Transmission Error Detection (SSTED) and
21 Service Specific Assured Data Transfer (SSADT) are not included.
22 4.5.6 Network and Transport Protocols

23
24 4.5.6.1 Signaling Connection Transport Protocol Options
25 Signaling over the Abis interface requires a reliable transport protocol and appropriate
26 addressing and routing mechanisms to deliver messages from source to destination. The
27 Abis signaling application is independent of the underlying transport, which is left to the
28 discretion of operators and manufacturers. The signaling protocol stack options available
29 to operators and manufacturers for the Abis interface include:
30
31 Abis Interface (signaling connection):
32
IOS Application IOS Application IOS Application IOS Application
TCP TCP UDP 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
IP IP IP IP
AAL5 Link Layer Link Layer Link Layer
ATM Phys. Lyr. Phys. Lyr. Phys. Lyr.

Phys. Lyr. (Note 1) (Note 1) (Note 1)
1
2 It is mandatory for operators and manufacturers to support ATM based link layer for
3 signaling over the Abis interface. The other signaling connection may support any of
4 the protocol stacks above and is left to the discretion of operators and vendors.
5 UDP may be used and limited to those cases when reliable delivery is not required : e.g.,
6 case when BSC sends general page message.
7 (Note 1) These protocol stacks shown in the table are examples.
8
9 4.5.6.2 User Traffic Connection Transport Protocol Options

10 The protocol stack options for transport of user traffic that are available to operators and
11 manufacturers include:
12
13 Abis Interface (user traffic sub-channel):
14
Abis Traffic Abis Traffic Abis Traffic Abis Traffic
UDP cUDP cUDP
IP SSCS PPPmux
SSSAR Link Layer AAL2 Link Layer
AAL2
Phys. Layer ATM Phys. Layer
ATM (Note 1) Phys. Layer (Note 1)
Phys. Layer (Note 1)
15
16 It is mandatory for operators and manufacturers to support ATM based transport for user
17 traffic over the Abis interface. The other signaling connection may support any of the
18 protocol stacks above and is left to the discretion of operators and vendors.
19 (Note 1) These protocol stacks shown in the table are examples.
20
21 4.5.6.3 TCP Transport Protocol Usage

22 The standard TCP, as described in RFC 793, shall be used for establishing, using, and
23 clearing TCP connections.
24 4.5.6.4 General Use of TCP

25 TCP connections for signaling may be set up on a per-call basis or signaling messages for
26 multiple calls may be multiplexed on a single TCP connection.
27 The TCP provides a reliable byte stream transfer. Therefore, a means needs to be
28 provided for two application entities to delimit the messages sent between them. The
29 technique for such delimitation is as follows.
12
1 4.5.6.4.1 Message Delimiting in TCP

2 TCP provides a reliable byte stream between two application entities. Because the
3 protocol in this standard uses messages to communicate, these messages shall be
4 delimited in the TCP byte stream. Such delimitation shall be done by means of a
5 two-byte flag field and a two-byte length field inserted at the beginning of each message
6 sent over a TCP connection. The flag field shall contain the hex value “F634”. The
7 purpose of the flag field is to facilitate verification of message boundaries and fast
8 reestablishment of synchronization if synchronization of message boundaries is lost.
9 See Figure 4.5.6.4.1-1:
10
13
1
7 6 5 4 3 2 1 0
Flag 1 1 1 1 0 1 1 0
Flag 0 0 1 1 0 1 0 0
Length (MSB)
Length (LSB)
First Octet of Abis Application Message
Second Octet of Abis Application Message
Msg Third Octet of Abis Application Message
...
Last Octet of Abis Application Message
Flag 1 1 1 1 0 1 1 0
Flag 0 0 1 1 0 1 0 0
Length (MSB)
Length (LSB)
...
Last Octet of Abis Application Message
Flag 1 1 1 1 0 1 1 0
Flag 0 0 1 1 0 1 0 0
Length (MSB)
Length (LSB)
...
2 Figure 4.5.6.4.1-1 Delimiting Messages in an Abis Application TCP Byte Stream
3 4.5.6.4.2 TCP Connection Establishment

4 A new TCP connection is established when a signaling message related to a call has to be
5 exchanged over an interface, and no such connection exists over the particular interface.
6 Normal TCP connection establishment procedures are used.
14
1 4.5.6.4.3 TCP Connection Release

2 An existing TCP connection over an interface is released when there are no more
3 signaling messages to be exchanged over the interface. Normal TCP connection release
4 procedures are used.
5 4.5.6.4.4 TCP Port Usage

6 The following TCP port values are reserved for signaling across Abis interfaces:
7 Abis: 5604 -- This is the well-known TCP port at a BS used for Abis signaling
8 interconnection between BTSs and a BSC.
9
10 4.5.6.5 Use of TCP for the Abis Interface

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

14 The standard IP protocol, as defined in RFC 791 (see TIA/EIA/IS-2001 section 1.5.4),
15 shall be used for routing Internet Protocol packets.
16
15
1 5. Call Processing
2
3 5.1 Mobile Originating Call

4 The following subsections describe the procedure for establishing a call through a mobile
5 originating action.
6 Mobile originating call setup involves exchange of the following BSC-BTS messages:
7 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 Abis-ACH Message Transfer

20 The Abis-Access Channel(ACH) Message Transfer is sent by the BTS to the BSC to
21 notify the BSC of the reception of an access channel message.
22 5.1.1.1 Successful Operation

23 When the BTS receives an access channel message, it shall encapsulate that message in
24 the Abis-ACH Msg Transfer, forward it to the BSC. The BTS may be responsible for
25 sending the Data Burst message for such forwarded access channel message.
26
27 Please refer to section 6.2.1, “Abis-ACH Msg Transfer,” for the format and content of
28 this message.
29 5.1.1.2 Failure Operation

30 None.
31
16
1 5.1.2 Unused Section

2
3 5.1.3 Abis-BTS Setup

4 The Abis-BTS Setup message is used by the BSC to request that the BTS allocate
5 resources in one or more cells for support of a call association.

7 When the BSC decides that one or more cells at the BTS are needed to support one or
8 more physical channel connections for a call, the BSC sends an Abis-BTS Setup message
9 to the BTS to indicate the resources required. The BSC then starts timer Tsetupb.
10 Please refer to section 6.2.5, “Abis-BTS Setup,” for the format and content of this
11 message.

13 If timer Tsetupb expires, the BSC may choose to resend the Abis-BTS Setup message.
14
15 5.1.4 Abis-Connect
16 The Abis-Connect message is sent from the BTS to the BSC to initiate to one or more
17 Abis traffic connection. The Abis-Connect Ack message is expected in response.

19 Upon receiving the Abis Signaling Address information, the BTS begins the process of
20 establishing the Abis signaling connection with the BSC. The Abis Signaling Address is
21 used by the BTS to allocate a logical circuit to be used for Abis signaling. The SDU ID
22 identifies the particular instance of the SDU function.
23 Following the establishment of the Abis signaling link, the Abis-Connect message is sent
24 from the BTS to the BSC. The BTS expects an Abis-Connect Ack message indicating the
25 result of processing the Abis-Connect message and starts timer Tconnb. When the Abis
26 traffic connection(s) is established, traffic packets are exchanged to verify that the two
27 entities can communicate via the Abis traffic connection(s).
28 Please refer to section 6.2.12, “Abis-Connect,” for the format and content of this
29 message.

31 If timer Tconnb expires, the BTS may choose to resend the Abis-Connect message.
32
33 5.1.5 Abis-Connect Ack

34 The Abis-Connect Ack message is sent from the BSC to the BTS to indicate the result of
35 processing the Abis-Connect message.
17

2 After processing the Abis-Connect message from the BTS, the BSC will indicate
3 success/failure to the BTS by sending an Abis-Connect Ack message.
4 If the Abis-Connect Ack message indicates that Abis-Traffic Channel Status message are
5 to be sent, then the BSC starts timer Tchanstatb to await Abis-Traffic Channel Status
6 message(s) for all new cells on each Abis connection. One instance of this timer is started
7 for each Abis connection to which one or more cells are being added.
8 Please refer to section 6.2.13, “Abis-Connect Ack,” for the format and content of this
9 message.

11 If an instance of timer Tchanstatb expires, the BSC may assume that a failure has
12 occurred at the BTS during activation of the transmitter(s)/receiver(s) and delete the
13 unreported cells from the active set attached to the Abis connection. The BSC may then
14 send an Abis-BTS Release message to the BTS to cleanly remove those cells from the
15 Abis connection.
16
17 5.1.6 Abis-BTS Setup Ack

18 The Abis-BTS Setup Ack message is used by the BTS to respond to a request that it
19 allocates resources in one or more cells for support of one or more physical channel
20 connections for a call association.

22 When the BTS receives an Abis-BTS Setup message, it determines what internal
23 resources are needed to support the requested physical channels for the call association.
24 Once those resources are allocated and the Abis-Connect Ack message(s) has been
25 received, the BTS responds by sending an Abis-BTS Setup Ack message to the BSC.
26 Please refer to section 6.2.6, “Abis-BTS Setup Ack,” for the format and content of this
27 message.

29 None.
30
31 5.1.7 Abis-IS-2000 FCH Forward

32 This message is sent from the BSC to the BTS on the Abis traffic subchannel connection
33 of type “IS-2000 FCH” (TIA/EIA/IS-2000 Fundamental Channel). It contains the
34 Forward air-frame for the served MS along with control information for the BTS.

36 This message is sent from the BSC to the BTS on Abis traffic subchannel connections of
37 type “FCH” (Fundamental Channel). FCH messages are sent once every 20ms.
18
1 Please refer to section 6.2.16, “Abis-IS-2000 FCH Fwd,” for the format and content of
2 this message.

4 None.
5
6 5.1.8 Abis-IS-2000 FCH Reverse

7 This message is sent from the BTS to the BSC on Abis traffic subchannel connections of
8 type “IS-2000 FCH” (TIA/EIA/IS-2000 Fundamental Channel). It contains the decoded
9 Reverse Traffic Channel frame received from the served MS along with control
10 information.

12 This message is sent to the BSC on the Abis traffic subchannel connections of type
13 “IS-2000 FCH” (TIA/EIA/IS-200 Fundamental Channel) following the decoding of the
14 Reverse Traffic Channel frame. IS-2000 frames are sent once every 20ms.
15 Please refer to section 6.2.17, “Abis-IS-2000 FCH Rvs,” for the format and content of
16 this message.

18 None.
19
20 5.1.9 Abis-PCH Msg Transfer

21 The Abis-Paging Channel (PCH) Msg Transfer is sent by the BSC to request that a
22 particular message is sent on the specified paging channel(s).
23

25 When the BSC wishes to send a message to the mobile station on the paging channel(s) of
26 the BTS, it encapsulates that message in an Abis-(PCH) Msg Transfer and sends it to the
27 BTS.
28 A Layer 2 acknowledgment indication can be requested. If such an acknowledgment is
29 received from the MS, an Abis-Paging Channel Message Transfer ACK message is used
30 to convey that information back to the BSC
31 Please refer to section 6.2.3, “Abis-PCH Msg Transfer” for the format and content of this
32 message.

34 None.
35
19
1 5.1.10 Abis-PCH Msg Transfer Ack

2 The Abis-PCH Msg Transfer Ack is used to respond to a request for a Layer 2
3 acknowledgment included in an Abis-PCH Msg Transfer.

5 When the BTS receives the Abis-PCH Msg Transfer including Abis Ack Notify IE, the
6 BTS sends the Abis-PCH Msg Transfer Ack upon receipt of the Layer 2
7 acknowledgment.
8 Please refer to section 6.2.4, “Abis-PCH Msg Transfer Ack” for the format and content of
9 this message.

11 None.
12
13 5.1.11 Abis-Traffic Channel Status

14 The Abis-Traffic Channel Status message is used by the BTS to notify the BSC that radio
15 transmission on the forward link has begun for the indicated cells, and that the
16 corresponding receivers have been activated. This message is sent when the
17 Abis-Connect Ack message indicates that it is requested.

19 When the BTS needs to notify the BSC of a status change relative to a specific set of cells
20 on one Abis connection, it sends an Abis-Traffic Channel Status message.
21 This message can be used to note that the indicated set of cells has begun radio
22 transmission on the forward link and that the corresponding receivers have been activated.
23 When this message is used in response to an Abis-Connect Ack message, the BTS does
24 not need to send this message if the transmitters(s)/receiver(s) are not turned on at the
25 BTS (i.e., the radio transmission on the forward link has not begun for the indicated
26 cells).
27 Multiple instances of this message may be sent relative to a single Abis connection if, for
28 instance, transmitter(s)/receiver(s) are activated at different times; however, all cells
29 referenced within a single instance of this message shall be attached to the same Abis
30 connection.
31 The BSC stops the instance of timer Tchanstatb for that Abis connection when
32 Abis-Traffic Channel Status message(s) have been received containing references to all
33 cells added to the Abis connection by the Abis-Connect message.
34 Please refer to section 6.2.18, “Abis-Traffic Channel Status,” for the format and content
35 of this message.

37 None.
38
39
20
1 5.1.12 Successful Mobile Originating Call

2 This section describes the call flow associated with an MS call origination in the IS-2000
3 system.
BS Time Comment
MS BTS BSC MSC
Origination 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
d
Abis-BTS Setup
e
Abis-Connect Tsetupb
f
Tconnb Abis-Connect Ack
g
Abis-BTS Setup Ack
h
Null Traffic Abis-IS-2000 FCH Fwd (Null Data)
i
Extended Abis-IS-2000 FCH Rvs (Idle)
j
Channel Assignment Abis-PCH Msg. Transfer (ECAM)
k
T10
Traffic Channel Preamble Abis-IS-2000 FCH Rvs (T-CH Preamble)
l
BS Ack Order Abis-IS-2000 FCH Fwd (BS Ack Order)

m
Idle Tch Data Frames Abis-IS-2000 FCH Rvs (Idle)
n
MS Ack Order Abis-IS-2000 FCH Rvs (MS Ack Order) o
Service Connect Abis-IS-2000 FCH Fwd (SCM)

p
Service Connect Completion Abis-IS-2000 FCH Rvs (SCCM)

q
Assignment Complete
r
4 Figure 5.1.12-1 Mobile Originating Call
6 a. The MS transmits an Origination Message, with layer 2

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

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

6 Complete Layer 3 Information message, and sends the message to the
7 MSC and starts timer T303. If the BSC requested a preferred
8 terrestrial circuit in the CM Service Request message and the MSC
9 can support that terrestrial circuit, the MSC shall use the same
10 terrestrial circuit in the Assignment Request message. Otherwise, the
11 MSC may assign a different terrestrial circuit.
12 d. The MSC sends an Assignment Request message to the BSC to

13 request assignment of radio resources. This message will include
14 information on the terrestrial circuit, if one is to be used between the
15 MSC and the BSC. The MSC then starts timer T10. Upon the receipt
16 of the Assignment Request message, the BSC stops timer T303.
17 e. The BSC sends an Abis-BTS Setup message to the BTS to request

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

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

32 Null Data to let the BTS send Null traffic data toward the MS. Then
33 the BTS begin sending Null Traffic data for synchronizing between
34 the BTS and the MS. The BTS may have a function that enables to
35 send a Null Traffic data for synchronization between the BTS and the
36 MS. BSC can notify whether the BTS has the function or not by
37 sending Null Traffic.
22
1 j. The BTS sends Abis-IS-2000 FCH Rvs message including Idle data
2 to the BSC.
3 k. The BSC sends an Abis-PCH Msg Transfer including Extended

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

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

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

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

27 Service Connect Completion message. Then the BTS transmits it
28 with an Abis-IS-2000 FCH Rvs message.
29 r. After the radio traffic channel and circuit have both been established
30 and fully interconnected, the BSC sends the Assignment Complete
31 message to the MSC and considers the call to be in conversation
32 state.
33 The MSC stops timer T10 upon receipt of the Assignment Complete
34 message.
35
23
24
1 5.2 Mobile Terminated Call

2 The following subsections describe the procedure for establishing a call through a mobile
3 terminated action.
4 Mobile terminated call setup involves exchange of the following BSC-BTS messages:
5 Abis-PCH Message Transfer
6 Abis-PCH Message Transfer Ack
7 Abis-BTS Setup
8 Abis-Connect
9 Abis-Connect Ack
13 Abis-ACH Message Transfer
14 Abis-ACH Message Transfer Ack
15 Abis-Traffic Channel Status
16
17 5.2.1 Abis-PCH Message Transfer

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

22

25
28

25

4
5 5.2.7 Abis-IS-2000 FCH Forward

7
8 5.2.8 Abis-IS-2000 FCH Reverse

10
11 5.2.9 Abis-ACH Message Transfer

13
14 5.2.10 Unused section

15
16

19
26
1 5.2.12 Successful Mobile Terminated Call

2 This section describes the call flow associated with a mobile station call termination in the
3 IS-2000 system.
MS BTS BSC MSC Time Comment
Paging Request a
General Page Abis-PCH Msg. Transfer (GPM)
b
Page Response Abis-ACH Msg. Transfer (PRM)
c
BS Ack Order d
Complete L3 Info:
Paging Response
e
T303 Assignment Request
Abis-BTS Setup f
g
h
i
Abis-BTS Setup Ack
j
Null Traffic Abis-IS-2000 FCH Fwd (Null Data) k
Abis-IS-2000 FCH Rvs (Idle)
Extended l
Abis-PCH Msg. Transfer (ECAM) T10
Channel Assignment
m
TCH Preamble Abis-IS-2000 FCH Rvs (Preamble)
n
BS Ack Order Abis-IS-2000 FCH Fwd (BS Ack)
o
Idle Tch Data Frames Abis-IS-2000 FCH Rvs (Idle)
p
MS Ack Order Abis-IS-2000 FCH Rvs (MS Ack)
q
Service Connect Abis-IS-2000 FCH Fwd (SCM)
r
Serv. Con. Completion Abis-IS-2000 FCH Rvs (SCCM)
s
Assignment Complete
t
Alert with Info Abis-IS-2000 FCH Fwd (AWIM)
u
MS Ack Order Abis-IS-2000 FCH Rvs (MS Ack)
T301 v
Connect Order Abis-IS-2000 FCH Rvs (Connect Order)
w
BS Ack Order Abis-IS-2000 FCH Fwd (BS Ack)
x
Connect
y
5 Figure 5.2.12-1 Mobile Terminated Call
27
1 a. The MSC sends the Paging Request message to the BSC to initiate a
2 mobile terminated call setup scenario.
3 b. The BSC constructs a General Page Message (GPM), places the

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

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

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

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

21 assignment of radio resources. The message will also include
22 terrestrial circuit if one it to be used between the MSC and the BSC.
23 The MSC then starts timer T10.
24 If the BSC requested a preferred terrestrial circuit in the CM Service

25 Request message and the MSC can support that terrestrial circuit, the
26 MSC shall use the same terrestrial circuit in the Assignment Request
27 message. Otherwise the MSC may assign a different terrestrial circuit.
28 Upon receipt of the Assignment Request message from the MSC, the
29 BSC stops timer T303.
30 g. The BSC sends an Abis-BTS Setup message to the BTS to request

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

35 resources and sends Abis-Connect message to initiates an Abis
28
1 connection and to report the result of resource allocation. The BTS

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

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

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

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

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

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

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

33 This is sent by the BTS to the BSC in the Abis-IS-2000 FCH Rvs
34 message.
29
1 r. The BSC sends the Service Connect Message (SCM) to the MS

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

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

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

18 Message by transmitting the MS Ack Order.
19 w. When the call is answered at the MS, a Connect Order, with

20 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
23 call has been answered at the MS. At this point, the call is considered
24 stable and in the conversation state. The MSC stops timer T301 upon
25 receipt of the Connect message from the BSC.
26
27
30
1 5.3 Call Clearing

2 MS, BTS, BSC or MSC will initiate call clearing procedure.
3 The Following messages are exchanged between BSC and BTS.
6 Abis-BTS Release
7 Abis-BTS Release Ack
8 Abis-BTS Remove
9 Abis-BTS Remove Ack
10 Abis-BTS Release Request
11
12 5.3.1 Call Clearing initiated by MS

13
14 5.3.1.1 Successful Clear Scenarios

15 For a normal clearing that is initiated by the MS, the MS will send a Release Order to the
16 BTS. The BTS shall send an Abis-IS-2000 FCH Rvs message that contains the Release
17 Order message to the BSC. Then BSC sends Clear Request message to the MSC and
18 starts timer T300 to wait for the Clear Command message from the MSC. For packet
19 data calls, call clearing does not normally clear the service session. The service session
20 will be cleared using procedures in this section for conditions such as MS power down,
21 termination of the PPP session by the mobile or the network, etc.
22 In response to the Clear Command message from the MSC, the BSC sends an
23 Abis-IS-2000 FCH Fwd message containing the Release Order message. The BTS
24 sends this to the MS on the forward traffic channel to wait for the Abis-Remove Ack
25 message from the BTS.
26 If the BTS receives the Abis-BTS Release message, the BTS starts to releases the radio
27 resource, sends Abis-Remove message to the BSC and starts timer Tdisconb.
28 In response to the Abis-Remove message from the BTS, the BSC sends Abis-Remove
29 Ack message to the BTS. The BTS will stop timer Tdisconb.
30 Then the BTS sends an Abis-BTS Release Ack message to the BSC to acknowledge the
31 completion of the releasing the radio resources.
32 If the BSC receives the Abis-BTS Release Ack message from the BTS, the BSC will stop
33 timer Tdrptgtb and sends a Clear Complete message to the MSC. Then the BSC
34 releases the related terrestrial circuit to the BTS, if allocated. The MSC stops timer
35 T315 upon receipt of the Clear Complete message. The MSC releases the underlying
36 transport connection.
37 The call flow scenarios are illustrated in section 5.3.4, 5.3.5 and 5.3.6..
31
1 5.3.1.2 Unsuccessful Call Clearing Procedures

2 Each node will supervise and detect the unnecessary reserved resource spontaneously,
3 and release it individually.
4 5.3.1.3 Abis-IS-2000 FCH Rvs

5 See 5.1.8.
6 5.3.1.3.1 Successful Operation

7 See 5.1.8.1.
8
9 5.3.1.3.2 Failure Operation

10 See 5.1.8.2.
11
12 5.3.1.4 Abis-IS-2000 FCH Fwd

13 See 5.1.7.

15 See 5.1.7.1.
16

18 See 5.1.7.2.
19
20 5.3.1.5 Abis-BTS Release

21 In response to the Clear Command message from the MSC, the BSC sends an
22 Abis-IS-2000 FCH Fwd message containing the Release Order message and then the
23 BSC sends an Abis-BTS Release message to the BTS.

25 The BSC, after sending an Abis-BTS Release message to the BTS and starts timer
26 Tdrptgtb to wait for the Abis-Release Ack message from the BTS.
27 Upon receipt of the Abis-BTS Release message, the BTS releases the associated radio
28 resources. The BTS sends an Abis-BTS Release Ack message to the BSC to acknowledge
29 the clearing of resources at the BTS.
32
32

2 If the BSC fails to receive an Abis-BTS Release Ack message before the expiration of
3 timer Tdrptgtb, the BSC may resend the Abis-BTS Release message to the BTS.
4
5 5.3.1.6 Abis-BTS Release Ack

6 The Abis-BTS Release Ack message is used by BTS to respond to a request that it
7 releases the radio resources in the BTS.

9 Upon receipt of the Abis-BTS Release message, the BTS releases the associated radio
10 resources. The BTS sends an Abis-BTS Release Ack message to the BSC to acknowledge
11 the clearing of resources at the BTS.
12

14 None
15
16 5.3.1.7 Abis-BTS Remove

17 In response to the Abis-BTS Release message from the BSC, the BTS sends an Abis-BTS
18 Remove message to the BSC and starts to releases the radio resource.

20 The BTS, after sending an Abis-BTS Remove message to the BSC and starts timer
21 Tdisconb to wait for the Abis-Remove Ack message from the BSC.
22 Then the BSC sends an Abis-BTS Remove Ack message to the BTS to acknowledge the
23 receiving of the message.
24

26 If an Abis-BTS Remove Ack message is not received from the BSC while timer Tdisconb
27 is active, the BTS may choose to resend a Abis-BTS Remove message to the BSC.
28
29 5.3.1.8 Abis-BTS Remove Ack

30 The Abis-BTS Remove Ack message is used by BSC to confirm the reception of the
31 Abis-Remove message in BSC.
33

2 The BSC sends an Abis-BTS Remove Ack message to the BTS to acknowledge the
3 receiving of Abis-BTS Remove message .
4

6 None
7
8
34
1 5.3.2 Call Clearing initiated by BS/MSC

2

4 If some internal BSC failure occurs, then the BSC will initiate call clearing.
5 The BSC sends Clear Request message to the MSC and starts timer T300 to wait for the
6 Clear Command message from the MSC.
7 The MSC is responsible for clearing any A1, A2, and/or A5 connections associated with
8 the call. To release all allocated resources, the MSC sends a Clear Command message to
9 the BSC and starts timer T315. The BSC responds with a Clear Complete message and
10 stop timer T300.
11 Then the BSC sends an Abis-IS-2000 FCH Fwd message containing the Release Order
12 message and the Release Order will be transferred to MS on the IS-2000 FCH Fwd
13 channel.
14 If the BTS receives Release Order from MS, the BTS sends Abis-IS-2000 FCH Rvs
15 message that contains the Release Order message to the BSC.
16 Then the BSC sends an Abis-BTS Release message to the BTS and starts timer Tdrptgtb
17 to wait for the Abis-Remove Ack message from the BTS.
18 If the BTS receives the Abis-BTS Release message, the BTS starts to releases the radio
19 resource, sends Abis-Remove message to the BSC and starts timer Tdisconb.
26 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.

31 Each node will detect the unnecessary reserved resource and release it individually.
32
33 5.3.2.3 Abis-IS-2000 FCH Rvs

34 See 5.1.8.

36 See 5.1.8.1
37
35

2 See 5.1.8.2
3
4 5.3.2.4 Abis-IS-2000 FCH Fwd

5 See 5.1.7.

7 See 5.1.7.1
8

10 See 5.1.7.2.
11

13 See 5.3.1.5

15 See 5.3.1.5.1.
16

18 See 5.3.1.5.2.
19

21 See 5.3.1.6.

23 See 5.3.1.6.1
24

26 None
27

29 See 5.3.1.7.
36

2 See 5.3.1.7.1.
3

5 See 5.3.1.7.1.
6
7
37
1 5.3.3 Call Clearing initiated by BTS

2

4 If the MS is not active (powered off) or if for any reason the radio channel failed between
5 the MS and the BTS or if some internal BTS failure occurs, then the BTS will initiate call
6 clearing by sending Abis-BTS Release Request and starts Tdrptgtb.
7 If the BSC receives Abis-BTS Release Request message, the BSC sends Clear Request
8 message to the MSC and starts timer T300 to wait for the Clear Command message from
9 the MSC.
10 The MSC is responsible for clearing any A1, A2, and/or A5 connections associated with
11 the call. To release all allocated resources, the MSC sends a Clear Command message to
12 the BSC and starts timer T315. The BSC stops timer T300.
13 Then the BSC sends an Abis-IS-2000 FCH Fwd message containing the Release Order
14 message and the Release Order will be transferred to MS on the IS-2000 FCH Fwd
15 channel.
16 If the BTS receives Release Order from MS, the BTS sends Abis-IS-2000 FCH Rvs
17 message that contains the Release Order message to the BSC.
18 Then the BSC sends an Abis-BTS Release message to the BTS and starts timer Tdrptgtb
19 to wait for the Abis-Remove Ack message from the BTS.
20 If the BTS receives the Abis-BTS Release message, the BTS stops timer Tdrptgtb , starts
21 to releases the radio resource and sends Abis-Remove message to the BSC and starts
22 timer Tdisconb.
29 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.

34 Each node will detect the unnecessary reserved resource and release it individually.
35
36 5.3.3.3 Abis-BTS Release Request

37 If the MS is not active (powered off) or if for any reason the radio channel failed between
38 the MS and the BTS or if some internal BTS failure occurs, then the BTS will send
39 Abis-BTS Release Request message to the BSC in order to initiate call clearing.
38

2 The BTS, after sending an Abis-BTS Release Request message to the BSC and starts
3 timer Trelreqb to wait for the Abis-Release message from the BSC.
4 If the BTS receives the Abis-BSC Release message, then the BTS stops Trelreqb and
5 starts to releases the radio resource.
6

8 If an Abis-BTS Release message is not received from the BSC while timer Trelreqb is
9 active, the BTS may choose to resend a Abis-BTS Release Request message to the BSC.
10
11 5.3.3.4 Abis-IS-2000 FCH Rvs

12 See 5.1.8.

14 See 5.1.8.1
15

17 See 5.1.8.2
18
19 5.3.3.5 Abis-IS-2000 FCH Fwd

20 See 5.1.7.

22 See 5.1.7.1
23

25 See 5.1.7.2
26

28 See 5.3.1.5

30 See 5.3.1.5.1.
39

3 See 5.3.1.5.2.
4

6 See 5.3.1.6.

8 See 5.3.1.6.1
9

11 None
12

14 See 5.3.1.7.

16 See 5.3.1.7.1.
17

19 See 5.3.1.7.1.
20
21 5.3.3.9 Abis-BTS Remove Ack

22 See 5.3.1.8.

24 See 5.3.1.8.1.
25

27 None
28
29
40
1 5.3.4 Call Clearing initiated by MS

2 This section provides the call flow diagram for a call clearing operation initiated by MS.
3
4
BS
5 MS BTS BSC MSC Time
6
7 a
Release Order Abis-IS-2000 FCH Rvs (Release Order)
8 Clear Request
b
9
T300
10
Clear Command c
11 Abis-IS-2000 FCH Fwd (Release Order)
Release Order
12 )
d
13 Abis-BTS Release
14 e
Tdrptgtb
15 Abis-Remove T315 f
16
Tdisconb
17 Abis-Remove Ack g
18
19 Abis-BTS Release Ack h
20 Clear Complete i
21 Figure 5.3.4-1 Call Clearing initiated by MS
22 a. The MS initiates call clearing by transmitting a Release Order over

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

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

9 acknowledge the Abis removal. Upon receipt of the Abis-BTS
10 Release Ack message the BSC stops timer Tdrptgtb.
11 i. The BSC sends a Clear Complete message to the MSC. Then BSC
12 releases the related terrestrial circuit to the BTS, if allocated. And
13 the MSC stops timer T315 upon receipt of the Clear Complete
14 message. The MSC releases the underlying transport connection.
15
16
42
1 5.3.5 Call Clearing initiated by BSC/MSC

2 This section provides the call flow diagram for a call clearing operation initiated by
3 BSC/MSC.
4
BS
BS
5
MS BTS
BTS BSC
BSC MSC
MSC Time
6 Clear Request
a
T300
7 Clear Command b
Release Order
Abis-IS-2000 FCH Fwd (Release Order)
8 c
9
Release Order Abis-IS-2000 FCH Rvs (Release Order)
d
10
T315
Abis-BTS Release e
11
Abis-Remove Tdrptgtb
f
Tdisconb
12 Abis-Remove Ack g
13 Abis-BTS Release Ack

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

16 acknowledge the Abis removal. If the BSC receives the Abis-Release
17 Ack message, BSC stops timer Tdrptgtb.
18 i. Upon receipt of the Abis BTS Release Ack message, the BSC sends
19 the Clear Complete message to the MSC. The MSC stops timer T315
20 upon receipt of the Clear Complete message. The MSC releases the
21 underlying transport connection.
22
44
1 5.3.6 Call Clearing initiated by BTS

2 This section provides the call flow diagram for a call clearing operation initiated by the
3 BTS.
4
5 BS
6 MS Time
BTS BSC MSC
7
8
Abis-BTS Release Request Clear Request
9 a
10 Trelreqb T300
11 Clear Command b
Release Order Abis-IS-2000 FCH Fwd (Release Order)
12 c
13
Abis-IS-2000 FCH Rvs (Release Order)
14 Release Order d
)
15
T315
16 Abis-BTS Release e
17
18 Abis-Remove
Tdrptgtb f
19 Tdisconb
Abis-Remove Ack g
20
21 Abis-BTS Release ACK
h
22 Clear Complete
i
23
24
25 Figure 5.3.6-1 Call Clearing initiated by BTS
26 a. In the case of a radio channel failure between the MS and the BTS, or
27 if the MS is not active, the BTS sends an Abis-BTS Release Request
28 message to BSC and the BTS starts timer Trelreqb. In response to
29 the message the BSC sends a Clear Request message to the MSC.
30 The BSC starts timer T300 and waits for the Clear Command from
31 the MSC. A Call Clearing flow initiated by BTS starts from this
32 step.
33 b. The MSC starts timer T315 and sends a Clear Command message to
34 instruct the BSC to release the associated dedicated resource (such as
35 terrestrial circuit). The BSC stops timer T300.
36 c. In response to the Clear Command message from the MSC, the BSC
37 sends Abis-IS-2000 FCH Fwd containing the Release Order message.
38 The BTS sends the Release Order message to the MS over the
39 forward traffic channel.
45
1 d. The MS replies with a Release Order over the reverse traffic channel.
2 In response to the order, BTS sends an Abis-IS-2000 FCH Rvs
3 containing the Release Order message to the BSC.
5 starts Tdrptgtb. If the BTS receives Abis-BTS Release message from
6 the BTS, the BTS stops timer Trelreqb.
9 g. In response to the Abis Remove message from the BTS and the BSC
10 sends an Abis Remove Ack message to the BTS and returns a Clear
11 Complete message to the MSC. Then the BSC releases the related
12 terrestrial circuit to the BTS, if allocated. If the BTS receives the
13 Abis-Remove Ack message, the BTS stops timer Tdisconb.

15 acknowledge the Abis removal. If the BSC receives the Abis-Release
16 Ack message, the BSC stops timer Tdrptgtb.
17 i. Upon receipt of the Abis-BTS Release Ack message, the BSC sends
18 the Clear Complete message to the MSC. The MSC stops timer T315
19 upon receipt of the Clear Complete message. The MSC releases the
20 underlying transport connection.
21
46
1 5.4 Handoff
2 This section describes handoff procedure using Abis interface within the BS. TIA/EIA/IS-2001
3 5.4.1 Abis-BTS Interface Procedures and Messages

4 This section describes the messages and procedures used Abis connection to support
5 soft/softer handoff, Hard handoff.
6 5.4.1.1 Abis-BTS Interface Messages

7 This section describes the messages and procedures used Abis connection to support BTS
8 soft/softer handoff.
9 These messages are:
10 Abis-BTS Setup
12 Abis-Connect
13 Abis-Connect Ack
14 Abis-IS-2000 FCH Forward
15 Abis-IS-2000 FCH Reverse
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 Abis-BTS Setup

23 The Abis-BTS Setup message is used by the BSC to request that a target BTS allocate
24 resources in one or more cells for support of a call association.
25
26 5.4.1.1.1.1 Successful Operation
27 When the BSC decides that one or more cells at a target BTS are needed to support one or
28 more physical channel connections for a call, the BSC sends an Abis-BTS Setup message
29 to the target BTS to indicate the resources required. The BSC then starts timer Tsetupb.
30 Please refer to section 6.1.5 “Abis-BTS Setup,” for the format and content of this
31 message.
32
47
1 5.4.1.1.1.2 Failure Operation
2 If timer Tsetupb expires, the BSC may choose to resend the Abis-BTS Setup message.
3
4 5.4.1.1.2 Abis-BTS Setup Ack

5 The Abis-BTS Setup Ack message is used by the target BTS to respond to a request that
6 it allocates resources in one or more cells for support of one or more physical channel
7 connections for a call association.
8
10 When the target BTS receives an Abis-BTS Setup message, it determines what internal
11 resources are needed to support the requested physical channels for the call association.
12 Once those resources are allocated and the Abis-Connect Ack message(s) has been
13 received, the target BTS responds by sending an Abis-BTS Setup Ack message to the
14 BSC.
15 Please refer to section 6.1.6 ”Abis-BTS Setup Ack” for the format and content of this
16 message.
17
19 None.
20
21 5.4.1.1.3 Abis -Connect

22 The Abis-Connect message is sent from the target BTS to the BSC to initiate or add cells
23 to one or more Abis user traffic connection. An Abis -Connect Ack message is expected
24 in response.
25
27 Upon receiving the Abis Signaling Address information, the receiving BTS begins the
28 process of establishing the Abis signaling connection with the BSC. The Abis Signaling
29 Address is used by the target BTS to allocate a logical circuit to be used for Abis
30 signaling. The SDU ID identifies the particular instance of the SDU function.
31 Following the establishment of the Abis signaling link, the Abis-Connect message is sent
32 from the target BTS to the entity at the other end. The target BTS expects an
33 Abis-Connect Ack message indicating the result of processing the Abis-Connect message
34 and, therefore, starts timer Tconnb. When the Abis user traffic connection(s) is
35 established, traffic packets are exchanged to verify that the two entities can communicate
36 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
48
1 If timer Tconnb expires, the BTS may choose to resend the Abis-Connect message.
2
3 5.4.1.1.4 Abis-Connect Ack.

4 The Abis-Connect Ack message is sent from the BSC to the target BTS to indicate the
5 result of processing the Abis-Connect message.
6
8 After processing the Abis-Connect message from the requesting BTS, the BSC will
9 indicate success/failure to the requesting BTS by sending an Abis-Connect Ack message.
10 If the Abis-Connect Ack message indicates that Abis-Traffic Channel Status messages are
11 to be sent, then the source BSC starts timer Tchanstatb to await Abis-Traffic Channel
12 Status message(s) for all new cells on each Abis connection. One instance of this timer
13 is started for each Abis connection to which one or more cells are being added.
14 Please refer to section 6.1.13 ”Abis-Connect Ack” or the format and content of this
15 message.
16
18 If an instance of timer Tchanstatb expires, the BSC may assume that a failure has
19 occurred at the BTS during activation of the transmitter(s)/receiver(s) and delete the
20 unreported cells from the active set attached to the Abis connection. The BSC may then
21 send an Abis-BTS Release message to the target BTS to cleanly remove those cells from
22 the Abis connection.
23 5.4.1.1.5 Abis-Traffic Channel Status

24 The Abis-Traffic Channel Status message is used by the target BS to notify the BSC that
25 radio transmission on the forward link has begun for the indicated cells, and that the
26 corresponding receivers have been activated. This message is sent when the
27 Abis-Connect Ack message indicates that it is requested.
28
30 When the target BS needs to notify the BSC of a status change relative to a specific set of
31 cells on one Abis connection, it sends an Abis-Traffic Channel Status message.
32 This message can be used to note that the indicated set of cells has begun radio
33 transmission on the forward link and that the corresponding receivers have been activated.
34 When this message is used in response to an Abis-Connect Ack message, the target BS
35 does not need to send this message if the transmitters(s)/receiver(s) are not turned on at
36 the target BS (i.e., the radio transmission on the forward link has not begun for the
37 indicated cells).
38 Multiple instances of this message may be sent relative to a single Abis connection if, for
39 instance, transmitter(s)/receiver(s) are activated at different times; however, all cells
49
1 referenced within a single instance of this message shall be attached to the same Abis
2 connection.
3 The BSC stops the instance of timer Tchanstatb for that Abis connection when
4 Abis-Traffic Channel Status message(s) have been received containing references to all
5 cells added to the Abis connection by the Abis-Connect message.
6 Please refer to section 6.1.18, “Abis-Traffic Channel Status,” for the format and content
7 of this message.
8
10 None.
11
12 5.4.1.1.6 Abis-IS-2000 FCH Forward

13 This message is sent from the BSC to the target BTS on the Abis IS-2000 user traffic
14 subchannel for subchannel of type “FCH” (Fundamental Channel). It contains the
15 Forward airframe for the served MS along with control information for the target BTS.
16
18 This message is sent from BSC to the target BTS on Abis IS-2000 user traffic subchannel
19 connections of type “FCH” (Fundamental Channel). FCH messages are sent once every
20 20 ms.
21 The forward path message delay shall be no more than 50ms measured from the time the
22 first bit of the frame is transmitted from the BSC to the time the first bit of the frame is
23 transmitted over the air interface at the channel element for any soft handoff leg. This
24 assumes a maximum transmission and queuing delay on the Abis traffic connection of
25 5ms. However, the delay limits defined above will not be applied to satellite applications.
26 Forward Frame Sequence Number Alignment clarification:
27 The SDU function may use the PATE and Sequence Number information received in the
28 Abis-IS-2000 FCH Reverse message to ensure that all BTS's involved in soft handoff for
29 a call will simultaneously transmit identical forward air frames during identical frame
30 boundaries.
31 Please refer to section 6.1.16 “Abis-IS-2000 FCH Forward” for the format and content of
32 this message.
33
35 None.
36
37 5.4.1.1.7 Abis-IS-2000 FCH Reverse
38 This message is sent from the target BTS to the BSC on Abis IS-2000 user traffic
39 subchannel connections of type “IS-2000 FCH” (TIA/EIA/IS-2000 Fundamental Channel).
50
1 It contains the decoded Reverse Traffic Channel frame received from the served MS
2 along with control information.
3
5 This message is sent to the BSC on the Abis IS-2000 user traffic subchannel connections
6 of type “IS-2000 FCH” (TIA/EIA/IS-2000 Fundamental Channel) following the decoding
7 of the Reverse Traffic Channel frame. IS-2000 FCH frames are sent once every 20 ms.
8 The reverse path message delay shall be no more than 60 ms measured from the time the
9 last bit of the frame is received on the air interface at the channel element of any soft
10 handoff leg to the time the last bit of the frame is received at the BSC. This assumes a
11 maximum transmission and queuing delay on the Abis traffic connection of 5 ms.
12 However, the delay limits defined above will not be applied to satellite applications.
13 Forward Frame Alignment Requirements:
14 As part of the reverse-link processing, each target BTS channel element shall estimate the
15 arrival time error for the Abis-IS-2000 FCH Forward message last received and shall set
16 the PATE field of the next transmitted Abis-IS-2000 FCH Reverse message to this value.
17 In the case when no forward data has been received for an interval of time exceeding the
18 maximum range of the PATE, the PATE value shall saturate (i.e., not rollover) at the
19 maximum positive value. Positive PATE values indicates that the message arrived too
20 late to be transmitted in the correct airframe. Negative PATE values indicate that the
21 message arrived too early and therefore shall be buffered before transmission. Zero PATE
22 value indicates that the message arrived at the optimum time for processing and
23 transmission.
24 Please refer to section 6.1.17 ”Abis-IS-2000 FCH Reverse” for the format and content of
25 this message.
26
28 None.
29
30 5.4.1.1.7 Abis-BTS Release

31 The Abis-BTS Release message is used by the BSC to request that a target BTS
32 deallocate resources in one or more cells currently being used for support of one or more
33 physical channel connections for a call association.
34
36 When the BSC decides that one or more cells at a target BTS are no longer needed to
37 support one or more physical channel connections for a call association, the BSC sends an
38 Abis-BTS Release message to the target BS to indicate the resources that are no longer
39 required. The BSC then starts timer Tdrptgtb.
40 Please refer to section 6.1.7, “Abis-BTS Release” for the format and content of this
41 message.
51
1
3 If timer Tdrptgtb expires, the BSC may choose to resend the Abis-BTS Release message.
4
5 5.4.1.1.8 Abis-BTS Release Ack

6 The Abis-BTS Release Ack message is used by the BSC to respond to a request that it
7 deallocate resources in one or more cells currently being used for support of one or more
8 physical channel connections for a call association.
9
11 When the BTS receives an Abis-BTS Release message, it determines what resources are
12 no longer needed to support the call association. Once those resources are deallocated,
13 the BTS responds by sending an Abis-BTS Release Ack message to the BSC.
14 Please refer to section 6.1.8, “Abis BTS Release Ack,” for the format and content of this
15 message.
16
18 None.
19
20 5.4.1.1.9 Abis-Remove
21 A target BTS uses the Abis-Remove message to request that the BSC remove the
22 indicated cells from the indicated Abis connections. This might result in the entire
23 removal of an Abis traffic subchannel if the last cell on that traffic subchannel is
24 removed.
25
27 The BTS sends an Abis-Remove message to the BSC requesting removal of the indicated
28 cells from one or more Abis connection. The BSC will reply with an Abis-Remove Ack
29 message. If the last cell is removed from an Abis traffic subchannel, the entire Abis
30 traffic subchannel is also terminated. The BTS starts timer Tdisconb.
31 Please refer to section 6.1.14, “Abis-Remove,” for the format and content of this
32 message.
33
35 If the BSC does not recognize an Abis user traffic connection identified in the
36 Abis-Remove message as being associated with the Call Connection Reference value
37 included in this message, it shall send an appropriate cause for the failure in the
38 Abis-Remove Ack message.
52
1 If timer Tdisconb expires, the BTS may resend the Abis-Remove message.
2
3 5.4.1.1.10 Abis-Remove Ack

4 The Abis-Remove Ack message is used by the BSC to notify the target BS that sent the
5 Abis-Remove message of the outcome of processing the Abis-Remove message.
6
8 The BSC sends an Abis-Remove Ack message to the target BTS that sent the
9 Abis-Remove message to indicate the results of processing the Abis-Remove message.
10 The Cause List element, when present, indicates any exceptions.
11 Please refer to section 6.1.15, “Abis-Remove Ack,” for the format and content of this
12 message.
13
15 None.
16
17
53
1 5.4.2 Soft/Softer Handoff addition (Intra-BTS)

2
Time
MS BTS BSC
Abis-BTS Setup a
Abis-Connect Tsetupb b
Tconnb Abis-Connect Ack c
Abis-BTS Setup Ack d
Tchanstatb
Abis-Traffic channel status
Conditional
Extended/General/Universal e
Handoff Direction Message Abis-IS-2000 FCH Fwd
f
MS Ack Order Abis-IS-2000 FCH Rvs

g
Handoff Completion Message Abis-IS-2000 FCH Rvs

h
BS Ack Order Abis-IS-2000 FCH Fwd i
3 Figure 5.4.2-1 Soft/Softer Handoff addition (Intra-BTS)
5 a. The BSC sends an Abis-BTS Setup message to the BTS to request

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

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

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

19 Setup. If the BSC requested a preferred Walsh code in the
54
4 different Walsh code assignment. The BSC stops the timer Tsetupb.
5 e. If the BSC has chosen to be notified of the start of transmission and

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

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

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

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

18 by sending a BS Ack Order.
19
20
55
1 5.4.3 Soft/Softer Handoff addition (Inter-BTS)

2
Tim e
S o urc e Targ et
MS B TS B TS BSC
A b is-B T S S etu p a
A b is-C o n n ec t T setu p b b
Tc o n n b A b is-C o n n ect A ck c
A b is-B T S S etu p A ck d
A b is-IS-2 0 0 0 F C H F wd ( F o rwa rd F ram es ) e
F o rw a rd Fram es T c h a n sta tb f
A b is-IS -2 0 0 0 F C H Rv s( Id le Fram es) g
A b is-Tra ffic C h a nn el S ta tus
E xten d ed /G en era l/U niv ers al C o n d ition a l h
H a n d o ff Directio n M ess a g e A b is-IS-2 0 0 0 F C H F wd
i
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
l
3 Figure 5.4.3-1 Soft/Softer Handoff addition (Inter-BTS)
4 a. The BSC decides that one or more cells at the target BTS are needed
5 to support the call in soft/softer handoff. The BSC sends an
6 Abis-BTS Setup message to the target BTS to request allocation of
7 radio resources at the BTS. The BSC may allocate a code channel
8 and include it in the Abis-BTS Setup. The BSC starts the timer
9 Tsetupb.
10 b. If resources are available, the target BTS responses with

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

13 Abis connection. The BTS stops timer Tconnb. If the BSC has
14 chosen to be notified of the start of transmission and reception at the
15 target BTS ,the BSC will set Abis-Connect Ack message indicating
16 that Abis-Traffic Channel Status message is requested, starts timer
17 Tchanstatb.
18
56
1 d. The target BTS sends Abis-BTS Setup Ack to acknowledge the

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

9 synchronization has occurred.
10 g. The target BTS begins to send reverse idle frames. The reverse
11 frames contain the timing adjustment information necessary to
12 achieve synchronization.
13 h. If the BSC has chosen to be notified of the start of transmission and

15 BTS have synchronized the Abis traffic sub-channel, the BTS send
16 an Abis-Traffic Channel Status message to the source BTS.
17 i. The BSC sends an Extended / General / Universal Handoff Direction

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

21 k. The MS indicates successful results of processing the Extended /

24 l. The BSC acknowledges receipt of the Handoff Completion Message

26
27
57
1 5.4.4 Soft/Softer Handoff Removal (Inter-BTS)

2
Time
Source Target
MS BT S BT S BSC
Extended/General/Universal
Handoff Direction Message Abis-IS-2000 FCH Fw d
a
b
Handoff Com pletion Message Abis-IS-2000 FCH Rvs

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
g
Abis-BTS Release Ack
h
3 Figure 5.4.4-1 Soft/Softer Handoff Removal (Inter-BTS)
5 a. The BSC sends an Extended / General / Universal Handoff Direction

6 Message to the MS to drop the cell to the active set.
7 b. The MS acknowledges receipt of the Extended / General / Universal

9 c. The MS indicates successful results of processing the Extended /

12 d. The BSC acknowledges receipt of the Handoff Completion Message

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

15 request that the specified cells be removed from the call. The BSC
16 starts timer Tdrptgtb.
58
1 f. The target BTS, upon receipt of the Abis-BTS-Release message,

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

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

9 to acknowledge the removal of the specified cells. The BSC stops
10 timer Tdrptgtb.
11
59
1 5.4.5 Hard Handoff (Inter-BTS)

2
Tim e
Source Target
MS BTS BTS BSC
Abis-BTS Setup a
b
c
Abis-BTS Setup Ack d
Abis-IS-2000 FCH Fwd( Forward Fram es) e
Forward Fram es
Tchanstat f
Abis-IS-2000 FCH Rvs( Idle Fram es)
g
Abis-Traffic Channel Status
Extended/G eneral/Universal Conditional
h
Handoff Direction Message Abis-IS-2000 FCH Fwd
i

j
Reverse Fram es Abis-IS-2000 FCH Rvs( Idle Fram es)
k
Handoff Com pletion Message Abis-IS-2000 FCH Rvs
l
BS Ack Order Abis-IS-2000 FCH Fwd
m
Abis-BTS Release
n
Abis-Rem ove Tdrptgtb
o
Tdisconb
Abis-Rem ove Ack
p
Abis-BTS Release Ack
q
3 Figure 5.4.5-1 Hard Handoff (Inter-BTS)
4 a. The BSC decides that one or more cells at the target BTS are needed
5 to support the call in hard handoff. The BSC sends an Abis-BTS
6 Setup to the target BTS to request allocation of radio resources at the
7 BTS. The BSC starts the timer Tsetupb.
8 b. If resources are available, The target BTS responses with an

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

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

16 BTS have synchronized Abis traffic subchannel, the BTS send an
17 Abis-Traffic Channel Status message to the BSC
18 i. The BSC sends an Extended / General / Universal Handoff Direction

19 Message to the MS to change the cell to the active set.
20 j. The MS acknowledges receipt of the Extended / General / Universal

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

23 preamble to the target BTS.
24 l. The MS indicates successful results of processing the Extended /

27 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

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

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

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

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

7 to acknowledge the removal of the specified cells. The BSC stops
8 timer Tdrptgtb.
62
1 5.5 SMS Delivery

2 Delivery of a mobile terminated SMS (SMS-MT) and a mobile originated SMS
3 (SMS-MO) messages on the control channel is accomplished by the exchange of the
4 following messages.
5 Abis-PCH Msg Transfer
6 Abis-PCH Msg Transfer Ack
7 Abis-ACH Msg Transfer.
8 Delivery of a mobile terminated SMS (SMS-MT) and a mobile originated SMS
9 (SMS-MO) on the traffic channel is accomplished by the exchange of the following
10 messages.
13 5.5.1 SMS Delivery on the Paging channel

14
15 5.5.1.1 Abis-PCH Msg Transfer

17

19 When the MSC determines that it needs to deliver an SMS message to a specific idle
20 mobile station, and a Layer 2 acknowledgment notification is required from the MS, the
21 MSC starts timer T3113, sends the ADDS Page message containing a Tag information
22 element to the BSC. MSC waits for the ADDS Page Ack message.
23 When the MSC determines that it needs to deliver an SMS message to a specific idle
24 mobile station, and the MSC does not require a Layer 2 acknowledgment notification, the
25 MSC sends the ADDS Page message, without a Tag information element, to the BSC.
26 When the BSC receives the ADDS Page message, the BSC sends an Abis-PCH Msg
27 Transfer to transfer a Data Burst Message to the BTS. The Data Burst Message contains
28 an SMS message sent from the MSC using the ADDS Page message. If the Tag
29 information element is included in the ADDS Page message, the BSC requires a Layer 2
30 acknowledgement from the MS by setting a Layer 2 Ack Request/Results field to ‘1’.
31 And ARQ fields of the Data Burst Message are also set to values that require the Layer 2
32 Acknowledgement.
33 When the BTS receives the Abis-PCH Msg Transfer message, the BTS sends Data Burst
34 Message on the Paging channel.

36 None.
37
63
1 5.5.1.2 Abis-PCH Msg Transfer Ack

3
4 5.5.1.2.1 Successful Operarion

5 If the Layer 2 acknowledgement is required, that is to say an Abis Ack Notify element
6 contained in the Abis-PCH Msg Transfer message is presented, the BTS sends the
7 Abis-PCH Msg Transfer Ack after the BTS receives an MS Ack Order from the MS. On
8 receipt of the Abis-PCH Msg Transfer Ack, the BSC will wait for A Abis ACH Message
9 Transfer carrying an MS Ack Order from the MS. On receipt of the Abis ACH Message
10 Transfer message the BSC sends a ADDS Page Ack to the MSC.
11

13 None.
14
15 5.5.1.3 Abis-ACH Msg Transfer

17

19 The BTS without L2 termination simply transfers an MS Ack order to the BSC by
20 utilizing an Abis-ACH Msg Transfer, when the BTS receives the MS Ack order.
21 On receipt of the MS Ack Order transferred by the Abis-ACH Msg Transfer, the BSC
22 sends the ADDS Page Ack to the MSC.
23

25 None.
26
27
28
64
1 5.5.2 Call flow example for SMS Delivery on the Paging channel
2 This section provides the call flow description for the delivery of an SMS from the MSC to an idle
3 mobile station on the paging channel.
4
BS
ADDS Page
Abis--PCH Msg Transfer a
(Data Burst Message)
b
Data Burst Message
c
MS Ack Order Abis-PCH Msg Transfer Ack T3113
d
Abis-ACH Msg Transfer
(MS Ack Order) ADDS Page Ack
e
6 Figure 5.5.2-1 SMS Delivery on the Paging channel
7 a. When the MSC determines that a point-to-point short message should be sent to an idle
8 MS, the MSC sends an ADDS Page message to the BSC. The ADDS Page message contains the
9 SMS message in its ADDS User Part information element. If the MSC requires an acknowledgment,
10 it will include the Tag element in the ADDS Page message. The MSC also starts timer T3113.
11 b. The BSC sends the Abis-PCH Msg. Transfer that includes a Data
12 Burst message. The Data Burst Message contains the short message
13 in received ADDS Page.
14 c. The BTS transfers the Data Burst message that is included in the
15 Abis-PCH Msg. Transfer message, on a Paging Channel.
16 d. In case that the BTS receives the Abis Ack Notify element included
17 in the Abis-PCH Msg Transfer message, the BTS sends Abis-PCH
18 Msg Transfer Ack after Layer 2 acknowledgement, i.e. receiving an
19 MS Ack Order from the MS. The BTS L2 Termination is set to ‘1’ to
20 indicate that Layer 2 is terminated at the BTS. When the BSC
21 receives the Abis-PCH Msg Transfer Ack and Layer 2 is terminated
22 at the BTS,
23 e. The BSC sends ADDS PAGE Ack to the MSC when the BSC
24 receives Abis-PCH Msg Transfer Ack.
65
1 f. When the MSC receives the ADDS Page Ack, the MSC stops timer
2 T3113 if the timer was previously started.
3
4
66
1 5.5.3 SMS Delivery on the Access channel

2
3 5.5.3.1 Abis-ACH Msg Transfer

5

7 When the BTS receives the Data Burst Message that contains an SMS message on the
8 Access channel from the MS, the BTS sends Abis-ACH Msg Transfer to transfer the Data
9 Burst Message to the BSC.
10
11 When the MS requires Layer 2 acknowledgement, the BTS sends the MS Ack Order to
12 the MS on the Paging channel.
13 The BSC sends the ADDS Transfer that includes the SMS message to the MSC.
14

16 None
17
18 5.5.3.2 Abis-PCH Msg Transfer

20

22 When the BTS receives the Abis-PCH Msg Transfer that contains the BS Ack Order, the
23 BTS sends the BS Ack Order to the MS on the Paging channel and sends the Abis-PCH
24 Msg Transfer Ack to the BSC.
25

27 None
28
29 5.5.3.3 Abis-PCH Msg Transfer Ack

30 See section 5.1.10
31
67

2 When the BSC receives the Abis-PCH Msg Transfer Ack from the BTS, the BSC knows
3 that the BTS received the Abis-PCH Msg Transfer successfully. A BTS L2 Termination
4 field in the Abis-PCH Msg Transfer Ack is set to ‘0’.
5

7 None
8
9
68
1 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
4 the MSC on the access channel.
BS
MS BTS BSC MSC
Time Comment
Data Burst Message

Abis-ACH Msg Transfer
a
b
BS Ack Order ADDS Transfer
c
5
6
7 Figure 5.5.3.5-1 SMS Delivery on the Access channel
8 a. a. The MS sends a Data Burst Message on the Access

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

13 MS Ack Order to the MS on the Paging channel.
14 c. The BSC sends the ADDS Transfer message to the MSC that
15 contains the Data Burst Message received from the MS in the ADDS
16 User Part element
17
18
69
1 5.5.4 SMS Delivery on the Traffic channel to MS

2 This section provides the call flow description for the delivery of an SMS from the MSC to a mobile
3 station operating on the traffic channel.
BS
MS BTS BSC MSC
Time Comment
ADDS Deliver
Abis-IS-2000 FCH Fwd a
b
Data Burst Message
c
MS Ack Order
Abis-IS-2000 FCH Rvs d
(MS Ack Order)
e
ADDS Deliver Ack
f
4
5 Figure 5.5.4-1 SMS Delivery on the Traffic channel to MS
6 a. When the MSC determines that a point-to-point short message should

7 be sent to an idle MS, the MSC sends an ADDS Deliver message to
8 the BSC. The ADDS Deliver message contains the short message in
9 the ADDS User Part information element.
10 b. The BSC sends Abis-IS-2000 FCH Fwd containing the Data Burst
11 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

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

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

18 Deliver.
19
20
70
1 5.5.5 SMS Delivery on the Traffic channel from MS

2 This section provides the call flow description for the delivery of an SMS from a mobile station
3 operating on the traffic channel to the MSC.
4
BS
Data Burst Message

A3-IS-2000 FCH Rvs a
b
ADDS Deliver
A3-IS-2000 FCH Fwd c
(BS Ack Order)
d
BS Ack Order
e
6 Figure 5.5.5-1 SMS Delivery on the Traffic channel from MS
7 a. The MS sends a Data Burst Message on the Access Channel to

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

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

14 Ack Order to acknowledge receipt of the Data Burst Message, if it is
15 required.
16 e. The BTS transfer the BS Ack Order.
17
18
71
1 5.6 Traffic Burst Operation

2 This section describes the messages and procedures used between BSC and BTS to
3 support Traffic Burst Operation. The following messages are used:
4 Abis-Burst Request
5 Abis-Burst Response
6 Abis-Burst Commit
7
8 5.6.1 Abis-Burst Request

9 The Abis-Burst Request message is used by the BSC to request that a BTS reserve a set
10 of radio resources in support of a traffic burst.
11

13 When the BSC determines that a traffic burst is required in support of a particular service
14 instance, it determines the cells needed to support the traffic burst and sends an
15 Abis-Burst Request to the BTS. This message requests that the BTS reserve the
16 indicated radio resources for a traffic burst beginning at a particular time and for a
17 particular duration. This message may also be used to request an extension of an
18 existing traffic burst by specifying the appropriate beginning and duration times. The
19 BSC then starts timer Tbstreqb.
20 Please refer to section 6.1.9, “Abis-Burst Request,” for the format and content of this
21 message.
22

24 If timer Tbstreqb expires, the BSC may choose to resend the Abis-Burst Request
25 message.
26
27 5.6.2 Abis-Burst Response

28 The Abis-Burst Response message is used by the BTS to respond to a request that it
29 reserve radio resources in one or more cells for support of traffic burst.
30

32 When the BTS receives an Abis-Burst Request message, it determines whether it can
33 provide the requested radio resources in support of the traffic burst. If a traffic burst for
34 the same service instance was already committed (and possibly active) at the time the
35 Abis-Burst Request message is received, the BTS shall examine the starting time and
72
1 duration, as well as the set of requested resources to determine if this request extends the
2 traffic burst. The BTS then creates one or more Abis-Burst Response message(s)
3 indicating its ability to support the requested traffic burst for each of the cells included in
4 the Abis-Burst Request message. The BTS starts timer Tbstcomb after each Abis-Burst
5 Response message. The BSC stops timer Tbstreqb when it receives Abis-Burst
6 Response message(s) accounting for all cells included in the Abis-Burst Request
7 message.
8 Please refer to section 6.1.10, “Abis-Burst Response,” for the format and content of this
9 message.
10

12 If timer Tbstcomb expires, the BTS may decommit all radio resources committed for the
13 cell(s) included in this message.
14
15 5.6.3 Abis-Burst Commit

16 The Abis-Burst Commit message is used by the BSC to indicate to the BTS the set of
17 target radio resources that will be used to support a traffic burst.
18

20 When the BSC has gathered traffic burst commitment information from BTSs and has
21 prepared the frame selector(s) to support the traffic burst, it sends an Abis-Burst Commit
22 message to the BTSs to indicate the set of committed target radio resources that will be
23 used to support the traffic burst.
24 When the BTS receives this message, it shall prepare all indicated resources for support
25 of the traffic burst. Any resources that were reserved but are not included in this
26 message may be decommitted by the BTS. This includes bandwidth and burst duration.
27 The BTS stops timer Tbstcomb.
28 Please refer to section 6.1.11, “Abis-Burst Commit,” for the format and content of this
29 message.
30

32 None
33
34 5.6.4 High Speed Packet Data

35 Support of high speed packet data (i.e., speeds greater than 14.4 kbps) may be
36 accomplished through the use of multiple physical channels. These physical channels
37 are supported in the infrastructure using Abis traffic connections during soft/softer
38 handoff. Setup of an Abis connection for a traffic burst is accomplished using
39 Abis-Burst Request, Abis-Burst Response, and Abis-Burst Commit messages.
73
1 Establishment of the Abis connection for the supplemental channel (SCH) is

2 accomplished via the Abis-BTS Setup, Abis-BTS Setup Ack, Abis-Connect and
3 Abis-Connect Ack messages.
4 In this version of this standard, it is assumed that any leg for a supplemental channel will
5 be established on a cell that already supports a leg for the fundamental channel (FCH) or
6 the dedicated control channel (DCCH) for the same mobile station. To minimize the
7 time required to establish a traffic burst, the Abis connection for the SCH is established
8 on the BTS at the transmission of the first data burst. When a leg is established for a
9 SCH, only the terrestrial resources are allocated, i.e., the Abis connection. This involves
10 choosing the traffic circuit to be used and establishing context between the BTS and the
11 BSC/SDU function. Allocation of radio resources for the SCH is made each time that a
12 traffic burst is set up.
13 When the BSC realizes that it is necessary to allocate radio resources for a traffic burst in
14 either the forward or reverse direction or both, it sends an Abis-Burst Request message to
15 each BTS to request reservation of specific radio resources. Each BTS responds with an
16 Abis-Burst Response message to indicate radio resource reservations. Once the BSC has
17 received all expected Abis-Burst Response messages, it sends an Abis-Burst Commit
18 message to each BTS to confirm the traffic burst and the set of radio resources to be used.
19 Each BTS then prepares all indicated cells, connects them to the pre-established Abis
20 connections, and then participates in the burst. This is shown in the example in section
21 5.6.5 and 5.6.6.
22
23
24
74
1 5.6.5 Initial Traffic Burst Example – Abis Connection Not Yet Established
2 The example below describes the support of traffic burst operation when the Abis
3 connection has not yet been established.
4
MS BTS BSC M SC Time Comment
SCRM (data to be sent)

a
Abis-BTS Setup
b
c
d
Abis-BTS Setup Ack
e
Abis-Burst Request
f optional
Abis-Burst Response Tbstreqb g optional
Tbstcomb Abis-Burst Commit h
ESCAM
i
Layer 2 Ack
j
Forward and/or reverse traffic burst
k
5
6
7 Figure 5.6.5-1 Initial Traffic Burst Example
8 a. Either the BSC receives an indication from the MS (via a SCRM

9 message) or from the network (via data being received from the
10 PDSN) that data needs to be sent to/from the MS. The BSC decides a
11 traffic burst on one or more new cells at a BTS is required in support
12 of a service instance in soft/softer handoff. This example assumes
13 that a Fundamental Channel (FCH) or Dedicated Control Channel
14 (DCCH) leg already exists on the selected cell(s) at the BTS.
15 b. The BSC assigns an Abis From ID value and sends an Abis BTS
16 Setup message to the BTS to establish an Abis traffic connection to
17 support a Supplemental Channel (SCH) for the call. This example
18 shows only a single Abis connection being established. The BSC is
19 not required to assign a physical Frame Selector at this time. The
20 BSC starts timer Tsetupb.
75
1 c. The BTS assigns a traffic circuit and optionally a Channel Element

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

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

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

23 BTS to request the reservation of the needed radio resources for the
24 supplemental channel. The BSC starts timer Tbstreqb. Note that the
25 BSC may send an Abis-Burst Request to the BTS at any time after
26 receiving the Abis-BTS Setup message in step c, and that the set of
27 cells may be subset of the cells assigned in step a-e.
28 g. The BTS determines that it can reserve part or all of the requested
29 resources and sends Abis-Burst Response message(s) including Abis
30 From ID to the BSC indicating the resources that have been reserved
31 and committed to the traffic burst, and the cause value for any
32 uncommitted cells. Each reservation includes a physical Channel
33 Element. Note that the physical Channel Element may be allocated
34 any time after step b. The BTS starts timer Tbstcomb. The BSC stops
35 timer Tbstreqb.
36 h. In the Abis-Burst commit message, Walsh codes are used as obtained

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

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

14 traffic burst information for the specified duration, or until the BSC
15 terminates or extends the traffic burst.
16
17
77
1 5.6.6 Subsequent Traffic Burst Example

2 The example below describes the support of traffic burst operation when the Abis
3 connection for the supplemental channel (SCH) has already been established.
4
SCRM (data to be sent)

a
Abis-Burst Request
b optional
Abis-Burst Response Tbstreqb
c optional
Tbstcomb
Abis-Burst Commit
d
ESCAM
e
Layer 2 Ack
f
Forward and/or reverse traffic burst g
6 Figure 5.6.6-1 Subsequent Traffic Burst Example
7 a. Either the BSC receives an indication from the MS (via a SCRM

8 message) or from the network (via data being received from the
9 PDSN) that data needs to be sent to/from the MS.
10 When the BSC has knowledge of resources for SCH in the BTS, the
11 procedure at step b and at step c is not necessary.
12 b. The BSC decides a traffic burst is required on one or more cells for
13 which an Abis connection already exists in support of a supplemental
14 channel. The BSC sends an Abis-Burst Request to the BTS to request
15 the reservation of the needed radio resources for the supplemental
16 channel. The BSC starts timer Tbstreqb.
17 c. The BTS determines that it can reserve part of all of the requested
18 resources and sends Abis-Burst Response message(s) to the BSC
19 indicating the resources that have been reserved and committed to the
20 traffic burst, and the cause value for any uncommitted cells. Each
21 reservation includes a physical Channel Element. Note that the
22 physical Channel Element may be allocated any time after step b. The
23 BTS starts timer Tbstcomb. The BSC stops timer Tbstreqb.
24 d. In the Abis-Burst commit message, Walsh codes are used as obtained

25 from the Abis-Burst Response message, but the rate could be
78
1 downgraded in the Abis-Burst commit message by the BSC. Thus the

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

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

15 burst information for the specified duration, or until the BSC
16 terminates or extends the traffic burst.
17
79
1 5.7 PACA Service

2 PACA queuing processing is performed by following message;
3 Abis-PACA Update
4
5 5.7.1 PACA Updating

6
7 5.7.1.1 Abis-PACA Update

8 The Abis-PACA Update message is used by the BSC to instruct the BTS to update PACA
9 related information.
10

12 The Abis-PACA Update message is sent by the BSC upon receiving a PACA Update
13 message from the MSC with an indication to “Remove MS from the queue”, “Remove
14 MS from the queue and release MS” or “Update Queue Position and Release MS” or if
15 the BSC autonomously decides to do a cancel a PACA call.
16

18 None.
19
20
21
22
80
1 5.7.2 Call flow example for PACA Updating

2 This section describes the call flow associated with PACA updating procedure.
3
BS
PACAUpdate
a
Abis-PACAUpdate
Tpaca2 b
PACAUpdate Ack
c
5 Figure 5.7.2-1 PACA Updating procedure
6 a. When the MSC determines that the PACA control for the BSC is
7 needed, the MSC sends the PACA Update message and starts the
8 timer Tpaca2.
9 b. Upon receipt of the PACA Update message with an indication to

10 “Remove MS from the queue”, “Remove MS from the queue and
11 release MS” or “Update Queue Position and Release MS”, the BSC
12 sends the Abis-PACA Update message to the BTS. In case of
13 “Remove MS from the queue and release MS” or “Update Queue
14 Position and Release MS” the BSC sends a message to the MS via
15 the Abis-IS-2000 FCH Fwd message, and in addition the BSC sends
16 the Abis-PACA Update message to instruct the BTS to perform the
17 desired update action.
18 c. The BSC sends the PACA Update Ack message to the MSC. The
19 MSC stops the timer Tpaca2 upon receipt of the PACA Update Ack
20 message.
21
22
23
24
25
26
81
1 6. Abis Interface Message
2 6.1 Abis Interface Message Formats

3 For Abis interface messages there are a number of information elements that are
4 individually defined in section 7.1. Each information element in a given message is
5 tagged with a reference in section 7.1, a direction indication (i.e., some elements within a
6 message are bi-directional and others are not), and a Required or Optional type (M/O)
7 indicator.
8 The inclusion of information elements in each message is specified as follows:
9 R - information elements which are required for the message.
10 O - information elements which are optional for the message.
11
12 6.1.1 Message Body, Coding, and Ordering of Elements

13 For each Abis Interface message there are a number of information elements that are
14 individually defined in section 7.1. Each information element in a given message is
15 tagged with a reference in section 7.1, a direction indication (i.e., some elements within a
16 message are bi-directional and others are not), and a required or optional type.
17 Information elements that are marked as optional carry an additional explanation of when
18 they are used. Some information elements are reused in multiple messages.
19
20 The DIRECTION indication associated with each message element pertains to the use of
21 that particular message element when used with the particular message (i.e., use of the
22 message element may be different in other messages). The format of the DIRECTION
23 indication is as follows:
24 Table 6.1.1-1 Element Flow DIRECTION Indication
BTS -> BSC Element flows from BTS to the BSC
BSC -> BTS Element flows from the BSC to the BTS
25
26 The inclusion of information elements in each message is specified as follows:
27 • O - information elements which are optional for the message. The conditions for inclusion of this
28 element are defined in the operation(s) where the message is used and in footnotes associated with the
29 table defining the order of information elements in the message.
30 • R - Required in this version of this specification in the message whenever the message is sent.
31 Information elements that are required for a given message shall be present, and shall
32 appear in the order shown in the message definitions in this chapter.
33
82
1 Information elements that are optional for a given message are included as needed for
2 specific conditions. When included, they shall appear in the order shown in the message
3 definitions in this chapter.
4
5 An information element can very well be required for some messages and optional for
6 other messages.
7 All information elements shall include their Information Element Identifier (IEI) except
8 for the “Message Type” IE.
9 The bitmap tables in the message subsections of 6.1 are patterned after the format for the
10 information elements of section 7.1 and use the following conventions:
11 ⇒ Element Name{<# instances>:
12 = Name of information element.
13 Different elements within a message are separated by
14 double lines.
15 Fields within elements are separated by single lines.
16 Octets are renumbered at the beginning of every element.
17 [<values>] = Set of allowed values.
18 } Element Name The number of instances of an element is 1 by default. If

19 the Element Name{<# instances … }Element Name
20 notation is used, the <# instances> notation indicates:
21 n = 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 = Number of instances of the bracketed set of fields where

28 <# instances> notation indicates:
29 n = 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
1 ssss ssss
3 6.1.2 Message Processing Guidelines

4 The following message processing guidelines apply unless overridden by explicit
5 processing directions in other places within this standard.
6 1. If a message is received containing a Message Type value that is not defined for the revision
7 level implemented then the message shall be discarded and ignored. There shall be no change
8 in state or in timers due to receipt of an unknown message.
9 2. If a message is received that contains an information element which is defined for the revision
10 level implemented but contains invalid values in some fields, these fields shall be ignored and
11 the remainder of the information element processed to the extent possible. The message and all
12 other information elements shall be processed to the extent possible. Failure handling may be
13 initiated if call processing cannot continue. See also message processing guidelines 9 and 10
14 below.
15 3. If a message is received that contains an Information Element Identifier which is not defined for
16 the revision level implemented then that element shall be discarded and ignored. The message
17 shall be processed to the extent possible. Failure handling may be initiated if call processing
18 cannot continue.
19 4. If a known but unexpected optional information element is received, that information element
20 shall be ignored. The message and all other information elements shall be processed.
21 5. If a message is received without an expected optional information element the message shall be
22 processed to the extent possible. Failure handling may be initiated if call processing cannot
23 continue.
24 6. No value of an information element that is indicated as “reserved” for the revision level
25 implemented shall be sent. If a valid information element contains a value which is specified
26 as “reserved” or is otherwise not defined in the revision level implemented then this field shall
27 be ignored and the remainder of the information element processed to the extent possible. The
28 message and all other information elements shall be processed to the extent possible.
29 7. Octets and bits designated as “Reserved” or which are undefined for the revision implemented
30 shall be set to zero by a sending entity and ignored by a receiving entity.
31 8. If an element is received containing a field that is larger than expected, i.e., is indicated as
32 having more bits/octets than expected, then the expected bits/octets of that field shall be
33 processed to the extent possible and the additional bits/octets shall be ignored.
84
1 9. If an element is received containing a field that is smaller than expected, i.e., is indicated as
2 having fewer bits/octets than expected, then the length field or other indicator will be considered
3 correct and the bits/octets actually present in the element shall be processed to the extent
4 possible. Failure handling may be initiated if call processing cannot continue.
6 6.1.3 Message Definition Guidelines

7 1. New messages shall have a Message Type that was never previously used.
8 2. Information Element Identifiers may be reused in future revisions only when:

9 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

15 revisions. The new version shall define the error handling when previously
16 valid values are received.
17 4. Octets and bits which are undefined or which are defined as reserved may be
18 used in future revisions.
19 5. New Information Elements in a message shall be defined after all previously

20 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,

23 provided that the Information Element is defined with a length field.
24
25
26
85
1 6.2 Abis interface messages

2
3 6.2.1 Abis-ACH Msg Transfer

4 This Abis interface message is sent from the BTS to the BSC to notify the BSC of the
5 reception of the contained message or Layer 2 acknowledgment on the specified access
6 channel.
Information Element Section Element Direction Type
Reference
Message Type 7.2 BTS -> BSC R
Correlation ID 7.3 BTS -> BSC O
Mobile Identity (IMSI) 7.4 BTS -> BSC O
Mobile Identity (ESN) 7.4 BTS -> BSC O
Cell Identifier 7.5 BTS -> BSC a
O
BTS L2 Termination 7.30 BTS -> BSC O
Air Interface Message 7.6 BTS -> BSC O
CDMA Serving One Way Delay 7.24 BTS -> BSC R
Authentication Challenge Parameter (RAND) 7.32 BTS -> BSC O
7 a. This element indicates the cell at the BTS on whose access channel the
8 air-interface message or Layer 2 acknowledgment was received.
9
10 The following table shows the bitmap layout for the Abis-ACH Msg Transfer message:
7 6 5 4 3 2 1 0 Octet
⇒ Message Type = [8EH] 1
⇒ Correlation ID: A3/A7 Element Identifier = [13H] 1
Length = [04H] 2
(MSB) 3
Correlation Value = <any value> 4
5
(LSB) 6
⇒ Mobile Identity (IMSI): A1 Element Identifier = [0DH] 1
Length = [06H-08H] (10-15 digits) 2
Identity Digit 1 = [0H-9H] (BCD) Odd/even Type of Identity 3
Indicator = [110] (IMSI)
= [1,0]
Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4
86
••• •••
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n
= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1
⇒ Mobile Identity (ESN): A1 Element Identifier = [0DH] 1
Length = [05H] 2
Identity Digit 1 = [0000] Odd/even Type of Identity 3
Indicator = [101] (ESN)
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
⇒ Cell Identifier: A1 Element Identifier = [05H] 1
Length = [03H] 2
Cell Identification Discriminator = [02H] 3
(MSB) Cell = [001H-FFFH] 4
(LSB) Sector = [0H-FH] (0H = Omni) 5
⇒ BTS L2 Termination: Abis Element Identifier = [73H] 1
Length = [01H] 2
Reserved = [0000 000] BTS 3
L2
Term
inati
on
=
[0/1]
⇒ Air Interface Message: Abis Element Identifier = [21H] 1
Length = <variable> 2
TIA/EIA-IS-2000 Message Type = <00H to FFH> 3
Air Interface Message Length = <variable> 4
(MSB) 5
Air Interface Message = <any value> …
(LSB) k
⇒ CDMA Serving One Way Delay: A1 Element Identifier = [0CH] 1
Length = [05H] 2
87
(MSB) CDMA Serving One Way Delay = [0000H-FFFFH] (x100ns) 6

(LSB) 7
⇒ Authentication Challenge Parameter: A1 Element Identifier = [41H] 1
Length 2
Reserved Random Number Type 3
(MSB) 4
RAND Value 5-m
(LSB) m+1
1
88
1 6.2.2 UNUSED SECTION

2
3 6.2.3 Abis-PCH Msg Transfer

4
5 This Abis interface message is sent from the BSC to the BTS to request the sending of the
6 contained message on the specified paging channels to a mobile station.
Reference
Message Type 7.2 BSC -> BTS R
Correlation ID 7.3 BSC -> BTS a
O
Mobile Identity (IMSI) 7.4 BSC -> BTS d
O
Mobile Identity (ESN) 7.4 BSC -> BTS O
Cell Identifier List 7.13 BSC -> BTS b
O
Air Interface Message 7.6 BSC -> BTS O
Layer 2 Ack Request/Results 7.8 BSC -> BTS c
O
Abis Ack Notify 7.34 BSC -> BTS e
O
7 a. If this element is included in this message, the value shall be returned in the
8 Abis-PCH Msg Transfer Ack message.
9 b. This element indicates the cells at the BTS on whose paging channel(s) the
10 air-interface message is to be sent.
11 c. This element is included if the BSC wants a Layer 2 acknowledgment from

12 the MS.
13 d. Either IMSI or ESN, but not both is included. (Only one instance of Mobile
14 ID should be allowed)
15 e. The BSC includes this element in this message when it wants to be

16 informed that a layer 2 ack was received from the MS. The BTS will use the
17 Abis-PCH Msg Transfer Ack message to notify the BSC that the layer 2 ack
18 was received. This element should not be included if the Abis Ack
19 Requested IE is absent.
20
21
89
1 The following table shows the bitmap layout for the Abis-PCH Msg Transfer
2 message:
7 6 5 4 3 2 1 0 Octet
⇒ Message Type = [8CH] 1
Length = [04H] 2
(MSB) 3
5
(LSB) 6
= [1,0]
••• •••
Length = [05H] 2
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
⇒ Cell Identifier List: A1 Element Identifier = [1AH] 1
Cell Identification {1+:
(MSB) Cell = [001H-FFFH] j
(LSB) Sector = [0H-FH] (0H = Omni) j+1
} Cell Identification
90
⇒ Air Interface Message: Abis Element Identifier = [21H] 1

TIA/EIA-IS-2000 Message Type = <00H to FFH> 3
Air Interface Message Length = <variable> 4
(MSB) 5
Air Interface Message = <any value> …
(LSB) k
⇒ Layer 2 Ack Request/Results: Abis Element Identifier = [23H] 1
Length = [01H] 2
Reserved = [0000 000] Layer 2 3
Ack
= [0/1]
⇒ Abis Ack Notify: Abis Element Identifier = [75H] 1

Length = [00H] 2
1
2
91
1 6.2.4 Abis-PCH Msg Transfer Ack

2 This Abis interface message is sent from the BTS to the BSC to report the results of
3 sending an air interface message on the specified paging when a layer 2 acknowledgment
4 had been requested by the BSC.
Reference
Correlation ID 7.3 BTS -> BSC a
O
Cause 7.9 BTS -> BSC b
O
BTS L2 Termination 7.30 BTS -> BSC O
5 a. This element is included if the Abis-PCH Msg Transfer contained this element.
6 It contains the value received on that message.
7 b. Inclusion of this element indicates a failure to send the paging channel message
8 as requested in the Abis-PCH Msg Transfer message. Allowable cause values:
9 OAM&P intervention, Equipment failure, SMS Message too long for delivery
10 on the paging channel.
11
12 The following table shows the bitmap layout for the Abis-PCH Msg Transfer Ack
13 message:
7 6 5 4 3 2 1 0 Octet
⇒ Message Type = [8DH] 1
Length = [04H] 2
(MSB) 3
5
(LSB) 6
⇒ Cause: A1 Element Identifier = [04H] 1
Length = [01H] 2
ext = [0] Cause Value = 3
[07H (OAM&P intervention),
20H (equipment failure),
71H (SMS Message too long for delivery on the paging channel)]
92
⇒ BTS L2 Termination: Abis Element Identifier = [73H] 1

Length = [01H] 2
Reserved = [0000 000] BTS 3
L2
Termi
natio
n
=
[0/1]
1
93

3
4 This Abis interface message is sent from the BSC to the BTS in order to request the BTS
5 to assign radio resource, the attributes of which are defined within the message.
Information Element Section Element Type
Reference Direction
Call Connection Reference 7.10 BSC -> BTS R
Band Class 7.11 BSC -> BTS O
Privacy Info 7.12 BSC -> BTS O
SDU-ID 7.14 BSC -> BTS O
Mobile Identity (IMSI) 7.4 BSC -> BTS O
Mobile Identity (ESN) 7.4 BSC -> BTS O
Physical Channel Info 7.15 BSC -> BTS O
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
CDMA Serving One Way Delay 7.24 BSC -> BTS R
CDMA Target One Way Delay 7.30 BSC -> BTS O
Walsh Code Assignment Request 7.31 BSC -> BTS Of
6 a. This element may be present only when the call is eligible for PACA service.
7 b. This element may be only used for packet data calls. In this version of this
8 standard, this element is used to carry a Packet Priority field coded on 4 bits.
9 Values ‘1110’ and ‘1111’ are reserved.
10 c. This element may be used to indicate a code channel that is allocated by the BSC.
11 It is assumed that the Cell Info Record is used and 0 fills the rest of the fields.
12 d. This element is optionally included by the BSC. If included, the value shall be
13 saved and used by the BTS in subsequent Abis message for this call association.
14
15 e. If the physical channel type is SCH, then the Extended Handoff Direction
16 Parameters Field Length shall be set to ‘0’ and the following fields shall be
94
1 ignored in the Cell Information Record: QOF_Mask, PWR_Comb_Ind, Pilot_PN,

2 Code Channel.
3 f. This element is included when the BSC requests the BTS for assignment of the
4 Walsh code. If this element is included, Code Channel field of the Abis Connect
5 Information IE is invalid.
6 g. The Service option is set to the service option received in the Origination or
7 Paging Response message from MS.
95
1 The following table shows the bitmap layout for the Abis-BTS Setup message:
7 6 5 4 3 2 1 0 Octet
⇒ Message Type = [80H] 1
⇒ Call Connection Reference: A1 Element Identifier = [3FH] 1
Length = [08H] 2
(MSB) Market ID = <any value> 3
(LSB) 4
(MSB) Generating Entity ID = <any value> 5
(LSB) 6
(MSB) 7
Call Connection Reference = <any value> 8
9
(LSB) 10
⇒ Band Class: A1 Element Identifier = [5DH] 1
Length = [01H] 2
Reserved = [000] Band Class = [ 00001 (PCS) 3
00010 (TACS)
00011 (JTACS)
00100 (Korean PCS)
00101 (NMT-450)
00110 (IMT-2000)]
⇒ Privacy Info: A3/A7 Element Identifier = [1DH] 1
Privacy Mask Information {1+:
Reserved Privacy Mask Type = [00001,00010] Status Available j
= [0] (public, private) = [0,1] = [0,1]
Privacy Mask Length = <variable> j+1
(MSB) Privacy Mask = <any value> j+2
••• •••
(LSB) k
} Privacy Mask Information
⇒ SDU ID: A3/A7 Element Identifier = [4CH] 1
(MSB) SDU ID = <any value> 3
••• •••
(LSB) m
96

= [1,0]
••• •••
Length = [05H] 2
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
⇒ Physical Channel Info: A3/A7 Element Identifier = [07H] 1
Length =[05H] 2
Frame Offset = [00H – FFH] 3
A3 Traffic Channel Protocol Pilot Gating Rate ARFCN (high part) 4
Stack = [001] = [00, 01, 10] = [000-111]
ARFCN (low part) = [00H-FFH] 5
Count of Physical Channels = [01H-02H] 6
Reserved = [0000] OTD= Count of Physical Channels = 6
[0,1] [001 – 010]
Physical Channel 2 = Physical Channel 1 = 7
0H – N/A, 0H – IS-95,
1H – FCH, 1H – FCH,
2H – SCH, 2H – SCH,
3H – DCCH 3H – DCCH
⇒ Service Option: A1 Element Identifier = [03H] 1
(MSB) Service Option 2
= [0000H - XXXXH] (LSB) 3
⇒ PACA Timestamp: A1 Element Identifier = [4EH] 1

Length = [04H] 2
(MSB) 3
97
PACA Queuing Time = <any value> 4

5
(LSB) 6
⇒ Quality of Service Parameters: A1 Element Identifier = [07H] 1
Length = [01H] 2
Reserved = [0000] Packet Priority = [0000 – 1101] 3
⇒ Abis Connect Information{1+: A3/A7 Element Identifier = [1BH] 1
Reserved = [000] Physical Channel Type New A3 3

= [0H - IS-95 Fundamental Channel, Indicator
1H – Fundamental Channel (FCH), = [0,1]
2H – Supplemental Channel (SCH), (exist,new)
3H – Dedicated Control Channel(DCCH)],
Length of Cell Info Record = <variable> 4
Cell Info Record {1+:
Cell Identification Discriminator = [02H] j
(MSB) Cell = [001H-FFFH] j+1
Reserved = [000] QoF Mask = New PWR_ (MSB) k
[00, 01, 10, 11] Cell Comb
Indicator _Ind
= [0,1] = [0,1]
(old, new) (no,yes)
Pilot_PN = <any value> (LSB) k+1
Code Channel = [00H - FFH] k+2
} Cell Info Record
Length of Traffic Circuit ID = [05H] 1
Traffic Circuit ID {1:
Length of Traffic Circuit Identifier = [02H] 2
(MSB) Traffic Circuit Identifier = <any value> 3
(LSB) 4
Length of Traffic Connection Identifier = [01H] 5
Traffic Connection Identifier = [00H-FFH] 6
(AAL2 CID)
} Traffic Circuit ID
Extended Handoff Direction Parameters Field Length = [09H] p
98
Extended Handoff Direction Parameters {1+:

Search Window A Size (Srch_Win_A) = Search Window N Size (Srch_Win_N) = p+1
[0H-FH] [0H-FH]
Search Window R Size (Srch_Win_R) = Add Pilot Threshold (T_Add) high order = p+2
[0H-FH] [0H-FH]
T_Add (low order) Drop Pilot Threshold (T_Drop) = [000000-111111] p+3
= [00-11]
Compare Threshold (T_Comp) Drop Timer Value (T_TDrop) p+4
= [0H-FH] = [0H-FH]
Neighbor Max Age (Nghbor_Max_AGE) Reserved = [0000] 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> q
(MSB) Channel Element ID = <any value> q+1
••• •••
(LSB) r
Length of A3 Originating ID = [02H] r+1
(MSB) A3 Originating ID = <any value> r+2
(LSB) r+3
Length of A7 Destination ID = [02H] r+4
(MSB) A7 Destination ID = <any value> r+5
(LSB) r+6
}Abis Connect Information
⇒ Abis Originating ID: Abis Element Identifier = [71H] 1
Length of Abis Originating ID = [02H] 1
(MSB) Abis Originating ID = <any value> 2
(LSB) 3
Length = [05H] 2
99
(LSB) 7
⇒ CDMA Target One Way Delay: Abis Element Identifier = [0BH] 1
Length = [02H] 2
CDMA Target One Way Delay (high part) 3
CDMA Target One Way Delay (low part) 4
⇒ Walsh Code Assignment Request: Abis Element Identifier = [74H] 1
Length = [00H] 2
1
2
100

2 This message is sent from BTS to BSC to acknowledge the Abis-BTS Setup.
3
Reference Direction
Call Connection Reference 7.10 BTS -> BSC R
Abis Connect Information 7.20 BTS -> BSC O
Abis Originating ID 7.21 BTS -> BSC Oa
Abis Destination ID 7.22 BTS -> BSC Ob
Cause 7.9 BTS -> BSC Oc
4 a. This element is optionally included by the BTS. If included, the value

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

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

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

2H – Supplemental Channel (SCH), (exist,new)
3H – Dedicated Control Channel(DCCH)],
Reserved = [000] QoF Mask = New PWR_ (MSB) k
[00, 01, 10, 11] Cell Comb
Indicator _Ind
= [0,1] = [0,1]
(old, new) (no,yes)
} Cell Info Record
102
(LSB) 4
(AAL2 CID)
Extended Handoff Direction Parameters Field Length = [09H] p
[0H-FH] [0H-FH]
[0H-FH] [0H-FH]
= [00-11]
= [0H-FH] = [0H-FH]
= [0H-FH]
Length of Channel Element ID = <variable> q
••• •••
(LSB) r
Length of A3 Originating ID = [02H] r+1
(LSB) r+3
Length of A7 Destination ID = [02H] r+4
(MSB) A7 Destination ID = <any value> r+5
(LSB) r+6
}Abis Connect Information
⇒ Abis Originating ID: Abis Element Identifier = [71H] 1
Length of Abis Originating ID = [02H] 2
103
(MSB) Abis Originating ID = <any value> 3

(LSB) 4
⇒ Abis Destination ID: Abis Element Identifier = [72H] 1
Length of Abis Destination ID = [02H] 2
(MSB) Abis Destination ID = <any value> 3
(LSB) 4
⇒ Cause: Abis Element Identifier = [04H] 1
Length = [01H] 2
Ext = [0] Cause Value = [21H (No radio resource available)] 3
1
2
104
1 6.2.7 Abis-BTS Release

2 This message is sent from BSC to BTS to instruct the BTS to release the associated
3 dedicated resource.
4

Reference Direction
Cell Identifier List 7.5 BSC -> BTS O
Correlation ID 7.3 BSC -> BTS O
5
6 The following table shows the bitmap layout for the Abis-BTS Release message:
7 6 5 4 3 2 1 0 Octet
Length = [08H] 2
(LSB) 4
(LSB) 6
(MSB) 7
9
(LSB) 10
Length = [04H] 2
(MSB) 3
105
5
(LSB) 6
1
2
106
1 6.2.8 Abis-BTS Release Ack

2 This message is sent from the BSC to the BTS to acknowledge the Abis-BTS Release.

Reference Direction
Correlation ID 7.3 BSC -> BTS O
4
5 The following table shows the bitmap layout for the Abis-BTS Release Request Ack message:
7 6 5 4 3 2 1 0 Octet
Length = [08H] 2
(LSB) 4
(LSB) 6
(MSB) 7
9
(LSB) 10
Length = [04H] 2
(MSB) 3
5
(LSB) 6
6
7
107
1 6.2.9 Abis-Burst Request

2 This Abis interface message is sent from the BSC to the BTS to request the reservation of
3 resources in support of a traffic burst.
4
Reference
Call Connection Reference 7.10 BSC -> BTS O
Band Class 7.11 BSC -> BTS O
Downlink Radio Environment 7.23 BSC -> BTS O
CDMA Serving One Way Delay 7.24 BSC -> BTS O
Privacy Info 7.12 BSC -> BTS O
Correlation ID 7.3 BSC -> BTS f
O
SDU ID 7.14 BSC -> BTS a
O
Mobile Identity (IMSI) 7.4 BSC -> BTS b
O
Mobile Identity (ESN) 7.4 BSC -> BTS b
O
Cell Identifier List 7.5 BSC -> BTS c
O
Forward Burst Radio Info 7.25 BSC -> BTS d
O
Reverse Burst Radio Info 7.26 BSC -> BTS e
O
Abis Destination ID 7.22 BSC -> BTS g
O
5 a. Optionally included by the BSC. If included, the value shall be saved and
6 used by the target BS on Abis signaling messages.
7 b. This element may be included for OA&M purposes.
8 c. The list of cell identifiers shall be assumed by the target BTS to be in priority
9 order with the highest priority cell listed first.
10 d. This element is only included when forward link radio resources are to be
11 allocated to the burst.
12 e. This element is only included when reverse link radio resources are to be
13 allocated to the burst.
14 f. If this element is included in this message, its value shall be returned in the
15 Abis-Burst Response message and used in the Abis-Burst Commit message.
108
1 g. This element is required if an Abis Origination ID value was included in an

2 Abis-BTS Setup Ack message previously received from the BTS for this call
3 association.
4 The following table shows the bitmap layout for the Abis-Burst Request message:
7 6 5 4 3 2 1 0 Octet
Length = [08H] 2
(LSB) 4
(LSB) 6
(MSB) 7
9
(LSB) 10
⇒ Band Class: A1 Element Identifier = [5DH] 1
Length = [01H] 2
Reserved = [000] Band Class = [00001] (PCS) 3
⇒ Downlink Radio Environment: A1 Element Identifier = [29H] 1
Number of Cells = <variable> 3
Downlink Radio Environment {1+:
Reserved = [00] Downlink Signal Strength Raw = [000000] (ignored) k
(MSB) CDMA Target One Way Delay k+1
(LSB) k+2
} Downlink Radio Environment
Length = [08H] 2
Cell Identification Discriminator = [ 02H] 3
109
(LSB) 7
⇒ Privacy Info: A3/A7 Element Identifier = [1DH] 1
Privacy Mask Information {1+:
Reserved Privacy Mask Type = [00001,00010] Status Available j
= [0] (public, private) = [0,1] = [0,1]
Privacy Mask Length = <variable> j+1
(MSB) Privacy Mask = <any value> j+2
••• •••
(LSB) k
} Privacy Mask Information
Length = [04H] 2
(MSB) 3
5
(LSB) 6
Length = [01H to 06H] 2
••• •••
(LSB) M
= [1,0]
••• •••
Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) N
Length = [05H] 2
= [0]
(MSB) 4
110
ESN = <any value> 5

6
(LSB) 7
Cell Identification{1+:
⇒ Forward Burst Radio Info: A3/A7 Element Identifier = [11H] 1
Length = [06H] 2
Coding Indicator Reserved QOF Mask Forward Code Channel Index 3
= [00, 01] = [0] = [00 – 11] (high part)
= [000 – 111]
Forward Code Channel Index (low part) = [00H – FFH] 4
Pilot PN Code (low part) = [00H – FFH] 5
Pilot PN Reserved Forward Supplemental Channel Rate 6
Code (high = [000] = [0000 – 1111]
part)
[0,1]
Reserved Forward Supplemental Channel Start Time 7
= [000] = [0 0000 – 1 1111]
Reserved Start Time Unit Forward Supplemental Channel Duration 8
= [0] = [000 – 111] = [0000 – 1111]
⇒ Reverse Burst Radio Info: A3/A7 Element Identifier = [12H] 1
Length = [04H] 2
Coding Indicator Reserved = [00 0000] 3
= [00, 01]
Reserved Reverse Supplemental Channel Rate 4
= [0000] = [0000 – 1111]
Reverse Supplemental Channel Start Time = [00H – FFH] 5
Reserved Start Time Unit Reverse Supplemental Channel Duration 6
= [0] = [000 – 111] = [0000 – 1111]
111
(LSB) 4
1
112
1 6.2.10 Abis-Burst Response

2 This Abis interface message is sent from the BTS to the BSC to respond to a request for
3 reservation of resources to support a traffic burst. Note that one or more Abis-Burst
4 Response messages may be used to respond to a single Abis-Burst Request message. A
5 result (committed or uncommitted) shall be provided for all cells in the Abis-Burst
6 Request message. Each Abis-Burst Response message includes at most one committed
7 cell.
8
9
Reference
Call Connection Reference 7.10 BTS -> BSC O
Correlation ID 7.3 BTS -> BSC a
O
Cell Identifier List (Committed) 7.5 BTS -> BSC d
O
Cell Identifier List (Uncommitted) 7.5 BTS -> BSC e
O
Forward Burst Radio Info 7.25 BTS -> BSC b
O
Reverse Burst Radio Info 7.26 BTS -> BSC c
O
Abis Destination ID 7.22 BTS -> BSC f
O
10 a. If this element was included in the Abis-Burst Request message, the

11 value shall be returned in this message.
12 b. This element is only included when this message includes

13 information about forward link radio resources that have been
14 reserved at the cell indicated in the Cell Identifier List (Committed)
15 element.
16 c. This element is only included when this message includes

17 information about reverse link radio resources that have been
18 reserved at the cell indicated in the Cell Identifier List (Committed)
19 element.
20 d. This element is only included when this message includes

21 information about a cell with radio resources reserved for the forward
22 and/or reverse burst indicated in the Forward and/or Reverse Burst
23 Radio Info element.
113
1 e. This element is only included when this message includes one or

2 more requested cells that are not being reserved. The allowable
3 cause values are: OAM&P intervention, Equipment failure, No radio
4 resource available, BS not equipped, Ciphering algorithm not
5 supported, Private Long Code not available or not supported,
6 Requested MUX option or rates not available, Requested privacy
7 configuration not available.
8 f. This element is required if an Abis Origination ID value was included

9 in an Abis-BTS Setup message previously received from the BSC for
10 this call association.
11
114
1 The following table shows the bitmap layout for the Abis-Burst Response message:
7 6 5 4 3 2 1 0 Octet
Length = [08H] 2
(LSB) 4
(LSB) 6
(MSB) 7
9
(LSB) 10
Length = [04H] 2
(MSB) 3
5
(LSB) 6
⇒ Cell Identifier List (committed): A1 Element Identifier = [1AH] 1
⇒ Cell Identifier List (uncommitted): A1 Element Identifier = [1AH] 1
-- Continued on next page --
2
115
1
-- Continued from previous page --
Length = [06H] 2
= [00, 01] = [0] = [00 – 11] (high part)
= [000 – 111]
Code (high = [000] = [0000 – 1111]
part)
[0,1]
= [000] = [0 0000 – 1 1111]
= [0] = [000 – 111] = [0000 – 1111]
Length = [04H] 2
= [00, 01]
= [0000] = [0000 – 1111]
= [0] = [000 – 111] = [0000 – 1111]
Length of Abis Destination = [02H] 2
(LSB) 4
2
116
2 6.2.11 Abis-Burst Commit

3 This Abis interface message is sent from the BSC to the BTS to commit a set of resources
4 that had been reserved to support a traffic burst.
5
Reference
Call Connection Reference 7.10 BSC -> BTS O
Correlation ID 7.3 BSC -> BTS a
O
Cell Identifier List (Forward) 7.5 BSC -> BTS Ob
Cell Identifier List (Reverse) 7.5 BSC -> BTS Ob
Forward Burst Radio Info 7.25 BSC -> BTS Oc, h
Reverse Burst Radio Info 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 g
O
6 a. Optionally included by the BSC. If included, the value shall be

7 saved and used by the target BTS on Abis signaling messages.
8 b. The length field of this element shall be set to ‘0’ if no resources are
9 to be allocated in the indicated direction.
10 c. This element is only included when forward link radio resources are
11 to be allocated to the burst.
12 d. This element is only included when reverse link radio resources are
13 to be allocated to the burst.
14 e. This element shall be included when supporting a secondary power

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

18 control sub-channel for the SCH. The FPC_MODE value shall go
19 into effect at the earlier of the burst start times indicated in the
20 Forward Burst Radio Info and/or Reverse Burst Radio Info element.
117
1 g. This element is required if an Abis Originating ID value was included

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

5 Response message, but the rate could be downgraded in this message.
7 Note: In the Abis-Burst commit message, Walsh codes are used as

8 obtained from the Abis-Burst Response message, but the rate could
9 be downgraded in the Abis-Burst commit message by the BSC. Thus
10 the BSC chooses the Walsh code that determines the actual rate for
11 the traffic burst. However, if the BSC chooses a Walsh code other
12 than the one allocated by the BTS, it shall do so only to reduce the
13 burst rate. The new Walsh code in the Burst Commit message shall
14 be derived from the Walsh code in the Burst Response Message.
15
118
1 The following table shows the bitmap layout for the Abis-Burst Commit message:
7 6 5 4 3 2 1 0 Octet
Length = [08H] 2
(LSB) 4
(LSB) 6
(MSB) 7
9
(LSB) 10
Length = [04H] 2
(MSB) 3
5
(LSB) 6
⇒ Cell Identifier List (Forward): A1 Element Identifier = [1AH] 1
⇒ Cell Identifier List (Reverse): A1 Element Identifier = [1AH] 1
2
119
1
Length = [06H] 2
= [00, 01] = [0] = [00 – 11] (high part)
= [000 – 111]
Code (high = [000] = [0000 – 1111]
part)
[0,1]
= [000] = [0 0000 – 1 1111]
= [0] = [000 – 111] = [0000 – 1111]
Length = [04H] 2
= [00, 01]
= [0000] = [0000 – 1111]
= [0] = [000 – 111] = [0000 – 1111]
⇒ IS-2000 Forward Power Control Mode: A3/A7 Element Identifier = [14H] 1
Length = [02H] 2
Reserved = [0000 0] FPC_MODE = [000 – 011] 3
ACTION_TIME = [00H] (ignored) 4
⇒ IS-2000 FPC Gain Ratio Info: A3/A7 Element Identifier = [15H] 1
Length = [08H] 2
Initial Gain Ratio = [00H – FFH] 3
120
Reser Gain Adjust Step Size = [0H – FH] Count of Gain Ratio Pairs = 4
ved = [011]
[0]
Min Gain Ratio 1 = [00H – FFH] 5
Max Gain Ratio 1 = [00H – FFH] 6
(LSB) 4
1
2
3
121
2
3 This message uses the same format as the A3-Connect message modified to include
4 “Physical Channel Info” IE as shown below.

Reference Direction
Message Type II 6.2.2.5 BTS -> SDU R
Call Connection Reference 6.2.2.98 BTS -> SDU R
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
Physical Channel Info 6.2.2.14 BTS -> SDU R
5 a. If this element is included in this message, it shall be returned in the

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

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

10 Multiple instances of this element may be present in this message.
11 c. If the physical channel type is SCH, then the Extended Handoff

12 Direction Parameters Field Length shall be set to ‘0’ and the
13 following fields shall be ignored in the Cell Information Record:
14 QOF_Mask, PWR_Comb_Ind, Pilot_PN, and Code_Chan.
15
16 The following table shows the bitmap layout for the A3-Connect message modified to include Physical Channel Info IE.
7 6 5 4 3 2 1 0 Octet
⇒ Message Type II = [01H] 1
Length = [08H] 2
(LSB) 4
(LSB) 6
(MSB) 7
122

9
(LSB) 10
1
123
1
Length = [04H] 2
(MSB) 3
5
(LSB) 6
Length = [01H to 06H] 2
••• •••
(LSB) n
⇒ A3 Connect Information{1+: A3/A7 Element Identifier = [1BH] 1
2H – Supplemental Channel (SCH) (exist,new)
3H – Dedicated Control Channel
(DCCH)],
Reserved = [000] QoF Mask = New PWR_ (MSB) K
[00, 01, 10, 11] Cell Comb
Indicator _Ind
= [0,1] = [0,1]
(old, new) (no,yes)
} Cell Info Record
2
124
1
(LSB) 4
(AAL2 CID)
Extended Handoff Direction Parameters Field Length = [09H] P
[0H-FH] [0H-FH]
[0H-FH] [0H-FH]
= [00-11]
= [0H-FH] = [0H-FH]
= [0H-FH]
Length of Channel Element ID = <variable> Q
••• •••
(LSB) …
2
125
1
Length of A3 Originating ID = [02H] R
(LSB) r+2
Length of A7 Destination ID = [02H] s
(MSB) A7 Destination ID = <any value> s+1
(LSB) s+2
}A3 Connect Information
⇒ Physical Channel Info: A3/A7 Element Identifier = [07H] 1
Length =[05H] 2
Frame Offset = [00H – FFH] 3
A3 Traffic Channel Protocol Pilot Gating Rate ARFCN (high part) 4
Stack = [001] = [00, 01, 10] = [000-111]
ARFCN (low part) = [00H-FFH] 5
Count of Physical Channels = [01H-02H] 6
Reserved = [0000] OTD= Count of Physical Channels = 6
[0,1] [001 – 010]
Physical Channel 2 = Physical Channel 1 = 7
0H – N/A, 0H – IS-95,
1H – FCH, 1H – FCH,
2H – SCH, 2H – SCH,
3H – DCCH 3H – DCCH
2
3
4
126

2 This message is used in the same format as the A3-Connect Ack message.
3 Refer to section 6.1.9.2, "A3-Connect Ack", TIA/EIA/IS-2001
4 In this case, message type “M” in A3 message will change to read “R”, and “C” to read
5 “O”.
6 6.2.14 Abis-Remove
7 This message is used in the same format as the A3-Remove message.
8 Refer to section 6.1.9.3, "A3-Remove", TIA/EIA/IS-2001
10 “O”.
11 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
15 “O”.
16 6.2.16 Abis-IS-2000 FCH Fwd

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
20 “O”.
21 6.2.17 Abis-IS-2000 FCH Rvs

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
25 “O”.

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
30 “O”.
31 6.2.19 Abis-BTS Release Request

32 This message is sent from the BTS to the BSC to request de-allocation of resources.
127

Reference Direction
Call Connection Reference 7.10 BTS -> BSC R
Cause 7.9 BTS -> BSC O
Manufacturer’s Specific Records 7.7 BTS -> BSC O
2
3 The following table shows the bitmap layout for the Abis-BTS Release Request message:
7 6 5 4 3 2 1 0 Octet
Length = [08H] 2
(LSB) 4
(LSB) 6
(MSB) 7
9
(LSB) 10
⇒ Cause: A1 Element Identifier = [04H] 1
Length = [01H] 2
ext = [0] Cause Value = 3
[07H (OAM&P intervention),
10H (Packet Data Going Dormant),
20H (equipment failure)]
⇒ Manufacturer’s Specific Records: Abis Element Identifier = [70H] 1
Length = [variable] 2
Manufacturer ID = [00H – FFH] 3
Manufacturer’s specific information 4
••• •••
n
4
128
1 6.2.20 Abis-IS-2000 SCH Fwd

2 This message is used in the same format as the A3-IS-2000 SCH Forward message.
3 Refer to section 6.1.9.16, "A3-IS-2000 SCH Forward", TIA/EIA/IS-2001.
5 “O”.
6 6.2.21 Abis-IS-2000 SCH Rvs

7 This message is used in the same format as the A3-IS-2000 SCH Reverse message.
8 Refer to section 6.1.9.17, "A3-IS-2000 SCH Forward", TIA/EIA/IS-2001.
10 “O”.
11 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.
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.
20 “O”.
21
22
23 6.2.24 Abis-PACA Update

24 This Abis interface message is sent from the BSC to the BTS to update PACA related
25 information at the BTS.
26
Reference Direction
Mobile Identity (IMSI) 7.4 BSC -> BTS O
BTS PACA Order 7.32 BSC -> BTS Oa
27 a. This element identifies the PACA action to be taken.
28 The following table shows the bitmap layout for the Abis-PACA Update message:
129
1
7 6 5 4 3 2 1 0 Octet
⇒ Message Type = [6EH] 1
Length = [08H] 2
(LSB) 4
(LSB) 6
(MSB) 7
9
(LSB) 10
= [1,0]
••• •••
⇒ BTS PACA Order: A1 Element Identifier = [5FH] 1

Length = [02H] 2
Reserved PACA Action Required
2
130
1 7. Information Element Definitions

2
3 7.1 Information Element Identifiers

4 The following table contains lists of all elements that make up the messages defined in
5 Chapter 7. The table includes the Information Element Identifier (IEI) coding which
6 distinguished one element from another.
7
8 Table 7.1-1 Abis Information Element Identifiers Sorted by Identifier value

Element Name Identifier Interface(s) Reference
(unused value – available) 01H-02H
Service Option 03H Abis, A1 7.17
Cause 04H Abis, A1 7.9
(unused value – available) 05H
Quality of Service Parameters 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.)
(unused value – available) 09-0AH
CDMA Target One Way Delay 0BH Abis 7.30
CDMA Serving One Way Delay 0CH Abis, A1, A7 7.24
Mobile Identity 0DH Abis, A1, A7 7.4
(unused value – available) 0E-10H
Forward Burst Radio Info 11H Abis, A7 7.25
Reverse Burst Radio Info 12H Abis, A7 7.26
Correlation ID 13H Abis, A3, A7 7.3
IS-2000 Power Control Mode 14H Abis, A3 7.27
IS-2000 FPC Gain Ratio Info 15H Abis, A7 7.28
(unused value – available) 16-19H
Cell Identifier List 1AH Abis, A1, A7 7.13
(unused value – available) 1B-1CH
Privacy Info 1DH Abis, A7 7.12
(unused value – available) 1EH-20H
Air Interface Message 21H Abis, A7 7.6
131

Layer 2 Ack Request/Results 23H Abis, A7 7.8
Downlink Radio Environment 29H Abis, A1, A7 7.23
(unused value – available) 2A-3EH
Call Connection Reference 3FH Abis, A1, A3, 7.10
A7
Authentication Challenge Parameter 41H Abis, A1 7.33
(unused value – available) 42-4BH
SDU ID 4CH Abis, A3, A7 7.14
(unused value – available) 4DH
PACA Timestamp 4EH Abis, A1 7.18
(unused value – available) 4F-5CH
Band Class 5DH Abis, A1, A7 7.11
(unused value – available) 5E
PACA Order 5FH Abis, A1 7.32
(unused value – available) 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
132
1 7.2 Message Type

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

Message
Type Section
Message Name Value Interface Reference
Abis-Connect 01H Abis Signaling
Abis-Connect Ack 02H Abis Signaling
Abis-Remove 03H Abis Signaling
Abis-Remove Ack 04H Abis Signaling
(unused value – available) 05H-0AH
Abis-IS-2000 FCH Fwd 0BH Abis Traffic 6.2.16
Abis-IS-2000 FCH Rvs 0CH Abis Traffic 6.2.17
Abis-Traffic Channel Status 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
(unused value – available) 12H-6DH
Abis-PACA-Update 6EH Abis Signaling 6.32
(unused value – available) 6FH-7FH
8
133
1 (cont.) - Abis Message Type Values
Message
Type Section
Message Name Value Interface 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
Abis-BTS Release Ack 83H Abis Signaling 6.2.8
Abis-BTS Release Request 84H Abis Signaling 6.2.19
(unused value – available) 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
2 All other values are reserved.
4 7.3 Correlation ID
5 Refer to section 6.2.2.108, “Correlation ID”, TIA/EIA/IS-2001.
6
7 7.4 Mobile Identity

8 Refer to section 6.2.2.16, “Mobile Identity”, TIA/EIA/IS-2001.
9 7.5 Cell Identifier

10 Refer to section 6.2.2.20, “Cell Identifier”, TIA/EIA/IS-2001.
11 7.6 Air Interface Message

12 Refer to section 6.2.2.152, “Air Interface Message”, TIA/EIA/IS-2001. ARQ fields
13 exchanged on an air-interface is not included in this information element.
134
1 7.7 UNUSED SECTION

2
3 7.8 Layer 2 Ack Request/Results

4 Refer to section 6.2.2.153, “Layer 2 Ack Request/Results”, TIA/EIA/IS-2001.
5
6 7.9 Cause
7 Refer to section 6.2.2.19, “Cause”, TIA/EIA/IS-2001.
8
9 7.10 Call Connection Reference

10 Refer to section 6.2.2.98, “Call Connection Reference”, TIA/EIA/IS-2001.
11
12 7.11 Band Class

13 Refer to section 6.2.2.106, “Band Class”, TIA/EIA/IS-2001.
14 7.12 Privacy Info

15 Refer to section 6.2.2.143, “Privacy Info”, TIA/EIA/IS-2001.
16
17 7.13 Cell Identifier List

18 Refer to section 6.2.2.21, “Cell Identifier List”, TIA/EIA/IS-2001.
19
20 7.14 SDU ID
21 Refer to section 6.2.2.91, “SDU ID”, TIA/EIA/IS-2001.
22 7.15 Physical Channel Info

23 Refer to section 6.2.2.14, “Physical Channel Info”, TIA/EIA/IS-2001.
135
1 7.16 Cell Information Record

2 Refer to section 6.2.2.89, “Cell Information Record”, TIA/EIA/IS-2001.
3
4 7.17 Service Option

5 Refer to section 6.2.2.66, “Service Option”, TIA/EIA/IS-2001.
6 7.18 PACA Timestamp

7 Refer to section 6.2.2.149, “PACA Timestamp”, TIA/EIA/IS-2001.
8 7.19 Quality of Service Parameters

9 Refer to section 6.2.2.54, “Quality of Service Parameters”, TIA/EIA/IS-2001.
10
11 7.20 Abis Connect Information

12 Refer to section 6.2.2.144, “A3 Connect Information”, TIA/EIA/IS-2001.
13 7.21 Abis Originating ID

14 This element contains an identifier chosen by the BSC (when the BSC sends an Abis
15 signaling message to the BTS) or BTS (when the BTS sends an Abis signaling message to
16 the BSC) for its own use in quickly processing Abis signaling messages received from the
17 BTS. For example, it may be used to identify the resources supporting the call
18 association that are internal to the BSC. If an Abis Originating ID is supplied by this BSC,
19 then the BTS includes this in the Abis Destination ID element in subsequent Abis
20 messages to this BSC.
21
7 6 5 4 3 2 1 0 Octet
Abis Element Identifier 1
Length 2
(MSB) Abis Originating ID 3
(LSB) •••
136
1 Length: This field indicates the number of octets in this element

2 following the Length field. The maximum value in
3 this version of this specification is 8 octets.
4 Abis Originating ID: This field has variable length. The actual length is
5 indicated in the Length field and is dependent upon the
6 particular implementation. In this version of this
7 standard, this value shall be no more than 8 octets long.
8 7.22 Abis Destination ID

9 This element contains an identifier chosen by the BSC (when the BSC sends an Abis
10 signaling message to the BTS) or BTS (when the BTS sends an Abis signaling message to
11 the BSC) for its own use in quickly processing Abis signaling messages.
12 If an Abis Originating ID was supplied by the BSC, then the BTS includes this value in
13 the Abis Destination ID element in subsequent Abis messages to the BSC.
14
7 6 5 4 3 2 1 0 Octet
Length 2
(MSB) Abis Destination ID 3
(LSB) •••
15 Length: This field indicates the number of octets in this element

16 following the Length field. The maximum value in
17 this version of this specification is 8 octets.
18 Abis Destination ID: This field has variable length. The actual length is
19 indicated in the Length field and is dependent upon the
20 particular implementation. In this version of this
21 standard, this value shall be no more than 8 octets long.
22 7.23 Downlink Radio Environment

23 Refer to section 6.2.2.25, “Downlink Radio Environment”, TIA/EIA/IS-2001.
24
25 7.24 CDMA Serving One Way Delay

26 Refer to section 6.2.2.79, “CDMA Serving One Way Delay”, TIA/EIA/IS-2001.
27
137
1 7.25 Forward Burst Radio Info

2 Refer to section 6.2.2.56, “Forward Burst Radio Info”, TIA/EIA/IS-2001.
3
4 7.26 Reverse Burst Radio Info

5 Refer to section 6.2.2.57, “Reverse Burst Radio Info”, TIA/EIA/IS-2001.
6
7 7.27 IS-2000 Forward Power Control Mode

8 Refer to section 6.2.2.177, “IS-2000 Forward Power Control Mode”, TIA/EIA/IS-2001.
9
10 7.28 IS-2000 FPC Gain Ratio Info

11 Refer to section 6.2.2.178, “IS-2000 FPC Gain Ratio Info”, TIA/EIA/IS-2001.
12
13 7.29 BTS L2 Termination

14 This information element is used to indicate whether the BTS terminates Layer 2 or not.
15 In this release of the Abis specification L2 termination is mandatory to be supported by
16 the BTS and may be supported by the BSC. Therefore BTS L2 termination shall be set
17 “1” in this version.
7 6 5 4 3 2 1 0 Octet
Length 2
Reserved BTS L2 3
Terminat
ion
18 Length: The Length field is a binary value indicating the number of

19 octets following the Length field.
20 BTS L2 Termination: This bit shall be set to ‘0’ when the BTS dose not
21 terminate Layer 2, and be set to ‘1’ when the BTS
22 terminates Layer 2.
23
138
1 7.30 CDMA Target One Way Delay

2 The BSC uses this IE to send the CDMA Target One Way Delay to each target BTS
3 involved in soft handoff.
4
7 6 5 4 3 2 1 0 Octet
Length 2
CDMA Target One Way Delay (high part) 3
CDMA Target One Way Delay (low part) 4
5
6
7 7.31 Walsh Code Assignment Reqest

8 This information element indicates the Walsh code in the message that this IE is sent is
9 invalid.
10
7 6 5 4 3 2 1 0 Octet
Length 2
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
17 upon receiving the Abis-PACA Update message.
18
7 6 5 4 3 2 1 0 Octet
A1 Element Identifier 1
Length 2
Reserved PACA Action Required 3
19
139
1 Length This field shall be set to the length of this element in octets following
2 the Length field.
3 The PACA Action Required field is coded as follows:
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
6 Reserved This field shall be set to ‘00000’.

7
8 7.33 Authentication Challenge Parameter (RAND)

9 The Authentication Challenge Parameter information element provides a non-predictable
10 number which is used for authentication/SSD update. Bit 7 of octet 2 is the most
11 significant bit, while bit 0 of the highest numbered octet is the least significant bit.
7 6 5 4 3 2 1 0 Octet
A1 Element Identifier 1
Length 2
Reserved Random Number Type 3
(MSB) 4
RAND Value 5-m
(LSB) m+1
12 Length: The Length field is a binary value indicating the number

13 of octets following the Length field.
14 Random Number Type:
Random Number Type Random Number Type Random Number
Value Length
0001 RAND 32 bits
140
1
2
3 7.34 Abis Ack Notify

4 This information element is used to indicate whether the BSC wants to be informed that a
5 layer 2 ack was received from the MS.
6
7 6 5 4 3 2 1 0 Octet
Length 2
7 Length: The Length field is a binary value indicating the number of

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

Timer Name Default Value Range of Granularity Section Timer Location
(seconds) Values (seconds) Reference
(seconds)
Tconnb 0.1 0 – 1.0 0.1 8.1 BTS
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
5
6
7 8.1 Tconnb :Timer for Abis-Connect message

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

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

16 The Tchanstatb timer is used by the BSC to wait for the Abis-Traffic Channel Status
17 message for all new cells on an Abis connection. This timer is started when the
18 Abis-Connect Ack message indicating that Abis-Traffic Channel Status messages are
19 requested is sent and stopped when Abis-Traffic Channel Status message(s) have been
20 received for all new cells on the Abis connection.
21
142
1 8.4 Tdisconb : Timer for Abis-Remove Ack message

2 The Tdisconb timer is used by the BTS to wait for the Abis-Remove Ack message. This
3 timer starts when the BTS sends Abis-Remove message, and stops when the BTS
4 receives the Abis-Remove Ack message.
5
6 8.5 Tdrptgtb : Timer for Abis-BTS Release Ack message

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

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

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

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

Abis Interface

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Abis Interface

Hochgeladen von

Copyright:

Verfügbare Formate

BTS-BSC Inter-operability (Abis Interface) A.S0003-Av2.

Date: July 2001

9 BTS-BSC Inter-operability (Abis Interface)

1 5.2.5 Abis-Connect Ack ........................................................................................................................ 25

1 6.2.1 Abis-ACH Msg Transfer .............................................................................................................. 86

1 7.19 Quality of Service Parameters....................................................................................................... 136

9 2.1 Scope of the document

1 2.2.1 Telecommunications Industry Association (TIA) / Electronics Industry

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

7 2.2.2 Standards Committee T1

9 2.2.3 International Telecommunications Union - Telecommunications Sector

1 PATE Packet Arrival Time Error

1 4. Network Reference Model and Interfaces

23 Figure 4-1 Reference Model

1 sub-layer and SAR sub-layer.

Air Interface Abis Interface

MS BTS Abis traffic BSC

FCH (f/r-dsch, f/r-dtch) FCH (Abis-IS-2000 FCH Fwd/Rvs)

ACH (r-csch) ACH (Abis-ACH Msg Transfer)

OAM Signaling (FFS)

1 Table 4-2 summaries the details of the Abis interface

3 Table 4-2 Abis interface description

5 4.1 Support of user traffic connections to a frame selector function

15 4.2 Support of paging channel messaging

4 4.3 Support of Access channel messaging

15 4.4 Support of broadcast system information functions

21 4.5 Layers 1 & 2

23 4.5.1 Physical Layer Specification (Layer 1)

29 4.5.2 Use of ATM (Layer 2)

34 4.5.3 Field of Application

1 4.5.4 ATM Layer

10 4.5.5 ATM Adaptation Layer

22 4.5.6 Network and Transport Protocols

24 4.5.6.1 Signaling Connection Transport Protocol Options

1 AAL5 is described in ITU-T I.363.5, B-ISDN ATM Adaptation Layer Specification:

ATM Phys. Lyr. Phys. Lyr. Phys. Lyr.

9 4.5.6.2 User Traffic Connection Transport Protocol Options

21 4.5.6.3 TCP Transport Protocol Usage

24 4.5.6.4 General Use of TCP

1 4.5.6.4.1 Message Delimiting in TCP

2 Figure 4.5.6.4.1-1 Delimiting Messages in an Abis Application TCP Byte Stream

3 4.5.6.4.2 TCP Connection Establishment

1 4.5.6.4.3 TCP Connection Release

5 4.5.6.4.4 TCP Port Usage

10 4.5.6.5 Use of TCP for the Abis Interface

13 4.5.6.6 IP Network Protocol Usage

3 5.1 Mobile Originating Call

19 5.1.1 Abis-ACH Message Transfer

22 5.1.1.1 Successful Operation

29 5.1.1.2 Failure Operation

1 5.1.2 Unused Section

3 5.1.3 Abis-BTS Setup

6 5.1.3.1 Successful Operation

12 5.1.3.2 Failure Operation

18 5.1.4.1 Successful Operation

30 5.1.4.2 Failure Operation

33 5.1.5 Abis-Connect Ack

1 5.1.5.1 Successful Operation

10 5.1.5.2 Failure Operation

17 5.1.6 Abis-BTS Setup Ack

21 5.1.6.1 Successful Operation

28 5.1.6.2 Failure Operation

31 5.1.7 Abis-IS-2000 FCH Forward

35 5.1.7.1 Successful Operation