Air Interface

Air Interface

1 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 1
Air Interface

N o kia Sie m e n s Net w orks

A ca dem y
Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Sie m ens Net works training
docu m entation, product docu m entation and slide presentation material, all of which are
forth with know n as Nokia Sie m ens Netw orks training material, are the exclusive property of
N okia Sie m e ns Net works. Nokia Sie m ens Net works o wns the rights to copying, modification,
translation, adaptation or derivatives including any improve m e nts or develop m ents. Nokia
Sie m ens Netw orks has the sole right to copy, distribute, a mend, modify, develop, license,
sublicense, sell, transfer and assign the Nokia Siem e ns Net works training m aterial.
Individuals can use the Nokia Sie m ens Net works training material for their o wn personal
self-developm e nt only, those sa m e individuals cannot subsequently pass on that sa m e
Intellectual Property to others without the prior written agree m e nt of Nokia Sie mens
N et works. The Nokia Siem e ns Net works training m aterial cannot be used outside of an
agreed Nokia Sie m ens Net works training session for develop m ent of groups without the
prior written agree m ent of Nokia Sie m ens Net works.

2 © Nokia Sie m e ns N et works R A2 0 1 93 E N 1 4 G L N 0

RA20193EN14GLN0 2
Air Interface

Module Objectives

After completing the module, the student will be able to:

• Describe the use of Erlang formulas
• Calculate the number of Circuit Switched timeslots needed for
voice, data and signalling
• Calculate the size of Packet Switched (GPRS/EDGE) Territory
Exercise:
• Given some information on the expected traffic, calculate
timeslots needed.

Refer to S14 Documentation:

• Plan and Dimension/Example of BSS connectivity dimensioning
• Plan and Dimension/Dimensioning of network elements and interfaces/BTS EDGE dimensioning
3 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 3
Air Interface

What do we have on the Air Interface?

The Air Interface is used by the mobile to access Network services.

The Air Interface should therefore provide the mobiles:
• Common Signaling Channels (signaling from between the cell and many
mobiles)
• Dedicated Signaling Channels (signaling dedicated to one mobile only)
• CS Traffic Channels (Voice, Fax, Data)
• PS Traffic (GPRS, EDGE)
The Dimensioning challenge is to determine how many channels are needed in
a typical cell. Usually every operator starts with a couple of typical cells i.e. one
big for Macro Coverage and one small for Micro Coverage

We start from understanding Logical Channels:

• Logical channels are an easy way to define the functionalities provided by the
air interface.

4 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 4
Air Interface

Logical Channels
LOGICAL
CHANNELS

COMMON Packet DEDICATED

CHANNELS COMMON CHANNELS
CHANNELS 

BROADCAST COMMON DEDICATED TRAFFIC

CHANNELS CONTROL CONTROL CHANNELS
CHANNELS CHANNELS

FCCH SCH BCCH SDCCH SACCH FACCH

TCH/FR TCH/HR PDTCH

PCH RACH AGCH

5 © Nokia Siemens Networks RA20193EN14GLN0

PHYSICAL CHANNEL: a single TSL on a single frequency ---> 8 TSL per frequency used (or
TDMA frame). The physical channel is the info contained in a burst.

LOGICAL CHANNEL: the type of info contained into a physical channel.

There are more functions to be dealt with so called logical channels than fitting into one
physical carriers with only 8 timeslots.

Several logical channel will be mapped one after each other onto one physical channel! This
is called a Multiframe.

The logical channels expect the traffic channels are used for signalling info. And since
recourses used for signalling cannot be used for paid calls, the physical space it takes must
be as small as possible, while still maintaining the required service!

Firstly we speak about logical channel functionality, then we explain the different Multiframe
structure.

More info in hidden slides if needed.

RA20193EN14GLN0 5
Air Interface

Broadcast Channels

Frequency Correction Channel (FCCH)

• It broadcasts a pure sine wave
• the MS searches for this channel after switching on
Synchronisation Channel (SCH)
• after locking onto the correct frequency, the MS synchronises by the SCH
• It contains the BSIC of the BTS and TDMA frame number (used in encryption)
Broadcast Control Channel (BCCH)
• Common information about the BTS:
• Used frequencies
• Frequency hopping sequence
• Channel combination
• Paging groups
• Surrounding cell information

6 © Nokia Siemens Networks RA20193EN14GLN0

Common Channels (CCH) are divided into: BCH and CCCH. They're all UNIDIRECTIONAL
BCH are all downlink info channels. They are sent by a BTS to inform all the MSs in the cell of
general info, about that cells and surrounding ones.
FCCH ----> Just switched on, the MS searches the last frequency he had stored. If it doesn't
hear it, it listens to all FCCH it can. In fact, FCCH carries info that will enables the MS to tune
its frequency to that being broadcast by the BTS. By FCCH, the MS can enter the network. It
carries a pure sine wave, that is 148 bits sequence of zeros.
SCH ------> after tuning, MS needs further info for going on with signalling procedures.
Base Station Identity Code (BSIC= NCC (Network colour code) + BCC (Base station colour code))
--> 6 bits: 3 bits NCC of the PLMN and 3 bits BCC of the BTS.
Reduced TDMA Frame Number (RFN) ------> by this the frame number can be calculated.
19 bits. ---> more secure ciphering.
BCCH ------> General info required for call set-up.
LAI = (MCC+MNC+LAC) & CGI (LAC+CI) ---> so MS can requires location updated (LAI) and
not to refresh continuously its registration data (CGI). CGI is unique in the network, BSIC not!
FH sequence: 6bit;
CH combination: 3bit--> n° AGCH blocks reserved onto each CCCH
2bit (1..4 values) --> n° CCCH allocated plus 1bit (V/F) to say if they are associated to DCH
onto the same physical channel.
Paging: According to IMSI/TMSI, MSs are separated in groups for target paging; 3bit say the
distance between two subsequent paging towards the same MS.
Surrounding: MS is informed which cells has to measure (adjacent cells and BA list)

RA20193EN14GLN0 6
Air Interface

Common Control Channels (CCCH)

Paging Channel (PCH)

• BTS uses it to page a mobile
• downlink channel only
Random Access Channel (RACH)
• MS uses it to require a dedicated control channel, i.e. a SDCCH
• used for mobile originated calls
• used as a response to a PCH due to incoming calls or location update requests
• uplink channel only
Access Grant Channel (AGCH)
• BTS uses it to assign a dedicated channel
• downlink channel only

7 © Nokia Siemens Networks RA20193EN14GLN0

These channels are called "common" again. They are used to access the BTS or the MS, but
now they are concerned with a particular MS that has already tuned and synchronized onto a
precise BTS.

PCH --> used for paging, to try to access a MS if there is an incoming call for it. It is sent in all
the cells of a certain Location Area or sub-areas if there are paging groups. It says: WHO IS
MR.SMITH?

RACH ---> request a SDCCH for setting up a call as mobile originated or as a response to a
PCH, but also for location updating. This channel undergoes possible "collisions" as obviously
there is no coordination among MSs in the same location area. As the requiring MS doesn't
know the timing advance by which it has to transmit - we shall see it later - RACH contains a
short auto synchronizing sequence. MR. SMITH RAISES HIS HAND.

AGCH ----> By it, the BTS informs the MS a DCH is reserved for it and which is it. MR.SMITH,
YOU CAN SPEAK!

RA20193EN14GLN0 7
Air Interface

Dedicated Control Channels (DCCH)

Stand Alone Dedicated Control Channel (SDCCH)

• bi-directional channel
• used for call set-up procedures, e.g. authentication and location update
• used for SMS
Slow Associated Control Channel (SACCH)
• associated with each SDCCH and TCH
• used for measurement reports
• used for MS power control
• used to maintain the correct timing alignment of a MS moving in a cell
Fast Associated Control Channel (FACCH)
• associated with a particular TCH
• for quick control communication, e.g. handover
• physically replaces one TCH burst (20 ms of speech): “steal mode”

8 © Nokia Siemens Networks RA20193EN14GLN0

They not only refer to a particular MS-BTS connection, but also to the particular TCH set for
furnishing the MS the required service.
SDCCH ---> It is fundamental for every access to the network. It is also used for carrying SMS
and IMSI attach! In the Abis IF, one TRXSIG can carry max 12 SDCCH.
SACCH ----> In downlink, the BTS sends the list of the frequencies to be measured and all
BCCH info (FH sequence changed, time advance changed etc.) that would be lost after the
MS synchronize to its dedicated TCH. SMS during a call are sent with a SACCH!
In uplink the MS sends its measures on the cell and the surrounding ones.
These messages are inserted periodically into the sequence of TSL of the TCH of the current
connection. It is "slow" due to the fact that it occurs regularly (every 26th frame on the TCH)
A SACCH always goes together with a dedicated resource, being a service channel for them.
When it is referred to a SDCCH it is one of the 8 SACCH blocks in a SDCCH/8 multiframe.
After the MS is given its TCH, a new SACCH, onto the traffic channel multiframe is given to
the TCH.
FACCH ----> Used instead of a SACCH, to inter-exchange info in a much quicker timescale
than with a SACCH. In fact it works in asynchronous mode: when it is needed it is sent!
HANDOVERS & EMERGENCY CALLS. It is mapped onto a TCH, replacing 20ms or 10ms of
speech (114/57 bits --> 1 or 1/2 burst) working in steal mode ----> remember the stealing
flags!

RA20193EN14GLN0 8
Air Interface

Traffic Channels (TCH)

Traffic Channel, Full Rate (TCH/FR)

• used for speech & data transmission
• speech bit rate is up to 13 kbit/s
• data bit rate can be 9.6 - 4.8 - 2.4 kbit/s
Traffic Channel, Half Rate (TCH/HR)
• used for speech & data transmission
• speech bit rate is up to 5.6 kbit/s
• data bit rate can be 4.8 - 2.4 kbit/s

9 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 9
Air Interface

Use of Logical Channels

FCCH
Search for frequency correction burst
SCH
search mode Search for synchronisation sequence
BCCH
Read system information

Listen for paging PCH

idle mode Send access burst RACH
Wait for signalling channel allocation
AGCH

Call setup SDCCH

dedicated
mode Traffic channel is assigned FACCH
Conversation TCH
Call release
FACCH

10 © Nokia Siemens Networks RA20193EN14GLN0

Three modes: some signalling procedure per each mode.

During these procedures the logical channels on the right are used.

RA20193EN14GLN0 10
Air Interface

Physical Channels

• Logical channels are multiplexed over physical channels that are transmitted in every
radio timeslot of the TRXs.
• The structure of logical channels over physical channels is called Multiframe.
• Every TRX creates its own TDMA frame made of 8 radio timeslots modulated and
managed completely independently

Physical Channels

RTSL 0 RTSL 1 RTSL 2 RTSL 3 RTSL 4 RTSL 5 RTSL 6 RTSL 7

BCCH SDCCH 2xTCH HR TCH FR TCH FR TCH FR PDTCH PDTCH

577µs 577µs 577µs 577µs 577µs 577µs 577µs 577µs

4.615 ms

11 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 11
Air Interface

Multiframe

12 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 12
Air Interface

CHANNEL CONFIGURATIONS
BCCH/CCCH Multiframe

Downlink 51 TDMA frames = 235 ms

f s b b b b c c c c f scf c c c c c c c f s cf c c c c c c c f s cf c c c c c c c f s cf c c c c c c c i

Uplink 1. 2. 3. 4. 5. 6. 7. 8. 9.

r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r rr r r r r r r i

1 51

CHANNELS: f = FCCH b = BCCH r = RACH i = idle

s = SCH c = CCCH (PCH - AGCH)

13 © Nokia Siemens Networks RA20193EN14GLN0

One of the basic and crucial tasks when planning a network and dimensioning a site, is to
map in a convenient way the logical channels onto the TSL of the TDMA frame. This task is
carried out by the operator, according to the features of the site, the traffic it has to sustain
and the coverage it has to assure.
In general, when a BTS has more than 1 TRX, TSL0 is typically used for BCH and CCH
transmission. Here we see the exact sequence of channels transmitted in 51 successive
TDMA frames, forming a so-called multiframe.
In downlink, FCCH and SCH appear one after the other every 10 timeslots. There are 'only' 4
timeslots for BCCH in each multiframe. PCH and AGCH are sent in a way dependent on the
customers' requirements. Ordinarily, PCH has priority to AGCH. TSL51 is not used. A full
BCCH/CCCH message is sent into 4 subsequent TSLs. The frequency whose TSL0 carries
the BCCH is called "main carrier". It is always broadcast with a higher power than other
frequencies, so that the MS can recognize it just before interpreting its info. For the same
reason, this frequency is not concerned with frequency hopping. We must note another thing:
this TSL is the most important, since it carries the tuning wave. So it cannot stop transmission,
and when there are idle frames or frames in which there is no info, dummy bursts - that is to
say filling bursts without info - are to be sent, while in other TSL transmission can be
suspended.
In uplink, all TSL are at disposal for RACH. Also in this case TSL51 is not used.

RA20193EN14GLN0 13
Air Interface

CHANNEL CONFIGURATIONS
SDCCH/8 Multiframe

Downlink 51 TDMA frames = 235 ms

t t t t t t t t t t t t tf t t t t t t t t t tf t t t t t t t t t sf s s s s s s s s s sf s s s s s i i i

1. 2. 3. 4. 5. 6. 7. 8. 1. 2. 3. 4.
Uplink 5. 6. 7. 8.

s s s s s s s s s s s s fi i i t t t t t t t tf t t t t t t t t t tf t t t t t t t t t tf t t t t s s s s

1 1. 2. 3. 1. 2. 3. 4. 5. 6. 7. 8. 4. 51
5. 6. 7. 8.

CHANNELS: t = SDCCH/8 s = SACCH/8 i = idle

14 © Nokia Siemens Networks RA20193EN14GLN0

When TSL0 is configured as we have seen in the previous slide, TSL1 is dedicated to SDCCH
and SACCH transmission. Nevertheless, it could also be for any other timeslot (in any other
TRX) according to the particular cell dimensioning.
The multiframe is organized in the same way, with 51 frames. Idle frames are generally used
to assure the maintaining of the alignment. Here we see the SDCCH-SACCH configuration
used for serving 8 subscribers, one SDCCH/SACCH block being composed of 4 consecutive
TSLs. An entire cycle is completed in 2 multiframes.
In the uplink, there is a shift of 3 SDCCH blocks and 3 idle frames in order to give the MS the
convenient time to switch from RX to TX and vice versa.
In the configuration of the "main carrier" of a BTS with more than one TRX, the other 6 TSL
can be used for traffic. Other TRXs of the BTS can have all the 8 TSLs assigned to traffic.

RA20193EN14GLN0 14
Air Interface

CHANNEL CONFIGURATIONS
Combined CCCH/SDCCH/4 Multiframe

Downlink 51 TDMA frames = 235 ms

f s b b b b c c c c f s cf c c c c c c c f s tf t t t t t t t f s tf t t t t t t t f s h
f hh hh hh h i

1. 2. 3. 1. 2. 3. 4. 1. 2.
Uplink 3. 4.

f h r r r r r r r r rf r r r r r r r r r rf r r r r t t t t t tf t t r r t t t t
t t t t r r h hhh hhh

1 1. 2. 51
4. 1. 2. 3.
3. 4.

CHANNELS: f = FCCH b = BCCH h = SACCH/4 s = SCH

c = CCCH r = RACH t = SDCCH/4 i = idle
15 © Nokia Siemens Networks RA20193EN14GLN0

Other configurations are possible when cells are designed for elevated traffic or limited one.
In the former case, for instance, we need many more BCCH and paging messages. So also
TSL2-4-6 of the main carrier can be reserved for these channels.
In cells for limited capacity of traffic, i.e. when you have one cell with a single TRX, it may be
that all logical signalling channels have to be mapped onto a unique TSL - the TSL0. Paging
and the immediate assignment processes use the same resources on the signalling channels,
CCCHs. There can be different strategies in defining their mutual priorities. In this typical case
we see CCCH combined with SDCCH for 4 subscribers.
When you cope with MML commands in order to carry out the Abis integration, you will have
to choose a channel configuration, from a certain menu. In general, the 1st slide configuration,
with BCH & CCCH onto TSL0 is identified by "MBCCH".
You can read "MBCCHC", when the configuration provides BCCH together with SDCCH for 4
users onto the same TSL, as in this slide. Finally you can also have "MBCCB": this
configuration provides a sequence of bursts similar to that represented here for MBCCHC, but
instead of the 4th SDCCH block there is a CBCH (CELL BROADCAST CHANNEL) block. It is
a particular BCH used to inform the user in which cell it is located at that moment.
In uplink direction, the TSL used for BCCH, in its different forms, is anyway used for RACH.
Nevertheless, we can also define another TSL for the so called ERACH. It means Extended
RACH, that is RACH for extended cells. DO YOU KNOW? Cells can be implemented for
covering more than 35 km, reaching 70 km!!!!!!!! The problem is not BTS transmission power,
but alignment. With ERACH one TRX has delayed RX frames at the same frequency of the
BCCH TRX, while TX ones are not used.
In MML, if you don't specify the use of a TSL it is considered for TCH by default.

RA20193EN14GLN0 15
Air Interface

CHANNEL CONFIGURATIONS
Full Rate Traffic Channel (TCH/FR) Multiframe

Downlink and Uplink

26 TDMA frames = 120 ms

t t t t t t t t t t t t sf t t t t t t t t t tf t t i

0 26

CHANNELS: t = TCH s = SACCH i=idle

16 © Nokia Siemens Networks RA20193EN14GLN0

Now, let's consider TCH channel configuration. We immediately note that multiframe is now
formed of 26 frames. Every 26 frames a SACCH is mapped onto the TCH (so named
SACCH/T), in order to have a regular communication link between BTS and MS during the
call. As for other signalling channels, a full SACCH message is sent in 4 frames. In this case,
these frames are not sent sequentially, but every 120ms (26 frames). This is called interblock
interleaving. And FACCHs? WE HAVE NOT SEEN THEIR CONFIGURATION!
FACCHs are sent asynchronously, by stealing a TCH TSL when needed!
Frame 26 is idle. As 51 and 26 are prime number, the SCH frame of the main carrier will be
able to run over all the idle frames of the TCH of the surrounding BTS/MS. In this way, at
regular intervals, the MS can get measures on the SCH frequency of its own cell and the
adjacent ones, so collecting data to be sent to the BTS. This idle frame is simply a regularly
guaranteed dedicated frame, since the MS always gets measures in the TSLs when it is not
transmitting or receiving.

RA20193EN14GLN0 16
Air Interface

Radio Network Objects

• The mobiles can only understand the presence of GS M Cells providing some
Services
• Cells are actually groups of TRXs installed in Base Stations and connected to
the antennas. The same group of TRXs is also called BTS from the network
point of view.
• One TRX is made of 8 RTSLs transmitting different multiframes.
• A site is made of one or more BTSs usually sharing antennas or at least the
antenna pole.
• One site can be made of different Base Stations

17 © N okia Siemens Networks R A 20193E N 14 G L N 0

A cell is the basic construction block of a GSM network. One cell is the geographical area
covered by one SEG. A segment contains one or more BTS and one BTS is made of many
TRXs with 8 TSLs transmitting different multiframes.

RA20193EN14GLN0 17
Air Interface

Dimensioning cells

• Dimensioning a cell means finding the answer to the fundamental question “How many
traffic channels does the cell need”?
• To solve the problem we have to calculate the number of Erlangs, the measuring unit of
network traffic. One Erlang equals the continuous use of a channel for one hour.
• In other words if we know how many calls there are in one hour (BHCA – Busy Hour Call
Attempts) and how long do they last (MHT – Mean Holding Time), we have the capacity in
Erlangs:
( BHCA )×( MHT )
Erlangs =
3600 Seconds
• Otherwise if we know how many subscribers we have in one area, we can use the Call
Mix input (25 mErl per subscriber) to calculate how many Erlangs we have:

Erlangs = Subscriber s × 0 .025 Erl / Subscriber

• For example, if you know that in one small cell you have to serve 80 subscribers, you
expect 2 Erl, or in other words 60 calls per hour lasting 120 seconds

18 © Nokia Siemens Networks RA20193EN14GLN0

SEG  BTS  TRX

Quite often, when there is only one BTS under a segment, a cell is defined as a BTS directly.

Erlangs = (calls per hour) x (average conversation time) / (observation period)

Example: if we have in one cell 450 calls per hour, given the assumed average conversation
time of 120 seconds, we have 15 Erl
This value is the input for the Erlang Table: 2% Blocking Probability we can deliver 15 Erl
using 22 or better 23 TSLs, therefore 3 TRXs.

RA20193EN14GLN0 18
Air Interface

From Erlangs to Timeslots

• To provide a certain capacity, you need a certain number of resources.

• But the capacity is an average: if at a certain time all resources are used, then the next
call will be blocked.
• The probability that this blocking
happens is called GoS (Grade of
Service) or B (Blocking Probability)
and is an input from the operator.
• We need an Erlang B Table to find
how many resources N we need to
provide a certain Erlang capacity
at a given GoS.
• For example, to provide 2 Erl we
need
– 5 TSLs in case of GoS = 5%
– 6 TSLs in case of GoS = 2%
– 10 TSLs in case of GoS = 0.01%
• GoS = 2% is the most commonly
used value for Voice TCH

19 © Nokia Siemens Networks RA20193EN14GLN0

You can calculate the GoS for any Resource/Erlang value with the excel formula
=POISSON(Resource,Erlang,FALSE)/POISSON(Resource,Erlang,TRUE)

Erlang B tables are commonly available on the internet and in literature. See the one in the
note pages for exercising.

RA20193EN14GLN0 19
Air Interface

Erlang B Table

RA20193EN14GLN0 20
Air Interface

The General Case

• The methodology just shown is the simplest case involving just “normal” calls (that is
FR, no HR, no signalling, no GPRS, no EDGE) .
• This problem of evaluating the capacity was first studied by Erlang in 1899, who derived
the well known and much used Erlang-B formula for blocking probability. It is an
accepted unit since 1940s.
• The formula gives the probability of having a call blocked by lack of resources given N
resources (channels) and the potential traffic generated in a cell (A).
• It assumes that call arrival is a Poisson-distributed stochastic process with exponential
distributed call duration.
• Dimensioning is purely based on hardware considerations and does not consider
interference and propagation issues that are better evaluated during frequency
planning.

21 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 21
Air Interface

Erlang definition

Erlang is the unit of traffic

• definition
( calls per hour )×( average conversati on time )
x Erlangs =
3600 Seconds

2 formulas
• Erlang B: for systems that support no queuing
• Erlang C: for systems that support queuing

Agner Krarup Erlang (1878-1929)

22 © Nokia Siemens Networks RA20193EN14GLN0

See GSM, GPRS and EDGE Performance 2nd Ed. Edited by T. Halonen, J. Romero and J.
Melero © 2003 John Wiley & Sons, Ltd ISBN: 0-470-86694-2 (Appendix B)
Agner Krarup Erlang was born in 1878 in Lønborg, Denmark. He was a pioneer in the study of
telecommunications traffic and, through his studies, proposed a formula to calculate the
fraction of callers served by a village exchange who would have to wait when attempting to
place a call to someone outside the village. In 1909, he published his first work: The Theory of
Probabilities and Telephone Conversations. He gained worldwide recognition for his work,
and his formula was accepted for use by the General Post Office in the UK.
Erlang never married. He worked for the Copenhagen Telephone Company for twenty years,
until his death in 1929. During the 1940s, the Erlang became the accepted unit of
telecommunication traffic measurement, and his formula is still used today in the design of
modern telecommunications networks.

Carried traffic in a cell is almost equal potential traffic if the blocking probability is low.

RA20193EN14GLN0 22
Air Interface

Erlang Formulas

Erlang B Erlang C
• no queuing: blocked calls are • queuing
dropped • applicable in trucking systems
• depends on call lengths & statistical
distribution of calls
• applicable in mobile systems (e.g.
air interface)

k
λ 
  / k!
μ AC
pk =   Pr ob ( delay > 0 ) =
M    A  C −1 A
k
A C + C ! 1−  
i
λ 
  
i= 0  μ
 / i!  C  k =0 k!
  

23 © Nokia Siemens Networks RA20193EN14 GL N0

RA20193EN14GLN0 23
Air Interface

Erlang B Table

• The Erlang B Table shows how much

traffic is handled by N channels (TSL)
given the blocking probability B (%).
• For example one full TRX can provide
3.637 Erl, that is a total of ~3.6 hours of
traffic per hour with the typical call mix.
• 2% is the most commonly used B

24 © Nokia Siemens Networks RA20193EN14 GLN0

RA20193EN14GLN0 24
Air Interface

What if we have Half Rate?

• In case of FR, one channel is one TSL, therefore given a target blocking probability, it is
possible to determine the traffic A that is possible to handle with N TSLs

• If HR is supported by the network (and most of the network do), then the blocking
probability is a function of the traffic generated in the cell (A), the number of HR mobiles
(HR penetration) and the number of available channels (N).

• The solution is a N²+2N+1 dimensional system of equations that can be used by

Dimensioning software but is too complex for manual dimensioning.

• That’s why we use TABLES instead of formulas: given a blocking probability, the tables
show how much traffic can be handled by a certain number of timeslots in case of a
certain percentage of HR connections.

25 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 25
Air Interface

In case of HR

• In case HR is used in the network we have one more variable:

– the percentage of HR connections.
• This value can come as an input from the operator (“I want at least this number
of HR calls because I want to use more intensively my network”)
• Or can be due to the H R feature penetration among the mobiles com monly used.
In this case it is a marketing input.
• The typical value used by operators is 30% H R connections. It may be
higher if AM R HR is used

26 © Nokia Siemens Networks RA20193EN14 GL N0

RA20193EN14GLN0 26
 Erlang B table for HR with 2% blocking
Air Interface

RA20193EN14GLN0
27
 Erlang B table for HR with 1% blocking
Air Interface

RA20193EN14GLN0
28
Air Interface

Exercise 1

• Try and dimension voice traffic for a Call Mix

cell where you have a typical
population of 350 subscribers (like
you can find it for instant in a a small
town).
• Suppose the usual call mix and an
HR penetration rate of 30% and 2%
Blocking probability
• For now, just consider the Voice.
25mErl per subscriber
120 seconds mean hold time
70% mobile-originated calls (MO)
30% mobile-terminated calls (MT)
1.5 handovers (HO) per call
2 location updates (LU) per call
0.1 IMSI detach per call
63% no paging response
1 SMS call rate subs/hour
(80% terminated SMS)

29 © Nokia Siemens Networks RA20193EN14GLN0

10 minutes

RA20193EN14GLN0 29
Air Interface

Exercise 1 Solution

• Try and dimension voice traffic for a Call Mix

cell where you have a typical
population of 350 subscribers (like
you can find it for instant in a a small
town).
• Suppose the usual call mix and an
HR penetration rate of 30% and 2%
Blocking probability
• For now, just consider the Voice.
350 subscribers at 25mErl means that
we need 8,75Erl in that location.
At 2% Blocking probability, 30% HR
penetration rate, we need 13
TIMESLOTS.
25mErl per subscriber
120 seconds mean hold time
70% mobile-originated calls (MO)
30% mobile-terminated calls (MT)
1.5 handovers (HO) per call
2 location updates (LU) per call
0.1 IMSI detach per call
63% no paging response
1 SMS call rate subs/hour
(80% terminated SMS)

30 © Nokia Siemens Networks RA20193EN14GLN0

10 minutes

350 subscribers at 25mErl means that we need 8,75Erl in that location.

At 2% Blocking probability, with only FR, we need 15 TIMESLOTS.
At 2% Blocking probability, 30% HR penetration rate, we need 13 TIMESLOTS.
At 1% Blocking probability, 30% HR penetration rate, we need 14 TIMESLOTS.

RA20193EN14GLN0 30
Air Interface

Signalling
# of BC CH SD CC H Total Total # of
Calls can also be blocked due to lack of signalling TRX Type TSLs SD CC H CC CH TCH
resources. 1 Co mbi 0 4 3 7
There are two important signalling channels on the 2 Co mbi 0 4 3 15
Air Interface: Nor m* 1* 8* 9* 14*
• SDCC H for dedicated mode procedures 3 Nor m 1 8 9 22
• CCC H for com m on procedures (PCH – Paging 4 Nor m 1 8 9 30
and AG CH – Access Grant)
5 Nor m 2 16 9 37
Air Interface Signalling Dimensioning is different
from Traffic Dim ensioning because 6 Nor m 2 16 9 45
• Blocking probability must be lower (usually 0.1 % 7 Nor m 3 24 9 52
or 0.2 %)
8 Nor m 3 24 9 60
• Nu mber of channels is not continuous but
depends on multiframe configuration: you can * when EGP RS is enabled use of Norm al BCCH is preferred
have multiple of 8 SDCCHs, you cannot have 7
or 9!
• Signalling is always dimensioned per cell. Co mbi BCCH Multiframe contains 3 CCCH and
4 SDCCH.
To make dimensioning easy we can use as thu mb
rule the table on the right: given the nu mber of TRX, Normal BCCH Multiframe contains 9 CCCH
it gives the num ber of SDCCH and TCH TSLs. Normal SDCCH contains 8 SDCC H

31 © Nokia Siemens Networks R A2019 3 EN 14 GLN 0

RA20193EN14GLN0 31
Air Interface

Using formulas

• The previous table is based on the Signaling Seconds

given Call Mix and on the Procedure
assumption that each signaling MOC 2.8
procedure uses one SDCCH for a MTC 2.8
certain number of seconds shown
here on the right. LUP 3.5
SMS 3.5
• It is therefore possible to calculate
the Signaling Erlangs generated by IMSI DET 2.8
the Call Mix and then the number of
signaling channels (SDCCH) Signaling Call Mix
needed at the Blocking Probability of Procedure
0.1% MOC 70% of calls
• Some operators, due to slow core MTC 30% of calls
network prefer using 7 seconds per LUP 2 per call
each procedure SMS 1 per subscriber & h
IMSI DET 0.1 per call

32 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 32
Air Interface

RACH Capacity

• The capacity of RACH is usually not a

problem.
• Even with 0.2% BP, one RACH Radio
Timeslot can handle 50000 calls per hour.
• Combined CCCH / SDCCH reduces the
capacity because 24 out of 51 frames are
used by Dedicated Channels. Therefore
the capacity decreases by 47% to 23500
calls per hour
• RACH retransmission reduces the
capacity by another 50% to 11750 calls
per hour
• PS channel requests decrease the
capacity by another 50% to 5875 calls per
hour.
• Even with these considerations one RACH
can handle about 200 Erl of traffic, more
than any Cell can handle.

33 © Nokia Siemens Networks RA20193EN14GLN0

5875calls/h*120s/call = 5875*120/3600 Erl = 195,8 Erl

RA20193EN14GLN0 33
Air Interface

PCH / AGCH Capacity

• Even with a Combined BCCH, a cell could

handle about 50000 calls per hour.
• But paging is usually per LAC, therefore the
amount of paging's depend on the size of the
LAC, not on the size of the cell.
• If Paging becomes a problem, it is possible to
change some parameters
– Number of blocks reserved to AGCH
(BS_AG_BLKS_RES)
– Type of paging (TMSI or IMSI) from MSC
– Immediate assignment extended feature doubles
AGCH capacity
• Remaining AGCH capacity can be used for PS
TBF Establishment:
– 1000 (1500 non comb) data sessions per hour in
case of 0.2% blocking probability
– 1400 (4300) data sessions per hour in case of 2%
blocking probability

34 © Nokia Siemens Networks RA20193EN14GLN0

4 TMSI or 2 IMSI can be paged per block

RA20193EN14GLN0 34
Air Interface

Correct Paging Capacity

• When we define the BS_AG_BLKS_RES parameter for the cell, we also define the cell
capacity in terms of PCH

3600 s
PCHperHour = ( AvailableC CCH − BS _ AG _ BLKS _ RE )*
0 . 235 s
• Given the cell configuration (combined or not) we know the AvailableCCCH
• Given the IMSI or TMSI and the # of retransmission used we know how many paged
mobiles we can support in that cell

• For example in case of not combined BCCH with the setting BS_AG_BLKS_RES = 5
and TMSI using 122553 MS can be paged when we assume 2 needed retransmissions.

4 3600 s
PagedMSPer Hour = PCHperHour = 2 * (9 − 5 )* = 122553
2 0 .235 s

35 © Nokia Siemens Networks RA20193EN14GLN0

4 TMSI or 2 IMSI can be paged per block

2 retransmissions
Available CCCH in a non-combined BCCH is 9 blocks
BS_AG_BLKS_RES = 5  5 blocks out of the 9 available blocks in BCCH are used for AGCH
 (9-5=4) : 4 PCH available

RA20193EN14GLN0 35
Air Interface

Exercise 2

• Starting from the previous exercise Call Mix

result (8.75 Erl in 13 TSLs) calculate 25mErl per subscriber
the needed amount of logical and
physical Signalling channels. 120 seconds mean hold time
• Use the following typical MHT 70% mobile-originated calls (MO)
Signaling Seconds 30% mobile-terminated calls (MT)
Procedure
MOC 2.8
1.5 handovers (HO) per call
MTC 2.8 2 location updates (LU) per call
LUP 3.5
SMS 3.5
0.1 IMSI detach per call
IMSI DET 2.8 63% no paging response
1 SMS call rate subs/hour
• Calculate the Signalling traffic per (80% terminated SMS)
subscriber
• show that one combined
CCCH/SDCCH TSL is not enough to
handle the Voice.

36 © Nokia Siemens Networks RA20193EN14GLN0

15 minutes

RA20193EN14GLN0 36
Air Interface

Exercise 2 solution

• BHCA = 350 sub

BHCA ⋅ MHT
Erlangs = = BHCA ⋅ Signalling _ Traffic _ per _ Subscriber
3600 Seconds

MHTtotal = MHTMOC / MTC + MHTHO + MHTLUP + MHTIMSI DET + MHTSMS

MHTtotal = 1 ⋅ 2,5s + 1,5 ⋅ 2,8s + 2 ⋅ 3,5 s + 0,1 ⋅ 2,8 s + 1 ⋅ 3,5s
MHTtotal = 17,78 s

MHTtotal 17,78s
Signalling _ Traffic _ per _ Subscriber = = = 4,93mErl
3600 s 3600 s

Erlangs = BHCA ⋅ Signalling _ Traffic _ per _ Subscriber = 350 * 4,93mErl = 1,73 Erl

• At 2% Blocking probability, 30% HR penetration rate, we need 6 log SDCCH channels.

• This is fitting to one standalone SDCCH.

Combi BCCH Multiframe contains 3 CCCH and

4 SDCCH.
Normal BCCH Multiframe contains 9 CCCH
Normal SDCCH contains 8 SDCCH

37 © Nokia Siemens Networks RA20193EN14GLN0

15 minutes

RA20193EN14GLN0 37
Air Interface

Coding Speed Modul.

GPRS Radio Timeslots Dimensioning and
modulation
MCS-1 8.8 GMSK
• GPRS dimensioning on the Air MCS-2 11.2 GMSK
interface is more difficult for many
reasons MCS-3 14.8 GMSK
– Radio Timeslots are shared BCCH = Signaling MCS-4 17.6 GMSK
– Coding Scheme can vary TS = Free TSL for CSW MCS-5 22.4 8-PSK
– Multi-slot capability TS = CDEF MCS-6 29.6 8-PSK
– Different services, different capacity.
TS = CSW Territory MCS-7 44.8 8-PSK
– More degraded due to radio
TS MCS-8 54.4 8-PSK
– Dynamic capacity on the TRX = (E)GPRS Territory/

• To keep PS dimensioning easier we TS = CDED MCS-9 59.2 8-PSK

assume the following Data Mix
– 12kbps (CS-2) in case of GPRS
– 35kbps (>MCS-6) in case of EDGE BCCH SDCCH TS TS TS TS TS TS
GTRX

GENA
Territory border EGENA
CMAX
TS TS TS TS TS TS TS TS
GTRX

Refer to S14 Documentation:

• Plan and Dimension/Example of BSS connectivity dimensioning
• Plan and Dimension/Dimensioning of network elements and interfaces/BTS EDGE dimensioning
38 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 38
Air Interface

Relation Between Data Rate and RF (C/I)

With Impairments
• The TSL data rate is C/I dependent
• Lower C/I can reduce the TSL data
rate significantly
• The figure shows that the TSL data
rate is around 25 kbps if the C/I is
15 dB.

Throughput
• The proper frequency plan of GSM
network is very important to
maximize TSL data rate

C/I

39 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 39
Air Interface

Two approaches

• Available data capacity

– Given an existing CS dimensioning we calculate what is the Default GPRS/EDGE
Capacity (CDEF) that does not block CS calls.
– For this approach we need the total bitrate that the operator wants to provide in the
cell, for example 200kbps for big cells (4 TRXs each), 100kbps for small cells (2 TRXs
each).
• Required data capacity
– Given the traffic volume, type, and performance requirements, we can find the needed
amount of Dedicated GPRS/EDGE Capacity (CDED).
– This approach can be used on Green Field networks to provided a certain Quality of
Service.
– For this approach let’s suppose we have a minimum data rate of 50kbps.
• In both cases we suppose
– 12kbps in case of GPRS
– 35kbps in case of EDGE

40 © Nokia Siemens Networks RA20193EN14GLN0

Available data capacity

Available data capacity strategy is used when you want to introduce EDGE to an
existing network. Dimensioning determines how much traffic is available through the
current system. The dimensioning input is a pre-defined system configuration. The
dimensioning output is the available traffic volume with a defined performance level.
Alternatively, you can calculate available capacities for different alternative
configurations.
Required data capacity
Required data capacity strategy is used when you want to design a network that
supports the defined amount of traffic and targeted performance level. The
dimensioning inputs are traffic volume, type, and performance requirements. The
dimensioning output is the needed amount of traffic dependent hardware and the
associated software configurations.

RA20193EN14GLN0 40
Air Interface

CSD and CSU

• CS Downgrade and CS Upgrade is not immediate but takes time.

• In order not to introduce additional blocking because of PS, the PS hardware keeps some
timeslots always available.
• Two BSC parameters (CSD and CSU) associated with the number of TRXs in the cell,
help tuning the number of free timeslots (that we can assume as average between these
two values).
• Averaging the two values.
– mean free RTSLs for two TRXs: (1+2)/2 → 1.5
– mean free RTSLs for four TRXs: (3+2)/2 → 2.5

TSL number after CS downgrade

TRX number 1 2 3 4 5
70 0 0 0 1 1
free TSL for CS downgrade (%)
95 1 1 1 2 2
(CSD)
99 1 1 2 2 3

TSL number after CS upgrade

TRX number 1 2 3 4 5
1 0 1 1 1 2
free TSL for CS upgrade (sec) 4 1 2 2 3 4
(CSU) 7 1 2 3 4 5
10 2 3 4 5 6

41 © Nokia Siemens Networks RA20193EN14GLN0

Table above gives free RTSLs with default parameters

• CS downgrade – if less RTSLs free in CS territory, PS territory downgrade triggered
• CS upgrade – PS territory upgrade can be triggered if at least that amount of RTSLs free
• Mean free RTSLs for 2 TRXs: 1.5; Mean free RTSLs for 4 TRXs: 2.5
free TSL for CS downgrade (CSD) – MML default: 95 %
free TSL for CS upgrade (CSU) – MML default: 4
CSU:
The margin of idle TCH/Fs that is required as a condition for starting a GPRS territory upgrade is defined by the
BSC parameter free TSL for CS upgrade (CSU). In fact, the parameter defines how many traffic channel radio
timeslots have to be left free after the GPRS territory upgrade. When defining the margin, a two-dimensional table is
used. In the two-dimensional table the columns are for different amounts of available resources (TRXs) in the BTS.
The rows indicate a selected time period (seconds) during which probability for an expected downgrade is no more
than 5%. The operator can modify the period with the BSC parameter CSU. The default value for the period length
is 4 seconds.
CSD:
The operator defines the margin of idle TCHs that the BSC tries to maintain free in a BTS for the incoming circuit
switched resource requests using the parameter free TSL for CS downgrade (CSD). If the number of idle TCH
resources in the circuit switched territory of the BTS decreases below the defined margin, a GPRS territory
downgrade is started if possible. The definition of the margin involves a two-dimensional table. One index of the
table is the number of TRXs in the BTS. Another index of the table is the needed number of idle TCHs. Actual table
items are percentage values indicating probability for TCH availability during a one-second downgrade operation
with the selected resource criterion. Default probability 95% can be changed through the free TSL for CS
downgrade (CSD) parameter.

CSD: Defining the margin of idle TCHs, %

CSU: Defining the margin of idle TCH/Fs
RA20193EN14GLN0 41
Air Interface
Air Interface – Available Capacity
2+2+2 configuration
• From the signalling table we know that 2
TRXs means:
– 2 RTSLs for signalling (1 BCCH and 1 SDCCH)
– 14 RTSLs for CS traffic
• CS BH traffic 8.2 Erl per Cell
• From the CSD / CSU table we know that the
Mean Free RTSLs is 1.5 for 2 TRXs
• Therefore the average number of timeslots
that can be used by GPRS is:
– 16 total timeslots
– Minus 2 for signalling
– Minus 8.2 for CS
– Minus 1.5 for CSD/CSU
– = 4.3 RTSLs = 150.5kbps with EDGE
42 © Nokia Siemens Networks RA20193EN14GLN0
Average PS traffic maximum during CS BH. If all average available PS RTSLs used during
CS BH, TRX RTSL utilization 100%.
RA20193EN14GLN0
4+4+4 configuration
• From the signalling table we know that 4 TRXs
means:
– 2 RTSLs for signalling (1 BCCH and 1 SDCCH)
– 30 RTSLs for CS traffic
• CS BH traffic 21.93 Erl per Cell
• From CSD / CSU table we know that the Mean
free RTSLs = 2.5 for 4 TRXs
• Therefore the average number of timeslots that
can be used by GPRS is:
– 32 total timeslots
– Minus 2 for signalling
– Minus 22 for CS
– Minus 2.5 for CSD/CSU
– = 5.5 RTSLs = 192.5 kbps with EDGE
• In this case we cannot provide the expected
data rate. Some hypothesis should be
removed.
42
Air Interface
Air Interface – Required Capacity
Default Territory Size CDEF
2+2+2 – territory considerations
• MS multislot capability (4 RTSLs)
• Data throughput 100 kbit/s
• Air interface – 35 kbit/RTSL
– => RTSLs to support 100 kbit/s
– 100/35 = 2.9 TSLs ~ 3 RTSLs
• Default territory size
• CDEF is given by Max(MS_multislot,
(expected traffic / average traffic per RTSL))
– Max(4, 2.9) => 4
• Max(MS_multislot, traffic) = 4 RTSLs
The results of default territory size calculations
determines the CDEF parameter value.
• The CDEF parameter set is 4 RTSLs
43 © Nokia Siemens Networks RA20193EN14GLN0
RA20193EN14GLN0
4+4+4 – territory considerations
• MS multislot capability (4 RTSLs)
• Data throughput 200 kbit/s
• Air interface – 35 kbit/RTSL
– => RTSLs to support 200 kbit/s
– 200/35 = 5.7 TSLs ~ 6 RTSLs
• Default territory size
• CDEF is given by Max(MS_multislot,
(expected traffic / average traffic per RTSL))
– Max(4, 5.7) => 6
• Max(MS_multislot, traffic) = 6 RTSLs
The results of default territory size calculations
determines the CDEF parameter value.
• The CDEF parameter set is 6 RTSLs
43
Air Interface

Air Interface – Required Capacity

Dedicated Territory Size CDED

• If the operator asks for 50kbps minimum per cell, then

• (50kbit/s)/(35 kbit/s / RTSL) = 2 RTSLs need to be dedicated (CDED) per cell to GPRS

2+2+2 configuration 2+2+2 configuration

• Available RTSLs for CS traffic per BTS
• 14 – 2 (CDED) = 12 RTSLs
• Traffic per cell = 8.2 Erl
• Erlang B (8.2 Erl, 12 TSLs) = 5.72% CS
blocking > than the expected 2%
• This problem can be solved by increasing
usage of HR or adding more hardware.
• Available RTSLs for CS traffic per BTS
• 30 – 2 (CDED) = 28 RTSLs
• Traffic per cell = 21.93 Erl
• Erlang B (21.93Erl, 28 TSLs) = 3.80% CS
blocking > than the expected 2%
• This problem can be solved by increasing
usage of HR or adding more hardware.

44 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 44
Air Interface

Air Interface Calculations – Summary

2+2+2 configurations 4+4+4 configurations

• Territory located in BCCH TRX • Territory located in BCCH TRX

• 2 RTSL dedicated territory to support
streaming
• 4 RTSL default territory for 2+2+2
configuration
• additional DR RTSLs needed to get
blocking less than 2%
• 2 RTSL dedicated territory per BTS for
streaming support
• 6 RTSL default territory for 4+4+4
configuration
• additional DR RTSLs needed to get
blocking less than 2%

45 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 45
Air Interface

Exercise 3

• Practice dimensioning the Air Call Mix

interface with CS, PS and signaling
• Use the usual Call Mix and the
results from Exercise 1 and 2.
• Dimension a cell for 350
subscribers, maximum 30% HR, 200
kbps average data, 50kbps
minimum.
• Consider MS Multislot capability of 4
RTSLs
25mErl per subscriber
120 seconds mean hold time
70% mobile-originated calls (MO)
30% mobile-terminated calls (MT)
1.5 handovers (HO) per call
2 location updates (LU) per call
0.1 IMSI detach per call
63% no paging response
1 SMS call rate subs/hour
(80% terminated SMS)

46 © Nokia Siemens Networks RA20193EN14GLN0

20 minutes

RA20193EN14GLN0 46
Air Interface

Exercise 3 solution
1/2
• Results from Exercise 1: 350 subscribers; 8,75Erl CS traffic; 2% Blocking probability, 30% HR
penetration rate; 13 TIMESLOTS min  2 TRXs.
• Results from Exercise 2: Two timeslots for Signalling needed; TSL0 = BCCH, TSL1 SDCCH
• Cells needs 2 TRXs: 
– 2 RTSLs for signalling (1 BCCH and 1 SDCCH)
– 14 RTSLs for CS traffic

• CS BH traffic 8.75 Erl per Cell

• From the CSD / CSU table we know that the Mean Free RTSLs is 1.5 for 2 TRXs
• Therefore the average number of timeslots that can be used by GPRS is:
– 16 total TS - 2 TSL for signalling - 8.75 TSL for CS - 1.5 TSL for CSD/CSU = 3.75 TSLs
– 3.75 TSLs * 35kbit/s per TSL = 131.25 kbps with EDGE
•  A cell with only 2 TRX cannot fulfil requirement of 200kbit/s average data throughput!
•  calculation with 3 TRXs
– 24 total TS - 2 TSL for signalling - 8.75 TSL for CS - 2.5 TSL for CSD/CSU = 10.75 TSLs
– 10.75 TSLs * 35kbit/s per TSL = 376.25 kbps with EDGE

47 © Nokia Siemens Networks RA20193EN14GLN0

RA20193EN14GLN0 47
Air Interface

Exercise 3 solution
2/2
• CDEF calculation:
– MS multislot capability (4 RTSLs)
– Data throughput 200 kbit/s
– Average Air interface throughput for EDGE is 35 kbit/RTSL
– => RTSLs to support 200 kbit/s = 200/35 = 5.7 TSLs ~ 6 RTSLs
• CDEF is given by Max(MS_multislot, (expected traffic / average traffic per RTSL))
– Max(4, 5.7) => 6
• CDED calculation:
• CDED = 50kbit/s / (35 kbit/s / RTSL) 1,4  2 RTSLs need to be dedicated (CDED) per cell to GPRS
• Available RTSLs for CS traffic per BTS
– 24 - 2 (Signalling) - 2 (CDED) = 20 RTSLs
– Traffic per cell = 8.75 Erl
• FR: Erlang B (8.75 Erl, 20 TSLs) = < 0,05% CS blocking < than the expected 2%
• Even with pure FR penetration the result is below assumed blocking
• RESULT:
– 2 TRX, Signalling: BCCH + 1 SDCCH
– 6 RTS for CDEF  Parameter CDEF = 28%
– 2 RTS for CDED  Parameter CDED = 10%

48 © Nokia Siemens Networks RA20193EN14GLN0

Calculation of Parameters in percent:

6/22 * 100 = 27.27%  considering rounding rules: 28%
2/22 * 100 = 9.09%  considering rounding rules: 10%

RA20193EN14GLN0 48