Beruflich Dokumente
Kultur Dokumente
V200R004C00
User Guide
Issue Draft A
Date 2011-06-07
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Preface
To improve the quality of version features, welcome to report feature comments to related
designers.
Feature Designer
If you have new requirements for the LTE UE, submit them to the LTE UE RAT requirement
management team through the RM platform at http://rm.huawei.com:8000/Agile/. For details
about RM operations, see section 9.25 “Using the RM Platform”.
If you have any questions in using the LTE UE, consult the version maintenance contact: Nie
Zhouyu (employee ID: 00108792).
Overview
This document describes the specifications, features, hardware installation, quick start,
software update, and basic operations of the LTE UE.
Product Version
The following table lists the product version related to this document.
LTE UE V200R004C00
Intended Audience
This document is intended for:
Development test engineers
Solution test engineers
Customer service engineers
Network planning and optimization engineers
Organization
1. Changes in the LTE UE User Guide
This chapter describes the changes in the LTE UE User Guide.
2 "Overview"
This chapter describes the LET UE, supported protocol specifications, UE specifications, and
RF indicators.
3 "Features"
This chapter describes the features of the LTE UE.
4 "Components"
This chapter describes the components of the LTE UE and the installation process of these
components.
5 "Quick Start"
This chapter describes the initial configuration of the UE, and assists you to quickly get
started for subsequent service tests.
6 "Software Update"
This chapter describes PC configuration requirements before LTE UE update, version
obtaining method, and OMT update and version update.
7 "Feature Guide
This chapter describes special features of the UE or the features newly added to the LTE UE
V200R004C00. These features include: special test, scanner, auto site test, remote test, multi
traffics, ETWS.
8 "FAQ"
This chapter describes some frequently asked questions (FAQs), such as the failed connection
between the OMT and a board, access, throughput, and handover.
9 "Appendix A Common Operations"
This chapter describes some common operations for your reference, such as the connection
between the Probe and UE, querying and modifying the maintenance IP address or host IP
address of the UE, checking hardware status, and configuring ARP and routes.
10 "Appendix B Feature Operations"
This chapter describes some precautions on operations related to UE features, such as settings
and observation points.
11 "Appendix C OMT Operations"
This chapter describes some OMT-related operations, such as UE operations, UE message
trace, log management, device management, integrated tools, data centers, file upload, UE
black boxes, alarm management, version management, serial port redirection, log redirection,
UE key performance indicators, and data capturing.
12 "Appendix D Terms and Definitions"
This chapter describes some LTE UE related terms that are used in the document.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows:
Symbol Description
Indicates a hazard with a high level of risk that, if not avoided,
will result in death or serious injury.
General Conventions
Convention Description
Command Conventions
Convention Description
GUI Conventions
Convention Description
Boldface Buttons, menus, parameters, tabs, windows, and dialog titles
are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"
signs. For example, choose File > Create > Folder.
Keyboard Operation
Format Description
Key Press the key. For example, press Enter and press Tab.
Mouse Operation
Action Description
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
Preface ......................................................................................................................................................ii
1 Changes in the LTE UE User Guide .............................................................................................. 1
2 Overview .............................................................................................................................................. 2
2.1 Product Profile ................................................................................................................................................. 2
2.2 Product Specifications ...................................................................................................................................... 3
2.2.1 Protocol Specifications............................................................................................................................ 3
2.2.2 UE Specifications .................................................................................................................................... 3
2.2.3 RF Indicators ........................................................................................................................................... 4
3 Features ................................................................................................................................................. 5
3.1 Features Supported by the UE .......................................................................................................................... 5
4 Components....................................................................................................................................... 13
4.1 Component Installation .................................................................................................................................. 13
4.1.1 UE Overview......................................................................................................................................... 15
7 Feature Guide.................................................................................................................................... 40
7.1 Special Test .................................................................................................................................................... 40
7.1.1 Overview ............................................................................................................................................... 40
7.1.2 Test Scenarios........................................................................................................................................ 40
7.1.3 Lock EARFCN...................................................................................................................................... 41
7.1.4 Lock Cell ............................................................................................................................................... 43
7.1.5 Lock PLMN .......................................................................................................................................... 45
7.1.6 CBA Invert ............................................................................................................................................ 46
7.1.7 Lock PUSCH Power ............................................................................................................................. 47
7.2 Scanner ........................................................................................................................................................... 49
7.2.1 Overview ............................................................................................................................................... 49
7.2.2 Test Scenarios........................................................................................................................................ 49
7.2.3 Cell Scan ............................................................................................................................................... 50
7.2.4 Frequency Scan ..................................................................................................................................... 57
7.3 Auto Site Test ................................................................................................................................................. 60
7.3.1 Overview ............................................................................................................................................... 60
7.3.2 Auto Site Test ........................................................................................................................................ 61
7.3.3 Presetting the Auto Site Test ................................................................................................................. 61
7.3.4 Performing and Observing the Auto Site Test ....................................................................................... 64
7.3.5 Exporting Result Details of the Auto Site Test ...................................................................................... 65
7.4 Remote Test .................................................................................................................................................... 67
7.4.1 Overview ............................................................................................................................................... 67
7.4.2 Remote Test ........................................................................................................................................... 67
7.4.3 UE Configuration and Debugging Before a Remote Test ..................................................................... 68
7.4.4 Remote Ping Test .................................................................................................................................. 70
7.4.5 Remote FTP Test ................................................................................................................................... 73
7.4.6 UE Connection and Control by the Remote Probe ................................................................................ 75
7.5 Multi Traffics.................................................................................................................................................. 76
7.5.1 Overview ............................................................................................................................................... 76
7.5.2 Dedicated Bearer-Related Configuration .............................................................................................. 76
7.5.3 PING ..................................................................................................................................................... 84
7.5.4 UDP Service .......................................................................................................................................... 84
7.5.5 VoIP ....................................................................................................................................................... 86
7.5.6 VOD ...................................................................................................................................................... 88
7.5.7 FTP........................................................................................................................................................ 90
7.6 ETWS ............................................................................................................................................................. 91
8 FAQ ...................................................................................................................................................... 95
8.1 OMT Connection Failure ............................................................................................................................... 95
8.2 Access Problems............................................................................................................................................. 99
8.2.1 Cell Search Failure ................................................................................................................................ 99
8.2.2 UE Access Failure ................................................................................................................................. 99
8.3 Throughput Problem....................................................................................................................................... 99
8.4 Handover Problems ...................................................................................................................................... 100
8.4.1 Handover Failure................................................................................................................................. 100
8.4.2 Handover Failure................................................................................................................................. 100
Figure
Table
Draft A (2011-06-07)
This is the draft.
2 Overview
UE category Cat4
TDD subframe SA0, SA1, SA2, SA5
assignment
TDD special subframe SSP4, SSP5, SSP7
patterns
2.2.2 UE Specifications
Table 2-2 UE specifications
2.2.3 RF Indicators
Table 2-3 RF indicators of the UE
3 Features
GPS receiver The UE has a built-in GPS receiver to Inherited For details, see Section 10.3
provide three-dimensional position "GPS Receiver."
information and global synchronization
time.
Operating multi-band: This feature enables the UE to operate Inherited N/A
900 M/2600 M on two different frequency bands.
Currently the UE supports 900 M (Band
8) and 2.6 G (Band 7). When the UE
Manual Dial With this feature, a subscriber can use Inherited For details, see section 9.5
the OMT to manually dial a number to "Powering on the UE."
initiate the access.
Auto Dial With this feature, the UE can Inherited N/A
automatically connect to the network
after the UE is powered on, and
automatically reconnect to the networks
after network disconnection, without the
need of manual intervention. With this
feature, a UE can serve as an
independent transmission device for
such scenarios as video surveillance.
Local maintenance of This feature enables local UE Enhanced Currently the UE does not
OMT management by using the OMT. support management on the
M2000. For use of the OMT,
see section 6.3 "OMT."
Software management This feature supports functions such as Enhanced For details, see section11.10
software version query, version check "Version Management."
and version update of UEs.
Configuration This feature supports online Enhanced For details, see section 11.1
management configuration, including UE "UE Operations" and section
management and maintenance, and file 11.7 "File Transfer."
management.
Performance This feature provides multiple methods Enhanced The monitored UE
management for monitoring UE performance. performance includes:
latency statistics,
performance monitoring,
recording time points for
sending air messages, cell
measurement, camp cell
information, CQI, MCS, and
power balance. For details,
4 Components
7 Two-in-one 1 Required The serial port connector of the two-in-one cable has the
cable same appearance as the Ethernet port connector. Connect
the cables by referring to the cable labels. Network cable
label: Ethernet. Serial port cable label: NBBI-Debug.
8 Network cable 1 Required The network cable is a common gigabit network cable
with RJ45 connectors at both ends.
Connect one end of the network cable to the FE/GE port
of the UE, and the other end to the Ethernet port of a PC.
9 Serial port 1 Optional The serial port cable has an RJ45 connector at one end,
cable and a DB9 male connector at the other end.
Connect the RJ45 connector of the serial port cable to the
NBBI-Debug port of the two-in-one cable, and the DB9
male connector to the serial port of the PC.
The serial port cable is used for UE commissioning.
Do not insert a network cable into the ETH port on the panel of the UE, otherwise, the transmit/and receive
loopback of the serial port may cause board fault.
4.1.1 UE Overview
Figure 4-2 UE panel
The UE works normally if the green RUN indicator blinks at 0.5Hz (at an interval of one
second) and the ALM indicator is steady off. Table 4-3 lists the indication of UE indicators.
5 Quick Start
Procedure
1. Install UE components. For details, see section 5.2 "Installing UE Components."
2. Insert a USIM. For details, see section 5.3 "Installing the USIM."
If no USIM is available, use a soft USIM. For details, see section 9.17 "UE Initial Configuration for Soft
USIM."
A USIM does not support hot swapping. Restart the UE after a USIM is inserted or removed.
3. Turn the switch on the back panel of the UE to ON. For details, see section 5.4 "Switching on
the UE."
4. Set the network adapter of the PC to obtain an IP address automatically. For details, see
section 5.5 "Setting the Network Adapter of the PC to Obtain an IP Address Automatically."
5. Install the OMT. For details, see section 5.6 "Installing the OMT."
6. Power on the UE for network access. For details, see section 5.7 "Powering on the UE for
Network Access."
For the use of the UE for the first time, the UE automatically searches all frequency bands (frequency
settings are not required). This process may take a long time. Please wait patiently.
7. Verify the UE. For details, see section 5.8 "Running the Ping Command."----End
Follow-up Operations
Now you can test the features of the UE. For details, see Table 3-1.
----End
Figure 5-4 Setting the network adapter of the PC to obtain an IP address automatically
----End
II. Procedure
1. Double-click the setup package of the OMT, as shown in Figure 5-6.
4. If the connection icon on the OMT becomes , the connection between the OMT and
UE is set up successfully.
5. If the OMT displays a wrong version, update the version of the UE. For details, see section
6.4.3 "UE Version Update."
----End
Figure 5-9 Running log after network access (OAM link over GE port)
For networking in the mode of OAM link over ETH port or PCs with dual network adapter, manually set
network parameters according to the printed running logs on the OMT, as shown in Figure 5-10. For
manual settings, see section 9.9 "Setting the ARP Manually", section 9.10 "Setting the Route Manually"
and section 9.6 "Setting the IP Address of Service Network Adapter Manually."
Figure 5-10 A message prompting manual configuration of network parameters in the running log
----End
6 Software Update
6.3 OMT
The OMT is an operation and maintenance tool designed for development engineers, test
engineers, and network planning and optimization engineers to operate the LTE UE. You can
use the OMT to perform functions such as version update and UE operation and maintenance.
1 Title bar Displays the IP address, port and duplex mode of the current
UE.
2 Menu bar Provides system menus.
3 Tool bar Provides shortcut icons of the system, including (from left to
right): Connect UE/Disconnect UE, Power On/Power Off,
Reaccess, Trace, UE Operate, Device, SeriesPort, Log and
ETWS.
4 Alarm Info Displays the current alarms. When an alarm occurs, the alarm
severity (Critical, Major, Minor, or Warning) is
highlighted.
UE Operation Refers to common operations of the UE, For details, see section
including Remote Test, Auto Site Test 11.1 "UE Operations."
and System Config.
UE Message Trace Monitors air messages, inter-stratum For details, see section
messages, and key events used for service 11.2 "UE Message
interaction of the UE, so that the technical Trace."
support engineers can use these messages
for future analysis.
Log Management Three types of OMT logs are available: For details, see section
OMT running logs, protocol stack service 11.3 "Log
logs, and operation logs. The OMT Management."
records and uploads related logs so that
the technical support engineers can use
the logs for future analysis.
Device Device management is used to monitor For details, see section
Management the CPU, memory, and threads on the UE 11.4 "Device
board in real time. Management."
Integrated Tool The integrated tool is used to add other For details, see section
external tools on the OMT to facilitate 11.5 "Integrated Tool."
tests and performance monitoring. The
integrated tool includes the Set External
Tool and internal FtpServer, TTI
Analysis.
Data Center The data center is used to save the For details, see section
configuration of the LTE UE. The OMT 11.6 "Data Center."
supports the functions of Data Back Up
Or Restore and Restore Settings Before
Delivery.
File Upload The function is used to obtain the required For details, see section
files from the UE to the PC through the 11.7 "File Transfer."
OMT.
UE Blackbox A UE automatically saves related For details, see section
information in blackbox files if an 11.8 "UE Blackbox."
exception occurs. This function is used to
upload blackbox files.
Alarm The function is the core part of the For details, see section
Management network fault management. Maintenance 11.9 "Alarm
engineers can know the actual running Management."
status of the system through alarms and
solve the related problems.
Version The function is used for version query, For details, see section
Management version verification, version update, and 11.10 "Version
version backup of the UE. Management."
Serial Port The function is used to perform related For details, see section
Redirection commands at the serial port by using the 11.11 "Serial Port
debug Ethernet port connected to the UE Redirection."
using the Telnet.
Log Redirection The function is used to display the For details, see section
operation logs, running logs, and debug 11.12 "Log
logs in the log redirection window in real Redirection."
time.
KPI of UE The function is used to collect the latency For details, see section
data of the UE, monitor the UE 11.13 "UE Key
performance indicators, cell information, Performance Indicator."
baseband CQI and MCS information, and
obtain real-time power balance.
Data Capture of The function is used to export data For details, see section
the UE according to preset stop conditions for 11.14 "Data Capture."
development or test engineers to analyze
the exported data.
Manage PIN The OMT supports the PIN management For details, see section
function to protect the USIM from being 11.15 "PIN
used by unauthorized users. Manage PIN Management."
includes Enable/Disable PIN, Modify
PIN, Validate PIN, and Unlock PIN.
For UE software loading, the OMT version must match the UE version; otherwise,
unpredictable result may occur.
----End
You can change the host IP addresses of multiple UEs to the IP address of one PC so that you can use
one PC to update these UEs.
Prerequisite
The setup program of the OMT is available.
No OMT is installed in the PC or the OMT has been uninstalled.
Procedure
1. Double-click to run the setup package of the OMT, as shown in Figure 6-3.
Full Installation: The OMT applications and common configuration files are installed.
Just Application: All program files except common configuration files are installed.
Custom Installation: You can select or clear a component by selecting the check box before the prompt
option according to actual requirements.
8. Click Install. The setup dialog box is displayed, as shown in Figure 6-7.
If a message is displayed saying "Your PC need JRE, please install it step by step." Click OK. The JRE
setup dialog box is displayed. Complete the installation of the JRE.
1. After OMT installation, double-click on the desktop. The User Login dialog box is
displayed. Enter the maintenance IP address of the UE. Then click Login.
2. If the connection icon on the OMT becomes , the connection between the OMT and
UE is set up successfully.
The default maintenance IP address of the UE is 192.168.0.79.Before login, you can connect to the
serial port of the UE using the hyper terminal of the Windows operating system (for details, see
section 9.13 "Connecting to the Serial Port of the UE Using the Hyper Terminal of Windows"). Run
the version command to query the maintenance IP address of the UE.
After login, you can change the maintenance IP address of the UE. For details, see section 9.3
"Querying and Modifying the Maintenance IP Address and Host IP Address of the UE."----End
Procedure
1. On the main interface of the FTP tool, choose Security > Users/rights….
2. The User/Rights Security Dialog dialog box is displayed. Click New User….Enter the user
name and password. The user name and password are those of the board queried on the UE
serial port. (For details, see section 9.16 "Querying the User Name and Password of the UE
Board"). Then click Done.
If a user name already exists, do not create a user; however, the password must be correct.
The default user name for the FTP tool of the UE is hbbi, and the password is hbbi.
After you complete FTP settings, no setting is required during the next update if the corresponding
user name is not deleted.
----End
2. The Update the version dialog box is displayed. Click Browse… to select the path of the
version (select the BBI folder). Then click OK.
3. To update all files, click Select All in the Update the version dialog box. All files are
selected. To replace some files, select these files, and then click Update.
4. The use of the OMT to update the UE version may take several minutes. Please wait. Do not
perform any operation on the UE before the update is complete.
5. Click Make Sure in the Alert dialog box to update the second bootrom.
6. After the update, an Alert dialog box is displayed, prompting you to reboot the UE. Click OK.
The UE reboots automatically.
7. After the reboot, click Connect UE on the toolbar to set up the connection between the OMT
and UE. If the icon becomes Disconnect, the connection between the OMT and UE is set up
successfully.
----End
7 Feature Guide
CBA Invert When a cell is set to the For details, see section 7.1.6
access-prohibited mode "CBA Invert."
(that is, the cell is set as a
barred cell), this function
forcibly removes limitation
of the barred cell. In this
way, the UE can camp on
the barred cell for further
access.
For details about Probe update, see the GENEX Probe User Guide.
For Probe documents, see http://support.huawei.com/support.
For details about connection setup between the Probe and UE, see section 9.1 "Connection between the
Probe and UE."
Power off the UE on the OMT before configuring a special test on the Probe.
2. In the LTE Forcing Feature dialog box, select Lock EARFCN from the Function Select:
drop-down list box, set the frequency to be locked in EARFCN, and then click Apply.
3. After you click Apply, a Probe dialog box is displayed, prompting you that the configuration
takes effect at the next power-on, as shown in Figure 7-3.
4. Click on the OMT to power on the UE. In this case, the UE is locked on the
specified frequency.
5. When the locking function is not required, click on the OMT to power off the UE
and then click Reset in the LTE Forcing Feature dialog box of the Probe. If the unlocking
operation succeeds, the UE is not locked on the specified frequency at the next power-on.
Observation Method
Choose View > LTE > Serving and Neighboring Cells and double click on the Probe to
observe whether the UE always camps on the locked frequency.
3. After you click Apply, a Probe dialog box is displayed, prompting you that the configuration
takes effect at the next power-on, as shown in Figure 7-7.
4. Click on the OMT to power on the UE. In this case, the UE is locked on the
specified cell.
5. When the locking function is not required, click on the OMT to power off the UE
and then click Reset in the LTE Forcing Feature dialog box. If the unlocking operation
succeeds, the UE is not locked on the specified cell at the next power-on.
Observation Method
Choose View > LTE > Serving and Neighboring Cells and double click on the Probe to
observe whether the UE always camps on the locked cell.
3. After you click Apply, the configuration takes effect at the next power-on.
4. Click on the OMT to power on the UE. In this case, the UE is locked on the
specified PLMN.
5. When the locking function is not required, click on the OMT to power off the UE
and then click Reset in the LTE Forcing Feature dialog box. If the unlocking operation
succeeds, the UE is not locked on the specified PLMN at the next power-on.
Observation Method
Choose View > LTE > UE State and double click on the Probe to observe whether the UE
always camps on the locked PLMN.
3. Click on the OMT to power on the UE. In this case, the UE can access the barred
cell.
4. When the CBA Invert function is not required, click on the OMT to power off the
UE and then click Reset in the LTE Forcing Feature dialog box. In this way, the UE can
restore normal protocol behaviors at the next power-on.
Observation Method
If the UE successfully camps on the cell, you can see camp on suitable cell in the Key
Events column.
After you forcibly remove the barred attribute of a cell, the UE can successfully camp on the cell. If
related limitation is set on the eNodeB, the UE access may be rejected. If no limitation is set on the
eNodeB, the UE can access successfully.
2. In the LTE Forcing Feature dialog box, select Lock PUSCH Power from the Function
Select: drop-down list box, set the PUSCH power in the Setting area, and then click Apply.
Observation Method
Choose View > LTE > Radio Parameters and double click on the Probe. The Radio
Parameters window is displayed. Observe whether PUSCH Power equals the locking value.
7.2 Scanner
7.2.1 Overview
Scanner indicates scanner functions provided by the UE, including cell scan and frequency
scan. Cell scan indicates that the UE scans cell information on a specified frequency band or
frequencies. The UE reports the scanned cell information such as RSRP and RSRQ to the
Probe for subscriber viewing and further analysis. Frequency scan indicates that the UE
reports the scanned frequency power to the Probe.
Cell scan on a specified frequency band stops after it is carried out once.
1. Start the Probe and press F9. The Test Plan Control window is displayed. Select Cell Scan,
as shown in Figure 7-15.
2. On the right pane, select Spec Band in Cell Scan Type and enter the start and end
frequencies of cell scan in Low Band and High Band, as shown in Figure 7-16.
Make sure that the entered frequencies are in the range of frequencies of the band supported by the UE.
You can view the frequency band and the range of frequencies currently supported by the UE on the
OMT. For details, see section9.4.2 "Querying Hardware Information about the UE."
3. Choose View > LTE > Cell and Frequency Measurement > Cell Scan and double click.
The Cell Scan window is displayed on the right.
4. Click in the Test Plan Control window to start cell scan. If no records are saved
previously, a dialog box is displayed. To save data, click Yes; otherwise, click No.
5. When cell scan succeeds, Cell Search Success… is returned on the status bar of the Test
Plan Control window. In addition, you can see cell information on the specified frequency
band in the Cell Scan window.
6. Click in the Test Plan Control window to stop cell scan. The button becomes
.
Cell scan on specified frequencies works cyclically until you stop it manually.
1. Start the Probe and press F9. The Test Plan Control window is displayed. Select Cell Scan,
as shown in Figure 7-15.
2. On the right pane, select Spec Freq in Cell Scan Type, set the number of frequencies to be
scanned (up to three) in FreqCount, and set the frequency to be scanned in SpecFreq1.
3. Choose View > LTE > Cell and Frequency Measurement > Cell Scan and double click.
The Cell Scan window is displayed on the right.
4. Click to start cell scan. If no records are saved previously, a dialog box is displayed. To
save data, click Yes; otherwise, click No.
5. When cell scan succeeds, Cell Search Success… is returned on the status bar of the Test
Plan Control window. In addition, you can see neighboring cell information on the specified
frequency in the Cell Scan window.
6. Click in the Test Plan Control window to stop cell scan. The button becomes
.
1. Start the Probe and press F9. The Test Plan Control window is displayed. Select Cell Scan,
as shown in Figure 7-15.
2. On the right pane, select Fast Cell Scan in Cell Scan Type, set the frequency of the cell to be
fast scanned in DL EARFCN, set the cell bandwidth in DL Band Width, and set the number
of transmitting antennas of the eNodeB in eNodeB Tx Antenna Number.
4. Click in the Test Plan Control window to stop fast cell scan. The button becomes
.
5. Click to disconnect the connection between the UE and Probe. Choose Logfile >
Export Data… to export the previously saved data.
6. Select CSV and click Next > in the displayed dialog box, as shown in Figure 7-24.
7. Select the previously saved *.gen file, set the location of the destination file, and then click
Next > in the displayed dialog box, as shown in Figure 7-25.
8. Select Fast Cell Scan and click Next > in the displayed dialog box, as shown in Figure 7-26.
10. Click Yes in the displayed dialog box. The window turns to the generated file (.csv).
Frequency scan of the TDD is subject to uplink and downlink sub-frames, so it will not be successful to
scan frequency every time.
3. Choose View > LTE > Cell and Frequency Measurement > Frequency Scan and double
click. The Frequency Scan window is displayed on the right.
4. Click to start frequency scan. A dialog box is displayed, as shown in Figure 7-32. To
save data, click Yes; otherwise, click No.
5. When frequency scan succeeds, Scan Success… is returned on the status bar of the Test Plan
Control window. In addition, you can see the frequency power of the serving cell in the
Frequency Scan window. The horizontal axis indicates the frequency and the vertical axis
indicates the power value (dbm).
6. Click in the Test Plan Control window to stop frequency scan. The button
becomes .
Make sure that the entered frequencies are in the range of frequencies of the band supported by the UE.
You can view the frequency band 9.4.2 "Querying Hardware Information about the UE. "
3. Choose View > LTE > Cell and Frequency Measurement > Frequency Scan and double
click. The Frequency Scan window is displayed on the right.
4. Click to start frequency scan. A dialog box is displayed, as shown in Figure 7-32. To
save data, click Yes; otherwise, click No.
5. When frequency scan succeeds, Scan Success… is returned on the status bar of the Test Plan
Control window. In addition, you can see the frequency power of the serving cell in the
Frequency Scan window. The horizontal axis indicates the frequency and the vertical axis
indicates the power value (dbm).
6. Click in the Test Plan Control window to stop frequency scan. The button
becomes .
Procedure
1. Customer service engineers preset the auto site test. For details, see section 7.3.3 "Presetting
the Auto Site Test."
2. Hardware installation engineers perform and observe the auto site test. For details, see section
7.3.4 "Performing and Observing the Auto Site Test."
3. Customer service engineers export result details of the auto site test. For details, see section
7.3.5 "Exporting Result Details of the Auto Site Test."
----End
2. Configure a test plan as required in the displayed Configure Test Plan dialog box, as shown
in Figure 7-37. For meanings of setting items, see Table 7-3. After the setting is complete,
click OK.
Table 7-3 Description of setting items in the auto site test plan
3 FTP server Server indicates the IP address of the FTP server. User Name
related settings and Password indicate the user name and password of the
FTP server.
4 FTP related FTP Send Window and FTP Receive Window indicate the
settings sizes of FTP send and receive windows. MTU indicates the
maximum transmission unit. FTP Send Window and FTP
Receive Window supported by the UE are up to 128K
currently (64K or 128K is recommended).
6 Ftp Download Download File indicates the download path of the server (./
indicates the FTP release directory). Test Time indicates the
time length of test (in units of minutes). Threshold indicates
the minimum downlink traffic allowed for test success. In the
scenario of auto site test, up to 70M downlink traffic is
supported.
7 Ftp Upload Remote Path indicates the upload path of the server (./
indicates the FTP release directory). Test Time indicates the
time length of a test (in units of minutes). Threshold
indicates the minimum uplink traffic allowed for test success.
In the scenario of auto site test, up to 30M uplink traffic is
supported.
It is not necessary to select a test file for uploading when you test the Ftp Upload function. The UE
automatically creates a file for test.
3. Click the Common tab on the left pane of the OMT and choose System Config > Mode, as
shown in Figure 7-38.
4. In the displayed UE Configuration dialog box, click Model Config, select Auto Site Test,
and then click OK, as shown in Figure 7-39.
5. To ensure that the traffic meets requirements, synchronously modify the size of the FTP
send/receive window and the MTU of the FTP server. In addition, make sure that Download
File and Remote Path set in step 2 exist on the server. If they do not exist, add them on the
server.
It is recommended that IIS of Windows not be used as the FTP server because IIS does not
support download of large size files.
When you modify the size of the FTP send/receive window and the MTU, make sure that the
settings on the server are larger than or equal to those on the UE mentioned in step 2.
For details about modifying the size of the send window of the server, see section 9.22 "Setting the
Size of the FTP Transmitting Window."
For details about modifying the size of the receive window of the server, see section 9.23 "Setting
the Size of the FTP Receiving Window."
For details about modifying the MTU of the server, see section 9.24 "Setting the MTU."
The UE location is related to the test result. Therefore, hardware test engineers must not place the UE in
a cell not to be tested or at the edge of two cells when it is necessary to place the UE in a cell to be
tested.
3. If the UE successfully accesses the network and meets test conditions, the UE enters the
service test state. If the UE successfully accesses the network but does not meet test
conditions, the UE enters the wait-for-test state. You can observe status indicators of the UE.
Table 7-4 lists meanings of the status indicators.
Table 7-4 Meanings of status indicators in the auto site test state
To be accessed The UE does not The RUN indicator blinks at 0.5 Hz (at an
access the network. interval of one second) and the ALM
indicator is off.
Wait for test The UE does not meet The RUN indicator is off and the ALM
test conditions. indicator blinks at 0.5 Hz.
Service test The UE is performing The RUN indicator blinks at 4 Hz and the
the service test. ALM indicator is off.
Test completion The UE completes the Test success: The RUN indicator is
test. constantly on and the ALM indicator is off.
Test failure: The RUN indicator is off and the
ALM indicator is constantly on.
2. Select the files to be exported, click Browse to select a storage location, and then click
Export, as shown in Figure 7-41. In this case, the test files are exported to the selected folder.
All the test data is stored in Excel file format. The naming rule of the files is: Global Cell ID (GCI) +
GCI of the tested cell + test type + test number.
3. View the test report. The test report contains the summary result of this test in two aspects.
One is the test environment information, including the UE IP, tested frequency, GCI and PCI
of the tested cell, SINR, and RSRP. The other is the test result information, including the
maximum PING delay, minimum PING delay, average PING delay, and PING success rate
(taking the PING test as an example).
4. View the detailed test records. Taking the PING test data as an example, the detailed test
result includes times of the PING tests, server IP of the PING test, size of the pinged packet,
delay of each PING test, and result of each PING test.
If a dedicated control PC does not exist, you can use the server at the gateway side.
Procedure
1. Perform UE configuration and debugging before a remote test. For details, see section 7.4.3
"UE Configuration and Debugging Before a Remote Test."
2. Perform a remote PING test. For details, see section 7.4.4 "Remote Ping Test."
3. Perform a remote FTP test. For details, see section 7.4.5 "Remote FTP Test."
4. Currently, only PING and FTP services are supported in remote test scenarios.
----End
Procedure
1. Complete networking debugging of the UE to make sure that the PING operation succeeds.
For details, see chapter 5 "Quick Start."
2. (Optional) Click the Debug tab on the left pane of the OMT and choose Debug Command >
Remote Test > CFG REMOTE TEST and double click. On the UE Operation tab page, set
PingCacheSwitch and FtpCacheSwitch to Open, and then click Send Cmd.
3. Click the Common tab on the left pane of the OMT and choose Remote Test > Server
Config, as shown in Figure 7-45.
4. In the displayed Server Config dialog box, enter the IP address of the remote server and click
Apply.
Remote control PC: Indicates the control PC connected to the core network.
5. Choose System > UE Configuration > Model Config on the local OMT. Select Remote
Test and click OK.
6. In the displayed dialog box, click OK to reboot the UE. The UE automatically accesses the
network after reboot.
----End
Prerequisite
The OMT is installed on the remote control PC. For details, see section 6.4.2 "OMT
Installation."
The UE is powered on.
Procedure
1. Run the OMT on the control PC, enter the UE IP, and click Login. In the remote mode, the
UE automatically sets the UE IP to its service IP. Therefore, the UE IP here is the service IP
of the UE allocated by the core network.
After connecting the remote OMT to the UE, you can perform related operations in the same way as
locally, such as transparent command sending, file upload, version update, and serial port redirection.
2. Click the Common tab on the left pane of the OMT and choose Remote Test > Ping Test.
3. In the displayed Ping Test dialog box, set the IP address of the server to be tested, PING
packet size, and test times in Parameter config (up to 10 PING test tasks can be set), and
then click Config.
5. Click Begin(B) in the Ping Test dialog box. The UE starts the Ping test. You can see the
current test result in the Test result area.
----End
Prerequisite
The OMT is installed on the remote control PC.
The FTPServer is started on the remote control PC, the related user is added, and the
related access directory is set.
The UE is powered on and the remote OMT is connected to the UE.
Procedure
1. Click the Common tab on the left pane of the OMT and choose Remote Test > Ftp Test, as
shown in Figure 7-54.
2. In the displayed FTP Test dialog box, enter the IP address of the server, user name and
password of the FTP server, remote file path, remote file name, and test times, and then click
Config, as shown in Figure 7-55.
During the FTP test, the user name and password configured on the OMT must be consistent with those
of the FTP server set on the remote server. In addition, the remote file path and remote file name must
exist on the remote server.
3. Click Begin(S). You can see the FTP test result in the Test result area, as shown in Figure
7-56.
----End
Prerequisite
The Probe is installed on the remote control PC.
Procedure
1. Connect the remote Probe to the UE. For details, see section 9.1 "Connection between the
Probe and UE."
2. Enable the monitoring function of the Probe to be viewed. The operation is the same as that
on a local end.
Neighboring cell scan and frequency scan by using the remote Probe are performed in the same way as
the local end. Differently, the local scan is performed cyclically; however, the remote scan is performed
only once.
QCI Indicates the QoS class It ranges from 1 to 9. Values 1-4 refer to
ID. GBR services and values 5-9 refer to
NON-GBR services.
QCI is one of the most important QoS parameters for the EPS bearer. It is a quantity class, indicating the
QoS features that the EPS must provide for the SDF. Each SDF is associated with only one QCI. If
multiple SDFs corresponding to the same IP-CAN session have the same QCI and ARP, they can be
handled as an independent service set, which is called SDF set. Table 7-6 lists the standard QCI
attributes defined by the EPS system. All the QCI attributes can be preset by the carrier on the eNodeB
as required. These parameters determine the allocation of bearer resources.
The CID of a dedicated bearer must be consistent with the CID set in the previous parameter
configuration.
2. When a dedicated bearer is successfully set up, you can see the following two messages
among air interface messages of the OMT. Double-click a message to check whether the
current settings are correct.
The CID of a released bearer must be the same as that of the bearer when it is set up. For example, if the
CID of a dedicated bearer is set to 3 when it is set up, the CID must also be set to 3 when it is released.
2. After the bearer is released, you can see the following two messages among air interface
messages of the OMT.
The CID of a modified bearer must be the same as that of the bearer when it is set up. For example, if
the CID of a dedicated bearer is set to 3 when it is set up, the CID must also be set to 3 when it is
modified.
7.5.3 PING
Prerequisite
Customer service engineers have completed installation and verification of the UE. For
details, see 5 "Quick Start."
Procedure
1. Power on the UE and the UE accesses the network successfully.
2. (Optional) To perform the ping service on a dedicated bearer, perform the dedicated bearer
related configuration. For details, see section 7.5.2 "Dedicated Bearer-Related Configuration."
3. Perform the ping operation. For details, see section 5.8 "Running the Ping Command."
4. (Optional) If a service is provided on a dedicated bearer, observe whether the service is
properly transmitted on the dedicated bearer by using the Probe. For details, see section 9.24
"Setting the MTU."
Prerequisite
Installation and verification of the UE are completed. For details, see chapter 5 "Quick
Start."
The packet sending tool gperf.exe is installed on the PC connected to the UE.
Procedure
1. Power on the UE and the UE accesses the network successfully.
2. (Optional) To perform the UDP service on a dedicated bearer, perform the dedicated bearer
related configuration. For details, see section 7.5.2 "Dedicated Bearer-Related Configuration."
Prerequisite
Installation and verification of the UE are completed. For details, see 5 "Quick Start."
The packet injection tool gperf.exe is installed on the server.
Procedure
1. Power on the UE and the UE accesses the network successfully.
2. (Optional) To perform the UDP service on a dedicated bearer, perform the dedicated bearer
related configuration. For details, see section 7.5.2 "Dedicated Bearer-Related Configuration."
If the service is performed on a dedicated bearer, the service IP address of the packet injection object
must be consistent with RmtIpv4Address set in TFT parameters of the dedicated bearer. The port
number for packet injection must be in the range between LcPortHighLimit and LcPortLowLimit set
in TFT parameters of the dedicated bearer.
7.5.5 VoIP
Prerequisite
Installation and verification of the UE are completed. For details, see 5 "Quick Start."
The Microsoft Portrait is installed on the server PC and the PC connected to the UE.
Procedure
1. Power on the UE and the UE accesses the network successfully.
2. (Optional) To perform the VoIP service on a dedicated bearer, perform the dedicated bearer
related configuration. For details, see section 7.5.2 "Dedicated Bearer-Related Configuration."
3. Double-click the Microsoft Portrait. A dialog box is displayed. Enter the IP address to be
called and click Call. As shown in Figure 7-68, set the IP address to be called to 172.21.64.3.
If the service is provided on a dedicated bearer, the IP address to be called must be consistent with
RmtIpv4Address set in TFT parameters of the dedicated bearer.
4. After you click Call, a dialog box displayed, as shown in Figure 7-69.
5. At this time, a dialog box is displayed on the server, as shown in Figure 7-70. Click Accept to
accept this call.
7.5.6 VOD
Prerequisite
Installation and verification of the UE are completed. For details, see 5 "Quick Start."
The VOD server is installed on the server PC. The following takes the Windows Media
Player as an example.
Procedure
1. Power on the UE and the UE accesses the network successfully.
2. (Optional) To provide the VOD service on a dedicated bearer, perform the dedicated bearer
related configuration. For details, see section 7.5.2 "Dedicated Bearer-Related Configuration."
3. Start the Windows Media Player and choose File > Open URL(U)… in the displayed
window.
4. Enter mms://Server IP/filename in the displayed Open URL dialog box, as shown in Figure
7-72.
If the service is provided on a dedicated bearer, the IP address of the server must be consistent with
RmtIpv4Address set in TFT parameters of the dedicated bearer.
7.5.7 FTP
Prerequisite
Installation and verification of the UE are completed. For details, see 5 "Quick Start."
The FTP software is installed on the server (for example, Ser-U) and the WS_FTP is
installed on the PC connected to the UE.
Procedure
1. Power on the UE and the UE accesses the network successfully.
2. (Optional) To provide the FTP service on a dedicated bearer, perform the dedicated bearer
related configuration. For details, see section 7.5.2 "Dedicated Bearer-Related Configuration."
3. Run the Ser-U on the server.
4. Start the WS_FTP on the UE, enter the IP address of the FTP server on the address bar, and
then click to set up a connection with the server. A Quick Connect dialog box is
displayed. Enter the user name and password (which are set when setting up the FTP server)
and click Go, as shown in Figure 7-73.
5. After the connection is set up, a dialog box is displayed, as shown in Figure 7-74. The files
stored on the server are listed on the right pane and those stored on the local UE are listed on
the left pane. Select a file stored on the server and click to perform FTP download.
Select a local file and click to perform FTP upload.
7.6 ETWS
7.6.1 Overview
The Public Warning System (PWS) provides alarms for natural disasters or human error
accidents that may cause loss of lives or properties.
The Earthquake and Tsunami Warning System (ETWS) is a special PWS that provides alarms
for natural disasters such as earthquake and tsunami, and post-disaster relief and
reconstruction. It is an emergency communication system.
The ETWS has two basic requirements, namely, delay and security. The propagation velocity
of the earthquake or tsunami is very high, and the warning message must be sent to users at
the first time. Therefore, the delay is highly required. Such a message may cause a large-scale
panic. Therefore, the security is also highly required. The message source is generally
controlled by the government.
The ETWS is proposed by a Japanese telecom operator NTT DOCOMO at a meeting of the
Security Association. In addition, network support for the ETWS is written in Japanese law
and serves as a requirement for admission to the Japanese market. The ETWS is implemented
in 3GPP Rel8, and carries ETWS messages through SIB 10 and SIB 11 of system information.
The ETWS network architecture is shown in Figure 7-75.
ETWS messages are sent to UEs through SIB 10 and SIB 11. Different from common system
information, ETWS messages fall into Primary Notification (PN) and Secondary Notification
(SN). The PN carries the most important and urgent information and must be sent to users at
the first time, for example, warning message on an earthquake or a tsunami sent through SIB
10. The SN carries the secondary urgent information, for example, help information and map
sent through SIB 11.
When a natural disaster occurs, the ETWS warning provider sends an alarm message to the
network side and the network side immediately broadcasts ETWS messages to UEs.
ETWS messages can be displayed in two modes, namely, instant display and interactive
display. The display mode is contained in ETWS messages. For instant display, the UE
displays the current ETWS message in a pop-up window. For interactive display, the UE
stores messages in the inbox and you can view messages manually in the inbox. ETWS
messages are transmitted in special encoding formats. Currently, the UE only supports UCS2
and GSM 7bit.
Click the inbox icon on the toolbar. All the earthquake and tsunami messages are displayed.
Double-click a message to view the history alarm information.
Instantly and interactively displayed PN/SN messages are both stored in the ETWS message
inbox. The inbox can save up to 1000 messages. If one more message is sent to the inbox after
1000 messages are already stored, a prompt saying “ETWS message inbox is full” is
displayed in the log running window of the OMT. New messages cannot be received any
more. In this case, right-click and select Delete All Messages or Delete Selected Messages
from the shortcut menu to delete the received ETWS messages.
8 FAQ
Troubleshooting
1. Check whether UE version is correct. For details, see section 11.10.2 "Version
Verification."Check whether the board is started. Use the Hyper Terminal of the Windows
system to connect to the UE serial port. (For details, see section 9.13 "Connecting to the
Serial Port of the UE Using the Hyper Terminal of Windows.") If the serial port indicates "UE
Version: V200R004C00", the UE is started.Check whether the maintenance PC and the UE
are connected properly, and whether the network cable is available. For details, see Figure
4-1Check the correctness of the maintenance IP address of the UE entered on the OMT.
Connect to the serial port of the UE using the Hyper Terminal of Windows (for details, see
section 9.13 "Connecting to the Serial Port of the UE Using the Hyper Terminal of
Windows."). Run the version command to query the maintenance IP address of the UE, as
shown in Figure 8-2.
Figure 8-2 The maintenance IP address of the UE for user login and the queried maintenance IP
address of the UE
5. Check whether the maintenance PC is configured with an IP address that shares the same
network segment with the maintenance IP address of the UE.
6. Ping the maintenance IP address of the UE on the maintenance PC, as shown in Figure 8-4.
7. If the ping fails, check whether the IP address of the maintenance PC shares the same network
segment with the maintenance IP address of the UE. If the maintenance IP address of the UE
is 192.168.0.79, the IP address of the PC is 192.168.0.XX. Here, XX ranges from 1 to 255
(excluding 79).
8. If the maintenance PC has more than one network adapter, enter the ipconfig command in the
C:\WINDOWS\system32\cmd.exe window to check whether the maintenance IP address
(such as 192.168.0.XX) is configured on a correct network adapter.
9. Do as follows to check whether any IP address conflict exists: Connect to the UE serial port
using the Hyper Terminal of Windows (for details, see section 9.13 "Connecting to the Serial
Port of the UE Using the Hyper Terminal of Windows."). Enter the ifShow command on the
serial port interface to check the MAC address of the UE, as shown in Figure 8-6.
Figure 8-6 Checking the MAC address of the UE on the serial port
Run the arp –a command on the maintenance PC. Check the MAC address of the UE that
matches the maintenance IP address of the UE, as shown in Figure 8-7. If the MAC addresses
in Figure 8-7 and Figure 8-6 are different, the two IP addresses conflict with each other.
Check the network environment, connect the PC and UE, or modify the maintenance IP
address of the UE.
Troubleshooting
1. Check the LTE UE V200R004C00 XX Upgrade Guide. Check whether any inconsistency
exists between the UE and eNodeB, or any special configuration is required.
2. Check whether the version matches. For details, see section 11.10.2 "Version Verification."
3. Check whether the cells of the eNodeB are activated and configured properly.
4. If the fault persists, contact Huawei technical support engineers.
Symptom
The UE access fails. No key event of "attach complete" is displayed in the Key Events
column on the OMT.
Troubleshooting
1. Check the LTE UE V200R004C00 XX Upgrade Guide. Check whether any inconsistency
exists between the UE and eNodeB, or any special configuration is required.
2. Check whether the NAS protocol version of the UE matches the protocol version of the
evolved packet core (EPC). On the main interface of the OMT, choose Debug Command >
Access > CFG ACCESS PARA and double-click. The NasVersionofMME dialog box is
displayed. Confirm whether the NAS protocol version of the UE matches the protocol version
of the EPC.
3. If the fault persists, contact Huawei technical support engineers.
Troubleshooting
1. Choose Debug Command > Access > CFG ACCESS PARA and double-click. The Debug
Command dialog box is displayed. Check whether the UeCategory parameter is
CATEGORY5. Set the AccessStratumRel parameter to HUAWEI_UE_R9.
Symptom
The UE fails in handover. No key event of "handover begin" is displayed in the Key Events
column on the OMT.
Troubleshooting
Troubleshooting
1. Check the current network situation. Check whether any sudden change of signal quality
exists.
2. If the fault persists, contact Huawei technical support engineers.
2. In the displayed Device Configure window, click . The Add Device dialog box is
displayed. Select LTE UE2.0 from the Model drop down list box. Then click Next.
3. The Add Device for LTE dialog box is displayed. Enter the maintenance IP address of the
UE in the UE IP address field. Then click OK.
4. Click . The button on the right becomes , indicating that the connection between the
Probe and UE is set up.
----End
2. Choose Debug Command > Radio Measurement > CFG CELL MEASUREMENT and
double-click The Debug Command pane is displayed. Set the MeasurePeriod parameter to
40 (in the high-speed scenario, the measurement period must be set to the minimum value to
increase the measurement frequency). Then click Send Cmd.
3. (Optional) If the current standard is TDD, the TDD assignment parameters are required.
Choose Debug Command > High Speed > CFG TDD PARA and double-click. The Debug
Command pane is displayed. Set the parameters SubframeAssign and
SpecialSubframePatterns to a proper value for the current cell. Then click Send Cmd.
----End
2. Choose Debug Command > Radio Measurement > CFG HIGH MEASUREMENT and
double-click The Debug Command pane is displayed. Set the MeasurementPeriod
parameter to 200. Then click Send Cmd.
----End
1. Click on the OMT. If the icon becomes , the connection between the
OMT and UE is set up successfully.
2. Enable the serial port redirection and connect the serial port. For details, see section 11.11
Serial Port Redirection.
3. Enter the version query command version to check the maintenance IP address and Host IP
address of the UE (the maintenance IP address of the UE is 192.168.0.79, and the Host IP
address of the UE is 192.168.0.1, as shown in Figure 9-9).
Figure 9-9 Querying the maintenance IP address and Host IP address of the UE
----End
1. Click on the OMT. If the icon becomes , the connection between the
OMT and UE is set up successfully.
2. On the left pane of the OMT, choose Debug Command > System > CFG MAINTAIN IP
and double-click. The configuration interface is displayed.
3. Set the OM IP and Host IP parameters. Then click Send Cmd.
After the settings, the UE automatically reboots. You must use the OMT to reconnect the UE manually.
----End
2. To query the detailed versions of all the UE modules, click Detail>> in the Version Query
dialog box.
----End
----End
2. On the toolbar of the OMT, click to power on the LTE UE. If the button turns
Figure 9-15 Checking the service IP address of the UE contained in the message
2. Set the IP address of the PC to the service IP address (the PC is connected to the GE/FE port
on the UE). For example, if the service IP address is 172.21.214.37, the configured IP address
is shown in Figure 9-16.
----End
1. Choose Start > Control Panel > Network Connections > Local Area Connection in the
Windows system.
2. The Local Area Connection Status window is displayed. Choose Properties > Internet
Protocol (TCP/IP). Select the Obtain an IP address automatically option button.
Figure 9-17 Setting the network adapter of the PC to obtain an IP address automatically
----End
The DHCP switch is valid only in the Auto Dial-up mode (Equal to Auto Connect mode). If the
DHCP switch is enabled, the UE will respond to the DHCP request from the TE, and allocates the IP
address (allocated by the EPC) to the service network adapter of the TE. You do not need to
configure the IP address of the service network adapter of the TE manually. If the DHCP switch is
disabled, the UE does not respond to the DHCP request from the TE, you must check the IP address
(allocated by the EPC) in the NAS message, and manually configure the IP address of the service
network adapter of the TE.
If the ARP switch is enabled, you can obtain the route between the UE and TE automatically. It is
not needed to configure the TE MAC manually. If the ARP is disabled, you must configure the TE
MAC manually.
TE Mac: Refers to the MAC address of service network adapter of the TE.
TE GateWay IP: Refers to the gateway IP address of the TE. This IP address belongs to the same
network segment as the IP address of the service Ethernet port of the service TE. The configuration
may vary in different application environment.Te GateWay IP Address Is valid only when the ARP
or DHCP function is enabled.
Note that you must run netsh -c i i delete neighbors UE service network adpater Idx to completely
remove the binding relationship of the ARP from the network adapter.
5. After the command is executed, click Start > Search programs and files, enter cmd, and
then enter arp -a to check whether the binding relationship is successfully bound.
Figure 9-19 Setting the ARP on Windows 7 with the service network adapter named GE
----End
2. Choose Start > Run. The Run dialog box is displayed. Enter cmd to display the cmd
window. Enter route print to query the route.
----End
9.11 Ping
1. In the Windows operating system of the PC which the UE is connected. Choose Start > Run.
The Run dialog box is displayed. Enter cmd to display the cmd window.
2. Run ping service server IP –t to check whether the user plane can be pinged successfully. For
example, run ping 172.21.64.2 –t. Figure 5-12 shows that the user plane can be pinged
successfully.
----End
1. Connect the serial ports between the UE and PC (that is, connect the serial port cable
(component 9) to the PC (component 10), as shown in Figure 4-1.
2. Choose Start > Programs > Accessories > Communications > Hyper Terminal in the
Windows operating system.
3. Enter the name of the new connection in the displayed Connection Description dialog box.
4. Select the corresponding COM port from the Connect using drop down list box in the
Connect To dialog box.
5. Set the properties in the displayed COM Properties dialog box, as shown in Figure
9-25.Click OK. The serial port connection window of the Hyper Terminal is displayed.
Figure 9-26 Checking printing information about the serial port of the UE
----End
4. Click on the Terminal tab page. The Connect config dialog box is displayed. Set all
parameters required for serial port connection. Set Type to the serial port to connect a PC,
Baud to 57600, Databit to 8, Stopbit to 1, Parity to None, and Flow to None.
5. After completing the setting, click OK. The UE serial port is displayed, as shown in Figure
9-29. You can enter and view data in this window.
9.15 Observing Power Control on the Probe The Probe provides the
function to observe power control of the UE. With this function, you can view the basic power
information of the UE.
Procedure
1. Connect the Probe to the UE. For details, see section 9.1 "Connection between the Probe and
UE."
2. On the main interface of the Probe, choose View > LTE > Radio Parameters and double
click. The Radio Parameters window is displayed. View the content in the red box shown in
Figure 9-30.
3. To view more details, choose View > LTE > Power Control and double-click. The Power
Control window is displayed. You can view details of the physical uplink shared channel
(PUSCH) and physical uplink control channel (PUCCH).
----End
Figure 9-32 Querying the user name and password of the board in the Hyper Terminal
----End
For the use of the UE for the first time, the UE automatically searches all frequency bands (frequency
settings are not required). This process may take a long time. Please wait patiently.
7. Verify the UE. For details, see section 5.8 "Running the Ping Command."
----End
2. Modify the following parameters based on the network environment. Then click Send Cmd.
If the returned result is Success, the configuration is successful.
To use a soft USIM on your UE, you must turn on the soft USIM switch. If the USIM is available,
the soft USIM switch is automatically turned off. A USIM is recommended. The USIM switch status
will not be changed no matter UE rebooting or updating.
The IMSI is provided by the operator. The PLMN ID depends on the access network of the operator.
If a USIM is inserted, the UE uses the IMSI/PLMNID on the USIM.
The settings of K and OP of the OMT must be the same as the Home Subscriber Server (HSS).
----End
Remote Test: This mode means that the OMT or Probe on the remote host can connect to the
UE by air interface to operate on UE. These functions are the same as local host. This mode is
applicable to scenarios where the remote control of the UE is required. The current version
supports the use of a remote OMT/Probe to connect to the UE and control the UE to do ping
test and FTP download test.
Auto Site Test: During large-scale LTE commercial applications, the installation of eNodeBs
is outsourced. After installation, the customer service engineers must reenter the sites for the
testing on the eNodeBs. This increases the costs. The UE supports auto site test, that is, the
UE automatically completes the ping and FTP tests after hardware installation, to check
whether an eNodeB status is normal. In this way, the customer service engineers do not need
to reenter the site.
Procedure
1. On the menu bar of the OMT, choose System > UE Configuration. The UE Configuration
dialog box is displayed. Select Model Config, as shown in Figure 9-34.
2. Select a mode according to the application scenario of the UE. Then click OK.
3. The Model Config dialog box is displayed. Click OK. The UE reboots automatically.
----End
----End
3. Click Send Cmd. If the returned result is Success, the configuration is successful.
4. Connect the Probe to the UE (for details, see section 9.1 "Connection between the Probe and
UE." Power on the Probe. Choose View >LTE > Location and Delay Information > HO
Interrupt Delay and double-click. The HO Interrupt Delay pane is displayed.
5. If a UE handover occurs, the uplink/downlink handover latency is visible on the MAC, RLC
and PDCP layers on the UE side in the HO Interrupt Delay: MSI window, as shown in
Figure 9-39.
4. On the right pane of the Registry Editor window, set the value name to TransmitIoLength,
as shown in Figure 9-41.
5. Double-click the new registry item on the right pane of the Registry Editor window. Set
Value data: and click OK in the displayed dialog box.
To set the size of the FTP transmitting window to 512K, set the value data to 80000 (hexadecimal).
4. On the right pane of the Registry Editor window, set the value name to TCPWindowSize, as
shown in Figure 9-44.
Figure 9-44 Setting the key value for the size of the FTP receiving window
5. Double-click the new registry item on the right pane of the Registry Editor window. Set
Value data: and click OK in the displayed dialog box.
To set the size of the FTP receiving window to 512K, set the value data to 80000 (hexadecimal).
4. On the right pane of the Registry Editor window, set the value name to MTU, as shown in
Figure 9-47.
5. Double-click the new registry item on the right pane of the Registry Editor window. Set
Value data: and click OK in the displayed dialog box.
4. Fill in the workflow as required in the displayed dialog box. Set RMT/RAT that Analyze
this Requirement to LTE UE RAT in the Assign RMT/RAT area.
----End
10.1 MIMO
Introduction
The Multiple Input Multiple Output (MIMO) is a technology to receive or send signals at the
receiving or transmitting terminal by using multiple antennas. By using the array gain,
diversity gain, spatial multiplexing gain, and interference suppression gain, the MIMO
improves system coverage and quality, and increases the peak rate. Multiple antennas enable
you to obtain the array gain by changing the direction of antennas. The advantages are as
follows:
The eNodeBs with the application of the MIMO technology have a wider coverage.
When the channel is in poor conditions, the diversity gain provides data backup by using
different antennas to send the same information, so that the data has stronger interference
resistance capability.
When the channel is in good conditions, the spatial multiplexing gain multiplies the data
transmission rate by using different antennas to send different types of data, so that the
peak rate of the system is greatly improved.
Antennas of the UE are located on two panels, namely, front panel and back panel. The front
panel contains two RRU0 ports: a transmit/receive port (RXA1/TX) and a receive port
(RXB1). The back panel contains two RRU1 ports: a transmit/receive port (RXA2/TX) and a
receive port (RXB2). In the MIMO scenario, select a proper antenna configuration for the UE
based on network topology. Take the 2 x 2MIMO networks for example. If the UE antenna
connects to the RXA1/TX and RXB1, select the RRU0 for the 1T2R mode. If the UE antenna
connects to the RXA2/TX and RXB2, select the RRU1 for the 1T2R mode.
Prerequisite
The OMT is connected to the UE properly.
Procedure
1. Click the Debug tab on the left pane of the main interface of the OMT.
2. Configure the antennas on the UE. Choose Debug Command > System > CFG UE INFO
and double-click. Configure UEAntennaInfo to make antenna configuration of the UE. For
details on configuration options, see Table 10-1.
RRU0_RRU1_2T2R (Tx The RXA1/TX and The RRU0 and RRU1 are in
power upgrade 3dBm) RXA2/TX are used for place. The RXA1/TX and
simultaneous transmitting. RXA2/TX are connected to
The RXA1/TX, RXA2/TX the communication antenna.
are used for receiving. If this option is selected, the
uplink transmit power is
increased by three dB.
RRU0_RRU1_1T2R The RXA1/TX and Just use for beam forming
(Antenna selection) RXA2/TX is used for testing。
alternative transmitting.
The RXA1/TX and
RXB2/TX are used for
receiving.
RRU0_RRU1_1T4R (RRU0 The RXA1/TX is used for The RRU0 and RRU1 are in
for transmitting) transmitting. The place. The RXA1/TX, RXB1,
RXA1/TX, RXB1, RXA2/TX and RXB2 are
RXA2/TX and RXB2 are connected to a
used for receiving. communication antenna.
RRU0_RRU1_2T4R (Tx The RXA1/TX and The RRU0 and RRU1 are in
Power Upgrade 3dBm) RXA2/TX are used for place. The RXA1/TX, RXB1,
simultaneous transmitting. RXA2/TX and RXB2 are
The RXA1/TX, RXB1, connected to the
RXA2/TX and RXB2 are communication antenna. If
used for receiving. this option is selected, the
uplink transmit power is
increased by three dB.
RRU0_RRU1_1T4R The RXA1/TX and Just use for beam forming
(Antenna selection) RXA2/TX is used for testing。
alternative transmitting.
The RXA1/TX, RXB1,
RXA2/TX and RXB2 are
used for receiving.
RRU0_1T1R (RRU0 used) The RXA1/TX is used for The RRU0 is in place. The
transmitting. The RXA1/TX is connected to the
RXA1/TX is used for communication antenna.
receiving.
RRU1_1T1R (RRU1 used) The RXA2/TX is used for The RRU1 is in place. The
transmitting. The RXA2/TX is connected to the
RXA2/TX is used for communication antenna.
receiving.
Observation Method
Use a tool (such as the Net Meter and Probe) to check whether the packet traffic meets the
expected requirements.
Prerequisite
The OMT is connected to the LTE UE properly.
The E-UTRAN supports IMS emergency calls.
The SAE supports IMS emergency calls.
The UE, E-UTRAN and SAE support the R9 protocol.
Procedure
3. To set up an emergency bearer, choose Debug Command > Bearer > SETUP BEARER and
double-click. The bear setup window is displayed. Set Cid to a desired value with the bearer
type set in the previous step. Then click Send Cmd, as shown in Figure 10-2.
3. On the main interface of the OMT, choose Debug Command > Access > CFG ACCESS
PARA and double-click. Set the protocol version of the AccessStratumRel and
BFProtoclVersion to R9.
4. Power on the UE. The UE camps on a cell where emergency calls are supported. For the
follow-up operations, see Steps 2–3 in the section “Emergency Calls in the in Normal Mode”.
The value of the Cid ranges from 0 to 31 (the range of 0 to 10 is recommended), because the Cid with a
range from 0 to 10 is still reserved after reboot. The Cid value in emergency bearer setup must be the
same as the Cid value set to the emergency bearer type.
Observation Method
After an emergency call is set up, you can view emergency pdn connectivity success in the
key event column of the OMT.
----End
Prerequisite
The OMT is connected to the LTE UE properly.
Procedure
1. Install the GPS antenna on the GPS port on the front panel of the UE, as shown in Figure 4-2.
2. Connect the Probe to the GPS. Start the Probe. Then click . The Add Device dialog box is
displayed. Select GPS from the Type drop-down list box, and select NMEA from the Model
drop-down list box. Then click Next.
3. The Add Device dialog box is displayed. Select 4800 from the Baud rate drop-down list box,
and select COM1 from the COM port drop-down list box. Then click OK.
4. Connect to the Probe. Click to connect the GPS to the Probe. Then the icon
becomes .
5. View the GPS information. On the main interface of the Probe, choose View > GPS. The
GPS: GPS1 window is displayed, as shown in Figure 10-7. You can view the information
about the GPS.
6. Choose View > OutdoorMap. The OutdoorMap window is displayed. Click to import
the map on the corresponding location.
7. Power on the UE. When the UE starts to move, it can draw points on the map.
Observation Method
After the UE starts to move, check whether the route on the map consists with the actual
route.
----End
11.1 UE Operations
11.1.1 Common Operations
To perform common operations on the UE, click the Common tab (the first tab on the left
pane of the OMT). This tab provides several function items, namely, Remote Test, Auto Site
Test, and System Config.
Prerequisite
The OMT is properly connected to the UE.
Context
Figure 11-1 shows the common operation interface of the OMT.
Table 11-1 lists common operations; include Auto Site Test, System Config, and Remote
Test.
Procedure
1. Click the Common tab on the left pane of the OMT, as shown in Figure 11-1.
2. Click an option you want to set, such as Auto Site Test. Then select an operation, as shown in
Figure 11-2.
3. Make settings in the displayed dialog box, such as Configure test plan in Auto Site Test, as
shown in Figure 11-3.
----End
Prerequisite
The OMT is properly connected to the UE.
Context
Figure 11-4 shows the advanced operations on the OMT.
The Advance tab involves complicated operations. For details, see Table 11-2 "Advanced
operations."
Context
Figure 11-5 shows the OMT debug commands.
Procedure
1. Click the Debug tab on the left pane of the main interface of the OMT.
2. Double-click a debug command you want to configure. For example, choose Debug
Command > USIM > CFG SOFT USIM and double-click.
3. Enter command parameters, as shown in Figure 11-6.
If the command includes querying the current system value, the system value will be displayed in
the Parameter Values column.
If the command sets a default parameter value, the default value is displayed in the Parameter
Values column.
If a parameter does not contain any value, you must enter a parameter value. You can set the value
according to the Description.
If a parameter is set incorrectly, click Clear All. Then reenter a parameter value.
4. Click Send Cmd. Observe the Response Results. The command name and parameter value
are displayed, as shown in Figure 11-7.
----End
Click on the toolbar of the OMT. The Message Trace window is displayed, as
shown in Figure 11-8.
Prerequisite
The network and UE are functional.
The OMT communicates properly with the UE.
Context
The GUI of tracing messages displays the following information:
No.: Records the SN reported in the current message.
Procedure
1. On the toolbar of the OMT, click . The system automatically traces messages. By
default, only air messages (including UU Message and Nas Message) are displayed.
2. Double-click a message in the Message Trace window to check the details, as shown in
Figure 11-9. You can click Previous or Next to check each message.
The upper part of the dialog box is the command tree and the lower part is the hexadecimal code stream.
----End
Context
When all the data is cleared, the data includes the data in the Message Trace window and the
data in the Key Events window.
Procedure
1. Right-click in the Message Trace window and then choose Clear All Data.
2. The Confirm Clear dialog box is displayed. Click OK. All data in the Message Trace
window and Key Events window is cleared.
Context
There are two ways to save data: manual saving and automatic saving.
The conditions for automatic saving are as follows:
1. If the number of displayed data records exceeds 1000, the system automatically saves the data
reported by the UE, including the data of the air messages, data of intra-stratum messages,
and data of key events. The data is saved in …\database\messages under the OMT running
directory. The file name is the time stamp + .tmf, such as 2011-06-24-15-06-03.tmf.
2. If the data is cleared, the cleared data is automatically saved. The saving path and file name
are the same as that mentioned earlier.
Procedure
1. Right-click in the Message Trace window and then choose Save As.
2. Select the saving path and then click Save. The data in the current Message Trace window is
saved in .tmf format.
---- End
Context
The importing of the historical message trace files in .tmf format is supported.
Procedure
1. Right-click in the Message Trace window and then choose “Load data…”.
2. The file in .tmf format is displayed by default in the dialog box. The Message Trace window
and Key Events window are displayed separately, as shown in Figure 11-10 and Figure
11-11.
----End
Procedure
1. Right-click in the Message Trace window and then choose Find.
2. In the displayed Query Message dialog box shown in Figure 11-12, enter the message name,
and then click Find.
The query results are displayed in list.
3. (Optional) Click Advance, enter the message name and other query conditions, such as the
source and destination module names, as shown in Figure 11-3.
----End
Context
Message filtering is used to filter messages displayed in the window, and does not cause data
loss. Inter-stratum messages are filtered by default.
Procedure
1. Right-click in the Message Trace window. Then choose Filter Air Message from the
shortcut menu. The air message is not displayed in the Message Trace window.
----End
Prerequisite
The data of inter-stratum messages is available in the Message Trace window. That is,
the message type is Stratum Message.
Context
There is a large quantity of some type of inter-stratum messages and this type of messages can
be ignored. In this case, the UE is notified to stop reporting these inter-stratum messages.
Procedure
There are two methods to stop reporting inter-stratum message:
Method 1: Use the right-click menu.
Select the target inter-stratum message and then right-click and choose No reporting on this
Stratum Message. The selected message is not reported by the UE.
Method 2: Use the system menu.
1. Choose System > UE Configuration. In the displayed dialog box, choose Inter-Stratum
Filtering on the left, as shown in Figure 11-15.
To deleted a message, right-click the message and choose Delete, and then click OK.
----End
Procedure
1. Right-click the base message and then choose Set the message as the base from the menu.
The base message can be an inter-stratum message, UU message, NAS message, or a key
event message.
2. Click another message to calculate the time delay. The time delay between two messages is
displayed in the status bar on the lower left corner of the OMT, as shown in Figure 11-16.
3. Reset the message delay calculation function. Right-click a message (except an alarm). Then
choose Reset count delay from the shortcut menu, as shown in Figure 11-17. It will reset the
count delay function to the initialized state, clear the delay count result in the status bar in the
lower left corner, and clear the reference time.
----End
Procedure
1. Right-click in the Message Trace window and choose Export Excel.
2. Select a path to save the file. By default, the file name is named in the form of time stamp
+ .xls (such as 2011-04-28-20-19-33.xls). Click Save.
----End
Prerequisite
The OMT is connected to UE properly.
Context
Figure 11-18 shows the key events, including the following information:
No.: Records the SN reported in the current message.
SN: SN of the store key event.
Time Stamp: Board system time stored in the key event.
Current Time: Records the PC system time reported in the current message.
Key Event Name: key event ID.
Key Event Description: description of the key event.
When the OMT performs the connection operation, tracing of key events is automatically
started.
Procedure
1. The operations of tracing key events are the same as that of tracing messages.
2. To upload a log, choose File Management > Log Upload, as shown in Figure 11-20.
3. The Log file upload dialog box is displayed. Click Browse… to select the path to save the
log files. Then click Upload. The debug log of the protocol stack is uploaded to a specified
path, as shown in Figure 11-21.
Context
CPU/Memory Usage: Usage of the master core on the UE board, indicated by
percentage.
Device Environment State: Fan rotation speed and temperature.
Flash Status: Usage of the flash memory of the UE.
Master Core Task Status: All the task lists of the UE master core.
Slave Core Task Status: All the task lists of the UE slave core.
Device Information: Current RFU board status, USIM and system information.
Port Status: Port information.
UE Status: To query RFU board TX power and RFU board main/slave antenna power.
Report period setting: Choose System > System Config > Device Management
Config, select the Report Period Setting check box, and set the reporting frequency.
The default reporting frequency is five seconds.
This setting is valid only for active data reporting except Flash Status. Flash Status can be queried after
the tab page is clicked.
Procedure
Click Device Environment State to check the device environment status (fan rotation
speed and temperature).
Click the Flash Status tab page to check the flash status
I/O operations on the flash memory have an impact on the query response time. Therefore, I/O
operations should be avoided during the query of the flash status.
Click Master Core Task Status to check the list of the master core task status.
Click Slave Core Task Status to check the list of the slave core task status.
Device Information: Click Device Information to check the RFU board, USIM and
system information.
Click Port Status to check the port information.
UE Status. Click Port Status to check the power of the RF module.
Context
FtpServer: It is used to set up the FTP server during FTP transmissions for file transfer from
the PC to the UE or from the UE to the PC.
Procedure
1. On the menu bar of the OMT, choose Integrated Tool > Set External Tool, as shown in
Figure 11-23.
2. In the setting window shown in Figure 11-24 the added external tools are displayed on the left
pane. You can click the tool to modify or delete the related parameters. You can add an
external tool on the right pane.
----End
Prerequisite
The OMT is connected to UE properly.
The FTP server is started. Perform settings on the FTP server. For details, see section
6.4.3.2 Setting the FTP Tool.
Context
Data restoration: This function is used to restore the data center files of the UE from the
data center files backed up on the PC.
Data backup: This function is used to upload the current data center file of the UE to the
specified path on the PC.
Procedure
1. Choose File Management > Data Center > Data Back Up Or Restore.
2. Select a data center operation. Click Browse… to select a path for saving the file, as shown in
Figure 11-26.
3. Click Restore or Back Up.
----End
Prerequisite
The OMT communicates properly with a UE.
The files of settings before delivery dftnas.cfg, dftrrc.cfg, and dftom.cfg exist.
Context
This function enables the configurations in the data center of the UE boards (you want to
restore) to the configurations during version release. The existing configuration data is
overwritten.
Procedure
1. Choose File Management > Data Center > Restore Delivery Settings.
2. The Restore Settings Before Delivery dialog box is displayed. Click OK.
3. The Alert dialog box is displayed. Click OK. The default settings are restored after the UE
reboots.
If Restoring the delivery settings succeeded. is displayed in the log, the restoration is successful.
The UE is restarted.
If Restoring the delivery settings failed. The configuration file is damaged. Please manually
restore the version configuration file in the data center. is displayed in the log, check whether the
three files of settings before delivery exist.
If Restoring the delivery settings failed. Please try again! is displayed in the log, attempt to restore
the delivery settings again.
---- End
Prerequisite
The OMT communicates properly with a UE.
The FTP server is started. Perform settings on the FTP server. For details, see section
6.4.3.2 Setting the FTP Tool.
Procedure
1. Ensure that the board is connected, and then choose File Management > Upload File.
2. The dialog box for uploading the file is displayed and the files in the UE root directory are
displayed in the file list, as shown in Figure 11-29.
3. Select a file you want to upload to the PC. Click Browse…. Then select the path for
uploading, and click Upload.
----End
11.8 UE Blackbox
This function is used to upload blackbox files of L2 and L3.
Prerequisite
The OMT communicates properly with a UE.
The FTP server is started. Perform settings on the FTP server. For details, see section
6.4.3.2 Setting the FTP Tool.
Procedure
1. On the menu bar of the OMT, choose File Management > UE Blackbox, as shown in Figure
11-30.
Blackbox files are stored in the directory of the hbbi user in the FtpServer.
---- End
Context
Alarm management consists of querying the current alarms, querying historical alarms,
obtaining alarm files, and alarm detection period, as shown in Figure 11-32.
Four alarm levels are available: Critical (indicated by ), Major (indicated by ), Minor
(indicated by ), and Warning (indicated by ). If an alarm occurs, the corresponding alarm
severity is highlighted, as shown in Figure 11-33.
Prerequisite
The OMT communicates properly with the UE.
Procedure
1. Choose Debug Command > Alarm > CFG FORBIDDEN ALARM and double-click. The
Debug Command pane is displayed, set the alarms you want to shield. Then click Send
Cmd.
Prerequisite
The OMT communicates properly with the UE.
Context
The alarm list provides the following information:
No.: Serial number of the currently reported alarm.
Alarm Name: Brief alarm information.
Alarm Severity: The degree of impact of the fault on services. The alarm severity is
classified into the critical alarm, major alarm, minor alarm, and warning alarm.
Alarm Source: Module where the alarm is generated.
Occurrence Time: Time when the alarm is generated.
Clear Time: Time when the alarm is cleared. If the alarm is not cleared, "---" is
displayed.
Current Status: State of the alarm. The state can be Generate, Automatic Clear, and
Manual Clear.
Alarm ID: Alarm ID in hexadecimal format.
Detailed Information: Detailed description of the alarm.
Handling Suggestions: Handling suggestions for clearing the alarm.
Procedure
1. On the menu bar of the OMT, choose Alarm Management > Query Current Alarms.
2. Right-click on the OMT and choose Search. A dialog box is displayed, as shown in Figure
11-35. Enter the key words for searching the alarm.
3. (Optional) Right-click on the OMT and choose Filter to filter alarms of certain severity, as
shown in Figure 11-36.
4. Excessive alarm records exist, the system automatically scrolls the alarm data. You can
choose Auto Roll or Stop Roll to check a data record.
5. To import data, check the obtained alarm files, select the folder of the alarm file
AlarmLog.log, and then select the alarm file. The alarm data in the file is displayed on the
OMT.
---- End
Prerequisite
The OMT communicates properly with the UE.
Context
Historical alarms refer to all the alarms generated after the UE is started.
Procedure
1. Choose Alarm Management > Query History Alarms on the OMT. Other operations are
the same as those in querying current alarms.
Prerequisite
The OMT communicates properly with the UE.
The FTP server is started. Perform settings on the FTP server. For details, see section
6.4.3.2 Setting the FTP Tool.
Context
The UE alarm file is obtained from the boards.
Procedure
1. Choose Alarm Management > Obtain Alarm File on the OMT.
2. Choose the save path of the alarm file (as D:\Alarm).
3. Click OK.
----End
Prerequisite
The OMT communicates properly with the UE.
Context
The OMT provides automatic alarm detection for the baseband, software at the bottom, and
RF modules. You can set the detection period as required. The default value is 20000 ms.
Procedure
1. Choose Alarm Management > Alarm Detection Period on the OMT.
A dialog box is displayed, as shown in Figure 11-39.
Procedure
1. Choose Version Management > Version Query. The Version Query dialog box is
displayed, as shown in Figure 11-40.
2. To query the detailed versions of all the UE modules, click Detail>>, as shown in Figure
11-41.
---- End
Prerequisite
The OMT is connected properly to the LTE UE.
Context
Version verification occurs in either of the following cases:
Automatic version verification after the OMT is properly connected to the UE.
Manual version verification on the OMT version management menu.
Procedure
Automatic version verification
1. The system automatically starts version verification after the OMT is properly connected to
the UE.
2. Verify the result.
If version verification is successful, the OMT does not display any messages. If version
verification fails, the OMT displays error messages, as shown in Figure 11-42.
---- End
Procedure
For details, see section 6.4.3.3 UE Version Update.
---- End
Prerequisite
The OMT communicates properly with a UE.
The FTP server is started. Perform settings on the FTP server. For details, see section
6.4.3.2 Setting the FTP Tool.
Procedure
1. On the menu bar of the OMT, choose Version Management > Version Backup. Select a
path for saving the version file.
2. Click Backup.
---- End
---- End
Prerequisite
The OMT communicates properly with the UE.
Procedure
Prerequisite
The OMT communicates properly with the UE.
The serial port is connected.
Procedure
1. Enter the serial port command in the window for display of the serial port and command input,
and then click Select Send.
---- End
Procedure
1. After entering the commands in the textbox for command input, select one or several lines of
commands, and then click Select Send to send the commands.
2. After entering the commands in the textbox for command input, select one or several lines of
commands, and then click Circular Send to send the commands in cycle mode.
3. After entering the commands in the textbox for command input, click All Send to send all the
commands.
---- End
Procedure
1. Click Open Script to open the script.
2. After modifying the script, click Save Script to save the script.
---- End
Procedure
1. Click Delay Configuration. The Delay Configuration dialog box is displayed.
2. Configure the Line Delay and Circle Delay, as shown in Figure 11-47.
3. Click OK.
Figure 11-47 Setting the delay of script running for serial port redirection
Context
This function is used to display the real-time operation logs, running logs, and debug logs in
the log redirection window.
Procedure
1. On the toolbar of the OMT, click for log redirection. The Log Redirect pane is
displayed. You can view the real-time printing information (Error level by default), as shown
in Figure 11-48.
2. To change the printing level, choose System > UE configuration > Log Configuration. To
select a desired printing level, double-click the log level. In addition, you can set the type of
displayed logs, and auto upload period, as shown in Figure 11-49.
Prerequisite
The OMT is properly connected to the UE.
The UE succeeds in network access.
Context
All latencies can be customized. By default, the OMT supports the following three delay
statistics functions:
Handover latency.
Access latency.
Interrupt latency on the uplink user plane.
Procedure
1. On the toolbar of the OMT, click Trace to enable the message trace function, as shown in 1.
2. On the left navigation bar of the OMT, click the Advance tab.
3. In the navigation tree, choose Key Performance Indicator > Latency and Performance >
Latency Statistic and double-click. The Latency pane is displayed. Observe the result, as
shown in Figure 11-51.
To observe the handover latency of the UE on the Probe, you must enable the latency reporting function
on the OMT. For details, see section9.21 "Observing the Handover Latency of the UE on the Probe."
----End
Context
You can customize the latency by setting start message and end messages.
Procedure
1. Choose System > UE configuration on the OMT, and then choose Latency Custom.
2. Enter a value in the Latency Type field. Select the type and name from the Begin\End
Message Type and Begin\End Message Name drop-down list boxes. Then click Apply, as
shown in Figure 11-52.
3. Check the customized latency information according to the procedures in section 11.13.1
"Collecting Statistics on Latency."
----End
Prerequisite
The LTE UE is properly connected to the OMT PC.
The LTE UE succeeds in network access.
Procedure
1. On the left navigation bar of the OMT, click the Advance tab.
2. In the navigation tree, choose Key Performance Indicator > Latency and Performances >
Performance and double-click. The Performance window is displayed. Check the result, as
shown in Figure 11-53.
----End
Prerequisite
The OMT is properly connected to the UE.
Procedure
1. On the left navigation bar of the OMT, click the Advance tab.
2. In the navigation tree, choose Key Performance Indicator > Latency and Performances >
Get Time Point and double-click. The Get Time Point window is displayed. Check the
result, as shown in Figure 11-54.
Prerequisite
The OMT is properly connected to the UE.
Procedure
1. On the left navigation bar of the OMT, click the Advance tab.
2. In the navigation tree, choose Key Performance Indicator > Cell > Cell Measure and
double-click. Check the RSSI, RSRP and RSRQ measuring results of the service cells and
neighboring cells, as shown in Figure 11-55.
3. In the navigation tree, click Camp Cell Information. The Camp Cell Information window
is displayed. Check the configuration information of the camp cell, as shown in Figure 11-56.
To observe the cell measuring information of the UE on the Probe, see the GENEX Probe User Guide.
Please visit http://support.huawei.com/support to get related Probe documents.
----End
Prerequisite
The OMT is properly connected to the UE.
The UE succeeds in network access.
Context
The OMT monitors the following baseband scheduling information:
Downlink full-band CQI and sub-band CQI.
Number of invokes of uplink and downlink MCSs of related orders, number of RBs, and
code rate.
Procedure
1. On the left navigation bar of the OMT, click the Advance tab.
2. In the navigation tree, choose Key Performance Indicator > Baseband > CQI and
right-click. The CQI window is displayed. Check the CQI of the downlink full-band and
sub-band, as shown in Figure 11-57.
3. In the navigation tree, choose Key Performance Indicator > Baseband > MCS and
double-click. The MCS window is displayed. Check the number of invokes of uplink and
downlink MCSs of related orders, number of RBs, and code rate, as shown in Figure 11-58.
----End
Prerequisite
The OMT is properly connected to the UE.
The UE succeeds in network access.
Context
The OMT monitors the information of current UE power margin in real time.
Procedure
1. On the left navigation bar of the OMT, click the Advance tab.
2. In the navigation tree, choose Key Performance Indicator > Real Time Information >
Power Balance and double-click. The Power Balance window is displayed. Check the
current power balance, as shown in Figure 11-59.
----End
Context
This function is developed for data collection and future analysis of bugs found in tests.
Procedure
1. On the left navigation bar of the OMT, click the Advance tab. Choose Capture Data >
Baseband Capture Data and double-click, as shown in Figure 11-60.
2. The Baseband Capture Data dialog box is displayed. Select a stop condition from the Stop
Condition drop-down list box. Select filtering conditions for some stop conditions.
3. Click Start. The data collection starts.
4. If the stop condition is met, the current frame number and subframe number are displayed in
the sampling information. There are two ways to export data, to export the sampling data with
a specified frame number or to export subframe number, and to export the sampling data of
one frame, as shown in Figure 11-61.
5. The exported data is saved in the user directory set in the FTP tool.
Figure 11-62 Setting the path for saving the sampling data
Context
This function is used to collect the current RF information.
Procedure
1. On the left navigation bar of the OMT, click the Advance tab. Choose Capture Data > RF
Information Collect and double-click.
2. The RF Information Collect dialog box is displayed. Select the RF information you want to
collect and the path for saving the information. Then click OK, as shown in Figure 11-63.
The initial PIN and PUK are provided by your service providers. For details, consult your service
provider.
Prerequisite
The OMT is properly connected to the UE.
The USIM is in place, and the protection function of the PIN is disabled.
Context
You can enable PIN protection. If this function is enabled, you must enter the PIN for
verification when the UE reboots or is powered on next time. If this function is disabled, you
do not need to enter the PIN for verification when the UE reboots or is powered on next time.
Procedure
1. On the menu bar of the OMT, choose System > Manage PIN > Enable PIN(E), as shown in
Figure 11-64.
Procedure
1. On the menu bar of the OMT, choose System > Manage PIN > Disable PIN(D), as shown in
Figure 11-66.
Prerequisite
The OMT is properly connected to the UE.
The USIM is in place, and the protection function of the PIN is enabled.
Context
You can enhance the USIM protection by modifying your PIN.
Procedure
1. On the menu bar of the OMT, choose System > Manage PIN > Modify PIN.
2. Enter the current PIN and the new PIN. Reenter the new PIN, and then click OK, as shown in
Figure 11-68.
Procedure
1. On the menu bar of the OMT, choose System > Manage PIN > Validate PIN.
2. Enter a valid PIN. Then click OK.
Context
If a USIM is locked, unlock the PIN with the PIN unblocking key (PUK).
Procedure
1. If a USIM is locked, an Error dialog box is displayed, as shown in Figure 11-70.
2. Enter the correct PUK. Then enter the new PIN for two times. Click OK.
A message is displayed, indicating the remaining PIN input times. If the number of incorrect PIN
attempts exceeds the limit, the USIM will be locked. In this case, you must unlock the PIN using the
PUK; otherwise, you cannot perform operation related to the USIM. A PUK contains four to eight digits.