GPRS Measurements in TEMS Products

White Paper

GPRS Measurements in TEMS Products White Paper

2/14/02

Ascom 2009. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright holder. TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders. The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ascom shall have no liability for any error or damage of any kind resulting from the use of this document.

2 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

Contents

1.
1.1. 1.2. 1.3. 1.4. 1.5. 1.6. 1.7.

Introduction ...............................................................................4
General ............................................................................................. 4 The GPRS Protocol Stack................................................................. 4 The GPRS Protocol Reference Model............................................... 6 The GPRS Frame Structure .............................................................. 7 Channel Coding of the RLC/MAC Layer............................................ 8 Mapping of Radio Blocks onto the GPRS Frame Structure ............. 10 RLC/MAC Throughput Calculations ................................................ 12

2.
2.1. 2.2. 2.3.

GPRS RF Measurements........................................................14
BER/Timeslot (%) ........................................................................... 15 FER/Timeslot (%)............................................................................ 16 Coding Scheme Downlink Usage (%) ............................................. 17

3.
3.1. 3.2.

RLC/MAC Layer Measurements .............................................18

RLC/MAC Reports .......................................................................... 18 RLC/MAC Information Elements ..................................................... 26

4.
4.1. 4.2. 4.3.

LLC Layer Measurements .......................................................28

LLC Layer Description..................................................................... 28 LLC Reports.................................................................................... 29 LLC Information Elements............................................................... 31

5.

Abbreviations ..........................................................................32

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

3 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

1.

Introduction

1.1. General
This chapter gives an introduction to the frame structure and channel coding in GPRS, also showing how data blocks are mapped onto the frame structure.

The GPRS protocol stack is described, and various theoretical maximum throughput values are explained for the RLC/MAC layer. The other chapters will refer to this chapter when calculating the throughput, retransmission, and decode error figures presented in the TEMS products.

1.2. The GPRS Protocol Stack

Figure 1 below shows the GPRS protocol stack layers, indicating which layers are located in the PC and which are in the mobile phone. PC user applications could be e.g. FTP, HTTP, or mail transfer protocols.

4 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

MOBILE PHONE

WAP USER APPLICATION UDP (WDP)

PC
WINSOCK

TCP IP

UDP
WINDOWSTM

L3MM

SMS

IP

PPP

DIAL UP

PPP

SNDCP

LLC

RLC/MAC

DOCUMENT SCOPE

GSM RF

Figure 1 The GPRS protocol stack.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

5 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

1.3. The GPRS Protocol Reference Model

Figure 2 shows the protocol stacks and layers in GPRS and the interfaces between the stacks. The RLC/MAC layer is handled in the BSS by the packet control unit, PCU, which receives LLC frames, builds RLC/MAC radio blocks, and handles retransmissions due to errors in the air interface (Um). The PCU could be located in the BTS, in the BSC, or even in the SGSN (in the latter case the Gb interface is inside the SGSN node). The application layer on top of IP could be TCP or UDP, handling user applications such as FTP or HTTP.

Application

Application IP
RELAY

IP

SNDCP

SNDCP

GTP

GTP

LLC
RELAY

LLC BSSGP
FrameRelay

UDP/TCP IP L2 L1

UDP/TCP

RLC/MAC

RLC/MAC

BSSGP
FrameRelay

IP L2 L1

GSM RF

GSM RF

L1bis

L1bis

MS

Um

BSS

Gb

SGSN

Gn

GGSN

Figure 2 The GPRS Protocol Reference Model

6 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

1.4. The GPRS Frame Structure

A GSM TDMA frame is built up by eight consecutive timeslots. Each timeslot will build up a logical frame structure, used for carrying e.g. BCCH information, paging information, speech, or data. In the GPRS case, each timeslot used for data could be shared by several simultaneous users by assigning different TFIs, temporary flow identities, to the users. Also one user can be assigned one or several timeslots.

Forming the 52-multiframe

1 2 3 4 5 One TDMA frame consists of eight timeslots, numbered 0 to 7.

The eight timeslots will be repeated, forming a continuous stream of TDMA frames where each timeslot could be set up for different types of data. In this case, timeslot 2 is configured for handling GPRS data.

T T T T T T T T T T T T P T T T T T T T T T T T T X T T T T T T T T T T T T P T T T T T T T T T T T T X 0 1 2 3 ...... 12 25 38 51

52 consecutive frames (timeslot number 2 shown) form a 52-multiframe.

Figure 3 The 52 multiframe used in GPRS.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

7 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

The 52-multiframe consists of 52 consecutive assigned timeslots with the same number (e.g. TS 2 as in Figure 3 Of the 52 timeslots, 48 are used for sending the actual GPRS data. Of the remaining four, the two timeslots marked X (nos. 25 and 51) are used for neighbour cell identification, similar to the IDLE frame in the 26 multiframe in the speech case. The mobile searches the SCH burst that holds the BSIC and timing information for the neighbour. During the X timeslot, the serving cell does not receive or transmit anything. Finally, the two timeslots marked P (nos. 12 and 38) form the PTCCH channel used for timing advance regulation.

1.5. Channel Coding of the RLC/MAC Layer

The RLC/MAC data is transmitted in radio blocks, the structure of which is defined in GSM specification 04.60. Both control blocks (with signalling information) and data blocks (with user data) uses a structure with a MAC header of one octet, followed by RLC data. The MAC header structure differs between the uplink- and downlink. The RLC data structure depends on the type of data in the block (control or user data). For user data a two octet RLC header is followed by the RLC data field containing the payload.

Octet 1 Octet 2 Octet 3 Octet 4 . . .

7 6 Payload Type

5 RRBP

3 S/P

1 USF

Bit no. MAC Header RLC Header

RLC Payload

Octet N Figure 4 The GPRS radio block structure for downlink user data.

8 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

The size of the radio blocks (N) depends on the coding scheme used when transmitting the block. The value of N corresponds to the number of bytes (octets) and differs between the different coding schemes according to Table 1 below. A control block is always coded with CS-1 while data can be coded using any of the four coding schemes.

Coding Scheme CS-1 CS-2 CS-3 CS-4

N (including MAC header) 23 33 39 53

RLC Payload data block size 20 30 36 50

Table 1 The size of the radio block for each coding scheme.

Each radio block is assembled differently depending on the coding scheme used. However, regardless of coding scheme, each radio block must be made 456 bits long in the end in order to fit it into the GSM bursts, as explained in section 1.6 below.

Before the application of channel coding, each radio block is assembled according to the table below. The spare bits added are padding needed to adapt the radio block size to the channel coder.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

9 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

Radio block size CS-1 CS-2 CS-3 CS-4 23*8 33*8 39*8 53*8

Spare bits added 0 7 3 7

Radioblock size excl. USF 23*8 + 0 3 = 181 33*8 + 7 3 = 268 39*8 + 3 3 = 312 53*8 + 7 3 = 428

USF

Precoded USF 3 6 6 12

BCS

Tail

3 3 3 3

40 16 16 16

4 4 4 0

Total no of bits per radioblock 181+3+40 +4 = 228 268+6+16 +4 = 294 312+6+16 +4 = 338 428+12+ 16+0=456

Table 2 Structure of radio block prior to channel coding.

The USF is precoded with a block code in the CS-2, CS-3, and CS-4 case in order to detect any errors in it. The block check sequence (BCS) is a block code for the whole radio block used for error detection. The rightmost column shows the total number of bits per radio block before it is put into the channel coder. CS-4 is a bit special since no channel coding is used at all; the bits are sent over the air interface with no protection. The channel coder used in CS-1, CS-2, and CS-3 is the same convolutional encoder as the one used for GSM signalling (i.e. SACCH, BCCH, FACCH etc.)

The channel encoder doubles the number of bits in CS-1, CS-2, and CS-3 (rate ) but leaves CS-4 uncoded. To bring down the number of bits to 456 as required, puncturing is used in CS-2 and CS-3. The resulting radio block is now ready for burst formatting.

CS-1 CS-2 CS-3 CS-4

Total no of bits Code rate Total no of bits Punctured bits No of bits to per radioblock after coding send 228 228*2 = 456 0 4560 = 456 294 294*2 = 588 132 588132 =456 338 338*2 = 676 220 676-220 = 456 456 1 456*1 = 456 0 4560 = 456 Table 3 Channel coding of radio blocks, each ending up 456 in length.

1.6. Mapping of Radio Blocks onto the GPRS Frame Structure

10 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

As explained in section 1.5, all GPRS blocks will end up containing 456 bits per frame, regardless of the coding scheme used. These 456 bits are split up into a number of bursts and mapped onto the 52-multiframe structure. The first thing to do is to split the 456 bits into eight parts containing 57 bits each, see Figure 5.

456

57

57

57

57

57

57

57

57

Figure 5 The 456 bits containing a coded radio block are split up into eight 57-bit blocks.
The data is then to be inserted into bursts (a burst is the data stream transmitted in one timeslot). Figure 6 below shows a normal burst in GSM (there are other types of bursts as well, but they will not be explained in this document). As can be seen, the normal burst has room for two data bit segments each of length 57 bits.

TAIL(3)

DATA(57 )

FACCH FLAG(1)

TSC(26)

FACCH FLAG(1)

DATA(57)

TAIL(3)

GUARD (8.25)

Figure 6 The structure of the normal burst in GSM.

The eight 57-bit segments constituting a radio block will thus take up four bursts. Interleaving is applied to four whole bursts at a time, i.e. to entire radio blocks.

The exact mapping can be found in Figure 7, where al are GPRS radio blocks.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

11 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

Each 52-multiframe contains 12 radio blocks.

a a a a b b b b c c c c P d d d d e e e e f f f f X g g g g h h h h i i i i P j j j j k k k k l l l l X 0 1 2 3 ...... 12 25 38 51

Figure 7 Distribution of radio blocks in the 52-multiframe.

1.7. RLC/MAC Throughput Calculations

In the literature, a number of different throughput values for GPRS are mentioned. This chapter intends to explain these throughput values. Throughout the chapter, in order to calculate bits per second, use is made of the fact that 8 bits = 1 byte and that there are 50 radio blocks per second. Note that the latter is an exact value and no approximation. As seen in Figure 7 above, there are 12 blocks per 52- multiframe; one 52-multiframe is exactly 52*120/26 = 240 ms; thus there are 12 blocks every 240 ms, or 12/0.240 = 50 blocks per second. If several timeslots are assigned, the calculated throughput should be multiplied by the number of timeslots.

RLC PAYLOAD THROUGHPUT This is the rate at which the LLC layer can receive data from and send data to the RLC/MAC layer.

Coding Scheme CS-1 CS-2 CS-3 CS-4

N (including MAC header) 23 33 39 53

RLC Payload data block size (bytes) 20 30 36 50

RLC Payload data throughput (bit/s)1 20*8*50 = 8000 30*8*50 = 12000 36*8*50 = 14400 50*8*50 = 20000

1 RLC Payload data throughput (bit/s) = (RLC Payload data block size) * 8 * 50

Table 4 RLC payload throughput calculations

12 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

RADIO BLOCK THROUGHPUT WITHOUT USF This is the throughput within the RLC/MAC layer, with the whole RLC header included (together with the MAC header), but with the uplink state flag (USF) excluded. The spare bits added for CS-2, CS-3, and CS-4 are included.

Coding Scheme CS-1 CS-2 CS-3 CS-4

1 See Table 2 on page 10

N (including MAC header) 23 33 39 53

Radio block size including spare bits but excl. USF1 23*8 + 0 3 = 181 33*8 + 7 3 = 268 39*8 + 3 3 = 312 53*8 + 7 3 = 428

Radio block excl. USF throughput (bit/s)2 181*50 = 9050 268*50 = 13400 312*50 = 15600 428*50 = 21400

2 Throughput (bit/s) = (Radio block size including spare bits but excl. USF) * 50

Table 5 Radio block throughput calculations, without USF

RADIO BLOCK THROUGHPUT WITH SPARE BITS INCLUDED This is the throughput within the RLC/MAC layer when the whole radio block is counted, including the whole RLC/MAC header and spare bits.

Coding Scheme CS-1 CS-2 CS-3 CS-4

N (including MAC header) 23 33 39 53

Radio block size including spare bits 23*8 + 0 = 184 33*8 + 7 = 271 39*8 + 3 = 315 53*8 + 7 = 431

Radio block throughput (bit/s)1 184*50 = 9200 271*50 = 13550 315*50 = 15750 431*50 = 21550

1 Radio block throughput (bit/s) = (Radio block size including spare bits) * 50

Table 6 Radio block throughput calculations with spare bits included

RADIO BLOCK THROUGHPUT This is the throughput within the RLC/MAC layer where the whole radio block is counted, including the whole RLC/MAC header, but excluding spare bits. This is the throughput reference for the RLC/MAC measurements in the TEMS products.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

13 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

Coding Scheme CS-1 CS-2 CS-3 CS-4

N (including MAC header) 23 33 39 53

Radio block size 23*8 = 184 33*8 = 264 39*8 = 312 53*8 = 424

Radio block throughput (bit/s)1 184*50 = 9200 264*50 = 13200 312*50 = 15600 424*50 = 21200

1 Radio block throughput (bit/s) = (Radio block size * 50)

Table 7 Radio block throughput calculations

The following table shows the theoretical maximum throughput values for different coding schemes and number of timeslots.

Number of timeslots 1 2 3 4

CS-1 9200 9200*2 = 18400 9200*3 = 27600 9200*4 = 36800

CS-2 13200 13200*2 = 26400 13200*3 = 39600 13200*4 = 52800

CS-3 15600 15600*2 = 31200 15600*3 = 46800 15600*4 = 62400

CS-4 21200 21200*2 = 42400 21200*3 = 63600 21200*4 = 84800

Table 8 Theoretical maximum throughput (bit/s)

2.

GPRS RF Measurements

These measurements take place in the GSM RF layer in the protocol stack and are applicable to the downlink only in the TEMS products. At this protocol level, it is not possible to distinguish blocks addressed to a specific mobile; all blocks to all mobiles (all TFIs) will be counted.

In GPRS mode, FER and BER will be updated every 24 radio blocks (i.e. every two 52-multiframes, or once every 4.615*52*2 = 480 ms).

In the calculations below, 24 radio blocks are used as the reference. If the GPRS transaction does not fill two complete 52 multiframes before it is terminated, only the blocks prior to termination will be counted.

14 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

2.1. BER/Timeslot (%)

The BER/timeslot parameter gives the bit error rate for each used timeslot. It is possible to choose the timeslot by setting the argument of the information element (argument = 0 points to the first used timeslot, not timeslot 0, etc.)

The BER is calculated by summing the number of bit errors for each of the 24 blocks included in the BER and then dividing the sum by the total number of bits in the 24 blocks. As explained in section 1.5, each radio block consists of 456 coded bits, so the total number of bits is 456*24 = 10944.

The number of bit errors can be counted thanks to the convolutional coding which makes it possible to detect and correct bit errors (so-called forward error correction, FEC).

After the channel decoder has decoded a 456-bit block, it is encoded again in the encoder, using the same code polynomial, and the resulting 456 bits are compared with the 456 input bits. The number of bits that differ between the two 456-bit blocks corresponds to the number of bit errors in the block (at least up to a fairly high number of bit errors). The number of bit errors is accumulated in a BER sum for each report interval (i.e. two 52-multiframes). The BER sum is then divided by the total number of bits (10944) to obtain the bit error rate.

Note that the BER calculation does not take into consideration whether the block shall be discarded due to error in the block check sequence (BCS).

Also note that since CS-4 uses no convolutional coding at all but sends all bits uncoded, it is not possible to detect and count any bit errors with this coding scheme.

Range: 0 ... 100%

Calculation formula: BER (%) = ((total number of bit errors in 24 blocks) / (total number of bits in 24 blocks)) * 100 where the total number of bits in 24 blocks = 10944.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

15 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

2.2. FER/Timeslot (%)

The FER/timeslot parameter gives the block error rate (BLER) for each used timeslot in the downlink direction. It is possible to choose the timeslot by setting the argument of the information element (argument = 0 points to the first used timeslot, not timeslot 0, etc.)

The FER is calculated as the percentage of blocks (out of a total of 24) that have an incorrect checksum in the block check sequence (BCS).

Range: 0 ... 100%

Calculated as: FER (%) = ((number of blocks with incorrect BCS) / (total number of blocks)) * 100 where total number of blocks = 24.

Example 1 Two 52-multiframes (480 ms)

FER REPORT

FER REPORT

Ref. BCS TFI BSN

0
OK OWN

1
OK OWN

2
OK OWN

3
FAIL ?

4
FAIL ?

5
OK OWN

6
OK OWN

7
OK X

8
FAIL ?

9
OK X OK X

24
OK X

25
OK X

26
OK X

10

11

14

15

Figure 8 Example showing three erroneous radio blocks.

The FER is based on all blocks (all TFIs), not only those addressed to a particular mobile (TFI). In Figure 8 above, the three blocks with BCS failure (ref. = 3, 4, 8) will be counted as erroneous, and all other blocks (ref. = 1, 2, 57, and 924) will be counted as error-free. The FER in this case will thus be 3/24 = 12.5%.

16 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

Example 2

0 1 2 ...... 12 25 38 51 a a a a b b b b c c c c P d d d d e e e e f f f f X g g g g h h h h i i i i P j j j j k k k k l l l l X m mmmn n n n o o o o P p p p p q q q q r r r r X s s s s t t t t u u u u P v v v v y y y y z z z z X 52 53 54 ...... 64 77 90 103

Figure 9 Example showing four erroneous blocks. The complete 52 multiframe is shown including the burst mapping.
In Figure 9 above, two complete 52-multiframes are shown. Four blocks (b, e, f, and t) have an incorrect BCS. The FER for this period (480 ms) will be (4/24)*100 = 17%.

2.3. Coding Scheme Downlink Usage (%)

This parameter shows the utilisation of each coding scheme. Both signalling and data blocks are counted, and since signalling blocks are always coded with CS-1, the parameter will indicate use of CS-1 even if the cell is set up for using CS-2. The argument of the information element indicates the coding scheme (e.g. argument = 1 gives CS-1 usage).

As with the FER and BER measurements described in section 2.1 and 2.2, coding scheme downlink usage is measured on blocks addressed to all mobiles, using the actual packed data channel (PDCH). Range: 0 ... 100%

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

17 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

3.

RLC/MAC Layer Measurements

3.1. RLC/MAC Reports

RLC/MAC measurements take place inside the TEMS mobile which sends two reports per second to the TEMS PC application: one report for the uplink channel (mobile to GPRS network) and one for the downlink channel. Each report contains data representing the last one-second period. Note that the report interval is not in any way related to the GPRS frame structure; it is controlled by a timer which is set to expire once every second. In order to get the throughput figures right, the exact number of TDMA frames in the measurement period is included in each report. The number of frames is converted to seconds using the following formula:

1 frame = (120/26) ms ( 4.615 ms) Figure 10 Formula for calculating the TDMA frame length

Each report contains data for calculating the RLC information elements specified in section 3.2.

All counters are reset for each report, which means that the information relates to the blocks handled since the last report. At this level, the timeslot configuration is of no importance; the RLC/MAC layer does not know about the number of used timeslots, so all physical channels are included in the measurements. RLC UPLINK REPORT This report contains data on the uplink (MS to BSS). Both RLC control blocks and RLC data blocks are included. Note that the number of bytes per radio block depends on the coding scheme used for each block.

The throughput should be compared to the figures in section 1.7. Since both control and data blocks are counted, signalling (which is coded with CS-1) will lower the throughput compared to the maximum throughput for data (if coded with CS-2, CS-3, or CS-4).

18 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

Information for throughput calculations: Number of TDMA frames representing the report content. Converted into seconds using the formula in Figure 10. [RLC_UL_NO_OF_SECONDS] Number of bytes transmitted for the first time. The bytes of each whole radio block (i.e. payload from the LLC layer, MAC and RLC headers, and RLC padding bytes [if any] to get a complete radio block) are counted according to Figure 4. Note that retransmissions are not included, only radio blocks transmitted for the first time. Blocks repeated as fill blocks are not counted either. The value given will always correspond to a whole number of radio blocks. [RLC_UL_NO_OF_BYTES]

Information for retransmission calculations: Number of radio blocks generated from payload data received from the LLC layer plus the number of RLC/MAC control blocks. No other blocks generated within the RLC/MAC layer (e.g. retransmissions or fill blocks) will be counted. [RLC_UL_NO_OF_NEW_BLOCKS] Number of retransmitted radio blocks. This is the number of radio blocks that the network (actually the PCU, packet control unit) requests to be retransmitted. [RLC_UL_NO_OF_RETRANSMITTED_BLOCKS]

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

19 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

Example 3 1 second

RLC UL REPORT

RLC UL REPORT

Ref USF BSN

0
OWN

1
OWN

2
OWN

3
OWN

4
OWN

5
OWN

6
OWN

7
OWN

8
OWN OWN

23
OWN

24
OWN

25
OWN

26
OWN

10

11

12

13

14

15

30

31

32

33

retransmissions UL ACK/NACK1
1 ACK/NACK from the PCU to the mobile, all packets OK except those with BSN 3 and 5.

In the above example, the RLC UL REPORT sent at ref. 25 will indicate two retransmitted blocks (BSNs 3 and 5) and 22 radio blocks not previously transmitted (BSNs 10 to 31). The number of bytes used for throughput calculations will be the number of bytes in the 22 radio blocks. Note that the number of bytes per radio block depends on the coding scheme used for each block. The throughput should be compared to the figures in section 1.7.

20 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

Example 4 1 second

RLC UL REPORT

RLC UL REPORT

Ref. USF BSN

0
X

1
X

2
OWN

3
OWN

4
OWN

5
OWN

6
OWN

7
OWN

8
X X

23
X

24
X

25
X

26
X

If the mobile wants to send a very short message (e.g. a GPRS attach), it will request an uplink TBF and send the message on the assigned USF (ref. 2 and 3 in the above figure). Now, only two radio blocks are needed for this message, but the mobile has to send something in the next four blocks as well (ref. 4, 5, 6, and 7). Therefore it will repeat the attach message twice as a fill block (reusing BSNs 0 and 1).

In the above example, the UL RLC REPORT sent at ref. 25 will indicate no retransmitted blocks and two blocks not previously transmitted (BSNs 0 and 1). The number of bytes used for throughput calculations will correspond to the number of bytes in these two radio blocks.

Note that as long as the PCU receives at least one of the three attach messages correctly, it will not ask for a retransmission. That is, even if the first block did not come through, no retransmission will be required as long as one of the other two (fill) blocks did. This means that the retransmission rate will be zero even if one or two radio blocks were actually lost.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

21 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

RLC DOWNLINK REPORT This report contains data on the downlink (BSS to MS). Both RLC control blocks and RLC data blocks are included. Note that the number of bytes per radio block depends on the coding scheme used for each block.

The throughput should be compared to the figures in section 1.7. Since both control and data blocks are counted, signalling (which is coded with CS-1) will lower the throughput compared to the maximum throughput for data (if coded with CS-2, CS-3, or CS-4).

Information for throughput calculations: Number of TDMA frames representing the report content. Converted into seconds using the formula in Figure 10. [RLC_DL_NO_OF_SECONDS] Number of bytes received and addressed to this mobile, including fill bits measured on correctly received blocks ready for delivery to the LLC layer. Only unique radio blocks ready for the LLC will be counted, i.e. no fill blocks or retransmissions. The value given will always correspond to a whole number of radio blocks. [RLC_DL_NO_OF_BYTES]

Information for decode error calculations: Number of received radio blocks addressed to this mobile, including fill bits but not including retransmissions or fill blocks. Only radio blocks ready for the LLC will be counted, i.e. no fill blocks or retransmissions. [RLC_DL_NO_OF_NEW_BLOCKS] Number of radio blocks which the mobile has requested the PCU to retransmit. If transmission of a block fails several times, the block will be counted once for each retransmission requested. Note that the block check sequence is not used directly, since if this fails it is not possible to check which mobile the block was intended for. Instead the measurement is based on the ACK/NACK sent to the PCU asking for a retransmission. The ACK/NACK is based on checking the BSN (block sequence number) of the latest received block number and holes (missing BSN as exemplified in Example 5) in the BSN series. [RLC_DL_NO_OF_MISSING_BLOCKS]

22 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

Example 5 1 second

RLC DL REPORT

RLC DL REPORT

Ref. BCS TFI BSN

0
OK OWN

1
OK OWN

2
OK OWN

3
OK OWN

4
FAIL ?

5
FAIL ?

6
OK OWN

7
OK OWN

8
OK OWN OK OWN

23
OK OWN

24
X

25
X

26
X

10

11

12

15

16

17

32

DL ACK/NACK1
1 ACK/NACK from the mobile to the PCU, all packets OK except the radio block with BSN 13 and 14.

In the above example, the RLC DL REPORT sent at ref. 25 will indicate two requests for retransmission (blocks with BSNs 13 and 14) and 21 correctly received radio blocks (BSNs 1012, 1532). The number of bytes used for throughput calculations will be the number of bytes in the 21 correctly received radio blocks. Note that the number of bytes per radio block depends on the coding scheme used for each block. The throughput should be compared to the figures in section 1.7.

Note that for the blocks corresponding to ref. 4 and 5 it is not possible to decide the TFI. The blocks in ref. 24 to 26 have a different TFI and will not be counted.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

23 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

Example 6 1 second

RLC DL REPORT

RLC DL REPORT

Ref. BCS TFI BSN

0
OK OWN

1
OK OWN

2
FAIL ?

3
OK OWN

4
X X

19
X

20
OK OWN

21
OK OWN

22
FAIL ?

23
FAIL ?

24
FAIL ?

25
FAIL ?

26
FAIL ?

10

12

13

14

DL ACK/NACK1
1ACK/NACK from the mobile to the PCU, all packets OK except the packet with BSN 11. Note that the last reported block will be BSN 14 (ref. 21).

In the above example, the RLC DL REPORT sent at ref. 25 will indicate one missing block (BSN 11) and four correctly received blocks (BSN 10, 12, 13, 14). The number of bytes used for throughput calculations will be the number of bytes in the four correctly received radio blocks. Note that the number of bytes per radio block depends on the coding scheme used for each block. The throughput should be compared to the figures in section 1.7.

The radio blocks from ref. 22 on will not be handled until a block has been decoded correctly so that the BSN can be checked.

24 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

Example 7 1 second

RLC DL REPORT

RLC DL REPORT

Ref. BCS TFI BSN

0
OK OWN

1
OK OWN

2
OK OWN

3
OK OWN

4
OK OWN

5
OK OWN

6
OK OWN

7
OK OWN

8
OK OWN OK OWN

23
OK OWN

24
OK OWN

25
OK OWN

26
OK OWN

10

11

12

13

11

12

13

14

29

30

31

32

DL FILL BLOCKS DL ACK/NACK1

1 ACK/NACK from the mobile to the PCU, all packets OK.

In the above example, the RLC DL REPORT sent at ref. 25 will indicate 21 correctly received radio blocks and no retransmissions. The radio blocks at ref. 5, 6, and 7 are fill blocks and have already been received, so they will not be counted again in the information element calculations, neither as retransmitted blocks nor as correctly received blocks. The throughput should be compared to the figures in section 1.7.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

25 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

3.2. RLC/MAC Information Elements

In order to calculate the information elements, data from the reports explained in section 3.1 is used. RLC Decode Errors DL (%) Percentage of RLC/MAC blocks which the mobile has requested the PCU to retransmit, as explained in section 3.1. Calculated as: RLC Decode Errors DL (%) = ([RLC_DL_NO_OF_MISSING_BLOCKS] / ([RLC_DL_NO_OF_ MISSING _BLOCKS] + [RLC_DL_NO_OF_NEW_BLOCKS])) * 100

RLC Retransmissions UL (%) Percentage of RLC/MAC blocks retransmitted on the uplink, based on data taken from the RLC UPLINK REPORT (section 3.1). Calculated as: RLC Retransmission UL (%) = ([RLC_UL_NO_OF_RETRANSMITTED_BLOCKS] / ([RLC_UL_NO_OF_RETRANSMITTED_BLOCKS] + [RLC_UL_NO_OF_NEW_BLOCKS])) * 100

RLC Throughput DL (kbit/s) Throughput in the RLC/MAC radio block layer according to section 3.1. The reference throughput table can be found in section 1.7. Calculated as: RLC Throughput DL (kbit/s) = ([RLC_DL_NO_OF_BYTES] * 8) / ([RLC_DL_NO_OF_SECONDS] * 1000)

26 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

RLC Throughput DL (%) Throughput (as defined in section 3.2 above) on the downlink at the RLC/MAC protocol level, compared to the theoretical maximum for the current channel setup (coding scheme and number of timeslots). During the measurement period, the coding scheme distribution is checked and the highest coding scheme used will form the basis for calculating the maximum throughput. This means that degradation both due to retransmissions and to fill blocks will be detected. In case of CS-2, CS-3, or CS-4 usage, degradation due to signalling in control blocks will also be detected. The reference throughput table for the theoretical maximum value can be found in section 1.7. Calculated as: RLC Throughput DL (%) = (RLC Throughput DL / RLC Throughput DLmax) * 100

RLC Throughput UL (kbit/s) Data throughput in the RLC/MAC radio block layer according to section 3.1. The reference throughput table can be found in section 1.7. Calculated as: RLC Throughput DL (kbit/s) = ([RLC_UL_NO_OF_BYTES] *8) / ([RLC_UL_NO_OF_SECONDS] * 1000)

RLC Throughput UL (%) Data throughput as calculated in section 3.2 on the uplink at the RLC/MAC protocol level, compared to the theoretical maximum for the current channel setup (coding scheme and number of timeslots). Can be used to check the loss compared to an optimal radio environment for this channel configuration. The reference coding scheme used for calculating the maximum throughput will be the coding scheme assigned to the mobile for sending RLC/MAC data blocks. The reference throughput table for the theoretical maximum value can be found in section 1.7. Calculated as: RLC Throughput UL (%) = (RLC Throughput UL/RLC UL Throughputmax) * 100

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

27 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

4.

LLC Layer Measurements

4.1. LLC Layer Description

The LLC layer provides a logical link between the mobile phone and the SGSN node, as seen in Figure 2. It is specified in GSM specification 04.64 and handles concatenation of radio blocks to/from the RLC/MAC layer into larger segments called LLC frames. An LLC frame has a variable length of 51560 octets and consists of a header (address + control field), an information field holding the user data to/from the upper layers (SNDCP SMS, L3MM (see Figure 1, above), and a frame check sequence field, FCS. The FCS consists of a 24-bit (3-octet) cyclic redundancy check (CRC) used for error detection.

Address field
1 octet

Ctrl Field
1 36 octets

Information field
0 1520 octets

FCS
3 octets

LLC Frame

Different LLC frames are defined for data transfer and control messages. There are four types of LLC frames: I-frames (Information frames) are used for transferring information between layer 3 entities with acknowledgement. S-frames (Supervision frames) are used to perform logical link supervisory control functions, such as acknowledging I-frames and requesting temporary shutdown of the information frame (I-frame) transmission. UI-frames (Unconfirmed Information frames) are used for transferring information between layer 3 entities without acknowledgement. U-frames (Unnumbered frames) are used to provide additional logical link control functions.

The LLC protocol can operate in acknowledged or unacknowledged mode and applies to the I- and S-frames. Acknowledged mode means that error detection and retransmission requests for erroneous I- and S-frames will be performed.

28 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

4.2. LLC Reports

LLC measurements take place inside the TEMS mobile. Two reports are sent to the TEMS PC application once every second, one for the uplink channel (mobile to GPRS network specifically, the SGSN node) and one for the downlink channel. Each report contains data representing the last second. Note that the report interval is not in any way related to the GPRS frame structure; it is controlled by a timer which is set to expire once every second.

In order to get the throughput figures right, the exact number of TDMA frames in the measurement period is included in each report.

Each report contains data used for calculating the LLC information elements presented in the TEMS products. The LLC information elements can be found in section 4.3.

All counters are reset for each report, which means that information relates to the number of blocks handled since the last report.

Note that LLC is commonly run in unacknowledged mode; the RLC/MAC layer takes care of the retransmission of erroneous blocks. In this case, the information elements presenting the decode errors and retransmission rate will always be zero.

Each LLC report from the mobile may include multiple data or control message frames and includes the total number of bytes passed through the LLC interface to/from the RLC layer.

The following table shows the theoretical maximum throughput values for different coding schemes and number of timeslots. The calculations are based on the RLC payload throughput calculations in section 1.7 and form the base for the LLC throughput calculations.

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

29 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

Number of timeslots 1 2 3 4

CS-1

CS-2

CS-3

CS-4 20000 20000*2 = 40000 20000*3 = 60000 20000*4 = 80000

8000 12000 14400 8000*2 = 16000 12000*2 = 24000 14400*2 = 28800 8000*3 = 24000 12000*3 = 36000 14400*3 = 43200 8000*4 = 32000 12000*4 = 48000 14400*4 = 57600 Table 9 Theoretical maximum throughput (bit/s)

LLC UPLINK REPORT This report contains data on the uplink (MS to SGSN). All types of LLC frames are included (I-, S-, UI-, and U-frames) and a mixture of the different types is handled as well. Note that at this level, the timeslot configuration is of no importance; the LLC layer does not know about the number of used timeslots, so all physical channels are included in the measurements. Information for throughput calculations: Number of TDMA frames representing the report content. Converted into seconds using the formula in Figure 10. [LLC_UL_NO_OF_SECONDS] Number of bytes transmitted for the first time for each whole LLC frame. The whole LLC frame is counted, including the header (address and control field), information field (including fill bits), and the FCS. No retransmissions are counted, nor are any LLC fill frames generated within the LLC layer. The number of bytes will correspond to a whole number of LLC frames. [LLC_UL_NO_OF_BYTES]

Information for retransmission calculations: Number of LLC frames generated from data received from the upper layer (SNDCP, L3MM, and SMS). No frames generated within the LLC layer (e.g. retransmissions or fill frames) are counted. [LLC_UL_NO_OF_NEW_FRAMES] Number of retransmitted LLC frames. Frames that the network (the SGSN node) requests to be retransmitted are counted. [LLC_UL_NO_OF_MISSING_FRAMES]

30 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

LLC DOWNLINK REPORT This report contains data on the downlink (SGSN to MS). All types of LLC frames are included (I-, S-, UI-, and U-frames). Note that at this level, the timeslot configuration is of no importance; the LLC layer does not know about the number of used timeslots, so all physical channels are included in the measurements.

Information for throughput calculations: Number of TDMA frames representing the report content. Converted into seconds using the formula in Figure 10. [LLC_DL_NO_OF_SECONDS] Number of bytes received and addressed to this mobile, including fill bits measured on correctly received blocks that are ready for delivery to the upper layers. Only unique LLC frames ready for the upper layers will be counted, not fill frames or retransmissions. The whole LLC frame is counted, including the header (address and control field), information field (including fill bits), and the FCS. The number of bytes will always correspond to a whole number of LLC frames. [LLC_DL_NO_OF_BYTES]

For retransmission calculations: Number of LLC frames received and addressed to this mobile measured on correctly received frames that are ready for delivery to the upper layers. Only unique LLC frames ready for the upper layers will be counted, not fill frames or retransmissions. [LLC_DL_NO_OF_NEW_FRAMES] Number of LLC frames that the mobile station has requested the SGSN node to retransmit. If transmission of a frame has failed several times, the frame will be counted once for each failure. [LLC_DL_NO_OF_MISSING_FRAMES]

4.3. LLC Information Elements

In order to calculate the information elements, data from the reports explained in section 4.2 is used.

LLC Decode Errors DL (%) Percentage of LLC frames that the mobile station has requested the SGSN to retransmit, as explained in section 4.2. Calculated as: LLC Decode Errors DL (%) =

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

31 (33)

GPRS Measurements in TEMS Products White Paper

2/14/02

([LLC_DL_NO_OF_MISSING_FRAMES] / ([LLC_DL_NO_OF_ MISSING _FRAMES] + [LLC_DL_NO_OF_NEW_FRAMES])) * 100

LLC Retransmissions UL (%) Percentage of LLC frames retransmitted on the uplink, based on data taken from the LLC UPLINK REPORT (section 4.2). Calculated as: LLC Retransmission UL (%) = ([LLC_UL_NO_OF_RETRANSMITTED_FRAMES] / ([LLC_UL_NO_OF_RETRANSMITTED_FRAMES] + [LLC_UL_NO_OF_NEW_FRAMES])) * 100

LLC Throughput DL (kbit/s) Data throughput in the LLC layer according to section 4.2. The reference throughput table can also be found in section 4.2. Calculated as: LLC Throughput DL (kbit/s) = ([LLC_DL_NO_OF_BYTES] * 8) / ([LLC_DL_NO_OF_SECONDS] * 1000)

LLC Throughput UL (kbit/s) Data throughput in the LLC layer according to section 4.2. The reference throughput table can also be found in section 4.2 Calculated as: LLC Throughput DL (kbit/s) = ([LLC_UL_NO_OF_BYTES] * 8) / ([LLC_UL_NO_OF_SECONDS] * 1000)

5.
BCS BER BSIC BSC BSN BSS

Abbreviations
Block Check Sequence Bit Error Rate Base transceiver Station Identity Code Base Station Controller Block Sequence Number Base Station System

32 (33)

EPL/N/TB-01:019

Rev B

Ascom 2009

Open

2/14/02

GPRS Measurements in TEMS Products White Paper

BSSGP BTS DL FER GPRS GSM HTTP IP L3MM LLC MAC MS PCU RLC RF SGSN SNDCP TCP TEMS TFI UDP UL USF WAP WDP

BSS GRPS Protocol Base Transceiver Station Downlink Frame Erasure Rate General Packet Radio Service Global System for Mobile communications Hypertext Transfer Protocol Internet Protocol Layer 3 Mobility Management Logical Link Control Medium Access Control Mobile Station Packet Control Unit Radio Link Control Radio Frequency Serving GPRS Support Node Sub-network Dependent Convergence Protocol Transmission Control Protocol Test Mobile System Temporary Flow Identity User Datagram Protocol Uplink Uplink State Flag Wireless Application Protocol Wireless Datagram Protocol

Ascom 2009

Open

EPL/N/TB-01:019

Rev B

33 (33)