FO - NP2004 LTE Networking Parameter Planning

LTE Networking Parameter Planning
EUTRAN Parameter Planning
Contents
1. ECGI Planning ...................................................................................................................... 3
1.1 ENodeB ID .......................................................................................................................................... 3
1.1.1 Overview ................................................................................................................................... 3
1.1.2 Configuration Principles ............................................................................................................ 3
1.2 Cell ID ................................................................................................................................................. 4
1.2.1 Overview ................................................................................................................................... 4
1.2.2 Configuration Principles ............................................................................................................ 5
2. Tracking Area Code Planning .............................................................................................. 6
2.1 Overview ............................................................................................................................................. 6
2.1.1 Paging ........................................................................................................................................ 6
2.1.2 Paging Occasion ........................................................................................................................ 7
2.1.3 Maximum Number of UEs That Can Be Paged Per Second...................................................... 9
2.2 Configuration Principles ...................................................................................................................... 9
2.2.1 Factors for TA Division ............................................................................................................. 9
2.2.2 Relevant Parameter Configuration Principles .......................................................................... 10
3. Physical Cell ID Planning ................................................................................................... 12
3.1 Overview ........................................................................................................................................... 12
3.2 Configuration Principles .................................................................................................................... 13
3.3 Settings in Netmax............................................................................................................................. 14
3.4 Setting in the Network Management System (NMS) ........................................................................ 14
4. PRACH Planning ................................................................................................................ 16
4.1 Overview ........................................................................................................................................... 16
4.4 Setting in the NMS ............................................................................................................................ 20
5. Neighboring Cell Planning ................................................................................................. 22
5.1 Overview ........................................................................................................................................... 22
6. Frequency Planning ............................................................................................................ 26
6.1 Overview ........................................................................................................................................... 26
6.2 ICIC Classification ............................................................................................................................ 27
6.2.1 Based On Same-Frequency...................................................................................................... 27
6.2.2 Based on SFR (Non Exclusive IC) .......................................................................................... 27
6.2.3 Based on SFR(Exclusive IC) ................................................................................................... 27
6.2.4 Based on Differ-Frequency ...................................................................................................... 28
i
Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. Error! Use the
Home tab to apply 标题 1 to the text that you want to appear here.
1. ECGI Planning
ECGI = PLMN + Cell Identity
PLMN = MCC + MNC
A Mobile Country Code (MCC), consisting of three decimal digits, is a code

used to identify the country that a mobile subscriber belongs to. Range: 0–999.
A Mobile Network Code (MNC) consists of two or three decimal digits. Range:
0–999.
Cell Idendity = eNodeB ID + Cell ID
A Cell Identity consists of 28 bits. The former 20 bits indicate the eNodeB ID,
and the latter 8 bits indicate the Cell ID.
1.1 ENodeB ID
1.1.1 Overview
ENodeB ID range: 0–1048575. An eNodeB ID is used in combination with a

PLMN and a Cell ID to form an ECGI. An eNodeB ID is used to uniquely identify
an eNodeB in a PLMN, meaning that an eNodeB ID is unique in an operator
network of a country.
1.1.2 Configuration Principles
Particular situations of different operators should be taken into account.
1. Small-sized network
If an operator has only one small-sized network, eNodeB IDs can be

numbered sequentially starting from 0.
2. Standard-sized network
ENodeB ID format in a standard-sized network: ABCDEF
AB indicates a city and a maximum of 99 cities can be represented.
F indicates whether it is an indoor or outdoor eNodeB. If F is set to 0, it

indicates an indoor eNodeB. Otherwise, it indicates an outdoor eNodeB.
3. Large-sized network
3
For China Mobile, eNodeB ID assignment within the entire network

should be taken into account. Coordination is required between different
cities.
If all the cities in China are planned together, different AB combinations

can indicate a maximum of 99 cities, each of which can accommodate a
maximum of 9999 eNodeBs.
If there are over 99 cities involved in the network, an AB combination can

indicate two or more cities, which can accommodate a maximum of 9999
eNodeBs in total. For example, if three cities use the same AB
combination, each city can accommodate an average of 3333 eNodeBs.
If a province has several small cities that have no large-sized sites, these
cities can be assigned the same AB combination. Other identities can be
used to differentiate these cities.
F indicates whether it is an indoor or outdoor eNodeB. If F is set to 0, it

indicates an indoor eNodeB. Otherwise, it indicates an outdoor eNodeB.
In some special cases, the value 9 for F indicates a remote eNodeB.
If the range that ABCDEF covers cannot meet the particular

requirements, you can use either of the following methods:
1) ABCDE: a maximum of 100,000 numbers, ranging from 0 to 99999,

can be used.
2) ABCDEFG: 48,575 more numbers can be used. If 500 numbers are
reserved, 48,000 numbers are still available.
4. Shared network
For a shared network, such as the TDD-FDD network of Hi3G, the TDD
network and the FDD network should share eNodeB IDs, and 6-digit
eNodeB IDs (format: ABCDEF) can be used as described below. Note
that solution change is not required if the solution has been confirmed.
1) A indicates the network system. The value 1 indicates a TDD network,

and 5 indicates an FDD network.
2) B indicates the city where the eNodeB is located. C can indicate
nothing special, and can also indicate the administrative region
where the eNodeB is located.
4) F indicates whether it is an indoor or outdoor eNodeB. If F is set to 0,
it indicates an indoor eNodeB. Otherwise, it indicates an outdoor
eNodeB.
1.2 Cell ID
1.2.1 Overview
The last eight bits of an ECGI indicate the Cell ID. A Cell ID is used in
combination with a PLMN and an eNodeB ID to form an ECGI. A Cell ID is used
4
Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. Error! Use the Home
tab to apply 标题 1 to the text that you want to appear here.
to uniquely identify a cell in a PLMN, meaning that a Cell ID is unique in an

eNodeB.
1.2.2 Configuration Principles
A Cell ID is unique within an eNodeB.
By default, Cell IDs start from 0, and 0, 1, and 2 indicates three cells
respectively. If there are over three cells, number them sequentially.
For indoor sites, Cell IDs can start from 100.
If different manufacturers and different network systems share Cell IDs, the
following rules can be used:
1) Outdoor site Cell IDs can start from 0.

2) Indoor site Cell IDs can start from 100.
3) Cell IDs for different manufacturers can start form 200.
An example is as follows: For an FDD network in China, numbers 0 to 3 are

used for 2.1 GHz band-1 cells, and numbers 48 to 51 are used for 1.8 GHz
band-3 cells.
5
2. Tracking Area Code Planning

2.1 Overview
A Tracking Area Code (TAC) is the code of a tracking area in a PLMN. A TAC
must be unique in a PLMN. TACs are used to manage UE locations and page
UEs.
TAI = PLMN + TAC
A cell must belong to a Tracking Area (TA), and belongs to only one TA.
When you plan a TAC, you must consider the number of cells in this TA. If too
many cells are included in a TA, paging costs may increase. If too few cells are
included in a TA, location update costs may increase. The binding relation
between a TAC and a cell is determined by the cell size, cell type (high-speed
cell or low-speed cell), and TA list configuration.
TA is similar to LA/RA in 2G/3G. In an LTE network, CN is invisible to cells (a

concept in an access network), and only visible to TAs. A TA corresponds to one
or multiple cells. In a Core Network (CN), UEs are paged in a TA or TA list, and
eNodeB checks the mapping between the TA and cells and then pages UEs in
the corresponding cells.
In LTE, TA list is introduced. Tracking Area Update (TAU) can be originated only
in a TA list boundary. This helps to reduce the number of TAUs. This also results
in paging workload increase. For an LTE system with high paging capabilities,
the LTE system burden to process such sudden numerous paging messages
needs to be assessed further. The size of a TA should be similar to or even
smaller than that of an RA (a TA list is equivalent to an RA). Currently, one TA is
included in a TA list by default. For future networking scenarios where more
than one TA is required in a TA list, you can analyze the scenarios and plan
relevant configurations till then.
2.1.1 Paging
A UE uses a P-RNTI to periodically monitor a PDCCH to know whether a paging

message exits on a PDSCH. If yes, the UE decodes the PCH paging message
contained on the PDSCH, and checks whether the decoded paging message
contains a record of paging this UE.
Each paging message contains a Paging Record List. This list contains the
records of all UEs that have been paged related to this message. Each record
contains a P-RNTI, which is a UE identifier for paging purposes. ENodeBs page
UEs through either IMSIs or S-TMSIs.
6
Figure 2-1 IMSI Structure
As shown in Figure 2-1, an IMSI is an identity consisting of not more than 15

digits. An IMSI consists of a 2-byte MCC, a 2-byte MNC, and a 4-byte MSIN.
Therefore, the length of an IMSI is eight bytes. An S-TMSI consists of an 8-bit
MMEC and a 32-bit M-TMSI. Therefore, the length of an S-TMSI is five bytes.
If S-TMSIs are used for paging UEs, the length of each paging record is about
five bytes.
If IMSIs are used for paging UEs, the length of each paging record is about
eight bytes. System paging capabilities can be estimated on the assumption
that an average of seven bytes is used for paging a UE. A PCH uses QPSK
modulation. A paging message is transferred on a PDSCH. For the convenience
of paging information design, each paging message includes at most 16 UE
records, meaning that a maximum of 16 UEs can be paged simultaneously.
2.1.2 Paging Occasion
A Paging Occasion (PO) is determined by two parameters: a frame parameter

Paging Frame (PF), and a sub-frame parameter OP. UEs paged need to be
grouped to prevent these UEs from originating random access within the same
period and to prevent excessively long paging messages. Radio resources can
be effectively used if these UEs can be distributed at regular intervals within that
period. When Discontinuous Reception (DRX) is used, each UE can be paged
only once in each cycle.
PF formula:
SFN mod T = (T/N) × (UE_ID mod N) formula 2.1-1
PO formula:
i_s = floor (UE_ID/N) mod Ns formula 2.1-2
For the value that the PO corresponding to a specified i_s is mapped to in TDD,
see Table 2-1.
Parameter value ranges in the two formulas are as follows:

7
● T (default paging cycle): 32, 64, 128, or 256 radio frames
● nB (one of parameters to derive the PF and PO. Value in multiples of T). Options
include 4T, 2T, T, 1/2T, 1/4T, 1/8T, 1/16T, or 1/32T.
● N (number of paging groups): min(T, nB)
● Ns (number of sub-frame paging groups): max(1, nB/T)
● UE_ID: IMSI mod 1024
Formula 2.1-3 shows that each PF has only one PO when nB is no greater than
T. If nB is greater than T, each PF can have two or four POs, and the
corresponding nB values are 2T and 4T respectively. The nB parameter directly
determines the number of times that paging can be originated within a T. Along
with the increase of sub-frames used for UE paging in each radio frame, the
paging capabilities also increase. The maximum value of nB is 4T, which
determines that at most four times of paging can be originated within a radio
frame. The maximum value of T is 256. In the corresponding cycle, there are
altogether 1024 POs, which is the upper limit supported by the current protocol.
Table 2-1 Sub-frame Patterns in TDD (all UL/DL patterns)
Ns PO when i_s=0 PO when i_s=1 PO when i_s=2 PO when i_s=3

1 0 N/A N/A N/A
2 0 5 N/A N/A
4 0 1 5 6
Table 2-2 lists the paging sub-frames available in TDD. In TDD, multiple uplink
and downlink sub-frame distribution exists. To prevent the protocol layer from
sending signals to instruct specified paging sub-frame locations, sub-frames 0
and 5 should be used preferentially because they are always downlink. DwPTS
in special sub-frames 1 and 6 should be considered secondly, because each of
these frames has a maximum of four paging sub-frames.
For the length of DwPTS, GP, and UpPTS in TDD, refer to Table 2-2. This table
shows that the length of DwPTS is at least three OFDM symbols, where the first
two are used for PDCCHs and the third is used for primary synchronization
signals. The length of DwPTS for configurations 0 and 5 is three OFDM symbols.
This is applicable to sparsely populated macro cells. Besides, the length of
DwPTS is six to nine OFDM symbols used for PDSCHs.
8
Table 2-2 Length of DwPTS, GP, and UpPTS in TDD
Configuration Normal CP Extended CP
DwPTS GP UpPTS DwPTS GP UpPTS
0 3 10 1 3 8 1
1 9 4 1 8 3 1
2 10 3 1 9 2 1
3 11 2 1 10 1 1
4 12 1 1 3 7 2
5 3 9 2 8 2 2
6 9 3 2 9 1 2
7 10 2 2 - - -
8 11 1 2 - - -
2.1.3 Maximum Number of UEs That Can Be Paged Per Second
The maximum number of UEs that a system can page is associated with the
setting of nB, as show in Table 2-3.
Table 2-3 Relation Between the Maximum Number of UEs That Can Be Paged and nB Setting
nB 4T 2T T 1/2T 1/4T 1/8T 1/16T 1/32T

Maximum
number of
UEs that
400 × 16 200 × 16 100 × 16 50 × 16 25 × 16 12.5 × 16 6.25 × 16 3.125 × 16
can be
paged per
second
When nB is set to 1/2T, 800 UEs can be paged every second. When nB is set to
1/4T, 400 UEs can be paged every second. The value can be set based on the
particular environment and paging requirements.
2.2 Configuration Principles

2.2.1 Factors for TA Division
1. Mobile stations
If the value of TAC is set too small, mobile station location updates will
increase so that signaling traffic will also increase. If the value of TAC is
set too large, a message that the network uses to page the same mobile
station will be sent to multiple cells, causing PCHs to be overloaded.
2. Geographical positions
9
TACs should be planned based on geographical distribution and

behavior of mobile subscribers to ensure that locations are updated less
frequently in LAC boundaries.
If there are two or more LAs in a heavy-traffic large city, topographical

features such as mountains or rivers in the city can be used as the
boundary between two adjacent LAs. In this way, two adjacent LAs can
overlap as slightly as possible. If such topographical features do not exist,
streets, shopping malls, or other heavy-traffic areas must not be used as
boundaries. TA boundaries must not be orthogonal or diagonal to the
road. TA boundaries must obliquely cross roads. In areas where
downtown places and suburbs meet, LA boundaries are generally placed
at peripheral frontline ENodeBs rather than heavy-traffic suburban
junctions to prevent frequent subscriber location updates in the suburban
junctions.
3. A TAC/TAL must not cross multiple MMEs.
2.2.2 Relevant Parameter Configuration Principles
In the current protocol, two paging DRX parameters are defined for each cell:
defaultPagingCycle and nB. Both parameters are specified in SIB2 (a system
message). PO and PF are both determined by these two parameters and
UE_ID.
The paging cycle is the smaller of the default DRX Cycle Length for Paging
contained in cell system information and UE specific DRX. UE specific DRX is
introduced because multiple types of terminals need to access
E-UTRANs .Some terminals, for example, laptops equipped with LTE data
cards, are sensitive to battery consumption. Some terminals, for example, LTE
mobile phones, hope to be paged as soon as possible. Therefore, the current
protocol supports UE specific DRX (optional).
Formula 2.2-1 shows that T/N is used to group a paging cycle. Its values 1, 2, 4,
8, 16, and 32 correspond to the number of paging groups. If N is not greater
than T, each UE can be paged once during the time period T. UE_ID mod N is
used to assign UEs to paging groups evenly.
 Configuration rule for nB
The configuration of nB is related to the traffic model of the local area. The
traffic model includes the original call traffic and the call traffic generated
during a handoff. It is recommended that nB is set to 1/2T initially.
 Configuration rules for T
The configuration of T is related to service OoS requirements. The T

parameter directly affects service call establishment delay. If the delay is
too long, the service OoS will be affected.
10
The configuration of T is related to UE power consumption. The value of T

should not be set too small if service OoS requirements can be met.
For a heavily and densely loaded area, the value of T should be set
smaller.
It is recommended that T be set to 64 initially.
11
3. Physical Cell ID Planning

3.1 Overview
Physical Cell ID (PCI) is the ID of a cell at the physical layer. An LTE system has
a maximum of 504 PCIs, ranging from 0 to 503. PCIs are divided into 168
groups, each of which contains three IDs. A UE checks SSCHs to identify which
PCI group among the 168 groups the UE belongs to, and checks PSCHs to
identify which PCI in the group the UE belongs to.
cell
N ID  3N ID
(1)
 N ID
(2)
(2)
The primary synchronization signal contains N ID (0-2) PCIs, and the
(1)
secondary synchronization signal contains N ID (0-167) PCls.
In a specified geographical area, the PCI of a cell is different from that of any
other cell. PCIs can be used for distinguishing one cell from another, and
generating scrambling codes and security keys for specified cells. A PCI must
be unique at the same frequency point in the same area, even at the boundaries
between different PLMNs. Otherwise, cells with the same PCI may cover the
same place; or a cell may have two or more neighboring cells with the same PCI.
Generally, a macro eNodeB has three cells. It is recommended that 0, 1, or 2 be
(2)
used for N ID . In this case, the Primary Synchronization Channels (PSCH) of a
cell can be distinguished from that of a neighboring cell.
PCIs are mainly used for searching for cells in a network. The detailed flow is as
follows:
Cells are detected through multiple downlink channels, including SCHs, BCHs,
and RSs.
SCHs are divided into PSCHs and Secondary Synchronization Channels

(SSCHs). BCHs are divided into Primary Broadcast Channels (PBCHs) and
Dynamic Broadcast Channels (DBCHs). PBCHs appear as formal channels. As
pure L1 channels, PSCHs and SSCHs are not used to transfer L2 and L3
control signals but are only used for synchronization and cell search. DBCHs do
not have their own channels and are finally contained in Downlink Shared
Channels (DL-SCHs). How a UE searches for cells is as follows:
A UE detects the PSCH to obtain the 5 ms clock and the cell IDs in a cell ID
group.
The UE detects the SSCH to obtain the RAN clock, the cell ID group and the
BCH antenna configuration.
The UE detects the downlink reference signals to obtain the BCH antenna
configuration and check whether pilot frequency shift is in use.
12
The UE reads the BCH to obtain the information about other cells.

1. In the current software, PCIs should be assigned in accordance with the
following principles:
1) Cells in the same site must have different PCIs.

2) The PCI of one neighboring cell of a cell must be different from that
of another neighboring cell of the same cell.
3) When PCIs are assigned to different cells controlled by the same
eNodeB, the values of “PCI mod 3” must be different. This principle
also apply when PCIs are assigned to a cell and its nearest
neighboring cell.
4) Cells sharing the same PCI should be as far from each other as
possible.
5) The following principles should apply when PCIs need to be reused
for cells farther than the specified reuse distance.
PCIs should be reused based on priorities. Assume that the PCIs in

group M are all assigned and PCI reuse is required for cell Z. In this
case, based on matrixes I and F, you must select, from the assigned
PCIs, the PCI whose cell priority is the lowest among all neighboring
cells. You can follow this rule to assign PCIs to other cells that need
to reuse PCIs used.
2. Generally, it is recommended that the following rules be followed for

using PCIs:
1) Reserve nine PCIs for CSG cells, which refer to eNodeBs in

particular currently. (PCI range: 495–503)
2) Reserve twenty-one PCIs for indoor coverage systems and micro
base stations. (PCI range: 474–494)
3) Reserve nine PCIs for new macro base stations.(PCI range:
465–473)
4) Use other PCIs for macro base stations. (PCI range: 0–464)
5) Provide reservation policies for boundaries between equipment
manufacturers. It is recommended that different PCIs be reserved for
different manufacturers to avoid boundary problems. You need to
negotiate with equipment manufacturers involved.
6) In a local environment, the same PCIs can be used for different
carrier frequencies.
13
3.3 Settings in Netmax

Figure 3-1 shows the PCI settings in NetMAX.
Figure 3-1 PCI Settings in NetMAX
 Note:
Angle To Distance Ratio: An angel is converted into a distance by being
multiplied by this parameter. Cells whose antennas are directly faced should be
preferentially added as mutual neighboring cells. You can use the default setting
currently. You need to use this parameter in combination with Reuse Distance.
Reuse Distance (m): PCIs are not allowed to be reused within the distance
specified by this parameter. .
Available PCI: all available PCIs for this planning.
Selected PCI: PCIs selected for this planning.
3.4 Setting in the Network Management System (NMS)

After planning PCIs with NetMAX, you can use a template to export the
planning result, and then use the template to import the planning result to the
NMS. Based on the result, the NMS will automatically update the data.
Figure 3-2 shows how to enter the result import dialog box in the NMS.
14
Figure 3-2 Path to the Inter Me Configuration Import and Export Dialog Box
In the Inter Me Configuration Import and Export dialog box, select

Operation > Config Data Import > ltetdd-ENodeB Radio Data. Click the Add
Data File button to start importing data.
Figure 3-3 Importing Radio Parameters
Figure 3-4 shows the PCI setting for a serving cell.
Figure 3-4 Serving Cell PCI Setting
15
4. PRACH Planning
4.1 Overview
Physical Random Access Channel (PRACH) is mainly used in the random
access procedure. Random access for a UE in an LTE network is used to:
 Establish uplink synchronization for example during initial access or

handoffs.
 Assign a unique C-RNTI for the UE during initial network access
establishment, for example, when the status is changed from RRC_IDLE to
RRC_CONNECTED.
There are two types of random access methods in the LTE system.
 Contention-based access
A contention-based access procedure can be triggered in any random access

scenario. During such a procedure, a UE randomly selects a preamble. Multiple
UEs may select the same preamble to send and collision will occur. A
contention solution is then required.
 Contention–free access
In the random access scenarios where a UE in RRC_CONNECTED state

needs to receive new downlink data or perform a handoff, an eNodeB can
assign a specified preamble to the UE to avoid contention and ensure random
access success rates.

Currently, PRACHs have the following five formats. Format 4 can only be used
in TDD LTE networks, and the main feature of this format is that fewer
resources are used because PRACHs are transmitted on UPPTS. It is
recommended that format 0 be used for outdoor coverage and FDD indoor
coverage, and that format 4 be used for TDD indoor coverage.
Table 4-1 PRACH Formats
Preamble Format Tcp (Ts) Tseq (Ts)

0 3168 24576
1 21024 24576
2 6240 2 × 24576
3 21024 2 × 24576
4 (frame structure type 2 only) 448 4096
16
Figure 4-1 PRACH Formats
1. Main input parameters and recommended default settings
1) CellUEAvgSpeed (average speed of a UE in a cell): 50

2) UESpeedThrdRa (speed threshold of the UE in the cell): 120
3) CellRadius (radius of the cell): 5 km
4) NumContFreeRA (number of contention-free random access times
every second): 100
5) NumContRA (number of contention-based random access times
every second): 300
6) RACollProb (random access collision probability that the cell
expects): 1%
7) PhyCell ID (physical cell ID): assigned based on the PCI algorithm.
8) UlDlConfig (uplink and downlink configuration): assigned based on
the actual environment. Default: 2: 2.
9) CellRadiusThr (cell radius threshold): 5.5 km
2. Main output parameters
RaNcsType (random access Ncs type): high-speed scenario or

low-speed scenario determined by UE speed.
Preamble Format: one of the five formats determined by CellRadius

and CellRadiusThr.
NcsPrach (preamble Ncs PRACH): determined by RaNcsType,

Preamble Format, channel scenario (outdoor: NLos, indoor: LOS), and
CellRadius.
64-NumRAPreambles (contention-free preamble quantity): determined

by NumContFreeRA and RASlot (number of slots accessed randomly
every second). If there are 64 access preambles in total,
NumRAPreambles = 64 – (64-NumRAPreambles).
PrachConfIndex (random access configuration index): The value

ranges of the NumContRA, RACollProb, and NumRAPreambles
parameters are checked in a table to obtain the value of RASlot. In
17
addition, based on Preamble Format and UlDlConfig, the value of

PrachConfIndex is finally determined.
RootSequenceStartNumber (logical root sequence configuration for

random access): Based on NcsPrach and speed scenario, Ncs quantity
and μ quantity are determined. Continuous root μ is used for each cell. If
the first root μ is known, other root μs can be obtained.
Based on the default parameter settings recommended in Step 1, default

PRACH output parameters can be derived as follows.
After the parameters are set as described above, the final PRACH
parameters are as follows:
1) RaNcsType = FALSE
2) Preamble Format = 0
3) NcsPrach = 9
4) NumRAPreambles = 60
5) PrachConfIndex = 15
3. Configuration Principles
Format selection: It is recommended that Format 0 be used for initial

network parameter configuration.
Root μ Sequence Configuration Principles:
Indoor and outdoor PRACHs should be planned separately. The radius

of an indoor coverage system is small, so the Ncs value is also small.
However, the radius of an outdoor coverage system is large, so more
root μ sequences are required. If PRACHs for indoor and outdoor cells
are planned together, indoor cells and outdoor cells use the same root μ
sequences, causing PRACH resource waste.
The following rules for PRACH selection are already included in the
algorithm:
1) Root μ sequences should meet speed requirements. The Ncs in a

high speed scenario should not be too large to address the impact on
the peak data rate check that a cyclic shift caused by frequency
offset has. The recommended value is given in the protocol.
2) The root μ sequences between neighboring cells should be different.

Figure 4-2 shows PRACH parameter settings in Netmax.
18
Figure 4-2 PRACH Settings in Netmax
 Note:
Cell Radius (m): range: 0–100 Km.
Cell UE Average Speed (Km/h): average UE speed
UE Speed Threshold (Km/h): maximum UE speed
Collision Probability (%): collision probability
Number of Dedicated Random Access (Times/s): number of contention-free

random access times every second
19
Number of Non-dedicated Random Access (Times/s): number of

contention-based random access times every second
Reuse distance (m): reuse distance
Cell Radius Threshold (m): cell radius threshold used to distinguish

high-speed cells from low-speed cells. Default: 5.5
Antenna Port Number: number of antenna ports. This parameter is generally

set to 2.
Prach Noise (dB): PRACH noise, which is mainly thermal interference noise.
UE Prach Max Power (dBm): maximum UE transmit power
Prach Average Pathloss(dB): average path loss of a PRACH
Enable GroupB: indicates whether to use GruopB parameters
Pathloss Estimate Error(dB): estimated path loss error
Pathloss Estimate Error Threshold (dB): maximum error allowed for path
loss estimation
Contend Handoff percent (%): contention-based handoff factor
Number of Radio Link Failed (Times/s): number of radio connection failures
UE Synchronization percent uplink(%): uplink UE synchronization

percentage
Cell Edge UE Percent (%): percentage of UEs at the edge of the cell
Channel Delay Spread Type: propagation delay type on a channel, which is

usually non-line-of-sight
Sub Frame Swith: sub-frame switch used to restrict the random access
configuration sequence
4.4 Setting in the NMS

After planning PRACHs with NetMAX, you can use a template to export the
planning result, and then use the template to import the planning result to the
NMS. Based on the result, the NMS will automatically update the data.
The PRACH template import GUI is the same as the PCI template import GUI.
Figure 4-3 shows the PRACH parameter settings in the NMS.
20
Figure 4-3 PRACH Parameter Settings
21
5. Neighboring Cell Planning

5.1 Overview
Neighboring cell planning aims to allow services of UEs on cell edges to be
handed over to neighboring cells with best signals so that voice quality and
performance of the entire network can be ensured.

Neighboring cells are generally planned based on the following principles:
1. Generally, geographically adjacent cells are configured as neighboring

cells.
2. Generally, neighboring cell relations are bilateral; they are unilateral at

times.
3. The number of neighboring cells should be appropriate. It is not good to

have too many or few neighboring cells. Too many neighboring cells may
cause UEs to be overloaded with measurements and too few
neighboring cells may result in inevitable call drops and handoff failures.
At most 16 neighboring cells are recommended for initial configuration.
4. Neighboring cell planning should be based on drive tests and actual

radio environment. To ensure possible handoffs in suburban and rural
areas, any cell that is geographically adjacent to the cell should be
configured as a neighboring cell, even if the distance between the two
cells is long.

Figure 5-1 show the neighboring cell parameter settings in Netmax.
22
Figure 5-1 Neighboring Cell Settings in Netmax
 Note:
Max Inter-eNodeB Distance: required for neighboring cell planning. This
parameter indicates the longest inter-eNodeB distance.
Half Bearing of Sector Coverage: required for neighboring cell planning. This
parameter indicates the half-coverage angle of a cell, meaning the angle shift to
the left and right on the basis of the orientation angle.
Nearest eNodeB Number for Sector Radius: optional for neighboring cell
planning. If this parameter is selected, the cell coverage radius will be
calculated based on the number of the nearest eNodeBs. If not selected, the
radius will be calculated in accordance with the engineering parameters.
Distance of Force neighbors (m): required for neighboring cell planning. Cells
within the distance specified for this parameter must be set as neighboring cells.
Sector Shelter Angle: required for neighboring cell planning. If line 1 formed by
cell 1 and the serving cell and line 2 formed by cell 2 and the serving cell are
both within the angle range specified for this parameter, the cell farther away
from the serving cell will be shielded by another cell.
Force Symmetry: optional for neighboring cell planning. If this parameter is

selected and the number of neighboring cells of the serving cell has not reached
the threshold, all adjacent cells will be forcibly set as neighboring cells of the
servicing cell.
Max Number of Neighbors: required for neighboring cell planning. This

parameter indicates the maximum number of neighboring cells allowed. If the
number of neighboring cells of a serving cell has reaches the value specified for
this parameter, no more neighboring cells can be configured for the serving cell.
23

After planning neighboring cells with NetMAX, you can use a template to export
the planning result, and then use the template to import the planning result to
the NMS. Based on the result, the NMS will automatically update the data.
The neighboring-cell template import GUI is the same as the PCI template
import GUI.
The steps for configuring a neighboring cell for a serving cell in the NMS are as
follows:
Add the neighboring cell for the serving cell.
Figure 5-2 Other ENodeB Cell Dialog Box
2. Set the neighboring cell.
24
Figure 5-3 ENodeB Neighboring Relation Dialog Box
25
6. Frequency Planning
6.1 Overview
Frequency planning is to assign a frequency to each cell in a mobile
communication network based on available frequencies, interference, and
maximal reuse coefficient to ensure high frequency spectrum usage.
In an LTE system, the Orthogonal Frequency Division Multiplexing (OFDM)

technology is used at the physical layer. The feature of this technology is that
the entire system channel can be divided into multiple orthotropic subcarriers
that overlap. At the edges of multiple cells, subcarriers at the same frequency
may interfere with one another so that the services may fail.
An LTE network is usually a Single Frequency Network (SFN). If the entire

network uses a 20 MHz bandwidth, different cells can be assigned different
frequency bands to prevent the above mentioned Inter Cell Interference
Coordination (ICIC). The frequency assignment rule is that different frequency
resources should be assigned to two cells that greatly interfere with each other.
Currently, frequencies can be assigned using four methods: Based On

Same-Frequency, Based on SFR (Non Exclusive IC), Based on SFR (Exclusive
IC), and Based on Differ-Frequency.
SFR: short for Soft Frequency Reuse.
Inter Cell (IC): central area of a cell.
Outer Cell (OC): edge of a cell.
Borrow Cell (BC): cell borrowed.
Cell Center User (CCU): users in the central area of a cell.
Cell Outer User (COU): users at the edge of a cell.
DownCenterFreBitMap: indicates the frequency resources that can be used in

the central area of a cell. This parameter is the output of a frequency plan.
DownEdgeFreBitMap: indicates the frequency resources that can be used at

the edge of a cell. This parameter is a frequency plan output.
DownCenterBorrowBitMap: indicates the neighboring cell OC resources that

the local CCU can use. This parameter is a frequency plan output.
Frequency segment: indicates to divide a frequency band into several

segments based on the number of RBs. Each segment is a frequency segment.
Based on Same-Frequency: based on single-frequency network architecture.
26
Based on SFR(Non Exclusive IC): based on SFR (non exclusive IC) network
architecture, meaning mode 3.
Based on SFR(Exclusive IC): based on SFR (exclusive IC) network

architecture, meaning mode 4.
Based on Differ-Frequency: based on different-frequency network

architecture.
6.2 ICIC Classification

The following methods are in accordance with the algorithms used in the current
Netmax planning tool. It is recommended that frequency assignment based on
SFR (Non Exclusive IC) be used currently.
Before planning frequencies, neighboring relations and available frequency

bands must be available.
ICIC frequency planning output for a cell includes DownCenterFreBitMap,

DownEdgeFreBitMap, and DownCenterBorrowBitMap of the cell.
Currently, DownCenterBorrowBitMap can be ignored in TDD mode.
6.2.1 Based On Same-Frequency
This planning method is used for single-frequency network architecture. There

are no concepts of ICs or OCs for a cell in such a network. Therefore, neither
DownCenterFreBitMap nor DownEdgeFreBitMap is involved, and CCUs and
COUs are not distinguished from one another. A user can use the entire
frequency band resource.
6.2.2 Based on SFR (Non Exclusive IC)
A specified frequency band needs to be divided into three frequency segments.

The TSCP algorithm will then be used to determine the DownEdgeFreBitMap
of each cell, meaning that the segment among the three segments that the OC
of each cell uses should be determined. For each cell, CCUs can use all
frequency segment resources except DownEdgeFreBitMap.The key point of
this algorithm is to use the frequency assignment algorithm to determine
DownEdgeFreBitMap of each cell.
6.2.3 Based on SFR(Exclusive IC)
A specified frequency band needs to be divided into four frequency segments. A

frequency segment is randomly selected for CCUs of all network-wide cells to
use. From other three frequency segments, frequency resources that COUs of
each cell use are planned, meaning that DownEdgeFreBitMap is determined.
For each cell, COUs can use the frequency segments specified for
DownEdgeFreBitMap, and CCUs can use the frequency segments specified
27
for ICs or other frequency segment resources than DownEdgeFreBitMap.

Therefore, the key point of this algorithm is to use the frequency assignment
algorithm to determine DownEdgeFreBitMap of each cell.
6.2.4 Based on Differ-Frequency
This planning method is used for different-frequency network architecture.

Three frequency bands with the same bandwidth need to be selected. The
frequency resources of each cell are one of the three frequency bands. From
the perspective of the small network containing the three cells, these cells are
actually in a single-frequency network.Therefore, there are no concepts of ICs
or OCs, and cell users can use the entire frequency band resources. The key
point of this algorithm is to use the frequency assignment algorithm to select a
frequency band for a cell from the three frequency bands.

Figure 6-1 show the frequency parameter settings in Netmax.
Figure 6-1 Frequency Settings in Netmax
 Note:
Frequency Band Name: name of a new frequency band. The name must be
different from any existing frequency band name.
E-UTRA Band Indicator: E-UTRA indicator
Center Frequency(MHz): central frequency
Band Width(MHz): bandwidth
28
Duplex Mode: duplex mode
Num of RB: varies with the selected bandwidth and is defined by the system.
Based on Same-Frequency: intra-frequency network architecture
Based on SFR(Non Exclusive IC): network architecture based on SFR (Non

Exclusive IC), meaning mode 3.
Based on SFR (Exclusive IC): network architecture based on SFR (Exclusive

IC), meaning mode 4.
Based on Differ-Frequency: inter-frequency network architecture
In the software, the default frequency band is 2.6 GHz. To add a new frequency
band, click New. In the displayed dialog box, select the desired frequency band,
see Figure 6-2.
Figure 6-2 Frequency Band Setting Dialog Box
29
Figure 6-3 ICIC Setting on the NMS
Currently, ICIC-related parameters are implemented in background codes. Two

static ICIC implementation solutions are as follows:
 Static SFR
Figure 6-4 shows that the whole frequency band is divided into three equal
32 RB parts, and f1, f2 and f3 indicate the outer region of the three sectors
respectively.
Figure 6-4 Static SFR
 Static FFR
30
Figure 6-5 shows that the whole frequency band is divided into four parts. It is
similar to the case that the f1 in SFR mode is divided into three equal parts,
each of which serves as the outer region of the three sectors respectively. In
this way, resources for COUs are separated from those for CCUs, reducing the
serving cell CCU interference caused by the neighboring cell sidelobe users. In
current tests, 36 RBs are included in an outer cell region, 12 RBs grouped
together are used as the cell edge, and the other 24 RBs are disabled in codes,
see the red crosses in Figure 6-5.
Figure 6-5 Static FFR
31

FO - NP2004 LTE Networking Parameter Planning

Загружено:

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

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

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

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

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

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

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

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

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

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

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

FO - NP2004 LTE Networking Parameter Planning

Загружено:

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

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

LTE Networking Parameter Planning

EUTRAN Parameter Planning

PLMN = MCC + MNC

A Mobile Country Code (MCC), consisting of three decimal digits, is a code

Cell Idendity = eNodeB ID + Cell ID

ENodeB ID range: 0–1048575. An eNodeB ID is used in combination with a

1.1.2 Configuration Principles

Particular situations of different operators should be taken into account.

If an operator has only one small-sized network, eNodeB IDs can be

ENodeB ID format in a standard-sized network: ABCDEF

AB indicates a city and a maximum of 99 cities can be represented.

F indicates whether it is an indoor or outdoor eNodeB. If F is set to 0, it

For China Mobile, eNodeB ID assignment within the entire network

If all the cities in China are planned together, different AB combinations

If there are over 99 cities involved in the network, an AB combination can

F indicates whether it is an indoor or outdoor eNodeB. If F is set to 0, it

If the range that ABCDEF covers cannot meet the particular

1) ABCDE: a maximum of 100,000 numbers, ranging from 0 to 99999,

1) A indicates the network system. The value 1 indicates a TDD network,

to uniquely identify a cell in a PLMN, meaning that a Cell ID is unique in an

1.2.2 Configuration Principles

A Cell ID is unique within an eNodeB.

For indoor sites, Cell IDs can start from 100.

1) Outdoor site Cell IDs can start from 0.

An example is as follows: For an FDD network in China, numbers 0 to 3 are

2. Tracking Area Code Planning

TAI = PLMN + TAC

TA is similar to LA/RA in 2G/3G. In an LTE network, CN is invisible to cells (a

A UE uses a P-RNTI to periodically monitor a PDCCH to know whether a paging

Figure 2-1 IMSI Structure

As shown in Figure 2-1, an IMSI is an identity consisting of not more than 15

2.1.2 Paging Occasion

A Paging Occasion (PO) is determined by two parameters: a frame parameter

SFN mod T = (T/N) × (UE_ID mod N) formula 2.1-1

i_s = floor (UE_ID/N) mod Ns formula 2.1-2

Parameter value ranges in the two formulas are as follows:

● T (default paging cycle): 32, 64, 128, or 256 radio frames

● N (number of paging groups): min(T, nB)

● Ns (number of sub-frame paging groups): max(1, nB/T)

● UE_ID: IMSI mod 1024

Table 2-1 Sub-frame Patterns in TDD (all UL/DL patterns)

Ns PO when i_s=0 PO when i_s=1 PO when i_s=2 PO when i_s=3

Table 2-2 Length of DwPTS, GP, and UpPTS in TDD

Configuration Normal CP Extended CP

DwPTS GP UpPTS DwPTS GP UpPTS

2.1.3 Maximum Number of UEs That Can Be Paged Per Second

nB 4T 2T T 1/2T 1/4T 1/8T 1/16T 1/32T

2.2 Configuration Principles

TACs should be planned based on geographical distribution and

If there are two or more LAs in a heavy-traffic large city, topographical

3. A TAC/TAL must not cross multiple MMEs.

2.2.2 Relevant Parameter Configuration Principles

 Configuration rule for nB

 Configuration rules for T

The configuration of T is related to service OoS requirements. The T

The configuration of T is related to UE power consumption. The value of T

It is recommended that T be set to 64 initially.

3. Physical Cell ID Planning

SCHs are divided into PSCHs and Secondary Synchronization Channels

3.2 Configuration Principles

1) Cells in the same site must have different PCIs.

PCIs should be reused based on priorities. Assume that the PCIs in

2. Generally, it is recommended that the following rules be followed for