04 Tm3101eu01tm 0001 Bssap

BSSAP Siemens
BSSAP
Contents
1 Protocol Architecture 3
2 Call Sequences 11
2.1 BSSMAP Procedures 12
2.2 Complete Sequences 30
3 Formatting Rules 39
4 Appendix 53
4.1 BSSMAP Procedures 56
4.2 K1103 Protocol Tester 62
5 Exercise 93
6 Solution 135
TM3101EU01TM_0001
1
Siemens BSSAP
2 TM3101EU01TM_0001
BSSAP Siemens
1 Protocol Architecture
TM3101EU01TM_0001
3
Siemens BSSAP
4 TM3101EU01TM_0001
BSSAP Siemens
The A-interface was defined by GSM as the interface between the Base Station
System (BSS) and the Switching Subsystem (SSS). It connects the Base Station
Controller (BSC) with the Mobile Switching Center (MSC). Its description is found in
the GSM guidelines 08.01 to 08.20.
The interface comprises both signaling and user channels. It consists of one or
several digital transmission links with 2048 kbit/s; they have a frame structure of 32
timeslots with 64 kbit/s each as it is described in the CCITT recommendation G.705.
The electrical-physical properties correspond to the CCITT recommendation G.703.
The timeslots are created as user or signaling channels. The user channels are
allocated to the mobile originating and terminating calls during connection set up and
released during connection clear down. The MSC is in charge of the user channel
selection. If, during the connection, digitized speech must be transmitted in the user
channels, the coding is done according to the A-law (see CCITT Rec. G.711).
The signaling channels are operated with the Common Channel Signaling System 7.
The only User Part which is applicable is the Signaling Connection Control Part
(SCCP), and the only network indicator in use is National 0. This means that the
Service Information Octet (SIO) has always the value 10000011 (Sub-Service Field =
10 = National 0, Spare = 00, Service Indicator = 0011 = SCCP). Otherwise, the
structure of the Message Transfer Part (BSN / BIB / FSN / FIB / LI / SIO and CRC)
and the Routing Label (DPC / OPC / SLS) corresponds to the CCITT
recommendations. Especially, this means that each BSC needs a signaling point
code (SPC) in the National 0 (NAT0) network in order to be addressed by the MSC.
At the A-interface, the SCCP supports two subsystems: the Base Station System
Application Part (BSSAP) and the BSS Operation and Maintenance Application
Part (BSSOMAP). The BSSAP is described in the GSM guideline 08.08, the
BSSOMAP in the 12-series of the GSM recommendations. In this course, we are
interested in the BSSAP only.
TM3101EU01TM_0001
5
Siemens BSSAP
The SCCP routing at the A-interface depends on the Destination Point Code (DPC) in
the Routing Label and on the distinction between the two subsystems exclusively.
Accordingly, the called party address (if available) in the SCCP-section of the
messages indicates to which of the two subsystems the message is related. The
called party address contains neither another signaling point code nor Global Title
digits.
The BSSAP uses the two SCCP protocol classes 0 (connectionless) and 2
(connection-oriented). Messages which are related to a particular RR connection at
the air interface (e.g. a user connection, a Location Update, etc.), are always
transmitted with protocol class 2. Messages, which do not concern a particular SCCP
connection, make use of protocol class 0.
The SCCP connections of protocol class 2 are set up together with the RR
connections. The Base Station knows the allocation between the RR connections at
the air interface and the SCCP connections at the A-interface. Therefore, the BSS
can forward each message it has received over a RR connection towards the MSC
over the allocated SCCP connection. Vice-versa, messages the BSS has received
over an SCCP connection are forwarded over the allocated RR connection towards
the Mobile Station.
Messages, which are exchanged in this manner between Mobile Station and MSC
transparently through the BSS, belong to the Direct Transfer Application Part
(DTAP). The DTAP is a part of the BSSAP and consists of those messages where
the layer 3 data are not modified in any way by the BSS. When the BSS receives
such a message on the air interface (RR connection), it evaluates the layer 2 data,
puts the layer 3 data without any alteration into an MTP-SCCP frame and transmits
this frame over the corresponding SCCP connection to the MSC. When the BSS
receives a DTAP message over an SCCP connection, it evaluates MTP and SCCP,
puts the DTAP data without any alteration into a layer 2 frame and forwards this layer
2 frame over the corresponding RR connection to the Mobile Station.
The reason for the introduction of the DTAP is that, with messages of the Mobility
Management (MM) and of the Connection Management (CM), not the BSS but the
SSS is affected. Only the Radio Resource Management (RR) lies within the
responsibility of the BSS. Therefore, the BSS should be transparent for MM and CM.
The other BSSAP messages (i.e. the messages where the BSS is not transparent)
forms the BSS Management Application Part (BSSMAP). With these messages,
the BSS at least modifies the received information, or it is alone the sender or the
receiver of these messages, respectively (e.g. the blocking of a terrestrial circuit).
6 TM3101EU01TM_0001
BSSAP Siemens
MSC
SIEMENS D900SIEMENS D900
A- Interface
BSS
MTP
SCCP
BSSOMAP BSSAP
DTAP BSSMAP
Fig. 1 Structure of the A-Interface
TM3101EU01TM_0001
7
Siemens BSSAP
It follows from what has been said that DTAP messages are always related to a
particular RR connection; thus, they are always transmitted in protocol class 2
(connection-oriented) between BSC and MSC. The BSSMAP messages can belong
to protocol class 2 as well, but there are connectionless BSSMAP messages, too
(protocol class 0).
Thus, the structure displayed Fig. 2 results for signaling messages of the A-interface.
All messages belong to the Common Channel Signaling System No. 7 with User Part
SCCP. There are the two Application Parts BSSOMAP and BSSAP; they are
distinguished in the Called Party Address of the SCCP. The BSSAP, in due course, is
subdivided into DTAP (BSS is transparent for layer 3) and BSSMAP (BSS is not
transparent for layer 3). The distinction between these two parts lies within the
BSSAP. the DTAP messages always belong to protocol class 2, but the BSSMAP
messages belong to protocol class 2 or 0.
To each RR connection MS-BSS, there is an SCCP connection BSS MSC. Since the
BSS is transparent for MM and CM messages, the MM and CM connections do not
exist between MS and BSS but between MS and MSC.
8 TM3101EU01TM_0001
BSSAP Siemens
BSS
MSC
S I E M E N S D 9 0 0
CM connection
MM connection
RR connection SCCP conn.
Fig. 2 Signaling Connections
TM3101EU01TM_0001
9
Siemens BSSAP
10 TM3101EU01TM_0001
BSSAP Siemens
2 Call Sequences
TM3101EU01TM_0001
11
Siemens BSSAP
2.1 BSSMAP Procedures

Fig. 3 gives an overview over all the procedures of the BSSMAP and their distribution
over the SCCP protocol classes 0 (connectionless) and 2 (connection-oriented). It
can be seen that all proceedings related to an existing user connection belong to
class 2 whilst global procedures such as blocking and releasing of circuits are
executed in class 0.
The set up of SCCP connections is performed by the BSSMAP, too. This can be
caused by the BSC and by the MSC as well. When a Mobile Station sets up a new
RR connection at the air interface, e.g. for a mobile originating or terminating call, or
for a location update, the Base Station reacts by setting up the SCCP connection to
the mobile switching center. This is the BSSMAP procedure "Initial MS message".
When, on the other hand, a Handover to a new BSC is executed, it is the MSC which
sets up the SCCP connection. This is done in the BSSMAP procedures "Handover
resource allocation" and "Handover execution".
12 TM3101EU01TM_0001
BSSAP Siemens
Procedure Class 0 Class 2
Initial MS message X
Assignment X
Release X
Cipher mode control X
Paging X
Handover required indication X
Handover resource allocation X
Handover execution X
Classmark update X
Trace invocation X
Queuing indication X
Data link control for SAPI=/ 0 X
Blocking X
Resource indication X
Reset X
Reset Circuit X
Handover candidate enquiry X
Flow control X
Fig. 3 BSSMAP procedures (GSM 08.08)
TM3101EU01TM_0001
13
Siemens BSSAP
In the first case, the Mobile Station uses the contention resolution procedure. This
means that the Mobile Station sends a SABM in the assigned SDCCH containing an
information field with a layer 3 message (e.g. "Location Update Request", "CM
Service Request" or "Paging Response"). Now, the contention resolution procedure
causes the BSC to set up an SCCP connection to the MSC. To do this, the BSC
selects a local reference and sends the SCCP message "Connect Request" (CR) to
the MSC. The "Connect Request" contains the local reference and the BSSAP
message "Complete Layer 3 Information". This message consists of the received
layer 3 data of the SABM and the identity of the cell where the request came from.
The "Complete Layer 3 Information" belongs to the BSSMAP although it contains
unaltered layer 3 data from the air interface, because the BSS has added data (i.e.
the cell identity).
Now, the MSC selects its own local reference and answers with the SCCP message
"Connect Confirm" (CC). This message contains both local references so that now
the SCCP connection is established. Furthermore, the CC might contain a BSSAP
message (e.g. "Authentication Request"), but this is not necessary.
Independently, the Base Station responds to the SABM with UA (Unnumbered
Acknowledgment). Now, the RR connection is established, too. At once, the two
connections are assigned to each other in the BSS so that DTAP messages can be
exchanged in both directions.
It can come to pass that, in the sequel, the RR connection is changed because the
Mobile Station switches to another signaling channel. This happens in the following
cases:
l User channel assignment (TCH+FACCH+SACCH)
l Handover within the cell
l Handover within the BSC.
In these cases, the SCCP connection remains stable, but the BSS modifies the
allocation to the RR connection. MM and CM connections can be "carried over".
In the second case of an SCCP connection set up (Handover to a new BSC), it is the
mobile switching center which selects a local reference first. It sends the SCCP
message "Connect Request" (CR) to the new BSC with the local reference and the
BSSMAP message "Handover Request". In this message, the MSC informs the BSC
about the selected terrestrial circuit, about the requested channel configuration at the
air interface and the valid air interface ciphering key. The selection of the radio
channel is left to the BSS. The BSS also selects its own local reference and tells it to
the MSC in the SCCP message "Connect Confirm" (CC) which contains the
BSSMAP message "Handover Request Acknowledge". Now, the SCCP connection is
established; for the present, it is assigned only to a radio channel (and not to an RR
connection).
14 TM3101EU01TM_0001
BSSAP Siemens
a) Set up of the SCCP connection by the BSS
BSS MSC
SABM CR (Complete L3 Info)
SDCCH
(Layer 3) (Cell-Id.,Layer 3)
UA SDCCH CC
b) Set up of the SCCP connection by the MSC
BSS MSC
(CR Handover Request)
CC ( Handover Request
Acknowledge)
FACCH Handover
Access DT 1 (Handover Detect)
FACCH SABM
UA FACCH
Fig. 4 Set up of the SCCP connection
TM3101EU01TM_0001
15
Siemens BSSAP
The Mobile Station announces itself in the new cell at first with "Handover Access"-
Bursts in the FACCH. As soon as the Base Station detects these bursts, it sends the
SCCP message "Data Form 1" (DT1) with the BSSMAP messages "Handover
Detected" to the MSC. Now, the Mobile Station will set up with an SABM a layer 2
connection and simultaneously a RR connection in the FACCH. This RR connection
is now assigned in the BSS to the existing SCCP connection. With this, the exchange
of DTAP messages is possible again.
Again, the RR connection can change (due to a Handover within the cell or within the
BSC area) without impact to the SCCP connection and to the MM and CM
connections.
The MSC side always initiates the clear down of SCCP connections. Normally,
this happens in the following cases:
l Termination of a proceeding (call clear down, successful location update)
l Handover to another BSC.
In these cases, the SCCP connection will not be cleared down until the circuit
between MSC and BSC is released. The MSC sends the SCCP message "Released"
(RLSD) with both local references to the BSC. The message can contain a last DTAP
message, which is then forwarded to the Mobile Station. At any rate, the BSC will
answer with "Release Complete" (RLC; this message, too, contains both local
references). Now, the clear down of the SCCP connection is completed; the
BSSMAP is not concerned.
The Assignment of the channels is a matter of the BSSMAP. Here, the MSC causes
the BSS to select a suitable channel at the air interface and to assign it to the Mobile
Station; simultaneously, a user channel between MSC and BSC will be seized, if
necessary and through-connected to the channel of the air interface. It is always the
BSC who selects and assigns the radio channel; the MSC causes it to do so by the
indication of the requested channel type. The MSC selects the terrestrial channel.
The MSC sends the BSSMAP message "Assignment Request" in a "Data Form 1"
(DT1) to the BSS. The message contains the type of the radio channel to be seized.
This comprises the purpose (speech/data/signaling), the sort of channel (Bm, Lm, or
both) and information about channel coding and the bit rate. If a speech or data
channel is to be seized, the MSC will additionally assign a terrestrial user channel; for
this, the "Assignment Request" contains the CIC (Circuit Identification Code) of this
channel. Thus, the CIC is not transmitted in the extended Routing Label (as it is done
in the case of the ISDN-UP and the TUP) but it is part of the BSSMAP data.
Thereupon, the BSS assigns to the Mobile Station a channel of the requested type
with "Assignment Command". After reception of "Assignment Complete", the BSS
acknowledges with a BSSMAP message of the same name to the MSC.
16 TM3101EU01TM_0001
BSSAP Siemens
BSS MSC
DCCH RLSD (poss.with DTAP)
RLC
Fig. 5 Clear down of the SCCP connection
BSS MSC
I (ASS.COMM.) DT 1 (Assign Request)

SDCCH
(TCH-No.) (Channel type, CIC)
SABM
FACCH
UA
FACCH
I (Ass.Compl.) DT 1 (Assign Complete)

FACCH
Fig. 6 Assignment
TM3101EU01TM_0001
17
Siemens BSSAP
The BSSAP release can have several reasons:

l End of a proceeding (as with the clear down of an SCCP connection, see there)
l Successful Handover
l Reasons in the BSS (e.g. failure, OAM intervention etc.)
In the first case, the MSC sends to the BSC in a DT1 the BSSMAP message "Clear
Command" with the cause for the release (e.g. "Call Control"). Thereupon, the BSS
releases the radio channel with the message "Channel Release". As soon as the
Mobile Station releases the layer 2 at the air interface, the BSC sends to the MSC the
BSSMAP message "Clear Complete" in a DT1. With this, the terrestrial channel (if
such a channel was seized) is released, too.
In the second case (successful Handover), the MSC also sends to the BSC a DT1
with the BSSMAP message "Clear Command", but the release cause is "Handover
successful". Thus, no message exchange with the Mobile Station is necessary (or
even possible), but the BSC can release the radio channel locally and answer
immediately to the MSC with "Clear Complete".
In the last case (channel release with reasons in the BSS), the BSC sends to the
MSC a DT1 with the BSSMAP message "Clear Request" which contains again the
cause for the release (e.g. "OAM intervention", "Equipment failure" etc.). The further
proceeding is as with the two former cases: the MSC transmits to the BSC a "Clear
Command" where it repeats the cause given by the BSC. The BSC releases with
"Channel Release" the radio channel, and as soon as the Mobile Station clears down
layer 2, the Base Station acknowledges to the MSC with "Clear Complete". Once
more, even the terrestrial circuit is released now, if such a circuit was assigned.
At any rate, the MSC clears down the SCCP connection after the channel release (for
this).
18 TM3101EU01TM_0001
BSSAP Siemens
MSC
a) Release at the end of a proceeding S IE M E N S D 900
BSS
I (Channel Rel) DT1 (Clear Command)

DCCH
(Cause)
DISC DT1 (Clear Complete)
DCCH
UA
DCCH
MSC
S IE M E N S D 900
a) Release for BSS causes
BSS
DT1 (Clear Request)
(Cause)
I (Channel Rel) DT1 (Clear Command)

DCCH
(Cause)
DISC DT1 (Clear Complete)
DCCH
UA
DCCH
Fig. 7 BSSAP release
TM3101EU01TM_0001
19
Siemens BSSAP
Two other BSSMAP procedures play a central role with mobile calls: the cipher mode
control and the paging.
The cipher mode control is initiated by the MSC with the BSSMAP message
"Cipher Mode Command". This message is transmitted in a DT1 and contains as
most important parameter the ciphering key for the air interface (Kc). The BSS
evaluates the message, stores the Kc and forwards to the Mobile Station a message
of the same name but without parameters (especially, without Kc). With the Kc, the
Base Station is able to encipher all future data to the Mobile Station and to decipher
all future data from the Mobile Station.
The Mobile Station answers with the message "Cipher Mode Complete" (already
ciphered). Thereupon, the Base Station sends a BSSMAP message of the same
name in a DT1 to the MSC, and the cipher mode control is completed.
Paging is initiated by the MSC with the BSSMAP message "Paging" which is
transmitted in the SCCP-message "Unitdata" (UDT; a message of the protocol class
0 [connectionless]). The message contains the IMSI and the TMSI of the called
subscriber as well as a list of the possible cells. The BSS is now able to call the
subscriber in the indicated cells, using the PCH.
If the Mobile Station recognizes its own TMSI, its first reaction is to have an SDCCH
assigned (via RACH and AGCH). In this SDCCH, it sets up a layer 2 connection and
transmits the message "Paging Response" in the SABM. Now, the Base Station
sends this "Paging Response" as a "Complete Layer 3 Information" in a CR to the
MSC, thus establishing the SCCP connection (see Fig. 4).
The Base Station answers to the SABM with a UA and acknowledges the set up of
the layer 2 connection. Also, the MSC answers to the CR with CC and acknowledges
the set up of the SCCP connection.
20 TM3101EU01TM_0001
BSSAP Siemens
MSC
S IE M E N S D 900
BSS
I (Ciph. Comm.) DT 1 (Cipher Command)

SDCCH
(Kc)
I (Ciph. Compl.) DT 1 (Cipher Complete)
SDCCH
Fig. 8 Cipher Mode Control
MSC
S IE M E N S D 900
BSS
UI (Paging Req.) UDT (Paging)

PCH
(TMSI) (IMSI, TMSI, Cell-List)
Channel Req.
RACH
UI (Imm. Ass.)
AGCH
(SDCCH-No.)
SABM (Paging Resp.) CR (Complete L3 Info)

SDCCH
(Cell- Id., Paging Resp.)
UA CC
SDCCH
Fig. 9 Paging
TM3101EU01TM_0001
21
Siemens BSSAP
Handover comprises several BSSMAP procedures. We consider a Handover from

one BSC to another one; this can be an Intra-MSC-Handover or an MSC-MSC-
Handover.
When the BSC decides (based on its own measurement results and on the
"Measurement Report" from the Mobile Station) that for the Mobile Station a
Handover is indicated which cannot be executed within the own BSC area, it sends
the BSSMAP message "Handover Required" in a DT1 to the MSC (this is the
BSSMAP procedure "Handover required indication"). The message contains the
Handover cause (e.g. "Uplink quality poor", "Response to MSC invocation" etc.) as
well as a list of the possible target cells. The sequence if the list is the sequence of
preference, i.e. the most suitable cell is mentioned first, the least suitable one comes
last.
The BSC repeats the "Handover Required" periodically; the time interval between two
subsequent "Handover Required" messages is the administrable timer T7. The
message is repeated until one of the following events occurs:
l The MSC sends "Handover Command" or the MSC sends "Reset"
l The reason for the Handover holds no longer, i.e. the radio quality improves
l It is too late, i.e. the radio contact to the Mobile Station is lost
l The call is cleared down.
After reception of the "Handover Required", the MSC contacts the new BSC; this is
the BSSMAP procedure "Handover resource allocation". With an Intra-MSC-
Handover, the former MSC contacts the new BSC, whilst, with an MSC-MSC-
Handover, it is another MSC and first communication MSC-MSC is required. At any
rate, the MSC sends to the new BSC the BSSMAP message "Handover Request" in
a CR. The message contains:
l the identity of the old and of the new cell
l the requested channel type at the air interface
l the ciphering key Kc for the air interface
l the CIC of the user channel MSC ® new BSC (selected by the MSC).
22 TM3101EU01TM_0001
BSSAP Siemens
a) Handover required indication

MSC old
S IE M E N S D 900
BSS
old
UI (Mess. Rep.) DT1 (Handover Required)

SACCH (Cause, Cell-List)
T7
DT1 (Handover Required)

(Cause, Cell-List)
T7
etc.
b) Handover resource allocation

MSC new
S IE M E N S D 900
BSS
new
CR (Handover Required)
(Old/new cell,
Channel type Kc, CIC)
CC (Handover Request
Acknowledgment)
(Um -message:
Handover Command)
Fig. 10 Handover - Part 1
TM3101EU01TM_0001
23
Siemens BSSAP
The new BSC selects a channel at the air interface and forms the air interface
message "Handover Command" which informs the MSC about the new cell, the new
channel and the Handover reference number. However, this message is not radiated
by the new BSC because the Mobile Station is still tuned to the old channel and to
the old cell. Rather, the new BSC puts this air interface message (together with an
indication of the selected channel) into the BSSMAP message "Handover Request
Acknowledge" and sends this message with a CC to the MSC.
The last step is the BSSMAP procedure "Handover execution". Here, the MSC sends
to the old BSC in a DT1 the BSSMAP message "Handover command" which contains
the air interface message of the same name coming from the new BSC. (Of course,
in the case of an MSC-MSC-Handover, a communication between old and new MSC
must precede.) Now the old BSC radiates this air interface message which has been
formulated by the new BSC. Thereupon, the Mobile Station switches from the old to
the new cell.
The Mobile Station announces itself in the new FACCH at first with "Handover
Access" bursts containing the allocated Handover reference number. As soon as the
new BSC detects a burst with the correct reference number, it sends a DT1 with
"Handover Detected" to the MSC. Although the Mobile Station sends the "Handover
Access" burst four times, "Handover Detected" BSC ® MSC comes only once. Now,
the Mobile Station sets up the layer 2 (and thus the RR connection) in the new
FACCH and sends as first message "Handover Complete"; this is forwarded by the
new BSC to the MSC in a BSSMAP message of the same name. Thereupon, the
MSC releases the user channel to the former BSC (DT1 with "Clear Command" -
Answer DT1 with "Clear Complete") and finally clears down the SCCP connection
(RLSD - answer RLC). Now, the Handover is accomplished.
With a Handover within the BSC or within the cell, the BSC informs the MSC with
a BSSMAP message "Handover Performed" (in a DT1). This contains the identity of
the new cell and optionally the new channel of the air interface.
24 TM3101EU01TM_0001
BSSAP Siemens
c) Handover execution
MSC old
S IE M E N S D 90 0
BSS
old
I (Hand. Comm.) DT1 (Handover Command)

FACCH
(Um-message:
Handover Command)
MSC new
SIEM E N S D 900
BSS
new
Handover Access DT1 (Handover Detected)
FACCH
4 times once
SABM
FACCH
UA
FACCH
I (Hand. Compl.) DT1 (Handover Complete)

FACCH
MSC old
S IE M E N S D 9 00
BSS
old
DT1 (Clear Command)
DT1 (Clear Complete)
RLSD
RLC
Fig. 11 Handover - Part 2
TM3101EU01TM_0001
25
Siemens BSSAP
Let's discuss now the connectionless procedures; of these, only Paging has been
treated hitherto. Blocking is used by the BSC to inform the MSC if certain terrestrial
circuits are no longer accessible from the BSC side. The MSC must know this since it
is in charge of the channel selection at the A-interface and must avoid these circuits
henceforth.
In order to block a channel, the BSC sends to the MSC a UDT with the BSSMAP
message "Block"; this contains the CIC of the blocked channel and the blocking
cause (e.g. "Equipment failure", "OAM intervention" etc.). The MSC answers with
another UDT, which contains the BSSMAP message "Blocking Acknowledge"; in this
message, the CIC is repeated for confirmation.
Beyond this, it is possible to block several channels simultaneously. This is done by
means of the BSSMAP message "Circuit Group Block" BSC ® MSC which contains
the cause and a whole list of CICs. The MSC answers with "Circuit Group Blocking
Acknowledge" and repeats the CIC list for confirmation.
When a blocked channel becomes accessible again, the BSC informs the MSC with
a UDT containing the BSSMAP message "Unblock" with the CIC of the newly
accessible channel. The MSC confirms with a UDT containing the BSSMAP message
"Unblocking Acknowledge" in which the CIC is repeated. Again, this unblocking is
possible for whole groups ("Circuit Group Unblock" BSC ® MSC with CIC list -
"Circuit Group Unblocking Acknowledge" MSC ® BSC repeating the CIC list).
26 TM3101EU01TM_0001
BSSAP Siemens
MSC
S I E M E N S D 9 0 0
BSS
UDT (Block/ Circuit Group Block)
(CIC/ CIC- List, Cause)
UDT (Blocking Ackn. / Circuit Group Blocking Ackn.)

(CIC/ CIC- List)
UDT (Unblock/ Circuit Group Unblock)

(CIC/ CIC- List)
UDT (Unblocking Ackn./ Circuit Group Unblocking Ackn)

(CIC/ CIC- List)
Fig. 12 Blocking
TM3101EU01TM_0001
27
Siemens BSSAP
The purpose of the Reset procedure is to re-initialize BSS and MSC after a failure, to
release all calls and all resources. For this, the side where the failure has happened
(BSC or MSC) sends the BSSMAP message "Reset" (in a UDT) with the failure
cause, and the partner side answers with "Reset Acknowledge" (in another UDT). If
the "Reset" came from the MSC, the BSC will at first inform the MSC about the
blocked channels of the A-interface ("Block" or "Circuit Group Block") since the MSC
could have lost this information as a result of the failure. It is only after the
acknowledgment from the MSC ("Blocking Acknowledge" or "Circuit Group Blocking
Acknowledge", respectively) that the BSC sends "Reset Acknowledge".
If the failure affects only single channels, the less restrictive procedure Circuit Reset
can be used instead. This has the advantage that connections in other channels
remain stable. In this case, the side where the failure has happened sends the
BSSMAP message "Reset Circuit" containing the CIC of the affected channel and the
failure cause, and the partner side answers with "Reset Circuit Acknowledge"; the
CIC is repeated for security reasons. Again: if the "Reset Circuit" came from the MSC
and if the affected channel was inaccessible in the BSC, the BSC sends a "Block" for
this channel and waits for the "Blocking Acknowledge" from the MSC before sending
"Reset Circuit Acknowledge".
28 TM3101EU01TM_0001
BSSAP Siemens
a) Reset by the BSC
MSC
SIEMENS D 900
BSS
UDT (Reset)
UDT (Reset Acknowledge)
b) Reset by the MSC

UDT (Reset)
UDT (Block / Circuit Group Block)
UDT (Block / Circuit Group Blocking Ackn.)
UDT (Reset Acknowledge)
Fig. 13 Reset
TM3101EU01TM_0001
29
Siemens BSSAP
2.2 Complete Sequences

In this section, we are going to investigate how the mobile specific procedures (i.e.
call set up and clear down and location update) appear at the A-interface, which parts
belong to the BSSMAP and which to the DTAP. An exception is Handover: this
affects the BSSMAP only and has already been discussed completely in the last
section (Fig. 10 and Fig. 11).
With all call setups, the case we are going to consider is with authentication and
enciphering, but without IMEI interrogation.
With Mobile Originating Calls (MOC), the following BSSMAP procedures are
affected:
At first, the Mobile Station sets up (after the channel assignment in the RACH /
AGCH) a layer 2 connection and demands in the SABM the set up of a layer 2
connection for call control (message "CM Service Request"). This is the Initial MS
Message; therefore, it leads to the SCCP connection set up, and the Base Station
forwards the "CM Service Request" in the CR to the MSC.
The following authentication makes use of the DTAP: the messages are transmitted
at the A-interface as SCCP-messages but at the air interface as I-Frames. The first
message "Authentication Request" can be contained in the SCCP-message CC,
which acknowledges the CR. Alternatively, it is possible that the MSC sends a CC
without user message to the BSS and transmits the "Authentication Request" in a
DT1.
Afterwards, the Cipher Mode Control corresponding to Fig. 8 is performed. The
following messages "Setup" and "Call Proceeding" again belong to the DTAP.
Sooner (without OACSU) or later (with OACSU), a user channel is assigned to the
Mobile Station. This is the BSSMAP procedure Assignment. All further proceedings
with a mobile originating call (see ch. 7, Fig. 19to Fig. 21) use the DTAP.
30 TM3101EU01TM_0001
BSSAP Siemens
MSC
S IE M E N S D 90 0
BSS
Channel Req.
RACH
UI (Imm. Assign.)
AGCH

SDDCH
(CM Request) (Cell-Id., CM-Request)
UA
SDDCH
I Authentication Request (RAND) CC
I Authentication Response (SRES) DT1
I(Ciph. Comm.) DT1 (Cipher Command)

SDDCH
I(Ciph. Compl.) DT1 (Ciph. Compl.)

SDDCH
I Setup DT1
and so on
I (Ass. Command) DT1 (Assign Request)

SDDCH
SABM
FACCH
UA
FACCH
I (Ass. Complete) DT1 (Assign Complete)

FACCH
Fig. 14 Mobile Originating Call (MOC)
TM3101EU01TM_0001
31
Siemens BSSAP
A Mobile Terminating Call (MTC) begins with Paging. In the course of this
procedure, both the RR connection at the air interface and the SCCP connection at
the A-interface are set up.
The following authentication is done in the DTAP whereas the Cipher Mode Control
is again a BSSMAP procedure.
"Setup" and "Call Confirmed" are DTAP messages. The last BSSMAP procedure is
the Assignment. Everything else again runs in the DTAP.
32 TM3101EU01TM_0001
BSSAP Siemens
MSC
SIEMENS D 900
BSS
UI (Paging Requ.) UDT (Paging)

PCH
Channel Request
RACH
UI (Imm. Assign.)
AGCH
SABM
SDCCH
(Paging Resp.)
UA CR (Complete L3 Info)
SDCCH
(Cell-Id., Paging resp.)

SDDCH

SDDCH
I Setup DT1
and so on
Channel assignment as with Mobile Originating Calls
Fig. 15 Mobile Terminating Call (MTC)
TM3101EU01TM_0001
33
Siemens BSSAP
With the Call clear down, the messages "Disconnect" (if it is the Mobile Station who
initiates the cleardown), "Release" and "Release Complete" run in the DTAP.
Afterwards, Channel Release is performed with "Clear Command" and "Clear
Complete" at the A-interface and "Channel Release" at the air interface. Finally, the
layer 2 connection at the air interface and the SCCP connection will be cleared down.
34 TM3101EU01TM_0001
BSSAP Siemens
initiated MSC
SIEMENS D 900
by the Mobile Station:
BSS
I Disconnect DT1
I Release DT1
I Release Complete DT1
I (Channel Rel.) DT1 (Clear Command)

FACCH
DISC
FACCH
RLSD
UA
FACCH RLC
MSC
initiated SIEMENS D 900
by the partner side:
BSS
I Release DT1
I Release Complete DT1
I (Channel Rel.) DT1 (Clear Command)

FACCH
DISC
FACCH
RLSD
UA
FACCH
RLC
Fig. 16 Call Clear Down
TM3101EU01TM_0001
35
Siemens BSSAP
Finally, with the Location Update, there are three relevant BSSMAP procedures. It
starts with the Initial MS-Message, namely the message "Location Update Request";
this includes the set up of the SCCP connection. As usual, the first Mobile Station
message (after the assignment of the SDCCH) is contained in the SABM (Contention
resolution procedure).
The following authentication again uses the DTAP. As before, "Authentication
Request" can run in the CC (this case is illustrated on Fig. 17) or in a DT1 (in this
case, the MSC must send an empty CC beforehand). Afterwards, the Cipher Mode
Control is performed in the BSSMAP.
The messages "Location Update Accept" and "TMSI Reallocation Complete" belong
to the DTAP. Afterwards, however, the Release procedure of the BSSMAP is
performed with "Clear Command" and "Clear Complete" at the A-interface and
"Channel Release" at the air interface. Finally, the layer 2 connection at the air
interface and the SCCP connection are cleared down.
36 TM3101EU01TM_0001
BSSAP Siemens
MSC
SIEMENS D 900
BSS
Channel Req.
RACH
UI (Imm. Assign.)
AGCH

SDDCH (Loc. Upd. Request) (Cell-Id., Loc. Upd.Request)
UA
SDDCH

SDDCH

SDDCH
I Location Update Accept DT1

I TMSI Reallocation Complete DT1
I (Channel Rel.) RLSD

SDDCH
RLC
DISC
SDCCH
UA
SDCCH
Fig. 17 Location Update
TM3101EU01TM_0001
37
Siemens BSSAP
38 TM3101EU01TM_0001
BSSAP Siemens
3 Formatting Rules
TM3101EU01TM_0001
39
Siemens BSSAP
The BSSAP is always transmitted in the SCCP parameter "Data". This is

l an optional parameter in the SCCP messages "Connection Request" (CR),
"Connection Confirm" (CC) and "Released"(RLSD)
l a mandatory parameter of variable length in the SCCP messages "Data Form 1"
(DT1) and "Unitdata"(UDT).
CR, CC, RLSD and DT1 are messages of the protocol class 2 (connection-oriented)
whilst UDT belongs (at the A-interface) to the protocol class 0 (connectionless).
Because "Data" can appear as an optional parameter or as a mandatory parameter
of variable length, the SCCP always contains a length indicator for the "Data" field,
which gives the total length of the BSSAP. After this length indicator, the so-called
Discrimination byte follows which distinguishes between DTAP and BSSMAP. The
most significant seven bit are 0, and the least significant bit (= the discrimination bit)
is 1 for the DTAP (i.e. transparent) and 0 for the BSSMAP (i.e. not transparent).
40 TM3101EU01TM_0001
BSSAP Siemens
Fig. 18 Embedding of the BSSAP into the SCCP
TM3101EU01TM_0001
41
Siemens BSSAP
In the case of the DTAP, after the Discrimination byte the Data Link Connection
Identification (DLCI) ensues which is also 1 byte long. The byte indicates the SAPI
(Service Access Point Identifier, from layer 2 of the air interface) with which the
message has been received or is to be sent, respectively.
After the DLCI, the following data ensue:
l the length indicator for layer 3 of the air interface (1 byte)
l layer 3 of the air interface corresponding its formatting rules .
The value of the SCCP length indicator for the "Data" parameter exceeds by 3 the
length indicator for layer 3 since the "Data" length indicator includes three additional
bytes (the discrimination byte, the DLCI and the length indicator for layer 3).
In the case of the BSSMAP, the following data ensue after the discrimination byte:
l the length indicator for layer 3 of the BSSMAP
l layer 3 of the BSSMAP itself.
This time, the two length indicators ("Data" parameter, layer 3 BSSMAP) differ by 2
only since the DLCI byte is omitted.
Layer 3 of the BSSMAP consists of information elements. The first information
element (after the length indicator) is the message type. It has a length of 1 byte and
classifies the messages as to their purpose (e.g. "Assignment Request", "Complete
Layer 3 Information" etc.).
The GSM guideline 08.08 contains, for each message type, a list of the further
information elements of the message; these further information elements can be
optional (O) or mandatory (M). However, the elements always begin with an element
identifier with the length of 1 byte. Thus, the only element without an element
identifier is the message type itself.
Simultaneously, the list of information elements indicates the sequence in which the
mandatory and optional parameters (the latter as far as present) must be sent. There
is no general rule for this sequence; rather, it is defined for each message type
individually.
42 TM3101EU01TM_0001
BSSAP Siemens
DTAP: 0 0 0 0 0 0 0 1 Discriminator:
transparent
0 0 0 0 0 SAPI DLCI
Length indicator
Layer 3 of the
air interface
BSSMAP: Discriminator:
0 0 0 0 0 0 0 0
not transparent
Length indicator
BSSMAP message type
information elements
(always with identifier)
Fig. 19 Layout of DTAP and BSSMAP (GSM 08.06)
TM3101EU01TM_0001
43
Siemens BSSAP
Elements of variable length contain after the identifier a length indicator of 1 byte,
which indicates how many bytes, will follow after the indicator. The total length of
such an element is the length indicator value +2 (since the length indicator does not
count the identifier and itself). With elements of fixed length, the length indicator is
omitted; here, after the identifier, the contents begin immediately.
Let's consider as a first example the message "Block", which is used by the BSC to
inform the MSC that it cannot access a certain terrestrial circuit any longer (see the
BSSMAP procedure "blocking"). Besides the message type, the message contains
two more parameters: the Circuit Identity Code (CIC) of the affected channel and the
cause for the blocking (e.g. "Equipment failure" or "OAM intervention"). Both
parameters are mandatory. Whilst the CIC has the fixed length of 3 byte, the cause
can have a length of 3 or 4 byte; thus, the indication of the length in the message is
necessary.
"Block" is always transmitted in a "Unitdata" (UDT). Therefore, "Data" is a mandatory
SCCP parameter of variable length.
As a second example, we take the message "Complete Layer 3 Information" which is
used by the BSC to set up the SCCP connection. This message belongs to the
BSSMAP procedure "Initial MS message". A layer 3 message of the air interface
received in an SABM is forwarded to the MSC; the BSC adds the identity of the radio
cell. Correspondingly, the message contains, besides the message type, the cell
identity and the layer 3 data of the air interface. Both parameters are mandatory and
have a variable length. As a consequence, length indicators are required. The
optional parameter chosen channel tells which channel was selected at the air
interface.
"Complete Layer 3 Information" is always transmitted in a "Connect Request" (CR).
Thus, "Data" is an optional SCCP parameter.
44 TM3101EU01TM_0001
BSSAP Siemens
Information element Type Length
Message type M 1
Circuit Identity Code (CIC) M 3
Cause M 3-4
Fig. 20 Block
Information element Type Length
Message type M 1
Cell Identity M 3-10
Layer 3 information M 3-n
Chosen Channel O 2
Fig. 21 Complete Layer 3 Information
TM3101EU01TM_0001
45
Siemens BSSAP
As an example for a DTAP message, we select the "Setup" MS ® BSS ® MSC. The
BSS removes the layer 2 frame of this message and adds instead
l the Discrimination byte (0000 0001 = transparent, i.e. DTAP)
l the DLCI (Data Link Control Identifier). The last 3 bit provide the SAPI value 000
(signaling)
l the length indicator of layer 3 (here: 17 byte).
The layer 3 data with protocol discriminator, transaction identifier, message type and
all information elements are forwarded to the MSC in an unaltered manner.
The DTAP message constructed in this way is contained in an SCCP message "Data
Form 1" (DT1) as parameter "Data".
46 TM3101EU01TM_0001
BSSAP Siemens
0 0 0 0 0 0 0 1 Discrim.:transparent
0 0 0 0 0 0 0 0 DLCI: SAPI = 0 (signaling)
0 0 0 1 0 0 0 1 Length indicator: 17 byte
0 TI-Value 0 0 1 1 Protocol discriminator CC (TI-Flag = 0)
0 N(SD) 0 0 0 1 0 1 Message Type "Setup"
0 0 0 0 0 1 0 0 Bearer Capability:
0 0 0 0 0 0 0 1 Length 1,
speech full rate, Circuit Mode
1 0 1 0 0 0 0 0
0 1 0 1 1 1 1 0
0 0 0 0 0 1 1 1
1 0 0 0 0 0 0 0
Called Party BCD Number:
1 0 0 0 0 0 0 0 Length 7,
Type of Number unknown,
0 1 1 1 1 0 0 1
Numbering Plan unknown,
0 0 1 0 0 0 1 0 Number 08972241497
0 0 0 1 0 1 0 0
1 0 0 1 0 1 0 0
1 1 1 1 0 1 1 1
0 1 1 1 1 1 0 0 Low Layer Capability:
0 0 0 0 0 0 0 1 Length 1,
speech
0 0 0 0 0 0 0 0
Fig. 22 Example for a DTAP message
TM3101EU01TM_0001
47
Siemens BSSAP
Now, we consider an example for a "Block" message. The message begins with the
Discriminator byte 0000 0000 (not transparent, i.e. BSSMAP). Their now follows the
length indicator (here: 7 byte). The subsequent message type 0100 0000 identifies
the message as "Block".
Afterwards, the CIC must ensure corresponding Fig. 20. Indeed, we find next the
element identifier 0000 0001 which marks the next element as CIC, followed by 2
bytes CIC value. Here, the length is fixed, and no length indicator is included.
Now, we find the element identifier 0000 0100, i.e. Cause, which again corresponds
with Fig. 20. This time, a length indicator is required since the total length can vary.
The length indicator has the value 1 (1 byte contents), and we conclude 3 bytes total
length of the element (1 byte identifier, 1 byte length indicator, 1 byte contents).
The content of the element "Cause" begins with an extension bit (value 0: no further
byte present). The next 3 bits identify the class of the cause (value 010: resource
unavailable), whilst the next 4 bits clearly identify the cause within its class (here:
equipment failure).
"Block" is a "Data" parameter in the SCCP message "Unitdata" (UDT).
48 TM3101EU01TM_0001
BSSAP Siemens
0 0 0 0 0 0 0 0 Discrim.: not transparent

0 1 0 0 0 0 0 0 Message Type Block
0 0 0 0 0 0 0 1 Element identifier Circuit Identity Code
CIC
0 0 0 0 0 1 0 0 Element identifier Cause

0 0 0 0 0 0 0 1 Length 1
0 0 1 0 0 0 0 0 Equipment Failure
Fig. 23 Example for a "Block"
TM3101EU01TM_0001
49
Siemens BSSAP
As last example, we consider a "Complete Layer 3 Information" where the layer 3

message "Location Update Request" is embedded. The message begins with the
Discriminator byte 0000 0000 (not transparent, i.e. BSSMAP), and the length
indicator ensues (here: 23 bytes). The next byte with the value 0101 0111 identifies
the BSSMAP message as "Complete Layer 3 Information".
According to Fig. 21, the first parameter is the cell identity which is marked by the
identifier value 0000 0101. The next byte says that 3 bytes for the contents are going
to follow; thus, the total length of the element is 5 bytes. Next, a discriminator follows,
which indicates which cell characteristics are contained in the element. The value
0000 0010 means that the cell is identified by the Cell Identity CI alone (and not by
LACOD+CI or even by CGI = MCC+MNC+LACOD+CI). Accordingly, two bytes CI-
value ensue.
The next - and last - parameter is the layer 3 information, marked by the identifier
0001 0111. The length indicator states that the layer 3 data have a length of 15
bytes; a total length of 17 bytes results. There now follows the "Location Update
Request" with protocol discriminator, transaction identifier, message type and all
information elements.
This BSSMAP message is a "Data" parameter in a "Connect Request" (CR) from the
Base Station to the MSC.
50 TM3101EU01TM_0001
BSSAP Siemens
0 0 0 0 0 0 0 0 Discrim .: not transparent

0 1 0 1 0 1 1 1 Message type Complete Layer 3 inform .
0 0 0 0 0 1 0 1 Element identifier Cell identity
0 0 0 0 0 0 1 1 Length 3 byte
0 0 0 0 0 0 1 0 Cell identified by CI
CI
0 0 0 1 0 1 1 1 Element identifier Layer 3 information

0 0 0 0 1 1 1 1 Length 15 byte
0 0 0 0 0 1 0 1 Protocol discriminator MM (Skipp indicator=
0 N(SD) 0 0 1 0 0 0 Message Type "Loc. Update Request"
Key Sequ. Nr. 0 0 0 0 Normal Loc. Upd.; no follow-on
MCC
1 1 1 1
MNC Location Area Identification
LACOD
0 0 0 0 0 RF power Mobile Station Classmark 1

0 0 0 0 0 1 0 1
1 1 1 1 0 1 0 0
Mobile Identity:
Length 5; TMSI
TMSI
Fig. 24 Example for a "Complete Layer 3 Information"
TM3101EU01TM_0001
51
Siemens BSSAP
52 TM3101EU01TM_0001
BSSAP Siemens
4 Appendix
TM3101EU01TM_0001
53
Siemens BSSAP
The function split between BSS and SSS is displayed in figure 18. Simplified, it can
be said that the BSS tries as far as possible to deal by itself with the proceedings at
the air interface, whereas the SSS is in charge of all proceedings between MSC and
BSC and, of course, within the SSS itself. Thus, the user channels at the A-interface
are always seized and released by the MSC; the BSC can only indicate if a channel
is blocked. On the other hand, all channels of the air interface are administered by
the BSC. Here, the MSC can only initiate the channel release (during call clear down,
Handover etc.). Handover within one cell or within the BSC area is controlled by the
BSC, but as soon as the BSC area is left, the MSC is in charge, of course. Finally,
the BSC enciphers and deciphers the radio channels, but it gets the ciphering key
from the MSC.
54 TM3101EU01TM_0001
BSSAP Siemens
Function BSS SSS

Terrestrial channel: Channel Allocation X
Terrestrial channel: Blocking indication X
Radio channel: Configuration X
Management
Radio channel: Frequency Hopping X
Management
Radio channel: Idle Channel Observation X
Radio channel: Power control X
TCH: Channel Allocation (Choice) X
TCH: Link Supervision X
TCH: Channel Release X X (Invoked by MSC)
BCCH / CCCH: Scheduling of Messages X
DCCH: Link Supervision X
DCCH: Channel Release X X (Invoked by MSC)
DCCH: Allocation X
Radio Resource Indication (report idle X
channels)
Channel Coding X MSC defines Call Type
Transcoding / Rate Adaptation X
Interworking Function (data calls) X
Measurements: Reported from MS X
Measurements: Uplink X
Measurements: Traffic X
Handover: within one cell X MSC informed
Handover: within the BSC X MSC informed
Handover: external; Recognition Radio X
Reason
Handover: external; Recognition Traffic X X
Reason
Handover: external; Decision X X
Handover: external; Execution X
MM: Authentication X
MM: Location Update X
MM: Paging X
Call Control X
User Data Encryption X Key / Algorithms from MSC
Signaling Element Encryption X Key / Algorithms from MSC
Fig. 25 BSS - SSS Function Split (GSM 08.02)
TM3101EU01TM_0001
55
Siemens BSSAP
4.1 BSSMAP Procedures

Discussing the remaining BSSMAP procedures from Fig. 3, we are brief. Let's begin
with the connection related procedures (as far as not yet treated). The Classmark
update procedure has the task to keep the MSC informed about important properties
of the Mobile Station (e.g. radio power, frequency range, short message capability
etc.). Normally, MSC and BSC obtain this information from the Mobile Station when
the first contact is made; the classmark is a parameter of the first message (Location
Update Request, CM Service Request, or Paging Response). In the case of an MSC-
MSC-Handover, the old MSC tells these data to the new one.
If these properties of the Mobile Station change during the proceedings (during the
call, during the location update), the Mobile Station informs the BSS with the RR
message "Classmark Change". The BSS forwards this with a "Classmark Update" in
a DT1 to the MSC.
With Trace invocation, the MSC requests the BSC with the BSSMAP message
"Trace Invocation" (in a DT1) to generate a trace file for the SCCP connection where
the message is sent. The BSC does not acknowledge this message.
The BSC can use Queuing indication if the MSC has demanded the seizure of a
channel of the air interface (with "Assignment Request" or "Handover Request") but
if, at present, no suitable radio channel is available. In this case, the Base Station
puts the channel request into a waiting queue and sends the BSSMAP message
"Queuing indication" in a DT1 or in a CC to the MSC. At the same time, the BSC
starts a supervision timer whose run time can be adjusted by the operator.
If a suitable channel at the air interface is released during the supervision time, the
Base Station seizes the channel according to the request and informs the MSC with a
delayed "Assignment Complete" or "Handover Request Acknowledge", respectively.
If, however, the timer expires and no suitable radio channel has become free, the
BSC will send to the MSC the BSSMAP message "Assignment Failure" or "Handover
Failure", respectively.
It is optional whether the Base Station supports the waiting queue operation or not.
56 TM3101EU01TM_0001
BSSAP Siemens
S IE M E N S
MSC D 900
BSS
I (Classm. Change) DT1 (Classmark Update)

DCCH
Fig. 26 Classmark Update
MSC
S IE M E N S D 900
BSS
DT1 (Trace Invocation)
Fig. 27 Trace Invocation
MSC
S IE M E N S D 900
BSS
DT1 (Assignment Request)

DT1 (Handover Request)
occupied
DT1 (Queing Indication)
time
DT1 (Assignment Failure)
DT1 (Handover Failure)
Fig. 28 Queuing Indication
TM3101EU01TM_0001
57
Siemens BSSAP
The last connection oriented procedure is Data link control for SAPI ¹ 0. In all
messages of the air interface, the SAPI among the layer 2 data indicates the
category of the message. SAPI = 0 is used for signaling. Especially, in all RR
connections, 0 is the value of the SAPI.
When an RR connection to a Mobile Station exists (and thus an SCCP connection
BSC-MSC), further layer 2 connections between mobile and Base Station with other
SAPI values than 0 can be established. These layer 2 connections will be managed
between BSC and MSC over the same SCCP connection as the RR connection.
The demand for the set up of a layer 2 connection with SAPI ¹ 0 can come from the
Mobile Station (with a SABM) or from the MSC (with an arbitrary DTAP message with
a SAPI value 0 for which no layer 2 connection exists). If the MSC requests the set
up of the layer 2 connection, and for some reason or other the BSC is not able to do
so, it answers with the BSSMAP message "SAPI 'n' Reject"; here, 'n' stands for the
requested SAPI value. The message contains the cause for the refusal (e.g. "BSS
not equipped", "MS not equipped" etc.).
The Resource indication is used to inform the MSC how many channels are available
at the air interface of a given cell. This may be decisive in a Handover decision of the
MSC. For this, the BSSMAP message "Resource Indication" exists which is
transmitted from the BSC to the MSC in a UDT and which tells how many full rate
and half rate channels are free in the various interference bands of the cell.
The "Resource Indication" is sent to the MSC either on request or when certain
conditions are met (periodically, on reaching a threshold value etc.). The BSSMAP
message "Resource Request" MSC ® BSC is used either to demand explicitly a
"Resource Indication" from the BSC or to define the conditions for a later "Resource
Indication". At any rate, the BSS sends a "Resource Indication" as an immediate
acknowledgment for the "Resource Request".
58 TM3101EU01TM_0001
BSSAP Siemens
MSC
S IE M E N S D 900
BSS
SABM DT1 (DTAP)

DCCH
(SAPI=0) (SAPI=0)
UA DT1 (SAPI`n`reject)
DCCH
(SAPI=0) (Cause)
Fig. 29 Data Link Control for SAPI ¹ 0
MSC
S IE M E N S D 900
BSS
UDT (Resource Request)

(Cell identity; Condition for ``Resource Indication``)
UDT (Resource Indication)

Acknowledgement for ``Resource Request``
Condition
met: UDT (Resource Indication)
(Cell identity; Amount of free traffic channels)
Fig. 30 Resource Indication
TM3101EU01TM_0001
59
Siemens BSSAP
The purpose of the Handover candidate enquiry is to find out in how far it is
possible to hand over the Mobile Station of a given cell to other cells (e.g. because
the BTS of this cell shall be switched off). The MSC sends to the BSC the BSSMAP
message "Handover Candidate Enquiry" (in a UDT) with the identity of the affected
cell and a list of possible target cells. Thereupon, the BSS finds out the possible
Handover candidates and sends for each of them on his SCCP connection a
"Handover Required"; unlike a normal Handover, this message will not be repeated
periodically with the timer T7. Finally, the BSC sends to the MSC a UDT with the
message "Handover Candidate Response". This contains the identity of the affected
radio cell and the amount of Handover candidates.
The flow control (no illustration) has the following philosophy: if one of the two sides
has overload problems, it sends the BSSMAP message "Overload" in a UDT. The
partner side will reduce the traffic step by step. At first, the traffic is reduced by one
step, and two timers are started (a short one and a long one). Further "Overload"
messages arriving during the run time of the short timer will be ignored in order not to
reduce the traffic too rapidly. Whenever an "Overload" message arrives during the
run time of the long timer but outside the run time of the short timer, the traffic will be
reduced by another step, and both timers will be started anew. If, however, the long
timer expires, the traffic will be increased by one step, and the long timer will be
started anew. This is repeated until the full traffic capacity is reached again.
60 TM3101EU01TM_0001
BSSAP Siemens
MSC
S IE M E N S D 900
BSS
UDT (Handover Candidate Enquiry)

(Cell Identity; List of possible target cells)

(Cell list)
Once per
handover
candidate

(Cell list)
UDT (Handover Candidate Required)

(Cell Identity; Amount of possible candidates)
Fig. 31 Handover Candidate Enquiry
TM3101EU01TM_0001
61
Siemens BSSAP
4.2 K1103 Protocol Tester

4.2.1 Design of the K1103 Protocol Tester
The Protocol Tester K1103 has been developed for network supervision and network
analysis of signaling system No. 7 (CCS7), GSM, CDMA, ISDN D-channel, X.25, Q.3
and V5.x protocols. The Protocol Tester features a self-explanatory user interface
(realized with Windows 3.11) with mouse-control. The measurement tool consists of
a basic device and one or two interface modules to achieve the specific measuring
task.
The K1103 consists of the functional units basic device and measuring unit. The main
components are a CPU, a transputer basic card for the connection to the interface
modules and one or two interface modules for capturing the signaling data.
Two interface modules can be operated in the K1103 Protocol Tester and two PCM
links can be connected to each interface module, so that in total 4 PCM links can be
monitored by the K1103 at the same time in both directions. The status of the PCM
links is shown on the front view by two LED strips. One LED strip consists of four
groups of LEDs (marked by A, B, C, D). Each LED group is assigned to one direction
of a PCM link, i.e. A and B (respectively C and D) are monitoring one PCM link in
both directions.
62 TM3101EU01TM_0001
BSSAP Siemens
Protocol Tester K1103

SIEMENS
9
8
7
6
Winch
Power 5
Reset
1 2
1 2 3 4
Sig. Correct input signal

Faulty input signal
AIS No Alarm Indication Signal
Alarm Indication Signal detected
PRI PRI
Sync. Receiver frame synchronous
Receiver not synchronous
A A
Error No remote alarm or CRC alarm
Remote alarm or CRC alarm detected
B B
C C 1 Color display
2, 3 LED’s port 1 and port 2
4 Keyboard correction
5 Reset opening
6 „Power on“ display
D D 7 Access display of hard disk
8 Access display of disk drive
9 Floppy disk drive
LED green
LED red
Fig. 32 Front view of the K1103
TM3101EU01TM_0001
63
Siemens BSSAP
The K1103 hardware consists of the following components:

Based on a Personal Computer (microprocessor 80386DX) with
l 4 Mbyte RAM
l 500 Mbyte hard disk
l 1.44 Mbyte floppy disk (3,5“)
l color display (640 x 400 dots) with VGA controller
l removal AT keyboard
l 2 serial interfaces for remote control
l serial/parallel printer interface
l RGB-TTL interface for external monitor (VGA)
Measuring hardware consisting of

l main transputer board with
l 3 transputers with 1 Mbyte RAM each
l 3 Mbyte RAM for capture buffer
Up to 2 „plug-in“ interface modules with

l 2 transputers with 1 Mbyte RAM each
l 4 test ports each (for 2 links one duplex basis)
64 TM3101EU01TM_0001
BSSAP Siemens
1 15
220
110
SIEMENS
Type label
2 3 4 5 6 7 8 9 10 11 12 13 14
1 V.24/COM2 connector 9 Slot for interface module 2

2 Sockets for signaling with grounding 10 Fixing screw
socket
3 VGA 11 Slot for interface module 1
4 CPU 12 Fixing screw
5 Free slot 13 Rating plate
6 Free slot 14 Main switch and fuse holder
7 Free slot 15 Selector 230/110 V
8 Transputer basic board
Fig. 33 Rear view of the K1103
TM3101EU01TM_0001
65
Siemens BSSAP
The Protocol Tester K1103 is designed for monitoring at the following PCM links in a
GSM network:
Interface Network components

Abis BSC <---> BTS
A MSC/VLR <---> BSC
C/D MSC/VLR <---> HLR/AC
E/G MSC/VLR <---> MSC/VLR
MSC <---> PSTN
It is often necessary to monitor more than one GSM interface simultaneously in order
to judge whether or not the network components are interacting correctly. An
application example for that case is shown on fig. 35 where four PCM systems are
monitored at the same time. It is possible to test up to eight signaling links at four
different PCM links in any combination at the same time.
66 TM3101EU01TM_0001
BSSAP Siemens
Abis
BTS BTS
BSC
E Abis
TRAU
MSC A
G
BTS AC
VLR
MSC
HLR D, C
C
VLR B
E
MSC VLR
BTS BSC
F
EIR
possible ISDN PSTN PLMN PSDN

K1103 test point
Fig. 34 Interfaces and K1103 test points in a GSM network
Abis
BTS BSC
MSC
PSTN
S IEMEN S
N IXDORF
K1103
HLR
Fig. 35 Application for monitoring at several interfaces (e.g. for a MTC)
TM3101EU01TM_0001
67
Siemens BSSAP
4.2.2 Basic Introduction for K1103 Protocol Tester Handling

This document is aimed at introducing people to the K1103. For more information
refer to the „User Manual“ (C73000-G6076-C304).
Although the K1103 can be used with many applications, this document shows an
example, how to use the K1103 at the A-interface.
68 TM3101EU01TM_0001
BSSAP Siemens
MSC
K1103
SIEMENS D900SIEMENS D900
CCS7
BSS
Fig. 36 K1103 used at A-Interface
TM3101EU01TM_0001
69
Siemens BSSAP
4.2.2.1 HW Set Up
Check the following on the rear of the K1103: (use the figure ‘Rear view of the
K1103’)
l 220 V must be connected (14)
On the right you will see a fuse, a switch, and a 220 V cable.
l There can be various interface modules plugged into the port positions (9, 11). For
the monitoring at the A-interface the standard PRI Interface module for the
monitoring of the PCM-interface (i.e. PCM30, PCM24 or PA) is used. The
allocation of the up to 4 PCM-connections is as follows:
PCM-conn. LED-row LED-group Module connector

(Monitor)
1 1 AB 1A
2 1 CD 1C
3 2 AB 2A
4 2 CD 2C
l At least one monitor is necessary for a trace

(in our example we use Monitor A, plug A, i.e. 1A)
l Mouse cable must be connected to „LPT/COM1“ port
Connect at least one of the monitor cables to the interface to be monitored. In our
case to the A-interface.
70 TM3101EU01TM_0001
BSSAP Siemens
4.2.2.2 Power Up
To power up switch on from rear of K1103 (14).
Wait for normal “Windows” self tests and configurations.
The K1103 runs up into the Main Menu .
Click “OK” when “CCS7 Monitor” is displayed.
After Power up...

The Main Block diagram shown on the screen is called “The Main Menu”.
This heading is displayed as “CCS No. 7 Monitor”
When a Main Menu block is outlined in black it indicates that the unit is active
The following display must exist on the Front of the K1103:

l There exist two vertical rows of LED (2, 3 front view).
l The right hand row can be ignored for the example of A interface tracing.
l The left row should display all green LED on the A and B monitor. That means that
the PCM-connection is fault free
l If this is not the case, select “configuration” then “Automatic Configuration”
finally “OK”.
l This will take +- 40 seconds. If the LED on the A monitor are still not all green then
inspect the PCM cable for bad contact and return to CCS No. 7 monitor, automatic
configuration.
TM3101EU01TM_0001
71
Siemens BSSAP
4.2.2.3 Settings (Configuration, Protocol Editor, Filters)

The most important initial setting are the configuration of the interface modules and
the link definitions. These two settings can be made either automatically by
l selecting the menu item Automatic Configuration
l loading a configuration file (menu item Read Setup)
l or can be set manually.
Configuration (Click on “Configuration“)

Configure up to 4 PCM 30 interfaces (click on “Interface“). The window
“Configuration of Interface“ opens and up to four PCM-interface can be configured
(1A, 1C, 2A and 2C).
Enter the following values:
l Frame Type: Multiframe+CRC4
l Coding: HDB3
l Impedance: high
l Confirm Changes: on
72 TM3101EU01TM_0001
BSSAP Siemens
Fig. 37 CCS No.7 - Monitor Main Menu
Fig. 38 Configuration of Interface
TM3101EU01TM_0001
73
Siemens BSSAP
Up to 8 signaling channels can be monitored at the same time (click on “Define

Links“)
The following values have to be selected:
l Number of link: up to 8 can be defined
l Source: e.g. interface module 1A and timeslot 16
l Level 2 method: SS#7
l Inverted bits: No
l Bit rate: 64kBit/sec
l Identifier: it is advisable to label the transmission direction (e.g. BSS to MSC)
Rx-Direction (1-4 Character) “BSS”
TX-Direction (1-4 Character “MSC”;
this can clearly be seen when evaluating a trace and gives the indication of the
direction of the message.
When the entries are completed, press “Configure Link“
The settings for the link definition could be checked in a short way:
Select the Main Menu and do a double click on the box “Interface”.
With Display of numerical values the following can be defined: SPC-length, SPC-
/CIC-grouping, output presentation of values like CIC, SPC, message type,... in the
formats HEX, DEC,...
The entries could be as follows:
l SPC length: 14 bits
l SPC grouping: 4-3-4-3 ON
l CIC grouping: no grouping ON
l Output Representation: for various values it could be selected how these values
appear in the trace.
At the end, this configuration can be (and should be, if you need it again !!) saved in a
standard file with the ending *.sup.
74 TM3101EU01TM_0001
BSSAP Siemens
Fig. 39 Definition of the signaling links
Fig. 40 Display of numerical values
TM3101EU01TM_0001
75
Siemens BSSAP
Protocol editor (Click on “Configuration“ and then “Protocol Editor stack“)

A protocol stack is used to load the programs, necessary for the decoding of the user
parts and signaling protocols from the hexadecimal to a mnemonic format.
A complete protocol stack can be stored in standard files (text file in ASCII-format)
which have the ending *.txt (Click on “File“ and “Load protocol stack“ for loading a
standard setting; the default file for the start up is protocol.txt). After the selection of
the menu "Load protocol stack" you get a mask to define the protocol which should
be loaded.
76 TM3101EU01TM_0001
BSSAP Siemens
Fig. 41 Selection of Editor for protocol stack
Fig. 42 Load protocol stack
TM3101EU01TM_0001
77
Siemens BSSAP
In the mask Editor for protocol stack each loaded protocol is represented by an
entry. Each entry consists of three connected lines with the following contents:
1st line: Short name / Protocol information / Used memory
2nd line: Protocol name
3rd line: File name
If you want to load a new single protocol, click on “Protocols“ and “Load new
protocol“. Standard single protocols are sorted to countries and already available at
the hard disc. All files containing a protocol description (i.e. files with the extension
*.upd) and located in the directory c:\k1103\awf or a subdirectory will be displayed.
Use the cursor to select a new protocol (selected entry is gray shaded) and press
"Load" button to add the protocol into the protocol stack.
78 TM3101EU01TM_0001
BSSAP Siemens
Fig. 43 Editor for protocol stack
Fig. 44 Load new protocol (Selection of a decoding program)
TM3101EU01TM_0001
79
Siemens BSSAP
To save the current protocol stack: click on "File" and "Save protocol stack"; it can
be saved at any directory and name but has to have the ending .txt . So, as well as
the standard settings have to prepared only once, the protocol stack is created only
one time for a specific interface (e.g. A-interface) and can be reloaded again at any
time.
80 TM3101EU01TM_0001
BSSAP Siemens
Fig. 45 Save current protocol stack
TM3101EU01TM_0001
81
Siemens BSSAP
Filter
Filter setting is shown at the example Disk Recording Filter. The same principle holds
for all the other filters. With filtering the K1103 Protocol Tester ignores messages you
don’t want to collect. Examples are the FISU messages of the level 2 of the signaling
system no. 7.
Double click on Disk Recording Filter
Ensure that the following are set at the mask “Criterion for recording file filter“:
Source=X (all on)
Filter condition =Message
Click on “Define”
Ensure that in the mask “Recording file filter at message level“ the following are
set:
User part =“??? All”
Message types =“???? On”
Top left of screen:

Message type =X
Middle of screen:
Same SPCs for all UP’s = X
Back Dir as well = X
Click on OK
Click on OK
82 TM3101EU01TM_0001
BSSAP Siemens
Fig. 46 Criterion for recording file filter
Fig. 47 Recording file filter at message level
TM3101EU01TM_0001
83
Siemens BSSAP
4.2.2.4 Monitoring Online
General
Once all the settings have been “set” you can put the K1103 onto “LIVE” monitor by
“double clicking” on the “Online Monitor” box.
As soon as events occur on the link that you are tracing , messages will appear on
the “LIVE” monitor screen.
Format
Each protocol level 2, 3 & 4 can be set to record either short, medium or complete
information.
Select Format => Format dialogue => “set “
(Even if you forget to set these levels they can be changed later before transferring to
the A drive)
While on line the “right mouse key” will bring up the Format Dialogue.
If you scroll through the trace information (“arrow up”, “arrow down” or use the
mouse), notice the top right corner of the screen “LIVE” will turn to bold print. This
indicates “freeze mode” . The K1103 is scrolling in the trace file, no new messages
will appear on the screen. They are still recorded on the disk however.
To return to “LIVE” mode (non scrolling) click on “LIVE”
(LIVE changes to LIVE)
84 TM3101EU01TM_0001
BSSAP Siemens
Fig. 48 Format Setting
TM3101EU01TM_0001
85
Siemens BSSAP
4.2.2.5 Save Data

The traced data are stored as long as the tracer is ruining. In the case of power
switch of, the trace data are lost. To store the data on floppy disk the following
procedure is necessary.
a) Selecting an area
To select an area the Online monitor must be in freeze mode and the cursor position
defines the begin of the area. Select now "File" form the menu and use option
"Selecting an area". Two possibilities exists: Begin or Again. Chose "Begin" from
the submenu.
Select the area with the mouse or with the cursor key.
To finish the selection the end of the area must be defined. Chose "End" of the
submenu.
Selected areas are automatically deselected by transfer function.
86 TM3101EU01TM_0001
BSSAP Siemens
Fig. 49 Select Begin of area
Fig. 50 Select End of area
TM3101EU01TM_0001
87
Siemens BSSAP
b) Transmission to disk
The content can be copied into three different files or a printout can be started. To
store the information in a standard text file use the menu "File", select the option
"Selected area" and choose "Text file" from the submenu. The file can be saved at
any directory. The directory and the filename can be defined in the next menu.
88 TM3101EU01TM_0001
BSSAP Siemens
Fig. 51 Copy to text file
Fig. 52 Define file name and store file
TM3101EU01TM_0001
89
Siemens BSSAP
4.2.2.6 Capture RAM

The signaling messages for the traced call are entered in the Capture RAM
(3 Mbyte). To delete the content of the capture RAM enter the following:
a) Select Main Menu (by minimizing the current screen)

b) Select Capture Ram (top of screen)
c) Select “Clear Ram”
d) Return to “Live” by selecting “on line Monitor”
90 TM3101EU01TM_0001
BSSAP Siemens
Fig. 53 Capture RAM
TM3101EU01TM_0001
91
Siemens BSSAP
92 TM3101EU01TM_0001
BSSAP Siemens
5 Exercise
TM3101EU01TM_0001
93
Siemens BSSAP
94 TM3101EU01TM_0001
BSSAP Siemens
Exercise
1. Which user parts and which application parts appear at the A-interface?
2. How can it be distinguished whether a given message at the A-interface belongs

to the BSSOMAP, to the BSSMAP or to the DTAP?
3. What is the difference between the message "Cipher Mode Command" at the A-
interface and the message with the same name at the air interface?
4. Which BSSMAP procedure is used in the event of a failure to release possible

calls and to reach a well-defined initial status?
5. Intra-MSC-Handover: which BSSMAP procedures are executed between the

MSC and the old BSC, and which ones between the MSC and the new BSC?
6. On reception a message from the Mobile Station, how can the Base Station
recognize whether it has to evaluate the message by itself or whether it must
forward the message transparently (i.e. via DTAP or complete layer 3
information) to the MSC?
7. a) Is an identifier included with mandatory BSSMAP parameters?

b) Is a length indicator included with BSSMAP parameters of fixed length?
TM3101EU01TM_0001
95
Siemens BSSAP
8. Use the K1103 to monitor a call flow at the A-interface.
Answer the following questions to printed K1103 traces:
a) Was there a repetition of any MSU (message signal unit) e.g. because of
check error during that call? By which values can you detect it?
b) How many SLS-values (signaling link selection) are used for that call (Give
as well the reasons for the number of SLS)?
c) Tell for every collected signaling message, if it belongs to MOC or MTC.
d) Find out the Local References of that call. Allocate them to the correct entity
and to MOC and MTC.
e) Write down the CICs of the user channels at the A-interface. In which
messages did you find them?
f) What are the SPCs for the MSC and BSS (in decimal format)?
g) Which values for IMSI are used for the mobile stations?
h) Write down the MSISDN for the called and for the calling party address. In
which message did you find that?
i) Find out the IMEI-values for both mobile stations. In which message did you
find that?
j) What is the release cause for that call? In which message did you find that?
96 TM3101EU01TM_0001
BSSAP Siemens
K1103-trace in format short:
K1103 --- CCS No. 7 - Monitor , Date: 20.01.97 , Time: 17:34:37
HH:MM:ss"m FROM TYPE BSN I FSN I LI SLS CIC NAME

15:20:51"6 bss sccp 43 1 49 1 45 5 CR
bmap 25 CL3I
dtap CMSREQ
15:20:51"7 msc sccp 49 1 44 1 27 11 CC
bmap 8 CICMD
15:20:52"3 bss sccp 44 1 50 1 15 5 DT1
bmap 1 CICMP
15:20:52"3 msc sccp 50 1 45 1 18 11 DT1
dtap 3 IDREQ
15:20:52"5 bss sccp 45 1 51 1 27 5 DT1
dtap 12 SETUP
15:20:52"6 msc sccp 51 1 46 1 17 11 DT1
dtap 2 CPROC
15:20:52"6 msc sccp 51 1 47 1 32 11 DT1
bmap 18 ASREQ
15:20:53"0 bss sccp 47 1 52 1 26 5 DT1
dtap 11 IDRES
15:20:53"8 bss sccp 47 1 53 1 15 5 DT1
bmap 1 ASCMP
15:20:54"1 msc sccp 53 1 48 1 42 3 UDT
bmap 19 PAGIN
15:20:55"1 bss sccp 48 1 54 1 45 4 CR
bmap 25 CL3I
dtap PAGRES
15:20:55"2 msc sccp 54 1 49 1 27 6 CC
bmap 8 CICMD
15:20:55"8 bss sccp 49 1 55 1 15 4 DT1
bmap 1 CICMP
15:20:55"8 msc sccp 55 1 50 1 18 6 DT1
dtap 3 IDREQ
15:20:55"9 msc sccp 55 1 51 1 28 6 DT1
dtap 13 SETUP
15:20:56"5 bss sccp 51 1 56 1 26 4 DT1
dtap 11 IDRES
15:20:56"7 bss sccp 51 1 57 1 17 4 DT1
dtap 2 CCONF
15:20:56"9 msc sccp 57 1 52 1 32 6 DT1
bmap 18 ASREQ
15:20:57"9 bss sccp 52 1 58 1 15 4 DT1
bmap 1 ASCMP
15:20:58"0 bss sccp 52 1 59 1 17 4 DT1
dtap 2 ALERT
15:20:58"1 msc sccp 59 1 53 1 21 11 DT1
dtap 6 ALERT
15:21:00"8 bss sccp 53 1 60 1 17 4 DT1
dtap 2 CONNECT
15:21:00"8 msc sccp 60 1 54 1 17 6 DT1
dtap 2 CONACK
15:21:00"9 msc sccp 60 1 55 1 17 11 DT1
dtap 2 CONNECT
15:21:01"0 bss sccp 55 1 61 1 17 5 DT1
dtap 2 CONACK
TM3101EU01TM_0001
97
Siemens BSSAP
15:21:08"1 bss sccp 55 1 62 1 20 5 DT1

dtap 5 DISC
15:21:08"2 msc sccp 62 1 56 1 21 11 DT1
dtap 6 RELEAS
15:21:08"2 msc sccp 62 1 57 1 21 6 DT1
dtap 6 RELEAS
15:21:08"4 bss sccp 57 1 63 1 17 5 DT1
dtap 2 RELCMP
15:21:08"4 bss sccp 57 1 64 1 17 4 DT1
dtap 2 RELCMP
15:21:08"4 msc sccp 64 1 58 1 22 11 DT1
bmap 8 CLCMD
15:21:08"5 bss sccp 58 1 65 1 15 5 DT1
bmap 1 CLCMP
15:21:08"5 msc sccp 64 1 59 1 22 6 DT1
bmap 8 CLCMD
15:21:08"5 msc sccp 65 1 60 1 14 11 RLSD
15:21:08"5 bss sccp 59 1 66 1 15 4 DT1
bmap 1 CLCMP
15:21:08"5 bss sccp 60 1 67 1 12 5 RLC
15:21:08"5 msc sccp 67 1 61 1 14 6 RLSD
15:21:08"6 bss sccp 61 1 68 1 12 4 RLC
98 TM3101EU01TM_0001
BSSAP Siemens
K1103-trace in format long:
K1103 --- CCS No. 7 - Monitor , Date: 21.01.97 , Time: 10:50:44
HH:MM:ss"m FROM TYPE SIO DPC OPC SLS CIC NAME

15:20:51"6 bss sccp 83 3050 408 5 CR
ITU-T WHITE BOOK SCCP (sccp) Connection Request (CR)
----0011 Service Indicator SCCP
--00---- Sub-Service: Priority Spare/priority 0 (U.S.A. only)
10------ Sub-Service: Network Ind National message
******** Destination Point Code 3050
******** Originating Point Code 408
******** Signalling Link Selection 5
00000001 SCCP Message Type 0x1
******** Source Local Reference 0x202C00
----0010 Protocol Class Class 2
0000---- Spare
00000010 Ptr to Called address pa 2
00000100 Ptr to optional param. 4
Called address parameter
00000010 Parameter Length 2
-------0 Point Code Indicator PC absent
------1- Subsystem No. Indicator SSN present
--0000-- Global Title Indicator No global title included
-1------ Routing Indicator Route on DPC + Subsystem No.
0------- For national use 0
11111110 Subsystem number BSSAP
Data parameter
00001111 Parameter name Data
00011011 Parameter length 27
******** Data 00 19 57 05 05 01 00 01 00 1A 17 0F
05 24 71 02 03 08 08 29 26 20 26 00
00 00 40
00000000 Parameter name End of Optional Params
bmap CL3I
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) Complete layer 3 information (CL3I)
-------0 Discrimination bit D BSSMAP
0000000- Filler
00011001 Message Length 25
01010111 Message Type 0x57
Cell Identifier
00000101 IE Name Cell identifier
00000101 IE Length 5
----0001 Cell ID discriminator LAC/CI used to ident cell
******** LAC 1
******** CI 26
LAyer 3 Information
00010111 IE Name Layer 3 information
00001111 IE Length 15
******** L3 Message Contents 05 24 71 02 03 08 08 29 26 20 26 00
00 00 40
dtap 5 CMSREQ
MM Message Connection management message
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) CM service request (CMSREQ)
----0101 Protocol Discriminator mobility management msg
-000---- Transaction Id value TI value 0
0------- Transaction Id flag message sent from orig TI
--100100 Message Type 0x24
TM3101EU01TM_0001
99
Siemens BSSAP
-0------ Send Sequence Number 0

0------- Extension bit
----0001 CM Service type MOC est/pkt mode con estab
0111---- Key sequence no key available/reserved
Mobile Station Classmark 2
-----011 RF power capability Class 4
----0--- A5/1 algorithm supported Available
---0---- Spare
-00----- Revision level Reserved for phase 1
0------- Spare
-------0 Frequency capability MS does not support the ext. band G1
-----00- Spare
----1--- SM capability Present
--00---- SS Screening Indicator Phase 1
-0------ PS capability Not present
0------- Spare
Mobile IDentity
-----001 Type of identity IMSI
----1--- Odd/Even Indicator Odd no of digits
******** Identity digits 262026200000004
100 TM3101EU01TM_0001
BSSAP Siemens
15:20:51"7 msc sccp 83 408 3050 11 CC

ITU-T WHITE BOOK SCCP (sccp) Connection Confirm (CC)
******** Destination Local Ref. 0x202C00
******** Source Local Reference 0x402021
0000---- Spare
Data parameter
******** Data 00 08 53 07 02 06 00 0A 01 01
bmap CICMD
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) Cipher Mode Command (CICMD)
0000000- Filler
Layer 3 header INformation
00000111 IE Name Layer 3 header information
----0110 Protocol Discriminator radio resources management msg
0000---- Spare
-----000 Transaction Id value TI value 0
----0--- Transaction Id flag message sent from orig TI
0000---- Spare
Encryption Information
00001010 IE Name Encryption information
-------1 No encryption May be used
------0- GSM A5/1 Not used
-----0-- GSM A5/2 Not used
----0--- GSM A5/3 Not used
---0---- GSM A5/4 Not used
--0----- GSM A5/5 Not used
-0------ GSM A5/6 Not used
0------- GSM A5/7 Not used
TM3101EU01TM_0001
101
Siemens BSSAP
15:20:52"3 bss sccp 83 3050 408 5 DT1

ITU-T WHITE BOOK SCCP (sccp) Data Form 1 (DT1)
******** Destination Local Ref. 0x402021
-------0 Segment/reass M indicator No more data
0000000- Spare
00000001 Ptr to Data parameter 1
Data parameter
******** Data 00 01 55
bmap CICMP
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) Cipher Mode Complete (CICMP)
0000000- Filler
102 TM3101EU01TM_0001
BSSAP Siemens
15:20:52"3 msc sccp 83 408 3050 11 DT1

0000000- Spare
Data parameter
******** Data 01 00 03 05 18 02
dtap 5 IDREQ
MM Message Security message
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Identity request (IDREQ)
-------1 Discrimination bit D DTAP
0000000- Filler
-----000 SAPI Signalling
--000--- Spare
00------ Radio channel id fACCH or sDCCH
-----010 Type of identity IMEI
----0--- Spare
0000---- Spare
TM3101EU01TM_0001
103
Siemens BSSAP
15:20:52"5 bss sccp 83 3050 408 5 DT1

0000000- Spare
Data parameter
******** Data 01 00 0C 03 45 04 01 A0 5E 05 81 26
00 00 F7
dtap 3 SETUP
CC Message Call establishment message
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Setup (SETUP)
0000000- Filler
--000--- Spare
----0011 Protocol Discriminator Call/Connection control, CR SS
Bearer Capability
00000100 IE Name Bearer Capability
-----000 Info transfer capability Speech
----0--- Transfer mode Circuit mode
---0---- Coding standard GSM standardized coding
-01----- Radio channel requirement Full rate channel
1------- Extension bit No Extension
CaLleD party BCD number
01011110 IE Name CaLleD party BCD number
----0001 Number plan ISDN/telephony numbering plan
-000---- Type of number Unknown
******** Called party number 6200007
1111---- Filler
104 TM3101EU01TM_0001
BSSAP Siemens
15:20:52"6 msc sccp 83 408 3050 11 DT1

0000000- Spare
Data parameter
******** Data 01 00 02 83 02
dtap 3 CPROC
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Call proceeding (CPROC)
0000000- Filler
--000--- Spare
1------- Transaction Id flag message sent to orig TI
TM3101EU01TM_0001
105
Siemens BSSAP
15:20:52"6 msc sccp 83 408 3050 11 DT1

0000000- Spare
Data parameter
******** Data 00 12 01 0B 03 01 08 01 07 02 06 00
06 01 15 01 00 01 19 01
bmap ASREQ
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) ASSignment REQest (ASREQ)
0000000- Filler
Channel Type
00001011 IE Name Channel type
00000001 Speech/Data Indicator Speech
00001000 Channel Rate/Type Full rate TCH channel Bm
00000001 Speech Encoding Algorithm GSM speech algorithm Ver 1
0000---- Spare
0000---- Spare
PRIority
00000110 IE Name Priority
-------1 Preemption Vulnerab. Ind Might be prerempted
------0- Queueing allowed ind not allowed
--0101-- Priority level 5
-0------ Preemption Capability ind not allowed
0------- Spare
Circuit Identity Code
00000001 IE Name Circuit identity code
00000000 PCM Multiplex a-h 0
000----- PCM Multiplex i-k 0
---00001 Timeslot in use 1
Downlink DTX flag
00011001 IE Name Downlink DTX flag
-------1 DTX in downlink direction forbidden
0000000- Spare
106 TM3101EU01TM_0001
BSSAP Siemens
15:20:53"0 bss sccp 83 3050 408 5 DT1

0000000- Spare
Data parameter
******** Data 01 00 0B 05 19 08 4A 09 01 40 01 34
85 09
dtap 5 IDRES
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Identity response (IDRES)
0000000- Filler
--000--- Spare
Mobile IDentity
******** Identity digits 490100410435890
15:20:53"8 bss sccp 83 3050 408 5 DT1

0000000- Spare
Data parameter
******** Data 00 01 02
bmap ASCMP
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) ASSignment COMplete (ASCMP)
0000000- Filler
TM3101EU01TM_0001
107
Siemens BSSAP
15:20:54"1 msc sccp 83 408 3050 3 UDT

ITU-T WHITE BOOK SCCP (sccp) Unitdata (UDT)
0000---- Message Handling No special options
00000111 Ptr to Calling address p 7
-------1 Point Code Indicator PC present
******** Called Party SPC 408
00------ Spare
Calling address parameter
******** Calling Party SPC 3050
00------ Spare
Data parameter
******** Data 00 13 52 08 08 29 26 20 26 00 00 00
70 1A 06 04 62 F2 20 00 01
bmap PAGIN
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) Paging (PAGIN)
0000000- Filler
IMSI
00001000 IE Name IMSI
******** IMSI digits 262026200000007
Cell Identifier List
00011010 IE Name Cell identifier list
----0100 Cell ID Discriminator LAI used to ident cell
0000---- Spare
******** MCC number 262
1111---- Filler
----0000 MNC digit 1 0
0010---- MNC digit 2 2
******** LAC 1
108 TM3101EU01TM_0001
BSSAP Siemens
15:20:55"1 bss sccp 83 3050 408 4 CR

ITU-T WHITE BOOK SCCP (sccp) Connection Request (CR)
0000---- Spare
-------0 Point Code Indicator PC absent
Data parameter
******** Data 00 19 57 05 05 01 00 01 00 1A 17 0F
06 27 07 02 03 08 08 29 26 20 26 00
00 00 70
bmap CL3I
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) Complete layer 3 information (CL3I)
0000000- Filler
Cell Identifier
00000101 IE Name Cell identifier
----0001 Cell ID discriminator LAC/CI used to ident cell
******** LAC 1
******** CI 26
LAyer 3 Information
00010111 IE Name Layer 3 information
00001111 IE Length 15
******** L3 Message Contents 06 27 07 02 03 08 08 29 26 20 26 00
00 00 70
dtap 6 PAGRES
RR Message Paging message
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Paging response (PAGRES)
-0100111 Message Type 0x27
----0111 Key sequence no key available/reserved
0000---- Spare
Mobile Station Classmark 2
-----011 RF power capability Class 4
----0--- A5/1 algorithm supported Available
TM3101EU01TM_0001
109
Siemens BSSAP
---0---- Spare
-00----- Revision level Reserved for phase 1
0------- Spare
-------0 Frequency capability MS does not support the ext. band G1
-----00- Spare
----1--- SM capability Present
--00---- SS Screening Indicator Phase 1
-0------ PS capability Not present
0------- Spare
Mobile IDentity
******** Identity digits 262026200000007
15:20:55"2 msc sccp 83 408 3050 6 CC

ITU-T WHITE BOOK SCCP (sccp) Connection Confirm (CC)
0000---- Spare
Data parameter
******** Data 00 08 53 07 02 06 00 0A 01 01
bmap CICMD
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) Cipher Mode Command (CICMD)
0000000- Filler
0000---- Spare
0000---- Spare
Encryption Information
00001010 IE Name Encryption information
-------1 No encryption May be used
------0- GSM A5/1 Not used
-----0-- GSM A5/2 Not used
----0--- GSM A5/3 Not used
---0---- GSM A5/4 Not used
--0----- GSM A5/5 Not used
-0------ GSM A5/6 Not used
0------- GSM A5/7 Not used
110 TM3101EU01TM_0001
BSSAP Siemens
15:20:55"8 bss sccp 83 3050 408 4 DT1

0000000- Spare
Data parameter
******** Data 00 01 55
bmap CICMP
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) Cipher Mode Complete (CICMP)
0000000- Filler
15:20:55"8 msc sccp 83 408 3050 6 DT1

0000000- Spare
Data parameter
******** Data 01 00 03 05 18 02
dtap 5 IDREQ
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Identity request (IDREQ)
0000000- Filler
--000--- Spare
----0--- Spare
0000---- Spare
TM3101EU01TM_0001
111
Siemens BSSAP
15:20:55"9 msc sccp 83 408 3050 6 DT1

0000000- Spare
Data parameter
******** Data 01 00 0D 13 05 04 01 A0 1E 02 EA 83
7D 02 91 81
dtap 3 SETUP
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Setup (SETUP)
0000000- Filler
--000--- Spare
Bearer Capability
00000100 IE Name Bearer Capability
-----000 Info transfer capability Speech
----0--- Transfer mode Circuit mode
---0---- Coding standard GSM standardized coding
-01----- Radio channel requirement Full rate channel
Progress Indicator
00011110 IE Name Progress Indicator
----1010 Location NTW beyond interworking point
---0---- Spare
-11----- Coding standard Standard for the GSM PLMNS
-0000011 Progress description Origination address
High Layer Compatibility
01111101 IE Name High Layer Compatibility
------01 Pres. of protocol profile Highlayer protocol profile
---100-- Interpretation Highlayer characteristics ID
-00----- Coding standard Standardized coding
-0000001 High layer character. ID Telephony
112 TM3101EU01TM_0001
BSSAP Siemens
15:20:56"5 bss sccp 83 3050 408 4 DT1

0000000- Spare
Data parameter
******** Data 01 00 0B 05 19 08 4A 09 21 42 51 50
43 09
dtap 5 IDRES
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Identity response (IDRES)
0000000- Filler
--000--- Spare
Mobile IDentity
******** Identity digits 490122415053490
TM3101EU01TM_0001
113
Siemens BSSAP
15:20:56"7 bss sccp 83 3050 408 4 DT1

0000000- Spare
Data parameter
******** Data 01 00 02 93 48
dtap 3 CCONF
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Call confirmed (CCONF)
0000000- Filler
--000--- Spare
114 TM3101EU01TM_0001
BSSAP Siemens
15:20:56"9 msc sccp 83 408 3050 6 DT1

0000000- Spare
Data parameter
******** Data 00 12 01 0B 03 01 08 01 07 02 06 00
06 01 19 01 00 05 19 01
bmap ASREQ
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) ASSignment REQest (ASREQ)
0000000- Filler
Channel Type
00001011 IE Name Channel type
00000001 Speech/Data Indicator Speech
00001000 Channel Rate/Type Full rate TCH channel Bm
00000001 Speech Encoding Algorithm GSM speech algorithm Ver 1
0000---- Spare
0000---- Spare
PRIority
00000110 IE Name Priority
-------1 Preemption Vulnerab. Ind Might be prerempted
------0- Queueing allowed ind not allowed
--0110-- Priority level 6
-0------ Preemption Capability ind not allowed
0------- Spare
Circuit Identity Code
00000001 IE Name Circuit identity code
00000000 PCM Multiplex a-h 0
000----- PCM Multiplex i-k 0
---00101 Timeslot in use 5
Downlink DTX flag
00011001 IE Name Downlink DTX flag
-------1 DTX in downlink direction forbidden
0000000- Spare
TM3101EU01TM_0001
115
Siemens BSSAP
15:20:57"9 bss sccp 83 3050 408 4 DT1

0000000- Spare
Data parameter
******** Data 00 01 02
bmap ASCMP
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) ASSignment COMplete (ASCMP)
0000000- Filler
15:20:58"0 bss sccp 83 3050 408 4 DT1

0000000- Spare
Data parameter
******** Data 01 00 02 93 01
dtap 3 ALERT
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Alerting (ALERT)
0000000- Filler
--000--- Spare
116 TM3101EU01TM_0001
BSSAP Siemens
15:20:58"1 msc sccp 83 408 3050 11 DT1

0000000- Spare
Data parameter
******** Data 01 00 06 83 01 1E 02 EA 88
dtap 3 ALERT
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Alerting (ALERT)
0000000- Filler
--000--- Spare
Progress Indicator
00011110 IE Name Progress Indicator
----1010 Location NTW beyond interworking point
---0---- Spare
-0001000 Progress description Info/pattern now available
TM3101EU01TM_0001
117
Siemens BSSAP
15:21:00"8 bss sccp 83 3050 408 4 DT1

0000000- Spare
Data parameter
******** Data 01 00 02 93 47
dtap 3 CONNECT
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Connect (CONNECT)
0000000- Filler
--000--- Spare
118 TM3101EU01TM_0001
BSSAP Siemens
15:21:00"8 msc sccp 83 408 3050 6 DT1

0000000- Spare
Data parameter
******** Data 01 00 02 13 0F
dtap 3 CONACK
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Connect acknowledge (CONACK)
0000000- Filler
--000--- Spare
--001111 Message Type 0xF
TM3101EU01TM_0001
119
Siemens BSSAP
15:21:00"9 msc sccp 83 408 3050 11 DT1

0000000- Spare
Data parameter
******** Data 01 00 02 83 07
dtap 3 CONNECT
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Connect (CONNECT)
0000000- Filler
--000--- Spare
120 TM3101EU01TM_0001
BSSAP Siemens
15:21:01"0 bss sccp 83 3050 408 5 DT1

0000000- Spare
Data parameter
******** Data 01 00 02 03 4F
dtap 3 CONACK
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Connect acknowledge (CONACK)
0000000- Filler
--000--- Spare
--001111 Message Type 0xF
TM3101EU01TM_0001
121
Siemens BSSAP
15:21:08"1 bss sccp 83 3050 408 5 DT1

0000000- Spare
Data parameter
******** Data 01 00 05 03 25 02 E0 90
dtap 3 DISC
CC Message Call clearing message
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Disconnect (DISC)
0000000- Filler
--000--- Spare
Cause
----0000 Location User
---0---- Spare
-0010000 Cause value Normal call clearing
122 TM3101EU01TM_0001
BSSAP Siemens
15:21:08"2 msc sccp 83 408 3050 11 DT1

0000000- Spare
Data parameter
******** Data 01 00 06 83 2D 08 02 E0 90
dtap 3 RELEAS
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Release (RELEAS)
0000000- Filler
--000--- Spare
--101101 Message Type 0x2D
Cause
00001000 IE Name Cause
---0---- Spare
TM3101EU01TM_0001
123
Siemens BSSAP
15:21:08"2 msc sccp 83 408 3050 6 DT1

0000000- Spare
Data parameter
******** Data 01 00 06 13 2D 08 02 E0 90
dtap 3 RELEAS
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Release (RELEAS)
0000000- Filler
--000--- Spare
--101101 Message Type 0x2D
Cause
---0---- Spare
124 TM3101EU01TM_0001
BSSAP Siemens
15:21:08"4 bss sccp 83 3050 408 5 DT1

0000000- Spare
Data parameter
******** Data 01 00 02 03 6A
dtap 3 RELCMP
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Release complete (RELCMP)
0000000- Filler
--000--- Spare
--101010 Message Type 0x2A
TM3101EU01TM_0001
125
Siemens BSSAP
15:21:08"4 bss sccp 83 3050 408 4 DT1

0000000- Spare
Data parameter
******** Data 01 00 02 93 2A
dtap 3 RELCMP
E-GSM 04.08 (DTAP) Version 4.8.0 (dtap) Release complete (RELCMP)
0000000- Filler
--000--- Spare
--101010 Message Type 0x2A
126 TM3101EU01TM_0001
BSSAP Siemens
15:21:08"4 msc sccp 83 408 3050 11 DT1

0000000- Spare
Data parameter
******** Data 00 08 20 07 02 06 00 04 01 09
bmap CLCMD
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) CLeaR CoMmanD (CLCMD)
0000000- Filler
0000---- Spare
0000---- Spare
CAUse
-0001001 Cause value Call control
0------- Cause Extension No Extension
TM3101EU01TM_0001
127
Siemens BSSAP
15:21:08"5 bss sccp 83 3050 408 5 DT1

0000000- Spare
Data parameter
******** Data 00 01 21
bmap CLCMP
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) CleaR COMplete (CLCMP)
0000000- Filler
15:21:08"5 msc sccp 83 408 3050 6 DT1

0000000- Spare
Data parameter
******** Data 00 08 20 07 02 06 00 04 01 09
bmap CLCMD
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) CLeaR CoMmanD (CLCMD)
0000000- Filler
0000---- Spare
0000---- Spare
CAUse
-0001001 Cause value Call control
0------- Cause Extension No Extension
128 TM3101EU01TM_0001
BSSAP Siemens
15:21:08"5 msc sccp 83 408 3050 11 RLSD

ITU-T WHITE BOOK SCCP (sccp) Released (RLSD)
00000000 Release Cause End user originated
15:21:08"5 bss sccp 83 3050 408 4 DT1

0000000- Spare
Data parameter
******** Data 00 01 21
bmap CLCMP
E-GSM 08.08 (BSSMAP) Version 4.7.0 (bmap) CleaR COMplete (CLCMP)
0000000- Filler
15:21:08"5 bss sccp 83 3050 408 5 RLC

ITU-T WHITE BOOK SCCP (sccp) Release Complete (RLC)
******** Source Local Reference 0x202C00
TM3101EU01TM_0001
129
Siemens BSSAP
15:21:08"5 msc sccp 83 408 3050 6 RLSD

ITU-T WHITE BOOK SCCP (sccp) Released (RLSD)
00000000 Release Cause End user originated
15:21:08"6 bss sccp 83 3050 408 4 RLC

ITU-T WHITE BOOK SCCP (sccp) Release Complete (RLC)
130 TM3101EU01TM_0001
BSSAP Siemens
9. Evaluate the following BSSAP-message with the help of the GSM-

recommendation.
K1103 --- CCS No. 7 - Monitor , Date: 21.01.97 , Time: 15:20:54"1 msc
sccp 83 408 3050 3 UDT
ITU-T WHITE BOOK SCCP (sccp) Unitdata (UDT)
0000---- Message Handling No special options
00000111 Ptr to Calling address p 7
******** Called Party SPC 408
00------ Spare
Calling address parameter
******** Calling Party SPC 3050
00------ Spare
Data parameter
******** Data
00
16
52
08
TM3101EU01TM_0001
131
Siemens BSSAP
08
29
26
10
77
80
51
74
11
09
04
21
132 TM3101EU01TM_0001
BSSAP Siemens
D0
67
AF
1A
03
05
2C
78
TM3101EU01TM_0001
133
Siemens BSSAP
134 TM3101EU01TM_0001
BSSAP Siemens
6 Solution
TM3101EU01TM_0001
135
Siemens BSSAP
136 TM3101EU01TM_0001
BSSAP Siemens
Solution
1. Which user parts and which application parts appear at the A-interface?
User parts: only Signaling Connection Control Part (SCCP)
Application parts: Base Station System OAM Application Part (BSSOMAP)
and Base Station System Application Part (BSSAP).
2. How can it be distinguished whether a given message at the A-interface belongs

to the BSSOMAP, the BSSMAP or to the DTAP?
In the Called Party Address of the SCCP, the subsystems BSSOMAP and
BSSAP (= BSSMAP + DTAP) are distinguished.
If the subsystem is BSSAP, then the first byte of the "Data" parameter (the
Discrimination byte) distinguishes between BSSMAP and DTAP.
3. What is the difference between the message "Cipher Mode Command" at the A-
interface and the message with the same name at the air interface?
At the A-interface, the ciphering key Kc for the air interface is included, at
the air interface itself, it is not included.
4. Which BSSMAP procedure is used in the event of a failure to release possible

calls and to reach a well-defined initial status?
Reset
5. Intra-MSC-Handover: which BSSMAP procedures are executed between the

MSC and the old BSC, and which ones between the MSC and the new BSC?
MSC «old BSC: Handover required indication Handover execution
MSC « new BSC: Handover resource allocation Handover execution
6. On reception a message from the Mobile Station, how can the Base Station
recognize whether it has to evaluate the message by itself or whether it must
forward the message transparently (i.e. via DTAP or complete layer 3
information) to the MSC?
By the protocol discriminator: RR = evaluate by itself, possibly BSSMAP
MM or CM = forward transparently
TM3101EU01TM_0001
137
Siemens BSSAP
7. a) Is an identifier included with mandatory BSSMAP parameters?

b) Is a length indicator included with BSSMAP parameters of fixed length?
a) yes (exception: the message type)
b) no
138 TM3101EU01TM_0001
BSSAP Siemens
8. Use the K1103 to monitor a call flow at the A-interface.
Answer the following questions to printed K1103 traces:
k) Was there a repetition of any MSU (message signal unit) e.g. because of
check error during that call? By which values can you detect it?
l) How many SLS-values (signaling link selection) are used for that call (Give
as well the reasons for the number of SLS)?
m) Tell for every collected signaling message, if it belongs to MOC or MTC.
n) Find out the Local References of that call. Allocate them to the correct entity
and to MOC and MTC.
o) Write down the CICs of the user channels at the A-interface. In which
messages did you find them?
p) What are the SPCs for the MSC and BSS (in decimal format)?
q) Which values for IMSI are used for the mobile stations?
r) Write down the MSISDN for the called and for the calling party address. In
which message did you find that?
s) Find out the IMEI-values for both mobile stations. In which message did you
find that?
t) What is the release cause for that call? In which message did you find that?
TM3101EU01TM_0001
139
Siemens BSSAP
140 TM3101EU01TM_0001

04 Tm3101eu01tm 0001 Bssap

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

04 Tm3101eu01tm 0001 Bssap

Uploaded by

Copyright:

Available Formats

BSSAP Siemens

Fig. 1 Structure of the A-Interface

RR connection SCCP conn.

Fig. 2 Signaling Connections

2.1 BSSMAP Procedures

Procedure Class 0 Class 2

Cipher mode control X

Handover required indication X

Handover resource allocation X

Data link control for SAPI=/ 0 X

Handover candidate enquiry X

Fig. 3 BSSMAP procedures (GSM 08.08)

a) Set up of the SCCP connection by the BSS

b) Set up of the SCCP connection by the MSC

Fig. 4 Set up of the SCCP connection

DCCH RLSD (poss.with DTAP)

Fig. 5 Clear down of the SCCP connection

I (ASS.COMM.) DT 1 (Assign Request)

I (Ass.Compl.) DT 1 (Assign Complete)

The BSSAP release can have several reasons:

I (Channel Rel) DT1 (Clear Command)

a) Release for BSS causes

I (Channel Rel) DT1 (Clear Command)

Fig. 7 BSSAP release

I (Ciph. Comm.) DT 1 (Cipher Command)

Fig. 8 Cipher Mode Control

UI (Paging Req.) UDT (Paging)

SABM (Paging Resp.) CR (Complete L3 Info)

Handover comprises several BSSMAP procedures. We consider a Handover from

a) Handover required indication

UI (Mess. Rep.) DT1 (Handover Required)

DT1 (Handover Required)

b) Handover resource allocation

Fig. 10 Handover - Part 1

I (Hand. Comm.) DT1 (Handover Command)

I (Hand. Compl.) DT1 (Handover Complete)

DT1 (Clear Complete)

Fig. 11 Handover - Part 2

UDT (Block/ Circuit Group Block)

(CIC/ CIC- List, Cause)

UDT (Blocking Ackn. / Circuit Group Blocking Ackn.)

UDT (Unblock/ Circuit Group Unblock)

UDT (Unblocking Ackn./ Circuit Group Unblocking Ackn)

a) Reset by the BSC

UDT (Reset Acknowledge)

b) Reset by the MSC

UDT (Block / Circuit Group Block)

UDT (Block / Circuit Group Blocking Ackn.)

UDT (Reset Acknowledge)

2.2 Complete Sequences

SABM CR (Complete L3 Info)

I Authentication Request (RAND) CC

I Authentication Response (SRES) DT1

I(Ciph. Comm.) DT1 (Cipher Command)

I(Ciph. Compl.) DT1 (Ciph. Compl.)

I (Ass. Command) DT1 (Assign Request)

I (Ass. Complete) DT1 (Assign Complete)

Fig. 14 Mobile Originating Call (MOC)

UI (Paging Requ.) UDT (Paging)

I Authentication Request (RAND) CC

I Authentication Response (SRES) DT1

I(Ciph. Comm.) DT1 (Cipher Command)