Abis CDMA2000

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 Rev. 1.0.0 Description Initial Publication Date March 2000
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
1. 2.
INTRODUCTION.................................................................................................................................................... 4 OBJECTIVES ........................................................................................................................................................... 4 2.1 SCOPE OF THE DOCUMENT..................................................................................................................................4
3.
GLOSSARY ............................................................................................................................................................... 4 3.1 GLOSSARY ............................................................................................................................................................4
4.
NETWORK REFERENCE MODEL AND INTERFACES .......................................................................... 7 4.1 SUPPORT OF USER TRAFFIC CONNECTIONS TO A FRAME SELECTOR FUNCT ION .........................................10 4.2 SUPPORT OF PAGING CHANNEL MESSAGING...................................................................................................10 4.3 SUPPORT OF A CCESS CHANNEL MESSAGING ..................................................................................................11 4.4 SUPPORT OF RADIO FUNCTIONS.......................................................................................................................11 4.5 SUPPORT OF BROADCAST SYSTEM INFORMATION FUNCTIONS.....................................................................11 4.6 LAYERS 1 & 2 ....................................................................................................................................................12 4.6.1 Physical Layer Specification (Layer 1)..............................................................................................12 4.6.2 Use of ATM (Layer 2)............................................................................................................................12 4.6.3 Field of Application ...............................................................................................................................12 4.6.4 ATM Layer...............................................................................................................................................12 4.6.5 ATM Adaptation Layer..........................................................................................................................12 4.6.6 Network and Transport Protocols.......................................................................................................14
4.6.6.1 4.6.6.2 4.6.6.3 4.6.6.4 4.6.6.5 Signaling Connection Transport Protocol Options...........................................................................14 User Traffic Connection Transport Protocol Options.......................................................................15 TCP Transport Protocol Usage..........................................................................................................15 General Use of TCP..........................................................................................................................15 Use of TCP for the Abis Interface.....................................................................................................17
4.6.7 5.
IP Network Protocol Usage..................................................................................................................17
CALL PROCESSING............................................................................................................................................18 5.1 M OBILE ORIGINATING CALL ...........................................................................................................................19 5.2 M OBILE TERMINATED CALL............................................................................................................................22 5.3 CALL CLEARING................................................................................................................................................27 5.3.1 Call Clearing initiated by MS..............................................................................................................27 5.3.2 Call Clearing initiated by BS/MSC.....................................................................................................29 5.3.3 Call Clearing initiated by BTS...............................................................................................................30 5.4 HANDOFF............................................................................................................................................................32 5.4.1 Soft/Softer Handoff (Intra-BTS)...........................................................................................................32 5.4.2 Soft/Softer Handoff (Inter-BTS)...........................................................................................................33 5.5 SMS DELIVERY .................................................................................................................................................35 5.5.1 SMS Delivery on the Paging channel .................................................................................................35 5.5.2 SMS Delivery on the Access channel..................................................................................................36 5.5.3 SMS Delivery on the Traffic channel to MS.......................................................................................37 5.5.4 SMS Delivery on the Traffic channel from MS..................................................................................38
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
7.
5.6 TRAFFIC BURST OPERATION............................................................................................................................39 5.6.1 Initial Traffic Burst Example Abis Connection Not Yet Established..........................................39 5.6.2 Subsequent Traffic Burst Example ......................................................................................................42 6. ABIS INTERFACE MESSAGE FORMATS ......................................................................................................44 6.1 A BIS INTERFACE MESSAGE ......................................................................................................................................44 6.1.1 Abis-ACH Msg Transfer ..........................................................................................................................44 6.1.2 Abis-ACH Msg Transfer Ack ..................................................................................................................47 6.1.3 Abis-PCH Msg Transfer ..........................................................................................................................48 6.1.4 Abis-PCH Msg Transfer Ack ..................................................................................................................50 6.1.5 Abis-BTS Setup .........................................................................................................................................52 6.1.6 Abis-BTS Setup Ack..................................................................................................................................58 6.1.7 Abis-BTS Release .....................................................................................................................................61 6.1.8 Abis-BTS Release Ack..............................................................................................................................62 6.1.9 Abis-Burst Request...................................................................................................................................63 6.1.10 Abis-Burst Response ................................................................................................................................72 6.1.11 Abis-Burst Commit ...................................................................................................................................77 6.1.12 Abis-Connect.............................................................................................................................................82 6.1.13 Abis-Connect Ack .....................................................................................................................................82 6.1.14 Abis-Remove..............................................................................................................................................82 6.1.15 Abis-Remove Ack......................................................................................................................................82 6.1.16 Abis-IS-2000 FCH Fwd...........................................................................................................................83 6.1.17 Abis-IS-2000 FCH Rvs ............................................................................................................................83 6.1.18 Abis-Traffic Channel Status....................................................................................................................83 6.1.19 Abis-BTS Release Request......................................................................................................................83 6.1.20 Abis-IS-2000 SCH Fwd .........................................................................................................................84 6.1.21 Abis-IS-2000 SCH Rvs ..........................................................................................................................84 6.1.22 Abis-IS-2000 DCCH Fwd .....................................................................................................................84 6.1.23 Abis-IS-2000 DCCH Rvs.......................................................................................................................84 INFORMATION ELEMENT DEFINITIONS ...............................................................................................85 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.11 7.12 INFORMATION ELEMENT IDENTIFIERS............................................................................................................85 M ESSAGE TYPE..................................................................................................................................................86 CORRELATION ID ..............................................................................................................................................87 M OBILE IDENTITY.............................................................................................................................................87 CELL IDENTIFIER...............................................................................................................................................88 A IR INTERFACE M ESSAGE ................................................................................................................................88 M ANUFACTURERS SPECIFIC RECORDS .........................................................................................................88 LAYER 2 A CK REQUEST /RESULTS...................................................................................................................88 CAUSE .................................................................................................................................................................88 CALL CONNECTION REFERENCE .....................................................................................................................89 BAND CLASS ......................................................................................................................................................89 PRIVACY INFO ....................................................................................................................................................89
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
7.13 7.14 7.15 7.16 7.17 7.18 7.19 7.20 7.21 7.22 7.23 7.24 7.25 7.26 7.27 7.28 7.29
CELL IDENTIFIER LIST ......................................................................................................................................89 SDU-ID ..............................................................................................................................................................89 PHYSICAL CHANNEL INFO................................................................................................................................89 A BIS CELL INFO.................................................................................................................................................89 SERVICE OPTION................................................................................................................................................89 PACA TIMESTAMP ............................................................................................................................................89 QUALITY OF SERVICE PARAMETERS ...............................................................................................................90 A BIS CONNECT INFORMATION ........................................................................................................................90 A BIS FROM ID ...................................................................................................................................................90 A BIS TO ID.........................................................................................................................................................90 DOWNLINK RADIO ENVIROMENT ...................................................................................................................91 CDMA SERVING ONE WAY DELAY ................................................................................................................91 FORWARD BURST RADIO INFO.........................................................................................................................91 REVERSE BURST RADIO INFO..........................................................................................................................91 IS-2000 FORWARD POWER CONTROL M ODE................................................................................................91 IS-2000 FPC GAIN RATIO INFO......................................................................................................................92 CELL IDENTIFIER LIST ......................................................................................................................................92
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
1.
Introduction
This document specifies the Abis (between the BSC and the BTS) interface for cdma2000 system. Abis interface is the reference point between the BSC and the BTS. The signaling flows and these signals are described.
2.
Objectives
The Abis interface specification achieves providing an open and interoperable system. And Abis interface does not disturb the coexistence with other A sub-interfaces specified in 3GPP2 A.S0001
2.1
Scope of the document

This specification defines the interface between BTS and BSC within the BS. The interface between BSs is specified in the 3GPP2 A.S0001 3GPP2 Access Network Interfaces Interoperability Specification (January 18th , 2000). The OAM&P related information can be transferred on this interface and the transport layer for these information are desirable to match with Abis interface. They are for further study and this specification does not contain them..
3.
3.1
Glossary
Glossary
The following is a list of acronyms that are used in this specification. 3G-IOS Third Generation InterOperability Specification AWIM Alert With Information Message BS Base Station BSC Base Station Controller BTS Base Tranceiver System ECAM Enhanced Channel Assignment Message GPM General Page Message ITU International Telecommunications Union MAC Medium Access Control MS Mobile Station MSC Mobile Switching Center ORM Origination Message
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
PRM QoS RAN RN RRC SCCM SCM SDU
Page Response Message Quality of Service Radio Access Network Radio Network Radio Resource Control Function Service Connect Completion Message Service Connect Message Selection/Distribution Unit function
1 2 3
4.
Network Reference Model and Interfaces

Following figure shows the network reference model used by this specification.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
BS BSC
Abis Signaling
SDU Function
Abis Signaling Abis Interface
Abis Traffic
Abis Traffic
BTS
CH element
BTS
CH element
a) Abis interface = Abis signaling + Abis traffic b) An SDU function is located in a BSC c) A channel element is located in a BTS Notes : The handoff procedure between BTSs within a BSC is defined in this document. The handoff procedures between the BSs have already defined in 3GPP2 A.S0001.
Fig.4-1. Network Reference Model for Abis interface

\\\\\\\\
Air Interface MS BTS

FCH (f/r-dsch, f/r-dtch) SCH (f/r-dtch) DCCH (f/r-dsch, f/r-dtch)
Abis Interface
BS
BSC
Abis traffic
FCH (Abis-IS-2000 FCH Fwd/Rvs) SCH (Abis-IS-2000 SCH Fwd/Rvs) DCCH (Abis-IS-2000 DCCH Fwd/Rvs)
Abis Signaling
ACH (r-csch) PCH (f-csch) ACH (Abis-ACH Msg Transfer) PCH (Abis-PCH Msg Transfer) BS Control Signaling OAM Signaling (FFS)
1 2 3 4 5 6 7
Note: This figure is informative. All signals defined in air interface are not described in this Figure.
Figure 4-2. Relationship between Air interface and Abis interface (Intra BS Model)
1
Abis function Abis connection establish (BSC invoke) Abis connection release (BSC invoke) Abis connection release (BTS invoke) Transaction - call setup - Handoff
Table 4-1 Abis interface description

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

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

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

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

Various functions can be considered with respect to the radios that exist under the control of a BTS. The interaction of these functions with Operations, Administration, Maintenance, and Provisioning (OAM&P) are for further study.
4.5
Support of broadcast system information functions

In a cdmaOne or a cdma2000 system, each BTS must broadcast various pieces of system information that the MS will capture and use during its interactions with the network. Much of that system information may be administrated through OAM&P functions. A small amount of such system information may be placed in BTS and OAM&P control of a BTS for the same purposes must be defined.
4.6
Layers 1 & 2
4.6.1
Physical Layer Specification (Layer 1)

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

Asynchronous Transfer Mode (ATM) is a suite of protocols that allow fast, efficient delivery of user traffic in a packet environment. ATM, for the purposes of this standard, consists of two main layers: the ATM Layer that uses the physical layer, and the ATM Adaptation Layer that adapts the basic ATM layer to specific uses .
4.6.3
Field of Application
Asynchronous Transfer Mode (ATM) is used to transport both signaling and user traffic (voice/data).
4.6.4
ATM Layer
The ATM Layer uses a basic 53 octet cell consisting of a 5 octet header and 48 octet payload. This standard uses the ATM Layer as specified in ANSI T1.627-1993 Telecommunications Broadband ISDN - ATM Layer Functionality and Specification without modification. For this specification only ATM permanent virtual circuits (PVCs) shall be required for the Abis interface. These virtual circuits shall be configured through administrative procedures and no special signaling interface procedures, e.g., ATM UNI (Q.2931), shall be required.
4.6.5
ATM Adaptation Layer

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

The standard IP protocol, as defined in RFC 791 (see IOS section 1.5.4), shall be used for routing Internet Protocol packets.
17
1 2 3 4 5 6 7 8
5.
Call Processing
18
1 2 3 4 5 6 7 8 9
5.1
Mobile Originating Call

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

This section describes the call flow associated with a mobile station call termination in the cdma2000 system. An Abis -PCH Msg Transfer Ack and an Abis -ACH Msg Transfer Ack are not presented in the following figure to simplify the figure, but actually, they would be sent after receipt of Abis -PCH Msg Transfer message or Abis -ACH Msg Transfer message respectively.
MS
BTS
BSC Paging Request
MSC
Time
Comment
General Page Page BS Ack Order
AbAbis -PCH Msg. Transfer (GPM) AbAbis -ACH Msg. Transfer Complete L3 Info: Paging Response AbAbis -PCH Msg. Transfer (BS Ack) Assignment AbAbis -BTS Setup A3Abis -Connect A3Abis -Connect Ack AbAbis -BTS Setup Ack A3Abis -IS-2000 FCH Fwd (Null Data) A3Abis -IS-2000 FCH Rvs (Idle) AbAbis -PCH Msg. Transfer (ECAM)
a b c d e f g h i j k l m
Null Traffic Extended Channel TCH Preamble BS Ack Order Idle Tch Data MS Ack Service Connect
A3Abis -IS-2000 FCH Rvs (Preamble) A3Abis -IS-2000 FCH Fwd (BS Ack)
n o
A3Abis -IS-2000 FCH Rvs (Idle) A3Abis -IS-2000 FCH Rvs (MS Ack) A3Abis -IS-2000 FCH Fwd (SCM)
p q r s t u v w x y
Serv. Con. Completion A3Abis -IS-2000 FCH Rvs (SCCM) Assignment Alert with Info A3Abis -IS-2000 FCH Fwd (AWIM) MS Ack Order Connect Order BS Ack Order A3Abis -IS-2000 FCH Rvs (MS Ack) A3Abis -IS-2000 FCH Rvs (Connect Order) A3Abis -IS-2000 FCH Fwd (BS Ack) Connect
8 9
Fig. 5-2 Mobile Terminated Call

22
23
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
a.
The MSC sends the Paging Request message to the BSC to initiate a mobile terminated call setup scenario. The BSC constructs a General Page Message (GPM), put the message into an Abis -PCH Msg Transfer Message and sends the Abis -PCH Msg Transfer Message to the BTS. The BTS sends the GPM to the MS over the paging channel. The BSC may send this message to multiple BTSs managed by this BSC. In the following description, it is assumed that the BSC sends this message to single BTS. The MS acknowledges the page by transmitting a Page Response Message (PRM) to the BTS over the access channel. Upon receipt of this message, the BTS put this message into an Abis -ACH Msg Transfer Message and sends it to the BSC. The BSC sends the Complete Layer 3 Information message containing the Paging Response message to the MSC. The BSC acknowledges the receipt of the PRM from the MS with a Base Station Acknowledgment Order to the MS. This message is sent by the BSC to the BTS in the Abis -PCH Msg Transfer. The MSC sends an Assignment Request message to request assignment of radio resources. The BSC sends an Abis -BTS Setup message to the BTS to request allocation of radio resources at the BTS. The BSC shall allocate a code channel and include it in the Abis -BTS Setup. Upon receipt of Abis -BTS Setup message, the BTS allocates radio resources and sends an Abis -Connect message to initiates an Abis connection and to report the result of resource allocation. The BSC replies with an Abis -Connect Ack message to complete the Abis connection. The BTS sends Abis -BTS Setup Ack to acknowledge the Abis -BTS Setup. The BTS may allocate a code channel. In this case, the BTS includes the allocated code channel in the Abis -BTS Setup Ack. Unless the BTS allocates a code channel, the BTS includes the code channel that has been indicated by Abis -BTS Setup (step g) in the Abis -BTS Setup Ack.
b.
c.
d.
e.
f.
g.
h.
i.
j.
24
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
k.
The BSC sends an Abis -IS-2000 FCH Fwd (Null Traffic Data) message to the BTS. The BTS starts sending Null Traffic Data to the MS. This allows the MS to acquire the FCH (Fundamental channel). The BTS may have function which sends Null Traffic data for synchronization between the BTS and the MS. Whether the BTS has the function or not, the BSC is assumed to send Null Traffic. Upon receiving the first Abis -IS-2000 FCH Fwd (Null Traffic Data) message, the BTS starts to send Abis -IS-2000 FCH Rvs (Idle frame) message to the BSC.
l.
m. The BSC sends an Extended Channel Assignment message to assign the FCH. n. The MS starts to send the Traffic Channel Preamble. Upon receiving the Traffic Channel Preamble, the BTS stops sending the idle frames and starts sending the traffic frames containing the Traffic Channel Preamble. The BSC sends the BS Ack Order to the MS via the BTS in the Abis -IS-2000 FCH Fwd message. The MS stops transmitting the Traffic Channel Preamble and starts to transmit idle traffic channel data frames upon receipt of the BS Ack order. The MS sends the MS Ack Order to acknowledge the BS Ack order. This is sent by the BTS to the BSC in the Abis -IS-2000 FCH Rvs message. The BSC sends the Service Connect Message (SCM) to the MS specifying the service configuration for the call. This message is sent by the BSC to the BTS in the Abis -IS-2000 FCH Fwd message. The MS begins processing traffic in accordance with the specified service configuration. On receipt of the Service Connect Message (SCM), the MS responds with a Service Connect Completion Message (SCCM). Upon receipt of this message at the BTS, it sends Abis -IS-2000 FCH Rvs message containing this message to the BSC. After the radio traffic channel and circuit have both been established, the BSC sends the Assignment Complete message to the MSC.
o.
p.
q.
r.
s.
t.
25
1 2 3 4 5 6 7 8 9 10 11 12 13
u.
The BSC sends an Alert with Information Message (AWIM) to the MS to cause ringing at MS. This message is sent by the BSC to BTS in the Abis -IS-2000 FCH Fwd message. The MS acknowledges the reception of the Alert with Information Message by transmitting the MS Ack Order.
v.
w. When the call is answered at the MS, a Connect Order, with acknowledgment required, is transmitted to the BSC via the BTS. x. y. The BSC acknowledges the Connect Order with the BS Ack order. The BSC sends a Connect message to the MSC to indicate that the call has been answered at the MS. At this point, the call is considered stable and in the conversation state.
26
1 2 3 4
5.3
Call Clearing
5.3.1
Call Clearing initiated by MS

BS
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
MS
Release Order
BTS
BSC
Abis-IS-2000 FCH Rvs (Release Order) Clear Request T300
MSC
Time
a b c d
Release Order
Abis-IS-2000 FCH Fwd (Release Order) ) Abis-BTS Release Abis-Remove Abis-Remove Ack Abis-BTS Release Ack
Clear Command
T315
f g h
Clear Complete
i
Fig. 5-3 Call Clearing initiated by MS

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

BS
MS 3 4 5 6 7 8 9 10
Release Order
BTS
BSC
Clear Request T300
MSC
Time
Clear Command Abis-IS-2000 FCH Fwd (Release Order)
b c
Release Order
Abis-IS-2000 FCH Rvs (Release Order) T315 Abis-BTS Release Abis-Remove
Abis-Remove Ack Abis-BTS Release Ack
Clear Complete
h
i
11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
a.
Fig. 5-4 Call Clearing initiated by BS/MSC

In the case where the BSC detects some failures related the call, the BSC sends a Clear Request message to the MSC. The BSC starts timer T300 and waits for the Clear Command from the MSC (step b). A Call Clearing flow initiated by BSC starts from this step. The MSC starts timer T315 and sends a Clear Command message to instruct the BSC to release the associated dedicated resource (such as terrestrial circuit). In the case of a Call Clearing initiated BS, the BSC stops timer T300. A Call Clearing flow initiated by MSC starts from this step. In response to the Clear Command message from the MSC, the BSC sends Abis -IS-2000 FCH Fwd containing the Release Order message. The BTS sends the Release Order message to the MS over the forward traffic channel. The MS replies with a Release Order over the reverse traffic channel. In response to the order, BTS sends a Abis -IS-2000 FCH Reverse n containing the Release Order message to the BSC. 29
b.
c.
d.
1 2 3 4 5 6 7 8 9 10 11 12 13
e. f.
The BSC then sends an Abis -BTS Release message to the BTS. The BTS releases the radio resource and sends Abis Remove message to the BSC. In response to the Abis Remove message from the BTS and BSC sends an Abis Remove Ack message to the BTS. Then BSC releases the related terrestrial circuit to the BTS, if allocated. The BS sends an Abis -BTS Release Ack message to the BSC to acknowledge the Abis removal Upon receipt of the Abis BTS Release Ack message, the BSC sends the Clear Complete message to the MSC. The MSC stops timer T315 upon receipt of the Clear Complete message. The MSC releases the underlying transport connection.
g.
h.
i.
5.3.3
Call Clearing initiated by BTS

BS
MS
BTS
Abis-BTS Release Request
BSC
Clear Request T300
MSC
Time
Clear Command Release Order Abis-IS-2000 FCH Fwd (Release Order)
b c
Release Order
Abis-IS-2000 FCH Rvs (Release Order) ) T315 Abis-BTS Release Abis-Remove
Abis-Remove Ack Abis-BTS Release ACK Clear Complete
h
i
14 15 16 17
a.
Fig. 5-5 Call Clearing initiated by BTS

In the case of a radio channel failure between the MS and the BTS, or if the MS is not active, the BTS sends an Abis -BTS Release Request 30
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
b.
message to BSC. In response to the message the BSC sends a Clear Request message to the MSC. The BSC starts timer T300 and waits for the Clear Command from the MSC (step b). A Call Clearing flow initiated by BS starts from this step. The MSC starts timer T315 and sends a Clear Command message to instruct the BSC to release the associated dedicated resource (such as terrestrial circuit). The BSC stops timer T300. In response to the Clear Command message from the MSC, the BSC sends Abis -IS-2000 FCH Fwd containing the Release Order message.The BTS sends the Release Order over the forward traffic channel. The MS replies with a Release Order over the reverse traffic channel. In response to the order, BTS sends an Abis -IS-2000 FCH Rvs containing the Release Order message to the BSC. The BSC then sends an Abis -BTS Release message to the BTS. The BTS releases the radio resource and sends Abis -Remove message to the BSC. In response to the Abis -Remove message from the BTS and BSC sends an Abis Remove Ack message to the BTS and returns a Clear Complete message to the MSC. Then BSC releases the related terrestrial circuit to the BTS, if allocated. The BS sends an Abis -BTS Release Ack message to the BSC to acknowledge the Abis -removal Upon receipt of the Abis BTS Release Ack message, the BSC sends the Clear Complete message to the MSC. The MSC stops timer T315 upon receipt of the Clear Complete message. The MSC releases the underlying transport connection.
c.
d.
e. f.
g.
h.
i.
31
1 2 3 4 5
5.4
Handoff
This section describes handoff procedure using Abis interface within the BS. The handoff between BSs is realized by A3 and A7 interface specified in 3GPP2 A.S0001.
5.4.1
Soft/Softer Handoff (Intra-BTS)

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

Source BTS Target BTS Time BSC
Ab Abis -BTS Setup A3 Abis -Connect A3 Abis -Connect Ack Ab Abis -BTS Setup Ack A3 Abis -IS-2000 FCH Fwd( Forward Frames) Forward Frames A3 Abis -IS-2000 FCH Rvs ( Ide le Frames) Ab Abis -Traffic Channel Extended/General/Universal Handoff Direction Message A3 Abis-IS-2000 FCH Fwd
a b c d e f g h i j k l
MS Ack Order
A3 Abis -IS-2000 FCH Rvs
Handoff Completion Message
A3 Abis -IS-2000 FCH Rvs
BS Ack Order
A3 Abis-IS-2000 FCH Fwd
10 11 12 13 14 15 16 17 18 19 20 21 22
Fig.5-7 Soft/Softer Handoff (Inter-BTS)

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

This section provides the call flow description for the delivery of an SMS from the MSC to an idle mobile station on the paging channel.
BS MS BTS
AbAbis--PCH Msg. Transfer (Data Burst Message)
BSC
ADDS Page
MSC
Time Comment
a b c d e
Data Burst Message

MS Ack Order AbAbis-ACH Msg.Transfer (MS Ack Order)
ADDS Page Ack
7 8 9 10 11 12 13 14 15 16 17 18 19
Fig. 5-8 SMS Delivery on the Paging channel

a. When the MSC determines that a point-to-point short message should be sent to an idle MS, the MSC sends ADDS Page message to the BSC. b. The BSC sends the Abis -PCH Msg. Transfer that includes a Data Burst Message. The Data Burst Message contains the short message in received ADDS Page. c. The BTS transfers the Data Burst Message which is included in the Abis -PCH Msg. Transfer message, on a Paging Channel. d. The MS acknowledges the receipt of the Data Burst Message, if it is required. e. The BTS sends the Abis -ACH Msg. Transfer message that contains an MS Ack Order Message. f. The BSC sends ADDS Page Ack to acknowledge the ADDS Page.
35
1 2 3
5.5.2
SMS Delivery on the Access channel

This section provides the call flow description for the delivery of an SMS from an idle mobile station to the MSC on the access channel.
BS
MS
Data Burst Message
BTS
BSC
MSC
Time Comment
AbAbis-ACH Msg. Transfer (Data Burst) AbAbis-PCH Msg.Transfer (BS Ack Order)
a b
ADDS Transfer
c d e
BS Ack Order
4 5 6 7 8 9 10 11 12 13 14 15 16 17
a. The MS sends a Data Burst Message on the Access Channel to transfer the SMS message. b. The BTS sends the Abis -ACH Msg. Transfer message that includes the Data Burst Message received on the Access Channel. c. The BSC sends the ADDS Transfer message to the MSC containing the Data Burst Message received from the MS in the ADDS User Part element. d. The BTS sends the Abis -PCH Msg. Transfer message that includes the BS Acknowledge Order Message to acknowledge the Data Burst Message, if it is required.
Fig. 5-9 SMS Delivery on the Access channel
e. The BTS sends the BS Ack Order included in the Abis -PCH Msg. Transfer message.
36
1 2 3
5.5.3
SMS Delivery on the Traffic channel to MS

This section provides the call flow description for the delivery of an SMS from the MSC to a mobile station operating on the traffic channel.
BS MS BTS
A3Abis-IS-2000 FCH Fwd (Data Burst Message)
BSC
ADDS Deliver
MSC a b c d e
ADDS Deliver Ack
Time Comment
Data Burst Message

MS Ack Order A3Abis-IS-2000 FCH Rvs (MS Ack Order)
4 5 6 7 8 9 10 11 12 13 14 15
Fig. 5-10 SMS Delivery on the Traffic channel to MS

a. When the MSC determines that a point-to-point short message should be sent to an MS operating on a traffic channel, the MSC sends ADDS Deliver message to the BSC. b. The BSC sends Abis -IS-2000 FCH Fwd containing the Data Burst Message c. The Data Burst Message is sent on the traffic channel. d. The MS acknowledges the receipt of the Data Burst Message, if it is required. e. The BTS sends Abis -IS-2000 FCH Rvs containing the MS Ack Order. f. The BSC sends ADDS Deliver Ack to acknowledge the ADDS Deliver.
37
1 2 3
5.5.4
SMS Delivery on the Traffic channel from MS

This section provides the call flow description for the delivery of an SMS from a mobile station operating on the traffic channel to the MSC.
BS
MS
Data Burst Message
BTS
AbA3-IS-2000 FCH Rvs (Data Burst Message) AbA3-IS-2000 FCH Fwd (BS Ack Order) BS Ack Order
BSC
MSC a b
ADDS Deliver
Time Comment
c d e
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Fig. 5-11 SMS Delivery on the Traffic channel from MS

a. The MS sends a Data Burst Message to the BTS on the Access Channel to transfer the SMS message. b. The BTS sends Abis -IS-2000 FCH Rvs containing the Data Burst Message to the BSC. c. The BS sends an ADDS Deliver message to the MSC. The ADDS User Part element contains the SMS message. d. The BSC sends an Abis -IS-2000 Fwd message and includes the BS Ack Order to acknowledge receipt of the Data Burst Message, if it is required. e. The BTS transfer the MS Ack Order.
38
1 2 3 4 5
5.6
Traffic Burst Operation
5.6.1
Initial Traffic Burst Example Abis Connection Not Yet Established

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

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

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

This Abis interface message is sent from the BTS to the BSC to notify the BSC of the reception of the contained message or Layer 2 acknowledgment on the specified access channel.
43
Information Element Message Type Correlation ID Mobile Identity (IMSI/MIN) Mobile Identity (ESN) Cell Identifier Air Interface Message Manufacturers Specific Record
Section Reference 7.2 7.3 7.4 7.4 7.5 7.6 7.7
Element Direction BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC M O O O O O O
b a
Type
1 2 3 4 5 6
7
a.
If this element is included in this message, the value shall be returned in the Abis -ACH Msg Transfer Ack message. This element indicates the cell at the BTS on whose acces s channel the air-interface message or Layer 2 acknowledgment was received.
b.
The following table shows the bitmap layout for the Abis -ACH Msg Transfer message: 6 5 4 3 2 1 0 Octet Message Type = [8EH] Abis Element Identifier = [13H] 1 1 2 3 Correlation Value = <any value> (LSB) Mobile Identity (IMSI): A1 Element Identifier = [0DH] Odd/even Indicator = [1,0] Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4 Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD) A1 Element Identifier = [0DH] n n+1 1 2 Type of Identity = [110] (IMSI) 4 5 6 1 2 3
Correlation ID:
Length = [04H] (MSB)
Length = [06H-08H] (10-15 digits) Identity Digit 1 = [0H-9H] (BCD)
Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits) Mobile Identity (ESN):
Length = [05H]
44
Identity Digit 1 = [0000]
Odd/even Indicator = [0]
Type of Identity = [101] (ESN)
(MSB) ESN = <any value> (LSB) Cell Identifier: A1 Element Identifier = [05H]
4 5 6 7 1 2 3 j MSCID = <any value> (LSB) j+1 j+2 j+3 j+4 1 2 3 4 5 Air Interface Message = <any value> (LSB)
Length = [06H] Cell Identification Discriminator = [07H] (MSB)
(MSB) (LSB) Air Interface Message:
Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) Abis Element Identifier = [21H]
Length = <variable> TIA/EIA-IS-2000 Message Type = <00H to FFH> Air Interface Message Length = <variable> (MSB)
k 1 2 3 4 n
Manufacturers Specific Records : Length = [variable]
Abis Element Identifier = [70H]
Manufacturer ID = [00H FFH] Manufacturers specific information
45
1 2 3 4
6.1.2
Abis-ACH Msg Transfer Ack
This Abis interface message is sent from the BSC to the BTS to acknowledge the receipt of the Abis -ACH Msg Transfer message. Information Element Section Element Direction Type Reference Message Type Correlation ID Manufacturers Specific Record 7.2 7.3 7.7 BSC -> BTS BSC -> BTS BSC -> BTS M O O
a
5 6 7 8 9
7
a.
This field is required if a Correlation ID value was included on the Abis -ACH Msg Transfer message to which this message is a response.
The following table shows the bitmap layout for the Abis -ACH Msg Transfer Ack message: 6 (MSB) Correlation Value = <any value> (LSB) Manufacturers Specific Records : Length = [variable] Manufacturer ID = [00H FFH] Manufacturers specific information Abis Element Identifier = [70H] 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 1 2 3 4 n Message Type = [8FH] Abis Element Identifier = [13H]
Correlation ID:
Length = [04H]
10
46
1 2 3 4
6.1.3
Abis-PCH Msg Transfer
This Abis interface message is sent from the BSC to the BTS to request the sending of the contained message on the specified paging channels to a mobile station. Information Element Section Element Direction Type Reference Message Type Correlation ID Mobile Identity (IMSI/MIN) Mobile Identity (ESN) Cell Identifier List Air Interface Message Layer 2 Ack Request/Results Manufacturers Specific Record 7.2 7.3 7.4 7.5 7.13 7.6 7.8 7.7 BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS M O O O O O O O
c b a
5 6 7 8 9 10 11
a.
If this element is included in this message, the value shall be returned in the Abis -PCH Msg Transfer Ack message. This element indicates the cells at the BTS on whose paging channel(s) the air-interface message is to be sent. This element is included if the source BS wants a Layer 2 acknowledgment from the MS.
b.
c.
47
1
7
The following table shows the bitmap layout for the Abis -PCH Msg Transfer message: 6 (MSB) Correlation Value = <any value> (LSB) Mobile Identity (IMSI): A1 Element Identifier = [0DH] Odd/even Indicator = [1,0] Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4 Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD) A1 Element Identifier = [0DH] Odd/even Indicator = [0] (MSB) ESN = <any value> (LSB) Cell Identifier List: A1 Element Identifier = [1AH] 4 5 6 7 1 2 3 j j+1 Type of Identity = [101] (ESN) n n+1 1 2 3 Type of Identity = [110] (IMSI) 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 1 2 3 Message Type = [8CH] Abis Element Identifier = [13H]
Correlation ID:
Length = [04H]
Length = [05H] Identity Digit 1 = [0000]
Length = <variable> Cell Identification Discriminator = [02H,05H] IF (Discriminator = 02H), Cell Identification {1+: (MSB) (LSB) Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni)
} OR IF (Discriminator = 05H), Cell Identification {1+: (MSB) LAC = [0001H-FFFFH] (LSB) j j+1
48
} Cell Identification Air Interface Message: Abis Element Identifier = [21H] 1 2 3 4 5 Air Interface Message = <any value> (LSB) Layer 2 Ack Request/Results: Length = [01H] Reserved = [0000 000] Layer 2 Ack = [0/1] Abis Element Identifier = [70H] Abis Element Identifier = [23H]
Length = <variable> TIA/EIA-IS-2000 Message Type = <00H to FFH> Air Interface Message Length = <variable> (MSB)
k 1 2 3
1 2 3 4 n
1 2 3 4 5 6 7 8 9
6.1.4
Abis-PCH Msg Transfer Ack
This Abis interface message is sent from the BTS to the BSC to report the results of sending an air interface message on the specified paging when a layer 2 acknowledgment had been requested by the BSC. Information Element Section Element Direction Type Reference Message Type 7.2 BTS -> BSC M
49
Correlation ID Layer 2 Ack Request/Results Cause Manufacturers Specific Record
7.3 7.8 7.9 7.7
BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC
O O O O
a b c
1 2 3 4 5 6 7 8 9
7
a.
This element is included if the Abis -PCH Msg Transfer contained this element. It contains the value received on that message. This element is included to indicate success or failure in receiving a Layer 2 acknowledgment from the MS. Inclusion of this element indicates a failure to send the paging channel message as requested in the Abis -PCH Msg Transfer message. Allowable cause values: OAM&P intervention, Equipment failure.
b.
c.
The following table shows the bitmap layout for the Abis -PCH Msg Transfer Ack message: 6 5 4 3 2 1 0 Octet Message Type = [8DH] Abis Element Identifier = [13H] 1 1 2 3 Correlation Value = <any value> (LSB) Layer 2 Ack Request/Results: Length = [01H] Reserved = [0000 000] Layer 2 Ack = [0/1] Abis Element Identifier = [23H] 4 5 6 1 2 3
Correlation ID:
Length = [04H] (MSB)
ext = [0]
Cause:
A1 Element Identifier = [04H] Length = [01H] Cause Value =
1 2 3
[07H (OAM&P intervention), 20H (equipment failure)] Manufacturers Specific Records : Length = [variable] Manufacturer ID = [00H FFH] Manufacturers specific information Abis Element Identifier = [70H] 1 2 3 4
50
1 2 3 4 5 6 7
6.1.5
Abis-BTS Setup
This Abis interface message is sent from the BSC to the BTS in order to request the BTS to assign radio resource, the attributes of which are defined within the message. Information Element Section Element Type Reference Direction Message Type Call Connection Reference Band Class Privacy Info SDU-ID Mobile Identity (IMSI/MIN) Mobile Identity (ESN) Physical Channel Info Abis Cell Info Service Option PACA Timestamp Quality of Service Parameters Abis Connect Information Abis From ID Manufacturers Specific Records 7.2 7.10 7.11 7.12 7.14 7.4 7.4 7.15 7.16 7.17 7.18 7.19 7.20 7.21 7.7 a. b. BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS M M O O O O O O O O Oa Ob Oc Od O
8 9 10 11 12 13 14
This element may be present only when the call is eligible for PACA service. This element may be only used for packet data calls. In this version of this standard, this element is used to carry a Packet Priority field coded on 4 bits. Values 1110 and 1111 are reserved. This element may be used to indicate a code channel that is allocated by the BSC. It is assumed that the Cell Info Record is used and the rest of the fields are filled by 0.
c.
51
1 2 3
d.
This element is optionally included by the BTS. If included, the value shall be saved and used by the BSC in subsequent Abis message for this call association.
52
1
7 6
d.
The following table shows the bitmap layout for the Abis -BTS Setup message: 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) 4 5 (LSB) 6 7 Call Connection Reference = <any value> (LSB) 8 9 10 1 2 3 1 2 Status = [0,1] Available = [0,1] j+1 j+2 (LSB) k j
Message Type = [80H] A1 Element Identifier = [3FH]
(MSB) (MSB) (MSB)
Call Connection Reference:
Length = [08H] Market ID = <any value> Generating Entity ID = <any value>
Reserved = [000]
Band Class:
A1 Element Identifier = [5DH] Length = [01H] Band Class = [00001] (PCS)
Privacy Info:
Abis Element Identifier = [1AH]
Length = <variable> Privacy Mask Information {1+: Reserved = [0] (MSB) Privacy Mask Type = [00001,00010] (public, private) Privacy Mask Length = <variable> Privacy Mask = <any value> } Privacy Mask Information
53
(MSB)
SDU ID: A1 Element Identifier = [4CH] Length = <variable> SDU ID = <any value> (LSB)
1 2 3 m 1 2 3
Mobile Identity (IMSI):
A1 Element Identifier = [0DH] Odd/even Indicator = [1,0] Type of Identity = [110] (IMSI)
Identity Digit 3 = [0H-9H] (BCD)
Identity Digit 2 = [0H-9H] (BCD)
Identity Digit N+1 = [0H-9H] (BCD) = [1111] (if even number of digits) Mobile Identity (ESN): Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD) A1 Element Identifier = [0DH] Odd/even Indicator = [0] (MSB) ESN = <any value> (LSB) Frame Selector Info: Abis Element Identifier = [07H] Type of Identity = [101] (ESN)
n n+1 1 2 3
4 5 6 7 1 2 3 4 j j+1 (FCH), (SCH), j+2 j+3 ARFCN (high part) = [000-111] j+4
Length = <variable> Count of Frame Selectors = [01H FFH] Length of Frame Selector Information = [08H] Frame Selector Entry {1+: Reserved = [00] = Frame Selector Index = [00 0001 11 1111] Physical Channel Type [ 01H Fundamental Channel 02H Supplemental Channel 03H Dedicated Control Channel (DCCH)]
Abis Traffic Channel Protocol Stack = [ 01H AAL2 / ATM / Physical Layer] Frame Offset = [00H FFH] Reserved = [000] Pilot Gating Rate = [00, 01, 10]
54
ARFCN (low part) = [00H-FFH] Forward Channel Bandwidth = [TBD] Reverse Channel Bandwidth = [TBD] } Frame Selector Entry Abis Cell Info: Abis Element Identifier = [08H]
j+5 j+6 j+7
1 2 3 j j+1 j+2 (LSB) j+3 j+4 j+5 k k+1 m
Length = <variable> Count of Cells = [01H FFH] Cell Entry {1+: Cell Discriminator Type = [07H] (MSB) MSCID = <any value> (MSB) (LSB) Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) Count of Frame Selectors for Cell = [01H FFH] Length of Frame Selector Information for Cell = [01H FFH] Frame Selector Entry {1+: Reserved = [0] Keep Abis = [0,1] } Frame Selector Entry } Cell Entry (MSB) Service Option: A1 Element Identifier = [03H] Service Option = [0000H - XXXXH] [Editors Note; In the first phase of the Abis interface standard, any service options specified in TSB58-B could transfer on the Abis interface.] (MSB) PACA Queuing Time = <any value> (LSB) Quality of Service Parameters: Length = [01H] Reserved = [0000] Abis Connect Information{1+: Packet Priority = [0000 1101] A3/A7 Element Identifier = [1BH] A1 Element Identifier = [07H] PACA Timestamp: A1 Element Identifier = [4EH] Length = [04H] (LSB) Frame Selector Index = [00 0001 11 1111]
1 2 3
1 2 3 4 5 6 1 2 3 1
55
Length = <variable> Reserved = [000] Physical Channel Type = [0H - IS-95 Fundamental Channel, 1H Fundamental Channel (FCH), 2H Supplemental Channel (SCH)], Length of Cell Info Record = <variable> Cell Info Record {1+: Cell Identification Discriminator = [07H] (MSB) MSCID = <any value> (LSB) (MSB) (LSB) Reserved = [000] QoF Mask = [00, 01, 10, 11] Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) New Cell Indicator = [0,1] (old, new) Pilot_PN = <any value> Code Channel = [00H - FFH] } Cell Info Record Length of Traffic Circuit ID = [05H] Traffic Circuit ID {1: Length of Traffic Circuit Identifier = [02H] (MSB) Traffic Circuit Identifier = <any value> (LSB) Length of Traffic Connection Identifier = [01H] Traffic Connection Identifier = [00H-FFH] (AAL2 CID) } Traffic Circuit ID Extended Handoff Direction Parameters Field Length = [09H] Extended Handoff Direction Parameters {1+: Search Window A Size (Srch_Win_A) = [0H-FH] Search Window R Size (Srch_Win_R) = [0H-FH] Search Window N Size (Srch_Win_N) = [0H-FH] Add Pilot Threshold (T_Add) high order = [0H-FH] PWR_ Comb _Ind = [0,1] (no,yes) (LSB) (MSB) New A3 Indicator = [0,1] (exist,new)
2 3
4 j j+1 j+2 j+3 j+4 j+5 k
k+1 k+2 1 2 3 4 5 6
p p+1 p+2
56
T_Add (low order) = [00-11]
Drop Pilot Threshold (T_Drop) = [000000-111111] Drop Timer Value (T_TDrop) = [0H-FH] Reserved = [0000]
p+3 p+4 p+5 p+6 p+7 p+8 p+9
Compare Threshold (T_Comp) = [0H-FH] Neighbor Max Age (Nghbor_Max_AGE) = [0H-FH] Reserved = [00] Reserved = [00] Reserved = [00]
SOFT_SLOPE = [00 0000 - 11 1111] ADD_INTERCEPT = [00 0000 - 11 1111] DROP_INTERCEPT = [00 0000 - 11 1111] Target BS P_REV = [00H FFH]
} Extended Handoff Direction Parameters Length of Channel Element ID = <variable> (MSB) Channel Element ID = <any value> (LSB) Length of A3 From ID = [02H] (MSB) A3 From ID = <any value> (LSB) Length of A3 To ID = [02H] (MSB) A3 To ID = <any value> (LSB) }Abis Connect Information (MSB) Abis From ID: Abis Element Identifier = [71H] 1 1 2 (LSB) Manufacturers Specific Records : Length = [variable] Manufacturer ID = [00H FFH] Manufacturers specific information Abis Element Identifier = [70H] 3 1 2 3 4 n q q+1 r r+1 r+2 r+3 r+4 r+5 r+6
Length of Abis From ID = [02H] Abis From ID = <any value>
1 2 3 4
57
6.1.6
Abis-BTS Setup Ack

This message is sent from BTS to BSC to acknowledge the Abis -BTS Setup.
Information Element Message Type Call Connection Reference Abis Connect Information Abis From ID Abis To ID Manufacturers Specific Records
Section Reference 7.2 7.10 7.20 7.21 7.22 7.7
Element Direction BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC
Type M M O Oa Ob O
1 2 3 4 5 6 7
7 6
a. This element is optionally included by the BTS. If included, the value shall be saved and used by the BSC in subsequent Abis message for this call association. b. This element is required if an Abis From ID value was included in the corresponding Abis -BTS Setup message
Octet 1 1 2 3
(MSB) (MSB) (MSB)
Length = [08H] Market ID = <any value> (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> (LSB) Abis Connect Information{1+: A3/A7 Element Identifier = [1BH]
4 5 6 7 8 9 10 1 2
Length = <variable> Reserved = [000] Physical Channel Type = [0H - IS-95 Fundamental Channel, 1H Fundamental Channel (FCH), 2H Supplemental Channel (SCH)], Length of Cell Info Record = <variable> Cell Info Record {1+: New A3 Indicator = [0,1] (exist,new)
58
Cell Identification Discriminator = [07H] (MSB) MSCID = <any value> (LSB) (MSB) (LSB) Reserved = [000] QoF Mask = [00, 01, 10, 11] Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) New Cell Indicator = [0,1] (old, new) Pilot_PN = <any value> Code Channel = [00H - FFH] } Cell Info Record Length of Traffic Circuit ID = [05H] Traffic Circuit ID {1: Length of Traffic Circuit Identifier = [02H] (MSB) Traffic Circuit Identifier = <any value> (LSB) Length of Traffic Connection Identifier = [01H] Traffic Connection Identifier = [00H-FFH] (AAL2 CID) } Traffic Circuit ID Extended Handoff Direction Parameters Field Length = [09H] Extended Handoff Direction Parameters {1+: Search Window A Size (Srch_Win_A) = [0H-FH] Search Window R Size (Srch_Win_R) = [0H-FH] T_Add (low order) = [00-11] Compare Threshold (T_Comp) = [0H-FH] Neighbor Max Age (Nghbor_Max_AGE) = [0H-FH] Reserved = [00] Reserved = [00] SOFT_SLOPE = [00 0000 - 11 1111] ADD_INTERCEPT = [00 0000 - 11 1111] Drop Timer Value (T_TDrop) = [0H-FH] Reserved = [0000] Search Window N Size (Srch_Win_N) = [0H-FH] Add Pilot Threshold (T_Add) high order = [0H-FH] PWR_ Comb _Ind = [0,1] (no,yes) (LSB) (MSB)
j j+1 j+2 j+3 j+4 j+5 k
k+1 k+2 1 2 3 4 5 6
p p+1 p+2 p+3 p+4 p+5 p+6 p+7
Drop Pilot Threshold (T_Drop) = [000000-111111]
59
Reserved = [00]
DROP_INTERCEPT = [00 0000 - 11 1111] Target BS P_REV = [00H FFH]
p+8 p+9
} Extended Handoff Direction Parameters Length of Channel Element ID = <variable> (MSB) Channel Element ID = <any value> (LSB) Length of A3 From ID = [02H] (MSB) A3 From ID = <any value> (LSB) Length of A3 To ID = [02H] (MSB) A3 To ID = <any value> (LSB) }Abis Connect Information (MSB) (MSB) Abis From ID: Abis Element Identifier = [71H] 1 1 2 (LSB) Abis To ID: Abis Element Identifier = [82H] 3 1 1 2 (LSB) Manufacturers Specific Records : Length = [variable] Manufacturer ID = [00H FFH] Manufacturers specific information Abis Element Identifier = [70H] 3 1 2 3 4 n q q+1 r r+1 r+2 r+3 r+4 r+5 r+6
Length of Abis From ID = [02H] Abis From ID = <any value>
Length of Abis To ID = [02H] Abis To ID = <any value>
1 2 3 4 5
6.1.7
Abis-BTS Release
This message is sent from BSC to BTS to instruct the BTS to release the associated dedicated resource.
Information Element Message Type
Section Reference 7.2
Element Direction BSC -> BTS M
Type
60
Call Connection Reference Manufacturers Specific Records
7.10 7.7
BSC -> BTS BSC -> BTS
M O
1 2
7 The following table shows the bitmap layout for the Abis -BTS Release message: 6 5 4 3 2 1 0 Octet (MSB) (MSB) (MSB) Call Connection Reference = <any value> (LSB) Manufacturers Specific Records : Length = [variable] Manufacturer ID = [00H FFH] Manufacturers specific information Abis Element Identifier = [70H] Message Type = [82H] A1 Element Identifier = [3FH] 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) 4 5 6 7 8 9 10 1 2 3 4 n
Length = [08H] Market ID = <any value>
3 4 5 6
Information Element Message Type Call Connection Reference Manufacturers Specific Records Section Reference 7.2 7.10 7.7 Element Direction BSC -> BTS BSC -> BTS BSC -> BTS Type M M O
6.1.8
Abis-BTS Release Ack

This message is sent from the BSC to the BTS to acknowledge the Abis -BTS Release
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
(MSB) (MSB) (MSB)
1 1 2 3 (LSB) 4 5 (LSB) 6 7 8 9 (LSB) 10 1 2 3 4 n
Length = [08H] Market ID = <any value> Generating Entity ID = <any value>
Call Connection Reference = <any value>
1 2 3 4 5 6 7 8 9 10
Information Element Message Type Call Connection Reference Band Class Downlink Radio Environment CDMA Serving One Way Delay Privacy Info Correlation ID Section Reference 7.2 7.10 7.11 7.23 7.24 7.12 7.3 Element Direction BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS M O O O O O
g
6.1.9
Abis-Burst Request
This Abis interface message is sent from the BSC to the BTS to request the reservation of resources in support of a traffic burst.
Type
62
SDU ID Mobile Identity (IMSI) Mobile Identity (ESN) Cell Identifier List Forward Burst Radio Info Reverse Burst Radio Info Abis To ID
7.14 7.4 7.4 7.13 7.25 7.26 7.22 a.
BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS
O O O O O O O
b c c d e f
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
If this element is omitted, the target BS shall send all Abis signaling messages related to the call to the same address as is used to reply to this A7 message. Optionally included by the source BS. If included, the value shall be saved and used by the target BS on Abis signaling messages. This element may be included for OA&M purposes. The list of cell identifiers shall be assumed by the target BS to be in priority order with the highest priority cell listed first. This element is only included when forward link radio resources are to be allocated to the burst. This element is only included when reverse link radio resources are to be allocated to the burst. If this element is included in this message, its value shall be returned in the Abis -Burst Response message and used in the Abis -Burst Commit message. This element is required if an Abis From ID value was included in an Abis -BTS Setup Ack message previously received from the BS for this call association.
b.
c. d.
e.
f.
g.
h.
63
1
7 (MSB) (MSB) (MSB)
The following table shows the bitmap layout for the Abis -Burst Request message: 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) Call Connection Reference = <any value> (LSB) Reserved = [000] Downlink Radio Environment: Length = <variable> Number of Cells = <variable> Cell Identification Discriminator = [07H] Downlink Radio Environment {1+: (MSB) MSCID = <any value> (LSB) (MSB) (LSB) Reserved = [00] (MSB) } Downlink Radio Environment -- Continued on next page -Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) Downlink Signal Strength Raw = [000000] (ignored) CDMA Target One Way Delay (LSB) j j+1 j+2 j+3 j+4 k k+1 k+2 Band Class: A1 Element Identifier = [5DH] Length = [01H] Band Class = [00001] (PCS) A1 Element Identifier = [29H] 4 5 6 7 8 9 10 1 2 3 1 2 3 4
64
1
-- Continued from previous page - CDMA Serving One Way Delay: Length = [08H] Cell Identification Discriminator = [ 07H] (MSB) MSCID = <any value> (LSB) (MSB) (LSB) (MSB) Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) (LSB) Privacy Info: Abis Element Identifier = [1AH] CDMA Serving One Way Delay = [0000H-FFFFH] (x100ns) A1 Element Identifier = [0CH] 1 2 3 4 5 6 7 8 9 10 1 2 Status = [0,1] Available = [0,1] j+1 j+2 (LSB) } Privacy Mask Information k j
Length = <variable> Privacy Mask Information {1+: Reserved = [0] (MSB) Privacy Mask Type = [00001,00010] (public, private) Privacy Mask Length = <variable> Privacy Mask = <any value>
(MSB)
Correlation ID:
1 2 3 4 5 (LSB) 6
Length = [04H] Correlation Value = <any value>
65
-- Continued on next page --- Continued from previous page - (MSB) SDU ID: A1 Element Identifier = [4CH] Length = [01H to 06H] SDU ID = <any value> (LSB) Mobile Identity (IMSI): A1 Element Identifier = [0DH] Odd/even Indicator = [1,0] Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4 Identity Digit N = [0H-9H] (BCD) Identity Digit N+2 = [0H-9H] (BCD) A1 Element Identifier = [0DH] Odd/even Indicator = [0] (MSB) ESN = <any value> (LSB) Cell Identifier List: A1 Element Identifier = [1AH] 4 5 6 7 1 2 3 J MSCID = <any value> (LSB) (MSB) (LSB) } Cell Identification -- Continued on next page -Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) j+1 j+2 j+3 j+4 Type of Identity = [101] (ESN) N n+1 1 2 3 Type of Identity = [110] (IMSI) 1 2 3 M 1 2 3
Length = <variable> Cell Discriminator Type = [07H] Cell Identification{1+: (MSB)
66
1
-- Continued from previous page - Coding Indicator = [00, 01] Forward Burst Radio Info: Reserved = [0] Abis Element Identifier = [11H] Forward Code Channel Index (high part) = [000 111] Forward Code Channel Index (low part) = [00H FFH] Pilot PN Code (low part) = [00H FFH] Pilot PN Code (high part) [0,1] Reserved = [000] Reserved = [0] Coding Indicator = [00, 01] Reserved = [0000] Reserved = [0] (MSB) Start Time Unit = [000 111] Abis To ID: Reverse Supplemental Channel Rate = [0000 1111] 5 6 1 2 3 (LSB) 4 Reverse Supplemental Channel Duration = [0000 1111] Abis Element Identifier = [72H] Length = [02H] Abis To ID = <any value> 4 Start Time Unit = [000 111] Reverse Burst Radio Info: Forward Supplemental Channel Start Time = [0 0000 1 1111] Forward Supplemental Channel Duration = [0000 1111] Abis Element Identifier = [12H] Reserved = [00 0000] 1 2 3 8 7 Reserved = [000] Forward Supplemental Channel Rate = [0000 1111] 4 5 6 1 2 3
Length = [06H] QOF Mask = [00 11]
Length = [04H]
Reverse Supplemental Channel Start Time = [00H FFH]
67
1 2 3 4 5 6 7 9 10
Information Element Message Type Call Connection Reference Correlation ID Cell Identifier List (Committed) Cell Identifier List (Uncommitted) Forward Burst Radio Info Reverse Burst Radio Info Abis To ID Section Reference 7.2 7.10 7.3 7.13 7.13 7.25 7.26 7.22 a. Element Direction BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC M O O O O
a d e b c
6.1.10
Abis-Burst Response
This Abis interface message is sent from the BTS to the BSC to respond to a request for reservation of resources to support a traffic burst. Note that one or more Abis -Burst Response messages may be used to respond to a single Abis -Burst Request message. A result (committed or uncommitted) must be provided for all cells in the Abis -Burst Request message. Each Abis -Burst Response message includes at most one committed cell.
Type
O O O
11 12 13 14 15 16 17 18 19 20 21 22 23 24
If this element was included in the Abis -Burst Request message, the value shall be returned in this message. This element is only included when this message includes information about forward link radio resources that have been reserved at the cell indicated in the Cell Identifier List (Committed) element. This element is only included when this message includes information about reverse link radio resources that have been reserved at the cell indicated in the Cell Identifier List (Committed) element. This element is only included when this message includes information about a cell with radio resources reserved for the forward and/or reverse burst indicated in the Forward and/or Reverse Burst Radio Info element. This element is only included when this message includes one or more requested cells that are not being reserved. The allowable cause values
b.
c.
d.
e.
68
1 2 3 4 5 6 7 8 9
f.
are: OAM&P intervention, Equipment failure, No radio resource available, BS not equipped, Ciphering algorithm not supported, Private Long Code not available or not supported, Requested MUX option or rates not available, Requested privacy configuration not available. This element is required if an Abis From ID value was included in an Abis -BTS Setup message previously received from the BSC for this call association.
69
The following table shows the bitmap layout for the Abis-Burst Response message:
7 (MSB) (MSB) (MSB) Call Connection Reference = <any value> (LSB) (MSB) Correlation Value = <any value> (LSB) Cell Identifier List (committed): Length = <variable> Cell Identification Discriminator = [07H] Cell Identification {1+: (MSB) MSCID = <any value> (LSB) (MSB) (LSB) } Cell Identification Cell Identifier List (uncommitted): Length = <variable> Cell Identification Discriminator = [07H] -- Continued on next page -A1 Element Identifier = [1AH] 1 2 3 Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) j j+1 j+2 j+3 j+4 A1 Element Identifier = [1AH] Correlation ID: Abis Element Identifier = [13H] 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) 4 5 6 7 8 9 10 1 2 3 4 5 6 1 2 3
Length = [04H]
70
1
-- Continued from previous page -Cell Identification {1+: (MSB) MSCID = <any value> (LSB) (MSB) (LSB) } Cell Identification Coding Indicator = [00, 01] Forward Burst Radio Info: Reserved = [0] Abis Element Identifier = [11H] Forward Code Channel Index (high part) = [000 111] Forward Code Channel Index (low part) = [00H FFH] Pilot PN Code (low part) = [00H FFH] Pilot PN Code (high part) [0,1] Reserved = [000] Reserved = [0] Coding Indicator = [00, 01] Reserved = [0000] Reserved = [0] (MSB) Start Time Unit = [000 111] Abis To ID: Reverse Supplemental Channel Rate = [0000 1111] 5 6 1 2 3 (LSB) 4 Reverse Supplemental Channel Duration = [0000 1111] Abis Element Identifier = [72H] Length = [02H] Abis To ID = <any value> 4 Start Time Unit = [000 111] Reverse Burst Radio Info: Forward Supplemental Channel Start Time = [0 0000 1 1111] Forward Supplemental Channel Duration = [0000 1111] Abis Element Identifier = [12H] Reserved = [00 0000] 1 2 3 8 7 Reserved = [000] Forward Supplemental Channel Rate = [0000 1111] 4 5 6 1 2 3 Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) j j+1 j+2 j+3 j+4
Length = [04H]
71
1 2 3 4 5 6 7 Abis
6.1.11
Abis-Burst Commit
This Abis interface message is sent from the BSC to the BTS to commit a set of resources that had been reserved to support a traffic burst.
Information Element Message Type Call Connection Reference Correlation ID Cell Identifier List (Forward) Cell Identifier List (Reverse) Forward Burst Radio Info Reverse Burst Radio Info IS-2000 Forward Power Control Mode IS-2000 FPC Gain Ratio Info Abis To ID
Section Reference 7.2 7.10 7.3 7.13 7.13 7.25 7.26 7.27 7.28 7.22 a.
Element Direction BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS BSC -> BTS M O O
a
Type
Ob Ob Oc Od Oe Of O
g
8 9 10 11 12 13 14 15 16 17 18 19 20
Optionally included by the source BS. If included, the value shall be saved and used by the target BS on Abis signaling messages. The length field of this element shall be set to 0 if no resources are to be allocated in the indicated direction. This element is only included when forward link radio resources are to be allocated to the burst. This element is only included when reverse link radio resources are to be allocated to the burst. This element shall be included when supporting a secondary power control subchannel. It provides information used for forward gain equalization for the SCH. This element shall be included when supporting a secondary power control subchannel for the SCH. The FPC_MODE value shall go into
b.
c.
d.
f.
e.
72
1 2 3 4 5 6
g.
effect at the earlier of the burst start times indicated in the Forward Burst Radio Info and/or Reverse Burst Radio Info element. This element is required if an Abis From ID value was included in an Abis BTS Setup Ack message previously received from the BS for this call association.
73
The following table shows the bitmap layout for the Abis-Burst Commit message:
7 (MSB) (MSB) (MSB) Call Connection Reference = <any value> (LSB) (MSB) Correlation Value = <any value> (LSB) Cell Identifier List (Forward): Length = <variable> Cell Identification Discriminator = [07H] Cell Identification {1+: (MSB) MSCID = <any value> (LSB) (MSB) (LSB) } Cell Identification Cell Identifier List (Reverse): Length = <variable> Cell Identification Discriminator = [07H] -- Continued on next page -A1 Element Identifier = [1AH] 1 2 3 Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) j j+1 j+2 j+3 j+4 A1 Element Identifier = [1AH] Correlation ID: Abis Element Identifier = [13H] 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) 4 5 6 7 8 9 10 1 2 3 4 5 6 1 2 3
Length = [04H]
74
1
-- Continued from previous page -Cell Identification {1+: (MSB) MSCID = <any value> (LSB) (MSB) (LSB) } Cell Identification Coding Indicator = [00, 01] Forward Burst Radio Info: Reserved = [0] Abis Element Identifier = [11H] Forward Code Channel Index (high part) = [000 111] Forward Code Channel Index (low part) = [00H FFH] Pilot PN Code (low part) = [00H FFH] Pilot PN Code (high part) [0,1] Reserved = [000] Reserved = [0] Coding Indicator = [00, 01] Reserved = [0000] Reserved = [0] Start Time Unit = [000 111] IS-2000 Forward Power Control Mode: [14H] Length = [02H] Reserved = [0000 0] ACTION_TIME = [00H] (ignored) FPC_MODE = [000 011] Reverse Supplemental Channel Rate = [0000 1111] 5 6 1 2 3 4 Reverse Supplemental Channel Duration = [0000 1111] Abis Element Identifier = 4 Start Time Unit = [000 111] Reverse Burst Radio Info: Forward Supplemental Channel Start Time = [0 0000 1 1111] Forward Supplemental Channel Duration = [0000 1111] Abis Element Identifier = [12H] Reserved = [00 0000] 1 2 3 8 7 Reserved = [000] Forward Supplemental Channel Rate = [0000 1111] 4 5 6 1 2 3 Cell = [001H-FFFH] Sector = [0H-FH] (0H = Omni) j j+1 j+2 j+3 j+4
Length = [04H]
75
-- Continued on next page --- Continued from previous page - IS-2000 FPC Gain Ratio Info: Length = [08H] Initial Gain Ratio = [00H FFH] Reser ved = [0] Gain Adjust Step Size = [0H FH] Count of Gain Ratio Pairs = [011] Abis Element Identifier = [15H] 1 2 3 4
Min Gain Ratio 1 = [00H FFH] Max Gain Ratio 1 = [00H FFH] Min Gain Ratio 2 = [00H FFH] Max Gain Ratio 2 = [00H FFH] Min Gain Ratio 3 = [00H FFH] Max Gain Ratio 3 = [00H FFH] (MSB) Abis To ID: Abis Element Identifier = [72H] Length = [02H] Abis To ID = <any value> (LSB)
5 6 7 8 9 10 1 2 3 4
1 2 3 4 5 6 7 8 9 10 11 12 13 14
6.1.12
Abis-Connect
This message is used the same format as the A3-Connect message. Refer to section 6.1.9.1 "A3-Connect" , 3G-IOS v4.0.0
6.1.13
Abis-Connect Ack
This message is used the same format as the A3-Connect Ack message. Refer to section 6.1.9.2 "A3-Connect Ack" , 3G-IOS v4.0.0
6.1.14
Abis-Remove
This message is used the same format as the A3-Remove message. Refer to section 6.1.9.3 "A3-Remove", 3G-IOS v4.0.0
6.1.15
Abis-Remove Ack
This message is used the same format as the A3-Remove Ack message. Refer to section 6.1.9.4 "A3-Remove Ack", 3G-IOS v4.0.0
76
1 2 3 4 5 6 7 8 9 10 11 12
6.1.16
Abis-IS-2000 FCH Fwd

This message is used the same format as the A3-IS-2000 FCH Forward message. Refer to section 6.1.9.9 "A3-IS-2000 FCH Forward", 3G-IOS v4.0.0
6.1.17
Abis-IS-2000 FCH Rvs

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

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

This message is sent from the BTS to the BSC to request deallocation resources..
Information Element Message Type Call Connection Reference Cause Manufacturers Specific Records
Section Reference 7.2 7.10 7.9 7.7
Element Direction BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC
Type M M O O
13 14 The following table shows the bitmap layout for the Abis-BTS Release Request message:
7 (MSB) (MSB) (MSB) Call Connection Reference = <any value> (LSB) Cause: A1 Element Identifier = [04H] 77 6 5 4 3 2 1 0 Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) 4 5 6 7 8 9 10 1
Length = [01H] ext = [0] Cause Value = [07H (OAM&P intervention), 20H (equipment failure)] Manufacturers Specific Records : Length = [variable] Manufacturer ID = [00H FFH] Manufacturers specific information Abis Element Identifier = [70H]
2 3
1 2 3 4 n
1 2 3 4 5 6 7 8 9 10 11 12 13
6.1.20
Abis-IS-2000 SCH Fwd

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

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

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

This message is used the same format as the A3-IS-2000 DCCH Reverse message. Refer to section 6.1.9.14 "A3-IS-2000 DCCH Forward", 3G-IOS v4.0.0
78
1 2 3 4 5 6 7 8
7. Information Element Definitions

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

Element Name (unused value available) (unused value available) Service Option Cause (unused value available) (unused value available) Frame Selector Info Quality of Service Parameters Abis Cell Info (Note: This Information Element is same with A7 Cell Info IE in 3GPP2 A.S0001.) (unused value available) CDMA Serving One-Way Delay Mobile Identity (unused value available) Forward Burst Radio Info Reverse Burst Radio Info Correlation ID (unused value available) IS-2000 Power Control Mode (unused value available) Cell Identifier List (unused value available) Privacy Info (unused value available) 09-0BH 0CH 0DH 0E-10H 11H 12H 13H 14H 15H 17-19H 1AH 1B-1CH 1DH 1EH-20H Abis,A7 6.2.2.143 Abis,A1, A7 6.2.2.21 Abis,A3 6.2.2.64 Abis,A7 Abis,A7 Abis,A3, A7 6.2.2.56 6.2.2.57 6.2.2.108 Abis,A1, A7 Abis,A1, A7 6.2.2.79 6.2.2.16 Identifier 01H 02H 03H 04H 05H 06H FFS FFS 08H Abis,A7 Abis,A1 Abis 6.2.2.14 6.2.2.54 6.2.2.24 Abis,A1 Abis,A1 6.2.2.96 6.2.2.125 Interface(s) Reference
79
Air Interface Message (unused value available) Layer 2 Ack Request/Results (unused value available) Downlink Radio Environment IS-2000 Power Control Info (unused value available) IS-2000 FPC Gain Ratio Info (unused value available) Call Connection Reference (unused value available) SDU ID PACA Timestamp Band Class Manufactures Specific Records Abis From ID Abis To ID Unused Value?
21H 22H 23H 24H 29H FFS 14H 15H 2C-2DH 3FH 40-48H 4CH 4EH 5DH 70H 71H 72H All other values are reserved.
Abis,A7 Abis,A7 Abis,A1, A7 A7 Abis,A7 Abis,A1, A3, A7
6.2.2.152 6.2.2.153 6.2.2.25 6.2.2.176 6.2.2.178 6.2.2.98
Abis,A3, A7 Abis,A1 Abis,A1, A7 Abis Abis Abis
6.2.2.91 6.2.2.149 6.2.2.106
1 2 3 4 5
7 The Message Type element is used to indicate the type of a message on the Abis interfaces. Element Format: 6 5 4 3 2 1 0 Octet 1
7.2
Message Type
Message Type
6 7
Table 7 - 2 Abis Message Type Values

Message Type Value 01H 02H 03H 04H Section Reference
Message Name Abis -Connect Abis -Connect Ack Abis -Remove Abis -Remove Ack
Interface Abis Signaling Abis Signaling Abis Signaling Abis Signaling
80
(unused value available) Abis -IS-2000 FCH Fwd Abis -IS-2000 FCH Rvs Abis -Traffic Channel Status Abis -IS-2000 DCCH Fwd Abis -IS-2000 DCCH Rvs Abis -IS-2000 SCH Fwd Abis -IS-2000 SCH Rvs (unused value available) Abis -BTS Setup Abis -BTS Setup Ack Abis -BTS Release Abis -BTS Release Ack Abis -BTS Release Request (unused value available) Abis -PCH Msg. Transfer Abis -PCH Msg. Transfer Ack Abis -ACH Msg. Transfer Abis -ACH Msg.Transfer Ack Abis -Burst Request Abis -Burst Response Abis -Burst Commit
05H-0AH 0BH 0CH 0DH 0EH 0FH 10H 11H 12H-7FH 80H 81H 82H 83H 84H 85H-8BH 8CH 8DH 8EH 8FH 90H 91H 92H Abis Signaling Abis Signaling Abis Signaling Abis Signaling Abis Signaling Abis Signaling Abis Signaling 6.1.3 6.1.4 6.1.1 6.1.2 6.1.9 6.1.10 6.1.11 Abis Signaling Abis Signaling Abis Signaling Abis Signaling Abis Signaling 6.1.5 6.1.6 6.1.7 6.1.8 6.1.19 Abis Traffic Abis Traffic Abis Traffic Abis Traffic Abis Traffic Abis Traffic Abis Traffic 6.1.16 6.1.17 6.1.18 6.1.22 6.1.23 6.1.20 6.1.21
1 2 3 4 5 6 7 8
All other values are reserved.
7.3
Correlation ID
Refer to section 6.2.2.108, 3G-IOS v4.0.0.
7.4
Mobile Identity
Refer to section 6.2.2.16, 3G-IOS v4.0.0).
7.5
Cell Identifier
81
1 2 3 4 5 6
7.6
Air Interface Message

Refer to section 6.2.2.152, 3G-IOS v4.0.0
7.7
Manufacturers Specific Records

This information element is used to send manufacturers specific records on the Abis interface.
4 Length
Octet 1 2 3 4 n
Abis Element Identifier Manufacturer ID Manufacturers specific information
7 8 9 10 11 12 13 14 15 16 17 18 19 20
Length
This field shall be set to the length of this element in octets following the Length field. This field identifies manufacturer that creates this information element. The value in this field is FFS.
Manufacturer ID
Manufacturers specific information This field includes manufacturers specific information. The content in this field is left to the BTS/BSC manufacturer.
7.8
Layer 2 Ack Request/Results

7.9
Cause
82
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
7.10
Call Connection Reference

7.11
Band Class
7.12
Privacy Info
7.13
Cell Identifier List

Refer to section 6.2.2.21, 3G IOS v4.0.0.
7.14
SDU-ID
7.15
Physical Channel Info

7.16
Abis Cell Info

7.17
Service Option
7.18
PACA Timestamp
83
1 2 3 4 5 6 7 8 9 10 11 12
7.19
Quality of Service Parameters

7.20
Abis Connect Information

7.21
Abis From ID
This element contains an identifier chosen by the BSC for its own use in quickly processing Abis signaling messages received from the BTS. For example, it may be used to identify the resources supporting the call association that are internal to the BSC. If an Abis From ID is supplied by this BSC, then the BTS includes this in the Abis To ID element in subsequent Abis messages to this BSC.
4 Length
Octet 1 2 3
Abis Element Identifier (MSB) Abis From ID (LSB)
13 14 15 16 17 18 19
Length:
This field indicates the number of octets in this element following the Length field. The maximum value in this version of this specification is 2 octets. This field has variable length. The actual length is indicated in the Length field and is dependent upon the particular implementation. In this version of this standard, this value shall be no more than 2 octets long.
Abis From ID:
20 21 22 23 24 25
7.22
Abis To ID
This element contains an identifier chosen by the BSC for its own use in quickly processing Abis signaling messages. If an Abis From ID was supplied by the BSC, then the BTS includes this value in the Abis To ID element in subsequent Abis messages to the BSC.
Octet
84
Abis Element Identifier Length (MSB) Abis To ID (LSB)
1 2 3
1 2 3 4 5 6 7
Length:
This field indicates the number of octets in this element following the Length field. The maximum value in this version of this specification is 2 octets. This field has variable length. The actual length is indicated in the Length field and is dependent upon the particular implementation. In this version of this standard, this value shall be no more than 2 octets long.
Abis To ID:
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
7.23
Downlink Radio Enviroment

7.24
CDMA Serving One Way Delay

7.25
Forward Burst Radio Info

7.26
Reverse Burst Radio Info

7.27
IS-2000 Forward Power Control Mode

85
1 2 3 4 5 6
7.28
IS-2000 FPC Gain Ratio Info

7.29
Cell Identifier List

86

Abis CDMA2000

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Abis CDMA2000

Uploaded by

Copyright:

Available Formats

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))

IP Network Protocol Usage..................................................................................................................17

Scope of the document

PRM QoS RAN RN RRC SCCM SCM SDU

Network Reference Model and Interfaces

Fig.4-1. Network Reference Model for Abis interface

Air Interface MS BTS

Table 4-1 Abis interface description

- call release - Handoff

Support of user traffic connections to a frame selector function

Support of paging channel messaging

Support of Access channel messaging

Support of radio functions

Support of broadcast system information functions

Physical Layer Specification (Layer 1)

T1 digital transmission system interfaces. Each 1.544 Mbits/s interface

Use of ATM (Layer 2)

ATM Adaptation Layer

5 AAL, August 1996. 12

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

Type 2 Specification, September 1997. 13

Network and Transport Protocols

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

IP Network Protocol Usage

Mobile Originating Call

a Complete L3 Info: CM Service Req. T303 Assignment Request b c d e f

Abis-IS-2000 FCH Rvs (MS Ack Order)

Fig. 5-1 Mobile Originating Call

Mobile Terminated Call

BSC Paging Request

General Page Page BS Ack Order

Fig. 5-2 Mobile Terminated Call

Call Clearing initiated by MS

Fig. 5-3 Call Clearing initiated by MS

Call Clearing initiated by BS/MSC

Clear Command Abis-IS-2000 FCH Fwd (Release Order)

Abis-IS-2000 FCH Rvs (Release Order) T315 Abis-BTS Release Abis-Remove

Abis-Remove Ack Abis-BTS Release Ack

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

Call Clearing initiated by BTS

Clear Command Release Order Abis-IS-2000 FCH Fwd (Release Order)

Abis-IS-2000 FCH Rvs (Release Order) ) T315 Abis-BTS Release Abis-Remove

Abis-Remove Ack Abis-BTS Release ACK Clear Complete

Fig. 5-5 Call Clearing initiated by BTS

Soft/Softer Handoff (Intra-BTS)

Ab Abis -BTS Setup Ack Extended/General/Universal Handoff Direction Message

A3 Abis -IS-2000 FCH Fwd

A3 Abis-IS-2000 FCH Rvs

Handoff Completion Message

A3 Abis-IS-2000 FCH Rvs

A3 Abis -IS-2000 FCH Fwd

Fig.5-6 Soft/Softer Handoff (Intra-BTS)

Soft/Softer Handoff (Inter-BTS)

A3 Abis -IS-2000 FCH Rvs

Handoff Completion Message

A3 Abis -IS-2000 FCH Rvs

A3 Abis-IS-2000 FCH Fwd

Fig.5-7 Soft/Softer Handoff (Inter-BTS)

SMS Delivery on the Paging channel

Data Burst Message