Com MN PG

11.02.2005 P.Schwab, N.Zicari

Weighted LLC Data Throughput

Requested counters are Weighted LLC User Data Throughput UL/DL in Kbytes per second.

LLC Data Throughput

LLC throughput UL/DL has to be measured as per “user perceived” and includes only application
data. Only end-user data shall be considered into the throughput. The DL dummy LLC blocks sent
in DL Delayed TBF Release phase must be excluded.

The measurement is based on CDF’s.

CDF := Continuous Data Transfer between 2 delayed phases inside one TBF.

GMM/SM signaling data

GMM/SM and other signaling related data blocks and signaling TBF’s shall be excluded from
throughput calculation.
The following criteria define token to extract such signaling data:
Downlink:
 “T – Bit” of QoS Profile IE as part of each DL-UNITDATA PDU, (3GPP 48018)
Uplink:
 Packet Channel Request received on PRACH indicating MM procedure or Page
Response or Cell Update (3GPP 44060)
 EGPRS Channel Request received on RACH or PRACH indicating Signalling.
 All messages using PFI 1.
 Two phase access with a Packet Resource Request indicating in access type field
Mobility Management or Cell Update or Page Response.
 UL TBF associated to Temporary Logical Link Identity (TLLI) with “Random” or
“Foreign” bit combinations, (3GPP 23.003)
TLLI structure starts with
o 11  local,
o 10  foreign,
o 01111  random

1.1 Calculation Method

The implementation of the new counters should calculate the relative throughput for all CDF’s of a
given cell, weight them by volume of data and build a mean value.

The value of the counters can be described as follows:

 Com MN PG

11.02.2005 P.Schwab, N.Zicari

 DATA  CDF  
Throughput    * weight  CDF  
( CDF )  LIFETIME  CDF  

Where weight is defined as:

DATA(cdf )
weight (cdf ) 
 DATA(cdf )
( CDF )

The formula could also be written as:

 DATA  CDF  
  LIFETIME  CDF  * DATA  CDF  
Throughput 
CDF  
 DATA  CDF 
CDF

To calculate the throughput, the following sub measurements are required:

a.) DATA (CDF): Total amount of LLC User Data (Kbytes) per CDF. GMM/SM and other
signaling related data blocks and signaling TBF’s shall be excluded.
b.) LIFETIME (CDF): Measurement period (sec) per CDF. Timestamps to define the period
will be described in the following chapters.

1.1.1 CDF Lifetime

CDF Lifetime
The total TBF time used for throughput calculation should be adjusted without counting period of
“delayed TBF release” and “extended TBF”. Details on timestamps to define TBF periods are
described in following chapter.
A TBF running over the end of a granularity period is counted in the starting new one.

1.1.1.1 DL Measurement

1.1.1.1.1 Normal Condition

Figure 2 shows the method to measure the LLC throughput components under “normal”
conditions where the TBF ends normally within the same cell.

Start-Time:
In this case, a time stamp is recorded when the first (non GMM/SM, non dummy LLC blocks) LLC
block is transmitted via the RLC block from the BSC to the BTS. Prior to this, TBF is setup or
more LLC blocks arrive for a TBF in “DL Delayed TBF Release phase”. During the downlink
transfer, the number of LLC bits successfully transferred (derived from PDAN/EPDAN) is counted.

End-Time:
 Com MN PG

11.02.2005 P.Schwab, N.Zicari

The ending timestamp is recorded when the last RLC block is successfully acknowledged
(End_Time). The end condition is given, when no further LLC blocks (non dummy LLC) are in the
queue to send and an EPDAN/PDAN is received for the last RLC block. Two sub cases must be
distinguished:
o “DL Delayed TBF Release” phase activated:
It is possible, that the last EPDAN/PDAN is received during a DL Delayed TBF Release
Phase. The condition FBI=1 cannot used to determine the last RLC block, since dummy
LLC blocks (time) must be excluded.
o “DL Delayed TBF Release” phase deactivated:
If DL Delayed TBF Release is switched off, then the trigger is exactly the FINAL
EPDAN/PDAN received, because no Delayed DL TBF Release is applied.

At the successful end of this condition, the elapsed time is determined and the running sums of
the # of LLC bits successfully transferred and the elapsed time are updated.

Figure 2: Downlink LLC throughput method when TBF is normally terminated on the same cell.

1.1.1.1.1.1 TBF carring 2 CDF

 Com MN PG

11.02.2005 P.Schwab, N.Zicari

Following picture shows an example of TBF carrying more then one CDF

Figure 2.1 Downlink LLC throughput; Example of TBF carrinyg more then one CDF

1.1.1.1.2 Cell Re-selection Condition

Figure 3 shows the method to measure the LLC throughput components when the user’s data
session does not complete on this cell and a FLUSH is received for this user on this cell. This
includes the “cell reselection” case from one cell to another.

This case starts out the same as case 1 (“Normal Condition”) where the TBF is being carried on
the “old cell”. However, due to the MS initiating a cell reselection to a “new cell”, there are LLC
blocks remaining in the queue of the “old cell”. In this case, the ending time stamp is recorded
when the FLUSH command is received by the SGSN. The running sum is then updated as in
case 1 above.

However, the number of LLC bits successfully sent is accumulated up to the moment the Flush
arrives. The measurement does not include those blocks not acknowledged by the mobile prior to
the cell reselection.
 Com MN PG

11.02.2005 P.Schwab, N.Zicari

Figure 3 Downlink LLC throughput method when TBF undergoes a cell reselection to another
cell.

1.1.1.1.3 Error Condition

In case a TBF will be terminated abnormally, no measurement according to this TFB will be done.

1.1.1.2 UL Measurement

1.1.1.2.1 Normal Condition

Figure 4 shows the method to measure the LLC throughput components under “normal”
conditions where the TBF ends normally within the same cell. This is a very similar case to the
downlink case with several exceptions as shown in the figure.

Due to the fact that the “final” PUAN can have a delay up to 4 seconds after the reception of the
last UL RLC block (CR2692), the reception of the last UL RLC block at BSC instead of sending
the “final” PUAN is used as trigger for Data counting.
 Com MN PG

11.02.2005 P.Schwab, N.Zicari

Figure 4 Uplink LLC throughput method when TBF is normally terminated on the same cell.

1.1.1.2.2 Cell Re-selection and Error Condition

Figure 5 shows the method to measure the LLC throughput component when the user’s TBF do
not fully complete for this cell. Only LLC bits successfully received are used to update the running
sum up to that moment.

If the MS initiate the cell re-selection or if the TBF is closed abnormally (i.e. due to “radio contact
lost”), the UL TBF is closed when TBF specific counter N3101 exceeds the O&M configured
maximum value. Normally this happens before a FLUSH arrives.

If the MS is moved via NCCR, the TBF is closed at moving decision.

 Com MN PG

11.02.2005 P.Schwab, N.Zicari

Figure 5 Uplink LLC throughput method when cell re-selection or TBF is closed abnormally.