Transmission Data Checks

05/12/2020 Security Level:
HSPA Data Transmission

Performance
Improvement
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HSDPA 性能研究与华为解决方案汇报
HSDPA Basic Concepts and Process of Identifying

Data Transmission Problems
HSUPA Basic Concepts and Process of Identifying

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Basic Concepts — Protocol Structure of HSDPA
User Plane
The data transmission protocol layers consist of the physical layer, MAC layers
(MAC-hs/ehs layer and MAC-d layer), RLC layer, PDCP layer, TCP/IP layer, and application
layer. Figure 2-1 shows the involved NEs and the relationships among layers.
On the RAN side (excluding the UE), the physical layer, MAC layer, and RLC layer are
involved. The TCP/IP layer is adjacent to the PDCP layer and the RLC layer. Therefore, the
TCP/IP layer may also be affected by the RAN in some scenarios
FTP servers, streaming
servers, and websites.
PDCP Packet Data Convergence Protocol

Basic Concepts — Data Frame Structure of HSDPA User
Plane Protocol
The rate at each layer is classified into the PDU rate and the SDU rate.
The PDU rate includes the overhead of the current layer, whereas the SDU rate does not
include the overhead of the current layer.
Therefore, the SDU rate of a layer equals to the PDU rate of the upper layer.
(s)RBs for UE1 (s)RBs for UE2 PDU structure
RLC SDU
RLC RLC RLC RLC RLC RLC RLC Payload

Header
MAC-d MAC-d RLC Payload

Header
MAC-c U-RNTI RLC Payload

Header
Iub-FP Iub-FP Iub-FP
MAC-ehs MAC-ehs U-RNTI RLC Payload

Header Header

Basic Concepts —CQI Report Principles
The UE measures the Ec/No of the Common Pilot Channel (CPICH) and adds a
Measurement Power Offset (MPO) as the Ec/No estimation value of the HS-
PDSCH.
HS-PDSCH Ec/No (estimation value) = Ec/No
cpich + MPO
That is, the UE assumes that the NodeB transmits the HS-PDSCH according to
CPICH Power + MPO.
Then, add the SF gain 10 * log16 to obtain the SNR of the HS-PDSCH.
SNR HS-PDSCH = HS-PDSCH Ec/No + SF gain 10
* log16

Basic Concepts —CQI Report Principles
The CQI is obtained according to the relationship between the SNR and CQI of the
simulated HS-PDSCH.
Generally, the difference between the CQI and SNR is a constant (4 or 4.5 dB).
CQI formula (for the HSDPA excluding 64QAM) :
CQI = CPICH Ec/No + MPO + 10 * log16 + 4.5

= SNRcpich + MPO + 4.5
= SNRhs-pdsch (based on assumed power) + 4.5 (depending on the UE
implementation)
MPO = min(13, Pcell-Pcpich - MPO constant) dB The MPO constant is 2.5 by

default.
The previous formula shows that CQI increase by 1 when SNR HS-PDSCH increase by
1.
With 64QAM: when the CQI is greater than 25, CQI increases by 1 when SNR
increases by 2 dB. CQI = SNRcpich + MPO + 4.5 if CQI <= 25
or CQI = 25 + (SNRcpich + MPO + 4.5 - 25)/2 if
In this case: CQI > 25

1. 终端能力
Basic Concepts — UE Capabilities
Maximum Maximum number of Supported Supported
Minimum Supported modulations
bits of an HS-DSCH modulations with
number of HS- without MIMO modulations
HS-DSCH category inter-TTI transport block MIMO operation
DSCH codes received within
operation
and without dual with dual cell
interval or dual cell operation
received an HS-DSCH TTI cell operation operation
5 3 7298
Category 1
5 3 7298
Category 2
5 2 7298
Category 3
5 2 7298
Category 4
5 1 7298
Category 5
QPSK, 16QAM
5 1 7298
Category 6
10 1 14411 Not applicable
Category 7
(MIMO not
10 1 14411 supported)
Category 8
15 1 20251
Category 9
15 1 27952 Not applicable (dual
Category 10
cell operation not
5 2 3630 supported)
Category 11
QPSK
5 1 3630
Category 12
15 1 35280
Category 13
QPSK, 16QAM, 64QAM
15 1 42192
Category 14
15 1 23370
Category 15
QPSK, 16QAM
15 1 27952
Category 16
35280 QPSK, 16QAM, 64QAM –
Category 17 15 1
23370 – QPSK, 16QAM
42192 QPSK, 16QAM, 64QAM –
Category 18 15 1
27952 – QPSK, 16QAM
15 1 35280
Category 19
QPSK, 16QAM, 64QAM
15 1 42192
Category 20
15 1 23370
Category 21
QPSK, 16QAM
15 1 27952
Category 22
- -
15 1 35280
Category 23 QPSK, 16QAM,
64QAM
HUAWEICategory
TECHNOLOGIES
24 CO.,
15 LTD. 1 Huawei42192
Confidential Page 7
Basic Concepts — Code Assignment (1/3)
The code assignment algorithm is involved in both RNC and NodeB.
RNC:
Manual assignment : set the number of codes to be assigned.
Automatic assignment : set the maximum number of codes and minimum
number of codes to be assigned.
NodeB: Enable or disable the NodeB dynamic code function.
We will introduce different combinations of the two algorithms. The number of

channels used by the cell is set by default (four HS-SCCHs with HSUPA
activated):
• Manually assign five codes on the RNC

• Disable the dynamic codes on the NodeB :
=> The HS-DSCH uses a maximum of 5 SF16 and a
minimum of 5 SF16.
• Enable the dynamic codes on the NodeB:

minimum of 5 SF16
• Automatically assign a maximum of ten codes and a minimum of five codes

on the RNC
• Disable the dynamic does on the NodeB:

=> The HS-DSCH uses a maximum of 10 SF16 and a minimum of 5 SF16.
• Enable the dynamic does on the NodeB:

minimum of 5 SF16.
• The policy of RNC manual assignment + NodeB dynamic code enabled
is recommended for the existing network.
• RNC automatic assignment + NodeB dynamic code disabled is

recommended if networks do not support the NodeB dynamic codes.
Over one SF16 codes are used by the Common Control Channels
=> maximum of 14 SF16 can be used for HSDPA

To ensure that 15 codes can be used by the accessed DPA user, you need to modify
the configurations of the channels (Eg disable HSUPA, only 2 HS-SCCHs in one TTI..)
SRB over DCH : Each accessed HSDPA user consumes an associated DPCCH using one
SF256
SRB over HSDPA : F-DPCH is multiplexed by all users => save codes
Default configuration for codes

usage by common channels in
the
• The CCH uses one SF32,
• Four HS-SCCHs, each one use
one SF128 => one SF32,
• The E-RGCH and E-HICH
multiplexes one SF128,
• The E-AGCH uses one SF256.

Basic Concepts — EL2 Principles (1/3)
Before the R7 which introduces the L2 enhancement, RLC PDU size was
configured to a fixed size.
Generally, the RLC SDU size configured on the network is small :
• The typical value of RLC SDU size is 320 bits or 640 bits.
• Although the RLC window size supports a maximum of 2048
For the following example : RLC PDU size is 640 bits, the RLC window size is
2048 RLC PDUs, and the RTT delay of the sender from transmitting data to
receiving the ACK message in AM mode is 100 ms.
The maximum
transmission rate is 640
bits * 2048/0.1s = 13.1
Mbit/s.

64QAM, MIMO, 64QAM+MIMO, and DC+64QAM technologies are introduced

in R8.
The theoretical peak rate of service data transmission can reach 21.6 Mbit/s,
28.8 Mbit/s, and 43.2 Mbit/s respectively.
• If the RLC PDU size is too large, no complete RLC PDU can be correctly
transmitted to the UE when the channel quality is poor; therefore, normal
data transmission cannot be performed and the coverage is reduced.
• If the RLC PDU size is too small and the RLC window size is increased to
improve the data transmission rate, many RLC PDUs are multiplexed in one
MAC-hs PDU when the user channel quality is good; therefore, much
redundant information is brought in the RLC PDU data heads, and the data
transmission efficiency of the air interface is reduced.
To fully match the data transmission capability of the air interface, improve
the data transmission efficiency, the L2 enhancement is introduced.

The maximum RLC PDU is set to

302 bytes (2416 bits) in EL2 by
default
The L2 enhancement mainly affects RLC layer, MAC layer, and user plane FP data
transmission of Iub interface on the RNC.
• The variable PDU size of downlink AM is introduced at the RLC layer.

• The MAC-ehs is introduced at the MAC layer.
• The 64QAM, MIMO, and DC-HSDPA features must be supported by EL2 enhancement.

Basic Concepts — Theoretical Rates of
Layers (1/2)
Relationships among the throughput of layers :
• TCP/IP layer: Data packets at this layer are received from the application
layer. The TCP/IP layer matches data packets based on the MTU (Maximum
Transfer Unit ) size. Generally, the MTU size is 1,500 bytes, which is equal to
12,000 bits. The header overhead of 40 bytes (320 bits) is added to each
MTU.
• PDCP layer: Data transmission is considered as transparent transmission

at this layer, and therefore no overhead is added.
• RLC layer: This layer matches data packets of the PDCP layer based on
the RLC SDU size. The overhead of 16 bits is added to each SDU to form an
RLC PDU. Then, the RLC PDU is transmitted to the MAC-d layer.
• MAC-d layer: Data transmission is considered as transparent transmission

at this layer, and therefore no overhead is added.

Basic Concepts — Theoretical Rates of
Layers (2/2)
• MAC-hs/ehs layer:
At this layer, a proper TBS is selected to match the data of the upper layer
and actual resources of the air interface.
• In non-EL2 mode, the overhead of the MAC-hs layer consists of the fixed
21-bit header overhead and the padding overhead of the TBS tail.
• In EL2 mode, the overhead of the MAC-ehs layer consists of the fixed 8-
bit header overhead and additional 16-bit header overhead required by
each MAC-ehs SDU (RLC PDU).
• Physical layer: The rate at this layer is 3.84 Mchip/s. The rate indicates
the rate of the MAC-hs/ehs layer, that is, TBS/2 ms.

Basic Concepts — Calculation of Theoretical
Rates (1/4)
Example for UE CAT14 ：
CAT14 supports EL2 and 64QAM (MAC-ehs entity) Maximum number of bits of an HS-DSCH
transport block received within
an HS-DSCH TTI
The maximum TBS used in CAT14 is 42192 bits
1) The maximum rate of the MAC-hs layer is: 42192 bits /2 ms = 21.096
Mbit/s
2) At the RLC layer (EL2) :

- The maximum RLC PDU is set to 302 bytes (2416 bits) in EL2 by default
- If 42192 (minus fixed 8 bits overhead for EL2) => 42184 bits
- Nb of RLC PDU (Mac-ehs SDU) => int (42184/2416) = 17 PDU
- 17 PDUs of 2416 bits can be carried and 16-bit overheads are introduced
(EL2). 42184 bits – (2416 bits * 17) – (16 * 17) = 840 bits.
- After subtracting the introduced 16-bit overhead, the PDU that can be carried
is 824 bits.
The maximum PDU rate at the RLC layer is: (2416 bits * 17 + 824 bits)/2
ms = 20.95 Mbit/s
Rates (2/4)
3) At the TCP/IP layer the maximum PDU rate is equal to the SDU rate at
the RLC layer, transparent transmission between the MAC-d layer and the PDCP layer
The overhead of 16 bits is added to each SDU to form an RLC PDU
which is: [(2416 - 16) bits * 17 + (824 – 16) bits] /2 ms = 20.8 Mbit/s.
4) If the MTU size (Maximum Transfer Unit ) is set to 1500 bytes At the TCP
layer, the rate at the application layer is: 20.8 Mbit/s * [(1500 – 40)/1500]
= 20.25 Mbit/s.
If there are only 14 HSPDSCH codes, the maximum TBS used in CAT14 is 38576
bits:
In this case, the maximum rates of the MAC-hs layer, RLC layer, TCP/IP layer,
and application layer are 19.29 Mbit/s, 19.16 Mbit/s, 19.03 Mbit/s, and 18.52
Mbit/s respectively.

Basic Concepts — Calculated of Theoretical
Rates (3/4)
Downlink UE Throughput During RNC Real-Time Performance Tracing
Real-time performance tracing from RNC give the Downlink UE throughput at the
MAC-d layer (that is, the SDU rate at the MAC-hs layer) or the PDU rate at the RLC
layer.
Downlink Throughput Displayed in DU Meter (monitor TCP IP throughout)
Downlink throughput displayed in DU meter can be considered as the SDU rate at the
RLC rate.

Rates (4/4)
IBLER / SBLER/ RBLER
• The 1st BLER is called initial BLER (IBLER).
• SBLER indicates the sum BLER, regardless of the initial TBS transmission or HARQ
retransmission.
• Residual BLER (RBLER) indicates the BLERs for TBs still incorrectly transmitted after all the
HARQ retransmissions at the MAC-hs layer.
Example:
The maximum number of HARQ retransmission is 4, three TBSs must be transmitted:
• The first TB is correctly transmitted during the initial transmission.
• The second TBS is retransmitted correctly after an initial transmission.
• The third TB is retransmitted incorrectly for four times.
• IBLER, the initial transmission of the first TB is successful and the initial transmissions of the
second and third TBs fail. Therefore, IBLER = 2/3 = 66.67%.
• SBLER, the first TBS is transmitted only once with zero transmission failure. The second TBS is
transmitted twice with one transmission failure. The third TBS is transmitted five times with
transmission failure five times. Therefore, SBLER = (0 + 1 + 5) /(1+2+5) = 75%.
• RBLER, the first TB is correctly transmitted during the initial transmission. The second TB is
retransmitted correctly after an initial transmission. The third TB fails to be retransmitted for
four times. Therefore, RBLER = 1/3 = 33.33%.

Process of identifying stationary test-based
HSDPA data transmission problems Identify stationary
test-based HSDPA data
transmission problems
Dial-up succeeds while

transmission fails
Y
N
3.2.1
Identify who
transmission fails
N
Can data transmission be started
Y
Y
Is data transmission OK?
3.2.2
Check RAN problems
RAN problems?
Y N
3.2.14
3.2.3 3.2.4 3.2.5 3.2.6 3.2.7
N
Check and Check cells’ Check access Check Check the Check bandwidth
clear alarms HSDPA status signaling licenses DCCC setting on the IU-PS
interface
Y 3.2.15
Is the problem identified?
Check packet
N loss on the Iub
interface
3.2.8 3.2.9
Check 3.2.10 3.2.11
Contact CN
Check downlink downlink code Check the number of Check radio 3.2.16 engineers to locate
power resources resources online users in a cell quality Check packet the fault, which
losses on the IU- Y
must be supported
PS interface and by the RAN
TCP mechanism
3.2.17
Y
Is the problem Check and Replace the UE or
identified? isolate UE faults driver program
N
3.2.13 3.2.18
Check the bandwidth on the lub interface Check CPU
usage of laptops
3.2.12
N
Check if RLC downlink Is the problem
window is full identified?
Y
Y
Is the problem
identified?
N
HUAWEI TECHNOLOGIES CO., LTD. Huawei Collect
Confidential
3.2.19 Page 20
data and
report problems END
Process of identifying Drive Test test-based
HSDPA data transmission problems
Identify DT test-based HSDPA
data transmission problems
Perform static test of Y Handle with the

data transmission on a near point,
check whether any problem
problem exists
3.2.4 3.2.5 3.2.7 3.2.10 3.2.11 3.2.14

Check and clear Check the license, Check downlink Check downlink Check the bandwidth
alarms, especially, Check cells’
HSDPA status especially the power resources code resources of the lub interface on
cell-level alarms NodeB-level license in each cell in each cell each NodeB
Perform DT in idle
period (with few
online users)
Does call Y Handle with the

drop or handover failure (or
problem
not timely) exist
Does abnormal Y
Handle with the
point exist (with high CQI but
problem
low throughput)
N N
Is the problem solved
Optimize RF coverage Y
and improve the
average CQI
Y
Is the problem solved END
3.2.19
Collect data and report
problems

Flowchart of analyzing HSDPA cell performance
problems
There is an Identify HSDPA
optimization scheme. cell performance
problems
The item cannot be
evaluated at present.
Does the
N average single-user throughput reach
END
the required BER on the air
interface?
Is the BER
Y on the air interface
high?
Optimize the Is the CQI Is the power

Y Y
coverage poor? usage high?
Perform Are there N

Y
expansion many UEs?
Perform Iub Is the Iub

Y transmission usage
expansion
high?
N
Is the
Optimize the Is the RLC
Y transmission quality of Y
transmission retransmission ratio
the Iub path poor?
high
Check power Is the residual

Y BER on the air interface
control parameters N
high?
N
UE problems
Perform Is the code usage

Y
expansion high?
Global or upper- Is upper-layer Does the theoretical cell rate

Y data insufficient? Y
layer problems meet the requirement?
N N
Other problems
END
Analysis on HSDPA cell performance
problems
Step Evaluation Item Evaluation Result and Handling Suggestion
High Low
(1)
Bit error rate (BER) on the air Optimize the coverage. Go to step (2).
interface in the cell
(2)
Perform the following operations based on the CQI:
Power usage of the cell If the CQI is poor, optimize the coverage. Go to step (3).
If the CQI is normal, add carriers.
(3)
Usage of the Iub transmission Expand the Iub transmission bandwidth. Go to step (4).
bandwidth
(4) Perform the following operations based on the IP path
transmission quality on the Iub interface:
If the transmission quality is poor, optimize
RLC retransmission rate transmission. Go to step (5).
If the transmission quality is normal, check the residual
bit errors on the air interface. For the cells with many bit
errors on the air interface, check power control
parameters.
(5) Check whether the
theoretical rate of the cell
meets the requirement. If
Code resource usage Add code resources. the theoretical rate meets
the requirement, the upper-
layer data sources are
insufficient.

HSDPA 性能研究与华为解决方案汇报
HSDPA Basic Concepts and Process of Identifying

HSUPA Basic Concepts and Process of Identifying


Basic Concepts — Protocol Structure of HSUPA User
Plane
Figure below shows the protocol structure of HSUPA data services. Different
from the R99 user plane, a MAC entity MAC-e/es is added at the MAC-d layer on the
HSUPA user plane.
DTCH DCCH DCCH DTCH
MAC-d MAC-d
MAC-es
MAC-es /
MAC-e
MAC-e MAC-e EDCH FP EDCH FP
PHY PHY TNL TNL TNL TNL
Uu
UE NodeB Iub DRNC Iur SRNC

Basic Concepts — Data Frame Structure of HSUPA User Plane
Protocol
MAC-es header overhead:
• TSN : Transmission Sequence Number (6 bits)
MAC-e header overhead:

• DDI : Data Description Indicator (6 bits)
• N: Number of Mac-d PDU in a logical channel (6 bits)
• SI system information : SI bits and padding bits in the end
MAC-d PDUs coming from one Logical Channel
RLC DCCH DTCH DTCH

RLC PDU: Header DATA MAC-d PDU MAC-d PDU MAC-d PDU
MAC-d MAC-d PDU: DATA
MAC-d Flows
DDI1 N1 TSN1 MAC-es SDU MAC-es SDU MAC-es SDU
Numbering Numbering Numbering MAC-es PDU: TSN DATA DATA N1 MAC-es SDUs of size and LCh indicated by DDI1
Multiplexing MAC-e PDU: MAC-es PDU1

MAC-es/e
DDI N DDI N DDI DATA DATA Padding
(Opt)
MAC-e header MAC-es PDU
HARQ
processes DDI1 N1 MAC-es PDU1 DDI2 N2 MAC-es PDU2 DDIn Nn MAC-es PDUn
L1 DATA
1. Simplified architecture showing MAC inter-working in UE. The left part shows the functional split while the right part shows PDU construction
Mapping info signaled over RRC
DDI1 N1 DDI2 N2 DDIn Nn DDI0 MAC-es PDU1 MAC-es PDU2 MAC-es PDUn SI Padding
PDU size, logical channel id, MAC-d flow (Opt) (Opt) (Opt)
id => DDI
MAC-e PDU

Basic Concepts — Factors Affecting the Uplink
Load
Number of Users in the Cell
• Check the number of users in the cell in real time on the RNC LMT.
The uplink load is shared by all users. When the number of users increases, the
available load of each user is reduced, therefore affecting the throughput.
On the other hand, the HSUPA scheduling can only control the load of the HSUPA
scheduling users.
If many non-HSUPA scheduling users exist in the cell, the available load of the HSUPA
scheduling user is affected, therefore affecting the actual rate of the HSUPA scheduling
users.
• If the actual load is less than or equal to 75%, the HSUPA user throughput
should be higher than to MAX(GBR, 1 RLC PDU rate).
• If the actual load is greater than 75% and less than 95%, the HSUPA user
throughput is equal or les than MAX(GBR, 1 RLC PDU rate).
1. Simplified architecture showing MAC inter-working in UE. The left part shows the functional split while the right part shows PDU construction
• If the actual load is greater than 95%, the HSUPA user throughput is hard to
reach the GBR but may meet 1 RLC PDU rate.

Background Noise Setting of the Cell
You can set the background noise of the cell in two methods: manual setting and automatic update.
If the background noise set on the RNC LMT is different with the background noise of the actual cell, the
cell throughput is affected.
• If the set value of the background noise is greater than the value of the actual background
noise
• The system stability may be reduced.
• The actual throughput of the cell is greater than the throughput related to the target value
of Rot.
•
•
When the set value of the background noise is smaller than the actual value,
• The actual throughput of the cell is smaller than the throughput related to the target value
of RoT.
Run LST UCELLCAC on the RNC LMT to query the background noise configuration in
Check thethe
setting
cell of the background noise and monitor the number of cell users in real time
on the RNC LMT:
Run MOD CELLCAC on the RNC LMT to modify the configuration background
• In test network
noise : if the query result shows that the background noise set in the cell is different
from the actual background noise
• In Commercial network : do not modify the configured background noise directly,

otherwise, the uplink coverage may shrink.
=> It is recommended
HUAWEI TECHNOLOGIES CO., LTD. that field engineers
Huawei check the cause
Confidential of the
Page 28 high background
noise.
Basic Concepts — Factors Affecting the Uplink
Load
External Interference :
External interference involves neighboring interference and foreign interference
If a burst of interference occurs, the load of the cell rises instantly causing the throughput
fluctuation of HSUPA users.
=> Check the RTWP of the cell when no user exists or identify the problem by using
frequency sweep.

Basic Concepts — Uplink CE Consumption
Rules
Rate Number of CEs Corresponding

Direction SF
(kbit/s) Consumed Credits Consumed
UL 8 64 1 2
UL 16 64 1 2
UL 32 32 1 2
UL 64 32 1 2
UL 128 16 2 4
UL 144 16 2 4
UL 256 8 4 8
UL 384 4 8 16
UL 608 4 8 16
UL 1450 2SF4 16 32
UL 2048 2SF2 32 64
UL 2890 2SF2 32 64
UL 5760 2SF2+2SF4 48 96

To support HSUPA, 3GPP TS 25.306 defined nine UE categories. These UEs support
different peak rates at the MAC layer, ranging from 711 kbit/s to 23 Mbit/s.
Max. Data Rate (Mbit/s)

E-DCH Max. Capability MAX EDCH MAX EDCH
E-DCH TTI
Category Combination TBS (10ms) TBS (2ms) MAC Layer MAC Layer
Air Interface
10 ms TTI 2 ms TTI
Category 1 1 x SF4 10 ms only 7110 0.71 - 0.96
Category 2 2 x SF4 10 ms and 2 ms 14484 14000 1.44484 1.40 1.92
Category 4 2 x SF2 10 ms and 2 ms 20000 289000 2.0 2.89 3.84
Category 6 2 x SF4 + 2 x SF2 10 ms and 2 ms 20000 57400 2.0 5.74 5.76
Category 7 2 x SF4 + 2 xS F2 10 ms and 2 ms 20000 1150000 2.0 11.50 11.52
Category 8 2 x SF4 + 2 xS F2 2 ms 20000 1150000 2.0 11.50 11.52
Category 9 2 x SF4 + 2 xS F2 2 ms 20000 2300000 2.0 23.00 23.04

Basic Concepts — calculated of Theoretical Rates
RLC PDU UL throughput :
= Total size of all RLC PDUs transmitted at the RLC layer within a
measurement period / Measurement period
• Total size of all RLC PDUs transmitted at the RLC layer :

- involves the PDUs transmission and retransmission.
- Data transmitted by the MAC-d layer including the header
overhead of the RLC PDU with total size of 16 bits.
• Measurement period : all the time whether data is transmitted or not.
Relationship between the RLC PDU UL throughput and the MAC-e

PDU available rate:
RLC PDU UL throughput = MAC-e PDU available rate * (1 - MAC-e PDU

header overhead ratio)

Basic Concepts — calculation of Theoretical
Rates
RLC SDU Throughput UL
= Total size of all RLC SDUs transmitted at the RLC layer within a measurement period /Measurement
period
• Total size of all RLC SDUs transmitted at the RLC layer :
= Total bits of RLC PDUs – Σ of retransmitted bits and RLC PDU header overhead (16bits in total).
The relationship between the RLC SDU Throughput UL and the RLC PDU Throughput UL :
RLC SDU throughput UL ≈“RLC PDU UL throughput” * “(1 - RLC PDU retransmission rate UL)” * “RLC
PDU header overhead ratio.”
Uplink Throughput involved in RNC Radio Performance Monitoring

MAC SDU rate (the input rate at the MAC layer) also called the RLC PDU rate (the output rate at
the RLC layer) involves the retransmitted data at the RLC layer.
MAC-d SDU rate = (TB-Size * Number of TBs) /
TTI
HSUPA CAT3, MAC SDU size = 336 bits:

MAC-d SDU rate = int(14484/336) * 336/10 = 1.4448 Mbit/s
HSUPA CAT6, MAC SDU size = 336 bits:

MAC-d SDU rate = int(11484/336) * 336/2 = 5.712 Mbit/s

Basic Concepts — HSUPA Theoretical Rates of
Layers
CAT3 ：
1) Throughput at the physical layer: (3840000/4) * 2 (SF4) = 1.92 Mbit/s
2) Data rate at the MAC-e layer: Maximum TBS at the MAC-e layer /10 ms
= 14484 * 1000/10 ms = 1.448 Mbit/s
Number of MAC-d PDUs per MAC-e PDU = Maximum TBS at the MAC-e layer (bits) / MAC-d
PDU size(bits)
Number of MAC-d PDUs (MAC-d PDU size = 336 bits) = int(14484/336) = 43,
RLC payload rate : CAT3 theoretical rate = (RLC payload size * Number of TBs) / TTI
RLC SDU size = MAC-d PDU - MAC header - RLC header = 336 -16 = 320 bits
CAT3 theoretical rate (MAC-d PDU size is 336 bits) = (320 * 43) /10 = 1.376 Mbit/s.
The MAC SDU rate monitored on the LMT = int(14484/336) * 336/10 = 1.448 Mbit/s.
The maximum throughput at the application layer ≈ the RLC payload rate / (1 + 10% of
HARQ retransmission) = 1.36 Mbit/s

Layers
CAT5 ：
Throughput at the physical layer: (3840000/2) * 2 (SF2) = 3.84 Mbit/s

Data rate at the MAC-e layer: Maximum TBS at the MAC-e layer * 1000/10 ms => 20000 * 1000/10 = 2
Mbit/s
Number of MAC-d PDUs per MAC-e PDU = Maximum TBS at the MAC-e layer (bits)/MAC-d PDU size (bits)
Number of MAC-d PDUs = int(20000/336) = 59
CAT5 theoretical rate (RLC payload rate) = (RLC payload size * Number of TBs)/TTI
RLC SDU size = MAC-d PDU - MAC header - RLC header = 16 bits
If the MAC-d PDU size is 336 bits, the CAT5 theoretical rate is 59 * 320/10 = 1.888 Mbit/s
The MAC SDU rate monitored on the LMT is: int(20000/336) * 336/10 = 1.9824 Mbit/s.
The maximum throughput at the application layer ≈ the RLC payload rate/(1 + 1% of HARQ retransmission)
= 1.87 Mbit/s
CAT6 （ SRB OVER E-DCH ）：
Throughput at the physical layer: (3840000/2) * 2 (SF2) + (3840000/4) * 2 (SF4) = 5.76 Mbit/s
Data rate at the MAC-e layer: Maximum TBS at the MAC-e layer * 1000/2 ms => 11484 * 1000/2 = 5.742
Mbit/s
If the MAC-d PDU size is 336 bits, the CAT6 theoretical rate is 34 * 320/2 = 5.44 Mbit/s.
The maximum throughput at the application layer ≈ the RLC payload rate/(1 + 10% of HARQ
retransmission) = 4.945 Mbit/s
Layers
CAT6 （ SRB OVER DCH ）：
Throughput at the physical layer: (3840000/2) * 2 (SF2) = 3.84 Mbit/s

Data rate at the MAC-e layer: Maximum TBS at the MAC-e layer * 1000/2 ms => 5772 * 1000/2 = 2.886
Mbit/s
If the MAC-d PDU size is 336 bits, the CAT6 theoretical rate is 17 * 320/2 = 2.72 Mbit/s.
The maximum throughput at the application layer ≈the RLC payload rate/(1 + 10% of HARQ retransmission)
= 2.473 Mbit/s

Process of Identifying Stationary Test-Based
HSUPA Problems Identify stationary test-based HSUPA
Dial-up succeeds while data N

transmission fails
Y
3.2.1
Identify data
transmission failure
Y
Is data transmission OK?
N
3.2.4
Check and
clear alarms
3.4.1
Y Check the minSF during the link
setup or re-configuration
N
3.4.2 3.4.3 3.4.4 3.4.5 3.4.7 END
Check the Check the
Check UE Check cell Check RAN
Assigned rate DCCC
capabilities capabilities parameters
of the CN algorithm
Y
Is the problem solved?
N
3.4.8
Y
Is UE traffic volume
restricted
N
3.4.8 3.4.8
Check the TCP layer 3.4.7
Check the RLC
and higher layers N
layer Is the UE transmission
power restricted
Y Is the problem
Replace the UE or driver Y
caused by UE 3.4.7
N Check UE location and outloop
power control
Is the
Modify the laptop setting Y
problem caused by Y
or replace the laptop
laptop Is the problem solved?
N
N
Contact CN engineers
Is the problem
to locate the fault, which Y
caused by server or
must be supported by
CN
the RAN
N
Y
Is the fault rectified
N
3.4.9 3.4.10 3.4.11

Check uplink load Check uplink CE
Check Iub resources
resources resources
N
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential
Is the problem solved? Page 37
3.2.19
Y Collect data and report
Process of Identifying DT Test-Based HSUPA Data
Transmission Problems Identify DT test-based HSUPA
Perform stationary test of Identify stationary

Y test-based data
data transmission on a near point, check whether any
problem exists transmission faults
N
3.2.4 3.4.3 3.4.12 3.4.10 3.4.11 3.4.9

Check and clear Check the handover Check uplink CE Check Iub Check uplink
Check cell
alarms, especially, strategies and resources on resources on each load resources
capabilities
cell-level alarms parameters each NodeB NodeB on each cell
Perform DT in idle
period (with few
online users)
Does call
Y Handle with the
drop or handover failure (or
problem
not in time) exist
Does abnormality Y Handle with the

exist (with high RSCP but low problem
throughput)
N
N
Is the problem solved?
Y
Optimize the RF
coverage
Y
Is the problem solved? END
3.2.19
Collect data and report
problems

Process of Identifying Performance
Measurement-Based HSUPA Data Transmission
Problems Evaluation item Identify HSUPA cell
performance problems
Y
The item cannot be
evaluated at present. Does the average
END N single-user throughput reach
the cell requirement?
Are data sources Is the UE in the

Y
insufficient? Unhappy state?
Is the RTWP limited? Y Is the uplink load limited?
N
Perform expansion,
use dynamic CEs, and Y Are CE resources limited?
optimize the GBR
The power control

of the control Is MultiACk N
Y Y
channel or UE is abnormal?
abnormal. N
N
Is the BLER on the
Power control air interface high?
parameters are
incorrect.
Y
N
Out-loop power control Is the residual
Y
problems BLER high? Is the RLC
retransmission ratio
N high?
The uplink RTWP is

high or the UE is far Is the transmit
Y power of the UE
away from the cell
center. limited? N
Is the Iub
Optimize the
Y transmission quality
transmission quality
poor?
Expand the Iub Are Iub
N transmission Y resources
bandwidth limited?
Other
HUAWEI TECHNOLOGIES CO., LTD. problems
Huawei Differential
ConfidentialOthers Page 39
causes
Process of Identifying Performance Measurement-
Based HSUPA Data Transmission Problems
Step Evaluation Item Evaluation Result and Handling Suggestion
Yes No
(1) Whether the UE is in the Happy state Data sources are insufficient. Go to step (2).
(2) Whether the uplink load is limited The RTWP is limited. Go to step (3).
(3) Whether CE resources are limited Add CEs, enable the dynamic CE feature, and Go to step (4).
optimize the GBR.
(4) Whether the BLER of the air interface is high Check whether MultiACK is abnormal. Go to step (5).
Yes: Check whether the power control of the control
channel or the UE is abnormal.
No: Check whether power control parameters are
correct.
(5) Check whether the RLC retransmission ratio is high Perform the following operations based on the Go to step (6).
residual BLER:
If the residual BLER is high, out-loop power control
is abnormal.
If the residual BLER is not high, check whether the
transmit power of the UE is limited. If yes, the
uplink RTWP is high or the UE is far away from
the cell center. If no, check the quality of Iub
transmission. If the quality of Iub transmission is
poor, optimize the transmission quality.
(6) Whether Iub resources are limited Expand the Iub transmission bandwidth. Check whether
other problems
occur.

Thank you
www.huawei.com
Basic Concepts—calculated of Theoretical Rates
Probe:
Scheduled rate = Total size of all TBs received by the MAC-hs layer within a measurement period/Total
duration for scheduling TBs within a measurement period
The total size of all TBs received at the MAC-hs layer within a measurement period: involves the TBs that are
correctly and incorrectly received.
Total duration for scheduling TBs within a measurement period: includes only the time when TBs are received.
For example, within a measurement period of 100 subframes (200 ms), if only 50 subframes contain data, the
duration for receiving TBs with data within a measurement period is 100 ms.
Served rate = Total size of all TBs received by the MAC-hs layer within a measurement period/Measurement
period
Total size of all TBs received at the MAC-hs layer within a measurement period involves the TBs that are
correctly and incorrectly received.
Measurement period indicates all the time when TBs are received and not received.
The relationship between the served rate and the scheduled rate is as follows:
Served Rate = Scheduled Rate * HS - SCCH success rate
HS-SCCH success rate = Total duration for receiving TBs within a measurement period /Measurement period.
The HS-SCCH success rate indicates the scheduling probability.
MAC layer rate = Total size of TBs correctly received at the MAC-hs layer within a measurement
period/Measurement period
Total size of TBs correctly received at the MAC-hs layer within a measurement period only involves the TBs that
are correctly received.
Measurement period indicates all the time when TBs are received and not received.
The relationship between the MAC layer rate and the served rate is as follows:
MAC layer rate = Served rate * (1 - SBLER)
SBLER = Total size of TBs incorrectly received within a measurement period/Total size of all TBs received within
a measurement period. The SBLER indicates the BLER of TBs.
To reflect user experience more approximately, the rate at the MAC layer is usually used.

Basic Concepts——calculated of Theoretical
Rates
Probe
MAC-e PDU non-DTX rate = Total size of all TBs during non-DTXs/(Number of non-DTXs * TTI)
Measurement period: The measurement period for a single log packet is 20 TTIs.
The MAC-e PDU non-DTX rate is the actual MAC-e rate excluding the TB transmission during DTXs but including
TB retransmission ；
Total size of all TBs during non-DTXs involves the TBs that are initially transmitted and retransmitted.
"Number of non-DTXs * TTI" indicates only the duration in which TBs are transmitted. For example, within a
measurement period of 100 subframes (200 ms), if only 50 subframes contain data, the "number of non-DTXs *
TTI" is 100 ms.
MAC-e PDU served rate = Total size of all TBs during non-DTXs/(NUM_SAMPLES * TTI)
The MAC-e PDU served rate is the MAC-e service rate including the TB transmission during DTXs and TB
retransmission.
Total size of all TBs during non-DTXs involves the TBs that are initially transmitted and retransmitted.
NUM_SAMPLES * TTI indicates duration in which TBs are transmitted and not transmitted. For example, within a
measurement period with 100 subframes (200 ms), if only 50 subframes contain data. However, the
"NUM_SAMPLES * TTI" is still 200 ms.
The relationship between the MAC-e PDU served rate and the MAC-e PUD non-DTX rate is as follows:
Served rate = MAC-e PDU non-DTX rate * Non-DTX probability
Non-DTX probability = Number of non-DTXs/NUM_SAMPLES * 100%
MAC-e PDU available rate = Total size of all TBs during non-DTXs and when COMB_HIGH is ACK and
ACK_NS/(NUM_SAMPLES * TTI)
Total size of all TBs during non-DTXs and when COMB_HIGH is ACK and ACK_NS" involves only the TBs that are
correctly transmitted.
NUM_SAMPLES * TTI indicates all the time whether data is transmitted or not.
The relationship between the MAC-e PDU available rate and the MAC-e PUD served rate is as follows:
MAC-e PDU available rate ≈"MAC-e PDU served rate" * (1 - SBLER)
SBLER = (Number of non-DTXs – Number of ACKs or ACK_NSs)/Number of non-DTXs * 100%

Transmission Data Checks

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Transmission Data Checks

Uploaded by

Copyright:

Available Formats

05/12/2020 Security Level:

HSPA Data Transmission

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HSDPA Basic Concepts and Process of Identifying

HSUPA Basic Concepts and Process of Identifying

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

PDCP Packet Data Convergence Protocol

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

(s)RBs for UE1 (s)RBs for UE2 PDU structure

RLC RLC RLC RLC RLC RLC RLC Payload

MAC-d MAC-d RLC Payload

MAC-c U-RNTI RLC Payload

Iub-FP Iub-FP Iub-FP

MAC-ehs MAC-ehs U-RNTI RLC Payload

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

CQI formula (for the HSDPA excluding 64QAM) :

CQI = CPICH Ec/No + MPO + 10 * log16 + 4.5

MPO = min(13, Pcell-Pcpich - MPO constant) dB The MPO constant is 2.5 by

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

NodeB: Enable or disable the NodeB dynamic code function.

We will introduce different combinations of the two algorithms. The number of

• Manually assign five codes on the RNC

• Enable the dynamic codes on the NodeB:

• Automatically assign a maximum of ten codes and a minimum of five codes

• Disable the dynamic does on the NodeB:

• Enable the dynamic does on the NodeB:

• RNC automatic assignment + NodeB dynamic code disabled is

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

Default configuration for codes

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

Generally, the RLC SDU size configured on the network is small :

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

64QAM, MIMO, 64QAM+MIMO, and DC+64QAM technologies are introduced

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

The maximum RLC PDU is set to

• The variable PDU size of downlink AM is introduced at the RLC layer.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

• PDCP layer: Data transmission is considered as transparent transmission

• MAC-d layer: Data transmission is considered as transparent transmission

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

2) At the RLC layer (EL2) :

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

Downlink Throughput Displayed in DU Meter (monitor TCP IP throughout)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

• The 1st BLER is called initial BLER (IBLER).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

Dial-up succeeds while

Perform static test of Y Handle with the

3.2.4 3.2.5 3.2.7 3.2.10 3.2.11 3.2.14

Does call Y Handle with the

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

Optimize the Is the CQI Is the power

Perform Are there N

Perform Iub Is the Iub

Check power Is the residual

Perform Is the code usage

Global or upper- Is upper-layer Does the theoretical cell rate

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23

HSDPA Basic Concepts and Process of Identifying

HSUPA Basic Concepts and Process of Identifying