CODICE-DATA-P0

GSM Normal Burst Formatting

Example (Full Rate)

Figure show the GSMK case. Behaviour in 8PSK is similar, but with higher bits are used.

Note: Green refers to TS 0.

See coverpage for conditions on the use of this document 0

 CODICE-DATA-P1

channel coding
signalling channel SCCH, FACCH, SDCCH, BCCH, PCH, AGCH + SCH and RACH

SCCH, FACCH,
SDCCH, BCCH,
PCH, AGCH

RACH
SCH

See coverpage for conditions on the use of this document

1
 CODICE-DATA-P2

Coding/Interleaving for SDCCH

1 message for User having SDCCH 0 assigned

1 encoded message for 1 user

Normal Burst Normal Burst

Normal Burst Normal Burst

SDCCH 0

SDCCH 0

SDCCH 0

SDCCH 0
See coverpage for conditions on the use of this document
2
 CODICE-DATA-P3

GPRS Channel Coding

CS1, CS2 and CS3

The first step of the coding procedure is to add a Block Check Sequence (BCS) for error detection obtaining Radio Block.
USF in Mac Header is kept as it is.

USF

MAC header RLC header RLC data unit Spare bits

Radio Block
Nota 1 USF BCS

Convolutional encoding

puncturing

456 bit
Nota 1. in CS2  CS4 3 USF bits are pre-encoded to 12 bit;

See coverpage for conditions on the use of this document

3
 CODICE-DATA-P4

GPRS Channel Coding

CS4

USF

MAC header RLC header RLC data unit Spare bits

Radio Block
USF BCS
Block
coding
No coding

456 bit

See coverpage for conditions on the use of this document

4
 CODICE-DATA-P5

EGPRS Channel Coding

MCS-9
• First step of the EGPRS coding procedure, is to add a Block CheckSequence (BCS) to each RLC data block, for error detection

• Second step consists of adding six tail bits (TB) and a 1/3 rate convolutional coding for error correction that is Punctured to
give the desired coding rate

• The Pi (puncturing schemes) for each MCS correspond to different puncturing schemes achieving the same coding rate

• Puncturing is a technique of removing bits in predetermined locations of thedata block after the block has been channel
coded
• MCS-9, MCS-8, MCS-7, MCS-4, MCS-3: are possible P1, P2, and P3
• MCS-6, MCS-5, MCS-2, MCS-1: P1 and P2 are possible

MAC/RLC header FBI/UL E RLC data unit FBI/UL E RLC data unit

See coverpage for conditions on the use of this document

5
 CODICE-DATA-P6

Section 2: LAPDm
Protocol

FUNDAMENTAL

The information contained in this document is the property of Value Team S.p.A. and the addressee of the document. The information is closely linked to the oral comments accompanying the same, and may be used only by those attending the
presentation. Copying, publishing or divulging the material contained in this document is forbidden and may be illegal. 6
 CODICE-DATA-P7

LAPDm overview

MS BSS

Layer 3 Layer 3

L3 Frame

LAPDm Layer LAPDm Layer

(Layer 2) (Layer 2)

LAPDm - Frame L3 Frame

RACH

BCCH

AGCH+PCH

SACCH
RACH

FACCH

SDCCH
BCCH

SACCH
FACCH

SDCCH

AGCH+PCH

4 Normal Bursts or
Physical Layer Access Burst Physical Layer
(Layer 1) (Layer 1)

See coverpage for conditions on the use of this document

7
 CODICE-DATA-P8

LAPDm General
Position in the GSM Protocol stack
• LAPDm forms Layer 2 (Link access layer) of the Um interface between the Base Transceiver Station and Mobile station.

• LAPDm is derived from a much older link layer protocol called HDLC. LAPDm is similar to the ISDN Layer 2, LAPD. In GSM system
LAPD is used over Abis Interface.

Um Abis A

CC/SMS/SS CC/SMS/SS
(24.008) (24.008)

MM MM
(24.008) relay (24.008)

RR BSSAP BSSAP
relay (44.018) (48.008) (48.008)
RR
(44.018)
RR BTSM BTSM
SCCP SCCP
(44.018) (48.058) (48.058)

LAPDm LAPDm
LAPD LAPD MTP MTP
(44.005; 44.006) (44.005; 44.006)

Physical Layer Physical Layer

L1 L1 L1 L1
(45-series) (45-series)

MS BTS BSC MSC

See coverpage for conditions on the use of this document

8
 CODICE-DATA-P9

LAPDm General
3GPP reference specification (http://www.3gpp.org/specification-numbering)
3G and
GSM only (Rel- GSM only
series beyond / GSM
4 and later) (before Rel-4)
(R99 and later)
General information (long defunct) 00 series
Requirements 21 series 41 series 01 series
Service aspects ("stage 1") 22 series 42 series 02 series
Technical realization ("stage 2") 23 series 43 series 03 series

Signalling protocols ("stage 3") - user equipment to network 24 series 44 series 04 series

Radio aspects 25 series 45 series 05 series

CODECs 26 series 46 series 06 series
47 series
Data 27 series 07 series
(none exists)
TS 44.005 Data Link (DL) Layer; General aspects
Signalling protocols ("stage 3") -(RSS-CN) and OAM&P and Charging
(overflow from 32.- range) Mobile 28 series -
Station Base48Station
series System
08 series
(MS - BSS) interface; Data Link (DL)
TS 44.006
layer specification
Signalling protocols ("stage 3") - intra-fixed-network 29 series 49 series 09 series
Programme management 30 series 50 series 10 series
•LAPDm is specified mainly in 3GPP specifications TS 44.005 and 44.006.
Subscriber Identity Module (SIM / USIM), IC Cards. Test specs. 31 series 51 series 11 series
•TS 44.005 describes concepts, terminology, overview description of LAPDm
OAM&P and Charging 32 seriesand the
functions and procedures, 52 series 12 series
relationship with other Technical
Access requirements and test specifications Specifications. 13 series (1) 13 series (1)
Security aspects •TS 44.006 describes33the frame (2)
series structure, format
(2) of fields and procedures for the
UE and (U)SIM test specifications 34 series
proper operation of LAPDm (2) 11 series
Security algorithms (3) 35 series 55 series (4)

LTE (Evolved UTRA) and LTE-Advanced radio technolgy 36 series - -

Multiple radio access technology aspects 37 series - -

See coverpage for conditions on the use of this document

9
 CODICE-DATA-P10

LAPDm services offered to upper layer

• The purpose of LAPDm is to convey information from layer 3 to GSM radio interface sent over RACH, BCCH,
FACCH, SDCCH, AGCH+PCH, SACCH logical channels.

• LAPDm stand for Link Access Procedure on the Dm channel. NOTE The term Dm channel is used for
convenience to designate the collection of all the various signalling channels required in the GSM system.
See also 3GPP TS 44.003

• Data on SAPs of control channels is exchanged in discrete blocks with a size of 23 (21 in case of SACCH)
octets.

• The RR message from upper layer is included in a LAPDm Frame and delivered to Physical Layer.
• For the acknowledged mode of information transfer the data link layer offers segmentation at the
transmitter of layer 3 message units if the message unit is longer than the information field of the
data layer frames. At the receiver the segmented layer 3 message units are concatenated such
that the integrity of the layer 3 message unit is restored.
• For unacknowledged operation the data link layer does not offer segmentation services.

• The LAPDm Frame is managed by physical Layer (encoding, interleaving, chipering, burst building).

See coverpage for conditions on the use of this document 10

 CODICE-DATA-P11

LAPDm
Elementary procedures
• LAPDm supports two modes of operation:
• unacknowledged operation using UI frames
• acknowledged operation using the multiple frame procedure. Entities exchange I-frame after
establishment procedure. At the end a release procedure is executed also.

• For the various channel types the following applies:

• BCCH: unacknowledged operation only;
• CCCH: unacknowledged operation only;
• SACCH: unacknowledged operation only
• SDCCH, FACCH: acknowledged operation only.

The LAPDm frame types are:

• for unacknowledged information transfer (sub-clause 8.3):
UI-command.
• for multiple frame acknowledged information transfer (sub-clauses 8.4 to 8.8):
SABM-command;
UA-response;
DM-response;
DISC-command;
RR-command/response;
RNR-command/response;
REJ-command/response;
I-command

See coverpage for conditions on the use of this document 11

 CODICE-DATA-P12

LAPDm Frame
Frame Format Type

23 octects (21 in case of SACCH)

Format A
(SDCCH, FACCH) Address (1 octects) Control (1 octect) Length Indicator (1 octect) Fill Bits

Format B Fill Bits

Address (1 octects) Control (1 octect) Length Indicator (1 octect) Information
(SDCCH, FACCH)

Format B4
Address (1 octects) Control (1 octect) Information
(Frame on SACCH)

23 octects except SACCH 21 octects

Format Bter Short L2 Header 1 (2bits) Information

(DCCH when applicable)

Format Bbis
Length Indicator (1 octect) Information Fill Bits
(on BCCH, PCH, NCH, AGCH)

Format C
1 octect
(RACH)

See coverpage for conditions on the use of this document

12
 CODICE-DATA-P13

LAPDm Frame
Frame Format Type

All data link layer peer-to-peer exchanges LAPDm Frames . Several format types are defined:
• Format A is used on DCCHs for frames where there is no information field.
• Formats B, Bter and B4 are used on DCCHs for frames containing an information field:
• format Bter is used on request of higher layers if and only if short L2 header type 1 is supported and a UI
command is to be transmitted on SAPI 0;
• format B4 is used for UI frames transmitted by the network on SACCH;
• format B is applied in all other cases.
• Format Bbis is used only on BCCH, PCH, NCH, and AGCH.
• In addition there is a Format C for transmission of random access signals. The format of the random access
message at the data link layer consists of 8 bits. The order of bit transmission is defined in 3GPP TS 44.004.

LAPDm length for format type A, B, B4, Bter, Bbis is 23 octects except SACCH that is 21 octects

See coverpage for conditions on the use of this document

13
 CODICE-DATA-P14

LAPDm Frame
Address Field format

Address field format

The Address field consists of:
• the address field extension bit EA;
• the command/response bit C/R;
• the SAPI (Service Access Point Identifier); only two values are possible:
• SAPI=0 for signaling and
• SAPI=3 for SMS.
• and the Link Protocol Discriminator LPD.
• The Link Protocol Discriminator (LPD) corresponding to the use in this Technical Specification shall LPD =
"0 0", all other values are reserved.
• LPD = "0 1" corresponds to the data link protocol used for SMSCB (see 3GPP TS 44.012).

8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
spare LPD SAPI C/R E/A …

Address Control

See coverpage for conditions on the use of this document 14

 CODICE-DATA-P15

LAPDm Frame
Control field formats
Control field formats
The control field identifies the type of frame, which will be either a command or a response.
The control field will contain sequence numbers, where applicable.
Three types of control field formats are specified:
• numbered information transfer (I format),
• supervisory functions (S format), and
• unnumbered information transfer and control functions (U format).
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
I format frame N(R) P N(S) 0 …
(I-command)
Address Control

8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
S format frame N(R) P/F S S 0 0 …
(RR-command/response;
RNR-command/response; Address Control
REJ-command/response;)
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
U format frame U U U P/F U U 1 1 …
(SABM-command;
UA-response; Address Control
DM-response; N(S) Transmitter send sequence number.
DISC-command N(R) Transmitter receive sequence number.
UI-Command) S Supervisory function bit.
U Unnumbered function bit.
P/F Poll bit, when issued as a command, final bit, when issued as a response

See coverpage for conditions on the use of this document

15
 CODICE-DATA-P16

LAPDm unacknowledged mode of operation

Frame exchange

UI-Frame Exchange
• Entities exchange UI-frame. Establishment/release procedure is not necessary.
• When a layer 3 entity requests unacknowledged information transfer, the UI unnumbered command shall be used to send information
to its peer without affecting data link layer variables.
• UI command frames do not carry a sequence number. Therefore, the UI frame may be lost without notification to the layer 3 entity if a
data link exception occurs during transmission of the command.

MS BTS

e.g. BCCH/CCCH

UI Frame exchange

UI-frame («L3»)

UI-frame («L3»)

Unacknowledged operation

See coverpage for conditions on the use of this document 16

 CODICE-DATA-P17

LAPDm acknowledged mode of operation

SDCCH
Establishment/Release

LAPDm setup handshake MS BTS

The Mobile initiates a LAPm connection with the BTS by sending a Set
Asynchronous Balanced Mode (SABM) message. The L3 Message (e.g. Establishment procedure
service request message or Paging Request) the MSC is also sent in this
message.
SABM-command («L3»)
The BTS replies with Unnumbered Acknowledge (UA) to complete the LAPm
setup handshake. UA-response («L3»)

I-Frame Exchange
Entities exchange I-frame using the so-called “multiple frame procedure”.
Both MS and BTS sends (I) command frames containing L3 message.
Each I frame is sequentially numbered by a sequence number which may
have the value 0 through 7.
I-Frame exchange
Receiver acknowldges Frames. If acknowledge is not received for a specific I-frame («L3»)
frame, Frame is retranmsitted.
I-frame («L3»)
In this way LAPDm ensure layer 3 entity that message is not lost.

Release procedure
DISC-command («L3»)
LAPDm release
The mobile sends a disconnect message to release the LAPm connection. UA-response («L3»)
The BSS replies with an Unnumbered Acknowledge message

Acknowledge operation using multiple frame procedure

See coverpage for conditions on the use of this document

17
 CODICE-DATA-P18

LAPDm vs LAPD

LAPDm
• The length is limited to max 21 octets of information.
• On radio interface two independent flows(one for signaling, and one for SMS) can exist simultaneously. These two flows are
distinguished by a link identifier called the SAPI(service access point identifier).
• SAPI=0 for signaling and
• SAPI=3 for SMS.
• There is no need of a TEI, because there is no need to distinguish the different mobile stations, which is done by distinguishing the
different radio channels.
LAPD
• The length is limited to max 260 octets of information.
• LAPDM has FLAG&FCS
• LAPD has the address of the destination terminal, to identify the TRX, since this is a point to multipoint interface.
Each TRX in a BTS are distinguished by TEI (Terminal Equipment Identities).
• SAPI
• SAP1=0 for radio signaling,
• SAPI=62 for OAM and
• SAPI=63 for layer 2 management on the Abis interface.

See coverpage for conditions on the use of this document

18
 CODICE-DATA-P19

Section 3: Radio Resource

Management overview

FUNDAMENTALS

The information contained in this document is the property of Value Team S.p.A. and the addressee of the document. The information is closely linked to the oral comments accompanying the same, and may be used only by those attending the
presentation. Copying, publishing or divulging the material contained in this document is forbidden and may be illegal. 19
 CODICE-DATA-P20

MS Capabilities
Overview

multi-band MS supports multiple radio frequency bands.

• Single-band supports GSM-900
• dual-band supports GSM-900 and GSM-1800
• tri-band supports GSM-900, DCS-1800 and PCS-1900
• quad-band supports GSM-900, DCS-1800 , PCS-1900 and GSM-850

Dual –mode MS supports multiple radio technologies e.g.

• Dual-mode GSM/UMTS MS

GPRS MS supports GPRS services

EGPRS MS supports GPRS and EGPRS services
VGCS MS supports VGCS services

Downlink Dual Carrier MS is able to receive on two ARFCNs simultaneously. It is only applicable for mobiles
which support EGPRS.

Combinations of VGCS, VBS and GPRS are not studied yet.

See coverpage for conditions on the use of this document

20
 CODICE-DATA-P21

MS capability
MS GPRS Class and DTM MS

GPRS standards provides for three classes of MS:

Class A: supports simultaneous attach, simultaneous activation, simultaneous monitor, simultaneous invocation
and simultaneous traffic. A CS call in the middle of PS call will not disrupt the latter. This class of a mobile may
even require two transceivers because CS and PS could be on different frequencies. RF duplexers may be needed
along with multiple call processing units. There is no coordination between the two service domains. As such, such
a mobile is quite complex and rarely implemented. The cost of such a mobile is also likely to be high and with
possibly low battery life.

Class B: supports simultaneous attach, simultaneous activation and simultaneous monitor. Service invocation and
traffic are mutually exclusive. This means that a CS call in the midst of a PS call will suspend the latter.

Class C: the two domains are mutually exclusive even for attach. If MS is used for the CS domain (possibly chosen
by the user), PS domain becomes unavailable.

The class A mobile is prohibitively complex. To overcome this problem, designers have standardized the Class A
Dual Transfer Mode (DTM) MS which can be seen as a subset of a Class A MS.
Dual Transfer Mode (DTM) MS supports simultaneous transfer of Circuit switched (CS) voice and Packet switched
(PS) data over the same ARFCN via coordination done in the Network.

See coverpage for conditions on the use of this document

21
 CODICE-DATA-P22

MS MultislotClasses
Definition

When an MS supports the use of multiple timeslots it shall belong to a multislot class as defined in 45.002:

EGPRS MS is characterized by two multislotclasses

• GPRS multislotclass
• EGPRS multislotclass
Typically, EGPRS multislotclass < GPRS multislotclass. E.g.the multislotclass of the mobile can be 3 RXs+ 2 TXs(class 6) in pure
GPRSmode and 2 RXs+ 1 TX (class 2) in pure EGPRS mode.

• Type 1 MS are not required to transmit and receive at the same time.
• Type 2 MS are required to be able to transmit and receive at the same time.

There are 45 multislot classes .

When the MS has monitored its last DL timeslot, it shall wait Ttb timeslots (i.e., 1 timeslot) before transmitting; after having transmitted
in the UL direction, it shall wait Tra timeslots (i.e., 2 timeslots) before starting to monitor on the DL direction.
• Tx.Maximum number of allocates TS in DL
• Rx. Maximum Number of allocated TS in UL
• Sum. Sum is the total number of uplink (u) and downlink (d) TS that can actually be used by the MS per TDMA frame.
• The MS must be able to support all combinations of integer values of d <= Rx and u <= Tx TS where 1 <= d + u <= Sum (depending
on the services supported by the MS). Sum is not applicable to all classes.
• Ttb. Ttb timeslots (i.e., 1 timeslot) before transmitting; after having transmitted in the UL direction.
• Tra. MS shall waits Tra timeslots (i.e., 2 timeslots) before starting to monitor on the DL direction.
Trb:Trb relates to the time needed for the MS to get ready to receive. This minimum requirement will only be used when adjacent cell
power measurements are not required by the service selected.
For type 1 MS it is the minimum number of timeslots that will be allowed between the previous transmit TS and the next receive TS or
between the previous receive TS and the next receive TS when the frequency is changed in between.
For type 2 MS it is the minimum number of timeslots that will be allowed between the end of the last receive burst in a TDMA frame
and the first receive burst in the next TDMA frame.

See coverpage for conditions on the use of this document

22
 CODICE-DATA-P23

Multislot Class
Table

Multislot class Maximum number of slots Minimum number of slots Type

Rx Tx Sum Tta Ttb Tra Trb
1 1 1 2 3 2 4 2 1
2 2 1 3 3 2 3 1 1
3 2 2 3 3 2 3 1 1
4 3 1 4 3 1 3 1 1
5 2 2 4 3 1 3 1 1
6 3 2 4 3 1 3 1 1
7 3 3 4 3 1 3 1 1
8 4 1 5 3 1 2 1 1
9 3 2 5 3 1 2 1 1
10 4 2 5 3 1 2 1 1
11 4 3 5 3 1 2 1 1
12 4 4 5 2 1 2 1 1
13 3 3 NA NA a) 3 a) 2
14 4 4 NA NA a) 3 a) 2
15 5 5 NA NA a) 3 a) 2
16 6 6 NA NA a) 2 a) 2
17 7 7 NA NA a) 1 0 2
18 8 8 NA NA 0 0 0 2
19 6 2 NA 3 b) 2 c) 1
20 6 3 NA 3 b) 2 c) 1
21 6 4 NA 3 b) 2 c) 1
22 6 4 NA 2 b) 2 c) 1
23 6 6 NA 2 b) 2 c) 1

See coverpage for conditions on the use of this document

23
 CODICE-DATA-P24

Multislot Class
Table [cont]

Multislot class Maximum number of slots Minimum number of slots Type

Rx Tx Sum Tta Ttb Tra Trb
23 6 6 NA 2 b) 2 c) 1
24 8 2 NA 3 b) 2 d) 1
25 8 3 NA 3 b) 2 d) 1
26 8 4 NA 3 b) 2 d) 1
27 8 4 NA 2 b) 2 d) 1
28 8 6 NA 2 b) 2 d) 1
29 8 8 NA 2 b) 2 d) 1
30 5 1 6 2 1 1 1 1
31 5 2 6 2 1 1 1 1
32 5 3 6 2 1 1 1 1
33 5 4 6 2 1 1 1 1
34 5 5 6 2 1 1 1 1
35 5 1 6 2 1 1+to 1 1
36 5 2 6 2 1 1+to 1 1
37 5 3 6 2 1 1+to 1 1
38 5 4 6 2 1 1+to 1 1
39 5 5 6 2 1 1+to 1 1
40 6 1 7 1 1 1 to 1
41 6 2 7 1 1 1 to 1
42 6 3 7 1 1 1 to 1
43 6 4 7 1 1 1 to 1
44 6 5 7 1 1 1 to 1
45 6 6 7 1 1 1 to 1

See coverpage for conditions on the use of this document

24
 CODICE-DATA-P25

Multislot Class
Example Multislot class 8

The Figure shows an example regarding a MS with multislot class=8: the MS has established concurrent TBFs, and it has 4 timeslots
in the DL direction and 1 timeslot in the UL direction (between DL and UL TDMA frames there is a temporal offset of 3 timeslots).
When the MS has monitored its last DL timeslot, it shall wait Ttb timeslots (i.e., 1 timeslot) before transmitting; after having transmitted
in the UL direction, it shall wait Tra timeslots (i.e., 2 timeslots) before starting to monitor on the DL direction.

See coverpage for conditions on the use of this document

25
 CODICE-DATA-P26

MS RR-state

• Idle mode. In this mode the MS is not allocated any dedicated physical channel; MS listens to the CCCH and the
BCCH.
• Dedicated mode. In this mode, the mobile station is allocated at least two dedicated channels, only one of them
being a SACCH. MS has SDCCH+SACCH or TCH+SACCH.

• Packet Idle Mode. (only applicable for mobile stations supporting GPRS) In packet idle mode, the mobile station
is prepared to transfer LLC PDUs on packet data physical channels. The mobile station is not allocated any radio
resource on a packet data physical channel; it listens to the PBCCH and PCCCH or, if those are not provided by
the network, to the BCCH and the CCCH.
• Packet Transfer Mode. (only applicable for mobile stations supporting GPRS) In packet transfer mode, the
mobile station is prepared to transfer LLC PDUs on packet data physical channels. The mobile station is
allocated radio resource on one or more packet data physical channels for the transfer of LLC PDUs.

• Dual Transfer Mode. (only applicable for mobile stations supporting GPRS and DTM) In dual transfer mode, the
mobile station is allocated radio resources providing an RR connection (3GPP TS 44.018) and a Temporary
Block Flow on one or more packet data physical channels. The allocation of radio resource for the RR connection
and the Temporary Block Flow is co-ordinated by the network in agreement with the capabilities of the mobile
station in dual transfer mode.

• Group receive mode. (Only applicable for mobile stations supporting VGCS listening or VBS listening) In this
mode, the mobile station is not allocated a dedicated channel with the network; it listens to the downlink of a
voice broadcast channel or voice group call channel allocated to the cell.
• Group transmit mode: (only applicable for mobile stations supporting VGCS talking) In this mode, one mobile
station of a voice group call is allocated two dedicated channels, one of them being a SACCH. These channels
can be allocated to one mobile station at a time but to different mobile stations during the voice group call.
See coverpage for conditions on the use of this document
26
 CODICE-DATA-P27

RR-State Mode transition

Idle Mode/ Packet Transfer

Packet Idle Mode Mode
Idle Dedicated
Mode mode

• MS without GPRS capability

Dedicated
Mode

• MS class B

Idle Mode/ Packet Transfer

Packet Idle Mode Mode
Idle Mode Group Receive
mode

Dedicated Dual Transfer

Mode Mode
Group Transmit
mode

• VGCS capable MS
• DTM MS

See coverpage for conditions on the use of this document 27

 CODICE-DATA-P28

Resource Management protocols

Overview

There are two standard s defining Radio Resource Managment:

• 44.018 RR Layer
• 44.060 RLC/MAC

• The RR layer is responsible for the management and allocation of radio resources for circuit-switched and is involved in the first
phase of PS GPRS services management if Packet Control channels does not exist.
• In short RR manages messages to be sent on BCCH, RACH, PAGCH+PCH, SDCCH, SACCH, FACCH

• RLC/MAC is responsible for the management and allocation of radio resources for packet-switched.
• In short RLC/MAC manages message to be sent on PDTCH, PACCH, PBCCH, PRACH, PAGCH, PPCH.

• In any case there is a strong interaction and coordination between two layers.

See coverpage for conditions on the use of this document

28
 CODICE-DATA-P29

Resource Management protocols

Overview

MS BTS/BSC

Resource RR Resource
RR
coordination coordination

RLC/ RLC/
MAC MAC

LAPDm Layer LAPDm Layer

(Layer 2) (Layer 2)
PAGCH*PPCH

PDTCH+PACCH
PBCCH

BCCH

SACCH
FACCH
SDCCH
AGCH+PCH
RACH

PAGCH*PPCH

PDTCH+PACCH
PBCCH
AGCH+PCH
RACH
BCCH

SACCH
FACCH
SDCCH
Physical Layer
Physical Layer
(Layer 1)
(Layer 1)

See coverpage for conditions on the use of this document

29
 CODICE-DATA-P30

Section 5: Radio Resource

Protocol Overview

FUNDAMENTALS

The information contained in this document is the property of Value Team S.p.A. and the addressee of the document. The information is closely linked to the oral comments accompanying the same, and may be used only by those attending the
presentation. Copying, publishing or divulging the material contained in this document is forbidden and may be illegal. 30
 CODICE-DATA-P31

Scope of this section

• This section covers fundamentals related to RR layer protocol.

• The RR layer is responsible for the management and allocation of radio resources for circuit-switched and GPRS
services if Packet Control channels does not exist.

• The RR layer is specified mainly in 3GPP specifications TS 24.007 and TS 44.018

• TS 24.007 describes general concepts related to Layer 3
• TS 44.018 describes the frame structure, format of fields and procedures for the proper operation of RR.

See coverpage for conditions on the use of this document

31
 CODICE-DATA-P32

RR
3GPP reference specification

TS Mobile radio interface signalling layer3G

3; and
General GSM only (Rel- GSM only
series beyond / GSM
24.007 Aspects 4 and later) (before Rel-4)
(R99 and later)
General information (long defunct) 00 series
Requirements 21 series 41 series 01 series
Service aspects ("stage 1") 22 series 42 series 02 series
Technical realization ("stage 2") 23 series 43 series 03 series

Signalling protocols ("stage 3") - user equipment to network 24 series 44 series 04 series

Radio aspects 25 series 45 series 05 series

CODECs 26 series 46 series 06 series
47 series
Data 27 series 07 series
(none exists)

Signalling protocols ("stage 3") -(RSS-CN) and OAM&P and Charging

28 series 48 series 08 series
(overflow from 32.- range)
TS Mobile radio interface layer 3 specification; Radio
Signalling protocols ("stage 3") - intra-fixed-network 44.018 29 series Control
Resource 49 series 09 series
(RRC) protocol
Programme management 30 series 50 series 10 series

Subscriber Identity Module (SIM / USIM), IC Cards. Test specs. 31 series 51 series 11 series

OAM&P and Charging 32 series 52 series 12 series

Access requirements and test specifications 13 series (1) 13 series (1)
Security aspects 33 series (2) (2)
UE and (U)SIM test specifications 34 series (2) 11 series
Security algorithms (3) 35 series 55 series (4)

LTE (Evolved UTRA) and LTE-Advanced radio technolgy 36 series - -

Multiple radio access technology aspects 37 series - -

See coverpage for conditions on the use of this document

32
 CODICE-DATA-P33

Position of RR in the protocol stack

Um Abis A

CC/SMS/SS CC/SMS/SS
(24.008) (24.008)

MM MM
(24.008) relay (24.008)

RR BSSAP BSSAP
relay (44.018) (48.008) (48.008)
RR
(44.018)
RR BTSM BTSM
SCCP SCCP
(44.018) (48.058) (48.058)

LAPDm LAPDm
LAPD LAPD MTP MTP
(44.006) (44.006)

Physical Layer Physical Layer

L1 L1 L1 L1
(45-series) (45-series)

MS BTS BSC MSC

Note1:
RR protocol on Network side is split between BTS and BSC.

See coverpage for conditions on the use of this document 33

 CODICE-DATA-P34

RR messages (1/2)
Channel establishment messages:
Paging and Notification messages:
ADDITIONAL ASSIGNMENT
PAGING REQUEST TYPE 1
IMMEDIATE ASSIGNMENT
PAGING REQUEST TYPE 2
IMMEDIATE ASSIGNMENT EXTENDED
PAGING REQUEST TYPE 3
IMMEDIATE ASSIGNMENT REJECT
PAGING RESPONSE
NOTIFICATION/NCH
Ciphering messages:
NOTIFICATION/RESPONSE
CIPHERING MODE COMMAND
CIPHERING MODE COMPLETE Miscellaneous messages:
CHANNEL MODE MODIFY
Configuration change messages: RR STATUS
CONFIGURATION CHANGE COMMAND CHANNEL MODE MODIFY ACKNOWLEDGE
CONFIGURATION CHANGE ACK. FREQUENCY REDEFINITION
CONFIGURATION CHANGE REJECT MEASUREMENT REPORT
CLASSMARK CHANGE
Handover messages: CLASSMARK ENQUIRY
ASSIGNMENT COMMAND EXTENDED MEASUREMENT REPORT
ASSIGNMENT COMPLETE EXTENDED MEASUREMENT ORDER
ASSIGNMENT FAILURE GPRS SUSPENSION REQUEST
HANDOVER COMMAND MBMS ANNOUNCEMENT
HANDOVER COMPLETE SERVICE INFORMATION
HANDOVER FAILURE
PHYSICAL INFORMATION

Channel release messages:

CHANNEL RELEASE
PARTIAL RELEASE
PARTIAL RELEASE COMPLETE

See coverpage for conditions on the use of this document

34
 CODICE-DATA-P35

RR messages (2/2)
System information messages: VGCS uplink control messages:
SYSTEM INFORMATION TYPE 8 VGCS UPLINK GRANT
SYSTEM INFORMATION TYPE 1 UPLINK RELEASE
SYSTEM INFORMATION TYPE 2 Reserved (see NOTE)
SYSTEM INFORMATION TYPE 3 UPLINK BUSY
SYSTEM INFORMATION TYPE 4 TALKER INDICATION
SYSTEM INFORMATION TYPE 5 PRIORITY UPLINK REQUEST
SYSTEM INFORMATION TYPE 6 DATA INDICATION
SYSTEM INFORMATION TYPE 7 DATA INDICATION 2
SYSTEM INFORMATION TYPE 2bis
SYSTEM INFORMATION TYPE 2ter Application messages:
SYSTEM INFORMATION TYPE 2quater APPLICATION INFORMATION
SYSTEM INFORMATION TYPE 5bis
SYSTEM INFORMATION TYPE 5ter DTM control messages:
SYSTEM INFORMATION TYPE 9 DTM ASSIGNMENT FAILURE
SYSTEM INFORMATION TYPE 13 DTM REJECT
SYSTEM INFORMATION TYPE 16 DTM REQUEST
SYSTEM INFORMATION TYPE 17 PACKET ASSIGNMENT
SYSTEM INFORMATION TYPE 14 DTM ASSIGNMENT COMMAND
SYSTEM INFORMATION TYPE 15 DTM INFORMATION
SYSTEM INFORMATION TYPE 18 PACKET NOTIFICATION
SYSTEM INFORMATION TYPE 19
SYSTEM INFORMATION TYPE 20 3G specific messages:
SYSTEM INFORMATION TYPE 13alt UTRAN CLASSMARK CHANGE
SYSTEM INFORMATION TYPE 2n CDMA 2000 CLASSMARK CHANGE
INTER SYSTEM TO UTRAN HANDOVER COMMAND
INTER SYSTEM TO CDMA2000 HANDOVER COMMAND
GERAN IU MODE CLASSMARK CHANGE

See coverpage for conditions on the use of this document

35
 CODICE-DATA-P36

RR messages
General message format

• Within the RR protocols defined in 3GPP TS 44.018, 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 3GPP TS 24.007.
Difference is on L2 pseudo length field as in the figure.

• More in general the message consists of the following parts (see figure):
• Protocol discriminator: 0110 identifies the RR Management protocol.
• Skip identifier: Value of 0000.
• Message type: Uniquely defines the function and format of each RR message. The message type is
mandatory for all messages. RR message types are summarized in the next slide
• Other information elements (IE), as required.

Message sent on BCCH, downlink CCCH, SCH,

RACH, and the HANDOVER ACCESS message Other messages
8 7 6 5 4 3 2 1
L2 pseudo length octet 1 8 7 6 5 4 3 2 1
Skip Indicator Protocol discriminator octet 2 Skip Indicator Protocol discriminator octet 2
Message type octet 3 Message type octet 3
octet 4 octet 4
Information Element (IE) Information Element (IE)

… …

Information Element (IE) Information Element (IE)

See coverpage for conditions on the use of this document 36

 CODICE-DATA-P37

RR message example
IMMEDIATE ASSIGNMENT from 44.018

Information element Type / Reference Presence Format length

L2 Pseudo Length L2 Pseudo Length M V 1
10.5.2.19
RR management Protocol Discriminator Protocol Discriminator M V 1/2
10.2
Skip Indicator Skip Indicator M V 1/2
10.3.1
Immediate Assignment Message Type Message Type M V 1
10.4
Page Mode Page Mode M V 1/2
10.5.2.26
Dedicated mode or TBF Dedicated mode or TBF M V 1/2
10.5.2.25b
Channel Description Channel Description C V 3
10.5.2.5
Packet Channel Description Packet Channel Description C V 3
10.5.2.25a
Request Reference Request Reference M V 3
10.5.2.30
Timing Advance Timing Advance M V 1
10.5.2.40
Mobile Allocation Mobile Allocation M LV 1-9
10.5.2.21
Starting Time Starting Time O TV 3
10.5.2.38
IA Rest Octets IA Rest Octets M V 0-11
10.5.2.16

See coverpage for conditions on the use of this document

37
 CODICE-DATA-P38

RR message example
CHANNEL REQUEST message

• RR message CHANNEL REQUEST does not follow the basic format.

• The message is only one octet long, coded as shown in figure.

8 7 6 5 4 3 2 1

ESTABLISHMENT RANDOM
octet 1
CAUSE REFERENCE

CHANNEL REQUEST message format

ESTABLISHMENT CAUSE
• 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
• This is an unformatted field with variable length (from 5 bits down to 2 bits).

• CHANNEL REQUEST is encoded by Physical Layer and formatted on Access Burst

Access burst (AB) TB Synchronization Sequence Encoded bits TB GP

8 41 36 3 68,25

See coverpage for conditions on the use of this document 38

 CODICE-DATA-P39

CHANNEL REQUEST message

Establishment cause
101xxxxx Emergency call
110xxxxx Call re-establishment; TCH/F was in use, or TCH/H was in use but the network does not set NECI bit to 1
011010xx Call re-establishment; TCH/H was in use and the network sets NECI bit to 1
011011xx Call re-establishment; TCH/H + TCH/H was in use and the network sets NECI bit to 1
100xxxxx Answer to paging
0010xxxx
0011xxxx See table 9.9a/GSM 04.18
0001xxxx
111xxxxx 1 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
0100xxxx 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. See note 5
0101xxxx 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. See note 5
000xxxxx Location updating and the network does not set NECI bit to 1
0000xxxx Location updating and the network sets NECI bit to 1
0001xxxx Other procedures which can be completed with note 1an SDCCH and the network sets NECI bit to 1
011110xx One phase packet access with request for single timeslot uplink transmission; one PDCH is needed.
01111x0x
01111xx0
01110xxx Single block packet access; one block period on a PDCH is needed for two phase packet access or other
RR signalling purpose.
01100111 LMU establishment, see note 2
01100xx0 Reserved for future use
01100x01
01100011 note 2a
01111111 Reserved for future use, see note 2b

See coverpage for conditions on the use of this document

39
 CODICE-DATA-P40

Fundamental Elementary procedures

List
• System information broadcasting (sub-clause 3.2.2);

• RR connection establishment (sub-clause 3.3):

-entering the dedicated mode: immediate assignment procedure (sub-clause 3.3.1.1);
-paging procedure for RR connection establishment (sub-clause 3.3.2);
-notification procedure (sub-clause 3.3.3) ------ VBS/VGBS only.

• Procedures in dedicated mode and in group transmit mode (sub-clause 3.4):

-measurement report procedure (sub-clause 3.4.1.2);
-intracell change of channels (sub-clause 3.4.3);
-intercell change of channels (sub-clause 3.4.4);
-frequency redefinition procedure (sub-clause 3.4.5);
-channel mode change procedure (sub-clause 3.4.6);
-ciphering mode setting procedure (sub-clause 3.4.7);
-additional channel assignment procedure (sub-clause 3.4.8);
-partial channel release procedure (sub-clause 3.4.9).

• Radio resources connection release (sub-clause 3.4.13);

• voice broadcast channels (VBS) and voice group call channels (VGBS):
•Specific RR procedures for voice broadcast channels and voice group call channels (sub-clause 3.4.15);

See coverpage for conditions on the use of this document

40
 CODICE-DATA-P41

Additional Elementary procedures

List
• Location Services (LS):
•application procedures (sub-clause 3.4.21);

• (E)GPRS services, if Packet Common control channels are not defined:

•RR procedures on CCCH related to temporary block flow establishment (sub-clause 3.5):
-packet paging procedure using CCCH (sub-clause 3.5.1);
-packet access procedure using CCCH (sub-clause 3.5.2).
•packet downlink assignment procedure using CCCH (sub-clause 3.5.3);
•RR procedures on DCCH related to temporary block flow establishment:
-Assignment to Packet Data Channel procedure (sub-clause 3.4.19);
-Network controlled cell reselection (sub-clause 3.4.20).

• MBMS
•RR procedure on DCCH related to MBMS:
-packet paging procedure for MBMS related to dedicated MBMS notification (sub-clause 3.4.27).
•RR procedures on CCCH related to MBMS:
-packet paging procedure for MBMS notification using CCCH (sub-clause 3.5.1.3);
-packet access procedure for MBMS using CCCH (sub-clause 3.5.4).

• PS Handover
•Procedures related to the simultaneous handover of dedicated and packet resources (sub-clause 3.7).

Note:
(E)GPRS services, if Packet Common control channels are not defined are covered in the RLC/MAC section

See coverpage for conditions on the use of this document 41

 CODICE-DATA-P42

Radio Resource Management

System information

See coverpage for conditions on the use of this document 42

 CODICE-DATA-P43

GSM & GPRS System information Scheduling

General
• All BTSs continuously pass on information about their current system configuration and other information needed
by mobile phones before they are allowed to access the network.

• The information broadcasted covers different aspects like e.g.:

-Location area (LAC) and cell (CI);
-information used for handover and cell selection procedures;
-information describing the current control channel structure;
-information controlling the random access channel utilization;
-information defining different options supported within the cell (e.g. GPRS, EGPRS, etc)

• This information is organized in various SYSTEM INFORMATION messages containing specific parameters.
• SYSTEM INFORMATION TYPE 1
• SYSTEM INFORMATION TYPE 2, 2bis, 2ter, 2quater
• SYSTEM INFORMATION TYPE 3
• SYSTEM INFORMATION TYPE 4
• SYSTEM INFORMATION TYPE 5, 5bis, 5ter
• SYSTEM INFORMATION TYPE 6
• SYSTEM INFORMATION TYPE 7
• SYSTEM INFORMATION TYPE 8
• SYSTEM INFORMATION TYPE 9
• SYSTEM INFORMATION TYPE 13
• SYSTEM INFORMATION TYPE 16
• SYSTEM INFORMATION TYPE 17
• SYSTEM INFORMATION TYPE 18
• SYSTEM INFORMATION TYPE 19
• SYSTEM INFORMATION TYPE 20
• SYSTEM INFORMATION TYPE 10

See coverpage for conditions on the use of this document

43
 CODICE-DATA-P44

GSM & GPRS System information Scheduling

General
• SI 2, 3 and 4 messages, and optionally TYPE 1, 2bis, 2ter, 7, 8, 13, 16 and 17 and further types are regularly
broadcast by the network on the BCCH (Broadcast Control Channel). Based on this information the mobile station
is able to decide whether and how it may gain access to the system via the current cell.

• SI 5, 5bis, 5ter and 6 are only transmitted on SACCH (Slow Associated Control Channel).

• SI 2quater, SI18, SI20 messages are only sent if there are UTRAN Neighbour cells.

• SI2ter, SI13, message shall be sent if and only if this is indicated in SYSTEM INFORMATION TYPE 3 message.

• SYSTEM INFORMATION TYPE 19 messages shall be provided if COMPACT neighbour cells exist (see
GSM 05.08). The presence of SI 19 messages shall be indicated in SI 9 message.

• 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.
• GSM 45.002 section 6.3.1.3 specifies the scheduling of SI in the BCCH Channel as summarized in the
table:
TC = (FN DIV 51) mod (8)).
• Network can specify a different scheduling in SI 9. If so, SI 3 specifies where to find SI 9 messages carrying
BCCH scheduling information.

• If the mobile station has received BCCH scheduling information, it shall assume that this BCCH scheduling
information is valid in the location area until new scheduling information is received. It may store the
information in the ME and assume its validity after switch on in the same location area.

See coverpage for conditions on the use of this document

44
 CODICE-DATA-P45

04.18 section 3.2.2.1

04.18 section 9.1.31 to 9.1.43h
GSM & GPRS System information Scheduling
Summary
SYSTEM INFORMATION TYPE Channel Main info contained in SI
System Information Type 1 sent if frequency hopping is in use or when the NCH (Notification
SYSTEM INFORMATION TYPE 1 Optional BCCH channel) is present in a cell.
SYSTEM INFORMATION TYPE 2 Mandatory BCCH list of neigbour cells in 900 band
SYSTEM INFORMATION TYPE 2bis Optional BCCH list of neigbour cells in 1800 band
SYSTEM INFORMATION TYPE 2ter Optional BCCH list of neigbour cells in 1800 band.
SYSTEM INFORMATION TYPE 2quater Optional BCCH list of neigbour cells in UTRAN band. Messages are only sent if there are UTRAN Neighbour cells.
SYSTEM INFORMATION TYPE 3 Mandatory BCCH Location Area (LAC), Cell Identifier (CI), SI13 presence, SI9 presence.
SYSTEM INFORMATION TYPE 4 Mandatory BCCH SI 4 repeats the main Information Elements sent in the SI 1-3
SYSTEM INFORMATION TYPE 5 Mandatory SACCH list of neigbour cells in 900 band. Used for Handover.
SYSTEM INFORMATION TYPE 5bis Mandatory SACCH list of neigbour cells in 1800 band. Used for Handover.
SYSTEM INFORMATION TYPE 5ter Mandatory SACCH list of neigbour cells in band. Used for Handover.
SYSTEM INFORMATION TYPE 6 Mandatory SACCH Location Area (LAC), Cell Identifier (CI)
SYSTEM INFORMATION TYPE 7 Optional BCCH Cell reselectionparameters to be used in that cell.
SYSTEM INFORMATION TYPE 8 Optional BCCH Cell reselection parameters to be used in that cell.
Scheduling of information on the BCCH. SI3 specifies where to find SI 9 messages carrying BCCH
SYSTEM INFORMATION TYPE 9 Optional BCCH scheduling information. SI 18 presence.
The message is sent by the network to provide GPRS information in the cell.
SYSTEM INFORMATION TYPE 13 Optional BCCH Boradcasted if GPRS Indicator is contained in SI 3.
SYSTEM INFORMATION TYPE 16 Optional BCCH SoLSA specific parameters
SYSTEM INFORMATION TYPE 17 Optional BCCH SoLSA specific parameters
sent when non-GSM broaodcast information must be transmitted. The scheduling and repetition rate
of these messages is determined by the system operator and is indicated in SYSTEM
SYSTEM INFORMATION TYPE 18 BCCH INFORMATION TYPE 9 message.
SYSTEM INFORMATION TYPE 19 messages shall be provided if COMPACT neighbour cells exist
SYSTEM INFORMATION TYPE 19 BCCH (see GSM 05.08). The presence of SI 19 messages shall be indicated in SI 9 message.
sent when non-GSM broaodcast information must be transmitted. The scheduling and repetition rate
of these messages is determined by the system operator and is indicated in SYSTEM
SYSTEM INFORMATION TYPE 20 Optional BCCH INFORMATION TYPE 9 message.
SYSTEM INFORMATION TYPE 10 Optional BCCH

See coverpage for conditions on the use of this document

45
 CODICE-DATA-P46

SYSTEM INFORMATION example

TYPE 3 (1/2)

L2PseudoLength : 73
Skip indicator : 0
Protocol discriminator : (6) Radio resources management messages
Message type : 27

Cell identity (CI) : 440 (Hex 0x01B8)

Location Area Identification

Mobile country code (MCC) : 555
Mobile network code (MNC) : 01
Location area code (LAC) : 413 (Hex 0x019D)

Control channel description

MSCR : (1) MSC is Release '99 onwards
Attach/detach allowed (ATT) : (1) YES
BS-AG-BLKS-RES : 1
CCCH-CONF : (0) 1 basic physical channel used for CCCH, not combined with SDCCHs
CBQ3 : (0) Iu mode not supported
BS-PA-MFRMS : 4 multiframes period
T3212 timeout value : (5) 0.5 hours

Cell options (BCCH)

Dynamic ARFCN mapping indicator (DN-IND) : (0) Dynamic ARFCN mapping is not used by the PLMN
Power control indicator (PWRC) : (1) Set
DTX indicator : (2) The MSs shall not use uplink discontinuous transmission
RADIO-LINK-TIMEOUT : 20

See coverpage for conditions on the use of this document

46
 CODICE-DATA-P47

SYSTEM INFORMATION example

TYPE 3 (2/2)

Cell selection parameters

CELL-RESELECT-HYSTERESIS : 4 dB Rxlev hysteresis for LA-reselection
MS-TXPWR-MAX-CCH : 5
ADDITIONAL RESELECT PARAM IND (ACS) : (0) System information type 16 and 17 are not broadcast on the BCCH
HALF RATE SUPPORT (NECI) : (1) New establishment causes are supported
RXLEV-ACCESS-MIN : 5

RACH control parameters

Max retransmission : (2) Maximum 4 retransmissions
Tx-integer : (7) 10 slots used
Cell bar access : (0) Not barred
Call reestablishment : (1) Not allowed
Access control
Emergency Call allowed : (0) All MSs
Barred classes :

Rest octets
System Information 2ter indicator - Not Available
Early classmark sending control - Explicity accepted
BCCH scheduling is not sent in SI9
Neither UTRAN nor CDMA2000 classmark change message shall be sent with the Early classmark sending

See coverpage for conditions on the use of this document

47
 CODICE-DATA-P48

SYSTEM INFORMATION example

TYPE 2

L2PseudoLength : 89
Skip indicator : 0
Protocol discriminator : (6) Radio resources management messages
Message type : 26

Neighbour Cell Description

EXT IND : (0) The information element carries the complete BA
BA IND : 1
Bitmap 0
Channels : 39

NCC permitted
NCC permitted values : 0

RACH control parameters

Max retransmission : (2) Maximum 4 retransmissions
Tx-integer : (7) 10 slots used
Cell bar access : (0) Not barred
Call reestablishment : (1) Not allowed
Access control
Emergency Call allowed : (0) All MSs
Barred classes :

See coverpage for conditions on the use of this document

48
 CODICE-DATA-P49

Radio Resource Management

Elementary Procedure for Basic services

See coverpage for conditions on the use of this document 49

 CODICE-DATA-P50

Mobile Originating Call – Call Setup

RR procedures

MS BTS MS BTS
MS in IDLE mode

RR connection establishment Ciphering mode setting procedure

MS Initiated I (CIPHERING MODE COMMAND) ---SDCCH
RANDOM ACCESS --- RACH I (CIPHERING MODE COMPLETE) --- SDCCH

UI (IMM ASSIGN) --- AGCH

<<L3>> message transfer
I (<<L3>>) ---SDCCH
MS in Dedicated mode (SDCCH Assigned)
I (<<L3>>) ---SDCCH
SDCCH link establishment
SABM (<<CM SERVICE REQUEST>>) ---SDCCH Assignment procedure
UA (<<CM SERVICE REQUEST>>)---SDCCH I (ASSIGNMENT COMMAND) --- SDCCH

SABM --- FACCH

Early Classmark sending
UA ---FACCH
I (CLASSMARK UPDATE ) --- SDCCH
I (ASSIGNEMENT COMPLETE) --- FACCH
<<L3>> message transfer SDCCH is released without signalling on Um interface
I (<<L3>>) ---SDCCH <<L3>> message transfer
I (<<L3>>) ---SDCCH I (<<L3>>) ---FACCH
I (<<L3>>) ---FACCH

See coverpage for conditions on the use of this document

50
 CODICE-DATA-P51

Mobile Originating Call – Call in progress & Release

RR procedures

MS BTS MS BTS

Call in progress

MEASUREMENT REPORT

MEASUREMENT REPORT --- SACCH

<<L3>> message transfer
MEASUREMENT REPORT --- SACCH I (<<L3>>) ---FACCH

MEASUREMENT REPORT --- SACCH I (<<L3>>) ---FACCH

MEASUREMENT REPORT --- SACCH

POWER Control Command on SACCH Header Channel Release

I (CHANNEL RELEASE) --- FACCH

DISC --- FACCH

SI on SACCH
UA ---FACCH
SI 5 --- SACCH
SI 5bis --- SACCH
SI 5ter --- SACCH
SI 6 --- SACCH

See coverpage for conditions on the use of this document

51
 CODICE-DATA-P52

RR connection establishment procedure

MS initiated

MS is in IDLE mode and upper layer requires to establish a connection to the

network.

MS prepares and sends ACCESS REQUEST to be sent on RACH.

MS BTS

On receipt of a CHANNEL REQUEST message, the network allocates a

MS in IDLE mode dedicated channel SDCCH to the mobile station by sending :
an IMMEDIATE ASSIGNMENT in unacknowledged mode on the same CCCH
timeslot on which it has received the CHANNEL REQUEST.
RR connection establishment
MS Initiated
The IMMEDIATE ASSIGNMENT message contains:
RANDOM ACCESS --- RACH • the description of the assigned channel;
Establishment cause • the information field of the CHANNEL REQUEST message and the frame
Random reference number of the frame in which the CHANNEL REQUEST message was
received;
UI (IMM ASSIGN) --- AGCH • the initial timing advance (cf. GSM 04.04);
• optionally, a starting time indication.
In this way MS is able to understand that IMMEDIATE ASSIGNMENT is for
him.
Service Request procedure
SABM (<<CM SERVICE REQUEST>>) ---SDCCH The establishment of the main signalling link is then initiated by use of an
SABM with information field containing the CM SERVICE REQUEST message
UA (<<CM SERVICE REQUEST >>) ---SDCCH
. The MM sublayer in the mobile station is informed that the RR entity has
entered the dedicated mode.
Network answer with UA containing the << CM SERVICE REQUEST >>
message

See coverpage for conditions on the use of this document 52


RR connection establishment procedure
Network initiated
MS
MS in IDLE mode
RR connection establishment
Network Initiated
UI (PAGING REQUEST) --- PCH
RANDOM ACCESS --- RACH
UI (IMM ASSIGN) --- AGCH
Service Request procedure
SABM (<<PAGING RESPONSE>>) ---SDCCH
UA (<<PAGING RESPONSE>>) ---SDCCH
See coverpage for conditions on the use of this document
CODICE-DATA-P53
MS is in IDLE mode.
BTS
MS prepares and sends ACCESS REQUEST to be sent on RACH.
On receipt of a CHANNEL REQUEST message, the network may allocate a
dedicated channel to the mobile station by sending :
an IMMEDIATE ASSIGNMENT message or IMMEDIATE ASSIGNMENT
EXTENDED message
Upon receipt of a paging request message, the addressed mobile station shall
initiate the immediate assignment procedure as specified in previous slide.
The establishment of the main signalling link is then initiated by use of an
SABM with information field containing the PAGING RESPONSE message .
The MM sublayer in the mobile station is informed that the RR entity has
entered the dedicated mode.
Network answer with UA containing the <<PAGING REQUEST>> message
53

Classmark sending
MS
Early Classmark sending
UI (CLASSMARK CHANGE) --- SDCCH
UI (UTRAN CLASSMARK CHANGE) ---
SDCCH
MS BTS
Classmark interrogation
UI (CLASSMARK ENQUIRY ) --- mainDCCH
UI (CLASSMARK CHANGE ) --- mainDCCH
See coverpage for conditions on the use of this document
CODICE-DATA-P54
BTS
• Early classmark sending consists in the mobile station sending as
early as possible after access a CLASSMARK CHANGE message to
provide the network with additional classmark information.
• In addition an MS supporting UTRAN shall send a UTRAN
CLASSMARK CHANGE message;
• an MS supporting CDMA2000 shall send a CDMA2000
CLASSMARK CHANGE message and
• an MS supporting GERAN Iu mode shall send a GERAN IU MODE
CLASSMARK CHANGE message.
• On receipt of the CLASSMARK ENQUIRY message the mobile
station sends a CLASSMARK CHANGE and/or a UTRAN
CLASSMARK CHANGE and/or a CDMA2000 CLASSMARK
CHANGE and/or a GERAN IU MODE CLASSMARK CHANGE
message to the network on the main DCCH.
• The Classmark Enquiry Mask information element in the
CLASSMARK ENQUIRY message indicates the type of request.
• If the Classmark Enquiry Mask information element is not included
in the CLASSMARK ENQUIRY message, this indicates a request
for CLASSMARK CHANGE message.
54
 CODICE-DATA-P55

Assignment procedure

• MS is in IDLE mode.

• The network initiates the channel assignment procedure by sending an

MS BTS ASSIGNMENT COMMAND message to the mobile station on the main
signalling link.

MS in Dedicated mode • Upon receipt of the ASSIGNMENT COMMAND message, the mobile station:
• initiates a local end release of link layer connections commands
the switching to the assigned channels and
Assignment procedure • initiates the establishment of lower layer connections (this
includes the activation of the channels, their connection and the
I (ASSIGNMENT COMMAND) --- SDCCH
establishment of the main signalling links).
SABM --- FACCH

UA ---FACCH

I (ASSIGNEMENT COMPLETE) --- FACCH

See coverpage for conditions on the use of this document 55

 CODICE-DATA-P56

RR Messages over SACCH

• MS is in DEDICATED Mode (SDCCH or TCH)

• When in dedicated mode or group transmit mode, the mobile station

MS BTS regularly sends either MEASUREMENT REPORT or ENHANCED
MEASUREMENT REPORT messages to the network. These messages
contain measurement results about reception characteristics from the current
cell and from neighbour cells.

UI (MEASUREMENT REPORT) --- SACCH

UI (MEASUREMENT REPORT) --- SACCH

UI (MEASUREMENT REPORT) --- SACCH

UI (MEASUREMENT REPORT) --- SACCH

SI 5 --- AGCH
SI 5bis --- AGCH
SI 5ter --- AGCH
SI 6 --- AGCH

See coverpage for conditions on the use of this document 56