GSM Basics

HUAWEI TECHNOLOGIES CO., LTD.
All rights reserved

Internal
www.huawei.com
Introduction to the
Simulation Principles and
GENEX U-Net
GSM-to-UMTS Training Series_V1.0
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 1

Date
Revision
Version
Description Author
2008-12-31 1.0
Draft completed. Gao Bo
2009-01-08 1.1
Notes are added on pages 26, 30,
31, 61, and 67, and some
WCDMA terms used in this
document (not involved in the
GSM) are described.
Kuang
Jun
Brief Introduction to the GENEX U-Net
The GENEX U-Net is a professional design tool for the wireless network. It
supports GSM GPRS-EDGE, Is-95 CDMAOne,
CDMA2000 1xRTT 1xEVDO, UMTS WCDMA, UMTS HSDPA, and Microwave
Radio Link.
The GENEX U-Net has real mobility for planning and design, used in lots of
different items. It supports the single-server configuration and network
configuration based on an enterprise server. In single-server mode, users can
share the project data of the GENEX U-Net without connecting to an external
database.
The GENEX U-Net has a modern software architecture and an open
extensible platform.
Brief Introduction to the GENEX U-Net
Requirements for the hardware and software configuration of the GENEX
U-Net are as follows.
GENEX U-Net workstation
Pentium 3 processor or a processor with higher-level configuration
and 256 MB memory or larger (512 MB memory is recommended)
Windows NT 4.0, Windows 2000 Professional, or Windows XP
In single-server mode, the GENEX U-Net need not be connected to an
external database.
A multi-user structure supports the following database management
systems (not applicable to a single-user structure).
Microsoft Access 97/2000
Microsoft SQL Server 7.0
Oracle V 8.1.7 or a higher version
Sybase Adaptive Server V 11.5
Chapter 1 Simulation Principles
Chapter 2 Operations with the
Simulation Tool
Chapter 3 Common Reasons for
Users Being Rejected and FAQs
Principles of System Simulations
Reasons for using system simulations
The WCDMA system ensures connection quality through power
control. Coverage is nearly associated with capacity. Both the
coverage and capacity are affected by many random factors and
thus cannot be calculated directly. Most network performance
indicators required for planning need to be determined through
system simulations.
Principles of System Simulations
Principles of system simulations
Static simulations
During a static simulation, you can learn the network
performance by analyzing the snapshots.
Dynamic simulations
During a dynamic simulation, you can learn the network
performance by analyzing the movement of UEs in
successive timeslots.
Principles of System Simulations: Static
Simulations
Taking a certain number of snapshots of the network
Each snapshot generates a mobile station or terminal distribution
according to certain rules (such as random even distribution);
The capability of a terminal for connecting to the network is
obtained through iterative calculation;
Various causes to connection failures are considered (exceeding
the maximum uplink (UL) or downlink (DL) transmit power, no
available channels, low Ec/Io, and UL or DL interference);
The statistics of snapshots can be collected and analyzed for
knowing the network performance.
The Monte Carlo simulation is a static simulation.
The Monte Carlo Simulation
Principles of System Simulations: Static
Simulations
Features of the Monte Carlo Simulation
Through the generation and statistics of random variables,
a complex system involving several random variables can
be simulated.
The simulation results become more accurate when more
samples are provided.
The Monte Carlo Simulation
Coverage Probability
100%
100% 20%
60%
0% 75% 40% 60%
Dynamic Simulations
Taking a certain number of snapshots of the network
In dynamic simulations, the scenarios where UEs move on
the network are simulated.
The distribution of UEs (similar to a snapshot) is generated
in the first timeslot;
In Successive timeslots, which are then simulated
dependant upon simulation results of the previous timeslot;
The simulation process begins when a new mobile station
is connected to the network and ends when the
conversation is over.
Comparison Between Different Simulation
Methods
Static Simulations vs. Dynamic Simulations
Static Simulations: A large amount of data needs to be
calculated (the specific amount of data depends on the number
of snapshots). The configuration and results are complex but
accurate.
Dynamic Simulations: A large amount of data needs to be
calculated and the calculation takes a long time. In addition,
accurate traffic maps are required for dynamic simulations. The
simulation results cannot be used for reference if the traffic
maps are not accurate.
Simulation Tool
Procedure for a System Simulation
Import a map
Import engineering
parameters
Correct a
propagation model
Predict the
network coverage
Adjust the cell
structure
Set up a
traffic model
Macroscopic
view
Output simulation
results
Adjust the network
structure and configuration
Microscopic
view
Components of Electronic MapDigital Map
Clutter
Heights
Vectors
BDM (Option)
Data Formats of Digital Maps
The data folders of digital maps are classified into Heights, Vector,
Clutter and Building folders. Each folder contains configuration files.
The Index file contains information of region coordinate;
The Projection file contains the projection mode of a map, ellipsoid,
ID of a projection zone, central meridian, and accuracy of digital maps.
The Heights folder
R
o
o
t

d
i
r
e
c
t
o
r
y

o
f

a

d
i
g
i
t
a
l

m
a
p

The Clutter folder
The Vector folder
The Building folder
The height data of digital clutters is in the Heights folder, which includes the following
files.
Height data of digital clutters (demo.b file)
The height data of digital clutters is binary mode saved by raster
format, and the metadata is elevation values.
Index.txt file
The ASCII format text file in the Index.txt file contains the information
about the position of each Height binary file. This file must be saved in
the same directory with the height database.
Projection.txt file
The Projection file is a projection parameter file. Take a digital map for
example. The details are as follows.
WGS-84..................................................................... name of the ellipsoid
50................................ ID of the projection zone (not necessarily involved)
UTM.................................................................................. Projection mode
0.0 117.0 500000.0 0.0........................ coordinate conversion parameter
The data of digital clutter is in the Clutter folder, which includes the
following files.
Digital clutter file (domo.b)
The clutter data of digital clutters is binary mode saved by raster
format., the metadata is the codes with ground coverage types.
Index.txt file
The ASCII format text file in the Index.txt file contains the
information about the position of each Clutter binary file. This file
must be saved in the same directory with the clutter data.
Menu.txt file
The Menu.txt file contains tables relevant to the codes saved in
the binary Clutter file, The clutter file contains tests which
describe the clutter classes. Each track contains a code and
description, which are separated by a space. This file must be
saved in the same directory with the clutter data.
Vector data is in the Vector folder, which includes the following files.
*.txt or *.vec file
Vector data includes the information about clutter classes such as
highways, railways, and coastlines. The data can be saved in the
ASCII format in .txt format or in proprietary binary format. Each
feature can correspond to more than one file.
Index.txt file
The Index.txt file contains the information about the position of each
Vector file. This file must be saved in the same directory with the
vector data.
Building vector data is in the Building folder, which includes the following
files.
Building vector data is special version of common vector data. It
describes the appearance and height of buildings. The building vector
data is saved in the ASCII format constituted with a vector file, a
feature file, and an index file.
Project Parameters
Site parameters
Antenna parameters
Transmitter parameters
You can set the cells
parameter through the
right key menu.
Site Parameters: Device Parameters
Device parameters
Manufacturer: name of the manufacturer of BTS device, such as Huawei
(optional)
Multi-user detecting function: whether the device has the multi-user
detecting function to eliminate UL interference
Rake factor: efficiency parameter of the rake receiver
Carrier selection mode: carrier transmission mode of the device (such as
the minimum UL noise, the minimum DL power, and randomly selection)
UL/DL spending channel elements: number of elements of UL/DL
spending channels (such as pilot channels and synchronization channels)
configuredfor the device
Determining whether only neighboring cells can access the Active Set
UL/DL channel elements configured on the device for each user (mobile
phone)
Site Parameters: spending Channel
Parameters
Nb CEs used: basic spending channels configured according to each
carrier rate (service)
Equipment Service Nb CEs used (UL) Nb CEs used (DL)
BTS3812 12.2K voice 1 1
BTS3812 Email 3 2
BTS3812 MMs 3 2
BTS3812 stream 384 10 8
BTS3812 Video Phone 3 2
BTS3812 Web 5 4
Site Project Parameters
Longitude
Latitude
Altitude
Number of UL/DL
CEs available at
the site
installed equipment
at the site
Project Parameters: Information About
Antennas
Manufacturers: names of the manufacturers of antennas used in each
sector, such as Andrew and Katherine
Antenna gains: gains of different antennas; unit: dBi
Vertical and horizontal lobe patterns of antennas: vertical and
horizontal lobe patterns which is accurate by the attenuation of each
degree.
Diversity gain of antennas: The unit is dB. The gain is generally
involved in the demodulation threshold of the BTS. Therefore, the value
is defined as 0.
Beamwidth of the antennas
Highest and lowest transmit frequencies of antennas; unit: MHz
Transmitter Parameters (1)
Name of a cell, antenna type,
antenna height, azimuth, downtilt,
and other project parameters
Transmission loss and reception
loss can be calculated in automatic
or manual mode. In automatic
mode, the software considers the
loss of all types in calculation.
Cell calculation radius, primary and
secondary propagation models,
TMA, feeder types, BTS
equipment, feeder length, and
calculation accuracy
Transmitter Parameters (2)
Average frequency (FDD)
used by propagation model
Carrier number
Spread bandwidth
Io calculation mode
Total noise
Without pilot
Nt calculation mode
Total noise
Without useful signal (signal of the
considered cell)
Default remaining
orthogonality factor at the
receiver
Maximal Ratio Combining in
softer/soft (2 sites, 3 Txs) (use both
of rake factor and UL Macro-diversity
gain)
Gain applied to the max Eb/Nt on several links in SHO in
order to determine the resulting quality at the RNC
Cell Parameters
Number of cell carriers: setting a single carrier or multiple carriers
Cell power value: power values of different channels in each cell, which
include power allocation of pilot frequency, synchronization channel (SCH),
and other CCHs
ID's of scrambling codes: ID's of the scrambling codes for each cell. The
GENEX U-Net can automatically allocate scrambling codes.
AS threshold: a threshold value for cells to access the Active Set. This value
is the maximum D-value of Ec/Io between an admittable cell and the best
server; unit: dB.
Relationships of neighbors: a relationship list of neighboring cells in each
sector. If the list does not exist, the automatic neighbor allocation function of
the GENEX U-Net can be enabled to configure the relationships of
neighboring cells.
Transmitter Parameters: Transmitter Device
Parameters (1)
Tower mounted amplifier: If the transmitter in a sector uses a tower
mounted amplifier (TMA) and the loss and gain of the TMA cannot
be ignored, the following parameters are required.
Name of the TMA
Noise figure of the TMA; unit: dB
Receive gain of the TMA; unit: dB
Transmit loss of the TMA; unit: dB
Transmitter Parameters: Transmitter Device
Parameters (2)
FeederIf the loss of the feeder in a sector cannot be ignored, the
following parameters are required.
Name of the feeder device
Feeder length: length of the feeder for receiving and transmitting in
each sector
Average specific loss of the feeder: average specific loss of the
feeder; unit: dB/m
Feeder connector loss: transmit and receive loss of the feeder; unit:
dB
BTSIf the noise of the BTS in a sector cannot be ignored, the
following parameters are required.
Name of the BTS device
BTS noise figure: noise figure of the BTS; unit: dB
Other losses: other UL and DL losses in each sector; unit: dB
Noise figure of the devices in Huawei 3G BTS is the noise figure of the
entire device detected on the top port.
Propagation Models: Major WCDMA Models
Okumura/Hata model
Frequency band: 900 to 2,000 MHz
COST231-Hata Model
COST231 Walfish-Ikegami Model
Keenan-Motley Model
Applicable to indoor transmission
Standard Propagation Model (SPM)
Applicable to macro cells with a
frequency band of 150 MHz to 2 GHz

Standard Propagation Model (SPM)
Ploss path loss; unit: dB
K1 offset constant
K2 distance loss constant
K3 the correction factor of the antenna height in the BTS
K4 the multiplier for diffraction calculation (must be positive number)
K5 the multiplier for log(d)log(Heff)
K6 the correction factor of the antenna height at the mobile station
Kclutter the correction factor of clutter loss
d the distance between the BTS and the mobile station; unit: m
HmeffsHeffthe effective hights of the antennas at the mobile station and BTS;
unit: m
Ploss=K1+K2logd+K3log(Heff)+K4Diffraction+K5log(d)log(Heff)
+K6(Hmeff)+Kclutterf(clutter)
K
K1 -52.92
K2 68.6
K3 5.83
K4 1
K5 -6.55
K6 0
Import a map
Import engineering
parameters
Correct a
propagation model
Predict the
network coverage
Adjust the
cell structure
Set up a
traffic model
Adjust the network
Output
simulation results
Macroscopic
view
Microscopic
view
Predictions
Independent of Traffic

Dependent on Traffic
Pilot Coverage
Best Server
Overlapping zones
Service Database

Environments
User profiles
Terminals
Mobility types
Services

Mobility type
Name: The rates can be considered as names, such as 50 km/h, 90
km/h, and a pacing rate.
Ec/Io threshold: the minimum Ec/Io value required to access the
Active Set of the mobile phone. The threshold is relevant to the
moving rate of the mobile phone.
For previous data WCDMA/UMTS standards or experiential data can
be refered to.
Pilot quality threshold (depending on
speed) to define the best server of a
mobile active set
Mobility type name
Terminals
Name: name of the mobile phone
Min Power: minimum transmit power of the mobile phone; unit: dBm
Gain: antenna gain of the mobile phone; unit: dB
Losses: antenna losses of the mobile phone; unit: dB
Noise figure: noise figure of the mobile phone; unit: dB
Active Set size: size of the Active Set
DL rate factor: downlink rate factor
Minimum and maximum
allowed power (UL) during
power control simulation
Gain and loss in terminal
Noise figure used in the DL load
factor determination
Active set size : number of
transmitters which can be
connected to a mobile
(maximum 4 in UMTS)
DL rake factor used for the
signal recombination at the
terminal
Terminal name
Services (1)
Service name
Min and max allowed transmitter traffic
power per link
Circuit : DL and UL activity factors (DTX -
Time)
Packet : DL and UL packet efficiency
factors (unsuccessful data retransmission)
DL and UL coding factors (rate)
DL and UL nominal rate (kbps) (seen by the
user)
Service priority (0 : lowest)
Macro-diversity use
Type of service
Body loss used in link budget
Services (2)
DL and UL Eb/Nt targets per mobility
Service name such as voice, short
message, Web browse, and video
call
Coding factor of each service
Channel activity/efficiency factor of
each service
UL and DL nominal rate of each
service
Body loss of each service; unit: dB
Maximum and minimum power of
DL traffic channel; unit: dBm
UL and DL Eb/Nt value at each rate
of each service
User Profiles
Name: The clutter classes of the user locations can be used as names, such as
urban users and suburban users.
Names can also be defined according to the activities of users, such as high-end
users and low-end users.
User activities: frequencies of each service used by each type of users
The preceding data can be determined according to the results of market
research, OMC statistical results, or planning objectives.
User profile name
Which service
with which
terminal
Usage frequency with different definition
Circuit : average number of calls per hour, average duration of a call in seconds
Packet : DL and UL packet efficiency factors (unsuccessful data retransmission)
Environments (1)
Name of the traffic environment: Clutter classes can be used as
names such as urban and suburb.
Mobility type and density (number of users/km2) of each type of users
in each traffic environment
List of user profiles
with associated
mobility and density
Environment
type name
Environments2
l Allocated weight proportions of traffic for each
type of clutter, which include indoor and outdoor
environment
Possible clutter weighting in order
to get an accurate user
distribution
Import a map
Import engineering
parameters
Correct a
propagation model
Predict the
network coverage
Adjust the
cell structure
Set up a
traffic model
Adjust the network
Output
simulation results
Macroscopic
view
Microscopic
view
Process of Monte Carlo Simulation
Setting the input of service database
Defining parameters for Environments
Setting appropriate ranges for Environments on the map
Performing the simulation calculation
Saving the calculation result and doing analyzing

Simulation Parameter Setting
Name of the simulation group
Times of simulations
Save modes of Simulation results:
1. Only average statistical results are
output.
2. Information about the terminal is not
output.
3. Standard information about the
terminal is output.
4. Detailed information about the terminal
is output.
Setting the restrictions on the GENEX U-Net
during a power control simulation:
Maximum value of cell power
Maximum number of channel elements
Maximum UL cell load (default: 75)
Validity of the Walsh codes
Simulation Results: Distribution of Users and
Services
Reasons for Call Rejections
Number Symptom Rejection Reason
1 Ec/Io < (Ec/Io)min The quality of DL pilot signals is not good.
2
Ptch > PtchMax (FCH or
SCH)
The receive power of DL traffic channel is
not adequate.
3 Pmob > PmobMax The UL transmit power is not adequate.
4 Admission rejection UL or DL access threshold is reached.
5
Load saturation (when the
admission is permitted or
congestion occurs )
The signal quality is not good (see rejection
reasons 1, 2, and 3). Thus, the maximum
load factor is exceeded.
6 Channel element saturation
reasons 1, 2, and 3). Thus, the site does
not have sufficient channel elements.
7 Cell power saturation
reasons 1, 2, and 3). Thus, the cell does
not have adequate power.
8 OVSF code saturation
reasons 1, 2, and 3). Thus, the OVSF
codes are saturated.
9 Multiple causes
When the network is saturated, any of the
preceding reasons may cause rejection to the
access of a mobile station.
Simulation Results: Statistics and Analyzing
System Simulation Outputs
Basic outputs of system simulations
Pilot coverage map of target planning region: Ec, Ec/Io
Best server distribution map
Geographical distribution map of communication probability of
each service
Geographical distribution map of Eb/Nt of each service
Geographical distribution map of UL and DL load of each cell
Geographical distribution map of pilot pollution conditions
Geographical distribution map of the handoff status of each
service
Pilot Coverage
Ec/Io
Best Server
Effective Service Area
Downlink Eb/Nt
Uplink Load
Pilot Pollution
Handoff Status
Neighbor Allocation Principles
1. Cells adjacent to each other are generally considered as neighboring cells. Neighboring
cells are generally neighbors to each other, that is, if sector carrier A takes B as a
neighbor, B should also take A as a neighbor.
2. In dense urban areas and common urban areas, the distance between sites are short (0.5
to 1.5 kilometre) and thus more neighboring cells should be configured. Currently, the
maximum number of intra-frequency, inter-frequency and inter-system neighboring cells
are respectively 32. Therefore, when configuring neighboring pilot frequencies, pay
attention to the number of neighbors. Those who are really neighbors should be
included and those who are not should be excluded, avoid to impropriate the
quota of neighboring cells gather.so that real pilot frequencies are not excluded from
the neighboring set to cause interference. In an actual network, adequate neighboring
cells should be configured but excessive neighboring cells should be avoided.
Neighbor Allocation Principles
3. In suburbs and suburban counties, though the distance between
sites is long, cells adjacent to each other must be considered as
neighboring cells to ensure quick handoff and avoid call drops.
4. In the WCDMA system, the neighboring cells do not have an
order and the detection period is short (generally a detection
period of 320 ms is required for 32 intra-frequency cells).
Therefore, neighboring cells only need to be neighboring cells
only need to be considered no miss,but do not need to be
ordered according to signal strength.
Classification of Neighboring Cells
Intra-frequency neighboring cells
Inter-frequency neighboring cells
Inter-system neighboring cells
Automatic Neighbor Planning
Configuration Parameters
Max number of neighbors: the maximum number of
neighboring cells. Generally, this parameter is set to
32.
Force co-site cells as neighbors: whether the co-site
cells always be configured as neighboring cells.
Generally, this parameter is set to yes.
Force adjacent cells as neighbors: whether the
adjacent cells be configured as neighboring cells.
Generally, this parameter is set to yes.
Force symmetry: whether neighboring cells are
neighbors to each other. Generally, this parameter is
set to no.
Force exceptional pairs: whether exceptions exists
Reset neighbors: resetting neighboring cells
Coverage conditions: coverage conditions that the
neighbor allocation should satisfy
% Min covered area: the minimum percentage of
covered area
Results of Planning
Cell Number Neighbour Distance ( m) Symmetry
Reason
(automatic
allocation)
2504-1 4 2504-2 0 True Co-Site
2504-1 4 2504-3 0 True Co-Site
2504-1 4 2519-1 2,066 True Symmetric
2504-1 4 2804-1 1,224 False Symmetric
2504-2 5 2504-1 0 True Co-Site
2504-2 5 2504-3 0 True Co-Site
2504-2 5 2581-1 1,496 True Symmetric
2504-2 5 2581-3 1,496 True Symmetric
2504-2 5 2804-1 1,224 True Symmetric
2504-3 5 2504-1 0 True Co-Site
2504-3 5 2504-2 0 True Co-Site
2504-3 5 2519-1 2,066 True Symmetric
2504-3 5 2804-1 1,224 True Symmetric
2504-3 5 2804-3 1,224 True Symmetric
Principles for Scrambling Code Planning
The allocation of DL primary scrambling codes does not affect the simulation of
the network. The number of DL primary scrambling codes, however, is only 512.
Because of limited resources, the allocation of DL primary scrambling codes
must be considered during the cell planning. Considering the future expansion
and coverage of the network, not all the DL primary scrambling codes are used
at the initial phase of the network planning. Some of the scrambling codes
should be reserved. Reasonable planning of DL primary scrambling codes is
required. Thus, the utilization of code resources can be enhanced through the
reuse of scrambling codes.
In the planning of primary scrambling codes of the cells, intra-frequency cells
that cause interference to the primary cell should not use the same primary
scrambling codes as the primary cell.

Parameters for Scrambling Code Planning (1)

Existing neighbors in
the Neighbours form
(the Existing
neighbours option)
A cell and its
neighbors cannot have
the same scrambling
codes. The neighbors
of the cell cannot have
the same scrambling
codes.
Neighbors of listed
neighboring cells (the
Second neighbours
option)
A cell and its
neighbors cannot have
the same scrambling
codes. In addition, all
the neighbors (first
neighbors and second
neighbors) cannot
have the same
scrambling codes.
512 Scrambling Codes
64 clusters and each includes eight codes
ID's of the clusters: 0-63
ID's of the codes: 0-511
Modeling
Domainborder or region
Groupcluster
A domaina group
One domain in each cell
Allocation Standards
Neighborship
Primary
Secondary
Extra constraints of Ec/Io (optional)
Reuse distance
Comparison between the inter-transmitter distance and
the reuse distance
Weighted calculation of the inter-transmitter distance by
the antenna azimuth
SC domain that is allocated to the cell
Results of Scrambling Code Planning
Review: Operation Procedure for the GENEX U-Net
Simulation Tool

Common Reasons for Users Being Rejected (1)
Pmob>PmobMax
Reason: The power of the mobile phone is not adequate.
Solution: Ensure that the maximum and minimum power of
the terminal is proper.

Ptch>PtchMax
Reason: The power of
traffic channel is not
adequate.
Solution: Ensure that the
maximum and minimum
allowed DL traffic power
is properly set.

Ec/Io>(Ec/Io)min
Reason: Ec/Io fails to reach the Ec/Io threshold to access the
Active Set.
Solution: Choose UMTS Parameters > Mobility Type >
properties for setting. Generally, the value cannot be modified,
because it is determined by the corresponding standard or device.
Only the azimuth or downtilt of the transmitter can be adjusted to
improve the network quality and lower the rejection rate.

Load saturation
Reason: network load saturation
Solution: Increase UL load. Generally, the parameter cannot be
modified. Reduce the number of users to reduce the network load.
You can also add more BTSs to improve the network bearer
capability.
Ch.Elts saturation
Reason: lack of channel elements (CEs)
Solution: Ensure that the number of CEs in the BTS is proper.
Cell power saturation
Reason: cell power saturation
Solution: Ensure that the allowable power of DL traffic serve
channel is properly set.
Multiple causes
Reasons: The same user is rejected in different iterations for different
reasons.
Solution: Check for the other main causes besides multiple cause. In
most cases, a user is not rejected for this reason. The times of being
rejected for this reason can be reduced by reducing the main reasons
for rejection.
Code saturation
Reason: lack of code
resources
Solution: As shown in the
following figure, if Number
of Codes is not selected,
code resources are not
considered during the
simulation. In addition,
Coding factor in the
Service Attribute window
should be proper.
Generally, the Coding
Factor is set to 1.

Admission rejection
Reason: The UL interference is too strong.
Solution: Lower the height of the antennas (the most effective
way);
Enlarge the downtilt of the antennas, and RET
antennas is preferred. Generally, set the mechanical tilt less than
six degree.
Adjust the azimuth;
Change the antennas;
Add BTSs.

Appendix: DL Load Prediction
Add a column to the Cells form. hit right key of mouse, the title bar of
Cells and choose Table Fields. See the following figure.

Click Add in the displayed dialog box and type the name of the column,
such as DL Load (%). Select the data type in Type. Enter the size in
Size. Click OK. The DL Load Column is added to Cells. DL Load (%
Used Power) of the simulation results of each sector can be copied to
this column.

hit right key of
mouse
Simulation
Group (or Single
Simulation) and
choose Average
Simulation (or
Properties). Find
DL Load (% Used
Power) in
Average [1xPTT],
as shown in the
following figure.
Copy the data in this
column to the DL
Load Column in
Cells.
Predict DL load
through Coverage by
Transmitter. Create
a Coverage by
Transmitter item.
Choose Value
Intervals in Display
Type on the Display
tab page. Choose
Cells: DL Load (%)
in Field. Set other
parameters according
to the actual situation.
See the following
figure.

www.huawei.com

GSM Basics

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

GSM Basics

Загружено:

Авторское право:

Доступные форматы

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

Вам также может понравиться