OMF001006 GSM Signaling System BSS Training 20060531 a 2.0

8/2/2019 OMF001006 GSM Signaling System BSS Training 20060531 a 2.0

1/39

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

www.huawei.com

Internal

OMF001006GSM Signaling System -

BSSAP(BSS)

ISSUE 2.0


2/39

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 2

References

31033202-BSS Signaling Analysis

Manual

GSM Specification 0808

GSM Specification 0408


3/39


Upon completion this course, you will be

able to:

Understand the structure of BSSAP

message

Distinguish BSSMAP and DTAP

messages

Know some BSSMAP and DTAPmessage elements


4/39


Chapter 1 BSSAP Functional Structure

Chapter 2 Typical Messages

Chapter 3 BSC Signaling and Interface Tracing


5/39


BSSAP Functional Structure

BSSAPBSS Application PartBSSMAPBSS Management Application Part

DTAPDirect Transfer Part

CM

MM

SCCPSignaling Connection Control Part

MTPMessage Transfer Part

BSSAP

SCCP

MTP-3

MTP-2

MTP-1


6/39


BSSAP Functional Structure

BSS

BSSAP

SCCP

DTAP BSSMAP

Distribution Function

BSSAP

SCCP

DTAP BSSMAP

A-Interface

MSC

MTP MTP

TransmissionEquipments forAir Interface

CorrespondingBSC ProcessingModules

Distribution Function

Corresponding MSCApplication andControl Modules


7/39HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 7

Distribution Sub-layer

To discriminate DTAP and BSSMAP messages

To distribute the DTAP messages to radio link L2 access point

To converge the DTAP messages received from radio link L2

to A-interface signaling link

Functions of BSSAP Distribution Sub-layer


8/39


Components of Distribution Sub-layer

Components of Distribution Sub-layer

Octet 1

Octet L

Octet 3

Octet 2

Octet 1

Octet 2

Octet 3

Octet 4

Octet L

DTAP BSSMAPIdentifier Identifier

DLCI

LI LI Length Indicator

L3 L3

MessageMessage

.. L3 Messages

Distribution

Data Unit

..


9/39


DTAP

DTAP takes charge of transferring transparent L3 messages from MSto MSC or from MSC to MS which BSS will not analyze. It is

transferred between BSS and MSC by using SCCP service class 2

(basic connection-oriented class).

III L3 Information

User data

I Distribution Data Unit

II Length Indication


10/39


DTAP Distribution Data Unit

Distribution Data Unit has two parameters:

Discriminator : 00000000

Data Link Connection IdentityDLCI:

To indicate the data link type that should be used on the radiointerface for the messages sent from MSC to BSS

To indicate the data link type on the radio interface that reports

the message which is sent by BSS to MSC.

Discriminator:Bit: 8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 D

D=1 stands for transparent

transmission (DTAP)


11/39


BSSMAP

The transmission of BSSMAP messages upon SCCP is for the

BSSMAP functional entities of both MSC and BSS to exchange

information.

The distribution data unit of BSSMAP messages only has the

discriminator. D should be equal to 0 which stands for non-transparent transmission.

Discriminator:Bit: 8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 D

D=0 stands for non-transparent

transmission (BSSAP)


12/39






13/39



1.1 BSSMAP Message

1.2 DTAP Message


14/39


Assignment Request

This message is sent from the MSC to the BSS via the relevant SCCPconnection in order to request the BSS to assign radio resource(s), the

attributes of which are defined within the message.

The message may also include the terrestrial circuit to be used.

INFORMATION ELEMENT REFERENCE DIRECTION TYPE LENMessage Type 3.2.2.1 MSC-BSS M 1

Channel Type 3.2.2.11 MSC-BSS M 5-10

Layer 3 Header Information 3.2.2.9 MSC-BSS O (3) 4

Priority 3.2.2.18 MSC-BSS O 3

Circuit Identity Code 3.2.2.2 MSC-BSS O (1) 3

Downlink DTX Flag 3.2.2.26 MSC-BSS O (2) 2Interference Band To Be Used 3.2.2.21 MSC-BSS O 2

Classmark Information 2 3.2.2.19 MSC-BSS O (4) 4-5

Group Call Reference 3.2.2.55 MSC-BSS O (5) 3-8

Talker Flag 3.2.2.54 MSC-BSS O (6) 1

Configuration Evolution Indication 3.2.2.57 MSC-BSS O (7) 2


15/39


Assignment Complete

The ASSIGNMENT COMPLETE message is sent from the BSS to the MSCand indicates that the requested assignment has been completed correctly.

The message is sent via the BSSAP SCCP connection associated with the

dedicated resource(s).

INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN

Message Type 3.2.2.1 BSS-MSC M 1

RR Cause 3.2.2.22 BSS-MSC O 2

Circuit Identity Code 3.2.2.2 BSS-MSC O (4) 3

Cell Identifier 3.2.2.17 BSS-MSC O (1) 3-10

Chosen Channel 3.2.2.33 BSS-MSC O (3) 2Chosen Encryption Algorithm 3.2.2.44 BSS-MSC O (5) 2

Circuit Pool 3.2.2.45 BSS-MSC O (2) 2

Speech Version (Chosen) 3.2.2.51 BSS-MSC O (6) 2

LSA Identifier 3.2.2.15 BSS-MSC O (7) 4


16/39


Assignment Failure

The ASSIGNMENT FAILURE message is sent from the BSS to

the MSC via the relevant SCCP connection. It indicates that

there has been a failure in the assignment process at the BSS

and that the assignment procedure has been aborted.



Cause 3.2.2.5 BSS-MSC M 3-4



Circuit Pool List 3.2.2.46 BSS-MSC O (2) V


17/39


Handover Required This message is sent from the BSS to the MSC to indicate that for a given

MS which already has dedicated radio resource(s) assigned, a handover is

required for the reason given by the cause element.


dedicated resource(s).

INFORMATION ELEMENT REFERENCE DIRECTION TYPE LENMessage Type 3.2.2.1 BSS-MSC M 1


Response Request 3.2.2.28 BSS-MSC O 1

Cell Identifier List(Preferred)

3.2.2.27 BSS-MSC M 2n+3to

7n+3


Current Channel Type 1 3.2.2.49 BSS-MSC O (2) 2

Speech Version (Used) 3.2.2.51 BSS-MSC O (3) 2

Queueing Indicator 3.2.2.50 BSS-MSC O 2

Old BSS to New BSS Information 3.2.2.59 BSS-MSC O 2-n


18/39


Handover Request

This message is sent from the MSC to the BSS via the relevant SCCPconnection to indicate that the MS is to be handed over to that BSS.


Message Type 3.2.2.1 MSC-BSS M 1

Channel Type 3.2.2.11 MSC-BSS M 5-10

Encryption Information 3.2.2.10 MSC-BSS M (1) 3-n

Classmark Information 1 Or 3.2.2.30 MSC-BSS M# 2

Classmark Information 2 3.2.2.19 MSC-BSS M (6) 4-5Cell Identifier (Serving) 3.2.2.17 MSC-BSS M 5-10

Priority 3.2.2.18 MSC-BSS O 3

Circuit Identity Code 3.2.2.2 MSC-BSS O (7) 3

Downlink DTX Flag 3.2.2.26 MSC-BSS O (3) 2

Cell Identifier (Target) 3.2.2.17 MSC-BSS M 3-10

Interference Band To Be Used 3.2.2.21 MSC-BSS O 2

Cause 3.2.2.5 MSC-BSS O (9) 3-4

Classmark Information 3 3.2.2.20 MSC-BSS O (4) 3-14

Current Channel type 1 3.2.2.49 MSC-BSS O (8) 2Speech Version (Used) 3.2.2.51 MSC-BSS O (10) 2

Group Call Reference 3.2.2.55 MSC-BSS O (5) 3-8

Talker Flag 3.2.2.54 MSC-BSS O (11) 1

Configuration Evolution Indication 3.2.2.57 MSC-BSS O (12) 2

Chosen Encryption Algorithm (Serving) 3.2.2.44 MSC-BSS O (2) 2

Old BSS to New BSS Information 3.2.2.59 MSC-BSS O(13) 2-n

LSA Information 3.2.2.23 MSC-BSS O(14) 3+4n


19/39


Handover Request Acknowledge

This message is sent from the BSS to the MSC and indicates that therequest to support a handover at the target BSS can be supported by the

BSS, and also to which radio channel(s) the MS should be directed.


dedicated resource.



Layer 3 Information 3.2.2.24 BSS-MSC M (1) 11-n

Chosen Channel 3.2.2.33 BSS-MSC O (4) 2

Chosen Encryption Algorithm 3.2.2.44 BSS-MSC O (5) 2Circuit Pool 3.2.2.45 BSS-MSC O (2) 2


Circuit Identity Code 3.2.2.2 BSS-MSC O (3) 3



20/39


Handover Command

This message is sent from the MSC to the BSS via the relevant

SCCP connection and contains the target channel to which the

MS should retune.



Layer 3 Information 3.2.2.24 MSC-BSS M (1) 11-n

Cell Identifier 3.2.2.17 MSC-BSS O 3-10


21/39


Handover Required Reject

This message is sent from the MSC to the BSS via the relevant

SCCP connection. It indicates to the BSS that the HANDOVER

REQUIRED message has not resulted in handover.



Cause 3.2.2.5 MSC-BSS M 3-4


22/39


Handover Complete

This message is sent from the BSS to the MSC via the relevant SCCP

connection.

It indicates that the correct MS has successfully accessed the target cell.





23/39


Handover Failure

This message is sent from the BSS to the MSC via the relevant

SCCP connection. It indicates to the MSC that there has been

a failure in the resource allocation process on handover, and

that the handover has been aborted.








24/39


Handover Performed

This message is sent from the BSS to the MSC in order to indicate that theBSS has performed an internal handover.

The cell identifier and (if required for O and M reasons) optionally the new

channel identity is included.


dedicated resource(s).INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN



Cell Identifier 3.2.2.17 BSS-MSC M 3-10


Chosen Encryption Algorithm 3.2.2.44 BSS-MSC O (2) 2




25/39


Paging

This message is sent from the MSC to the BSS and containssufficient information to allow the paging message to be transmitted

by the correct cells at the correct time.

This message is sent as a connectionless SCCP message.



IMSI 3.2.2.6 MSC-BSS M 3-10

TMSI 3.2.2.7 MSC-BSS O (1) 6

Cell Identifier List 3.2.2.27 MSC-BSS M 3 to

3+7n

Channel Needed 3.2.2.36 MSC-BSS O (2) 2

eMLPP Priority 3.2.2.56 MSC-BSS O (3) 2


26/39


Clear Request

This message is sent from the BSS to the MSC to indicate to the

MSC that the BSS wishes to release the associated dedicated

resource(s).

The message is sent via the BSSAP SCCP connection associated

with the dedicated resource(s).





27/39


Clear Command

This message is sent from the MSC to the BSS to instruct the

BSS to release the associated dedicated resource(s).

The message is sent via the BSSAP SCCP connection

associated with the dedicated resource(s).



Layer 3 Header Information 3.2.2.9 MSC-BSS O (1) 4

Cause 3.2.2.5 MSC-BSS M 3-4


28/39


Complete Layer 3 Information

The message is sent from the BSS to the MSC on receipt of the initial layer3 message on a dedicated channel, e.g. Paging response, Location

Updating Request, CM Reestablishment Request, CM Service Request,

IMSI detach.

The BSS does not analyse the contents of the initial layer 3 message, other

than the Classmark information.

The message is sent via the BSSAP SCCP connection established for the

associated dedicated resource(s).INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN


Cell Identifier 3.2.2.17 BSS-MSC M 3-10

Layer 3 Information 3.2.2.24 BSS-MSC M 3-n


LSA Identifier List 3.2.2.16 BSS-MSC O (2) 2+3n


29/39



1.1 BSSMAP Message

1.2 DTAP Message


30/39


Location Updating Accept

This message is sent by the network to the mobile station to indicate

that updating or IMSI attach in the network has been completed.

IEI Information element Type / Reference Presence Format Length

Mobility management

protocol discriminator

Protocol discriminator/10.2 M V 1/2

Skip Indicator Skip Indicator/10.3.1 M V 1/2

Location Updating Accept

message typeMessage type/10.4 M V 1

Location area identificationLocation area

identification/10.5.1.3M V 5

17 Mobile identity Mobile identity/10.5.1.4 O TLV 3-10

A1 Follow on proceedFollow on

proceed/10.5.3.7O T 1

A2 CTS permission CTS permission/10.5.3.10 O T 1


31/39


Location Updating Reject

This message is sent by the network to the mobile station to indicate

that updating or IMSI attach has failed.


Mobility management

protocol discriminator

Protocol discriminator

10.2

M V 1/2

Skip Indicator Skip Indicator

10.3.1

M V 1/2

Location Updating

Reject message type

Message type

10.4

M V 1

Reject cause Reject cause

10.5.3.6

M V 1


32/39


Disconnect (network to mobile station direction)

This message is sent by the network to indicate that the end-to-endconnection is cleared.


Call controlprotocol discriminator

Protocol discriminator10.2

M V 1/2

Transaction identifier Transaction identifier

10.3.2

M V 1/2

Disconnectmessage type

Message type 10.4 M V 1

Cause Cause 10.5.4.11 M LV 3-31

1C Facility Facility 10.5.4.15 O TLV 2-?

1E Progress indicator Progress indicator

10.5.4.21

O TLV 4

7E User-user User-user10.5.4.25

O TLV 3-131

7B Allowed actions $(CCBS)$ Allowed actions10.5.4.26

O TLV 3


33/39


Disconnect (mobile station to networkdirection)

Disconnect

This message is sent by the mobile station torequest the network to clear an end-to-endconnection.

The message contents are similar to those ofDisconnect (network to mobile station direction)


34/39


Setup (mobile originating call establishment)

This message is sent from the mobile station to the network to initiatea mobile originating call establishment.


Call controlprotocol discriminator

Protocol discriminator10.2

M V 1/2

Transaction identifier Transaction identifier10.3.2

M V 1/2

Setupmessage type

Message type10.4

M V 1

D- BC repeat indicator Repeat indicator10.5.4.22

C TV 1

04 Bearer capability 1 Bearer capability10.5.4.5

M TLV 3-15

04 Bearer capability 2 Bearer capability10.5.4.5

O TLV 3-15

1C Facility (simple recall alignment) Facility10.5.4.15

O TLV 2-

5D Calling party sub-address

Calling party subaddr.10.5.4.10

O TLV 2-23

5E Called party BCDnumber

Called party BCD num.10.5.4.7

M TLV 3-43

6D Called party sub-address

Called party subaddr.10.5.4.8

O TLV 2-23


35/39






36/39


Means of BSC Signaling and InterfaceTracing

Signaling analyzer

MA10

KC1297

BSC Maintenance Console

GSM Interface Tracing

GSM Interface Tracing ReviewNO7 Message Tracing

NO7 Message Tracing Review


37/39


Comparison of different means

Signaling Analyzer

Expensive, additional investment needed.

Can trace all the signaling of A-interface and Abis-interface

from the physical layer.

GSM Interface Trace

No additional equipment and investment needed.

A-interface trace to trace BSSAP and SCCP in BSC.

A-bis interface trace to trace A-bis interface L3 messages.

Um interface trace to trace Um interface L3 messages.


38/39


Relevant GSM Specifications

GM 0808A interface

GM 0858A-bis interface

GM 0408Um interface


39/39

www.huawei.com

Thank You

Documents

OMF001006 GSM Signaling System BSS Training 20060531 a 2.0