Vous êtes sur la page 1sur 119

GSM 900/1800 BSS

Signalling Examples
Training Document

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

1 (119)

Signalling Examples

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia Telecommunications' customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be reproduced or transmitted in any
form or means without the prior written permission of Nokia Telecommunications. The
document has been prepared to be used by professional and properly trained personnel, and
the customer assumes full responsibility when using it. Nokia Telecommunications welcomes
customer comments as part of the process of continuous development and improvement of
the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding
but shall be defined in the agreement made between Nokia Telecommunications and the
customer. However, Nokia Telecommunications has made all reasonable efforts to ensure
that the instructions contained in the document are adequate and free of material errors and
omissions. Nokia Telecommunications will, if necessary, explain issues which may not be
covered by the document.
Nokia Telecommunications' liability for any errors in the document is limited to the
documentary correction of errors. Nokia Telecommunications WILL NOT BE RESPONSIBLE
IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES,
INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise
from the use of this document or the information in it.
This document and the product it describes are considered protected by copyright according
to the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this document may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright Nokia Telecommunications Oy 1999. All rights reserved.

2 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Contents

Contents
1
1.1
1.2
1.3
1.4
1.5

Signalling procedures............................................................................4
Radio access part.....................................................................................4
Establishment part ...................................................................................5
Location update or call setup ...................................................................5
Conversation part .....................................................................................6
Release after call or location update ........................................................6

2
2.1
2.2

Mobile call signalling .............................................................................7


Mobile Originated Call Signalling Example ..............................................8
Mobile Terminated Call Signalling Example...........................................41

3
3.1
3.2
3.3
3.4

Location update....................................................................................72
Normal location update ..........................................................................72
Periodic location update .........................................................................72
IMSI attach/detach location update ........................................................72
Location Update Signalling Example......................................................74

4
4.1
4.2
4.3

Handovers.............................................................................................92
Inter-Cell Handovers ..............................................................................92
Intra Cell Handovers...............................................................................94
Handover Signalling Examples ..............................................................95

5
5.1
5.2

BCCH and system information .........................................................113


System info type -messages ................................................................113
Information elements............................................................................116

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

3 (119)

Signalling Examples

Signalling procedures
The BSS signalling procedures are mainly related to actions and events
triggered by or for the MS. This document describes the signalling procedures,
the signalling flow and the messages used for the various services.
In this part the different phases of the signalling procedures are explained.

1.1

Radio access part


Before any signalling event (e.g. MOC or LUP) can take place the MS has to
make a radio access. This consists of three phases, the random access, the
channel activation and the immediate assignment.
The MS will send a RACH burst to the BTS when performing a location update,
originating a call, or answering a page in the case of an MTC. When a RACH
is received, the BTS requests a signalling channel from the BSC. The BSC will
activate an SDCCH in the BTS. The BSC then sends an Immediate Assignment
message (AGCH on Air interface) which will tell the mobile to use the assigned
SDCCH channel.
During radio access the communication is based on a Random Reference
Number produced by the MS. The MS will send a random number with the
RACH burst and the BSC will include this number in the Immediate
Assignment Command. The other RACH related parameters are described in
the BCCH description in this document.

4 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Signalling procedures

1.2

Establishment part
After the MS has started transmitting on the SDCCH it will send a signalling
connection establishment message, SABM. This message has to be
acknowledged by the BTS with a UA-message. Included in the SABM message
is the first MM-message describing the service required by the MS. Once the
signalling connection between the MS and the BTS has been established, and
the MS has requested a service, the SCCP connection-oriented signalling can
begin on the A interface.

1.3

Location update or call setup


After the signalling connections have been established the procedure varies
depending on the type of service requested.
Location Update

In the case of a Location Update Request, the MSC will check the MS identity
based on IMSI or TMSI and perform authentication. If this is successful,
ciphering is activated, after which the MS equipment identity can be checked.
With the Location Update Accepted message the MSC will allow the MS to
access the network and a new TMSI is allocated.
Call Setup

After the authentication, ciphering and TMSI reallocation procedures as


described above have been completed, the system has to assign a traffic channel
(TCH) to the MS. All of these procedures may vary, depending on the network
settings.
The setup of the call is divided into two parts, traffic channel assignment and
connection of the call. The traffic channel is taken into use during the
assignment procedure. The procedure starts with an Assignment Request and
can be split into three phases. The first phase consists of A-interface TCH
allocation and of Air interface TCH activation. The MSC will inform the BSC
which speech circuit will be used on the A-I/F and the BSC will activate a TCH
in the BTS for the MS.
The second phase is to assign the channel to the MS. When the MS switches to
the assigned TCH it will use FACCH mode (stealing mode) to send signalling.
The third phase is to start the signalling connection with SABM. After this, the
MS will use the assigned signalling connection, FACCH, to send an
Assignment Complete message to the MSC.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

5 (119)

Signalling Examples

Once the channels have been successfully allocated between the subscribers, the
second part of call setup takes place. This involves alerting the called party (the
phone rings) and connection (if the phone is answered).

1.4

Conversation part
The conversation part can start when the Connect Acknowledgement message is
received. During the conversation there will be measurement signalling between
the MS, BTS and BSC. If required the BTS can change the Timing Advance of
the MS and the BSC can make decisions on power level modifications or
handovers. It is also possible to send SMS messages on the SACCH.

1.5

Release after call or location update


When either the called or the calling party hangs up, the Disconnect message
will be sent. This initiates the release procedure, which can be divided into four
phases. Firstly, the call connection will be released and then the signalling
connections (FACCH and the associated SACCH) can be disconnected. When
the logical resources using the physical TCH have been cleared the RF channel
can be released. Last part of the release is to clear the SCCP connectionoriented signalling communication between MSC and BSC.
In the case of a Location Update the used resources will be cleared in the same
way. This will happen after the Location Update Accepted message is received
by the MS and the TMSI reallocation is completed. The RF resource used in
this case is an SDCCH with its associated SACCH.

6 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

Mobile call signalling


This section describes the signalling message flow of a mobile call. The
signalling message flow of a mobile originated call differs from that of a mobile
terminated call. The signalling flow will also be affected when the release of the
call is made by the calling or called party. The particular messages are
explained in the signalling examples below.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

7 (119)

Signalling Examples

2.1

Mobile Originated Call Signalling Example

VLR

MSC

BSC

BTS
2

C h a n n e l R e q u ir e d

3
5

P r oc es s A c c es s R e q u es t

12

A u th e n tic a te

19

DT1

C M S e r v ic e R e q u es t ( S D C C H )

SABM

10

E S T A B L IS H M E
PART

U A (S D C C H )

A u t h e n tic a tio n R e q u es t ( S D C C H )

14

A u th e n tic a tio n R es p o n s e ( S D C C H )

16
A u th e n tic a tio n R e s p o n s e

C ip h e rin g M o d e C o m m a n d

2 0 C ip h er in g M o d e C o m m a n d

15

21

C ip h er in g M o d e C o m m a n d ( S D C C H )

E n c r yp tio n C o m m a n d

C ip h er in g M o d e C o m p le t e ( S D C C H )

23
C ip h e rin g M o d e C o m p let e

DT1

Im m e d ia te A s s ig m e n t ( A G C H ) .

E s t ab lis h In d ic a tio n

D T 1 A u t h e n tic a tio n R e q u es t

DT1

17

S et C ip h er in g M o d e

CC

13

A u th e n tic a tio n R es p o n s e

18

11

R A D IO
ACC ESS
PART

Im m e d ia t e A s s ig m e n t C o m m a n d .

C M S e r v ic e R e q u es t
(C M S e r v ic e R e q u es t)

C h a n n e l A c tiva tio n
C h a n n e l A c tiva tio n A c k .

CR

MS
C h a n n e l R e q u es t ( R A C H )

22

2 4A c c es s R e q u e s t A c c e p t e d
25

F or w a rd N e w T M S I

2T6M S I R e a lloc a tio n C o m m a n d

30

TMSI Ack.

S en d I n f o f or O .G . C a ll
C om p le te C a ll

34

27

T M S I R e a lloc a tio n C o m m a n d ( S D C C H )
T M S I R e a lloc a tio n C o m p le te ( S D C C H )

29
T M S I R e a lloc a tio n C o m p le te
DT1

33

3 5 D T 1 C a ll P r oc e e d in g
3 7D T 1 A s s ig n m e n t R e q u es t

36
38

C all P r oc e e d in g ( S D C C H )
P h ys ic al C o n t e xt R e q u es t

P h ys ic al C o n te x t C o n f irm e d

40

C h a n n e l A c tiv a tio n
C h a n n e l A c tiva t io n A c k .

42

47

39
41

A s s ig n m e n t C o m m a n d ( S D C C H )
SABM ( FACCH )

44

E s t ab lis h In d ic a tio n

DT1

31

S et u p ( S D C C H )

32

S e tu p

43

UA ( FACCH )

45

A s s ig n m e n t C o m p le te ( F A C C H )

A s s ig n m e n t C o m p let e

48

C IP H E R ING ,
A U T H E N T IC A T
A N D C ALL SE T
PAR T

28

46

T C H S E IZ E D

R F C h a n n e l R e le a s e
R F C h a n n e l R e le a s eA c k .

50

DT1

52

DT1

49

A le rt in g

51

C onn ect

A ler tin g ( F A C C H )
C on n ec t ( F A C C H )

53
DT1

C onn ec tA c k .

54

C on n ec t A c k .( F A C C H )

55

M e a s u r e m e n t R e p o rt/R e s u lt

57

M e a s u r e m e n t R e p o rt ( S A C C H )

56
58

D is c o n n e c t ( F A C C H )
DT1

60

DT1

59

( R e le a s e )

61
DT1

64

( D is c o n n ec t )

DT1

( R e le a s e C o m p le te)

63

( C le a r C o m m a n d )

R ele a s e ( F A C C H )
R ele a s e C o m p le t e ( F A C C H )

65
66

73

8 (119)

R LSD
R LC

( C le a r C o m p lete )

72

62

C h a n n e l R ele as e ( F A C C H )

R E LE A S E B Y

D e ac tiv a t e S A C C H
D IS C ( F A C C H )
R ele a s e In d ic a tio n

70
DT1

CO NV ERS ATI
PART

69

68

67

UA ( FACCH )

R F C h a n n e l R e le a s e
R F C h a n n e l R e le a s eA c k .

71

( S C C P R e le a s e d )
( S C C P R e le as e dA c k .)

Nokia Telecommunications Oy

74

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

1.

Channel Request (MS to BTS;RACH)

The MS requests a channel by sending a random access burst on a RACH


channel to a BTS. The Channel request message contains the establishment
cause (3 bits) which can be response to paging, emergency call or 'other
services' e.g. Mobile Originated Call, Short Message Service or Location
Update. Additionally, this message contains a Random Reference, which
consists of 5 bits randomly selected by the MS. This random reference is used
to separate two MSs that are attempting to access the network at exactly the
same time.

2.

Channel Request (BTS to BSC;BTSM)

Upon receiving the Channel Request message from the MS, the BTS sends a
Channel-Required message to the BSC, which contains the information
contained in the channel request. To this, the BTS adds the TDMA frame
number and the Access Delay, which is the first timing advance estimate made
by the BTS.
CHAN RQD (CCh) T=0
Channel Nr
- uplink CCCH (RACH)
- timeslot : 0
Req. Ref
- MOC, SMS
- random reference : 2 (2h)
- N32 : 11 (bh)
- N26 : 14 (eh)
- N51 : 35 (23h)
Access Delay
- value : 0 (00h)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

9 (119)

Signalling Examples

3.

Channel Activation(BSC to BTS;BTSM)

After receiving the Channel-Required message, the BSC allocates an SDCCH channel for this call. It sends a Channel Activation message to the BTS
containing the following parameters: DTX control, channel description, mobile
allocation, maximum power levels of the MS and BTS and the timing advance
as calculated by the BSC.
CHAN. ACT. (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Act. Type
- immediate assignment procedure
Channel Mode
- length : 4
- downlink DTX not used, uplink DTX not used
- channel type : 03h 01h 00h
Channel Id
- length : 6
- SDCCH/8 subch 1
- timeslot : 1
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)
- frequencies included from CA :
BS Power
- power control level : 14 (eh)
MS Power
- power control level : 0 (0h)
Timing Adv.
- 0 (00h) (0 km)

10 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

4.

Channel Activation Ack (BTS to BSC;BTSM)

A response to the Channel Activation message. When the BTS has received this
message it starts to send and receive on the SACCH channel.
CHAN. ACT. ACK (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Frame Number
- N32 : 11 (bh)
- N26 : 24 (18h)
- N51 : 45 (2dh)

5.

Immediate Assignment Command


(BSC to BTS;BTSM;L3)

The BSC tells the BTS about the characteristics of the SDCCH channel to
use.
IMM.ASS. CMD (CCh) T=0
Channel Nr
- downlink CCCH (PCH + AGCH)
- timeslot : 0
Imm. Ass. Info
- value (hex) : 06 3F 00 49 03 5C E2
5C 6E 00 00
IMMEDIATE ASSIGNMENT (RR)
Page Mode
- normal paging
Channel Description
- SDCCH/8 subchannel 1
- timeslot : 1
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

11 (119)

Signalling Examples

Request Reference
- MOC, SMS
- random reference : 2 (2h)
- N32 : 11 (bh)
- N26 : 14 (eh)
- N51 : 35 (23h)
Timing Advance
- 0 (00h) (0 km)
Mobile Allocation
- frequencies included from CA :

6.

Immediate Assignment (BSC to MS;AGCH)

The BSC informs the MS via the BTS on the AGCH channel the characteristics
of the SDCCH channel to be used. Parameters include the page mode, SDCCH
channel description, SACCH, hopping indicator, the initial timing advance, and
mobile allocation (if frequency hopping applies). Additionally, the request
reference (random reference and the TDMA frame number) originally sent by
the MS is included to identify the relevant MS. The MS is then able to switch to
this SDCCH channel.

7.

CM Service Request (MS to BTS;SDCCH)

SABM (LAPDm) After receiving the IMMEDIATEASSIGNMENT message,


the MS tunes to the assigned SDCCH and starts to establish the signalling link
across the network. The MS sends the layer 2 SABM to the BTS on the
SDCCH. The SABM contains a layer 3 service request message indicating the
service type required to the network through the service request message.

8.

CM Service Request (BTS to BSC; L3)


Establish Indication (BTSM)

BTS acknowledges the Immediate Assignment Command by returning


Establish Indication message. Establish indication -message has two uses.
Firstly, when used in this phase it points out that from the BTS point of view,
the MS is now on the SDCCH-channel. Also the BTS identifies the link id as
the main signalling channel and adds received Layer 3 information into this
message. The BSC starts the handover algorithm.
EST. IND (RLL) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Link Id

12 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- main DCCH (FACCH or SDCCH)


- SAPI : 0
L3 Info
CM SERVICE REQUEST

(MM)

CM Service Type
- value : 1h
Ciphering Key Seq. Nr
- value : 2h
MS Classmark 2
- length : 2 (02h)
- revision level : reserved for phase 1
- encryption algorithm A5
- class 1, vehicle and portable
- frequency band 0
- short message capability present
Mobile Identity
- length : 5h
- TMSI : ca290100

9.

Complete L3 Information
(BSC to MSC;BSSMAP)
CM Service Request ( L3 )

The CM Service Request message is forwarded to the MSC


- BSSMAP (length : 22, 16h)
COMPLETE L3 INFORMATION
Cell Identifier
- length : 5 (05h)
- cell identified with LAC + CI
- location area code : 1369 (0559h)
- cell identifier : 174 (00AEh)
Layer 3 Information
-length : 12 (0Ch)
CM SERVICE REQUEST

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

(MM)

13 (119)

Signalling Examples

CM Service Type
- value : 1h
Ciphering Key Seq. Nr
- value : 2h
MS Classmark 2
- length : 2 (02h)
- revision level : reserved for phase 1
- encryption algorithm A5
- class 1, vehicle and portable
- frequency band 0
- short message capability present
Mobile Identity
- length : 5h
- TMSI : ca290100

10.

UA (BTS to MS;SDCCH LAPDm)

The BTS acknowledges the SABM sent by the MS.

11.

Process Access Request (MSC to VLR;CCS7

MSC forwards MS's request for access management from


VLR by Process Access Request message.

12.

Authentication (VLR to MSC;CCS7)

VLR initiates authentication request by sending an Authenticate


message to MSC.

13.

Authentication Request
(MSC to BSC ; L3)

The network sends this message to the mobile to initiate the


authentication of the mobile station identity. The mobile uses the RAND
as an input to the authentication algorithm to calculate the response,
SRES.
- DTAP (length : 19, 13h)
- SAPI : 0, main DCCH is used
AUTHENTICATION REQ

(MM)

Ciphering Key Seq. Nr

14 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- value : 2h
Auth. Parameter RAND
741D0912FA6493F91D8AC833ACA2075D

14.

Authentication Request
(BSC to BTS ;BTSM L3)
(BTS to MS ; SDCCH L3)

DATA REQ (RLL) T=1


Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
AUTHENTICATION REQ

(MM)

Ciphering Key Seq. Nr


- value : 2h
Auth. Parameter RAND
741D0912FA6493F91D8AC833ACA2075D
This element is used to identify a previously calculated and stored ciphering key
(Kc) in the mobile. The mobile stores this sequence number it received from the
network with the corresponding Kc.

15.

Authentication Response
(MS to BTS;SDCCH L3)
(BTS to BSC; BTSM L3)

The MS responds to the Authentication Request with the Signed Response


SRES. There are two algorithms used in the Authentication procedure, A3 and
A8. In the MS, these algorithms are stored on the SIM card, along with a 32digit key called Ki. The same information can be found in the Authentication
Centre (AuC). When the network requests MS Authentication, the AuC/VLR
sends a 32 digit RANDom Number to the MS. The MS calculates the Signed
Response (SRES) and sends it to the VLR. The VLR then compares the MSs
SRES with the AuCs SRES and if they are the same, the call set-up can
continue.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

15 (119)

Signalling Examples

Note
The first 8 digits of the Ki are used for Authentication and SRES calculation,
the other 24 are reserved for Ciphering Key (Kc) calculation.

DATA IND (RLL) T=1


Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
AUTHENTICATION RSP

(MM)

Auth. Parameter SRES : 741C0B11

16.

Authentication Response

(BSC to MSC; L3)


The BSC forwards the SRES to the VLR.
- DTAP (length : 6, 06h)
- SAPI : 0, main DCCH is used
AUTHENTICATION RSP

(MM)

Auth. Parameter SRES : 741C0B11

17.

Authentication Response (MSC to VLR)

MSC sends a positive response to Authenticate message.

18.

SET_CIPHERING_MODE

VLR sends MSC Set Ciphering Mode message that is used for changing MSBTS connection ciphering status.

19.

Cipher Mode Command (MSC to BSC;BSSMAP)

The MSC uses this command, which includes Kc to initiate ciphering if the
function is enabled.
- BSSMAP (length : 16, 10h)
CIPHER MODE COMMAND

16 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

L3 Header Information
- length : 2 (02h)
- protocol discr. : Radio Resources
- transaction id. : 0 (0h)
- message send from originating side
Encryption Information
- length : 9 (09h)
- GSM user data encr. v. 1
- ciphering key, length : 8 (08h)
FE 61 95 FE E5 73 32 C8
-----------------------------------------------------------------------------------------------Layer 3 Header Information
This element is used to supply the BSS with the necessary information in order
to carry the layer 3 messages to the mobile over the radio interface.
L3 Header Information

length : d (xh)

protocol discriminator pd text

transaction identifier : d (xh)

message sent dir text originating side

Protocol discriminator
value

pd text

3h

Call Control

5h

Mobility Management

6h

Radio Resources

9h

SMS with call

Bh

SMS wthiout call

Fh

GSM test procedures

others

Unknown protocol discriminator : d (xh)

The dir text is replaced with "to", if the TI flag is set to one. Otherwise "from" is
displayed.
Encryption information
This element carries the user data encryption information necessary to control
the encryption equipment in the BSS.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

17 (119)

Signalling Examples

-----------------------------------------------------------------------------------------------Encryption information

length : d (xh)

algorithm id text

ciphering key, length : d (xh)


xx xx xx xx xx xx xx xx

Algorithm idetifier
Phase 1:
Value

algorithm id text

no encryption required

GSM encryption version 1

others

Unknown algorithm id : d (xh)

Bit No

algorithm id text

no encryption required

GSM user data encryption version 1 (A%/1)

GSM A5/2

GSM A5/3

GSM A5/4

GSM A5/5

GSM A5/6

GSM A5/7

Phase 2:

The chipering key bytes shall be displayed in hex in the order they apper in the
information element

20.

Ciphering Mode Command (BSC to BTS;L3)


Establishment Command (BTSM)

The BSC stores the Encryption information and forwards the command to the
BTS. If the BTS software contains the algorithm specified by the MSC it can
start ciphering, otherwise it sends a reject message back to the MSC.
ENCR. CMD (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Encr. Info

18 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- lentgh : 9
- GSM A5/1
- ciphering key : FE 61 95 FE E5 73
32 C8
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CIPH. MODE COMMAND (RR)
Cipher Mode Setting
- start ciphering

21.

Ciphering Mode Command (BTS to MS;SDCCH)

The BTS commands the MS to start ciphering (whether required or not) and
starts receiving in the ciphered mode.

22.

Ciphering Mode Complete

(MS to BTS to BSC;SDCCH BTSM L3)


DATA IND (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CIPH. MODE COMPLETE (RR)
The MS acknowledges the ciphering command in the specified cipher mode.
This message may include the IMEI.(for phase 2)

23.

Cipher Mode Complete

(BSC to MSC;BSSMAP)
The BSC forwards the cipher response to the MSC.
- BSSMAP (length : 1, 01h)
CIPHER MODE COMPLETE

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

19 (119)

Signalling Examples

24.

Access Request Accept (MSC to VLR;CCS7)

VLR sends a positive acknowledge to Process Access Request message.

25.

Forward New TMSI (VLR to MSC;CCS7)

VLR requests MSC to perform TMSI reallocation.

25+. Identity Request (MSC to BSC to BTS to MS)


- DTAP (length : 3, 03h)
- SAPI : 0, main DCCH is used
IDENTITY REQUEST

(MM)

Identity Type

25++.

Identity Response(MS to BTS to BSC to MSC)

DATA IND (RLL) T=1


Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
IDENTITY RESPONSE

(MM)

Mobile Identity
- length : 8h
- IMEI : 495000100676140

26.

TMSI Reallocation Command


(MSC to BSC; L3)

The purpose of the TMSI reallocation procedure is to provide identity


confidentiality. Usually the TMSI reallocation is performed at least at each
change of location area. MSC initiates the TMSI reallocation procedure by
sending TMSI Reallocation command message to the MS. TMSI Reallocation
Command message contains a new combination of TMSI and LAI allocated by
the network or a LAI and the IMSI if the used TMSI shall be deleted. Usually
the TMSI Reallocation Command message is sent to the MS by using a RR
connection in ciphered mode.
- DTAP (length : 13, 0Dh)

20 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- SAPI : 0, main DCCH is used


TMSI REALLOC COMMAND (MM)
Location Area Id.
- MCC : 262
- MNC : 09
- LAC : 1369 (559h)
Mobile Identity
- length : 5h
- TMSI : ca2a0100

27.

TMSI Reallocation Command


(BSC to BTS to MS;BTSM SDCCH L3)

DATA REQ (RLL) T=1


Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
TMSI REALLOC COMMAND (MM)
Location Area Id.
- MCC : 262
- MNC : 09
- LAC : 1369 (559h)
Mobile Identity
- length : 5h
- TMSI : ca2a0100

---------------------------------------------------------------------------------------Location Area Identification


The purpose of this element is to uniquely idetify a location area withn GSM
network. This information is broadcast on the BCCH to all mobiles. Mobiles
use this information to decide when there is a need to update the location
information of that mobile to the network.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

21 (119)

Signalling Examples

Location Area Id.

MCC : ddd

MNC : dd

LAC : d (xh)

-----------------------------------------------------------------------------------------------Mobile Identity

length : d (xh)

identity text : dddd

Type of identity
value

identy text

no identity

IMSI

IMEI

IMEISV

TIMSI

other

Unknown identity type : d (xh)

If the number of digits is even, the upper nibble of the last octet is then
interpreted as spare bits. In IMSI, they must be set to one.

28.

TMSI Reallocation Complete


(MT to BTS to BSC;SDCCH BTSM L3)

DATA IND (RLL) T=1


Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
TIMSI REALLOC COMP. (mm)
When the MS receives the TMSI Reallocation Command message, it stores the
LAI in the SIM. If the received identity is the IMSI of the MS, it deletes any
previously stored TMSI. If the received identity is a TMSI, the MS stores it in

22 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

the SIM. In both cases the MS send a TMSI Reallocation Complete message to
the network.

29.

TMSI Reallocation Complete


(BSC to MSC ; L3)

TMSI Reallocation Complete message is forwarded to the MSC.


- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
TMSI REALLOC COMPL. (MM)

30.

TMSI Ack (MSC to VLR;CCS7)

MSC sends VLR a positive response to reallocation of TMSI.

31.

Setup (MS to BTS to BSC ;SDCCH BTSM L3)

After authentication, Identification and Ciphering, the MS is on the SDCCH


channel and ready to start real call setup signalling. The MS sends a Setup
message to the BSC to be forwarded to the MSC
DATA IND (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
SETUP

(CC)
Bearer Capability
- length : 1 (1h)
- info xfer cap : speech
- xfer mode : circuit
- coding std : GSM standardized
- radio ch req: full rate ch required
Called Party BCD Nr
- nr type : 0
- nr plan : 1
- nr : 01772000001

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

23 (119)

Signalling Examples

32.

Setup (BSC to MSC ; L3)

- DTAP (length : 14, 0Eh)


- SAPI : 0, main DCCH is used
SETUP

(CC)
Bearer Capability
- length : 1 (1h)
- info xfer cap : speech
- xfer mode : circuit
- coding std : GSM standardized
- radio ch req: full rate ch required
Called Party BCD Nr
- nr type : 0
- nr plan : 1

- nr : 01772000001
-----------------------------------------------------------------------------------------------Called Party BCD number
This element contains the called party BCD number. In a normal call, this
element contains the dialled digits.
Called Party Number

nr type : d

nr plan : d

nr ddddddddddddddd

The meaning of different values for type of number is:


value

type of number

Unknown

international

national

network specific

dedicate PAD access

Other values are reserved.


The meaning of different values for numbering plan is:
value

24 (119)

numpering plan

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

Unknown

ISDN/telephony

data (X.121)

telex (F.69)

national

private

Other values are reserved.


The digits of the party number are displayed in the order as they apper in the
message. Digits from 0 to 9 are displayed as themselves. For other digits the
following interpretation shall be used:

33.

Ah

':'

Bh

';'

Ch

'<'

Dh

'='

Eh

'>'

Fh

'?', endmark.

Send information for Originated call


(MSC to VLR;CCS7)

VLR requests for retrieval of call data.


34.

Complete call (VLR to MSC ;CCS7)

Call completion acknowledged by VLR for MOC.

35.

Call Proceeding (MSC to BSC ; L3)

- DTAP (length : 2, 02h)


- SAPI : 0, main DCCH is used
CALL PROCEEDING (CC)
The MSC responds to the Setup message.

36.

Call Proceeding
(BSC to BTS to MS;BTSM SDCCH L3)

DATA REQ (RLL) T=1


Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

25 (119)

Signalling Examples

- SAPI : 0
L3 Info
CALL PROCEEDING

37.

(CC)

Assignment Request (MSC to BSC;BSSMAP)

- BSSMAP (length : 16, 10h)


ASSIGNMENT REQUEST
Channel Type
- length : 3 (03h)
- speech
- TCH/FS
- GSM speech encoding algorithm version 1
L3 Header Information
- length : 2 (02h)
- protocol discr. : Radio Resources
- transaction id. : 0 (0h)
- message send from originating side
Priority
- length : 1 (01h)
- priority level 3 (3h)
- queueing allowed
- preemption vulnerability indi not allowed
Circuit Identity Code
- pcm multiplex : 1 (001h)
- pcm timeslot : 1 (01h)
This message starts the TCH allocation. In the A- interface, MSC is the master
and it hunts the circuit used for this call through the A- interface. This message
can contain some optional information according to GSM-recommendations.
This optional information is: Priority of the call, Downlink Discontinuous
Transmission (DTX), Radio channel identity and Interference band to use.

26 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

38.

Physical Context Request(BSC to BTS ;BTSM)

By using this message, the BSC interrogates the actual timing advance from the
BTS in order to start TCH allocation through the Abis -interface.
PHYS. CONTEXT REQ (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1

39.

Physical Context Confirm (BTS to BSC ;BTSM)

BSC receives the timing advance information from the BTS and starts TCH
reservation and allocation. This reservation & allocation procedure is similar to
the case of the SDCCH -channel.
PHYS. CONTEXT CNF (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
BS Power
- power control level : 14 (eh)
MS Power
- power control level : 0 (0h)
Timing Adv.
- 0 (00h) (0 km

40.

Channel Activation (BSC to BTS;BTSM)

After the BSC's internal channel reservation and allocation, it activates the TCH
by sending this message towards the BTS. Contents: channel number, activation
type, channel mode (DTX/No DTX), channel type (Speech / data: if speech,
then GSM encoding algorithm included, if data, then information about
transparency or non-transparency of the channel and data rate), channel identity,
encryption information if received, BS & MS power levels as received in
'Physical context confirm' -message and timing advance.
CHAN. ACT. (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 6

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

27 (119)

Signalling Examples

Act. Type
- normal assignment procedure
Channel Mode
- length : 4
- downlink DTX not used, uplink DTX not used
- channel type : 01h 08h 01h
Channel Id
- length : 6
- full rate TCH
- timeslot : 6
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)
- frequencies included from CA :
Encr. Info
- lentgh : 9
- GSM A5/1
- ciphering key : FE 61 95 FE E5 73
32 C8
BS Power
- power control level : 14 (eh)
MS Power
- power control level : 0 (0h)
Timing Adv.
- 0 (00h) (0 km)

41.

Channel Activation Ack (BTS to BSC; BTSM)

The BTS returns current TDMA frame number and after that the TCH is
activated through the Abis-interface
CHAN. ACT. ACK (DCh) T=0
Channel Nr
- full rate TCH

28 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- timeslot : 6
Frame Number
- N32 : 12 (ch)
- N26 : 14 (eh)
- N51 : 46 (2eh)

42.

Assignment Command
(BSC to BTS to MS;BTSM SDCCH L3)

The BTS delivers received information further on towards the MS. Contents:
channel description, power levels, cell channel description, channel mode (Full /
Half) and mobile allocation.
DATA REQ (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
ASSIGNMENT COMMAND (RR)
Channel Description
- full rate TCH
- timeslot : 6
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)
Power Command
- power level of MS : 0
Channel Mode
- speech FR or HR version 1

43.

SABM (MS to BTS ;FACCH)

This is a Layer 2 message.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

29 (119)

Signalling Examples

44.

Establish Indication (BTS to BSC ;BTSM)

Establish indication -message has two uses. Firstly, when used this phase it
points out that from the point of view of the BTS, the MS is now on the
FACCH-channel. Thus, the BTS sends information back to the BSC that the
MS is now on this kind of FACCH-channel which description is like this etc.
Also the BTS identifies the link = main signalling channel and adds received
Layer 3 information into this message. This layer 3 information is coming from
the MS, of course. (L3 information is optional)
EST. IND (RLL) T=0
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0

45.

UA (BTS to MS ;FACCH)

UA is normal Level 2 acknowledgement when setting up the Layer 2 level link


in LAPDm-protocol.

46.

Assignment Complete

(MS to BTS to BSC;FACCH BTSM L3)


The MS informs it is now on the TCH and everything is OK.
DATA IND (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
ASSIGNMENT COMPLETE (RR)
RR Cause
- normal

30 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

47.

Assignment Complete (BSC to MSC ; L3)

The BSS acknowledges the channel seizure to the MSC.


- BSSMAP (length : 3, 03h)
ASSIGNMENT COMPLETE
RR Cause
- norma

48.

RF Channel Release (BSC to BTS ;BTSM)

When MS has informed the network it is in the TCH, there is no need to use the
SDCCH -channel for this call setup any more. By RF Channel Release
procedure it is released.
RF CHANNEL REL. (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1

49.

RF Channel Release Ack.(BTS to BSC ;BTSM)

The BTS acknowledges the RF Channel Release message.


RF CH. REL. ACK (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1
(Paging the other end;MS power control; ccch load)

50.

Alerting (MSC to BSC ; L3)

This message is sent to the originating side during call set up to inform that the
alerting of the called party has been started.
- DTAP (length : 6, 06h)
- SAPI : 0, main DCCH is used
ALERTING

(CC)

Progress Indicator
- value (hex) :E0 88

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

31 (119)

Signalling Examples

51.

Alerting (BSC to BTS to MS ;BTSM FACCH L3)

The MSC informs the MS that the called subscriber has been alerted. This
message can contain also so-called progress indicator IE, which tells that there
are in-band announcements or other similar information to be received. In brief,
this means that the connection is not end-to-end ISDN connection. If the MS
receives this element, it shall through-connect the speech path. In case it is not,
the MS generates ringing tone in itself. This information can also be transferred
in a Progress message.
DATA REQ (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
ALERTING

(CC)

Progress Indicator
- value (hex) :E0 88

52.

Connect (MSC to BSC ; L3)

The MSC sends a Connect message to the MS via the BSS. This message
indicates the MS that a connection has been established through the network.
- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
CONNECT

53.

(CC)

Connect (BSC to BTS to MS;BTSM FACCH L3)

When the MS receives a Connect message, it attaches the user connection to the
radio path, returns a Connect Acknowledge message, stops any locally
generated alerting indication (if applied) and enters the "active" state.
DATA REQ (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id

32 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- main DCCH (FACCH or SDCCH)


- SAPI : 0
L3 Info
CONNECT

54.

(CC)

Connect Ack.

(MS to BTS to BSC;FACCH BTSM L3)


By using this message, the MS informs the MSC that the MS is now in the
"active" state.
DATA IND (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CONNECT ACKNOWLEDGE

55.

(CC)

Connect Ack. (BSC to MSC ; L3)

The message is forwarded to the MSC.


- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
CONNECT ACKNOWLEDGE
(CC)
This is the point at which speech is connected & conversation starts.

56.

Measurement Report (MS to BTS ;SACCH L3)

When call is on, the MS sends measurement report concerning mainly the
quality of the speech connection two times per second.

57.

Measurement Report (BTS to BSC ;BTSM L3)

If these measurement reports are pre-processed in the BTS then measurement


results are sent towards the BSC. If the is no pre-processing in the BTS, then
measurement reports are sent. In this phase, Nokia BTS does not make any preprocessing.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

33 (119)

Signalling Examples

MEAS. RES. (DCh) T=0


Channel Nr
- full rate TCH
- timeslot : 6
Meas.Res. Nr
- value : 42 (2ah)
Uplink Meas.
- length : 3 (3h)
- downlink DTX not used
- rxlev_full : 43 (-68 - -67 dBm)
- rxlev_sub : 43 (-68 - -67 dBm)
- rxqual_full : 0
- rxqual_sub : 0
BS Power
- power control level : 14 (eh)
L1 Info
- MS power control level : 1 (1h)
- actual TA : 0 (00h) (0 km)
L3 Info
MEASUREMENT REPORT (RR)
Measurement Results
- BCCH allocation sequence number : 0
- DTX was not used
- serving cell rxlev_full : 31 (-80 - -79 dBm)
- serving cell rxlev_sub : 32 (-79 - -78 dBm)
- measurement results are valid
- serving cell rxqual_full : 0
- serving cell rxqual_sub : 0
- no neighbour cell meas results
Conversation

34 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

58.

Disconnect
( MS to BTS to BSC;BTSM FACCH L3)

This request is sent by MS. Contents: clear end-to-end connection. This


message stops the charging concerning this call connection.
DATA REQ (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
DISCONNECT

(CC)

Cause
- length : 2
- coding standard : GSM
- location : user
- normal event
- cause: normal clearing
Progress Indicator
- value (hex) :E0 88

59.

Disconnect (BSC to MSC ; L3)

The Disconnect message is forwarded to the MSC.


- DTAP (length : 9, 09h)
- SAPI : 0, main DCCH is used
DISCONNECT

(CC)

Cause
- length : 2
- coding standard : GSM
- location : user
- normal event
- cause: normal clearing

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

35 (119)

Signalling Examples

Progress Indicator
- value (hex) :E0 88

60.

Release (MSC to BSC ; L3)

Actual release is coming from the MSC; real call is just about to end.
- DTAP (length : 6, 06h)
- SAPI : 0, main DCCH is used
RELEASE

(CC)
Cause
- length : 2
- coding standard : GSM
- location : user
- normal event
- cause: normal clearing

61.

Release ( BSC to BTS to MS;BTSM L3)

The Release message is forwarded to the MS.


DATA IND (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
RELEASE

(CC)
Cause
- length : 2
- coding standard : GSM
- location : user
- normal event
- cause: normal clearing

36 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

62.

Release Complete

( MS to BTS to BSC ;BTSM FACCH L3)


MS informs that it will release the transaction identifier, i.e. call release is
proceeding.
DATA REQ (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
RELEASE COMPLETE

63.

(CC)

Release Complete (BSC to MSC ; L3)

The Release Complete message is forwarded to the MSC.


- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
RELEASE COMPLETE

64.

(CC)

Clear Command (MSC to BSC;BSSMAP)

This message is coming from the MSC and releases the associated dedicated
resources, i.e. BSSAP connection concerning this call.
- BSSMAP (length : 1, 01h)
CLEAR COMPLETE

65.

Channel Release

(BSC to BTS to MS ;BTSM FACCH L3)


Deactivation command of the used TCH. This is sent by the BSC towards the
MS. Quite often this is also called '3rd layer disconnection'. In case of normal
call setup case, the release cause is 'normal'.
DATA REQ (RLL) T=1
Channel Nr

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

37 (119)

Signalling Examples

- full rate TCH


- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CHANNEL RELEASE

(RR)

RR Cause
- normal

66.

Deactivate SACCH (BSC to BTS;BTSM)

By sending this message to downlink direction, the BSC inhibits system


information message sending towards the MS. In fact, there is no use to
send/receive any information in the SACCH channel any more, so it will be
deactivated.
DEACT. SACCH (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 6

67.

DISC (MS to BTS;FACCH )

The MS send Layer 2 frame DISConnect to uplink direction in order to inform


the BTS it is stopping the traffic in the TCH/FACCH.

68.

UA (BTS to MS ;FACCH)

The BTS acknowledges DISC -frame. Consequences: the MS starts to listen


BCCH -channel again and all the Air interface resources are released.

69.

Release Indication(BTS to BSC ;BTSM)

The BTS informs the BSC that the MS has no more any dedicated Air interface
resources (i.e. TCH/FACCH) in use.
REL IND (RLL) T=0
Channel Nr
- full rate TCH
- timeslot : 6
Link Id

38 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- main DCCH (FACCH or SDCCH)


- SAPI : 0

70.

RF Channel Release (BSC to BTS ;BTSM)

The BSC tells the BTS to release the rest of the radio resources.
RF CHANNEL REL. (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 6

71.

RF Channel Release Ack.

All the rest of the radio resources have been released; BTS send an
acknowledgement to BSC. These radio resources are TCH/FACCH and
SACCH.
RF CH. REL. ACK (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 6

72.

Clear Complete (BSC to MSC ; BSSMAP)

This is acknowledgement to the message SCCP Data (Clear Command). Now


the BSC informs the MSC that all radio resources related to this call are
released.
- BSSMAP (length : 1, 01h)
CLEAR COMPLETE

73.

SCCP Released (MSC to BSC;SCCP)

When all radio resources are released, BSSAP connection concerning this call is
not needed any more. This message tells the BSC to release this SCCP
connection. The message is sent as RLSD message.
RLSD - RELEASED
Routing Label
- DPC : 432 (01B0h) OPC : 12600 (3138h)
- SLC : 11 (0Bh)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

39 (119)

Signalling Examples

Destination Local Reference


- 0D8056h
Source Local Reference
- 4B814Ch
Release Cause
- SCCP user originated

74.

SCCP Released Ack. (BSC to MSC ;SCCP)

BSC informs MSC that now the dedicated SCCP connection concerning this
call is released. The message is sent as RLC message.
RLC - RELEASE COMPLETE
Routing Label
- DPC : 12600 (3138h) OPC : 432 (01B0h)
- SLC : 13 (0Dh)
Destination Local Reference
- 4B814Ch
Source Local Reference
- 0D8056h

40 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

2.2

Mobile Terminated Call Signalling Example

VLR

MSC

BSC

BTS

MS

Send info for IC Call


PAGING
PART

Page MS

UDT Paging

Paging Command

Channel Activation
Immediate

Assigment

Command.

12

CR (Paging Response)
Authenticate

14

15
17

Immediate

Assigment

( AGCH ).

SABM Paging Response(SDCCH)

11

Establish Indication

DT1 Authentication Request

RADIO
ACCESS
PART

Ack .

PagingResponse
CC

Channel Activation

Process Access Request

Paging Request
Channel Request ( RACH )

Channel Required

13

10
UA (SDCCH)

ESTABLISHMENT
PART

Authentication Request ( SDCCH )


Authentication Response ( SDCCH )

16

DT1 Authentication Response


Authentication Response
Set Ciphering Mode

18

DT1 Ciphering Mode Command

19

DT1Ciphering Mode Complete

20
Ciphering Mode Command(SDCCH)

Encryption Command

22

21

Ciphering Mode Complete ( SDCCH )

Access Request Accepted


Forward New TMSI

TMSI

23TMSI Reallocation Command

27

DT1

Setup

28

Assignment Request

Setup ( SDCCH )

Physical Context Confirmed

36

33

Channel Activation
Channel Activation

Ack .

DT1 Assignment Complete

41

38

43

58

55

50
52

Release ( FACCH )

RELEASE BY MS

Release Complete ( FACCH )

57

CONVERSATION
PART

56

DT1 Clear Command

59
60

DT1

Clear Complete

Channel Release (FACCH)


Deactivate SACCH
DISC ( FACCH )

66

64

RF Channel Release
RF Channel Release

63

62

61

UA ( FACCH )

65

Ack .

RLSD ( SCCP Released )


RLC ( SCCP Released

NTC CTXX 0677


Issue 4.0 en

Measurement Report ( SACCH )

51

53

Release Indication

67

46

Disconnect ( FACCH )

DT1 Release

DT1 Release Complete

44

Connect Ack .( FACCH )

49

Measurement Report/Result

54

Alerting ( FACCH )

Connect ( FACCH )

47

DT1 Disconnect

40

Ack .

45
Ack .

TCH SEIZED

UA ( FACCH )

RF Channel Release
RF Channel Release

DT1 Connect

37

SABM ( FACCH )

39

Assignment Complete (FACCH)

42

48

35

Assignment Command ( SDCCH )


Establish Indication

DT1 Connect

29

32Physical Context Request


34

DT1 Alerting

25

Call Confirmed ( SDCCH )

30

DT1 Call Confirmed

31 DT1

TMSI Reallocation Command ( SDCCH )


TMSI Reallocation Complete ( SDCCH )

TMSI Reallocation Complete26

Ack .

Complete IC

24

CIPHERING,
AUTHENTICATIO
AND CALL SETUP
N
PART

Nokia Telecommunications Oy

68

Ack .)

41 (119)

Signalling Examples

1.

Paging (MSC to BSC ;BSSMAP)

This message is sent by MSC when it has found out the called MS is
somewhere under him (= MSC recognises this is a GSM_END -call). This
message contains mainly four kind of information: message type, IMSI of the
called subscriber, TMSI of the called subscriber and Cell Identifier list. If TMSI
-numbers are defined for use these have the priority one, for security reasons
and if the network does not use TMSIs then IMSI -number is included only. The
paging is sent as an UDT (Unit Data) message to the BSC.
- BSSMAP (length : 28, 1Ch)
PAGING
IMSI
- length : 8 (08h)
- identity contains an IMSI
- mobile country code : 262
- mobile network code : 09
- MSIN : 0000000002
TMSI
- length : 4 (04h)
- TMSI value : CA2A0100h
Cell Identifier List
- length : 9 (09h)
- cell identified with LAC + CI
- location area code : 1369 (0559h)
- cell identifier : 173 (00ADh)
- location area code : 1369 (0559h)
- cell identifier : 174 (00AEh)

2.

Paging Command (BSC to BTS ;BTSM)

The BSC always calculates so-called paging group. The idea of this calculation
is to find out in which radio time slots the BTS can send the Paging Requests
out towards the MS. Reason: in the network, there is a possibility to have at
least three different kind of BCCH-TRX -radio time slot configurations and thus
logical channel PCH can have at least three different kinds of location. If the
BSC receives both TMSI and IMSI from the MSC, then it uses always TMSI
number when sending paging further on.

42 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

PAGING CMD (CCh) T=0


Channel Nr
- downlink CCCH (PCH + AGCH)
- timeslot : 0
Paging Group
- value : 2 (02h)
MS Identity
- TMSI : ca2a0100

3.

Paging Request (BTS to MS;PCH)

The BTS sends paging on a PCH channel.

4.

Channel Request ( MS to BTS ;RACH)

The MS requests a channel by sending a random access burst on a RACH


channel to a BTS. The Channel request message contains the establishment
cause (3 bits) which can be response to paging, emergency call or 'other
services' e.g. Mobile Originated Call, Short Message Service or Location
Update. Additionally, this message contains a Random Reference, which
consists of 5 bits randomly selected by the MS. This random reference is used
to separate two MSs that are attempting to access the network at exactly the
same time.

5.

Channel Required (BTS to BSC ;BTSM)

The BTS sends a channel-required message to the BSC, which contains the
information contained in the channel request. To this, the BTS adds the TDMA
frame number and the Access Delay, which is the first timing advance estimate
made by the BTS.
CHAN RQD (CCh) T=0
Channel Nr
- uplink CCCH (RACH)
- timeslot : 0
Req. Ref
- answer to paging
- random reference : 25 (19h)
- N32 : 10 (ah)
- N26 : 23 (17h)
- N51 : 34 (22h)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

43 (119)

Signalling Examples

Access Delay
- value : 0 (00h)

6.

Channel Activation (BSC to BTS ;BTSM)

After receiving the channel-required message, the BSC allocates an SDCCH channel for this call. It sends a Channel Activation message to the BTS
containing the following parameters: DTX control, channel description, mobile
allocation, maximum power levels of the MS and BTS and the timing advance
as calculated by the BSC.
CHAN. ACT. (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Act. Type
- immediate assignment procedure
Channel Mode
- length : 4
- downlink DTX not used, uplink DTX not used
- channel type : 03h 01h 00h
Channel Id
- length : 6
- SDCCH/8 subch 3
- timeslot : 1
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)
- frequencies included from CA :
BS Power
- power control level : 14 (eh)
MS Power
- power control level : 0 (0h)
Timing Adv.
- 0 (00h) (0 km)

44 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

7.

Channel Activation Ack . (BTS to BSC;BTSM)

A response to the channel activation message. When the BTS has received this
message it starts to send and receive on the SDCCH channel.
CHAN. ACT. ACK (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Frame Number
- N32 : 10 (ah)
- N26 : 7 (7h)
- N51 : 44 (2ch)

8.

Immediate Assignment Command

(BSC to BTS ;BTSM L3)


The BSC tells the BTS about the characteristics of the SDCCH channel to use.
IMM.ASS. CMD (CCh) T=0
Channel Nr
- downlink CCCH (PCH + AGCH)
- timeslot : 0
Imm. Ass. Info
- value (hex) : 06 3F 00 59 03 5C 99
54 57 00 00
IMMEDIATE ASSIGNMENT (RR)
Page Mode
- normal paging
Channel Description
- SDCCH/8 subchannel 3
- timeslot : 1
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)
Request Reference

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

45 (119)

Signalling Examples

- answer to paging
- random reference : 25 (19h)
- N32 : 10 (ah)
- N26 : 23 (17h)
- N51 : 34 (22h)
Timing Advance
- 0 (00h) (0 km)
Mobile Allocation
- frequencies included from CA :

9.

Immediate Assignment (BTS to MS ;AGCH )

The BTS informs the MS on the AGCH channel the characteristics of the
SDCCH channel to be used. Parameters include the page mode, SDCCH
channel description, SACCH, hopping indicator, the initial timing advance, and
mobile allocation (if frequency hopping applies). Additionally, the request
reference (random reference and the TDMA frame number) originally sent by
the MS is included to identify the relevant MS. The MS is then able to switch to
this SDCCH channel.
-----------------------------------------------------------------------------------------------Page Mode
The purpose of this element is to control the behavour of a mobile belonging to
the paging subgroup to which this element is sent.
Page Mode

page text

Paging mode

10.

value

page text

normal paging

extended paging

paging reorganisation

same as before

SABM (MS to BTS ;SDCCH)


Paging Response (MS to BTS ; L3)

The MS responds to the paging on the signalling channel.

46 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

11.

Establish Indication (BTS to BSC ;BTSM)


Paging Response (L3)

BTS acknowledges the Immediate Assignment Command by returning


Establish Indication message. Establish indication -message has two uses.
Firstly, when used in this phase it points out that from the BTS point of view,
the MS is now on the SDCCH-channel. Thus, the BTS sends information back
to the BSC that the MS is now on this kind of SDCCH-channel which
description is like this etc. Also the BTS identifies the link = main signalling
channel and adds received Layer 3 information into this message.
EST. IND (RLL) T=0
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
PAGING RESPONSE (RR)
Ciphering Key Seq. Nr
- value : 2h
MS Classmark 2
- length : 2 (02h)
- revision level : reserved for phase 1
- encryption algorithm A5
- class 1, vehicle and portable
- frequency band 0
- short message capability present
Mobile Identity
- length : 5h
- TMSI : ca2a0100

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

47 (119)

Signalling Examples

12.

Paging Response
(BSC to MSC ; SCCP BSSMAP L3)

The BSC initiates the MSC about the connection by paging response, which is a
CR (Connection Request) me
CR - CONNECTION REQUEST
Routing Label
- DPC : 12600 (3138h) OPC : 432 (01B0h)
- SLC : 13 (0Dh)
Source Local Reference
- 7DC056h
Protocol Class
- protocol class : 2h, connection oriented
Called Party Address
- length 2 (02h)
- no global title present
- routing based on SSN and MTP routing label
- subsystem is BSSAP
Calling Party Address
- length 4 (04h)
- no global title present
- routing based on SSN and MTP routing label
- point code : 432 (01B0h)
- subsystem is BSSAP
SCCP User Data
- length 24 (18h)
End of Optional Parametersssage.
- BSSMAP (length : 22, 16h)
COMPLETE L3 INFORMATION
Cell Identifier
- length : 5 (05h)
- cell identified with LAC + CI
- location area code : 1369 (0559h)
- cell identifier : 174 (00AEh)

48 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

Layer 3 Information
- length : 12 (0Ch)
PAGING RESPONSE

(RR)

Ciphering Key Seq. Nr


- value : 2h
MS Classmark 2
- length : 2 (02h)
- revision level : reserved for phase 1
- encryption algorithm A5
- class 1, vehicle and portable
Process Access Request (MSC to VLR)
Authentication (VLR to MSC)

13.

UA (BTS to MS ;SDCCH )

UA is normal Layer 2 level acknowledgement when setting up the Layer 2 level


link in LAPDm -protocol.
-------SCCP----------CC - CONNECTION CONFIRM
Routing Label
- DPC : 432 (01B0h) OPC : 12600 (3138h)
- SLC : 12 (0Ch)
Destination Local Reference
- 7DC056h
Source Local Reference
- 4C814Ch
Protocol Class
- protocol class : 2h, connection oriented

14.

Authentication Request (MSC to BSC ;BSSMAP L3)

As a CC (Connection Confirmed) message, the MSC sends an


Authentication Request message to the BSC. The message contains the RAND.
- DTAP (length : 19, 13h)
- SAPI : 0, main DCCH is used

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

49 (119)

Signalling Examples

AUTHENTICATION REQ

(MM)

Ciphering Key Seq. Nr


- value : 3h
Auth. Parameter RAND
EE2DF3382E516497A5BE005BDD1B7313

15.

Authentication Request
(BSC to BTS to MS; BTSM SDCCH L3)

The BSC forwards the message via the BTS to the MS.
DATA REQ (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
AUTHENTICATION REQ

(MM)

Ciphering Key Seq. Nr


- value : 3h
Auth. Parameter RAND
EE2DF3382E516497A5BE005BDD1B7313

16.

Authentication Response
(MS to BTS to BSC; SDCCH BTSM L3)

The MS responds to the Authentication Request with the Signed Response


SRES. The Authentication Response is sent to the BSC via the BTS.In the MS
Authentication procedure, two algorithms, A3 and A8 are used. In the SIM card (In MS), both of these algorithms and 32 -digit key are stored) and the very
same information can be found in Authentication Centre (AuC) also. When MS
Authentication is requested by the network, AuC/VLR sends 32 -digit
RANDom Number to the MS. MS calculates then Signed Response (SRES and
returns that back to the VLR. VLR makes a comparison if received SRES is
same than it has received inside of the Authentication triplet from the AuC
before. If these two SRESs are the same, authentication went OK and MS can
continue the call setup. Should you notice, the first 8 digits of the KI are used

50 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

for Authentication and SRES calculation, the rest 24 are reserved for Ciphering
Key calculation.
DATA IND (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
AUTHENTICATION RSP

(MM)

Auth. Parameter SRES : EE2CF13B

17.

Authentication Response
(BSC to MSC ;BSSMAP L3)

Inside of this message, the SRES value from the MS is forwarded back to the
VLR in order to finalise authentication procedure.
This and all other messages in the A-interface up to the releasing of the SCCP
connection are transmitted by using SCCP DT1 (Data Form 1) messages.
- DTAP (length : 6, 06h)
- SAPI : 0, main DCCH is used
AUTHENTICATION RSP

(MM)

Auth. Parameter SRES : EE2CF13B


Authentication Response (MSC to VLR)
Set Ciphering Mode (VLR to MSC)

18.

Ciphering Mode Command (MSC to BSC;BSSMAP )

The MSC asks the BSC start ciphering on the radio path. This message is sent
in the A-interface in case the network wants to initiate ciphering over the radio
interface. If the network uses ciphering then MS starts ciphering after receiving
this message.
- BSSMAP (length : 16, 10h)
CIPHER MODE COMMAND
L3 Header Information
- length : 2 (02h)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

51 (119)

Signalling Examples

- protocol discr. : Radio Resources


- transaction id. : 0 (0h)
- message send from originating side
Encryption Information
- length : 9 (09h)
- GSM user data encr. v. 1
- ciphering key, length : 8 (08h)
2A 54 62 90 5D 47 FA A0

19.

Encryption command (BSC to BTS ;BTSM L3)

The BSC stores the Encryption information to its memory and sends an
Encryption command to the BTS to start ciphering mode operations.
ENCR. CMD (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Encr. Info
- lentgh : 9
- GSM A5/1
- ciphering key : 2A 54 62 90 5D 47
FA A0
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CIPH. MODE COMMAND (RR)
Cipher Mode Setting
- start ciphering

20.

Ciphering Mode Command (BTS to MS;SDCCH)

The BSS informs the MS about beginning of ciphering , and starts receiving in
the ciphered mode.

52 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

21.

Ciphering Mode Complete


(MS to BTS to BSC ;SDCCH BTSM L3)

The MS acknowledges ciphering command.


DATA IND (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CIPH. MODE COMPLETE (RR)

22.

Ciphering Mode Complete (BSC to MSC;BSSMAP)

If ciphering is in use, this is the first ciphered message (by the MS) in the Air
interface. The BSS acknowledges the Ciphering Command, informs the MSC
that MS has started ciphering and starts sending information in ciphered mode.
- BSSMAP (length : 1, 01h)
CIPHER MODE COMPLETE
Access Request Accepted (VLR to MSC)
Forward New TMSI (VLR to MSC)
Identity Request (MSC to BSC to BTS to MS)
Identity Response(MS to BTS to BSC to MSC)

23.

TMSI Realloction Command


(MSC to BSC;BSSMAP L3)

The purpose of the TMSI reallocation procedure is to provide identity


confidentiality. Usually the TMSI reallocation is performed at least at each
change of location area. MSC initiates the TMSI reallocation procedure by
sending TMSI Reallocation command message to the MS. TMSI Reallocation
Command message contains a new combination of TMSI and LAI allocated by
the network or a LAI and the IMSI if the used TMSI shall be deleted. Usually
the TMSI Reallocation Command message is sent to the MS by using a RR
connection in ciphered mode.
- DTAP (length : 13, 0Dh)
- SAPI : 0, main DCCH is used

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

53 (119)

Signalling Examples

TMSI REALLOC COMMAND (MM)


Location Area Id.
- MCC : 262
- MNC : 09
- LAC : 1369 (559h)
Mobile Identity
- length : 5h
- TMSI : ca2d0100

24.

TMSI Reallocation Command


(BSC to BTS to MS;BTSM SDCCH L3)

TMSI Reallocation Command is forwarded to the MS.


DATA REQ (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
TMSI REALLOC COMMAND (MM)
Location Area Id.
- MCC : 262
- MNC : 09
- LAC : 1369 (559h)
Mobile Identity
- length : 5h
- TMSI : ca2d0100

25.

TMSI Realloction Complete


(MS to BTS to BSC;SDCCH BTSM L3)

When the MS receives the TMSI Reallocation Command message, it stores the
LAI in the SIM. If the received identity is the IMSI of the MS, it deletes any
previously stored TMSI. If the received identity is a TMSI, the MS stores it in

54 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

the SIM. In both cases the MS send a TMSI Reallocation Complete message to
the network.
DATA IND (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
TMSI REALLOC COMPL. (MM)

26.

TMSI Reallocation Complete


(BSC to MSC ;BSSMAP L3)

TMSI Reallocation Complete message is forwarded to the MSC.


- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
TMSI REALLOC COMPL. (MM)
---------------------------------------------------------------TMSI Ack. (MSC to VLR)
Complete IC (VLR to MSC)
-----------------------------------------------------------------

27.

Setup(MSC to BSC ;BSSMAP L3)

After authentication, Identification and Ciphering, the MS is in the SDCCH


channel and ready to start real call setup signalling. The MSC sends a Setup
message to the BSC to be forwarded to the MS.
- DTAP (length : 5, 05h)
- SAPI : 0, main DCCH is used
SETUP (CC)
Bearer Capability
- length : 1 (1h)
- info xfer cap : speech
- xfer mode : circuit
- coding std : GSM standardized

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

55 (119)

Signalling Examples

- radio ch req: full rate ch required

28.

Setup (BSC to BTS to MS;BTSM SDCCH L3)

The BSC sends the Setup message to the MS via BTS in order to inform the MS
about the incoming call.
DATA REQ (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
SETUP (CC)
Bearer Capability
- length : 1 (1h)
- info xfer cap : speech
- xfer mode : circuit
- coding std : GSM standardized
- radio ch req: full rate ch required

29.

Call Comfirmed (MS to BTS ;SDCCH)

The MS responds after having checked the compatibility with a requested


bearer capability.
DATA IND (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CALL CONFIRMED

56 (119)

(CC)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

30.

Call Confirmed (BSC to MSC ;BSSMAP L3)

The information is forwarded to the MSC. This message indicates that the
network has received all information that is required for call setup and no more
such information will be accepted.
- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
CALL CONFIRMED

31.

(CC)

Assignment Request

(MSC to BSC;BSSMAP)

This message starts the TCH allocation. In the A- interface, MSC is the master
and it hunts the circuit used for this call through the A- interface. This message
can contain some optional information according to GSM- recommendations.
This optional information is: Priority of the call, Downlink Discontinuous
Transmission (DTX), Radio channel identity and Interference band to use.
- BSSMAP (length : 16, 10h)
ASSIGNMENT REQUEST
Channel Type
- length : 3 (03h)
- speech
- TCH/FS
- GSM speech encoding algorithm version 1
L3 Header Information
- length : 2 (02h)
- protocol discr. : Radio Resources
- transaction id. : 0 (0h)
- message send from originating side
Priority
- length : 1 (01h)
- priority level 3 (3h)
- queueing allowed
- preemption vulnerability indi not allowed
Circuit Identity Code
- pcm multiplex : 1 (001h)
- pcm timeslot : 2 (02h)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

57 (119)

Signalling Examples

32.

Physical Context Request (BSC to BTS ;BTSM)

By using this message, the BSC interrogates the actual timing advance from the
BTS in order to start TCH allocation through the Abis -interface.
PHYS. CONTEXT REQ (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1

33.

Physical Context Confirme (BTS to BSC ;BTSM)

BSC receives the timing advance information from the BTS and starts TCH
reservation and allocation. This reservation & allocation procedure is similar to
the case of the SDCCH -channel.
PHYS. CONTEXT CNF (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
BS Power
- power control level : 14 (eh)
MS Power
- power control level : 0 (0h)
Timing Adv.
- 0 (00h) (0 km)

34.

Channel Activation (BSC to BTS ;BTSM)

After the BSC's internal channel reservation and allocation, it activates the TCH
by sending this message towards the BTS. Contents: channel number, activation
type, channel mode (DTX/No DTX), channel type (Speech / data: if speech,
then GSM encoding algorithm included, if data, then information about
transparency or non-transparency of the channel and data rate), channel identity,
encryption information if received, BS & MS power levels as received in
'Physical context confirm' -message and timing advance
CHAN. ACT. (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 7

58 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

Act. Type
- normal assignment procedure
Channel Mode
- length : 4
- downlink DTX not used, uplink DTX not used
- channel type : 01h 08h 01h
Channel Id
- length : 6
- full rate TCH
- timeslot : 7
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)
- frequencies included from CA :
Encr. Info
- lentgh : 9
- GSM A5/1
- ciphering key : 2A 54 62 90 5D 47
FA A0
BS Power
- power control level : 14 (eh)
MS Power
- power control level : 0 (0h)
Timing Adv.
- 0 (00h) (0 km)

35.

Channel Activation Ack. (BTS to BSC ;BTSM)

The BTS returns current TDMA frame number and after that the TCH is
activated through the Abis-interface.
CHAN. ACT. ACK (DCh) T=0
Channel Nr
- full rate TCH

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

59 (119)

Signalling Examples

- timeslot : 7
Frame Number
- N32 : 11 (bh)
- N26 : 2 (2h)
- N51 : 2 (2h)

36.

Assignment Command
(BSC to BTS to MS;BTSM SDCCH L2)

The BTS delivers received information further on towards the MS. Contents:
channel description, power levels, cell channel description, channel mode (Full /
Half) and mobile allocation
DATA REQ (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 3
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
ASSIGNMENT COMMAND (RR)
Channel Description
- full rate TCH
- timeslot : 7
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)
Power Command
- power level of MS : 0
Channel Mode
- speech FR or HR version 1

60 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

37.

SABM (MS to BTS ;FACCH)


SABM (Set Asynchronous Balanced Mode)

This is Layer 2 message and contains some Layer 3 information. Content of this
message: service request (look establishment cause!), ciphering key sequence,
Mobile Station Classmark and Mobile Identity.

38.

Establish Indication (BTS to BSC ;BTSM)

Establish indication -message has two uses. Firstly, when used this phase it
points out that from the point of view of the BTS, the MS is now on the
FACCH-channel. Thus, the BTS sends information back to the BSC that the
MS is now on this kind of FACCH-channel which description is like this etc.
Also the BTS identifies the link = main signalling channel and adds received
Layer 3 information into this message. This layer 3 information is coming from
the MS, of course.
EST. IND (RLL) T=0
Channel Nr
- full rate TCH
- timeslot : 7
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0

39.

UA (BTS to MS; FACCH )

UA is normal Level 2 acknowledgement when setting up the Layer 2 level link


in LAPDm-protocol.

40.

Assignment Complete
(MS to BTS to BSC ;BTSM FACCH )

The MS informs it is now on the TCH and everything is OK.


DATA IND (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 7
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
ASSIGNMENT COMPLETE (RR)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

61 (119)

Signalling Examples

RR Cause
- normal

41.

Assignment complete (BSC to MSC ;BSSMAP)

The BSS acknowledges the channel seizure to the MSC.


- BSSMAP (length : 3, 03h)
ASSIGNMENT COMPLETE
RR Cause
- normal

42.

RF Channel Release (BSC to BTS ;BTSM)

When MS has informed the network it is in the TCH, there is no need to use the
SDCCH -channel for this call setup any more. By RF Channel Release
procedure it is released.
RF CHANNEL REL. (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1

43.

RF Channel Release Ack.(BTS to BSC ;BTSM)

The BTS acknowledges the RF Channel Release message.


RF CH. REL. ACK (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 1
- timeslot : 1

44.

Alerting (MS to BTS to BSC;FACCH BTSM L3)

The MS sends an Alerting message via BSS.


DATA IND (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 7
Link Id

62 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- main DCCH (FACCH or SDCCH)


- SAPI : 0
L3 Info
ALERTING

45.

(CC)

Alerting (BSC to MSC;BSSMAP L3)

The MS informs that the subscriber has been alerted. This message can contain
also so-called progress indicator IE, which tells that there are in-band
announcements or other similar information to be received. In brief, this means
that the connection is not end-to-end ISDN connection. If the MS receives this
element, it shall through-connect the speech path. In case it is not, the MS
generates ringing tone in itself. This information can also be transferred in a
Progress message.
- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
ALERTING

46.

(CC)

Connection (MS to BTS to BSC ;BTSM FACCH L3)

When the MS receives a Connect message, it attaches the user connection to the
radio path, returns a Connect Acknowledge message, stops any locally
generated alerting indication (if applied) and enters the "active" state.
DATA REQ (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CONNECT

47.

(CC)

Connection (BSC to MSC ;BSSMAP L3)

The MSC sends a Connect message to the MS via the BSS. This message
indicates the MS that a connection has been established through the network.
- DTAP (length : 2, 02h)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

63 (119)

Signalling Examples

- SAPI : 0, main DCCH is used


CONNECT

48.

(CC)

Connection Ack. (MSC to BSC ;BSSMAP L3)

The message is forwarded to the MSC.


- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
CONNECT ACKNOWLEDGE (CC)

49.

Connection Ack.
(BSC to BTS to MS;FACCH BTSM L3)

By using this message, the MS informs the MSC that the MS is now in the
"active" state.
DATA IND (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CONNECT ACKNOWLEDGE (CC)
Conversation

50.

Measurement Report (MS to BTS ;SACCH L3)

When call is on, the MS sends measurement report concerning mainly the
quality of the speech connection two times per second.

51.

Measurement Report (BTS to BSC ;BTSM L3)

If these measurement reports are pre-processed in the BTS then measurement


results are sent towards the BSC. If the is no pre-processing in the BTS, then
measurement reports are sent. In this phase, Nokia BTS does not make any preprocessing.
MEAS. RES. (DCh) T=0
Channel Nr

64 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- full rate TCH


- timeslot : 6
Meas.Res. Nr
- value : 42 (2ah)
Uplink Meas.
- length : 3 (3h)
- downlink DTX not used
- rxlev_full : 43 (-68 - -67 dBm)
- rxlev_sub : 43 (-68 - -67 dBm)
- rxqual_full : 0
- rxqual_sub : 0
BS Power
- power control level : 14 (eh)
L1 Info
- MS power control level : 1 (1h)
- actual TA : 0 (00h) (0 km)
L3 Info
MEASUREMENT REPORT (RR)
Measurement Results
- BCCH allocation sequence number : 0
- DTX was not used
- serving cell rxlev_full : 31 (-80 - -79 dBm)
- serving cell rxlev_sub : 32 (-79 - -78 dBm)
- measurement results are valid
- serving cell rxqual_full : 0
- serving cell rxqual_sub : 0
- no neighbour cell meas results
Conversation

52.

Disconnect
( MS to BTS to BSC;BTSM FACCH L3)

This request is sent by MS. Contents: clear end-to-end connection. This


message stops the charging concerning this call connection.
DATA REQ (RLL) T=1

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

65 (119)

Signalling Examples

Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
DISCONNECT (CC)
Cause
- length : 2
- coding standard : GSM
- location : user
- normal event
- cause: normal clearing
Progress Indicator
- value (hex) :E0 88

53.

Disconnect (BSC to MSC ;BSSMAP L3)

The Disconnect message is forwarded to the MSC.


- DTAP (length : 9, 09h)
- SAPI : 0, main DCCH is used
DISCONNECT (CC)
Cause
- length : 2
- coding standard : GSM
- location : user
- normal event
- cause: normal clearing
Progress Indicator
- value (hex) :E0 88

66 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

54.

Release (MSC to BSC ;BSSMAP L3)

Actual release is coming from the MSC; real call is just about to end.
- DTAP (length : 6, 06h)
- SAPI : 0, main DCCH is used
RELEASE

(CC)

Cause
- length : 2
- coding standard : GSM
- location : user
- normal event
- cause: normal clearing

55.

Release ( BSC to BTS to MS;BTSM L3)

The Release message is forwarded to the MS.


DATA IND (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
RELEASE

(CC)

Cause
- length : 2
- coding standard : GSM
- location : user
- normal event
- cause: normal clearing

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

67 (119)

Signalling Examples

56.

Release Complete
( MS to BTS to BSC ;BTSM FACCH L3)

MS informs that it will release the transaction identifier, i.e. call release is
proceeding.
DATA REQ (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
RELEASE COMPLETE

57.

(CC)

Release Complete (BSC to MSC ;BSSMAP L3)

The Release Complete message is forwarded to the MSC.


- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
RELEASE COMPLETE

58.

(CC)

Clear Command (MSC to BSC;BSSMAP)

This message is coming from the MSC and releases the associated dedicated
resources, i.e. BSSAP connection concerning this call.
- BSSMAP (length : 1, 01h)
CLEAR COMPLETE

59.

Channel Release
(BSC to BTS to MS ;BTSM FACCH L3)

Deactivation command of the used TCH. This is sent by the BSC towards the
MS. Quite often this is also called '3rd layer disconnection'. In case of normal
call setup case, the release cause is 'normal'.
DATA REQ (RLL) T=1
Channel Nr
- full rate TCH

68 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CHANNEL RELEASE

(RR)

RR Cause
- normal

60.

Detactive SACCH (BSC to BTS;BTSM)

By sending this message to downlink direction, the BSC inhibits system


information message sending towards the MS. In fact, there is no use to
send/receive any information in the SACCH channel any more, so it will be
deactivated.
DEACT. SACCH (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 6

61.

DISC (MS to BTS;FACCH )

The MS send Layer 2 frame DISConnect to uplink direction in order to inform


the BTS it is stopping the traffic in the TCH/FACCH.

62.

UA (BTS to MS ;FACCH)

The BTS acknowledges DISC -frame. Consequences: the MS starts to listen


BCCH -channel again and all the Air interface resources are released.

63.

Release Indication(BTS to BSC ;BTSM)

The BTS informs the BSC that the MS has no more any dedicated Air interface
resources (i.e. TCH/FACCH) in use.
REL IND (RLL) T=0
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

69 (119)

Signalling Examples

- SAPI : 0

64.

RF Channel Release (BSC to BTS ;BTSM)

The BSC tells the BTS to release the rest of the radio resources.
RF CHANNEL REL. (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 6

65.

RF Channel Release Ack.(BTS to BSC;BTSM)

All the rest of the radio resources have been released; BTS send an
acknowledgement to BSC. These radio resources are TCH/FACCH and
SACCH.
RF CH. REL. ACK (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 6

66.

Clear Complete (BSC to MSC ;BTSM)

This is acknowledgement to the message SCCP Data (Clear


Command). Now the BSC informs the MSC that all radio resources related to
this call are released.
- BSSMAP (length : 1, 01h)
CLEAR COMPLETE

67.

SCCP Released (MSC to BSC;SCCP)

When all radio resources are released, BSSAP connection concerning this call is
not needed any more. This message tells the BSC to release this SCCP
connection. The message is sent as RLSD message.
RLSD - RELEASED
Routing Label
- DPC : 432 (01B0h) OPC : 12600 (3138h)
- SLC : 11 (0Bh)
Destination Local Reference

70 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Mobile call signalling

- 0D8056h
Source Local Reference
- 4B814Ch
Release Cause
- SCCP user originated

68.

SCCP Released Ack. (BSC to MSC ;SCCP)

BSC informs MSC that now the dedicated SCCP connection concerning this
call is released. The message is sent as RLC message.
RLC - RELEASE COMPLETE
Routing Label
- DPC : 12600 (3138h) OPC : 432 (01B0h)
- SLC : 13 (0Dh)
Destination Local Reference
- 4B814Ch
Source Local Reference
- 0D8056h

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

71 (119)

Signalling Examples

Location update
The purpose of a Location Update is to inform the network of a mobile's
position, minimising the area over which a mobile is paged. There are three
different kinds of location updates: normal, periodic and IMSI attach/detach.

3.1

Normal location update


The normal location update is performed when an MS moves into a new
location area. This area can be controlled by the same MSC/VLR or by a new
MSC/VLR. In latter case the new MSC will the notify HLR, which informs the
old MSC/VLR.

3.2

Periodic location update


Periodic location update means that the MS is required to contact regularly the
network. This is done automatically by the MS. The period is under control of
the BSC and defined by the BTS parameter: Timer for periodic MS location
updating (PER). Range of the parameter is from 6 minutes to 25.5 hours. This
parameter can be modified by the MML-command ZEQJ. The value is sent to
the network in the Broadcast Control Channel (BCCH).

3.3

IMSI attach/detach location update


When the Mobile Station is switched off the incoming calls toward the
corresponding subscriber cannot be completed. To avoid unnecessary signalling
the IMSI attach/detach function can be activated in the network be BTS
Parameter Allow IMSI attach detach (ATT). Parameter can have the values
on/off and it can be modified by MML-command ZEQJ. If the value is on, it

72 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

means that when the MS is switched off it sends to the visited MSC/VLR IMSI
DETACH message and the corresponding subscriber will no be paged. When
the MS is next time switched on the function IMSI attach informs the
MSC/VLR that the MS is in the active state and calls can be transferred.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

73 (119)

Signalling Examples

3.4

Location Update Signalling Example

VLR

MSC

BSC

BTS
Channel Required

MS
Channel Request ( RACH 1)

RADIO
ACCESS
PART

Channel Activation
Channel Activation Ack. 4

5 Immediate Assignment Command.


6 Immediate Assignment ( AGCH ).
Location Update Request 7
Location Update Request 8
Establish Indication

CR Location Update Req. 9


Process Access Request

SABM (SDCCH)
LOCATION
UPDATE
REQUEST

10 UA ( SDCCH )

CC

Identity Request

11 DT1 Identity Request

15 DT1Authentication Request

Set Ciphering Mode

16

18
DT1 Authentication Response

Authentication Response

19

Identity Request ( SDCCH )

13

Identity Response ( SDCCH )

DT1 Identity Response 14

Identity Response
Authenticate

12

IDENTIFICATION
AND
AUTHENTICATION
PROCEDURES

Authentication Request ( SDCCH )


Authentication Response ( SDCCH )

17

21
Ciphering Mode Command ( SDCCH )
20 Encryption Command

DT1 Cipher Mode Command

CIPHERING AND
ENCRYPTION
PART

Ciphering Mode Complete ( SDCCH ) 22

23

DT1Cipher Mode Complete


Access Request Ack.

24 DT1 Location Update Accepted


25

Location Update Accepted


LOCATION
UPDATE

TMSI reallocation Complete

27

26

DT1TMSI Reallocation Complete

28 DT1 Clear Command

29
30

Channel Release ( SDCCH )


Deactivate SACCH

Release Indication

34
DT1 Clear Complete

36

CHANNEL
RELEASE

DISC ( SDCCH )

33

32

31

UA ( SDCCH )

RF Channel Release
RF Channel Release Ack.35

37 RLSD (SCCP Released)


RLC (SCCP Released Ack.)
38

74 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

1.

Channel Request (MS to BTS ;RACH)

The MS requests a channel by sending a random access burst on a RACH


channel to a BTS. The Channel request message contains the establishment
cause (3 bits) which can be response to paging, emergency call or 'other
services' e.g. Mobile Originated Call, Short Message Service or Location
Update. Additionally, this message contains a Random Reference, which
consists of 5 bits randomly selected by the MS. This random reference is used
to separate two MSs that are attempting to access the network at exactly the
same time.

2.

Channel Required (BTS to BSC ;BTSM)

The BTS sends a channel-required message to the BSC, which contains the
information contained in the channel request. To this, the BTS adds the TDMA
frame number and the Access Delay, which is the first timing advance estimate
made by the BTS.
CHAN RQD (CCh) T=0
Channel Nr
- uplink CCCH (RACH)
- timeslot : 0
Req. Ref
- loc upd, imsi detach etc.
- random reference : 14 (eh)
- N32 : 14 (eh)
- N26 : 14 (eh)
- N51 : 29 (1dh)
Access Delay
- value : 1 (01h)

3.

Channel Activation (BSC to BTS ;BTSM)

After receiving the channel-required message, the BSC allocates an SDCCH channel for this call. It sends a Channel Activation message to the BTS
containing the following parameters: DTX control, channel description, mobile
allocation, maximum power levels of the MS and BTS and the timing advance
as calculated by the BSC.
CHAN. ACT. (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

75 (119)

Signalling Examples

Act. Type
- immediate assignment procedure
Channel Mode
- length : 4
- downlink DTX not used, uplink DTX not used
- channel type : 03h 01h 00h
Channel Id
- length : 6
- SDCCH/8 subch 6
- timeslot : 1
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)
- frequencies included from CA :
BS Power
- power control level : 14 (eh)
MS Power
- power control level : 0 (0h)
Timing Adv.
- 1 (01h) (0 km)

4.

Channel Activation Ack. (BTS to BSC ;BTSM)

A response to the channel activation message. When the BTS has received this
message it starts to send and receive on the SACCH channel.
CHAN. ACT. ACK (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Frame Number
- N32 : 14 (eh)
- N26 : 24 (18h)
- N51 : 39 (27h)

76 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

5.

Immediate Assignment Command


(BSC to BTS ;BTSM L3)

The BSC tells the BTS about the characteristics of the SDCCH channel to use.
IMM.ASS. CMD (CCh) T=0
Channel Nr
- downlink CCCH (PCH + AGCH)
- timeslot : 0
Imm. Ass. Info
- value (hex) : 06 3F 00 71 03 5C 0E
73 AE 01 00
IMMEDIATE ASSIGNMENT (RR)
Page Mode
- normal paging
Channel Description
- SDCCH/8 subchannel 6
- timeslot : 1
- training sequence code : 0
- hopping : 0
- Frequency band nr : 3
- ARFCN : 92 (5ch)
Request Reference
- loc upd, imsi detach etc.
- random reference : 14 (eh)
- N32 : 14 (eh)
- N26 : 14 (eh)
- N51 : 29 (1dh)
Timing Advance
- 1 (01h) (0 km)
Mobile Allocation
- frequencies included from CA :

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

77 (119)

Signalling Examples

6.

Immediate Assignment (BTS to MS ;AGCH)

The BTS informs the MS on the AGCH channel the characteristics of the
SDCCH channel to be used. Parameters include the page mode, SDCCH
channel description, SACCH, hopping indicator, the initial timing advance, and
mobile allocation (if frequency hopping applies). Additionally, the request
reference (random reference and the TDMA frame number) originally sent by
the MS is included to identify the relevant MS. The MS is then able to switch to
this SDCCH channel.

7.

SABM (MS to BTS ;SDCCH)

Location Update Request (MS to BTS ;L3)


After receiving the IMMEDIATE ASSIGNMENT message, the MS tunes to the
assigned SDCCH and starts to establish the signalling link across the network.
The MS sends the layer 2 SABM to the BTS on the SDCCH. The SABM
contains a layer 3 service request message indicating the service type required
to the network through the service request message.

8.

Establish Indication (BTS to BSC ;BTSM )

Location Update Request ( L3)


BTS acknowledges the Immediate Assignment Command by returning
Establish Indication message. Establish indication -message has two uses.
Firstly, when used in this phase it points out that from the BTS point of view,
the MS is now on the SDCCH-channel. Also the BTS identifies the link id as
the main signalling channel and adds received Layer 3 information into this
message. The BSC starts the handover algorithm.
EST. IND (RLL) T=0
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
LOCATION UPD. REQ

(MM)

Location Updating Type


- FOR : no follow on req. pend.
- LUT: normal location updating
Ciphering Key Seq. Nr
- value : 7h
Location Area Id.

78 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

- MCC : 262
- MNC : 09
- LAC : 0 (0h)
MS Classmark 1
- revision level : reserved for phase 1
- encryption algorithm A5
- class 1, vehicle and portable
Mobile Identity
- length : 8h
- IMSI : 262090000000002

9.

Location Update Req. (BSC to MSC ;BSSMAP L3)

The Location Update Request message is forwarded to the MSC as a CR


(Connection Request) message. The message includes the type of location
update (IMSI attach, periodic or normal), mobile identity, ciphering key,
location id, MS classmark and the mobile identity (IMSI/TMSI)
SCCP part:
CR - CONNECTION REQUEST
Routing Label
- DPC : 12600 (3138h) OPC : 432 (01B0h)
- SLC : 9 (09h)
Source Local Reference
- 098056h
Protocol Class
- protocol class : 2h, connection oriented
Called Party Address
- length 2 (02h)
- no global title present
- routing based on SSN and MTP routing label
- subsystem is BSSAP
Calling Party Address
- length 4 (04h)
- no global title present
- routing based on SSN and MTP routing label

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

79 (119)

Signalling Examples

- point code : 432 (01B0h)


- subsystem is BSSAP
SCCP User Data
- length 30 (1Eh)
End of Optional Parameters
CC - CONNECTION CONFIRM
Routing Label
- DPC : 432 (01B0h) OPC : 12600 (3138h)
- SLC : 3 (03h)
Destination Local Reference
- 098056h
Source Local Reference
- 43814Ch
Protocol Class
- protocol class : 2h, connection oriented
- BSSMAP (length : 28, 1Ch)
COMPLETE L3 INFORMATION
Cell Identifier
- length : 5 (05h)
- cell identified with LAC + CI
- location area code : 1369 (0559h)
- cell identifier : 174 (00AEh)
Layer 3 Information
- length : 18 (12h)
LOCATION UPD. REQ

(MM)

Location Updating Type


- FOR : no follow on req. pend.
- LUT: normal location updating
Ciphering Key Seq. Nr
- value : 7h
Location Area Id.
- MCC : 262
- MNC : 09

80 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

- LAC : 0 (0h)
MS Classmark 1
- revision level : reserved for phase 1
- encryption algorithm A5
- class 1, vehicle and portable
Mobile Identity
- length : 8h
- IMSI : 262090000000002
Process Access Request (MSC to VLR)
Identity Request (VLR to MSC )

10.

UA (BTS to MS ;SDCCH)

The BTS acknowledges the SABM sent by the MS.

11.

Identity Request (MSC to BSC ;BSSMAP L3)

This is an identification procedure used for IMEI (International Mobile


Equipment Identity) checking by the EIR (Equipment Identity Register). The
network may also require the IMSI from the mobile if it cannot be derived from
the TMSI.
- DTAP (length : 3, 03h)
- SAPI : 0, main DCCH is used
IDENTITY REQUEST (MM)
Identity Type
- value : 2h

12.

Identity Request (BSC to BTS to MS ;BTSM SDCCH L3)

The BSS forwards the Identity Request message to the MS.


DATA REQ (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
IDENTITY REQUEST (MM)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

81 (119)

Signalling Examples

Identity Type
- value : 2h

13.

Identity Response (MS to BTS to BSC;BTSM SDCCH L3)

The MS sends a response to the Identity Request containing its mobile identity
information (IMEI).
DATA IND (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
IDENTITY RESPONSE

(MM)

Mobile Identity
- length : 8h
- IMEI : 495000100676140

14.

Identity Response (BSC to MSC;BSSMAP L3)

The message is forwarded to the MSC.


- DTAP (length : 11, 0Bh)
- SAPI : 0, main DCCH is used
IDENTITY RESPONSE

(MM)

Mobile Identity
- length : 8h
- IMEI : 495000100676140
Identity Response (MSC to VLR)
Authenticate (VLR to MSC)

15.

Authentication Request (MSC to BSC ; BSSMAP L3)

The MSC sends an Authentication Request message to the BSC in a DT1 (Data
Form 1) message. The message contains the RAND.
- DTAP (length : 19, 13h)
- SAPI : 0, main DCCH is used

82 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

AUTHENTICATION REQ

(MM)

Ciphering Key Seq. Nr


- value : 0h
Auth. Parameter RAND
B1FE7D11F95159DB3FD16BA6A786056A

16.

Authentication Request
(BSC to BTS to MS;BTSM SDCCH L3)

The BSC forwards the message via the BTS to the MS.
DATA REQ (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
AUTHENTICATION REQ

(MM)

Ciphering Key Seq. Nr


- value : 0h
Auth. Parameter RAND
B1FE7D11F95159DB3FD16BA6A786056A

17.

Authentication Response
( MS to BTS to BSC; SDCCH BTSM L3)

The MS responds to the Authentication Request with the Signed Response


SRES.
There are two algorithms used in the Authentication procedure, A3 and A8. In
the MS, these algorithms are stored on the SIM card, along with a 32-digit key
called Ki. The same information can be found in the Authentication Centre
(AuC). When the network requests MS Authentication, the AuC/VLR sends a
32 digit RANDom Number to the MS. The MS calculates the Signed Response
(SRES) and sends it to the VLR. The VLR then compares the MSs SRES with
the AuCs SRES and if they are the same, the call set-up can continue.
Note
The first 8 digits of the Ki are used for Authentication and SRES calculation,

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

83 (119)

Signalling Examples

the other 24 are reserved for Ciphering Key (Kc) calculation.

DATA IND (RLL) T=1


Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
AUTHENTICATION RSP

(MM)

Auth. Parameter SRES : B1FF7F12

18.

Authentication Response (BSC to MSC ;BSSMAP L3)

The BSC forwards the SRES to the VLR.


- DTAP (length : 6, 06h)
- SAPI : 0, main DCCH is used
AUTHENTICATION RSP

(MM)

Auth. Parameter SRES : B1FF7F12


Authentication Response (MSC to VLR)
Set Cipering Mode (VLR to MSC)

19.

Cipher Mode command (MSC to BSC ;BSSMAP )

The MSC uses this command, which includes Kc to initiate ciphering if the
function is enabled.
- BSSMAP (length : 16, 10h)
CIPHER MODE COMMAND
L3 Header Information
- length : 2 (02h)
- protocol discr. : Radio Resources
- transaction id. : 0 (0h)
- message send from originating side
Encryption Information

84 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

- length : 9 (09h)
- GSM user data encr. v. 1
- ciphering key, length : 8 (08h)
FD 54 5F DC C7 28 91 5D

20.

Encryption Command (BSC to BTS ;BTSM )

Ciphering Mode Command (BSC to BTS ; L3)


The BSC stores the Encryption information and forwards the command to the
BTS. If the BTS software contains the algorithm specified by the MSC it can
start ciphering, otherwise it sends a reject message back to the MSC.
ENCR. CMD (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Encr. Info
- lentgh : 9
- GSM A5/1
- ciphering key : FD 54 5F DC C7 28
91 5D
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CIPH. MODE COMMAND (RR)
Cipher Mode Setting
- start ciphering

21.

Ciphering Mode Command (BTS to MS ;SDCCH)

The BTS commands the MS to start ciphering (whether required or not) and
starts receiving in the ciphered mode.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

85 (119)

Signalling Examples

22.

Ciphering Mode Complete


(MS to BTS to BSC ;SDCCH BTSM L3)

The MS acknowledges the ciphering command in the specified cipher mode.


This message may include the IMEI.
DATA IND (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CIPH. MODE COMPLETE (RR)

23.

Cipher Mode Complete (BSC to MSC ;BSSMAP)

The BSC forwards the cipher response to the MSC.


- BSSMAP (length : 1, 01h)
CIPHER MODE COMPLETE
Access Request Ack .(VLR to MSC )

24.

Location Update Accepted (MSC to BSC ;BSSMAP L3)

The MSC sends the Location Updating Accept message to the MS to indicate
that updating has been completed. This message includes the location area id
and the TMSI.
- DTAP (length : 14, 0Eh)
- SAPI : 0, main DCCH is used
LOCATION UPD. ACC

(MM)

Location Area Id.


- MCC : 262
- MNC : 09
- LAC : 1369 (559h)
Mobile Identity
- length : 5h
- TMSI : ca200100

86 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

25.

Location Update Accepted


(BSC to BTS to MS ;BTSM SDCCH L3)

The Location Updating Accept message is forwarded to the MS by the BSS.


DATA REQ (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
LOCATION UPD. ACC

(MM)

Location Area Id.


- MCC : 262
- MNC : 09
- LAC : 1369 (559h)
Mobile Identity
- length : 5h
- TMSI : ca200100

26.

TMSI Reallocation Complete


(MS to BTS to BSC;SDCCH BTSM L3)

The TMSI Reallocation Complete message is sent to the network to indicate


that it has accepted the new TMSI.
DATA IND (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
TMSI REALLOC COMPL.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

(MM)

87 (119)

Signalling Examples

27.

TMSI Reallocation Complete (BSC to MSC ;BSSMAP L3)

The TMSI Reallocation Complete message is forwarded to the MSC.


- DTAP (length : 2, 02h)
- SAPI : 0, main DCCH is used
TMSI REALLOC COMPL. (MM)

28.

Clear Command (MSC to BSC ;BSSMAP)

The MSC releases the associated dedicated resources, i.e. BSSAP connection
concerning this call.
- BSSMAP (length : 8, 08h)
CLEAR COMMAND
L3 Header Information
- length : 2 (02h)
- protocol discr. : Radio Resources
- transaction id. : 0 (0h)
- message send from originating side
Cause
- length : 1 (01h)
- call control

29.

Channel Release (BSC to BTS to MS ;BTSM SDCCH )

Deactivation command of the used SDCCH.. This is sent by the BSC towards
the MS. Quite often this is also called '3rd layer disconnection'.
DATA REQ (RLL) T=1
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
CHANNEL RELEASE

(RR)

RR Cause

88 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

- normal

30.

Deactivate SACCH (BSC to BTS ;BTSM)

The BSC indicates to the BTS that system information messages towards the
MS are no longer required.
DEACT. SACCH (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1

31.

DISC (MS to BTS ;SDCCH)

The MS sends a Layer 2 frame DISConnect to the BTS to disconnect the


SDCCH.

32.

UA (BTS to MS ;SDCCH)

The BTS acknowledges DISC -frame. Consequences: the MS starts to listen


BCCH -channel again and all the Air interface resources are released.

33.

Release Indication (BTS to BSC;BTSM)

The BTS informs the BSC that the MS is no longer using the dedicated
resources.
REL IND (RLL) T=0
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0

34.

RF Channel Release (BSC to BTS ;BTSM)

The BSC tells the BTS to release the rest of the radio resources.
RF CHANNEL REL. (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

89 (119)

Signalling Examples

35.

RF Channel Release Ack . (BTS to BSC ;BTSM)

BTS send an acknowledgement to BSC.


RF CH. REL. ACK (DCh) T=0
Channel Nr
- SDCCH/8 subchannel 6
- timeslot : 1

36.

Clear Complete (BSC to MSC ;BSSMAP)

This is acknowledgement of the Clear Command. It informs the MSC that all
radio resources related to this call have been released.
- BSSMAP (length : 1, 01h)
CLEAR COMPLETE

37.

RLSD ;SCCP Released (MSC to BSC ;SCCP)

When all radio resources are released, the BSSAP connection concerning this
call is not needed any more. This message tells the BSC to release this SCCP
connection. The message is sent as RLSD message.
RLSD - RELEASED
Routing Label
- DPC : 432 (01B0h) OPC : 12600 (3138h)
- SLC : 3 (03h)
Destination Local Reference
- 098056h
Source Local Reference
- 43814Ch
Release Cause
- SCCP user originated

38.

RLC;SCCP Released Ack .(BSC to MSC ;SCCP)

The BSC acknowledges the SCCP_RELEASE message.


RLC - RELEASE COMPLETE
Routing Label
- DPC : 12600 (3138h) OPC : 432 (01B0h)
- SLC : 9 (09h)

90 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Location update

Destination Local Reference


- 43814Ch
Source Local Reference
- 098056h

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

91 (119)

Signalling Examples

Handovers
The measurements reported from BTS and MS are all the time monitored by the
BSC. These measurements are received for all active signalling and traffic
channels. In the BSC there are defined thresholds for e.g. the rx quality and rx
level and the measurement average values are compared with these. Based on
this comparison the BSC will decide if a handover is required. The reasons for
the handovers are listed below.

4.1

Inter-Cell Handovers

The different handover reasons

The inter-cell handovers are triggered for the following reasons:

92 (119)

uplink rx quality or rx level

downlink rx quality or rx level

MS-BTS distance

better cell (power budget)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

Synchronisation of handovers and Timing Advance

The inter-cell handover can be defined either as synchronised or as not


synchronised. In case the source and target cell use the same master
synchronisation source, which is only in the case that the target and source cell
belong to the same BCF, the handover can defined as synchronised. If the
source and target cell belongs to the same BCF they use the MCLG clocksignals from the BCFA card (3rd gen. BTS). In this case the MS can access the
target cell with the same Timing Advance as it used in the source cell.
The handover from one cell to another belonging to different BCF:s will be not
synchronised. This means that the MS will access with no timing advance to the
cell and the BTS has to correct the timing advance as the first thing after access.
This is done with a Physical Info message.

Intra-BSC HO signalling and resource allocation

In the intra-BSC handover the A-interface TCH allocated for the call can remain
as same. That allows the BSC to control the whole handover. The whole
handover procedure can be split into four parts: handover decision, new TCH
activation, the handover and release of the old TCH.
The handover decision is based on the threshold comparison done by the BSC.
When the BSC has noticed that there is a need for a HO the BSC will make a
target cell evaluation. If the target cell is under the same BSC it will be a intraBSC HO.
After this the BSC will activate a new traffic channel in the target BTS. The
third part is the handover itself. The BSC sends a Handover Command on the
old TCH (in FACCH signalling mode) to the MS with the information about the
target cell and TCH. The mobile station will change to this channel and send a
HO Access message to the target BTS over the new TCH (also in FACCH
mode). The target BTS will inform the BSC about the MS access with HO
Detect message. After this the MS establish the LapDm signalling. When the
BTS acknowledge the signalling connection to the MS, the MS sends a
Handover Complete message to the BSC. This message will acknowledge the
Handover Command sent by BSC and at this point the HO is considered
successful.
The last part is to inform the MSC that a handover took place and to release the
old radio resources, i.e. the old TCH and SACCH.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

93 (119)

Signalling Examples

Inter BSC HO signalling and resource allocation

As the inter-BSC HO requires also reallocation of the speech circuit used from
MSC to BSC, the MSC will control the HO procedure. The handover need
detection and target cell evaluation will be done in the same way as in the intraBSC HO. The difference in this case is that the chosen target cell is not under
the BSC controlling the source cell. In such case the source BSC will instead
send a Handover required to the MSC. The MSC will check the identification of
the requested target cell in its own cellular network configuration and send a
Handover Request to the BSC controlling that cell. The Target BSC will
activate a new TCH to the target BTS.
The handover itself is triggered as the target BSC sends a Handover Command
via the MSC to the source BSC and from there to the MS. The MS will access
the cell in the same way as it accessed to the target cell in the intra-BSC HO
case. The only difference is that the Handover Complete message is sent the
MSC, which will then send clear command to the source BSC. This will clear
the old resources used by the MS on the Abis, Air and A-interface.

4.2

Intra Cell Handovers


This type of handover is triggered only by interference. In case of interference
the rx level is good but the rx quality is bad. The reason for this is that there is
interference on the timeslot or frequency in use.
The intra-cell HO can be done from one timeslot to another on the same TRX or
from one TRX to another TRX in the cell if there are any. To make a handover
like this is to try to avoid the interfered resource. In case of one a TRX cell and
the whole frequency is interfered this handover type can cause so called pingpong handovers. This means that the system is all the time performing intra-cell
handovers. This can be avoided by disabling the intra-cell interference HO in
the cell.
The procedure itself is not like the inter-cell handover. In this case the BSC will
not use Handover Command, but instead it will use channel assignment
commands. Basically it can be compared to the TCH assignment in the call
setup but the source is instead of SDCCH a TCH. The phases of the intra-cell
HO are new TCH activation, assignment of the call to the new channel and
release of the source resources.

94 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

4.3

Handover Signalling Examples

Internal Handover, Intra Cell

MSC

BSC

BTS

MS
Measurement Report ( SACCH )

Measurement Report/Result

PHYSICAL
CONTEXT
INFORMATION

4
NEW
RESERVATION
AND
ACTIVATION

Channel Activation

Channel Activation Ack.

Assignment Command (FACCH )

SABM ( FACCH )
Establish Indication

9
10

15

1.

Receiver Ready ( FACCH )

12
RF Channel Release
RF Channel Release Ack.

SIGNALLING
ON FACCH OLD

UA ( FACCH )

Assignment Complete ( FACCH )

13

HO
MEASUREMENTS

Physical Context Request


Physical Context Confirmed

DT1 ( HO Performed )

14

SIGNALLING ON
FACCH NEW

11
OLD
RELEASE

MEASUREMENT_REPORT

When call is on, the MS sends measurement report concerning mainly the
quality of the speech connection two times per second.

2.

MEASUREMENT_REPORT/RESULT

If these measurement reports are pre-processed in the BTS then measurement


results are sent towards the BSC. If the is no pre-processing in the BTS, then
measurement reports are sent.

3.

PHYSICAL_CONTEXT_REQUEST

4.

PHYSICAL_CONTEXT_CONFIRM

5.

CHANNEL_ACTIVATION

The BSC sends a Channel Activation message to the BTS. After receiving
Handover Request from the MSC, the BSC starts to search and allocate TCH
for this call on certain terms, the most important is of course which BTS and
then the channel configuration of this BTS. Parameters: DTX control, channel
ID & description & mobile allocation, maximum power levels of the MS and
BS and finally, the first timing advance concerning this access calculated by the
BSC.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

95 (119)

Signalling Examples

6.

CHANNEL_ACTIVATION_ACK.

A response to the Channel Activation message. When BTS has received this
message it starts to send and receive TCH/SACCH. The reference used in this
case is the power levels received in Channel Activation message.

7.

ASSIGNMENT_COMMAND

8.

SABM (Set Asynchronous Balanced Mode)

This is Layer 2 message and contains some Layer 3 information. Content of this
message: service request (look establishment cause!), ciphering key sequence,
Mobile Station Classmark and Mobile Identity.

9.

ESTABLISH_INDICATION

BTS acknowledges the Immediate Assignment Command by returning


Establish Indication message. Establish indication -message has two uses.
Firstly, when used in this phase it points out that from the BTS point of view,
the MS is now on the new TCH. Thus, the BTS sends information back to the
BSC that the MS is now on this kind of TCH which description is like this etc.
Also the BTS identifies the link = main signalling channel and adds received
Layer 3 information into this message.

10.

UA

UA is normal Layer 2 level acknowledgement when setting up the Layer 2 level


link in LAPDm -protocol.

11.

ASSIGNMENT_COMPLETE

This message is sent by the MS to the network to indicate that the MS has
established the main signalling link successfully.

12.

RR

The BTS sends a Receive Ready message to the MS.

13.

HO_PERFORMED

The Handover Complete message is forwarded to the MSC. When the Handover
Complete message is received, the network releases the old channels.

14.

RF_CHANNEL_RELEASE

When MS has informed the network it is in the TCH, there is no need to use the
old TCH for this call setup any more. By Channel Release procedure it is
released.

15.

RF_CHANNEL_RELEASE_ACK.

The BTS acknowledges the Channel Release message.

96 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

Internal Handover, Inter Cell

MSC

BSC

BTS 2

BTS 1

Measurement Report ( SACCH )

Measurement Report/Result

Establish Indication

TCH
RESERVATION AND
ACTIVATION IN BTS2

8
11

HO Command ( FACCH )

HO Access ( FACCH )

SABME ( FACCH )

12

Handover Complete

17

15

14

SIGNALLING
ON FACCH IN BTS1

Physical Info ( FACCH )

10

SIGNALLING
ON FACCH IN BTS2

UA ( FACCH )
Handover Complete ( FACCH )

13

Receiver Ready ( FACCH )

RF Channel Release
RF Channel Release Ack.

1.

HO
MEASUREMENTS

Handover Command

Handover Detect

16

Channel Activation
Channel Activation Ack.

DT1 ( HO Performed )

MS

TCH RELEASE IN
BTS1

18

MEASUREMENT_REPORT

When call is on, the MS sends measurement report concerning mainly the
quality of the speech connection two times per second.

2.

MEASUREMENT_REPORT/RESULT

If these measurement reports are pre-processed in the BTS then measurement


results are sent towards the BSC. If the is no pre-processing in the BTS, then
measurement reports are sent.

3.

CHANNEL_ACTIVATION

The BSC sends a Channel Activation message to the BTS. After receiving
Handover Request from the MSC, the BSC starts to search and allocate a TCH
for this call on certain terms, the most important is of course which BTS and
then the channel configuration of this BTS. Parameters: DTX control, channel
ID & description & mobile allocation, maximum power levels of the MS and
BS and finally, the first timing advance concerning this access calculated by the
BSC.

4.

CHANNEL_ACTIVATION_ACK.

A response to the Channel Activation message. When BTS has received this
message it starts to send and receive TCH/SACCH. The reference used in this
case is the power levels received in Channel Activation message.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

97 (119)

Signalling Examples

5.

HO_COMMAND

Handover Command message is sent from the BSC to the BTS to change the
dedicated channel configuration and timing adjustment needed.

6.

HO_COMMAND

The BTS forwards the message to the MS.

7.

HO_ACCESS

The MS sends a Handover Access message in random mode to the new BTS.

8.

HO_DETECT

The new BTS informs the BSC, that it has detected a handover access message.

9.

PHYSICAL_INFO

The Physical Information message contains various physical layer related


informations, allowing a proper transmission by the MS.

10.

SABM (Set Asynchronous Balanced Mode)

This is Layer 2 message and contains some Layer 3 information. Content of this
message: service request (look establishment cause!), ciphering key sequence,
Mobile Station Classmark and Mobile Identity.

11.

ESTABLISH_INDICATION

BTS acknowledges the Immediate Assignment Command by returning


Establish Indication message. Establish indication -message has two uses.
Firstly, when used in this phase it points out that from the BTS point of view,
the MS is now on the new TCH. Thus, the BTS sends information back to the
BSC that the MS is now on this kind of TCH which description is like this etc.
Also the BTS identifies the link = main signalling channel and adds received
Layer 3 information into this message.

12.

UA

UA is normal Layer 2 level acknowledgement when setting up the Layer 2 level


link in LAPDm -protocol.

13.

HO_COMPLETE

This message is sent by the MS to the network to indicate that the MS has
established the main signalling link successfully.

14.

RR

The BTS sends a Receive Ready message to the MS.

15.

HO_COMPLETE

The Handover Complete message is sent to the BSC.

16.

HO_PERFORMED

The Handover Complete message is forwarded to the MSC. When the Handover
Complete message is received, the network releases the old channels.

98 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

17.

RF_CHANNEL_RELEASE

When MS has informed the network it is in the new TCH, there is no need to
use the old TCH for this call setup any more. By Channel Release procedure it
is released.

18.

RF_CHANNEL_RELEASE_ACK.

The BTS acknowledges the Channel Release message.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

99 (119)

Signalling Examples

External Handover

MSC

DT1

BSC1

BSC2

CR

HO Required

Measurement
R
t/R
lt

BTS 1

Measurement Report ( SACCH


HO
)
1
MEASUREMENTS
AND
DECISION

Channel Activation
Channel Activation Ack
.

CC HO_
Req.Ack
HO Command

TCH
RESERVATION
AND
ACTIVATION
IN BSS2
HO Command ( FACCH )

HandoverDetect
HO Detect

7
DT1 HandoverCommand
HO Command

HO Access ( FACCH )

11

12

13
15

16

HandoverComplete

19

14

UA ( FACCH )
HandoverComplete ( FACCH )

18

10

Physical Info ( FACCH )


SABME ( FACCH )

Establish Indication

DT1

MS

HO_Request)

DT1

BTS 2

17

Receiver Ready ( FACCH )

HO Complete20
DT1 Clear Command

21

22

RF Channel Release
RF Channel Release Ack
.

DT1

Clear Complete

RSLD

(SCCP Released)

RLC

(SCCP Released Ack)

1.

23

DISCONNECTION
AND TCH
RELEASE
IN BSS1

24

Measurement Report (MS to BTS1 ;SACCH)

When call is on, the MS sends measurement report concerning mainly the
quality of the speech connection two times per second.

2.

Measurement Report (BTS1 to BSC1;BTSM L3)

If these measurement reports are pre-processed in the BTS then measurement


results are sent towards the BSC. If the is no pre-processing in the BTS, then
measurement reports are sent.
MEAS. RES. (DCh) T=0
Channel Nr
- full rate TCH

100 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

- timeslot : 6
Meas.Res. Nr
- value : 10 (0ah)
Uplink Meas.
- length : 3 (3h)
- downlink DTX not used
- rxlev_full : 48 (-63 - -62 dBm)
- rxlev_sub : 45 (-66 - -65 dBm)
- rxqual_full : 0
- rxqual_sub : 0
BS Power
- power control level : 14 (eh)
L1 Info
- MS power control level : 0 (0h)
- actual TA : 0 (00h) (0 km)
L3 Info
MEASUREMENT REPORT (RR)
Measurement Results
- BCCH allocation sequence number : 0
- DTX was not used
- serving cell rxlev_full : 34 (-77 - -76 dBm)
- serving cell rxlev_sub : 34 (-77 - -76 dBm)
- measurement results are valid
- serving cell rxqual_full : 0
- serving cell rxqual_sub : 0
- number of neigh cell meas results : 1
- rxlev[1] : 31, (-80 - -79 dBm)
- neighbour BA index[1] : 1
- BSIC[1] : 0

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

101 (119)

Signalling Examples

3.

HO Required (BSC1 to MSC;BSSMAP )

The BSC informs the MSC, that according to the measurement results, a
handover is needed.
- BSSMAP (length : 12, 0Ch)
HANDOVER REQUIRED
Cause
- length : 1 (01h)
- better cell
Response Request
Cell Identifier List
- length : 5 (05h)
- cell identified with LAC + CI
- location area code : 2369 (0941h)
- cell identifier : 274 (0112h)

4.

( prefer cell )

HO Request (MSC to BSC02;BSSMAP)

The MSC sends a Handover Request message to the new BSC, which starts
channel activation. (Serving&Target)
- BSSMAP (length : 41, 29h)
HANDOVER REQUEST
Channel Type
- length : 3 (03h)
- speech
- TCH/FS
- GSM speech encoding algorithm version 1
Encryption Information
- length : 9 (09h)
- GSM user data encr. v. 1
- ciphering key, length : 8 (08h)
B8 30 95 D1 94 3D 3B AE
Classmark Type 2
- length : 2 (02h)
- revision level : reserved for phase 1

102 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

- encryption algorithm A5
- class 1, vehicle and portable
- frequency band 0
- short message capability present
Cell Identifier
- length : 5 (05h)
- cell identified with LAC + CI
- location area code : 1369 (0559h)
- cell identifier : 174 (00AEh)
Priority
- length : 1 (01h)
- priority level 2 (2h)
- queueing allowed
- preemption vulnerability indi not allowed
Circuit Identity Code
- pcm multiplex : 0 (000h)
- pcm timeslot : 28 (1Ch)
Cell Identifier
- length : 5 (05h)
- cell identified with LAC + CI
- location area code : 2369 (0941h)
- cell identifier : 274 (0112h)

5.

Channel Activation (BSC2 to BTS2;BTSM )

The BSC sends a Channel Activation message to the BTS. After receiving
Handover Request from the MSC, the BSC starts to search and allocate a TCH
for this call on certain terms, the most important is of course which BTS and
then the channel configuration of this BTS. Parameters: DTX control, channel
ID & description & mobile allocation, maximum power levels of the MS and
BS and finally, the first timing advance concerning this access calculated by the
BSC.
CHAN. ACT. (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 2

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

103 (119)

Signalling Examples

Act. Type
- asynchronous handover procedure
Channel Mode
- length : 4
- downlink DTX not used, uplink DTX not used
- channel type : 01h 08h 01h
Channel Id
- length : 6
- full rate TCH
- timeslot : 2
- training sequence code : 0
- hopping : 0
- Frequency band nr : 2
- ARFCN : 108 (6ch)
- frequencies included from CA :
Encr. Info
- lentgh : 9
- GSM A5/1
- ciphering key : B8 30 95 D1 94 3D
3B AE
Handover Ref.
- value : 10 (0ah)
BS Power
- power control level : 15 (fh)
MS Power
- power control level : 9 (9h)

104 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

6.

Channel Activation Ack .(BTS2 to BSC2;BTSM)

A response to the Channel Activation message. When BTS has received this
message it starts to send and receive TCH/SACCH. The reference used in this
case is the power levels received in Channel Activation message.
CHAN. ACT. ACK (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 2
Frame Number
- N32 : 7 (7h)
- N26 : 21 (15h)
- N51 : 27 (1bh)

7.

HO Req.Ack. (BSC2 to MSC;BSSMAP)

HO Command (L3)
After channel activation the new BSC sends a Handover Request Acknowledge
message to the MSC to indicate, that the channel activation procedure is
executed.
- BSSMAP (length : 15, 0Fh)
HANDOVER REQUEST ACKNOWLEDGE
Layer 3 Information
- length : 12 (0Ch)
HANDOVER COMMAND

(RR)

Cell Description
- BCCH band number : 2 (2h)
- NCC : 0 (0h)
- BCC : 0 (0h)
- BCCH carrier : 108
Channel Description
- full rate TCH
- timeslot : 2
- training sequence code : 0
- hopping : 0
- Frequency band nr : 2

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

105 (119)

Signalling Examples

- ARFCN : 108 (6ch)


Handover Reference
- value : 10 (0ah)
Power Command
- power level of MS : 9
Sync. Indication
- ROT:Time Diff IE excluded in HANDOVER
COMP msg
- SI: non-synchronized
- NCI: tim adv is ignored
Channel Mode
- speech FR or HR version 1

8.

HO Command (MSC to BSC1 ; BSSMAP L3)

Handover Command message is sent from the MSC to the BSC to change the
dedicated channel configuration and timing adjustment needed.
- BSSMAP (length : 15, 0Fh)
HANDOVER COMMAND
Layer 3 Information
- length : 12 (0Ch)
HANDOVER COMMAND

(RR)

Cell Description
- BCCH band number : 2 (2h)
- NCC : 0 (0h)
- BCC : 0 (0h)
- BCCH carrier : 108
Channel Description
- full rate TCH
- timeslot : 2
- training sequence code : 0
- hopping : 0
- Frequency band nr : 2
- ARFCN : 108 (6ch)

106 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

Handover Reference
- value : 10 (0ah)
Power Command
- power level of MS : 9
Sync. Indication
- ROT:Time Diff IE excluded in HANDOVER COMP msg
- SI: non-synchronized
- NCI: tim adv is ignored
Channel Mode
- speech FR or HR version 1

9.

HO command (BSC1 to BTS1 to MS;BTSM FACCH L3)

The BSC forwards the message via the BTS to the MS.
DATA REQ (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 6
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0
L3 Info
HANDOVER COMMAND

(RR)

Cell Description
- BCCH band number : 2 (2h)
- NCC : 0 (0h)
- BCC : 0 (0h)
- BCCH carrier : 108
Channel Description
- full rate TCH
- timeslot : 2
- training sequence code : 0
- hopping : 0
- Frequency band nr : 2

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

107 (119)

Signalling Examples

- ARFCN : 108 (6ch)


Handover Reference
- value : 10 (0ah)
Power Command
- power level of MS : 9
Sync. Indication
- ROT:Time Diff IE excluded in
HANDOVER COMP msg
- SI: non-synchronized
- NCI: tim adv is ignored
Channel Mode
- speech FR or HR version 1

10.

HO Access (MS to BTS2;FACCH )

The MS sends a Handover Access message in random mode to the new BTS.

11.

HO Detect (BTS2 to BSC2; BTSM)

The new BTS informs the BSC, that it has detected a handover access message.
HANDOVER DET. (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 2
Access Delay
- value : 1 (01h)

12.

HO Detect (BSC2 to MSC ;BSSMAP)

The new BSC sends a Handover Detection message to the MSC, which starts
channel establishment procedure on the new BSS.
- BSSMAP (length : 1, 01h)
HANDOVER DETECT

13.

Physical Info (BTS2 to MS;FACCH)

The Physical Information message contains various physical layer related


information, allowing a proper transmission by the MS.

108 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

14.

SABM (MS to BTS2;FACCH)

This is Layer 2 message and contains some Layer 3 information. Content of this
message: service request (look establishment cause!), ciphering key sequence,
Mobile Station Classmark and Mobile Identity.

15.

Establish Indication (BTS2 to BSC2;BTSM)

BTS acknowledges the Immediate Assignment Command by returning


Establish Indication message. Establish indication -message has two uses.
Firstly, when used in this phase it points out that from the BTS point of view,
the MS is now on the new TCH. Thus, the BTS sends information back to the
BSC that the MS is now on this kind of TCH which description is like this etc.
Also the BTS identifies the link = main signalling channel and adds received
Layer 3 information into this message.
EST. IND (RLL) T=0
Channel Nr
- full rate TCH
- timeslot : 2
Link Id
- main DCCH (FACCH or SDCCH)
- SAPI : 0

16.

UA (BTS2 to MS ;FACCH)

UA is normal Layer 2 level acknowledgement when setting up the Layer 2 level


link in LAPDm -protocol.

17.

Handover Complete (MS to BTS2 ;FACCH)

This message is sent by the MS to the network to indicate that the MS has
established the main signalling link successfully.

18.

Receiver Ready (BTS2 to MS;FACCH)

The BTS sends a Receive Ready message to the MS.

19.

Handover Complete (BTS2 to BSC2; BTSM L3)

The Handover Complete message is forwarded to the BSC.


DATA IND (RLL) T=1
Channel Nr
- full rate TCH
- timeslot : 2
Link Id
- main DCCH (FACCH or SDCCH)

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

109 (119)

Signalling Examples

- SAPI : 0
L3 Info
HANDOVER COMPLETE

(RR)

RR Cause
- normal

20.

Handover Complete (BSC2 to MSC;BSSMAP L3)

The Handover Complete message is forwarded to the MSC. When the Handover
Complete message is received, the network releases the old channels.
- BSSMAP (length : 3, 03h)
HANDOVER COMPLETE
RR Cause
- normal

21.

Clear command (MSC to BSC1 ;BSSMAP )

This message is coming from the MSC and releases the associated dedicated
resources, i.e. BSSAP connection concerning this call.
- BSSMAP (length : 8, 08h)
CLEAR COMMAND
L3 Header Information
- length : 2 (02h)
- protocol discr. : Radio Resources
- transaction id. : 0 (0h)
- message send from originating side
Cause
- length : 1 (01h)
- handover succesful

110 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

Handovers

22.

RF Channel Release (BSC1 to BTS1;BTSM)

When MS has informed the network it is in the TCH, there is no need to use the
old TCH for this call setup any more. By Channel Release procedure it is
released.
RF CHANNEL REL. (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 2

23.

RF Channel Release Ack .(BTS1 to BSC1;BTSM)

The BTS acknowledges the Channel Release message.


RF CH. REL. ACK (DCh) T=0
Channel Nr
- full rate TCH
- timeslot : 2

24.

Clear Complete (BSC1 to MSC ;BSSMAP)

This is acknowledgement to the message BSSMAP Data (Clear Command).


Now the BSC informs the MSC that all radio resources related to this call are
released.
- BSSMAP (length : 1, 01h)
CLEAR COMPLETE

25.

RSLD ;SCCP Released (MSC to BSC1;SCCP)

RLSD - RELEASED
Routing Label
- DPC : 688 (02B0h) OPC : 12600 (3138h)
- SLC : 7 (07h)
Destination Local Reference
- 038056h
Source Local Reference
- F7404Ch
Release Cause
- SCCP user originated

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

111 (119)

Signalling Examples

26.

RLC;SCCP Released Ack .(BSC1 to MSC SCCP)

RLC - RELEASE COMPLETE


Routing Label
- DPC : 12600 (3138h) OPC : 688 (02B0h)
- SLC : 3 (03h)
Destination Local Reference
- F7404Ch
Source Local Reference
- 038056h

112 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

BCCH and system information

BCCH and system information


The BCCH is a Common Control Channel following 51 TDMA multiframe. It
is transmitted in the timeslot 0 on one of the frequencies of each cell/sector in
the TDMA-frame following the synchronisation channel (SCH).
The information to be sent is divided to different information elements, which
are distributed by several System Information Type messages.

5.1

System info type -messages


In the following list the information elements of the System Info Type 1-6
messages are according to GSM phase 1 specifications. The System Info Type
2bis, 5bis, 2ter, 5ter, 7 and 8 messages are according to GSM phase 2
specifications.

SYSTEM INFO TYPE 1

Cell Channel Description

RACH Control Parameters

SYSTEM INFO TYPE 2

NTC CTXX 0677


Issue 4.0 en

Neighbour Cells Description

NCC Permitted

RACH Control Parameters

Nokia Telecommunications Oy

113 (119)

Signalling Examples

SYSTEM INFO TYPE 3

Cell Identity

Location Area id.

Control Channel Description

Cell Options

Cell Selection Params

RACH Control Params

SYSTEM INFO TYPE 4

Location Area Identification

Cell Selection Params

RACH Control Params

SYSTEM INFO TYPE 5

Neighbour Cells Description

SYSTEM INFO TYPE 6

Cell Identity

Location Area Identification

Cell Options

NCC Permitted

System Info Type 5 and 6 are used in handover situations. They are sent first
right after a handover on the Slow Associated Control Channel (SACCH) and
then whenever there is nothing else to be sent on that channel.

SYSTEM INFO TYPE 2bis

114 (119)

Neighbour Cells Description

RACH Control Params

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

BCCH and system information

SYSTEM INFO TYPE 5bis

Neighbour Cells Description

SYSTEM INFO TYPE 2ter

Additional multiband information

Neighbour Cells Description

SYSTEM INFO TYPE 5ter

Additional multiband information

Neighbour Cells Description

SYSTEM INFO TYPE 7

SYSTEM INFO TYPE 8

System info type 7 and 8 are sent giving information about cell reselect
parameters to be used in that cell.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

115 (119)

Signalling Examples

5.2

Information elements
In the following all the information elements, which are transmitted on the
BCCH are listed along with their purpose, explanations and examples of usage.

Cell Channel Description

This information element provides the frequency reference list to be used to


decode the mobile allocation information element. Mobile allocation IE defines
the frequencies to be used in frequency hopping.

RACH Control Parameters

The purpose of this IE is to control the way the mobiles use the Random Access
Channel (RACH) and whether or not MS is allowed to access the cell:

max retrans of access burst (RET)


-

maximum number of retransmissions on RACH by the MS

range 1,2,4,7

related MML-command(s):EQM, EQO

# of slots to spread transm. (SLO)


-

the number of TDMA frames over which retransmission is spread in


the random access channel. Range 3..12, 14, 16, 20, 25, 32, 50

related MML-command(s): EQM, EQO

cell is not barred (BAR)


-

the parameter indicates if MSs are not allowed to access the cell.

related command(s):EQF EQO

call reestablishment not allowed (RE)


-

the parameter indicates if call re-establishment is allowed in the cell.

related command(s):EQF EQ

emerg. call allowed for all MSs


-

116 (119)

specifies whether emergency calls are allowed for mobiles or only for
those mobiles whose SIMs have access class 11-15.

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

BCCH and system information

allowed acc. Classes


-

access Classes are given by each operator randomly between 0-9 to


all subscribers and it is stored in the
SIM. In overload or maintenance situations this feature can be used to
bar 10-100% of the mobiles from accessing the network. All
subscribers have an access class between 1-10, but above that they
may have also an extra access class between 11-15, thus enabling
privilege user classes for security services, public utilities, emergency
service and PLM staff

Neighbour Cells Description

This IE contains the BCCH frequencies of adjancent cells to be monitored by


the mobile

BA-list, BCCH Allocation Frequency List, max. 32 frqs.


-

related MML-command(s):EBC EBM EBO

NCC Permitted

This IE provides the list of permitted network colour codes of which the mobile
station is allowed to monitor the BCCH frequencies.

Cell Identity

This element gives cell identity, which uniquely identifies one cell within
location area.

Location Area id.

This IE identifies uniquely the location area in the whole GSM system. It
includes mobile country code (MCC) and mobile network code (MNC) and
location area code (LAC).

Control Channel Description

Structure of Common Control Channel is defined in this IE

NTC CTXX 0677


Issue 4.0 en

IMSI attach/detach

access grant block reserved

Nokia Telecommunications Oy

117 (119)

Signalling Examples

- The number of the block reserved for access grant.


- Range depends on the control channel structure:
- 0..7

(if combined BCCH not used)

- 1..7

(if CBCH used at SDCCH/8)

- 0..2

(if combined BCCH used)

- The bigger this value is, less capacity we have for paging
- A common setting is having a combined control channel, reserving 1
block for access grant channels and 2 block for paging.

CCCH configuration
- Determines the number of physical channels used for Common
Control Channels and if the CCCH is combined with the SDCCHs.

Paging group repeat rate


- Determines the number of multiframes between the sending of paging
messages to the same paging subgroup.

Periodic loc upd timer T3212


- This value sets the periodic location update period of the mobiles, if
the value is 0 no periodic update is done. Values from 1 to 225 define
the location update period in decihours (from 6 minutes to 22.5
hours).

Cell Options

PWRC power control indicator


- This parameter tells the mobile station not to include the BCCH
frequency when it makes measurements of received levels. This is set
if frequency hopping is activated and the BCCH frequency is among
the hopping ones and downlink transmission power control is
activated. MS knows not to include measurements on the BCCH
frequency when it averages its measurements on the RXLEV as that
might yield invalid results since all the burst on the BCCH frequency
are always sent with constant power.

DTX Discontinuous Transmission


- This parameter determines whether the MSs must, may or may not use
discontinuous transmission. DTX means that the MS transmits speech
frames only when voice activity is detected, otherwise so called silent
frames are sent every 480 ms.

118 (119)

Nokia Telecommunications Oy

NTC CTXX 0677


Issue 4.0 en

BCCH and system information

Radio Link Timeout


- Specifies the initialising value for the radio link timeout counter in the
MS. Each time when the MS is not able to decode a SACCH message
properly the value is decreased by one and when a SACCH message is
properly decoded, the value of the counter is increased by 2, but not
above the radio link timeout.
- When the counter reaches 0 it will taken as a radio link failure
- The maximum value of the radio link counter expressed in SACCH
blocks. The possible values range from 4 to 64 blocks, and can be
changed by 4 block steps at a time

Cell Selection Parameters

Contains parameters for the calculation of the path loss criterion C1, which is
used in cell selection
Cell reselect hysteresis

The received RF power level hysteresis for required cell reselection. The value
is added to the C1 value to bias the selection of a cell
- The possible values range from 0 to 14 dB, and can be changed by 2
dB steps at a time.

MS TXPWR MAX CCH


- The maximum transmission power an MS may use when accessing a
CCH in the cell.

RXLEV ACCESS MIN


- The minimum power level an MS has to receive before it is allowed to
access the cell. The possible values range from -110 dBm to -47 dBm.

NTC CTXX 0677


Issue 4.0 en

Nokia Telecommunications Oy

119 (119)

Vous aimerez peut-être aussi