abis interface technical report for cdma2000 spread ... · 3 1 2 1. introduction 3 this...

3GPP2 A.R0003

Version 1.0.0

Date: December 17, 1999

Abis interface Technical Report for cdma2000Spread Spectrum Systems (A.R0003 : Abis TechnicalReport)

COPYRIGHT3GPP2 and its Organizational Partners claim copyright in this document and individualOrganizational Partners may copyright and issue documents or standards publications inindividual Organizational Partner's name based on this document. Requests for reproductionof this document should be directed to the 3GPP2 Secretariat at [email protected] to reproduce individual Organizational Partner's documents should be directed to

that Organizational Partner. See www.3gpp2.org for more information.

Revision History

Revision Description Date

Rev. 1.0.0 Initial Publication December 1999

1

1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2. OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3. GLOSSARY AND DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.1 GLOSSARY .................................................................................................................... 343.2 DEFINITIONS ................................................................................................................. 35

4. FUNCTIONAL ARCHITECTURE AND INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.1 SUPPORT OF USER TRAFFIC CONNECTIONS TO A FRAME SELECTOR FUNCTION............................... 674.2 SUPPORT OF PAGING CHANNEL MESSAGING .......................................................................... 684.3 SUPPORT OF ACCESS CHANNEL MESSAGING.......................................................................... 794.4 SUPPORT OF RADIO FUNCTIONS.......................................................................................... 7104.5 SUPPORT OF BROADCAST SYSTEM INFORMATION FUNCTIONS.................................................... 7114.6 TRANSPORT PROTOCOL ................................................................................................... 812

5. CALL PROCESSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913

5.1 NOTES FOR ALL FLOWS.................................................................................................... 9145.2 MOBILE ORIGINATING CALL............................................................................................10155.3 MOBILE TERMINATED CALL ............................................................................................12165.4 CALL CLEARING ...........................................................................................................1617

5.4.1 Call Clearing initiated by MS...................................................................................16185.4.2 Call Clearing initiated by BS/MSC............................................................................18195.4.3 Call Clearing initiated by BTS............................................................................1920

5.5 HANDOFF ....................................................................................................................21215.6 SMS DELIVERY ............................................................................................................2322

5.6.1 SMS Delivery on the Paging channel .........................................................................23235.6.2 SMS Delivery on the Access channel .........................................................................24245.6.3 SMS Delivery on the Traffic channel to MS .................................................................25255.6.4 SMS Delivery on the Traffic channel from MS..............................................................2626

6. AB INTERFACE MESSAGE FORMATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 727

6.1 AB INTERFACE MESSAGE .................................................................................................27286.1.1 Ab-ACH Msg Transfer ............................................................................................27296.1.2 Ab-ACH Msg Transfer Ack ......................................................................................30306.1.3 Ab-PCH Msg Transfer ............................................................................................31316.1.4 Ab-PCH Msg Transfer Ack ......................................................................................33326.1.5 Ab-BTS Setup........................................................................................................35336.1.6 Ab-BTS Release .....................................................................................................39346.1.7 Ab-Connect ..........................................................................................................40356.1.8 Ab-Connect Ack ....................................................................................................40366.1.9 Ab-Remove ...........................................................................................................40376.1.10 Ab-Remove Ack .....................................................................................................4038

2

6.1.11 Ab-IS-2000 FCH Fwd .............................................................................................4016.1.12 Ab-IS-2000 FCH Rvs ..............................................................................................4026.1.13 Ab-Traffic Channel Status .......................................................................................4036.1.14 Ab-BTS Release Request .........................................................................................404

7. INFORMATION ELEMENT DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 25

7.1 MESSAGE TYPE ............................................................................................................4267.2 CORRELATION ID ..........................................................................................................4377.3 MOBILE IDENTITY.........................................................................................................4387.4 CELL IDENTIFIER ..........................................................................................................4397.5 AIR INTERFACE MESSAGE ...............................................................................................44107.6 MANUFACTURER’S SPECIFIC RECORDS ..............................................................................44117.7 LAYER 2 ACK REQUEST /RESULTS.....................................................................................44127.8 CAUSE ........................................................................................................................44137.9 CALL CONNECTION REFERENCE .......................................................................................45147.10 BAND CLASS................................................................................................................45157.11 PRIVACY INFO ..............................................................................................................45167.12 A3 SIGNALING ADDRESS ................................................................................................45177.13 SDU-ID ......................................................................................................................45187.14 FRAME SELECTION INFO.................................................................................................45197.15 A7 CELL INFO..............................................................................................................45207.16 SERVICE OPTION ...........................................................................................................45217.17 PACA TIMESTAMP ........................................................................................................45227.18 QUALITY OF SERVICE PARAMETERS ..................................................................................4623

3

1

1. Introduction2

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

5

2. Objectives6

The Ab interface specification achieve providing open and interoperabe system.7

And Ab interface does not disturb coexistence with other Ax intercaces.8

9

3. Glossary and Definitions10

11

3.1 Glossary12

The following is a list of acronyms that are used in the baseline text.133G-IOS Third Generation InterOperability Spesification14ITU International Telecommunications Union15MAC Medium Access Control16MS Mobile Station17QoS Quality of Service18RAN Radio Access Network19RN Radio Network20RRC Radio Resource Control Function21SDU Selection/Distribution Unit function22

23

3.2 Definitions24

A3 interface :25

26

The A3 interface carries coded user information (voice/data) and signaling information27between the SDU function and the channel element component of the BS (BTS). The A328interface is composed of two parts: signaling and user traffic. The signaling information is29carried across a separate logical channel from the user traffic channel, and controls the30allocation and use of channels for transporting user traffic.31

A7 interface :32

33

4

The A7 interface carries signaling information between a source BS and a target BS.1

Ab interface: [TBD]2

The Ab interface between the BSC and the BTS is composed of two parts: Ab Signaling3Part and Ab Traffic Part.4

The Ab Signaling Part carries signaling information between the BSC and the BTS.5

The Ab Traffic Part carries coded user information (voice/data) and signaling information6between the BSC (SDU function) and the channel element component of the BTS, like the7A3 interface on the 3G-IOS. The Ab Traffic Part is composed of two sub-parts; signaling8and user traffic. The signaling information is carried across a separate logical channel from9the user traffic channel, and controls the allocation and use of channels for transporting10user traffic.11

12

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

14

15

5

4. Functional Architecture and interfaces1

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

The new Ab interface is between the BSC and the BTS.5

6

The Abis interface consists of the A3 and Ab components, however, this contribution7provides the specifications for Ab component since A3 part is already specified in the83G-IOS specification.9

The Major components of the BSC – BTS interface definition for a CDMA system are:10

1. Support of user traffic connections to a frame selector function (A3);11

2. Support of Paging Channel messaging (Ab);12

3. Support of Access Channel messaging (Ab);13

4. Support of radio functions (Ab);14

5. Support of broadcast system information functions (Ab);15

6. Transport and protocol stack for user traffic and signaling;16

17

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

20

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

28

Following figure shows the working assumption.29

6

1

23456789

10111213141516171819

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

4.1 Support of user traffic connections to a frame selector function23

In a CDMA system, the user traffic (voice, data, etc.) of a Mobile Station may be connected24to the network using one or more conections from MS to BTS(s). If multiple connections25are used for a single flow of user information, the user traffic connection is said to be in soft26handoff. The first step within the network is carry these multiple connections back to a27single point from which a selection is made of the “best” frame received over the radio28connections. This implies a connection from each involved BTS back to a central point29where frame selection occurs. This central point is referred to as the “SDU function.”30

In both the cdmaOne and cdma2000 systems, 3G-IOS has defined the A3 interface to31support connections from the BTS to the SDU function. For details on the A3 interface see32the 3G-IOS specification.33

34

4.2 Support of paging channel messaging35

When a MS is to be sent a message on a paging channel, the BSC will typically format the36majority of that message and then forwarded that message to the BSC along with various37parameters including the identity of the cell and sector on which the message was received,38etc. The ability to forward such a paging message from the BTS to the BSC is part of the39functionality of the Ab interface.40

BSC BSC

BTS BTS

Ab Traffic Ab Traffic Ab SigAb Sig

A7 Sig

A3 Traffic

A3 Sig

7

An additional requirement of a CDMA systme is that such message may also need to be1forwarded between BSCs to be transmitted on a BTS belonging to a BSC other than the2BSC that originally creates the message. This requirement comes through support for3access handoff and other such cdmaOne and cdma2000 features. The BSC to BSC4signaling on the A7 interface to support such forwarding has been defined in the 3G-IOS5specification.6

7

4.3 Support of Access channel messaging8

When a MS sends a message on a access channel, the BTS will forward that message to the9BSC along with various parameters including the identity of the cell and sector on which10the message was received, etc. The ability to forward such a origination message from BTS11to the BSC is part of the functionality of the Ab interface.12

An additional requirement of a CDMA system is that such message may also need to be13forwarded between BSCs to a BSC other than the BSC that owns the BTS that originally14recieves the message. This requirement comes through support for access handoff and15other such cdmaOne and cdma2000 features. The BSC to BSC signaling on the A716interface to support such forwarding has been defined in the 3G-IOS specification.17

18

4.4 Support of radio functions19

Various functions can be considered with respect to the radios that exist under the control20of a BTS. Examples of such functions that require BSC-BTS signaling on the Ab interface21turning radio rquipment on and off;22

-Determining available of radio capacity;23

-Determining radio interface levels;24

-Determining received and transmitted power levels;25

26

The interaction of these functions with Operations, Administration, Maintenance, and27Provisioning(OAM&P) are for further study.28

29

4.5 Support of broadcast system information functions30

In a cdmaOne or a cdma2000 system, each BTS must broadcast various pieces of system31information that the MS will capture and use during its interactions with the network. Much32of that system information may be administratered through OAM&P functions. A small33amount of such system information may be placed information and OAM&P control of a34BTS for the same purposes must be defined.35

36

8

4.6 Transport Protocol1

For further study.2

9

1

5. Call Processing2

3

5.1 Notes for all flows4

In this contribution, we use new messages analysed and defined on previous contribution5(3GPP2-AB-19990930-02) . Followings are the reffered text.6

7Procedures A1 signaling IS-2000 air signalingCall origination / termination, etc 3G-IOS V4.0.0 V&V

( Nov. 05, 1999)IS-2000 Ballot ResolutionVersion (July, 1999)

8

9

1011

10

5.2 Mobile Originating Call1

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

Fig. 5-2 Mobile Originating Call28

29

MS BTS MSC

Origination

Complete L3 Info: CM Service Req.

Assignment Request

ExtendedChannel Assignment

Service Connect (voice)

Service Connect Completion

Assignment CompleteRing Back Tone(In-band Tone)

BSC

BS

Ab-Connect

Ab-Connect Ack

Null Traffic Ab-IS-2000 FCH Fwd (Null Data)

Ab-IS-2000 FCH Rvs (Idle)

Traffic Channel Preamble Ab-IS-2000 FCH Rvs (T-CH Preamble)

Ab-IS-2000 FCH Fwd (BS Ack Order)BS Ack Order

Idle Tch Data Frames Ab-IS-2000 FCH Rvs (Idle)

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

Voice Communication

Ab-IS-2000 FCH Fwd (SCM)

Ab-IS-2000 FCH Rvs (SCCM)

Ab-BTS Setup

Ab-ACH Msg. Transfer (ORM)

Ab-PCH Msg. Transfer (ECAM)

a

b

c

d

e

f

g

h

i

j

k

l

m

n

o

p

T303

T10

Time Comment

11

a. The MS transmits an Origination Message, with layer 2 acknowledgement required, over1the access channel of the air interface to the BTS. Then the BTS sends an Ab-ACH Msg2Transfer including the Origination message frame in Ab signaling interface.3

b. The BSC constructs the CM Service Request message, places it in the Complete Layer 34Information message, sends the message the MSC, and starts timer T303. The BSC may5request the MSC to allocate a preferred terrestrial circuit.6

c. The MSC sends an Assignment Request message to the BSC to request assignment of7radio resources. This message will include information on the terrestrial circuit, if one is8to be used between the MSC and the BSC. The MSC then starts timer T10.9

d. The BSC sends Ab-BTS Setup message to get the resource between BSC and BTS.10

e. If resourcees are available, BTS responses with Ab-Connect message.11

f. The BSC sends Ab-Connect Ack message.12

g. The BSC transmits the Ab-IS-2000 FCH Fwd message including Null Data to let the13BTS send Null traffic data toward the MS. Then the BTS begin sending Null Traffic data14for synchronizing between the BTS and the MS.15

h. The BTS sends Ab-IS-2000 FCH Rvs message including Idle data.16

i. The BSC sends a Ab-PCH Msg Transfer including Extended Channel Assignment17message. The BTS sends an Extended Channel Assignmnet message over the paging18channel of the radio interface (with the MS address) to initiate the establishment of a19radio traffic channel.20

j. The MS begins sending the traffic channel preamble (TCH Preamble) over the21designated reverse traffic channel. Then the BTS transmits this preamble with an Ab-22IS-2000 FCH Rvs message.23

k. Once the BSC acquires the reverse traffic channel, it sends an Ab-IS-2000 FCH Fwd24message including a Base Station Acknowledgement Order with layer 225acknowledgement required , to the MS over the forward traffic channel.26

l. After receiving a BS Ack Order message, the MS begins sending Idle Tch Data Frames27over the reverse traffic channel. Then the BTS transmits this frame message with an28Ab-IS-2000 FCH Rvs message.29

m. The MS Ack Order message is sent from MS, and then the BTS transmits it to the BSC30with an Ab-IS-2000 FCH Rvs message.31

n. The BSC then sends the Ab-IS-2000 FCH Fwd message including the Service Connect32message to the BTS specifying the service configuration for the call. Then the BTS33transmits the Service Connect message to the MS. The MS begins processing traffic in34accordance with the specified service configuration.35

o. On receipt of the Service Connect message, the MS responds with a Service Connect36Completion message. Then the BTS transmits it with a n Ab-IS-2000 FCH Rvs message.37

p. After the radio traffic channel and circuit have both been established and fully38interconnected, the BSC sends the Assignment Complete message to the MSC and39considers the call to be in conversation state.40

The MSC stops timer T10 upon receipt of the Assignment Complete message.4142

12

5.3 Mobile Terminated Call1

This section describes the call flow associated with a mobile station call termination in the2cdma2000 system. An Ab-PCH Msg Transfer Ack and an Ab-ACH Msg Transfer Ack are not3presented in the following figure to simplify the figure, but actually, they would be sent after4receipt of Ab-PCH Msg Transfer message or Ab-ACH Msg Transfer message respectively.5

MS BTS MSC Time Comment

a

b

cde

fg

Paging Request

BSC

h

j

i

k

l

m

n

Ab-PCH Msg. Transfer (GPM)General Page

Complete L3 Info:Paging Response

o

p

q

rst

Page Response Ab-ACH Msg. Transfer (PRM)

Ab-PCH Msg. Transfer (BS Ack)BS Ack Order

Assignment RequestAb-BTS Setup

Ab-Connect

Ab-Connect Ack

Ab-IS-2000 FCH Fwd (Null Data)Null Traffic

Ab-IS-2000 FCH Rvs (Idle)

Ab-PCH Msg. Transfer (ECAM)ExtendedChannel Assignment

TCH Preamble Ab-IS-2000 FCH Rvs (Preamble)

Ab-IS-2000 FCH Fwd (BS Ack)BS Ack Order

Idle Tch Data Frames Ab-IS-2000 FCH Rvs (Idle)

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

Ab-IS-2000 FCH Fwd (SCM)Service Connect

Serv. Con. Completion Ab-IS-2000 FCH Rvs (SCCM)Assignment Complete

Ab-IS-2000 FCH Fwd (AWIM)Alert with Info

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

Connect Order Ab-IS-2000 FCH Rvs (Connect Order)

Ab-IS-2000 FCH Fwd (BS Ack)BS Ack OrderConnect

u

v

wx

6

Fig. 5-3 Mobile Terminated Call7

13

a. The MSC sends the Paging Request message to the BS to initiate a1mobile terminated call setup scenario.2

b. The BSC constructs an General Page Message (GPM), put the3message into an Ab-PCH Msg Transfer Message and sends the Ab-4PCH Msg Transfer Message to the BTS. The BTS sends the GPM to5the MS over the paging channel. The BSC may send this message to6multiple BTSs managed by this BSC. In the following description, it is7assumed that the BSC sends this message to single BTS.8

c. The MS acknowledges the page by transmitting an Page Response9Message (PRM) to the BTS over the access channel. Upon receipt of10this message, the BTS put this message into an Ab-ACH Msg Transfer11Message and sends it to the BSC.12

d. The BS sends the Complete Layer 3 Information message containing13the Paging Response message to the MSC.14

e. The BS acknowledges the receipt of the PRM from the MS with a Base15Station Acknowledgment Order to the MS. This massage is sent by the16BSC to the BTS in the Ab-PCH Msg Transfer.17

f. The MSC sends an Assignment Request message to request18assignment of radio resources.19

g. The BSC sends an Ab-BTS Setup message to the BTS to request20allocation of radio resources at the BTS.21

h. Upon receipt of Ab-BTS Setup message, the BTS allocates radio22resources and sends an Ab-Connect message to initiates an Ab23connection and to report the result of resource allocation.24

i. The BSC replies with a Ab-Connect Ack message to complete the Ab25connection.26

j. The BSC sends an Ab-IS-2000 FCH Fwd (Null Traffic Data) message27to the BTS. The BTS starts sending Null Traffic Data to the mobile28station. This allows the mobile station to acquire the FCH29(Fundamental channel).30

k. Upon receiving the first Ab-IS-2000 FCH Fwd (Null Traffic Data)31message, the BTS starts to send Ab-IS-2000 FCH Rvs (Idle frame)32message to the BSC.33

14

l. The BSC sends an Extended Channel Assignment message to assign1the FCH.2

m. The MS starts to send the Traffic Channel Preamble. Upon receiving3the Traffic Channel Preamble, the BTS stops sending the idle frames4and starts sending the traffic frames containing the Traffic Channel5Preamble.6

n. The BSC sends the BS Ack Order to the MS via the BTS in the Ab-7IS-2000 FCH Fwd message.8

o. The MS stops transmitting the Traffic Channel Preamble and starts to9transmit idle traffic channel data frames upon receipt of the BS Ack10order.11

p. The MS sends the MS Ack order to acknowledge the BS Ack order.12This is sent by the BTS to the BSC in the Ab-IS-2000 FCH Rvs13message.14

q. The BSC sends the Service Connect Message (SCM) to the MS15specifying the service configuration for the call. This message is sent16by the BSC to the BTS in the Ab-IS-2000 FCH Fwd message. The MS17begins processing traffic in accordance with the specified service18configuration.19

r. On receipt of the Service Connect Message (SCM), the MS responds20with a Service Connect Completion Message (SCCM). Upon receipt21of this message at the BTS, it sends Ab-IS-2000 FCH Rvs message22containing this message to the BSC.23

s. After the radio traffic channel and circuit have both been established,24the BS sends the Assignment Complete message to the MSC.25

t. The BSC sends Alert with Information Message (AWIM) to the MS to26cause ringing at MS. This message is sent by the BSC to BTS in the27Ab-IS-2000 FCH Fwd message.28

u. The MS acknowledges the reception of the Alert with Information29Message by transmitting the MS Ack Order.30

v. When the call is answered at the MS, a Connect Order, with31acknowledgment required, is transmitted to the BSC via the BTS.32

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

15

x. The BSC sends a Connect message to the MSC to indicate that the call1has been answered at the MS. At this point, the call is considered stable2and in the conversation state.3

4

16

5.4 Call Clearing1

2

5.4.1 Call Clearing initiated by MS3

4

56789

1011121314151617181920

Fig. 5-4-1 Call Clearing initiated by MS21

a. The mobile station initiates call clearing by transmitting a Release22Order over the reverse traffic channel. In response to the order, BTS23sends an Ab-IS-2000 FCH Rvs message containing the Release Order24message to the BSC.25

b. The BSC then sends the Clear Request message to the MSC to initiate26the call clear transaction. Timer T300 is started by the BSC.27

c. The MSC starts timer T315 and sends a Clear Command message to28the BSC to instruct the BSC to release the associated dedicated29resource (such as terrestrial circuit). The BSC stops timer T300.30

d. In response to the Clear Command message from the MSC, the BSC31sends an Ab-IS-2000 FCH Fwd message containing the Release Order32message. The BTS then acknowledges the MS by sending it a Release33Order over the forward traffic channel .34

MS BTS MSC

Clear Request

Clear Command

Clear Complete

BSC

BS

Release Order Ab-IS-2000 FCH Rvs (Release Order)

Ab-IS-2000 FCH Fwd (Release Order))

Release Order

Ab-Remove

Ab-Remove Ack

T300

T315

a

b

c

d

e

f

g

Time

Ab-BTS Release

h

17

e. The BSC then sends an Ab-BTS Release message to the BTS. The1BTS starts to release the radio resource after sending Ab remove2message.3

f. The BTS releases the radio resource and sends Ab Remove message to4the BSC.5

g. In response to the Ab-Remove message from the BTS, BSC sends an6Ab-Remove Ack message to the BTS.7

h. The BSC sends a Clear Complete message to the MSC. Then BSC8releases the related terrestrial circuit to the BTS, if allocated. And the9MSC stops timer T315 upon receipt of the Clear Complete message.10The MSC releases the underlying transport connection.11

12

18

5.4.2 Call Clearing initiated by BS/MSC1

2

3

4

5

67

8

9

10

11

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

a. In the case of the BSC detects some failures related the call, the BSC13sends a Clear Request message to the MSC. The BSC starts timer T30014and waits for the Clear Command from the MSC (step b). A Call15Clearing flow initiated by BSC starts from this step.16

b. The MSC starts timer T315 and sends a Clear Command message to17instruct the BSC to release the associated dedicated resource (such as18terrestrial circuit). In the case of a Call Clearing initiated BS, the BSC19stops timer T300. A Call Clearing flow initiated by MSC starts from20this step.21

c. In response to the Clear Command message from the MSC, the BSC22sends Ab-IS-2000 FCH Fwd containing the Release Order message.23The BTS then acknowledges the MS by sending it a Release Order24over the forward traffic channel.25

d. The mobile station replies a Release Order over the reverse traffic26channel. In response to the order, BTS sends a Ab-IS-2000 FCH27Reverse containing the Release Order message to the BSC.28

MS BTS MSC

Clear Request

Clear Command

Clear Complete

BSC

BS


Ab-IS-2000 FCH Fwd (Release Order))

Release Order

Ab-Remove

Ab-Remove Ack

T300

T315

a

b

c

d

e

f

g

Time

Ab-BTS Release

ｈ

19



g. In response to the Ab Remove message from the BTS, BSC sends an6Ab Remove Ack message to the BTS and returns a Clear Complete7message to the MSC. Then BSC releases the related terrestrial circuit8to the BTS, if allocated.9

h. The MSC stops timer T315 upon receipt of the Clear Complete10message. The MSC releases the underlying transport connection.11

5.4.3 Call Clearing initiated by BTS12

13

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

a. In the case of a radio channel failure between the MS and the BTS, or15if the MS is not active, the BTS sends an Ab-BTS Release Request16message to BSC. In response to the message the BSC sends a Clear17Request message to the MSC. The BSC starts timer T300 and waits for18

MS BTS MSC

Clear Request

Clear Command

Clear Complete

BSC

BS


Ab-IS-2000 FCH Fwd (Release Order)

)Release Order

Ab-Remove

Ab-Remove Ack

T300

T315

a

b

c

d

e

f

g

Time

Ab-BTS Release

ｈ

Ab-BTS Release Request

20

the Clear Command from the MSC (step b). A Call Clearing flow1initiated by BS starts from this step.2

b. The MSC starts timer T315 and sends a Clear Command message to3instruct the BSC to release the associated dedicated resource (such as4terrestrial circuit). The BSC stops timer T300.5

c. In response to the Clear Command message from the MSC, the BSC6sends Ab-IS-2000 FCH Fwd containing the Release Order message.7The BTS then acknowledges the MS by sending it a Release Order8over the forward traffic channel.9

d. The mobile station replies a Release Order over the reverse traffic10channel. In response to the order, BTS sends a Ab-IS-2000 FCH Rvs11containing the Release Order message to the BSC.12



g. In response to the Ab Remove message from the BTS, BSC sends an18Ab Remove Ack message to the BTS and returns a Clear Complete19message to the MSC. Then BSC releases the related terrestrial circuit20to the BTS, if allocated.21

h. The MSC stops timer T315 upon receipt of the Clear Complete22message. The MSC releases the underlying transport connection.23

21

5.5 Handoff1

2

3

Fig. 5-5 Soft/Softer Handoff4

a. The source BS decides that one or more cells at the target BS are needed to support the5call in soft/softer handoff. The source BS sends an A7-Handoff Request to the target BS6and then the target BSC sends an Ab-BTS Setup to one or more target BTS to initiate an7A3 connection.8

b. If resources are available, The target BTS responses with Ab-Connect messaege. The9target BS initiates an A3 connection by sending an A3-Connect message to the specified10address. Note that a single A7-Handoff Request message may result in multiple A311connections being established, each using a separate A3-Connect message. This12exsample shows only a single A3 connection being established.13

c. The source BS replies with an A3-Connect Ack message to complete the A3 connection14or to acknowlege the addition of cells to an existing A3 connection. The target BSC15sends Ab-Connect Ack message to the target BTS.16

d. The source BS begins to send the forward frames to the target BTS through the target BS.17

e. The target BTS begins to transmit the forward frames as soon as synchronization has18occurred and to send reverse idle frames and then the target BS sends reverse idle frames19as soon as the first forward frame is received from the source BS. The reverse frames20contain the timing adjustment information necessary to achieve synchronization.21

f. The target BS sends an A7-Handoff Request Ack message to the source BS to indicate22the success of the cell addition.23

Ab-BTS Setup

A7-Handoff Request Ack

Source BS

MS MSCBTS BSC

Target BS

BTSBSC

Extended/General/UniversalHandoff Direction Message

MS Ack Order

Handoff Performed

A3-Connect Ack

A3-Connect

A7-Handoff Request

Handoff Completion Message

A3-Traffic Channel Status

BS Ack Order

a

b

c

e

g

k

d

f

h

ji

l

Ab-Connect

Ab-Connect Ack

Ab-Traffic Channel Status

A3-IS-2000 FCH Fwd( Forward Frames)

A3-IS-2000 FCH Rvs( Idele Frames)

Ab-IS-2000-FCH Fwd

Ab-IS-2000-FCH RvsForward Frames

22

g. If the source BS has chosen to be notified of the start of transmission and reception at the1target BS, when its SDU function and the target BS have synchronized the A3 and Ab2traffic subchannel, the target BTS replies with an Ab-Traffic Channel Status message3and then the target BS send an A3-Traffic Channel Status message to the source BS4

h. The source BSC sends an Extended / General / Universal Handoff Direction Message to5the mobile station to add the new cell to the active set.6

i. The mobile station acknowledges recipt of the Extended / General / Universal Handoff7Direction Messagae with an MS Ack Order.8

j. The mobile station indicates successful results of processing the Extended / General /9Universal Handoff Direction Message by sending a Handoff Completion message.10

k. The source BSC acknowlegdes recipt of the Handoff Completion Message by sending a11BS Ack Order.12

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

23

5.6 SMS Delivery1

2

5.6.1 SMS Delivery on the Paging channel3This section provides the call flow description for the delivery of an SMS from the MSC4to an idle mobile station on the paging channel.5

6

7

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

a. The MSC determines that a point-to-point short message is to be sent to an idle9mobile station.10

b. The BSC sends the Ab-PCH Msg. Transfer that includes a Data Burst Message. The11Data Burst Message contains the short message in received ADDS Page.12

c. The BTS transfers the Data Burst Message which is included in the Ab-PCH Msg.13Transfer message, on a Paging Channel.14

d. The MS acknowledges the receipt of the Data Burst Message, if it is required.15

e. The BTS sends the Ab-ACH Msg. Transfer message that contains an MS Ack Order16Message.17

f. The BSC sends ADDS Page Ack to acknowledge the ADDS Page.18

19

MS BTS MSCADDS Page

ADDS Page Ack

BSC

BS

MS Ack Order

Data Burst Message

Ab--PCH Msg. Transfer (Data Burst Message)

Ab-ACH Msg.Transfer (MS Ack Order)

a

b

c

d

e

f

Time Comment

24

5.6.2 SMS Delivery on the Access channel1This section provides the call flow description for the delivery of an SMS from an idle2mobile station to the MSC on the access channel.3

4

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

6

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

b. The BTS sends the Ab-ACH Msg. Transfer message that includes the Data Burst9Message received on the Access Channel.10

c. The BSC sends the ADDS Transfer message to the MSC containing the Data Burst11Message received from the MS in the ADDS User Part element.12

d. The BTS sends the Ab-PCH Msg. Transfer message that includes the BS13Acknowledge Order Message to acknowledge the Data Burst Message, if it is14required.15

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

MS BTS MSC

ADDS Transfer

BSC

BS

BS Ack Order

Data Burst MessageAb-ACH Msg. Transfer

(Data Burst)

Ab-PCH Msg.Transfer

(BS Ack Order)

a

b

c

d

e

Time Comment

25

5.6.3 SMS Delivery on the Traffic channel to MS1This section provides the call flow description for the delivery of an SMS from the MSC to2a mobile station operating on the traffic channel.3

4

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

a. The MSC determines that a point-to-point short message is to be sent to a mobile6station operating on a traffic channel.7

b. The BSC sends Ab-IS-2000 FCH Fwd containing the Data Burst Message8

c. The Data Burst Message is sent on the traffic channel.9

d. The MS acknowledges the receipt of the Data Burst Message, if it is required.10

e. The BTS sends Ab-IS-2000 FCH Rvs containing the MS Ack Order.11

f. The BSC sends ADDS Page Ack to acknowledge the ADDS Page.12

13

MS BTS MSC

ADDS Deliver

ADDS Deliver Ack

BSC

BS

MS Ack Order

Data Burst Message

Ab-IS-2000 FCH Fwd(Data Burst Message)

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

a

b

c

d

e

f

Time Comment

26

5.6.4 SMS Delivery on the Traffic channel from MS1This section provides the call flow description for the delivery of an SMS from a mobile2station operating on the traffic channel to the MSC.3

456

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

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

b. The BTS sends Ab-IS-2000 FCH Rvs containing the Data Burst Message.10

c. The BS sends an ADDS Deliver message to the MSC. The ADDS User Part element11contains the SMS message.12

d. The BSC sends Ab-IS-2000 Fwd includes the BS Ack Order to acknowledge receipt13of the Data Burst Message, if it is required.14

e. The BTS transfer the MS Ack Order.15

16

17

MS BTS MSC

ADDS Deliver

BSC

BS

BS Ack Order

Data Burst MessageAb-IS-2000 FCH Rvs(Data Burst Message)

Ab-IS-2000 FCH Fwd (BS Ack Order)

a

b

c

d

e

Time Comment

27

6. Ab Interface Message Formats1

For Ab Interface message there are a number of information elements that are individually2defined in section 6.1. Each information element in a given message is tagged with a3reference in section 6.1, a direction indication (i.e., some elements within a message are4bi-directional and others are not), and a mandatory/optional type (M/O) indicator.5

The inclusion of information elements in each message is specified as follows:6

• M - information elements which are mandatory for the message.7

• O - information elements which are optional for the message.8

6.1 Ab interface message9

10

6.1.1 Ab-ACH Msg Transfer11

This Ab interface message is sent from the BTS to the BSC to notify the BSC of the12reception of the contained message or Layer 2 acknowledgment on the specified access13channel.14

Information Element SectionReference

Element Direction Type

Message Type 7.1 BTS -> BSC M

Correlation ID 7.2 BTS -> BSCO

a

Mobile Identity (IMSI/MIN) 7.3 BTS -> BSC O

Mobile Identity (ESN) 7.3 BTS -> BSC O

Cell Identifier 7.4 BTS -> BSCO

b

Air Interface Message 7.5 BTS -> BSC O

Manufacturer’s Specific Record 7.6 BTS -> BSC O

a. If this element is included in this message, the value shall be returned in the15Ab-ACH Msg Transfer Ack message.16

b. This element indicates the cell at the BTS on whose access channel the air-17interface message or Layer 2 acknowledgment was received.18

19

The following table shows the bitmap layout for the Ab-ACH Msg Transfer message:207 6 5 4 3 2 1 0 Octet

⇒ Message Type = [8EH] 1

⇒ Correlation ID: A3/A7 Element Identifier = [13H] 1

Length = [04H] 2

28

(MSB) 3

Correlation Value = <any value> 4

5

(LSB) 6

⇒ Mobile Identity (IMSI): A1 Element Identifier = [0DH] 1

Length = [06H-08H] (10-15 digits) 2

Identity Digit 1 = [0H-9H] (BCD) Odd/evenIndicator

= [1,0]

Type of Identity

= [110] (IMSI)

3

Identity Digit 3 = [0H-9H] (BCD) Identity Digit 2 = [0H-9H] (BCD) 4

• • • • • •

Identity Digit N+1 = [0H-9H] (BCD) Identity Digit N = [0H-9H] (BCD) n

= [1111] (if even number of digits) Identity Digit N+2 = [0H-9H] (BCD) n+1

⇒ Mobile Identity (ESN): A1 Element Identifier = [0DH] 1

Length = [05H] 2

Identity Digit 1 = [0000] Odd/evenIndicator

= [0]

Type of Identity

= [101] (ESN)

3

(MSB) 4

ESN = <any value> 5

6

(LSB) 7

⇒ Cell Identifier: A1 Element Identifier = [05H] 1

Length = [06H] 2

Cell Identification Discriminator = [07H] 3

(MSB) j

MSCID = <any value> j+1

(LSB) j+2

(MSB) Cell = [001H-FFFH] j+3

(LSB) Sector = [0H-FH] (0H = Omni) j+4

29

⇒ Air Interface Message: A3/A7 Element Identifier = [21H] 1

Length = <variable> 2

TIA/EIA-95 Message Type = <00H to FFH> 3

Air Interface Message Length = <variable> 4

(MSB) 5

Air Interface Message = <any value> …(LSB) k

⇒ Manufacturer’s Specific Records : Ab Element Identifier = [XXH] 1

Length = [XXH] 2

Manufacturer ID = [00H – XXH] 3

Manufacturer’s specific information 4

• • • • • •

n

30

6.1.2 Ab-ACH Msg Transfer Ack12

This Ab interface message is sent from the BSC to the BTS to acknowledge the receipt of3the Ab-ACH Msg Transfer message.4



Message Type 7.1 BSC -> BTS M

Correlation ID 7.2 BSC -> BTSO

a

Manufacturer’s Specific Record 7.6 BSC -> BTS O

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

7

The following table shows the bitmap layout for the Ab-ACH Msg Transfer Ack message:87 6 5 4 3 2 1 0 Octet

⇒ Message Type = [8FH] 1


Length = [04H] 2

(MSB) 3


5

(LSB) 6


Length = [XXH] 2



• • • • • •

n

31

6.1.3 Ab-PCH Msg Transfer12

This Ab interface message is sent from the BSC to the BTS to request the sending of the3contained message on the specified paging channels to a mobile station.4




Correlation ID 7.2 BSC -> BTSO

a

Mobile Identity (IMSI/MIN) 7.3 BSC -> BTS O

Mobile Identity (ESN) 7.3 BSC -> BTS O

Cell Identifier List 7.4 BSC -> BTSO

b

Air Interface Message 7.5 BSC -> BTS O

Layer 2 Ack Request/Results 7.7 BSC -> BTSO

c

Manufacturer’s Specific Record 7.6 BSC -> BTS O

a. If this element is included in this message, the value shall be returned in the5Ab-PCH Msg Transfer Ack message.6

b. This element indicates the cells at the BTS on whose paging channel(s) the7air-interface message is to be sent.8

c. This element is included if the source BS wants a Layer 2 acknowledgment9from the MS.10

32

The following table shows the bitmap layout for the Ab-PCH Msg Transfer message:17 6 5 4 3 2 1 0 Octet

⇒ Message Type = [8CH] 1


Length = [04H] 2

(MSB) 3


5

(LSB) 6




= [1,0]

Type of Identity

= [110] (IMSI)

3


• • • • • •




Length = [05H] 2


= [0]

Type of Identity

= [101] (ESN)

3

(MSB) 4

ESN = <any value> 5

6

(LSB) 7

⇒ Cell Identifier List: A1 Element Identifier = [1AH] 1


Cell Identification Discriminator = [02H,05H] 3

IF (Discriminator = 02H), Cell Identification {1+:

(MSB) Cell = [001H-FFFH] j


} OR IF (Discriminator = 05H), Cell Identification {1+:

(MSB) LAC = [0001H-FFFFH] j

(LSB) j+1

33

} Cell Identification

⇒ Air Interface Message: A3/A7 Element Identifier = [21H] 1


TIA/EIA-95 Message Type = <00H to FFH> 3

Air Interface Message Length = <variable> 4

(MSB) 5

Air Interface Message = <any value> …(LSB) k

⇒ Layer 2 Ack Request/Results: A3/A7 Ele ment Identifier = [23H] 1

Length = [01H] 2

Reserved = [0000 000] Layer 2Ack

= [0/1]

3


Length = [XXH] 2



• • • • • •

n

1

2

3

45

6.1.4 Ab-PCH Msg Transfer Ack6

This Ab interface message is sent from the BTS to the BSC to report the results of sending7an air interface message on the specified paging when a layer 2 acknowledgment had been8requested by the BSC.9




34

Correlation ID 7.2 BTS -> BSCO

a

Layer 2 Ack Request/Results 7.7 BTS -> BSCO

b

Cause 7.8 BTS -> BSCO

c

Manufacturer’s Specific Record 7.6 BTS -> BSC O

a. This element is included if the Ab-PCH Msg Transfer contained this element. It1contains the value received on that message.2

b. This element is included to indicate success or failure in receiving a Layer 23acknowledgment from the MS.4

c. Inclusion of this element indicates a failure to send the paging channel message as5requested in the Ab-PCH Msg Transfer message. Allowable cause values:6OAM&P intervention, Equipment failure.7

8

The following table shows the bitmap layout for the Ab-PCH Msg Transfer Ack message:97 6 5 4 3 2 1 0 Octet

⇒ Message Type = [8DH] 1


Length = [04H] 2

(MSB) 3


5

(LSB) 6

⇒ Layer 2 Ack Request/Results: A3/A7 Element Identifier = [23H] 1

Length = [01H] 2

Reserved = [0000 000] Layer 2Ack

= [0/1]

3

⇒ Cause: A1 Element Identifier = [04H] 1

Length = [01H] 2

ext = [0] Cause Value =

[07H (OAM&P intervention),

20H (equipment failure)]

3


Length = [XXH] 2



35

• • • • • •

n

123

6.1.5 Ab-BTS Setup45

This Ab interface message is sent from the BSC to the BTS in order to request the BTS to6assign radio resource, the attributes of which are defined within the message.7


ElementDirection

Type


Call Connection Reference 7.9 BSC -> BTS M

Band Class 7.10 BSC -> BTS O

Privacy Info 7.11 BSC -> BTS O

A3 Signaling Address 7.12 BSC -> BTS O

SDU-ID 7.13 BSC -> BTS O

Mobile Identity (IMSI/MIN) 7.3 BSC -> BTS O

Mobile Identity (ESN) 7.3 BSC -> BTS O

Frame Selection Info 7.14 BSC -> BTS O

A7 Cell Info 7.15 BSC -> BTS O

Service Option 7.16 BSC -> BTS O

PACA Timestamp 7.17 BSC -> BTS Oa

Quality of Service Parameters 7.18 BSC -> BTS Ob

Manufacturer’s Specific Records 7.6 BSC -> BTS O

a. This element may be present only when the call is eligible for PACA service.8

b. This element may be only used for packet data calls. In this version of this9standard, this element is used to carry a Packet Priority field coded on 4 bits.10Values ‘1110’ and ‘1111’ are reserved.11

12

36

The following table shows the bitmap layout for the Ab-BTS Setup message:17 6 5 4 3 2 1 0 Octet

⇒ Message Type = [80H] 1

⇒ Call Connection Reference: A1 Element Identifier = [3FH] 1

Length = [08H] 2

(MSB) Market ID = <any value> 3

(LSB) 4

(MSB) Generating Entity ID = <any value> 5

(LSB) 6

(MSB) 7

Call Connection Reference = <any value> 8

9

(LSB) 10

⇒ Band Class: A1 Element Identifier = [5DH] 1

Length = [01H] 2

Reserved = [000] Band Class = [00001] (PCS) 3

⇒ Privacy Info: A3/A7 Element Identifier = [1AH] 1


Privacy Mask Information {1+:

Reserved

= [0]

Privacy Mask Type = [00001,00010]

(public, private)

Status

= [0,1]

Available

= [0,1]

j

Privacy Mask Length = <variable> j+1

(MSB) Privacy Mask = <any value> j+2

• • • • • •

(LSB) k

} Privacy Mask Information

⇒ A3 Signaling Address: A1 Element Identifier = [49H] 1

Length = [07H] 2

Address Type = [01H] (IPv4) 3

(MSB) TCP Port 4

(LSB) 5

(MSB) 6

A3 Address = <any value> 7

8

(LSB) 9

⇒ SDU ID: A1 Element Identifier = [4CH] 1

37


(MSB) SDU ID = <any value> 3

• • • • • •

(LSB) m




= [1,0]

Type of Identity

= [110] (IMSI)

3


• • • • • •




Length = [05H] 2


= [0]

Type of Identity

= [101] (ESN)

3

(MSB) 4

ESN = <any value> 5

6

(LSB) 7

⇒ Frame Selector Info: A3/A7 Element Identifier = [07H] 1


Count of Frame Selectors = [01H – FFH] 3

Length of Frame Selector Information = [08H] 4

Frame Selector Entry {1+:

Reserved = [00] Frame Selector Index = [00 0001 – 11 1111] j

Physical Channel Type

= [ 01H – Fundamental Channel (FCH),02H – Supplemental Channel (SCH),03H – Dedicated Control Channel (DCCH)]

j+1

A3 Traffic Channel Protocol Stack

= [ 01H – AAL2 / ATM / Physical Layer]

j+2

Frame Offset = [00H – FFH] j+3

Reserved = [000] Pilot Gating Rate= [00, 01, 10]

ARFCN (high part)

= [000-111]

j+4

ARFCN (low part) = [00H-FFH] j+5

38

Forward Channel Bandwidth = [TBD] j+6

Reverse Channel Bandwidth = [TBD] j+7

} Frame Selector Entry

⇒ A7 Cell Info: A3/A7 Element Identifier = [08H] 1


Count of Cells = [01H – FFH] 3

Cell Entry {1+:

Cell Discriminator Type = [07H] j

(MSB) j+1

MSCID = <any value> j+2

(LSB) j+3

(MSB) Cell = [001H-FFFH] j+4


Count of Frame Selectors for Cell = [01H – FFH] k

Length of Frame Selector Information for Cell = [01H – FFH] k+1

Frame Selector Entry {1+:

Reserved= [0]

Keep A3= [0,1]

Frame Selector Index = [00 0001 – 11 1111] m

} Frame Selector Entry

} Cell Entry

⇒ Service Option: A1 Element Identifier = [03H] 1

(MSB) Service Option 2

= [0000H - XXXXH]

[Editor’s Note; In the first phase of Abis interface standard, any service optionsspecified in TSB58-B could transfer on the Ab interface.]

(LSB) 3

⇒ PACA Timestamp: A1 Element Identifier = [4EH] 1

Length = [04H] 2

(MSB) 3

PACA Queuing Time = <any value> 4

5

(LSB) 6

⇒ Quality of Service Parameters: A1 Element Identifier = [07H] 1

Length = [01H] 2

Reserved = [0000] Packet Priority = [0000 – 1101] 3


Length = [XXH] 2


39


• • • • • •

n

12

6.1.6 Ab-BTS Release3

This message is sent from BSC to BTS to instruct the BTS to release the associated4dedicated resource.5

6


ElementDirection

Type


Call Connection Reference 7.9 BSC -> BTS M

Manufacturer’s Specific Records 7.6 BSC -> BTS O

7

The following table shows the bitmap layout for the Ab-BTS Release message:87 6 5 4 3 2 1 0 Octet



Length = [08H] 2


(LSB) 4


(LSB) 6

(MSB) 7


9

(LSB) 10


Length = [XXH] 2



• • • • • •

n

9

10

40

6.1.7 Ab-Connect1

This message is used the same format as the A3-Connect message.2

Refer to section 6.1.9.1 "A3-Connect" , 3G-IOS v4.0.03

6.1.8 Ab-Connect Ack4

This message is used the same format as the A3-Connect Ack message.5

Refer to section 6.1.9.2 "A3-Connect Ack" , 3G-IOS v4.0.06

6.1.9 Ab-Remove7

This message is used the same format as the A3-Remove message.8

Refer to section 6.1.9.3 "A3-Remove", 3G-IOS v4.0.09

6.1.10 Ab-Remove Ack10

This message is used the same format as the A3-Remove Ack message.11

Refer to section 6.1.9.4 "A3-Remove Ack", 3G-IOS v4.0.012

6.1.11 Ab-IS-2000 FCH Fwd13

This message is used the same format as the A3-IS-2000 FCH Forward message.14

Refer to section 6.1.9.9 "A3-IS-2000 FCH Forward", 3G-IOS v4.0.015

6.1.12 Ab-IS-2000 FCH Rvs16

This message is used the same format as the A3-IS-2000 FCH Reverse message.17

Refer to section 6.1.9.10 "A3-IS-2000 FCH Reverse", 3G-IOS v4.0.018

6.1.13 Ab-Traffic Channel Status19

This message is used the same format as the A3-Traffic Channel Status message.20

Refer to section 6.1.9.15 "A3-Traffic Channel Status", 3G-IOS v4.0.021

6.1.14 Ab-BTS Release Request22

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

24


ElementDirection

Type


Call Connection Reference 7.9 BTS -> BSC M

Cause 7.8 BTS -> BSC O

Manufacturer’s Specific Records 7.6 BTS -> BSC O

41

1

The following table shows the bitmap layout for the Ab-BTS Release Request message:2

7 6 5 4 3 2 1 0 Octet



Length = [08H] 2


(LSB) 4


(LSB) 6

(MSB) 7


9

(LSB) 10

⇒ Cause: A1 Element Identifier = [04H] 1

Length = [01H] 2

ext = [0] Cause Value =

[07H (OAM&P intervention),

20H (equipment failure)]

3


Length = [XXH] 2



• • • • • •

n

3

42

7. Information Element Definitions1

2

7.1 Message Type3

4

The Message Type element is used to indicate the type of a message on the Ab interfaces.5

Element Format:67 6 5 4 3 2 1 0 Octet

Message Type 1

7

Table 7 - 1 Ab Message Type Values8

Message Name

MessageTypeValue Interface

SectionReference

Ab-Connect 01H Ab Traffic 6.1.7

Ab-Connect Ack 02H Ab Traffic 6.1.8

Ab-Remove 03H Ab Traffic 6.1.9

Ab-Remove Ack 04H Ab Traffic 6.1.10

(unused value – available) 05H





(unused value – available) 0AH

Ab-IS-2000 FCH Fwd 0BH Ab Traffic 6.1.11

Ab-IS-2000 FCH Rvs 0CH Ab Traffic 6.1.12

Ab-Traffic Channel Status 0DH Ab Traffic 6.1.13

(unused value – available) 0EH

(unused value – available) 0FH



43

(cont.) - Ab Message Type Values1

Message Name

MessageTypeValue Interface

SectionReference

Ab-BTS Setup 80H Ab Signaling 6.1.5


Ab-BTS Release 82H Ab Signaling 6.1.6


Ab-BTS Release Request 84H Ab Signaling 6.1.14






(unused value – available) 8AH

(unused value – available) 8BH

Ab-PCH Msg. Transfer 8CH Ab Signaling 6.1.3

Ab-PCH Msg. Transfer Ack 8DH Ab Signaling 6.1.4

Ab-ACH Msg. Transfer 8EH Ab Signaling 6.1.1

Ab- ACH Msg.Transfer Ack 8FH Ab Signaling 6.1.2




All other values are reserved.2

3

7.2 Correlation ID4

Refer to section 6.2.2.108, 3G-IOS v4.0.0.5

7.3 Mobile Identity6

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

7.4 Cell Identifier8


44

7.5 Air Interface Message1

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

7.6 Manufacturer’s Specific Records3

This information element is used to send manufacturer’s specific records on the Ab4interface.5

67 6 5 4 3 2 1 0 Octet

Ab Element Identifier 1

Length 2

Manufacturer ID 3

4

Manufacturer’s specific information • • •

n

Length This field shall be set to the length of this element in octets following the7Length field.8

Manufacturer ID This field identifies manufacturer that creates this information element.9The value in this field is FFS.10

Manufacturer’s specific information11

This field includes manufacturer’s specific information. The content in12this field is left to the BTS/BSC manufacturer.13

14

7.7 Layer 2 Ack Request/Results15


7.8 Cause18


45

7.9 Call Connection Reference1


7.10 Band Class4


7.11 Privacy Info6


7.12 A3 Signaling Address8


7.13 SDU-ID11


7.14 Frame Selection Info13


7.15 A7 Cell Info15


7.16 Service Option18


7.17 PACA Timestamp20


46

7.18 Quality of Service Parameters1


4

abis interface technical report for cdma2000 spread ... · 3 1 2 1. introduction 3 this...

Documents