LTE TDD PCI Planning Guide

Issue

1.1

Date

2012-03-29

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address:

Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website:

http://www.huawei.com

Email:

support@huawei.com

LTE
TDD PCI Planning Guide

About This Document

About This Document

Author
Prepared by

Date

Reviewed by

Date

Reviewed by

Date

Approved by

Date

Change History
Date

Issue

Change Description

Author

2009-07-12

V1.0

First release.

He Li

2012-03-30

V1.1

Revised the document.

Jian Xiongjun

LTE
TDD PCI Planning Guide

Contents

Contents
About This Document.......................................................................ii
1 Overview...................................................................................... 1
2 PCI Design.................................................................................... 2
2.2 PSCH Sequence Design.....................................................................................................................................3
2.3 SSCH Sequence Design.....................................................................................................................................5
2.4 Downlink Cell-Shared Pilot Design..................................................................................................................8

3 Planning Principle.......................................................................10
4 PCI Planning Using the U-Net.......................................................12
4.1 Preparation.......................................................................................................................................................12
4.2 Starting PCI Planning......................................................................................................................................13
4.3 Configuring Planning Parameters....................................................................................................................14
4.4 Checking the PCI Planning Result...................................................................................................................18
4.5 Submitting the PCI Planning Result................................................................................................................19
4.6 Displaying the PCI Planning Result................................................................................................................19
4.7 Exporting the PCI Planning Result..................................................................................................................25
4.8 Manually Configuring PCIs.............................................................................................................................26

5 References.................................................................................29

LTE
TDD PCI Planning Guide

5 References

Overview

In LTE systems, each cell has a unique physical cell identifier (PCI) in a network, enabling
user equipment (UE) to differentiate radio signals of different cells.
In LTE systems, cells are grouped. They are searched based on the primary and secondary
synchronization sequences. The secondary synchronization sequence on the secondary
synchronization channel (SSCH) determines the cell group ID and the primary
synchronization sequence on the primary synchronization channel (PSCH) determines the cell
ID in a cell group.
A large number of cell IDs can facilitate multi-cell networking, which, however, requires
sufficient synchronization sequences with high performance to search a cell ID quickly and
accurately. To balance the number of cell IDs and the cell search speed, 168 cell groups are
configured with each consisting of three cells.
In the live network, cell IDs may be reused. If the reuse distance is small, PCI collisions
occur. To resolve this problem, PCIs are planned to ensure that each cell is assigned a cell ID.
This prevents interference between downlink signals in the intra-frequency cells with the
same ID and the negative effects on UE synchronization and decoding on pilot channels of the
serving cell.

2012-03-29

Huawei Proprietary and Confidential

Copyright Huawei Technologies Co.,
Ltd.

PCI Design

Before a UE accesses an LTE cell, it must search cells for time and frequency synchronization
and obtain some important system parameters. Time and frequency synchronization enables
the UE to correctly demodulate downlink signals and transport uplink signals.
LTE systems support two cell search procedures:

Initial cell search: After the UE detects an LTE cell, it interprets all information
necessary for it to register in the cell. Initial cell search occurs at the moment a UE is
powered on or the UE is disconnected from the serving cell.

Search for new cells during a handover: The search occurs after the UE has been
connected to an LTE cell. When the requirements for event A3 conditions are met, the
UE reports the measurement information about neighboring cells to the serving eNodeB
for a handover.
According to 3GPP TS 36.211, the relationship between PHY_CELL_ID and the
(2)

(1)

primary synchronization signal ( N ID ) and secondary synchronization signal ( N ID ) is as

follows:
cell
(1)
(2)
N ID
3N ID
N ID

(1)

Where,
(1)
(2)
N ID
ranges from 0 to 167 and N ID from 0 to 2.

Primary synchronization signals vary with the frequency-domain length-62 ZC sequence that
can be set to three different values. As illustrated in formula 2, primary synchronization
signals have optimal orthogonal performance. Secondary synchronization signals differ for
secondary synchronization slots 0 and 5 in a frame. There are 168 secondary synchronization
signal types. As illustrated in formula 3, secondary synchronization signals has poorer
orthogonal performance than primary synchronization signals. Combination of primary and
secondary synchronization signals forms 504 different PHY_CELL_IDs.

d u ( n)

un ( n 1)
63

u ( n1)( n 2 )
j
63

n 0,1,...,30
n 31,32,...,61

(2)

where the ZC root sequence index is given by the following table.

Root index u

(2)
N ID

25

29

34

s 0( m0 ) ( n)c0 n in subframe 0
d ( 2n ) ( m )
1
s1 ( n)c0 n in subframe 5
s1( m1 ) ( n)c1 n z1( m0 ) n in subframe 0
d ( 2n 1) ( m )
( m1 )
0
s 0 ( n)c1 n z1 n in subframe 5 (3)

s0

s1

c1 are
two different scrambling sequences depends on the primary synchronization signal, and z1 is
where

and

are two different m-sequences depending on PHY_CELL_ID,

c0

and

an m-sequence depending on PHY_CELL_ID.

In application, different primary synchronization codes (PSCs) are recommended for different
cells in an eNodeB to minimize inter-cell interference. According to formula 1, the 504
PHY_CELL_IDs can be grouped based on the PSCs. Table 2.1.1.I.1.1.1.1 lists the
PHY_CELL_ID groups.
Table 2.1.1.I.1.1.1.1 PHY_CELL_ID groups
(2)
N ID

PHY_CELL_ID

501

10

502

11

503

In the previous table, each column indicates the number of SCH sequences allocated to an eNodeB.

The PHY_CELL_ID group ID and PHY_CELL_ID depend on the SCH sequence. The SCH
is firstly detected after the UE is powered on. Therefore, the UE must perform sequence
detection on the SCH for downlink synchronization and transportation of basic system
information, since there is no prior information and modulation or demodulation cannot be
performed.

2.2 PSCH Sequence Design

PSCH sequence orthogonality determines PSC performance and inter-cell interference in an
eNodeB. The E-UTRA system requires synchronization. It supports multicast/broadcast over
single frequency network (MBSFN) and inter-cell interference coordination. If cell-common
PSC is used in an E-UTRA system, the following problems occur[3]:

A UE receives single frequency network (SFN) signals that combine numerous PSC
multi-path signals. When used with the cross-correlation method, cell-shared PSC
provides better clock synchronization performance on the PSCH than cell-specific PSC.
If used with the auto-correlation method, cell-shared PSC provides the same clock
synchronization performance as cell-specific PSC [1].

Cell-shared PSC affects coherent detection on the secondary synchronization channel

(SSCH). Secondary synchronization code (SSC) detection uses PSCs for channel
estimation. If cell-shared PSC is used, SFN-combined channel data is obtained during
channel estimation. If cell-specific PSC is used, unicast channel information of each
physical cell is obtained during channel estimation. The channel estimation results are
different, and the result using cell-shared PSC is unreliable.

To resolve the previous problems, a moderate number of PSCs must be used. The number of
PSCs must be used to ensure that the following requirements are met:

PSC detection performance does not seriously deteriorate.

The synchronization detection complexity is minimized.

SFN signal combination is prevented for the most adjacent cells to ensure accurate
unicast channel estimation of the target cell.

In Huawei LTE systems, three PSCs are used. Each PSC is mapped to a cell ID.
PSCs must have the following characteristics:

Low correlation: Cross correlation must be minimized between PSCs, and the peak data
result contains the same number of cells as the number of cells that uses PSCs when the
correlation between PSC samples and receive signals are detected.

Similar amplitude in the frequency domain: This ensures satisfactory channel estimation
performance during SSCH coherent detection.

Low complexity to ensure quick synchronization and cell search

Satisfactory cell search performance

Currently, LTE standards use constant amplitude zero auto-correlation (CAZAC) sequences
that provide constant amplitudes in the time domain and constant envelop modulation in the
frequency domain. CAZAC sequences accurately estimate the channel fading per subcarrier.
PSC sequences use the frequency-domain ZC sequences that are not duplicated in the time
domain, which ensures low correlation between PSCs and neighboring data channels. LTE
standards use three length-62 ZC sequence numbers to prevent interference between the PSC
and neighboring channels and to reduce sequence complexity, as shown in Figure
2.2.1.I.1.1.1.
Figure 2.2.1.I.1.1.1 Mapping of PSC sequences in the frequency domain

PSCs are used to obtain the physical cell identity within a PHY_CELL_ID group, and to
perform symbol synchronization, frequency synchronization, and 5-ms time synchronization
(PSCH signals are transmitted per half-frame). The sequence used for PSC is generated from
frequency-domain ZC sequences according to the following formula:

d u ( n)

un ( n 1)
63

u ( n 1)( n 2 )
j
63

n 0,1,...,30
n 31,32,...,61

where n is the sequence length and is used to select different ZC sequences. The
relationship between n and is 0,1,2..., n 1 , where and n are prime number of
each other. There are three ZC sequence types on the PSCH according to the values of (
= 25, 29, and 34).
During cell search, ZC sequences are modulated to different sub-carriers and are transmitted
in the frequency domain in OFDM mode. This ensures accurate timing estimation and
prevents the adverse effect of frequency offset correction when frequency offsets exist. The
PSCH occupies 62 subcarriers and is configured with an effective transport bandwidth of 1.25
MHz. The bandwidth includes that of direct current (DC) subcarriers. Other subcarriers are
used for data protection, as shown in Figure 2.2.1.I.1.1.1.

2.3 SSCH Sequence Design

Figure 1.1.1.I.1.1.1 shows the LTE cell search flowchart.
Figure 1.1.1.I.1.1.1 LTE cell search flowchart

The SSCH is used for detecting PHY_CELL_ID group IDs and frame timing. The sequence
used for the SSC is an interleaved concatenation of two binary sequences. Two SSCs within a
radio frame use different binary sequences for frame timing. LTE standards use m-sequences
for SSC sequence design.
After cyclic shifts, a sequence group is derived from a length-31 m sequence, and two
sequences are selected from the sequence group as SSCs. The SSC pair scrambles a binary
scrambling code corresponding to the PSC to prevent inter-SSC interference within a group
and to decrease PAPR. Then, the SSCs are alternately mapped to the 62 subcarriers used by
the SSCH so that they are alternately multiplexed on the SSCH in the frequency domain.
In a radio frame, subframe 0 and subframe 5 use different SSCs, which allows the system to
detect only one SSC to achieve frame synchronization. The SSC sequences are mapped in
binary phase shift keying (BPSK) constellation mapping mode in the frequency domain, as
shown in Figure 2.3.1.I.1.1.1.
Figure 2.3.1.I.1.1.1 Mapping of SSC sequences in the frequency domain

The two length-31 sequences defining the SSCH differ between subframe 0 and subframe 5
according to

s 0( m0 ) (n)c0 n in subframe 0

d ( 2n)

( m1 )
s1 (n)c 0 n in subframe 5
s ( m1 ) (n)c1 n z1( m0 ) n in subframe 0
d (2n 1) 1( m )
( m1 )
0
s 0 (n)c1 n z1 n in subframe 5
(1)
where 0 n 30. The indexes m0 and m1 are derived from the PHY_CELL_ID group N ID
(ranging from 0 to 167) according to

The two sequences

s0( m0 ) (n) and s1( m1 ) (n) are defined as two different cyclic shifts of the m

sequence s (n) according to

where s(i ) 1 2 x(i ),

0 i 30

x (i ) is defined by

with initial conditions x(0) 0 , x (1) 0 , x(2) 0 , x (3) 0 , x(4) 1 .

The two scrambling sequences c0 (n) and c1 (n) depend on the PSC and are defined by two

~
different cyclic shifts of the m-sequence c ( n) according to

( 2)
where N ID 0,1,2 is the physical-layer identity within the physical-layer cell identity group
(1)
~
N ID
and c (i) 1 2 x(i ) , 0 i 30 , is defined by

x(i 5) x(i 3) x(i ) mod 2,

0 i 25

with initial conditions x(0) 0, x(1) 0, x(2) 0, x(3) 0, x(4) 1 .

( m0 )
z ( m1 ) (n)
The scrambling sequences z1 (n) and 1
are defined by a cyclic shift of the m~z ( n)
sequence
according to

where z (i ) 1 2 x (i ),

0 i 30 , is defined by

with initial conditions x(0) 0 , x (1) 0 , x(2) 0 , x (3) 0 , x(4) 1 .

(1)
Figure 2.3.1.I.1.1.2 shows the mapping between PHY_CELL_ID group N ID and the indexes
m 0 and m1 .
(1)
Figure 2.3.1.I.1.1.2 mapping between PHY_CELL_ID group N ID and the indexes m 0 and m1

2.4 Downlink Cell-Shared Pilot Design

Three types of downlink reference signals are defined:

Cell-specific reference signals: also known as common reference signals, applicable to

all UEs in a cell

UE-specific reference signals: transmitted only in resource elements specific for a UE

MBSFN reference signals: applicable only to MBSFN

All the three types of reference signals are modulated in QPSK mode. This ensures a low
PAPR and lowers the requirements for power amplifiers. The reference-signal sequence
rl ,ns (m)
is defined by

rl ,ns (m)

1
[1 2c(2m)] j 2[1 2c(2m 1)]
2

where m is the reference signal index, ns is the slot number within a radio frame, and

is

the OFDM symbol number within the slot. The pseudo-random sequence c(i ) is defined by a
length-31 Gold sequence in different initial configurations. Different initial configurations
indicate different reference signal types.
cell
cell
A reference signal uniquely carries a N ID . N ID mod 6 determines the frequency-domain
shifts of cell-shared reference signals. The shifts prevent collisions between cell-shared
reference signals in the time domain sent from six neighboring cells.

Planning Principle

In LTE systems, the eNodeB distinguishes two length-31 m-sequences by scrambling an msequence with a binary scrambling code defining the PSC, and distinguishes cells by using
three length-62 ZC sequences (root sequence index = 35, 29, 34). Only a maximum of 504
PCIs have satisfactory orthogonal performance. Therefore, they must be numbered to prevent
PCI confusion.
Though all cells have different PCIs, the PCI reuse distance is insufficient for UEs to prevent
interference between non-correlated pilot signals. Consequently, errors occur when the UE
trances pilot signals. If the errors occur during eNodeB identification, the UE may be
unexpectedly handed over to a different cell, which may cause service drop.
This chapter describes the problems when these 504 PCIs are reused.

Collision
If two neighboring cells are allocated with the same PCI in an intra-frequency network, a
maximum of one cell can be detected by the UE, and only one cell can be synchronized
during initial cell search. If the synchronized cell does not meet the handover requirements, a
collision occurs, as shown in Figure 1.1.1.I.1.1.1.
Figure 1.1.1.I.1.1.1 Collision

Confusion
If neighboring cells have the same PCI (ID A in Figure 1.1.1.I.1.1.1) and UEs are to be
handed over to a neighboring cell, the eNodeB cannot decide which neighboring cell is the
target cell. Consequently, confusion occurs.

Figure 1.1.1.I.1.1.1 Confusion

Therefore, PCI planning must ensure that the PCI is free from confusion and collision. In
addition, PCI planning must comply with the following principles:

If a serving cell is configured with intra-frequency neighboring cells with strong

interference, the neighboring cells cannot use the same PCI as the serving cell.
This principle does not apply to inter-frequency neighboring cells.

At the edge of a serving cell, the pilot signals transmitted by the neighboring cell are
stronger than the receive signal level of the UE.
Interference occurs if a UE receives weak pilot signals from non-neighboring nearby
cells at the edge of the serving cell. In this case, these nearby cells can adopt the same
PCI as the serving cell only when the interference level is lower than the associated
threshold.
The cells that do not interfere with the serving cell can adopt the same PCI as the serving
cell.

Pilot symbol positions of neighboring cell are staggered to the maximum extent.
The position of an LTE pilot symbol is associated with the PCI code assigned by the cell.
To prevent interference between pilot symbols and improve overall network
performance, the pilot symbol of the serving cell cannot be located side by side with
those of neighboring cells. The position of pilot symbols in the frequency domain is
determined by PCI MOD 3 in two- and four-antenna scenarios and by PCI MOD 6 in the
single-antenna scenario.

PCI planning is performed easily and facilitates future network expansion. The PCIs of
the same eNodeB must belong to the same PCI group, and the PCIs of the neighboring
eNodeB must belong to a different PCI group from those of the current eNodeB.

For indoor coverage scenarios, PCIs are planned as follows:

If only few RRUs cover an indoor area (typically in early site deployment stages) and
macro eNodeBs are used for coverage, PCIs can be planned in the same way for
indoor and outdoor scenarios.

If a large number of RRUs cover an indoor area, PCIs must be planned separately for
indoor and outdoor scenarios, and PCIs can be reused to the maximum extent.

PCI Planning Using the U-Net

This chapter describes how to plan PCIs using the Huawei-developed U-Net for newly
deployed and expanded eNodeBs. During PCI planning, eNodeB are grouped in different
clusters prior to allocation of PCIs.
During PCI allocation, the number of cells in each site must be considered. In standard
configurations, three cells are configured for each site. Non-standard configurations are
adopted only in some special scenarios. The U-Net allocates PCIs in priority based on PCI
groups. If a site is configured with more than three cells, two PCI groups are configured for
the site. The redundant PCIs are automatically reserved.

4.1 Preparation

The U-Net has been installed. V300R003 or later is recommended.

Engineering parameters related to the site to be planned, including longitude and latitude,
altitude, RF parameters, and digital maps, are obtained.

Available PCIs are obtained from the operator, and PCI reservation for future capacity
expansion is considered. It is recommended that the number of PCIs equals the number
of PCI groups multiplied by an integer.

Site information, cell information, digital maps, and simulation parameters have been
imported in the U-Net.

The PCI planning method has been finalized.

The U-Net allows for topology-based PCI planning and coverage prediction-based PCI
planning. If RF parameters are configured properly during simulation tests, coverage
prediction-based PCI planning is recommended. In other situations, topology-based PCI
planning is recommended.

Figure 4.1.1.I.1.1.1 U-Net

4.2 Starting PCI Planning

In the Project Explorer navigation tree of the U-Net, click
, right-click LTE PCI
Planning, and choose Automatic Allocation from the shortcut menu to start PCI planning, as
shown in Figure 4.2.1.I.1.1.1.

In V300R005, right-click PCI Planning under Transceiver and choose Planning from the shortcut
menu.

Figure 4.2.1.I.1.1.1 Starting automatic PCI planning

4.3 Configuring Planning Parameters

After Automatic Allocation is chosen, the PCI Planning dialog box is displayed, as shown
in Figure 4.3.1.I.1.1.1.

Figure 4.3.1.I.1.1.1 PCI Planning dialog box

General tab page: allows you to configure available PCIs and reserve PCIs for capacity
expansion and to select the area to be planned.

Reserve Ratio: specifies the ratio of the PCIs to be reserved to the total PCIs. It is
recommended that the available PCIs be specified prior to the PCIs to be reserved.

Start and End: specifies the start and end number of available PCIs. Consecutive
PCIs are recommended. The non-consecutive PCIs can be reserved or used for cell
adjustment. You can click Add repeatedly to add multiple PCI groups, as shown in
Figure 4.3.1.I.1.1.2.

Figure 4.3.1.I.1.1.2 Adding multiple PCI groups

Area: specifies the areas for PCI planning. You can specify multiple areas for CPI
planning. By default, PCI are planned for the full map. The Filter button allows you
to filter out the cells that do not require PCI planning. As shown in Figure
1.1.1.I.1.1.2, on the Cell Select dialog box displayed after you click Filter, you can
deselect the cells that do not require PCI planning.

Figure 1.1.1.I.1.1.2 Filtering out the cells that do not require PCI planning

Load: used to import planned PCI parameters. To ensure that a cell belongs to the
same cluster after its capacity expansion, you can load the configuration files
obtained during initial network deployment.

Run: Used to implement PCI planning.

Control Parameter: Provides control parameters related to PCI planning, as shown in

Figure 4.3.1.I.1.1.3.

Figure 4.3.1.I.1.1.3 Control parameters related to PCI planning

The parameters in the Control Parameter dialog box are described as follows:

Max Interference Distance: If the topological distance between two cells is greater
than this value, there is no interference between these cells and these cells do not
neighbor with each other.

Reset PCI: specifies whether to clear the existing PCIs. If the Reset PCI check box
is selected, the existing PCIs are cleared and PCIs of all cells must be planned again.

With Neighbor: specifies whether to consider the impact of neighboring cell

configurations during PCI planning. For example, tier-one and tier-two neighboring
cells of a cell cannot be configured with the same PCI. It is recommended that the
With Neighbor check box be selected if neighboring cell configurations have been
complete before PCIs are planned.

RS-Timing Shift: specifies whether to consider timing shifts during PCI planning.
The RS-Timing Shift check box is not recommended during PCI planning.

With Existing PCI: specifies whether to implement large-scale PCI planning in

capacity expansion scenarios. If this check box is selected, PCIs are planned to all
cells to be planned by cluster, which is similar to that of a newly deployed cell.

Advanced Parameter: specifies PCI planning modes, including topology-based and

coverage prediction-based PCI planning, as shown in Figure 4.3.1.I.1.1.4.

Figure 4.3.1.I.1.1.4 PCI planning modes

Topology-based PCI planning considers topological factors, such as the azimuth between
cells, antenna height, and cell distance. During PCI planning, PCI groups are allocated based
on the number of tiers for reusing PCIs and the distance between cells, and pilot symbol
positions and PCIs are determined based on interference scores. In coverage prediction-based
PCI planning, V-shift and PCIs are allocated based on the same interference score.
If the Prediction option box is selected, you need to specify control parameters related to
coverage prediction, including Min Signal Level(dBm), Handover area threshold(dBm),
Shadowing taken into account, Cell Edge Coverage Probability, and Indoor Coverage.
After all the preceding parameters are set, click Run to implement PCI planning.

4.4 Checking the PCI Planning Result

Figure 1.1.1.I.1.1.3 shows the PCI planning result.

Figure 1.1.1.I.1.1.3 PCI planning result

4.5 Submitting the PCI Planning Result

In the PCI Planning Result dialog box, click Commit to submit the PCI planning result.

4.6 Displaying the PCI Planning Result

After the PCI planning result is imported by clicking Commit in the PCI Planning Result
dialog box, click , right-click Transceiver, and choose Display Setting from the shortcut
menu, as shown in Figure 1.1.1.I.1.1.4.

Figure 1.1.1.I.1.1.4 Choosing Display Setting

The Display Field dialog box is displayed, as shown in Figure 1.1.1.I.1.1.5.

In the displayed dialog box, select PCI in the Available Fields area, and click OK.

Figure 1.1.1.I.1.1.5 Selecting PCI

The PCI planning result is displayed, as shown in Figure 1.1.1.I.1.1.6.

Figure 1.1.1.I.1.1.6 Displaying the PCI planning result

Figure 1.1.1.I.1.1.6 shows the PCI planning result in a two-antenna scenario. If you want to
view the PCI mod3 result, perform the following steps:
Step 2 In the Project Explorer navigation tree, click , right-click Transceiver, and choose Cells
> Open Table from the shortcut menu. In the displayed cell table, copy the PCI column to an
XLS file, as shown in Figure 4.6.1.I.1.1.1.

Figure 4.6.1.I.1.1.1 Copy the PCI column

Step 3 Calculate the Mod3 values corresponding to each PCI using the model function, as
shown in Figure 4.6.1.I.1.1.2.

Figure 4.6.1.I.1.1.2 Calculating Mod3 values

Step 4 Copy the mod3 values to the TAC column in the cell table, and display the mod3
planning result, as shown in Figure 4.6.1.I.1.1.3.

Figure 4.6.1.I.1.1.3 Displaying the mod3 planning result

Different colors indicate different mod3 planning results. As shown in the preceding figure,
some PCI planning result needs to be manually adjusted.

4.7 Exporting the PCI Planning Result

In the U-Net, choose File > Export > Engineering Parameters to export the PCI planning
result, as shown in Figure 4.7.1.I.1.1.1.
Figure 4.7.1.I.1.1.1 Exporting the PCI planning result

4.8 Manually Configuring PCIs

You can manually plan or modify the PCI of a single cell or multiple cells.
Perform the following operations to plan the CPI of a single cell:
Step 1 In the Project Explorer navigation tree, click , right-click a cell name under Transceiver,
and choose Properties from the shortcut menu, as shown in Figure 4.8.1.I.1.1.1.
The Transceiver Properties dialog box is displayed, as shown in Figure 4.8.1.I.2.1.1.
Figure 4.8.1.I.1.1.1 Choosing Properties

Step 2 In the LTE-TDDCell tab page of the dialog box, modify PCI settings for the cell.

Figure 4.8.1.I.2.1.1 Modifying PCI settings for a single cell

Perform the following operations to plan the CPIs for multiple cells:
1 In the Project Explorer navigation tree, click , right-click Transceiver, and choose Cells
> Open Table, as shown in Figure 4.8.1.I.2.1.2.

Figure 4.8.1.I.2.1.2 Opening the cell table

Step 3 In the displayed dialog box, set the PCI ranging from 0 to 503.
Figure 4.8.1.I.3.1.1 Modifying PCI settings for multiple cells.

References

[1] 3GPP TS 36.211 Evolved Universal Terrestrial Radio Access (E-UTRA); Physical
channels and modulation
[2] 3GPP R1-070145. Motorola, P-SCH Sequence Design, 3GPP TSG RAN WG1 Meeting
#47bis
[3] 3GPP R1-061744. Texas Instruments, Proposal for DL SYNC channel (SCH) for EUTRA, 3GPP TSG RAN WG1 Meeting #Ad Hoc on LTE(June_2006)
[4] 3GPP R1-061747. Texas Instruments, Performance of Timing Acquisition and Cell
Specific Info Detection in Tightly Synchronized Network for E-UTRA, 3GPP TSG RAN
WG1 Meeting #Ad Hoc on LTE(June_2006)
[5] 3GPP R1-071496. NEC Group, Basic requirements for PSC and SSC design, 3GPP TSG
RAN WG1 Meeting #48bis
[6] 3GPP R1-071583. Ericsson, Primary Synchronization Signal Design, 3GPP TSG RAN
WG1 Meeting #48bis
[7] 3GPP R1-071794. Qualcomm, Ericsson, Motorola, Nokia, Nortel, NEC, Texas Ins.,
Huawei, Siemens, Philips, LGE, Samsung, Panasonic, ETRI, Way Forward for stage 2.5
details of SCH, 3GPP TSG RAN WG1 Meeting #48bis
[8] 3GPP R1-070262. Texas Instruments, Performance of 3-Stage Cell Search, 3GPP TSG
RAN WG1 Meeting #47bis
[9] 3GPP R1-072131. Motorola, Cell Search E-mail Reflector Summary, 3GPP TSG RAN
WG1 Meeting #49
[10]3GPP R1-070630. Ericsson, Nokia, Huawei, NTT DoCoMo, Motorola, Qualcomm,
Samsung, TI, Alcatel-Lucent, LGE, Nortel Networks, Way forward on DL RS, 3GPP TSG
RAN WG1 Meeting #47bis
[11]3GPP R1-071481. Texas Instruments, Summary of Reflector Discussions on E-UTRA DL
RS, 3GPP TSG RAN WG1 Meeting #48bis
[12]3GPP R1-074066. Samsung, Summary of Reflector Discussions on EUTRA DL RS,
3GPP TSG RAN WG1 Meeting #50bis
[13]3GPP R1-081096. Nokia, Nokia Siemens Networks, Broadcom, Freescale, Huawei, LG
Electronics, NXP Semiconductors, Samsung, Texas Instruments, ZTE, NextWave

Wireless, Way Forward on Orthogonal Sequences for DL Reference signals, 3GPP TSG
RAN WG1 Meeting #52