Transcript
8/13/2019 Iub Investigation
1/32
1.1.1 Iub bandwidth ofinvestigation,
an the task description
according toto check the transmission Configure Iub interface specification, the overall principle is to
provide enough Iub bandwidth.2,inputs,
No
3 tools
RNC LMT and NodeB LMT
4,steps
ifare ATM
Bandwidth: Step1:implementation of DSP E1T1 the RNC LMT, check the number of E1 NodeB
available correspondence, and then estimate the available bandwidth of the physical (one pair E1 can
provide a rate of about 0.75 ~ 0.8Mbps), If not, the need to increase E1;Step2: Executive LST AAL2PATH (if it is carrying the optical port) or LST IMAGRP (if it is carried in
the form of IMA Group) at the RNC LMT, the corresponding query NodeB traffic using the index; then
perform LST ATMTRF, check the configuration of the average rate (SCR), the need is greater than the
testing requirements, if not met, need to be modified;
Step3: receiving a query execution LST AAL2PATH cell rate (RCR) in the NodeB LMT requiring RCR
configuration
8/13/2019 Iub Investigation
2/32
I) according to NODET = IUPS keywords to find IU-PS segments adjacent points in the MML, if
there are multiple IU-PS, one by one check.
1 Find IU-PS neighborsII) Find carry PATH IU-PS according to neighbors (generally IU-PS are carryingover RXBW
8/13/2019 Iub Investigation
3/32
2 Find IU-PS bearer PATHIII) examination carries PATH bandwidth (TXBW of downstream bandwidthIP),as upstream
bandwidth, unit Kbit / s), the configuration recommended configuration is consistent with the
bandwidth of the physical abilities, such as the 100M Ethernet port bandwidth recommended
configuration for the 100M, 1000M Ethernet port is also assigned to at least 300M or more (assuming
the maximum throughput capacity of the cell To XiM, linked to the ability to lower the number of RNC
cell Xi is Ni, then the bandwidth interface configuration IuPS least as X1 * N1 + X2 * N2 + ...).
1.1.3 Iub mouth droppinginvestigation,
an the task description
to check the Iub interface (including RNC transmission interface board, NodeB transmission interface
board, Iub oral transmission) there is no packet loss.
2, the input
port Iub loss is certainly a phenomenon manifested rate fluctuations (volatility generally very intense),
if the rate is very stable, you can skip this task.
3, the tool
RNC UMAT
LMT,4,steps
Step1: make the user data transmission process CDT RNC user tracking, measuring modes and L2
election increases the number of reported mass, as shown below. In steady-state tracking data
transmission few minutes (3-5 minutes), otherwise it will have a significant amount of data.
8/13/2019 Iub Investigation
4/32
3 RNC CDT track the number of users passingStep2:
A method for determining loss: Iub mouth if there is packet loss (including the RNC, NodeB Iub
interface board packet loss and transmission loss), will be the performance of RLC layer retransmission
rate. Can be opened with UMAT Step1 tracking data, according to the operation shown below were
observed, corresponding indicators RB.UsDlRetranRate. The method can also refer to FIG 13 shows, the
check downlink RLC retransmission rate.
8/13/2019 Iub Investigation
5/32
4 View downlink RLC retransmission ratein general, not limited by the bandwidth of the Iub or Iub bandwidth is limited when it opened the flow
control, RLC retransmission rate should be close to zero. If the retransmission rate is higher, indicating
possible loss of the Iub interface, you need to troubleshoot Iub interface.
Two methods to determine packet loss: L2 CDT details will track the use of UMAT convert
Winshark can view the TCP packet (see below).
8/13/2019 Iub Investigation
6/32
5 The CDT tracked L2 detailed information into TCP packetretransmission packet loss will have a general loss will have a lot of repetition (> = 5) of the ACK,
therefore, according to the serial number of duplicate ACK to the front to find the serial number. If you
have not received the packet sequence number, indicating loss over the capture position, if the number
received the previous packet, indicating loss below the capture location.
The figure below is an example (using WireShark open), a large number of duplicate ACK
Description 13241193 packets lost. Ethereal packet loss appears at the top position (ie IU-PS mouth
dropping) appeared packet loss (because from capture to see the red part of the analysis tools to see, do
not receive the packet sequence number 13241193); conversely if it is There are dropping below the
capture location (possibly Iub mouth dropping, the capture location RNC), then we can look forward to
find the number of packets.
If packet loss is detected IU-PS, on the need to troubleshoot IP interface port mode configuration:generally required to use the full-duplex mode. RNC side Ethernet interface board verifiable command
DSP ETHPORT, or if it is half-duplex auto-negotiation may cause transmission loss. If the modification or
the IU-PS packet loss is detected, the reference 3.2.17.
If found RNC RNC MAC layer packet capture packets received, but the message is still lost, you
need to troubleshoot if there is packet loss Iub interface.
8/13/2019 Iub Investigation
7/32
6 TCP packet lossdetermine
8/13/2019 Iub Investigation
8/32
is detected toif there is packet loss, thenthe
if Iub IP transmission is the first work to check the Ethernet link between the RNC and NodeB
whether full-duplex: RNC and NodeB side were executed in the DSP ETHPORT, double check whether
workers are full-duplex mode, and if not, recommendations are configured for full duplex. (If there are
other intermediate routing devices, you also need to check the port duplex mode corresponding device)
does not solve the problem of RLC retransmission rate downward if configured for full duplex
transmission or if the ATM is usually described Iub transport port itself poor quality, there is a loss, you
need to focus on the investigation Iub mouth transmission quality. Iub transmission quality to determine if
the mouth is no problem, skip 3.2.17 feedback problems.
Note: Iub mouth packet loss, get rid of the problem duplex mode configuration, the general population in Iub
transmission loss as much, and therefore need to be on-site investigation to solve the transmission quality. If there is
no packet loss Iub transport, you need to research the feedback problem troubleshooting interface board is abnormal
cause packet loss. Iub interface transmission quality investigation, refer to the attached document "ATM transmission
QOS issues positioning guide book V1.5.doc" and "RAN12 IP QoS transmission troubleshooting guide book-
20101208-V1.0.doc".
8/13/2019 Iub Investigation
9/32
1.1.4 Iub mouth droppinginvestigation,
an the task description
to check the Iub interface (including RNC transmission interface board, NodeB transmission interface
board, Iub oral transmission) there is no packet loss.
2, the input
port Iub loss is certainly a phenomenon manifested rate fluctuations (volatility generally very intense),
if the rate is very stable, you can skip this task.
3, the tool
RNC UMAT
LMT,4,steps
Step1: make the user data transmission process CDT RNC user tracking, measuring modes and L2
election increases the number of reported mass, as shown below. In steady-state tracking data
transmission few minutes (3-5 minutes), otherwise it will have a significant amount of data.
8/13/2019 Iub Investigation
10/32
7 RNC CDT track the number of users passingStep2:
A method for determining loss: Iub mouth if there is packet loss (including the RNC, NodeB Iub
interface board packet loss and transmission loss), will be the performance of RLC layer retransmission
rate. Can be opened with UMAT Step1 tracking data, according to the operation shown below were
observed, corresponding indicators RB.UsDlRetranRate. The method can also refer to FIG 13 shows, the
check downlink RLC retransmission rate.
8/13/2019 Iub Investigation
11/32
8 View downlink RLC retransmission ratein general, not limited by the bandwidth of the Iub or Iub bandwidth is limited when it opened the flow
control, RLC retransmission rate should be close to zero. If the retransmission rate is higher, indicating
possible loss of the Iub interface, you need to troubleshoot Iub interface.
Two methods to determine packet loss: L2 CDT details will track the use of UMAT convert
Winshark can view the TCP packet (see below).
8/13/2019 Iub Investigation
12/32
9 The CDT tracked L2 detailed information into TCP packetretransmission packet loss will have a general loss will have a lot of repetition (> = 5) of the ACK,
therefore, according to the serial number of duplicate ACK to the front to find the serial number. If you
have not received the packet sequence number, indicating loss over the capture position, if the number
received the previous packet, indicating loss below the capture location.
The figure below is an example (using WireShark open), a large number of duplicate ACK
Description 13241193 packets lost. Ethereal packet loss appears at the top position (ie IU-PS mouth
dropping) appeared packet loss (because from capture to see the red part of the analysis tools to see, do
not receive the packet sequence number 13241193); conversely if it is There are dropping below the
capture location (possibly Iub mouth dropping, the capture location RNC), then we can look forward to
find the number of packets.
If packet loss is detected IU-PS, on the need to troubleshoot IP interface port mode configuration:generally required to use the full-duplex mode. RNC side Ethernet interface board verifiable command
DSP ETHPORT, or if it is half-duplex auto-negotiation may cause transmission loss. If the modification or
the IU-PS packet loss is detected, the reference 3.2.17.
If found RNC RNC MAC layer packet capture packets received, but the message is still lost, you
need to troubleshoot if there is packet loss Iub interface.
8/13/2019 Iub Investigation
13/32
10 TCP packet lossdetermine
8/13/2019 Iub Investigation
14/32
is detected toif there is packet loss, thenthe
if Iub IP transmission is the first work to check the Ethernet link between the RNC and NodeB
whether full-duplex: RNC and NodeB side were executed in the DSP ETHPORT, double check whether
workers are full-duplex mode, and if not, recommendations are configured for full duplex. (If there are
other intermediate routing devices, you also need to check the port duplex mode corresponding device)
does not solve the problem of RLC retransmission rate downward if configured for full duplex
transmission or if the ATM is usually described Iub transport port itself poor quality, there is a loss, you
need to focus on the investigation Iub mouth transmission quality. Iub transmission quality to determine if
the mouth is no problem, skip 3.2.17 feedback problems.
Note: Iub mouth packet loss, get rid of the problem duplex mode configuration, the general population in Iub
transmission loss as much, and therefore need to be on-site investigation to solve the transmission quality. If there is
no packet loss Iub transport, you need to research the feedback problem troubleshooting interface board is abnormal
cause packet loss. Iub interface transmission quality investigation, refer to the attached document "ATM transmission
QOS issues positioning guide book V1.5.doc" and "RAN12 IP QoS transmission troubleshooting guide book-
20101208-V1.0.doc".
8/13/2019 Iub Investigation
15/32
1.1.5 Assessed in accordance with the port bandwidth utilization IUB
1, task descriptions
investigation IUB interface transfer bandwidth-limited question
2, enter
the configuration file RNC, NodeB, then the system, RNC, then the system
3, tools
Nastar
4, steps
STEP1. to assess IUB Interface ATM / IP port bandwidth . utilization
1) In carrying ATM transmission mode, using the following counter: VS.ATMDlTotal.1
VS.ATMDlTotal.2 VS.ATMDlTotal.3 VS.ATMDlTotal.4 VS.ATMDlAvgUsed.1 VS.ATMDlAvgUsed.2
VS.ATMDlAvgUsed
NodeB
VS.ATMDlAvgUsed.4
.3
utilization calculation port 1 (ATM1_Used_Ratio): VS.ATMDlAvgUsed.1 / VS.ATMDlTotal.1
port 2 utilization (ATM2_Used_Ratio): VS.ATMDlAvgUsed.2 / VS.ATMDlTotal.2
utilization of port 3 (ATM3_Used_Ratio): VS.ATMDlAvgUsed.3 / VS.ATMDlTotal.3
4 port utilization VS.ATMDlAvgUsed.4 / VS.ATMDlTotal.4
(ATM4_Used_Ratio):2)in the IP transport bearer mode, use the following NodeB counter:
VS. VS.IPDlTotal.2 VS.IPDlTotal.3 VS.IPDlTotal.4 VS.IPDlAvgUsed.1 VS.IPDlAvgUsed.2
VS.IPDlAvgUsed.3 VS.IPDlAvgUsed.4
IPDlTotal.1
8/13/2019 Iub Investigation
16/32
utilization calculation port 1 (IP1_Used_Ratio): VS.IPDlAvgUsed .1 / VS.IPDlTotal.1
port 2 utilization (IP2_Used_Ratio): VS.IPDlAvgUsed.2 / VS.IPDlTotal.2
port 3 utilization (IP3_Used_Ratio): VS.IPDlAvgUsed.3 / VS.IPDlTotal.3
utilization of port 4 (IP4_Used_Ratio): VS.IPDlAvgUsed.4 / VS.IPDlTotal.4
expansion port bandwidth utilization threshold and expansion threshold IUB samethreshold70%Y..
STEP2. basebyto meet the conditions, output the positioning table IUB Tran limit SUMMARY column
output Other empty
optimization methods:
1) expansion IUB transmission bearer network transmission bandwidth expansion IUB interface physical
bandwidth.
2) expansion IUB interface transfer configuration bandwidth.
In the IUB interface to the ATM transmission bearer mode, the transmission bandwidth expansion byADD ATMTRF configure and use the MOD AAL2PATH the original AAL2PATH in TX traffic record
index, RX traffic record index index was revised to flow after the expansion of bandwidth. As shown
below:
If you need to increase the number of PATH, directly ADD AAL2PATH expansion, as follows:
8/13/2019 Iub Investigation
17/32
In the IUB interface IP transport bearer mode transport configuration by MOD IPPATH expansion of
bandwidth, or use the ADD IPPATH expansion of the number of PATH.
1.1.6 Quality assessment oftransmission
abandwidth,task description
transmission qualitytroubleshoot problems
2, enter
the configuration file RNC, NodeB, then the system, RNC, then the system
3, tools
Nastar
4,steps
STEP1. using the followingNodeB counter, perform frame loss rate statistics
VS.IUB.FlowCtrol. VS.IUB.FlowCtrol.DL.DropNum.LgcPort2
VS.IUB.FlowCtrol.DL.ReceiveNum.LgcPort1VS.IUB.FlowCtrol.DL.ReceiveNum.LgcPort2
DL.DropNum.LgcPort1
NodeBNodeB
port a frame loss rate (transport1 drop ratio)VS.IUB.FlowCtrol.DL.DropNum.LgcPort1VS.IUB.FlowCtrol.DL.ReceiveNum.LgcPort1
=/NodeB
port 2 frame loss rate drop ratio) = VS.IUB.FlowCtrol.DL.DropNum.LgcPort2
(transport2/ VS. IUB.FlowCtrol.DL.ReceiveNum.LgcPort2 NodeB
STEP2. transmission delay statistics for each port
8/13/2019 Iub Investigation
18/32
port a delay mean (transport1 delay): VS.IUB.FlowCtrol.DL.DelayVara.LgcPort1.Avg NodeB
port 2 delay mean (transport2 delay): VS.IUB.FlowCtrol.DL.DelayVara.LgcPort2.Avg
next few counter first presented as a 50332728 VS.IUB.FlowCtrol.DL.Delay.UpBW.Num.LgcPort1
reference:NodeB IUB logical ports available bandwidth based on a downlink HSDPA increase the number
of times the bandwidth delay50332753 VS.IUB.FlowCtrol.DL.Delay.UpBW.Num.LgcPort2 NodeB IUB HSDPA downlink logical port
2 increases the number of available bandwidth based on the bandwidth delay
50332729 VS.IUB.FlowCtrol.DL.Drop.UpBW . Num.LgcPort1 NodeB IUB logical port 1 HSDPA
downlink bandwidth available bandwidth based on packet loss increases the number
50332754 VS.IUB.FlowCtrol.DL.Drop.UpBW.Num.LgcPort2 NodeB IUB logical port 2 HSDPA
downlink bandwidth available bandwidth based on packet loss increase the number
50332731 VS.IUB.FlowCtrol.DL.DelayCong.DownBWNum.LgcPort1 NodeB IUB logical port 1 HSDPA
downlink bandwidth is reduced based on the number of available bandwidth delay
50332756 VS.IUB.FlowCtrol.DL.DelayCong.DownBWNum.LgcPort2 NodeB IUB logical port 2 HSDPA
downlink bandwidth is reduced based on the number of available bandwidth delay
50332733 VS.IUB.FlowCtrol.DL.DropCong.DownBWNum.LgcPort1 NodeB IUB logical port 1 HSDPA
downlink bandwidth available bandwidth based on packet loss down the number
50332758 VS.IUB.FlowCtrol.DL . DropCong.DownBWNum.LgcPort2 NodeB IUB logical port 2 HSDPA
downlink bandwidth available bandwidth based on packet loss down the number
50332745 VS.IUB.FlowCtrol.DL.CongTime.LgcPort1 NodeB IUB logical port congestion time a
downlink HSDPA
50332770 VS.IUB.FlowCtrol. DL.CongTime.LgcPort2 NodeB IUB logical port 2 HSDPA downlink
congestion time
STEP3. IUB interfaces according to the following criteria to evaluate the transmission
1 When the frame loss rate is greater than or equal to 5% is considered frame loss rate, the transmission
quality is relatively poor
quality:2 when transmission delay parameter greater than or equal SET HSDPAFLOWCTRLPARA TD,
default 5% is considered high latency, poor transmission quality Note: The default value is 4, the unit is
5ms, which is 20ms (to not implement this ruling, only. output as a reference, Shanghai Unicom verified
as most of the stronghold of 740ms, the need for further appropriate more game point data)
will meet the conditions of the base station, the base station will be following all the cells in the output
table positioning conclusion IUB Tran quality limit other column output Y. empty
optimization methods:
1) check the configuration IUB interface transfer bandwidth.
If the IUB interface ATM transmission bearer, then the RNC side by ADD AAL2PATH PATH command
to query each transmission resource index references, and then check the configuration of the PATH index
corresponding transmission bandwidth is through ADD ATMTRF; in NodeB side by ADD AAL2PATH
query configuration bandwidth.
If the IUB interface IP transport bearer, check the RNC and NodeB side by ADD IPPATH command.
8/13/2019 Iub Investigation
19/32
2) IUB transmission bandwidth of the query above configuration, the physical interface transfer capability
contrast.
If the transmission bandwidth is greater than the physical capacity configured in IUB interface to the ATM
transmission bearer mode, MOD ATMTRF piecemeal transmission bandwidth configuration; at IUB
interface IP transport bearer mode, MOD IPPATH bandwidth of the transmission configuration piecemeal,
so that the physical bearer consistent ability.
3) Check the intermediate transmission is abnormal, so IUB interface transfer quality deterioration.
8/13/2019 Iub Investigation
20/32
1.1.7 IUB resource investigation
Data issued by theUE correctly received by Node B after FP frame forms need to be sent through
RNC IUB interface transfer resources. If the IUB interface transfer resource-constrained, will also lead to
user rate can not achieve the desired objectives.
General transport limited following reasons: due to the transmission configuration causes; Because
traffic reasons; due to transmission delay jitter and packet loss.
Atransmission configuration checkIf the ATMBandwidth: Step1:
implementation of DSP E1T1 the RNC LMT, see the corresponding number of E1 NodeB available,
and then estimate the available bandwidth of the physical (one pair E1 provides a rate of about 1.5Mbps
or so), if you do not meet the need to increase the E1;
Step2: execute LST AAL2PATH the RNC LMT (optical port if it is hosted) or LST IMAGRP (if it is IMA
Group in the form of bearer), check the corresponding flow index NodeB use; then perform LST
ATMTRF, check the configuration Average rate (SCR), requires more than testing requirements, if not
met, need to be modified;
Step3: receiving a query execution LST AAL2PATH cell rate (RCR) in the NodeB LMT, RCR
requirements consistent configuration and SCR RNC side configuration, if you do not meet the need to
modify.
If the IP
Bandwidth: Step1:run on the RNC LMT LST IPPATH, check the configuration of the transmission
rate rate test requirements are met, and if not satisfied, you need to modify; Step2: execute LST IPLOGICPORT the RNC LMT, check whether the logical port : If not configured,
skip this step; If configured, the configuration of the logical port bandwidth required to meet the testing
requirements, if not met, you need to modify.
BTraffic inspection1, type:
rate for all users under the NodeB RNC LMT-tracking; under the NodeB RTWP all cell tracking; or
NodeB users CDT track.
2, tool
RNC LMT or NodeB LMT
3,
Step1:steps:Tracking down all the NodeB HSUPA user throughput on the LMT;RNC
Step2:RNCunder the NodeB RTWP tracking on all cells LMT;
Step3:the RNC LMT inquiry HSUPA available bandwidth;
8/13/2019 Iub Investigation
21/32
If the rate of all users and available bandwidth * ~ = HSUPA bandwidth utilization, indicating Iub
bandwidth is limited. RTWP measured at the observed values of the cell, the configuration at this time
should be less than the target RNC (Iub bandwidth because all cells share a NodeB, it is judged whether
the subject is in the Iub bandwidth required to obtain all of the HSUPA users NodeB rate information).
If you need further analysis, we can track the user's CDT on NodeB LMT, message tracking as
shown in Figure 3-45 (hook on Hsupa Rlenhance Info Statistic: UPA scheduling information and
DecR6FlowCtrlInfo, DecR99FlowCtrlInfo: UPA, R99 flow control information).
If the actual traffic and smaller than the theoretical value, you need to IUB loss investigation.
4, Output:
tracking results
Ctransmission delay jitter and packet loss inspectionRAN11 version, HSUPA of FPPM turned on by default, L2 will be flow control congestion detection,
the decision whether the user has a delay or packet loss congestion.
1, enter:RNC LMT-user CDT track
2, tools
RNC LMT
3,
Step1:steps:Tracking RNC CDT, as shown below.
11 RNC CDT track
8/13/2019 Iub Investigation
22/32
Step2:Use UMAT tool to open CDT track, you can confirm whether the user has Iub congestion
delay congestion and packet loss statistics based on L2 FP layer.
The following four indicators indicates the number of times within a specified period of congestion
occurs (instead of dropping the number), is an accumulated value, if you want to determine whether the
packet loss during the week, you will need to subtract the statistics of the cycle statistics on the cycle is
not 0, then think there is IUB loss.
ucTNLIubDchFrmLostNum; / * IUB DCH TNL congestion dropped frames occur number / *
* / ucTNLIubDchTimeDelayNum;IUB DCH TNL times of congestion delay occurs / *
* / ucTNLIubEDchTimeDelayNum;IUB EDCH TNL delay times of congestion occurs / *
* / ucTNLIubEdchFrmLostNum;IUB EDCH TNL happen the number of dropped frames
congestion * /
12 L2 uplink Iub flow control packet loss indicationif IUB port packet loss, you need to troubleshoot packet loss.
5, Output:
tracking results
8/13/2019 Iub Investigation
23/32
1.1.8 assessed in accordance with the port bandwidth utilization IUB
1, task descriptions
investigation IUB interface transfer bandwidth-limited question
2, enter
the configuration file RNC, NodeB, then the system, RNC, then the system
3, tools
Nastar
4, steps
STEP1. to assess IUB Interface ATM / IP port bandwidth utilization
1) In carrying ATM transmission mode, using the following counter: VS.ATMUlTotal.1 VS.ATMUlTotal.2
VS.ATMUlTotal.3 VS.ATMUlTotal.4 VS.ATMUlAvgUsed.1
NodeB
VS. VS.ATMUlAvgUsed.3 VS.ATMUlAvgUsed.4
ATMUlAvgUsed.2
port 1 utilization (ATM1_Used_Ratio): VS.ATMUlAvgUsed.1 / VS.ATMUlTotal.1
port 2 utilization (ATM2_Used_Ratio): VS.ATMUlAvgUsed.2 / VS.ATMUlTotal. 2
Port 3 utilization (ATM3_Used_Ratio): VS.ATMUlAvgUsed.3 / VS.ATMUlTotal.3
port 4 utilization VS.ATMUlAvgUsed.4 / VS.ATMUlTotal.4
(ATM4_Used_Ratio):2)In IP transport bearer mode, use the following counter: VS.IPUlTotal.1
VS.IPUlTotal.2 VS.IPUlTotal.3 VS.IPUlTotal.4 VS.IPUlAvgUsed.1 VS.IPUlAvgUsed.2 VS.IPUlAvgUsed.3
VS.IPUlAvgUsed.4
NodeB
8/13/2019 Iub Investigation
24/32
port 1 utilization (IP1_Used_Ratio) : VS.IPUlAvgUsed.1 / VS.IPUlTotal.1
port 2 utilization (IP2_Used_Ratio): VS.IPUlAvgUsed.2 / VS.IPUlTotal.2
port 3 utilization (IP3_Used_Ratio): VS.IPUlAvgUsed.3 / VS.IPUlTotal.3
4 port utilization (IP4_Used_Ratio): VS.IPUlAvgUsed.4 / VS.IPUlTotal.4
expansion port bandwidth utilization thresholds and IUB expansion threshold using the same threshold of
70%in.
STEP2. to meet the conditions of the base station, the base station will be all of the following areas,
Conclusion output positioning table IUB Tran limit empty column output Y. other
optimization tips:
1) expansion IUB transmission bearer network transmission bandwidth expansion IUB interface physical
bandwidth.
2) expansion IUB interface transfer configuration bandwidth.
In the IUB interface to the ATM transmission bearer mode, the transmission bandwidth expansion by
ADD ATMTRF configure and use the MOD AAL2PATH the original AAL2PATH in TX traffic record
index, RX traffic record index index was revised to flow after the expansion of bandwidth. As shown
below:
If you need to increase the number of PATH, directly ADD AAL2PATH expansion, as follows:
8/13/2019 Iub Investigation
25/32
In the IUB interface IP transport bearer mode transport configuration by MOD IPPATH expansion of
bandwidth, or use the ADD IPPATH expansion of the number of PATH.
1.1.9 Quality assessment oftransmission
abandwidth,task description
transmission qualitytroubleshoot problems
2, enter
the configuration file RNC, NodeB, then the system, RNC, then the system
3, tools
Nastar
4,steps
STEP1. thenNodeB system using statistical frame loss rate
VS.IUB.FlowCtrol.UL. VS.IUB.FlowCtrol.UL.DropNum.LgcPort2
VS.IUB.FlowCtrol.UL.SendNum.LgcPort1 VS.IUB.FlowCtrol.UL.SendNum.LgcPort2
DropNum.LgcPort1
port a frame loss rate = VS.IUB.FlowCtrol
(IubTranDropRatioPort1). UL.DropNum.LgcPort1 / VS.IUB.FlowCtrol.UL.SendNum.LgcPort1
port 2 frame loss rate =
VS.IUB.FlowCtrol.UL.DropNum.LgcPort2VS.IUB.FlowCtrol.UL.SendNum.LgcPort2
(IubTranDropRatioPort2)/
STEP2. calculation of port congestion delay andrate of
8/13/2019 Iub Investigation
26/32
delayport 1 Mean (IubTranDelayPort1): VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1.Avg
port 2 delay mean (IubTranDelayPort2): VS.IUB.FlowCtrol.UL.DelayVara.LgcPort2. Avg
port a delay congestion rate (IubTranCongtPort1): VS.IUB.FlowCtrol.UL.CongTime.LgcPort1/3600
port 2 delay congestion rate (IubTranCongtPort2): VS.IUB.FlowCtrol.UL.CongTime.LgcPort2/3600
next few counter first presented as a 50332730 VS.IUB.FlowCtrol.UL.DelayCong.DownBWNum.LgcPort1
reference:NodeB IUB logical ports 1 upstream bandwidth is reduced based on the number of available
bandwidth delay
50332755 VS.IUB.FlowCtrol.UL.DelayCong.DownBWNum. LgcPort2 NodeB IUB logical port 2 upstream
bandwidth is reduced based on the number of available bandwidth delay
50332732 VS.IUB.FlowCtrol.UL.DropCong.DownBWNum.LgcPort1 NodeB IUB logical ports 1 upstream
bandwidth available bandwidth dropping down on the number
50332757 VS.IUB. FlowCtrol.UL.DropCong.DownBWNum.LgcPort2 NodeB IUB logical port 2 upstream
bandwidth available bandwidth dropping down on the number
50332727 VS.IUB.FlowCtrol.UL.UpBW.Num.LgcPort1 IUB an uplink logical ports available bandwidth
increases the number
50332752 VS. IUB.FlowCtrol.UL.UpBW.Num.LgcPort2 IUB 2 uplink logical ports available bandwidth
increases the number
50332744 VS.IUB.FlowCtrol.UL.CongTime.LgcPort1 IUB logical ports 1 upstream congestion time
50332769 VS.IUB.FlowCtrol.UL.CongTime.LgcPort2 IUB logical port 2 uplink congestion time
STEP3. transmission quality as assessed by standard
1) When the frame loss rate is greater than or equal to 5% is considered high frame loss, poor transmission
quality
When2) When the transmission delay is greater than equal to 60ms, the transmission is considered delay jitter
is too large, the transmission quality is relatively poor.
3) congestion time, and if more than 30 percent of congestion (tentatively) that transmission congestion. . IUB
transmission resource constrained
STEP4. to meet the conditions of base stations, base station beneath all this area, locate the conclusions in
the output table IUB Tran quality limit output Y. other column is empty
optimization methods:
1) check the configuration IUB interface transfer bandwidth.
If the IUB interface ATM transmission bearer, then the RNC side by ADD AAL2PATH PATH command
to query each transmission resource index references, and then check the configuration of the PATH index
corresponding transmission bandwidth is through ADD ATMTRF; in NodeB side by ADD AAL2PATH
query configuration bandwidth.
If the IUB interface IP transport bearer, check the RNC and NodeB side by ADD IPPATH command.
8/13/2019 Iub Investigation
27/32
2) IUB transmission bandwidth of the query above configuration, the physical interface transfer capability
contrast.
If the transmission bandwidth is greater than the physical capacity configured in IUB interface to the ATM
transmission bearer mode, MOD ATMTRF piecemeal transmission bandwidth configuration; at IUB
interface IP transport bearer mode, MOD IPPATH bandwidth of the transmission configuration piecemeal,
so that the physical bearer consistent ability.
3) Check the intermediate transmission is abnormal, so IUB interface transfer quality deterioration.
1.1.10 HSUPA aggregate output node performance issues
above calculation results are summarized in the following table output: (transmission auxiliary counter is not
presented, but also to the need for a summary table)
Table 1: Positioning Conclusion:
Table 2: intermediate process, analyze artificial data used:
8/13/2019 Iub Investigation
28/32
1.1.11 IUB mouth loss leads to low throughput (IUB mouth problems)
Problem Description (version V2R11C00SPC200)
a game point a 10ms HSUPA speed test sites, the largest only to around 1Mbps,is
not in line with expectations
the problemanalysis of
1) based onthe first basic troubleshooting data transmission problems locating PS:
UE data source is not sufficient and power limited space Kouchong pass
convergence (UE side through data analysis, information can also be enhanced
through the network to determine the downstream side NodeB CDT).
2) According to information confirmed enhanced NodeB CDT downside: low throughput
due to the IUB port bandwidth is limited due to the results as follows:
From the above information we can see that UPA did not rise fast (keeping &
deceleration) of the basic reasons for the IUB mouth due to limited bandwidth.
a) IUB mouth Bandwidth View (information extraction and Field Meaning Refer 3.3.2
(3) below):
print information by NodeB CDT can check the bandwidth outBW and statistical Loss export
item, you can see the exit port is limited bandwidth of IUB is about 915k.
8/13/2019 Iub Investigation
29/32
b) Limited bandwidthanalysis
limited bandwidthIUB mouth There are several reasons:
IUB interface resource itself is not enough, because too much traffic,causing congestion resulting in flow control algorithm into force after
dropping the initiative to adjust the bandwidth
delay jitter IUB port flow control algorithm leads to the entry into
forceinitiative to adjust the bandwidth
IUB mouthloss caused by non-congestion will adjust the bandwidth (eg
transport configuration reasons, etc.)
analysis based on the above reasons, we need to troubleshoot if there is packet lossL2, further excluded if there is packet loss IUB mouth (information extraction Please refer
to the meaning and Field 3.3 in (2) below), can be seen from the figure downward negative
acknowledgment packet (usDlSufiListNum) and the number of dropped frames IUB mouth
(ucTNLIubEdchFrmLostNum) is constantly increasing, so you can determine the presence of IUB
mouth loss:
8/13/2019 Iub Investigation
30/32
Loss of points IUB has the following ports need to gradually investigation confirmed
that the specific location of theloss
RNC to the middle of the transmissionof a dropoutNodeB
RNCinterface board packet loss (generally use PING way to check)
NodeB internal loss
packettreatment
dropout Troubleshooting: Run the NodeB LMT Ping command to open a continuous ping
detection switch, set the ping packet size of 1400 and 1470, if there is ping 1400 can
pass, and ping 1470 barrier, intermediate transmission equipment can determine the MTU
setting unreasonable, less than 1500 .
Solution:the MTU setting is lower than 1500 localwas revised to 1500
8/13/2019 Iub Investigation
31/32
1.2 bandwidth utilizationIUB
When1) Iub transport of ATM, HSUPA Iub bandwidth utilization rate = TCP layer / ATMof bandwidth
13 ATM transmission efficiencywhen the TCP layer rate
8/13/2019 Iub Investigation
32/32
14 IP bandwidth utilizationwhen the TCP layer rate
top related