03814

EXERCISES
Uppgjord (ven faktaansvarig om annan) - Prepared (also subject responsible if other)
KI/ERA/GD/UX Iwona Maksymowicz

Dokansv/Godk - Doc respons/Approved
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
1 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
GSM ADVANCED SYSTEM TECHNIQUE
LIST OF EXERCISES
EXERCISE 1
CHANNEL CONCEPT
EXERCISE 2
TRAFFIC CASES, GROUP EXERCISE
EXERCISE 3
PAGING GROUP
EXERCISE 4
TEMS EXERCISE
EXTRA EXERCISE (IF TIME ALLOWS)
9
15
EXERCISE 5
25
DECODING OF AN ABIS MESSAGE
25
EXERCISE 6
31
DECODING OF THE MSU
31
EXERCISE 7
37
ABIS, PROTOCOL ANALYZER

PRINTOUT OF LOG FILE
37
41
EXERCISE 8
53
A INTERFACE, PROTOCOL ANALYZER

53
58
EXERCISE 9
65
NETWORK SERVICE PART (NSP)

65
68
EXERCISE 10
87
SCCP USER INFORMATION

87
90
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
2 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXTRACT FROM GSM 05.02
111
137
139
185
187
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
3 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISE 1
Channel Concept
1. How many logical channels are defined in GSM?
_________________________________________________
_________________________________________________
2. How many control channels are there?

_________________________________________________
3. Name at least three of the control channels.

_________________________________________________
4. What is a burst?
_________________________________________________
5. Why is the access burst special?

_________________________________________________
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
4 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
6. What physical channels (frequency/timeslot) are the following

logical channels mapped upon in our example?
A. SDCCH
B. SCH
C. SACCH________________________________________
7. A handover must be performed during a call. What logical channel
is used for the Handover Command message?
_________________________________________________
_________________________________________________
_________________________________________________
8. Why is the 26th TDMA frame idle in a TCH multiframe?
_________________________________________________
_________________________________________________
_________________________________________________
9. How many traffic channels are there in a cell with our setup if
there are:
one carrier? _______________________________________
two carriers? _______________________________________
10. A mobile is idle, tuned to the BCCH channel. The subscriber

wants to make a call. Name the logical channels used during call
setup.
_________________________________________________
_________________________________________________
_________________________________________________
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
5 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISE 2
Traffic Cases, Group Exercise
Describe the signaling procedure for the following traffic cases:

A. International location updating
A mobile with an English subscription is switched on in
Spain. Describe the signaling.
B. International mobile to mobile call

A German mobile in Spain calls a Swedish mobile in
Germany. Describe between what network entities the
signaling is going.
C. Mobile to mobile SMS

Describe briefly the transfer of an SMS between two
MSs.
D. International inter MSC handover

A Swedish mobile crosses the border to Norway.
Describe a handover from a Swedish MSC to a
Norwegian MSC.
EXERCISES

038 14 - LZU
Kontr - Checked
t io
e n na
lly
I nt
KI/ERA/GD/UXC
Bl n
a
6 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
7 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISE 3
Paging Group
1. Find out how the paging group for a general mobile is determined,
use the GSM recommendations 05.02.
____________________________________________________
____________________________________________________
____________________________________________________
2. Use the rule from question 1 to determine the paging group for the
mobile described below.
IMSI = 2400100061162
MSISDN = 46705902149
Access class = 8
Control channels : SDCCH/8, one CCCH
BS_AG_BLKS_RES = 0
BS_PA_ MFRMS = 5
____________________________________________________
____________________________________________________
3. On what frequency (c0 - cn) and what timeslot are SDCCH/8 and
SACCH/C8 allowed?
____________________________________________________
4. On what frequencies and what timeslots are PCH and RACH

allowed?
____________________________________________________
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
8 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
5. On SCH reduced TDMA frame number is used. This is described

in GSM recommendation 05.02. In what way does this number
differ from the normal TDMA frame number? (Additional help can
be found in GSM recommendation 05.10).
____________________________________________________
____________________________________________________
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
9 (199)
Nr - No.
123 3333
Rev
File
07/01/00
03814.doc
EXERCISE 4
TEMS Exercise
Choose Log, and then Replay logfile, see figure 1 below
(figure 1)
Choose the file that contains a location update. Figure 2 shows an example.
(figure 2)
A window like the one below turns up.
(figure 3)
Uen
Datum - Date
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
10 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Choose Monitor, and then Layer 3 messages, see figure 4 below
(figure 4)
Location updating
In the window Replay log control press Go to. In the window as figure 5 shows, select Go to
Message and then select CHANNEL RELEASE and then press OK.
(figure 5)
Enlarge your window Layer 3 message so you can see from CHANNEL REQUEST up to
CHANNEL RELEASE.
To be able to see the details of a Layer 3 message, click on it as figure 6 is showing.
This CHANNEL REQUEST

is then showed in detail to the right
(figure 6)
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
11 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
1. The message CHANNEL REQUEST is sent on the RACH. The message consists of two parts;
establishment cause and random reference.
What is the value of the random reference?
2. In the message IMMEDIATE ASSIGNMENT sent on AGCH, the MS is told which logical channels to
use throughout the location updating. Describe these logical channels.
a) Logical Channels:
b) Timeslot:
c) Sub channel number:
3. Look at the message LOCATION UPDATING REQUEST.

a) What type of Location updating is this? IMSI attach, normal or periodic registration.
b) What identity is the mobile using, IMSI/TMSI?
c) The old LAI (MCC+MNC+LAC) is sent. Give this old LAI which has been written on the SIM card.
4. Complete the example below, so it reflects this location updating.

Do NOT include any of the following messages: SYSTEM INFORMATION 5-6, MEASUREMENT
REPORT and SYNCH CHANNEL INFORMATION
MS
Network
(Logical Channel used, NOT shown by TEMS)
UL: CHANNEL REQUEST

------------------------->
DL: IMMEDIATE ASSIGNMENT
<------------------------UL: LOCATION UPDATING REQUEST
------------------------->
(RACH)
DL: LOCATION UPDATING ACCEPT

<-------------------------
(----)
DL: CHANNEL RELEASE

<-------------------------
(----)
(AGCH)
(Answer in 2a:
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
12 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
5. If authentication is used, then what value has RAND and SRES, respectively?
a) RAND:
b) SRES:
6. If ciphering is used, then which algorithm is used?
7. Look at the message: LOCATION UPDATING ACCEPT. What LAI is being sent to the MS in this
message?
8. Compare the LAI in question 7 with the LAI in question 3c. Are these answers supporting your
answer in question 3a?
9. Use the SYSTEM INFORMATION messages just before the CHANNEL REQUEST message. The
MS reads this before trying to make a Location updating.
a) Which country and operator (MCC+MNC) does this cell belong to? (See table)
b) What is the LAI? Compare this LAI with the answer on question 7.
c) Which neighboring frequencies is the MS measuring on in Idle mode? These frequencies

(ARFCN Absolute Radio Frequency Channel Number) are called neighboring BCCH-frequencies.
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
13 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
LAYER 2 (LAPDm)
The same traffic case will be studied from Layer 2 point of view. Use the book as help (Ch. Um
interface, signaling layer 2).
Choose in the menu Monitor, Layer 2 Messages (see figure 4)
Press Restart in the Log replay control-window.
Go To CHANNEL REQUEST. Press the STEP-button in the window Replay log control until
CHANNEL RELEASE and a few more messages are visible in the window Layer 3 messages.
Make sure what you see in the window Layer 2 message starts by SABM-CMD & UA-RSP and
ends with DISC-CMD & UA-RSP. It will look similar to figure 7.
CMD
DISC
I
RSP
SABM
UA
Command
DISConnect
(terminates Acknowledge Mode)
Information
Response
Set Asynchronous Balanced Mode
(starts Acknowledge Mode)
Unnumbered Acknowledge
(figure 7)
10. Click on the first I-CMD message, what Layer 3 message is this Layer 2 message carrying?
11. Compare the size of the message dump for this Layer 2 message and the corresponding Layer 3
message. They differ by 3 octets; Length Indicator, Address and Control Field.
N(S) and N(R) are two parts of the Control Field. Study how they change during this location
updating.
What is the purpose of N(S) and N(R)?
Close this file.
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
14 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
CALL
A call will be studied.
Replay the file that contains a call
Monitor Layer 3 messages only (see figure 4).
Go to the message ASSIGNMENT COMMAND (see figure 5).
12. Answer with help of the figures in the chapter Traffic cases. Is this call a Mobile Terminated call
or a Mobile Originated call?
13. What is the difference between the messages/procedures in the book and in this call set-up?
14. If this is a Mobile Terminated call answer this question. Find the PAGING REQUEST that contains
this MS. Is IMSI/TMSI used? What value is it?
15. Give the telephone number the other party has. This is written in the SETUP message
16. Find out the following about the TCH described in the message ASSIGNMENT COMMAND
Frequency hopping:
Frequency/frequencies:
Timeslot:
Training Sequence Code:
Close this file
YES/NO
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
15 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Extra Exercise (if time allows)

Handover
Replay the file that contains a handover.
Monitor Layer 3 Messages (see figure 4)
Choose the menu Monitor, then under Status information select Graphical presentation.
The grey color is the serving cell
Light grey = IDLE mode
Dark grey = BUSY mode
This vertical line indicates

a handover.
Different colors mean neighboring cells
By clicking in the window you see

information about that moment in the
lower part of this window
Go to a HANDOVER COMMAND in the file (see figure 5).
17. Which frequency was (frequencies were) used after the handover?
18. What is the first message in the new cell?
19. Give the value of the handover reference value.
20. What is the Timing Advance value in the new cell?
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
16 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Measurements
Look at a MEASUREMENT REPORT.
21. How many neighbors can a report contain?
22. How many neighbors are reported in the one you are looking at?
23. How many MEASUREMENT REPORTS are sent each second?
24. Now and then SYNCH CHANNEL INFORMATION is read from the neighboring cells. Why?
Close the file and exit the program.
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
17 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Some GSM mobile operators MCC+MNC

Country
-----Albania
Andorra
Armenia
Australia
Operator name
------------AMC
STA-Mobiland
Armentel
Optus
Telecom/Telstra
Vodafone
Austria
Mobilkom Austria
max.mobil.
Connect Austria
Azerbaidjan Azercell
JV Bakcell
Bahrain
Batelco
Bangladesh
Grameen Phone Ltd.
TM International
Sheba Telecom
Belgium
Proximus
Mobistar
KPN Orange
Bosnia
Cronet
PTT Bosnia
Botswana
Mascom Wireless
Brunei
DSTCom
Jabatan Telekom
Bulgaria
MobilTel AD
Burkina Faso OnaTel
Cambodia
CamGSM
Cambodia Samart
Cambodia Shinawatra
Cape Verde
Cabo Verde Telecom
Cameroon
PTT Cameroon Cellnet
Cape Verde
Cabo Verde Telecom
Canada
Microcell
Chile
Entel Telefonia
China
Guangdong MCC
Beijing Wireless
China Unicom
Zhuhai Comms
DGT MPT
Jiaxing PTT
Tjianjin Toll
Liaoning PPTA
Congo
African Telecoms
Congolaise Wireless
Network code
-----------276 01
213 03
283 01
505 02
505 01
505 03
232 01
232 03
232 05
400 01
400 02
426 01
470 01
470 19
206
206
206
218
218
652
528
528
284
01
10
20
01
19
01
11
01
01
456 01
456 02
625 01
624 01
302 37
460 00
460 01
460 02
EXERCISES

KI/ERA/GD/UXC
Croatia
038 14 - LZU
Kontr - Checked
18 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
HR Cronet
Vipnet
Cyprus
CYTA
Czech Rep.
Eurotel Praha
Radio Mobil
Denmark
Sonofon
Tele Danmark Mobil
Mobilix
Telia
Egypt
MobiNil
Click GSM
Estonia
EMT
Radiolinja Eesti
Q GSM
Ethiopia
ETA
Faroe Isl.
Faroese Telecom
Fiji
Vodafone
Finland
Radiolinja
Sonera
Alands Mobiltelefon
Telia
Finnet
Lnnen Puhelin
Helsingin Puhelin
France
France Telecom
SFR
Bouygues Telekom
Fr.Polynesia Tikiphone
Fr.W.Indies Ameris
Georgia
Superphone
Geocell
Magticom
Germany
D1, DeTeMobil
D2, Mannesmann
E-Plus Mobilfunk
Viag Interkom
Ghana
Franci Walker Ltd.
ScanCom
Gibraltar
GibTel
G Britain
Cellnet
Vodafone
Jersey Telecom
Guernsey Telecom
Manx Telecom
One2One
Orange
219
219
280
230
230
238
238
238
238
602
602
248
248
248
636
01
10
01
02
01
02
01
30
20
01
02
01
02
03
01
542
244
244
244
244
244
244
244
208
208
208
547
340
01
05
91
05
03
09
09
09
01
10
20
20
01
282
282
262
262
262
262
01
02
01
02
03
07
620
266
234
234
234
234
234
234
234
01
01
10
15
50
55
58
30
33
EXERCISES

KI/ERA/GD/UXC
Greece
Greenland
Guinea
Hong Kong
Hungary
Iceland
India
038 14 - LZU
Kontr - Checked
19 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Panafon
STET
Cosmote
Tele Greenland
Intl Wireless
Spacetel
Sotelgui
HK Hutchison
SmarTone
Telecom CSL
P Plus Comm
New World PCS
Mandarin Comm
Pacific Link
Peoples Telephone
SMC PCS
Pannon GSM
Westel 900
Post & Simi
Icelandic Mobile Phone
Airtel
Essar
Maxtouch
BPL Mobile
Command
Mobilenet
Skycell
RPG MAA
Modi Telstra
Sterling Cellular
Mobile Telecom
Airtouch
BPL USWest
Koshika
Bharti Telenet
Birla Comm
Cellular Comms
TATA
Escotel
JT Mobiles
Evergrowth Telecom
Aircel Digilink
Hexacom India
Reliance Telecom
Fascel Limited
202 05
202 10
202 01
611
611
611
454
454
454
454
454
454
454
454
454
216
216
274
274
404
404
404
404
404
404
404
404
404
404
02
04
06
00
22
10
16
18
12
22
01
30
01
02
10
11
20
21
30
31
40
41
14
11
404 27
404 07
404 12
404 15
EXERCISES

KI/ERA/GD/UXC
Indonesia
038 14 - LZU
Kontr - Checked
20 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
TELKOMSEL
PT Satelit Palapa
Excelcom
PT Indosat
Iraq
Iraq Telecom
Iran
T.C.I.
Celcom
Kish Free Zone
Ireland
Eircell
Digifone
Meteor
Israel
Partner Communications
Italy
Omnitel
Telecom Italia Mobile
Wind
Ivory Coast Ivoiris
Telecel
Comstar
Loteny Telecom
Jordan
JMTS
Kenya
Kenya Telecom
Kuwait
MTCNet
Kyrgyz Rep
Bitel Ltd.
La Reunion
SRR
Laos
Lao Shinawatra
Latvia
LMT
BALTCOM GSM
Lebanon
Libancell
Cellis
Lesotho
Vodacom
Liechtenstein Natel-D
Lithuania
Omnitel
Bite GSM
Luxembourg
P&T LUXGSM
Millicom Lux S.A
Lybia
Orbit
El Madar
Macao
CTM
Macedonia
PTT Makedonija
Madagascar
Sacel
Madacom
SMM
Malawi
TNL
Malaysia
Celcom
Maxis
TM Touch
Adam
Digi Telecom
510 10
510 01
510 11
418
432 11
272
272
272
425
222
222
222
612
612
612
612
416
01
02
03
01
10
01
88
03
01
05
01
419 02
437 01
647 10
457 01
247 01
247 02
415 03
415 01
651 01
228 01
246 01
246 02
270 01
270 77
455
294
646
646
646
650
502
502
502
502
502
01
01
03
01
02
01
19
12
13
17
16
EXERCISES

038 14 - LZU
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Advanced
Telecell
Marocco
O.N.P.T.
Mauritius
Cellplus
Moldova
Voxtel
Monaco
France Telecom
SFR
Office des Telephones
Mongolia
MobiCom
Montenegro
Pro Monte
Mozambique
Telecom de Mocambique
T.D.M GSM1800
Namibia
MTC
Netherlands PTT Netherlands
Libertel
Telfort Holding NV
Ben
Dutchtone
New Caledonia Mobilis
New Zealand Bell South
Nigeria
EMIS
Norway
NetCom
TeleNor Mobil
Oman
General Telecoms
Palestinia
Palestine Telecoms
Pakistan
Mobilink
Papua
Pacific
Philippines Globe Telecom
Islacom
Smart
Poland
Plus GSM
ERA GSM
IDEA Centertel
Portugal
Telecel
TMN
Main Road Telecoms
Optimus
Qatar
Q-Net
Romania
MobiFon
MobilRom
278
278 01
604 01
617 01
KI/ERA/GD/UXC
Malta
Kontr - Checked
21 (199)
Nr - No.
208 01
208 10
220 02
634 01
649
204
204
204
204
204
546
530
01
08
04
12
16
20
01
01
242 02
242 01
422 02
410
310
515
515
515
260
260
260
268
268
01
01
02
01
03
01
02
03
01
06
268
427
226
226
03
01
01
10
EXERCISES

KI/ERA/GD/UXC
Russia
038 14 - LZU
Kontr - Checked
22 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Mobile Tele... Moscow

United Telecom Moscow
NW GSM, St. Petersburg
Dontelekom
KB Impuls
JSC Siberian Cellular
BM Telecom
Beeline
Extel
Far Eastern Cell
San Marino
Omnitel
Wind
SaudiArabia Al Jawal
EAE
Senegal
Sonatel
Seychelles
SEZ SEYCEL
Airtel
Serbia
Serbian PTT
Singapore
Singapore Telecom
MobileOne
Binariang
Slovak Rep
Eurotel
Globtel
Slovenia
Mobitel
SI.Mobil
South Africa MTN
Vodacom
Sri Lanka
MTN Networks Pvt Ltd.
Spain
Airtel
Telefonica Spain
Amena
Sudan
Mobitel
Sweden
Comviq
Europolitan
Telia Mobile
Switzerland Swisscom 900
Swisscom 1800
diAx mobile
Orange
Syria
SYR MOBILE
250 01
250
250
250
250
250
250
250
250
222
222
222
420
420
608
633
633
220
525
525
02
10
99
07
28
12
10
01
88
01
07
01
01
10
03
01
03
231 02
231 01
293 41
655 10
655 01
413 02
214 01
214 07
214 03
634 01
240 07
240 08
240 01
228 01
228 01
228 02
417 09
EXERCISES

KI/ERA/GD/UXC
Taiwan
Tanzania
Thailand
Tunisia
Turkey
UAE
Uganda
Ukraine
USA
Uzbekistan
Vatican
Venezuela
Vietnam
Yugoslavia
Zaire
Zimbabwe
038 14 - LZU
Kontr - Checked
23 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
LDTA
Mobitai
TransAsia
TWN
Tuntex
KG Telecom
FarEasTone
Chunghwa
Tritel
TH AIS GSM
Total Access Comms
WCS
Hello
Tunisian PTT
Telsim
Turkcell
UAE ETISALAT-G1
UAE ETISALAT-G2
Celtel Cellular
MTN
Mobile comms
Golden Telecom
Radio Systems
Kyivstar JSC
Bell South
Sprint Spectrum
Voice Stream
Aerial Comms.
Omnipoint
Powertel
Wireless 2000
Daewoo GSM
Coscom
Buztel
Omnitel
Wind
Infonet
Digitel
MTSC
DGPT
Mobile Telekom
Promonte
Telekom Serbia
African Telecom Net
NET*ONE
Telecel Zimbabwe
466
466
466
466
466
466
466
466
640
520
520
520
520
605
286
286
424
424
641
641
255
255
255
255
310
310
310
310
310
310
310
434
434
434
222
222
222
734
92
93
99
97
06
88
01
11
01
01
18
10
23
02
02
01
01
02
01
10
01
05
02
03
15
02
26
31
16
27
11
04
05
01
10
01
88
01
452
452
220
220
220
01
02
01
02
03
648 01
648 04
EXERCISES

038 14 - LZU
Kontr - Checked
t io
e n na
lly
I nt
KI/ERA/GD/UXC
Bl n
a
24 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISES

25 (199)
Nr - No.
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISE 5
Decoding of an Abis Message

EXAMPLE
The following message is sent on Abis in the uplink direction. Hexadecimal
notation is used.
00 01 3E 62 0C 13 01 88 13 E4 06 42 11 01
Use the figure describing the LAPD frame format in Abis chapter in the
AST book. On the Abis bus log neither the flags nor the FCS are shown.
Try to decode the message using GSM recommendations 08.58 and

04.08.
Solution
First look at the figure in Abis chapter of the AST book where we find the
structure of a LAPD frame.
The address and control fields are LAPD functions and are not described in
the GSM specifications. LAPD functions are specified in CEPT T/S 46-20 (not
included in this booklet). Only the contents in the information field are
described in GSM TS 08.58.
00 01 3E 62 0C 13 01 88 13 E4 06 42 11 01
address:
SAPI
SAPI=0
RSL message
hex
bin
0000
0000
0000
0001
C/R
EA
command more
(uplink)
octets in
address
TEI
TEI=0
HW address of
TRX
EA
last
octet in
address
EXERCISES

26 (199)
Nr - No.
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
00 01 3E 62 0C 13 01 88 13 E4 06 42 11 01
control field:
hex
bin
0011
1110
0110
0010
N(S)
send seq.No.
31
fixed
0
N(R)
P/F
receive seq.No. poll/final

49
0
Start to check in 08.58, section 8 (Message formats) what a message looks

like in general.
All messages start with a message discriminator.
See 08.58 ( sections 9 and 9.1) for Information element coding and message
discriminator.
00 01 3E 62 0C 13 01 88 13 E4 06 42 11 01
message discr.:
hex
bin
0000
1100
Message discriminator: By looking in 9.1 we see that this is a message in the

common channel management message group. First bit to the right indicates
if this message is transparent or not for BTS. T = 0 in this case, which means
that it is a non-transparent message.
Now we know it is a common channel management message.
EXERCISES

27 (199)
Nr - No.
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Look up the format in 08.58, section 8.5
Information element
reference
type
length
Message discriminator
9.1
Message type
9.2
Channel number
9.3.1
Information elements
depending on message
type
We see that the next octet gives us the message type.

00 01 3E 62 0C 13 01 88 13 E4 06 42 11 01
message type:
hex
bin
0001
0011
Message type is described in 9.2.

We find that this means channel required. There is a reference to 8.5.3.
8.5.3 CHANNEL REQUIRED

Information element
reference
type
length
9.1
Message type
9.2
Channel number
9.3.1
Request Reference
9.3.19
Access Delay
9.3.17
Physical Context
9.3.16
EXERCISES
28 (199)
Nr - No.
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
We see that the next 2 octets describe the channel number.

00 01 3E 62 0C 13 01 88 13 E4 06 42 11 01
channel No.:
hex
bin
0000
0001
1000
1000
We look in the given reference 9.3.1, where we see what these 2 octets
consist of.
The first octet is the element identifier (check 9.3) telling us that the next octet
contains the channel number. In 9.3.1 we see that this is uplink CCCH
(RACH) and that timeslot 0 is used.
Go to 8.5.3 again. Next 4 octets contain Request reference.
Go to 9.3.19.
00 01 3E 62 0C 13 01 88 13 E4 06 42 11 01
First octet can be decoded by looking in 9.3.
hex
bin
0001
0011
Element identifier = Request reference
Next octet gives us the Random Access information, which is described in

GSM TS 04.08, section 9.1.8.
Establishment cause
Random reference
hex
bin
1110
0100
Establish cause = originating call (while this is taken from a MO call)
EXERCISES

29 (199)
Nr - No.
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Random reference: a value between 0 and 31 which here equals 4.

Next two octets (06 42) indicate in which TDMA frame number the request
was received at the BTS. 0000 0110 0100 0010. Note: this is not the
complete frame number but FN MOD 42432 meaning only 16 bits are used.
There are 2 octets left. Go back to 8.5.3.
00 01 3E 62 0C 13 01 88 13 E4 06 42 11 01
As we know from looking in 8.5.3, these 2 octets describe the access delay.
Go to 9.3.17
Check in 9.3 that the element identifier is what we expect
hex
bin
0001
0001
0000
0001
Last octet contains the access delay and there is one bit access delay.
As we see in 8.5.3 there is a possibility to send an optional parameter. This
parameter is not used here.
Exercise
The message below is sent on the Abis interface in the downlink direction.
The message is described using the hexadecimal code.
Decode the message using GSM recommendations 08.58 and 04.08.
Flags and LAPD checksum are not included.
02 01 04 B8 08 26 01 51 07 01 01 02 00 0B 00 03 06 35 00
EXERCISES

038 14 - LZU
Kontr - Checked
t io
e n na
lly
I nt
KI/ERA/GD/UXC
Bl n
a
30 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
31 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISE 6
Decoding of the MSU

MAP is the protocol used between exchanges in GSM. MAP uses TCAP,
SCCP and MTP to send information.
TCAP encodes, packs and sends the information received from MAP. SCCP
is used for analysis and addressing. MTP receives the information from
SCCP, adds information for error detection and correction and puts the data
in specified fields. This forms a message signal unit (MSU) which is sent by
the signaling terminal to the receiving exchange.
In this exercise you shall decode a message sent between two exchanges in
the GSM service area. You find each field described on the pages following
the exercise. The last page shows how TCAP packs the information, forming
constructors out of elements.
Concentrate on the SIO and SIF fields.
Between what GSM nodes is this message sent?
Where do you find the information about which MAP operation it is?
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
DPC
21
12
Called
Address
Uen
Rev
File
07/01/00
03814.doc
SIO
PointerPointer Pointer
data calling called
123 3333
Datum - Date
FL
01001000100001 0000 0011 LI
Len
32 (199)
Nr - No.
Protocol
class
F FSN B BSN 0111 1110
Message
type
SLS
OPC
3 1000 0000 0000 1001 0000 01001010000101
Nature
of address
Numb plan
+ Encoding
Transl.
type
Address
type
SSN
21 80 44 0000 0100 0001 0010 0000 0000 0000 0110 0001 0010
Nature
of address
Numb plan
+ Encoding
Transl.
type
Address
type
SSN
Length
46 0000 0100 0001 0010 0000 0000 0000 0111 0001 0010 9 23
ID
ID
length
Transaction
ID (Orig.)
Total
length
Tag
(Begin)
0000 0100
0100 1000
30
0110 0010
Operation
code tag
Invoke Invoke
ID
ID length
Invoke
ID Tag
Comp.
length
Calling Address
Comp.
type tag
(invoke)
34
52
Comp.
p. length
70
Comp.
p. tag
0000 0010 0000 0110 1 0000 0010 23 1010 0001 25 0110 1100
IMSI
41
23
Sequence
Length
Tag
Length
Tag = 0
1000 0000
Length
Tag = 16
Sequence
0011 0000
15
Operation Op. code

code
Length
0011 0000
09
IMSI
9F
78
34
12
Request Param.
Authentication Length
Flag
0111 1110
56
CK
0000 0001
00
Tag = 10
Enumerated
0000 1010
EXERCISES

33 (199)
Nr - No.
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
File
07/01/00
03814.doc
16
8n, n>1
FL
CK
SIF
SIO
SSF
SI
LI
F FSN B BSN
FL
CK
SIF
SIO
LI
F
FSN
B
BSN
SSF
SI
00xx
01xx
10xx
11xx
SSF
International Network
Spare (for International Use)
National Network
Reserved for National Use
xx
xx
Spare for International Use

Application Dependent in National Use
16
8n, n>1
FL
CK
SIF
SIO
LI F FSN B BSN
SCCP
8
Mandatory Fixed
Part
Message
Type
32
Routing
Label
Message Type
0000 0001
0000 0010
0000 0011
0000 0100
0000 0101
0000 0110
0000 1001
0001 0000
CR Connection Request
CC Connection Confirm
CREF Connection Refusal
RLSD Released
RLC Release Complete
DT1 Data Form 1
UDT Unit Data
IT Interactivity Test
SLS
DPC
OPC
SLS
SLC
OPC
8
FL
SI
Signaling Network Management
Signaling Network Testing and
Maintenance Message
Spare
SCCP
TUP
ISUP
DUP
DUP
0010
0011
0100
0101
0110
0111
Flag
Check sum
Signaling Information Field
Service Information Octet
Length Indicator
Forward Indicator Bit
Forward Sequence Number
Backward Indicator Bit
Backward Sequence Number
Sub service Field
Service Indicator
0000
0001
Optional Mandatory Variable

Part
Part
Uen
Rev
123 3333
Datum - Date
DPC
Destination Point Code

Originating Point Code
Signaling Link Select
Signaling Link Code
SLS = SLC in a TUP message
8
FL
EXERCISES

34 (199)
Nr - No.
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
32
Optional Mandatory Variable Mandatory Fixed Message Routing

Part
Part
Part
Type
Label
Protocol Class
0000
0001
0010
0011
0100
Class 0
Class 1
Class 2
Class 3
Class 4
CL
CL
CO
CO
CO
bit 8765 are spare at Connection Oriented

bit 8765 are coded for connection Less
0000
No special option
1000
Return message on error
0xxx
Spare
Data
Calling Party Called Party

Address
Address
Pointer
data
Pointer
calling
Pointer
called
The pointer value gives the number of octets

between the pointer itself (Included) and the first
octet (Not included) of the parameter associated
with that pointer.
Address
Address
Type
Length
Length = Number of octets

Address Type
000x 00x1 SPC included
000x 001x SSN included
0001 00xx GT included
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
Data
35 (199)
Nr - No.
Calling Party
Address
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Called Party
Address
Pointer
data
Pointer
calling
Pointer
called
See next
page
8
Address
Address
Type
Length
Last two digits

of address
1st two digits

of address
Nature of
Address
Numb.
Plan
Encod
Scheme
8
Trans.
Type
ENCODING SCHEME
0001
BCD odd Number
0010
BCD even Number
Subsystem number, SSN

0000 0110
MAP-HLR
0000 0111
MAP-VLR
NATURE OF ADDRESS
0000 0001
Subscriber
0000 0011
National
0000 0100
International
TRANSLATION TYPE
usually coded as
0000 0000 for GSM
CALLING PARTY ADDRESS

Coded as called part address
DATA
See next page
NUMBERING PLAN
0001 = E.164
0111 = E.214
8
SSN
EXERCISES

36 (199)
Nr - No.
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
Uen
Rev
File
07/01/00
03814.doc
MESSAGE TYPE TAG (BEGIN)
TOTAL MESSAGE LENGTH
TRANSACTION PORTION INFO ELEMENT

(TAG, LENGTH, ID)
COMPONENT PORTION TAG
COMPONENT PORTION LENGTH
COMPONENT TYPE TAG (INVOKE)
COMPONENT LENGTH
INVOKE ID TAG
INVOKE ID LENGTH
INVOKE ID
OPERATION CODE TAG
OPERATION CODE LENGTH
9 (=send parameters)
SEQUENCE TAG
SEQUENCE LENGTH
TAG = 0
123 3333
Datum - Date
(IMSI)
LENGTH
IMSI
SEQUENCE TAG
LENGTH
TAG=10 (ENUMERATED)
LENGTH
1 (=req auth set)
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
37 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISE 7
Abis, Protocol Analyzer

During this exercise you will study signaling on Abis, recorded in a logfile
called motabis.msu.
To start the exercise, follow the instruction below (1 - 9):
1. Choose: MPA Eventlog browser in the program group GN Nettest
MPA.
2. Go to: File, Open.
3. Choose: motabis.msu.
4. To the right of the format-button, there is a window displaying:
overview- one line.
Press the arrow pointing downwards and choose:
detailed- all fields with hex.
5. Press the format- button. In the Decode params-folder, choose
relative in the Time option box. Then go to the Protocol layers folder.
6. Choose ETSI GSM Abis in the window to the right of Protocols, in use
Make sure there is an x in all the white boxes. That is, in: LAPD,
L2Mngt, Network Mngt,Traffic Mngt, DTAP and SS.
7. Go to the link colors- folder.
8. LU2 TLink1A SLink2 is Abis uplink, lets have it in red!
LU2 TLink1B SLink2 is Abis downlink, make it blue!
To color each entire message use the Apply Color box.
Click OK!
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
38 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
9. In the colored header of each frame there is a number for each frame.
The first frame in the logfile has No. 1.441.
Below the header, the frame content is shown. There are three columns:
In the left column the octets are displayed in hex.
The middle column shows the names of the information fields in the
octet. Double-click on the name for more info. Then exit
The right column shows the decoding of the information fields.
Your traffic case starts in frame 29.175 and stops in frame 39.979. Try to
answer the questions on the following pages. Where applicable make a note
of where in the logfile you found the answer.
1. Is the message in frame No. 29.175 sent uplink or downlink?
2. Look at the L2 header (address and control field):

A. What logical link carries this message?
B. Is it a command or response?
C. To which TRX is the message sent?
D. What are the values of the sequence counters?
3. To what group of traffic management messages does this

message belong?
4. In that group, what is the Abis message?
5. On what channel is the message sent over the air?
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
39 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
6. What paging group does the searched MS belong to?
7. Is the MS close to or far away from the BTS (see frame 30.122)?
Look at the following frames:

8. What downlink Abis message is sent in frame 30.131?
9. Describe the air channel handled in that message:

A. channel combination and sub-channel number
B. timeslot number
C. is frequency hopping used?
D. what about DTX uplink and downlink?
E. what TA value will the MS use (compare to access delay)?
10. In frame No. 30.153 the analyzer fails to decode the layer 3
information.
A. What is the problem?
B. What Abis message is it?
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
40 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
11. Look at frame 30.442.

A. What Abis message is there?
B. This message carries layer 3 information from the air
interface. What identity is MS using to identify itself?
C. What is the maximum output power of the MS?
D. Which is the home network of this subscriber?
12. Will encryption be used?
13. What happens in frame 30.947?
14. Is the Assignment command message handled transparently or

non-transparently by the BTS?
15. Which frequency and timeslot will be used by the TCH?
16. What happens in frames 31.768 and 31.778?
When the call is over:

17. Who initiates call clearing, the A or the B subscriber?
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
41 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Printout of Log file
LU2 TLink1B SLink2 29.175

Error: PDU is longer than expected
=== LAPD ===
--- ADDRESS --02
SAPI
: 0 = Radio Signaling
CR
: ......1.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
--- CONTROL ----- I_FRAME --FA
N(S)
: 125
IFORMAT
: .......0
B2
N(R)
: 89
P
: .......0
--- INFO --=== TRAF MGMT ===
0C
MESS DISCR : 06h = Common Channel Management
T-Bit
: .......0 = Non-Transparent
15
ExtBit
: 0.......
MESS TYPE : 15h = Paging Command
--- PAGE CMD --01
IE ID
: 01h
--- CHANNEL NO --90
CHANNEL
: 10010... = Downlink CCCH (PCH + AGCH)
TIMESLOT
: 0
0E
IE ID
: 0Eh
--- PAGE GROUP --03
PAGE GROUP : 3
0C
IE ID
: 0Ch
--- MS IDENT ----- MOBILE ID --08
LEN
: 8
29
TYPE
: 1 = IMSI
ODD/EVEN
: ....1... = Odd
26 20 04 88
09 01 30
IDENTITY
: 262024088901003
28 02
BYTE DUMP : 28 02h
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
42 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
LU2 TLink1A SLink2 30.122

=== LAPD ===
--- ADDRESS --00
SAPI
CR
: ......0.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
--- CONTROL ----- I_FRAME --B2
N(S)
: 89
IFORMAT
: .......0
FC
N(R)
: 126
P
: .......0
0C
T-Bit
13
ExtBit
: 0.......
MESS TYPE : 13h = Channel Required
--- CHAN RQD --01
IE ID
: 01h
--- CHANNEL NO --88
CHANNEL
: 10001... = Uplink CCCH (RACH)
TIMESLOT
: 0
13
IE ID
: 13h
--- REQ REF --92
RA
: 92h
F2
N32
: 30
95
N51
: 20
N26
: 21
11
IE ID
: 11h
--- ACC DELAY --01
ACC DELAY : 1
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
43 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
______________________________________________________________________________
=== LAPD ===
--- ADDRESS --02
SAPI
CR
: ......1.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
--- CONTROL ----- I_FRAME --FC
N(S)
: 126
IFORMAT
: .......0
B4
N(R)
: 90
P
: .......0
08
MESS DISCR : 04h = Dedicated Channel Management
T-Bit
21
ExtBit
: 0.......
MESS TYPE : 21h = Channel Activation
--- CHAN ACTIV --01
IE ID
: 01h
--- CHANNEL NO --6A
CHANNEL
: 01101... = SDCCH/8 + ACCH, subch. 5
TIMESLOT
: 2
03
IE ID
: 03h
--- ACTIV TYPE --00
RESERVED
: 00h
ACTIV TYPE : 0 = Immediate assignment procedure
06
IE ID
: 06h
04
LEN
: 4
--- CHAN MODE --00
RESERVED
: 0
DTXd
: ......0.
DTXu
: .......0
--- CHAN TYPE --03
SPCH/DATA : 03h = Signaling
01
CHAN RATE : 1 = SDDCH
00
SPEECH ENC : 0 = No Resources Required
05
IE ID
: 05h
06
LEN
: 6
--- CHANNEL ID ----- CHAN DESCR --64
IE ID
: 64h
6A
CHAN TYPE : 01101... = SDCCH/8 + ACCH, subch. 5
TIMESLOT
: 2
80
TRAIN SEQ : 100.....
H
: ...0.... = Single RF Channel
SPARE
: ....00..
FREQ BAND : 0
1D
SPARE
: 0.......
ARFCN
: 29
--- MOBILE ALL --72
IE ID
: 72h
00
LEN
: 0
0D
IE ID
: 0Dh
--- MS POWER --05
RESERVED
: 0
MS PWR LEV : 5
18
IE ID
: 18h
--- TIMING ADV --01
RESERVED
: 0h
TIMING ADV : 01h
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
44 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
______________________________________________________________________________
Error: Unknown Message Type
=== LAPD ===
--- ADDRESS --02
SAPI
CR
: ......1.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
--- CONTROL ----- I_FRAME --FE
N(S)
: 127
IFORMAT
: .......0
B6
N(R)
: 91
P
: .......0
0C
T-Bit
16
ExtBit
: 0.......
MESS TYPE : 16h = Immediate Assign Command
--- IMM AS CMD --01
IE ID
: 01h
--- CHANNEL NO --90
CHANNEL
: 10010... = Downlink CCCH (PCH + AGCH)
TIMESLOT
: 0
2B
IE ID
: 2Bh
17
LEN
: 23
--- IMM AS INF --2D
TIFLAG
: 0h = Sent from TI originator
TIVAL
: 2h
PDC
: 13 = ???
06
ExtBit
: 0.......
N(SD)
: .0......
MESS TYPE : 6 = ???
3F 03 6A 80 1D 92 F2 95 01 00 2B 2B 2B 2B 2B 2B 2B 2B 2B 2B 2B
BYTE DUMP : 3F 03 6A 80 1D 92 F2 95 01 00 2B 2B 2B 2B 2B 2B 2B 2B
2B 2B 2Bh
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
45 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
______________________________________________________________________________
=== LAPD ===
--- ADDRESS --00
SAPI
CR
: ......0.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
--- CONTROL ----- I_FRAME --B6
N(S)
: 91
IFORMAT
: .......0
00
N(R)
: 0
P
: .......0
02
MESS DISCR : 01h = Radio Link Layer Management
T-Bit
06
ExtBit
: 0.......
MESS TYPE : 06h = Establish Indication
--- EST IND --01
IE ID
: 01h
--- CHANNEL NO --6A
CHANNEL
: 01101... = SDCCH/8 + ACCH, subch. 5
TIMESLOT
: 2
02
IE ID
: 02h
--- LINK ID --00
CHAN TYPE : 0 = Main Signaling Channel
NA
: ..0.....
RESERVED
: 0h
SAPI
: 0 = High Priority
0B
IE ID
: 0Bh
00 0F
LEN
: 15
--- L3-INFO --=== DTAP ===
06
TIFLAG
TIVAL
: 0h
PDC
: 6 = Radio Resources
27
ExtBit
: 0.......
N(SD)
: .0......
MESS TYPE : 27h = Paging Response
--- PAGINGRESP ----- CIPHER KEY --07
KEY SEQ
: 7
SPARE
: ....0...
SPARE
: 0000....
--- MS CLASS 2 --02
LEN
: 2
03
REV. LEVEL : 000.....
ENCRYPTION : ...00... = Algorithm A5
RF POWER
: .....011 = Class 4, handheld
18
SPARE
: 0001....
SM CAP
: ....1... = SM capability present
FREQ CAP
: .....000 = Band number 0
--- MOBILE ID --08
LEN
: 8
29
TYPE
: 1 = IMSI
ODD/EVEN
: ....1... = Odd
26 20 04 88
09 01 30
IDENTITY
: 262024088901003
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
46 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
______________________________________________________________________________
=== LAPD ===
--- ADDRESS --02
SAPI
CR
: ......1.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
--- CONTROL ----- I_FRAME --00
N(S)
: 0
IFORMAT
: .......0
B8
N(R)
: 92
P
: .......0
08
T-Bit
26
ExtBit
: 0.......
MESS TYPE : 26h = Encryption Command
--- ENCR CMD --01
IE ID
: 01h
--- CHANNEL NO --6A
CHANNEL
: 01101... = SDCCH/8 + ACCH, subch. 5
TIMESLOT
: 2
07
IE ID
: 07h
01
LEN
: 1
--- ENCR INFO --01
ALGORITHM : 1 = No Encryption required
02
IE ID
: 02h
--- LINK ID --00
NA
: ..0.....
RESERVED
: 0h
SAPI
: 0 = High Priority
0B
IE ID
: 0Bh
00 03
LEN
: 3
--- L3-INFO --=== DTAP ===
06
TIFLAG
TIVAL
: 0h
PDC
35
ExtBit
: 0.......
N(SD)
: .0......
MESS TYPE : 35h = Ciphering Mode Command
--- CIPHMDECMD ----- CIPH MODE --00
SC
: .......0 = DTX was not used
SPARE
: ....000.
SPARE
: 0000....
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
47 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
______________________________________________________________________________
=== LAPD ===
--- ADDRESS --02
SAPI
CR
: ......1.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
N(S)
: 1
IFORMAT
: .......0
BA
N(R)
: 93
P
: .......0
03
T-Bit
: .......1 = Transparent
01
ExtBit
: 0.......
MESS TYPE : 01h = Data Request
--- DATA REQ --01
IE ID
: 01h
--- CHANNEL NO --6A
CHANNEL
: 01101... = SDCCH/8 + ACCH, subch. 5
TIMESLOT
: 2
02
IE ID
: 02h
--- LINK ID --00
CHAN TYPE : 0 = Main signaling Channel
NA
: ..0.....
RESERVED
: 0h
SAPI
: 0 = High Priority
0B
IE ID
: 0Bh
00 03
LEN
: 3
--- L3-INFO --=== DTAP ===
05
TIFLAG
TIVAL
: 0h
PDC
: 5 = Mobility Management
18
ExtBit
: 0.......
N(SD)
: .0......
MESS TYPE : 18h = Identity Request
--- IDENT REQ ----- IDENTITY --02
TYPE
: .....010 = IMEI
SPARE
: ....0...
SPARE
: 0000....
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
48 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc

=== LAPD ===
--- ADDRESS --02
SAPI
CR
: ......1.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
N(S)
: 4
IFORMAT
: .......0
C0
N(R)
: 96
P
: .......0
03
T-Bit
01
ExtBit
: 0.......
MESS TYPE : 01h = Data Request
--- DATA REQ --01
IE ID
: 01h
--- CHANNEL NO --6A
CHANNEL
: 01101... = SDCCH/8 + ACCH, subch. 5
TIMESLOT
: 2
02
IE ID
: 02h
--- LINK ID --00
NA
: ..0.....
RESERVED
: 0h
SAPI
: 0 = High Priority
0B
IE ID
: 0Bh
00 08
LEN
: 8
--- L3-INFO --=== DTAP ===
06
TIFLAG
TIVAL
: 0h
PDC
2E
ExtBit
: 0.......
N(SD)
: .0......
MESS TYPE : 2Eh = Assignment Command
--- ASSIG CMD ----- CHAN DESCR --0C
CHAN TYPE : 00001... = Bm + ACCH
TIMESLOT
: 4
80
TRAIN SEQ : 100.....
H
: ...0.... = Single RF Channel
SPARE
: ....00..
FREQ BAND : 0
1D
SPARE
: 0.......
ARFCN
: 29
--- POWERCMD --05
SPARE
: 000.....
POWERLEVEL : 5
--- CHAN MODE --63
IE ID
: 63h
01
MODE
: 01h = Speech full rate
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
49 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
________________________________________________________________________

=== LAPD ===
--- ADDRESS --02
SAPI
CR
: ......1.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
--- CONTROL ----- I_FRAME --0A
N(S)
: 5
IFORMAT
: .......0
C4
N(R)
: 98
P
: .......0
08
T-Bit
2E
ExtBit
: 0.......
MESS TYPE : 2Eh = RF Channel Release
--- RF CHN REL --01
IE ID
: 01h
--- CHANNEL NO --6A
CHANNEL
: 01101... = SDCCH/8 + ACCH, subch. 5
TIMESLOT
: 2
=== LAPD ===
--- ADDRESS --02
SAPI
CR
: ......1.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
--- CONTROL ----- S_FRAME --01
SPARE
: 0
S
: 0 = RR
SFORMAT
: 1
0C
N(R)
: 6
P/F
: .......0
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
50 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc

=== LAPD ===
--- ADDRESS --00
SAPI
CR
: ......0.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
--- CONTROL ----- I_FRAME --C4
N(S)
: 98
IFORMAT
: .......0
0C
N(R)
: 6
P
: .......0
08
T-Bit
33
ExtBit
: 0.......
MESS TYPE : 33h = RF Channel Release Acknowledge
--- RF CH RACK --01
IE ID
: 01h
--- CHANNEL NO --6A
CHANNEL
: 01101... = SDCCH/8 + ACCH, subch. 5
TIMESLOT
: 2
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
51 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
LU2 TLink1A SLink2 35.964 SAPI: 0 TEI: 0 RR

LU2 TLink1A SLink2 36.146 SAPI: 0 TEI: 0 UI MEAS RES Bm + ACCH TIMESLOT: 4 Measurement
Report
Report
Report
Report
LU2 TLink1B SLink1 37.753 SAPI: 0 TEI: 1 RR
Report
LU2 TLink1A SLink2 38.383 SAPI: 0 TEI: 0 DATA IND Bm + ACCH TIMESLOT: 4 Disconnect CAUSE
VAL: 16
LU2 TLink1B SLink2 38.422 SAPI: 0 TEI: 0 DATA REQ Bm + ACCH TIMESLOT: 4 Release CAUSE
VAL: 16
Report
LU2 TLink1A SLink2 38.581 SAPI: 0 TEI: 0 DATA IND Bm + ACCH TIMESLOT: 4 Release Complete
LU2 TLink1B SLink2 38.621 SAPI: 0 TEI: 0 DATA REQ Bm + ACCH TIMESLOT: 4 Channel Release
Normal Release
LU2 TLink1B SLink2 38.622 SAPI: 0 TEI: 0 DACT SACCH Bm + ACCH TIMESLOT: 4
LU2 TLink1A SLink2 38.761 SAPI: 0 TEI: 0 EST IND Bm + ACCH TIMESLOT: 4
Report
LU2 TLink1A SLink2 39.503 SAPI: 0 TEI: 0 UI MEAS RES Bm + ACCH TIMESLOT: 4
LU2 TLink1B SLink2 39.968 SAPI: 0 TEI: 0 RF CHN REL Bm + ACCH TIMESLOT: 4
LU2 TLink1A SLink2 39.979 SAPI: 0 TEI: 0 RF CH RACK Bm + ACCH TIMESLOT: 4
EXERCISES

038 14 - LZU
Kontr - Checked
t io
e n na
lly
I nt
KI/ERA/GD/UXC
Bl n
a
52 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
53 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISE 8
A INTERFACE, Protocol Analyzer
During this exercise you will study signaling on A interface, recorded in a
logfile called lu1.msu. The corresponding signaling on Abis is also included.
To start the exercise, follow the instruction below (1-9):
1. Choose: MPA Eventlog browser in the program group GN Nettest
MPA.
2. Go to: File, Open.
3. Choose: lu1.msu.
4. To the right of the format button, there is a window displaying: overview
- more lines. Press the arrow pointing downwards and choose: detailed all fields with hex.
5. Press the format button. In the Decode params folder, choose
relative in the Time option box. Then go to the Protocol layers folder.
6. Choose ETSI GSM A interface in the window to the right of Protocols,
in use: Make sure there is an x in all the white boxes. That is, in: MTP,
SCCP, BSSAP, BSSMAP, DTAP and SS.
Choose ETSI GSM Abis in the window to the right of Protocols, in use
Make sure there is an x in all the white boxes. That is, in: LAPD,
L2Mngt, Network Mngt,Traffic Mngt, DTAP and SS.
7. Go to the link colors folder.
8. LU1 TLink1A SLink1 is A interface uplink, lets have it in magenta.
LU1 TLink1B SLink1 is A interface downlink, make it red.
LU2 TLink1A SLink2 is Abis uplink, lets have it in blue.
LU2 TLink1B SLink2 is Abis downlink, make it cyan.
Since we will not investigate LU2 TLink1A Slink1 nor LU2 TLink1B Slink1
we mark them black.
To color each entire message use the Apply Color box.
Click OK!
9. In the colored header of each frame there is a number for each frame.
The first frame in the logfile has No. 0.074.
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
54 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Below the header, the frame content is shown. There are three columns:
In the left column the octets are displayed in hex.
The middle column shows the names of the information fields in the
octet. Double click on the name for more info. Then exit.
The right column shows the decoding of the information fields.
Your traffic case starts in frame 20.992 and ends in frame 23.375.
Try to answer the following questions. Where applicable make a note of
where in the logfile you found the answer.
1. On what interface is the message in frame no. 20.992 sent? Is it
an uplink or downlink message?
2. What happens in frames 20.992 21.040?
3. What timeslot is allocated to the MS for signaling?
4. How is that timeslot configured?
5. What kind of traffic case is this (frame 21.433)?
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
55 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Look at frame 21.451

6. Over which interface is this message sent?
7. Is it uplink or downlink?
8. What is the value of BSN and FSN in the first octet?
9. What information is given in the Length Indicator?
10. Look in the SIO field. Who is the MTP user?
11.
A. What is the name of the MTP user message?
B. Find the source local reference
12. This message initiates the ________________ signaling mode.

13. There are two pointers, one for mandatory and one for optional
parameters. What is the mandatory parameter?
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
56 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
14. What kind of address information can be transferred in this

parameter and what information shall be used for routing of this
particular message?
15. There are two optional parameters. Look at the initial octets of the
second optional parameter.
A. What application protocol does this message belong to?
B. Which message in that protocol is it?
C. What upper layer information is carried over the interface in
this message?
16. Look at the message in frame 21.466.

A. Over which interface is this message transmitted?
B. Which direction?
C. What is the value of BSN and FSN (compare to previous
message)?
D. What is the name of the SCCP message?
E. What SCCP address information is included (compare
previous message)?
17. Look at the next message (21.478).

A. Over which interface is this message transmitted?
B. Which direction?
C. What is the value of BSN and FSN?
D. What is the name of the SCCP message?
E. What SCCP address information is included?
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
57 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
18. In the BSSAP header you find the discriminator (DISC) and the
data link connection identifier (DLCI).
A. Is this a DTAP or BSSMAP message?
B. How will this message be sent over the air?
19. Which air interface message is it?
Look at the identity of the mobile subscriber.

20. What is the home network of this subscriber?
21. Describe briefly what happens in the frames 21.482 - 23.375.
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
58 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Printout of log file

=== LAPD ===
--- ADDRESS --00
SAPI
CR
: ......0.
EA0
: .......0
01
TEI
: 0
EA1
: .......1
N(S)
: 74
IFORMAT
: .......0
C6
N(R)
: 99
P
: .......0
0C
T-Bit
13
ExtBit
: 0.......
MESS TYPE : 13h = Channel Required
--- CHAN RQD --01
IE ID
: 01h
--- CHANNEL NO --88
CHANNEL
: 10001... = Uplink CCCH (RACH)
TIMESLOT
: 0
13
IE ID
: 13h
--- REQ REF --1E
RA
: 1Eh
9B
N32
: 19
89
N51
: 28
N26
: 9
11
IE ID
: 11h
--- ACC DELAY --01
ACC DELAY : 1
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
59 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
__________________________________________________________________
Error: Unknown optional parameter in SCCP Connection Request message
Error: PDU is shorter than expected
Error: Cannot find end of optional parameter list
=== MTP ===
95
BSN
: 21
BIB
: 1.......
E3
FSN
: 99
FIB
: 1.......
3D
LI
: 61 = MSU
SPARE
: 00......
83
SIO
: 83h = nSCCP
=== SCCP ===
2C 41
DPC
: 0- 37-4
19 30
OPC
: 0- 12-5
SLS
: 3
01
MTYPE
: 01h = CR
--- CR --1B 00 03
SRC LREF
: 196635
--- PROT CLASS --02
PROT CLASS : 2 = Simple connection-oriented
SPARE
: 0000....
02
MAND PTR
: 2
06
OPT PTR
: 6
04
LEN
: 4
--- CALLED --43
RESERVED
: 0.......
ROUT IND
: .1......
GBLTIT IND : ..0000..
SUBSYS IND : ......1.
PC IND
: .......1
2C 01
PC
: 0- 37-4
SPARE
: 00......
FE
SUBSYS NO. : FEh = BSSAP
04
CODE
: 04h
04
LEN
: 4
--- CALLING --43
RESERVED
: 0.......
ROUT IND
: .1......
GBLTIT IND : ..0000..
SUBSYS IND : ......1.
PC IND
: .......1
65 00
PC
: 0- 12-5
SPARE
: 00......
FE
SUBSYS NO. : FEh = BSSAP
0F
CODE
: 0Fh
23
LEN
: 35
--- DATA --=== BSSAP ===
--- DISC --00
SPARE
: 0000000.
DISCR
: .......0 = Not Transparent
21
LENGTH
: 33
=== BSSMAP ===
57
MT
: 57h = Complete Layer 3 Info
--- LAYER 3 --05
IE ID
: 05h
EXERCISES

KI/ERA/GD/UXC
08
00
62 F2
20
00 01
00 07
17
12
05
08
72
62 F2
20
00 01
03
08
29
26 20 04 88
09 01 30
21
01
00
038 14 - LZU
Kontr - Checked
60 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
LEN
: 08h
--- CELL ID --DISCRIMIN : 0
MCC DIG
: 262
SPARE
: 1111....
MNC DIG
: 02
LAC
: 0001h
CI VALUE
: 0007h
IE ID
: 17h
LEN
: 12h
=== DTAP ===
TIFLAG
TIVAL
: 0h
PDC
ExtBit
: 0.......
N(SD)
: .0......
MESS TYPE : 08h = Location Updating Request
--- LOCUPDREQ ----- LOC UPDATE --TYPE
: ......10 = IMSI attach
SPARE
: ....00..
--- CIPHER KEY --KEY SEQ
: 7
SPARE
: 0.......
--- LOCAT AREA --MCC
: 262
FILLER
: 1111....
MNC
: 02
LAC
: 0001h
--- MS CLASS 1 --REV. LEVEL : 000.....
ENCRYPTION : ...00... = Algorithm A5
RF POWER
: .....011 = Class 4, handheld
--- MOBILE ID --LEN
: 8
TYPE
: 1 = IMSI
ODD/EVEN
: ....1... = Odd
IDENTITY
: 262024088901003
CODE
: 21h
LEN
: 1
--- UNKNOWN --DATA
: 00h
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
61 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
_________________________________________________________________
=== MTP ===
E3
BSN
: 99
BIB
: 1.......
96
FSN
: 22
FIB
: 1.......
0E
LI
: 14 = MSU
SPARE
: 00......
83
SIO
: 83h = nSCCP
=== SCCP ===
65 00
DPC
: 0- 12-5
4B E0
OPC
: 0- 37-4
SLS
: 14
02
MTYPE
: 02h = CC
--- CC --1B 00 03
DEST LREF : 196635
B0 00 02
SRC LREF
: 131248
--- PROT CLASS --02
PROT CLASS : 2 = Simple connection-oriented
SPARE
: 0000....
00
OPT PTR
: 0
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
62 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc

=== MTP ===
E3
BSN
: 99
BIB
: 1.......
97
FSN
: 23
FIB
: 1.......
20
LI
: 32 = MSU
SPARE
: 00......
83
SIO
: 83h = nSCCP
=== SCCP ===
65 00
DPC
: 0- 12-5
4B E0
OPC
: 0- 37-4
SLS
: 14
06
MTYPE
: 06h = DT1
--- DT1 --1B 00 03
DEST LREF : 196635
--- SEGM/REASM --00
MORE DATA : .......0 = no more data
SPARE
: 0000000.
01
MAND PTR
: 1
14
LEN
: 20
--- DATA --=== BSSAP ===
--- DISC --01
SPARE
: 0000000.
DISCR
--- DLCI --00
CBIT
: 00...... = FACCH/SDCCH
SPARE
: ..000...
SAPI
: .....000 = Call Control, Mobility Mgmt,
Radio Resources
11
LENGTH
: 17
=== DTAP ===
05
TIFLAG
TIVAL
: 0h
PDC
02
ExtBit
: 0.......
N(SD)
: .0......
MESS TYPE : 02h = Location Updating Accept
--- LOCUPDACC ----- LOCAT AREA --62 F2
MCC
: 262
FILLER
: 1111....
20
MNC
: 02
00 01
LAC
: 0001h
--- MOBILE ID --17
IE ID
: 17h
08
LEN
: 8
29
TYPE
: 1 = IMSI
ODD/EVEN
: ....1... = Odd
26 20 04 88
09 01 30
IDENTITY
: 262024088901003
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
63 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
LU2 TLink1A SLink2 20.992 SAPI: 0 TEI: 0 CHAN RQD Uplink CCCH (RACH) TIMESLOT: 0
LU2 TLink1B SLink2 21.016 SAPI: 0 TEI: 0 CHAN ACTIV SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
LU2 TLink1A SLink2 21.029 SAPI: 0 TEI: 0 CH ACT ACK SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
LU2 TLink1B SLink2 21.040 Error: Unknown Message Type SAPI: 0 TEI: 0 IMM AS CMD Downlink
CCCH (PCH + AGCH) TIMESLOT: 0 ???
LU2 TLink1A SLink2 21.433 SAPI: 0 TEI: 0 EST IND SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
Location Updating Request IMSI
262024088901003
LU1 TLink1A SLink1 21.451 Error: Unknown optional parameter in SCCP Connection Request message
Error: PDU is shorter than expected
Error: Cannot find end of optional parameter list
MSU nSCCP 0- 37- 4 0- 12- 5 3 CR 0- 37- 4 FE 0- 12- 5 FE Complete Layer 3 Information CELL ID 262
02 0001 0007
Location Updating Request IMSI 262024088901003
LU1 TLink1B SLink1 21.466 MSU nSCCP 0- 12- 5 0- 37- 4 14 CC
LU1 TLink1B SLink1 21.478 MSU nSCCP 0- 12- 5 0- 37- 4 14 DT1 Location Updating Accept IMSI
262024088901003
LU1 TLink1B SLink1 21.482 MSU nSCCP 0- 12- 5 0- 37- 4 14 DT1 Clear Command CAUSE Call control
LU2 TLink1B SLink2 21.492 SAPI: 0 TEI: 0 DATA REQ SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
Location Updating Accept IMSI
262024088901003
Channel Release Normal Release
LU1 TLink1A SLink1 21.498 MSU nSCCP 0- 37- 4 0- 12- 5 3 DT1 Clear Complete
LU2 TLink1B SLink2 21.502 SAPI: 0 TEI: 0 DACT SACCH SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
LU1 TLink1B SLink1 21.511 MSU nSCCP 0- 12- 5 0- 37- 4 14 RLSD end user originated
LU2 TLink1A SLink2 21.512 SAPI: 0 TEI: 0 UI MEAS RES SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
Measurement Report
LU1 TLink1A SLink1 21.522 MSU nSCCP 0- 37- 4 0- 12- 5 14 RLC
Measurement Report
Measurement Report
LU2 TLink1B SLink2 23.364 SAPI: 0 TEI: 0 RF CHN REL SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
LU2 TLink1A SLink2 23.375 SAPI: 0 TEI: 0 RF CH RACK SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
LU1 TLink1B SLink1 21.478 MSU nSCCP 0- 12- 5 0- 37- 4 14 DT1 Location Updating Accept IMSI
262024088901003
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
64 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
LU1 TLink1B SLink1 21.482 MSU nSCCP 0- 12- 5 0- 37- 4 14 DT1 Clear Command CAUSE Call control
Location Updating Accept
IMSI 262024088901003
Channel Release Normal
Release
LU1 TLink1A SLink1 21.498 MSU nSCCP 0- 37- 4 0- 12- 5 3 DT1 Clear Complete
LU2 TLink1B SLink2 21.502 SAPI: 0 TEI: 0 DACT SACCH SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
LU1 TLink1B SLink1 21.511 MSU nSCCP 0- 12- 5 0- 37- 4 14 RLSD end user originated
Measurement Report
LU1 TLink1A SLink1 21.522 MSU nSCCP 0- 37- 4 0- 12- 5 14 RLC
Measurement Report
Measurement Report
LU2 TLink1B SLink2 23.364 SAPI: 0 TEI: 0 RF CHN REL SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
LU2 TLink1A SLink2 23.375 SAPI: 0 TEI: 0 RF CH RACK SDCCH/ 8 + ACCH, subch. 1 TIMESLOT: 2
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
65 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISE 9
Network Service Part (NSP)
In this exercise you will examine the SCCP addressing information used on
the A interface and in the Switching System. The provided printout of a log file
contains all the SCCP fields found in messages exchanged during a certain
traffic case. The data fields are not decoded.
In order to complete the exercises you need to find out some information
about the nodes and messages:
1. Nodes: for every node involved in the traffic case fill in the type of the
node and the address of the node in the network (use the square fields
above the vertical lines)
2. Messages: for every message sent in transmitted during the traffic case
find out its direction (add arrows to the lines representing the messages),
the name of the SCCP message (insert it into the smaller rectangle above
the message) and the addressing information used by SCCP for the
routing of the message (insert it into the larger rectangle above the
message).
For your answer you can use the form provided on the next pages. The round
field above every message contains the message number as found in the log
file.
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
BSC
SPC = 2-6058
1
2
CR
66 (199)
Nr - No.
Address:DPC = 2-10368, SSN=BSSAP
8
9
10
11
12
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
File
07/01/00
03814.doc
14
15
19
20
21
22
23
24
Uen
Rev
13
18
123 3333
Datum - Date
BSC
SPC = 2-6058
17
67 (199)
Nr - No.
16
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
68 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc

Message 1
HH:MM:ss"m FROM TYPE SIO DPC
OPC SLS CIC NAME
14:16:53"6 b1bs SCCP 83 10368 6058 13
CR
ITU-T WHITE BOOK SCCP (SCCP) Connection Request (CR)
----0011 Service Indicator
SCCP
--00---- Sub-Service: Priority
Spare/priority 0 (U.S.A. only)
10------ Sub-Service: Network Ind
National message
******** Destination Point Code
10368
******** Originating Point Code
6058
******** Signaling Link Selection 13
00000001 SCCP Message Type
0x1
******** Source Local Reference
0x90048
----0010 Protocol Class
Class 2
0000---- Spare
00000010 Ptr to Called address pa
2
00000110 Ptr to optional param.
6
Called address parameter
00000100 Parameter Length
4
-------1 Point Code Indicator
PC present
------1- Subsystem No. Indicator
SSN present
--0000-- Global Title Indicator
No global title included
-1------ Routing Indicator
Route on DPC + Subsystem No.
0------- For national use
0
******** Called Party SPC
10368
00------ Spare
11111110 Subsystem number
BSSAP
Calling address parameter
00000100 Parameter name
Calling party address
4
PC present
SSN present
0
******** Calling Party SPC
6058
00------ Spare
BSSAP
Data parameter
Data
00100000 Parameter length
32
******** Data
00 1E 57 05 08 00 62 F2 20 00 02 00
08 17 0F 05 08 00 62 F2 20 00 03 23
05 F4 00 00 40 DD 21 81
End of Optional Params
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
69 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 2
14:16:53"7 mapr SCCP 83 6049 10368 11
UDT
ITU-T WHITE BOOK SCCP (SCCP) Unitdata (UDT)
SCCP
National message
6049
10368
0x9
Class 0
1000---- Message Handling
3
00000101 Ptr to Calling address p
5
00001001 Ptr to Data parameter
9
2
PC absent
SSN present
0
VLR
4
PC present
SSN present
0
10368
00------ Spare
VLR
Data parameter
34
******** Data
62 20 48 04 FA 00 14 4E 6C 18 A1 16
02 01 01 02 01 09 30 0E 81 04 00 00
40 DD 30 06 0A 01 00 0A 01 01
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
70 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 3
14:16:53"7 b1br SCCP 83 6058 10368 9
CC
ITU-T WHITE BOOK SCCP (SCCP) Connection Confirm (CC)
SCCP
National message
6058
10368
0x2
******** Destination Local Ref.
0x90048
0x21009
Class 2
0000---- Spare
0
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
71 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 4
14:16:53"7 maps SCCP 83 10368 6049 14
UDT
SCCP
National message
10368
6049
0x9
Class 0
3
7
17
4
PC present
SSN present
0
10368
00------ Spare
VLR
10
PC absent
SSN present
Has transln,n-plan,code,natur
Route on Global Title
0
VLR
00000000 Translation Type
Not used
----0010 Encoding Scheme
BCD, even number of digits
0001---- Numbering Plan
ISDN/Telephony (E.164/E.163)
-0000011 Nat. of Address Indicator National significant number
0------- Spare
******** Calling Address Signals
1725100097
Data parameter
32
******** Data
64 1E 49 04 FA 00 14 4E 6C 16 A2 14
02 01 01 30 0F 02 01 09 30 0A 80 08
62 02 52 01 00 97 47 F1
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
72 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 5
14:16:53"8 mapr SCCP 83 6049 10368 1
UDT
SCCP
National message
6049
10368
0x9
Class 0
3
5
9
2
PC absent
SSN present
0
HLR
4
PC present
SSN present
0
10368
00------ Spare
VLR
Data parameter
35
******** Data
62 21 48 04 FA 00 15 47 6C 19 A1 17
02 01 01 02 01 09 30 0F 80 08 62 02
52 01 00 97 47 F1 30 03 0A 01 01
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
73 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 6
14:16:53"8 maps SCCP 83 10368 6049 15
UDT
SCCP
National message
10368
6049
0x9
Class 0
3
7
17
4
PC present
SSN present
0
10368
00------ Spare
VLR
10
PC absent
SSN present
0
HLR
Not used
0------- Spare
1725100096
Data parameter
133
******** Data
64 81 82 49 04 FA 00 15 47 6C 7A A2
78 02 01 01 30 73 02 01 09 30 80 A1 22 04 10 A6 6C 02 8C 4E 67 A3 40 1C
11 7F 38 86 CC 19 DE 04 04 5E 03 61 0C 04 08 BE B3 01 4A E7 D1 30 00 A1
22 04 10 3D 20 CB 79 B7 47 93 4C 9C BE 9C 6C 08 85 4B 4F 04 04 32 0B 28
0E 04 08 E3 04 52 6E 9E 19 10 00 A1 22 04 10 B5 7F 78 5F 8F 3F 2E C6 CE
30 E0 D2 4F 08 51 C8 04 04 02 9F A7 AD 04 08 15 96 63 A5 FC D1 78 00 00
00
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
74 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 7
14:16:53"9 b1br SCCP 83 6058 10368 9
DT1
ITU-T WHITE BOOK SCCP (SCCP) Data Form 1 (DT1)
SCCP
National message
6058
10368
0x6
0x90048
-------0 Segment/reass M indicator No more data
0000000- Spare
1
Data parameter
22
******** Data
01 00 13 05 12 01 A6 6C 02 8C 4E 67
A3 40 1C 11 7F 38 86 CC 19 DE
Message 8
14:16:55"5 b1bs SCCP 83 10368 6058 13
DT1
SCCP
National message
10368
6058
0x6
0x21009
0000000- Spare
1
Data parameter
9
******** Data
01 00 06 05 54 5E 03 61 0C
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
75 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 9
14:16:55"6 mapr SCCP 83 6049 10368 4
UDT
SCCP
National message
6049
10368
0x9
Class 0
3
5
9
2
PC absent
SSN present
0
HLR
4
PC present
SSN present
0
10368
00------ Spare
VLR
Data parameter
82
******** Data
62 50 48 04 FA 00 17 47 6B 1A 28
06 07 00 11 86 05 01 01 01 A0 0D
0B A1 09 06 07 04 00 00 01 00 01
6C 2C A1 2A 02 01 01 02 01 02 30
04 08 62 02 52 01 00 97 47 F1 81
91 94 71 72 06 00 79 04 07 91 94
72 06 00 79 8A 04 00 00 00 01
18
60
02
22
07
71
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
76 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 10
14:16:55"7 maps SCCP 83 10368 6049 6
UDT
SCCP
National message
10368
6049
0x9
Class 1
3
7
17
4
PC present
SSN present
0
10368
00------ Spare
VLR
10
PC absent
SSN present
0
HLR
Not used
0------- Spare
1725100096
Data parameter
201
******** Data
65 81 C6 48 03 CC 00 FF 49 04 FA 00
17 47 6B 2A 28 28 06 07 00 11 86 05 01 01 01 A0 1D 61 1B 80 02 07 80 A1
09 06 07 04 00 00 01 00 01 02 A2 03 02 01 00 A3 05 A1 03 02 01 00 6C 80
A1 81 88 02 01 04 02 01 07 30 80 81 07 91 94 71 52 71 79 14 82 01 0A 83
01 00 A4 12 04 01 11 04 01 12 04 01 13 04 01 14 04 01 15 04 01 16 A6 0F
04 01 11 04 01 21 04 01 22 04 01 61 04 01 62 A7 80 A0 80 04 01 21 30 80
30 06 83 01 10 84 01 (there was more, deleted)
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
77 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 11
14:16:55"8 mapr SCCP 83 6049 10368 11
UDT
SCCP
National message
6049
10368
0x9
Class 0
3
5
9
2
PC absent
SSN present
0
HLR
4
PC present
SSN present
0
10368
00------ Spare
VLR
Data parameter
20
******** Data
65 12 48 04 FA 00 17 47 49 03 CC 00
FF 6C 05 A2 03 02 01 04
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
78 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 12
14:16:55"8 maps SCCP 83 10368 6049 6
UDT
SCCP
National message
10368
6049
0x9
Class 1
3
7
17
4
PC present
SSN present
0
10368
00------ Spare
VLR
10
PC absent
SSN present
0
HLR
Not used
0------- Spare
1725100096
Data parameter
213
******** Data
65 81 D2 48 03 CC 00 FF 49 04 FA 00
17 47 6C 81 C4 A1 81 C1 02 01 05 02 01 07 30 80 A7 80 A0 80 04 01 2A 30
80 30 06 83 01 10 84 01 04 30 06 83 01 60 84 01 04 30 06 82 01 10 84 01
04 00 00 00 00 A0 80 04 01 2B 30 80 30 06 83 01 10 84 01 04 30 06 83 01
60 84 01 04 30 06 82 01 10 84 01 04 00 00 00 00 A1 25 04 01 92 30 20 30
06 83 01 10 84 01 04 30 06 83 01 20 84 01 04 30 06 83 01 60 84 01 04 30
06 82 01 10 84 01 04 A1 25 04 01 93 30 20 30 06 83 01 10 84 01 04 30 06
83 01 20 84 01 04 30 06 (there was more, deleted)
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
79 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 13
14:16:55"8 maps SCCP 83 10368 6049 6
UDT
SCCP
National message
10368
6049
0x9
Class 1
3
7
17
4
PC present
SSN present
0
10368
00------ Spare
VLR
10
PC absent
SSN present
0
HLR
Not used
0------- Spare
1725100096
Data parameter
143
******** Data
65 81 8C 48 03 CC 00 FF 49 04 FA 00
17 47 6C 7F A1 7D 02 01 06 02 01 07 30 80 A7 80 A1 0D 04 01 94 30 08 30
06 82 01 10 84 01 04 A3 06 04 01 71 84 01 05 A3 06 04 01 51 84 01 05 A3
09 04 01 12 84 01 05 82 01 00 A3 06 04 01 14 84 01 05 A3 09 04 01 11 84
01 05 81 01 01 A3 09 04 01 13 84 01 05 81 01 01 A3 0B 04 01 41 84 01 04
30 03 83 01 10 A3 0B 04 01 41 84 01 04 30 03 83 01 60 A3 0B 04 01 41 84
01 04 30 03 82 01 10 00 00 00 00
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
80 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 14
14:16:55"9 mapr SCCP 83 6049 10368 10
UDT
SCCP
National message
6049
10368
0x9
Class 0
3
5
9
2
PC absent
SSN present
0
HLR
4
PC present
SSN present
0
10368
00------ Spare
VLR
Data parameter
20
******** Data
65 12 48 04 FA 00 17 47 49 03 CC 00
FF 6C 05 A2 03 02 01 05
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
81 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 15
14:16:55"9 mapr SCCP 83 6049 10368 8
UDT
SCCP
National message
6049
10368
0x9
Class 0
3
5
9
2
PC absent
SSN present
0
HLR
4
PC present
SSN present
0
10368
00------ Spare
VLR
Data parameter
20
******** Data
65 12 48 04 FA 00 17 47 49 03 CC 00
FF 6C 05 A2 03 02 01 06
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
82 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 16
14:16:55"9 maps SCCP 83 10368 6049 6
UDT
SCCP
National message
10368
6049
0x9
Class 1
3
7
17
4
PC present
SSN present
0
10368
00------ Spare
VLR
10
PC absent
SSN present
0
HLR
Not used
0------- Spare
1725100096
Data parameter
31
******** Data
64 1D 49 04 FA 00 17 47 6C 15 A2 13
02 01 01 30 0E 02 01 02 30 09 04 07
91 94 71 52 01 00 69
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
83 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 17
14:16:56"0 b1br SCCP 83 6058 10368 9
DT1
SCCP
National message
6058
10368
0x6
0x90048
0000000- Spare
1
Data parameter
20
******** Data
00 12 53 07 02 06 00 0A 09 03 BE B3
01 4A E7 D1 30 00 23 01
Message 18
14:16:56"2 b1bs SCCP 83 10368 6058 13
DT1
SCCP
National message
10368
6058
0x6
0x21009
0000000- Spare
1
Data parameter
18
******** Data
00 10 55 20 0B 17 09 43 09 15 60 11
50 45 09 F1 2C 02
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
84 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 19
14:16:56"3 b1br SCCP 83 6058 10368 9
DT1
SCCP
National message
6058
10368
0x6
0x90048
0000000- Spare
1
Data parameter
17
******** Data
01 00 0E 05 02 62 F2 20 00 02 17 05
F4 61 00 00 03
Message 20
14:16:57"4 b1bs SCCP 83 10368 6058 13
DT1
SCCP
National message
10368
6058
0x6
0x21009
0000000- Spare
1
Data parameter
5
******** Data
01 00 02 05 1B
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
85 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 21
14:16:57"4 b1br SCCP 83 6058 10368 9
DT1
SCCP
National message
6058
10368
0x6
0x90048
0000000- Spare
1
Data parameter
10
******** Data
00 08 20 07 02 06 00 04 01 09
Message 22
14:16:57"6 b1bs SCCP 83 10368 6058 13
DT1
SCCP
National message
10368
6058
0x6
0x21009
0000000- Spare
1
Data parameter
3
******** Data
00 01 21
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
86 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 23
14:16:57"6 b1br SCCP 83 6058 10368 9
RLSD
ITU-T WHITE BOOK SCCP (SCCP) Released (RLSD)
SCCP
National message
6058
10368
0x4
0x90048
0x21009
00000000 Release Cause
End user originated
0
Message 24
14:16:57"7 b1bs SCCP 83 10368 6058 9
RLC
ITU-T WHITE BOOK SCCP (SCCP) Release Complete (RLC)
SCCP
National message
10368
6058
0x5
0x21009
0x90048
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
87 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
EXERCISE 10
SCCP User information
In this exercise you will examine the SCCP User information exchanged
during a certain traffic case on the A interface and in the Switching System.
The provided printout of a log file contains only the data fields. These are the
data fields from the messages you were analyzing in exercise 9 Network
Service Part.
Note that some of the messages you analyzed in exercise 9 did not carry any
SCCP user data, therefore they will not appear in this exercise.
In order to complete the exercises you need to:
1. Identify the SCCP user in each case
2. Identify the message in each case
3. Point out different MAP dialogues where relevant
4. Point out the question-answer message pairs within the MAP dialogues
5. Note the content of the SCCP User messages.
For your answer you can use the form provided on the next pages. The round
field above every message contains the message number as found in the log
file. Into the light gray field insert the SCCP User name, into the darker gray
field what SCCP User message is sent.
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
Uen
Rev
File
07/01/00
03814.doc
1
2
BSSMAP
123 3333
Datum - Date
MSC/VLR
BSC
88 (199)
Nr - No.
Complete Layer 3 Information
TMSI = 000040DD
3
4
8
9
10
11
12
VLR/HLR
EXERCISES

KI/ERA/GD/UXC
BSC
038 14 - LZU
Kontr - Checked
File
07/01/00
03814.doc
14
15
19
20
21
22
23
24
Uen
Rev
13
18
123 3333
Datum - Date
MSC/VLR
17
89 (199)
Nr - No.
16
VLR/HLR
EXERCISES

90 (199)
Nr - No.
038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc

Message 1
E-GSM 08.08 (BSSMAP) Rev 5.3.0 (BSSM)
-------0 Discrimination bit D
0000000- Filler
00011110 Message Length
01010111 Message Type
Cell identifier
00000101 IE Name
00001000 IE Length
----0000 Cell ID discriminator
******** MCC number
1111---- Filler
----0000 MNC digit 1
0010---- MNC digit 2
******** LAC
******** CI
Layer 3 information
00010111 IE Name
00001111 IE Length
******** L3 Message Contents
Complete layer 3 information (CL3I)

BSSMAP
Chosen Channel
00100001 IE Name
----0001 Channel
1000---- Spare
DTAP 5
MM Message
E-GSM 04.08 (DTAP 5.3.0,SMCP 5.1.0)
(LUREQ)
----0101 Protocol Discriminator
-000---- Transaction Id value
0------- Transaction Id flag
--001000 Message Type
-0------ Send Sequence Number
0------- Extension bit
------00 LUT
-----0-- Spare
----0--- Follow-On Request
0000---- Key sequence
Location Area identification
******** MCC number
1111---- Filler
******** LAC
Mobile Station Classmark 1
-----011 RF power capability
30
0x57
Cell identifier
8
CGI used to identify cell
262
0
2
2
8
Layer 3 information
15
05 08 00 62 F2 20 00 03 23 05 F4 00
00 40 DD
Chosen Channel
SDCCH
-- unknown / undefined value -LUREQ
Registration message
(DTAP) Location updating req.
mobility management msg
TI value 0
message sent from orig TI
0x8
0
Normal loc updating
No follow-on request pending
0
262
0
2
3
Class 4, GSM 900
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
91 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
----0--- A5/1 algorithm supported

Available
---0---- Ctr Early Classmark SendingNot implemented
-01----- Revision level
Used by phase 2 MSs
0------- Spare
Mobile IDentity
00000101 IE Length
5
-----100 Type of identity
TMSI
----0--- Odd/Even Indicator
Even no of digits
1111---- Filler
******** MID TMSI
00 00 40 DD
Message 2
E-GSM 09.02 (MAP) Version 4.9.0 (MAP)
Begin
1 Origination Transaction ID
******** Orig Trans ID
0xFA00144E
2 Component Portion
2.1 Invoke
2.1.1 Invoke ID
00000001 Invoke ID value
1
2.1.2 Local Operation
00001001 Operation Code
Send Parameters
2.1.3 Parameter Sequence
2.1.3.1 Tmsi
******** TMS ID
00 00 40 DD
2.1.3.2 Request Parameter List
2.1.3.2.1 Request Parameter
00000000 Request Parameter
Request iMSI
Request authentication set
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
92 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 4
End
1 Destination Transaction ID
******** Dest Trans ID
0xFA00144E
2 Component Portion
2.1 Return Result Last
2.1.1 Invoke ID
1
2.1.2 Return Result Sequence
2.1.2.1 Local Operation
Send Parameters
2.1.2.2 Sent Parameter List
2.1.2.2.1 Imsi
******** MCC + MNC + MSIN
262025100079741
1111---- FILLER
Message 5
Begin
0xFA001547
2 Component Portion
2.1 Invoke
2.1.1 Invoke ID
1
Send Parameters
2.1.3.1 Imsi
262025100079741
1111---- FILLER
2.1.3.2 Request Parameter List
Request authentication set
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
93 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 6
End
0xFA001547
2 Component Portion
2.1.1 Invoke ID
1
Send Parameters
2.1.2.2 Sent Parameter List
2.1.2.2.1 Authentication Set
2.1.2.2.1.1 Rand
******** Authentication Random No
A6 6C 02 8C 4E 67
86 CC 19 DE
2.1.2.2.1.2 Sres
******** Authentication Response
5E 03 61 0C
2.1.2.2.1.3 Kc
******** Ciphering Key
BE B3 01 4A E7 D1
2.1.2.2.2.1 Rand
3D 20 CB 79 B7 47
08 85 4B 4F
2.1.2.2.2.2 Sres
32 0B 28 0E
2.1.2.2.2.3 Kc
E3 04 52 6E 9E 19
2.1.2.2.3.1 Rand
B5 7F 78 5F 8F 3F
4F 08 51 C8
2.1.2.2.3.2 Sres
02 9F A7 AD
2.1.2.2.3.3 Kc
15 96 63 A5 FC D1
A3 40 1C 11 7F 38
30 00
93 4C 9C BE 9C 6C
10 00
2E C6 CE 30 E0 D2
78 00
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
94 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 7
E-GSM 04.08 (DTAP 5.3.0,SMCP 5.1.0) (DTAP) Authentication request (AUTREQ)
DTAP
0000000- Filler
-----000 SAPI
Signaling
--000--- Spare
00------ Radio channel id
fACCH or sDCCH
19
TI value 0
0x12
0
----0001 Key sequence
1
0000---- Spare
Authentication parameter RAND
******** RAND Value
A6 6C 02 8C 4E 67 A3 40 1C 11 7F 38
86 CC 19 DE
Message 8
E-GSM 04.08 (DTAP 5.3.0,SMCP 5.1.0) (DTAP) Authentication response (AUTREP)
DTAP
0000000- Filler
-----000 SAPI
Signaling
--000--- Spare
fACCH or sDCCH
6
TI value 0
0x14
1
Authentication parameter SRES
******** Authen response signature 5E 03 61 0C
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
95 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 9
Begin
0xFA001747
2 Dialogue Portion
2.1 Dialogue External
2.1.1 Dialogue Object ID
00000000 Authority
CCITT Recommendation
00010001 Name Form
q
10000110 Rec Number
7
00000101 Rec Number
73
00000001 AS
1
00000001 Dialog-AS
Dialogue PDU
00000001 Version
2.1.2 Dialogue single ASN1
2.1.2.1 Dialogue Request
2.1.2.1.1 Application Context Name
2.1.2.1.1.1 ACN Object ID
0000---- ObjId
CCITT
----0100 Organization
Identified-organization
00000000
ETSI
00000000 Domain
Mobile Domain
00000001 Mobile Subdomain
GSM-Network
00000000 Common Component ID
AC-ID
00000001 Application Context
networkLocUp
00000010 Version
2
3 Component Portion
3.1 Invoke
3.1.1 Invoke ID
1
Update Location
3.1.3.1 Imsi
262025100079741
1111---- FILLER
3.1.3.2 Msc Number
1------- Extension Indicator
No Extension
-001---- Nature of Address
International number
----0001 Numbering Plan Indicator
ISDN Telephony No plan (E.164)
******** MSC Address Signals
491727600097
3.1.3.3 Vlr Number
No Extension
******** VLR Address Signals
491727600097
3.1.3.4 Lmsi
******** LMSI
00 00 00 01
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
96 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 10
Continue
0xFFCC00FF
0xFA001747
3 Dialogue Portion
3.1 Dialogue External 3.1.1 Dialogue Object ID
00000000 Authority
CCITT Recommendation
00010001 Name Form
q
10000110 Rec Number
7
00000101 Rec Number
73
00000001 AS
1
00000001 Dialog-AS
Dialogue PDU
00000001 Version
3.1.2 Dialogue single ASN1
3.1.2.1 Dialogue Response
3.1.2.1.1 Protocol Version
00000111 UnusedBits
7
1------- Version 1
Yes
-0000000 Filler
3.1.2.1.2 Application Context Name
3.1.2.1.2.1 ACN Object ID
0000---- ObjId
CCITT
----0100 Organization
Identified-organization
00000000
ETSI
00000000 Domain
Mobile Domain
00000001 Mobile Subdomain
GSM-Network
00000000 Common Component ID
AC-ID
00000001 Application Context
netLocUp
00000010 Version
2
3.1.2.1.3 Result
3.1.2.1.3.1 Associate Result
00000000 Associate Result
Accepted
3.1.2.1.4 Result Source Diagnostic
3.1.2.1.4.1 Dialogue Service User
3.1.2.1.4.1.1 Dialogue Service User Value
00000000 Dialogue Servie User
Null
4 Component Portion
4.1 Invoke
4.1.1 Invoke ID
4
Insert Subscriber Data
4.1.3.1 Msisdn
No Extension
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
97 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc

******** MS ISDN Address Signals
491725179741
4.1.3.2 Category
00001010 Category Q.763
Ordinary calling subscriber
4.1.3.3 Subscriber Status
00000000 Subscriber Status
Service granted
4.1.3.4 Bearer Service List
4.1.3.4.1 Bearer Service Code
00010001 Bearer Service Code
Data cDA 300bps
Data cDA 1200bps
Data cDA 1200 75bps
Data cDA 2400bps
Data cDA 4800bps
Data cDA 9600bps
4.1.3.5 Teleservice List
4.1.3.5.1 Teleservice Code
00010001 Teleservice Code
Telephony
Short message mT PP
Short message mO PP
Facsimile group3And alter speech
Automatic facsimile group3
4.1.3.6 Provisioned Ss
4.1.3.6.1 Forwarding Info
4.1.3.6.1.1 Ss Code
00100001 Ss Code
Cfu
4.1.3.6.1.2 Forwarding Feature List
4.1.3.6.1.2.1 Forwarding Feature
4.1.3.6.1.2.1.1 Teleservice
00010000 Teleservice
All speech transmission services
4.1.3.6.1.2.1.2 Ss Status
0000---- Unused
0
----0--- Quiescent/Operative Ind
Operative
-----1-- Provision indicator
Provisioned
------0- Registration indicator
Not Registered
-------0 Activation indicator
Not Active
All facsimile transmission services
4.1.3.6.1.2.2.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
98 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc

Not Active
4.1.3.6.1.2.3.1 Bearer Service
00010000 Bearer Service
All data cDA Services
4.1.3.6.1.2.3.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
4.1.3.6.2.1 Ss Code
00101001 Ss Code
Cfb
4.1.3.6.2.2.1.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
4.1.3.6.2.2.2.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
4.1.3.6.2.2.3.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
99 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 11
Continue
1 Origination Transaction
2 Destination Transaction
3 Component Portion
3.1.1 Invoke ID
ID
0xFA001747
ID
0xFFCC00FF
Message 12
Continue
0xFFCC00FF
0xFA001747
3 Component Portion
3.1 Invoke
3.1.1 Invoke ID
5
3.1.3.1.1.1 Ss Code
00101010 Ss Code
Cfnry
3.1.3.1.1.2.1.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
3.1.3.1.1.2.2.2 Ss Status
0000---- Unused
0
EXERCISES

KI/ERA/GD/UXC
----0-------1-------0-------0
00010000
0000-------0-------1-------0-------0
00101011
00010000
0000-------0-------1-------0-------0
01100000
0000-------0-------1-------0-------0
00010000
0000-------0-------1-------0-------0
10010010
00010000
038 14 - LZU
Kontr - Checked
100 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Quiescent/Operative Ind
Operative
Provision indicator
Provisioned
Registration indicator
Not Registered
Activation indicator
Not Active
Bearer Service
3.1.3.1.1.2.3.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
3.1.3.1.2.1 Ss Code
Ss Code
Cfnrc
Teleservice
3.1.3.1.2.2.1.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
Teleservice
3.1.3.1.2.2.2.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
Bearer Service
3.1.3.1.2.2.3.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
3.1.3.1.3 Call Barring Info
3.1.3.1.3.1 Ss Code
Ss Code
Baoc
3.1.3.1.3.2 Call Barring Feature List
3.1.3.1.3.2.1 Call Barring Feature
Teleservice
3.1.3.1.3.2.1.2 Ss Status
EXERCISES

KI/ERA/GD/UXC
0000-------0-------1-------0-------0
00100000
0000-------0-------1-------0-------0
01100000
0000-------0-------1-------0-------0
00010000
0000-------0-------1-------0-------0
10010011
00010000
0000-------0-------1-------0-------0
00100000
0000-------0-------1--
038 14 - LZU
Kontr - Checked
101 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
Teleservice
All short message services
3.1.3.1.3.2.2.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
Teleservice
3.1.3.1.3.2.3.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
Bearer Service
3.1.3.1.3.2.4.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
3.1.3.1.4.1 Ss Code
Ss Code
Boic
Teleservice
3.1.3.1.4.2.1.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
Teleservice
3.1.3.1.4.2.2.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
EXERCISES

KI/ERA/GD/UXC
038 14 - LZU
Kontr - Checked
102 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc

Not Registered
Not Active
3.1.3.1.4.2.3.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
3.1.3.1.4.2.4.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
3.1.3.1.5.1 Ss Code
10010100 Ss Code
Boic ex hC
3.1.3.1.5.2.1.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
3.1.3.1.5.2.2.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
3.1.3.1.5.2.3.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
103 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 13
Continue
0xFFCC00FF
0xFA001747
3 Component Portion
3.1 Invoke
3.1.1 Invoke ID
6
3.1.3.1.1.1 Ss Code
10010100 Ss Code
Boic ex hC
3.1.3.1.1.2.1.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
3.1.3.1.2 Ss Data
3.1.3.1.2.1 Ss Code
01110001 Ss Code
Aoci
3.1.3.1.2.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Active
3.1.3.1.3 Ss Data
3.1.3.1.3.1 Ss Code
01010001 Ss Code
Multi pTY
3.1.3.1.3.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Active
3.1.3.1.4 Ss Data
3.1.3.1.4.1 Ss Code
00010010 Ss Code
Clir
EXERCISES

KI/ERA/GD/UXC
0000-------0-------1-------0-------1
00000000
00010100
0000-------0-------1-------0-------1
00010001
0000-------0-------1-------0-------1
00000001
00010011
0000-------0-------1-------0-------1
00000001
01000001
0000-------0-------1-------0-------0
00010000
038 14 - LZU
Kontr - Checked
104 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
3.1.3.1.4.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Active
3.1.3.1.4.3 Cli Restriction Option
Cli Restriction Option
Permanent
3.1.3.1.5 Ss Data
3.1.3.1.5.1 Ss Code
Ss Code
Colr
3.1.3.1.5.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Active
3.1.3.1.6 Ss Data
3.1.3.1.6.1 Ss Code
Ss Code
Clip
3.1.3.1.6.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Active
3.1.3.1.6.3 Override Category
Override Category
Override disabled
3.1.3.1.7 Ss Data
3.1.3.1.7.1 Ss Code
Ss Code
Colp
3.1.3.1.7.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Active
3.1.3.1.7.3 Override Category
Override Category
Override disabled
3.1.3.1.8 Ss Data
3.1.3.1.8.1 Ss Code
Ss Code
Cw
3.1.3.1.8.2 Ss Status
Unused
0
Operative
Provision indicator
Provisioned
Not Registered
Not Active
3.1.3.1.8.3 Basic Service Group List
3.1.3.1.8.3.1 Teleservice
Teleservice
3.1.3.1.9 Ss Data
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
105 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
3.1.3.1.9.1 Ss Code
01000001 Ss Code
Cw
3.1.3.1.9.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
3.1.3.1.9.3.1 Teleservice
3.1.3.1.10 Ss Data
3.1.3.1.10.1 Ss Code
01000001 Ss Code
Cw
3.1.3.1.10.2 Ss Status
0000---- Unused
0
Operative
Provisioned
Not Registered
Not Active
3.1.3.1.10.3.1 Bearer Service
Message 14
Continue
1 Origination Transaction
2 Destination Transaction
3 Component Portion
3.1.1 Invoke ID
ID
0xFA001747
ID
0xFFCC00FF
Message 15
Continue
0xFA001747
0xFFCC00FF
3 Component Portion
3.1 Return Result Last 3.1.1 Invoke ID
6
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
106 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 16
End
0xFA001747
2 Component Portion
2.1.1 Invoke ID
1
Update Location
2.1.2.2 Extensible Update Location Res
2.1.2.2.1 Hlr Number
No Extension
******** HLR Address Signals
491725100096
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
107 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 17
0000000- Filler
Layer 3 header information
00000111 IE Name
00000010 IE Length
0000---- Spare
-----000 Transaction Id value
----0--- Transaction Id flag
0000---- Spare
Encryption information
00001010 IE Name
00001001 IE Length
-------1 No encryption
------1- GSM A5/1
-----0-- GSM A5/2
----0--- GSM A5/3
---0---- GSM A5/4
--0----- GSM A5/5
-0------ GSM A5/6
0------- GSM A5/7
******** Encryption Key
Cipher Response Mode
00100011 IE Name
-------1 Cipher Response Mode
0000000- Spare
Cipher Mode Command (CICMD)

BSSMAP
18
0x53
2
radio resources management msg
TI value 0
9
May be used
May be used
Not used
Not used
Not used
Not used
Not used
Not used
BE B3 01 4A E7 D1 30 00
Cipher Response Mode
IMEISV must be included by MS
Message 18
0000000- Filler
Layer 3 Message Contents
00100000 IE Name
00001011 IE Length
******** Layer 3 Message Contents
Chosen Encryption Algorithm
00101100 IE Name
00000010 Algorithm Identifier
Cipher Mode Complete (CICMP)

BSSMAP
16
0x55
Layer 3 Message Contents
11
17 09 43 09 15 60 11 50 45 09 F1
Chosen Encryption Algorithm
GSM user data encrypt. v1 A5/1
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
108 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 19
E-GSM 04.08 (DTAP 5.3.0,SMCP 5.1.0) (DTAP) Location updating accept (LUACC)
DTAP
0000000- Filler
-----000 SAPI
Signaling
--000--- Spare
fACCH or sDCCH
14
TI value 0
0x2
0
Location Area identification
******** MCC number
262
1111---- Filler
0
2
******** LAC
2
Mobile IDentity
00010111 IE Name
Mobile IDentity
00000101 IE Length
5
-----100 Type of identity
TMSI
----0--- Odd/Even Indicator
Even no of digits
1111---- Filler
******** MID TMSI
61 00 00 03
Message 20
E-GSM 04.08 (DTAP 5.3.0,SMCP 5.1.0) (DTAP) TMSI reallocation complete
(TRCMP)
DTAP
0000000- Filler
-----000 SAPI
Signaling
--000--- Spare
fACCH or sDCCH
2
TI value 0
0x1B
0
EXERCISES

038 14 - LZU
Kontr - Checked
KI/ERA/GD/UXC
109 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Message 21
0000000- Filler
00000111 IE Name
00000010 IE Length
0000---- Spare
-----000 Transaction Id value
----0--- Transaction Id flag
0000---- Spare
Cause
00000100 IE Name
00000001 IE Length
-0001001 Cause value
0------- Cause Extension
CLeaR CoMmanD (CLCMD)

BSSMAP
8
0x20
2
radio resources management msg
TI value 0
Cause
1
Call control
No Extension
Message 22
BSSM
CLCMP
E-GSM 08.08 (BSSMAP) Rev 5.3.0 (BSSM) CleaR COMplete (CLCMP)
BSSMAP
0000000- Filler
1
0x21
EXERCISES

038 14 - LZU
Kontr - Checked
t io
e n na
lly
I nt
KI/ERA/GD/UXC
Bl n
a
110 (199)
Nr - No.
123 3333
Uen
Datum - Date
Rev
File
07/01/00
03814.doc
Draft prETS 300 908 (GSM 05.02 version 5.8.0 Release 1996): April 1999
Scope
This European Telecommunications Standard (ETS) defines the physical channels of the radio
sub-system required to support the logical channels. It includes a description of the logical channels and
the definition of frequency hopping, TDMA frames, timeslots and bursts.
1.1
Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the
latest edition of the publication referred to applies.
[1]
GSM 01.04 (ETR 350): "Digital cellular telecommunications system (Phase 2+);
Abbreviations and acronyms".
[2]
GSM 03.03 (ETS 300 927): "Digital cellular telecommunications

(Phase 2+); Numbering, addressing and identification".
[3]
GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile

Station - Base Station System (MS - BSS) interface Channel structures and
access capabilities".
[4]
GSM 04.06 (ETS 300 938): "Digital cellular telecommunications system; Mobile
Station - Base Station System (MS - BSS) interface Data Link (DL) layer
specification".
[5]
GSM 04.08 (ETS 300 940): "Digital cellular telecommunications

(Phase 2+); Mobile radio interface layer 3 specification".
system
[6]
GSM 05.03 (ETS 300 909): "Digital

(Phase 2+); Channel coding".
[7]
GSM 05.04 (ETS 300 959):

Modulation".
system
cellular
telecommunications
system
"Digital cellular
telecommunications
system;
[8]
GSM 05.05 (ETS 300 910): "Digital cellular

(Phase 2+); Radio transmission and reception".
telecommunications
system
[9]

(Phase 2+); Radio subsystem link control".
telecommunications
system
[10]

(Phase 2+); Radio subsystem synchronization".
telecommunications
system
[11]
GSM 03.64: "Digital cellular telecommunications system (Phase 2+); General

Packet Radio Service (GPRS); Overall description of the GPRS Radio Interface;
Stage 2".
[12]
GSM 04.60: "Digital cellular telecommunications system (Phase 2+); General

Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System
(BSS interface; Radio Link Control (RLC) and Medium Access Control (MAC)
Layer Specification".
1.2
Abbreviations
Abbreviations used in this ETS are listed in GSM 01.04 [1].
GSM Advanced System Technique
Exercises
111 (199)
General
The radio subsystem is required to support a certain number of logical channels that can be separated
into categories as defined in GSM 04.03:
i)
ii)
The traffic channels (TCHs)

The control channels
More information is given about these logical channels in clause 3 which also defines a number of special
channels used by the radio sub-system.
Clause 4 of this document describes the physical resource available to the radio sub-system, clause 5
defines physical channels based on that resource and clause 6 specifies how the logical channels shall
be mapped onto physical channels. Figure 1 depicts this process.
Logical channels
3.1
General
This section describes the logical channels that are supported by the radio subsystem.
3.2
Traffic channels
3.2.1
General
Traffic channels (TCHs) are intended to carry either encoded speech or user data in circuit switched
mode. Two general forms of traffic channel are defined:
i)
ii)
Full rate traffic channel (TCH/F). This channel carries information at a gross rate of
22,8 kbit/s.
Half rate traffic channel (TCH/H). This channel carries information at a gross rate of
11,4 kbit/s.
All traffic channels are bi-directional unless otherwise stated. Unidirectional downlink full rate channels,
TCH/FD, are defined as the downlink part of the corresponding TCH/F.
Multiple full rate channels can be allocated to the same MS. This is referred to as multislot configurations,
which is defined in sub-clause 6.4.2.1.
The specific traffic channels available in the categories of speech and user data are defined in the
sections following.
3.2.2
Speech traffic channels
The following traffic channels are defined to carry encoded speech:

i)
ii)
3.2.3
Full rate traffic channel for speech (TCH/FS).

Half rate traffic channel for speech (TCH/HS).
Circuit switched data traffic channels
The following traffic channels are defined to carry user data:

i)
ii)
iii)
iv)
v)
vi)
Full rate traffic channel for 9,6 kbit/s user data (TCH/F9.6).
Half rate traffic channel for 4,8 kbit/s user data (TCH/H4.8).
Half rate traffic channel for 2,4 kbit/s user data (TCH/H2.4).
Exercises
112 (199)
3.3
Control channels
3.3.1
General
Control channels are intended to carry signaling or synchronization data. Three categories of control
channel are defined: broadcast, common and dedicated. Specific channels within these categories are
defined in the sections following.
3.3.2
Broadcast channels
3.3.2.1
Frequency correction channel (FCCH)
The frequency correction channel carries information for frequency correction of the mobile station. It is
required only for the operation of the radio sub-system.
3.3.2.2
Synchronization channel (SCH)
The synchronization channel carries information for frame synchronization of the mobile station and
identification of a base transceiver station. It is required only for the operation of the radio sub-system.
Specifically the synchronization channel shall contain two encoded parameters:
a)
Base transceiver station identity code (BSIC): 6 bits (before channel coding) consists of
3 bits of PLMN color code with range 0 to 7 and 3 bits of BS color code with range 0 to 7 as
defined in GSM 03.03.
b)
Reduced TDMA frame number (RFN): 19 bits (before channel coding) =

T1
T2
T3
(11 bits)
(5 bits)
(3 bits)
range 0 to 2047
range 0 to 25
range 0 to 4
= FN div ( 26 x 51)
= FN mod 26
= (T3 - 1) div 10
where
T3
(6 bits)
range 0 to 50 = FN mod 51
and
FN = TDMA frame number as defined in sub-clause 4.3.3.
GSM 04.06 and GSM 04.08 specify the precise bit ordering, GSM 05.03 the channel coding of the above
parameters and GSM 05.10 defines how the TDMA frame number can be calculated from T1, T2, and
T3.
3.3.2.3
Broadcast control channel (BCCH)
The broadcast control channel broadcasts general information on a base transceiver station per base
transceiver station basis. Of the many parameters contained in the BCCH, the use of the following
parameters, as defined in GSM 04.08 are referred to in sub-clause 6.5:
a)
CCCH_CONF which indicates the organization of the common control channels:

From this parameter, the number of common control channels (BS_CC_CHANS) and
whether or not CCCH or SDCCH are combined (BS_CCCH_SDCCH_COMB = true or false)
are derived as follows:
Exercises
113 (199)
CCCH_CONF
BS_CC_CHANS
000
001
010
100
110
1
1
2
3
4
BS_CCCH_SDCCH_COMB
false
true
false
false
false
b)
BS_AG_BLKS_RES which indicates the number of blocks on each common control channel
reserved for access grant messages:
3 bits (before channel coding) range 0 to 7.
c)
BS_PA_MFRMS which indicates the number of 51 TDMA frame multiframes between

transmission of paging messages to mobiles of the same paging group:
3 bits (before channel coding) range 2 to 9.
3.3.3
Common control type channels
3.3.3.1
Common control type channels, known when combined as a common control

channel (CCCH)
i)
Paging channel (PCH): Downlink only, used to page mobiles.
ii)
Random access channel (RACH): Uplink only, used to request allocation of a SDCCH.
iii)
Access grant channel (AGCH): Downlink only, used to allocate a SDCCH or directly a TCH.
iv)
Notification channel (NCH): Downlink only, used to notify mobile stations of voice group and
voice broadcast calls.
3.3.4
Dedicated control channels
3.3.4.1
Circuit switched dedicated control channels
i)
ii)
iii)
iv)
v)
vi)
vii)
viii)
ix)
Slow, TCH/F associated, control channel (SACCH/TF).

Fast, TCH/F associated, control channel (FACCH/F).
Slow, TCH/H associated, control channel (SACCH/TH).
Fast, TCH/H associated, control channel (FACCH/H).
Stand alone dedicated control channel (SDCCH/8).
Slow, SDCCH/8 associated, control channel (SACCH/C8)
Stand alone dedicated control channel, combined with CCCH (SDCCH/4).
Slow, SDCCH/4 associated, control channel (SACCH/C4).
slow, TCH/F associated, control channel for multislot configurations (SACCH/M).
All associated control channels have the same direction (bi-directional or unidirectional) as the
channels they are associated to. The unidirectional SACCH/MD is defined as the downlink part of
SACCH/M.
3.3.5
Cell Broadcast Channel (CBCH)
The CBCH, downlink only, is used to carry the short message service cell broadcast (SMSCB). The
CBCH uses the same physical channel as the SDCCH.
3.4
Combination of channels
Only certain combinations of channels are allowed as defined in GSM 04.03. Sub-clause 6.4 lists the
combinations in relation to basic physical channels.
Exercises
114 (199)
4
4.1
The physical resource

General
The physical resource available to the radio sub-system is an allocation of part of the radio spectrum.
This resource is partitioned both in frequency and time. Frequency is partitioned by radio frequency
channels (RFCHs) divided into bands as defined in GSM 05.05. Time is partitioned by timeslots and
TDMA frames as defined in sub-clause 4.3 of this ETS.
4.2
4.2.1
Radio frequency channels

Cell allocation and mobile allocation
GSM 05.05 defines radio frequency channels (RFCHs), and allocates numbers to all the radio frequency
channels available to the system. Each cell is allocated a subset of these channels, defined as the cell
allocation (CA). One radio frequency channel of the cell allocation shall be used to carry synchronization
information and the BCCH, this shall be known as BCCH carrier. The subset of the cell allocation,
allocated to a particular mobile, shall be known as the mobile allocation (MA).
4.2.2
Downlink and uplink
The downlink comprises radio frequency channels used in the base transceiver station to mobile station
direction.
The uplink comprises radio frequency channels used in the mobile station to base transceiver station
direction.
4.3
4.3.1
Timeslots and TDMA frames

General
A timeslot shall have a duration of 3/5 200 seconds ( 577 s). Eight timeslots shall form a TDMA frame
( 4,62 ms in duration).
At the base transceiver station the TDMA frames on all of the radio frequency channels in the downlink
shall be aligned. The same shall apply to the uplink (see GSM 05.10).
At the base transceiver station the start of a TDMA frame on the uplink is delayed by the fixed period of
3 timeslots from the start of the TDMA frame on the downlink (see figure 2).
At the mobile station this delay will be variable to allow adjustment for signal propagation delay. The
process of adjusting this advance is known as adaptive frame alignment and is detailed in GSM 05.10.
The staggering of TDMA frames used in the downlink and uplink is in order to allow the same timeslot
number to be used in the downlink and uplink whilst avoiding the requirement for the mobile station to
transmit and receive simultaneously. The period includes time for adaptive frame alignment, transceiver
tuning and receive/transmit switching (see figure 4).
4.3.2
Timeslot number
The timeslots within a TDMA frame shall be numbered from 0 to 7 and a particular timeslot shall be
referred to by its timeslot number (TN).
4.3.3
TDMA frame number
TDMA frames shall be numbered by a frame number (FN). The frame number shall be cyclic and shall
have a range of 0 to FN_MAX where FN_MAX = (26 x 51 x 2048) -1 = 2715647 as defined in GSM 05.10.
The frame number shall be incremented at the end of each TDMA frame.
Exercises
115 (199)
The complete cycle of TDMA frame numbers from 0 to FN_MAX is defined as a hyperframe. A
hyperframe consists of 2048 superframes where a superframe is defined as 26 x 51 TDMA frames. A
26 TDMA frame multiframe is used to support traffic and associated control channels and a 51 TDMA
frame multiframe is used to support broadcast, common control and stand alone dedicated control (and
their associated control) channels. Hence a superframe may be considered as 51 traffic/associated
control multiframes or 26 broadcast/common control multiframes.
The need for a hyperframe of a substantially longer period than a superframe arises from the
requirements of the encryption process which uses FN as an input parameter.
5
5.1
Physical channels
General
A physical channel uses a combination of frequency and time division multiplexing and is defined as a
sequence of radio frequency channels and timeslots. The complete definition of a particular physical
channel consists of a description in the frequency domain, and a description in the time domain.
The description in the frequency domain is addressed in sub-clause 5.4, the description in the time
domain is addressed in sub-clause 5.5.
5.2
5.2.1
Bursts
General
A burst is a period of R.F carrier which is modulated by a data stream. A burst therefore represents the
physical content of a timeslot.
5.2.2
Types of burst and burst timing
A timeslot is divided into 156,25 bit periods. A particular bit period within a timeslot is referenced by a bit
number (BN), with the first bit period being numbered 0, and the last (1/4) bit period being numbered 156.
In the sections following the transmission timing of a burst within a timeslot is defined in terms of bit
number. The bit with the lowest bit number is transmitted first.
Different types of burst exist in the system. One characteristic of a burst is its useful duration. This
document, in the sections following, defines four full bursts of 147 bits useful duration, and one short burst
of 87 bits useful duration. The useful part of a burst is defined as beginning from half way through bit
number 0. The definition of the useful part of a burst needs to be considered in conjunction with the
requirements placed on the phase and amplitude characteristics of a burst as specified in GSM 05.04 and
05.05.
The period between bursts appearing in successive timeslots is termed the guard period. Subclause 5.2.8 details constraints which relate to the guard period.
5.2.3
Normal burst (NB)

Bit Number
(BN)
0 - 2
3 - 60
61 - 86
87 - 144
145 - 147
(148 - 156
Length
of field
3
58
26
58
3
8,25
Contents
of field
tail bits
encrypted bits (e0 . e57)
training sequence bits
tail bits
guard period (bits)
Definition
(below)
05.03
(below)
05.03
(below)
subclause 5.2.8)
where the "tail bits" are defined as modulating bits with states as follows:
(BN0, BN1, BN2)
(BN145, BN146, BN147)
= (0, 0, 0)
= (0, 0, 0)
and
Exercises
116 (199)
-
where the "training sequence bits" are defined as modulating bits with states as given in the
following table according to the training sequence code, TSC. For broadcast and common control
channels, the TSC must be equal to the BCC, as defined in GSM 03.03 and as described in this
technical specification in sub-clause 3.3.2.
Training
Training sequence bits
Sequence
(BN61, BN62 .. BN86)
Code (TSC)
(0,0,1,0,0,1,0,1,1,1,0,0,0,0,1,0,0,0,1,0,0,1,0,1,1,1)
(0,0,1,0,1,1,0,1,1,1,0,1,1,1,1,0,0,0,1,0,1,1,0,1,1,1)
(0,1,0,0,0,0,1,1,1,0,1,1,1,0,1,0,0,1,0,0,0,0,1,1,1,0)
(0,1,0,0,0,1,1,1,1,0,1,1,0,1,0,0,0,1,0,0,0,1,1,1,1,0)
(0,0,0,1,1,0,1,0,1,1,1,0,0,1,0,0,0,0,0,1,1,0,1,0,1,1)
(0,1,0,0,1,1,1,0,1,0,1,1,0,0,0,0,0,1,0,0,1,1,1,0,1,0)
(1,0,1,0,0,1,1,1,1,1,0,1,1,0,0,0,1,0,1,0,0,1,1,1,1,1)
(1,1,1,0,1,1,1,1,0,0,0,1,0,0,1,0,1,1,1,0,1,1,1,1,0,0)
Under certain circumstances only half the encrypted bits present in a normal burst will contain complete
information. For downlink DTX operation on TCH-FS and TCH-HS, when a traffic frame (as defined in
GSM 06.31) is scheduled for transmission and one of its adjacent traffic frames is not scheduled for
transmission, the other half of the encrypted bits in the normal bursts associated with the scheduled traffic
frame shall contain partial SID information from any associated SID frame, with the appropriate stealing
flags BN60 or BN87 set to 0. In other cases the binary state of the remaining bits is not specified.
5.2.4
Frequency correction burst (FB)

Bit Number
length
Contents
(BN)
of field
of field
0 - 2
tail bits
(below)
3 - 144
142
fixed bits
(below)
tail bits
(below)
8,25
guard period (bits)
subclause 5.2.8)
145 - 147
(148 - 156
(BN0, BN1, BN2)
(BN145, BN146, BN147)
Definition
= (0, 0, 0)
= (0, 0, 0)
and
where the "fixed bits" are defined as modulating bits with states as follows:
(BN3, BN4 .. BN144)
= (0, 0 .. 0)
Exercises
117 (199)
NOTE:
5.2.5
This burst is equivalent to unmodulated carrier with a +1 625/24 kHz frequency offset,
above the nominal carrier frequency.
Synchronization burst (SB)

Bit Number
Length
Contents
(BN)
of field
of field
0 - 2
tail bits
(below)
3 - 41
39
05.03
42 - 105
64
extended training sequence bits
(below)
106 - 144
39
encrypted bits (e39 .. e77)
05.03
145 - 147
tail bits
(below)
8,25
guard period (bits)
subclause 5.2.8)
(148 - 156
(BN0, BN1, BN2)
(BN145, BN146, BN147)
(1, 0, 1, 1, 1, 0, 0, 1, 0, 1, 1, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 1, 0,
0, 0, 0, 0, 0, 1, 1, 1, 1, 0, 0, 1, 0, 1, 1, 0, 1, 0, 1, 0, 0, 0,
1, 0, 1, 0, 1, 1, 1, 0, 1, 1, 0, 0, 0, 0, 1, 1, 0, 1, 1)
Bit Number
Length
Contents
(BN)
of field
of field
0 - 2
tail bits
(below)
3 - 144
142
mixed bits
(below)
tail bits
(below)
8,25
guard period (bits)
subclause 5.2.8)
(148 - 156
Definition
(BN0, BN1, BN2)
(BN145, BN146, BN147)
and
Dummy burst
145 - 147
= (0, 0, 0)
= (0, 0, 0)
where the "extended training sequence bits" are defined as modulating bits with states as follows:
(BN42, BN43 .. BN105)
5.2.6
Definition
= (0, 0, 0)
= (0, 0, 0)
and
where the "mixed bits" are defined as modulating bits with states as follows:
Exercises
118 (199)
(BN3, BN4 .. BN144)
5.2.7
Bit Number
Length
Contents
(BN)
of field
of field
0 - 7
extended tail bits
(below)
8 - 48
41
synch. sequence bits
(below)
49 - 84
36
encrypted bits (e0..e35)
05.03
85 - 87
tail bits
(below)
68,25
extended guard period (bits)
sub-clause 5.2.8)
0,
0,
Definition
where the "extended tail bits" are defined as modulating bits with the following states:
(BN0, BN1, BN2 .. BN7)
1,
0,
0,
Access burst (AB)
(88 - 156
-
(1, 1, 1, 1, 1, 0, 1, 1, 0, 1, 1, 1, 0, 1, 1, 0, 0, 0, 0, 0, 1, 0,
0, 0, 1, 0, 0, 1, 1, 1, 0, 0, 0, 0, 0, 1, 0, 0, 1, 0, 0, 0, 1,
0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 0, 0, 0, 1, 1, 1, 0, 0, 0, 1, 0, 1, 1, 1,
0, 0, 1, 0, 1, 1, 1, 0, 0, 0, 1, 0, 1
0, 1, 1, 1, 0, 1, 0, 0, 1, 0, 1, 0, 0, 0, 1, 1, 0, 0, 1, 1, 0, 0, 1, 1, 1, 0,
1, 1, 1, 1, 0, 1, 0, 0, 1, 1, 1, 1, 1, 0, 0, 0, 1, 0, 0, 1, 0, 1, 1, 1, 1, 1,
1, 0, 1, 0)
= (0, 0, 1, 1, 1, 0, 1, 0)
where the "tail bits" are defined as modulating bits with the following states:
(BN85, BN86, BN87) = (0, 0, 0)
where the "sync. sequence bits" are defined as modulating bits with the following states:
(BN8, BN9 .. BN48)
5.2.8
(0, 1, 0, 0, 1, 0, 1, 1, 0, 1, 1, 1, 1, 1, 1, 1, 1, 0, 0, 1, 1, 0, 0,
1, 1, 0, 1, 0, 1, 0, 1, 0, 0, 0, 1, 1, 1, 1, 0, 0, 0)
Guard period
The guard period is provided because it is required for the MSs that transmission be attenuated for the
period between bursts with the necessary ramp up and down occurring during the guard periods as
defined in GSM 05.05. A base transceiver station is not required to have a capability to ramp down and
up between adjacent bursts, but is required to have a capability to ramp down and up for non-used
timeslots, as defined in GSM 05.05. In any case where the amplitude of transmission is ramped up and
down, then by applying an appropriate modulation bit stream interference to other RF channels can be
minimized.
5.3
Physical channels and bursts
The description of a physical channel will be made in terms of timeslots and TDMA frames and not in
terms of bursts. This is because there is not a one to one mapping between a particular physical channel,
and the use of a particular burst.
5.4
Radio frequency channel sequence
The radio frequency channel sequence is determined by a function that, in a given cell, with a given set of
general parameters, (see sub-clause 5.6.2), with a given timeslot number (TN), a given mobile radio
frequency channel allocation (MA) and a given mobile allocation index offset (MAIO), maps the TDMA
frame number (FN) to a radio frequency channel.
Exercises
119 (199)
In a given cell there is therefore, for a physical channel assigned to a particular mobile, a unique
correspondence between radio frequency channel and TDMA frame number.
The detailed hopping generation algorithm is given in sub-clause 6.2.
5.5
Timeslot and TDMA frame sequence
A given physical channel shall always use the same timeslot number in every TDMA frame. Therefore a
timeslot sequence is defined by:
i)
ii)
a timeslot number (TN); and

a TDMA frame number sequence.
The detailed definitions of TDMA frame number sequences are given in clause 7.
The physical channels where the TDMA frame number sequence is 0,1. . FN_MAX (where FN_MAX is
defined in sub-clause 4.3.3) are called "basic physical channels".
5.6
Parameters for channel definition and assignment
5.6.1
General
This section describes the set of parameters necessary to describe fully the mapping of any logical
channel onto a physical channel. These parameters may be divided into general parameters, that are
characteristic of a particular base transceiver station, and specific parameters, that are characteristic of a
given physical channel.
5.6.2
General parameters
These are:
i)
ii)
the set of radio frequency channels used in the cell (CA), together with the identification of
the BCCH carrier.
the TDMA frame number (FN), which can be derived from the reduced TDMA frame number
(RFN) which is in the form T1, T2, T3, see 3.3.2.
These parameters are broadcast (or derived from parameters broadcast) in the BCCH and SCH.
5.6.3
Specific parameters
These parameters define a particular physical channel in a base transceiver station. They are:
o)
i)
ii)
iii)
iv)
v)
vi)
the training sequence Code (TSC);

the timeslot number (TN);
the mobile radio frequency channel allocation (MA);
the mobile allocation index offset (MAIO);
the hopping sequence number (HSN);
the type of logical channel;
the sub-channel number (SCN).
The last two parameters allow the determination of the frame sequence.
6
6.1
Mapping of logical channels onto physical channels

General
The detailed mapping of logical channels onto physical channels is defined in the following sections.
Section 6.2 defines the mapping from TDMA frame number (FN) to radio frequency channel (RFCH).
Section 6.3 defines the mapping of the physical channel onto TDMA frame number. Sub-clause 6.4 lists
the permitted channel combinations and sub-clause 6.5 defines the operation of channels and channel
combinations.
Exercises
120 (199)
6.2
Mapping in frequency of logical channels onto physical channels
6.2.1
General
The parameters used in the function which maps TDMA frame number onto radio frequency channel are
defined in sub-clause 6.2.2. The definition of the actual mapping function, or as it is termed, hopping
sequence generation is given in sub-clause 6.2.3.
6.2.2
Parameters
The following parameters are required in the mapping from TDMA frame number to radio frequency
channel for a given assigned channel.
General parameters of the BTS, specific to one BTS, and broadcast in the BCCH and SCH:
i)
ii)
CA: Cell allocation of radio frequency channels.

FN: TDMA frame number, broadcast in the SCH, in form T1, T2, T3 (see sub-clause 3.3.2).
Specific parameters of the channel, defined in the channel assignment message:

i)
ii)
iii)
6.2.3
MA: Mobile allocation of radio frequency channels, defines the set of radio frequency
channels to be used in the mobiles hopping sequence. The MA contains N radio frequency
channels, where 1 N 64.
MAIO: Mobile allocation index offset.(0 to N-1, 6 bits).
HSN: Hopping sequence (generator) number (0 to 63, 6 bits).
Hopping sequence generation
For a given set of parameters, the index to an absolute radio frequency channel number (ARFCN) within
the mobile allocation (MAI from 0 to N-1, where MAI=0 represents the lowest absolute radio frequency
channel number (ARFCN) in the mobile allocation, ARFCN is in the range 0 to 7023 and the frequency
value can be determined according to GSM 05.05 sec 2 with n= ARFCN), is obtained with the following
algorithm:
if HSN = 0 (cyclic hopping) then:
MAI, integer (0 .. N-1) :
MAI = (FN + MAIO) modulo N
else:
M, integer (0 .. 152)
S, integer (0 .. N-1)
M = T2 + RNTABLE((HSN xor T1R) + T3)

:
M = M modulo (2 ^ NBIN)
T = T3 modulo (2 ^ NBIN)
if M < N then:
S = M
else:
S = (M+T) modulo N
MAI, integer (0 .. N-1) :
NOTE:
MAI = (S + MAIO) modulo N
Due to the procedure used by the mobile for measurement reporting when DTX is
used, the use of cyclic hopping where (N)mod 13 = 0 should be avoided.
where:
Exercises
121 (199)
T1R: time parameter T1, reduced modulo 64 (6 bits)
T3: time parameter, from 0 to 50 (6 bits)
T2: time parameter, from 0 to 25 (5 bits)
NBIN: number of bits required to represent N = INTEGER(log2(N)+1)
^: raised to the power of
xor: bit-wise exclusive or of 8 bit binary operands
RNTABLE: Table of 114 integer numbers, defined below:
Address
000...009:
010...019:
020...029:
030...039:
040...049:
050...059:
060...069:
070...079:
080...089:
090...099:
100...109:
110...113:
48,
0,
101,
80,
55,
87,
82,
77,
117,
16,
91,
125,
98,
64,
47,
34,
111,
19,
58,
108,
114,
49,
15,
99,
63,
25,
118,
127,
75,
3,
40,
122,
4,
7,
21,
17,
Contents
36,
76,
18,
6,
109,
110,
32,
60,
43,
119,
46,
1,
81,
85,
13,
38,
68,
107,
37,
90,
79,
24,
123,
95,
59,
56,
89,
71,
26,
5,
66,
52,
61,
39,
78,
124,
96,
57,
112,
33,
106,
121,
53,
22,
93,
102,
23,
86,
103,
29,
31,
92,
42,
113,
84,
105,
94,
104,
54,
12,
11,
8,
62,
51,
120,
9,
65,
73,
100,
2,
74,
88,
45,
67,
126,
72,
97,
70,
The hopping sequence generation algorithm is represented diagrammatically in figure 6.

6.2.4
Specific cases
On the RFCH carrying a BCCH (C0), frequency hopping is not permitted on any timeslot supporting a
BCCH according to table 3 of clause 7. A non-hopping radio frequency channel sequence is
characterized by a mobile allocation consisting of only one radio frequency channel, i.e. with N=1,
MAIO=0. In this instance sequence generation is unaffected by the value of the value HSN.
6.2.5
Change in the frequency allocation of a base transceiver station
The consequence of adding or removing a number of radio frequency channels in a base transceiver
station is a modification of the cell allocation (CA) and the mobile allocation (MA). In order to achieve this
without disruption to mobile stations with currently assigned channels it is necessary to send a message
to all mobiles with assigned channels. The message, as defined in 04.08, will contain a new cell allocation
(if necessary), mobile allocation and a time (in the form of a TDMA frame number) at which the change is
to occur. A new cell allocation may not be necessary if channels are only being removed, and not added.
6.3
6.3.1
6.3.1.1
Mapping in time of logical channels onto physical channels

Mapping in time of circuit switched logical channels onto physical channels
General
The mapping in time of circuit switched logical channels is defined in the tables of clause 7, which also
defines the relationship of the air interface frames to the multiframe.
6.3.1.2
Key to the mapping table of clause 7
The following relates to the tables of clause 7. The columns headed:
Exercises
122 (199)
i)
"Channel designation" gives the precise acronym for the channel to which the mapping
applies.
ii)
"Sub-channel number" identifies the particular sub-channel being defined where a basic
physical channel supports more than one channel of this type.
iii)
"Direction" defines whether the mapping given applies identically to downlink and uplink
(D&U), or to downlink (D) or uplink (U) only.
iv)
"Allowable timeslot assignments" defines whether the channel can be supported on, or
assigned to, any of the timeslots, or only on specific timeslots.
v)
"Allowable RF channel assignments" defines whether the channel can use any or all of the
radio frequency channels in the cell allocation (CA), or only the BCCH carrier (C0). It should
be noted that any allocated channel Cx within CA could be any radio frequency channel, and
that no ordering of radio frequency channel number is implied. For example, allocated
channel C0 need not have the lowest radio frequency channel number of the allocation.
vi)
"Burst type" defines which type of burst as defined in clause 5.2 is to be used for the physical
channel.
vii)
"Repeat length in TDMA frames" defines how many TDMA frames occur before the mapping
for the inter-leaved blocks repeats itself e.g. 51.
viii)
"Inter-leaved block TDMA frame mapping" defines, within the parentheses, the TDMA
frames used by each inter-leaved block (e.g. 0..3). The numbers given equate to theTDMA
frame number (FN) module the number of TDMA frames per repeat length; Therefore, the
frame is utilized when:
TDMA frame mapping number = (FN)mod repeat length given
Where there is more than one block shown, each block is given a separate designation e.g. B0, B1.
Where diagonal inter-leaving is employed then all of the TDMA frames included in the block are given,
and hence the same TDMA frame number can appear more than once (see GSM 05.03). It should be
noted that the frame mapping for the SACCH/T channel differs according to the timeslot allocated in order
to lower the peak processing requirements of the BSS.
6.3.1.3
Mapping of BCCH data
In order to facilitate the MS operation, it is necessary to transmit some System Information messages in
defined multiframes and defined blocks within one multiframe, as follows (where TC = (FN DIV 51) mod
(8)):
System Information Message
Type 1
Type 2
Type 2 bis
Type 2 ter
Type 3
Type 4
Type 7
Type 8
Type 9
Sent when TC =
0
1
5
5 or 4
2 and 6
3 and 7
7
3
4
Allocation
BCCH Norm
BCCH Norm
BCCH Norm
BCCH Norm
BCCH Norm
BCCH Norm
BCCH Ext
BCCH Ext
BCCH Norm
This sub-clause defines requirements on minimum scheduling: the network may send any System
Information message when sending of a specific System Information message is not required. The
following rules apply:
i)
BCCH Ext may share the resource with PCH and AGCH (see sub-clause 6.5.1).
Exercises
123 (199)
ii)
System Information Type 1 need only be sent if frequency hopping is in use or when the NCH is
present in a cell. If the MS finds another message when TC = 0, it can assume that System
Information Type 1 is not in use.
iii)
System information type 2 bis or 2 ter messages are sent if needed, as determined by the system
operator. If only one of them is needed, it is sent when TC = 5. If both are needed, 2bis is sent
when TC = 5 and 2 ter is sent at least once within any of 4 consecutive occurrences of TC = 4. A SI
2 messages will be sent at least every time TC = 1.
iv)
The definitions of BCCH Norm and BCCH Ext are given in clause 7 table 3 of 5.
v)
Use of System Information type 7 and 8 is not always necessary. It is necessary if System
Information type 4 does not contain all information needed for cell selection.
vi)
System Information type 9 is sent in those blocks with TC = 4 which are specified in system
information type 3 as defined in GSM 04.08.
All the allowable timeslot assignments in a frame (see table 3 of 5 in clause 7) shall contain the same
information.
6.3.1.4
Mapping of SID Frames
When the DTX mode of operation is active, it is required to transmit Silence Descriptor (SID) information,
or equivalent dummy information, during the SACCH/T block period (104 TDMA frames). As the SID
frames do not constitute a logical channel and their use is specific to DTX operation, the mapping of SID
frames onto the TDMA frames is specified in GSM 05.08.
6.4
Permitted channel combinations
6.4.1
Permitted channel combinations onto a basic physical channel
The following are the permitted ways, as defined by GSM 04.03, in which channels can be combined onto
basic physical channels (numbers appearing in parenthesis after channel designations indicate
sub-channel numbers; channels and sub-channels need not necessarily be assigned):
i)
ii)
iii)
iv)
v)
vi)
vii)
viii)
ix)
x)
TCH/F + FACCH/F + SACCH/TF

TCH/H(0,1) + FACCH/H(0,1) + SACCH/TH(0,1)
TCH/H(0,0) + FACCH/H(0,1) + SACCH/TH(0,1) + TCH/H(1,1)
FCCH + SCH + BCCH + CCCH
FCCH + SCH + BCCH + CCCH + SDCCH/4(0..3) + SACCH/C4(0..3)
BCCH + CCCH
SDCCH/8(0 .7) + SACCH/C8(0 . 7)
TCH/F + FACCH/F + SACCH/M
TCH/F + SACCH/M
TCH/FD + SACCH/MD
where CCCH = PCH + RACH + AGCH + NCH.
6.4.2
NOTE 1:
Where the SMSCB is supported, the CBCH replaces SDCCH number 2 in cases v)
and vii) above.
NOTE 2:
A combined CCCH/SDCCH allocation (case v) above) may only be used when no

other CCCH channel is allocated.
NOTE 3:
Combinations viii), ix) and x) are used in multislot configurations as defined in subclause 6.4.2.
Multislot configurations
A multislot configuration consists of multiple
Exercises
124 (199)
-
circuit
traffic channels together with associated control channels, allocated to the same MS. The multislot
configuration occupies up to 8 basic physical channels, with different timeslot numbers (TN) but with the
same frequency parameters (ARFCN or MA, MAIO and HSN) and the same training sequence (TSC).
6.4.2.1
Multislot configurations for circuit switched connections
Two types of multislot configurations exist, symmetric and asymmetric. The symmetric case consists of
only bi-directional channels. The asymmetric case consists of both bi-directional and unidirectional
downlink channels.
The occupied physical channels shall consist of the following channel combinations as defined in subclause 6.4.1.
one main channel of type viii) +
x secondary channels of type ix) +
y secondary channels of type x)
where
0<= x <= 7, y = 0
0<= x <= 6, 1 <= y <= 7, x+y <= 7
for symmetric multislot configuration

for asymmetric multislot configuration
The main channel is the bi-directional channel that carries the main signaling (FACCH and SACCH) for
the multislot configuration. The position of the main channel is indicated by the allocation message
(GSM 04.08). Secondary channels may be added or removed without changing the main channel.
The allocation of channels to a Multislot Configuration must always consider the multislot capability of the
MS, as defined by the multislot class described in annex B.
There is no limitation in this TS to the possible TCH types (see sub-clause 3.2) which may be used in a
Multislot Configuration.
High Speed Circuit Switched Data (HSCSD) is one case of multislot configuration. The full rate traffic
channels of a HSCSD configuration shall convey the same user bit rate (see sub-clause 3.2.3).
NOTE:
6.5
6.5.1
For the maximum number of timeslots to be used for a HSCSD, see GSM 03.34.
Operation of channels and channel combinations

General
i)
A base transceiver station must transmit a burst in every timeslot of every TDMA frame in the
downlink of radio frequency channel C0 of the cell allocation (to allow mobiles to make power
measurements of the radio frequency channels supporting the BCCH, see GSM 05.08). In order to
achieve this requirement a dummy burst is defined in sub-clause 5.2.6 which shall be transmitted
by the base transceiver station on all timeslots of all TDMA frames of radio frequency channel C0
for which no other channel requires a burst to be transmitted.
ii)
Timeslot number 0 of radio frequency channel C0 of the cell allocation must support either channel
combinations iv) or v) in sub-clause 6.4.1. No other timeslot or allocated channel from the cell
allocation is allowed to support channel combinations iv) or v) in sub-clause 6.4.1.
iii)
The parameter BS_CC_CHANS in the BCCH defines the number of basic physical channels
supporting common control channels (CCCHs). All shall use timeslots on radio frequency channel
C0 of the cell allocation. The first CCCH shall use timeslot number 0, the second timeslot number
2, the third timeslot number 4 and the fourth timeslot number 6. Each CCCH carries its own
CCCH_GROUP of mobiles in idle mode. Mobiles in a specific CCCH_GROUP will listen for paging
messages and make random accesses only on the specific CCCH to which the CCCH_GROUP
belongs. The method by which a mobile determines the CCCH_GROUP to which it belongs is
defined in sub-clause 6.5.2.
Exercises
125 (199)
iv)
The parameter BS_CCCH_SDCCH_COMB in the BCCH (see sub-clause 3.3.2) defines whether
the common control channels defined are combined with SDCCH/4(0.3) + SACCH/C4(0.3) onto the
same basic physical channel. If they are combined then the number of available random access
channel blocks (access grant channel blocks and paging channel blocks; see following), are
reduced as defined in table 5 of clause 7.
v)
The PCH, AGCH, NCH and BCCH Ext may share the same TDMA frame mapping (considered
modulo 51) when combined onto a basic physical channel. The channels are shared on a block by
block basis, and information within each block, when de-interleaved and decoded allows a mobile
to determine whether the block contains paging messages, system information messages or
access grants. However, to ensure a mobile satisfactory access to the system a variable number of
the available blocks in each 51 multiframe can be reserved for access grants and system
information messages, only. The number of blocks not used for paging (BS_AG_BLKS_RES)
starting from, and including block number 0 is broadcast in the BCCH (see sub-clause 3.3.2). As
above the number of paging blocks per 51 TDMA frame multiframe considered to be "available"
shall be reduced by the number of blocks reserved for access grant messages.
If system information messages are sent on BCCH Ext, BS_AG_BLKS_RES shall be set to a value
greater than zero.
Table 5 of clause 7 defines the access grant blocks and paging blocks available per 51 TDMA
frame multiframe.
vi)
Another parameter in the BCCH, BS_PA_MFRMS indicates the number of 51 TDMA frame
multiframes between transmissions of paging messages to mobiles in idle mode of the same
paging group. The "available" paging blocks per CCCH are then those "available" per 51 TDMA
frame multiframe on that CCCH (determined by the two above parameters) multiplied by
BS_PA_MFRMS. Mobiles are normally only required to monitor every Nth block of their paging
channel, where N equals the number of "available" blocks in total (determined by the above BCCH
parameters) on the paging channel of the specific CCCH which their CCCH_GROUP is required to
monitor. Other paging modes (e.g. page reorganize or paging overload conditions described in
GSM 04.08) may require the mobile to monitor paging blocks more frequently than this. All the
mobiles listening to a particular paging block are defined as being in the same PAGING_GROUP.
The method by which a particular mobile determines to which particular PAGING_GROUP it
belongs and hence which particular block of the available blocks on the paging channel is to be
monitored is defined in sub-clause 6.5.2.
vii)
An MS which has its membership of at least one voice group or voice broadcast call group set to
the active state shall, in addition monitor the paging blocks as described above, monitor the
notification channel, NCH. This logical channel is always mapped onto contiguous blocks reserved
for access grants, in a position and number as given by the parameter NCP, defined in GSM 04.08,
broadcast on the BCCH. The channel may be present when a cell supports voice group or voice
broadcast calls. The coding of the various structural parameters described above in this section is
not changed. Information within a block, when de-inter-leaved and decoded, allows the MS to
determine whether the block contains access grant messages or notification messages.
6.5.2
Determination of CCCH_GROUP and PAGING_GROUP for MS in idle mode

CCCH_GROUP (0 .. BS_CC_CHANS-1) = ((IMSI mod 1000) mod (BS_CC_CHANS x N)) div N
PAGING_GROUP (0 .. N-1) = ((IMSI mod 1000) mod (BS_CC_CHANS x N)) mod N
where
N = number of paging blocks "available" on one CCCH = (number of paging blocks
"available" in a 51 frame TDMA multiframe on one CCCH) x BS_PA_MFRMS.
IMSI = International Mobile Subscriber Identity, as defined in GSM 03.03.
mod = Modulo.
div = Integer division.
Exercises
126 (199)
6.5.3
Determination of specific paging multiframe and paging block index
The required 51 TDMA frame multiframe occurs when:

PAGING_GROUP div (N div BS_PA_MFRMS) = (FN div 51) mod (BS_PA_MFRMS)
The index to the required paging block of the "available" blocks in the 51 TDMA frame multiframe:
Paging block index = PAGING_GROUP mod (N div BS_PA_MFRMS)
where the index is then used with the look-up table 5 of clause 7 to determine the actual paging channel
inter-leaved block to be monitored.
6.5.4
Short Message Service Cell Broadcast (SMSCB)
When a short message service cell broadcast (SMSCB) message is to be sent, the message shall be
sent on one of the two cell broadcast channels (CBCH): the basic and the extended cell broadcast
channel in four consecutive multiframes using the block defined in table 3 of clause 7. The multiframes
used for the basic cell broadcast channel shall be those in which TB = 0,1,2 and 3. The multiframes used
for the extended cell broadcast channel shall be those in which TB = 4, 5, 6 and 7 where:
TB = (FN DIV 51)mod(8)
The SMSCB header shall be sent in the multiframe in which TB = 0 for the basic, and TB = 4 for the
extended cell broadcast channel. When SMSCB is in use, this is indicated within the BCCH data (see
GSM 04.08), and the parameter BS_AG_BLKS_RES shall be set to one or greater. When the CBCH is
mapped onto a CCCH+SDCCH/4 channel, use of SMSCB does not place any constraint on the value of
BS_AG_BLKS_RES.
NOTE:
6.5.5
The MS reading of the extended CBCH is occasionally interrupted by MS idle mode

procedures.
Voice group and voice broadcast call notifications
When mobile stations are to be alerted on a voice group or voice broadcast call, notification messages
shall be sent on the notification channel (NCH), using the blocks defined in sub-clause 6.5.1.
When the NCH is in use, the parameter BS_AG_BLKS_RES shall be set to a value not lower than the
number of blocks used for the NCH, see sub-clause 6.5.1 vii).
Exercises
127 (199)
Channel
designation
Sub-channel
number
TCH/FS
TCH/F2.4
TCH/HS
0
1
FACCH/F
FACCH/H
FACCH/H
FACCH/H
FACCH/H
0
0
1
1
SACCH/TF
SACCH/TF
SACCH/TF
SACCH/TF
SACCH/TF
SACCH/TF
SACCH/TF
SACCH/TF
SACCH/M
SACCH/TH
Direction
Allowable timeslot
assignments
Allowable RF channel
assignments
NB1
13
B0(0...7),B1(4...11),B2(8...11,0...3)
D&U2
0 ... 7
C0 ... Cn
NB1
13
B0(0,2,4,6),B1(4,6,8,10),B2(8,10,0,2)
B0(1,3,5,7),B1(5,7,9,11),B2(9,11,1,3)
D&U
0 ... 7
C0 ... Cn
NB1
13
B0(0...7),B1(4...11),B2(8...11,0...3)
U
D
U
D
0 ... 7
0 ... 7
0 ... 7
0 ... 7
C0 ... Cn
C0 ... Cn
C0 ... Cn
C0 ... Cn
NB1
NB1
NB1
NB1
26
26
26
26
B0(0,2,4,6,8,10),B1(8,10,13,15,17,19),B2(17,19,21,23,0,2)
B0(4,6,8,10,13,15),B1(13,15,17,19,21,23),B2(21,23,0,2,4,6)
B0(1,3,5,7,9,11),B1(9,11,14,16,18,20),B2(18,20,22,24,1,3)
B0(5,7,9,11,14,16),B1(14,16,18,20,22,24),B2(22,24,1,3,5,7)
D&U2
D&U2
D&U2
D&U2
D&U2
D&U2
D&U2
D&U2
D&U2
0
1
2
3
4
5
6
7
C0 ... Cn
C0 ... Cn
C0 ... Cn
C0 ... Cn
C0 ... Cn
C0 ... Cn
C0 ... Cn
C0 ... Cn
104
104
104
104
104
104
104
104
B(12, 38, 64, 90)

B(25, 51, 77, 103)
B(38, 64, 90, 12)
B(51, 77, 103, 25)
B(64, 90, 12, 38)
B(77, 103, 25, 51)
B(90, 12, 38, 64)
B(103, 25, 51, 77)
0 ... 7
C0 ... Cn
NB3
NB3
NB3
NB3
NB3
NB3
NB3
NB3
NB3
104
B(12, 38, 64, 90)
D&U2
C0 ... Cn
NB3
104
D&U2
C0 ... Cn
NB3
104
D&U2
C0 ... Cn
NB3
104
D&U2
C0 ... Cn
NB3
104
D&U2
C0 ... Cn
NB3
104
D&U2
C0 ... Cn
NB3
104
D&U2
C0 ... Cn
NB3
104
D&U2
C0 ... Cn
NB3
104
B(12, 38, 64, 90)

B(25, 51, 77, 103)
B(12, 38, 64, 90)
B(25, 51, 77, 103)
B(38, 64, 90, 12)
B(51, 77, 103, 25)
B(38, 64, 90, 12)
B(51, 77, 103, 25)
B(64, 90, 12, 38)
B(77, 103, 25, 51)
B(64, 90, 12, 38)
B(77, 103, 25, 51)
B(90, 12, 38, 64)
B(103, 25, 51, 77)
B(90, 12, 38, 64)
B(103, 25, 51, 77)
An Access Burst (AB) may be used on the uplink during handover.
SACCH/TH
SACCH/TH
SACCH/TH
block
C0 ... Cn
NOTE 3:
SACCH/TH
Interleaved
TDMA frame mapping
0 ... 7
SACCH/TH
SACCH/TH
Repeat length
in TDMA frames
D&U2
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
SACCH/TH
Burst
type
NOTE 1:
An Access Burst (AB) is used
on the uplink during handover
and on channels used for voice
group calls when a request to
talk is made.
NOTE 2:
The uplink of a channel
used for voice broadcast
or a voice group call may
actually not be used.
Clause 7 Table 1 of 6: Mapping of logical channels onto physical channels (see sub-clauses 6.3, 6.4, 6.5)
Exercises
128 (199)
Channel
designation
Subchannel
number
Direction
TCH/F4.8
TCH/F9.6
TCH/F14.4
TCH/H2.4
TCH/H4.8
Allowable
timeslot
assignments
Allowable
RF channel
assignments
Burst
type
D&U
0 ... 7
C0 ... Cn
NB1
26
B0(0
...
11,
13
...
B1(4
...
11,
13
...
24,
0,
B2(8
...
11,
13
...
24,
0
...
B3(13
...
24,
0
...
B4(17
...
24,
0
...
11,
13,
B5(21 ... 24, 0 ... 11, 13 ... 18)
D&U
0 ... 7
C0 ... Cn
NB1
26
B0(0,2,4,6,8,10,13,15,17,19,21,
23,0,2,4,6,8,10,13,15,17,19)
B1(8,10,13,15,17,19,21,23,0,2,4,
6,8,10,13,15,17,19,21,23,0,2),
B2(17,19,21,23,0,2,4,6,8,10,13,
15,17,19,21,23,0,2,4,6,8,10)
NOTE:
Repeat
Interleaved
length in
TDMA
TDMA frames mapping
block
frame
22)
1)
5)
9)
14)
B0(1,3,5,7,9,11,14,16,18,20,22,
24,1,3,5,7,9,11,14,16,18,20),
B1(9,11,14,16,18,20,22,24,1,3,5,
7,9,11,14,16,18,20,22,24,1,3),
B2(18,20,22,24,1,3,5,7,9,11,14,
16,18,20,22,24,1,3,5,7,9,11)
An Access Burst (AB) is used on the uplink during handover.

Exercises
129 (199)
Channel
designation
Subchannel
number
Direction
Allowable
timeslot
assignments
Allowable
RF channel
assignments
Burst
type
Repeat
length in
TDMA frames
Interleaved
TDMA
mapping
block
frame
FCCH
C0
FB
51
B0(0),B1(10),B2(20),B3(30),B4(40)
SCH
C0
SB
51
B0(1),B1(11),B2(21),B3(31),B4(41)
BCCH Norm
0,2,4,6
C0
NB
51
B(2..5)
BCCH Ext
0,2,4,6
C0
NB
51
B(6...9)
PCH
AGCH
0,2,4,6
C0
NB
51
B0(6..9),B1(12..15),B2(16..19)
B3(22..25),B4(26..29),B5(32..35),
B6(36..39),B7(42..45),B8(46..49)
NCH
C0
NB
51
B0(6..9),B1(12..15),B2(16..19)
B3(22..25),B4(26..29),B5(32..35),
B6(36..39)
RACH
0,2,4,6
C0
AB
51
B0(0),B1(1)..B50(50)
CBCH(SDCCH/4)
C0
NB
51
B(32..35)
CBCH(SDCCH/8)
0 ... 3
C0 ... Cn
NB
51
B(8..11)
D
U
D
U
D
U
D
U
C0
NB1
51
B(22..25)
B(37..40)
B(26..29)
B(41..44)
B(32..35)
B(47..50)
B(36..39)
B(0..3)
D
U
D
U
D
U
D
U
C0
NB3
102
B(42..45)
B(57..60)
B(46..49)
B(61..64)
B(93..96)
B(6..9)
B(97..100)
B(10..13)
SDCCH/4
0
1
2
3
SACCH/C4
0
1
2
3
NOTE 1:
An Access Burst (AB) is used
On the uplink during handover
NOTE 3:An Access Burst (AB) may be used on the uplink during handover.
Exercises
130 (199)
Channel
designation
SDCCH/8
Subchannel
number
Direction
0
1
2
3
4
5
6
7
SACCH/C8
0
1
2
3
4
5
6
7
Allowable
timeslot
assignments
Allowable
RF channel
assignments
D
U
D
U
D
U
D
U
D
U
D
U
D
U
D
U
0 ... 7
C0 ... Cn
NB1
51
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B (43 ... 46)
(0
(15
(4
(19
(8
(23
(12
(27
(16
(31
(20
(35
(24
(39
(28
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
3)
18)
7)
22)
11)
26)
15)
30)
19)
34)
23)
38)
27)
42)
31)
D
U
D
U
D
U
D
U
D
U
D
U
D
U
D
U
0 ... 7
C0 ... Cn
NB3
102
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B (8 ... 11)
(32
(47
(36
(51
(40
(55
(44
(59
(83
(98
(87
(0
(91
(4
(95
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
35)
50)
39)
54)
43)
58)
47)
62)
86)
101)
90)
3)
94)
7)
98)
NOTE 1:
An Access Burst (AB) is used on the uplink during handover.
NOTE 3:
An Access Burst (AB) may be used on the uplink during handover.
Burst
type
Repeat
Interleaved
length in
TDMA
TDMA frames mapping
block
frame
Exercises
131 (199)
BS_CCCH_SDCCH_COMB
Random access channel blocks available

Access grant blocks available (NOTE: Some access grant blocks may also be used for the NCH)
BS_AG_BLKS_RES
Number of paging blocks available per 51 multiframe
Paging channel blocks available
(Paging block index = 0, 1, 2, 3, 4, 5, 6, 7, 8)
False
B0, B1, B2, B3, B4, B5, B6, B7, B8
False
B1, B2, B3, B4, B5, B6, B7, B8
False
B2, B3, B4, B5, B6, B7, B8
False
B3, B4, B5, B6, B7, B8
False
B4, B5, B6, B7, B8
False
B5, B6, B7, B8
False
B6, B7, B8
False
B7, B8
B0, B1, B2
True
B1, B2
True
B2
True
B0, B1 ... B50
B0, B1 ... B8
B4, B5, B14, B15 ... B36, B45, B46
B0, B1, B2
Exercises
132 (199)
Interleaved block TDMA frame mapping
Multiframe
length in
TDMA frames
52
B0(0...3), B1(4...7), B2(8...11), B3(13...16), B4(17...20), B5(21..24),
B6(26...29), B7(30...33), B8(34...37), B9(39...42), B10(43...46),
B11(47...50)
C0...Cn
NB
52
B0(0... 3), B6(26...29), B3(13...16), B9(39...42)
C0...Cn
NB
51
B0(2... 5)
C0...Cn
AB
52
B0(0)...B11(11), B12(13)...B23(24),
B24(26)... B35(37), B36(39)...B47(50)
C0...Cn
NB
52
B1(4 ... 7), B2(8...11), B3(13...16), B4(17...20), B5(21..24),
B6(26...29), B7(30...33), B8(34...37), B9(39...42), B10(43...46),
B11(47...50)
C0...Cn
NB
51
B0(6..9), B1(12..15), B2(16..19), B3(22..25), B4(26..29),
B5(32..35), B6(36..39), B7(42..45), B8(46..49) B6(36..39),
B7(42..45), B8(46..49)
C0...Cn
NB
416
B0(12,38,64,90), B2(116,142,168,194), B3(220,246,272,298),
B4(324,350,376,402)
C0...Cn
AB
416
B0(12)
B0(38)
B0(64)
B0(90)
B0(116)
B0(142)
B0(168)
B0(194)
B0(220)
B0(246)
B0(272)
B0(298)
B0(324)
B0(350)
B0(376)
B0(402)
Clause 7 Table 6 of 6: Inter-leaved block TDMA frame mapping
PDTCH,
PACCH
D&U
Time-slot
Allowable Allowa
ble
assignment RF channel
type
assignment
0...7
C0...Cn
NB1
PBCCH
PBCCH
PRACH
D
D
U
0...7
0...7
0...7
PAGCH, PPCH,
PNCH
0...7
PAGCH, PPCH,
PNCH
0...7
PTCCH/D
0...7
0...7
Channel
designation
PTCCH/U
Subchannel
number
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Direction
Exercises
133 (199)
LAND
U
S
E
R
C
H
A
N
N
E
L
S
C
O
N
T
R
O
L
E
N
T
I
T
I
E
S
NETWORK
MOBILE
(Air interface)
PHYSICAL
CHANNELS
LOGICAL
CHANNELS
Traffic
= TCH (Bm or Lm)
Control and
Signalling
= CCH (Dm)
M
A
P
P
I
N
G
PHYSICAL
RESOURCE
( Timslot
number,
TDMA frame
sequence
RF Channel
sequence )
PHYSICAL
CHANNELS
( Timslot
number,
Frequency
(RF Channels)
Time
(Timeslots)
TDMA frame
sequence
RF Channel
sequence )
LOGICAL
CHANNELS
M
A
P
P
Traffic
I = TCH (Bm or Lm)
N
G
Control and
Signalling
= CCH (Dm)
C
O
N
T
R
O
L
E
N
T
I
T
I
E
S
U
S
E
R
C
H
A
N
N
E
L
S
Figure 1: Mapping of logical channels onto physical channels based on the physical resource
Exercises
134 (199)
TDMA frame number

0
Downlink
(BTS -> MS)
R
F
Delay
Timeslot number
Uplink
(MS -> BTS)
c
h
a
n
n
e
l
s
TDMA frame number
Figure 2: The structure imposed on the physical resource: Timeslots, TDMA Frames and Radio Frequency channels
(in this example the cell has an allocation of 4 RF Channels pairs
Exercises
135 (199)
t io
e n na
lly
In
t
GSM 08.58 version 5.9.0 Release 1996: July 1999
Bl n
a
Exercises
136 (199)
Draft prETS 300 912 (GSM 05.10 Version 5.2.1 Release 1996): April 1999
Timing of transmitted signals

The timing of signals transmitted by the MS and BTS are defined in
GSM 05.02.
The MS can use the timing of receipt of the synchronization burst to set up its
timebase counters as follows:
QN
TN
is set by the timing of the training sequence;

=
0 when the synch burst is received;
FN
=
51 ((T3-T2) mod (26)) + T3 + 51 x 26 x T1 when
the synch burst is received,
(where T3 = (10 x T3) +
1, T1, T2 and T3 being contained in information fields in
synchronization burst).
Thereafter, the timebase counters are incremented as in sub-clause 3.2.

(When adjacent BTSs are being monitored for handover purposes, or for cell
re-selection purposes in group receive mode, the MS may choose to store the
values of QN, TN and FN for all the BTSs whose synchronization bursts have
been detected relative to QN, TN and FN for its current serving BTS).
Exercises
137 (199)
t io
e n na
lly
In
t
Draft prETS 300 912 (GSM 05.10 Version 5.2.1 Release 1996): April 1999
Bl n
a
Exercises
138 (199)
Message formats and contents
This clause defines the format and contents of the messages sent over the A-bis interface. Similar coding principles
as in recs. 04.08 and 08.08 are used.
For each message, the contained Information Elements are listed. For each Information Element, the following
information is given:
-
Name of Information Element;
Reference section for the coding of the Information Element;
Presence condition for the Information Element;

M
Mandatory, must always be present;
receiver: if not present, consider message erroneous;
C
Conditional, presence depending on e.g.
a)
value of other element;
b)
presence of optional element;
receiver: if not present when condition met, consider
message erroneous, else accept message;
O
Optional,
receiver: present or not, accept message;
Format of Information Element:

T
Type only, fixed length, only Element Identifier;
V
Value only, fixed length, no Element Identifier included;
TV
Type and Value, fixed length, Element Identifier included;
TLV Type, Length and Value, variable length, Element Identifier and Length Indicator included;
Total length of Information Element; for variable length, lower and upper limits.
NOTE:
Maximum message length is determined by the N201 parameter of GSM 08.56.
In a message, the message discriminator is transmitted first. The purpose is to distinguish between transparent
messages (T-bit set to 1) and non-transparent messages (T-bit set to 0) and also between messages related to
Radio Link Layer Management, Dedicated Channel Management, Common Channel Management and TRX
Management. The octets are sent in the order shown in the description of the messages and information elements.
8.1
Transparent messages
Transparent messages are used at the A-bis interface to convey layer 3 messages for the radio interface as
defined in GSM 04.08 and for which BTS has to take or has taken no specific action. The T- bit of the Message
Discriminator is set to 1.
In the uplink direction (messages from MS), all messages received in I- frames and all messages received in UIframes except for the MEASurement REPort message are considered as transparent. They are forwarded to BSC
as DATA INDication and UNIT DATA INDication messages respectively.
In the downlink direction (messages to MS) all messages as defined in GSM 04.08 are transparent except for the
following messages, which are replaced by BSC-BTS specific messages over the A- bis interface and where BTS
will send the corresponding L3 message over the radio interface after the necessary actions have been taken:
Exercises
139 (199)

Message to MS
Replaced on A-bis interface by
CIPHering MODe CoMmanD
ENCRyption CoMmanD
PAGing REQuest
PAGing CoMmanD
NOTIFication
NOTIFication CoMmanD
SYSTEM INFOrmation
BCCH INFOrmation and SACCH FILLing
EXTENDED MEASUREMENT ORDER
SACCH FILLing $(MAFA)$
Immediate assign (3 types)
IMMEDIATE ASSIGN COMMAND
Transparent messages are sent by BSC as DATA REQuest or UNIT DATA REQuest messages.
8.2
Non-transparent messages (BSC-BTS specific messages)
These messages are used over the A-bis interface for messages on which BTS has to take some action (BSC to
BTS direction) and for messages which are the result from actions taken by BTS (BTS to BSC direction). The T-bit
of the Message Discriminator is set to 0.
8.3
Radio link layer management messages
These messages are related to Radio Link Layer Management procedures. They all have the following general
format:
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+
0HVVDJHGLVFULPLQDWRU

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU

0

0

0

0
9

9

79

79

,QIRUPDWLRQHOHPHQWV

GHSHQGLQJRQPHVVDJH
W\SH
The messages concerned are the following:
Message name
DATA REQuest
DATA INDication
ERROR INDication
ESTablish REQuest
ESTablish CONFirm
ESTablish INDication
RELease REQuest
RELease CONFirm
RELease INDication
UNIT DATA REQuest
UNIT DATA INDication
Reference section
8.3.1
8.3.2
8.3.3
8.3.4
8.3.5
8.3.6
8.3.7
8.3.8
8.3.9
8.3.10
8.3.11
Exercises
140 (199)

8.3.1
DATA REQUEST
This message is sent from BSC to BTS to request the sending of a message in acknowledged mode on a radio link
layer connection.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU

/,QIRUPDWLRQ
8.3.2

0

0

0

0

0
9

9

79

79

7/9

!
DATA INDICATION
This message is sent from BTS to BSC to indicate the reception of a message in acknowledged mode on a radio
link layer connection.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU

/,QIRUPDWLRQ
8.3.3

0

0

0

0

0
9

9

79

79

7/9

!
ERROR INDICATION
This message is sent from BTS to BSC to indicate an abnormal case for a radio link layer connection.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU

5/0&DXVH
8.3.4

0

0

0

0

0
9

9

79

79

7/9

ESTABLISH REQUEST
This message is sent from BSC to BTS to request the establishment of a multi-frame mode (acknowledged mode)
link layer connection on the radio path.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU

Exercises
0

0

0

0
9

9

79

79

141 (199)

8.3.5
ESTABLISH CONFIRM
This message is sent from BTS to BSC to confirm the establishment of a radio link layer connection in multi-frame
(acknowledged) mode.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU
8.3.6

0

0

0

0
9

9

79

79

ESTABLISH INDICATION
This message is sent from BTS to BSC to indicate the establishment of a radio link layer connection in multi-frame
mode, initiated by an MS.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU

/,QIRUPDWLRQ
8.3.7

0

0

0

0

2
9

9

79

79

7/9

1)
The L3 Information field is present only if the SABM frame contained a non-empty information
field.
NOTE:
The "establish mode" parameter appearing in GSM 04.06 is used only on the MS side.
RELEASE REQUEST
This message is sent from BSC to BTS to request the release of multiframe mode of a radio link layer connection.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU

5HOHDVH0RGH

Exercises
0

0

0

0

0
9

9

79

79

79

142 (199)

8.3.8
RELEASE CONFIRM
This message is sent from BTS to BSC to confirm the release of multiframe mode of a radio link layer connection.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU
8.3.9

0

0

0

0
9

9

79

79

RELEASE INDICATION
This message is sent from BTS to BSC to indicate the release of a radio link layer connection (initiated by MS).
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU
8.3.10

0

0

0

0
9

9

79

79

UNIT DATA REQUEST
This message is sent from BSC to BTS to request the sending of a message in unacknowledged mode on a radio
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU

/,QIRUPDWLRQ
8.3.11

0

0

0

0

0
9

9

79

79

7/9

UNIT DATA INDICATION
This message is sent from BTS to BSC to indicate the reception of a message in unacknowledged mode on a radio
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

/LQN,GHQWLILHU

/,QIRUPDWLRQ

Exercises
0

0

0

0

0
9

9

79

79

7/9

143 (199)

8.4
DEDICATED CHANNEL MANAGEMENT MESSAGES
These messages are related to Dedicated Channel Management procedures. They all have the following general
format:
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

,QIRUPDWLRQHOHPHQWV
GHSHQGLQJRQPHVVDJH
W\SH

0

0

0

9

9

79


Message name
CHANnel ACTIVation
CHANnel ACTIVation ACKnowledge
CHANnel ACTIVation Negative ACK
CONNection FAILure INDication
DEACTIVATE SACCH
ENCRyption CoMmanD
HANDOver DETection
TALKER DETection
LISTENER DETection
MEASurement RESult
MODE MODIFY REQuest
MODE MODIFY ACKnowledge
MODE MODIFY Negative ACKnowledge
PHYsical CONTEXT REQuest
PHYsical CONTEXT CONFirm
RF CHANnel RELease
MS POWER CONTROL
BS POWER CONTROL
PREPROCecc CONFIGure
PREPROCessed MEASurement RESult
RF CHANnel RELease ACKnowledge
SACCH INFO MODIFY
Reference section
8.4.1
8.4.2
8.4.3
8.4.4
8.4.5
8.4.6
8.4.7
8.4.21
8.4.22
8.4.8
8.4.9
8.4.10
8.4.11
8.4.12
8.4.13
8.4.14
8.4.15
8.4.16
8.4.17
8.4.18
8.4.19
8.4.20
Exercises
144 (199)

8.4.1
CHANNEL ACTIVATION
This message is sent from BSC to BTS in order to activate a radio channel. The attributes of the channel are
defined in the message.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

$FWLYDWLRQ7\SH

&KDQQHO0RGH

&KDQQHO,GHQWLILFDWLRQ

(QFU\SWLRQLQIRUPDWLRQ

+DQGRYHU5HIHUHQFH

%63RZHU

063RZHU

7LPLQJ$GYDQFH

%63RZHU3DUDPHWHUV

063RZHU3DUDPHWHUV

3K\VLFDO&RQWH[W

6$&&+,QIRUPDWLRQ

8,&

0DLQFKDQQHOUHIHUHQFH

0

0

0

0

0

2

2

&

2

2

&

2

2

2

2

2

2
9

9

79

79

7/9

7/9

7/9

79

79

79

79

7/9

7/9

7/9

7/9

7/9

79

!

!

!

!

!

1)
The Encryption Information element is only included if ciphering is to be applied.
2)
The Handover Reference element is only included if activation type is handover.
3)
If BS Power, MS Power and/or Timing Advance elements are present, they are to be used to set
the initial transmission power and the initial L1-header.
4)
The Timing Advance element must be included if activation type is intra cell channel change.
5)
The BS and MS Power Parameters elements are included to indicate that BS and/or MS power
control is to be performed by BTS. The maximum power to be used is indicated in the BS and
MS Power elements respectively.
6)
Optional element for additional physical channel information.
7)
Included if compatibility with phase1 is required.
8)
Optional element for setting the SACCH filling information individually for this channel. If this
element is present, the SACCH filling information as given by this element shall be used for this
channel (replacing any SACCH filling information as given by the SACCH FILLING message(s))
until the channel is released or the information is changed by a SACCH INFO MODIFY
message. (If this element is not present, the SACCH filling as given by the SACCH FILLING
message(s) shall be used.)
9)
The UIC element may be included for voice group calls. It is used in the same way as the BSIC
for decoding the random access bursts when decoding uplink access bursts. If not included, the
BSIC shall be used for decoding uplink access bursts.
Exercises
145 (199)

10)
8.4.2
Optional element for multislot operation, it may be used in case of power control in the BTS.
CHANNEL ACTIVATION ACKNOWLEDGE
This message is sent from BSC to BTS to acknowledge that the requested channel activation has been completed
correctly.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

)UDPHQXPEHU

0

0

0

0
9

9

79

79

The Frame Number element is used by BSC to calculate the Starting Time parameter when required.
8.4.3
CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE
This message is sent from BTS to BSC to indicate that the channel activation could not be performed as requested.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

&DXVH

0

0

0

0
9

9

79

7/9

!
If the Channel Activation message was received with an erroneous Channel number information element, the
Channel Activation Negative Acknowledge message is returned with the Channel Number information element
equal to the received (and erroneous) Channel number and the Cause value "Mandatory Information Element
Error" with Diagnostics equal to the Channel number element identifier value.
8.4.4
CONNECTION FAILURE INDICATION
This message is sent from BTS to BSC to indicate that an active connection has been broken for some reason.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

&DXVH
8.4.5

0

0

0

0
9

9

79

7/9

!
DEACTIVATE SACCH
This message is sent from BSC to BTS in order to deactivate the SACCH of an active channel.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

Exercises
0

0

0
9

9

79

146 (199)

8.4.6
ENCRYPTION COMMAND
This message is sent from BSC to BTS to start ciphering mode operation.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU


/LQN,GHQWLILHU

/,QIR&,3+02'&0'

0

0

0

0

0

0
9

9

79

7/9

79

7/9

!

The L3 Info element contains the complete Ciphering Mode Command message as defined in GSM 04.08.
8.4.7
HANDOVER DETECTION
This message is sent from BTS to BSC when BTS correctly receives information from an MS on the handover
activated channel.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

$FFHVV'HOD\
1)
8.4.8

0

0

0

21)
9

9

79

79

The Access Delay element is included if the sending of the handover detection message was triggered by
the reception of a handover access burst with the correct handover reference.
MEASUREMENT RESULT
This message from BTS to BSC is used to report to BSC the results of radio channel measurements made by BTS
(uplink) and to convey the measurement reports from MS received on SACCH and in the L1 headers.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

0HDVXUHPHQWUHVXOW
QXPEHU

8SOLQN0HDVXUHPHQWV

%63RZHU

/,QIRUPDWLRQ

/,QIR0($65(3RU(;7
0($65(3

067LPLQJ2IIVHW

Exercises
0

0

0

0

0

0

2

2

2
9

9

79

79

7/9

79

79

7/9

79

!

147 (199)

1)
The L1 Information element contains the last received L1-header (MS Power and Timing
Advance) from MS and the L3 Information element contains the complete MEASurement
REPort message or EXTended MEASurement REPort message received from MS. They are
included only if received since last (EXTended) MEASurement RESult message.
2)
MS Timing Offset can be optionally included to increase the accuracy of possible distance
measurements.
8.4.9
MODE MODIFY
This message is sent from BSC to BTS to request a change of channel mode of an active channel.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

&KDQQHO0RGH


0DLQFKDQQHOUHIHUHQFH
8.4.10

0

0

0

0

2

2
9

9

79

7/9

7/9

79

!

1)
The Encryption Information element is only included if ciphering is to be applied.
2)
Optional element for multislot operation, it may be used in case of power control in the BTS.
MODE MODIFY ACKNOWLEDGE
This message is sent from BTS to BSC to confirm the change of channel mode of an active channel.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU
8.4.11

0

0

0
9

9

79

MODE MODIFY NEGATIVE ACKNOWLEDGE
This message is sent from BTS to BSC to indicate that the channel mode modification could not be performed as
requested.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

&DXVH
8.4.12

0

0

0

0
9

9

79

7/9

!
PHYSICAL CONTEXT REQUEST
This message is sent from BSC to BTS to request the "physical context" of an active channel.
Exercises
148 (199)

,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU
8.4.13

0

0

0
9

9

79

PHYSICAL CONTEXT CONFIRM
This message is sent from BTS to BSC as a response to a PHYsical CONTEXT REQuest message. The message
contains the "physical context" information.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

%63RZHU

063RZHU

7LPLQJ$GYDQFH

3K\VLFDO&RQWH[W
1)
8.4.14

0

0

0

0

0

0

2
9

9

79

79

79

79

7/9

!

RF CHANNEL RELEASE
This message is sent from BSC to BTS to inform that a radio channel is no longer needed.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU
8.4.15

0

0

0
9

9

79

MS POWER CONTROL
This message is sent from BSC to BTS to change the MS power level or the parameters used by TRX to control
the MS power.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

063RZHU

063RZHU3DUDPHWHUV
1)

0

0

0

0

2
9

9

79

79

7/9

!
If the MS Power Parameters element is present it indicates that the MS power control is to be
performed by TRX. The MS Power element then indicates the maximum MS power to be used.
Exercises
149 (199)

8.4.16
BS POWER CONTROL
This message is sent from BSC to BTS to change the TRX transmission power level or the parameters used by
TRX to control its transmission power.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

%63RZHU

%63RZHU3DUDPHWHUV
1)
8.4.17

0

0

0

0

2
9

9

79

79

7/9

!
If the BS Power Parameters element is present it indicates that the TRX transmission power
control is to be performed by TRX. The BS Power element then indicates the maximum
transmission power to be used.
PRE-PROCESS CONFIGURE
This message is sent from BSC to BTS to modify the pre-processing parameters used by BTS.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

3UHSURF3DUDPHWHUV
8.4.18

0

0

0

0
9

9

79

7/9

!
PRE-PROCESSED MEASUREMENT RESULT
This message is used by BTS to report the results of radio parameter pre-processing.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

3UHSURF0HDVXUHPHQWV
8.4.19

0

0

0

0
9

9

79

7/9

!
RF CHANNEL RELEASE ACKNOWLEDGEMENT
This message is sent from BTS to BSC as an acknowledgment to a RF CHANnel RELease message.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

Exercises
0

0

0
9

9

79

150 (199)

8.4.20
SACCH INFO MODIFY
This message is sent from BSC to BTS to modify the SACCH filling information sent on an individual SACCH
channel. This new SACCH filling information shall be sent on the indicated channel until the channel is released or
the information is changed by another SACCH INFO MODIFY message.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

6\VWHP,QIR7\SH

/,QIR

6WDUWLQ7LPH

0

0

0

0

2

2
9

9

79

79

7/9

79

1)
If the L3 Info information element is not included, this indicates that transmission of the indicated
message shall be stopped, i.e. message shall no longer be sent on this channel.
2)
The Starting Time element is optionally used to indicate when transmission of the new
information is to start and when transmission is to stop.
The System Info Type element indicates the type of SYSTEM INFORMATION/EXTENDED MEASUREMENT
ORDER message which follows in the L3 Info field.
The L3 Information element contains the relevant SYSTEM INFORMATION/EXTENDED MEASUREMENT
ORDER message as defined in GSM 04.08.
8.4.21
TALKER DETECTION
This message is sent from BTS to BSC when BTS correctly receives on a channel activated for VGCS an access
from an MS indicating that it requires the uplink of the channel.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

$FFHVV'HOD\
1)

0

0

0

21)
9

9

79

79

The Access Delay element is included if the sending of the uplink access message was triggered by the
reception of an uplink access burst with the correct values.
Exercises
151 (199)

8.4.22
LISTENER DETECTION
This message is sent from BTS to BSC when BTS correctly receives on a channel activated for VGCS or VBS an
access from an MS indicating its presence on the channel.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

$FFHVV'HOD\
1)
8.5

0

0

0

21)
9

9

79

79

The Access Delay element is included if the sending of the uplink access message was triggered by the
reception of an uplink access burst with the correct value.
COMMON CHANNEL MANAGEMENT MESSAGES
These messages are related to Common Channel Management procedures. They all have the following general
format:
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

0

0

0
9

9

79

.
.
,QIRUPDWLRQHOHPHQWV
GHSHQGLQJRQPHVVDJH
W\SH
Message name
BCCH INFOrmation
CCCH LOAD INDication
CHANnel ReQuireD
DELETE INDication
PAGING CoMmanD
NOTification CoMmanD
SMS BroadCast REQuest
SMS Broadcast Command
CBCH LOAD INDICATION
8.5.1
Reference section
8.5.1
8.5.2
8.5.3
8.5.4
8.5.5
8.5.10
8.5.6
8.5.7
8.5.8
8.5.9
BCCH INFORMATION
This message is sent from BSC to BTS to indicate new information to be broadcast on BCCH.
Exercises
152 (199)

,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

6\VWHP,QIR7\SH

)XOO%&&+,QIR
6<6,1)2

6WDUWLQJ7LPH

0

0

0

0

2

2
9

9

79

79

7/9

79

1)
If the Full BCCH information element is not included this indicates that transmission of the
indicated SYSTEM INFORMATION message shall be stopped.
2)
information is to start or when transmission is to stop.
The System Info Type element indicates the type of SYSTEM INFORMATION message which follows in the Full
BCCH Information element.
The Full BCCH Information element contains the relevant SYSTEM INFORMATION message as defined in
GSM 04.08.
8.5.2
CCCH LOAD INDICATION
This message is sent from BTS to BSC to report the current load on the indicated CCCH timeslot (random access,
RACH, and paging, PCH).
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHUQRWH

5$&+/RDG

3DJLQJ/RDG

0

0

0

&

&
9

9

79

7/9

79

!

NOTE:
The BTS may set the "Channel Number" information element in this message to either the
"uplink CCCH" or the "downlink CCCH" on that timeslot number.
1)
The RACH load information element is included only if the Channel number information
indicates "uplink CCCH".
2)
The Paging load information element is included only if the Channel number information
indicates "downlink CCCH".
Exercises
153 (199)

8.5.3
CHANNEL REQUIRED
This message is sent from BTS to BSC to indicate the reception of a CHANnel REQuest message (special access
burst message) from an MS.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

5HTXHVW5HIHUHQFH

$FFHVV'HOD\

3K\VLFDO&RQWH[W
1)

0

0

0

0

0

2
9

9

79

79

79

7/9

!
The Request Reference element contains the random access reference value sent by MS in the CHANnel
REQuest message and some low order bits of the absolute frame number for the reception of the access burst.
8.5.4
DELETE INDICATION
This message is sent from BTS to BSC to indicate the deletion of an access grant message (IMMediate ASSIGN)
due to overload of downlink CCCH.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

)XOO,PP$VVLJQ,QIR
8.5.5

0

0

0

0
9

9

79

7/9

PAGING COMMAND
This message is sent from BSC to BTS to request the paging of an MS.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

3DJLQJ*URXS

06,GHQWLW\

&KDQQHO1HHGHG

H0/333ULRULW\

0

0

0

0

0

2

2
9

9

79

79

7/9

79

79

1)
If the Channel Needed element is not present, the default value is assumed to be 00 (any
channel).
2)
If the eMLPP Priority is not present then the BTS does not include the eMLPP priority in the
radio interface message.
Exercises
154 (199)

The Paging Group element is used by BTS to calculate the correct DRX paging block to be used for the
transmission of the PAGing REQuest message as defined in GSM 05.02.
8.5.6
This message is sent from BSC to BTS to request the transmission of an immediate assignment message.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

)XOO,PP$VVLJQ,QIR

0

0

0

0
9

9

79

7/9

The Full Imm. Assign Info element contains the relevant immediate assignment message as defined in GSM 04.08
(IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT REJECT)
with the "Page Mode" element set to the value "no change".
8.5.7
SMS BROADCAST REQUEST
This message is sent from BSC to BTS to request the sending of a Short Message Service Cell Broadcast
message.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

606&%,QIRUPDWLRQ

606&%&KDQQHO,QGLFDWRU

0

0

0

0

2
9

9

79

79

79

The SMSCB Information element contains the complete information to be broadcast on the CBCH as defined in
GSM 04.12 (including the Layer 2 header to be used on the radio path).
1)
8.5.8
The SMSCB Channel Indicator IE indicates the CBCH which shall be used for broadcasting the
data. If this information element is not present the basic CBCH (see GSM 05.02) shall be used.
SMS BROADCAST COMMAND
This message is sent from BSC to BTS to command Short Message Service Cell Broadcast.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

&%&RPPDQGW\SH

606&%PHVVDJH

606&%&KDQQHO,QGLFDWRU

0

0

0

0

0

2
9

9

79

79

7/9

79

The CB Command type IE contains the command to be performed, allowing the BSC to:
-
request immediate broadcast i.e. transmission in the next CBCH opportunity;
Exercises
155 (199)

-
set the BTS broadcast default mode.
The SMSCB message IE contains the actual message to be broadcast on the CBCH i.e. a maximum of 88 octets of
data. The BTS is responsible for performing the segmentation, building the block types and padding if necessary,
see GSM 04.12 for the message format on the radio path.
1) The SMSCB Channel Indicator IE indicates the CBCH which shall be used for broadcasting the data.
If this information element is not present the basic CBCH [see GSM 05.02] shall be used.
8.5.9
CBCH LOAD INDICATION
This message is sent from BTS to BSC to indicate a CBCH underflow/overflow situation in the BTS and to request
the BSC to accelerate or pause the cell broadcast for a period indicated by BTS.
Information Element
Message type
Channel number
CBCH Load Information
SMSCB Channel Indicator
Reference
9.1
9.2
9.3.1
9.3.43
9.3.44
Presence
M
M
M
M
O 1)
Format
V
V
TV
TV
TV
Length
1
1
2
2
2
The CBCH Load Information element indicates the load situation in CBCH (underflow/overflow) and information
about the requested acceleration/suspension period of cell broadcast.
1) The SMSCB Channel Indicator IE indicates the CBCH which shall be used for broadcasting the data. If this
information element is not present the basic CBCH [see GSM 05.02] shall be used.
8.5.10
NOTIFICATION COMMAND
This message is sent from BSC to BTS to request a change of notification for voice group call.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&KDQQHOQXPEHU

&RPPDQGLQGLFDWRU

*URXSFDOOUHIHUHQFH

&KDQQHO'HVFULSWLRQ

1&+'5;LQIRUPDWLRQ
1)

0

0

0

0

2

2

2
9

9

79

7/9

7/9

7/9

7/9

Q

This information element indicates the type of command that is to be performed by the BTS with
respect to information contained in the rest of the message.
Exercises
156 (199)

8.6
TRX MANAGEMENT MESSAGES
These messages are related to TRX Management procedures. They all have the following general format (no
channel number included):
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

0

0
9

9

,QIRUPDWLRQHOHPHQWV

GHSHQGLQJRQPHVVDJH
W\SH
Message name
Reference section
RF RESource INDication
SACCH FILLing
OVERLOAD
ERROR REPORT
8.6.1
8.6.1
8.6.2
8.6.3
8.6.4
RF RESOURCE INDICATION
This message is sent from BTS to BSC to indicate the interference level on idle channels of a TRX.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

5HVRXUFH,QIRUPDWLRQ
8.6.2

0

0

0
9

9

7/9

!
SACCH FILLING
This message is sent from BSC to BTS to indicate the new broadcast information to be used as filling information
on downlink SACCH.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

6\VWHP,QIR7\SH

/,QIR6<6,1)2

6WDUWLQJ7LPH

0

0

0

2

2
9

9

79

7/9

79

1)
If the L3 Info information element is not included this indicates that transmission of the indicated
SYSTEM INFORMATION message shall be stopped.
2)
information is to start and when transmission is to stop.
The System Info Type element indicates the type of SYSTEM INFORMATION message which follows in the L3 Info
field.
The L3 Information element contains the relevant SYSTEM INFORMATION message as defined in GSM 04.08.
Exercises
157 (199)

8.6.3
OVERLOAD
This message is sent from BTS to BSC to indicate an overload situation. Possible cause values include:
-
CCCH overload;
ACCH overload;
processor overload.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&DXVH
8.6.4

0

0

0
9

9

7/9

!
ERROR REPORT
This message is sent from BTS to BSC to report a detected error which cannot be reported in any other message.
,1)250$7,21(/(0(17 5()(5(1&( 35(6(1&( )250$7 /(1*7+

0HVVDJHW\SH

&DXVH

0HVVDJH,GHQWLILHU

&KDQQHO1XPEHU

/LQNLGHQWLILHU

(UURQHRXV0HVVDJH

0

0

0

2

2

2

2
9

9

7/9

79

79

79

7/9

!

!
1)
Used to indicate which type of message was considered erroneous.
2)
Used to indicate for which radio channel the error is reported.
3)
Used to indicate for which radio L2 link the error is reported.
4)
This element may be used to carry the complete erroneous message as it was received from
the BSC.
Exercises
158 (199)
Information element codings
This clause contains the codings of the signalling elements used. The following conventions are assumed for the
sequence of transmission of bits and bytes:
-
Each bit position is numbered as 1 to 8.

The least significant bit is bit 1 and is transmitted first, followed by bits 2, 3, 4 etc.
In an element, octets are identified by number. Octet 1 is transmitted first, then octet 2 etc.
When a field extends over more than one octet, the order of bit values progressively decreases as the octet
number increases. The least significant bit of the field is represented by the lowest numbered bit of the
highest numbered octet of the field.
For variable length elements, a length indicator is included. This indicates the number of octets following in
the element.
All spare or reserved bits are set to 0.
9.1
A 1 octet field is used in all messages to discriminate between Transparent and Non-Transparent messages and
also between Radio Link Layer Management, Dedicated Channel Management, Common Channel Management
and TRX Management messages.
8
******* 7
The T-bit is set to 1 to indicate that the message is to be/was considered transparent by BTS. All other messages
shall have the T-bit set to 0.
The G-bits are used to group the messages as follows:
G7 G6 G5 G4 G3 G2 G1
Message Group
0
0
0
0
0
reserved
Radio Link Layer Management messages
Dedicated Channel Management messages
Common Channel Management messages
TRX Management messages
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
1
1
0
0
0
0
1
0
0
1
0
0
0
All other values are reserved for future use.

9.2
MESSAGE TYPE
The Message Type uniquely identifies the function of the message being sent. It is a single octet and coded in the
following way:
8
(00HVVDJHW\SH
Bit 8 is the extension bit and is reserved for future use. The following message types are used (all other values are
reserved):
87654321
Message
Reference
0 0 0 0 - - - - Radio Link Layer Management messages:

0001
- DATA REQuest
Exercises
8.3.1
159 (199)

0010
0011
0100
0101
0110
0111
1000
1001
1010
1011
- DATA INDication
- ERROR INDication
- ESTablish REQuest
- ESTablish CONFirm
- ESTablish INDication
- RELease REQuest
- RELease CONFirm
- RELease INDication
- UNIT DATA REQuest
- UNIT DATA INDication
8.3.2
8.3.3
8.3.4
8.3.5
8.3.6
8.3.7
8.3.8
8.3.9
8.3.10
8.3.11
0001---0001
0010
0011
0100
0101
0110
0111
1001
1010
1011
1100
1101
1110
1111
Common Channel Management/TRX Management messages:

- BCCH INFOrmation
8.5.1
- CCCH LOAD INDication
8.5.2
- CHANnel ReQuireD
8.5.3
- DELETE INDication
8.5.4
- PAGING CoMmanD
8.5.5
- IMMEDIATE ASSIGN COMMAND
8.5.6
- SMS BroadCast REQuest
8.5.7
- RF RESource INDication
8.6.1
- SACCH FILLing
8.6.2
- OVERLOAD
8.6.3
- ERROR REPORT
8.6.4
- SMS BroadCast CoMmanD
8.5.8
- CBCH LOAD INDication
8.5.9
- NOTification CoMmanD
8.5.10
001----00001
00010
00011
00100
00101
00110
00111
01000
01001
01010
01011
01100
01101
01110
01111
10000
10001
10010
10011
10100
10101
10110
Dedicated Channel Management messages:

- CHANnel ACTIVation
8.4.1
- CHANnel ACTIVation ACKnowledge
8.4.2
- CHANnel ACTIVation Negative ACK
8.4.3
- CONNection FAILure
8.4.4
- DEACTIVATE SACCH
8.4.5
- ENCRyption CoMmanD
8.4.6
- HANDOver DETection
8.4.7
- MEASurement RESult
8.4.8
- MODE MODIFY REQuest
8.4.9
- MODE MODIFY ACKnowledge
8.4.10
- MODE MODIFY Negative ACKnowledge 8.4.11
- PHYsical CONTEXT REQuest
8.4.12
- PHYsical CONTEXT CONFirm
8.4.13
- RF CHANnel RELease
8.4.14
- MS POWER CONTROL
8.4.15
- BS POWER CONTROL
8.4.16
- PREPROCess CONFIGure
8.4.17
- PREPROCessed MEASurement RESult 8.4.18
- RF CHANnel RELease ACKnowledge
8.4.19
- SACCH INFO MODIFY
8.4.20
- TALKER DETection
8.4.21
- LISTENER DETection
8.4.22
Exercises
160 (199)

9.3
Other information elements
The information elements used and the coding of their Element Identifier fields are:
Element
Identifier bits
87654321
Element name
Reference
00000001
00000010
00000011
00000100
00000101
Channel Number
Link Identifier
Activation Type
BS Power
Channel Identification
9.3.1
9.3.2
9.3.3
9.3.4
9.3.5
00000110
00000111
00001000
00001001
00001010
Channel Mode
Encryption Information
Frame Number
Handover Reference
L1 Information
9.3.6
9.3.7
9.3.8
9.3.9
9.3.10
00001011
00001100
00001101
00001110
00001111
L3 Information
MS Identity
MS Power
Paging Group
Paging Load
9.3.11
9.3.12
9.3.13
9.3.14
9.3.15
00010000
00010001
00010010
00010011
00010100
Physical Context
Access Delay
RACH Load
Request Reference
Release Mode
9.3.16
9.3.17
9.3.18
9.3.19
9.3.20
00010101
00010110
00010111
00011000
00011001
Resource Information
RLM Cause
Starting Time
Timing Advance
Uplink Measurements
9.3.21
9.3.22
9.3.23
9.3.24
9.3.25
00011010
00011011
00011100
00011101
00011110
Cause
Measurement result number
Message Identifier
reserved
System Info Type
9.3.26
9.3.27
9.3.28
00011111
00100000
00100001
00100010
00100011
MS Power Parameters
BS Power Parameters
Pre-processing Parameters
Pre-processed Measurements
reserved
9.3.31
9.3.32
9.3.33
9.3.34
00100100
00100101
00100110
00100111
00101000
SMSCB Information
MS Timing Offset
Erroneous Message
Full BCCH Information
Channel Needed
9.3.36
9.3.37
9.3.38
9.3.39
9.3.40
00101001
00101010
00101011
00101100
00101101
CB Command type
SMSCB message
Full Immediate Assign Info
SACCH Information
9.3.41
9.3.42
9.3.35
9.3.29
9.3.43
9.3.30
Exercises
161 (199)

Element
Identifier bits
87654321
Element name
Reference
00101110
00101111
00110000
00110001
00110010

Group call reference
Channel description
NCH DRX information
Command indicator
9.3.44
9.3.45
9.3.46
9.3.47
9.3.48
00110011
00110100
00110101
eMLPP Priority
UIC
Main channel reference
9.3.49
9.3.50
9.3.51
00110110
to
11101111
Reserved for future use
11110000
to
11111111
Not used
9.3.1
Channel Number
In the direction BSC to BTS the Channel Number parameter is used to indicate on which physical channel/subchannel the message is to be sent. In the direction BTS to BSC the Channel Number indicates on which physical
channel/sub-channel the message was received. It is coded in two octets as follows:
8
(OHPHQWLGHQWLILHU
&&&&& 71
The C-bits describe the channel as follows:

C5 C4 C3 C2 C1
0 0 0 0 1 Bm + ACCHs
0 0 0 1 TLm + ACCHs
0 0 1 T TSDCCH/4 + ACCH
0 1 T T T
SDCCH/8 + ACCH
1 0 0 0 0 BCCH
1 0 0 0 1 Uplink CCCH (RACH)
1 0 0 1 0 Downlink CCCH (PCH + AGCH)
The T-bits indicate, coded in binary, the sub-channel number as specified in GSM 05.02.
TN is timeslot number, binary represented as in GSM 05.02.
9.3.2
Link Identifier
This element identifies the signalling channel and SAPI of the radio data link.
8
(OHPHQWLGHQWLILHU
&& 1$ UHVHUYHG 6$3,
The NA bit (bit 6 in octet 2) is set to 1 to indicate that the Link Identifier is not applicable for this message. In all
other cases it is set to 0.
The C-bits indicate the channel type as follows:
Exercises
162 (199)

C2 C1
0 0
main signalling channel (FACCH or SDCCH)
0 1
SACCH

The SAPI field contains the SAPI value as defined in GSM 04.05.
9.3.3
Activation Type
This element is used to indicate the type of activation requested in the CHANnel ACTIVation message. It is coded
in two octets as follows:
8
(OHPHQWLGHQWLILHU
5 5HVHUYHG $$$
The R bit indicates if the procedure is an initial activation or a reactivation.
R
0
1
Initial activation
Reactivation
The A-bits indicate the type of activation, which defines the access procedure and the operation of the data link
layer, as follows:
A3 A2 A1
0 0 0
1
Activation related to intra-cell channel change

- related to immediate assignment procedure
- related to normal assignment procedure
0 1 0
1
Activation related to inter-cell channel change (handover)

- related to asynchronous handover procedure
- related to synchronous handover procedure
1 0 0
1
Activation related to secondary channels

- related to additional assignment procedure
- related to multislot configuration
All other values reserved for future use.

NOTE:
9.3.4
For the main TCH channel in a Multislot configuration activation types for intra-cell and inter-cell
channel change are used.
BS Power
This information element indicates the TRX transmission power level on a particular channel.
8
(OHPHQWLGHQWLILHU
5HVHUYHG 3RZHU/HYHO
Exercises
163 (199)

The Power Level field (octet 2) indicates the number of 2 dB steps by which the power shall be reduced from its
nominal value, Pn, set by the network operator to adjust the coverage. Thus the Power Level values correspond to
the following powers (relative to Pn):
Value
00000
00001
00010
.
.
01110
01111
Power level
Pn
Pn - 2 dB
Pn - 4 dB
Pn - 28 dB
Pn - 30 dB

See also GSM 05.05, subclause 4.1.2 and GSM 05.08, sub-clause 4.5.
9.3.5
Channel Identification
This information element describes some aspects of a channel together with its SACCH.
8
(OHPHQWLGHQWLILHU
/HQJWK
&KDQQHO'HVFULSWLRQ
0RELOH$OORFDWLRQ
A * denotes that the whole of the 04.08 element including the element identifier and length should be included. The
04.08 "Mobile Allocation" shall for compatibility reasons be included but empty, i.e. the length shall be zero.
9.3.6
Channel Mode
This element gives information on the mode of coding/decoding and transcoding/rate adaption of a channel.
8
(OHPHQWLGHQWLILHU
/HQJWK
5HVHUYHGIRUIXWXUHXVH '7;G '7;X
6SHHFKRUGDWDLQGLFDWRU
&KDQQHOUDWHDQGW\SH
6SHHFKFRGLQJDOJRUGDWDUDWHWUDQVSLQG
The DTX bits of octet 3 indicate whether DTX is applied:
1 DTX is applied
0 DTX is not applied.
DTXd indicates use of DTX in the downlink direction (BTS to MS) and DTXu indicates use of DTX in the uplink
direction (MS to BTS).
The "Speech or data indicator" field (octet 4) is coded as follows:
0000 0001
0000 0010
0000 0011
Speech
Data
Signalling
Exercises
164 (199)

All other values are reserved.
The "Channel rate and type" field (octet 5) is coded as follows:
0000 0001
0000 1000
0000 1001
0000 1010
0001 1010
0001 1000
0001 1001
0010 1000
0010 1001
SDCCH
Full rate TCH channel Bm
Half rate TCH channel Lm
Full rate TCH channel bi-directional Bm, Multislot configuration
Full rate TCH channel uni-directional downlink Bm, Multislot configuration
Full rate TCH channel Bm Group call channel
Half rate TCH channel Lm Group call channel
Full rate TCH channel Bm Broadcast call channel
Half rate TCH channel Lm Broadcast call channel

The "speech coding algorithm/data rate + transparency indicator" field (octet 6) is coded as follows:
If octet 4 indicates speech, then octet 6 is coded as follows:
0000 0001
0001 0001
0010 0001
GSM speech coding algorithm version 1


If octet 4 indicates signalling then octet 6 is coded as follows:
0000 0000
No resources required

If octet 4 indicates data, then octet 6 is coded as follows:
8
H[W 717 5DWH RFWHW

Bit 8:
Reserved for extension
Bit 7: 0 Transparent service

1 Non-transparent service.
For the non-transparent service, bits 6 to 1 indicate the radio interface data rate:
65 4321
01 100014.5 kbit/s
01 000012 kbit/s
01 00016 kbit/s
all other values are reserved.
Exercises
165 (199)

For the transparent service, bits 6-1 indicate the data rate:
65 4321
01 100014.4 kbit/s
01 00009.6 kbit/s
01 00014.8 kbit/s
01 00102.4 kbit/s
01 00111.2 kbit/s
01 0100600 bit/s
01 01011 200/75 bit/s (1 200 network-to-MS, 75 MS-to-network)
9.3.7
This element is a variable length element. It contains necessary information to control encryption devices.
8
(OHPHQWLGHQWLILHU
/HQJWK
$OJRULWKPLGHQWLILHU
.H\

.
.

Q
The Algorithm Identifier field (octet 3) indicates the relevant ciphering algorithm. It is coded as:
0000 0000
0000 0001
0000 0010
0000 0011
0000 0100
0000 0101
0000 0110
0000 0111
0000 1000
Reserved
No encryption shall be used.
GSM encryption algorithm version 1 (A5/1)
GSM A5/2
GSM A5/3
GSM A5/4
GSM A5/5
GSM A5/6
GSM A5/7
All other values are reserved

The Key field (octets 4-n) indicates the ciphering key. It shall be an integral number of octets and the length is given
as the value of the Length field minus 1.
9.3.8
Frame Number
This element contains the absolute frame number (FN) modulo 42432. It is used to carry the current timing in BTS
to BSC for calculation of the Starting Time parameter required in some messages.
8
(OHPHQWLGHQWLILHU
7
7KLJK
7ORZ7
Octets 2-3 are coded as defined for octets 2-3 of the Starting Time information element of GSM 04.08.
Exercises
166 (199)

9.3.9
Handover reference
The information is coded in two octets and contains the handover reference value.
8
(OHPHQWLGHQWLILHU
+DQGRYHUUHIHUHQFH
The Handover Reference octet contains the handover reference value as defined in GSM 04.08.
9.3.10
L1 Information
This element carries the information used in the L1 header of SACCH blocks.
8
(OHPHQWLGHQWLILHU
06SRZHUOHYHO 5HVHUYHG
$FWXDO7LPLQJ$GYDQFH 5HVHUYHG
Octets 2-3 contain the L1 header information of SACCH blocks. The information fields and codings are as defined
in GSM 04.04.
9.3.11
L3 Information (message name)
This element contains a link layer service data unit (L3 message). It is used to forward a complete L3 message as
specified in GSM 04.08 between BTS and BSC.
8
(OHPHQWLGHQWLILHU
/HQJWK

,QGLFDWRU
/LQN/D\HU6HUYLFH'DWD8QLW

.
(i.e. a layer 3 message
.

DVGHILQHGLQ*60 Q
The Length Indicator field (octets 2-3) indicates in binary the remaining length of the element (octets 4-n). The most
significant bit is bit 8 of octet 2 and the least significant bit is bit 1 of octet 3.
Octets 4-n contain the complete L3 message as defined in GSM 04.08. In the message format section, the 04.08
message name to be included is indicated within brackets.
Exercises
167 (199)

9.3.12
MS Identity
This element carries the identity of an MS (TMSI or IMSI). It is a variable length element.
8
(OHPHQWLGHQWLILHU
/HQJWK

.
MS Identity
.

1
The MS Identity field (octets 3-N) is coded as specified for the Mobile Identity information element of GSM 04.08,
octets 3-N.
9.3.13
MS Power
This element carries the power level of MS.

8
(OHPHQWLGHQWLILHU
5HVHUYHG 3RZHU/HYHO
The coding and meaning of the Power Level field is as defined in GSM 05.05 and GSM 05.08. See also
GSM 04.04.
9.3.14
Paging Group
This element carries the paging population of an MS to be paged.

8
(OHPHQWLGHQWLILHU
3DJLQJ*URXS
The Paging Group field (octet 2) contains the binary representation of the paging group as defined in GSM 05.02.
9.3.15
Paging Load
This element carries data about the load of a paging channel (PCH).
8
(OHPHQWLGHQWLILHU

3DJLQJ%XIIHU6SDFH

The Paging Buffer Space field (octets 2-3) indicates the remaining space for Paging Commands associated with
this CCCH timeslot, given as the number of additional Paging Commands that it is possible to store. The number is
binary coded with the most significant bit in bit 8 of octet 2 and the least significant bit in bit 1 of octet 3.
9.3.16
Physical Context
This element contains supplementary information on the transmission/reception process. It is a variable length
element.
Exercises
168 (199)

8
(OHPHQWLGHQWLILHU
/HQJWK
3K\VLFDO

.
Context
.

,QIRUPDWLRQ 1
The Physical Context Information field is not specified. This information should not be analysed by BSC, but merely
forwarded from one TRX/channel to another.
9.3.17
Access Delay
This element contains the delay of the access burst as measured by BTS at random access or at handover access.
8
(OHPHQWLGHQWLILHU
$FFHVV'HOD\
The Access Delay field contains the delay of the access burst as measured by BTS. The delay is expressed as
defined for the Timing Advance TA in GSM 05.10 but with the range extended to 8 bits, i.e. the six least significant
bits of the field correspond to the Timing Advance.
9.3.18
RACH Load
This element is used to carry information on the load of the RACH (Random Access Channel) associated with this
CCCH timeslot. It is of variable length.
8
(OHPHQWLGHQWLILHU
/HQJWK

5$&+6ORW&RXQW

5$&+%XV\&RXQW

5$&+$FFHVV&RXQW

6XSSOHPHQWDU\
.
.
,QIRUPDWLRQ
1
The RACH Slot Count field (octets 3-4) indicates the total number of available access slots over which the
measurement (counting) was performed. The value is binary coded with the most significant bit in bit 8 of the first
octet and the least significant bit in bit 1 of the second octet.
The RACH Busy Count field (octets 5-6) indicates the number of RACH burst periods during which the received
signal level has exceeded a given threshold. This will give a measure of the number of "busy" random access slots.
The value is binary coded with the most significant bit in bit 8 of the first octet and the least significant bit in bit 1 of
the second octet.
Exercises
169 (199)

The RACH Access Count field (octets 7-8) indicates the number of received access bursts during the same
measurement period. The value is binary coded with the most significant bit in bit 8 of the first octet and the least
significant bit in bit 1 of the second octet.
The busy count signal level threshold and the measurement period are parameters set by O&M.
The Supplementary Information field may carry additional operator dependent information.
9.3.19
Request Reference
This element carries the Request Reference parameters used for contention resolution on RACH.
8
(OHPHQWLGHQWLILHU
5$
7
7KLJK
7ORZ7
Octets 2-4 are coded as the corresponding fields of the Request Reference element of GSM 04.08. (Octet 2, RA, is
the Random Access Information field set by MS in the CHANnel REQuest message. Octets 3-4 contain the
absolute frame number modulo 42432 for the frame number when the access burst was received, see Starting
Time information element of GSM 04.08).
9.3.20
Release Mode
This element is used to distinguish between normal release and local end release of the radio data link connection.
8
(OHPHQWLGHQWLILHU
5HVHUYHGIRUIXWXUHXVH 0
The M bit is coded as follows:
0
normal release
local end release
9.3.21
Resource Information
This element is used to indicate the interference level for each of the idle channels of a TRX.
8
(OHPHQWLGHQWLILHU
/HQJWK
&KDQQHO1XPEHU

,QWHUIHUHQFHOHYHO
.
.
.
.
&KDQQHO1XPEHU1 1

,QWHUIHUHQFHOHYHO1 1
The Length field indicates in binary the remaining length of the element (octets 3-N).
Octets 3-N forms a list of Channel Numbers and Interference levels measured on the corresponding channel.
Exercises
170 (199)

The Channel Number octet is coded as octet 2 of the Channel Number information element, sub-clause 9.3.1.
The Interference Level octet is coded as follows:
8
,QWHUI%DQG 5HVHUYHGIRUIXWXUHXVH
The Interf Band field (bits 6-8) indicates in binary the interference level expressed as one of five possible
interference level bands as defined by O&M. The interference level is averaged over a period of Intave (parameter
set by O&M, see GSM 05.08) immediately before the transmission of the RF RESource INDication message. See
also GSM 08.08, sub-clause 3.1.3.1 and GSM 05.08, sub-clause 3.1 e) of appendix A.
9.3.22
RLM Cause
This element is used to indicate the precise protocol error or the reason for a release on the radio link layer.
8
(OHPHQWLGHQWLILHU
/HQJWK
(&DXVH9DOXH
The Cause Value is a one octet field if the extension bit is set to 0. If the extension bit is set to 1, the Cause Value
is a two octet field.
Exercises
171 (199)

The Cause Value field is coded as follows:
87654321
00000000
00000001
00000010
00000011
00000100
00000101
00000110
00000111
00001000
00001001
00001010
00001011
00001100
00001101
00001110
reserved
timer T200 expired (N200+1) times
re-establishment request
unsolicited UA response
unsolicited DM response
unsolicated DM response, multiple frame established state
unsolicited supervisory response
sequence error
U-frame with incorrect parameters
S-frame with incorrect parameters
I-frame with incorrect use of M bit
I-frame with incorrect length
frame not implemented
SABM command, multiple frame established state
SABM frame with information not allowed in this state

9.3.23
Starting Time
This element provides the starting time expressed as FN modulo 42432 (FN is absolute frame number).
8
(OHPHQWLGHQWLILHU
7
7KLJK
7ORZ7
Octets 2-3 are coded as defined for octets 2-3 of the Starting Time information element of GSM 04.08.
9.3.24
Timing Advance
This element contains the timing advance to be used by MS in subsequent communications. It is calculated by BTS
at the reception of a CHANnel REQuest message (random access burst) or a handover access burst.
8
(OHPHQWLGHQWLILHU
5HVHUYHG 7LPLQJ$GYDQFH
The Timing Advance field contains the timing advance TA as specified in GSM 05.10.
Bits 7-8 of octet 2 are reserved for future use.
9.3.25
Uplink Measurements
This element is used to report the results of the TRX measurements on the uplink radio path of an activated basic
radio channel. It is of variable length.
Exercises
172 (199)

8
(OHPHQWLGHQWLILHU
/HQJWK
UIX '7;G 5;/(9 )8// XS
5HVHUYHG 5;/(9 68% XS
5HVHUYHG 5;48$/ )8// XS 5;48$/ 68% XS
6XSSOHPHQWDU\

.
Measurement
.

,QIRUPDWLRQ 1
rfu = Reserved for Future Use.
Octets 3-5 contain results from measurements made by TRX on the uplink.
The Supplementary Measurement Information field (octets 6-N) may carry additional operator dependent
information.
The DTXd field (octet 3) indicates whether DTX was employed by TRX on the downlink transmission during the
measurement period.
The RXLEV-FULL-up and RXLEV-SUB-up fields (octets 3-4) report the average uplink signal level as measured by
TRX over the measurement period on all slots and on a subset of the slots respectively (see GSM 05.08, subclause 8.2). Each field is coded as defined in GSM 05.08, sub-clause 8.1.4.
The RXQUAL-FULL-up and RXQUAL-SUB-up fields (octet 5) report the average uplink quality as measured by
TRX over the measurement period on all slots and on a subset of the slots respectively (see GSM 05.08, subclause 8.2). Each field is coded as defined in GSM 05.08, sub-clause 8.2.4.
9.3.26
Cause
The cause element is used to indicate the reason for a particular event to have occurred and is coded as shown
below.
8
(OHPHQWLGHQWLILHU
/HQJWK
(&DXVH9DOXH
&DXVH([WHQVLRQ D

:
Diagnostic(s) if any
:

1
The Cause Value is a single octet field (octet 3) if the extension bit E (bit 8) is set to 0. If it is set to 1 then the
cause value is a 2 octet field (octets 3 and 3a).
The Cause Value is divided into two fields: a class (bits 5-7 of octet 3) and a value within the class (bits 1-4 of octet
3).
Exercises
173 (199)

If the value of the first octet of the cause field is 1XXX 0000 then the second octet is reserved for national
applications (XXX will still indicate the class).
Diagnostic information is not available for every cause, see the table below. When available, it is coded in the same
way as the corresponding information element in clause 9. Inclusion of diagnostics is optional.
Classes:
Class (000): Normal event
Class (001): Normal event
Class (010): Resource unavailable
Class (011): Service or option not available
Class (100): Service or option not implemented
Class (101): Invalid message (e.g. parameter out of range)
Class (110): Protocol error
Class (111): Interworking
CAUSE VALUES:
Class
0 0 0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 1
0 0 1
0 0 1
0 0 1
0 0 1
0 0 1
0 0 1
0 1 0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0 1 1
9DOXH

&DXVH

1RUPDO(YHQW

UDGLRLQWHUIDFHIDLOXUH
UDGLROLQNIDLOXUH
KDQGRYHUDFFHVVIDLOXUH
WDONHUDFFHVVIDLOXUH
UHVHUYHGIRULQWHUQDWLRQDOXVH
2 0LQWHUYHQWLRQ


QRUPDOHYHQWXQVSHFLILHG

1RUPDO(YHQW


UHVHUYHGIRUQDWLRQDOXVH

5HVRXUFHXQDYDLODEOH

HTXLSPHQWIDLOXUH
UDGLRUHVRXUFHQRWDYDLODEOH
WHUUHVWULDOFKDQQHOIDLOXUH
&&&+RYHUORDG
$&&+RYHUORDG
SURFHVVRURYHUORDG
%76QRWHTXLSSHG
UHPRWHWUDQVFRGHUIDLOXUH
QRWLILFDWLRQRYHUIORZ
UHVRXUFHQRWDYDLODEOH
XQVSHFLILHG

6HUYLFHRU2SWLRQ1RW
$YDLODEOH
Exercises
'LDJQRVWLFV
&KDQQHO1XPEHU
&KDQQHO1XPEHU
&KDQQHO1XPEHU
&KDQQHO1XPEHU
&KDQQHO1XPEHU
&KDQQHO1XPEHU
&KDQQHO1XPEHU
&KDQQHO1XPEHU
&KDQQHO1XPEHU
&KDQQHO1XPEHU
174 (199)

Class
0 1 1
0 1 1
0 1 1
0 1 1
0 1 1
1 0 0
1 0 0
1
1
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
1 0 0
1 0 1
1 0 1
1 0 1
1 0 1
1 0 1
1 0 1
1 0 1
1 0 1
1 0 1
1 1 0
1
1
1
1
1
1
1
1
0
0
0
0
1 1 0
1 1 0
1 1 0
1 1 0
1 1 0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
0
0
0
0
0
0
1 1 1
9DOXH

&DXVH 'LDJQRVWLFV

UHTXHVWHGWUDQVFRGLQJUDWH &KDQQHO1XPEHU
DGDSWLRQQRWDYDLODEOH


VHUYLFHRURSWLRQQRW
DYDLODEOHXQVSHFLILHG

6HUYLFHRU2SWLRQ1RW
,PSOHPHQWHG

HQFU\SWLRQDOJRULWKPQRW &KDQQHO1XPEHU
LPSOHPHQWHG



VHUYLFHRURSWLRQQRW
LPSOHPHQWHGXQVSHFLILHG

,QYDOLG0HVVDJH

UDGLRFKDQQHODOUHDG\
DFWLYDWHGDOORFDWHG



LQYDOLGPHVVDJHXQVSHFLILHG

3URWRFRO(UURU

PHVVDJHGLVFULPLQDWRUHUURU
PHVVDJHW\SHHUURU
PHVVDJHVHTXHQFHHUURU
JHQHUDOLQIRUPDWLRQHOHPHQW
HUURU
PDQGDWRU\LQIRUPDWLRQHOHPHQW
HUURU
RSWLRQDOLQIRUPDWLRQHOHPHQW
HUURU
LQIRUPDWLRQHOHPHQW
QRQH[LVWHQW
LQIRUPDWLRQHOHPHQWOHQJWK
HUURU
LQYDOLGLQIRUPDWLRQHOHPHQW
FRQWHQWV
SURWRFROHUURUXQVSHFLILHG
&KDQQHO1XPEHU
0HVVDJH'LVFULP
0HVVDJH7\SH
0HVVDJH7\SH
(OHPHQW,GHQWLI
(OHPHQW,GHQWLI
(OHPHQW,GHQWLI
(OHPHQW,GHQWLI
,QIRUP(OHPHQW

,QWHUZRUNLQJ
Exercises
175 (199)

Class
1 1 1
1 1 1
1 1 1
1 1 1
1 1 1
1 1 1
1 1 1
9.3.27
9DOXH

&DXVH 'LDJQRVWLFV



LQWHUZRUNLQJXQVSHFLILHG
Measurement result number
This element is used by BTS to number, (on a channel), the measurement result messages sent to BSC. It is set to
0 at activation time of the channel. The numbering is modulo 256.
8
(OHPHQWLGHQWLILHU
0HDVXUHPHQWUHVXOWQXPEHU
9.3.28
Message Identifier
This element is used to indicate a message type within a message.

8
(OHPHQWLGHQWLILHU
0HVVDJH7\SH
Octet 2 is coded as the Message Type information element, subclause 9.2.
9.3.29
SACCH Information
This element is used to carry the SACCH filling information (System Information messages, or EXTENDED
MEASUREMENT ORDER message) that is to be used on a specific channel.
8
(OHPHQWLGHQWLILHU
/HQJWK
1XPEHURIPHVVDJHV
7\SHRIVWPHVVDJH
/HQJWKRIVWPHVVDJH

VWPHVVDJH
.
. j
.
.
.
.
7\SHRIQ
WKPHVVDJH O
/HQJWKRIQ
WKPHVVDJH O
1
Q
WKPHVVDJH
.
.
The Length field (octet 2) indicates in binary the total remaining length of the element (octets 3 - N).
Exercises
176 (199)

The Number of SI messages field (octet 3) indicates in binary the number of messages contained in the element.
The coding of each of these messages consists of a type field (Type of nth msg), a length field (Length of nth
message) and a message field (nth message).
The "Type of nth msg" field indicates the type of SYSTEM INFORMATION, or an EXTENDED MEASUREMENT
ORDER message that follows in the "nth message" field. It is coded as follows:
Value
0000
0000
0000
0000
0100
Message
0101
0110
1101
1110
0111
SYSTEM INFORMATION 5
SYSTEM INFORMATION 5bis
SYSTEM INFORMATION 5ter
EXTENDED MEASUREMENT ORDER $(MAFA)$

The "Length of nth SI message" field indicates in binary the length of the "nth message" field that follows.
The "nth message" field contains a complete SACCH message as defended in GSM 04.08.
9.3.30
System Info Type
This element is used to indicate the type of SYSTEM INFORMATION message or an EXTENDED
MEASUREMENT ORDER message as defined in GSM 04.08 .
8
(OHPHQWLGHQWLILHU
6\V,QIR7\SH
The Sys Info Field (octet 2) indicates the type of message. It is coded as follows:
Value
Message
0000 0000
0000 0001
0000 0010
0000 0011
0000 0100
0000 0101
0000 0110
0000 0111
0000 1010
0000 1011
0000 1101
0000 1110
0100 0111
EXTENDED MEASUREMENT ORDER $(MAFA)$
Exercises
177 (199)

9.3.31
MS Power Parameters
This element carries the parameters required by TRX for MS power control.
8
(OHPHQWLGHQWLILHU
/HQJWK

063RZHU&RQWURO
.
.
3DUDPHWHUV
1
The MS Power Control Parameters field contains the parameters and limits required when MS power control is to
be performed by BTS. The coding is operator dependent. Examples of possible parameters and algorithms can be
found in GSM 05.08 (RXLEV, RX-QUAL-FULL, RX-QUAL-SUB, DISTANCE (Timing Advance) etc.).
9.3.32
BS Power Parameters
This element carries the parameters required by TRX for control of its own transmission power.
8
(OHPHQWLGHQWLILHU
/HQJWK

%63RZHU&RQWURO
.
.
3DUDPHWHUV
1
The BS Power Control Parameters field contains the parameters and limits required when TRX transmission power
control is to be performed by BTS. The coding is operator dependant. Examples of possible parameters and
algorithms can be found in GSM 05.08 (RXLEV, RX-QUAL-FULL, RX-QUAL-SUB, DISTANCE (Timing Advance)
etc.).
9.3.33
Pre-processing Parameters
This element contains the parameters required by BTS for the pre-processing of radio measurement data.
8
(OHPHQWLGHQWLILHU
/HQJWK
UHVHUYHGIRUIXWXUHXVH 3

3UHSURFHVVLQJ
.
.
3DUDPHWHUV
1
The P bit (bit 1 of octet 3) indicates whether pre-processing is to be used and it is coded as follows:
0
1
use the basic measurement reporting procedure (report raw data);

use the pre-processed measurement reporting procedure.
If pre-processing is to be used, the Pre-processing Parameters field (octets 4-N) contains the parameters required
by BTS. The coding of this field is operator dependant.
Exercises
178 (199)

9.3.34
Pre-processed Measurements
This element is used by BTS to report the results of the pre-processing of radio measurement data.
8
(OHPHQWLGHQWLILHU
/HQJWK

3UHSURFHVVHG
.
.
0HDVXUHPHQWV
1
The Pre-processed Measurements field (octets 3-N) contains the results of the pre-processing in BTS. The coding
of this field is operator dependant.
9.3.35
Full Immediate Assign Info
This element is used to convey a full L3 immediate assign message (3 types).

8
(OHPHQWLGHQWLILHU
/HQJWK,QGLFDWRU

)XOO,PPHGLDWH
.
Assign
.
,QIR

The Length Indicator field (octet 2) indicates in binary the remaining length of the element (octets 3-25).
The Full Immediate Assign Info field (octets 3-25) contains a complete immediate assign message (IMMEDIATE
ASSIGN or IMMEDIATE ASSIGN EXTENDED or IMMEDIATE ASSIGN REJECT) as defined in GSM 04.08.
9.3.36
SMSCB Information
This element is used to convey a complete frame to be broadcast on the CBCH including the Layer 2 header for
the radio path.
8
(OHPHQWLGHQWLILHU

606&%IUDPH
.
.

9.3.37
MS Timing Offset
The information is coded in two octets and contains the MS Timing Offset as measured by the BTS.
8
(OHPHQWLGHQWLILHU
7LPLQJ2IIVHW
The meaning of the MS Timing Offset is as defined in GSM 05.10. The value of MS Timing Offset is the binary
value of the 8-bit Timing Offset field (octet 2) - 63. The range of MS Timing Offset is therefore -63 to 192.
Exercises
179 (199)

9.3.38
Erroneous Message
This information element is used to carry a complete A-bis interface message which was considered erroneous at
reception.
8
(OHPHQWLGHQWLILHU
/HQJWK

.
Received Message
.

1
The Received Message field contains a complete A-bis interface L3 message as defined in clause 8 of this GTS,
including Message Discriminator and Message Type.
9.3.39
Full BCCH Information (message name)
This information element contains a complete L3 message as specified in GSM 04.08.

8
(OHPHQWLGHQWLILHU
/HQJWK,QGLFDWRU
/D\HUPHVVDJH

DV

.
defined
.

LQ*60*60
The Length Indicator field (octet 2) indicates in binary the remaining length of the element (octets 3-25). The most
significant bit is bit 8 of octet 2 and the least significant bit is bit 1 of octet 2.
Octets 3-25 contain the complete L3 message as defined in GSM 04.08. In the message format section, the
GSM 04.08 message name to be included is indicated within brackets.
9.3.40
Channel Needed
This information element is used to indicate to the mobile station which channel will be needed for the transaction
linked to the paging procedure.
8
(OHPHQWLGHQWLILHU
5HVHUYHGIRUIXWXUHXVH &KDQQHO
The Channel Field (bits 1-2 of octet 2) indicates the further combination of channel which will be needed. It is coded
as follows:
Exercises
180 (199)

Value
00
01
10
11
9.3.41
Channel Needed.
Any Channel.
SDCCH.
TCH/F (Full rate).
TCH/F or TCH/H (Dual rate).
CB Command type
This element is used to indicate the type of broadcast requested.

8

(OHPHQWLGHQWLILHU

&RPPDQG'HIDXOW/DVW%ORFN
%URDGFDVW6SDUH

The Command Field (bits 5 to 8) indicates the command to be performed. It is coded as follows:
Value
Command
0000
1000
1110
1111
Normal message Broadcast.

Schedule message Broadcast.
Default message Broadcast.
Null message Broadcast.

When the Command Field is different from the value 1110 (Default message Broadcast), the BTS uses the SMSCB
message IE together with the Command Field and the Last Block Field to build the blocks sent on the Radio
interface, as defined by GSM 04.12. In that case bit 4 is ignored.
When the Command Field takes the value 1110 (Default message Broadcast), the BTS uses the SMSCB message
IE together with the Default Broadcast Field and the Last Block Field to build the blocks sent on the Radio interface,
as defined by GSM 04.12.
The Default Broadcast Field (bit 4) is coded as follows:
Value
Default message to be broadcast
0
1
Normal message.
Null message.
The BTS uses the Last Block Field to signal to the MS the last block containing useful information as defined by
GSM 04.12. This Field (bits 1 and 2) is coded as follows:
Value
Last Block containing useful information
00
01
10
11
Block 4
Block 1
Block 2
Block 3
Exercises
181 (199)

9.3.42
SMSCB Message
This element is used to convey the message to be broadcast on the CBCH.

8

(OHPHQWLGHQWLILHU

/HQJWK

606&%0HVVDJH

.
.

1

9.3.43
This information element is used to indicate to the BSC the load situation of CBCH in the BTS.
8
CBCH
Load
Type
Spare
4
3
Element identifier
Message Slot Count
The CBCH Load Type field (bit 8 of octet 2) indicates either an underflow or an overflow situation of the CBCH in
the BTS. It is coded as follows:
Value
0
1
CBCH Load Type

Underflow
Overflow
The Message Slot Count field (bits 1-4 of octet 2) indicates either the amount of SMSCB messages that are
needed immediately by BTS or the amount of delay in message slots that is needed immediately by BTS
depending on the value of the CBCH Load Type field. It is coded as follows:
CBCH Load Type
0
1
9.3.44
Message Slot Count

indicates the amount of SMSCB messages (1-15) that are needed immediately by
BTS
indicates the amount of delay in message slots (1-15) that is needed immediately
by BTS.
This element is used to indicate the CB channel [see GSM 05.02] to be used for broadcasting the data.
8
7
Spare
5
4
3
2
Element identifier
Channel Ind
1
1
2
This element is used to indicate the CB channel to be used for broadcasting the data. The Channel Ind field is
coded as follows:
Value Channel Ind
0 0 0 0 Basic CBCH
0 0 0 1 Extended CBCH (supporting the extended CBCH by the network or MSs is optional)
all other values are reserved.
9.3.45
Group call reference
It is coded as follows:
Exercises
182 (199)

8

(OHPHQWLGHQWLILHU

/HQJWK

'HVFULSWLYHJURXSRUEURDGFDVWFDOOUHIHUHQFH

The octets 3 to 8 are coded in the same way as the octets 1-6 in the Descriptive group or broadcast call reference
information element as defined in GSM 04.08.
9.3.46
Channel description
This is a variable length element used to pass a radio interface information element from BSC to BTS.
8

(OHPHQWLGHQWLILHU

/HQJWK

*URXS&KDQQHO'HVFULSWLRQ Q

Octet j (j = 3, 4, ..., n) is the unchanged octet j-2 of a radio interface Group Channel description information element
as defined in GSM 04.08, n-2 is equal to the length of the radio interface Group channel description information
element.
9.3.47
NCH DRX information
This is a variable length element used to pass a radio interface information element from BSC to BTS.
8

(OHPHQWLGHQWLILHU

/HQJWK

1&+'5;LQIRUPDWLRQ

Octet 3 bits 1 and 2 are bits 1 and 2 of the radio interface NLN as defined in GSM 04.08.
Octet 3 bits 3, 4 and 5 are bits 1, 2 and 3 of the radio interface eMLPP priority as defined in GSM 04.08.
Octet 3 bit 6 is the NLN status parameter as defined in GSM 04.08.
Octet 3 bits 7 and 8 are spare and set to zero.
9.3.48
Command indicator
8

(OHPHQWLGHQWLILHU

/HQJWK

(&RPPDQG9DOXH

&RPPDQG([WHQVLRQ D

The Command Value is a single octet field (octet 3) if the extension bit E (bit 8) is set to 0. If it is set to 1 then the
Command value is a 2 octet field (octets 3 and 3a).
COMMAND VALUES:
Exercises
183 (199)

Value
0
0
0
0
1
0
0
0
:
0
0
0
0
:
0
0
0
0
:
0
0
0
0
:
0
0
0
1
:
0
0
1
0
:
0
1 0 0 0 0 0 1
1 : : : : : :
1 1 1 1 1 1 1
9.3.49
&RPPDQG

6WDUW
6WRS


eMLPP Priority
This Information Element contains the eMLPP priority of the call.

8

(OHPHQWLGHQWLILHU

VSDUH FDOOSULRULW\

The call priority field (bit 3 to 1 of octet 2) is coded in the same way as the call priority field (bit 3 to 1 of octet 5) in
the Descriptive group or broadcast call reference information element as defined in GSM 04.08.
9.3.50
UIC
8

(OHPHQWLGHQWLILHU

/HQJWK

8,&LQIRUPDWLRQ

Octet 3 bits 1 to 6 contain the radio interface octet 2 bits 3 to 8 of the UIC information element as defined in
GSM 04.08.
Octet 3 bits 7 and 8 are spare and set to zero.
9.3.51
Main channel reference
This element contains the main channel reference of a multislot connection.

It is coded in two octets as follows:
8
(OHPHQWLGHQWLILHU
5HVHUYHGIRUIXWXUHXVH 71
TN is timeslot number, binary represented as in GSM 05.02.
Exercises
184 (199)
Draft prETS 300 939 (GSM 04.07 Version 5.3.0): January 1998

11.2
Standard L3 messages
11.2.1
Components of a standard L3 message
A standard L3 message consists of an imperative part, itself composed of a header and the rest of imperative part,
followed by a non-imperative part. Both the non-header part of the imperative part and the non-imperative part are
composed of successive parts referred to as standard information elements.
11.2.1.1
Format of standard information elements
A standard IE may have the following parts, in that order:

-
an information element identifier (IEI);

a length indicator (LI);
a value part.
A standard IE has one of the formats shown in table 11.1:

Table 11.1: Formats of information elements
Format
T
V
TV
LV
TLV
Meaning
Type only
Value only
Type and Value
Length and Value
Type, Length and Value
IEI present
yes
no
yes
no
yes
LI present
no
no
no
yes
yes
Value part present

no
yes
yes
yes
yes
Some IEs may appear in the structure, but not in all instances of messages. An IE is then said to be present or not
present in the message instance. If an IE is not present in a message instance, none of the three parts is present.
Otherwise, parts must be present according to the IE format.
In the message structure, an IE that is allowed not to be present in all message instances is said not to be
mandatory. Other IEs are said to be mandatory.
11.2.1.1.1
Information element type and value part
Every standard IE has an information element type which determines the values possible for the value part of the
IE, and the basic meaning of the information. The information element type describes only the value part. Standard
IEs of the same information element type may appear with different formats. The format used for a given standard
IE in a given message is specified within the description of the message.
The value part of a standard IE either consists of a half octet or one or more octets; the value part of a standard IE
with format LV or TLV consists of an integral number of octets, between 0 and 255 inclusive ; it then may be empty,
i.e., consist of zero octets; if it consists of a half octet and has format TV, its IEI consists of a half octet, too. The
value part of a standard IE may be further structured into parts, called fields.
11.2.1.1.2
Length indicator
When present, the LI of a standard IE consists of one octet. It contains the binary encoding of the number of octets
of the IE value part. The length indicator of a standard IE with empty value part indicates 0 octets. Standard IE of
an information element type such that the possible values may have different values must be formatted with a
length field, i.e., LV or TLV.
11.2.1.1.3
Information element identifier
When present, the IEI of a standard IE consists of a half octet or one octet. A standard IE with IEI consisting of a
half octet has format TV, and its value part consists of a half octet. The value of the IEI depends on the standard IE,
Exercises
185 (199)
Draft prETS 300 939 (GSM 04.07 Version 5.3.0): January 1998
not on its information element type. The IEI, if any, of a given standard IE in a given message is specified within the
description of the message. In some protocol specifications, default IEI values can be indicated. They are to be
used if not indicated in the message specification. Non mandatory standard IE in a given message, i.e., IE which
may be not be present (formally, for which the null string is acceptable in the message), must be formatted with an
IEI, i.e., with format T, TV or TLV.
Exercises
186 (199)
Draft prETS 300 940 (GSM 04.08 version 5.13.0 Release 1996): July 1999
Message functional definitions and contents
This section defines the structure of the messages of those layer 3 protocols defined in GSM 04.08. These are
standard L3 messages as defined in GSM 04.07 with the exception of those sent on the SCH, RACH, and the
HANDOVER ACCESS message.
Each definition given in the present section includes:
a)
a brief description of the message direction and use, including whether the message has:
1.
2.
3.
4.
b)
Local significance, i.e. relevant only on the originating or terminating access;

Access significance, i.e. relevant in the originating and terminating access, but not in the network;
Dual significance, i.e. relevant in either the originating or terminating access and in the network; or
Global significance, i.e. relevant in the originating and terminating access and in the network.
a table listing the information elements known in the message and their order of their appearance in the
message. In messages for circuit-switched call control also a shift information element shall be considered
as known even if not included in the table. All information elements that may be repeated are explicitly
indicated. ( V and LV formatted IEs, which compose the imperative part of the message, occur before T, TV,
and TLV formatted IEs which compose the non-imperative part of the message, cf. GSM 04.07.) In a
(maximal) sequence of consecutive information elements with half octet length, the first information element
with half octet length occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of
octet N+1 etc. Such a sequence always has an even number of elements.
For each information element the table indicates:
1.
NOTE
3.
4.
5.
6.
c)
the information element identifier, in hexadecimal notation, if the IE has format T, TV, or TLV. Usually,
there is a default IEI for an information element type; default IEIs of different IE types of the same
protocol are different. If the IEI has half octet length, it is specified by a notation representing the IEI as
a hexadecimal digit followed by a "-" (example: B-).
The same IEI may be used for different information element types in different messages of the
same protocol.2. The name of the information element (which may give an idea of the
semantics of the element). The name of the information element (usually written in italics)
followed by "IE" or "information element" is used in GSM 04.08 as reference to the information
element within a message.
the name of the type of the information element (which indicates the coding of the value part of the IE),
and generally, the referenced sub-section of section 10 of GSM 04.08 describing the value part of the
information element.
the presence requirement indication (M, C, or O) for the IE as defined in GSM 04.07.
The format of the information element (T, V, TV, LV, TLV) as defined in GSM 04.07.
The length of the information element (or permissible range of lengths), in octets, in the message,
where "?" means that the maximum length of the IE is only constrained by link layer protocol, and in
the case of the Facility IE by possible further conditions specified in GSM 04.10. This indication is nonnormative.
sub-sections specifying, where appropriate, conditions for IEs with presence requirement C or O in the
relevant message which together with other conditions specified in GSM 04.08 define when the information
elements shall be included or not, what non-presence of such IEs means, and - for IEs with presence
requirement C - the static conditions for presence and/or non-presence of the IEs (cf. GSM 04.07).
Exercises
187 (199)
9.1.8
Channel request
This message is sent in random mode on the RACH. It does not follow the basic format. The possible formats are
presented directly below, without reference to information fields. The order of bit transmission is defined in
GSM 04.04.
The message is only one octet long, coded as shown in figure 9.1/GSM 4.08 and table 9.9/GSM 04.08.
8
(67$%/,6+0(17 5$1'20
RFWHW
&$86( 5()(5(1&(
Figure 9.1/GSM 04.08: CHANNEL REQUEST message content
ESTABLISHMENT CAUSE (octet 1)
This information field indicates the reason for requesting the establishment of a connection. This field has a
variable length (from 3 bits up to 6 bits).
RANDOM REFERENCE (octet 1)
This is an unformatted field with variable length (from 5 bits down to 2 bits).
The Channel Request message is coded as follows:
(Random Reference field is filled with "x").
Table 9.9/GSM 04.08: CHANNEL REQUEST message content
MS codes
bits
8 .... 1
101xxxxx
110xxxxx
011010xx
011011xx
100xxxxx
0010xxxx
0011xxxx
0001xxxx
111xxxxx
0100xxxx
0101xxxx
000xxxxx
0000xxxx
0001xxxx
01100xxx
0111xxxx
NOTE 1:
According to Establishment cause:
Emergency call
Call re-establishment; TCH/F was in use, or
TCH/H was in use but the network does not
set NECI bit to 1
Call re-establishment; TCH/H was in use and the
network sets NECI bit to 1
Call re-establishment; TCH/H + TCH/H was in use
and the network sets NECI bit to 1
Answer to paging
See table 9.9a/GSM 04.08
Originating call and TCH/F is needed, or originating call
and the network does not set NECI bit to 1, or
procedures that can be completed with a SDCCH and the
network does not set NECI bit to 1.
note 1
Originating speech call from dual-rate mobile station when TCH/H
is sufficient and supported by the MS for speech calls and the network
sets NECI bit to 1
note 5
Originating data call from dual-rate mobile station when TCH/H
is sufficient and supported by the MS for data calls and the network sets
NECI bit to 1
note 5
Location updating and the network does not set NECI bit to 1
Location updating and the network sets NECI bit to 1
Other procedures which can be completed with
note 1
an SDCCH and the network sets NECI bit to 1
Reserved for future use
note 2
Examples of these procedures are: IMSI detach, Short Message Service (SMS), Supplementary
Service management.
Exercises
188 (199)
NOTE 2:
If such messages are received by a network, an SDCCH may be allocated.
Table 9.9a/GSM 04.08: CHANNEL REQUEST message (when answering to paging)

06&DSDELOLW\

3DJLQJ
,QGLFDWLRQ

)XOOUDWH
RQO\

'XDO
UDWH
QRWH

6'&&+
RQO\
$Q\FKDQQHO [[[[[ [[[[[ [[[[[

6'&&+ [[[[ [[[[ [[[[
7&+) [[[[[ [[[[ [[[[
7&++RU7&+) [[[[[ [[[[ [[[[
9.1.9
NOTE 3:
The Paging Indication is provided by the Channel Needed IE (or the Channel Needed field)
associated with the page which triggered the sending of the CHANNEL REQUEST message.
NOTE 4:
In some cases the established connection will be used only to allow a default rejection
mechanism to take place (typically the mobile station will send a RELEASE COMPLETE
message with cause #88 "incompatible destination" as an answer to the incoming SETUP
message).
NOTE 5:
In this section, dual rate capability means that the MS supports both full rate and half-rate
channels at least for the signalling channel mode. In addition, it may support either speech
channel mode, or data channel modes, or both on half-rate channels.
Ciphering mode command
This message is sent on the main DCCH from the network to the mobile station to indicate that the network has
started deciphering and that enciphering and deciphering shall be started in the mobile station, or to indicate that
ciphering will not be performed. See table 9.10/GSM 04.08.
Message type:CIPHERING MODE COMMAND
Significance:
dual
Direction:
network to mobile station
Table 9.10/GSM 04.08: CIPHERING MODE COMMAND message content
IEI
Information element
RR management
Protocol Discriminator
Skip Indicator
Cipher Mode Command
Message Type
Ciphering Mode Setting
Cipher Response
9.1.10
Type / Reference
10.2
Skip Indicator
10.3.1
Message Type
10.4
Cipher Mode Setting
10.5.2.9
Cipher Response
10.5.2.10
Presence
M
Format
V
length
1/2
1/2
1/2
1/2
Ciphering mode complete
This message is sent on the main DCCH from the mobile station to the network to indicate that enciphering and
deciphering has been started in the MS. See table 9.11/GSM 04.08.
Message type:CIPHERING MODE COMPLETE
Significance:
dual
Direction:
mobile station to network
Exercises
189 (199)
Table 9.11/GSM 04.08: CIPHERING MODE COMPLETE message content
IEI
17
Information element
RR management
Skip Indicator
Cipher Mode Complete
Message Type
Mobile Equipment
Identity
9.1.10.1
Type / Reference
10.2
Skip Indicator
10.3.1
Message Type
10.4
Mobile Identity
10.5.1.4
Presence
M
Format
V
length
1/2
1/2
TLV
3-11
Mobile Equipment Identity
This information element is included if and only if the mobile station shall include its IMEISV (see section 3.4.7).
This information element shall only refer to IMEISV.
Exercises
190 (199)
10
General message format and information elements coding
The figures and text in this section describe the Information Elements content.
10.1
Overview
Within the Layer 3 protocols defined in GSM 04.08, every message with the exception of the messages sent on the
BCCH, downlink CCCH, SCH, RACH, and the HANDOVER ACCESS message, is a standard L3 message as
defined in GSM 04.07. This means that the message consists of the following parts:
a)
b)
c)
d)
protocol discriminator;
transaction identifier;
message type;
other information elements, as required.
This organization is illustrated in the example shown in figure 10.1/GSM 04.08.

8
7UDQVDFWLRQLGHQWLILHU 3URWRFROGLVFULPLQDWRU RFWHW

RU6NLS,QGLFDWRU
0HVVDJHW\SH RFWHW
2WKHULQIRUPDWLRQHOHPHQWVDVUHTXLUHG HWF

Figure 10.1/GSM 04.08
General message organization example
Unless specified otherwise in the message descriptions of section 9, a particular information element shall not be
present more than once in a given message.
The term "default" implies that the value defined shall be used in the absence of any assignment, or that this value
allows negotiation of alternative values in between the two peer entities.
When a field extends over more than one octet, the order of bit values progressively decreases as the octet
number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest
numbered octet of the field.
10.2
The Protocol Discriminator (PD) and its use are defined in GSM 04.07. GSM 04.08 defines the protocols relating to
the PD values:
bits
4321
0011
0101
0110
Call Control; call related SS messages

Mobility Management messages
Radio Resource management messages
except the call related SS procedures, which are defined in GSM 04.10.
10.3
10.3.1
Skip indicator and transaction identifier

Skip indicator
Bits 5 to 8 of the first octet of every Radio Resource management message and Mobility Management message
contains the skip indicator. A message received with skip indicator different from 0000 shall be ignored. A message
received with skip indicator encoded as 0000 shall not be ignored (unless it is ignored for other reasons). A protocol
entity sending a Radio Resource management message or a Mobility Management message shall encode the skip
indicator as 0000.
Exercises
191 (199)
10.3.2
Transaction identifier
Bits 5 to 8 of the first octet of every message belonging to the protocol "Call Control; call related SS messages"
contain the transaction identifier (TI). The transaction identifier and its use are defined in GSM 04.07.
10.4
Message Type
The message type IE and its use are defined in GSM 04.07. Tables 10.3/GSM 04.08, 10.4/GSM 04.08, and
10.5/GSM 04.08 define the value part of the message type IE used in the Radio Resource management protocol,
the Mobility Management protocol, and the Call Control protocol.
Table 10.1/GSM 04.08 (page 1 of 2): Message types for Radio Resource management

&KDQQHOHVWDEOLVKPHQWPHVVDJHV
$'',7,21$/$66,*10(17
,00(',$7($66,*10(17
,00(',$7($66,*10(17(;7(1'('
,00(',$7($66,*10(175(-(&7

&LSKHULQJPHVVDJHV
&,3+(5,1*02'(&200$1'
&,3+(5,1*02'(&203/(7(

&RQILJXUDWLRQFKDQJHPHVVDJHV
&21),*85$7,21&+$1*(&200$1'
&21),*85$7,21&+$1*($&.
&21),*85$7,21&+$1*(5(-(&7

+DQGRYHUPHVVDJHV
$66,*10(17&200$1'
$66,*10(17&203/(7(
$66,*10(17)$,/85(
+$1'29(5&200$1'
+$1'29(5&203/(7(
+$1'29(5)$,/85(
3+<6,&$/,1)250$7,21

&KDQQHOUHOHDVHPHVVDJHV
&+$11(/5(/($6(
3$57,$/5(/($6(
3$57,$/5(/($6(&203/(7(

3DJLQJDQG1RWLILFDWLRQPHVVDJHV
3$*,1*5(48(677<3(
3$*,1*5(48(677<3(
3$*,1*5(48(677<3(
3$*,1*5(63216(
127,),&$7,211&+
127,),&$7,21)$&&+
5HVHUYHGVHH127(
5HVHUYHGVHH127(
NOTE:
(continued...)
This value was allocated but never used in earlier phases of the protocol.
Exercises
192 (199)
Table 10.1/GSM 04.08 (page 2 of 2): Message types for Radio Resource management

6\VWHPLQIRUPDWLRQPHVVDJHV
6<67(0,1)250$7,217<3(
6<67(0,1)250$7,217<3(
6<67(0,1)250$7,217<3(
6<67(0,1)250$7,217<3(
6<67(0,1)250$7,217<3(
6<67(0,1)250$7,217<3(
6<67(0,1)250$7,217<3(
6<67(0,1)250$7,217<3(

6\VWHPLQIRUPDWLRQPHVVDJHV
6<67(0,1)250$7,217<3(ELV
6<67(0,1)250$7,217<3(WHU
6<67(0,1)250$7,217<3(ELV
6<67(0,1)250$7,217<3(WHU
6<67(0,1)250$7,217<3(

0LVFHOODQHRXVPHVVDJHV
&+$11(/02'(02',)<
5567$786
&+$11(/02'(02',)<$&.12:/('*(
)5(48(1&<5('(),1,7,21
0($685(0(175(3257
&/$660$5.&+$1*(
&/$660$5.(148,5<
(;7(1'('0($685(0(175(3257
0 1 1 0 1 1 1 - EXTENDED MEASUREMENT ORDER

9*&6XSOLQNFRQWUROPHVVDJHV

9*&683/,1.*5$17
83/,1.5(/($6(
83/,1.)5((
83/,1.%86<
7$/.(5,1',&$7,21
Bit 8 is reserved for possible future use as an extension bit, see GSM 04.07.
Exercises
193 (199)
Table 10.2/GSM 04.08: Message types for Mobility Management

[5HJLVWUDWLRQPHVVDJHV
,06,'(7$&+,1',&$7,21
/2&$7,2183'$7,1*$&&(37
/2&$7,2183'$7,1*5(-(&7
/2&$7,2183'$7,1*5(48(67

[6HFXULW\PHVVDJHV
$87+(17,&$7,215(-(&7
$87+(17,&$7,215(48(67
$87+(17,&$7,215(63216(
,'(17,7<5(48(67
,'(17,7<5(63216(
706,5($//2&$7,21&200$1'
706,5($//2&$7,21&203/(7(

[&RQQHFWLRQPDQDJHPHQWPHVVDJHV
&06(59,&($&&(37
&06(59,&(5(-(&7
&06(59,&($%257
&06(59,&(5(48(67
&06(59,&(352037
127,),&$7,215(63216(
&05((67$%/,6+0(175(48(67
$%257

[0LVFHOODQHRXVPHVVDJHV
0018//
0067$786
00,1)250$7,21
Bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from
the network, bit 7 is coded with a "0". See GSM 04.07.
Exercises
194 (199)
Table 10.3/GSM 04.08: Message types for Call Control and call related SS messages

[HVFDSHWRQDWLRQDOO\VSHFLILF
PHVVDJHW\SHVVHHEHORZ

[&DOOHVWDEOLVKPHQWPHVVDJHV
$/(57,1*
&$//&21),50('
&$//352&((',1*
&211(&7
&211(&7$&.12:/('*(
(0(5*(1&<6(783
352*5(66
&&(67$%/,6+0(17
&&(67$%/,6+0(17&21),50('
5(&$//
67$57&&
6(783

[&DOOLQIRUPDWLRQSKDVHPHVVDJHV
02',)<
02',)<&203/(7(
02',)<5(-(&7
86(5,1)250$7,21
+2/'
+2/'$&.12:/('*(
+2/'5(-(&7
5(75,(9(
5(75,(9($&.12:/('*(
5(75,(9(5(-(&7

[&DOOFOHDULQJPHVVDJHV
',6&211(&7
5(/($6(
5(/($6(&203/(7(

[0LVFHOODQHRXVPHVVDJHV
&21*(67,21&21752/
127,)<
67$786
67$786(148,5<
67$57'70)
6723'70)
6723'70)$&.12:/('*(
67$57'70)$&.12:/('*(
67$57'70)5(-(&7
)$&,/,7<
1):
When used, the message type is defined in the following octet(s), according to the national
specification.
Bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from
the network, bit 7 is coded with a "0". See GSM 04.07.
10.5
Other information elements
The different formats (V, LV, T, TV, TLV) and the four categories of information elements (type 1, 2, 3, and 4) are
defined in GSM 04.07.
The first octet of an information element in the non-imperative part contains the IEI of the information element. If
this octet does not correspond to an IEI known in the message (see GSM 04.07), the receiver shall assume that the
information element is:
-
if bit 8 of the first octet of the IE has the value 1, the IE is of type 1 or 2, i.e. that it is an information element
of one octet length; or
Exercises
195 (199)
-
if bit 8 of the first octet of the IE has the value 0, the IE is of type 4, i.e. that the next octet is the length
indicator indicating the length of the remainder of the information element. If in this case bits 5, 6, and 7 of
the first octet of the IE also have the value 0, the IE is encoded as "comprehension required".
NOTE:
The handling of messages containing unknown IEs encoded as "comprehension required" is

specified in section 8.
This rule allows the receiver to jump over unknown information elements and to analyse any following information
elements.
The information elements which are common for at least two of the three protocols Radio Resources management,
Mobility Management and Call Control, are listed in section 10.5.1.
The information elements for the protocols Radio Resources management, Mobility Management and Call Control
are listed in sections 10.5.2, 10.5.3 and 10.5.4 respectively. Default information element identifiers are listed in
annex K.
NOTE:
Different information elements may have the same default information element identifier if they
belong to different protocols.
The descriptions of the information element types in sections 10.5.1, 10.5.2, 10.5.3, and 10.5.4 are organized in
alphabetical order of the IE types. Each IE type is described in one sub-section.
The sub-section may have an introduction:
-
possibly explaining the purpose of the IE;
possibly describing whether the IE belongs to type 1, 2, 3, 4 or 5;
possibly indicating the length that the information element has if it is either type 5 or if it is used in format TV
(type 1 and 3) or TLV (type 4).
A figure of the sub-section defines the structure of the IE indicating:

-
possibly the position and length of the IEI. (However it depends on the message in which the IE occurs
whether the IE contains an IEI.);
the fields that IE value part is composed of;
possibly the position and length of the length indicator. (However it depends on the IE type whether the IE
contains a length indicator or not.);
possibly octet numbers of the octets that compose the IE (see clause a) below).
Finally, the sub-section contains tables defining the structure and value range of the fields that compose the IE
value part. The order of appearance for information elements in a message is defined in section 9.
The order of the information elements within the imperative part of messages has been chosen so that information
elements with 1/2 octet of content (type 1) go together in succession. The first type 1 information element occupies
bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N + 1 etc. If the number of type 1
information elements is odd then bits 5 to 8 of the last octet occupied by these information elements contains a
spare half octet IE in format V.
Where the description of information elements in this Technical Specification contains bits defined to be "spare
bits", these bits will be set to the indicated value (0 or 1) by the sending side, and their value will be ignored by the
receiving side. With few exceptions, spare bits are indicated as being set to "0" in GSM 04.08.
The following rules apply to the coding of type 4 information elements:
a)
The octet number of an octet (which is defined in the figure of a sub-section) consists of a positive integer,
possibly of an additional letter, and possibly of an additional asterisk, see clause f). The positive integer
identifies one octet or a group of octets.
Exercises
196 (199)
b)
Each octet group is a self contained entity. The internal structure of an octet group may be defined in
alternative ways.
c)
An octet group is formed by using some extension mechanism. The preferred extension mechanism is to
extend an octet (N) through the next octet(s) (Na, Nb, etc.) by using bit 8 in each octet as an extension bit.
The bit value "0" indicates that the octet group continues through to the next octet. The bit value "1" indicates
that this octet is the last octet of the group. If one octet (Nb) is present, the preceding octets (N and Na) shall
also be present.
In the format descriptions appearing in section 10.5.1 to 10.5.4, bit 8 is marked "0/1 ext" if another octet
follows. Bit 8 is marked "1 ext" if this is the last octet in the extension domain.
Additional octets may be defined in later versions of the protocols ("1 ext" changed to "0/1 ext") and
equipment will be prepared to receive such additional octets; the contents of these octets will be ignored.
However the length indicated in sections 9 and 10 only takes into account this version of the protocols.
d)
In addition to the extension mechanism defined above, an octet (N) may be extended through the next
octet(s) (N+1, N+2 etc.) by indications in bits 7-1 (of octet N).
e)
The mechanisms in c) and d) may be combined.
f)
Optional octets are marked with asterisks (*).
10.5.1
10.5.1.1
Common information elements.

Cell identity
The purpose of the Cell Identity information element is to identify a cell within a location area.
The Cell Identity information element is coded as shown in figure 10.2/GSM 04.08 and table 10.5/GSM 04.08.
The Cell Identity is a type 3 information element with 3 octets length.
8
&HOO,GHQWLW\,(, RFWHW

&,YDOXH RFWHW

&,YDOXHFRQWLQXHG RFWHW
Cell Identity information element
Table 10.5/GSM 04.08: Cell Identity information element

&,YDOXH&HOOLGHQWLW\YDOXHRFWHWDQG

,QWKH&,YDOXHILHOGELWRIRFWHWLVWKHPRVW
VLJQLILFDQWELWDQGELWRIRFWHWWKHOHDVW
VLJQLILFDQWELW

7KHFRGLQJRIWKHFHOOLGHQWLW\LVWKH
UHVSRQVLELOLW\RIHDFKDGPLQLVWUDWLRQ&RGLQJ
XVLQJIXOOKH[DGHFLPDOUHSUHVHQWDWLRQPD\EHXVHG
7KHFHOOLGHQWLW\FRQVLVWVRIRFWHWV
Exercises
197 (199)
10.5.2.9
Cipher Mode Setting
The purpose of the Cipher Mode Setting information element is to indicate whether stream ciphering will be started
or not and if it is to be started, which algorithm to use.
The Cipher Mode Setting information element is coded as shown in figure 10.23/GSM 04.08 and
table 10.27/GSM 04.08.
The Cipher Mode Setting is a type 1 information element.
8
DOJRULWKP RFWHW

&LSK0RG6HW,(, LGHQWLILHU 6&
Cipher Mode Setting information element
Table 10.27/GSM 04.08: Cipher Mode Setting information element

DOJRULWKPLGHQWLILHU
,I6& WKHQ
ELWV

FLSKHUZLWKDOJRULWKP$
UHVHUYHG

,I6& WKHQELWVDQGDUHVSDUHDQGVHWWR

6&RFWHW
%LW

1RFLSKHULQJ
6WDUWFLSKHULQJ
10.5.2.10
Cipher Response
The Cipher Response information element is used by the network to indicate to the mobile station which
information the mobile station has to include in the CIPHERING MODE COMPLETE message.
The Cipher Response
table 10.28/GSM 04.08.
information
element
is
coded
as
shown
in
figure 10.24/GSM 04.08
and
The Cipher Response is a type 1 information element.

8
RFWHW

&LSKHU5HVS,(, 6SDUH &5
Cipher Response information element
Exercises
198 (199)
Table 10.28/GSM 04.08: Cipher Response information element
&5&LSKHU5HVSRQVHRFWHW
%LW

,0(,69VKDOOQRWEHLQFOXGHG
,0(,69VKDOOEHLQFOXGHG
Exercises
199 (199)

03814

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

03814

Transféré par

Droits d'auteur :

Formats disponibles

EXERCISES

Uppgjord (ven faktaansvarig om annan) - Prepared (also subject responsible if other)

KI/ERA/GD/UX Iwona Maksymowicz

GSM ADVANCED SYSTEM TECHNIQUE

TRAFFIC CASES, GROUP EXERCISE

DECODING OF AN ABIS MESSAGE

DECODING OF THE MSU

ABIS, PROTOCOL ANALYZER

A INTERFACE, PROTOCOL ANALYZER

NETWORK SERVICE PART (NSP)

SCCP USER INFORMATION

KI/ERA/GD/UX Iwona Maksymowicz

EXTRACT FROM GSM 05.02

EXTRACT FROM GSM 05.10

EXTRACT FROM GSM 08.58

EXTRACT FROM GSM 04.07

EXTRACT FROM GSM 04.08

KI/ERA/GD/UX Iwona Maksymowicz

2. How many control channels are there?

3. Name at least three of the control channels.

5. Why is the access burst special?

KI/ERA/GD/UX Iwona Maksymowicz

6. What physical channels (frequency/timeslot) are the following

10. A mobile is idle, tuned to the BCCH channel. The subscriber

KI/ERA/GD/UX Iwona Maksymowicz

Traffic Cases, Group Exercise

Describe the signaling procedure for the following traffic cases:

B. International mobile to mobile call

C. Mobile to mobile SMS

D. International inter MSC handover

KI/ERA/GD/UX Iwona Maksymowicz

KI/ERA/GD/UX Iwona Maksymowicz

4. On what frequencies and what timeslots are PCH and RACH

KI/ERA/GD/UX Iwona Maksymowicz

5. On SCH reduced TDMA frame number is used. This is described

KI/ERA/GD/UX Iwona Maksymowicz

Choose Log, and then Replay logfile, see figure 1 below

A window like the one below turns up.

KI/ERA/GD/UX Iwona Maksymowicz

Choose Monitor, and then Layer 3 messages, see figure 4 below

To be able to see the details of a Layer 3 message, click on it as figure 6 is showing.

This CHANNEL REQUEST

KI/ERA/GD/UX Iwona Maksymowicz

c) Sub channel number:

3. Look at the message LOCATION UPDATING REQUEST.

4. Complete the example below, so it reflects this location updating.

(Logical Channel used, NOT shown by TEMS)

UL: CHANNEL REQUEST

DL: LOCATION UPDATING ACCEPT

DL: CHANNEL RELEASE

KI/ERA/GD/UX Iwona Maksymowicz

c) Which neighboring frequencies is the MS measuring on in Idle mode? These frequencies

KI/ERA/GD/UX Iwona Maksymowicz

Choose in the menu Monitor, Layer 2 Messages (see figure 4)

Press Restart in the Log replay control-window.

Close this file.

KI/ERA/GD/UX Iwona Maksymowicz

Replay the file that contains a call

Monitor Layer 3 messages only (see figure 4).

Go to the message ASSIGNMENT COMMAND (see figure 5).

Close this file

KI/ERA/GD/UX Iwona Maksymowicz

Extra Exercise (if time allows)