Air Interface Um

Siemens

Air Interface Um

Contents
1 1.1 1.2 2 3 3.1 3.2 4 4.1 Layer 1 of Air Interface - Um Physics of Layer 1 (Um) Logic of Layer 1 (Um) Layer 2 - Um-Interface Layer 3 - Um Radio Resource- , Mobility- , Connection Management Formatting Rules Call Sequences on Um Complete Sequences 3 6 34 53 61 62 74 79 80

MN1788EU08MN_0001

Siemens

Air Interface Um

MN1788EU08MN_0001

Air Interface Um

Siemens

Layer 1 of Air Interface - Um

MN1788EU08MN_0001

Siemens

Air Interface Um

The MS is linked to the fixed PLMN structure via a radio link. The air or radio interface Um describes the radio link function. The MS/BSS interface must ensure: use of the same standard interface by the MS and terminal equipment (TE) use of MSs from different manufacturers in the whole system area of the GSM network connection with terminal equipment using the same identifiers and codes independent of the respective location of the unit The transmission of speech, data and signaling is carried out on the air interface Um via radio channels (RFCs). The RFCs form layer 1 of the GSM system air interface. Layer 1 (Um) is described in GSM-Rec. 04.04.

MN1788EU08MN_0001

Air Interface Um

Siemens

Layer 3

CC

SS

SMS

CM

MM

RR

Layer 2

Logik Layer 1 Physik

Fig. 1 Layer 1 - 3 of the air interface Um

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

Siemens

Air Interface Um

1.1

Physics of Layer 1 (Um)

Speech and data transmission on the air interface Um is carried out via the physical channels. A physical channel is defined by a specific carrier pair (RFC = Radio Frequency Channel) in the UL and DL and the number of the time slot in the TDMA frame. Layer 1 (physical Layer : GSM 04.04) is a physical bi-directional point to point connection in multiframe mode. Layer 1 communicates with layer 3 directly according to channel management and measurement control. The physical layer will offer layer 2 appropriate channels by usage of the following functions :
l l l

Burst transmission Error correction and -detection Supervision of RSS Link Control

Furthermore the layer 1 protocol defines the mobile station's search for a suitable BCCH and the seizure of DCCH through the MS (after allocation by the base station)

MN1788EU08MN_0001

Air Interface Um

Siemens

UL

DL

7 6 5 4 3 2 1 RFC 1 RFC 2 RFC 3 0 RFC 174 TDMA

RFC 1

RFC 2

FDMA

Fig. 2 Physical channel in the FDMA and TDMA frame

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

6 4 5
TDMA RFC 3 RFC 174 FDMA

7 6

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

Siemens

Air Interface Um

1.1.1

The TDMA Frame

A TDMA frame is divided into 8 time slots (= TS). The whole TDMA frame lasts 4.615 ms, an individual time slot 0.577 ms. A physical channel is assigned exactly one time slot TS in the TDMA frame. Each subscriber receives a time slot and sends all 8 time slots1 once. Transmission is not allowed outside the allocated time slots TS (i.e. after the TS has expired) so other physical channels are not exposed to interference.

With full rate transmission; with half rate transmission every 16 time slots; HSCSD and GPRS are not yet taken into consideration

MN1788EU08MN_0001

Air Interface Um

Siemens

TDMA-frame

0,577 ms 4,615 ms

Fig. 3 Assignment / repeat of a TDMA frame

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

Siemens

Air Interface Um

1.1.2

Burst / Normal Burst

Sending the information in the individual time slot of 0.577 ms with a permanently defined bit sequence is called a burst. The burst is realized by the MS by switching on, transmitting briefly and switching off the transmitter again.

10

MN1788EU08MN_0001

Air Interface Um

Siemens

Power

542,80 ms 28 ms 28 ms

Time

Fig. 4 Time pattern of the resulting transmit power of a burst2

Note: the duration of a time slot is 577 ms according to the definition. These 577 ms are not given in descriptions of the transmit power of a burst and often irritate readers of literature on GSM. The time domain of 542.8 ms shown in fig. 8 and 9 (corresponding with 147 bit, also known as useful part) is the range where transmit power is required at a constant power level almost as a information transmission platform. Together with the time ranges from the flanks (increase/decrease of power) of a maximum of 28 ms each this gives 598.8 ms and is thus slightly longer than the duration of the accompanying time slot. The two 28 ms are however only time maximum limits for the flanks and interference from burst of successive time slots. They are reliable when the power is appropriately low so the duration of the technically realized burst coincides with the defined duration of a time slot in the 1st approach.

MN1788EU08MN_0001

11

Siemens

Air Interface Um

With base stations the dynamic range is 70 dB, with low power (mobile phone: 2.5 W) 36 dB. The set tolerance masks for transmitting a burst from a BTSE are shown in the following diagram.

12

MN1788EU08MN_0001

Air Interface Um

Siemens

Power (dB) 4 0,5 0 -0,5

-6

-30

-70

useful part 147 bits

10

10

T0

10 Time (ms)

10

Fig. 5 Tolerance masks of the TDMA burst

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

13

Siemens

Air Interface Um

Time structure of the time frame / bit sequence A time slot is defined at a time frame of 577ms (to be precise: 576 12/13 ms @ 576.923 ms). This time frame is divided into 156.25 bit. This means an individual bit has a duration of 3.6923 ms. The 156.25 bits are used as follows:
l l

142 bits for information transmission, 3 bits each as tail bits (TB) for edge limitation of the time slots. They are also used as protection zones if a neighboring channel happens to interfere with the first or lasts bits. 8.25 bits as a guard period (GP) (exception: the GP for access burst is 68.25 bits long) for collecting variable run or reception times (determined by the distance BTSE MS).

14

MN1788EU08MN_0001

Air Interface Um

Siemens

. . .

. . .

TB 3

142 Information

TB 3

GP 8,25

Burst

Fig. 6 Breaking down a time slot into bits

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

15

Siemens

Air Interface Um

Realization of information transmission in the burst As a rule 142 bits of information transmission are realized in a burst presented as "1" or "0" as indicated below. They are in the time middle of the burst transmission in the "useful part". The two 3 tail bits (TB) on the edge of the information section provided as security zones are realized as constant transmission of "0". No information is transmitted in the guard period (GP). There are 5 different types of burst
l l l l l

Normal burst Frequency correction burst Synchronization burst Access burst Dummy burst

Each of these bursts has a different configuration and has a particular purpose. The normal burst It contains
l l l

2 x 3 bits as tail bits (TB); 2 x 57 encrypted data bits which carry the actual information 2 x 1 bit as a "stealing flag" which tell the receiver that data transmission is being interrupted briefly and signaling data is being transmitted instead of useful data (or vice versa). 26 bits for synchronizing and problem detection (training sequence) which allow both the BS and the MS to synchronize themselves to a burst and allocate the data bits exactly. Distorted or incomplete received signals can thus be reconstructed.

Now that the contents of the most important burst has been described down to the bit level, how information transmission is realized at the level of individual bits in the burst now has to be described. This means: How is the "0" or "1" presented exactly on the radio path?

16

MN1788EU08MN_0001

Air Interface Um

Siemens

TB

Encrypted Bits

S Training Sequence

S Encrypted Bits

TB

57

26

57

Fig. 7 Normal burst

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

17

Siemens

Air Interface Um

GMSK - Gaussian Minimum Shift Keying The information to be transmitted consisting of a sequence of binary data (bit sequence) must be modulated on an information carrier with a specific rate (bit rate). The receiver must then be able to remove them from this carrier. To obtain the best possible bandwidth utilization taking the minimum requirements for transmission quality into consideration, a frequency modulation method was chosen for the GSM system. It is known as GMSK (Gaussian Minimum Shift Keying). In principle the bandwidth of a radio channel (RFC) of 200 kHz varies here around the center of the bandwidth (carrier frequency ft) with a maximum frequency displacement Df = 67.7 kHz3 .

MSK - Minimum Shift Keying MSK is a frequency shifting modulation process which involves the information in the instantaneous frequency of the HF signal. This process stands out because of the continuous phase4 processing of the modulation signal resulting in excellent bandwidth utilization. The binary signal is modulated5 on the carrier using a modulation index h = Df/fmod = 0.5. The instantaneous frequency of the HF signal changes with the applied modulation data. When there is a "1", the carrier frequency ft is increased by Df, when there is a "0" decreased by Df. With a modulation index of 0.5 Df corresponds with the half modulation frequency fmod. With MSK the phase angle j of the carrier is changed linearly and continually during the bit duration T. It is changed by +90 for a logical "1" at the modulator input and by -90 for a "0". The frequency of the HF signal can be seen in the context of the phase relationship. It is also obtained from the trajectory of the phase path or the phase path is obtained from the integral of the frequency path. Df can also be calculated from bit duration T and the change in the phase relationship (Dj). Df = (Dj/Dt) / 2p; with Dj = p/2 (90) and Dt = T = 3.6923 ms hence: Df = 1/(4T) = 1/(4*3.6923ms) = 67.7 kHz

3 4

Df = 1/(4T) applies; T = duration of a bit = 3.6923 ms i.e. there is no phase jittering 5 Df = carrier deviation; fmod = modulation frequency; fmod < 1/2 bit rate fbit

18

MN1788EU08MN_0001

Air Interface Um

Siemens

MSK Modulation
Phase response Binary signal f Frequency response f f f f 0 1

+180 +90 Phase t -90 -180

Fig. 8 Frequency and phase response with the MSK modulation process

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

19

Siemens

Air Interface Um

GMSK Reducing the bandwidth required for MSK can be achieved by prefiltering the data signal. The "increments" of the data (0 1) and thus also frequencies or unsteadiness of the phase path result in a comparably wide spectrum. To reduce the bandwidth requirement by means of improved attenuation of the side bands a lowpass prefilter with the pass through characteristic of a Gaussian bell-shaped curve is used. The filter used with bandwidth B6 has the following impulse answer (Rec. 05.04): H (t ) = 1 / 2 PI T * e -t
2 2

/ 2I 2T 2

with I = 2 P / 2 PB * T

H ( f ) = e -(ln 2 / 2 B

)* f 2

The data signals Gaussian filtered here have "softer" transitions thus affecting the phase path. A frequency or phase change without jumps (continuous) results.

0.3 was chosen as a standardized filter bandwith for the Gauss filter, i.e. bandwidth B * bit duration T 0.3; given B = 81.25 kHz

20

MN1788EU08MN_0001

Air Interface Um

Siemens

MN1788EU08MN_0001

21

Siemens

Air Interface Um

1.1.3

Time Organization (Framing)

The transmission of the control and user information (speech/data) takes place in physical channels. A time slot is available in the TDMA frame every 4.615 ms. The information is transmitted according to specific time schemas, i.e. certain contents are repeated at specific time intervals. This process, i.e. the periodical repeat of the TDMA frame is called "framing".

22

MN1788EU08MN_0001

Air Interface Um

Siemens

BCCHMultiframe Time 50 49 48 47 46 . . . . . . . . 6 5 4 3 2 1 RFC 1 RFC 2 0 0 RFC 3 1 RFC 174 Frequency FDMA 2 3 25 . 24 . . . 6 5 4 3 2 1 0 4 TDMA Frame 5 6 7 TCHMultiframe

Fig. 9 Physical channels / traffic and control channel multiframe

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

23

Siemens

Air Interface Um

Multiframe TDMA frames belonging together in a first framing level are called multiframes. There are 26 TDMA frames in a user channel7 multiframe, in a control or signaling channel multiframe there are 51 TDMA frames. The control channel multiframes are transmitted as a rule in time slot 0 of one of the radio channels (RFCs) from a BTSE, the remaining time slots are available for user channel multiframes.

Note: Not only subscriber information (speech/data) can be transmitted in a traffic channel. If the signaling requirement increases, signaling can also be transmitted via a traffic channel. A change between subscriber information and signaling is indicated by the so-called stealing flags in the normal burst.

24

MN1788EU08MN_0001

Air Interface Um

Siemens

1 Multiframe for signaling 1) 51 TDMA frame = 235,38 ms 0 1 2 49 50 0

1 Multiframe for Speech/Data 2) 26 TDMA frame = 120 ms 1 2 1) 2) 1 TDMA frame 4,615 ms 4 5 6 7 24 25

Signaling channels User channels and associated signaling channels

8 Time slot = 0 1 2 3

1 Time slot BURST = Contents of a time slot

156,25 bit = 576,88 ms (1 bit = 3,692 ms)

Time organization of the air interface

Fig. 10 Multiframe

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

25

Siemens

Air Interface Um

The multiframe for user information (full or half rate transmission) will be used at this point as an example of multiframe time organization. The diagram shows the periodical repeat of the fixed structure of certain "logical contents" for a user channel with half and full rate transmission. All 26 TDMA frames repeat specific contents. This is necessary because not only user information (data, speech) is transmitted in the traffic channel connection (called TCH here) but also further specific signaling information (SACCH) has to be transmitted repeatedly at fixed intervals in a traffic channel multiframe. The information (user information signaling) is transmitted between MS and BTS as burst in physical channels. To differentiate the contents a division into "logical" channels is useful. These "logical channels" specify therefor certain contents of the transmission over the air interface. In particularly for signaling different contents and therefor "logical channels" are relevant. They are repeated in the signaling channel multiframe every 51 TDMA frames.

26

MN1788EU08MN_0001

Air Interface Um

Siemens

UPLINK / DOWNLINK: Traffic Channel (TCH)

26 TDMA frame 120 ms

A full rate TCH T/t A/a = TDMA frame for TCH TDMA frame for SACCH/T

Two full rate TCH

Fig. 11 Multiframe for a user channel

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

27

Siemens

Air Interface Um

Superframe / Hyperframe The data packets from the time slots are compiled in even higher frame structures in addition to this first framing level of the merging of the TDMA frames to multiframes. These are called superframes and hyperframes. A superframe comprises 26 x 51 = 1326 frames and is thus 6.12 s long. The superframe is the smallest common multiple of traffic channel multiframes (26 frames) and control or signaling channel multiframes (51 frames). The time window of a superframe is the shortest cycle in which the organization of all channels is repeated. Some characteristics of the channel organization are excluded from this repeat. These are contained in the hyperframe. The hyperframe is the numbering period. It comprises 2048 superframes and is thus exactly 12,533.760 s or 3 h 28 min 56.76 s long. It is a multiple of all cycles described up to now and determines all transmission cycles or periods on the air interface in practice.

28

MN1788EU08MN_0001

Air Interface Um

Siemens

Hyperframe = 2048 Superframe

Superframe = 26 x 51 (Multi-) Frames

TCH Multiframe 0 1 2 3 24 25

BCH Multiframe 0 1 2 3 4 49 50

TDMA Frame

Fig. 12 Time organization: multiframe, superframe and hyperframe

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

29

Siemens

Air Interface Um

1.1.4

Adaptive Frame Alignment

Adaptive frame alignment is the time condition between uplink (UL) and downlink (DL). The TDMA frames (UL) running from the mobile station (MS) to the base station (BS) or especially the transmission and reception station (BTSE) are delayed by 3 time slots (burst periods) compared with the (DL) TDMA frame running in the opposite direction. The BTSE sets the frame (master), the MS has to adapt itself to the presetting. The delay of 3 time slots (= 1.73 ms) is GSM-defined. This GSM convention is set up in such a way that the numbering of the time slots can be identical both in the UL and the DL direction. The time delay allows the mobile station to avoid sending and receiving at the same time. This means substantially simpler technical implementation as the MS receiver does not have to be protected against the transmitter from the same MS ("signal isolation"). The so-called "combining" of antennas is thus not necessary. Timing advance There is a problem, however, when implementing this convention. If the distance between the BTSE and the MS is greater, the delay due to the run time of the signals must be taken into consideration. Even at the speed of light (3 x 108 m/s) the radio signals also require a specific time to bridge the path between the BTSE and the MS. With a maximum cell radius (GSM900) of approx. 35 km this means a delay of approx. 0.1 ms for the path BTSE - MS or of approx. 0.2 ms for a "round path". This delay in the run time must be taken into consideration when the signal is sent from the MS because it is absolutely necessary that the BTSE receives the signals (bursts) from the different MS in the correct time range. Bursts can otherwise overlap time slots from neighboring time slots and thus reduce the transmission quality substantially or even lead to a communication breakdown. This problem can be solved by the MS transmitting its signals earlier and compensating the run time delay. This compensation or its amount is called the "timing advance" (TA). The exact relocation between DL and UL from the viewpoint of the MS is 3 time slots minus the timing advance, i.e.: 1.73 ms - TA. The duration of the timing advance is measured by the BTSE and transferred to the MS. This takes it into consideration within the framework of adaptive frame alignment and signals the total relocation (1.73 ms - TA) to the MS so the MS can take it into consideration when sending its bursts.

30

MN1788EU08MN_0001

Air Interface Um

Siemens

BS transmission/receive station (BTS)

Information for MS on the Timing Advance

1 Mobile station (MS) 2 x Run time (TA)

Transmitter Receiver

Dt = 3 Time slots

Fig. 13 Adaptive frame alignment

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

31

Siemens

Air Interface Um

1.1.5

Frequency Hopping

Frequency hopping means that RFC physical channels8, therefore the transmit channel and consequently the transmit frequency are changed to a set algorithm. The time slot is not changed. The logic behind frequency hopping is to guarantee that all channels have the same high degree of transmission quality by dividing possible interference occurring in only one RFC over all available channels. Frequency hopping is used to reduce or evenly distribute signal losses. These can be caused by screening of an MS in a vehicle or due to multipath propagation (direct signal + on trees, houses, mountains,... reflected signals) as a result of negative interference. As the local occurrence of these signal losses is directly dependent on the wave length of the radio signal (approx. 33 cm at 900 MHz), changing the transmission frequency will also lead to a change in the radio wave propagation. This allows great transmission losses to be minimized. As well as reducing interference, frequency hopping also improves protection against eavesdropping. The BTSE controls optional frequency hopping. As the MS also has to carry out these the BTSE also transmits the frequency hopping algorithm via a BCCH. This BCCH is therefore not affected by the frequency hopping.

The exception is the channels of the RFCs on which the BCCH is sent

32

MN1788EU08MN_0001

Air Interface Um

Siemens

TDMA Frame RFC 1

RFC 2

RFC 3

RFC 4

RFC 5 Frame 0 Frame 1 Frame 2 Frame 3 Frame 4 Frame 5

TCH

Fig. 14 An example of frequency hopping

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

33

Siemens

Air Interface Um

1.2
1.2.1

Logic of Layer 1 (Um)

Logical Types - an Overview

A multitude (for signaling in particular) of different "logical channels" or "logical channel types" is used in the GSM system for transmission via the air interface. These logical types:
l l

traffic channels signaling channels

34

MN1788EU08MN_0001

Air Interface Um

Siemens

CHANNELS

TRAFFIC CHANNELS

SIGNALING CHANNELS

FULL RATE

HALF RATE

BROADCAST CONTROL CHANNLES

COMMON CONTROL CHANNLES

DEDICATED CONTROL CHANNLES

UL + DL UL + DL UL + DL DL DL UL

TCH/F

TCH/H

BCCH FCCH

SCH PCH NCH AGCH

RACH

SACCH

SDCCH FACCH

Fig. 15 Hierarchy of the logical channels

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

35

Siemens

Air Interface Um

1.2.2

Traffic Channels

Traffic channels TCH The task of the traffic channels is to transmit coded speech and data information from the mobile subscriber. Two general forms of a traffic channels are defined: a) Full rate traffic channels (TCH / F) This channel transmits speech on the air interface Um at a transmission rate of 13 kbit/s (TCH / FS) or data at 9.6 kbit/s (TCH / F9.6), 4.8 kbit/s (TCH / F4.8) or 2.4 kbit/s (TCH / F2.4). b) Half rate traffic channels (TCH / H) Speech is transmitted at 6.5 kbit/s (TCH / HS), data is transmitted at 4.8 kbit/s (TCH / H4.8) or 2.4 kbit/s (TCH / H2.4).

1.2.3
l l l

Signaling Channels
BCCH CCCH DCCH

The signaling channels are organized into 3 types according to their tasks: Broadcast control channels: Common control channels: Dedicated control channels:

36

MN1788EU08MN_0001

Air Interface Um

Siemens

Broadcast control channels BCCH The broadcast control channels BCCH are used for synchronizing and transmitting the cell-specific data from the BTSE to the MS. They only work in downlink (DL) direction, i.e. from the BS in the direction of the MS. There are the following according to tasks:
l

Frequency correction channel FCCH: allows exact frequency matching for MS Synchronization channel SCH: after frequency synchronization (by the FCCH) the MS receives further information via the SCH in order to continue with the check-in procedure. The information contains the BSIC and the current TDMA frame number

Broadcast control channel BCCH: contains further information which the MS requires as a reference to the cell (e.g.: channel combination, frequency hopping sequence, cell identification CGI)

Common control channels CCCH The common control channels CCCH are used to control access to the BTSE or the MS. They are unidirectional channels, i.e. they work in either downlink (DL) or uplink (UL) direction There are the following according to tasks:
l

Paging channel PCH: used (DL) by the BTSE to call the MS Notification Channel NCH: used (only DL) to notify mobile stations of voice group and voice broadcast calls. Random access channel RACH: used by the MS to request a signaling channel (UL) from the network or to react to a PCH.

Access grant channel AGCH: assignment of a signaling channel by the BTSE (network) for the MS (DL).

MN1788EU08MN_0001

37

Siemens

Air Interface Um

Dedicated control channels DCCH The group of dedicated control channels DCCH also comprises 3 channels:
l

Stand alone dedicated control channel SDCCH: Bi-directional and used for call setup. Authentication and other main signaling functions takes place here. The MS is assigned a specific TCH with the help of the SDCCH.

Slow associated control channel SACCH: always coupled to an SDCCH or with a TCH. Signaling information (control and measuring parameters) is exchanged between the MS and BTSE via the SACCH.

BS:

transmits network-specific information using SACCH to keep the MS up to date on any changes in the cell parameters. Furthermore the control commands for timing advance and power control are transmitted by the BS to the MS via the SACCH. transmits measuring results (e.g. receive level) to the BS to support them in decisions on the handover. It also informs the BS of the current values of transmission power and timing advance. This function is known as a measurement report.

MS:

Fast associated control channel) FACCH: activated when the signaling requirement increases in certain situations (e.g. during a handover). The FACCH is transmitted instead of a TCH. The "stealing bits" in the TCH indicate the channel change.

38

MN1788EU08MN_0001

Air Interface Um

Siemens

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

39

Siemens

Air Interface Um

1.2.4

Burst Types

As previously described transmission of the information from an individual time slot with a permanently defined bit sequence is called a burst. There are 5 different types of bursts:
l l l l l

Normal burst Frequency correction burst Synchronization burst Access burst Dummy burst

Normal burst The normal burst contains information in traffic and control channels and is structured as following:
l l l

2 x 3 bits as tail bits (TB) for edge limitation of the time slot. 2 x 57 encrypted bits which carry the actual information / data. 2 x 1 bit as a "stealing flag" which tells the receiver that the user data transmission is interrupted briefly and signaling data is transmitted instead of the user data (or vice versa). 26 bits for synchronizing and fault detection (training sequence) allow both the BS and the MS to synchronize itself to a burst and thus assign the data bits exactly. There are 8 various training sequences in the GSM with a permanently defined bit pattern allowing the bit sequence actually received to be compared with the known bit sequence. This allows distorted or incomplete received signals9 to be reconstructed. 8.25 bits guard period (GP) for collecting run times and reception times (determined by the distance BTSE MS).

Due to multipath propagation, Doppler effect

40

MN1788EU08MN_0001

Air Interface Um

Siemens

148 bit = 546,12 ms (+8,25 bit = 30,44 ms )

TB

Information

Training Sequence

Information

TB

GP

57

26

57

8,25 bit

Fig. 16 Normal burst

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

41

Siemens

Air Interface Um

Frequency correction burst The frequency correction burst is transmitted from the BTS for frequency synchronization. The bit sequence of the fixed bits corresponds with an unmodulated carrier, i.e. a pure sine wave, so the MS can synchronize itself to the preset frequency. The repeat of frequency correction bursts is also known as the frequency correction channel (FCCH). The frequency correction burst consists of:
l l l

2 x 3 bit tail bits (TB); 142 bit as fixed bits (sine wave10) for frequency synchronization; 8.25 bit guard period (GP);

To be more precise: the fixed bits (142 x signal 0) lead via this modulation, to a sinusoidal signal for this period with a frequency being 67,7 kHz above the carrier central frequency

10

42

MN1788EU08MN_0001

Air Interface Um

Siemens

TB

fixed Bits

TB

GP

142

8,25 bits

Fig. 17 Frequency correction burst

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

43

Siemens

Air Interface Um

Synchronization burst The MS receives the first information on the BS from the synchronization burst allowing it to synchronize time on the base station. The burst contains a long training sequence, the TDMA number and the identity code of the BS, BSIC11. The TDMA frame number is required as one of the parameters for encryption. The synchronization burst is transmitted together with the frequency correction burst in the TDMA time slot zero. The repeat of synchronization bursts is called synchronization channel. The synchronization burst consists of:
l l l l

2 x 3 bit tail bits (TB); 2 x 39 bit which contain the TDMA frame number and the identity code of the BS (BSIC); 64 bit training sequence for time synchronization and fault detection; 8.25 bit guard period (GP);

BSIC ( Base transceiver Station Identity Code): Identity code of the BTS allowing the MS to distinguish between different BTS; it consists of 6 characters: 3 characters for the NCC (Network Color Code = PLMN identity) and 3 characters for the BCC (Base Color Code) which allows different RFCs with the same frequency in neighboring clusters to be distinguished.

11

44

MN1788EU08MN_0001

Air Interface Um

Siemens

TB

Information

Training Sequence

Information

TB

GP

39

64

39

8,25 bits

Fig. 18 Synchronization burst

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

45

Siemens

Air Interface Um

Access burst The access burst is used for the MS contact setup with the BTSE. It is characterized by a long protection time (GP = 68.25 bits or 252 ms) which takes the signal run time12 from MS to BTSE into consideration. The MS does not know the distance to the BTSE first of all and therefore does not know how the transmission has to be staggered (moved forward). The access burst consists of:
l l l l

8 + 3 bit tail bits (TB); 41 bit synchronization sequence; 36 bit information bits; 68.25 bit guard period (GP);

Dummy burst The dummy burst is sometimes sent as padding if there is no other information. It does not contain any information but has the same format as the normal burst.

Note: The length of the access burst is decisive for the maximum cell size of a GSM900 cell. When a contact is setup with an MS, the 68.25 bits with a duration of 252 ms are sufficient as a security distance for 3 x 108 m/s x 252 ms = 75.6 km. The cell radius must therefore be less than 37.8 km taking the way BTSE MS BTSE into consideration

12

46

MN1788EU08MN_0001

Air Interface Um

Siemens

TB

Synchro.- Sequence

Information

TB

GP

41

36

68,25 bits

Fig. 19 Access burst

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

47

Siemens

Air Interface Um

1.2.5

Multiframe, Channel Combination

The description of the multiframe mentioned that there was only one possibility of arranging the logical channels in multiframes. Moreover there are 7 different combinations (channel combinations) for arranging logical channels in multiframes. In the channel combinations13 listed below RACH, PCH and AGCH are combined in CCCHs as they all involve the allocation of a channel to a subscriber: I) TCH/F + FACCH/F + SACCH/F II) TCH/H(0,1) + FACCH/H(0,1) + SACCH/H(0,1) III) TCH/H(0) + FACCH/H(0) + SACCH/H(0) + TCH/H(1) + FACCH/H(1) + SACCH/H(1) IV) FCCH + SCH + CCCH + BCCH V) FCCH + SCH + CCCH + BCCH + SDCCH/4 + SACCH/4 VI) CCCH + BCCH VII) SDCCH/8 + SACCH/8

F S 0 1

BCCH 2-5

CCCH 6-9

F S 10 11

CCCH 12 - 19

F S 20 21

CCCH 22 - 29

F S 30 31

CCCH 32 - 39

F S 40 41

CCCH 42 - 49

I 50

DL: F = FCCH, S = SCH, B = BCCH, C = CCCH, (PCH, AGCH), I = idle

R R 0 1

R R 10 11

R R 20 21 UL: R = RACH

R R 30 31

R R 40 41

R 50

Fig. 20 Multiframe for channel combination IV) FCCH + SCH + CCCH + BCCH

13

/4 or /8 means up to 4 / 8 dedicated and associated connections to MS

48

MN1788EU08MN_0001

Air Interface Um

Siemens

51 TDMA Rahmen = 235,38 ms DOWNLINK: Broadcast Control Channel (BCCH), Common Control Channel (CCCH) +4 Stand Alone Dedicated Control Channels (SDCCH/4)

FS FS

B B

C C

FS FS

C C

C C

FS FS

D0 D0

D1 D1

FS FS

D2 D2

D3 D3

FS FS

A0 A2

A1 A3

I I

UPLINK:

Common Control Channel (CCCH) +4 Stand Alone Dedicated Control Channels (SDCCH/4)

D3 D3

RR RR

A2 A0

A3 A1

RRRRRRRRRRRRRRRRRRRRRRR RRRRRRRRRRRRRRRRRRRRRRR

D0 D0

D1 D1

RR RR

D2 D2

A B C D F R S I

TMDA frame for SACCH BCCH CCCH SDCCH frequency correction burst RACH synchronized burst idle

Fig. 21 Multiframe for channel combination V)

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

MN1788EU08MN_0001

49

Siemens

Air Interface Um

Purpose / use of the different channel combinations: I) - III) I) Call and data transmission in a 26 TCH frame; Combination I) is primarily used to transmit TCH/F (full rate speech). In combination I) the first 12 frames (0 - 11) are used for call or data transmission, a SACCH is then transmitted (frame 12) and also 12 frames (13 - 24) for call and data transmission. The last frame (25) is not used (I: idle). Combination II) and III) are primarily used for transmitting user data at half rate. 2 TCH/H have to "share" the 26 multiframe with their associated control channels. Data from the first or second subscriber is alternately filled into the frame. The SACCH of the 1st subscriber is in frame 12, the SACCH of the 2nd subscriber in frame 25. This means there are no empty (idle) frames.

II) III)

The FACCH does not have a fixed frame in combination I) to III). If signaling is necessary, indicated by the "stealing flag" in the normal burst, a 20 ms long part of the multiframe which is 120 ms long in total is occupied with FACCHs instead of TCHs. V) - VII) V) BTSE MS signaling: Channel combination V) is the minimum configuration for a base station. It is mostly used when a BTS is only equipped with 1 or 2 RFCs. Channel combination V) may only be used once in a cell because the mobile station searches for the frequency correction channel FCCH for synchronizing and the channel for time synchronization SCH. It is transmitted to time slot 0 of an RFCs (base frequency14). Channel combination V) and IV) rule each other out.

14

The base frequency can be any RFC, it must be sent constantly however

50

MN1788EU08MN_0001

Air Interface Um

Siemens

IV)

Channel combination IV) is mainly used for BTS with several RFCs as it provides the common control channels CCCH with a lot of space. It may only be used once for the same reasons as with combination V) (in time slot 0 of one of the RFC). As opposed to combination V) there are no dedicated channels in combination IV). Channel combination VII) is thus also required when channel combination IV) is used. A BTS can contain up to 16 RFCs in the GSM system. When a lot of RFCs are used (corresponding with a very high traffic volume in the cell) further task sharing can be useful in the channel combination. Channel combination VI) which only contains common control channels CCCH as well as the BCCH is used for this. This means that it is necessary to also use combination IV) and VII) in addition to channel combination VI). Combination IV) is in time slot 0 of the base frequency and VI) going onto 2, 4 and 6. Channel combination VII) is used to accommodate the dedicated channels SDCCH and SACCH each for up to 8 connections between BTSE and MS and is used as a supplement to combination IV) and VI). Meanwhile there are channel combinations existing, which inhabit the Cell Broadcast (for SMS CBS).

VI)

VII)

Remark:

MN1788EU08MN_0001

51

Siemens

Air Interface Um

52

MN1788EU08MN_0001

Air Interface Um

Siemens

Layer 2 - Um-Interface

MN1788EU08MN_0001

53

Siemens

Air Interface Um

The task of layer 2, the data circuit layer, is so-called "linking", i.e. the safe transmission of signaling messages via an individual signaling link. Layer 2 (linking) protocols in the different GSM interfaces are the same to a great extent, they have very similar functions. The main tasks of layer 2 are generally the structuring of the information to be transmitted on the communication channel:
l l l l

Fault detection and correction Stable transmission, i.e. guaranteed free of errors; otherwise transmission repeat Disassembly of the individual data stream and reconstruction Flow control

Layer 2 (Data Link Layer) defines the structure of the 23-byte blocks in the CCM and in particular the numbering and acknowledgment of the blocks.

54

MN1788EU08MN_0001

Air Interface Um

Siemens

CC Call Control

SSS Supplementary Services Support

SMS Short Message Service

Layer 3 Network Layer CM Connection Management MM Mobility Management

RR Radio Resource Management

Layer 2 Data Link Layer

Layer 1 Physical Layer

Fig. 22 Layers 1 to 3 at the air interface; the sublayers of layer 3

MN1788EU08MN_0001

55

Siemens

Air Interface Um

The structure of a 23-byte transmission block in the SDCCH, FACCH, PCH, AGCH or BCCH is shown in the adjacent figure. (The block structure in SACCH deviates slightly from the illustration, whilst a block in the RACH consists of only one byte). A block of this type (known also as layer 2 frame) begins with an address field (1 byte), a control field (1 byte) and a length indicator (1 byte). The subsequent information field contains the layer 3 data. If the 20 bytes available for this data are not completely used, the residual bytes are filled with the fill bit pattern "00101011" ("11111111" also permissible in uplink direction) in order to attain a total length of 23 bytes. Address field contents:
l l

Link Protocol Discriminator (LPD) for discriminating between the GSM protocol and other protocols (national or manufacturer-specific) Service Access Point Identifier (SAPI) for discriminating between short message service (SMS) and other layer 3 parts (RR, MM, CC or SSS) in the information field. (A special layer 3 format is used for SMS, and the SMS messages are numbered independently of the other messages in the control field). Command/Response Field bit (C/R) for discriminating between commands (messages transmitted on own initiative) and responses (reactions to received commands).

The control field is used to number and acknowledge the frames. Its structure is shown in the next figure. The length indicator specifies the length in bytes of the information field. The indicator additionally contains the More Data bit (M) specifying whether the layer 3 message extends to the follow-on layer 2 frame. It may be the case that a layer 3 message is longer than 20 bytes and must therefore be distributed over several layer 2 frames. In this case, the last frame is transmitted with M = 0 and all preceding frames with M = 1 ("Continuation in the next issue"). If the layer 3 messages fits into one layer 2 frame, the More-Data bit of the latter is set to 0 ("End").

56

MN1788EU08MN_0001

Air Interface Um

Siemens

1 2 3

LPD

SAPI see next figure

C/R

Address Field Control Field

Length

Length Indicator

n Layer 3

23

Fill bits

Fig. 23 Structure of a Layer 2 frame (acc. to GSM 04.06)

MN1788EU08MN_0001

57

Siemens

Air Interface Um

The control field differentiates the following three frame types: Information Frames (I-frames), Supervisory Frames (S-frames) and Unnumbered Frames (U-frames). Information frames are identified by the digit 0 in the least significant bit in the control field. These frames are used for error-protected message transmission. "Error protection" means in this context that the messages are individually numbered and acknowledged, thus allowing the receiver the opportunity to request a repeat transmission in the event of a transmission error or reception fault. Accordingly, the control field in the I-frame contains one send number N(S) and one reception number N(R), each 3 bits in length. The send number numbers consecutively all Iframes running in the same direction on one CCH, whereby short message service (SMS) messages and other layer 3 part messages are counted separately. The reception number specifies which I-frame is next expected in the counterdirection; thus, the number is that of the last correctly-received I-frame + 1. I-frames are always commands and always include an information field. Supervisory frames are identified by the bit combination "01" in the two least significant bits in the control field. These frames are used for acknowledgment of received information frames without simultaneously supplying new information. Therefore, the S-frame control fields have only a reception number N(R) indicating the next anticipated I-frame in the counterdirection. Three types of S-frame are distinguished:
l l l

Receive Ready (RR): positive acknowledgment in normal operation Receive Not Ready (RNR): positive acknowledgment simultaneously declaring that due to overload no further I-frames can currently be accepted Reject (REJ): negative acknowledgment (i.e. repeat request)

Supervisory frames can occur as commands or responses; they never include an information field. If information and supervisory frames are exchanged between MS and BSS in a CCH, a layer 2 connection is said to exist in this CCH. The set up of such a layer 2 connection means that both sides allocate storage space for the valid send and reception numbers as well as for the buffering of as yet unacknowledged I-frames (which must possibly be retransmitted). This storage space is released when the layer 2 connection is cleared down.

58

MN1788EU08MN_0001

Air Interface Um

Siemens

Frame I

Format

bit pattern 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1

Command Response N(S) Command both both both Command Response Command Command Response

Inform. Field yes no no no possible no yes no possible

N(R) RR N(R) N(R) N(R) 0 0 0 0 0 0 0 0 1 1 1 0 0 0 1

P P/F P/F P/F P F P P F 0 0 1 1 1 0 0 0

0 1 0 1 1 0 0 0

RNR REJ SABM DM

UI DISC UA

Fig. 24 Control Field Structure (acc. to GSM 04.06)

MN1788EU08MN_0001

59

Siemens

Air Interface Um

As SMS messages are numbered separately from other messages, two independent layer 2 connections can exist in the same CCH: one layer 2 connection for SMS, one for all other layer 3 messages. Layer 2 connections may only be established in SDCCH and FACCH. For this reason, only unnumbered frames are used in all other CCH (i.e. BCCH, AGCH, PCH and SACCH). Unnumbered frames are identified by the digit 1 in the two least significant bits in the control field. These frames contain like their name suggests neither a send number nor reception number. The frames are not acknowledged, therefore, and the receiver cannot request a retransmission. A distinction is made between the following types of unnumbered frames:
l l l l

Set Asynchronous Balanced Mode (SABM): layer 2 connection set up Disconnect (DISC): layer 2 connection cleardown Unnumbered acknowledge (UA): positive acknowledgment for SABM Disconnect Mode (DM): negative acknowledgment for SABM; is also used in cases where an I-frame or S-frame arrives without a layer 2 connection having been established Unnumbered Information (UI): transmission of an information field without layer 2 connection.

SABM, DISC and UI are commands; UA and DM are responses. An information field is always included in the UI, but never in the DISC or DM. SABM and UA may optionally contain an information field. As layer 2 connections exist only in the SDCCH and FACCH, UI-frames are used exclusively in the BCCH, AGCH, PCH and SACCH. The P, F or P/F bits shown in table 3 are known as poll bits in commands and final bits in responses. Their standard value is 0. By transmitting a command with P = 1, one side (MS or BSS) can specially request the opposite side to send a response labeled with F = 1. This polling method is used for set up and cleardown of the layer 2 connection (SABM or DISC with P = 1, UA with F = 1). The BSS likewise polls the MS to ascertain whether the latter is still accessible. Polling is additionally used when one side reports overload with RNR: the opposite side regularly queries (command RR with P = 1) whether the overload still exists (response RNR with F = 1) or not (response RR with F = 1). For all details of the Layer 2 protocol release refer to GSM Guideline 04.06

60

MN1788EU08MN_0001

Air Interface Um

Siemens

Layer 3 - Um

MN1788EU08MN_0001

61

Siemens

Air Interface Um

3.1

Radio Resource- , Mobility- , Connection Management

The layer 3 is composed of three sublayers comprising :

l l l

the Radio Resource Management (RR) functions the Mobility Management (MM) functions the Connection Management (CM) functions.

The Layer 3 messages can only contain maximal 249 Bytes.

62

MN1788EU08MN_0001

Air Interface Um

Siemens

CC Call Control

SSS Suplementary Services Support

SMS Short Message Service

Layer 3 Network Layer CM Connectioon Management MM Mobility Management

RR Radio Resuorce Management

Layer 2 Data Link Layer

Layer 1 Physical Layer

Fig. 25 Layers to 3 at the air interface; the sublayers of layer 3

MN1788EU08MN_0001

63

Siemens

Air Interface Um

3.1.1

Radio Resource Management (RR)

The Radio Resource management (GSM 04.08) messages will be sent between MS and BTS / BSC. Many RR messages will be transported over the Abis Interface within the RSL / DTAP to the BSC. Radio Resource management procedures include the functions related to the management of the common transmission resources, e.g. the physical channels and the data link connections on control channels. The general purpose of Radio Resource procedures is to establish, maintain and release RR connections that allow a point-to-point dialogue between the network and a Mobile Station. This includes the cell selection/reselection and the handover procedures. Moreover, Radio Resource management procedures include the reception of the uni-directional BCCH and CCCH when no RR connection is established. This permits automatic cell selection/reselection.

64

MN1788EU08MN_0001

Air Interface Um

Siemens

The elementary procedures for Radio Resource management are as follows :

l

Idle mode procedures: System information broadcasting Paging

RR connection establishment procedures: Entering the dedicated mode: immediate assignment procedure Entering the group transmit mode: uplink access procedure Paging procedure for RR connection establishment Notification procedure

Procedures in dedicated mode and in group transmit mode: SACCH procedures Channel assignment procedure Handover procedure Frequency redefinition procedure Channel mode modify procedure Ciphering mode setting procedure Additional channel assignment procedure Partial channel release procedure Classmark change procedure Classmark interrogation procedure RR connection release procedure Group receive mode procedures Configuration change procedure

The following table summarizes Radio Resource Management messages:

MN1788EU08MN_0001

65

Siemens

Air Interface Um

RR Management Messages channel establishment messages: ADDITIONAL ASSIGNMENT IMMEDIATE ASSIGNMENT IMMEDIATE ASSIGNMENT EXTENDED IMMEDIATE ASSIGNMENT REJECT Ciphering messages: CIPHERING MODE COMMAND CIPHERING MODE COMPLETE Handover messages: ASSIGNMENT COMMAND ASSIGNMENT COMPLETE ASSIGNMENT FAILURE PDCH ASSIGNMENT COMMAND HANDOVER ACCESS HANDOVER COMMAND HANDOVER COMPLETE HANDOVER FAILURE RR-CELL CHANGE ORDER PHYSICAL INFORMATION RR INITIALISATION REQUEST HANDOVER ACCESS HANDOVER COMMAND HANDOVER COMPLETE HANDOVER FAILURE PHYSICAL INFORMATION Channel release messages: CHANNEL RELEASE PARTIAL RELEASE PARTIAL RELEASE COMPLETE

Remarks

66

MN1788EU08MN_0001

Air Interface Um

Siemens

Paging messages: PAGING REQUEST TYPE 1 PAGING REQUEST TYPE 2 PAGING REQUEST TYPE 3 PAGING RESPONSE System information messages: SYSTEM INFORMATION TYPE 1 SYSTEM INFORMATION TYPE 2 SYSTEM INFORMATION TYPE 2bis SYSTEM INFORMATION TYPE 2ter SYSTEM INFORMATION TYPE 3 SYSTEM INFORMATION TYPE 4 SYSTEM INFORMATION TYPE 5 SYSTEM INFORMATION TYPE 5bis SYSTEM INFORMATION TYPE 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 Specific messages for VBS/VGCS: NOTIFICATION/FACCH NOTIFICATION/NCH TALKER INDICATION UPLINK ACCESS UPLINK BUSY UPLINK FREE UPLINK RELEASE

MN1788EU08MN_0001

67

Siemens

Air Interface Um

VGCS UPLINK GRANT EXTENDED MEASUREMENT ORDER EXTENDED MEASUREMENT REPORT Miscellaneous messages: CHANNEL MODE MODIFY CHANNEL MODE MODIFY ACKNOWLEDGE CHANNEL REQUEST CLASSMARK CHANGE CLASSMARK ENQUIRY FREQUENCY REDEFINTION MEASUREMENT REPORT SYNCHRONIZATION CHANNEL INFORMATION RR STATUS GPRS SUSPENSION REQUEST Configuration Change messages: CONFIGURATION CHANGE COMMAND CONFIGURATION CHANGE ACKNOWLEDGE CONFIGURATION CHANGE REJECT Application messages: APPLICATION INFORMATION

68

MN1788EU08MN_0001

Air Interface Um

Siemens

3.1.2

Mobility Management (MM)

The Mobility Management (GSM 04.08) messages will be sent between MS and MSC and have no influences to the BSS. The MM messages will be transported over the Abis and A-Interface within the RSL / DTAP and DTAP to the BSC. The main function of the Mobility Management sublayer (GSM 04.08) is to support the mobility of user terminals, such as informing the network of its present location and providing user identity confidentiality. A further function of the MM sublayer is to provide connection management services to the different entities of the upper Connection Management (CM) sublayer. The elementary procedures for Mobility Management are as follows :
l

MM common procedures: TMSI reallocation procedure Authentication procedure Identification procedure IMSI detach procedure Abort procedure MM information procedure

MM specific procedures: Location updating procedure Periodic updating IMSI attach procedure Generic Location Updating procedure

Connection management sublayer service provision: MM connection establishment MM connection information transfer phase MM connection release

The following table summarizes Mobility Management messages:

MN1788EU08MN_0001

69

Siemens

Air Interface Um

MM Management messages Registration messages: IMSI DETACH INDICATION LOCATION UPDATING ACCEPT LOCATION UPDATING REJECT LOCATION UPDATING REQUEST Security messages: AUTHENTICATION REJECT AUTHENTICATION REQUEST AUTHENTICATION RESPONSE IDENTITY REQUEST IDENTITY RESPONSE TMSI REALLOCATION COMMAND TMSI REALLOCATION COMPLETE Connection management messages: CM SERVICE ACCEPT CM SERVICE REJECT CM SERVICE ABORT CM SERVICE REQUEST CM RE-ESTABLISHMENT REQUEST ABORT Miscellaneous messages: MM INFORMATION MM STATUS MM NULL

Remarks

70

MN1788EU08MN_0001

Air Interface Um

Siemens

3.1.3
l l l

Connection Management (CM)

The Connection Management (CM) sublayer is composed of : Call Control (CC) Short Message Service Support (SMS) Supplementary Services Support (SS)

The CC messages will be sent between the MS and the MSC and will therefore be considered mainly. Every mobile station must support the call control protocol. If a mobile station does not support any bearer capability at all then it shall respond to a SETUP message with a RELEASE COMPLETE message. In the call control protocol, more than one CC entity are defined. Each CC entity is independent from each other and shall communicate with the correspondent peer entity using its own MM connection. Different CC entities use different transaction identifiers. The elementary procedures for circuit switched Call Control are as follows:
l

Call establishment procedures: Mobile originating call establishment Mobile terminating call establishment

Signaling procedures during the "active" state User notification procedure Call rearrangements User initiated level up- and downgrading

Call clearing Clearing initiated by the mobile station Clearing initiated by the network Clear collision

Miscellaneous procedures In-band tones and announcements Call collisions Status procedures Call re-establishment, mobile station side Call re-establishment, network side DTMF protocol control procedure

The following table summarizes Call Control messages:

MN1788EU08MN_0001

71

Siemens

Air Interface Um

CC messages Call establishment messages: ALERTING CALL CONFIRMED CALL PROCEEDING CONNECT CONNECT ACKNOWLEDGE EMERGENCY SETUP PROGRESS SETUP Call information phase messages: MODIFY MODIFY COMPLETE MODIFY REJECT USER INFORMATION Call clearing messages: DISCONNECT RELEASE RELEASE COMPLETE Messages for supplementary service control: FACILITY HOLD HOLD ACKNOWLEDGE HOLD REJECT RETRIEVE RETRIEVE ACKNOWLEDGE RETRIEVE REJECT

Remarks

72

MN1788EU08MN_0001

Air Interface Um

Siemens

Miscellaneous messages: CONGESTION CONTROL NOTIFY START DTMF START DTMF ACKNOWLEDGE START DTMF REJECT STATUS STATUS ENQUIRY STOP DTMF STOP DTMF ACKNOWLEDGE

CC Call Control

SSS Supplementary Services Support

SMS Short Message Service

Layer 3 Network Layer CM Connection Management

MM Mobility Management

RR Radio Resource Management

Layer 2 Data Link Layer

Layer 1 Physical Layer

Fig. 26 Layers to 3 at the air interface; the sublayers of layer 3

MN1788EU08MN_0001

73

Siemens

Air Interface Um

3.2

Formatting Rules

Every layer 3 message is comprised of several parameters, also known as information elements. Section 9 of GSM Guideline 04.08 defines the mandatory and optional parameters for every message. The same parameter may be mandatory for one message and optional for another. Optional parameters bear an identifier (Information Element Identifier, IEI) to designate their presence. The identifier is always located at the beginning of the parameter. Mandatory parameters, by contrast, include sometimes - dependent on the position - an identifier. The parameters are sub-divided into 5 parameter formats (described in GSM 04.07): V (value only) parameters have neither an identifier (IEI) nor a length indicator; they are mandatory parameters of fixed length. The length is either an integer amount of bytes or 1/2 byte. In the last case, V-parameters of 1/2 byte length are combined to form pairs whenever possible. The first parameter in the combination encompasses the 4 least significant bits, the second parameter the 4 most significant bits. If the total number of V-parameters of 1/2 byte is odd, the 4 most significant bits of the last byte are filled with 0000. (type and value) parameters have an identifier (IEI) but no length indicator. If the length of the contents is an integer amount of bytes, then the IEI is 1 byte in length, and the most significant IEI bit is 0. If the length of the contents is 1/2 byte, then the IEI is likewise 1/2 byte in length. The most significant bit is 1, and the succeeding bits must not be 010 (to distinguish them from Tparameters, see below). (type only) parameters have 0 byte content. The communicated information consists solely in the presence or absence of the parameter. Obviously, such parameters can only be considered as optional. The identifier (IEI) is 1 byte in length and begins with 1010 (so that no confusion with TV-parameters is possible). One example of a type-2 parameter is the authorization given in "Location Update Accept" for the Mobile Station to set up a MM connection directly after the location update (i.e. in the same RR connection). This authorization may, or may not, be present. (length and value) parameters have a length indicator but no identifier (IEI); they are mandatory parameters of variable length. The length indicator is the first byte and indicates how many bytes of contents follow. (type, length and value) parameters have an identifier (IEI) and a length indicator. The IEI is the first byte of the parameter; its most significant bit is 0. The length indicator is the second byte of the parameter and indicates how many bytes of contents follow.

TV

LV

TLV

74

MN1788EU08MN_0001

Air Interface Um

Siemens

Layer 3 parameters (GSM 04.07)

Parameter Format Length integer amount of Bytes Length of 1/2 Bytes Example: 5 parameters V alue content content 2 content 4 0 0 0 0 content 1 content 3 content 5

T ype, V alue

IEI 0 content IEI 010 content

T ype

1 0

IEI

L ength, V alue

Length indicator content

T ype, L ength, V alue

IEI Length indicator content

Fig. 27 Parameter formats

MN1788EU08MN_0001

75

Siemens

Air Interface Um

Each message begins with the same three V-parameters: The protocol discriminator specifies the layer 3 part to which the message belongs. It is a parameter of 1/2 byte length. The transaction identifier (TI) characterizes the transaction ( = CM connection, cf. 2.3). It is a V-parameter of 1/2 byte, too; in conformity with the rules, the protocol discriminator and the TI together fill 1 byte. For RR and MM messages (protocol discriminator = 0110 or 0101), no CM connection is established; for this reason, the TI is replaced by the skip indicator whose value is 0. With a proper TI, the most significant bit serves as TI flag in messages for other TI parts; it is 0 in messages from the side which set up the transaction, and 1 in messages to the side which set up the transaction. The three remaining bits form the TI value are freely selected by the initiating side in a transaction set up; the value 111 is not permissible. The message type identifies the nature of the message (e.g. "Handover Command", "Location Update Request", "Setup" and many other examples). It is a V-parameter with a length of 1 byte. The second bit is the send sequence number N(SD). In all messages from the Base Station, as well as in RR messages from the Mobile Station, this bit is 0. In MM and CM messages from the Mobile Station the bit alternately has the values 0 and 1. For the remaining parameters, the protocol may define three different presence requirements: M (mandatory), C (conditional) or O (optional). An M-parameter must always be included in a message of a given type; its absence is reason enough for the receiver to reject the whole message. A C-parameter must be present under certain conditions, but can be absent under other conditions. An O-parameter, finally, is never bound to be present; its absence is never sufficient reason for the receiver to reject the message.

76

MN1788EU08MN_0001

Air Interface Um

Siemens

Transaction identifier or Skip indicator

Protocol discriminator

TIflag

TI-Value

Protocol discriminator Message type

N(SD)

Message Type
Fig. 28 Layer 3 message header (GSM 04.07)

Value 0110 0101 0011 1011 1001 1111

Layer 3 part Radio Resource Management (RR) Mobility Management (MM) Call Control (CC) Supplementary Services Support (SSS) Short Message Service (SMS) reserved for tests

Fig. 29 Protocol discriminator

MN1788EU08MN_0001

77

Siemens

Air Interface Um

Some examples of layer 3 messages will now be examined. First we shall consider a Radio Resource Management message the "Handover Command" from Base Station to Mobile Station. Apart from the parameters in the message header, the mandatory parameters are the description of the new cell (Cell Description), the specification of the new speech channel (Description of the First Channel) and the required power of the Mobile Station in the new cell (Power Command). Several conditional and optional parameters exist which depend on the cell synchronization or on whether frequency hopping is employed in the new cell. The length specifications indicate the total parameter lengths, i.e. inclusive of identifier and length indicator, where applicable. Thus, V-parameters have the length 1/2 or an integer value. With TV-parameters, the length is 1 if they have 1/2 byte contents and 1/2 byte identifier; otherwise, the length of the contents is 1 byte less than the indicated length (because the first byte is the IEI). T-parameters always have a length of 1 byte. LV-parameters have a length of the contents which is 1 byte less than the indicated length (here, the first byte is the length indicator). Finally, with TLV-parameters, the length of the contents is 2 bytes less than the indicated length, since the first byte is the IEI and the second byte is the length indicator. For example, the parameter "Real Time Difference" (TLV) has a total length of 3 bytes. When 1 byte is subtracted for identifier and length indicator respectively, 1 byte remains for the content.

78

MN1788EU08MN_0001

Air Interface Um

Siemens

Call Sequences on Um

MN1788EU08MN_0001

79

Siemens

Air Interface Um

4.1

Complete Sequences

Our consideration of a location update will be confined to the following case: a Mobile Station, which is in service but without an existing user connection, changes its location area. As soon as the Mobile Station has tuned itself to the new Base Station and recognizes the new LAI in the BCCH, it requests (via the RACH) a signaling channel (SDCCH). After being assigned a signaling channel (in the AGCH), the Mobile Station sets up a layer 2 connection with the "Contention Resolution" procedure, including in the SABM the layer 3 message "Location Update Request" along with the old CKSN, the prior TMSI and previous LAI. The Mobile Station additionally indicates that the requested location update is a normal one (and not a periodic one or an IMSI Attach). The Base Station acknowledges the SABM with UA. The VLR determines the IMSI on the basis of the TMSI and LAI (and possibly by querying the previous VLR), and notifies (if necessary) the HLR. Before confirming the location update and assigning a new TMSI to the Mobile Station, the VLR performs the authentication (I-frames "Authentication Request" and "Authentication Response") and the ciphering activation (I-frames "Ciphering Mode Command" and "Ciphering Mode Complete"). After this, a new TMSI can be allocated with the enciphered message "Location Update Accept"; the Mobile Station responds with "TMSI Reallocation Complete". The Base Station then clears down the RR connection.

80

MN1788EU08MN_0001

Air Interface Um

Siemens

Location update

RACH

Channel Request (Reason = Loc. Upd., Random Reference) UI (Immediate Assignment) (Request Reference, SDCCH-No.) SABM (Location Update Request) (TMSI + old LAI, CKSN, loc upd. type) UA I (Authentication Request) (RAND, CKSN) I (Authentication Response) (SRES) I (Ciphering Mode Command) I (Ciphering Mode Complete) I (Location Update Accept) (new TMSI, new LAI) I (TMSI Reallocation Complete) I (Channel Release)

AGCH

SDCCH

SDCCH SDCCH

SDCCH

SDCCH

SDCCH

SDCCH

SDCCH

SDCCH

SDCCH

DISC UA

SDCCH

Fig. 30 Location Update

MN1788EU08MN_0001

81

Siemens

Air Interface Um

For a mobile originating call (MOC) we will consider the case that a Mobile Station, whose current location is already updated, sets up an outgoing call. Therefore, a location update with directly following MM connection set up is not required first of all; instead, a RR connection must be set up specifically for the MOC. For this, the Mobile Station requests a SDCCH (in the RACH; reason for request = MOC set up). After allocation of the SDCCH (via the AGCH), the Mobile Station sets up the layer 2 connection and conveys in the SABM the message "CM Service Request", which includes the CKSN of the last authentication and the information that a MM connection for call control (CC) is to be set up. The Base Station acknowledges the SABM with UA. The Base Station now performs the authentication (I-frames "Authentication Request" and "Authentication Response") and ciphering activation (I-frames "Ciphering Mode Command" and "Ciphering Mode Complete"). With this, the MM connection is set up and the Mobile Station for its part can establish a CC connection with the message "Setup". This message contains a new transaction identifier (TI; selected by the Mobile Station) as well as all information required for a network call set up (in particular the bearer capability and the called party number). The Base Station answers with the I-frame "Call Proceeding", to which the Mobile Station responds with "Receive Ready".

82

MN1788EU08MN_0001

Air Interface Um

Siemens

Mobile originating call (MOC), beginning

RACH

Channel Request (Reason = MOC, Random Reference) UI (Immediate Assignment) (Request Reference, SDCCH-No.)

AGCH

SDCCH

SABM (CM Service Request) (CC, CKSN) UA

SDCCH SDCCH

I (Authentication Request) (RAND, CKSN)

SDCCH

I (Authentication Response) (SRES) I (Ciphering Mode Command)

SDCCH

SDCCH

I (Ciphering Mode Complete) Receive Ready

SDCCH

SDCCH

I (Setup) (bearer capability, compatibility, called party number, features) I (Call Proceeding)

SDCCH

SDCCH

Receive Ready

Fig. 31 Mobile originating call, part 1

MN1788EU08MN_0001

83

Siemens

Air Interface Um

At this stage, if Off-Air Call Set up (OACSU) is not active, the network side assigns a speech channel by sending an "Assignment Command" I-frame with the TCH number. The Mobile Station responds with "Receive Ready", whereupon the layer 2 connection in the SDCCH can be cleared down locally, and a new layer 2 connection is set up in the FACCH. The Mobile Station uses this new FACCH to acknowledge the received "Assignment Command" with "Assignment Complete". As soon as ringing begins for the called party, the network side sends to the Mobile Station the I-frame "Alerting", to which the Mobile Station responds with "Receive Ready". Once the called party answers, the network side sends the I-frame "Connect" to the Mobile Station; the latter responds with I-frame "Connect Acknowledge". Finally, the Base Station acknowledges the MS response with "Receive Ready", thus completing the connection set up.

84

MN1788EU08MN_0001

Air Interface Um

Siemens

Mobile originating call (MOC), continuation without OACSU

I (Assignment Command) (TCH-No.)

SDCCH

SDCCH FACCH

Receive Ready SABM UA

FACCH

FACCH

I (Assignment Complete) Receive Ready I (Alerting) Receive Ready I (Connect) I (Connect Acknowledge) Receive Ready

FACCH FACCH

FACCH

FACCH

FACCH

FACCH

Fig. 32 Mobile originating call, part 2a

MN1788EU08MN_0001

85

Siemens

Air Interface Um

If Off-Air Call Set up (OACSU) is active, the speech channel is first assigned when the called party answers (i.e. directly before the "Connect"). The transmission of "Alerting" and the associated "Receive Ready" continues in the SDCCH.

86

MN1788EU08MN_0001

Air Interface Um

Siemens

Mobile originating call (MOC), continuation with OACSU

I (Alerting)

SDCCH

SDCCH

Receive Ready I (Assignment Command) (TCH-No.)

SDCCH

SDCCH FACCH

Receive Ready

SABM UA I (Assignment Complete) I (Connect) I (Connect Acknowledge) Receive Ready

FACCH

FACCH

FACCH

FACCH

FACCH

Fig. 33 Mobile originating call, part 2b

MN1788EU08MN_0001

87

Siemens

Air Interface Um

The Base Station initiates a mobile terminating call (MTC) by paging. For this, it sends in the PCH a UI-frame "Paging Request" including the TMSI. The called Mobile Station requests ("Channel Request" in RACH, Reason = Answer to paging) and obtains ("Immediate Assignment" in AGCH) a channel, in which it sets up a layer 2 connection. The SABM for this set up includes the message "Paging Response" along with the last CKSN and the TMSI. The network recognizes the positive paging result and answers the SABM with UA. The Base Station now performs the authentication (I-frames "Authentication Request" and "Authentication Response") and ciphering activation (I-frames "Ciphering Mode Command" and "Ciphering Mode Complete"). With this, the MM connection is set up and the Base Station can establish a CC connection with the message "Setup". This message contains a new transaction identifier (TI; selected by Base Station) as well as all information required for a call set up (in particular the bearer capability). The Mobile Station answers with the I-frame "Call Confirmed", to which the Base Station responds with "Receive Ready".

88

MN1788EU08MN_0001

Air Interface Um

Siemens

Mobile terminating call (MTC), beginning

UI (Paging Request) (Mobile Identity)

PCH

RACH

Channel Request (Reason = Answer to Paging, Random Reference) UI (Immediate Assignment) (Request Reference, SDCCH-No.) SABM (Paging Response) (TMSI, CKSN) UA

AGCH

SDCCH

SDCCH SDCCH

I (Authentication Request) (RAND, CKSN)

SDCCH

I (Authentication Response) (SRES) I (Ciphering Mode Command)

SDCCH

SDCCH

I (Ciphering Mode Complete) I (Setup) (bearer capability, compatibility, calling party number, features)

SDCCH

SDCCH

I (Call Confirmed) Receive Ready

SDCCH

Fig. 34 Mobile terminating call, part 1

MN1788EU08MN_0001

89

Siemens

Air Interface Um

If Off-Air Call Set up (OACSU) is not active, the Base Station assigns the speech channel at this point. The procedure is identical with that for a mobile originating call (see above). Most importantly, the remaining RR connection in the SDCCH is replaced by a new one in the FACCH. As soon as ringing begins for the called party, the Mobile Station sends the I-frame "Alerting", to which the Base Station responds with "Receive Ready". If the called party answers, the Mobile Station notifies the Base Station with the Iframe "Connect". The Base Station responds with "Connect Acknowledge". Finally, the Mobile Station acknowledges the Base Station response with "Receive Ready", thus completing the connection set up for a mobile terminating call.

90

MN1788EU08MN_0001

Air Interface Um

Siemens

Mobile terminating call (MTC), continuation without OACSU

I (Assignment Command) (TCH-No.)

SDCCH

SDCCH FACCH

Receive Ready SABM UA

FACCH

FACCH

I (Assignment Complete) Receive Ready I (Alerting) Receive Ready

FACCH

FACCH

FACCH

FACCH

I (Connect) I (Connect Acknowledge)

FACCH

FACCH

Receive Ready

Fig. 35 Mobile terminating call, part 2a

MN1788EU08MN_0001

91

Siemens

Air Interface Um

If Off-Air Call Set up (OACSU) is active, the speech channel is first assigned when the called party answers (i.e. after the "Connect"). The transmission of "Alerting", the associated "Receive Ready", and "Connect" continue in the SDCCH.

92

MN1788EU08MN_0001

Air Interface Um

Siemens

Mobile terminating call (MTC), continuation with OACSU

SDCCH

I (Alerting) Receive Ready

SDCCH

SDCCH

I (Connect) I (Assignment Command) (TCH-No.)

SDCCH

SDCCH FACCH

Receive Ready SABM UA

FACCH

FACCH

I (Assignment Complete) I (Connect Acknowledge)

FACCH

FACCH

Receive Ready

Fig. 36 Mobile terminating call, part 2b

MN1788EU08MN_0001

93

Siemens

Air Interface Um

From the view of the Mobile Station, the Handover procedure begins when the Base Station sends an I-frame with a "Handover Command" message in the FACCH valid up to that point. The message contains specifications of the new cell (e.g. color code, channel structure, timing advance), of the new speech channel (TCH) and a new Handover reference number. The Mobile Station acknowledges this I-frame with "Receive Ready". With this, the layer 2 connection in the remaining FACCH is cleared down locally. The old speech channel (TCH), together with its associated signaling channels (FACCH and SACCH), is now idle once more. The Mobile Station now logs-on in the new cell by transmitting four separate "Handover Access" messages in the FACCH of the new TCH. This message does not conform to the standard format of 23 Byte length; it is one byte long and comprises only the Handover reference number. The Mobile Station subsequently sets up with SABM the layer 2 connection in the new FACCH and, after receiving the UA, transmits the message "Handover Complete" in the first I-frame to the new Base Station. This Base Station responds with "Receive Ready". From the viewpoint of the Mobile Station, the handover is now completed.

94

MN1788EU08MN_0001

Air Interface Um

Siemens

Handover

I (Handover Command) (data about new cell, new TCH-No., handover reference)

FACCH old

FACCH old FACCH new FACCH new FACCH new FACCH new FACCH new

Receive Ready Handover Access (Handover Reference) Handover Access (Handover Reference) Handover Access (Handover Reference) Handover Access (Handover Reference) SABM UA

FACCH new

FACCH new

I (Handover Complete) Receive Ready

FACCH new

Fig. 37 Handover

MN1788EU08MN_0001

95

Siemens

Air Interface Um

The call cleardown can be initiated by either the Mobile Station or network side (i.e. the partner side). Here, only the cleardown of an established useful connection will be considered. If the Mobile Station initiates the cleardown, it sends the I-frame "Disconnect". The Base Station responds by clearing down the CM connection with the I-frame "Release", which is answered by "Release Complete". If the partner side initiates the cleardown, the Base Station transmits "Release" immediately. Again, the Mobile Station answers with "Release Complete". The MM connection is cleared down only locally. The RR connection, however must be cleared down explicitly. The Base Station must initiate the RR cleardown (irrespective of the initiating side for the user connection cleardown) by sending the Iframe "Channel Release". Finally, the Mobile Station clears down the layer 2 connection with DISC, which the Base Station acknowledges with UA. With this, all seized resources are released, and the connection cleardown is completed.

96

MN1788EU08MN_0001

Air Interface Um

Siemens

Call cleardown

Initiated by mobile station

FACCH

I (Disconnect) I (Release)

FACCH

FACCH

I (Release Complete) I (Channel Release)

FACCH

FACCH

DISC UA

FACCH

Initiated by partner side I (Release)

FACCH

FACCH

I (Release Complete) I (Channel Release)

FACCH

FACCH
UA

DISC

FACCH

Fig. 38 Call clear down

MN1788EU08MN_0001

97

Siemens

Air Interface Um

98

MN1788EU08MN_0001