LTE - eRan13.1 - LTE Only Suggest to Use NIC - LTE - eRan13.1 - LTE Only Suggest to Use NIC - 01.【GUL Data Collection Assistant】【Throughput】KPI DL Scanario

【GUL Data Collection Assistant】【Throughput】Gene
It is suggested that use NIC to collect the log of typical scenario. Click me to find the
For issue site or cell, please collect the needed logs of following list.
Needed Logs
No. (Click hyperlink to find the
collection guide)
1 KPI Counters
2 UU/S1/X2 Trace
3 Cell DT Trace
4 MPT/BBP/RRU Board Log

on Assistant】【Throughput】General KPI DL Scenario
collect the log of typical scenario. Click me to find the collecting method.
ollect the needed logs of following list.
Collection Settings and Requirements Tool
Hourly, Cell level, As long as better(It needs to

contains the counters before problem happened at U2000/PRS
least one week)
Collecting 1 hour, do not select paging message U2000
Select L2, Input 14/34/41/50/133, Same collecting U2000

time with UU/S1 trace
After finished UU/S1 and Cell DT collection 20

minutes, collect the board log. U2000/WebLMT
If the site is Lampsite then it needs to collect
the RHUB log.
KPI DL Scenario
ing method.
Remark
Back
No. Counter ID Counter Name

1 1526728320 L.Cell.Avail.Dur
2 1526728298 L.UL.Interference.Avg PRS_Template_LTE_Data_Counte
3 1526727378 L.Traffic.User.Avg
4 1526727379 L.Traffic.User.Max
5 1526728333 L.Traffic.User.Ulsync.Avg
6 1526737851 L.Traffic.User.InSession.Avg PRS_Template_LTE_Data_Counte
7 1526737852 L.Traffic.User.InSession.Max
8 1526728975 L.Traffic.ActiveUser.Avg
9 1526728976 L.Traffic.ActiveUser.Max
10 1526728969 L.Traffic.ActiveUser.DL.Avg
11 1526728972 L.Traffic.ActiveUser.UL.Avg PRS_Template_LTE_Data_Count
12 1526728546 L.Traffic.User.Cdrx.Avg
13 1526732721 L.Traffic.User.VoIP.Avg
14 1526731537 L.Traffic.User.US.Avg
15 1526730832 L.Traffic.SUNPT.DL.Avg
16 1526730833 L.Traffic.SUNPT.DL.Max
17 1526730558 L.Cell.DL.PDSCH.Tti.Num
18 1526730559 L.Cell.UL.PUSCH.Tti.Num
19 1526728433 L.ChMeas.PRB.DL.Avail
20 1526726740 L.ChMeas.PRB.DL.Used.Avg
21 1526728434 L.ChMeas.PRB.UL.Avail
22 1526726737 L.ChMeas.PRB.UL.Used.Avg
23 1526728545 L.ChMeas.PRB.UL.PreSch.Used.Avg
24 1526728483 L.ChMeas.PRB.UL.FSS.Avg
25 1526728484 L.ChMeas.PRB.DL.FSS.Avg
26 1526730557 L.ChMeas.PRB.UL.PUSCH.Avail
27 1526728764 L.ChMeas.PRB.PUSCH.Avg
28 1526728762 L.ChMeas.PRB.UL.DrbUsed.Avg
29 1526727483 L.ChMeas.PRB.PUCCH.Avg
30 1526728763 L.ChMeas.PRB.DL.DrbUsed.Avg
31 1526730102 L.ChMeas.PRB.DL.SrbUsed.Avg
32 1526730103 L.ChMeas.PRB.DL.PagingUsed.Avg
33 1526728340 L.ULCoMP.RB
34 1526728424 L.ChMeas.PRB.DL.PCell.Used.Avg
35 1526728425 L.ChMeas.PRB.DL.SCell.Used.Avg
36 1526733015 L.ChMeas.PRB.UL.PCell.Used.Avg
37 1526733016 L.ChMeas.PRB.UL.SCell.Used.Avg
38 1526728564 L.Thrp.bits.DL.CAUser
39 1526728565 L.Thrp.Time.DL.CAUser
40 1526740440 L.Thrp.bits.DL.LastTTI.CAUser
41 1526740441 L.Thrp.Time.DL.RmvLastTTI.CAUser
42 1526732658 L.CA.Traffic.bits.DL.PCell
43 1526729259 L.CA.Traffic.bits.DL.SCell
44 1526728765 L.ChMeas.CCE.Avail
45 1526728303 L.ChMeas.CCE.CommUsed
46 1526728304 L.ChMeas.CCE.ULUsed
47 1526728305 L.ChMeas.CCE.DLUsed
48 1526729292 L.ChMeas.CCE.DLUsed.DRB
49 1526729293 L.ChMeas.CCE.DLUsed.SRB
50 1526729294 L.ChMeas.CCE.DLUsed.MCE
51 1526729295 L.ChMeas.CCE.ULUsed.Equivalent
52 1526729296 L.ChMeas.CCE.DLUsed.Equivalent
53 1526730844 L.ChMeas.CCE.UL.AllocFail
54 1526730845 L.ChMeas.CCE.DL.AllocFail
55 1526728664 L.ChMeas.PDCCH.DL.DTXNum.AggLvl1
59 1526728668 L.ChMeas.PDCCH.AggLvl1Num
63 1526739747 L.ChMeas.PDCCH.UL.AggLvl1Num
67 1526728259 L.Thrp.bits.UL
68 1526728261 L.Thrp.bits.DL
69 1526729005 L.Thrp.bits.DL.LastTTI
70 1526729015 L.Thrp.Time.DL.RmvLastTTI
71 1526729049 L.Thrp.bits.UE.UL.LastTTI
72 1526729050 L.Thrp.Time.UE.UL.RmvLastTTI
73 1526729415 L.Thrp.bits.UE.UL.SmallPkt
74 1526729416 L.Thrp.Time.UE.UL.RmvSmallPkt
75 1526728998 L.Thrp.Time.Cell.UL.HighPrecision
76 1526728997 L.Thrp.Time.Cell.DL.HighPrecision
77 1526728262 L.Thrp.Time.DL
78 1526728260 L.Thrp.Time.UL
79 1526742186 L.Thrp.Time.DL.SmallPktConverted
80 1526745988 L.Thrp.TransferTime.DL.RmvLastTTI
81 1526728178 L.Thrp.bits.DL.SRB
82 1526728179 L.Thrp.bits.UL.SRB
83 1526736796 L.Traffic.UL.PktLoss.Tot
84 1526736795 L.Traffic.UL.PktLoss.Loss
85 1526736794 L.Traffic.DL.PktUuLoss.Tot
86 1526736793 L.Traffic.DL.PktUuLoss.Loss
87 1526736797 L.PDCP.Tx.Disc.Trf.SDU
88 1526736798 L.PDCP.Tx.TotRev.Trf.SDU
89 1526736792 L.Traffic.DL.PktDelay.Num
90 1526736791 L.Traffic.DL.PktDelay.Time
91 1526732755 L.Traffic.DL.EmptyBuf.PDCPLat.Num
92 1526732765 L.Traffic.DL.EmptyBuf.PDCPLat.Time
93 1526727354 L.Traffic.DL.SCH.QPSK.TB
94 1526727355 L.Traffic.DL.SCH.16QAM.TB
96 1526728180 L.Traffic.DL.SCH.QPSK.ErrTB.Ibler
97 1526728182 L.Traffic.DL.SCH.16QAM.ErrTB.Ibler
99 1526728181 L.Traffic.DL.SCH.QPSK.ErrTB.Rbler
100 1526728183 L.Traffic.DL.SCH.16QAM.ErrTB.Rbler
103 1526739657 L.Traffic.DL.SCH.256QAM.TB.bits
106 1526727366 L.Traffic.UL.SCH.QPSK.TB
107 1526727367 L.Traffic.UL.SCH.16QAM.TB
108 1526727368 L.Traffic.UL.SCH.64QAM.TB
109 1526728186 L.Traffic.UL.SCH.QPSK.ErrTB.Ibler
110 1526728188 L.Traffic.UL.SCH.16QAM.ErrTB.Ibler
111 1526728190 L.Traffic.UL.SCH.64QAM.ErrTB.Ibler
112 1526728187 L.Traffic.UL.SCH.QPSK.ErrTB.Rbler
113 1526728189 L.Traffic.UL.SCH.16QAM.ErrTB.Rbler
114 1526728191 L.Traffic.UL.SCH.64QAM.ErrTB.Rbler
115 1526727360 L.Traffic.DL.SCH.QPSK.TB.Retrans
116 1526727361 L.Traffic.DL.SCH.16QAM.TB.Retrans
117 1526727362 L.Traffic.DL.SCH.64QAM.TB.Retrans
118 1526727372 L.Traffic.UL.SCH.QPSK.TB.Retrans
119 1526727373 L.Traffic.UL.SCH.16QAM.TB.Retrans
120 1526727374 L.Traffic.UL.SCH.64QAM.TB.Retrans
121 1526735156 L.Traffic.DL.SCH.HOCmd.TB
122 1526735157 L.Traffic.DL.SCH.HOCmd.ErrTB.Ibler
123 1526735158 L.Traffic.DL.SCH.HOCmd.ErrTB.Rbler
124 1526730141 L.ChMeas.RI.Rank1
128 1526727396 L.ChMeas.CQI.DL.0
129 1526727397 L.ChMeas.CQI.DL.1
130 1526727398 L.ChMeas.CQI.DL.2
131 1526727399 L.ChMeas.CQI.DL.3
132 1526727400 L.ChMeas.CQI.DL.4
133 1526727401 L.ChMeas.CQI.DL.5
134 1526727402 L.ChMeas.CQI.DL.6
135 1526727403 L.ChMeas.CQI.DL.7
136 1526727404 L.ChMeas.CQI.DL.8
137 1526727405 L.ChMeas.CQI.DL.9
138 1526727406 L.ChMeas.CQI.DL.10
139 1526727407 L.ChMeas.CQI.DL.11
140 1526727408 L.ChMeas.CQI.DL.12
141 1526727409 L.ChMeas.CQI.DL.13
142 1526727410 L.ChMeas.CQI.DL.14
143 1526727411 L.ChMeas.CQI.DL.15
144 1526728956 L.RA.TA.UE.Index0
145 1526728957 L.RA.TA.UE.Index1
146 1526728958 L.RA.TA.UE.Index2
147 1526728959 L.RA.TA.UE.Index3
148 1526728960 L.RA.TA.UE.Index4
149 1526728961 L.RA.TA.UE.Index5
150 1526728962 L.RA.TA.UE.Index6
151 1526728963 L.RA.TA.UE.Index7
152 1526728964 L.RA.TA.UE.Index8
153 1526728965 L.RA.TA.UE.Index9
154 1526728966 L.RA.TA.UE.Index10
155 1526728967 L.RA.TA.UE.Index11
156 1526728547 L.Cdrx.Enter.Num
157 1526728548 L.Cdrx.Exit.Num
158 1526728549 L.Cdrx.Active.TtiNum
159 1526728550 L.Cdrx.Sleep.TtiNum
160 1526743735 L.Rel.DL.AMBR.Samp.Index0
170 1526727444 L.ChMeas.PDSCH.MCS.0
1526727468 L.ChMeas.PDSCH.MCS.24
1526727412 L.ChMeas.PUSCH.MCS.0
1526729668 L.Traffic.DL.PktSize.Samp.Index0
1526729768 L.Traffic.UL.PktSize.Samp.Index0
1526732808 L.Traffic.User.PL0
1526729283 L.Traffic.DL.SCH.TB.OL.Rank1
1526729281 L.Traffic.DL.SCH.TB.CL.Rank1
1526729455 L.Traffic.DL.SCH.TB.TM1
1526727393 L.ChMeas.MIMO.PRB.OL.Rank1
1526727391 L.ChMeas.MIMO.PRB.CL.Rank1
1526728881 L.ChMeas.BF.PRB.OL.Rank1
1526728882 L.ChMeas.BF.PRB.OL.Rank2
1526729289 L.Traffic.DL.SCH.TB.BF.Rank1
1526729290 L.Traffic.DL.SCH.TB.BF.Rank2
1526727388 L.DLPwr.Max
1526727389 L.DLPwr.Avg
1526728299 L.ChMeas.PDCCH.SymNum.1
1526730124 L.Traffic.PktInterval.Num.Index0
1526732727 L.ChMeas.PRB.PDSCH.Util.Samp.Index0
1526732697 L.ChMeas.PRB.PUSCH.Util.Samp.Index0
1526732739 L.DLPSServ.EstDelay.Avg.Idle
1526732896 L.ULPSServ.EstDelay.Avg.Idle
1526729056 L.Thrp.DL.BitRate.Samp.Index0
1526729435 L.Thrp.UL.BitRate.Samp.Index0
1526734093 L.UL.RSRP.PUSCH.Index0
1526743701 L.UL.SINR.PUSCH.Index0
1526747036 L.PHR.UE.Index0
1526729471 L.AQM.PacketDropNum.QCI.6
1526726833 L.PDCP.Tx.Disc.Trf.SDU.QCI.1
1526727889 L.PDCP.Tx.TotRev.Trf.SDU.QCI.1
1526727934 L.Traffic.DL.PktUuLoss.Loss.QCI.1
1526727935 L.Traffic.DL.PktUuLoss.Tot.QCI.1
1526727961 L.Traffic.UL.PktLoss.Loss.QCI.1
1526727962 L.Traffic.UL.PktLoss.Tot.QCI.1
1526727908 L.Traffic.DL.PktDelay.Num.QCI.1
1526727907 L.Traffic.DL.PktDelay.Time.QCI.1
1526732756 L.Traffic.DL.EmptyBuf.PDCPLat.Num.QCI.1
1526732766 L.Traffic.DL.EmptyBuf.PDCPLat.Time.QCI.1
1526729466 L.RLC.FirstPacketDelay.NonGBR.Index0
1526746033 L.Thrp.Time.UE.UL.FirstPktDelay
1526746034 L.Thrp.UL.FirstPktNum
1526732743 L.Thrp.bits.DL.PerUser.In.Index0
1526732749 L.Thrp.bits.DL.PerUser.Out.Index0
1526728445 L.Traffic.ActiveUser.UL.QCI.Total
1526728455 L.Traffic.ActiveUser.DL.QCI.Total
1526728338 L.ULCoMP.User.Avg
1526728426 L.Traffic.User.PCell.DL.Avg
1526728427 L.Traffic.User.SCell.DL.Avg
1526732707 L.ChMeas.PRB.UL.TaSch.Used.Avg
1526728481 L.Traffic.User.SRS.Avg
1526728482 L.Traffic.User.SRS.Max
1526728970 L.Traffic.ActiveUser.DL.Max
1526728973 L.Traffic.ActiveUser.UL.Max
1526728598 L.Traffic.UL.SCH.bits.Max
1526728663 L.Traffic.DL.SCH.bits.Max
1526730143 L.Traffic.User.TAMeas.PUCCH.Avg
1526730144 L.Traffic.User.TAMeas.PUCCH.Max
1526726657 L.RRC.ConnReq.Msg
1526726658 L.RRC.ConnReq.Att
1526726659 L.RRC.ConnReq.Succ
1526728774 L.RRC.ConnSetup.TimeAvg
1526727545 L.E-RAB.AttEst
1526727544 L.E-RAB.SuccEst
1526728776 L.E-RAB.Est.TimeAvg
1526727547 L.E-RAB.NormRel
1526727546 L.E-RAB.AbnormRel
1526727085 L.RRC.ReEst.Att
1526727086 L.RRC.ReEst.Succ
1526728167 L.EMC.E-RAB.AttEst
1526728521 L.Paging.Dis.PchCong
1526727212 L.Paging.Dis.Num
1526726884 L.Paging.S1.Rx
1526729479 L.HHO.InterFreq.Service.PrepAttOut
1526729480 L.HHO.InterFreq.Service.ExecAttOut
1526729481 L.HHO.InterFreq.Service.ExecSuccOut
1526728933 L.HHO.InterFreq.Coverage.PrepAttOut
1526728934 L.HHO.InterFreq.Coverage.ExecAttOut
1526728935 L.HHO.InterFreq.Coverage.ExecSuccOut
1526729482 L.HHO.InterFreq.FreqPri.PrepAttOut
1526729483 L.HHO.InterFreq.FreqPri.ExecAttOut
1526729484 L.HHO.InterFreq.FreqPri.ExecSuccOut
1526728526 L.HHO.InterFreq.Load.PrepAttOut
1526728527 L.HHO.InterFreq.Load.ExecAttOut
1526728528 L.HHO.InterFreq.Load.ExecSuccOut
1526729559 L.HHO.InterFreq.UeNumLoad.PrepAttOut
1526729560 L.HHO.InterFreq.UeNumLoad.ExecAttOut
1526729561 L.HHO.InterFreq.UeNumLoad.ExecSuccOut
1526729574 L.RRCRedirection.IntraLTE.Load
1526728936 L.RRCRedirection.IntraLTE.Coverage
1526729632 L.RRCRedirection.InterFddTdd.Coverage
1526729879 L.RRCRedirection.InterFddTdd.Load
1526730526 L.InterFreq.Load.Meas.Num.Cell
1526730527 L.InterFreq.Load.MeasSucc.Num.Cell
1526741893 L.HHO.PingPongHo
1526745971 L.HHO.PingPongHo.Consecutive
1526745973 L.HHO.A2MeasHOTooLate
1526741894 L.HHO.HoToWrgCell
1526741895 L.HHO.HoTooearly
1526741896 L.HHO.HoToolate
1526747686 L.Traffic.User.Avg.DLHighAMBR
1526747688 L.Traffic.User.DLData.Avg.DLHighAMBR
1526747689 L.Traffic.User.InSession.Avg.DLHighAMBR
1526747690 L.Thrp.bits.DL.DLHighAMBR
1526747691 L.Thrp.bits.DL.LastTTI.DLHighAMBR
1526747692 L.Thrp.Time.DL.RmvLastTTI.DLHighAMBR
1526747681 L.MeasRpts.RSRP.Index0
1526739759 L.Thrp.TCP.Bytes.InitTransfer
1526739760 L.Thrp.TCP.Time.InitTransfer
1526739762 L.PDCP.TCP.time.RANRtt.ConnSetup
1526739763 L.PDCP.TCP.Time.TerrestrialRtt.ConnSetup
1526739764 L.PDCP.TCP.RANRtt.ConnSetup
1526739765 L.PDCP.TCP.TerrestrialRtt.ConnSetup
1526732775 L.Thrp.bits.UE.UL.PL0
1526732797 L.Thrp.bits.UE.UL.SmallPkt.PL0
1526732786 L.Thrp.Time.UE.UL.RmvSmallPkt.PL0
1526728599 L.ChMeas.PRB.DL.RANK1.MCS.0
1526729319 L.ChMeas.CQI.DL.SingleCW.Periodic.0
1526729335 L.ChMeas.CQI.DL.SingleCW.Aperiodic.0
1526729351 L.ChMeas.CQI.DL.DualCW.Code0.Periodic.0
1526729367 L.ChMeas.CQI.DL.DualCW.Code0.Aperiodic.0
PRS_Template_LTE_Data_Counters_01.xml
436286787.xlsx 文档密级
Back
Collection Way
Trace UU/S1 by U2000
Trace UU/S1 by WebLMT
Trace UU/S1 by U2000
Step 1 Create a Uu/S1 interface tracing task
Choose Monitor > Signaling Trace > Signaling Trace Management from the m
09/06/2019 华为保密信息,未经授权禁止扩散第20页，共66页

Double click to open the UU/S1 interface trace. Enter the task name, and

Do not select Paging message and click Finish as following figure.
Step 2 Save the result.

Manually stop the UU/S1 interface tracing task by right-clicking t
Status column, right-click the task and choose Export from the sho

Trace UU/S1 by WebLMT
Step 1 Create Uu/S1 interface tracing task
Open UU Interface Trace and S1 Interface Trace in WebLMT.

Step 2 View the tracing result
Step 3 Save the result
Manually stop the S1 interface tracing task by right-clicking the task a

choose Save All Messages from the shortcut menu to save the tracing resu


anagement from the main menu of the U2000.

r the task name, and select an eNodeB.

following figure.
by right-clicking the task and choosing Stop from the shortcut menu. If Finished is displayed in the
Export from the shortcut menu to save the tracing result as a TMF file on the local PC.


-clicking the task and choosing Stop Trace Task from the shortcut menu. Then, right-click the task and
ave the tracing result as a TMF file on the local PC.


s displayed in the
l PC.

k the task and

Back
Collection Way
Trace Cell DT by U2000
Trace Cell DT by U2000
Step 1 Create Cell DT tracing task
Choose Monitor > Signaling Trace > Signaling Trace Management from the m
In the navigation tree of the displayed Signaling Trace Management windo

In the displayed Cell DT Trace dialog box, enter the task name, select a

Set parameters for cell DT tracing, and then click Finish

14/34/41/50/133
Step 2 Save the result

Manually stop the tracing task by right-clicking the task and choo
column, right-click the task and choose Export from the shortcut m

NOTE
1.Not all trace models can be simultaneously selected. If
traced on an LBBP. Otherwise, the data is excessively grea
are not selected, multiple cells can be traced at the same
recommended because cell tracing is oriented to all UEs an
2.If cell DT tracing is simultaneously performed with IFTS
and MAC Layer Trace Field prevail

anagement from the main menu of the U2000.
ace Management window, choose Trace Type > LTE > Information Collection > Cell DT Trace, and double-click Cel

task name, select an eNodeB, and click Next.


14/34/41/50/133
g the task and choosing Stop from the shortcut menu. If Finished is displayed in the Status
from the shortcut menu to save the tracing result as a TMF file on the local PC.

ously selected. If L1 or L2 related contents are selected, only one cell can be
is excessively great in amount, affecting services. If L1 or L2 related contents
traced at the same time. However, simultaneous tracing of multiple cells is not
ented to all UEs and the data is excessively great in amount.
performed with IFTS tracing, the latest values configured for MAC Layer Trace Item

and double-click Cell DT Trace.

he Status

Back
Collection Way
Collect Board Log by U2000
Collect Board Log by WebLMT
Collect Board Log by U2000
Step 1 Open the window for log collection
Choose Software > Software Browser from the main menu of the U2000. On the NE t
and choose Other from the shortcut menu. On the Other tab page in the right pan
Step 2 Export the logs
Right-click BRDLOG -ENODEB and choose Transfer > From NE to OSS Client from the
Choose needed site and select "All", and then set the parameters.
Set the destination path for storing the logs on the local PC, and click OK to
Collect Board Log by WebLMT
Step 1 Start the FTP server

When BRD logs are collected by using the Web LMT, the eNodeB directly uploads l
Ensure that the FTP server works properly before collection is started.
Step 2 Upload BRD logs
Run the ULD FILE command to upload BRD logs. In the command, set IP to the IP a
ULD FILE: FUNCTYPE=ENODEB, SRCF=BRDLOG-ENODEB, CN=0, SRN=0, SN=7, DSTF="LMPT-BR
NOTE
1.Uploading files in non-compressed mode takes a longer time than uploadi
10% to 50%, and CPU overload affects UE access. Therefore, it is recommen
2.BRD logs on different boards need to be collected separately. The cab
be queried by running the DSP BRD command (applicable to 3900 series ba
Step 3 Query the result
Search for the BRD log file in GZ format in the path configured on the FTP serv
decompressed to ensure that the format of the compressed file is correct.
e U2000. On the NE tab page of the displayed Software Browser page, right-click the desired NE
age in the right pane, select BRDLOG -ENODEB.
OSS Client from the shortcut menu.

PC, and click OK to start the log collection.
B directly uploads logs to the PC through the FTP server.

is started.
, set IP to the IP address of the FTP server, and set the user name and password to those configured on the F
SN=7, DSTF="LMPT-BRD-007-LOG", MODE=IPV4, IP="10.148.30.21", USR="admin", PWD="*****", CF=COMPRESSED;
ger time than uploading files in compressed mode. However, uploading files in compressed mode increases CPU usage
efore, it is recommended that files be uploaded in non-compressed mode with flow control performed.
d separately. The cabinet number, subrack number, and slot number that must be set based on site conditions c
ble to 3900 series base stations). For the BTS3202E/BTS3203E, run the DSP BRU command.
ured on the FTP server. Click the file to check whether the compressed file can be properly
le is correct.
ose configured on the FTP server.
, CF=COMPRESSED;
mode increases CPU usage by

performed.
ed on site conditions can
perly
NIC Scenario Collection
Collection Way
By NIC
After eRan12.1 SPC260（U2000 17BSPC240），it is suggested that use NIC(Network Information Collecti
For KPI Counters collecting, NIC can collect the KPI counters of last week. If you need more early
NIC
Step1 Login NIC
U2000 Client->Maintenance->Network Information Collection
Input "User Name" and "Password". The "User Name" and "Password" are same as U2
Step2 Select Fault Handling
Step3 Select problem scenario, Input Task Name and then click "Next"
The typical scenarios include: Access / Call Drop / Handover / Inter-RAT /
eg. Access scenario include: KPI Counters(last two weeks), UU/S1 Trace(1 ho
Click OK button to start monitoring the 1 minute KPI, and the 1 minute KPI can
Step4 Set KPI Counters collection time range by "Data collection time range", Sel
Also can set the timed task and target server for collection result file.
Select problem site.
Step5 Set parameters and click "Finish" to collect log of problem scenario
eg. For Access, it just needs to input "Local Cell ID" because other parameters
Local Cell ID：If you know which cell have problem then input its local
Gather Time(s)： The time range of UU/S1 and Cell DT collection. The de
L2 Trace Model：L2 Cell DT tracing items. For example, the Access scena
Step6 Wait for NIC collection. After finished, download the logs and etrans to GT
NIC is collecting.
After finished, download the logs and etrans to GTAC or R&D.
Back
Information Collection) to collect the typical scenario logs.

you need more early than last week please collect them on U2000 or PRS.
word" are same as U2000 login.

ver / Inter-RAT / Throught / Volte / Abnormal Cell / Transmission Link Fault / SON and so on.
), UU/S1 Trace(1 hour), Cell DT trace(1 hour), CFG file, MML result, Board logs.
he 1 minute KPI can be exported as excel document.
on time range", Select problem sites, and then click "Next"
n result file.
lem scenario
use other parameters have been set the default value(also you can change them). Click "Finish" to collect the
then input its local cell ID. If you do not know which cell have problem in site then input one cell of them
DT collection. The default value is 3600 seconds(1 hour).
ple, the Access scenario needs 11/14/34/50.
gs and etrans to GTAC or R&D.
SON and so on.
"Finish" to collect the logs.
input one cell of them.

LTE - eRan13.1 - LTE Only Suggest to Use NIC - LTE - eRan13.1 - LTE Only Suggest to Use NIC - 01.【GUL Data Collection Assistant】【Throughput】KPI DL Scanario

Uploaded by

Document Information

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

LTE - eRan13.1 - LTE Only Suggest to Use NIC - LTE - eRan13.1 - LTE Only Suggest to Use NIC - 01.【GUL Data Collection Assistant】【Throughput】KPI DL Scanario

Uploaded by

Copyright:

Available Formats

【GUL Data Collection Assistant】【Throughput】Gene

4 MPT/BBP/RRU Board Log

Collection Settings and Requirements Tool

Hourly, Cell level, As long as better(It needs to

Collecting 1 hour, do not select paging message U2000

Select L2, Input 14/34/41/50/133, Same collecting U2000

After finished UU/S1 and Cell DT collection 20

No. Counter ID Counter Name

Trace UU/S1 by U2000

Step 1 Create a Uu/S1 interface tracing task

09/06/2019 华为保密信息,未经授权禁止扩散 第20页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第21页，共66页

Do not select Paging message and click Finish as following figure.

Step 2 Save the result.

09/06/2019 华为保密信息,未经授权禁止扩散 第22页，共66页

Trace UU/S1 by WebLMT

Step 1 Create Uu/S1 interface tracing task

Open UU Interface Trace and S1 Interface Trace in WebLMT.

09/06/2019 华为保密信息,未经授权禁止扩散 第23页，共66页

Step 2 View the tracing result

Step 3 Save the result

Manually stop the S1 interface tracing task by right-clicking the task a

09/06/2019 华为保密信息,未经授权禁止扩散 第24页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第25页，共66页

anagement from the main menu of the U2000.

09/06/2019 华为保密信息,未经授权禁止扩散 第26页，共66页

r the task name, and select an eNodeB.

09/06/2019 华为保密信息,未经授权禁止扩散 第27页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第28页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第29页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第30页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第31页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第32页，共66页

k the task and

09/06/2019 华为保密信息,未经授权禁止扩散 第33页，共66页

Trace Cell DT by U2000

Step 1 Create Cell DT tracing task

In the navigation tree of the displayed Signaling Trace Management windo

09/06/2019 华为保密信息,未经授权禁止扩散 第34页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第35页，共66页

Set parameters for cell DT tracing, and then click Finish

09/06/2019 华为保密信息,未经授权禁止扩散 第36页，共66页

Step 2 Save the result

09/06/2019 华为保密信息,未经授权禁止扩散 第37页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第38页，共66页

anagement from the main menu of the U2000.

09/06/2019 华为保密信息,未经授权禁止扩散 第39页，共66页

task name, select an eNodeB, and click Next.

09/06/2019 华为保密信息,未经授权禁止扩散 第40页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第41页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第42页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第43页，共66页

and double-click Cell DT Trace.

09/06/2019 华为保密信息,未经授权禁止扩散 第44页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散 第45页，共66页

Collect Board Log by U2000

Step 1 Open the window for log collection

Step 2 Export the logs

Collect Board Log by WebLMT

Step 1 Start the FTP server

Step 2 Upload BRD logs

Step 3 Query the result

OSS Client from the shortcut menu.

09/06/2019 华为保密信息,未经授权禁止扩散第20页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第21页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第22页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第23页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第24页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第25页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第26页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第27页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第28页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第29页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第30页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第31页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第32页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第33页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第34页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第35页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第36页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第37页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第38页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第39页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第40页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第41页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第42页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第43页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第44页，共66页

09/06/2019 华为保密信息,未经授权禁止扩散第45页，共66页