Title Type
LGE LTE DM User Guide Manual
ABSTRACT
HISTORY
Rev Status Date Author Contents
V1.0 Created 2009-11-16 MCTR Release version
V1.1 Updated 2009-12-18 MCTR Updated PS items
V1.2 Updated 2009-12-30 MCTR Updated PS items
V1.3 Updated 2010-02-24 MCTR Updated PS items
V1.4 Updated 2010-03-30 MCTR Updated L1 items
V1.5 Updated 2010-04-12 MCTR Updated PS items
V1.6 Updated 2010-05-17 MCTR Updated PS items
V1.7 Updated 2010-07-14 MCTR Updated L1 & Common items
V1.8 Updated 2010-07-29 MCTR Updated L1 item
V1.9 Updated 2010-08-27 Updated L1 item(SCSQ)
MCTR
Updated PS items
V2.0 Updated 2010-10-11 MCTR Updated PS items
Key Words
LTE, DM
©Copyright,
LGE Proprietary2010 By LG Electronics Inc. All
i rights reserved. MCTR Lab.
No part of this document may be reproduced in any way, or by any means, without
the express written permission of LG Electronics Inc
Updated File Rev.
LG Electronics 2010-11-10 LLDM_User_Guide_v2.0.pdf 2.0
CONTENTS
1 Overview .........................................................................................................................................6
1.1 Purpose ........................................................................................................................................6
6
1.2 Scope ...........................................................................................................................................
1.3 Definitions and Abbreviations ....................................................................................................... 6
1.3.1 Definitions ........................................................................................................................ 6
1.3.2 Abbreviations ................................................................................................................... 6
2 LLDM Introduction ........................................................................................................................... 7
2.1 What is LLDM?............................................................................................................................. 7
2.2 Components ................................................................................................................................. 7
2.3 Target Systems ............................................................................................................................ 7
2.4 Operation Environment ................................................................................................................ 7
8
3 Installation .......................................................................................................................................
3.1 Required H/W and S/W................................................................................................................ 8
3.2 Installing LLDM............................................................................................................................. 8
4 License key activation .................................................................................................................. 12
4.1 Step 1 ........................................................................................................................................12
4.2 Step 2 ........................................................................................................................................12
4.3 Step 3 ........................................................................................................................................13
5 Operation...................................................................................................................................... 14
5.1 Setup Menu ............................................................................................................................... 14
5.1.1 Configure 3GPP Baseline............................................................................................. 14
5.1.2 Connection with LTE UE .............................................................................................. 14
5.1.3 Logging Mask (Debug Message Level Setting) ............................................................ 17
5.2 Information Menu ...................................................................................................................... 20
5.2.1 Logging Status.............................................................................................................. 20
5.3 Replay Menu ............................................................................................................................. 21
5.3.1 Load Replay Menu ....................................................................................................... 21
5.3.2 Replay Toolbar ............................................................................................................. 22
5.4 Exit Menu .................................................................................................................................. 22
5.5 Tree View (menu)...................................................................................................................... 23
5.5.1 Log Message ................................................................................................................ 24
5.5.2 Debug Message ........................................................................................................... 25
5.5.3 Control .......................................................................................................................... 27
5.6 Layer 1 Menu ............................................................................................................................ 29
5.6.1 Searcher Control .......................................................................................................... 30
5.6.2 TX Control .................................................................................................................... 30
5.6.3 DL Codec Control ......................................................................................................... 31
5.6.4 Search Result ............................................................................................................... 31
5.6.5 Cell Information ............................................................................................................ 33
5.6.6 Channel Information ..................................................................................................... 34
5.6.7 Path Profile Information ................................................................................................ 36
5.6.8 Wide-Band CQI Information ......................................................................................... 38
5.6.9 Sub-Band CQI Information ........................................................................................... 39
5.6.10 RI/CQI/PMI for CQI report ............................................................................................ 40
5.6.11 Serving Cell Quality Information ................................................................................... 50
5.6.12 CFI Information............................................................................................................. 51
5.6.13 DL-ACK Detection Rate................................................................................................ 52
5.6.14 TX Power Information................................................................................................... 53
5.6.15 RACH Information ........................................................................................................ 55
5.6.16 UL Transmission Modes - UCI ..................................................................................... 56
5.6.17 TA Information .............................................................................................................. 58
5.6.18 UL PRB MAP Information ............................................................................................. 59
5.6.19 PDSCH PHY Throughput ............................................................................................. 61
LGE Proprietary ii/186 MCTR Lab.
Updated File Rev.
LG Electronics 2010-11-10 LLDM_User_Guide_v2.0.pdf 2.0
FIGURES
TABLES
1 Overview
1.1 Purpose
This user guide describes how to install and setup LLDM. It also describes LLDM features and
operation procedures.
1.2 Scope
This user guide is intended for users of LLDM who need to know how to install, setup, and operate.
This document is based on 3gpp LTE standards, which are compliant with June2009,
September2009 as well as December2009.
1.3.2 Abbreviations
Abbreviation Description
DM Diagnostic Monitor
UE User Equipment
2 LLDM Introduction
LLDM is a Diagnostic Monitor for logging and analyzing over-the-air network system
performance and parameters.
2.2 Components
PC Side
LLDM Host (Measurement Tool) : logs and analyzes real-time diagnostic and
measurement data
LTE UE Side
LLDM Agent : collects diagnostic and measurement data and transfers to LLDM
Description
CPU Pentium IV 1.8GHz ~
RAM 512MB ~
Video 1024 * 768 ~
Operating system Windows XP professional
Interfaces USB 2.0 High Speed or Ethernet
3 Installation
License Agreement
Installing
4.1 Step 1
Run “Start>Program>LLDM>LGE_LLDM_PcSerialChecker”
4.2 Step 2
This is your own ID.
*PcSerialChecker is a tool for getting your own ID, which is defined based on your hardware
and operating system. Thus, your ID will be changed if you re-install OS.
4.3 Step 3
User should copy this ID in a clip board, and paste it into an email. Then please forward it to a
person in charge.
After you receive the license file(named “NETIMIZER.LIC”), please copy it to the LLDM installation
folder(i.e., C:\Program Files\LGE\LLDM).
Normally, the license file expires after a certain period of time, which depends on the license
agreement. As long as the license file is valid, you may upgrade the new LLDM if you get one.
Thus, please backup your own license file into a safe folder.
5 Operation
In this chapter, it describes the basic How-to-use of LLDM.
Choose LLDM program from [Start Programs LLDM] Menu and run LLDM.
Make sure LTE UE is running and USB cable or Ethernet cable is connected properly.
Port Setting [ Only if LLDM is connected with LTE UE through USB cable ]
Select [Setup Set Com Port] in LLDM.
Click “CH1” check box.
Set Port number (LTE USB Modem Port Number). If LTE UE is connected with LLDM
through USB, LTE USB Modem Port is appeared in Device Manager)
Set Baud Rate, Flow Control like the below picture
Click “Log Mask” Icon to select items to be transmitted from LTE UE.
Click “OK” button
Description
Port LTE USB Modem Port
Baud Rate Baud Rate (115200 fixed)
Flow control Flow Control Type
(None, Hardware ,Software type)
RTS RTS (Request To Send)
DTR DTR (Data Terminal Ready)
Log Mask The only log data items you choose in Log Mask Setting Tree View
are collected at LTE UE side and sent to LLDM.
Port Setting [ Only if LLDM is connected with LTE UE through Ethernet cable ]
Select [Setup Set Com Port] in LLDM.
Click “CH1” check box.
Set IP address, Port number, TCP.
Click “Log Mask” Icon to select items to be transmitted from LTE UE.
Make sure NTWK LED of DECA is turned on.
Click “OK” button.
Description
IP IP address (ex, 192.168.1.1)
Port Port Number (ex, 50001)
TCP/UDP Transport Protocol (ex, TCP)
The connection status can be checked on the status bar. When connected correctly, “R(115200)”
will be appeared like the following picture.
Description
Disconnected with UE
Connected with UE (blue color)
R: Real time mode
115200 : Baud rate
0% : DM port utilization ratio
The only log data items you choose in Log Mask Setting Tree View are gathered at LTE UE side
and sent to LLDM.
Through Debug Level Setting, you can change the debug message level. LTE UE will send the
only items you choose at the Debug Level Setting ComboBox. It applies to only Debug Message.
Level Description
DM_LVL_FATAL Fatal Error or above
DM_LVL_ERROR General Error or above
DM_LVL_HIGH High Level Message or above
DM_LVL_MID Medium Level Message or above
DM_LVL_LOW Low Level Message or above
DM_LVL_ALL All Message
DM_LVL_UNKNOWN No Message
item description
Logging status Current logging status.
Log start time Time that logging was started.
Elapsed time Elapsed time from the log start time.
Log file name Log file name.
Log file size Log file size. (bytes)
Received logs Total received log number
Start Start the logging.
Stop Stop the logging.
When logging starts, LLDM automatically determine the name of logging file based on logging
start time.
Log File Name Description
_YYYYMMDD_HHNNSS_CHx.DML YYYY : year (2002)
(Example : _20020729_094734_CH1.DML) MM : month (07)
DD : date (29)
HH : hour (09)
NN : minute (47)
SS : second (34)
x : channel (1)
Icon Description
Load/close log file for replay.
Start replay
Stop replay
Pause replay
Resume replay
Display/change the replay speed (1/10 X, 1/5 X, 1 X, 5 X, 10 X).
Left time Logging start and end time of the log file
Right times Current replay time
Slider Replay progress
To fix tree view menu on the left side of LLDM. Click button.
Log message Window displays DM log message (DM Log Data + Debug Message) from UE.
2
1
# Description
① ②
Selects log messages type to be displayed in window , and set the colors of each
②
log message type.
Shows brief information of collected log messages.
Time: Time stamp contained in log message.
Log Type: Channel type: Paging, Access, Forward Traffic, Reverse Traffic, etc.
Message : Message type.
Size : Size of message.
Direction : Forward or Reverse
# : Log message sequence
③ When user double-click any item in ②
, the detailed contents of selected log
message is displayed.
If button in the top-left side is pressed down, the detailed contents of recently
④ ③
collected log message are displayed.
⑤
You can change the font used for , through the popup menu.
select a pre-defined preset. Preset means the saved
filter set. “None” preset means all is uncheck..
Preset has information about check/uncheck and
②
color setting information.
Pause (down)/Resume (up) display. ( )
On (down)/Off (up) detailed display. (③)
For user-convenience, when exiting LLDM, It automatically save log message check/uncheck
information and window size and restore when starting it.
Item Description
No Sequence Number
Time Timestamp
Module Module Name
File Name File name
Line# Line number where debug message sent
Level Debug Message Level
Message Text Debug Message Text (Printf)
Debug Message Window provides a context menu. To show a context menu, click right mouse-
button.
Item Description
Clear Clear debug message window
Pause Pause displaying debug message
File Logging Export to File or Excel
Message Level Debug Message Level
5.5.3 Control
Item Description
Compile Date LTE UE Software Compile Date
S/W Version LTE UE Software Version
Build option LTE UE Build Option
H/W Version Hardware Version
DM Agent Version LTE UE DM Agent Version
DM Version LLDM Version
BB Rev. LTE UE Baseband Revision
Core Info. LTE UE Core information
Opt. Level LTE UE S/W Optimization level
Mode Operation Mode
3GPP Baseline 3GPP standard baseline
USIM UICC Mode
L1 menus are consists of command and log items. L1 command items are intended for L1 single
test without protocol stack. Do not try to use L1 command items when UE Configuration menu in
Protocol stack is enabled. L1 log items can be displayed without any restriction if each item log
mask is enabled.
Control Item
Log Item
5.6.2 TX Control
5.6.2.1 Menu
[Control L1 Control Tx Control]
TimingAdjustment value
Valid only when TaValidity is TRUE
TA value range : -31 ~ 2047 [TA]
TxTa Data format [1 TA unit]
Default: 0
Advance range :1 ~ 2047
Retard range : -31 ~ -1
Basically, Ta should be used to timing adjustment
between eNB and UE. Therefore, we don’t expect to
TxTs
use Ts value in IOT.
-15 ~15 (Ts)
RF Gain Setting Check for Fixed Power or Fixed Power/RB
Check for Fixed Power setting
FixedPowValidity 0 : FALSE, 1 : Fixed Power, 2 : Adjust MAX Power
Check for Fixed Power /RB setting
FixedPowPerRBValidity 0 : FALSE,1 : TRUE
Apply RF Gain value
Valid only when Fixed Power or Fixed Power/RB is
checked.
Fixed Power
Range: -50..23
Default: 0
Unit: 0.5dB (ex. -20.5 is -20.5dB)
5.6.2.4 Note
Search Result log shows Mp Search result and Cell Search result.
5.6.4.4 Note
Cell Information display neighbor cell lists which are collected from the searcher and
measurement module. Each cell set type can be described by followings;
This item provide DL frequency, Frame boundary and RSRP value for all of cell in neighbor cell list
with detected cells, also history of RSRP of each cell is described by graph window.
5.6.5.4 Note
The above window shows the TX and RX channel correlations across the system bandwidth. The
sub-bands are a set of 30 sampled channels across the system bandwidth. The method of
computing channel correlation is explained in detail as follows.
The 3GPP specification, TS36.101, states that for the case of 2x2 antennas at either eNodeB or
UE or both, the channel spatial correlation matrix Rspat can be expressed as the Kronecker
product of ReNB and RUE according to Rspat = ReNB ⊗ RUE . ReNB is a channel correlation for the
eNB and RUE for the UE.
1 β α αβ
*
1 αβ * α
1 α 1 β β
Rspat = ReNB ⊗ RUE = * ⊗ * = *
α 1 β 1 α α β 1 β
*
* * * *
α β α β 1
The parameters, α and β in the equation defines the spatial correlation between the antennas at
the eNodeB and UE.
h h h h3
= 00 01 = 1
If a complex channel matrix is H and h = vec( H ) = [h1 h2 h3 h4 ]
,
h10 h11 h2 h4
consisting of element hij where i is the index of receive antenna and j transmit antenna or
hk where k is an index for stacking column vector, Rspat is expressed as
The alpha value shall be the transmitter correlation and the beta be the receive correlation. Finally,
we have correlation estimator as follows by taking time average into consideration. The moving
average filter shall be one-pole IIR filter or alpha tracker with forgetting parameter 1/128.
The average of TX and RX correlations for all samples are shown in the following GUI.
Information element
Description
/Group name
validity 1: valid, 0: invalid
chan_H [30 ]
> h00 H00 channel information
>> re Real value
>> im Imaginary value
> h01 H01 channel information
>> re Real value
>> im Imaginary value
> h10 H10 channel information
>> re Real value
>> im Imaginary value
> h11 H11 channel information
>> re Real value
>> im Imaginary value
5.6.6.4 Note
This information shows the channel impulse response of reference signals in the time domain. In
the upper right part of GUI, the basic information of serving cell demodulation. The serving cell ID
indicates which cell is currently being tracked. The reference timing gives the information of
reference cell timing of demodulation. The reference EsNo is the detected RS SNR in the
reference position.
In the middle of GUI, the channel impulse response (CIR) of reference signals in the time domain
is shown. The CIR of reference signals gives us how time delay of propagation channel is shaped.
Some of the path profile information is also shown in the L1 graph. The reference EsNo and timing
is drawn in the time domain. User can choose an option of enabling display of that information by
checking boxes in the GUI.
Information
element/Group Description
name
validity True if this information is valid
reserved Reserved
Serving_cell_ID Serving cell ID
N Noise power metric
RS power metric of reference path. EsNo is calculated by computing
Ref_EsNo
10*log10(RS power metric/noise power metric)
Ref_timing Reference timing of serving cell. The resolution is Ts in a frame
Path_info[16]
>EsNo RS power metric of this path
>Position Timing offset from reference timing ( Ts resolution)
5.6.7.4 Note
This information is valid only if a cell is selected in the UE. The interval of displaying this
information is aperiodic. However, its value is not deterministic but can be random according to
the execution context of UE system since UE sends this information upon CPU idle time.
The wideband CQI information shows measured CQI of wideband in the UE under the assumption
of the configuration of aperiodic CQI. It simultaneously shows CQI for rank1, rank2 of codeword 0
and 1 as well as PMI for each. User can enable or disable the display of wide-band information by
clicking the check-boxes in the GUI.
The rank information shows average of rank in the UE. The UE sends a rank, 0 or 1, according to
measured propagation condition. The DM shows an instant value of rank as well as average value.
This average is reset when the reset button is pressed.
The update period is variable since this information is refreshed only when UE CPU sends upon
idle task opportunities in the OS context. Due to this fact, the aperiodic CQI reports to eNode-B
may not be time-synchronized with this information.
Information
element/Group Description
name
validity True if this information is valid
Rank Rank
wb_cqi_info wide band CQI information
>rank1_cqi Rank1 wide band CQI
>rank1_pmi Rank1 wide band PMI
>rank2_cw0_cqi Rank2 wide band CQI for CW0
>rank2_cw1_cqi Rank2 wide band CQI for CW1
>rank2_pmi Rank2 wide band PMI
sb_cqi_info sub-band CQI information
>rank1_cqi[28] Rank1 sub band CQI
>rank1_pmi[28] Rank1 sub band PMI
>rank2_cw0_cqi[28] Rank2 sub band CQI for CW0
>rank2_cw1_cqi[28] Rank2 sub band CQI for CW1
>rank2_pmi[28] Rank2 sub band PMI
5.6.8.4 Note
The sub-band CQI information shows the CQI (channel quality information) of sub-bands. The
sub-band is defined a unit for a group of resource elements used for reporting sub-band CQI. The
reference algorithm for display is based on the configuration of current aperiodic CQI report format.
The number of sub-bands can be varied according to system bandwidth. For example, the GUI
shows CQIs for 9 sub-bands for 10MHz system bandwidth.
For rank1 CQI, it can be associated either with transmit diversity or with spatial multiplexing of
rank 1 according to transmission mode. For example, in the case of open-loop MIMO transmission
mode, the rank1 will display transmit diversity case. For rank2 CQI, CQI of the codeword for each
layer is displayed assuming spatial multiplexing.
The update period is variable since this information is refreshed only when UE CPU sends upon
idle task opportunities in the OS context. Due to this fact, the aperiodic CQI reports to eNode-B
may not be time-synchronized with this information.
Information
element/Group Description
name
validity True if this information is valid
Rank Rank
wb_cqi_info wide band CQI information
>rank1_cqi Rank1 wide band CQI
>rank1_pmi Rank1 wide band PMI
>rank2_cw0_cqi Rank2 wide band CQI for CW0
>rank2_cw1_cqi Rank2 wide band CQI for CW1
>rank2_pmi Rank2 wide band PMI
sb_cqi_info sub-band CQI information
>rank1_cqi[28] Rank1 sub band CQI
>rank1_pmi[28] Rank1 sub band PMI
>rank2_cw0_cqi[28] Rank2 sub band CQI for CW0
>rank2_cw1_cqi[28] Rank2 sub band CQI for CW1
>rank2_pmi[28] Rank2 sub band PMI
5.6.9.4 Note
The interval of displaying this information is periodic. However, its value is not deterministic but
can be random according to the task execution context of UE system.
5.6.10.1 Menu
[Layer 1 RI/CQI/PMI for CQI report]
There are four types of CQI report for periodic report and five for aperiodic report. This information
shows the log of CQI reports performed by UE. When aperiodic and periodic CQIs are overlapped,
it shall display those logs simultaneously. The logging format shall be based on text print in the
5.6.10.3 Note
Note that RI/CQI/PMI can be dropped on the actual uplink transmission even though GUI window
displays them.
According to “CQI reporting instance type” in the header, the format of display CQI information
differs. From next sections, we describe those formats.
This is wide-band CQI report type through PUSCH with multiple PMI feedback type. Closed-loop
spatial multiplexing and closed-loop rank 1 pre-coding scheme are operated with this report type.
The channel quality information format for this report is shown in the following table.
In case of RI=0, Wideband CQI codeword 1 is filled with zero. We explain the interpretation of
header field in the last sub-section. For this mode, the DM shall display the field of CQI information.
For example, it prints the CQI information in a GUI window for rank2.
[TM5] Aperiodic CQI 1-2, STI 504, RI 1, WB CQI 15,15 PMI 1,1,0,1,0,1,1,0,0
The DM shall interpret the DM data packet and display associated information as shown in the
example.
This is UE selected CQI report type through PUSCH without PMI feedback. Single antenna,
transmit diversity, and open-loop spatial multiplexing are operated with this report type. The
channel quality information format for this report is shown in the following table.
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank2. The display of the position of the M selected sub-bands
shall not be encoded. For example, it prints the CQI information in a GUI window for rank2.
[TM3] Aperiodic CQI 2-0, STI 3, RI 1, WB CQI 15 , SB CQI 15, M-selec 2,4,5,6,7
The DM shall interpret the DM data packet and display associated information as shown in the
example. We explain the interpretation of header field in the last sub-section.
This is UE selected CQI report type through PUSCH with multiple PMI feedback. Closed-loop
spatial multiplexing and closed-loop rank 1 pre-coding scheme are operated with this report type.
The channel quality information format for this report is shown in the following table.
In case of RI=0, Wideband and sub-band CQI for codeword 1 is filled with zero. For this mode, the
DM shall display the field of CQI information. For example, it shall print the CQI information in a
GUI window for rank2. The display of the position of the M selected sub-bands and CQI shall not
be encoded.
[TM4] Aperiodic CQI 2-2, STI 430, RI 12, WB CQI 15,15, SB CQI 15, 15, M-selec 2,4,5,6, PMI 1
The DM shall interpret the DM data packet and display associated information as shown in the
example.
This is higher-layer configured CQI report type through PUSCH without PMI feedback. Single
antenna, transmit diversity, and open-loop spatial multiplexing are operated with this report type.
The channel quality information format for this report is shown in the following table.
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank2. The displayed CQI shall not be differentially encoded.
[TM3]Aperiodic CQI 3-0, STI 459, RI 1, WB CQI 15, SB CQI 15, 15, 14, 13, 15, 14, 15, 15, 13
The DM shall interpret the DM data packet and display associated information as shown in the
example..
This is higher-layer configured CQI report type through PUSCH with multiple PMI feedback type.
Closed-loop spatial multiplexing, closed-loop rank 1 pre-coding, and multi-user MIMO scheme are
operated with this report type. The channel quality information format for this report is shown in the
following table.
In case of RI=0, wideband and sub-band CQI for codeword 1 is filled with zero.We explain the
interpretation of header field in the last sub-section.
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank2. The displayed CQI shall not be differentially encoded.
[TM4] Aperiodic CQI 3-1, STI 459, Rank 2, WB CQI0 15, SB CQI0 15, 15, 14, 13, 15, 14, 15, 15,
13 WB CQI1 15, SB CQI1 14, 13, 14, 15, 15, 16, 15, 15, 13 PMI 1
The DM shall interpret the DM data packet and display associated information as shown in the
example.
This is RI reporting format for wide-band CQI report type without PMI through PUCCH. Single
antenna, transmit diversity, and open-loop spatial multiplexing are operated with this report type.
The channel quality information format for this report is shown in the following table.
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank1.
The DM shall interpret the DM data packet and display associated information as shown in the
example. We explain the interpretation of header field in the last sub-section.
This is RI reporting format for wide-band CQI report type with single PMI through PUCCH. Closed-
loop spatial multiplexing, closed-loop rank 1 pre-coding and multi-user MIMO scheme are
operated with this report type. The channel quality information format for this report is shown in the
following table.
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank1.
The DM shall interpret the DM data packet and display associated information as shown in the
example. We explain the interpretation of header field in the last sub-section.
This is RI reporting format for UE selected CQI report type without PMI through PUCCH. Single
antenna, transmit diversity, and open-loop spatial multiplexing are operated with this report type.
The channel quality information format for this report is shown in the following table.
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank1.
The DM shall interpret the DM data packet and display associated information as shown in the
example. We explain the interpretation of header field in the last sub-section.
This is RI reporting format for UE selected CQI report type with single PMI through PUCCH.
Closed-loop spatial multiplexing, closed-loop rank 1 pre-coding and multi-user MIMO scheme are
operated with this report type. The channel quality information format for this report is shown in the
following table.
Header field Bit
width
CQI reporting instance 8
type
Transmission mode 4
RI 4
STI 16
Additional info1 (void) 8
Reserved 1 8
Reserved 2 16
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank2.
The DM shall interpret the DM data packet and display associated information as shown in the
example. We explain the interpretation of header field in the last sub-section.
This is wide-band CQI reporting format for wide-band CQI report type without PMI through
PUCCH. Single antenna, transmit diversity, and open-loop spatial multiplexing are operated with
this report type. The uplink control information (UCI) format for this report is shown in the following
table.
Header field Bit
width
CQI reporting instance 8
type
Transmission mode 4
RI 4
STI 16
Additional info1 (void) 8
Reserved 1 8
Reserved 2 16
Bit
Payload field
width
Wide-band
4
CQI
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank2.
The DM shall interpret the DM data packet and display associated information as shown in the
example. We explain the interpretation of header field in the last sub-section.
This is wide-band CQI reporting format for wide-band CQI report type with single PMI through
PUCCH. Closed-loop spatial multiplexing, closed-loop rank 1 pre-coding, and multi-user MIMO
scheme are operated with this report type. The uplink control information (UCI) format for this
report is shown in the following table.
Bit
Payload field
width
Wide-band CQI0 4
Wide-band CQI1 4
Precoding matrix
4
indication
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window. The displayed CQI shall not be differentially encoded.
[TM4] Periodic CQI 1-1, STI 459, RI 1, WB CQI0 12, WB CQI 13, PMI 1
The DM shall interpret the DM data packet and display associated information as shown in the
example.
We explain the interpretation of header field in the last sub-section.
This is wide-band CQI reporting format for UE selected CQI report type without PMI through
PUCCH. Single antenna, transmit diversity, and open-loop spatial multiplexing are operated with
this report type. The uplink control information(UCI) format for this report is shown in the following
table.
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank2.
The DM shall interpret the DM data packet and display associated information as shown in the
example. We explain the interpretation of header field in the last sub-section.
This is wide-band CQI reporting format for UE selected CQI report type with single PMI through
PUCCH. Closed-loop spatial multiplexing, closed-loop rank 1 pre-coding, and multi-user MIMO
scheme are operated with this report type. The uplink control information(UCI) format for this
report is shown in the following table.
Bit
Payload field
width
Wide-band CQI0 4
Wide-band CQI1 4
Precoding matrix
4
indication
In case of RI=0, Wideband codeword 1 is filled with zero. For this mode, the DM shall display the
field of CQI information. For example, it shall print the CQI information in a GUI window for rank2.
The displayed CQI shall not be differentially encoded
[TM4] Periodic CQI 2-1, STI 459, RI 1, WB CQI0 15, WB CQI1 14, PMI 0
The DM shall interpret the DM data packet and display associated information as shown in the
example.
We explain the interpretation of header field in the last sub-section.
This is sub-band CQI reporting format for UE selected CQI report type without PMI through
PUCCH. Single antenna, transmit diversity, and open-loop spatial multiplexing are operated with
this report type. The uplink control information (UCI) format for this report is shown in the following
table.
For this mode, the DM shall display the field of CQI information. For example, it shall print the CQI
information in a GUI window for rank2.
The DM shall interpret the DM data packet and display associated information as shown in the
example. We explain the interpretation of header field in the last sub-section.
This is sub-band CQI reporting format for UE selected CQI report type with single PMI through
PUCCH. Closed-loop spatial multiplexing, closed-loop rank 1 pre-coding and multi-user MIMO
scheme are operated with this report type. The uplink control information (UCI) format for this
report is shown in the following table.
Bit
Payload field
width
Sub-band CQI0 4
Sub-band CQI1 4
Sub-band
4
position
Label 4
In case of RI=0, Sub-band codeword 1 is filled with zero. For this mode, the DM shall display the
field of CQI information. For example, it shall print the CQI information in a GUI window for rank2.
[TM2] Periodic CQI 2-1, STI 459, RI 1, SB CQI0 15, SB CQI1 14, SB BP 3, Label2
The DM shall interpret the DM data packet and display associated information as shown in the
example. We explain the interpretation of header field in the next section.
The first bit of the field of header and payload corresponds to LSB and the last bit MSB. The
header has the following format.
When the payload includes information related to sub-band, it shall be expressed in the increasing
order of the sub-bands. Additional information can be either the number of sub-bands or selected
sub-bands according to CQI reporting mode.
The transmission mode field has a format of “enum(TM1,TM2,…)”. STI is equal to SFN *1024 +
sub-frame number. RI has a format of “enum(rank1, rank2)”. The CQI reporting instance type is
The serving cell quality information shows SNR of reference signal (RS SNR) and received power
of reference signal (RS RSSI). For RS SNR, reference signal power and noise power for a
resource element containing RS are estimated. The ratio of them is averaged over the assigned
bandwidth and displayed in the time domain.
RS SNR = 10 * log (total RS domain power [W] / (RS RSSI [W] – total RS domain power [W]))
where total RS domain power [dBm] = RSRP [dBm] + 10*log(number of RS per antenna port).
Information
element/Group Description
name
validity True if this information is valid
reserved Reserved
rs_rssi [2] RS RSSI
rs_rssi_factor Reserved
reserved_A[2] Reserved
reserved_A_factor Reserved
reserved_B[2] Reserved
reserved_B_factor Reserved
reserved_S [2] Reserved
reserved_N[2] Reserved
signal_pwr[2] Signal power metric
noise_pwr[2] Noise power metric
5.6.11.4 Note
The CFI information shows frequency counts for detected CFI during 1sec. It displays not the
direct CFI value but that of CFI index is displayed. The CFI index corresponds to the actual control
symbol length of PDCCH. The CFI index to PDCCH symbol length is given by
User can enable or disable the display of that information by clicking check-boxes in the GUI.
Information
Description
element/Group name
validity True if this information is valid
CFI_hit Detected CFI index out of total received count
[RXM_CFI_DM_LOG_N
UM]
5.6.12.4 Note
The interval of displaying this information is periodic. However, its value is not deterministic but
can be random according to the execution context of UE system.
Information
Description
element/Group name
validity True if this information is valid
ack_cnt DL ACK hit count
5.6.13.4 Note
TX power log shows the TX power level. Check the log mask of TX power log mask to display as
described in the section 5.1.3. Each item description is as follows in detail.
Information
element/Group Description
name
StartFrameNum Frame number (0~1023)
StartTTINum Sub frame number (0~9)
Tx power[100]
0:SRS 1: PUCCH, 2: PUSCH, 3: PRACH, 4: PUCCH+SRS 5:
>ChanType
PUSCH+SRS, 6: DTX
>Alpha Alpha semi-statically configured value by higher layer
P0 semi-statically configured value by higher layer
Unit: 0.1dB
PUSCH : PO_PUSCH ( j )
PRACH: PREAMBLE_RECEIVED_TARGET_POWER
>P0 SRS: PSRS_OFFSET
PUCCH: PO_PUCCH
PUSCH+SRS : PO_PUSCH ( j )
PUCCH+SRS : PO_PUCCH
MPR ⋅ K S PUSCH
PUSCH : ∆ TF (i ) = 10 log10 ((2 − 1) β offset )
PRACH: DELTA_PREAMBLE
SRS: 0
>DeltaMCS
PUCCH: ∆ F_PUCCH ( F )
MPR ⋅ K S PUSCH
PUSCH+SRS : ∆ TF (i ) = 10 log10 ((2 − 1) β offset )
PUCCH+SRS : ∆ F_PUCCH ( F )
PUSCH : f (i )
PRACH: (PREAMBLE_TRANSMISSION_COUNTER-1) *
POWER_RAMP_STEP
>fvalue SRS: f (i )
PUCCH: g (i )
PUSCH+SRS : f (i )
PUCCH+SRS : g (i )
5.6.14.4 Note
Power Measurement
- Instantaneous Power – PRACH
- Average Power – PUSCH, PUCCH, TOTAL, Number of averaged power per each
channel is 10.
TX Power
- PUSCH : PUSCH average UE output power in dBm
- PUCCH : PUCCH average UE output power in dBm
- PRACH : PRACH instantaneous UE output power in dBm
- TOTAL(PUSCH, PUCCH,PRACH) : 1 frame based average UE output power in dBm
TX Power / RB
- PUSCH : PUSCH per RB average UE output power in dBm
- PUCCH : PUCCH per RB average UE output power in dBm
- PRACH : PRACH per RB instantaneous UE output power in dBm
- SRS : SRS per RB average UE output power in dBm
- TOTAL(PUSCH, PUCCH,PRACH) : average total power per RB , 1 frame based average
UE output power in dBm
Information element
Description
/Group name
FN Start frame number
SubFN Start subframe number
Preamble Format Format 0 ~4
Normal Speed Mode(Unrestricted set) and High Speed mode
Speed mode
(restricted set)
Root sequence Physical root sequence number
Cyclic Shift Cyclic Shift per User (Cv value)
Zero Correlation Zone Ncs value
Retransmit Number Retransmit number
TX Power RACH transmit power (dBm)
Information element
Description
/Group name
Start_FN Start frame number
Start sub_FN Start subframe number
Simultaneous ACK and CQI higherlayer configuration
SimulACKandCQI
(simultaneous or Not)
Simultaneous ACK and SRS higherlayer configuration
SimulACKandSRS
(simultaneous or Not)
Control_info_s[100] UL control Information
0:PUCCH Format 1, 1:PUCCH Format1a, 2:PUCCH
>Channel Info Format1b,3:PUCCH Format2 , 4:PUCCH Format2a , 5:PUCCH
Format2b 6:PUSCH 7: PRACH 8:SRS, 9: DTX
>Configurations 0 ….31 (if 0 is No configuration)
>RI Valid:0or 1 , Invalid :0xff , drop : 2
>CQI bitsize 0xff : invalid 0:drop 1: cqi[2]is valid
CQI value
… …
UCI has a column of CQI bits (b0 b31) (b32 b63).
5.6.16.4 Note
UCI configuration
Conf # Data CQI ACK SR SRS
0
1 x
2 x
3 x x
4 x
5 x x
6 x x
7 x x x
8 x
9 x x
10 x x
11 x x x
12 x x
13 x x x
14 x x x
15 x x x x
5.6.17 TA Information
5.6.17.1 Menu
[L1 TA Information(R1)]
TA information shows log about updated TA command. Check the log mask of TA information log
mask to display as described in the section. Each item description is as follows in detail.
Information element
Description
/Group name
RX SFN Received frame number
RX TTI Received subframe number
Timing advance command
NTA In case of random access response : 11bit for NTA
In other case : 6bit for NTA (TA = 0, 1, 2,..., 63)
Accum TA Accumulate timing advance command
5.6.17.4 Note
Information element
Description
/Group name
Start_FN Start frame number
Start sub_FN Start subframe number
Bandwidth 0:1.4MHz, 1:3MHz, 2:5MHz, 3:10MHz, 4:15MHz, 5:20MHz
PrbMapInfo[100] UL physical mapping information
16bit binary format
Format Type | Channel Type
00000000000 | 00000
Example)
5.6.18.4 Note
PDSCH PHY Throughput has displays how much to get the downlink data in 1sec. this unit is
Mbps.
Information
Description
element
cw_0 instant throughput of codeword#0 (a number of bit)
cw_1 instant throughput of codeword#1 (a number of bit)
5.6.19.4 Note
PDSCH BLER displays how much transport blocks get CRC_NOK about total received transport
blocks. This unit is percentage.
Information
Description
element
bler_info[2]
> total_nums total received transport blocks
> err_nums transport blocks that CRC is NOK
5.6.20.4 Note
UE can’t calculate PDCCH BLER because UE doesn’t know when eNode-B sends its PDCCH. In
other words, UE detects PDCCH blindly.
So, UE DM supports this item similar with PDCCH BLER. This item displays how much detects
PDCCH(each DCI format ) for 1 second. That is, It displays amount, not percentage(ratio)
Information
Description
element
DCI0 The number of detection for DCI#0
DCI1 The number of detection for DCI#1
DCI1A The number of detection for DCI#1A
DCI1B The number of detection for DCI#1B
DCI1C The number of detection for DCI#1C
DCI2 The number of detection for DCI#2
DCI2A The number of detection for DCI#2A
DCI3 The number of detection for DCI#3
DCI3A The number of detection for DCI#3A
reserved N/A (for debug)
DL Grant & UL ACK/NACK Status(Improved) displays DL grant regardless any DCI format in
every TTI. According to TS36.212, each DCI format has the specific fields, not all, and the
unnecessary fields are displayed to the blank. Additionally, UL_ACK/NACK, CFI, and DCI_3/3A
payload will be included in this item.
5.6.22.4 Note
1) When the value of field has 0xFF or 0xFFFF or 0xFFFFFFFF, DM host program displays
blank for this. Especially, When CFI has 0xFF or 0xFFFF or 0xFFFFFFFF, DM host
program displays blanks for all fields of the row having this CFI.
2) When UE receives DL grant in N timing, DM host program (also raw data) displays that
DL grant information (also DCI_3/3A) is in N timing, that CRC result and UL ACK/NACK
are in N+4 timing to understand DL HARQ operation easily (relation between DL grant
and UL ACK/NACK by 3GPP spec).
Common DL Grant & PDCCH Event Status displays DL grant of common RNTI (RA-RNTI/P-
RNTI/SI-RNTI) only when UE receives it. Additionally, Events through PDCCH(SPS/PDCCH
order) will be displayed in this item.
Information
Description
element
sfn SFN value
tti TTI value
cfi CFI
PDCCH event type
text display
event_type 0:"RAR",1:"PAGING",2:"DBCH",3:"DBCH(SIB1)",4:"DBCH(SI-x)",
5:"PDCCH ORDER",6:"DL SPS ACT",7:"DL SPS REL",
8:"UL SPS ACT",9:"UL SPS REL",10:"DEBUG"
DCI format
text display
dci_format
0:"DCI_1",1:"DCI_1A,2:"DCI_1B",3:"DCI_1C",4:"DCI_2",
5:"DCI_2A",6:"DCI_3",7:"DCI_3A"
RNTI type
text display
rnti
0:"C-RNTI",1:"RA-RNTI",2:"P-RNTI",3:"SI-RNTI",
4:"PUCCH",5:"PUSCH",6:"SPS-RNTI"
transmission scheme
text display
tm_scheme
0:"SING-ANT(P0)",1:"SING-ANT(P5)",2:"TRANS-
DIV",3:"LARGE-CDD",4:"CLOSE-SM",5:"MU-MIMO"
distribution flag
d_flag text display
0:"LOCAL", 1:"DIST"
gap_value gap value
harq HARQ number
RB assignment
rb_assign
hexa display ex> “0x????????”
tpc TPC
mcs MCS
ndi NDI
rv redundancy version
modulation type
mod text display
1:"QPSK",2:"16QAM",3:"64QAM"
new or retransmission type
new_re text display
//0:"RE",1:"NEW"
tb_size transport block size
CRC result
crc_result text display
0:"NOK", 1:"OK"
preamble_idx preamble index for PDCCH order
mask_idx preamble index for PDCCH order
5.6.23.4 Note
PBCH BLER displays how much transport blocks get CRC_NOK about total received transport
blocks. This unit is percentage.
Information
Description
element
bler_info
> total_nums total received transport blocks
> err_nums transport blocks that CRC is NOK
5.6.24.4 Note
UL Throughput log shows the Uplink data throughput at UE side. The types of information are
transferred to the DM. One is the number of bits in new transmission only. The other is the number
of bits in all transmission including new transmission.
Information element
Description
/Group name
new_bit_nums A number of bits about new transmission per 1 sec
retrans_bit_nums A number of bits about re-transmission per 1 sec
5.6.25.4 Note
Information element
Description
/Group name
Frame_num Number of Frame
Sub_frame_num Number of Sub-frame
UlGrantInfo [100] Format of UL Grant Information
>block_size Transport Block size
>rb_assign Resurce block assingment
0 :disable Frequency hopping
>fh
1 :enable Frequency hopping
MCS index
- 0 ~ 10 : QPSK, RV 0
- 11 ~ 28 : 16QAM, RV 0
>mcs
- 29 : RV 1
- 30 : RV 2
- 31 : RV 3
New data indicator(NDI)
>ndi The NDI is toggled for each new transport block
Default value: 0
Power control of PUSCH
>tpc
-0~3
Cyclic shift for DMRS
>cs_dmrs
- 0, 2, 3, 4, 6, 8, 9, 10
>cqi_req
0: Non- aperiodic CQI/PMI/RI reporting
1: Aperiodic CQI/PMI/RI reporting using the PUSCH
0 :NACK
>dl_ack_nack
1 :ACK
>reserved Reserved
5.6.26.4 Note
1) When the value of field has 0xFF or 0xFFFF DM host program displays blank for this.
Especially, When block_size, rb_assign, fh, mcs, ndi, tpc, cs_dmrs, cpi_req, dl_ack_nack,
and reserved field has invalid value(0xFF or 0xFFFF) at the same time, DM host program
displays blanks for all fields of the row.
Left side of L1 Status Information window shows logging history with time stamp including UE local
time and synchronized time to the serving cell. Right side of the window shows detailed
information of selected log from the left side.
State Information shows physical layer state corresponding to RRC state and channel setup status.
State shows physical layer state corresponding to RRC state. Following states are possible:
BCH, PCH, DL-SCH for BCCH, UL/DL-SCH and RACH shows configuration status of each
channel, RELEASE or SETUP.
Serving Cell Information shows physical cell identity of the serving cell, carrier frequency and
bandwidth for uplink and downlink, number of downlink transmission antenna.
5.7.1 UE Control
The following control items are not applicable for the dual-mode devices.
5.7.1.1.1 Menu
[Views->UE Mode]
The following is the procedure to test the normal behavior of the UE.
1) switch on the UE.
2) Select the Normal mode and click the Send button.
3) Configure the necessary information of each layer to start the UE
ex) NAS Configuration, RRC Configuration
4) Perform the procedure according to UE Network Setting guide in below clause to camp
on the UE
5.7.1.1.4 Note
5.7.1.2.1 Menu
[Views->Control->PS Control->NAS Config Info Tab]
Information
element/Group Description
name
It is entered in 15 digit format.
Each digit is from 0 to 9.
IMSI
5.7.1.2.4 Note
This Item information must be set before the UE is camped on an E-UTRA cell.
5.7.1.3.1 Menu
[Views->Control->PS Control->RRC Config Tab]
5.7.1.3.4 Note
This Item information must be set before the UE is camped on an E-UTRA cell.
5.7.1.4.1 Menu
[Views->Control->UE Network]
5.7.1.4.4 Note
c. If the user name, password and APN are needed for attach, type the user name, password and
APN.
d. If a user clicks the “Connect” button, then the UE executes the attach procedure.
e. If a user clicks the “Disconnect” button, then the UE executes the detach procedure
5.7.1.5.1 Menu
[Views->PS->NAS-> Bearer Resource Procedure Status R3->Bearer Resource Allocation Request
R3 tab]
5.7.1.5.4 Note
The usage of this item is the following:
a. A user must set parameters values.
b. click the “Parameter Set” button
5.7.1.6.1 Menu
[Views->PS->NAS-> Bearer Resource Procedure Status R3->Bearer Resource Release Request
R3 tab]
5.7.1.6.4 Note
The usage of this item is the following:
a. A user must set parameters values.
b. click the “Parameter Set” button
5.7.1.7.1 Menu
[Views->PS->NAS-> Bearer Resource Procedure Status R3->Bearer Resource Modify Request
R3 tab]
5.7.1.7.4 Note
The usage of this item is the following:
a. A user must set parameters values.
b. click the “Parameter Set” button
5.7.1.8.1 Menu
[Views->PS->NAS-> PDN Procedure Status R3->PDN Connect R3 tab]
5.7.1.8.4 Note
The usage of this item is the following:
a. A user must set parameters values.
b. click the “Parameter Set” button
5.7.1.9.1 Menu
[Views->PS->NAS-> PDN Procedure Status R3-> PDN Disconnect R3 tab]
5.7.1.9.4 Note
The usage of this item is the following:
a. A user must set parameters values.
b. click the “Parameter Set” button
5.7.1.10.1 Menu
[Views->PS->NAS-> packet Filter Lists R3 tab]
5.7.1.10.4 Note
The usage of this item is the following:
a. A user must set EPS bearer Id.
b. click the “Get Config” button
5.7.2 PDCP
5.7.2.1 PDCP UL Statistics 2
5.7.2.1.1 Menu
[Views PS PDCP PDCP UL Statistics2]
Information
element/Group Description
name
RB ID RB ID
Received The number of PDCP PDUs received from upper layer.
Processed The number of PDCP PDUs which is sent to lower layer, but not
received ack from lower layer.
Sent The number of PDCP PDUs which are received ack (success) from
lower layers
Failed The number of PDCP PDUs which are received nack (fail) from lower
layers
Retransmit The number of retransmitted PDCP PDUs when PDCP re-
establishment is occurred
Discarded The number of PDCP PDUs which are received ack (fail) from lower
layers
5.7.2.1.4 Note
5.7.2.2.1 Menu
[Views PS PDCP PDCP DL Statistics2]
Information
element/Group Description
name
RB ID RB ID
Received The number of PDCP PDUs received from lower layer.
Sent The number of PDCP SDUs sent to upper layer.
Duplicate The number of PDCP PDUs which are duplicated at HO
PDUs in The number of PDCP PDUs saved in reordering buffer now.
Reordering Buf
5.7.2.2.4 Note
It is updated per 1sec.
5.7.2.3.1 Menu
[Views PS PDCP PDCP UL & DL PDU]
5.7.2.3.4 Note
When you chose Log Type PDCL UL&DL PDU, you can look at IP Header parsing result.
The parsing result of IPv6 will be updated as soon as possible.
5.7.2.4.1 Menu
[Views PS PS Graph]
5.7.2.4.4 Note
Total bytes is updated every 1s. It is accumulated during 1 second and calculate throughput
5.7.2.5.1 Menu
[Views PS PDCP Configuration]
5.7.2.5.3
Excel Log Format
Information
element/Group Description
name
RB ID RB ID
EPS ID EPS ID
It is valid only for DRB
UL state PDCP UL entity state
☞ PDCP_NULL
Initial state. PDCP entity is not established.
☞ PDCP_ACTIVE
PDCP entity is established.
Data transmission is possible.
☞ PDCP_CONFIGURED
EPS bearer is activated, but radio bearer is not configured..
Data transmission is not possible.
☞ PDCP_RE_ESTABLISH
PDCP entity is suspended.
Data transmission is stopped for DRB.
☞ PDCP_NULL
Initial state. PDCP entity is not established.
☞ PDCP_ACTIVE
PDCP entity is established.
Data reception is possible.
☞ PDCP_RE_ESTABLISH
PDCP entity is suspended.
Data reception is stopped for DRB.
☞ PDCP_PENDING
PDCP entity is pending.
Data reception is stopped for DRB.
RLC Mode RLC Mode (AM, UM, or TM)
RB Mode SRB or DRB
Discard Timer PDCP SDU discard timer for UL
(50, 100, 150, 300, 500, 750, 1500, infinity)
Status Report whether to send status report in PDCP re-establishment
NumProfiles The Number of supported ROHC profiles
MaxCid The Highest context id using rohc compression
Active profiles ROHC profile value
☞ 0x0001 - RTP/UDP/IP
☞ 0x0002 - UDP/IP
☞ 0x0003 - ESP/IP
☞ 0x0004 - IP
5.7.2.5.4 Note
This item is updated when PDCP context change is occurred
5.7.2.6.1 Menu
[Views PS PDCP Configuration]
Information
element/Group Description
name
Int_algo Integrity protection algorithm
☞ 0 - EIA1 (SNOW3G)
☞ 1 - EIA2 (AES)
☞ 2 - N/A
Enc_algo Ciphering algorithm
☞ 0 - EIA1 (SNOW3G)
☞ 1 - EIA2 (AES)
☞ 2 - EEA0
Rrc_int_key RRC integrity key
Rrc_enc_key RRC ciphering key.
Up_enc_key UP ciphering key.
5.7.2.6.4 Note
Key value is displayed 16byte value in hex
5.7.2.7.1 Menu
[Views PS PDCP UL WindowStatus]
Information
element/Group Description
name
rbId RB ID
epsId EPS ID
It is valid only for DRB
rlcMode RLC Mode (AM, UM, or TM)
numStatus Number of storing UL WinStatus data
UL_WinStatus Structure for UL window status
>sti UL window status data receiving time
STI is consist of SFN+TTI
Value less than 10 corresponding with TTI value
Value greater than 10 corresponding with SFN value
>exTxSn Expected SN to send to lower layer(RLC)
>exCnfSn Last confirmed SN by RLC + 1
>retxBuf_In SN to be stroring for retransmission when HO is occured
>retxBuf_Out SN to be retransmitted after HO is finished
5.7.2.7.4 Note
5.7.2.8.1 Menu
[Views PS PDCP DL WindowStatus]
Information
element/Group Description
name
rbId RB ID
epsId EPS ID
It is valid only for DRB
rlcMode RLC Mode (AM, UM, or TM)
numStatus Number of storing UL WinStatus data
DL_WinStatus Structure for DL window status
>sti UL window status data receiving time
STI is consist of SFN+TTI
Value less than 10 corresponding with TTI value
Value greater than 10 corresponding with SFN value
>rcvRxSn Last submitted SN to uppler layer
5.7.2.8.4 Note
5.7.2.9.1 Menu
[Views PS PDCP UL ROHC]
Information
element/Group Description
name
rbId RB ID
epsId EPS ID
It is valid only for DRB
rlcMode RLC Mode (AM, UM, or TM)
numData Number of storing UL WinStatus data
RohcInfo Structure for DL window status
>pdcpSn Compressed/decompressed PDCP PDU’s SN
☞ 0 - UNCOMPRESSED
☞ 1 - RTP_UDP_IP
☞ 2 - UDP_IP
☞ 3 - ESP_IP
☞ 4 - IP
☞ 0 - NORMAL_UNCOMP
☞ 1 - IR
☞ 2 - IR_DYN
☞ 3 - R_0
☞ 4 - R_0_CRC
☞ 5 - UO_0
☞ 6 - R_1
☞ 7 - R_1_ID
☞ 8 - R_1_TS
☞ 9 - UO_1
☞ 10 - UO_1_ID
☞ 11 - UO_1_TS
☞ 12 - UOR_2
☞ 13 - UOR_2_ID
☞ 14 - UOR_2_TS
>unCompHdrLen Uncompressed (Original) IP Header Length
> compHdrLen Compressed/decompressed IP Header Length
5.7.2.9.4 Note
5.7.2.10.1 Menu
[Views PS PDCP DL ROHC]
Information
element/Group Description
name
rbId RB ID
epsId EPS ID
It is valid only for DRB
rlcMode RLC Mode (AM, UM, or TM)
numData Number of storing UL WinStatus data
RohcInfo Structure for DL window status
>pdcpSn Compressed/decompressed PDCP PDU’s SN
☞ 0 - UNCOMPRESSED
☞ 1 - RTP_UDP_IP
☞ 2 - UDP_IP
☞ 3 - ESP_IP
☞ 4 - IP
☞ 0 - NORMAL_UNCOMP
☞ 1 - IR
☞ 2 - IR_DYN
☞ 3 - R_0
☞ 4 - R_0_CRC
☞ 5 - UO_0
☞ 6 - R_1
☞ 7 - R_1_ID
☞ 8 - R_1_TS
☞ 9 - UO_1
☞ 10 - UO_1_ID
☞ 11 - UO_1_TS
☞ 12 - UOR_2
☞ 13 - UOR_2_ID
☞ 14 - UOR_2_TS
>unCompHdrLen Uncompressed (Original) IP Header Length
> compHdrLen Compressed/decompressed IP Header Length
5.7.2.10.4 Note
5.7.2.11.1 Menu
[Views PS PDCP PDCP control PDU]
5.7.2.11.4 Note
PDCP Control PDU for PDCP status report is displayed once it is sent/received.
However PDCP Control PDU for interspersed ROHC feedback packet is displayed when 100
items are stored.
5.7.2.12.1 Menu
[Views PS PDCP UL ROHC Comp Information]
Information
element/Group Description
name
RB ID RB ID
dummy reserved
stCompInfo structure for compression information
ROHC compression information
>pdcp_sn Compressed PDCP PDU’s SN
>sn ROHC master SN
>pktType ROHC Packet Type
☞ 0 - NORMAL_UNCOMP
☞ 1 - IR
☞ 2 - IR_DYN
☞ 3 - R_0
☞ 4 - R_0_CRC
☞ 5 - UO_0
☞ 6 - R_1
☞ 7 - R_1_ID
☞ 8 - R_1_TS
☞ 9 - UO_1
☞ 10 - UO_1_ID
☞ 11 - UO_1_TS
☞ 12 - UOR_2
☞ 13 - UOR_2_ID
☞ 14 - UOR_2_TS
>unCompHdrLen Uncompressed Packet Header Length to be compressed by ROHC
(Before compression)
According to ROHC profile, it is contained also IP, UDP, RTP header,
etc.
If ROHC Profile is UNCOMPRESSED, this value is 0(invalid).
☞ 0 - UNCOMPRESSED
☞ 1 - RTP_UDP_IP
☞ 2 - UDP_IP
☞ 3 - ESP_IP
☞ 4 - IP
>state ROHC compressor’s state
☞ 0 - IR
☞ 1 - FO
☞ 2 - SO
>mode ROHC compressor’s mode
☞ 0 - U_Mode
☞ 1 - O_Mode
☞ 2 - R_Mode
>mode_trans ROHC compressor’s mode transition information
☞ 0 - INITIATED
☞ 1 - PENDING
☞ 2 - DONE
☞ 3 - CANCEL
>tunnel IP in IP. Tunneling information
Packet parsing information
>ip_version IP version.
If tunnel is true, it is indicated outer IP version.
>extension ROHC extension information
☞ 0 - NO
☞ 1 - EXT_0
☞ 2 - EXT_1
☞ 3 - EXT_2
☞ 4 - EXT_3
5.7.2.12.4 Note
5.7.2.13.1 Menu
[Views PS PDCP UL ROHC Decomp Information]
Information
element/Group Description
name
RB ID RB ID
dummy reserved
stDecompInfo structure for decompression information
ROHC decompression information
>pdcp_sn Decompressed PDCP PDU’s SN
>sn ROHC master SN
☞ 0 - NORMAL_UNCOMP
☞ 1 - IR
☞ 2 - IR_DYN
☞ 3 - R_0
☞ 4 - R_0_CRC
☞ 5 - UO_0
☞ 6 - R_1
☞ 7 - R_1_ID
☞ 8 - R_1_TS
☞ 9 - UO_1
☞ 10 - UO_1_ID
☞ 11 - UO_1_TS
☞ 12 - UOR_2
☞ 13 - UOR_2_ID
☞ 14 - UOR_2_TS
>deCompHdrLen Decompressed Packet Header Length by ROHC (Adter compression)
According to ROHC profile, it is contained also IP, UDP, RTP header,
etc.
If ROHC Profile is UNCOMPRESSED, this value is 0(invalid).
>compHdrLen Compressed Packet Header Length to be decompressed by ROHC
(Before decompression).
If ROHC Profile is UNCOMPRESSED, this value is 0(invalid).
>payloadLen Payload length.
it is not compressed by ROHC
If ROHC Profile is UNCOMPRESSED, this value is 0(invalid).
ROHC context information
>cid ROHC context ID
>profile ROHC Profile
☞ 0 - UNCOMPRESSED
☞ 1 - RTP_UDP_IP
☞ 2 - UDP_IP
☞ 3 - ESP_IP
☞ 4 - IP
>state ROHC decompressor’s state
☞ 0 - NC
☞ 1 - SC
☞ 2 - FC
☞ 0 - U_Mode
☞ 1 - O_Mode
☞ 2 - R_Mode
>mode_trans ROHC compressor’s mode transition information
☞ 0 - INITIATED
☞ 1 - PENDING
☞ 2 - DONE
☞ 3 - CANCEL
>tunnel IP in IP. Tunneling information
Packet parsing information
>ip_version IP version.
If tunnel is true, it is indicated outer IP version.
>extension ROHC extension information
☞ 0 - NO
☞ 1 - EXT_0
☞ 2 - EXT_1
☞ 3 - EXT_2
☞ 4 - EXT_3
>ipid IP ID field in IP header.
This is valid in case IP version is 4.
>rtp_timestamp RTP timestamp in RTP header.
This is valid in case profile is RTP.
>rtp_ts_offset RTP timestamp offset
This is valid in case profile is RTP.
>rtp_ts_stride RTP timestamp stride.
This is valid in case profile is RTP.
>udp_checksum UDP checksum in UDP header.
This is invalid in case profile is IP or Uncompressed.
>dummy reserved
5.7.2.13.4 Note
5.7.2.14.1 Menu
[Views PS PDCP UL ROHC Comp Statistics]
5.7.2.14.2 UI & Description the accumulated byte statistics, accumulated packet type statistics,
current context statistics of ROHC compressor.
.
Information
element/Group Description
name
RB ID RB ID
dummy reserved
stCompStats structure for compressor statistics
* accumulated value
>comp_hdr_bytes accumulated compressed header bytes
>uncomp_hdr_byt accumulated uncompressed header bytes
es
>comp_bytes accumulated compressed packet bytes
>uncomp_bytes accumulated uncompressed packet bytes
>errors num of Error packets
>ir num of IR packets
>ir_dyn num of IR-DYN packets
>type0 num of Type0 packets
>type1 num of Type1 packets
>type2 num of Type2 packets
>normal num of Normal packets
>feedback num of Feedback packets
>used_contexts Num of used contexts
(current value)
>reuse contexts Num of reuse contexts
(current value)
5.7.2.14.4 Note
5.7.2.14.5 Note
5.7.2.15.1 Menu
[Views PS PDCP UL ROHC Decomp Statistics]
5.7.2.15.2 UI & Description the accumulated byte statistics, accumulated packet type statistics,
current context statistics of ROHC decompressor.
.
Information
element/Group Description
name
RB ID RB ID
dummy reserved
stDecompStats structure for decompressor statistics
* accumulated value
>comp_hdr_bytes accumulated compressed header bytes
>decomp_hdr_byt accumulated decompressed header bytes
es
>comp_bytes accumulated compressed packet bytes
>decomp_bytes accumulated decompressed packet bytes
>crc_errors num of CRC Error packets
>udp_errors num of UDP Error packets
>ir num of IR packets
>ir_dyn num of IR-DYN packets
>type0 num of Type0 packets
>type1 num of Type1 packets
>type2 num of Type2 packets
>normal num of Normal packets
>feedback num of Feedback packets
5.7.2.15.4 Note
5.7.3 RLC
5.7.3.1 RLC AM TxData 2
5.7.3.1.1 Menu
[Views->PS->RLC->RLC AM TxData2]
This item displays transmitted data information such as number of transmitted data pdus or control
pdus. This information is accumulated for every established RLC AM Tx Entity.
st
And it is updated whenever one of the parameter is changed after establishment of 1 RLC Tx
Entity.
Information
element/Group Description
name
> RBId Mapping RBId with the entity
>numRlcTxAmData number of transmitted RLC Tx AM PDU
>dmRlcTxAmData RLC AM Tx Data structure
>>STI Current STI Information
>>VT_S Send State variable
>>VT_A Acknowledge state variable
Total Number of Retransmitted pdu excluding Re-
>>PDU_Retx
segmented PDU
>>bCrlc_Status Flag for indicating CRLC_STATUS_IND is sent or not.
>>SDU_TotalRecei
Total number of RLC SDUs received from the application
ved
>>SDU_TotalProce
Total number of RLC SDUs after processing by RLC layer.
ssed
>>SDU_OverflowD Total number of RLC SDUs discarded due to SDU buffer
iscard overflow
5.7.3.1.4 Note
When 100 items are stored or RLC AM Tx Entity is released, it’s going to be displayed.
5.7.3.2.1 Menu
[Views->PS->RLC->RLC AM RxData 3]
This item displays received data information such as number of received pdus or discarded pdus.
This information is accumulated for every established RLC AM Rx Entity each of them.
st
And it is updated whenever one of the parameter is changed after establishment of 1 RLC Rx
Entity
Information
element/Group Description
name
> RBId Mapping RBId with the entity
>
number of received RLC Rx AM PDU
numRlcRxAmData
>
RLC AM Rx Data structure
dmRlcRxAmData
>>STI Current STI Information
>>VR_R Receive state variable
>>VR_H Highest received state variable
the highest possible value of the SN which can be indicated
>>VR_MS
by “ACK_SN” when a STATUS PDU needs to be constructed
>>
Total number of RLC SDUs Sending to the application
SDU_TotalSend
Total number of duplicate packets received in the DL
>>PDU_Duplicate
direction
>>PDU_Outofwin Total number of RLC data PDUs discarded since they were
dow received out of window in the DL
Total number of DL RLC PDUs (Data + control) that were
>>PDU_Discarde discarded before being decoded by RLC layer
d (Invalid state or Invalid RLC Info(e.g Invalid LI), receive
queue full)
>>Reserved
5.7.3.2.4 Note
When 100 items are stored or RLC Rx AM Entity is released, it’s going to be displayed.
5.7.3.3.1 Menu
[Views->PS->RLC->RLC Tx State]
Information
element/Group Description
name
RBId Mapping RBId with the entity
Mode RLC Mode
(AM /UM/TM)
State RLC Tx Entity state
(NULL/DTR)
5.7.3.3.4 Note
This Item information is updated when RLC Tx Entity is Established/ Reset triggered/ Released
5.7.3.4.1 Menu
[Views->PS->RLC->RLC Rx State]
Information
element/Group Description
name
RBId Mapping RBId with the entity
Mode RLC Mode
(AM /UM/TM)
State RLC Rx Entity state
(NULL/DTR)
5.7.3.4.4 Note
This Item information is updated when RLC Rx Entity is Established/Reset/Released
5.7.3.5.1 Menu
[Views->PS->RLC->RLC AM Status PDU 2]
When RLC Tx Entity generate or Rx Entity received status PDU including ACK or Nack
information.
If the ACK info is exist in the status pdu, it displays LSN.
If the NACK info is exist in the status pdu, it displays SN, SOS, SOE value.
User can check Tx Status information using Tx Tab and Rx Status Information using Rx Tab.
Information
element/Group Description
name
Assigned index value of GUI TAB for display
>Index
(Tx = 1, Rx = 2)
> RB Id Mapping RBId with the entity
> numRlcStatus Number of tansmitted/received RLC Status PDU
> dmRlcStatus STATUS PDU information structure
>>STI Current STI Information
Flag to indicate ACK sufi is exist or not
>>AckExist
(0 = not exist, 1 = exist)
Flag to indicate LIST or SLIST sufi is exist or not
>>NackExist
(0 = not exist, 1 = exist)
>>LSN Last Sequence Number
>>Length Number of NACK Information
>>Reserved
>>NACK NACK information structure
>>>SN Missing PDU or segment’s Sequence Number
SO Start.
>>>SOS The position of the first byte of the missing part the PDU with
SN
SO End.
>>>SOE The position of the last byte of the missing part the PDU with
SN
5.7.3.5.4 Note
This Item information is updated when 20 items are stored or RLC AM Tx or AM Rx Entity is
released.
5.7.3.6.1 Menu
[Views->PS->PS Graph->RLC Tx Data Throughput]
Entity 1~3 displays throughput information of AM Entity, Entity 4~5 displays throughput information
of UM Entity.
Information
element/Group Description
name
TxTput RLC Tx Entities’ Throughput information structure
Throughput information of 5 RLC Tx Entities is displayed
(AM :1~3, UM: 4~5)
>RBId Mapping RBId with the entity
>Index Assigned index value of GUI column for display
(AM :1~3, UM: 4~5)
>TotalByte Total transmitted data byte from RLC to MAC including 1st
transmission PDU, Retransmitted PDU, Control PDU.
5.7.3.6.4 Note
TotalByte is updated every 1second.
DM displays current and average value calculated based on TotalByte
5.7.3.7.1 Menu
[Views->PS->RLC->RLC Rx Data Throughput]
Entity 1~3 displays throughput information of AM Entity, Entity 4~5 displays throughput information
of UM Entity.
Information
element/Group Description
name
RxTput RLC Rx Entities’ Throughput information structure
Throughput information of 5 RLC Rx Entities is displayed
(AM :1~3, UM: 4~5)
>RBId Mapping RBId with the entity
>Index Assigned index value of GUI column for display
(AM :1~3, UM: 4~5)
>TotalByte Total data byte of SDUs which are transmitted from RLC to
PDCP
5.7.3.7.4 Note
TotalByte is updated every 1second.
DM displays throughput value calculated based on TotalByte
5.7.3.8.1 Menu
[Views->PS->RLC-> RLC UM TxData 2]
This item displays transmitted data information such as number of transmitted data pdus and this
information is accumulated for every established RLC UM Tx Entity each of them.
st
And it is updated whenever one of the parameter is changed after establishment of 1 RLC Tx
Entity.
Information
element/Group Description
name
>RB Id Mapping RBId with the entity
Table 6-8 RBId_R1
>numRlcTxUmDa
number of transmitted RLC Tx UM PDU
ta
>
RLC UM Tx Data structure
dmRlcTxUmData
>>STI Current STI Information
>>VT_US Send State variable
>>SDU_TotalRec Total number of RLC SDUs received from the application
eived
>>SDU_TotalPro Total number of RLC SDUs after processing by RLC layer.
cessed
>>SDU_Overflow Total number of RLC SDUs discarded due to SDU buffer
Discard overflow
>>SDU_Discards Total number of RLC SDUs discarded during discard
procedure
>>Reserved
5.7.3.8.4 Note
When 20 items are stored or RLC UM Tx Entity is released, it’s going to be transferred
5.7.3.9.1 Menu
[Views->PS->RLC-> RLC UM RxData 2]
This item displays received data information such as number of received pdu or discarded pdu
and this information is accumulated for every established RLC UM Rx Entity each of them.
st
And it is updated whenever one of the parameter is changed after establishment of 1 RLC Tx
Entity.
Information
element/Group Description
name
>RB Id Mapping RBId with the entity
>
number of received RLC Rx UM PDU
numRlcRxUmData
> dmRlcRxUmData RLC UM Rx Data structure
>>STI Current STI Information
>>VR_UR Receive state variable
>>VR_UH Highest received state variable
>>VR_UX T_reordering state variable
>> SDU_TotalSendTotal number of RLC SDUs Sending to the application
Total number of duplicate packets received in the DL
>>PDU_Duplicate
direction
Total number of DL RLC PDUs (Data + control) that were
discarded before being decoded by RLC layer
>>PDU_Discarded
(Invalid state or Invalid RLC Info(e.g Invalid LI), receive
queue full)
5.7.3.9.4 Note
When 20 items are stored or RLC UM Rx Entity is released, it’s going to be transferred
5.7.3.10.1 Menu
[Views->PS->RLC-> RLC AM Header Information]
The Header information is updated whenever RLC generates or receive AMD PDU.
This item displays fixed header contents and following raw data of the RLC PDU.
Information
element/Group Description
name
Assigned index value of GUI TAB for display
>Index
(Tx = 1, Rx = 2)
> RB Id Mapping RBId with the entity
>
Number of tansmitted/received RLC AM PDU
numRlcAMHdrInfo
> dmRlcAMHdrInfo RLC AM Header Information structure
>>STI Current STI Information
>>SN 10bit Sequence Number
>>RF Re-segmentation Flag
(1 –Re-segment 0 – no Re-segment)
>>P Poll bit
(1 – Poll set, 0 – no Poll set)
>>FI Framing Info
(0(0x00) – PDU’s1 st Byte corresponding SDU’s 1 st Byte &
PDU’s last Byte corresponding SDU’s last Byte
1(0x01) – PDU’s1 st Byte corresponding SDU’s 1 st Byte &
PDU’s last Byte not corresponding SDU’s last Byte
8(0x10) - PDU’s1 st Byte not corresponding SDU’s 1 st Byte
& PDU’s last Byte corresponding SDU’s last Byte
16(0x11) - PDU’s1 st Byte not corresponding SDU’s 1 st
Byte & PDU’s last Byte not corresponding SDU’s last Byte)
>>E Extention Bit
5.7.3.10.4 Note
When 100 items are stored or RLC AM Tx or AM Rx Entity is released, it’s going to be displayed.
5.7.3.11.1 Menu
[Views->PS->RLC-> RLC UM Header Information]
The Header information is updated whenever RLC generates or receive UMD PDU.
This item displays fixed header contents and following raw data of the RLC PDU
Information
element/Group Description
name
Assigned index value of GUI TAB for display
>Index
(Tx = 1, Rx = 2)
> RB Id Mapping RBId with the entity
>
Number of tansmitted/received RLC UM PDU
numRlcUMHdrInfo
> dmRlcUMHdrInfo
>>STI Current STI information
>>SN 10bit Sequence Number or 5bit Sequence number base
upon configuration.
>>FI Framing Info
(0(0x00) – PDU’s1 st Byte corresponding SDU’s 1 st Byte &
PDU’s last Byte corresponding SDU’s last Byte
1(0x01) – PDU’s1 st Byte corresponding SDU’s 1 st Byte &
PDU’s last Byte not corresponding SDU’s last Byte
8(0x10) - PDU’s1 st Byte not corresponding SDU’s 1 st Byte
& PDU’s last Byte corresponding SDU’s last Byte
16(0x11) - PDU’s1 st Byte not corresponding SDU’s 1 st
Byte & PDU’s last Byte not corresponding SDU’s last Byte)
>>E Extention Bit
5.7.3.11.4 Note
When 20 items are stored or RLC UM Tx or UM Rx Entity is released, it’s going to be displayed.
5.7.3.12.1 Menu
[Views->PS->RLC-> RLC Configuration]
Information
element/Group Description
name
txConfigParam
> Mode RLC Mode
> RBId Mapping RBId with the entity
> LCId Mapping LC Id with the entity
> PollPDU PDU transmission number for triggering polling
> PollByte Transmitted data byte number for triggering polling
Value of Poll Timer duration
> TmrPoll If value is 0, display “Disable”
Unit : msec
> MaxRetx Maximum retransmitted number of PDU
> SN_SIZE Sequence Number bit Size
5.7.3.12.4 Note
This Log Item information is updated below conditions when Tx Entity is established or released.
5.7.3.13.1 Menu
[Views->PS->RLC-> RLC Configuration]
Information
element/Group Description
name
numRB
number of established RLC tx entity
rtxConfigParam
> Mode RLC Mode
> RBId Mapping RBId with the entity
> LCId Mapping LC Id with the entity
> Value of StatusProhibit Timer duration
TmrStatusProhibit(unit) msec
Value of Reordering Timer duration
> TmrReordering
(unit) msec
> SN_SIZE Sequence Number bit Size
5.7.3.13.4 Note
This Log Item information is updated below conditions when Rx Entity is established or released.
5.7.3.14.1 Menu
[Views->PS->RLC-> RLC AM Nack Info]
Information
element/Group Description
name
Number of UL RLC aborts (aborts = MAX Retransmission).
> numAbort
This is accumulated value.
> numRB number of established RLC AM entity
> nackInfoParam
>> RBId Mapping RBId with the entity
>> Reserved
>> numTxNack Number of RLC Nack transmitted
>> numRxNack Number of RLC Nack received
5.7.3.14.4 Note
RLC collect NACK information whenever RLC AM entity receives or transmits NACK or Re-
establishment is triggered by max retransmission has been reached. When the periodic timer (1
sec) is expired or RLC AM entity is released, this log item is displayed into GUI.
5.7.4 MAC
5.7.4.1 MAC STATE
5.7.4.1.1 Menu
[Views->PS->MAC->MAC State]
Information
element/Group Description
name
Current State of MAC downlink
MacDlState
(0-NOT_CONFIGURED, 1-CONFIGURED)
5.7.4.1.4 Note
5.7.4.2.1 Menu
[Views->PS->MAC->RACH REQ Information]
Information
element/Group Description
name
TxTTI RACH transmit time
RetNum Retransmission Num
0: INITIAL
1: HANDOVER
2: UL DATA ARRIVAL
RachType
3: DL DATA ARRIVAL
4: SR MAX
5 : NO_SR_CONFIG
PreambleID Preamble Identity
RA_RNTI RACH RNTI
5.7.4.2.4 Note
5.7.4.3.1 Menu
[Views->PS->MAC->RACH RSP General Info]
Information
element/Group Description
name
RxSTI RACH response receiving time
Result RACH result(0: ACK, 1: NACK)
HeaderInfo RAR sub-header information
>RAPID Preamble Identity
>BI RACH Back-Off Index
RAR Payload RAR payload
>TA Timing Advance Command
>T_CRNTI Temporary C-RNTI
>MCS Truncated modulation and coding Scheme
>TPC TPC command for scheduled PUSCH
>HF Hopping Flag
>UlDelay Uplink transmission Delay
>CQIReq CQI Request
>RbAssign Fixed size resource block assignment
5.7.4.3.4 Note
5.7.4.4.1 Menu
[Views->PS->MAC->MAC DL Statistics]
Sum of MAC SDU is same as summation of totalSduCnt per LCID during 1sec.
Information
element/Group Description
name
accumSduCnt the accumulated number of received MAC SDU
MacDlSduInfo Structure type
5.7.4.4.4 Note
5.7.4.5.1 Menu
[Views->PS->MAC->MAC DL PDU]
Information
element/Group Description
name
numMacDlPdu number of received MAC DL PDU
MacDlPdu Structure type
>TB_Size Transport Block Size of MAC DL
>RxSTI Reception Time
>AntIdx Antenna number
>LogChID logical channel ID
>Length Length Field
5.7.4.5.4 Note
5.7.4.6.1 Menu
[Views->PS->MAC->MAC UL Statistics]
Sum of MAC SDU is same as summation of totalSduCnt per LCID during 1sec.
Information
element/Group Description
name
accumSduCnt the accumulated number of transmitting MAC SDU
MacUlSduInfo Structure type
5.7.4.6.4 Note
5.7.4.7.1 Menu
[Views->PS->MAC->MAC UL PDU]
Information
element/Group Description
name
numMacUlPdu number of received MAC UL PDU
reserved
MacUlPdu Structure type
CRNTI
5
PHR
BSR
6
PHR
7 CRNTI
BSR
PHR
5.7.4.7.4 Note
5.7.4.8.1 Menu
[Views->PS->MAC->MAC UL BO Info]
Information
element/Group Description
name
numMacUlBo number of received MAC UL BO
reserved
dmMacUlBo Structure type
0:TRANS, 1:NO_TRANS
>NumBo Number of BO
>BoTransBitwise BO location
>BoDbInfo Structure type
>>BO-ID Logical Channel Group Identity
>>BO-TotalBytes Total byte of BO
5.7.4.8.4 Note
5.7.4.9.1 Menu
[Views->PS->MAC->MAC UL Transmission]
Information
element/Group Description
name
SuccessCnt0 Success in 1st transmission
SuccessCnt1 Success in 1st re-transmission
SuccessCnt2 Success in 2nd re-transmission
SuccessCnt3 Success in 3rd re-transmission
SuccessCnt4 Success in 4th re-transmission
SuccessCnt5 Success in 5th re-transmission
SuccessCnt6 Success in 6th re-transmission
SuccessCnt7 Success in 7th re-transmission
SuccessCnt8 Success in 8th re-transmission
SuccessCnt9 Success in 9th re-transmission
SuccessCnt10 Success in 10th re-transmission
BadCnt Bad Count
5.7.4.9.4 Note
5.7.4.10.1 Menu
[Views->PS->PS Graph]
Information
element/Group Description
name
MacDlTotalBytes total byte of MAC DL PDU
MacUlTotalBytes total byte of MAC UL PDU
5.7.4.10.4 Note
5.7.4.11.1 Menu
[Views->PS->MAC->MAC HARQ ACK/NACK INFO]
Information
element/Group Description
name
numMacHqInfo number of received MAC UL BO
MacHqAckNackDb Structure type
5.7.4.11.4 Note
5.7.4.12.1 Menu
[Views->PS->PS Graph]
Information
element/Group Description
name
A number of total transport blocks per
Cwd0TBNum
1sec for code word #0
A number of transport blocks having
Cwd0ErrNum “max retrans” per 1sec for code word
#0
A number of total transport blocks per
Cwd1TBNum
1sec for code word #1
A number of transport blocks having
Cwd1ErrNum “max retrans” per 1sec for code word
#1
5.7.4.12.4 Note
5.7.4.13.1 Menu
[Views->PS->MAC->MAC UL PH Info]
Information
element/Group Description
name
numMacUlPh number of received MAC UL PH
dmMacUlPh Structure type
PH event type
0: PH_NO_EVENT
>Type 1: PH_THRESHOLD_EVENT
2: PH_PERIODIC_EVENT
3: PH_CONFIG_EVENT
5.7.4.13.4 Note
5.7.4.14.1 Menu
[Views->PS->MAC->MAC UL TA Info]
Information
element/Group Description
name
RxSTI TA Receiving Time
TA Received TA Value
Type RAR or MAC DL Control Element
Time_Duration TA Timer Duration
5.7.4.14.4 Note
5.7.4.15.1 Menu
[Views->PS->MAC->MAC Configuration Info]
Information
Description
element/Group name
INDEX Number of DM Items
5.7.4.15.4 Note
5.7.4.16.1 Menu
[Views->PS->MAC->MAC DRX Info]
Information
element/Group Description
name
dmMacDrxInfo Structure type
>RxSTI UL/DL Grant receiving time
DRX Event Type:
EventType Value
NO_EVENT 0x0
DRX_MODE_START 0x1
SR_TRIGGER 0x2
ONDURATION 0x4
INACTIVITY_UL 0x8
>Event Type INACTIVITY_DL 0x10
RETX_TIME_START 0x20
RETX_TIME_STOP 0x40
HARQ_RETX_UL 0x80
ONDURATION
INACTIVITY_UL
DRX STATE:
0 - ACTIVE
>DRX STATE
1 - DRX_1
2 - DRX_2
5.7.4.16.4 Note
5.7.5 NAS
5.7.5.1.1 Menu
[Views->PS->NAS-> Location Information of current cell R1]
Information
element/Group Description
name
GUTI Allocated GUTI
TAI[0] 1st registered TAI in TAI list
TAI[1] 2nd registered TAI in TAI list
TAI[2] 3rd registered TAI in TAI list
TAI[3] 4th registered TAI in TAI list
TAI[4] 5th registered TAI in TAI list
TAI[5] 6th registered TAI in TAI list
TAI[6] 7th registered TAI in TAI list
TAI[7] 8th registered TAI in TAI list
TAI[8] 9th registered TAI in TAI list
TAI[9] 10th registered TAI in TAI list
TAI[10] 11th registered TAI in TAI list
TAI[11] 12th registered TAI in TAI list
TAI[12] 13th registered TAI in TAI list
TAI[13] 14th registered TAI in TAI list
TAI[14] 15th registered TAI in TAI list
TAI[15] 16th registered TAI in TAI list
5.7.5.1.4 Note
This Item information is updated when the GUTI is reallocated.
5.7.5.2.1 Menu
[Views->PS->NAS-> Location Information of current cell R1]
Information
element/Group Description
name
PLMN ID PLMN ID of the current cell
TAC TAC of the current cell
Cell ID Cell ID of the current cell
5.7.5.2.4 Note
This Item information is updated when the serving cell is changed.
5.7.5.3.1 Menu
[Views->General->Signal Log Messages ]
Information
element/Group Description
name
Target 1(fixed value)
0: DL (Downlink)
Direction
1: UL (Uplink)
Length Length of the NAS message
Data Content of the NAS message
5.7.5.3.4 Note
To see the NAS message in the Log Message window, the NAS message should be checked in
the left side of the Log Message window.
5.7.5.4.1 Menu
[Views->PS->NAS-> NAS signaling failure]
Information
element/Group Description
name
NAS signalling failure cause value
- Establish_Fail_caused_by_lower_layer_failure
- Establish_Fail caused_by_cell_reselection,
- Establish_rejected_by_network,
- Release_with_cause_Other_by_network,
- Release_ with_cause _RRC_Connection_
Failure_by_network,
- Release_ with_cause _Load_Balancing_TAU_
NAS Signalling Required_by_network,
Failure - Release_ with_cause _Redirection_by_network,
- Data_transmission_Failure_casued_by_
RRC_mobility,
- Service_Loss,
- T3411_Attach_Attempt_Timer_Expiry,
- T3402_Attach_Attempt_Long_Timer_Expiry,
- T3410_Attach_Timer_Expiry,
- T3411_TAU_Attempt_Timer_Expiry,
- T3402_TAU_Attempt_Long_Timer_Expiry,
- T3430_TAU_Timer_Expiry,
- T3421_Detach_Timer_Expiry,
- T3417_Service_Request_timer_Expiry,
- T3418_AUTH_MAC_failure_timer_Expiry,
- T3420_AUTH_SYNC_failure_timerExpiry,
-
T3440_NAS_Signalling_connection_locally_releae_timer_Expiry
,
5.7.5.4.4 Note
This Item information is updated when the NAS signaling is released or the NAS timer is expired.
5.7.5.5.1 Menu
[Views->PS->NAS-> PDN Address R3]
Information
Description
element/Group name
PDN Address Allocated IP address
IPv4 Primary DNS Address IPv4 Primary DNS Address
IPv4 Secondary DNS Address IPv4 Secondary DNS Address
IPv6 Primary DNS Address IPv6 Primary DNS Address
IPv6 Secondary DNS Address IPv6 Secondary DNS Address
5.7.5.5.4 Note
This Item information is updated when IP address is configured.
5.7.5.6.1 Menu
[Views->PS->NAS-> ESM Instance Information R3]
Information
element/Group Description
name
epsId EPS ID
LBId Linked Bearer ID
PDNAddress Ex) 11.22.33.44
apn Ex) www.lge.com
QCI
epsType 0 : NONE BEARER TYPE
1 : DEFAULT_BEARER
2 : DEDICATED_BEARER
esmState 0 : DEACTIVE
1 : ACTIVE
PTI
instanceId Instance ID
deactivateMode 0: NONE_MODE,
1: NORMAL,
2: NORMAL_ALL,
3 :DETACH,
4 : STATUS_IND
5 : PDN_DISCONNECT
6 : PDN_DISCONNECT_REJECT
7 : PDN_DISCONNECT_TIMEOUT
8 : MODIFICATION_RJECT
9 : MODIFICATION_TIMEOUT
10 : OVERWRITE
11 : LOCALLY
overWriteMode 0 : NONE BEARER TYPE
1 : DEFAULT_BEARER
2 : DEDICATED_BEARER
5.7.5.6.4 Note
This Item information is updated when ESM instance is added, modified or removed.
5.7.5.7.1 Menu
[Views->PS->NAS-> Available PLMN List]
Information
element/Group Description
name
PLMN [0] MCC digit 2 + MCC digit 1
PLMN [1] MNC digit 3 + MCC digit 3
PLMN [2] MNC digit 2 + MNC digit 1
5.7.5.7.4 Note
This Item information is updated when equivalent PLMN list, forbidden PLMN list, equivalent
HPLMN list or available PLMN list is updated.
5.7.5.8.1 Menu
[Views->PS->NAS-> NAS Message Decoder]
5.7.5.8.4 Note
5.7.5.9.1 Menu
[Views->PS->NAS->NAS Sate R4]
Information
element/Group Description
name
Current state of EMM (EPS Mobility Management)
0: EMM_NULL
1: EMM_DEREGISTERED_INITIATED
2: EMM_DEREGISTERED_NORMAL_SERVICE
3: EMM_DEREGISTERED_LIMITED_SERVICE
4: EMM_DEREGISTERED_ATTEMPTING_TO_ATTACH
5: EMM_DEREGISTERED_PLMN_SEARCH
6: EMM_DEREGISTERED_NO_CELL_AVAILABLE
7: EMM_REGISTERED_INITIATED
8: EMM_REGISTERED_NORMAL_SERVICE
EMM state 9: EMM_REGISTERED_ATTEMPTING_TO_UPDATE
10: EMM_REGISTERED_LIMITED_SERVICE
11: EMM_REGISTERED_PLMN_SEARCH
12: EMM_REGISTERED_NO_CELL_AVAILABLE
13: EMM_TRACKING_AREA_UPDATING_INITIATED
14: EMM_SERVICE_REQUEST_INITIATED
15: EMM_WAIT_FOR_CONN_ESTABLISH_CNF
16: EMM_WAIT_FOR_ESM_RSP
17: EMM_DEREGISTERED_NO_IMSI
18: EMM_WAIT_FOR_USIM_RSP
19: EMM_WAIT_FOR_AVAILABLE_CELL
Current state of ECM (EPS Connection Management)
ECM state 0: ECM_IDLE,
1: ECM_CONNECTED
Current state of PLMN
0: PLMN_NULL,
1: PLMN_IDLE,
PLMN state 2: PLMN_PLMN_SEARCH,
3: PLMN_ON_PLMN,
4: PLMN_WAIT_FOR_EMM_IDLE,
5: PLMN_NOT_ON_PLMN,
Current EU (EPS Update) status
EMMCacheState
0: EMMCache_WAIT_FOR_CACHE_INIT,
1: EMMCache_VALID_USIM,
2: EMMCache_WAIT_FOR_REFRESH,
3: EMMCache_NO_USIM,
5.7.5.9.4 Note
This Item information is updated when EMM, ECM or PLMN state, or EMM Cache State are
changed.
5.7.6 RRC
5.7.6.1.1 Menu
[Views->PS->RRC-> Radio Problem cause]
Information
element/Group Description
name
0: MAC_RA_PROBLEM
- upon Random access problem indication from
MAC while neither T300, T301, T304 nor
T311 is running.
1: MAC_OUT_OF_SYNC
- upon TA timer expiry or SR Max transmission
indication from MAC
2: RLC_MAX_RST
- upon indication from RLC that the maximum
number of retransmissions has been reached
Radio Problem Cause
3: INTEGRITY_FAILURE
- upon integrity protection failure indication
from PDCP
4: T300_Expire
- upon T300 expiry (RRC Connection failure)
5: T301_Expire
- upon T301 expiry
(RRC Connection reestablishment failure)
6: T304_Expire
- upon T304 expiry (Handover failure)
7: T310_Expire
- upon T310 expiry (physical layer problem)
8: T311_Expire
- upon T311 expiry (cell selection failure for
reestablishment)
9: SRB_BUFFER_FULL
- When the L2 buffer for SRB is full.
10: TA_Expire
- upon TA timer expiry from MAC
11: SR_MAX_Transmission
- upon SR Max transmission
indication from MAC
5.7.6.1.4 Note
5.7.6.2.1 Menu
[Views->PS->RRC-> Cell Information]
Information
element/Group Description
name
Current UE state
- UE_IDLE_MODE
UE state - UE_CONNECTED_MODE
- UE_NO_SERVICE
- UE_NON_LTE_RAN
FREQ_UL Uplink Carrier Frequency (Unit : 100kHz)
FREQ_DL Downlink Carrier Frequency (Unit : 100kHz)
Cell ID Physical Cell Identity
Plmn Identity Plmn id
Global Cell ID Cell id in SIB1
TAC Tracking Area Code
5.7.6.2.4 Note
5.7.6.3.1 Menu
[Views->PS->RRC-> Cell reselection]
Information
element/Group Description
name
Old Freq DL Old Carrier Frequency (Unit : 100kHz)
Old Cell ID Old Cell Identity
New Freq DL New Carrier Frequency (Unit : 100kHz)
New Cell ID New Cell Identity
5.7.6.3.4 Note
This item can be displayed by 10 information
5.7.6.4.1 Menu
[Views->PS->RRC-> RRC Sub-Module States]
5.7.6.4.4 Note
5.7.6.5.1 Menu
[Views->PS->RRC-> Neighbor Cell Lists 2]
Information
element/Group Description
name
Freq DL Downlink Frequency (Unit : 100kHz)
Cell Indentity Physical Cell Identity
RSRP RSRP (Unit : dBM)
Reported RSRP The reported RSRP value according to the below
mapping table in 4.8.6.5.4 Note
RSRQ RSRQ (Unit : dB)
Reported RSRQ The reported RSRP value according to the below
mapping table in 4.8.6.5.4 Note
RSSI RSSI (Unit : dBM)
Cell Type 0 : serving cell
1 ; monitored cell
2 : detected cell
5.7.6.5.4 Note
Reported RSRP mapping table
5.7.6.6.1 Menu
[Views->PS->RRC-> RRC BCH Status]
Information
element/Group Description
name
5.7.6.6.4 Note
5.7.6.7.1 Menu
[Views->PS->RRC-> RRC Freq Scan Information]
Information
element/Group Description
name
Search Type Cell Search Method
- Frequency LIST
- Frequency RANGE
Freq DL Downlink Frequency (Unit : 100kHz)
FreqCellList
> numCell Number of scanned cell
> cell Id Physical Cell Identity
> rsrp Unit : dBm
5.7.6.7.4 Note
5.7.6.8.1 Menu
[Views->General->Signal Log Messages]
Information
element/Group Description
name
LOG TYPE Type of logical channel
0 – UL_CCCH
1 – UL_DCCH
2 – DL_CCCH
3 – DL_DCCH
4 – DL BCCH: PBCH
5 – DL BCCH: DL_SCH
6 – DL_PCCH
Direction
Uplink or Downlink
Message
RRC Message Type
5.7.6.8.4 Note
Information
element/Group Description
name
Handover Type 0 : LTE
1 : OUTBOUND_IRAT
2 : INBOUND_IRAT
Soruce cell Source Cell Physical Cell Identity
Target cell Target Cell Physical Cell Identity
Handover Delay Handover Delay (ms). Refer to 3GPP TS 36.133
for definition of handover delay (Dhandover)
Result Handover Result.
0: FAIL
(when T304 expires)
1 : SUCCESS
(when Connection Resolution is successful)
Refer to 3GPP TS 36.331 for detail information
5.7.6.9.4 Note
Information
element/Group Description
name
bandClass CDMA 2000 band class
0 : bc0
1 : bc1
…
17 : bc17
arfcn CDMA2000 frequency (0..2047)
phyCellId PN Offset (0..511)
pilotStrength [-2 x 10 log 10 Ec/Io] in units of 0.5dB (0..63)
5.7.6.10.4 Note
5.7.7 USIM
5.7.7.1.1 Menu
[Views->PS-> EMMUSIM Data]
[ EF_IMSI]
Information
element/Group Description
name
IMSI International Mobile Subscriber Identity
[ EF_AD]
Information
element/Group Description
name
0x00: normal operation,
0x80: type approval operations,
0x01: normal operation + specific facilities,
UE Operation Mode 0x81: type approval operations + specific
facilities,
0x02: maintenance (off line),
0x04: cell test operation
MNC length in the IMSI MNC length in the IMSI
[ EF_EPSLOCI]
Information
element/Group Description
name
GUTI Globally Unique Temporary Identifier
Last visited registered
Last visited registered TAI
TAI
EU1_UPDATED: The last attach or tracking area
updating attempt was successful.
EU2_NOT_UPDATED: The last attach, service
request or tracking area updating attempt failed
procedurally, i.e. no response or reject message
EPS update status was received from the MME.
EU3_ROAMING_NOT_ALLOWED: The last attach,
service request or tracking area updating attempt
was correctly performed, but the answer from the
MME was negative (because of roaming or
subscription restrictions).
[ EF_EPSNSC]
Information
element/Group Description
name
Key set identifier
Identifier of K_ASME
KSI_ASME
ASME key (K_ASME) Created key by a run EPS AKA
Uplink NAS count Uplink NAS count
Downlink NAS count Downlink NAS count
Identifiers of selected
NAS integrity Type of integrity protection algorithm
algorithms
Identifiers of selected
NAS encryption Type of ciphering algorithm
algorithms
5.7.7.1.4 Note
This Item information is updated when one of these EFs is updated in USIM.
5.7.7.2.1 Menu
[Views->PS->EMMNVM Data]
[ NVM_IMSI]
Information
element/Group Description
name
IMSI International Mobile Subscriber Identity
[ NVM_IMEI]
Information
element/Group Description
name
IMEI International Mobile Equipment Identity
[NVM_SW Version]
Information
element/Group Description
name
SW Version SW Version number
[NVM_DRX Value]
Information
element/Group Description
name
0: DRX value not specified by the MS
6: T = 32
7: T = 64
DRX Value
8: T = 128
9: T = 256
Others : DRX value not specified by the MS
Information
element/Group Description
name
0: Automatic network selection mode
PLMN Search Mode
1: Manual network selection mode
Information
element/Group Description
name
0: ESM information dose not need to be sent
security protected
ESM Information Flag
1: ESM information needs to be sent security
protected
[ NVM_EPSLOCI]
Information
element/Group Description
name
GUTI Globally Unique Temporary Identifier
Last visited registered
Last visited registered TAI
TAI
EU1_UPDATED: The last attach or tracking area
updating attempt was successful.
EU2_NOT_UPDATED: The last attach, service
request or tracking area updating attempt failed
procedurally, i.e. no response or reject message
EPS update status was received from the MME.
EU3_ROAMING_NOT_ALLOWED: The last attach,
service request or tracking area updating attempt
was correctly performed, but the answer from the
MME was negative (because of roaming or
subscription restrictions).
[NVM_EPSNSC]
Information
element/Group Description
name
Key set identifier
Identifier of K_ASME
KSI_ASME
ASME key (K_ASME) Created key by a run EPS AKA
Uplink NAS count Uplink NAS count
Downlink NAS count Downlink NAS count
Identifiers of selected
NAS integrity Type of integrity protection algorithm
algorithms
Identifiers of selected
NAS encryption Type of ciphering algorithm
algorithms
5.7.7.2.4 Note
This Item information is updated when one of these NVM item is updated in NV Memory.
5.7.8 Data
5.7.8.1.1 Menu
[Views PS Data Data Path Loss]
Information
Description
element/Group name
UINC_UsbBlockTime UL:USB Blocking time (ms)
UIINC_HimAllocFail UL:Memory allocation fail count in HIM
5.7.8.1.4 Note
Difference and Accumulation are updated every 1second.
5.7.8.2.1 Menu
[Views PS Data DIM Packet Filter Lists]
Information
Description
element/Group name
Default EPS Id
EPSId
It is displayed on Tab
index Tab index in which data is displayed
numPacketFilterList number of Packet filter list
Packet Filter List
> EPSId Dedicated EPS ID
> packetFilterId Packet Filter Id
> evalValue Evaluation Precedence value
> remoteIPv4 Remote IPv4 address
> subNetMaskIPv4 Remote IPv4 address subnet mask
> remoteIPv6 Remote IPv6 address
> subNetMaskIPv6 Remote IPv6 address subnet mask
> protocolId Protocol Id(IPv4) or
NextHeader(IPv6)
> singleLocalPort Single Local Port
> singleRemotePort Single Remote Port
> localPortRangeLow Low port number of local port range
> localPortRangeHigh High port number of local port range
> Low port number of remote port range
remotePortRangeLow
> High port number of remote port range
remotePortRangeHigh
> SPI Security Parameters Index
> typeOfService Type of service(IPv4) or Traffic Class(IPv6)
> typeOfServiceMask Type of service Mask(IPv4) or Traffic Class Mask(IPv6)
> flowLabel Flow Label
5.7.8.2.4 Note
This log item is updated whenever packet filter is added, replaced or deleted by ESM.
5.7.8.3.1 Menu
[Views PS Data DIM Statistics]
Information
Description
element/Group name
numIPv4 The number of valid elements of array for IPv4 tab.
numIPv6 The number of valid elements of array For IPv6 tab
ipv4Statistics DIM Statistics for IPv4
>EPSId EPS ID
>dimCnt
>> UL_Sent The number of packet sent on UL
>> DL_Rcvd The number of packet received on DL
ipv6Statistics DIM Statistics for IPv6
>EPSId EPS ID
>dimCnt
>> UL_Sent The number of packet sent on UL
>> DL_Rcvd The number of packet received on DL
5.7.8.3.4 Note
DIM increase the each count when it sends packet data to PDCP_UL or receives from PDCP_DL.
When the periodic timer (1 sec) is expired, this log item is displayed into GUI.