Beruflich Dokumente
Kultur Dokumente
Peak Throughput
Bandwidth (Mbit/s)
The table on the right describes the ratio of throughput to Signal-to-Noise Ratio (SNR) on a fading
channel for Cat 5 UE at the bandwidth of 20 MHz in a single cell in a lab test. The baseline varies
between different UEs for about 5%. The number of radio blocks (RBs) increases and reduces
based on the bandwidth. The comparison is based on the maximum capabilities of different
category UEs.
E-1: LTE-S indicates that tracing items can be selected from the drop-down menu. E-2: CINR0 and CINR1
indicates the SINRs of two antenna ports.
E-3: Tx-Power indicates the current TX power of the UE. E-4: displays the BLERs of the UL and DL
channels. average number of RBs, and MCS order within the measurement period.
E-5: RSRP indicates the signal level received at the two antenna ports.
M2000: cell
performance
monitoring
and user
performance
monitoring
Choose Monitor > Signaling Trace > Signaling Trace Management > Cell Performance
Monitoring on the M2000 to query the RB utilization ratio, total throughput, cell interference
monitoring data, and number of UEs.
Choose Monitor > Signaling Trace > Signaling Trace Management > User Performance
Monitoring on the M2000 to query the power headroom, channel quality, throughput, and MCS
count number, and BLER.
IFTS tracing
can trace TTI-
level data.
Determining a TCP Fault or a Non-TCP Fault
Determining a TCP Fault or a Non-TCP Fault
UE subscription rate The UE subscription rate can be viewed by performing S1 tracing or be observed on the UE side. Alternatively,
the UE subscription rate can be queried on the home subscriber server (HSS).
Query the UE capability by viewing the UE capability message. Generally, commercial UEs support category 2
UE capability and category 3. Huawei test UEs support category 4 and category 5. UEs of different categories support
different UL and DL throughput.
Individual factor of the UE Use other UEs of the same brand; use UEs of a different brand for test
Antenna of the UE If external antennas are used, you are advised to place two antennas vertically at a proper interval. If built-in
antennas are used, adjust the angle and location of the UE.
eNodeB alarm If an alarm is generated, try to clear it. If the alarm does not have clearance conditions, analyze whether the
alarm affects the throughput.
Whether multiple UEs are
Use the cell performance monitoring function of the eNodeB to check whether a cell has multiple UEs.
in the cell
Whether the throughput is The license certificate may restrict the total cell throughput and therefore the throughput is low. Run DSP
restricted by the license LICENSE to check the license status of the eNodeB.
The LTE system provides larger throughput and therefore requires servers and laptops with better
performance. During UL packet injection, a laptop needs to connect to the power supply to prevent packet
Performance check on the injection failures caused by insufficient power.
server and the laptop If there is no valid judgment method, replace a server or laptop to test for comparison. You are advised to use
a high-end ThinkPad T400 series laptop with a dual-core CPU of 2.0 GHz or above, a hard disk of 7200 RPM,
Gigabit network ports, and the operating system of windows XP SP3.
Compatibility of the Some laptops encounter faults in installing windows 7 and the Iperf tool in an outdoor test. The problem is
solved after the Gperf tool is used. Inject 1000-byte packets in the test for comparison. Replace the FTP
packet injection tool
download tool with the recommended Filezilla.
Check whether the UL CL Check whether the corresponding switch of the eNodeB is turned on, whether the UE supports the UL CL
power control. Huawei UEs support the UL CL power control. For Samsung UEs, JL1 and JI1 cannot work in
power control is valid.
CL power control mode but the JF1+Patch can.
eNodeB parameter check For details about specific operations of eNodeB parameter check, see LTE Parameter Check Manual.
GBR
AMBR
Unit: bit/s
Determining a TCP Fault or a Non-TCP Fault
Determining a TCP Fault or a Non-TCP Fault
b. Use the TCP parameter setting.reg tool to modify parameters on the transmitting side and
import the parameters. After completing the preceding two operations, restart the PC to
activate the modified configurations. If the parameters cannot be modified on the server,
modify the configurations only on the PC connecting to the UE.
Note: The TCP fault location module is designed to have the PDCP module record the number of Dup-ACK
messages for determining packet loss or out-of-order packets, and then determine in which segment the
packet loss occurs by checking whether the PDCP module continuously receives the Dup_ACK packet
numbers.
1. On point A, capture only the 100 bytes of the packet head to save the file size and name the captured result as follows:
Site name_UEPC.pcap
2. If the gateway is deployed on the network, configure the IPSec channel as empty encryption and capture a complete
packet on point B for the purpose of properly decrypting the data. At the same time, save captured data in multiple files to
prevent a single file from occupying too much memory space. If there is no IPSec configuration, you are advised to
capture only the 150 bytes of the packet head. The captured data on point B is named as follows: Site name_eNB.pcap
3. Capture only the 150 bytes of the packet head on point C and name the captured data as follows: Site name
_UGW.pcap.
4. Capture only the 100 bytes of the packet head on point D and name the captured data as follows: Site
name_Server.pcap.
5. Configure packet capture on each point by using the Wireshark and then start data transmission. Several seconds later,
stop packet capture.
Simple analysis process:
1. Check whether packet loss occurs on point A based on the condition of "tcp.analysis.duplicate_ack_num >= 2". If packet
loss occurs, find the faulty point and compare the captured data with that captured on point B and then check the fault
based on segments.
2. Check whether a window shrinks on point A based on the condition of "tcp.window_size <1000". Compare the occurrence
time of window shrinking with that displayed in the IO Graphs of the Wireshark. If the occurrence time is consistent, the
performance of the PC connecting to the UE cannot meet requirements.
Determining a TCP Fault or a Non-TCP Fault
The number of The number of The MCS order The IBLER is The DL MIMO
scheduling times RBs is is low. abnormally mode is abnormal.
is insufficient. insufficient. diverged.
(2/3)
The number of RBs is insufficient.
On DL, the UE capability is not restricted and all RBs are scheduled.
on UL, if the CL power control is enabled with a path loss exceeding 120 dB to 125 dB, the UL
RBs to be scheduled starts to decrease and the MCS order ranges from order 3 to order 5. If the
path loss is less than 120 dB, all the RBs are scheduled. (All RBs Total number of RBs
Number of PUCCH RBs; the calculation result must meet rule 2-3-5. Rule 2-3-5 means that the
number of RBs for a single UE must be a multiple of 2, 3, or 5.
(3/3)
How to Identify an Excessively High BER
In a peak-throughput area, the BER must be 0 or smaller.
In a non-peak-throughput area, a BER of 10% is normal. If the BER is higher than 10%, it is
abnormal.
If the MCS is at order 0, a high BER can also be considered to be normal.
How to Identify a Low MCS Order
It is difficult to determine whether the MCS order is correct when the distance is moving towards a
remote point away from the cell center. When the path loss exceeds 120 dB to 125 dB and the
number of RBs decreases, the MCS order generally remains at orders 3 to 5. When the number
of RBs reaches the minimum, the MCS order may drop. You can use a simple way to identify a
low MCS order. That is, when the UE performs transmission at a full power of 23 dBm, if the
number of scheduling times and number of RBs are normal but the total throughput is low, the
MCS order is too low.
Main and
diversity Main and
RSRPs of a diversity RSRPs
Huawei UE of a Samsung
on the Probe UE on the X-Cal
Solution:
Laboratory test:
(1) Modify the network to make the main and diversity
antennas connected separately.
(2) Cables in the VAM must also be connected
separately.
(3) Check interference in the laboratory. If the
interference is stronger than the signal, the TX and RX
signal correlation becomes high.
Outdoor test:
(1) In a scenario with line of sight, the correlation is
high. Avoid an area with line of sight.
(2) If external antennas are used, enlarge the interval
between two antennas or place the two antennas
vertically.
Description:
(1) Check whether there are multiple cells displayed in the
Detected Cell area on the M2000 and the difference between the
RSRP of more than one cell and that of the serving cell is within 3
dB. If the difference is within 3 dB, strong interference is received
from neighboring cells.
(2) The physical cell identifier (PCI) of a neighboring cell contained
in the detected cells cannot be the same as that of the serving
cell.
(3) Check whether the Channel Quality Indicator (CQI) of the DL
subband is excessively low in a segment. If the CQI is excessively
low in a segment, DL transmission encounters severe narrowband
interference.
(4) Estimate the difference between RSRP and SNR. If the
difference is greater than 115 dBm, strong interference is
received.
Solution:
(1) Strong interference from neighboring cells can be reduced by
adjusting the direction of the antenna.
(2) Severe narrowband interference can be eliminated by
removing interference sources detected in spectrum scanning. For
details about interference check and elimination, see LTE RF
Channel Manual.
(2) The UE receiving power generally ranges from -50 dBm to 90 dB. A receiving power greater
than -50 dBm possibly results in wave clipping and then leads to a low DL SNR. A receiving power
lower than -90 dBm may lead to a low DL SNR, affecting the DL transmission performance.
Observe the UE receiving power with the following methods:
In a lab test, the path loss can be adjusted to
resolve the problem.
In an outdoor test, you can adjust the interval
between sites and the power ratio of the eNodeB.
This problem must be reported to Huawei
headquarters for analysis and optimization.
Determining a TCP Fault or a Non-TCP Fault
c. Select a network adapter and then set the packet length. Capture of 100-byte packets is recommended on the
UE and the server sides while capture of 200-byte packets on the S1 transmission side.
d. Click Start to start packet capture. Press Ctrl E or click the stop button on the tool bar to stop the packet
capture.
e. Press Ctrl S or choose File > Save in the menu to save the packet capture data.
TTI tracing: Currently, the TTI tracing targets the first UE accessing the cell after the eNodeB is started. Therefore,
you need to start TTI tracing before the UE accesses the cell and uses services. If mass data is obtained in
TTI tracing, use the corresponding tool to process the data before sending the data to Huawei Headquarters.
Step 2. Fill in
the trace
name.
Table 2
Table 1
This slide takes octet3, octet5, and octet7 as examples. The UL and DL conversion method is the same.
The AMBR conversion must follow the following rules:
1. When octet5 is 0 and octet7 is 0, see the value of octet3. For the conversion formula, see table 2.
2. When octet7 is 0 and octet5 is not 0, see the final converted values of octet3 and octet5. For the
conversion formula, see table 2.
3. When octet7 is not 0, see the value of octet7. For the conversion formula, see table 2.