A S0003 PDF

3GPP2 A.
S0003
Version 1.0.0
Date: March 16, 2000
Abis interface Technical Specification for cdma2000

Spread Spectrum Systems
(A.S0003 : BSC to BTS Interoperability specification

(Abis))
COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual
Organizational Partners may copyright and issue documents or standards publications in
individual Organizational Partner's name based on this document. Requests for reproduction
of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org.
Requests to reproduce individual Organizational Partner's documents should be directed to
that Organizational Partner. See www.3gpp2.org for more information.
Revision History
Revision Description Date
Rev. 1.0.0 Initial Publication March 2000

1
1
1 1. INTRODUCTION.................................................................................................................................................... 4
2 2. OBJECTIVES ........................................................................................................................................................... 4
3 2.1 SCOPE OF THE DOCUMENT..................................................................................................................................4
4 3. GLOSSARY ............................................................................................................................................................... 4
5 3.1 GLOSSARY ............................................................................................................................................................4
6 4. NETWORK REFERENCE MODEL AND INTERFACES .......................................................................... 7
7 4.1 SUPPORT OF USER TRAFFIC CONNECTIONS TO A FRAME SELECTOR FUNCT ION .........................................10
8 4.2 SUPPORT OF PAGING CHANNEL MESSAGING...................................................................................................10
9 4.3 SUPPORT OF A CCESS CHANNEL MESSAGING ..................................................................................................11
10 4.4 SUPPORT OF RADIO FUNCTIONS.......................................................................................................................11
11 4.5 SUPPORT OF BROADCAST SYSTEM INFORMATION FUNCTIONS.....................................................................11
12 4.6 LAYERS 1 & 2 ....................................................................................................................................................12
13 4.6.1 Physical Layer Specification (Layer 1)..............................................................................................12
14 4.6.2 Use of ATM (Layer 2)............................................................................................................................12
15 4.6.3 Field of Application ...............................................................................................................................12
16 4.6.4 ATM Layer...............................................................................................................................................12
17 4.6.5 ATM Adaptation Layer..........................................................................................................................12
18 4.6.6 Network and Transport Protocols.......................................................................................................14
19 4.6.6.1 Signaling Connection Transport Protocol Options...........................................................................14
20 4.6.6.2 User Traffic Connection Transport Protocol Options.......................................................................15
21 4.6.6.3 TCP Transport Protocol Usage..........................................................................................................15
22 4.6.6.4 General Use of TCP..........................................................................................................................15
23 4.6.6.5 Use of TCP for the Abis Interface.....................................................................................................17
24 4.6.7 IP Network Protocol Usage..................................................................................................................17
25 5. CALL PROCESSING............................................................................................................................................18
26 5.1 M OBILE ORIGINATING CALL ...........................................................................................................................19

27 5.2 M OBILE TERMINATED CALL............................................................................................................................22
28 5.3 CALL CLEARING................................................................................................................................................27
29 5.3.1 Call Clearing initiated by MS..............................................................................................................27
30 5.3.2 Call Clearing initiated by BS/MSC.....................................................................................................29
31 5.3.3 Call Clearing initiated by BTS...............................................................................................................30
32 5.4 HANDOFF............................................................................................................................................................32
33 5.4.1 Soft/Softer Handoff (Intra-BTS)...........................................................................................................32
34 5.4.2 Soft/Softer Handoff (Inter-BTS)...........................................................................................................33
35 5.5 SMS DELIVERY .................................................................................................................................................35
36 5.5.1 SMS Delivery on the Paging channel .................................................................................................35
37 5.5.2 SMS Delivery on the Access channel..................................................................................................36
38 5.5.3 SMS Delivery on the Traffic channel to MS.......................................................................................37
39 5.5.4 SMS Delivery on the Traffic channel from MS..................................................................................38
1
1 5.6 TRAFFIC BURST OPERATION............................................................................................................................39
2 5.6.1 Initial Traffic Burst Example Abis Connection Not Yet Established..........................................39
3 5.6.2 Subsequent Traffic Burst Example ......................................................................................................42
4 6. ABIS INTERFACE MESSAGE FORMATS ......................................................................................................44
5 6.1 A BIS INTERFACE MESSAGE ......................................................................................................................................44

6 6.1.1 Abis-ACH Msg Transfer ..........................................................................................................................44
7 6.1.2 Abis-ACH Msg Transfer Ack ..................................................................................................................47
8 6.1.3 Abis-PCH Msg Transfer ..........................................................................................................................48
9 6.1.4 Abis-PCH Msg Transfer Ack ..................................................................................................................50
10 6.1.5 Abis-BTS Setup .........................................................................................................................................52
11 6.1.6 Abis-BTS Setup Ack..................................................................................................................................58
12 6.1.7 Abis-BTS Release .....................................................................................................................................61
13 6.1.8 Abis-BTS Release Ack..............................................................................................................................62
14 6.1.9 Abis-Burst Request...................................................................................................................................63
15 6.1.10 Abis-Burst Response ................................................................................................................................72
16 6.1.11 Abis-Burst Commit ...................................................................................................................................77
17 6.1.12 Abis-Connect.............................................................................................................................................82
18 6.1.13 Abis-Connect Ack .....................................................................................................................................82
19 6.1.14 Abis-Remove..............................................................................................................................................82
20 6.1.15 Abis-Remove Ack......................................................................................................................................82
21 6.1.16 Abis-IS-2000 FCH Fwd...........................................................................................................................83
22 6.1.17 Abis-IS-2000 FCH Rvs ............................................................................................................................83
23 6.1.18 Abis-Traffic Channel Status....................................................................................................................83
24 6.1.19 Abis-BTS Release Request......................................................................................................................83
25 6.1.20 Abis-IS-2000 SCH Fwd .........................................................................................................................84
26 6.1.21 Abis-IS-2000 SCH Rvs ..........................................................................................................................84
27 6.1.22 Abis-IS-2000 DCCH Fwd .....................................................................................................................84
28 6.1.23 Abis-IS-2000 DCCH Rvs.......................................................................................................................84
29 7. INFORMATION ELEMENT DEFINITIONS ...............................................................................................85
30 7.1 INFORMATION ELEMENT IDENTIFIERS............................................................................................................85

31 7.2 M ESSAGE TYPE..................................................................................................................................................86
32 7.3 CORRELATION ID ..............................................................................................................................................87
33 7.4 M OBILE IDENTITY.............................................................................................................................................87
34 7.5 CELL IDENTIFIER...............................................................................................................................................88
35 7.6 A IR INTERFACE M ESSAGE ................................................................................................................................88
36 7.7 M ANUFACTURERS SPECIFIC RECORDS .........................................................................................................88
37 7.8 LAYER 2 A CK REQUEST /RESULTS...................................................................................................................88
38 7.9 CAUSE .................................................................................................................................................................88
39 7.10 CALL CONNECTION REFERENCE .....................................................................................................................89
40 7.11 BAND CLASS ......................................................................................................................................................89
41 7.12 PRIVACY INFO ....................................................................................................................................................89
2
1 7.13 CELL IDENTIFIER LIST ......................................................................................................................................89
2 7.14 SDU-ID ..............................................................................................................................................................89
3 7.15 PHYSICAL CHANNEL INFO................................................................................................................................89
4 7.16 A BIS CELL INFO.................................................................................................................................................89
5 7.17 SERVICE OPTION................................................................................................................................................89
6 7.18 PACA TIMESTAMP ............................................................................................................................................89
7 7.19 QUALITY OF SERVICE PARAMETERS ...............................................................................................................90
8 7.20 A BIS CONNECT INFORMATION ........................................................................................................................90
9 7.21 A BIS FROM ID ...................................................................................................................................................90
10 7.22 A BIS TO ID.........................................................................................................................................................90
11 7.23 DOWNLINK RADIO ENVIROMENT ...................................................................................................................91
12 7.24 CDMA SERVING ONE WAY DELAY ................................................................................................................91
13 7.25 FORWARD BURST RADIO INFO.........................................................................................................................91
14 7.26 REVERSE BURST RADIO INFO..........................................................................................................................91
15 7.27 IS-2000 FORWARD POWER CONTROL M ODE................................................................................................91
16 7.28 IS-2000 FPC GAIN RATIO INFO......................................................................................................................92
17 7.29 CELL IDENTIFIER LIST ......................................................................................................................................92
18
3
1
2 1. Introduction
3 This document specifies the Abis (between the BSC and the BTS) interface for cdma2000
4 system. Abis interface is the reference point between the BSC and the BTS. The signaling
5 flows and these signals are described.
6
7 2. Objectives
8 The Abis interface specification achieves providing an open and interoperable system.
9 And Abis interface does not disturb the coexistence with other A sub-interfaces specified in
10 3GPP2 A.S0001
11 2.1 Scope of the document

12 This specification defines the interface between BTS and BSC within the BS. The
13 interface between BSs is specified in the 3GPP2 A.S0001 3GPP2 Access Network
14 Interfaces Interoperability Specification (January 18th , 2000).
15 The OAM&P related information can be transferred on this interface and the transport
16 layer for these information are desirable to match with Abis interface. They are for further
17 study and this specification does not contain them..
18
19 3. Glossary
20
21 3.1 Glossary
22 The following is a list of acronyms that are used in this specification.
23 3G-IOS Third Generation InterOperability Specification
24 AWIM Alert With Information Message
25 BS Base Station
26 BSC Base Station Controller
27 BTS Base Tranceiver System
28 ECAM Enhanced Channel Assignment Message
29 GPM General Page Message
30 ITU International Telecommunications Union
31 MAC Medium Access Control
32 MS Mobile Station
33 MSC Mobile Switching Center
34 ORM Origination Message
4
1 PRM Page Response Message
2 QoS Quality of Service
3 RAN Radio Access Network
4 RN Radio Network
5 RRC Radio Resource Control Function
6 SCCM Service Connect Completion Message
7 SCM Service Connect Message
8 SDU Selection/Distribution Unit function
9
10
11
12
13
14
15
5
1
6
1 4. Network Reference Model and Interfaces
2
3 Following figure shows the network reference model used by this specification.
7
1
2
3 BS
4
5 BSC SDU Function
6
7 Abis Signaling Abis Signaling
8 Abis Interface
9 Abis Traffic Abis Traffic
10
BTS CH element BTS CH element
11
12
13
14 a) Abis interface = Abis signaling + Abis traffic
15
16 b) An SDU function is located in a BSC
17 c) A channel element is located in a BTS
18
19 Notes : The handoff procedure between BTSs within a BSC is defined in this document. The handoff
20 procedures between the BSs have already defined in 3GPP2 A.S0001.
21
22 Fig.4-1. Network Reference Model for Abis interface
23
24 \\\\\\\\
25
26
27
28
8
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)
BS Control Signaling
OAM Signaling (FFS)
1
2 Note: This figure is informative. All signals defined in air interface are not described in this Figure.
3
4 Figure 4-2. Relationship between Air interface and Abis interface (Intra BS Model)
5
6
7
9
1 Table 4-1 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 ...)
- Abis -ACH Msg Transfer Ack (A7-ACH ... Ack)
SCH transfer - SCH setup - Abis-Burst Request (A7-Burst Req.)
and establish - Abis-Burst Response (A7-Burst Rsp.)
-Abis-Burst Commit (A7-Burst Commit)
2
3
4 4.1 Support of user traffic connections to a frame selector function

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

15 When a BS sends a message on a paging channel, the BSC typically formats the majority of
16 the message and then forwards it to the BTS along with various parameters including the
17 destined cell identifier The ability to forward such a paging message from the BSC to the
18 BTS is part of the functionality of the Abis interface.
19 An additional requirement of a CDMA system is that such messages may also need to be
20 forwarded between BSCs to be transmitted to a BTS belonging to a BSC other than the
21 BSC that originally created the message. This requirement comes through support for
22 access handoff and other such cdmaOne and cdma2000 features. The BSC to BSC
10
1 signaling on the A7 interface to support such forwarding has been defined in the 3G-IOS
2 specification.
3 4.3 Support of Access channel messaging

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

15 Various functions can be considered with respect to the radios that exist under the control
16 of a BTS.
17 The interaction of these functions with Operations, Administration, Maintenance, and

18 Provisioning (OAM&P) are for further study.
19
20 4.5 Support of broadcast system information functions

21 In a cdmaOne or a cdma2000 system, each BTS must broadcast various pieces of system
22 information that the MS will capture and use during its interactions with the network. Much
23 of that system information may be administrated through OAM&P functions. A small
24 amount of such system information may be placed in BTS and OAM&P control of a BTS
25 for the same purposes must be defined.
26
27
28 4.6 Layers 1 & 2

29
30 4.6.1 Physical Layer Specification (Layer 1)

31 The Abis interface is based on the use of:
32 T1 digital transmission system interfaces. Each 1.544 Mbits/s interface
11
1 provides24*56 kbits/s or 24*64 kbits/s channels which can be used for traffic or
2 signaling as the operator requires. Common physical interface standards are found in
3 ANSI T1.101 and related references.
4 E1 digital transmission interfaces consisting of 30*64 kbits/s user channels can also
5 be used for traffic or signaling as the operator requires, and as applicable to the
6 network.
7 As a BS/MSC agreed option, dedicated DS0 signaling link[s] may be used instead of
8 the T1/E1 interface.
9 T3 digital transmission interfaces supporting transmission rates of 43.232 Mbits/sec.
10 OC3 digital transmission interfaces supporting transmission rates of 155.52
11 Mbits/sec.
12 4.6.2 Use of ATM (Layer 2)

13 Asynchronous Transfer Mode (ATM) is a suite of protocols that allow fast, efficient
14 delivery of user traffic in a packet environment. ATM, for the purposes of this standard,
15 consists of two main layers: the ATM Layer that uses the physical layer, and the ATM
16 Adaptation Layer that adapts the basic ATM layer to specific uses .
17 4.6.3 Field of Application

18 Asynchronous Transfer Mode (ATM) is used to transport both signaling and user traffic
19 (voice/data).
20 4.6.4 ATM Layer

21 The ATM Layer uses a basic 53 octet cell consisting of a 5 octet header and 48 octet
22 payload. This standard uses the ATM Layer as specified in ANSI T1.627-1993
23 Telecommunications Broadband ISDN - ATM Layer Functionality and Specification
24 without modification.
25 For this specification only ATM permanent virtual circuits (PVCs) shall be required for
26 the Abis interface. These virtual circuits shall be configured through administrative
27 procedures and no special signaling interface procedures, e.g., ATM UNI (Q.2931), shall
28 be required.
29 4.6.5 ATM Adaptation Layer

30 To make use of the basic cell transfer capability of the ATM Transport Layer in specific
31 uses , various ATM Adaptation Layers (AALs) have been defined.
32 Within this standard, two AALs are used:
33 AAL51 - for the transfer of signaling, and
34 AAL22 - for the transfer of user traffic (voice/data) on A3 traffic subchannels.
1 AAL5 is described in ITU-T I.363.5, B-ISDN ATM Adaptation Layer Specification: Type
5 AAL, August 1996.
12
1 Both AAL5 and AAL2 will be used without modification in this standard. The Service
2 Specific Segmentation and Reassembly (SSSAR) sublayer for AAL2, as specified inITU-T
3 I.366.1, is used for segmentation and reassembly of AAL2 SDUs.
4 In this version of this standard, the functionality of other sublayers of AAL2 is not
5 supported. Specifically, Service Specific Transmission Error Detection (SSTED) and
6 Service Specific Assured Data Transfer (SSADT) are not included.
7
2 AAL2 is described in ITU-T Recommendation I.363.2, B-ISDN ATM Adaptation Layer

Type 2 Specification, September 1997.
13
1 4.6.6 Network and Transport Protocols
2
3 4.6.6.1 Signaling Connection Transport Protocol Options
4 Signaling over the Abis interface requires a reliable transport protocol and appropriate
5 addressing and routing mechanisms to deliver messages from source to destination. The
6 Abis signaling application is independent of the underlying transport, which is left to the
7 discretion of operators and manufacturers. The signaling protocol stack options available to
8 operators and manufacturers for the Abis interface include:
9
10 Abis Interface (signaling connection):
11
Abis Signaling Application
TCP/IP
AAL5
ATM
Phys. Lyr.
12
13
14
15
14
1 4.6.6.2 User Traffic Connection Transport Protocol Options
2 The protocol stack options for transport of user traffic that are available to operators and
3 manufacturers include:
4
5 Abis Interface (user traffic subchannel):
6
Abis Traffic
SSSAR
AAL2
ATM
Phys. Layer
7
8 4.6.6.3 TCP Transport Protocol Usage
9 The standard TCP protocol, as described in reference 3, IOS section 1.5.4, shall be used for
10 establishing, using, and clearing TCP connections.
11 4.6.6.4 General Use of TCP
12 TCP connections for signaling may be set up on a per-call basis or signaling messages for
13 multiple calls may be multiplexed on a single TCP connection.
14 The TCP protocol provides a reliable byte stream transfer. Therefore, a means needs to be
15 provided for two application entities to delimit the messages sent between them. The
16 technique for such delimitation is given below.
17 4.6.6.4.1 Message Delimiting in TCP
18 TCP provides a reliable byte stream between two application entities. Because the protocol
19 in this standard uses messages to communicate, these messages shall be delimited in the
20 TCP byte stream. Such delimitation shall be done by means of a two byte flag field and a
21 two byte length field inserted at the beginning of each message sent over a TCP connection.
22 The flag field shall contain the hex value F634. The purpose of the flag field is to
23 facilitate verification of message boundaries, and fast reestablishment of synchronization if
24 synchronization of message boundaries is lost. See Figure 4-3 below.
25
15
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-3- Delimiting Messages in an Abis Application TCP Byte Stream
16
1 4.6.6.4.2 TCP Connection Establishment
2 A new TCP connection is established when a signaling message related to a call has to be
3 exchanged over an interface, and no such connection exists over the particular interface.
4 Normal TCP connection establishment procedures are used.
5 4.6.6.4.3 TCP Connection Release
6 An existing TCP connection over an interface is released when there are no more signaling
7 messages to be exchanged over the interface. Normal TCP connection release procedures
8 are used.
9 4.6.6.4.4 TCP Port Usage
10 The following TCP port values are reserved for signaling across Abis interfaces:
11 Abis : 5604 -- This is the well-known TCP port at a BS used for Abis signaling
12 interconnection between BTSs and a BSC .
13
14 Editors Note : These port number is requested now. The value may be changed. And the
15 value will be defined in A.S0001 later version.
16
17 A7: (BS-to-BS) 5602 -- This is the well-known TCP port at a BS used for signaling
18 interconnection to another BS.
19 A9: (BS-to-PCF) 5603 -- This is the well-known TCP/UDP port at a BS used for signaling
20 interconnection to a PCF.
21 4.6.6.5 Use of TCP for the Abis Interface
22 The standard "Transport Control Protocol (TCP)", as described in RFC793 and shown in
23 IOS section 5.4.1 shall be used on the A3 (signaling subchannel) and A7 interfaces.
24 4.6.7 IP Network Protocol Usage

25 The standard IP protocol, as defined in RFC 791 (see IOS section 1.5.4), shall be used for
26 routing Internet Protocol packets.
27
17
1
2 5. Call Processing
3
4
5
6
7
18
1 5.1 Mobile Originating Call
2 This section describes the call flow associated with a mobile station call
3 origination in the cdma2000 system.
4
BS Time Comment
5
MS BTS BSC MSC
6
7 Origination Abis-ACH Msg. Transfer (ORM)
a
8 Complete L3 Info: CM Service Req.
b
T303 Assignment Request
9 c
Abis-BTS Setup
10 d
Abis-Connect
e
11 Abis-Connect Ack
f
12 Abis-BTS Setup Ack
g
Null Traffic Abis-IS-2000 FCH Fwd (Null Data)
13 h
Extended Abis-IS-2000 FCH Rvs (Idle)
14 i
Channel Assignment Abis-PCH Msg. Transfer (ECAM)
15 j
T10
Traffic Channel Preamble Abis-IS-2000 FCH Rvs (T-CH Preamble)
16 k
17 BS Ack Order Abis-IS-2000 FCH Fwd (BS Ack Order)

l
Idle Tch Data Frames Abis-IS-2000 FCH Rvs (Idle)
18 m
MS Ack Order Abis-IS-2000 FCH Rvs (MS Ack Order)
19 n
20
Service Connect Abis-IS-2000 FCH Fwd (SCM)
21 o
Service Connect Completion Abis-IS-2000 FCH Rvs (SCCM)

22 p
23 Assignment Complete
q
24
25
26
27 Fig. 5-1 Mobile Originating Call
28
19
1 a. The MS transmits an Origination Message, with layer 2 acknowledgement required, over
2 the access channel of the air interface to the BTS. Then the BTS sends an Abis -ACH
3 Msg Transfer including the Origination message frame in Abis signaling interface.
4 b. The BSC constructs the CM Service Request message, places it in the Complete Layer 3
5 Information message, sends the message to the MSC, and starts timer T303. The BSC
6 may request the MSC to allocate a preferred terrestrial circuit.
7 c. The MSC sends an Assignment Request message to the BSC to request assignment of
8 radio resources. This message will include information on the terrestrial circuit, if one is
9 to be used between the MSC and the BSC. The MSC then starts timer T10.
10 d. The BSC sends Abis -BTS Setup message to get the resource between BSC and BTS.
11 The BSC shall allocate a code channel and include it in the Abis -BTS Setup.
12 e. If resources are available, BTS responses with Abis -Connect message.
13 f. The BSC sends Abis -Connect Ack message to the BTS.
14 g. The BTS sends Abis -BTS Setup Ack to the BSC to acknowledge the Abis -BTS Setup.
15 The BTS may allocate a code channel. In this case, the BTS includes the allocated code
16 channel in Abis -BTS Setup Ack. Unless the BTS allocates a code channel, the BTS
17 includes the code channel that has been indicated by Abis -BTS Setup (step d) in the
18 Abis -BTS Setup Ack.
19 h. The BSC transmits the Abis -IS-2000 FCH Fwd message to the BTS including Null Data
20 to let the BTS send Null traffic data toward the MS. Then the BTS begin sending Null
21 Traffic data for synchronizing between the BTS and the MS. The BTS may have function
22 which sends Null Traffic data for synchronization between the BTS and the MS.
23 Whether the BTS has the function or not, the BSC is assumed to send Null Traffic.
24 i. The BTS sends Abis -IS-2000 FCH Rvs message to the BSC including Idle data.
25 j. The BSC sends an Abis -PCH Msg Transfer including Extended Channel Assignment
26 message to the BTS. The BTS sends an Extended Channel Assignment message to the
27 MS over the paging channel of the radio interface (with the MS address) to initiate the
28 establishment of a radio traffic channel.
29 k. The MS begins sending the traffic channel preamble (TCH Preamble) over the
30 designated reverse traffic channel. Then the BTS transmits this preamble with an
31 Abis -IS-2000 FCH Rvs message.
32 l. Once the BSC acquires the reverse traffic channel, it sends an Abis -IS-2000 FCH Fwd
33 message including a Base Station Acknowledgement Order with layer 2
34 acknowledgement required, to the MS over the forward traffic channel.
35 m. After receiving a BS Ack Order message, the MS begins sending Idle Tch Data Frames
36 over the reverse traffic channel. Then the BTS transmits this frame message with an
37 Abis -IS-2000 FCH Rvs message.
38 n. The MS Ack Order message is sent from MS, and then the BTS transmits it to the BSC
39 with an Abis -IS-2000 FCH Rvs message.
40 o. The BSC then sends the Abis -IS-2000 FCH Fwd message including the Service Connect
41 message to the BTS specifying the service configuration for the call. Then the BTS
42 transmits the Service Connect message to the MS. The MS begins processing traffic in
43 accordance with the specified service configuration.
20
1 p. On receipt of the Service Connect message, the MS responds with a Service Connect
2 Completion message. Then the BTS transmits it with an Abis -IS-2000 FCH Rvs
3 message.
4 q. After the radio traffic channel and circuit have both been established and fully
5 interconnected, the BSC sends the Assignment Complete message to the MSC and
6 considers the call to be in conversation state.
7 The MSC stops timer T10 upon receipt of the Assignment Complete message.
8
9
21
1 5.2 Mobile Terminated Call
2 This section describes the call flow associated with a mobile station call termination in the
3 cdma2000 system. An Abis -PCH Msg Transfer Ack and an Abis -ACH Msg Transfer Ack are
4 not presented in the following figure to simplify the figure, but actually, they would be sent
5 after receipt of Abis -PCH Msg Transfer message or Abis -ACH Msg Transfer message
6 respectively.
7
MS BTS BSC MSC Time Comment
Paging Request
a
General Page AbAbis -PCH Msg. Transfer (GPM)
b
Page AbAbis -ACH Msg. Transfer Complete L3 Info:
c
Paging Response
d
BS Ack Order AbAbis -PCH Msg. Transfer (BS Ack)
e
Assignment
AbAbis -BTS Setup f
g
A3Abis -Connect
h
A3Abis -Connect Ack
i
AbAbis -BTS Setup
j
Ack
Null Traffic A3Abis -IS-2000 FCH Fwd (Null Data)
k
A3Abis -IS-2000 FCH Rvs (Idle)
Extended l
Channel AbAbis -PCH Msg. Transfer (ECAM)
m
TCH Preamble A3Abis -IS-2000 FCH Rvs (Preamble)
n
BS Ack Order A3Abis -IS-2000 FCH Fwd (BS Ack)
o
Idle Tch Data A3Abis -IS-2000 FCH Rvs (Idle)
p
MS Ack A3Abis -IS-2000 FCH Rvs (MS Ack)
q
Service Connect A3Abis -IS-2000 FCH Fwd (SCM)
r
Serv. Con. Completion A3Abis -IS-2000 FCH Rvs (SCCM)
s
Assignment
t
Alert with Info A3Abis -IS-2000 FCH Fwd (AWIM)
u
MS Ack Order A3Abis -IS-2000 FCH Rvs (MS Ack)
v
Connect Order A3Abis -IS-2000 FCH Rvs (Connect Order)
w
BS Ack Order A3Abis -IS-2000 FCH Fwd (BS Ack)
x
Connect
8 y
9 Fig. 5-2 Mobile Terminated Call
22
1
23
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), put the message
4 into an Abis -PCH Msg Transfer Message and sends the Abis -PCH
5 Msg Transfer Message to the BTS. The BTS sends the GPM to the MS
6 over the paging channel. The BSC may send this message to multiple
7 BTSs managed by this BSC. In the following description, it is assumed
8 that the BSC sends this message to single BTS.
9 c. The MS acknowledges the page by transmitting a Page Response

10 Message (PRM) to the BTS over the access channel. Upon receipt of
11 this message, the BTS put this message into an Abis -ACH Msg
12 Transfer Message and sends it to the BSC.
13 d. The BSC sends the Complete Layer 3 Information message containing

14 the Paging Response message to the MSC.
15 e. The BSC acknowledges the receipt of the PRM from the MS with a
16 Base Station Acknowledgment Order to the MS. This message is sent
17 by the BSC to the BTS in the Abis -PCH Msg Transfer.
18 f. The MSC sends an Assignment Request message to request

19 assignment of radio resources.
20 g. The BSC sends an Abis -BTS Setup message to the BTS to request
21 allocation of radio resources at the BTS. The BSC shall allocate a code
22 channel and include it in the Abis -BTS Setup.
23 h. Upon receipt of Abis -BTS Setup message, the BTS allocates radio
24 resources and sends an Abis -Connect message to initiates an Abis
25 connection and to report the result of resource allocation.
26 i. The BSC replies with an Abis -Connect Ack message to complete the
27 Abis connection.
28 j. The BTS sends Abis -BTS Setup Ack to acknowledge the Abis -BTS
29 Setup. The BTS may allocate a code channel. In this case, the BTS
30 includes the allocated code channel in the Abis -BTS Setup Ack.
31 Unless the BTS allocates a code channel, the BTS includes the code
32 channel that has been indicated by Abis -BTS Setup (step g) in the
33 Abis -BTS Setup Ack.
24
1 k. The BSC sends an Abis -IS-2000 FCH Fwd (Null Traffic Data)
2 message to the BTS. The BTS starts sending Null Traffic Data to the
3 MS. This allows the MS to acquire the FCH (Fundamental channel).
4 The BTS may have function which sends Null Traffic data for
5 synchronization between the BTS and the MS. Whether the BTS has
6 the function or not, the BSC is assumed to send Null Traffic.
7 l. Upon receiving the first Abis -IS-2000 FCH Fwd (Null Traffic Data)
8 message, the BTS starts to send Abis -IS-2000 FCH Rvs (Idle frame)
9 message to the BSC.
10 m. The BSC sends an Extended Channel Assignment message to assign

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

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

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

22 This is sent by the BTS to the BSC in the Abis -IS-2000 FCH Rvs
23 message.
24 r. The BSC sends the Service Connect Message (SCM) to the MS

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

30 with a Service Connect Completion Message (SCCM). Upon receipt
31 of this message at the BTS, it sends Abis -IS-2000 FCH Rvs message
32 containing this message to the BSC.
33 t. After the radio traffic channel and circuit have both been established,
34 the BSC sends the Assignment Complete message to the MSC.
25
1 u. The BSC sends an Alert with Information Message (AWIM) to the MS
2 to cause ringing at MS. This message is sent by the BSC to BTS in the
3 Abis -IS-2000 FCH Fwd message.
4 v. The MS acknowledges the reception of the Alert with Information

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

7 acknowledgment required, is transmitted to the BSC via the BTS.
8 x. The BSC acknowledges the Connect Order with the BS Ack order.
9 y. The BSC sends a Connect message to the MSC to indicate that the call
10 has been answered at the MS. At this point, the call is considered stable
11 and in the conversation state.
12
13
26
1 5.3 Call Clearing
2
3 5.3.1 Call Clearing initiated by MS

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

24 reverse traffic channel. In response to the order, BTS sends an
25 Abis -IS-2000 FCH Rvs message containing the Release Order
26 message to the BSC.
27 b. The BSC then sends the Clear Request message to the MSC to initiate
28 the call clear transaction. Timer T300 is started by the BSC.
29 c. The MSC starts timer T315 and sends a Clear Command message to
30 the BSC to instruct the BSC to release the associated dedicated
31 resource (such as terrestrial circuit). The BSC stops timer T300.
32 d. In response to the Clear Command message from the MSC, the BSC
33 sends an Abis -IS-2000 FCH Fwd message containing the Release
27
1 Order message. The BTS then acknowledges the MS by sending it a
2 Release Order over the forward traffic channel.
3 e. The BSC then sends an Abis -BTS Release message to the BTS.
4 f. The BTS releases the radio resource and sends Abis -Remove message
5 to the BSC.
6 g. In response to the Abis -Remove message from the BTS, BSC sends an
7 Abis -Remove Ack message to the BTS.
8 h. The BTS sends an Abis -BTS Release Ack message to the BSC to
9 acknowledge the Abis removal.
10 i. The BSC sends a Clear Complete message to the MSC. Then BSC
11 releases the related terrestrial circuit to the BTS, if allocated. And the
12 MSC stops timer T315 upon receipt of the Clear Complete message.
13 The MSC releases the underlying transport connection.
14
15
28
1 5.3.2 Call Clearing initiated by BS/MSC
2 BS
MS BTS BSC MSC Time
3
Clear Request a
4
T300
Clear Command b
5 Release Order Abis-IS-2000 FCH Fwd (Release Order)
c
6 Release Order Abis-IS-2000 FCH Rvs (Release Order) d

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

8 acknowledge the Abis removal
9 i. Upon receipt of the Abis BTS Release Ack message, the BSC sends
10 the Clear Complete message to the MSC. The MSC stops timer T315
11 upon receipt of the Clear Complete message. The MSC releases the
12 underlying transport connection.
13 5.3.3 Call Clearing initiated by BTS
BS
MS BTS BSC MSC Time
Abis-BTS Release Request Clear Request a

T300
Clear Command b
Release Order Abis-IS-2000 FCH Fwd (Release Order)
c
Release Order Abis-IS-2000 FCH Rvs (Release Order) d

)
T315
Abis-BTS Release e
Abis-Remove
f
Abis-Remove Ack g
Abis-BTS Release ACK

h
Clear Complete
i
14
15 Fig. 5-5 Call Clearing initiated by BTS
16 a. In the case of a radio channel failure between the MS and the BTS, or
17 if the MS is not active, the BTS sends an Abis -BTS Release Request
30
1 message to BSC. In response to the message the BSC sends a Clear
2 Request message to the MSC. The BSC starts timer T300 and waits for
3 the Clear Command from the MSC (step b). A Call Clearing flow
4 initiated by BS starts from this step.
5 b. The MSC starts timer T315 and sends a Clear Command message to
6 instruct the BSC to release the associated dedicated resource (such as
7 terrestrial circuit). The BSC stops timer T300.
8 c. In response to the Clear Command message from the MSC, the BSC
9 sends Abis -IS-2000 FCH Fwd containing the Release Order
10 message.The BTS sends the Release Order over the forward traffic
11 channel.
12 d. The MS replies with a Release Order over the reverse traffic channel.
13 In response to the order, BTS sends an Abis -IS-2000 FCH Rvs
14 containing the Release Order message to the BSC.
16 f. The BTS releases the radio resource and sends Abis -Remove message
17 to the BSC.
18 g. In response to the Abis -Remove message from the BTS and BSC
19 sends an Abis Remove Ack message to the BTS and returns a Clear
20 Complete message to the MSC. Then BSC releases the related
21 terrestrial circuit to the BTS, if allocated.
22 h. The BS sends an Abis -BTS Release Ack message to the BSC to

23 acknowledge the Abis -removal
24 i. Upon receipt of the Abis BTS Release Ack message, the BSC sends
25 the Clear Complete message to the MSC. The MSC stops timer T315
26 upon receipt of the Clear Complete message. The MSC releases the
27 underlying transport connection.
28
31
1 5.4 Handoff
2 This section describes handoff procedure using Abis interface within the BS. The handoff
3 between BSs is realized by A3 and A7 interface specified in 3GPP2 A.S0001.
4 5.4.1 Soft/Softer Handoff (Intra-BTS)

5
Time
MS BTS BSC
Ab Abis-BTS Setup a
A3 Abis -Connect b
A3 Abis -Connect Ack c
Ab Abis -BTS Setup Ack d
Extended/General/Universal
Handoff Direction Message A3 Abis -IS-2000 FCH Fwd e
MS Ack Order A3 Abis-IS-2000 FCH Rvs f
Handoff Completion Message A3 Abis-IS-2000 FCH Rvs g
BS Ack Order A3 Abis -IS-2000 FCH Fwd h
6 Fig.5-6 Soft/Softer Handoff (Intra-BTS)
7
8 a. The BSC sends an Abis -BTS Setup message to the BTS to request that the specified
9 cells be added to the call. The BSC shall allocate a code channel and include it in the
10 Abis -BTS Setup.
11 b. The BTS allocates internal resources related to the specified cells. The BTS sends an
12 Abis -Connect message to the SDU function.
13 c. The SDU function of BSC replies with an Abis -Connect Ack message and allocate
14 internal resources.
15 d. The BTS sends Abis -BTS Setup Ack to acknowledge the Abis -BTS Setup. The BTS
16 may allocate a code channel. In this case, the BTS includes the allocated code channel in
17 Abis -BTS Setup Ack. Unless the BTS allocates a code channel, the BTS includes the
18 code channel that has been indicated by Abis -BTS Setup (step a) in the Abis -BTS Setup
19 Ack.
20 e. The BSC sends an Extended / General / Universal Handoff Direction Message to the MS
21 to add the new cell to the active set.
32
1 f. The MS acknowledges receipt of the Extended / General / Universal Handoff Direction
2 Message with an MS Ack Order.
3 g. The MS indicates successful results of processing the Extended / General / Universal
4 Handoff Direction Message by sending a Handoff Completion message.
5 h. The BSC acknowledges receipt of the Handoff Completion Message by sending a BS
6 Ack Order.
7
8 5.4.2 Soft/Softer Handoff (Inter-BTS)

9
Time
Source Target
MS BTS BTS BSC
Ab Abis -BTS Setup a

A3 Abis -Connect b
A3 Abis -Connect Ack c
Ab Abis -BTS Setup Ack d
A3 Abis -IS-2000 FCH Fwd( Forward Frames) e
Forward Frames f
A3 Abis -IS-2000 FCH Rvs ( Ide le Frames) g
Ab Abis -Traffic Channel h
Extended/General/Universal
Handoff Direction Message A3 Abis-IS-2000 FCH Fwd i
MS Ack Order A3 Abis -IS-2000 FCH Rvs j
Handoff Completion Message A3 Abis -IS-2000 FCH Rvs k
BS Ack Order A3 Abis-IS-2000 FCH Fwd l
10 Fig.5-7 Soft/Softer Handoff (Inter-BTS)
11 a. The BSC decides that one or more cells at the target BTS are needed to support the call
12 in soft/softer handoff. The BSC sends an Abis -BTS Setup to the target BTS to get the
13 resource between BSC and the target BTS. The BSC shall allocate a code channel and
14 include it in the Abis -BTS Setup.
15 b. If resources are available, The target BTS responses with Abis -Connect message.
16 c. The BSC replies with an Abis -Connect Ack message to complete the Abis connection.
17 d. The target BTS sends Abis-BTS Setup Ack to acknowledge the Abis -BTS Setup. The
18 target BTS may allocate a code channel. In this case, the target BTS includes the
19 allocated code channel in Abis -BTS Setup Ack. Unless the target BTS allocates a code
20 channel, the target BTS includes the code channel that has been indicated by Abis -BTS
21 Setup (step a) in the Abis -BTS Setup Ack.
22 e. The BSC begins to send the forward frames to the target BTS.
33
1 f. The target BTS transmits the forward frames to the MS.
2 g. The target BTS begins to transmit the forward frames as soon as synchronization has
3 occurred and to send reverse idle frames. The reverse frames contain the timing
4 adjustment information necessary to achieve synchronization.
5 h. If the BSC has chosen to be notified of the start of transmission and reception at the
6 target BTS, when its SDU function and the target BTS have synchronized Abis traffic
7 subchannel, the BSC send an Abis -Traffic Channel Status message to the source BTS
8 i. The BSC sends an Extended / General / Universal Handoff Direction Message to the MS
9 to add the new cell to the active set.
10 j. The MS acknowledges receipt of the Extended / General / Universal Handoff Direction
11 Message with an MS Ack Order.
12 k. The MS indicates successful results of processing the Extended / General / Universal
13 Handoff Direction Message by sending a Handoff Completion message.
14 l. The BSC acknowledges receipt of the Handoff Completion Message by sending a BS
15 Ack Order.
16
34
1 5.5 SMS Delivery
2
3 5.5.1 SMS Delivery on the Paging channel

4 This section provides the call flow description for the delivery of an SMS from the MSC
5 to an idle mobile station on the paging channel.
6
BS
ADDS Page
AbAbis--PCH Msg. Transfer a
(Data Burst Message)
b
Data Burst Message
c
MS Ack Order
AbAbis-ACH Msg.Transfer d
(MS Ack Order)
e
ADDS Page Ack
f
7
8 Fig. 5-8 SMS Delivery on the Paging channel
9 a. When the MSC determines that a point-to-point short message should be sent to an
10 idle MS, the MSC sends ADDS Page message to the BSC.
11 b. The BSC sends the Abis -PCH Msg. Transfer that includes a Data Burst Message.
12 The Data Burst Message contains the short message in received ADDS Page.
13 c. The BTS transfers the Data Burst Message which is included in the Abis -PCH Msg.
14 Transfer message, on a Paging Channel.
15 d. The MS acknowledges the receipt of the Data Burst Message, if it is required.
16 e. The BTS sends the Abis -ACH Msg. Transfer message that contains an MS Ack
17 Order Message.
18 f. The BSC sends ADDS Page Ack to acknowledge the ADDS Page.
19
35
1 5.5.2 SMS Delivery on the Access channel
2 This section provides the call flow description for the delivery of an SMS from an idle
3 mobile station to the MSC on the access channel.
BS
MS BTS BSC MSC
Time Comment
Data Burst Message

AbAbis-ACH Msg. Transfer a
(Data Burst)
b
ADDS Transfer
AbAbis-PCH Msg.Transfer c
(BS Ack Order)
d
BS Ack Order
e
4
5 Fig. 5-9 SMS Delivery on the Access channel
6
7 a. The MS sends a Data Burst Message on the Access Channel to transfer the SMS
8 message.
9 b. The BTS sends the Abis -ACH Msg. Transfer message that includes the Data Burst
10 Message received on the Access Channel.
11 c. The BSC sends the ADDS Transfer message to the MSC containing the Data Burst
12 Message received from the MS in the ADDS User Part element.
13 d. The BTS sends the Abis -PCH Msg. Transfer message that includes the BS
14 Acknowledge Order Message to acknowledge the Data Burst Message, if it is
15 required.
16 e. The BTS sends the BS Ack Order included in the Abis -PCH Msg. Transfer message.
17
36
1 5.5.3 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
3 a mobile station operating on the traffic channel.
BS
MS BTS BSC MSC
Time Comment
ADDS Deliver
A3Abis-IS-2000 FCH Fwd a
b
Data Burst Message
c
MS Ack Order
A3Abis-IS-2000 FCH Rvs d
(MS Ack Order)
e
ADDS Deliver Ack
f
4
5 Fig. 5-10 SMS Delivery on the Traffic channel to MS
6 a. When the MSC determines that a point-to-point short message should be sent to an
7 MS operating on a traffic channel, the MSC sends ADDS Deliver message to the
8 BSC.
9 b. The BSC sends Abis -IS-2000 FCH Fwd containing the Data Burst Message
10 c. The Data Burst Message is sent on the traffic channel.
11 d. The MS acknowledges the receipt of the Data Burst Message, if it is required.
12 e. The BTS sends Abis -IS-2000 FCH Rvs containing the MS Ack Order.
13 f. The BSC sends ADDS Deliver Ack to acknowledge the ADDS Deliver.
14
15
37
1 5.5.4 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
3 station operating on the traffic channel to the MSC.
BS
Data Burst Message

AbA3-IS-2000 FCH Rvs a
b
ADDS Deliver
AbA3-IS-2000 FCH Fwd c
(BS Ack Order)
d
BS Ack Order
e
4
5
6
7 Fig. 5-11 SMS Delivery on the Traffic channel from MS
8 a. The MS sends a Data Burst Message to the BTS on the Access Channel to transfer
9 the SMS message.
10 b. The BTS sends Abis -IS-2000 FCH Rvs containing the Data Burst Message to the
11 BSC.
12 c. The BS sends an ADDS Deliver message to the MSC. The ADDS User Part element
13 contains the SMS message.
14 d. The BSC sends an Abis -IS-2000 Fwd message and includes the BS Ack Order to
15 acknowledge receipt of the Data Burst Message, if it is required.
16 e. The BTS transfer the MS Ack Order.
17
18
38
1 5.6 Traffic Burst Operation
2
3 5.6.1 Initial Traffic Burst Example Abis Connection Not Yet Established
4 The example below describes the support of traffic burst operation when the Abis connection
5 has not yet been established.
SCRM (data to be sent)

a
AbAbis-BTS Setup
b
A3Abis-Connect
c
A3Abis-Connect Ack
d
AbAbis-BTS Setup Ack
e
AbAbis-Burst Request
f optional
AbAbis-Burst Response g optional
AbAbis-Burst Commit h
ESCAM
i
Layer 2 Ack
j
Forward and/or reverse traffic burst
k
6
7 Fig. 5-12 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 of
12 a service instance in soft/softer handoff. This example assumes that a
13 Fundamental Channel (FCH) leg already exists on the selected cell(s)
14 at the BTS.
15 b. The BSC assigns an Abis From ID value and sends an Abis BTS Setup
16 message to the BTS to establish an Abis traffic connection to support a
17 Supplemental Channel (SCH) for the call. This example shows only a
18 single Abis connection being established. The BSC is not required to
19 assign a physical Frame Selector at this time.
39
1 c. The BTS assigns a traffic circuit and optionally a Channel Element ID
2 (CE ID) for each Abis traffic connection and sends an Abis -Connect
3 message to the BSC indicating the Traffic Circuit ID, optional Abis
4 From ID and CE ID to be associated with the specified Abis From ID.
5 The BSC and BTS save the association of CE ID, Traffic Circuit ID,
6 with Cell ID(s). The BSC also saves the Abis From ID value, to be
7 included in subsequent Abis messages to the BTS. This is only done at
8 the initial burst.
9 d. The BSC responds with anAbis Connect Ack message to complete the
10 Abis connection. This includes an Abis From ID value assigned by the
11 BSC, which will be included by the BTS in subsequent Abis messages
12 to the BSC.
13 e. The BTS sends Abis -BTS Setup Ack messages to the BSC to complete
14 the Abis traffic circuit connection setup procedure for the specified set
15 of cells. This includes an Abis From ID value assigned by the BTS,
16 which will be included by the BSC in subsequent Abis messages to the
17 BTS for this call association.
18 When the BSC has knowledge of resources for SCH in the BTS, the
19 procedure at step f and at step g is not necessary.
20 f. The BSC sends an Abis -Burst Request including the Abis to ID to the
21 BTS to request the reservation of the needed radio resources for the
22 supplemental channel. Note that the BSC may send an Abis -Burst
23 Request to the BTS at any time after receiving the Abis -BTS Setup
24 message in step c, and that the set of cells may be subset of the cells
25 assigned in step a-e.
26 g. The BTS determines that it can reserve part or all of the requested
27 resources and sends Abis -Burst Response message(s) including Abis
28 From ID to the BSC indicating the resources that have been reserved
29 and committed to the traffic burst, and the cause value for any
30 uncommitted cells. Each reservation includes a physical Channel
31 Element. Note that the physical Channel Element may be allocated any
32 time after step b.
33 h. The BSC makes a final decision on the resources to be used for the
34 traffic burst and sends an Abis -Burst Commit message to each BTS
35 indicating the set of committed resources that will actually be used for
36 the traffic burst. Note that the BSC may allocate the frame selector any
37 time after step b. Any resources (cells) not included in the Abis -Burst
38 Commit message may be released by the BTS.
40
1 i. The BSC commands the MS to prepare for the traffic burst via an
2 ESCAM message.
3 j. The MS acknowledges the command from the source BS with a Layer

4 2 Ack.
5 k. The network and MS exchange forward and/or reverse traffic burst

6 information for the specified duration, or until the BSC terminates or
7 extends the traffic burst.
8
9
41
1 5.6.2 Subsequent Traffic Burst Example
2 The example below describes the support of traffic burst operation when the Abis connection
3 for the supplemental channel (SCH) has already been established.
SCRM (data to be sent)

a
AbAbis-Burst Request
b optional
AbAbis-Burst Response
c optional
AbAbis-Burst Commit
d
ESCAM
e
Layer 2 Ack
f
Forward and/or reverse traffic burst g
5 Fig. 5-13 Subsequent Traffic Burst Example
6 a. Either the BSC receives an indication from the MS (via a SCRM

7 message) or from the network (via data being received from the
8 PDSN) that data needs to be sent to/from the MS.
9 When the BSC has knowledge of resources for SCH in the BTS, the
10 procedure at step b and at step c is not necessary.
11 b. The BSC decides a traffic burst is required on one or more cells for
12 which an Abis connection already exists in support of a supplemental
13 channel. The BSC sends an Abis -Burst Request to the BTS to request
14 the reservation of the needed radio resources for the supplemental
15 channel.
16 c. The target BS determines that it can reserve part of all of the requested
17 resources and sends Abis -Burst Response massage(s) to the BSC
18 indicating the resources that have been reserved and committed to the
19 traffic burst, and the cause value for any uncommitted cells. Each
20 reservation includes a physical Channel Element. Note that the
21 physical Channel Element may be allocated any time after step b.
22 d. The BSC makes a final decision on the resources to be used for the
23 traffic burst and sends an Abis -Burst Commit message to each BTS
24 indicating the set of committed resources that will actually be used for
42
1 the traffic burst. Note that the BSC may allocate the frame selector any
2 time after step b. Any resources (cells) not included in the Abis -Burst
3 Commit message may be released by the BTS.
4 e. The BSC commands the MS to prepare for the traffic burst via an
5 ESCAM message.
6 f. The MS acknowledges the command from the source BS with a Layer

7 2 Ack.
8 g. The network and MS exchange forward and/or reverse traffic burst

9 information for the specified duration, or until the BSC terminates or
10 extends the traffic burst.
11
12
13 Abis Interface Message Formats

14 For Abis Interface message there are a number of information elements that are
15 individually defined in section 6.1. Each information element in a given message is tagged
16 with a reference in section 6.1, a direction indication (i.e., some elements within a message
17 are bi-directional and others are not), and a mandatory/optional type (M/O) indicator.
18 The inclusion of information elements in each message is specified as follows:
19 ? M - information elements which are mandatory for the message.
20 ? O - information elements which are optional for the message.
21 6.1 Abis interface message

22
23 6.1.1 Abis-ACH Msg Transfer

24 This Abis interface message is sent from the BTS to the BSC to notify the BSC of the
25 reception of the contained message or Layer 2 acknowledgment on the specified access
26 channel.
43
Information Element Section Element Direction Type
Reference
Message Type 7.2 BTS -> BSC M
Correlation ID 7.3 BTS -> BSC a
O
Mobile Identity (IMSI/MIN) 7.4 BTS -> BSC O
Mobile Identity (ESN) 7.4 BTS -> BSC O
Cell Identifier 7.5 BTS -> BSC b
O
Air Interface Message 7.6 BTS -> BSC O
Manufacturers Specific Record 7.7 BTS -> BSC O
1 a. If this element is included in this message, the value shall be returned in the
2 Abis -ACH Msg Transfer Ack message.
3 b. This element indicates the cell at the BTS on whose acces s channel the
4 air-interface message or Layer 2 acknowledgment was received.
5
6 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: Abis 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

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
44
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 = [06H] 2
Cell Identification Discriminator = [07H] 3
(MSB) j
MSCID = <any value> j+1
(LSB) j+2
(MSB) Cell = [001H-FFFH] j+3
(LSB) Sector = [0H-FH] (0H = Omni) j+4
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
Manufacturers Specific Records : Abis Element Identifier = [70H] 1
Length = [variable] 2
Manufacturer ID = [00H FFH] 3
Manufacturers specific information 4

n
1
45
1 6.1.2 Abis-ACH Msg Transfer Ack
2
3 This Abis interface message is sent from the BSC to the BTS to acknowledge the receipt of
4 the Abis -ACH Msg Transfer message.
Reference
Message Type 7.2 BSC -> BTS M
Correlation ID 7.3 BSC -> BTS a
O
Manufacturers Specific Record 7.7 BSC -> BTS O
5 a. This field is required if a Correlation ID value was included on the Abis -ACH
6 Msg Transfer message to which this message is a response.
7
8 The following table shows the bitmap layout for the Abis -ACH Msg Transfer Ack
9 message:
7 6 5 4 3 2 1 0 Octet
Message Type = [8FH] 1

Length = [04H] 2
(MSB) 3
5
(LSB) 6

n
10
46
1 6.1.3 Abis-PCH Msg Transfer
2
3 This Abis interface message is sent from the BSC to the BTS to request the sending of the
4 contained message on the specified paging channels to a mobile station.
Reference
O
Mobile Identity (IMSI/MIN) 7.4 BSC -> BTS O
Mobile Identity (ESN) 7.5 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
Manufacturers Specific Record 7.7 BSC -> BTS O
5 a. If this element is included in this message, the value shall be returned in the
6 Abis -PCH Msg Transfer Ack message.
7 b. This element indicates the cells at the BTS on whose paging channel(s) the
8 air-interface message is to be sent.
9 c. This element is included if the source BS wants a Layer 2 acknowledgment

10 from the MS.
11
47
1 The following table shows the bitmap layout for the Abis -PCH Msg Transfer 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 Discriminator = [02H,05H] 3
IF (Discriminator = 02H), Cell Identification {1+:
(MSB) Cell = [001H-FFFH] j
} OR IF (Discriminator = 05H), Cell Identification {1+:
(MSB) LAC = [0001H-FFFFH] j
(LSB) j+1
48
} Cell Identification
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]

n
1
2
3
4
5
6 6.1.4 Abis-PCH Msg Transfer Ack

7 This Abis interface message is sent from the BTS to the BSC to report the results of
8 sending an air interface message on the specified paging when a layer 2 acknowledgment
9 had been requested by the BSC.
Reference
49
O
Layer 2 Ack Request/Results 7.8 BTS -> BSC b
O
Cause 7.9 BTS -> BSC c
O
Manufacturers Specific Record 7.7 BTS -> BSC O
1 a. This element is included if the Abis -PCH Msg Transfer contained this element. It
2 contains the value received on that message.
3 b. This element is included to indicate success or failure in receiving a Layer 2

4 acknowledgment from the MS.
5 c. Inclusion of this element indicates a failure to send the paging channel message as
6 requested in the Abis -PCH Msg Transfer message. Allowable cause values:
7 OAM&P intervention, Equipment failure.
8
9 The following table shows the bitmap layout for the Abis -PCH Msg Transfer Ack message:
7 6 5 4 3 2 1 0 Octet
Message Type = [8DH] 1

Length = [04H] 2
(MSB) 3
5
(LSB) 6
Layer 2 Ack Request/Results: Abis Element Identifier = [23H] 1
Length = [01H] 2
Reserved = [0000 000] Layer 2 3
Ack
= [0/1]
Cause: A1 Element Identifier = [04H] 1
Length = [01H] 2
ext = [0] Cause Value = 3
[07H (OAM&P intervention),
20H (equipment failure)]
50

n
1
2
3
4 6.1.5 Abis-BTS Setup

5
6 This Abis interface message is sent from the BSC to the BTS in order to request the BTS to
7 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 M
Band Class 7.11 BSC -> BTS O
Privacy Info 7.12 BSC -> BTS O
SDU-ID 7.14 BSC -> BTS O

Mobile Identity (IMSI/MIN) 7.4 BSC -> BTS O
Mobile Identity (ESN) 7.4 BSC -> BTS O
Physical Channel Info 7.15 BSC -> BTS O
Abis Cell Info 7.16 BSC -> BTS O
Service Option 7.17 BSC -> BTS O
PACA Timestamp 7.18 BSC -> BTS Oa
Quality of Service Parameters 7.19 BSC -> BTS Ob
Abis Connect Information 7.20 BSC -> BTS Oc
Abis From ID 7.21 BSC -> BTS Od
Manufacturers Specific Records 7.7 BSC -> BTS O
8 a. This element may be present only when the call is eligible for PACA service.
9 b. This element may be only used for packet data calls. In this version of this
10 standard, this element is used to carry a Packet Priority field coded on 4 bits.
11 Values 1110 and 1111 are reserved.
12 c. This element may be used to indicate a code channel that is allocated by the BSC.
13 It is assumed that the Cell Info Record is used and the rest of the fields are filled by
14 0.
51
1 d. This element is optionally included by the BTS. If included, the value shall be
2 saved and used by the BSC in subsequent Abis message for this call association.
3
52
1 d. 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
Privacy Info: Abis Element Identifier = [1AH] 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
53
SDU ID: A1 Element Identifier = [4CH] 1
(MSB) SDU ID = <any value> 3

(LSB) m
= [1,0]

Length = [05H] 2
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
Frame Selector Info: Abis Element Identifier = [07H] 1
Count of Frame Selectors = [01H FFH] 3
Length of Frame Selector Information = [08H] 4
Frame Selector Entry {1+:
Reserved = [00] Frame Selector Index = [00 0001 11 1111] j
Physical Channel Type j+1
= [ 01H Fundamental Channel (FCH),
02H Supplemental Channel (SCH),
03H Dedicated Control Channel (DCCH)]
Abis Traffic Channel Protocol Stack j+2
= [ 01H AAL2 / ATM / Physical Layer]
Frame Offset = [00H FFH] j+3
Reserved = [000] Pilot Gating Rate ARFCN (high part) j+4
= [00, 01, 10] = [000-111]
54
ARFCN (low part) = [00H-FFH] j+5
Forward Channel Bandwidth = [TBD] j+6
Reverse Channel Bandwidth = [TBD] j+7
} Frame Selector Entry
Abis Cell Info: Abis Element Identifier = [08H] 1

Count of Cells = [01H FFH] 3
Cell Entry {1+:
Cell Discriminator Type = [07H] j
(MSB) j+1
(LSB) j+3
Count of Frame Selectors for Cell = [01H FFH] k
Length of Frame Selector Information for Cell = [01H FFH] k+1
Frame Selector Entry {1+:
Reserved Keep Frame Selector Index = [00 0001 11 1111] m
= [0] Abis =
[0,1]
} Frame Selector Entry
} Cell Entry
Service Option: A1 Element Identifier = [03H] 1

(MSB) Service Option 2
= [0000H - XXXXH] (LSB) 3
[Editors Note; In the first phase of the Abis interface standard, any service
options specified in TSB58-B could transfer on the Abis interface.]
PACA Timestamp: A1 Element Identifier = [4EH] 1
Length = [04H] 2
(MSB) 3
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
55
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)
Length of Cell Info Record = <variable> 4
Cell Info Record {1+:
Cell Identification Discriminator = [07H] j
(MSB) j+1
(LSB) j+3
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
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]
56
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 From ID = [02H] r+1
(MSB) A3 From ID = <any value> r+2
(LSB) r+3
Length of A3 To ID = [02H] r+4
(MSB) A3 To ID = <any value> r+5
(LSB) r+6
}Abis Connect Information
Abis From ID: Abis Element Identifier = [71H] 1
Length of Abis From ID = [02H] 1
(MSB) Abis From ID = <any value> 2
(LSB) 3

n
2 6.1.6 Abis-BTS Setup Ack

3 This message is sent from BTS to BSC to acknowledge the Abis -BTS Setup.
4
57
Reference
Call Connection Reference 7.10 BTS -> BSC M
Abis Connect Information 7.20 BTS -> BSC O
Abis From ID 7.21 BTS -> BSC Oa
Abis To ID 7.22 BTS -> BSC Ob
Manufacturers Specific Records 7.7 BTS -> BSC O
1 a. This element is optionally included by the BTS. If included, the value

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

5 corresponding Abis -BTS Setup message
7
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
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)
Length of Cell Info Record = <variable> 4
Cell Info Record {1+:
58
Cell Identification Discriminator = [07H] j
(MSB) j+1
(LSB) j+3
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
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
59
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 From ID = [02H] r+1
(MSB) A3 From ID = <any value> r+2
(LSB) r+3
Length of A3 To ID = [02H] r+4
(MSB) A3 To ID = <any value> r+5
(LSB) r+6
}Abis Connect Information
Abis From ID: Abis Element Identifier = [71H] 1
Length of Abis From ID = [02H] 1
(MSB) Abis From ID = <any value> 2
(LSB) 3
Abis To ID: Abis Element Identifier = [82H] 1
Length of Abis To ID = [02H] 1
(MSB) Abis To ID = <any value> 2
(LSB) 3

n
2 6.1.7 Abis-BTS Release

3 This message is sent from BSC to BTS to instruct the BTS to release the associated
4 dedicated resource.
5
Reference Direction
60
1
2 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

n
3
4 6.1.8 Abis-BTS Release Ack

5 This message is sent from the BSC to the BTS to acknowledge the Abis -BTS Release
6
Reference Direction
7
8 The following table shows the bitmap layout for the Abis-BTS Release Request Ack message:
7 6 5 4 3 2 1 0 Octet
61

Length = [08H] 2
(LSB) 4
(LSB) 6
(MSB) 7
9
(LSB) 10

n
1
2
3 6.1.9 Abis-Burst Request

4 This Abis interface message is sent from the BSC to the BTS to request the reservation of
5 resources in support of a traffic burst.
6
7
8
9
10
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 g

O
62
SDU ID 7.14 BSC -> BTS b
O
Mobile Identity (IMSI) 7.4 BSC -> BTS c
O
Mobile Identity (ESN) 7.4 BSC -> BTS c
O
Cell Identifier List 7.13 BSC -> BTS d
O
Forward Burst Radio Info 7.25 BSC -> BTS e
O
Reverse Burst Radio Info 7.26 BSC -> BTS f
O
Abis To ID 7.22 BSC -> BTS h
O
1 a. If this element is omitted, the target BS shall send all Abis signaling messages
2 related to the call to the same address as is used to reply to this A7 message.
3 b. Optionally included by the source BS. If included, the value shall be saved and
4 used by the target BS on Abis signaling messages.
5 c. This element may be included for OA&M purposes.
6 d. The list of cell identifiers shall be assumed by the target BS to be in priority

7 order with the highest priority cell listed first.
8 e. This element is only included when forward link radio resources are to be
9 allocated to the burst.
10 f. This element is only included when reverse link radio resources are to be
11 allocated to the burst.
12 g. If this element is included in this message, its value shall be returned in the
13 Abis -Burst Response message and used in the Abis -Burst Commit message.
14 h. This element is required if an Abis From ID value was included in an Abis -BTS
15 Setup Ack message previously received from the BS for this call association.
16
63
1 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+:
(MSB) j
(LSB) j+2
Reserved = [00] Downlink Signal Strength Raw = [000000] (ignored) k
(MSB) CDMA Target One Way Delay k+1
(LSB) k+2
} Downlink Radio Environment
-- Continued on next page --
2
64
1
-- Continued from previous page --
CDMA Serving One Way Delay: A1 Element Identifier = [0CH] 1
Length = [08H] 2
Cell Identification Discriminator = [ 07H] 3
(MSB) 4
MSCID = <any value> 5
(LSB) 6
(MSB) Cell = [001H-FFFH] 7
(LSB) Sector = [0H-FH] (0H = Omni) 8
(MSB) CDMA Serving One Way Delay = [0000H-FFFFH] (x100ns) 9
(LSB) 10
Privacy Info: Abis Element Identifier = [1AH] 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
65
SDU ID: A1 Element Identifier = [4CH] 1
Length = [01H to 06H] 2
(MSB) SDU ID = <any value> 3

(LSB) M
= [1,0]

Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) N
Length = [05H] 2
= [0]
(MSB) 4
ESN = <any value> 5
6
(LSB) 7
Cell Identifier List: A1 Element Identifier = [1AH] 1
Cell Discriminator Type = [07H] 3
Cell Identification{1+:
(MSB) J
(LSB) j+2
1
66
1
Forward Burst Radio Info: Abis 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: Abis 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]
Length = [02H] 2
(LSB) 4
2
67
1
2 6.1.10 Abis-Burst Response

3 This Abis interface message is sent from the BTS to the BSC to respond to a request for
4 reservation of resources to support a traffic burst. Note that one or more Abis -Burst
5 Response messages may be used to respond to a single Abis -Burst Request message. A
6 result (committed or uncommitted) must be provided for all cells in the Abis -Burst Request
7 message. Each Abis -Burst Response message includes at most one committed cell.
9
10
Reference
Call Connection Reference 7.10 BTS -> BSC O
O
Cell Identifier List (Committed) 7.13 BTS -> BSC d
O
Cell Identifier List (Uncommitted) 7.13 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 To ID 7.22 BTS -> BSC f
O
11 a. If this element was included in the Abis -Burst Request message, the
12 value shall be returned in this message.
13 b. This element is only included when this message includes information

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

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

20 about a cell with radio resources reserved for the forward and/or
21 reverse burst indicated in the Forward and/or Reverse Burst Radio Info
22 element.
23 e. This element is only included when this message includes one or more
24 requested cells that are not being reserved. The allowable cause values
68
1 are: OAM&P intervention, Equipment failure, No radio resource
2 available, BS not equipped, Ciphering algorithm not supported,
3 Private Long Code not available or not supported, Requested MUX
4 option or rates not available, Requested privacy configuration not
5 available.
6 f. This element is required if an Abis From ID value was included in an

7 Abis -BTS Setup message previously received from the BSC for this
8 call association.
69
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 Identification {1+:
(MSB) j
(LSB) j+2
Cell Identifier List (uncommitted): A1 Element Identifier = [1AH] 1
2
70
1
(MSB) j
(LSB) j+2
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 = [02H] 2
(LSB) 4
2
71
1
2 6.1.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 Abis
6
7
Reference
Call Connection Reference 7.10 BSC -> BTS O
O
Cell Identifier List (Forward) 7.13 BSC -> BTS Ob
Cell Identifier List (Reverse) 7.13 BSC -> BTS Ob
Forward Burst Radio Info 7.25 BSC -> BTS Oc
Reverse Burst Radio Info 7.26 BSC -> BTS Od
IS-2000 Forward Power Control Mode 7.27 BSC -> BTS Oe
IS-2000 FPC Gain Ratio Info 7.28 BSC -> BTS Of
Abis To ID 7.22 BSC -> BTS g
O
8 a. Optionally included by the source BS. If included, the value shall be

9 saved and used by the target BS on Abis signaling messages.
10 b. The length field of this element shall be set to 0 if no resources are to

11 be allocated in the indicated direction.
12 c. This element is only included when forward link radio resources are to
13 be allocated to the burst.
14 d. This element is only included when reverse link radio resources are to
15 be allocated to the burst.
16 f. This element shall be included when supporting a secondary power

17 control subchannel. It provides information used for forward gain
18 equalization for the SCH.
19 e. This element shall be included when supporting a secondary power

20 control subchannel for the SCH. The FPC_MODE value shall go into
72
1 effect at the earlier of the burst start times indicated in the Forward
2 Burst Radio Info and/or Reverse Burst Radio Info element.
3 g. This element is required if an Abis From ID value was included in an

4 Abis BTS Setup Ack message previously received from the BS for this
5 call association.
73
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
(MSB) j
(LSB) j+2
Cell Identifier List (Reverse): A1 Element Identifier = [1AH] 1
2
74
1
(MSB) j
(LSB) j+2
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: Abis Element Identifier = 1

[14H]
Length = [02H] 2
Reserved = [0000 0] FPC_MODE = [000 011] 3
ACTION_TIME = [00H] (ignored) 4
75
IS-2000 FPC Gain Ratio Info: Abis Element Identifier = [15H] 1
Length = [08H] 2
Initial Gain Ratio = [00H FFH] 3
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
Length = [02H] 2
(LSB) 4
1
2
3 6.1.12 Abis-Connect
4 This message is used the same format as the A3-Connect message.
5 Refer to section 6.1.9.1 "A3-Connect" , 3G-IOS v4.0.0
6 6.1.13 Abis-Connect Ack

7 This message is used the same format as the A3-Connect Ack message.
8 Refer to section 6.1.9.2 "A3-Connect Ack" , 3G-IOS v4.0.0
9 6.1.14 Abis-Remove
10 This message is used the same format as the A3-Remove message.
11 Refer to section 6.1.9.3 "A3-Remove", 3G-IOS v4.0.0
12 6.1.15 Abis-Remove Ack

13 This message is used the same format as the A3-Remove Ack message.
14 Refer to section 6.1.9.4 "A3-Remove Ack", 3G-IOS v4.0.0
76
1 6.1.16 Abis-IS-2000 FCH Fwd
2 This message is used the same format as the A3-IS-2000 FCH Forward message.
3 Refer to section 6.1.9.9 "A3-IS-2000 FCH Forward", 3G-IOS v4.0.0
4 6.1.17 Abis-IS-2000 FCH Rvs

5 This message is used the same format as the A3-IS-2000 FCH Reverse message.
6 Refer to section 6.1.9.10 "A3-IS-2000 FCH Reverse", 3G-IOS v4.0.0
7 6.1.18 Abis-Traffic Channel Status

8 This message is used the same format as the A3-Traffic Channel Status message.
9 Refer to section 6.1.9.15 "A3-Traffic Channel Status", 3G-IOS v4.0.0
10 6.1.19 Abis-BTS Release Request

11 This message is sent from the BTS to the BSC to request deallocation resources..
12

Reference Direction
Call Connection Reference 7.10 BTS -> BSC M
Cause 7.9 BTS -> BSC O
Manufacturers Specific Records 7.7 BTS -> BSC O
13
14 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
77
Length = [01H] 2
ext = [0] Cause Value = 3
[07H (OAM&P intervention),
20H (equipment failure)]

n
1 6.1.20 Abis-IS-2000 SCH Fwd

2 This message is used the same format as the A3-IS-2000 SCH Forward message.
3 Refer to section 6.1.9.16 "A3-IS-2000 SCH Forward", 3G-IOS v4.0.0
4 6.1.21 Abis-IS-2000 SCH Rvs

5 This message is used the same format as the A3-IS-2000 SCH Reverse message.
6 Refer to section 6.1.9.17 "A3-IS-2000 SCH Forward", 3G-IOS v4.0.0
7 6.1.22 Abis-IS-2000 DCCH Fwd

8 This message is used the same format as the A3-IS-2000 DCCH Forward message.
9 Refer to section 6.1.9.13 "A3-IS-2000 DCCH Forward", 3G-IOS v4.0.0
10 6.1.23 Abis-IS-2000 DCCH Rvs

11 This message is used the same format as the A3-IS-2000 DCCH Reverse message.
12 Refer to section 6.1.9.14 "A3-IS-2000 DCCH Forward", 3G-IOS v4.0.0
13
78
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 Table7-1 Abis Information Element Identifiers Sorted by Identifier value
Element Name Identifier Interface(s) Reference
(unused value available) 01H
Service Option 03H Abis,A1 6.2.2.96
Cause 04H Abis,A1 6.2.2.125
Frame Selector Info FFS Abis,A7 6.2.2.14
Quality of Service Parameters FFS Abis,A1 6.2.2.54
Abis Cell Info 08H Abis 6.2.2.24
(Note: This Information Element is same with
A7 Cell Info IE in 3GPP2 A.S0001.)
(unused value available) 09-0BH
CDMA Serving One-Way Delay 0CH Abis,A1, A7 6.2.2.79
Mobile Identity 0DH Abis,A1, A7 6.2.2.16
(unused value available) 0E-10H
Forward Burst Radio Info 11H Abis,A7 6.2.2.56
Reverse Burst Radio Info 12H Abis,A7 6.2.2.57
Correlation ID 13H Abis,A3, A7 6.2.2.108
IS-2000 Power Control Mode 15H Abis,A3 6.2.2.64
(unused value available) 17-19H
Cell Identifier List 1AH Abis,A1, A7 6.2.2.21
(unused value available) 1B-1CH
Privacy Info 1DH Abis,A7 6.2.2.143
(unused value available) 1EH-20H
79
Air Interface Message 21H Abis,A7 6.2.2.152
Layer 2 Ack Request/Results 23H Abis,A7 6.2.2.153
Downlink Radio Environment 29H Abis,A1, A7 6.2.2.25
IS-2000 Power Control Info FFS A7 6.2.2.176
IS-2000 FPC Gain Ratio Info 15H Abis,A7 6.2.2.178
(unused value available) 2C-2DH
Call Connection Reference 3FH Abis,A1, A3, A7 6.2.2.98
(unused value available) 40-48H
SDU ID 4CH Abis,A3, A7 6.2.2.91

PACA Timestamp Unused Value? 4EH Abis,A1 6.2.2.149
Band Class 5DH Abis,A1, A7 6.2.2.106
Manufactures Specific Records 70H Abis
Abis From ID 71H Abis
Abis To ID 72H Abis
All other values are reserved.
2 7.2 Message Type

3
4 The Message Type element is used to indicate the type of a message on the Abis interfaces.
5 Element Format:
7 6 5 4 3 2 1 0 Octet
Message Type 1
6
7 Table 7 - 2 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
80
(unused value available) 05H-0AH
Abis -IS-2000 FCH Fwd 0BH Abis Traffic 6.1.16
Abis -IS-2000 FCH Rvs 0CH Abis Traffic 6.1.17
Abis -Traffic Channel Status 0DH Abis Traffic 6.1.18
Abis -IS-2000 DCCH Fwd 0EH Abis Traffic 6.1.22
Abis -IS-2000 DCCH Rvs 0FH Abis Traffic 6.1.23
Abis -IS-2000 SCH Fwd 10H Abis Traffic 6.1.20
Abis -IS-2000 SCH Rvs 11H Abis Traffic 6.1.21
(unused value available) 12H-7FH
Abis -BTS Setup 80H Abis Signaling 6.1.5
Abis -BTS Setup Ack 81H Abis Signaling 6.1.6
Abis -BTS Release 82H Abis Signaling 6.1.7
Abis -BTS Release Ack 83H Abis Signaling 6.1.8
Abis -BTS Release Request 84H Abis Signaling 6.1.19
(unused value available) 85H-8BH
Abis -PCH Msg. Transfer 8CH Abis Signaling 6.1.3
Abis -PCH Msg. Transfer Ack 8DH Abis Signaling 6.1.4
Abis -ACH Msg. Transfer 8EH Abis Signaling 6.1.1
Abis -ACH Msg.Transfer Ack 8FH Abis Signaling 6.1.2
Abis -Burst Request 90H Abis Signaling 6.1.9
Abis -Burst Response 91H Abis Signaling 6.1.10
Abis -Burst Commit 92H Abis Signaling 6.1.11
1 All other values are reserved.
3 7.3 Correlation ID
4 Refer to section 6.2.2.108, 3G-IOS v4.0.0.
5 7.4 Mobile Identity

6 Refer to section 6.2.2.16, 3G-IOS v4.0.0).
7 7.5 Cell Identifier

81
1 7.6 Air Interface Message
2 Refer to section 6.2.2.152, 3G-IOS v4.0.0
3 7.7 Manufacturers Specific Records

4 This information element is used to send manufacturers specific records on the Abis
5 interface.
6
7 6 5 4 3 2 1 0 Octet
Abis Element Identifier 1
Length 2
Manufacturer ID 3
4
Manufacturers specific information
n
7 Length This field shall be set to the length of this element in octets following the
8 Length field.
9 Manufacturer ID This field identifies manufacturer that creates this information element.
10 The value in this field is FFS.
11 Manufacturers specific information
12 This field includes manufacturers specific information. The content in

13 this field is left to the BTS/BSC manufacturer.
14
15 7.8 Layer 2 Ack Request/Results

17
18 7.9 Cause
20
82
1 7.10 Call Connection Reference
3
4 7.11 Band Class

6 7.12 Privacy Info

8 7.13 Cell Identifier List

9
10 Refer to section 6.2.2.21, 3G IOS v4.0.0.
11
12 7.14 SDU-ID
14 7.15 Physical Channel Info

16 7.16 Abis Cell Info

18
19 7.17 Service Option

21 7.18 PACA Timestamp

83
1 7.19 Quality of Service Parameters
3
4 7.20 Abis Connect Information

6 7.21 Abis From ID

7 This element contains an identifier chosen by the BSC for its own use in quickly processing
8 Abis signaling messages received from the BTS. For example, it may be used to identify
9 the resources supporting the call association that are internal to the BSC. If an Abis From
10 ID is supplied by this BSC, then the BTS includes this in the Abis To ID element in
11 subsequent Abis messages to this BSC.
12
7 6 5 4 3 2 1 0 Octet
Length 2
(MSB) Abis From ID 3
(LSB)
13 Length: This field indicates the number of octets in this element

14 following the Length field. The maximum value in this
15 version of this specification is 2 octets.
16 Abis From ID: This field has variable length. The actual length is
17 indicated in the Length field and is dependent upon the
18 particular implementation. In this version of this
19 standard, this value shall be no more than 2 octets long.
20 7.22 Abis To ID
21 This element contains an identifier chosen by the BSC for its own use in quickly processing
22 Abis signaling messages.
23 If an Abis From ID was supplied by the BSC, then the BTS includes this value in the Abis
24 To ID element in subsequent Abis messages to the BSC.
25
7 6 5 4 3 2 1 0 Octet
84
Length 2
(MSB) Abis To ID 3
(LSB)
1 Length: This field indicates the number of octets in this element

2 following the Length field. The maximum value in this
3 version of this specification is 2 octets.
4 Abis To 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 2 octets long.
8 7.23 Downlink Radio Enviroment

10
11 7.24 CDMA Serving One Way Delay

13
14 7.25 Forward Burst Radio Info

16
17 7.26 Reverse Burst Radio Info

19
20 7.27 IS-2000 Forward Power Control Mode

22
85
1 7.28 IS-2000 FPC Gain Ratio Info
3
4 7.29 Cell Identifier List

6
86

A S0003 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

A S0003 PDF

Загружено:

Авторское право:

Доступные форматы

3GPP2 A.

Date: March 16, 2000

Abis interface Technical Specification for cdma2000

(A.S0003 : BSC to BTS Interoperability specification

Revision Description Date

Rev. 1.0.0 Initial Publication March 2000

3 2.1 SCOPE OF THE DOCUMENT..................................................................................................................................4

5 3.1 GLOSSARY ............................................................................................................................................................4

6 4. NETWORK REFERENCE MODEL AND INTERFACES .......................................................................... 7

26 5.1 M OBILE ORIGINATING CALL ...........................................................................................................................19

4 6. ABIS INTERFACE MESSAGE FORMATS ......................................................................................................44

5 6.1 A BIS INTERFACE MESSAGE ......................................................................................................................................44

29 7. INFORMATION ELEMENT DEFINITIONS ...............................................................................................85

30 7.1 INFORMATION ELEMENT IDENTIFIERS............................................................................................................85

11 2.1 Scope of the document

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)

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

14 4.2 Support of paging channel messaging

3 4.3 Support of Access channel messaging

14 4.4 Support of radio functions

17 The interaction of these functions with Operations, Administration, Maintenance, and

20 4.5 Support of broadcast system information functions

28 4.6 Layers 1 & 2

30 4.6.1 Physical Layer Specification (Layer 1)

12 4.6.2 Use of ATM (Layer 2)

17 4.6.3 Field of Application

20 4.6.4 ATM Layer

29 4.6.5 ATM Adaptation Layer

33 AAL51 - for the transfer of signaling, and

34 AAL22 - for the transfer of user traffic (voice/data) on A3 traffic subchannels.

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

3 4.6.6.1 Signaling Connection Transport Protocol Options

8 4.6.6.3 TCP Transport Protocol Usage

11 4.6.6.4 General Use of TCP

17 4.6.6.4.1 Message Delimiting in TCP

2 Figure 4-3- Delimiting Messages in an Abis Application TCP Byte Stream

5 4.6.6.4.3 TCP Connection Release

9 4.6.6.4.4 TCP Port Usage

21 4.6.6.5 Use of TCP for the Abis Interface

24 4.6.7 IP Network Protocol Usage

17 BS Ack Order Abis-IS-2000 FCH Fwd (BS Ack Order)

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

MS BTS BSC MSC Time Comment

9 Fig. 5-2 Mobile Terminated Call

9 c. The MS acknowledges the page by transmitting a Page Response

13 d. The BSC sends the Complete Layer 3 Information message containing

18 f. The MSC sends an Assignment Request message to request

10 m. The BSC sends an Extended Channel Assignment message to assign

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

18 p. The MS stops transmitting the Traffic Channel Preamble and starts to

21 q. The MS sends the MS Ack Order to acknowledge the BS Ack order.

24 r. The BSC sends the Service Connect Message (SCM) to the MS

29 s. On receipt of the Service Connect Message (SCM), the MS responds

4 v. The MS acknowledges the reception of the Alert with Information

6 w. When the call is answered at the MS, a Connect Order, with

3 5.3.1 Call Clearing initiated by MS

22 Fig. 5-3 Call Clearing initiated by MS

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

6 Release Order Abis-IS-2000 FCH Rvs (Release Order) d

12 Fig. 5-4 Call Clearing initiated by BS/MSC