3GPP2 A.R0003 Version 1.0.

0 Date: December 17, 1999

Abis interface Technical Report for cdma2000 Spread Spectrum Systems (A.R0003 : Abis Technical Report)

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 December 1999

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

1. 2. 3.

INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 GLOSSARY AND DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1 3.2 GLOSSARY .................................................................................................................... 3 DEFINITIONS ................................................................................................................. 3

4.

FUNCTIONAL ARCHITECTURE AND INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1 4.2 4.3 4.4 4.5 4.6 SUPPORT OF USER TRAFFIC CONNECTIONS TO A FRAME SELECTOR FUNCTION............................... 6 SUPPORT OF PAGING CHANNEL MESSAGING .......................................................................... 6 SUPPORT OF A CCESS CHANNEL MESSAGING.......................................................................... 7 SUPPORT OF RADIO FUNCTIONS.......................................................................................... 7 SUPPORT OF BROADCAST SYSTEM INFORMATION FUNCTIONS.................................................... 7 TRANSPORT PROTOCOL ................................................................................................... 8

5.

CALL PROCESSING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.1 NOTES FOR ALL FLOWS.................................................................................................... 9 5.2 M OBILE ORIGINATING CALL............................................................................................10 5.3 M OBILE TERMINATED CALL ............................................................................................12 5.4 CALL CLEARING ...........................................................................................................16 5.4.1 Call Clearing initiated by MS...................................................................................16 5.4.2 Call Clearing initiated by BS/MSC............................................................................18 5.4.3 Call Clearing initiated by BTS............................................................................19 5.5 HANDOFF ....................................................................................................................21 5.6 SMS DELIVERY ............................................................................................................23 5.6.1 SMS Delivery on the Paging channel .........................................................................23 5.6.2 SMS Delivery on the Access channel .........................................................................24 5.6.3 SMS Delivery on the Traffic channel to MS.................................................................25 5.6.4 SMS Delivery on the Traffic channel from MS..............................................................26

6.

AB INTERFACE MESSAGE FORMATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 7 6.1 A B INTERFACE MESSAGE .................................................................................................27 6.1.1 Ab-ACH Msg Transfer ............................................................................................27 6.1.2 Ab-ACH Msg Transfer Ack ......................................................................................30 6.1.3 Ab-PCH Msg Transfer ............................................................................................31 6.1.4 Ab-PCH Msg Transfer Ack ......................................................................................33 6.1.5 Ab-BTS Setup........................................................................................................35 6.1.6 Ab-BTS Release.....................................................................................................39 6.1.7 Ab-Connect ..........................................................................................................40 6.1.8 Ab-Connect Ack ....................................................................................................40 6.1.9 Ab-Remove ...........................................................................................................40 6.1.10 Ab-Remove Ack .....................................................................................................40

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

6.1.11 6.1.12 6.1.13 6.1.14

Ab-IS-2000 FCH Fwd.............................................................................................40 Ab-IS-2000 FCH Rvs ..............................................................................................40 Ab-Traffic Channel Status .......................................................................................40 Ab-BTS Release Request .........................................................................................40

INFORMATION ELEMENT DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.11 7.12 7.13 7.14 7.15 7.16 7.17 7.18 M ESSAGE TYPE ............................................................................................................42 CORRELATION ID ..........................................................................................................43 M OBILE IDENTITY.........................................................................................................43 CELL IDENTIFIER ..........................................................................................................43 A IR INTERFACE M ESSAGE ...............................................................................................44 M ANUFACTURERS SPECIFIC RECORDS ..............................................................................44 LAYER 2 A CK REQUEST /RESULTS.....................................................................................44 CAUSE ........................................................................................................................44 CALL CONNECTION REFERENCE .......................................................................................45 BAND CLASS ................................................................................................................45 PRIVACY INFO ..............................................................................................................45 A3 SIGNALING A DDRESS ................................................................................................45 SDU-ID ......................................................................................................................45 FRAME SELECTION INFO .................................................................................................45 A7 CELL INFO ..............................................................................................................45 SERVICE OPTION ...........................................................................................................45 PACA TIMESTAMP ........................................................................................................45 QUALITY OF SERVICE PARAMETERS ..................................................................................46

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
3 The A3 interface carries coded user information (voice/data) and signaling information between the SDU function and the channel element component of the BS (BTS). The A3 interface is composed of two parts: signaling and user traffic. The signaling information is carried across a separate logical channel from the user traffic channel, and controls the allocation and use of channels for transporting user traffic. A7 interface:

1.

Introduction
This contribution proposes a technical report on the Ab (between the BSC and BTS) interface for cdma2000 system. The signaling flows and these signals are described.

2.

Objectives
The Ab interface specification achieve providing open and interoperabe system. And A b interface does not disturb coexistence with other Ax intercaces.

3.
3.1

Glossary and Definitions

Glossary
The following is a list of acronyms that are used in the baseline text. 3G-IOS Third Generation InterOperability Spesification ITU International Telecommunications Union MAC Medium Access Control MS Mobile Station QoS Quality of Service RAN Radio Access Network RN Radio Network RRC Radio Resource Control Function SDU Selection/Distribution Unit function

3.2

Definitions
A3 interface:

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

The A7 interface carries signaling information between a source BS and a target BS. Ab interface: [TBD] The Ab interface between the BSC and the BTS is composed of two parts: Ab Signaling Part and Ab Traffic Part. The Ab Signaling Part carries signaling information between the BSC and the BTS. The Ab Traffic Part carries coded user information (voice/data) and signaling information between the BSC (SDU function) and the channel element component of the BTS, like the A3 interface on the 3G-IOS. The Ab Traffic Part is composed of two sub-parts; signaling and user traffic. The signaling information is carried across a separate logical channel from the user traffic channel, and controls the allocation and use of channels for transporting user traffic.

Abis interface:[TBD]The interface consists of the A3 and Ab components.

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

4.

Functional Architecture and interfaces

The 3G-IOS specified several interfaces between the RAN and other Core Network entities. Also, it specified interfaces within the RAN itself such as the A7 and A3 corresponding to the interfaces between the direct BSC to BSC and the SDU to BTS interfaces. The new Ab interface is between the BSC and the BTS.

The Abis interface consists of the A3 and Ab components, however, this contribution provides the specifications for Ab component since A3 part is already specified in the 3G-IOS specification. The Major components of the BSC BTS interface definition for a CDMA system are: 1. Support of user traffic connections to a frame selector function (A3); 2. Support of Paging Channel messaging (Ab); 3. Support of Access Channel messaging (Ab); 4. Support of radio functions (Ab); 5. Support of broadcast system information functions (Ab); 6. Transport and protocol stack for user traffic and signaling;

The OAM&P related information can be transferred in this interfaces and the transport layer for these informations are desiable to match with Ab interface, but they are FFS.

There need much more discussion for the relation ship between Abis interface and Ab, A3, A7 interfaces. And we may need some extended understanding for the network reference model defined in 3G-IOS. With the history of the discussion in the 3GPP2 TSG-A WGB in this document we assume Abis interface would be composed with Ab signaling and Ab traffic interface as a working assumption. And on this working assumption we will study detailed BSC - BTS interface in the mean time. After we complete this interface specification, we will consider whether each signal can be merged into existing interface.

Following figure shows the working assumption.

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

A7 Sig BSC BSC

Ab Traffic

Ab Sig A3 Traffic BTS A3 Sig

Ab Traffic

Ab Sig

BTS

Fig.4 RAN and RAN-CN interfaces (Working Assumption)

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 conections from MS to BTS(s). If multiple connections are used for a single flow of user information, the user traffic connection is said to be in soft handoff. The first step within the network is 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. In both the cdmaOne and cdma2000 systems, 3G-IOS has defined the A3 interface to support connections from the BTS to the SDU function. For details on the A3 interface see the 3G-IOS specification.

35 36 37 38 39 40

4.2

Support of paging channel messaging

When a MS is to be sent a message on a paging channel, the BSC will typically format the majority of that message and then forwarded 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 a paging message from the BTS to the BSC is part of the functionality of the Ab interface. 6

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

An additional requirement of a CDMA systme is that such message may also need to be forwarded between BSCs to be transmitted on a BTS belonging to a BSC other than the BSC that originally creates 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.3

Support of Access channel messaging

When a MS sends a message on a 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 a origination message from BTS to the BSC is part of the functionality of the Ab interface. An additional requirement of a CDMA system is that such message may also need to be forwarded between BSCs to a BSC other than the BSC that owns the BTS that originally recieves 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. Examples of such functions that require BSC-BTS signaling on the Ab interface turning radio rquipment on and off; -Determining available of radio capacity; -Determining radio interface levels; -Determining received and transmitted power levels;

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 administratered through OAM&P functions. A small amount of such system information may be placed information and OAM&P control of a BTS for the same purposes must be defined.

1 2

4.6

Transport Protocol
For further study.

1 2 3 4 5 6 7 Procedures Call origination / termination, etc 8 9 10 11 A1 signaling 3G-IOS V4.0.0 V&V ( Nov. 05, 1999) IS-2000 air signaling IS-2000 Ballot Resolution Version (July, 1999)

5.
5.1

Call Processing
Notes for all flows
In this contribution, we use new messages analysed and defined on previous contribution (3GPP2-AB-19990930-02) . Followings are the reffered text.

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

5.2

Mobile Originating Call

BS MS
Origination

Time Comment

BTS

BSC

MSC

Ab-ACH Msg. Transfer (ORM) Complete L3 Info: CM Service Req. T303 Ab-BTS Setup Ab-Connect Ab-Connect Ack Assignment Request

a b c d e f g h i T10 j k l m

Null Traffic Extended Channel Assignment

Ab-IS-2000 FCH Fwd (Null Data) Ab-IS-2000 FCH Rvs (Idle) Ab-PCH Msg. Transfer (ECAM)

Traffic Channel Preamble Ab-IS-2000 FCH Rvs (T-CH Preamble) BS Ack Order Idle Tch Data Frames MS Ack Order Ab-IS-2000 FCH Fwd (BS Ack Order) Ab-IS-2000 FCH Rvs (Idle) Ab-IS-2000 FCH Rvs (MS Ack Order)

Service Connect (voice) Service Connect Completion

Ab-IS-2000 FCH Fwd (SCM) Ab-IS-2000 FCH Rvs (SCCM) Assignment Complete

n o p

Ring Back Tone (In-band Tone)

Voice Communication

Fig. 5-2 Mobile Originating Call

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 33 34 35 36 37 38 39 40 41 42

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 Ab-ACH Msg Transfer including the Origination message frame in Ab signaling interface. b. The BSC constructs the CM Service Request message, places it in the Complete Layer 3 Information message, sends the message 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 Ab-BTS Setup message to get the resource between BSC and BTS. e. If resourcees are available, BTS responses with Ab-Connect message. f. The BSC sends Ab-Connect Ack message. g. The BSC transmits the Ab-IS-2000 FCH Fwd message including Null Data to let the BTS send Null traffic data toward the MS. Then the BTS begin sending Null Traffic data for synchronizing between the BTS and the MS. h. The BTS sends Ab-IS-2000 FCH Rvs message including Idle data. i. The BSC sends a Ab-PCH Msg Transfer including Extended Channel Assignment message. The BTS sends an Extended Channel Assignmnet message over the paging channel of the radio interface (with the MS address) to initiate the establishment of a radio traffic channel. j. 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-2000 FCH Rvs message. k. Once the BSC acquires the reverse traffic channel, it sends an Ab-IS-2000 FCH Fwd message including a Base Station Acknowledgement Order with layer 2 acknowledgement required , to the MS over the forward traffic channel. l. 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 Ab-IS-2000 FCH Rvs message. m. The MS Ack Order message is sent from MS, and then the BTS transmits it to the BSC with an Ab-IS-2000 FCH Rvs message. n. The BSC then sends the Ab-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. o. On receipt of the Service Connect message, the MS responds with a Service Connect Completion message. Then the BTS transmits it with a n Ab-IS-2000 FCH Rvs message. p. 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.

11

1 2 3 4 5

5.3

Mobile Terminated Call

This section describes the call flow associated with a mobile station call termination in the cdma2000 system. An Ab-PCH Msg Transfer Ack and an Ab-ACH Msg Transfer Ack are not presented in the following figure to simplify the figure, but actually, they would be sent after receipt of Ab-PCH Msg Transfer message or Ab-ACH Msg Transfer message respectively.
MS MSC Paging Request General Page Page Response BS Ack Order Ab-PCH Msg. Transfer (GPM) Ab-ACH Msg. Transfer (PRM) Ab-PCH Msg. Transfer (BS Ack) Assignment Request Ab-BTS Setup Ab-Connect Ab-Connect Ack Null Traffic Extended Channel Assignment TCH Preamble BS Ack Order Idle Tch Data Frames MS Ack Order Service Connect Serv. Con. Completion Alert with Info MS Ack Order Connect Order BS Ack Order Ab-IS-2000 FCH Fwd (Null Data) Ab-IS-2000 FCH Rvs (Idle) Ab-PCH Msg. Transfer (ECAM) Ab-IS-2000 FCH Rvs (Preamble) Ab-IS-2000 FCH Fwd (BS Ack) Ab-IS-2000 FCH Rvs (Idle) Ab-IS-2000 FCH Rvs (MS Ack) Ab-IS-2000 FCH Fwd (SCM) Ab-IS-2000 FCH Rvs (SCCM) Assignment Complete Ab-IS-2000 FCH Fwd (AWIM) Ab-IS-2000 FCH Rvs (MS Ack) Ab-IS-2000 FCH Rvs (Connect Order) Ab-IS-2000 FCH Fwd (BS Ack) Connect Complete L3 Info: Paging Response Time Comment

BTS

BSC

a b c d e f g h i j k l m n o p q r s t u v w x

6 7

Fig. 5-3 Mobile Terminated Call

12

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 BS to initiate a mobile terminated call setup scenario. The BSC constructs an General Page Message (GPM), put the message into an Ab-PCH Msg Transfer Message and sends the AbPCH 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 an Page Response Message (PRM) to the BTS over the access channel. Upon receipt of this message, the BTS put this message into an Ab-ACH Msg Transfer Message and sends it to the BSC. The BS sends the Complete Layer 3 Information message containing the Paging Response message to the MSC. The BS acknowledges the receipt of the PRM from the MS with a Base Station Acknowledgment Order to the MS. This massage is sent by the BSC to the BTS in the Ab-PCH Msg Transfer. The MSC sends an Assignment Request message to request assignment of radio resources. The BSC sends an Ab-BTS Setup message to the BTS to request allocation of radio resources at the BTS. Upon receipt of Ab-BTS Setup message, the BTS allocates radio resources and sends an Ab-Connect message to initiates an Ab connection and to report the result of resource allocation. The BSC replies with a Ab-Connect Ack message to complete the Ab connection. The BSC sends an Ab-IS-2000 FCH Fwd (Null Traffic Data) message to the BTS. The BTS starts sending Null Traffic Data to the mobile station. This allows the mobile station to acquire the FCH (Fundamental channel). Upon receiving the first Ab-IS-2000 FCH Fwd (Null Traffic Data) message, the BTS starts to send Ab-IS-2000 FCH Rvs (Idle frame) message to the BSC.

b.

c.

d.

e.

f.

g.

h.

i.

j.

k.

13

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

l.

The BSC sends an Extended Channel Assignment message to assign the FCH.

m. 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. n. The BSC sends the BS Ack Order to the MS via the BTS in the AbIS-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 Ab-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 Ab-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 Ab-IS-2000 FCH Rvs message containing this message to the BSC. After the radio traffic channel and circuit have both been established, the BS sends the Assignment Complete message to the MSC. The BSC sends Alert with Information Message (AWIM) to the MS to cause ringing at MS. This message is sent by the BSC to BTS in the Ab-IS-2000 FCH Fwd message. The MS acknowledges the reception of the Alert with Information Message by transmitting the MS Ack Order. When the call is answered at the MS, a Connect Order, with acknowledgment required, is transmitted to the BSC via the BTS.

o.

p.

q.

r.

s.

t.

u.

v.

w. The BSC acknowledges the Connect Order with the BS Ack order.

14

1 2 3 4

x.

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.

15

1 2 3 4

5.4

Call Clearing

5.4.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 34

MS
Release Order

BTS

BSC

MSC

Time

Ab-IS-2000 FCH Rvs (Release Order) Clear Request T300 Clear Command

a b c d e

Release Order

Ab-IS-2000 FCH Fwd (Release Order) ) Ab-BTS Release Ab-Remove Ab-Remove Ack

T315

f g

Clear Complete

Fig. 5-4-1 Call Clearing initiated by MS a. The mobile station initiates call clearing by transmitting a Release Order over the reverse traffic channel. In response to the order, BTS sends an Ab-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 Ab-IS-2000 FCH Fwd message containing the Release Order message. The BTS then acknowledges the MS by sending it a Release Order over the forward traffic channel .

b.

c.

d.

16

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

e.

The BSC then sends an Ab-BTS Release message to the BTS. The BTS starts to release the radio resource after sending Ab remove message. The BTS releases the radio resource and sends Ab Remove message to the BSC. In response to the Ab-Remove message from the BTS, BSC sends an Ab-Remove Ack message to the BTS. 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.

f.

g.

h.

17

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

5.4.2
MS

Call Clearing initiated by BS/MSC

BS BTS BSC
Clear Request T300 Clear Command

MSC

Time

Release Order

Ab-IS-2000 FCH Rvs (Release Order) Ab-IS-2000 FCH Fwd (Release Order) ) Ab-BTS Release Ab-Remove

b c

Release Order

T315
e

Ab-Remove Ack

Clear Complete

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

a. In the case of 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 Ab-IS-2000 FCH Fwd containing the Release Order message. The BTS then acknowledges the MS by sending it a Release Order over the forward traffic channel. The mobile station replies a Release Order over the reverse traffic channel. In response to the order, BTS sends a Ab-IS-2000 FCH Reverse containing the Release Order message to the BSC. 18

b.

c.

d.

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

e.

The BSC then sends an Ab-BTS Release message to the BTS. The BTS starts to release the radio resource after sending Ab remove message. The BTS releases the radio resource and sends Ab Remove message to the BSC. In response to the Ab Remove message from the BTS, BSC sends an Ab 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 MSC stops timer T315 upon receipt of the Clear Complete message. The MSC releases the underlying transport connection.

f.

g.

h.

5.4.3
MS

Call Clearing initiated by BTS

BS BTS
Ab-BTS Release Request

BSC
Clear Request

MSC

Time

Release Order

Ab-IS-2000 FCH Rvs (Release Order) Ab-IS-2000 FCH Fwd (Release Order) ) Ab-BTS Release Ab-Remove

T300 Clear Command

b c

Release Order

T315
e

Ab-Remove Ack

Clear Complete

13 14 15 16 17 18

Fig. 5-4-3 Call Clearing initiated by BTS

a. In the case of a radio channel failure between the MS and the BTS, or if the MS is not active, the BTS sends an Ab-BTS Release Request 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

19

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

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 Ab-IS-2000 FCH Fwd containing the Release Order message. The BTS then acknowledges the MS by sending it a Release Order over the forward traffic channel. The mobile station replies a Release Order over the reverse traffic channel. In response to the order, BTS sends a Ab-IS-2000 FCH Rvs containing the Release Order message to the BSC. The BSC then sends an Ab-BTS Release message to the BTS. The BTS starts to release the radio resource after sending Ab remove message. The BTS releases the radio resource and sends Ab Remove message to the BSC. In response to the Ab Remove message from the BTS, BSC sends an Ab 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 MSC stops timer T315 upon receipt of the Clear Complete message. The MSC releases the underlying transport connection.

c.

d.

e.

f.

g.

h.

20

1 2

5.5

Handoff
Source BS M S BTS BSC MSC Target BS BSC BTS

A7-Handoff Request A3-Connect A3-Connect Ack Forward Frames A3-IS-2000 FCH Fwd( Forward Frames) A3-IS-2000FCH Rvs( Idele Frames) A7-Handoff Request Ack Extended/General/Universal Handoff Direction Message MSAck Order Handoff Completion Message BS Ack Order Handoff Performed A3-Traffic Channel Status

Ab-BTS Setup Ab-Connect Ab-Connect Ack Ab-IS-2000-FCH Fwd Ab-IS-2000-FCH Rvs

a b c d e f g h i j k l

Ab-Traffic Channel Status

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

Fig. 5-5 Soft/Softer Handoff

a. The source BS decides that one or more cells at the target BS are needed to support the call in soft/softer handoff. The source BS sends an A7-Handoff Request to the target BS and then the target BSC sends an Ab-BTS Setup to one or more target BTS to initiate an A3 connection. b. If resources are available, The target BTS responses with Ab-Connect messaege. The target BS initiates an A3 connection by sending an A3-Connect message to the specified address. Note that a single A7-Handoff Request message may result in multiple A3 connections being established, each using a separate A3-Connect message. This exsample shows only a single A3 connection being established. c. The source BS replies with an A3-Connect Ack message to complete the A3 connection or to acknowlege the addition of cells to an existing A3 connection. The target BSC sends Ab-Connect Ack message to the target BTS. d. The source BS begins to send the forward frames to the target BTS through the target BS. e. The target BTS begins to transmit the forward frames as soon as synchronization has occurred and to send reverse idle frames and then the target BS sends reverse idle frames as soon as the first forward frame is received from the source BS. The reverse frames contain the timing adjustment information necessary to achieve synchronization. f. The target BS sends an A7-Handoff Request Ack message to the source BS to indicate the success of the cell addition.

21

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

g. If the source BS has chosen to be notified of the start of transmission and reception at the target BS, when its SDU function and the target BS have synchronized the A3 and Ab traffic subchannel, the target BTS replies with an Ab-Traffic Channel Status message and then the target BS send an A3-Traffic Channel Status message to the source BS h. The source BSC sends an Extended / General / Universal Handoff Direction Message to the mobile station to add the new cell to the active set. i. The mobile station acknowledges recipt of the Extended / General / Universal Handoff Direction Messagae with an MS Ack Order. j. The mobile station indicates successful results of processing the Extended / General / Universal Handoff Direction Message by sending a Handoff Completion message. k. The source BSC acknowlegdes recipt of the Handoff Completion Message by sending a BS Ack Order.

l. The source BS may send a Handoff Performed message to the MSC. The Handoff
Performed message may be sent any time after the Handoff Completion Message is recived by the BS.

22

1 2 3 4 5 6

5.6

SMS Delivery

5.6.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
Ab--PCH Msg. Transfer (Data Burst Message)

BSC
ADDS Page

MSC

Time Comment

a b c

Data Burst Message

MS Ack Order Ab-ACH Msg.Transfer (MS Ack Order)

d e
ADDS Page Ack

7 8 9 10 11 12 13 14 15 16 17 18 19

Fig. 5-6-1 SMS Delivery on the Paging channel

a. The MSC determines that a point-to-point short message is to be sent to an idle mobile station. b. The BSC sends the Ab-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 Ab-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 Ab-ACH Msg. Transfer message that contains an MS Ack Order Message. f. The BSC sends ADDS Page Ack to acknowledge the ADDS Page.

23

1 2 3

5.6.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

Ab-ACH Msg. Transfer (Data Burst) Ab-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
a. The MS sends a Data Burst Message on the Access Channel to transfer the SMS message. b. The BTS sends the Ab-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 Ab-PCH Msg. Transfer message that includes the BS Acknowledge Order Message to acknowledge the Data Burst Message, if it is required.

Fig. 5-6-2 SMS Delivery on the Access channel

e. The BTS sends the BS Ack Order included in the Ab-PCH Msg. Transfer message.

24

1 2 3

5.6.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
Ab-IS-2000 FCH Fwd (Data Burst Message)

BSC
ADDS Deliver

MSC

Time Comment

a b c

Data Burst Message

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

d e
ADDS Deliver Ack

4 5 6 7 8 9 10 11 12 13

Fig. 5-6-3 SMS Delivery on the Traffic channel to MS

a. The MSC determines that a point-to-point short message is to be sent to a mobile station operating on a traffic channel. b. The BSC sends Ab-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 Ab-IS-2000 FCH Rvs containing the MS Ack Order. f. The BSC sends ADDS Page Ack to acknowledge the ADDS Page.

25

1 2 3

5.6.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
Ab-IS-2000 FCH Rvs (Data Burst Message) Ab-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

Fig. 5-6-4 SMS Delivery on the Traffic channel from MS

a. The MS sends a Data Burst Message on the Access Channel to transfer the SMS message. b. The BTS sends Ab-IS-2000 FCH Rvs containing the Data Burst Message. c. The BS sends an ADDS Deliver message to the MSC. The ADDS User Part element contains the SMS message. d. The BSC sends Ab-IS-2000 Fwd 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.

26

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

6.

Ab Interface Message Formats

For Ab 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

Ab interface message

6.1.1

Ab-ACH Msg Transfer

This Ab interface message is sent from the BTS to the BSC to notify the BSC of the reception of the contained message or Layer 2 acknowledgment on the specified access channel. Information Element Section Element Direction Type Reference Message Type Correlation ID Mobile Identity (IMSI/MIN) Mobile Identity (ESN) Cell Identifier Air Interface Message Manufacturers Specific Record 7.1 7.2 7.3 7.3 7.4 7.5 7.6 BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC M O O O O O O
b a

15 16 17 18 19 20
7

a.

If this element is included in this message, the value shall be returned in the Ab-ACH Msg Transfer Ack message. This element indicates the cell at the BTS on whose access channel the airinterface message or Layer 2 acknowledgment was received.

b.

The following table shows the bitmap layout for the Ab-ACH Msg Transfer message: 6 5 4 3 2 1 0 Octet 1 1 2 Message Type = [8EH] A3/A7 Element Identifier = [13H]

Correlation ID:

Length = [04H]

27

(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) Type of Identity = [110] (IMSI)

3 4 5 6 1 2 3

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): 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: A1 Element Identifier = [05H] Type of Identity = [101] (ESN)

n n+1 1 2 3

Length = [05H] Identity Digit 1 = [0000]

4 5 6 7 1 2 3 j MSCID = <any value> (LSB) j+1 j+2 j+3 j+4

Length = [06H] Cell Identification Discriminator = [07H] (MSB)

(MSB)

Cell = [001H-FFFH] (LSB) Sector = [0H-FH] (0H = Omni)

28

Air Interface Message:

A3/A7 Element Identifier = [21H]

1 2 3 4 5

Length = <variable> TIA/EIA-95 Message Type = <00H to FFH> Air Interface Message Length = <variable> (MSB) Air Interface Message = <any value> (LSB) Manufacturers Specific Records : Length = [XXH] Manufacturer ID = [00H XXH] Manufacturers specific information Ab Element Identifier = [XXH]

k 1 2 3 4 n

29

1 2 3 4

6.1.2

Ab-ACH Msg Transfer Ack

This Ab interface message is sent from the BSC to the BTS to acknowledge the receipt of the Ab-ACH Msg Transfer message. Information Element Section Element Direction Type Reference Message Type Correlation ID Manufacturers Specific Record 7.1 7.2 7.6 BSC -> BTS BSC -> BTS BSC -> BTS M O O
a

5 6 7 8
7

a.

This field is required if a Correlation ID value was included on the Ab-ACH Msg Transfer message to which this message is a response.

The following table shows the bitmap layout for the Ab-ACH Msg Transfer Ack message: 6 (MSB) Correlation Value = <any value> (LSB) Manufacturers Specific Records : Length = [XXH] Manufacturer ID = [00H XXH] Manufacturers specific information Ab Element Identifier = [XXH] 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 1 2 3 4 n Message Type = [8FH] A3/A7 Element Identifier = [13H]

Correlation ID:

Length = [04H]

30

1 2 3 4

6.1.3

Ab-PCH Msg Transfer

This Ab 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.1 7.2 7.3 7.3 7.4 7.5 7.7 7.6 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

a.

If this element is included in this message, the value shall be returned in the Ab-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.

31

1
7

The following table shows the bitmap layout for the Ab-PCH Msg Transfer message: 6 5 4 3 2 1 0 Octet Message Type = [8CH] A3/A7 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] Odd/even Indicator = [0] Type of Identity = [101] (ESN) 4 ESN = <any value> (LSB) Cell Identifier List: A1 Element Identifier = [1AH] 5 6 7 1 2 3 j j+1 n n+1 1 2 3 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] Identity Digit 1 = [0000]

(MSB)

Length = <variable> Cell Identification Discriminator = [02H,05H] IF (Discriminator = 02H), Cell Identification {1+: (MSB) Cell = [001H-FFFH] (LSB) Sector = [0H-FH] (0H = Omni)

} OR IF (Discriminator = 05H), Cell Identification {1+: (MSB) LAC = [0001H-FFFFH] (LSB) j j+1

32

} Cell Identification Air Interface Message: A3/A7 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] Ab Element Identifier = [XXH] A3/A7 Ele ment Identifier = [23H]

Length = <variable> TIA/EIA-95 Message Type = <00H to FFH> Air Interface Message Length = <variable> (MSB)

k 1 2 3

Manufacturers Specific Records : Length = [XXH]

1 2 3 4 n

Manufacturer ID = [00H XXH] Manufacturers specific information

1 2 3 4 5 6 7 8 9

6.1.4

Ab-PCH Msg Transfer Ack

This Ab 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.1 BTS -> BSC M

33

Correlation ID Layer 2 Ack Request/Results Cause Manufacturers Specific Record

7.2 7.7 7.8 7.6

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 Ab-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 Ab-PCH Msg Transfer message. Allowable cause values: OAM&P intervention, Equipment failure.

b.

c.

The following table shows the bitmap layout for the Ab-PCH Msg Transfer Ack message: 6 (MSB) Correlation Value = <any value> (LSB) Layer 2 Ack Request/Results: Length = [01H] Reserved = [0000 000] Layer 2 Ack = [0/1] A3/A7 Element Identifier = [23H] 5 4 3 2 1 0 Octet 1 1 2 3 4 5 6 1 2 3 Message Type = [8DH] A3/A7 Element Identifier = [13H]

Correlation ID:

Length = [04H]

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 = [XXH] Manufacturer ID = [00H XXH] Manufacturers specific information Ab Element Identifier = [XXH] 1 2 3 4

34

1 2 3 4 5 6 7

6.1.5

Ab-BTS Setup

This Ab 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 A3 Signaling Address SDU-ID Mobile Identity (IMSI/MIN) Mobile Identity (ESN) Frame Selection Info A7 Cell Info Service Option PACA Timestamp Quality of Service Parameters Manufacturers Specific Records 7.1 7.9 7.10 7.11 7.12 7.13 7.3 7.3 7.14 7.15 7.16 7.17 7.18 7.6 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 O Oa Ob O

8 9 10 11 12

a. b.

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.

35

1
7

The following table shows the bitmap layout for the Ab-BTS Setup message: 6 5 4 3 2 1 0 Message Type = [80H] A1 Element Identifier = [3FH]

Octet 1 1 2 3

Call Connection Reference:

Length = [08H] (MSB) (MSB) (MSB) Call Connection Reference = <any value> (LSB) Reserved = [000] Privacy Info: Band Class: A1 Element Identifier = [5DH] Length = [01H] Band Class = [00001] (PCS) A3/A7 Element Identifier = [1AH] Market ID = <any value> (LSB) Generating Entity ID = <any value> (LSB)

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

Length = <variable> Privacy Mask Information {1+: Reserved = [0] (MSB) Privacy Mask Type = [00001,00010] (public, private) Privacy Mask Length = <variable> Privacy Mask = <any value> (LSB) } Privacy Mask Information A3 Signaling Address: A1 Element Identifier = [49H] Status = [0,1] Available = [0,1]

j j+1 j+2 k

1 2 3 4 (LSB) 5 6 7 8 (LSB) 9 1

Length = [07H] Address Type = [01H] (IPv4) (MSB) (MSB) A3 Address = <any value> TCP Port

SDU ID: A1 Element Identifier = [4CH]

36

Length = <variable> (MSB) 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) Type of Identity = [110] (IMSI)

2 3 m 1 2 3

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): 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: A3/A7 Element Identifier = [07H] Type of Identity = [101] (ESN)

n n+1 1 2 3

Length = [05H] Identity Digit 1 = [0000]

4 5 6 7 1 2 3 4 j j+1 (FCH), (SCH), j+2 j+3 ARFCN (high part) = [000-111] j+5 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)]

A3 Traffic Channel Protocol Stack = [ 01H AAL2 / ATM / Physical Layer] Frame Offset = [00H FFH] Reserved = [000] Pilot Gating Rate = [00, 01, 10] ARFCN (low part) = [00H-FFH]

37

Forward Channel Bandwidth = [TBD] Reverse Channel Bandwidth = [TBD] } Frame Selector Entry A7 Cell Info: A3/A7 Element Identifier = [08H]

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) Cell = [001H-FFFH] (LSB) 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 A3 = [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 Abis interface standard, any service options specified in TSB58-B could transfer on the Ab interface.] (MSB) PACA Queuing Time = <any value> (LSB) Quality of Service Parameters: Length = [01H] Reserved = [0000] Manufacturers Specific Records : Length = [XXH] Manufacturer ID = [00H XXH] Packet Priority = [0000 1101] Ab Element Identifier = [XXH] 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 2 3

38

Manufacturers specific information

4 n

1 2 3 4 5 6

6.1.6

Ab-BTS Release
This message is sent from BSC to BTS to instruct the BTS to release the associated dedicated resource.

Information Element Message Type Call Connection Reference Manufacturers Specific Records

Section Reference 7.1 7.9 7.6

Element Direction BSC -> BTS BSC -> BTS BSC -> BTS M M O

Type

7 8
7 The following table shows the bitmap layout for the Ab-BTS Release message: 6 5 4 3 2 1 0 (MSB) (MSB) (MSB) Call Connection Reference = <any value> (LSB) Manufacturers Specific Records : Length = [XXH] Manufacturer ID = [00H XXH] Manufacturers specific information Ab Element Identifier = [XXH] Message Type = [82H] A1 Element Identifier = [3FH] Octet 1 1 2 3 (LSB) Generating Entity ID = <any value> (LSB) 4 5 6 7 8 9 10 1 2 3 4 n

Call Connection Reference:

Length = [08H] Market ID = <any value>

9 10
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

6.1.7

Ab-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.8

Ab-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.9

Ab-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.10

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

6.1.11

Ab-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.12

Ab-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.13

Ab-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.14

Ab-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.1 7.9 7.8 7.6

Element Direction BTS -> BSC BTS -> BSC BTS -> BSC BTS -> BSC

Type M M O O

40

1 2 The following table shows the bitmap layout for the Ab-BTS Release Request message:
7 6 5 (MSB) (MSB) (MSB) Call Connection Reference = <any value> (LSB) ext = [0] Cause: A1 Element Identifier = [04H] Length = [01H] Cause Value = [07H (OAM&P intervention), 20H (equipment failure)] Manufacturers Specific Records : Length = [XXH] Manufacturer ID = [00H XXH] Manufacturers specific information Ab Element Identifier = [XXH] 1 2 3 4 n 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

Message Type = [84H] A1 Element Identifier = [3FH]

Call Connection Reference:

Length = [08H] Market ID = <any value>

41

1 2 3 4 5 6

7. Information Element Definitions

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

Message Type

7 8
Table 7 - 1 Ab Message Type Values Message Type Value 01H 02H 03H 04H 05H 06H 07H 08H 09H 0AH 0BH 0CH 0DH 0EH 0FH 10H 11H Ab Traffic Ab Traffic Ab Traffic 6.1.11 6.1.12 6.1.13

Message Name Ab-Connect Ab-Connect Ack Ab-Remove Ab-Remove Ack (unused value available) (unused value available) (unused value available) (unused value available) (unused value available) (unused value available) Ab-IS-2000 FCH Fwd Ab-IS-2000 FCH Rvs Ab-Traffic Channel Status (unused value available) (unused value available) (unused value available) (unused value available)

Interface Ab Traffic Ab Traffic Ab Traffic Ab Traffic

Section Reference 6.1.7 6.1.8 6.1.9 6.1.10

42

(cont.) - Ab Message Type Values

Message Type Value 80H 81H 82H 83H 84H 85H 86H 87H 88H 89H 8AH 8BH 8CH 8DH 8EH 8FH 90H 91H 92H Ab Signaling Ab Signaling Ab Signaling Ab Signaling 6.1.3 6.1.4 6.1.1 6.1.2 Ab Signaling 6.1.14 Ab Signaling 6.1.6 Section Reference 6.1.5

Message Name Ab-BTS Setup (unused value available) Ab-BTS Release (unused value available) Ab-BTS Release Request (unused value available) (unused value available) (unused value available) (unused value available) (unused value available) (unused value available) (unused value available) Ab-PCH Msg. Transfer Ab-PCH Msg. Transfer Ack Ab-ACH Msg. Transfer Ab- ACH Msg.Transfer Ack (unused value available) (unused value available) (unused value available)

Interface Ab Signaling

2 3 4 5 6 7 8 9

All other values are reserved.

7.2

Correlation ID
Refer to section 6.2.2.108, 3G-IOS v4.0.0.

7.3

Mobile Identity
Refer to section 6.2.2.16, 3G-IOS v4.0.0).

7.4

Cell Identifier
Refer to section 6.2.2.20, 3G-IOS v4.0.0.

43

1 2 3 4 5 6

7.5

Air Interface Message

Refer to section 6.2.2.152, 3G-IOS v4.0.0

7.6

Manufacturers Specific Records

This information element is used to send manufacturers specific records on the Ab interface.

4 Length

Octet 1 2 3 4 n

Ab 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.7

Layer 2 Ack Request/Results

Refer to section 6.2.2.153, 3G-IOS v4.0.0.

7.8

Cause
Refer to section 6.2.2.19, 3G-IOS v4.0.0.

44

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

7.9

Call Connection Reference

Refer to section 6.2.2.98, 3G-IOS v4.0.0.

7.10

Band Class
Refer to section 6.2.2.106, 3G-IOS v4.0.0.

7.11

Privacy Info
Refer to section 6.2.2.143, 3G-IOS v4.0.0.

7.12

A3 Signaling Address
Refer to section 6.2.2.90, 3G-IOS v4.0.0.

7.13

SDU-ID
Refer to section 6.2.2.91, 3G-IOS v4.0.0.

7.14

Frame Selection Info

Refer to section 6.2.2.14, 3G-IOS v4.0.0.

7.15

A7 Cell Info
Refer to section 6.2.2.24, 3G-IOS v4.0.0.

7.16

Service Option
Refer to section 6.2.2.66, 3G-IOS v4.0.0.

7.17

PACA Timestamp
Refer to section 6.2.2.149, 3G-IOS v4.0.0.

45

1 2 3 4

7.18

Quality of Service Parameters

Refer to section 6.2.2.54, 3G-IOS v4.0.0.

46