Documente Academic
Documente Profesional
Documente Cultură
Contents
5. Dynamic Management..................................................................................................... 33
1. Brief Introduction
We have to apply for a user name first if we are going to use EMS. Just contact your
team leader and he will help you apply for that.
After getting authentication, log in EMS like below. At first, we have to add one
bureau, the server address is 172.29.219.3, bureau name can be anything. Then fill in
your user name and password, click OK.
After logging in, choose NE Management under Configuration. Then select the MO
SDR in which the site is, right click to start NE management. (We can see different
cities belong to different MO SDR.)
After starting, right click again and we can see a lot of functions. We can choose one
according to our purpose. The most frequently used are Configuration Management
and Dynamic Management. Configuration mangement is to check the
configuration/parameters of the sites and Dynamatic configuration is for checking
In Configuration Management, the upper box shows us the site list, we can search it
and click the Modify Area. Wait for a while and the lower box will shown. In the
lower box, it tell us all the parameters configured for this site. But for us, the most
frequently used is Radio Parameter. We can check the parameters for TDD and FDD
separately. For details, please read Chapter 4.
In dynamic management, the upper box lists all the sites which we can choose. The
lower box shows all the dynamic commands. It contains SDR part, LTE FDD part and
LTE TDD part. We only need to find the right command in LTE FDD or LTE TDD. For
SDR part, it’s not our concern. For more details, please read Chapter 5.
We need to apply for mutex right to prevent two users are configuring the same site
at the same time. It’s used in Configuration Management.
We can manage mutex right here, like apply for the right or release right. Here we
can also do batch apply and batch release. It’s more convenient.
There’s also another way to apply the mutex right. Just choose your site and right
click. Select Apply for Mutex Right.
If this symbol appears in front of eNodeB, it means that the Mutex Right is given.
Yet if it’s a red lock, it means the mutex right is taken by other users. As shown
below:
Click Configuration management-> Data Synchronization. Then choose the sites that
need to be synchronized, and click ‘synchronize’. Wait for a moment and enter the
All rights reserved. No spreading without permission of ZTE. Page8
Internal Use Only
verification code. Still have to wait for a while then it will finish.
With this way, we can do batch synchronization when you modified many sites at
one time.
Also, similar like Mutex Right, we can also synchronize as following. Yet the
difference is if we choose the following way, we can only synchronize one by one.
a. No need to synchronize
This symbol means this site is connected to OMMB, and no parameters change.
But it doesn’t mean this site has no alarm.
c. Link broken
If the link is broken, we cannot synchronize it until the link is ok. For this kind of
sites, they have at least one alarm: Link Broken between OMM and NE.
1. Radio Standard.
a. TDD Only
b. FDD Only
All rights reserved. No spreading without permission of ZTE. Page10
Internal Use Only
c. TDD&FDD
2. Bandwidth and Frequency.
a. TDD: 20MHz(2330MHz---2350MHz, centre carrier frequency=2340MHz)
+10MHz(2350MHz---2360MHz, centre carrier frequency=2354.4MHz)
Band Indicator for Frequency: 40
b. FDD: 5MHz(DL centre carrier frequency=876.7MHz, UL centre carrier
frequency=831.7MHz,)
Band Indicator for Frequency: 5
3. PLMN.
a. TDD: 51009 (MCC510+MNC09)
b. FDD: 51028 (MCC510+MNC28)
4. Cell ID, from which we can know it is TDD cell or FDD cell.
a. 11/12/13 (20MHz TDD cell)
b. 21/22/23 (10MHz TDD cell)
c. 31/32/33 (5MHz FDD cell)
5. CA(Carrier Aggregation)
Carrier Aggregation means more than one carrier work together to improve the
throughput, that’s why there are 20MHz and 10MHz cells. In this project, we
configure Downlink CA ONLY and ONLY for TDD.
Cell 11&21 are a pair. Cell 12&22 are a pair. Cell 13&23 are a pair. We specially
configure them for Coordination.
3. Alarm check
The premise for SSV is that the site is alarm-cleared or has alarms which won’t
impact the live traffic. Sometimes, the alarms may occur suddenly and cause some
problems for our testing.
a. Alarm Monitoring
In Alarm Monitoring, we can check all the alarms under one network.
This is the picture after we click Alarm Monitoring. It shows all the alarms of all sites
in the live network.
Usually we need to check the alarms for one or more special sites, so we click NE
tree and search the site ID as shown. (If there’s nothing shown in the right box below,
it means this site has no active alarms.)
It’s also possible to right click on this site to check the history alarms.
We just need to search the site ID, choose the right site and click ok. This method is
useful for batch alarm checking.
This attached alarm list defines which alarms are non-service alarm and which are
service alarms.
Site Alarms.xlsx
4. Configuration Management
In chapter 1, we already said the most frequently used is Radio Parameter. We can
find any radio parameters here. If we already know the parameter name, we can
search in the lower box. But for the most frequently used parameters, we better
remember where we can find it. Like PCI, we can find it here:
But in this example, this site is TDD Only site, so it’s empty in the right part of the
following picture. We can only find TDD cells in the next picture. Actually, for TDD
and FDD, the operation is the same.
RS Power
Sometimes after analyzing the drive test log, there are some requirements for RS
power adjustment. The way to check and modify RS power is as below. Currently we
only change RS Power is enough, no need to modify PA and PB.
We can see the expanded parameters by clicking the view button or modify it by
clicking the edit button:
PA
Similar like RS Power, we can find PA value like below, under DL Power Control.
Please pay attention that we only modify Power Offset between PDSCH and Cell RS
(P_A_DTCH) as marked in the above picture.
PB
Just double click E-UTRAN FDD Cell or E-UTRAN TDD Cell, same as PCI check, we can
All rights reserved. No spreading without permission of ZTE. Page18
Internal Use Only
find PB. Also, as we can see below, the configuration about bandwidth and center
carrier frequency, etc is also here.
Sometimes for one parameter, we need to modify not only one site. If we do it one
by one, it will take a long time. Here using data batch configuration can make it
easier.
Data batch configuration is under Configuration Management. Click the marked area
as shown below.
Select the sites. You can search it one by one if not too many sites.
Choose the parameters you need to modify. (RS Power for example)
Then click the edit button, modify it as the required value, then click save.
Synchronize modified data after modification.
Similar like data batch configuration in 4.3, we can also export and import Excel files
to modify parameters.
At first, select all sites, and find the parameter you want to modify. Let’s take PA for
example.
Then click export. Choose one File path and export it.
Open the exported Excel file. Using Vlookup to find the sites/cells which need to be
modified and change the value paForDTCH. In this example, the original value of
paForDTCH is 4, but we have to modify some sites to value 2.
For the sites which need to be modified, use M in the column MODIND. Leave the
rest blank.
Then delete the rows which don’t need to make any change (Delete the selected
rows in the above picture) and save it.
Planning data in optimization part usually means the original planned PCI/Neighbor
Relation/PRACH parameters. We can export them using Planning Data Export.
Choose the sites in the left, and then select the template type (TDD or FDD); choose
the file path and write a name prefix, and click Export.
Actually planning data only include some important parameters. If you want to know
more parameters, especially radio parameters, we can export Optimization data.
Click Live Data Area and all the live subnets are shown in the right. Those are all the
live data. We don’t need to care about the Plan Area, because Plan Area data maybe
created long time ago, a lot different from the live.
Choose one Data Type, TDD Radio or FDD Radio. If we selected more than one
subnet, we can click Merge to one File because in default it’s one file for one subnet.
Then click next, select one file path and click export.
Please pay attention that we can also export Planning Data from here. Just need to
click Plan first then select Data Type. For the rest is the same as Optimization data.
If we want to add neighbors for many sites, we can import the planning data. Only
need to fill in 2 sheets. Take FDD for example: ExternalEUtranCellFDD and
EUtranRelation. Just fill in the needed information, keep the rest the same as the
exported data, then import.
Here, EUtranRelation is the neighbor relations for each cell, for example, site A cell
31 add site B cell 31, site A cell 32 add site B cell 31. The ExternalEUtrancellFDD
means all the external relations for each site. It’s related with EUtranRelation. Still in
this example, the ExternalEUtrancellFDD should be site A add site B cell 31.
After click Planning Data Import, select Add and choose the file which needs to be
imported, and click import. Please synchronize after import.
For batch data importing, we use planning data import. But sometimes when in drive
test, our DT engineers find the neighbor missing between two cells. So we use
Neighbor Cell Management.
Choose one site as Source eNodeB, choose another as Neighbor eNodeB and click
search. It will show the detailed neighbor list between these two sites.
In the red marked area, there are all the existing neighbors between these two sites.
On the above are the available neighbor relations. Choose the one(s) we want and
All rights reserved. No spreading without permission of ZTE. Page29
Internal Use Only
click add. Please pay attention to the PCI, Cell ID and frequency column. Make sure
all information is right.
4.7 CA Configuration
For all sites which contain TDD cells, there is CA configuration on these sites.
a. Check the neighbor relations between Cell 11 and Cell 21, between Cell 12 and
Cell 22 and between Cell 13 and Cell 23, 6 relations as shown below.
We can search one site, and click query, then the result is shown. The correct setting
should be same as in this picture. Cell 11 and Cell 21 is one pair. Cell 12 and Cell 22 is
one pair. Cell 13 and Cell 23 is one pair.
But if there is no value here in DL CA, the parameter Cooperative Relationship Type
will be wrong.
Then we have to group it manually. Just Select the cell and click Group.
Find the correct neighbor cell (in this example, we should find Cell 21 of Site 220237)
and click OK. Synchronize and operation is done.
5. Dynamic Management
To check the status of each site, we use query cell status command. Double click the
command and click run.
Please pay attention that many sites have two modes, TDD&FDD. While the DT
engineers are testing, please make sure the mode you are checking is the same with
the one they are testing.
To manually shut down cell, we use immediate shut down cell command. Also,
please pay attention to mode, and choose the cell which needs to be shut down and
click run.
To start up the cells which are manually shut down before, we use start up cell
command. Similar like shutting down cells, choose the correct mode, correct cell and
click run.
To check how many users in one site, we can use query UE information command,
as following:
In the detailed information, one Successful row means one user. If it’s failed, it
means no user within this cell. In this example, there are 3 users in cell32, but no
user in cell31 and cell33. For more details, we can check it inside the result.
Before doing the drive test, sometimes we are not sure if all sites are up. So if we
want to start up all sites, we can do the following steps:
Select all sites and then start up all sites. We can see the number of selected NE. It
may take a long time to start up all cells.
Also, if there is a site list and we need to check the site status for these sites, it might
be difficult for us to check them one by one. Here we can export them in excel file
and use vlookup to check.
Only need to choose all the sites in cluster, and use Start DL Simulation Loading
(BPL1/BPN) command.
There are two steps needed. At first, click Parameter Config, select Analogy UE
priority and RB fixed. Then choose Life cycle according to the test period (2hours or
4hours or more).
After that, click Add. For FDD, we fill in RB number 6 and RB start position 19. For
TDD 20M, we use RB number 25 and RB start position 75. For TDD 10M, we use RB
number 12 and RB start position 38.
Pdsch loading power should be the same with PA which is mentioned in Section 4.2.
Better check the PA value first then choose the same result. (In this example, PA=0)
We can check the detailed parameters for DL simulation loading through Query DL
Simulation Loading (BPL1/BPN).
After click run, the detailed information is shown. This information is the parameters
we configured in section 5.6 (in Parameter Config and Add). We can export and
check if the configuration is correct.
After the test is finished, we have to stop DL simulation loading. Use command Stop
DL Simulation Loading (BPL1/BPN).
Select the correct command and click run, the result will show.
In our project, some sites are installed with RET (Remote Electronic Tilt), but some
are not. We can check the RET tilt in the following way:
Choose the site and use command Query RET Tilt and double click.
If it’s empty in the right part, it means this site is not configured with RET now.
In the example below, this site has both TDD and FDD, and all 9 cells have RET. The
tilt result is shown in the detailed information.
We can distinguish different cells by Customized description field. For FDD it’s easy
because FDD-800M-CELL1 means Cell 31, FDD-800M-CELL2 means Cell 32, and
FDD-800M-CELL3 means Cell 33. For TDD, TDD-2.3G-CELL-1-1 means Cell 11, while
TDD-2.3G-CELL1-2 means Cell 21. TDD-2.3G-CELL-2-1 means Cell 12, while
TDD-2.3G-CELL2-2 means Cell 22. TDD-2.3G-CELL-3-1 means Cell 13, while
TDD-2.3G-CELL3-2 means Cell 23.
According to the drive test result, sometimes we have to adjust the electronic tilt.
We use Set RET Tilt command.
Choose the cell first, then click run button. In this example, we set the tilt for TDD
cell 21. TDD-2.3G-CELL1-2 means cell 21.
Then double click the space under Attribute Value, you can fill in the value of
electronic tilt. In this example, we set the electronic tilt to 5 for cell 21.
Idle Mode:
Connected Mode:
Here shows the inter-frequency neighbor relations. As we can see, TDD 20M has
relations with both TDD 10M and FDD 5M. But TDD 10M ONLY has relations with
TDD 20M. FDD 5M ONLY has relations with TDD 20M.
No inter-frequency neighbor relations between TDD 10M and FDD 5M. So when we
are adding neighbors please do double check if we are following this strategy.
7. Performance management
Usually, for some frequently used KPI, we group them in a template so that we can
easily fetch the data.
Here we introduce the way of query NI for example. I already created the template,
so we can Query Template Management (we will introduce the way to create
template next):
Right click the name, and choose query by template. (Take NI_FDD for example,
NI_TDD is the same)
In the below dialog box, we only need to fill in Object Selection and Time Selection.
In Objection Selection, choose the sites you want to query or just select all sites
depending on the requirements.
At first, prepare the .csv file using the attached format. Then click Import Location,
select the prepared file. Then the cells in the .csv files are chosen.
Cluster_FDD.csv
In Time Selection, we have to choose one Query Granularity and select the Time
settings on the right, then click OK.
The results are shown here. We can click export and save as any version you want.
Input the name and description. And choose NE type (ME (MO SDR)), MO type
(usually [LTE] Serving Cell), and Mode filter (either LTE TDD, or LTE FDD, or both). We
can search the KPI or counters we need in the left and the selected ones are shown
in the right.
In Statistic Info, we can choose Location group, by cell or by others. Then click OK.
After that, the template we created is shown in the list. We can query it at anytime.
8. Query NE location
Sometimes the planning coordinate of the site is different from the actual one. To
query the longitude and latitude, we use Diagnosis Test.
Then, select the sites as you want or select all, then click OK. Wait for a while, the
result of longitude and latitude will show.
9. CC UDP Test
SF LTE CC UDP
Test Guideline V1.0.docx
MTS trace is for real-time tracing the UE throughput/CQI /MCS etc. We can know the
GID and throughput during UDP test through MTS trace.
Please pay attention here, do not delete the tasks created by other users.
Especially please don’t click that delete button shown below.
If we want to start a MTS trace, press these 3 letters (s u r) at the same time and a
window will show.
Totally EMS real-time trace can trace 6 cells only. So I suggest only trace one or two
cells. For FDD and TDD 20M, we only need to trace the serving cell (one cell). While
for CA test, we need to trace two cells, for example, cell 11&cell 21 together.
Then click Next, choose LTE BPL1(BPN), and click Next again.
Here is to choose the start time and end time. Default end time is one hour after
start time. If we need a longer time, we can change the end time to any value.
Let’s take the below picture for example. Usually we pay attention to 3 columns:
UEGid and Tput0 and Tput1. If there are a lot of users, there will be many different
Gids (only one user in this example). At first we should ask test engineers to do
download, then the throughput result will show here, then we can know the UEGid
for this test UE.
The throughput should be added by Tput0 and Tput1. For CA, as there are two cells,
the throughput should be four values add together. Like this example, the
throughput marked in the red area is about 90Mbps.
CC Iperf.docx
Before FDD PAC test, we need to modify one parameter, paForDTCH, which is
mentioned in Section 4.2 already. The recommended value is 0. Here is the way to
modify it.
First, in Data Batch Configuration Management, choose all sites in this cluster.
It’s time wasting if we click the sites one by one every time. We can Export Tree
Node after choosing all sites, and save as a cluster name. Then next time if we need
again we can Import Tree Node. But please pay attention if new sites are on air in
this cluster, we need to update.
Another way is in NE Filter, we can filter NE ID using comma to connect all NE IDs in
this cluster. Then copy and paste it in NE Filter. This is an example:
225265,225266,225020,225014,225221,220169,220173,220176,220175,225296,220
170,220172,220189,220181,220182,220183,220184,220186,220193,220194,220191
,220192,
After clicking OK, all sites in this cluster are filtered, and click all.
Third, modify parameter paForDTCH to 0 (in this parameter, 4 means 0)and save as
another excel file.
But please remember to rollback after test. Just need to import the exported file in
Step 2 and synchronize.
a. 20M Test
We need to shut down 10M cells while testing 20M. Also, we need to modify the
thresholdOfRSRP for Measurement Configuration Index=10 to -130. The way is
simillar with modifying paforDTCH in FDD.
Only when exporting data, we have to choose TDD UE E-UTRAN Measurement, and
then filter Measurement Configuration Index=10 as shown below:
Find the parameter thresholdOfRSRP in column N and change the value to -130.
Then save as another file.
b. 30M Test
We need to start up all 10M cells for 30M test. Also, we have to rollback the
parameter changed in 20M test. Just import the original exported file and
synchronize.