Physical Cell ID (PCI ) planning

Principle, planning requirements and Atoll implementation

Hans Jörg Hamers

VF-TSO- Access- Design

1 PCI planning Vodafone confidential

25 August 2014
Physical Cell ID (PCI) planning
Principle, planning requirements and Atoll Implementation

Understand
Principle - PCI implementation based on the 3GPP Specification

Understand
Planning requirements - planning requirements as result of the PCI implementation

Understand
Atoll Implementation - current implementation and restrictions within Atoll 2.8.3

Understand
Atoll requests - requests to Forsk on PCI allocation algorithm

Final Atoll Understand

Implementation - final implementation within Atoll 2.8.3 and 3.1.1

2 PCI planning Vodafone confidential

25 August 2014
 Principle

Physical Cell ID (PCI) planning

Principle (1)

• Cell ID is required to identify each cell

• A Cell ID is the combination of one P-SCH and the Group ID supported by S-SCH

Principle
Site x Site y Site z
Physical layer
cell identity identified by …
Physical layer cell
identity group 0 1 167
(1 out of 504)

Physical layer 0 1 2 0 1 2 0 1 2
identity

1. Primary synchronisation signal

- 3 possible sequences to identify the cell’s physical layer identity (0,1,2)

The rule is like following: 2. Secondary synchronisation signal

- 168 different sequences to identify physical layer cell identity group

NID(1) = 0 … 167; NID(2) = 0,1,2; NIDcell = 3NID(1) + NID(2)

PCI planning Vodafone confidential
August 25, 2014
 Principle

Physical Cell ID (PCI) planning

Principle (2)

PCI planning Vodafone confidential

August 25, 2014
 Principle

Physical Cell ID (PCI) planning

Principle (3)

PCI planning Vodafone confidential

August 25, 2014
 Principle

Physical Cell ID (PCI) planning

Principle (4)

Frequency shift for RS

subcarrier

time
• Reference Signals are transmitted with one of 6 possible
frequency shifts (modulo 6) to avoid time-frequency
collisions between common Reference Signals from up to 6
adjacent cells

• Frequency shift is related to assigned PCI

Frequency shift PCIs

0 0,6,12,18,…
1 1,7,13,19,…
…

5 5,11,17,23,…

PCI planning Vodafone confidential

August 25, 2014
 Planning
requirements
Physical Cell ID (PCI) planning
Planning requirements (1)

Vodafone strategy:

in line with vendor strategy: Ericsson and Huawei

PCI planning Vodafone confidential

August 25, 2014
 Planning
requirements
Physical Cell ID (PCI) planning
Planning requirements (2)

PCI planning Vodafone confidential

August 25, 2014
 Planning
requirements
Physical Cell ID (PCI) planning
Planning requirements (3)

Example:

Site with group identity 8 assigned Æ PCIs 24,25,26

The figure shows an example where the cells in a site are

assigned different primary sequences and the same identity
Group.

PCI planning Vodafone confidential

August 25, 2014
 Planning
requirements
Physical Cell ID (PCI) planning
Planning requirements (4)

SSS: 1
Example: 3 Sector Site PSS: 2
PCI: 5

SSS: 1
PSS: 1
PCI: 4 SSS: 1
PSS: 0
PCI: 3
Modulo 6:
0,1,2,
6,7,8,
12,13,14,
SSS: 0 18,19,20,
SSS: 0
PSS: 2
PSS: 0 …
PCI: 0
PCI: 2 not allowed

SSS: 0
PSS: 1
PCI: 1

PCI planning Vodafone confidential

August 25, 2014
 Planning
requirements
Physical Cell ID (PCI) planning
Planning requirements (5)
SSS: 1
PSS: 1
PCI: 4
Example: 4 Sector Site
SSS: 0
PSS: 2 SSS: 0
PCI: 2 PSS: 0
Modulo 6:
PCI: 0
0,1,2,
SSS: ?
6,7,8,
SSS: 0
PSS: ? 12,13,14, PSS: 1
PCI: ? 18,19,20, PCI: 1
…
SSS: 0
PSS: 2
not allowed
SSS: 0
PCI: 2 PSS: 0
PCI: 0

SSS: 0
PSS: 1
PCI: 1

PCI planning Vodafone confidential

August 25, 2014
 Atoll
Physical Cell ID (PCI) planning implementation

Atoll implementation (1)

Automatic Allocation (Atoll 2.8.3. built 3507)
without AFP module using AFP module

Relations based on: neighbours, min reuse distance

Strategy free, same SSS-ID per site

ID-Range Entire (0-503); excluded IDs

Code range restrictions need to be defined for each allocation /

no restriction possible (without AFP module)
Æ AFP module required!
PCI planning Vodafone confidential
August 25, 2014
 Atoll
Physical Cell ID (PCI) planning implementation

Atoll implementation (2)

Results without AFP usage (1):

Allocation strategy SSS-ID “same per site” is implemented only as “soft constraint”

PCI planning Vodafone confidential

August 25, 2014
 Atoll
Physical Cell ID (PCI) planning implementation

Atoll implementation (3)

Results without AFP usage (2):

Atoll allocates reuse for the CPIs although there is no need to have a reuse

PCI planning Vodafone confidential

August 25, 2014
Physical Cell ID (PCI) planning Atoll requests
Atoll requests (1)

Requests addressed to Forsk:

1. Implementation of “Code group” and “Code domain” based on SSS-ID

• enable area wise PCI allocation (border coordination)

2. SSS-ID Allocation Strategy “same per site” implemented as “hard constraint”

• to follow Vodafone strategy

3. Usage of all available Codes within allocation

• radio planner is in charge of PCI resources, not Atoll

PCI planning Vodafone confidential

August 25, 2014
Physical Cell ID (PCI) planning Atoll requests
Atoll requests (1)

Feedback from Forsk:

Atoll 2.8.3 built 3616 (temporary) Æ built 3782 (public)

• same SSS-ID per site

• still soft constraint
• bug fixed that enhances the co-sites relations
• strengthened weight assigned to this constraint
• weights can be changed within atoll.ini file

• ID range
• different ranges can be assigned using AFP

• Uniform distribution
• can be activated within atoll.ini
[OFDM]
UniformIDDistribution = 1

Atoll 3.1.1

• implementation of all addressed requests for PCI allocation within AFP

PCI planning Vodafone confidential

August 25, 2014
Physical Cell ID (PCI) planning
Final Atoll
Final Atoll Implementation – Check (1) Implementation

all Sites on air by 22.02.2011

• 204 Sites
• 574 Transmitter

Perform allocation based on

Atoll 2.8.3 built 3616

Step 1: Automatic Neighbour allocation

Step 2: PCI allocation

PCI planning Vodafone confidential

August 25, 2014
Physical Cell ID (PCI) planning
Final Atoll
Final Atoll Implementation – Check (2) Implementation

Settings used for Neighbour Allocation

PCI planning Vodafone confidential

August 25, 2014
Physical Cell ID (PCI) planning
Final Atoll
Final Atoll Implementation – Check (3) Implementation

Atoll 2.8.3 built 3616

atoll.ini

[OFDM] [OFDM] [OFDM] [OFDM]

UniformIDDistribution = 1 UniformIDDistribution = 1 UniformIDDistribution = 1 UniformIDDistribution = 1

[LTE] [LTE] [LTE] [LTE]

IDWeight = 50 IDWeight = 15 IDWeight = 70 IDWeight = 15
PSSWeight = 25 PSSWeight = 15 PSSWeight = 15 PSSWeight = 70
SSSWeight = 25 SSSWeight = 70 SSSWeight = 15 SSSWeight = 15

4 different configurations within atoll.ini have been used

PCI planning Vodafone confidential

August 25, 2014
 Physical Cell ID (PCI) planning
Final Atoll
Final Atoll Implementation – Check (4) Implementation

Results:
[OFDM] [OFDM] [OFDM] [OFDM]
UniformIDDistribution = 1 UniformIDDistribution = 1 UniformIDDistribution = 1 UniformIDDistribution = 1

[LTE] [LTE] [LTE] [LTE]

IDWeight = 50 IDWeight = 15 IDWeight = 70 IDWeight = 15
PSSWeight = 25 PSSWeight = 15 PSSWeight = 15 PSSWeight = 70
SSSWeight = 25 SSSWeight = 70 SSSWeight = 15 SSSWeight = 15

PCI planning Vodafone confidential

August 25, 2014
Physical Cell ID (PCI) planning
Final Atoll
Final Atoll Implementation – Check (5) Implementation

Results:

PCI allocation for 4 sector solution possible

with current implementation

PCI planning Vodafone confidential

August 25, 2014
Physical Cell ID (PCI) planning
Final Atoll
Final Atoll Implementation – Check (6) Implementation

Atoll 3.1.1 built 4286

Domains and
Groups are available

Domains assigned for each transmitter

PCI planning Vodafone confidential

August 25, 2014
 Physical Cell ID (PCI) planning
Final Atoll
Final Atoll Implementation – Check (7) Implementation

Atoll 3.1.1 built 4286 with AFP

Relation weights to be defined via

Constraint violation dialogue window

Uniform distribution
PCI planning Vodafone confidential
August 25, 2014
Physical Cell ID (PCI) planning
Final Atoll
Final Atoll Implementation – Check (8) Implementation

Atoll 3.1.1 built 4286 without AFP

No allocation without module possible

Æ AFP module required!

PCI planning Vodafone confidential

August 25, 2014
Physical Cell ID (PCI) planning
Final Atoll
Final Atoll Implementation – Check (9) Implementation

Summary:
      Atoll Atoll
Task 2.8.3  3.1.x 3.2.1
automated allocation AFP (ranges) / no AFP (only total range) only with AFP  AFP with RACH Rootsequence
index planning
groups / domains ‐‐ available available
same SSS ID per site soft constraint, weighting possible soft constraint, weighting possible

uniform distribution atoll.ini: "UniformIDDistribution = 1" defined within allocation dialogue

allocation strategies weighting via atoll.ini weighted via dialogue window

relation impact ‐‐ weighted via dialogue window

allocation time 100% (reference) 10% to 20% (of reference)

all addressed request have been implemented,

no additional request identified

PCI planning Vodafone confidential

August 25, 2014