3.

Signaling in GSM
a) Signaling protocols in GSM
HLR

VLR

MAP

MAP
MAP

VLR
MAP
PSTN /
ISDN

HLR

MAP/ISUP

AUC

MAP
MAP/ISUP

MAP/ISUP

MSC

MAP

MSC

MAP

MSC

EIR

PLMN
BSSAP/Q.931

BSC

BSS

LAPD/Q.931/RR/MM
BTS
LAPDm/Q.931/RR/MM
MS
Note:

VLR may be integrated with MSC &

AUC may be integrated with HLR

Figure 3.1 - GSM system model - signaling view

-------------------------------------------------------------------------------------------------86

b) Mobile Application Part in GSM

Dialog

MAP

MAP

TCAP

Transaction

TCAP

SCCP

SCCP

SCCP

MTP

MTP

MTP

Node A

Node X

Node B

Application
Layer 7

NSP
Layers 1-3

Figure 3.2 MAP & OSI model

1) MAP Application Entities (AEs)
MAP to MAP communication between MAP entities

Location Registration
Location cancellation
De-registration
Transfer of subscriber data/service profile
Transfer of authentication/security data
Routing of mobile-terminated calls
Handover
MAP Application Entities (AEs) with
Subsystem Numbers (SSNs)

MAP-MSC
MAP-VLR
MAP-HLR
MAP-EIR
MAP-AUC
MAP-SM-SC

-------------------------------------------------------------------------------------------------87

2) Application Service Elements (ASEs)

ASE
1

Node A

Node B

MAP-VLR

MAP-HLR

ASE
2

ASE
1

ASE
3

ASE
2

ASE
3

TCAP ASE

TCAP ASE

Component sub-layer

Component sub-layer

Transaction sub-layer

Transaction sub-layer

SSN

SSN

NSP
Figure 3.3 MAP AEs & ASEs
ASEs are software functions within Application Entities and
handle one or more operations to handle a task. One entity may
have to interact concurrently with several other entities, as in the
case of hand-over.

ASE 1
MAP
VLR

Logical connections

ASE 1

ASE 2

ASE 2

ASE 1

ASE 1

ASE 2

ASE 2

MAP
HLR

Figure 3.4 MAP ASEs & logical connections

-------------------------------------------------------------------------------------------------88

Examples of ASE operations

Location updating
Insert subscriber data
Location Cancellation

VLR >> HLR

HLR >> VLR
HLR >> VLR

Functions

Functions

Location
Updating

Location
Updating

Location
Cancellation

T
C
A
P

N
S
P

N
S
P

T
C
A
P

Location
Cancellation

Roaming
Number

Roaming
Number

MSC/VLR

HLR

Figure 3.5 MAP in MSC/VLR & HLR and the ASEs

c) BSS Application Part in GSM

Transparent to BSS
DTAP

LAPDm
M

Initial MS Messages M

BSSMAP

S
C

BSC/BTS
Figure 3.6 BSSAP protocols between MS & MSC

-------------------------------------------------------------------------------------------------89

1) Direct Transfer Application Part (DTAP) Messages

Types of DTAP messages

Mobility management messages

Call control messages (Q.931) (SCCP connection-less)
(for circuit-switched connections)
Supplementary service control

Direct transfer messages pass through transparently through the

BSS. Call control messages are transported between BSC &
MSC using the connection-less services of SCCP.
Mobility management messages
Registration
messages

Connection
management (CM)
messages

Security messages

Location Updating
Request

Authentication
Request

CM Service Request

Location Updating
Accept

Authentication
Response

CM Service Accept

Location Updating
Reject

Authentication
Reject

CM Service Reject

Identity Request
Identity Response
Figure 3.7 DTAP messages for mobility management

-------------------------------------------------------------------------------------------------90

Call control messages for circuit-switched connections

Call setup phase

Call supervision

Call clearing

Setup

Modify

Disconnect

Call Proceeding

Modify Reject

Release

Emergency Setup

Release Complete

Progress
Alerting
Connect
Connect
Acknowledged
Figure 3.8 DTAP messages for circuit-mode connections
Supplementary service control messages
FACILITY (Request/Accepted/Reject)
The message contains an Information Element called
Facility in which the service to be invoked is specified.
2) Initial MS Messages
Some Initial MS messages

CM-Service Request (Connection Management)

Location Updating Request
Paging Response

-------------------------------------------------------------------------------------------------91

These Initial MS messages are semi-transparent in the sense that

the BSS analyses them and may add some information such as
CGI to a Service Request message. This may be required for
cell-dependent charging or for routing an emergency call.
Otherwise, the messages pass through BSS transparently.
3) BSS Management (BSSMAP) Messages
BSSMAP messages are used between MSC and BSS. They are
required for paging order, handover control, Radio Resource (RR)
management, etc.
Both the connection-less and connection-oriented services of
SCCP are used to transport BSSMAP messages.
Connection-less

Connection-oriented

Block

Assignment Request

Blocking Acknowledge

Assignment Complete

Unblock

Assignment Failure

Unblocking Acknowledge

Cipher Mode Command

Reset

Clear Request

Reset Acknowledge

Clear Command

Reset Circuit

Clear Complete

Reset Circuit Acknowledge

Class-mark Update

Paging

Handover Command
Handover Complete
Handover Failure
Complete Layer 3 Information

Figure 3.9 BSSMAP messages

-------------------------------------------------------------------------------------------------92

d) A-Interface Signaling between MSC & BSS

Of the PCM links between the MSC & BSC, one or more timeslots
are used as bearer for BSSAP signaling. BSSAP transports DTAP,
Initial MS & BSSMAP messages using both connection-less and
connection-oriented services of SCCP. Initial MS messages and
DTAP messages are transported identically.
A virtual connection is established for every call before callassociated messages are transported.

BSSAP
DTAP

BSSAP

BSSMAP

DTAP

BSSMAP

Distribution
Sub-layer

Distribution
Sub-layer

SCCP

SCCP

MTP

MTP

BSC

A-Interface

MSC

Figure 3.10 BSSAP & the A-Interface

Distribution Data Unit

Figure 3.11 Header of BSSAP messages
Header of the message consists of Distribution Data Unit. This
information is used by the Distribution Sub-layer to distinguish
between DTAP & BSSMAP messages.

-------------------------------------------------------------------------------------------------93

BSSMAP

DTAP
Discrimination

Discrimination

DLCI
Length

Length
Message Type

Message type

TI / PD
INFO

INFO
Figure 3.12 BSSAP Message structure
Header Discrimination

Discrimination field of one octet (and also DLCI octet in the case of
DTAP) constitutes the header for analysis by the Distribution Sublayer.
In the case of DTAP messages bit 7 of Discrimination further
distinguishes whether the message is transparent through the BSS.
Bit 7:

0
1

not transparent
transparent

Header Data Link Connection Identifier (DLCI)

Bit 7 6:

00
10

FACCH
SACCH

Bit 1 0:

00
SAPI = 0 = Call control signaling (Q.931)
11
SAPI = 3 = Short Message Service
Message Type examples
H 01
H 02
H 10
H 11

Assign Request
Assign Complete
Handover Request
Handover Required

-------------------------------------------------------------------------------------------------94

Protocol Discriminator (PD)

PD distinguishes between messages belonging to different
procedures such as:

Call Control
Mobility Management
Radio Resource Management
Supplementary Service control
Others

Transaction Identifier (TI)

TI distinguishes between multiple concurrent ongoing transactions
within one mobile station.
TI is equivalent to the call reference field defined for Q.931.

e) Layer 2 signaling between BSC & BTS

1) General
There may be one or more PCM links between BSC & BTS. One
of the 64 Kbps is used for signaling. Other timeslots are used for
voice or data traffic. To save on transmission, four traffic
channels may be packed into one 64Kbps timeslot.
The signaling link may carry signaling messages to or from either
the BTS or MS.
While a 64Kbps timeslot provides the Layer 1 bearer channel, we
need Layer 2 link control functions to take care of bit errors,
acknowledgement, retransmission, etc. LAPD protocol specified
for ISDN D-channel signaling is used between BSC & BTS for this
purpose.
2) LAPD Protocol
LAPD frame
LAPD supports two types of information transfer services.
-------------------------------------------------------------------------------------------------95

10

 Unacknowledged Information Transfer

Layer 3 information is transferred in unnumbered frames. FCS
field is used to detect errors and discard errored frames but
there is no error or flow control. The control field consists of
one octet.
Acknowledged Information Transfer
Layer 3 information is transferred in numbered frames that are
acknowledged. The protocol includes error control and flow
control procedures. This is also known as multiple-frame
operation whereby multiple LAPD logical connections can be
established, similar to multiple virtual circuits of X.25.

FCS

Info

Control

Address

Figure 3.13 LAPD frame structure

Address field in the LAPD frame
TEI
C/R
SAPI
TEI

SAPI

C/R

Command / Response
Service Access Point Identifier
Terminal Endpoint Identifier
Figure 3.14 LAPD Address field

SAPI is the address used to access different functions such as

call control signaling.
SAPI = 0

Radio Signaling Link / Traffic Management

Procedures / Call Control signaling

SAPI = 62

Operation & Maintenance Procedures

SAPI = 63

Layer 2 Management procedures

-------------------------------------------------------------------------------------------------96

11

TEI is the address used to access different entities such as

individual TRX for radio signaling.
SAPI & TEI in the address field together identify the right entity
and functions.
BTS & the Abis interface
TRX 1
TRX 2

Abis

BSC

TRX 3

MSC

BC
BTS site

BC
TRX

Base Controller (Functions)

Transceiver

Figure 3.15 Abis interface between the BSC & the BTS
One of the timeslots in the PCM link between the BSC & the BTS
is used for signaling between them. The signaling uses LAPD
protocol for layer 2.

SAPI & TEI

SAPI = 0 (Radio signaling)

SAPI = 62 (O&M)

TEI = 3
TEI = 4
TEI = 5

BC functions
BC
BC

SAPI = 63 (Layer 2)

TEI = 6

Layer 2 functions

TEI = 0
TEI = 1
TEI = 2

TRX 1
TRX 2
TRX 3

Figure 3.16 Addressing by SAPI & TEI

-------------------------------------------------------------------------------------------------97

12

Normally, more than one transceiver is located in a BTS. They

need to be accessed to transmit certain signaling information to
the MS.
A base controller is needed to control functions such as frequency
hopping, time base for the BTS, power supply, etc. that need to
be controlled by the signaling management.
SAPI & TEI are used to address the transceivers & functions.
TEI values are assigned manually in GSM.
The control field in the LAPD frame
LAPD supports three types of frames that can be identified by the
control field.
I-frame or the information frame. Bit 0 of I-frame is always set
to zero. I-frame is used for transferring layer 3 information.
The N(S) & N(R) fields in the control field represent Send &
Receive counters at the two ends, maintained by layer 2.

C/R

15 14 13 12 11 10 9

7 6 5 4 3 2 1

N(R)

N(S)

Figure 3.17 Control field of an I frame

S-frame or the Supervisory frame. Bits 1 & 0 of S-frames are
always set to the combination 01.
Figure 12.17 Control field of an I frame
15 14 13 12 11 10 9
8
7 6 5 4

3 2 1 0

C/R

RR

N(R)

P/F

0 0 0 0

0 0 0 1

RNR

N(R)

P/F

0 0 0 0

0 1 0 1

REJ

N(R)

P/F

0 0 0 0

1 0 0 1

Figure 3.18 Control field of an S frame

-------------------------------------------------------------------------------------------------98

13

Layer 2 uses S-frames to inform the sending end to either

proceed, to hold transmission or to retransmit. These are
Receiver Ready (RR), Receiver Not Ready (RNR) and
Reject (REJ) frames used for acknowledging I-frames.
U-frame or Unnumbered frame. These frames are used for
setting up or dismantling of layer 2 logical link. U-frame can
also be used for carrying UI or Unnumbered Information.
U-frames are only one octet long.
7 6 5

3 2 1 0

SABME

0 0 1

1 1 1 1

DM

0 0 0

1 1 1 1

UI

0 0 0

0 0 1 1

DISC

0 1 0

0 0 1 1

UA

0 0 1

0 0 1 1

SABME
DM
UI
DISC
UA

Set Asynchronous Balanced Mode Extended

Disconnected Mode
Unnumbered Information
Disconnect
Unnumbered Acknowledge

Figure 3.19 Control field of an U frame

Poll/Final bits are used for forcing (polling) a response (from
the other end) by setting P bit to ONE in the command frame.
The F bit is set to ONE in the resulting Response frame.
The Send & Receive Counters in LAPD protocol
The send counter is stepped up after sending and receive counter
after receiving an I-frame. The counters indicate the next I-frame
to be sent or to be received. Thus the N(R) in the I-frame, RR,
RNR or REJ frames acknowledge the receipt of N(R) 1 frame.

-------------------------------------------------------------------------------------------------99

14

A received I-frame can be acknowledged by an outgoing I-frame.

If there is no outgoing I-frame, the S-frame RR or RNR can be
used after having received a number of I-frames equal to the
window size. RNR is used if the receiver is not ready to receive
further messages and wants to do flow-control. Later whenever
ready, the receiver can send the RR frame.

FCS

Info
N(R)

Control
P/F

N(S)

N(S)
N(R)

Counter R
N(S)

Counter R
(R)

XX

XX

00

00

00

01

01
01
I

02

01

02

02

Counter S

UA

I
02

N(R)

SABME

I
01

Counter S

(S)

Address

00

00

00

01

01

01

REJ

01

01

01

01

02

X
S
I

(S)

(R)

XX

XX

00

00

00

01

01

01

01

01

01

02

02

02

DISC
UA
Figure 3.20 Send Receive Counters and N(S) & N(R)
-------------------------------------------------------------------------------------------------100

15

f) Layer 2 signaling between BTS & MS

1) General
LAPDm protocol is used in GSM between BTS & MS to transfer
layer 3 information. The layer 3 information may be sent over
BCH, CCH or the DCCH. LAPDm is implemented in the MS and
the BTS controller.
LAPDm is based on LAPD functionality but adapted to the needs
of radio interface. While LAPD allows for frame lengths of up to
249 + 11 octets, LAPDm uses frame segments of 18, 20 or 22
octets depending on the radio channel.
2) LAPDm Protocol
Operation modes
BCCH, PCH & AGCH
Unacknowledged mode only
SDCCH, SACCH & FACCH Both Acknowledged and
Unacknowledged modes
Unacknowledged operation
Messages are sent in UI-frames. There is no error correction or
flow control for these messages. Unacknowledged messages in
UI frames do not exceed a total length of 22 octets.
Acknowledged operation
Layer 3 messages are sent in numbered I-frames. Next I-frame
is sent only after the previous one has been acknowledged.
Acknowledged messages over I-frames may have a maximum
length of 249 octets and would require segmentation for sending
over the radio interface.
Segmentation
Segmentation is not necessary for unacknowledged messages
sent over the BCCH or the CCCH channels, as they do not
exceed a total length of 22 octets. All other messages need to be
buffered and segmented before transmission. At the receiving
end they need to be reassembled by layer 2.
-------------------------------------------------------------------------------------------------101

16

Depending on the frame type to be sent, different information is

added by the layer 2. The maximum length of a segment
including the length indicator is 23 octets.

Layer 3 Information

Layer 3 Information

22 Octets

Max. 249 Octets

Layer 2 operation

Layer 2 operation

Unacknowledged
Mode
BCCH
CCCH

Acknowledged Mode
SDCCH
SACCH
FACCH

22 Octets

Max. 249 Octets

Segmentation
20 (18) Octets
20 (18) Octets
20
20(18)
(18)Octets
Octets

Buffer
Max
249
20 (18) Octets
Octets

22 Octets

184 bits

20 Octets
31

23 Octets

18 Octets
31
21 Octets +
Timer Alignment
Power Order

+ Fire Code & Convolution Coding

456 bits
Layer 1 operation

Interleaving

Figure 3.21 Segmentation & signaling over Radio Interface

-------------------------------------------------------------------------------------------------102

17

LAPDm functions

Filler

Info

Length

Control

Address

Figure 3.22 A LAPDm frame carrying Layer 3 Info segment

The Layer 3 information is broken up into a number of
segments
If the Layer 3 information is shorter than 23 octets including
Address, Control, Length & Flags, fill bits are added.
Note that the FCS field is not used in LAPDm since the layer 1
does convolution coding & adds the Fire code for each
segment.
Length Indicator is added to show the length of Layer 3
Information segment.
Address field in the LAPDm frame
Address field in LAPDm is of one octet. We have a Link Protocol
Discriminator (LPD) sub-field of 2 bits. LPD=1 corresponds to
SMS Cell Broadcast (SMSCB) service.

0
C/R
SAPI
LPD

LPD

SAPI

C/R

Command / Response
Service Access Point Identifier
Link Protocol Discriminator
Figure 3.23 LAPDm Address field

Control field in the LAPDm frame

The control field of 1 octet identifies three types of frame formats.
I-frame is used to transfer Layer 3 information in modulo-8
sequentially numbered frames.
-------------------------------------------------------------------------------------------------103

18

N(R)

C/R

N(S)

Figure 3.24 LAPDm Control field of an I-frame

S-frame is used for data link Supervisory control functions such
as request for retransmission of an I-frame.
7

C/R

RR

N(R)

P/F

RNR

N(R)

P/F

REJ

N(R)

P/F

Figure 3.25 Control field of an S frame in LAPDm

U-frame provides for additional data link control functions and
also Unacknowledged Information (UI) transfer.
C

SABM
DM

0
7 0
6 1
5
0 0 0

P
4
F

1
3 1
2 1
1 1
0
1 1 1 1

R
C

UI

0 0 0

0 0 1 1

DISC

0 1 0

0 0 1 1

UA

0 0 1

0 0 1 1

SABM
DM
UI
DISC
UA

Set Asynchronous Balanced Mode Extended

Disconnected Mode
Unnumbered Information
Disconnect
Unnumbered Acknowledge

Figure 3.26 Control field of an U frame in LAPDm

-------------------------------------------------------------------------------------------------104

19

Length Indicator octet in the LAPDm frame

7

Length

EL

Figure 3.27 LAPDm Length field in an I-frame

EL
M

Length Indicator Extension bit

More Data bit
Used to indicate that the original layer 3 information
has been segmented and there is more to come. M
bit is set to ONE for the last segment.

Length Value below the maximum length indicates filler bits

at the end of Info.
Filler octets
Up-link
Down-link

FF
2B

--------------------------------------------------------------------------------------------------

20

105
3) LAPDm Protocol & a Traffic Case

MS

BTS
SABM (Paging Response)
UA (Paging Response)

A data link on SDCCH

is established

I (Authentication Request)
N(S) = 0, N(R) = 0
I (Authentication Response)
N(S) = 0, N(R) = 1
I (Cipher Mode Command)
N(S) = 1, N(R) = 1
I (Cipher Mode Complete)
N(S) = 1, N(R) = 2
I (Setup)
N(S) = 2, N(R) = 2
RR
N(R) = 3
I (Setup)

An S-frame RR is lost;
After timeout, I-frame
N(S) = 2 is repeated

N(S) = 2, N(R) = 2
RR
N(R) = 3
I (Setup)

A setup message may

need more than one Iframe

N(S) = 3, N(R) = 2
Figure 3.28 LAPDm & a call setup scenario
--------------------------------------------------------------------------------------------------

21

106

f) Call scenarios & signaling sequences

1) Incoming call to MS
GMSC
IAM

HLR

MSC/VLR

TC-INV (Send Routing info)

TC-INV (Provide Roaming)
TC-BEGIN
TC-BEGIN
TC-RES (Send Routing Info)
TC-END

TC-RES (Provide Roaming)

TC-END

IAM (ISUP)
Figure 3.29 a) MAP dialog for MSRN
MSC/VLR

BSC

MS

Page (BSSMAP) (UDT)

SCCP-CR (Paging Result)
SCCP-CC
Authentication Request (DTAP)
Authentication Response (DTAP)
CIPHER MODE CMD (DT1)
CIPHER MODE COMP (DT1)
SETUP (DTAP)
CALL CONFIRM (DTAP)
ASSIGNMENT REQ (DT1)
ACM

ASSIGNMENT COMP (DT1)

Figure 3.29 b) Call setup BSSMAP & Q.931 over DTAP

--------------------------------------------------------------------------------------------------

22

107

MSC/VLR

BSC

MS

ALERTING (DTAP)

CPG

CONNECT (DTAP)

ANM

CONNECT ACK (DTAP)

SCCP-IT (DT1)
SCCP-IT (DT1)
Conversation
DISCONNECT (DTAP)
REL

RELEASE (DTAP)
RELESE COMPLETE (DTAP)
Clear Command (DT1)
Clear Complete (DT1)
SCCP-RLSD
SCCP-RLC

Figure 3.29 c) Call completion & clear BSSMAP & Q.931 over DTAP
2) Call handling phases within the BSS
Call to MS

Call from MS

Paging
Immediate Assignment
Assignment
Handover
Call clearing
Figure 3.30 Call handling phases in the BSS
--------------------------------------------------------------------------------------------------

23

108
3) Paging & Immediate Assignment
MSC/VLR

BSC

BTS

MS

Page (UDT)
Paging Command
Channel Required
Channel ACT

Paging (PCH)
Channel REQ
(RACH)

Channel ACT Ack

Immediate Assign
Command

Immediate Assign
(AGCH)
SABM (Page Resp.)
(SDCCH)
UA (Page Resp.)

Establish Ind.
(Paging Response)
SCCP-CR
(Page Resp.)
SCCP-CC
Figure 3.31 Paging & Immediate Assignment
Paging
The procedure starts with the PAGING message sent by the MSC
to the BSC. The BSC in turn sends PAGING COMMAND to each
BTS of the cells of the specified Location Area.
Immediate Assignment
On receipt of a request on the RACH, the BTS sends a
CHANNEL REQUIRED message to the BSC. BSC allocates a
free SDCCH and asks BTS to activate it.
--------------------------------------------------------------------------------------------------

24

109
On receipt of acknowledgement, BSC sends an IMMEDIATE
ASSIGNMENT to the BTS which relays this to the MS on the
AGCH asking the MS to switch to the allocated SDCCH.
The BTS & the MS establish a LAPDm data link on the SDCCH
by means of SABM & UA frames. The MS piggybacks the
PAGING RESPONSE information on the SABM. The BTS then
sends the ESTABLISH INDICATION message to the BSC.
The BSC initiates the SCCP logical connection with the MSC and
the PAGING RESPONSE from the MS is piggybacked on the CR
message.
4) Authentication & Ciphering
MSC sends the RAND in a DTAP message Authentication
Request to which the MS sends the SRES in a DTAP message
Authentication Response.
On SRES match, the MSC sends a BSSMAP message to BSC.
The Ciphering Constant contained in the message is used by the
BTS for ciphering purposes.
MSC/VLR

BSC

BTS

MS

Authentication Request (DTAP)

Authentication Response (DTAP)
Cipher Mode
Command (DT1)

Cipher Mode
Complete (DT1)

Cipher Mode
Command

Cipher Mode
Complete

Cipher Mode
Comm
and.
Cipher Mode
Complete

Figure 3.32 Authentication & Ciphering messages on SDCCH

--------------------------------------------------------------------------------------------------

25

110
5) Assignment of a TCH
The MSC sends an ASSIGNMENT REQUEST containing the
frequency and timeslot information. The BSC then allocates a
traffic channel in the correct cell and sends a CHANNEL
ACTIVATION message to the BTS. BTS responds with
CHANNEL ACTIVATION ACK.
BSC establishes a circuit-switched connection between the
channel towards the MSC and that of the BTS. BSC then sends
an ASSIGNMENT COMMAND to the MS via BTS asking both of
them to switch to the new TCH.
The MS establishes the LAPDm data link with the BTS on the
SACCH. BTS sends Establish Indication to the BSC. The MS
then sends Assignment Complete using FACCH that is conveyed
to the MSC. MS sends a DTAP ALERT message.
MSC/VLR

BSC

Assignment
Request

BTS

MS

Channel
Activation
Channel Act. Ack.
Assignment Cmd.

Establish Ind.

Assignment
Complete

Assignment Comp.

Assignment
Command
(SDCCH)
SABM (TCH-SACCH)
UA (TCH-SACCH)
Assignment
Comp.
(FACCH)

Alert (DTAP)
Figure 3.33 TCH Assignment procedure
--------------------------------------------------------------------------------------------------

26

111
6) Handover
General
The Handover procedure is initiated by the Locating function of
the BSC. The locating function sends a list of candidate cells
with priority to the Connection Management function. If the
topmost cell in the list belongs to the same BSC and a channel is
free, it is a case of intra-BSC handover.
Intra-BSC Handover
BSC sends Channel Activation message to BTS including the
encryption information. After getting acknowledgement, BSC
sends a HANDOVER COMMAND over the FACCH to the MS.
When the MS switches to the new channel, BTS sends a
Handover Detection message to the BSC. On establishing the
data link, the BTS sends an Establish Indication to the BSC.

MSC/VLR

BSC

BTS 1

BTS 2

MS

Channel Activation
Channel Act. Ack.
Handover Command (FACCH)
Handover Detection
Establish Indication
Handover Complete

Handover
Performed

RF Channel
Release
RF Channel REL
Ack.

Handover
Co
mp

Figure 3.34 Intra-BSC Handover

--------------------------------------------------------------------------------------------------

27

112
After receiving the Handover Complete message from the MS, the
old channel is released by sending the RF Channel Release
message. MSC is then informed about Handover.
7) Call clear
The purpose of the procedure is to clear all the dedicated
resources used for the call and are no longer required.
MSC initiates the procedure by sending a CLEAR COMMAND.
After releasing the resources, the BSC sends a Clear Complete
message.
BSC then sends a Channel Release message to the MS and then
asks the BTS to release the data link over SACCH. After getting
the Release Indication from the BTS, BSC sends RF Channel
Release message to the BTS. The procedure is complete when
the BTS returns acknowledgement.
MSC/VLR

BSC

BTS

MS

Clear Cmd
Clear Comp

Channel Release (SACCH)

Deactivate SACCH
Release Indication
RF Channel Release
RF Channel Release Ack

Figure 3.35 Intra-BSC Handover

--------------------------------------------------------------------------------------------------

28

113

29