GPRS Chap10

GPRS-Protocols and aspects of the air interface page137
9. Protocols and aspects of the GPRS air interface

Following the description of the physical and logical channels, as well as the used
burst type and the mapping of the logical channels onto a multiframe structure,
chapter shall give some details about the data transfer on the GPRS air interface.
Furthermore it describes the used strategies, protocols and functions used thereby.
Referencing to the chapter about the transmission planes, this block dives into the
physical layer and the RLC/MAC-layer. Thereby is no distinction taken between
transfer of signalling messages and transfer of traffic data.
The packet switched mode requires new concepts on the air interface, on one side,
the data throughput rate has to be enhanced, on the other side we have to fulfil the
integration of packet data transfer. This elicits of course consequences for the data
transfer mode on the air interface. About GSM we have to change the protocol stack,
the procedures of channel allocation as well as channel access. This chapter
describes the exchange of packet data units between the application side LLC and
the network are exchanged via the air interface.
LLC LLC
(Note)
RLC RLC
MAC MAC
Phys. Link Phys. Link
Phys. RF Phys. RF
Um
MS Network
Figure: Protocol stack on the air interface
9.1. The Physical Link Layer in GPRS
This paragraph shall give some information about the physical layer in more details.
First it has to be distinguished between the physical link layer and the physical RF
layer. The physical RF has the same tasks and functions as its counterpart of GSM,
or in other words, it stays the same. The modulation scheme GMSK and the used
carrier frequencies do not change. Only modification in this part will be the multislot
ability, the bundling of timeslots. The physical link layer shall convey the packets of
the RLC/MAC-layer via the air interface.
Main task of the Physical Link Layer is the date transport over the air interface, e.g.
traffic data being present as LLC frames or signalling information in RLC/MAC units.
It guarantees by this way the physical connection between the MS and the network.
Rohde & Schwarz Trainingcenter, V 1.0

Tasks of the Physical Link Layer:
♦ Block Coding:
Block coding is the insertion of Control Bits in the burst structure, e.g. the Uplink
State Flag USF or the Parity Check Bits.
♦ Forward Error Correction, FEC

Enables the detection and the correction of transmission errors. The forward error
correction is done with the aid of the presented convolutional coder, incidentally
the same as used in GSM, and the different Coding Schemes CS1-4.
Figure: Example of Convolutional coder
The convolutional coder possesses a memory of the last sent bits and links
every incoming bit with its past, the stored predecessor bits. At the output
normally we find words with a length longer than the input word, will say 1 bit.
The error correction ability is given due to the case, that the output can change
from one state into only other 2 states, depending of the actual input. Surges
another output signal as one of the expected ones, the decoder has detected
an error that must be corrected. The above-presented convolutional encoder
has a memory of K=5 bit and produce a codeword by the length of v=2 output
bit for every input. For example: All registers are pre-initialised with 0. With the
input sequence given in the table, the encoder produces the following output
signal:
Step Input Output 1 Output 2

1. Input 0 0 0
2. Input 1 1 1
3. Input 0 0 1
3. Input 1 1 0
Now we can see, after step 2, the Output State is 11 and with the possible
input values 0 or 1 the encoder can only generate the output sequence 01 or
10. If there is happening a transmission error, that means, the receiver detects
in the step 3 the sequence 00, we know, this sequence is impossible at this
moment and that there happened an transmission error which has to be
corrected due to the knowledge of the encoding principle.

♦ Interleaving:
The information is spread over 4 Bursts in a way, that associated or combined
information is distributed over different bursts. This guarantees the re-correction
or re-establishment of the original signal with the aid of the FEC because only
single bits are lost in case of a transmission fault on the radio link. For example, in
a burst the bits are spread in that way, that first, the complete sequence is
separated into two subblocks, one subblock carries only the even bit numbers, the
other the odd bit numbers.
♦ Recognition of jamming on the air interface
♦ Synchronisation, examination and adjustment of the Timing Advance value
♦ Functions to estimate the RxQUAL value, corresponding to the radio link quality
♦ Functions for the cell reselection, determination of the RxLEV, the received power
level.
♦ Power adjustment of the Transmitter
♦ Power control, e.g. discontinuous reception or transmission, DRX and DTX
♦ Burst generation
Serves to form the structure of a normal burst, e.g. insertion of the tail bits and the
training sequence.
9.2. RLC / MAC – layer
Main task of the RLC / MAC-layer is the data transport of its superior layer, LLC.
Further tasks are the control of the radio link and its access. In the first contemplation
step the feature data transport is considered, the functions used for the radio link
control are described in the following chapters.

As multiple other protocols, also the RLC/MAC protocol works belong the principle of
segmentation and encapsulation. Data of the application side, i.e. the superior layer
are embedded into a frame, together with a protocol header and the new frame will
be transferred. The segmentation principle segments the higher layer frame into
smaller parts, for that they can be embedded into the lower protocols layer frame.
LLC
frame FH Informationfield FCS
LLC
layer
RLC BH Info field BCS BH Info field BCS BH Info field BCS
blocks
RLC/MAC
Primary Following layer
block block
Physical
Normal burst Normal burst Normal burst Normal burst layer
FH = Frame Header BH = Block Header

FCS= Frame Check Sequence BCS= Block Check Sequence
Figure: Data flow in GPRS, segmentation
As to be seen in above figure, the RLC/MAC-layer forms a frame, called RLC-Block,

or Radio Block.
9.3. Radio Block structure
There are two different Radio Blocks defined, concerning their structure, one is used
for data transfer and the other is used for transfer of signalling information. Both
structures are presented in the figure below. Generally remarked is the fact, that in
this chapter signalling describes only the signalling information exchanged between
tow RLC/MAC-layers, i.e. signalling information of higher protocol layers is
considered as data.
A Radio Block consists of a MAC-Header, a Block Check Sequence BCS, a Data
field with either RLC-Data (=data of higher protocol layers) or signalling information
of the RLC/MAC-layer. The RLC Block header is optional and only present in case
that it is about a Radio Block transporting data of higher protocol layers. Furthermore
there is to be distinguished between Radio Blocks send in Uplink or Downlink.
As mentioned, the RLC-Header is only present in Radio Blocks used for data transfer
and it is of variable length, independent and different for either downlink or uplink.
The Block Check Sequence BCS forms a square sum that is calculated by
transmitting and after receiving. The comparison between the delivered BCS and the
calculated one in the receiver provides the detection of transmission errors.
The RLC-data field contains data of one ore more LLC-PDU’s, i.e. an LLC-data field.
The RLC/MAC-control field contains an RLC/MAC-control message, exchanged
between two RLC/MAC-layers.

RLC/MACblock
RLC/MAC blockstructure
structure
Radio Block structure for data transfer
MAC RLC
RLC Data BCS
Header Header
Radio Block structure for control message
MAC
RLC/MAC Control Message BCS
Header
Figure: Radio Block Structures for data transfer and signalling
9.4. Channel Coding
The channel coding performs the projection of an RLC-block onto Normal Bursts,
which are later on transmitted via a RF-channel to its destination entity. Further task
of the channel coding is the protection of the transferred data against transmission
errors on the air interface. The used physical transfer channel “radio interface” is
submitted to the physical effects like: multipath propagation, fading effects, time
delay, Doppler shift etc. The main principle of channel coding consists of redundant
data transfer, the transferred digital data is protected by redundant signals. The
already described covolutional coder transmits additional to the user data bit
sequence some redundancy bits, e.g. with the code rate of ½, each data bit is
transferred as a 2-bit word.
Channel coding in GPRS, Coding Schemes CS1 – CS4:

A comprehensible reflection of data transmission in GPRS is the fact, that forward
error correction is very helpful but not always essential. Depending on the quality of
the radio link it can be affirmed that additional redundancy, normally useful, can be
considered more or less as padding, slowing down the data throughput. The initial
statement of GPRS is the following: There are defined different Coding Schemes,
distinguishing each other in their different code rates, i.e. the level of redundancy.
From this results the ability of error correction. The rate between data throughput and
error correction or redundancy can be varied dynamically.

Possible is all that due to the 4 Coding Schemes CS-1 – CS-4 with currently different
net data throughput rate.
♦ CS-1: The coding scheme, originally developed for the SACCH, is also
used for Coding scheme 1. The net data throughput rate is 9.05 KBPS.
♦ CS-2: In this coding scheme, in the first step, the data bits are transferred
by the convolutional principle into a data word, containing redundancy.
Though it results, that the obtained data sequence is much larger than the
allowed data sequence, to be transferred over 4 Normal Bursts. With the
aid of the puncturing procedure, the obtained data rate after convolutional
coding is reduced to the maximum input data rate for the physical link
layer, i.e. the redundancy data rate is reduced. The resulting net data rate
is given with 13.4 KBPS.
♦ CS-3: Functions like CS-2 but with a much higher initial bit sequence and
therefore a much higher resulting redundancy rate. As net data rate we
obtain 15.6 KBPS.
♦ CS-4: This coding scheme does not use any kind of error correction. Solely
the Uplink State Flag, USF is pre-coded and error protected by redundancy
bits. All the traffic data bits are protected without error protection in this
layer. The error protection has to be performed by higher protocol layers.
The resulting maximal data rate is then given by 21.4 KBPS.
Scheme Code rate USF Pre-coded USF Radio Block excl. BCS Tail Coded Punctured Data rate
USF and BCS bits bits kb/s
CS-1 1/2 3 3 181 40 4 456 0 9.05
CS-2 ≈2/3 3 6 268 16 4 588 132 13.4
CS-3 ≈3/4 3 6 312 16 4 676 220 15.6
CS-4 1 3 12 428 16 - 456 - 21.4
Figure: Coding rates used for GPRS coding schemes
Above table shows an overview of the used coding schemes and the different
parameters used for the certain coding schemes. The column pre-coded USF
signifies, that the Uplink State Flag, USF, with the length of 3 bits is protected by a
pre-coding procedure that inserts some redundancy. For example: Pre-coded USF =
6 Bit in line CS-3 signifies, that the 3 bits of the USF are previously coded and
expressed with a 6 Bit word. Following this pre-coding procedure, there is the
described convolutional coding procedure. As example, we can read the line CS-1 as
follows: 3 Bit (Pre-coded USF) + 181 Bit (Radio Block) + 40 Bit (BCS) + 4 Bit (Tail) =
228 Bit. Due to the convolutional coding with the rate of ½ the result will be: 228 Bit *
2 = 456 Bit (Coded bits).
Puncturing:
In the above table it is clear to see, that there is a resulting data rate for the coding
schemes CS-2 and CS-3 of much more than the maximum data rate to be allowed to
be transferred to the physical link layer. Reminding, a Normal Burst contains two
information fields, each of them has a length of 57 Bit! => the transferred data rate
must be a multiple of this amount. The obtained 456 Bit, resulting of CS-1 can be
transferred within 4 Normal Bursts on the air interface, but the resulted data rate of
588 Bit respectively 676 Bit for CS-2 and CS-3 is too large. This is the reason, why it
is used the procedure of Puncturing. Puncturing signifies, the purposeful removal of

single redundancy bits after the channel coding. The code rate, corresponding to the
ability of error correction of the FEC is reduced by that way. Incidentally it shall be
remarked, that channel coding with the aim of error protection is not used in CS-4. By
that way, in CS-4 there is also no puncturing.
Radio Block
MAC-Header RLC
netto USF
RLC Data BCS
Header
Convolutional
Coding
Channel Puncturing
coding
456 Bit
Burst Forming
Radio Block
= 4 Bursts 57 Bit 57 Bit 57 Bit 57 Bit 57 Bit 57 Bit 57 Bit 57 Bit 57 Bit
Figure: Transition between net data rate -> channel coding -> Puncturing -> Normal
Burst
9..5. Medium Access Control, MAC: Channel allocation and Channel access
As already mentioned, GPRS offers the possibility to manage the physical resources
in uplink and downlink dynamically. Resulting is a so-called asymmetrical and
asynchronous data connection. Asynchronous means, that the data can be
transferred in an irregular mode, with various time intervals between. Asymmetric
means, that the data rate used in uplink and downlink can be differing from each
other. For that there will be no conflict in Uplink or Downlink, there is inserted the
protocol layer Medium Access Control, MAC. This protocol entity is responsible for
the sharing of the physical resource between different participants, or mobile stations.
The dividing of the physical resource in uplink and downlink can be performed in a
symmetrical or asymmetrical mode, i.e. there is a different allocation of the resources
to be at disposal.

Downlink Uplink Downlink Uplink
Symmetric data transfer Asymmetric data transfer
Synchronous data transfer
Sender Asynchronous data transfer Receiver
time
Figure: Difference symmetrical– asymmetrical and synchronous – asynchronous data

transfer
Allocation of a physical channel
The assignment of the physical resource required for the connection can be
performed in 3 variants: Fixed allocation, dynamic allocation or extended dynamic
allocation.
Fixed allocation:
This form of the channel assignment contains a starting point, the used timeslots and
eventually the length of the transmission, given in the number of radio blocks to be
transmitted. Regarded like this, the fixed allocation does not differ too much from the
mode of allocation used in a circuit switched connection. This mode is used for
example if the MS has requested a certain number of Radio-Blocks on the physical
interface.
Dynamic allocation:
This way of allocation describes the assignment of temporarily valid physical
resources. The assignment is strongly combined with the meaning of the Uplink State
Flag, USF. In each 52-multiframe there are 12 Radio Blocks contained. A mobile
station can use each of these blocks. But how to proceed, if more MS want to get
access to the same radio link?
Each Radio Block on the downlink channel contains a field with the Uplink State Flag,
USF. The USF can have values between 0 and 7, it is coded with 3 Bit. If an MS gets
the assignment of a physical resource and the allocation mode is dynamic allocation,
the MS will receive an USF-value, valid for that PDCH (=this timeslot on a certain
frequency). If the MS recognises its USF value in one downlink radio block, it has
received the permission to use the following uplink radio block on this physical
channel.

Extended dynamic allocation:

In case of extended dynamic allocation, a network dependent optional possibility, the
USF does not only point to the following Radio Block, furthermore it points to the
succeeding 4 Radio Blocks.
One special case shall be remarked: Does the PDCH contain not only PDTCH and
PACCH, but also PCCCH including the PRACH, the access channel where every MS
may send an Random Access Burst to request for a channel to initiate a connection,
the value USF = 111 indicates an PRACH on the Uplink. This means, a MS that
wants to initiate a connection, surveys all USF on that frequency channel containing
the channel combination including PCCCH and if the USF given in a downlink Radio
Block has the value USF =111, i.e. FREE it signifies, that the following uplink radio
block can be used to transmit such an Random Access Burst.
Monitoring USF in Block B(n)

Sends in Block B(n+1)
or in Blocks B(n+1) - B(n+4)
USF = R1
)
lock B(n
oB
Radi downlink
USF = R2
USF
k
USF = R3 uplin
)
k B(n+1
c
adio Blo
R
USF = Free
USF = Free
Monitoring Paging Channel
Send Access Burst
Figure: Dynamic Allocation on the physical channel

9.6. RLC / MAC – Block structure, details
This paragraph shall give some further details of the RLC / MAC – Structure, i.e. all
the elements, of which such a block consists. The protocol layer above the
RLC/MAC-layer is as well known the LLC-layer. By this way, the LLC-frames are
segmented and inserted into the data field of every RLC/MAC-block . The rough
structure of such an RLC/MAC-Block are already given a following:
RLC/MACblock
structure
MAC RLC
RLC Data BCS
Header Header
MAC
RLC/MAC Control Message BCS
Header
Figure: Structure of the RLC/MAC-Block
In the further description, the presentation of the Block Check Sequence, BCS will be
omitted, it does contain neither traffic data, nor signalling information. The resulting
structure of the RLC / MAC – Block will then be:
RLC/MACblock
structure

RLC/MAC block
RLC data block
MAC RLC
RLC Data Unit spare
Header Header
If necessary BCS
MAC Control
RLC/MAC Control Message
Header Header
RLC/MAC block
RLC/MAC control block

Figure: Structure RLC / MAC – Block, detailed presentation, without BCS
As to be seen, there are 2 different structures to be taken into consideration, one

used to transport data of higher layer protocols, the other used for transportation of
signalling information between two RLC peer entities. Furthermore there must to be
distinguished between Uplink and Downlink. The following figure describes the
succeeding different points of consideration. The structure of the following chapter is
given belong this picture, it describes the different RLC/MAC-blocks.
Differences in Block Structre
RLC/MAC - Block
Data Transfer Signalling
Downlink Uplink Downlink Uplink

•MAC-Header •MAC-Header •MAC-Header •MAC-Header
•RLC-Data Block •RLC-DataBlock •RLC/MAC-Control Block •RLC/MAC Control Block
Figure: Different structures of RLC/MAC-Blocks
The content of the spare-bits is always the value 0, their tasks are in case of an
overhang of the data field to fill up the content bit sequence up to the replenishment
of the burst. They are only used in that way and they do not have other functions.
it
9.7. GPRS RLC-Data Blocks, Data transfer.
The RLC Data Block consists of an RLC-Header, a data field, the RLC Data Unit and
spare bits if necessary. The length of the RLC Data Blocks depends of the used
Coding Scheme.
The following table, taken out of the GSM-Specifications shows the lengths of the
data field plus RLC-Header field in octets, corresponding to the used coding field.
RLC data block

Channel Coding size Number of
Scheme spare bits
CS-1 22 0
CS-2 32 7
CS-3 38 3
CS-4 52 7
Figure: Length of the RLC-Data Block, depending on the used Coding Scheme

RLCblock
RLC block size
size
RLC- Block structure for data transfer

RLC data block
RLC
RLC Data Unit spare
Header
Size =
RLC data
Channel block size RLC data
Number of
Coding without block size
spare bits
Scheme spare bits (octets)
(octets)
CS-1 22 0 22
CS-2 32 7 32 7/8
CS-3 38 3 38 3/8
CS-4 52 7 52 7/8
Figure: Length of the RLC-Blocks
In t he following consideration of the RLC-Data Blocks there must be distinguished

between Downlink and Uplink. The structure is different in both cases.
RLC-Data Block
structure
Downlink- Uplink -
direction direction

9.7.1. RLC/MAC-Data Block for data transfer in downlink:
First lets contemplate the RLC/MAC-Block like it is sent in downlink direction. It has
the following structure:
Bit
8 7 6 5 4 3 2 1
Payload Type RRBP S/P USF MAC Header
Octet 1
PR TFI FBI
Octet 2
Time to Live Protocol
BSN Header Checksum E
Length indicator M E Octet 3 (optional)
Length indicator M E Octet M (optional)
RLC Data
Octet N
Figure: RLC / MAC – Block structure for data transfer in downlink
Contemplating the single elements of the complete structure of this RLC/MAC-Block.

Starting with the MAC- Header:

MAC – Header for Data transfer in downlink:
Bit
8 7 6 5 4 3 2 1
Figure: MAC – Header structure for Downlink-data transfer
It signifies:
Uplink State Flag, USF:

As mentioned, the USF labels the legitimate user of the next uplink Radio
Blocks, i.e. the following 4 Normal Bursts that the MS is allowed to transmit in
uplink direction. The USF field is sent in all downlink RLC/MAC blocks and
indicates the owner or use of the next uplink Radio block on the same timeslot.
The USF field is three bits in length and eight different USF values can be
assigned, except on PCCCH, where the value '111' (USF=FREE) indicates
that the corresponding uplink Radio block contains PRACH.
Supplementary / Polling Bit, S/P:

The S/P bit is used to indicate whether the RRBP field is valid or not valid. 0 =
not valid, 1 = valid.
Relative Reserved Block Period, RRBP:

The RRBP value specifies a single uplink block in which the mobile station
shall transmit either a PACKET CONTROL ACKNOWLEDGEMENT message
or a PACCH block to the network. The two bits are indicating a time interval,
after that, the MS must send the control block. This procedure is valid in the
case if the RLC-block contains data as well as if it contains signalling
information.
Payload Type:
The Payload Type field shall indicate the type of data contained in remainder
of the RLC/MAC block. Again, the expression signalling in this chapter means
signalling of the RLC-layer and not signalling of higher protocol layers. This
field is essential, because of the packet oriented data transfer in GPRS there
are no fixed logical channels assigned to be used for signalling. The signalling
is inserted into the data flow and has to be indicated separately.

RLC-Data Block for data transfer in downlink:
Explaining now the structure of the RLC-Block, as it is used for data transfer in
downlink. Principally this block consists of a header, a data field and if necessary
some spare-bits.
Octet 1
PR TFI FBI
Octet 2
Octet 3 (optional)
Length indicator M E
RLC Data
Octet N
Figure: RLC-Block structure for data transport in downlink
Final Block Indicator, FBI (1 Bit):

The Final block indicator (FBI) bit indicates that the downlink RLC data block is
the last RLC data block of the downlink TBF.
0 = Current block is not last RLC data block in TBF
1 = Current block is last RLC data block in TBF
Temporary Flow Identifier, TFI (5 Bit) :

In RLC data blocks, the TFI identifies the Temporary Block Flow (TBF) to
which the RLC data block belongs. For the downlink and the uplink TFI the TFI
field is 5 bits in length and are encoded as a binary number with range 0 to 31.
In downlink RLC/MAC control blocks, the TFI identifies the Temporary Block
Flow (TBF) to which the RLC/MAC control message contained in the downlink
RLC/MAC control block relates. If present, this field indicates the mobile
station to which the control message is addressed, and all other mobile
stations shall ignore the control message. If this field is not present all mobile
stations shall interpret the contents of the control message.
Power Reduction, PR (2 Bit).

This field indicates how many dB the output power level of the actual RLC-
Block is reduced compared with the BCCH-carrier frequency channel. Remark:
At the moment, the feature Base Station Power Control in GPRS networks is
in experimental phase and not realised. For that reason, this field does not
have a signification at the moment.
Block Sequence Number, BSN (7 Bit):

The Block Sequence Number (BSN) field carries the sequence absolute Block
Sequence Number (BSN') modulo Sequence Number Space (SNS) (128 in GPRS
and 2048 in EGPRS) of each RLC data block within the TBF.
Extension Bit, E (1 Bit):

The Extension (E) bit is used to indicate the presence of an optional octet in
the RLC data block header 0 = additional octet follows immediately, 1 = no
additional octet follows.
Length Indicator, LI (6 Bit per Octet, usage is optional):

The Length Indicator is used to delimit LLC PDUs within the RLC data block.
The first Length Indicator shall indicate the number of octets of the RLC data
field belonging to the first LLC PDU, the second Length Indicator shall indicate
the number of octets of the RLC data field belonging to the second LLC PDU,
etc. Only the last segment of any LLC PDU of a TBF (either this segment
carries the entire LLC PDU or not) shall be identified with a Length Indicator
within the corresponding RLC data block.
More Bit, M (1 Bit):

In GPRS TBF mode, the M bit, along with the E bit and the Length Indicator
(LI), are used to delimit LLC PDUs within a TBF. When the M bit is present it
indicates whether or not another LLC PDU follows the current one within the
RLC data block.
RLC Data (variable, depends on used Coding Scheme):

The RLC data field contains the bits sequences of the higher protocol layers.
Its length is variable and also depending from the used coding scheme. The
length varies between 19, 29, 35 or 49 Octets.

9.7.2. RLC/MAC – Block for data transfer in Uplink
The Structure of a RLC/MAC-Block for data transfer in uplink is given belong the
following figure:
Bit
8 7 6 5 4 3 2 1
Payload Type Countdown Value SI R MAC Header
Octet 1
Spare PI TFI FBI
Octet 2
TLLI
PFI
RLC Data
Octet N
Figure: RLC/MAC – Block for data transfer in Uplink
Also here we have to distinguish in our consideration between MAC-Header and the
RLC-Data block.

MAC – Header for Data transfer in Uplink:
The MAC-Header for data transfer in Uplink has the following structure:
Bit
8 7 6 5 4 3 2 1
Payload Type Countdown Value SI R MAC Header
Figure: MAC-Header for Data transfer in Uplink
The single field are corresponding to:
Retry – Bit, R (1 Bit):

The Retry (R) bit shall indicate whether the mobile station transmitted the
CHANNEL REQUEST message, PACKET CHANNEL REQUEST message, or
EGPRS PACKET CHANNEL REQUEST message one time or more than one
time during its most recent channel access. The mobile station shall send the
same value for the R bit in each uplink RLC/MAC block of the TBF. O = MS
has sent channel request – only 1 time, 1 = channel request – message sent
more than 1 time.
Stall Indicator, SI (2 Bit):

The Stall indicator (SI) bit indicates whether the mobile's RLC transmit window
can advance (i.e., is not stalled) or can not advance (i.e., is stalled). The
mobile station shall set the SI bit in all uplink RLC data blocks. 0 = MS transmit
window is not stalled, 1 = MS transmit window is stalled
Countdown Value, CV (4 Bits):

The Countdown Value (CV) field is sent by the mobile station to allow the
network to calculate the number of RLC data blocks remaining for the current
uplink TBF. It enables the network to estimate the number of radio blocks still
to be sent. The CV field is 4 bits in length and is encoded as a binary number
with range 0 to 15. This forms more or less a counter that’s value is decrement
from 15 up to 0 to countdown the last Radio Blocks.
Payload Type:
This field indicates if the following RLC-Block contains signalling data or traffic
data. Does this field contain the value 0 0 , so it is implicated, that the content
of the RLC-block field is given as traffic data.

RLC-Data Block for Data Transfer in Uplink:
The RLC-Data Block for Data transfer in Uplink consists, same as its counterpart for
the downlink direction of a header field, a data field and some eventually spare-bits.
Bit
8 7 6 5 24 3 2 1
Octet 1
Spare PI TFI TI
Octet 2
TLLI
PFI
RLC Data
Octet N
Figure: RLC – Data Block for Data transfer in Uplink:
The single fields signify:
TLLI Indicator Bit, TI ( 1 Bit):

Indicates, that there is an optional TLLI-field within the RLC-data block
Temporary Flow Identifier, TFI:

In RLC data blocks, the TFI identifies the Temporary Block Flow (TBF) to
which the RLC data block belongs.
PFI Indicator Bit, PI (1 Bit):

Index for the existence of an optional PFI – field.
Block Sequence Number, BSN (7 Bit):

The Block Sequence Number BSN carries the reference number to indicate
the position of the actual RLC-block within the total TBF.

Extension Bit, E (1 Bit):

Indicator if an extension octet follows to the header.
Length Indicator, LI and M-Bit:

Same function as in downlink, i.e. indicate that in the presented RLC are
eventually more LLC PDU’s and are giving the length to reference them.
Temporary Logical Link Identifier, TLLI ( 4 Octets, optional):

The optional TLLI field contains a TLLI encoded as the contents of the TLLI
information element. TLLI is the identifier for the logical link between the
SGSN and the MS. The TLLI is only transmitted within the first 3 Radio Blocks
only in uplink to guarantee, that the legitimated user uses the uplink resource.
Packet Flow Identifier, PFI.

The PFI field contains a PFI value encoded as the contents of the PFI
information element as defined in 3G TS 24.008, the UMTS – Specifications.
The Packet Flow Identifier allows additional parameter to determine the data
flow context, e.g. the priority level.
Data field, RLC-Data:

Same as in downlink, this field contains the data of higher protocol layers. Its
length is variable and depends on the used coding scheme.

9.8. RLC/MAC-Block for Signalling
The RLC/MAC-Block is also used to convey signalling information, but again, hereby
it is only meant the signalling between two RLC-entities. Signalling messages of
higher protocol layers are regarded by the RLC/MAC-layer as traffic data, there is no
further distinction. A RLC/MAC-Block used for transport of signalling information has
the following general structure:
MAC Control
RLC/MAC Control Message
Header Header
RLC/MAC block
RLC/MAC control block

Figure: RLC/MAC-Block structure for signalling
The RLC/MAC-Block for signalling consists of a MAC-Header, an optional RLC-

Control-Header and a field, that contains the RLC/MAC-signalling information
message.
For the case of signalling transfer, it is always used the coding scheme 1, i.e. there is
automatically chosen the best error protection level.
Also in this case, it has to be distinguished between uplink and downlink.

9.8.1. RLC/MAC-Block for Signalling in Downlink
The RLC/MAC-Block naturally used for the convey of signalling messages, but only
signalling messages of the RLC/MAC-layer possesses the following detailed
structure:
Bit
8 7 6 5 4 3 2 1
RBSN FS AC Octet 1 (optional)

RTI
PR TFI Header Checksum D Octet 2 (optional)
Octet M
Control Message Contents
Octet 22
Figure: RLC/MAC-Block for Signalling in Downlink
MAC-Header for Signalling in Downlink
Again it has to be distinguished between MAC-Header and RLC-Data-Block. The

MAC-Header has the main task to indicate the following RLC-data block as carrier of
signalling messages. The structure of only the MAC-Header looks like:
Bit
8 7 6 5 4 3 2 1
The single fields are corresponding to:
Uplink State Flag, USF (3 Bit):

Is used to indicate the legitimated user or owner of the following Radio Block.
The USF is contained in every downlink Radio Block, independent if this
carries traffic data or signalling messages.

Supplementary / Polling Bit, S/P (1 Bit):

The S/P bit is used to indicate whether the RRBP field is valid or not valid. By
that way, the MS can be “polled”, i.e. the MS is invited to send a control
message within a PACCH-Block.
Relative Reserved Block Period, RRBP (2 Bit):

Same procedure as in the case of data transfer. There is given a time offset
value, relative to the actual frame number, after that the MS is requested to
send an control block on the PACCH.
Payload Type (2 Bit):

This field distinguishes the content of the RLC-data field as followed:
01 RLC/MAC block contains an RLC/MAC control block that does
not include the optional octets of the RLC/MAC control header
10 In the downlink direction, the RLC/MAC block contains an
RLC/MAC control block that includes the optional first octet of the
RLC/MAC control header. In the uplink direction, this value is
reserved.
The value 11 is used for future developments.
RLC-Data Block for Signalling in Downlink
Hereby there are existing two possibilities how the structure or the block can look
like. One possibility is, that the RLC-Data Block contains fully a whole RLC/MAC-
Signalling message, the other possibility is that the RLC-Data-Block contains an
additional Header-Field that gives further information. Which one of both possibilities
is used, depends on the signalling message that is transmitted.
The general structure is given as followed:
Bit
8 7 6 5 4 3 2 1
RBSN RTI FS AC Octet 1 (optional)
PR TFI Header Checksum D Octet 2 (optional)
Octet M
Octet 22
Figure: RLC-Data Block for Signalling in Downlink, including the optional RLC-
Header field

The single fields of this block contain the following information:
Reduced Block Sequence Number Bit, RBSN (1 Bit):

The Reduced Block Sequence Number (RBSN) bit carries the sequence
number of the downlink RLC/MAC control blocks. The RBSN bit is encoded as
a binary number with range 0 to 1.
Radio Transaction Identifier, RTI (5 Bit):

The Radio Transaction Identifier (RTI) field is used to group the downlink
RLC/MAC control blocks that make up an RLC/MAC control message and
identifies the segmented control message sequence with which the downlink
RLC/MAC control block is associated. The RTI field is five bits in length with
range 0 to 31.
Final Segment Bit, FS (1 Bit):

The Final Segment (FS) bit indicates that the downlink RLC/MAC control block
contains the final segment of an RLC/MAC control message. 0 = Current block
does not contain the final segment of an RLC/MAC control message, 1 =
Current block contains the final segment of an RLC/MAC control message
Access Control Bit, AC (1 Bit):

The Address Control (AC) bit is used to indicate the presence of the optional
TFI/D octet in the header of downlink RLC/MAC control blocks. 0 = additional
octet with TFI/D-field, 1 = immediately following octet contains to the header
and carries the TFI/D-field.
Power Reduction Field, PR (2 Bit):

The Power Reduction (PR) field indicates the power level reduction of the
current RLC block. This touches only the downlink messages and refers to the
feature that the BTS reduces its transmitting power on all channels except the
BCCH carrier. Certainly, this feature will not be used in the first realisation
step.
Temporary Flow Identity, TFI (5 Bit):

Just like in the case of data transfer, this field identifies the Temporary Block
Flow, TBF. In Downlink-Signalling messages, due to this field, the user or
receiver of the message can be addressed.
Direction Bit, D (1 Bit):

The Direction (D) bit indicates the direction of the TBF identified by the TFI
field in the downlink RLC/MAC control block header. 0 = TBF in Downlink, 1 =
TBF in Uplink.
Control Message Content:

The rest of this field contains the original signalling message that is exchanged
between the two RLC/MAC-entities. Its length is fixed and is given always as
22 Octets. This is derived from the fact, that for signalling messages transfer,
always Coding Schemes CS-1 are used, synonymous with maximum security.

9.8.2. RLC/MAC-Block for Signalling in Uplink
As last case we want to consider the case of transfer of signalling messages in uplink
direction. In that case, we found the block structure given as followed:
Bit
8 7 6 5 4 3 2 1
Payload Type spare R MAC Header
Octet 1
Octet 22
Figure: RLC/MAC-Block for Signalling in Uplink
In the case of uplink, the only important and relevant field is the MAC-header that
distinguishes between signalling messages and data transfer.
MAC-Header for Signalling in Uplink:
Bit
8 7 6 5 4 3 2 1
Payload Type spare R MAC Header
Figure: MAC-Header for Signalling in Uplink
On the first view it can be seen, that the MAC-Header has a completely reduced
format. In effective, there are only two relevant fields:
Payload Type (2 Bit):

Identifies the content of the RLC-Block as signalling. In uplink it can be
distinguished between the following parameters:
00 RLC/MAC Block contains RLC-data block
01 RLC/MAC Block contains RLC/MAC Control Block, i.e. signalling
message for the RLC-layer.
Retry Bit, R (1 Bit):

Just as in the case of data transfer, this bit indicates whether the Channel
Request message on the PRACH or RACH at the beginning of the TBF
establishment was sent one time or more.

Spare (5 Bit):
Filling bits, those are set on 0, without further signification.
RLC-Data Block for Signalling in Uplink:
In Uplink direction there is no RLC-header for signalling. There is only a data field
that contains exclusively signalling information. The length of this field is fixed and is
about 22 octets. Channel coding is performed belonging to Coding Scheme 1.
9.9. RLC-Signalling messages
Via the RLC/MAC-Layer the Radio Resource Management is sending a lot of

signalling messages. The following figures are presenting the allowed signalling
messages exchanged between MS and network. It shall again be reminded, that
these messages are only those of the RLC-layer, referring to the air interface, or
radio resource management. Further signalling messages are part of higher layer
protocols, for example messages of the GPRS Mobility Management, GMM or
Session Management. These messages are transported via the LLC-layer and are
regarded as traffic data by the RLC/MAC-layer.
GRR Signalling Messages(Via RLC/MAC)
Downlink Messages
•Packet TBF Release
• Packet Access Reject •Packet Uplink Ack /Nack
• Packet Cell Change Order •Packet Uplink Assignment
• Packet Downlink Assignment •Packet Downlink Dummy Control Block
• Packet Paging Request •Packet System Information Type 1
• Packet PDCH Release •Packet System Information Type 2
• Packet Polling Request •Packet System Information Type 3
• Packet Power Control/Timing Advance •Packet System Information Type 3 bis
• Packet PRACH Parameters •Packet System Information Type 4
• Packet Queueing Notification •Packet System Information Type 5
• Packet Timeslot Reconfigure •Packet System Information Type 13
Figure: Messages of the Radio Resource Management transferred via the RLC/MAC
layer in downlink-direction

GRR Signalling Messages (Via RLC/MAC)
• Uplink Messages
• Packet Cell Change Failure
• Packet Control Acknowledgement
• Packet Downlink Ack/Nack
• Packet Uplink Dummy Control Block
• Packet Measurement Report
• Packet Resource Request
• Packet Mobile TBF Status (SMG #30+)
• Packet PSI Status (SMG #30+)
Figure: Messages of the Radio Resource Management sent via the RLC/MAC in
uplink-direction
9.10. Access to the radio interface: 1 Phase Access and 2 Phase Access
Previous chapters are describing the procedure, how a data transfer is initiated via
the MM-context activation procedure and the PDP context activation procedure. But
these processes are performed by higher layer protocols. The following paragraph
shall describe the physical channel activation procedure or the request for physical
resource. It is explained, how data is transferred via the radio link, with the help of the
transport structure: Radio Block. But it is actually not described how the allocation of
uplink or downlink physical resource is been performed.
Mobile Originated Packet Transfer

Prerequisite for any kind of data transfer is the previous MM and PDP context
activation. These are messages of higher protocol layers and they have to be
embedded in lower layer messages, e.g. the Channel Request message in the RLC
layer shall indicate this higher layer request. The data to be transferred can be a
bursty application, there is no continuous data transfer, and it is running in bursty
intervals. Before the continuation of the physical data transfer there must be an
renewed physical resource activation procedure.
How is the request for physical channel resource performed in GPRS and how is the
allocation of physical resource realised?
In GPRS it must be distinguished between one phase and two phase access. The
one phase access is mandatory, while the two phase access is optional for the
network. The MS has to perform both kind of access routines, depending what the
network requires.

The following figure describes the two phases in radio network access:
Mobile Originated Packet Transfer
Net-
MS work
Packet Channel Request

1 PRACH or RACH
Phase One
Phase One Access
Packet Immediate Assignment Access
2 PAGCH or AGCH
Packet Resource Request

3 PACCH Phase Two
Phase Two Access
Access
Packet Resource Assignment (optional)
4 PACCH
Figure: Radio network access in one phase or two phases
1. Packet Channel Request

The Uplink Packet Transfer is initiated by a Packet Channel Request message,
sent from the MS. This message can either be send on a RACH or PRACH. The
MS has two possibilities to indicate or request a physical resource. One
possibility is the request for an uplink radio block, i.e. the physical resource
needed is only one radio block. This is used in the case of higher layer signalling
messages, for example the GPRS Attach request message is indicated in that
way. Or the MS has the possibility to initiate the two phase access in that way,
the first Packet Channel Request Message requests only one radio block, but
the message sent in this allocated radio block will then be a Packet Resource
Request message to request more radio resource.
The second possibility is the request for a PDCH, the network gets the
information that the MS requests for a PDCH. But the result of this message will
be the allocation of a single PDCH, i.e. physical resource on one timeslot.
2. Packet Immediate Assignment

The network assigns physical channel resource with the aid of the Packet
Immediate Assignment message. The assignment of physical resource shall
consider the needed channel capacity. But this seems to be the problem, GPRS
allows a lot of different data transfer combination, for example in the chapter

about GPRS Services there were given a lot of Quality of Service Profiles.
Compared to GSM, where the request was only Full Rate Traffic Channel or only
signalling message on SDCCH, GPRS allows much more. But the MS need more
capacity in the request message to describe more detailed the needed physical
resource. But this capacity is not available in Packet Channel Request message
sent within an Access Burst. The network has, after the reception of such an
Access Burst only few information about the requested service and therefore how
much physical channel resource shall be assigned.
• The network assigns one single PDCH, i.e. one timeslot on one frequency
channel. If the MS would request more, it will answer with the additional
Packet Resource Request message on the assigned PDCH.
• Another possibility is, that the network assigns only physical resource about
one uplink radio block. This is done in that way, if the MS has only
requested one uplink radio block, practically done to transmit signalling
messages, e.g. GPRS Attach. But the network to request the two-phase
access can also use this procedure. If the MS has requested a PDCH, the
network will assign only a single uplink radio block, knowing that this is
much less then needed to force the MS to react with the transmission of a
Packet Resource Request message and handing out further information
about the required service.
Power Control (PC) and Timing Advance (TA) information is included in the
Packet Uplink Assignment message.
The one phase network access is restricted to the two messages Packet Channel
Request and Packet Immediate Assignment.
The two-phase access is always initiated if the MS is not content with the assigned
physical resource, it requests much more. Its use is optional, depending on the
requested service.
3. Packet Resource Request

This message includes a detailed description of the requested service and of the
requested physical channel resource.
4. Packet Resource Assignment
This message is the answer of the network to the requested resource and
contains a channel description element, indicating what physical channel
resource is assigned on the uplink direction. Power Control (PC) and Timing
Advance (TA) information are included into this message.
The MS has after receipt of this message no further possibility to request more
physical resource, it may only terminate the connection if the assigned resource
does not fit with the desired service.
Both messages, Packet Resource Request and Packet Resource Assignment are
transmitted on the PACCH.

GPRS Chap10

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

GPRS Chap10

Enviado por

Direitos autorais:

Formatos disponíveis

GPRS-Protocols and aspects of the air interface page137

9. Protocols and aspects of the GPRS air interface

Figure: Protocol stack on the air interface

9.1. The Physical Link Layer in GPRS

Rohde & Schwarz Trainingcenter, V 1.0

Tasks of the Physical Link Layer:

♦ Forward Error Correction, FEC

Figure: Example of Convolutional coder

Step Input Output 1 Output 2

Rohde & Schwarz Trainingcenter, V 1.0

♦ Recognition of jamming on the air interface

♦ Synchronisation, examination and adjustment of the Timing Advance value

♦ Power adjustment of the Transmitter

♦ Power control, e.g. discontinuous reception or transmission, DRX and DTX

9.2. RLC / MAC – layer

Rohde & Schwarz Trainingcenter, V 1.0

FH = Frame Header BH = Block Header

Figure: Data flow in GPRS, segmentation

As to be seen in above figure, the RLC/MAC-layer forms a frame, called RLC-Block,

9.3. Radio Block structure

Rohde & Schwarz Trainingcenter, V 1.0

Radio Block structure for data transfer

Radio Block structure for control message

9.4. Channel Coding

Channel coding in GPRS, Coding Schemes CS1 – CS4:

Rohde & Schwarz Trainingcenter, V 1.0

CS-3 ≈3/4 3 6 312 16 4 676 220 15.6

CS-4 1 3 12 428 16 - 456 - 21.4

Figure: Coding rates used for GPRS coding schemes

is used the procedure of Puncturing. Puncturing signifies, the purposeful removal of

Rohde & Schwarz Trainingcenter, V 1.0

Symmetric data transfer Asymmetric data transfer

Synchronous data transfer

Sender Asynchronous data transfer Receiver

Figure: Difference symmetrical– asymmetrical and synchronous – asynchronous data

Allocation of a physical channel

Rohde & Schwarz Trainingcenter, V 1.0

Extended dynamic allocation:

Monitoring USF in Block B(n)

Rohde & Schwarz Trainingcenter, V 1.0

9.6. RLC / MAC – Block structure, details

Radio Block structure for data transfer

Radio Block structure for control message

Radio Block structure for data transfer

RLC/MAC control block

As to be seen, there are 2 different structures to be taken into consideration, one

Differences in Block Structre

Data Transfer Signalling

Downlink Uplink Downlink Uplink

Figure: Different structures of RLC/MAC-Blocks

RLC data block

Rohde & Schwarz Trainingcenter, V 1.0

RLC- Block structure for data transfer

Figure: Length of the RLC-Blocks

In t he following consideration of the RLC-Data Blocks there must be distinguished

Rohde & Schwarz Trainingcenter, V 1.0

9.7.1. RLC/MAC-Data Block for data transfer in downlink:

Payload Type RRBP S/P USF MAC Header

Length indicator M E Octet 3 (optional)

Length indicator M E Octet M (optional)

Figure: RLC / MAC – Block structure for data transfer in downlink

Contemplating the single elements of the complete structure of this RLC/MAC-Block.

Rohde & Schwarz Trainingcenter, V 1.0

MAC – Header for Data transfer in downlink: