Sei sulla pagina 1di 25

Physical Cell ID (PCI ) planning

Principle, planning requirements and Atoll implementation

Hans Jörg Hamers VF-TSO- Access- Design

1

PCI planning 25 August 2014

Vodafone confidential

and Atoll implementation Hans Jörg Hamers VF-TSO- Access- Design 1 PCI planning 25 August 2014 Vodafone

Physical Cell ID (PCI) planning

Principle, planning requirements and Atoll Implementation

Principle
Principle

Understand

- PCI implementation based on the 3GPP Specification

Planning requirements
Planning requirements

Understand

- planning requirements as result of the PCI implementation

Atoll Implementation
Atoll Implementation
Atoll requests
Atoll requests

Understand

- current implementation and restrictions within Atoll 2.8.3

Understand

- requests to Forsk on PCI allocation algorithm

Final Atoll Implementation
Final Atoll
Implementation

2

PCI planning 25 August 2014

Understand

- final implementation within Atoll 2.8.3 and 3.1.1

Vodafone confidential

2 PCI planning 25 August 2014 Understand - final implementation wit hin Atoll 2.8.3 and 3.1.1

Physical Cell ID (PCI) planning

Principle (1)

Principle
Principle

• 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

Physical layer cell identity (1 out of 504)
Physical layer
cell identity
(1 out of 504)
Principle Physical layer cell identity (1 out of 504) Site x Site y 0 1 0
Principle Physical layer cell identity (1 out of 504) Site x Site y 0 1 0
Site x Site y 0 1 0 1 2 0 1 2
Site x
Site y
0 1
0
1
2
0
1
2
(1 out of 504) Site x Site y 0 1 0 1 2 0 1 2

Site z

167

0 1 2
0
1
2
identified by …
identified by …

Physical layer cell identity group

Physical layer

identity

Physical layer cell identity group Physical layer identity 1. Primary synchronisation signal - 3 possible sequences

1.

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

2.

Secondary synchronisation signal - 168 different sequences to identify physical layer cell identity group

The rule is like following:

N ID (1) = 0 … 167; N ID (2) = 0,1,2; N ID cell
N ID (1) = 0 … 167; N ID (2) = 0,1,2;
N ID cell = 3N ID (1) + N ID (2)
PCI planning
August 25, 2014
Vodafone confidential
(1) = 0 … 167; N ID (2) = 0,1,2; N ID cell = 3N ID

Physical Cell ID (PCI) planning

Principle (2)

Principle
Principle
Physical Cell ID (PCI) planning Principle (2) Principle PCI planning August 25, 2014 Vodafone confidential

PCI planning August 25, 2014

Vodafone confidential

Physical Cell ID (PCI) planning Principle (2) Principle PCI planning August 25, 2014 Vodafone confidential
Principle
Principle

Physical Cell ID (PCI) planning

Principle (3)

Principle Physical Cell ID (PCI) planning Principle (3) PCI planning August 25, 2014 Vodafone confidential

PCI planning August 25, 2014

Vodafone confidential

Principle Physical Cell ID (PCI) planning Principle (3) PCI planning August 25, 2014 Vodafone confidential

Physical Cell ID (PCI) planning

Principle (4)

Frequency shift for RS

Principle
Principle
subcarrier
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 August 25, 2014

Vodafone confidential

… 1 1,7,13,19, … … … 5 5,11,17,23, … PCI planning August 25, 2014 Vodafone confidential

Physical Cell ID (PCI) planning

Planning requirements (1)

Planning requirements
Planning
requirements
Vodafone strategy:
Vodafone strategy:

in line with vendor strategy: Ericsson and Huawei

PCI planning August 25, 2014

Vodafone confidential

Vodafone strategy: in line with vendor strategy: Ericsson and Huawei PCI planning August 25, 2014 Vodafone

Physical Cell ID (PCI) planning

Planning requirements (2)

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

PCI planning August 25, 2014

Vodafone confidential

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

Physical Cell ID (PCI) planning

Planning requirements (3)

Planning requirements
Planning
requirements

Example:

Planning requirements (3) Planning requirements Example: Site with group identity 8 assigned PCIs 24,25,26 The
Planning requirements (3) Planning requirements Example: Site with group identity 8 assigned PCIs 24,25,26 The
Planning requirements (3) Planning requirements Example: Site with group identity 8 assigned PCIs 24,25,26 The

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 August 25, 2014

Vodafone confidential

are assigned different primary sequences and the same identity Group. PCI planning August 25, 2014 Vodafone

Physical Cell ID (PCI) planning

Planning requirements (4)

Planning requirements
Planning
requirements

Example: 3 Sector Site

(4) Planning requirements Example: 3 Sector Site SSS: 0 PSS: 0 SSS: 0 PSS: 2 SSS:

SSS: 0

PSS: 0

requirements Example: 3 Sector Site SSS: 0 PSS: 0 SSS: 0 PSS: 2 SSS: 0 PSS:

SSS: 0

PSS: 2

Example: 3 Sector Site SSS: 0 PSS: 0 SSS: 0 PSS: 2 SSS: 0 PSS: 1
Example: 3 Sector Site SSS: 0 PSS: 0 SSS: 0 PSS: 2 SSS: 0 PSS: 1

SSS: 0

PSS: 1

3 Sector Site SSS: 0 PSS: 0 SSS: 0 PSS: 2 SSS: 0 PSS: 1 Modulo

Modulo 6:

0,1,2,

6,7,8,

12,13,14,

18,19,20,

not allowed

SSS: 1

PSS: 2

PCI: 5

18,19,20, … not allowed SSS: 1 PSS: 2 PCI: 5 SSS: 1 PSS: 1 SSS: 1

SSS: 1

PSS: 1

… not allowed SSS: 1 PSS: 2 PCI: 5 SSS: 1 PSS: 1 SSS: 1 PSS:

SSS: 1

PSS: 0

PCI: 3
PCI: 3
SSS: 1 PSS: 2 PCI: 5 SSS: 1 PSS: 1 SSS: 1 PSS: 0 PCI: 3

PCI planning August 25, 2014

Vodafone confidential

SSS: 1 PSS: 2 PCI: 5 SSS: 1 PSS: 1 SSS: 1 PSS: 0 PCI: 3

Physical Cell ID (PCI) planning

Planning requirements (5)

Example: 4 Sector Site

SSS: 0

PSS: 2

requirements (5) Example: 4 Sector Site SSS: 0 PSS: 2 SSS: ? PSS: ? PCI: ?

SSS: ?

PSS: ? PCI: ?
PSS: ?
PCI: ?
Example: 4 Sector Site SSS: 0 PSS: 2 SSS: ? PSS: ? PCI: ? SSS: 0
Example: 4 Sector Site SSS: 0 PSS: 2 SSS: ? PSS: ? PCI: ? SSS: 0

SSS: 0

PSS: 0

Site SSS: 0 PSS: 2 SSS: ? PSS: ? PCI: ? SSS: 0 PSS: 0 SSS:

SSS: 0

PSS: 1

0 PSS: 2 SSS: ? PSS: ? PCI: ? SSS: 0 PSS: 0 SSS: 0 PSS:

PCI planning August 25, 2014

Modulo 6:

0,1,2,

6,7,8,

12,13,14,

18,19,20,

SSS: 1

PSS: 1 PCI: 4
PSS: 1
PCI: 4
6: 0,1,2, 6,7,8, 12,13,14, 18,19,20, SSS: 1 PSS: 1 PCI: 4 SSS: 0 SSS: 0 PSS:

SSS: 0

SSS: 0

PSS: 2

18,19,20, SSS: 1 PSS: 1 PCI: 4 SSS: 0 SSS: 0 PSS: 2 PSS: 1 PCI:
18,19,20, SSS: 1 PSS: 1 PCI: 4 SSS: 0 SSS: 0 PSS: 2 PSS: 1 PCI:
PSS: 1 PCI: 1
PSS: 1
PCI: 1

not allowed

Vodafone confidential

Planning requirements
Planning
requirements

SSS: 0

PSS: 0 PCI: 0
PSS: 0
PCI: 0
4 SSS: 0 SSS: 0 PSS: 2 PSS: 1 PCI: 1 … not allowed Vodafone confidential

Physical Cell ID (PCI) planning

Atoll implementation (1)

Automatic Allocation (Atoll 2.8.3. built 3507)

Atoll implementation
Atoll
implementation

without AFP module

using AFP module

Atoll implementation without AFP module using AFP module based on: neighbours, min reuse distance free, same

based on: neighbours, min reuse distance

free, same SSS-ID per site

neighbours, min reuse distance free, same SSS-ID per site Relations Strategy ID-Range Entire (0-503); excluded IDs
Relations Strategy
Relations
Strategy
ID-Range Entire (0-503); excluded IDs Code range restrictions need to be defined for each allocation
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
August 25, 2014
Vodafone confidential
no restriction possible (without AFP module) AFP module required! PCI planning August 25, 2014 Vodafone confidential

Physical Cell ID (PCI) planning

Atoll implementation (2)

Results without AFP usage (1):

Atoll implementation (2) Results without AFP usage (1): Atoll implementation Allocation strategy SSS-ID “same per
Atoll implementation (2) Results without AFP usage (1): Atoll implementation Allocation strategy SSS-ID “same per
Atoll implementation
Atoll
implementation
Allocation strategy SSS-ID “same per site” is implemented only as “soft constraint”
Allocation strategy SSS-ID “same per site” is implemented only as “soft constraint”

PCI planning August 25, 2014

Vodafone confidential

SSS-ID “same per site” is implemented only as “soft constraint” PCI planning August 25, 2014 Vodafone

Physical Cell ID (PCI) planning

Atoll implementation (3)

Results without AFP usage (2):

Atoll implementation (3) Results without AFP usage (2): Atoll implementation Atoll allocates reuse for the CPIs
Atoll implementation
Atoll
implementation
(3) Results without AFP usage (2): Atoll implementation Atoll allocates reuse for the CPIs although there
Atoll allocates reuse for the CPIs although there is no need to have a reuse
Atoll allocates reuse for the CPIs although there is no need to have a reuse

PCI planning August 25, 2014

Vodafone confidential

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

Physical Cell ID (PCI) planning

Atoll requests (1)

Requests addressed to Forsk:

Atoll requests
Atoll requests

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 August 25, 2014

Vodafone confidential

allocation • radio planner is in charge of PCI resources, not Atoll PCI planning August 25,

Physical Cell ID (PCI) planning

Atoll requests (1)

Feedback from Forsk:

Atoll requests
Atoll requests

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 August 25, 2014

Vodafone confidential

implementation of all addressed requests for PCI allocation within AFP PCI planning August 25, 2014 Vodafone

Physical Cell ID (PCI) planning

Final Atoll Implementation – Check (1)

ID (PCI) planning Final Atoll Implementation – Check (1) PCI planning August 25, 2014 Vodafone confidential

PCI planning August 25, 2014

Vodafone confidential

Final Atoll Implementation
Final Atoll
Implementation

all Sites on air by 22.02.2011

• 204 Sites

• 574 Transmitter

Sites on air by 22.02.2011 • 204 Sites • 574 Transmitter Perform allocation based on Atoll

Perform allocation based on Atoll 2.8.3 built 3616

Step 1: Automatic Neighbour allocation

Step 2: PCI allocation

Perform allocation based on Atoll 2.8.3 built 3616 Step 1: Automatic Neighbour allocation Step 2: PCI

Physical Cell ID (PCI) planning

Final Atoll Implementation – Check (2)

Final Atoll Implementation
Final Atoll
Implementation
Implementation – Check (2) Final Atoll Implementation Settings used for Neighbour Allocation PCI planning August

Settings used for Neighbour Allocation

PCI planning August 25, 2014

Vodafone confidential

(2) Final Atoll Implementation Settings used for Neighbour Allocation PCI planning August 25, 2014 Vodafone confidential

Physical Cell ID (PCI) planning

Final Atoll Implementation – Check (3)

Final Atoll Implementation
Final Atoll
Implementation

Atoll 2.8.3 built 3616

Check (3) Final Atoll Implementation Atoll 2.8.3 built 3616 [OFDM] UniformIDDistribution = 1 [LTE] IDWeight =

[OFDM] UniformIDDistribution = 1

[LTE] IDWeight = 50 PSSWeight = 25 SSSWeight = 25

atoll.ini

[OFDM] UniformIDDistribution = 1

[LTE] IDWeight = 15 PSSWeight = 15 SSSWeight = 70

[OFDM] UniformIDDistribution = 1

[LTE] IDWeight = 70 PSSWeight = 15 SSSWeight = 15

[OFDM] UniformIDDistribution = 1

[LTE] IDWeight = 15 PSSWeight = 70 SSSWeight = 15

4 different configurations within atoll.ini have been used

PCI planning August 25, 2014

Vodafone confidential

= 15 4 different configurations within atoll.ini have been used PCI planning August 25, 2014 Vodafone

Physical Cell ID (PCI) planning

Final Atoll Implementation – Check (4)

Results:

[OFDM] UniformIDDistribution = 1

[LTE] IDWeight = 50 PSSWeight = 25 SSSWeight = 25

[OFDM] UniformIDDistribution = 1

[LTE] IDWeight = 15 PSSWeight = 15 SSSWeight = 70

[OFDM] UniformIDDistribution = 1

[LTE] IDWeight = 70 PSSWeight = 15 SSSWeight = 15

= 1 [LTE] IDWeight = 70 PSSWeight = 15 SSSWeight = 15 PCI planning August 25,
= 1 [LTE] IDWeight = 70 PSSWeight = 15 SSSWeight = 15 PCI planning August 25,

PCI planning August 25, 2014

PSSWeight = 15 SSSWeight = 15 PCI planning August 25, 2014 Vodafone confidential Final Atoll Implementation
PSSWeight = 15 SSSWeight = 15 PCI planning August 25, 2014 Vodafone confidential Final Atoll Implementation
PSSWeight = 15 SSSWeight = 15 PCI planning August 25, 2014 Vodafone confidential Final Atoll Implementation
PSSWeight = 15 SSSWeight = 15 PCI planning August 25, 2014 Vodafone confidential Final Atoll Implementation

Vodafone confidential

Final Atoll Implementation
Final Atoll
Implementation

[OFDM] UniformIDDistribution = 1

[LTE] IDWeight = 15 PSSWeight = 70 SSSWeight = 15

Final Atoll Implementation [OFDM] UniformIDDistribution = 1 [LTE] IDWeight = 15 PSSWeight = 70 SSSWeight =
Final Atoll Implementation [OFDM] UniformIDDistribution = 1 [LTE] IDWeight = 15 PSSWeight = 70 SSSWeight =
Final Atoll Implementation [OFDM] UniformIDDistribution = 1 [LTE] IDWeight = 15 PSSWeight = 70 SSSWeight =

Physical Cell ID (PCI) planning

Final Atoll Implementation – Check (5)

Results:

planning Final Atoll Implementation – Check (5) Results: PCI planning August 25, 2014 Vodafone confidential Final

PCI planning August 25, 2014

Vodafone confidential

Final Atoll Implementation
Final Atoll
Implementation

PCI allocation for 4 sector solution possible with current implementation

confidential Final Atoll Implementation PCI allocation for 4 sector solution possible with current implementation
confidential Final Atoll Implementation PCI allocation for 4 sector solution possible with current implementation

Physical Cell ID (PCI) planning

Final Atoll Implementation – Check (6)

Final Atoll Implementation
Final Atoll
Implementation

Atoll 3.1.1 built 4286

Domains and Groups are available
Domains and
Groups are available
Atoll 3.1.1 built 4286 Domains and Groups are available Domains assigned for each transmitter PCI planning

Domains assigned for each transmitter

PCI planning August 25, 2014

Vodafone confidential

Domains and Groups are available Domains assigned for each transmitter PCI planning August 25, 2014 Vodafone

Physical Cell ID (PCI) planning

Final Atoll Implementation – Check (7)

Atoll 3.1.1 built 4286 with AFP

Implementation – Check (7) Atoll 3.1.1 built 4286 with AFP Relation Constraint violation weights to be

Relation Constraint violation

3.1.1 built 4286 with AFP Relation Constraint violation weights to be defined via dialogue window Uniform

weights to be defined via dialogue window

violation weights to be defined via dialogue window Uniform distribution PCI planning August 25, 2014 Vodafone

Uniform distribution

to be defined via dialogue window Uniform distribution PCI planning August 25, 2014 Vodafone confidential Final
to be defined via dialogue window Uniform distribution PCI planning August 25, 2014 Vodafone confidential Final

PCI planning August 25, 2014

Vodafone confidential

Final Atoll Implementation
Final Atoll
Implementation
via dialogue window Uniform distribution PCI planning August 25, 2014 Vodafone confidential Final Atoll Implementation

Physical Cell ID (PCI) planning

Final Atoll Implementation – Check (8)

Atoll 3.1.1 built 4286 without AFP

– Check (8) Atoll 3.1.1 built 4286 without AFP No allocation without module possible AFP module
No allocation without module possible AFP module required!
No allocation without module possible
AFP module required!

PCI planning August 25, 2014

Vodafone confidential

Final Atoll Implementation
Final Atoll
Implementation
module possible AFP module required! PCI planning August 25, 2014 Vodafone confidential Final Atoll Implementation

Physical Cell ID (PCI) planning

Final Atoll Implementation – Check (9)

Summary:

Final Atoll Implementation
Final Atoll
Implementation
   

Atoll

Atoll

Task

2.8.3

 

3.1.x

3.2.1

automated allocation

AFP (ranges) / no AFP (only total range)

   

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)

 

PCI planning August 25, 2014

all addressed request have been implemented, no additional request identified
all addressed request have been implemented,
no additional request identified

Vodafone confidential

August 25, 2014 all addressed request have been implemented, no additional request identified Vodafone confidential