11 RA4120BEN20GLA0 LTE Deployment Scenarios v03

LTE Deployment Scenarios

LTE RPESS LTE Deploym Deployment ent Scenario Scenarioss

1

©Nokia ©NokiaSiem emens Networks

RA4120BEN20GLA0

RA4120BEN20GLA0

1


Nokia Siemens Siemens Networks Academy Legal notice Intellectual Property Rights All All copyrig rights and inte intelllle ectua tual prop roperty rty rig rights for for Nokia Siem iemens Netwo tworks rks tra trainin ining g documentati tatio on, prod roduct documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.

2

© Nokia Siemens Networks

RA4120BEN20GLA0

RA4120BEN20GLA0

2


Module Objectives Aft Afte er completi letin ng this this module, le, the the partic ticipa ipant should be able to: to:

• Identify different solutions to provide LTE Coverage • Discuss alternatives to improve the indoor coverage • Understand the concept of Microcell • Describe at an overview overview level the the requir requirem ements ents for Co-Sit Co-Siting ing isolation isolation & configuration

• Recall ecall the concepts concepts of Tracking Area, Area, eNode eNode B identi identififier, er, neighbour neighbour cell and its planning principles.

3


RA4120BEN20GLA0

RA4120BEN20GLA0

3


Module Contents

• Macrocells Indoorr So Soluti lutions ons • Indoo • Microcells Bands nds • Co-Siting Ba • Co-Planning Tracking Area Planning − Physical Layer Cell Identity Planning eNode odeB B and and Cell Identity Identity Planning − eN − Neighbour Planning

−

4


RA4120BEN20GLA0

RA4120BEN20GLA0

4


Introduction

Macrocells • provide coverage and capacity across wide areas • Standard deployment solution

Indoor solutions • improve coverage when indoor macrocell coverage is weak • provide high capacity solutions

Microcells • serve traffic hotspots • provide coverage when macrocell sites are not available

5


RA4120BEN20GLA0

RA4120BEN20GLA0

5


Macrocell with Flexi Multiradio BTS • Flexi RF modules can be located adjacent to the Flexi System module (Picture on the left)

• But Flexi RF modules can also be located adjacent to the antenna to create a feeder-less design (optical connection between System Module and RF Module)

• Tower Mounted Amplifier (TMA) / Mast Head Amplifier (MHA) can be used to compensate for feeder losses in the uplink direction

• Antennas can be mounted according to the site design, e.g. roof-top, mast, Optional TMA/MHA

side of building

RF Connection

System Module 1 or 2 RF Modules Optional AC/DC with Battery Backup 6


RA4120BEN20GLA0

TMA not meaningful, if RF Module is close to antenna

RA4120BEN20GLA0

6


LTE 2600 can be deployed on UMTS 2100MHz grid (figures applicable to Urban Deployment) Uplink

Downlink UMTS

UMTS LTE

LTE 1.08km

1.17km

1.09km

1.22km

142.8dB

140.2dB

142.9dB

140.8dB

Conclusion 

Delta between max. allowable pathloss values: 

2.1 dB in downlink benefit of LTE 2.6 dB in uplink benefit of LTE

7




Delta between outdoor cell range values:



DL:LTE cell range nearly identical to UMTS UL:LTE cell range nearly identical to UMTS

RA4120BEN20GLA0

RA4120BEN20GLA0

7


Module Contents

• Macrocells • Indoor Solutions • Microcells • Co-Siting Bands • Co-Planning Tracking Area Planning − Physical Layer Cell Identity Planning − eNodeB and Cell Identity Planning − Neighbour Planning

−

8


RA4120BEN20GLA0

RA4120BEN20GLA0

8


Indoor Solutions • Indoor solutions can be based upon the Flexi BTS connected to a Distributed Antenna System (DAS)

• Passive DAS for small and moderate sized indoor areas • Active DAS for large indoor areas • Passive and Active DAS connected to a Flexi BTS are able to provide both coverage and capacity. Multiple sectors can be licensed to increase capacity

• Repeaters can also be used to extend outdoor coverage across an indoor area • Historically, indoor solutions have been designed with single transmit and receive paths. This excludes the possibility of uplink receive diversity and MIMO

• Indoor solution design requires a set of planning guidelines to ensure that proven approaches are used in a consistent manner

9


RA4120BEN20GLA0

RA4120BEN20GLA0

9


Minimum Coupli ng Loss (MCL) • MCL represents the minimum allowed link loss between the UE and Node B cabinet antenna connector • The MCL should be sufficient to ensure that the BTS does not become desensitised when a UE is physically close to an antenna

• The MCL should also be sufficient to ensure that the UE does not receive more downlink power than it is capable of receiving when it is physically close to an antenna

• The MCL requirement depends upon the thermal noise floor of the Node B receiver, i.e. dependant upon receiver bandwidth and Noise Figure

• Assuming a 43 dBmtransmit power from the LTE BTS means that an MCL of 68 dB is required to ensure that UE do not receive more than -25 dBm

(from 3GPP TS 36.101)

Comparing the uplink and downlink MCL requirements indicates that the uplink requirement dominates: an MCL of between 70 and 75 dB is necessary 10


RA4120BEN20GLA0

RA4120BEN20GLA0

10


Antenna Placement • Indoor solution design includes making decisions regarding the location of each remote antenna • Antenna placement should account for:  Service and Reference Signal link budget requirements  Leakage requirements  Distribution of interference fromthe Macrocell layer  Minimum Coupling Loss (MCL) requirements  Distribution of UE and the associated traffic

Sectorisation Strategy • • • • • • 11

Indoor solutions may be configured with single or multiple sectors The level of sectorisation should be defined by the capacity requirements This requires a definition of the traffic expectation Sectorisation should be planned to achieve sufficient isolation between sectors Sectorisation in multi-storey buildings can take advantage of the inter-floor isolation Overlap is required to allow time for inter-sector handover © Nokia Siemens Networks

RA4120BEN20GLA0

RA4120BEN20GLA0

11


Selection between Active and Passive DAS • Two general approaches can be adopted:  passive DAS should be able to maintain ~15 dBmof downlink transmit power at

each antenna. If not, then active DAS should be selected  rule-of-thumb based upon the number of antennas, e.g. if the antenna requirement

is above 5 then select an active DAS

• In general, active DAS are easier to sectorise subsequent to initial deployment because it is relatively easy to lay spare fibre optic during installation

RF Carrier Assignment • RF carrier used for indoor solutions can be the same as that used for the outdoor macrocell • Unlikely to be practical to dedicate and RF carrier to indoor solutions when wide bandwidths are allocated to LTE

• Important to ensure that indoor solution has dominance so the number of antennas required may increase if macrocell signal is relatively strong indoors 12


RA4120BEN20GLA0

RA4120BEN20GLA0

12


Verification of Existi ng Coverage • Indoor solution may be proposed for coverage or capacity reasons • Possible that macrocell layer already provides coverage while indoor solution is required for capacity

• Important that indoor solution dominated over macrocell to avoid loading the macrocell layer

• Macrocell measurements should be recorded prior to indoor solution design

Leakage Requirements • Requirement to minimise leakage from indoor solution to the outdoor environment • If leakage is not limited then UE in the outdoor environment could camp and establish connections upon the indoor solution

• An example approach is that the indoor solution Reference Signal Received Power (RSRP) should not exceed –125 dBmat a distance of 20 m from the building

• This absolute power threshold may be translated into a link loss based threshold

13


RA4120BEN20GLA0

RA4120BEN20GLA0

13


Mobility with Macrocell Layer • LTE handovers are based upon Reference Signal Received Power (RSRP) or Reference Signal Received Quality (RSRQ)

• Handover and cell re-selection boundaries between macrocell and indoor solution will depend upon:  relative transmit powers of the indoor solution and macrocell  measurement offsets defined for each adjacency

• If handover boundary is too close to the indoor solution then there is a danger that the indoor solution experiences uplink interference from UE connected to macrocells

Macrocell Reference Signal EIRP Indoor Solution Reference Signal EIRP

• Measurement offsets should be applied with care because they can result in MS not being connected to the ‘best’ cell

• Indoor solution handover areas are usually located around the building entrances

Potential interference

• Tall buildings may have stronger macrocell coverage MS approaching indoor solution

14


across the upper floors, potentially allowing MS to handover onto macrocells inside the building

RA4120BEN20GLA0

RA4120BEN20GLA0

14


Module Contents

• Macrocells • Indoor Solutions • Microcells • Co-Siting Bands • Co-Planning Tracking Area Planning − Physical Layer Cell Identity Planning − eNodeB and Cell Identity Planning − Neighbour Planning

−

15


RA4120BEN20GLA0

RA4120BEN20GLA0

15


Microcells • Microcells can be used to serve traffic hotspots • A microcell can be categorised as a Node B which has outdoor, below rooftop antenna placement

• Like macrocell, a microcell Node B is a Flexi System Module equipped with a Flexi RF module

• The isolation provided by neighbouring buildings limits both coverage and inter-cell interference Microcell based upon Flexi RF Module

16


RA4120BEN20GLA0

RA4120BEN20GLA0

16


Microcell Link Budget • Microcell antennas typically have a lower gain than macrocell antennas e.g. 12 dBi • Lower gain corresponds to less directivity and an increase in vertical beamwidth

Microcell antenna

Macrocell antenna

• Feeders are typically short but may have a smaller diameter than that used for macrocells – smaller diameter allows a tighter bending radius for easier installation

• Microcells are typically introduced for capacity so should be planned assuming a relatively high cell load for both UL & DL. Example Parameters for Microcell Link Budget

17


Antenna Gain

12 dBi

Feeder Loss

1 dB

Uplink Load

80 %

RA4120BEN20GLA0

RA4120BEN20GLA0

17


Microcell Sectorisation • Sectorisation of LTE microcells is unlikely to be common because it’s difficult to achieve sufficient isolation between sectors

• Sectorised GSM microcells benefit from having different RF carriers assigned to each sector • The high quantity of scattering tends to mean that sectors have very similar coverage areas • Antenna direction may not have a very large impact as a result of the scattering

Example Microcell Propagation for two cells with different antenna directions

18


RA4120BEN20GLA0

RA4120BEN20GLA0

18


Microcell RF Carriers • LTE microcells are likely to be configured using the same RF carrier as the macrocell layer

• Wide channel bandwidth results in a requirement to use a frequency re-use factor of 1

• Sharing the same RF carrier between macro and micro layers potentially results in a low isolation

• Most likely to be true when microcells are introduced for capacity within an area of macrocell coverage

• Requirement to ensure that microcells are dominant across their target coverage area • Sharing the same RF carrier allows intra-frequency hard handovers between the macro and micro layers

• Potential requirement to tune mobility parameters to account for differences between the macro and micro downlink transmit powers

19


RA4120BEN20GLA0

RA4120BEN20GLA0

19


Module Contents

• Macrocells • Indoor Solutions • Microcells • Co-Siting Bands • Co-Planning

− Tracking Area Planning − Physical Layer Cell Identity Planning − eNodeB and Cell Identity Planning − Neighbour Planning

20


RA4120BEN20GLA0

RA4120BEN20GLA0

20


Operating Bands Specified by 3GPP • LTE operating bands are similar to those for UMTS • This implies there will be a requirement for LTE to share operating bands with UMTS, i.e. to operate in adjacent spectrum

• In the case of co-siting for FDD RATs, the duplex spacing provides isolation in the frequency domain, i.e. the BTS transmit band is relatively distant from the BTS receive band LTE FDD Operating Bands (a part of the complete list) UMTS FDD Operating Bands Extract from 3GPP TS 25.104

21


RA4120BEN20GLA0

Extract from 3GPP TS 36.104

RL10 Flexi RF Module Support RL20 Flexi RF Module Support

RA4120BEN20GLA0

21


Module Contents



22


RA4120BEN20GLA0

RA4120BEN20GLA0

22


Introduction • Co-Planning activities are those for which re-use from other network planning projects may be applied

• Experience gained while planning 2G and 3G networks can be used to improve the efficiency with which LTE networks can be planned

• Potential activities for co-planning are: • 3G routing area planning with LTE tracking area planning • 3G Node B identity planning with LTE eNode B identity planning • 3G neighbour list planning with LTE neighbour list planning

23


RA4120BEN20GLA0

RA4120BEN20GLA0

23


Module Contents



24


RA4120BEN20GLA0

RA4120BEN20GLA0

24


Evolved Packet System

Background (I) • • • • • •

Tracking areas are used for EPS Mobility Management (EMM) Paging messages are broadcast across the tracking areas within which the UE is registered Each eNode B can contain cells belonging to different tracking areas Each cell can belong to several tracking area A tracking area can be shared by multiple MME Tracking Area Identity (TAI)

• Constructed from the Mobile Country Code (MCC), Mobile Network Code (MNC) and TAC (Tracking Area Code)

• The TAC, MCC and MNC are broadcast within SIB 1

S1 Application Protocol Paging Message extracted from 3GPP TS 36.413 Tracking areas are the equivalent of Location Areas and Routing Areas for LTE

25


RA4120BEN20GLA0

EMM Registered EMM Deregistered: Successful Attach and Tracking Area Update (TAU) procedures lead to transition to EMM-REGISTERED

RA4120BEN20GLA0

25


Background (II)

• The normal tracking area updating procedure is used when a UE moves into a tracking area within which it is not registered

• The periodic tracking area updating procedure is used to periodically notify the availability of the UE to the network (based upon T3412)

• Tracking area updates are also used for • registration during inter-system changes • MME load balancing

Further details in 3GPP TS 24.301

• Large tracking areas result in • Increased paging load • Reduced requirement for tracking area updates resulting from mobility

26


RA4120BEN20GLA0

MME load balancing: Since TA can belong to more than one MME, if one MME is loaded then it is possible to send the paging message through other MMEs

RA4120BEN20GLA0

26


Planning Guidelines

• Tracking areas should be planned to be relativ ely large (100 eNodeB) rather than relatively small

• Their size should be reduced subsequently if the paging load becomes high

• Existing 2G and 3G location area and routing area boundaries should be used as a basis for defining LTE tracking area boundaries

• Tracking areas should not run close to and parallel to major roads nor railways. Likewise, boundaries should not traverse dense subscriber areas

• Cells which are located at a tracking area boundary and which experience large numbers of updates should be monitored to evaluate the impact of the update procedures

27


RA4120BEN20GLA0

RA4120BEN20GLA0

27


Module Contents



28


RA4120BEN20GLA0

RA4120BEN20GLA0

28


Introduction Parameter Object Range • There are 504 unique Physical Layer Cell Identities phyCellId LNCEL 0 to 503 • Organised in 168 groups of 3 • NID1 in the range 0 to 167 represents the Physical Layer Cell Identity group

• NID2 in the range 0 to 2 represents the identity within the group • Physical Layer Cell Identity = (3 × NID1) + NID2 • NID2 defines the Primary Synchronisation Signal (PSS) sequence • NID1 defines the Secondary Synchronisation Signal (SSS) sequence • The Physical Layer Cell Identity has an impact upon the allocation of resource elements to the reference signal and the set of physical channels

Resource element allocation to the Reference Signal

Allocation pattern repeats every 6th Physical Layer Cell Identity 29


RA4120BEN20GLA0

Compared with 512 scrambling codes in 3G (64 groups of 8) First: PSS and SSS signals: The PSS is generated out of 3 different sequences – each of these sequences indicates one Physical Layer Cell Identity The SSS is generated out of 168 sequences – each of these sequences indicates one Physical Layer Cell Identity Group

RA4120BEN20GLA0

29


Planning (I)

• The allocation of physical layer cell identities is analogous to scrambling code planning for UMTS

• The isolation between cells which are assigned the same physical layer cell identity should be maximised

• The isolation between cells which are assigned the same physical layer cell identity should be sufficiently great to ensure that UE never simultaneously receive the same identity from more than a single cell. Id = 0

Example Physical Layer Cell Identity Plan

Id = 2

Id = 6 Id = 8

Id = 1 Id = 3 Id = 5

Id = 11 Id = 4

30


Id = 7 Id = 9

Id = 10

RA4120BEN20GLA0

RA4120BEN20GLA0

30


Planning (II)

• Specific physical layer cell identities can be excluded from theplan to allow for future network expansion or the introduction of Home eNodeB (Femto)

• If there is a possibility that the level of sectorization is going to be increased from 3 to 6 then every second group of identities could be allocated within the initial plan. This would allow eNodeB to be allocated identities from two adjacent groups when the number of cells is increased from 3 to 6

• There should be some level of co-ordination across international borders when allocating physical layer cell identities. This will help to avoid operators allocating the same identity to cells on the same RF carrier and in neighbouring geographic areas 31


RA4120BEN20GLA0

RA4120BEN20GLA0

31


Module Contents



32


RA4120BEN20GLA0

RA4120BEN20GLA0

32


eNode B Identifier • • • •

The Global eNodeB Identifier is used to identify eNode B globally It is constructed from the MCC, MNCand eNodeB Identifier (eNB-Id) The eNB-Id is used to identify eNBwithin a PLMN The eNB-Id can have a lengths of

• Short (20 bits) allowing – 256 cells to be addressed per eNB – 1 048 576 eNBper PLMN • Long (28 bits) allowing – 1 cell to be addressed per eNB – 268 435 456 eNBper PLMN

• The short eNB-ID is appropriate for macrocell networks which include more than a single cell per eNB

• The long eNB-ID is appropriate for picocell and femto networks which are based upon large numbers of Node B with only a single cell per Node B

33


RA4120BEN20GLA0

RA4120BEN20GLA0

33


Cell Identifi er • The E-UTRAN Cell Global Identifier (ECGI) is used to identify cells globally • The ECGI is constructed from the MCC, MNC and E-UTRAN Cell Identifier (ECI) • The ECI is used to identify cells within a PLMN • It has a length of 28 bits and contains the eNode B Identifier • It is only necessary to configure an ECI when a short eNB-Id is used • The ECI, MCC and MNC are broadcast within SIB 1

34


RA4120BEN20GLA0

RA4120BEN20GLA0

34


Module Contents



35


RA4120BEN20GLA0

RA4120BEN20GLA0

35


Background • LTE mobility does not rely upon neighbour lists • UE are responsible for identifying neighbouring cells • This effectively removes the requirement for neighbour list planning • However, the UE can be provided with: • neighbour cell specific measurement offsets, e.g. to make a specific neighbour appear more attractive

• RF carriers upon which to search for neighbours • Mobility information can be provided for: • E-UTRAN Intra-frequency • E-UTRAN Inter-frequency • UTRAN inter-RAT • GERAN inter-RAT • CDMA200 inter-RAT

36


RA4120BEN20GLA0

RA4120BEN20GLA0

36


Automated neighbor relation (ANR) configuration •

Neighbour relations are important as wrong neighbour definitions cause HO failures and dropped calls Self configuration of relations avoids manual planning & maintenance

•

ANR co vers 4 step s: 1)

Neighbour cell discovery

2)

Neighbour Site’s X2 transport configuration discovery (i.e. Neighbour Site IP@)

3)

X2 Connection Set-up with neighbour cell configuration update

4) ANR Optimization

•

The scope within ANR is to establish an X2 connection between source and target nodes and for that it is necessary that source eNB knows the target eNB IP@

•

How the source eNB gets the IP@ differentiates the ANR features:

37

–

LTE Automatic Neighbour Cell Configuration (RL09)

–

Central ANR (RL10)

–

ANR (RL20)

–

ANR- Fully UE based (RL30)


RA4120BEN20GLA0

NetAct Optimizer supervises all registered cell relations between neighbouring LTE cells if they are still valid and reliable candidates to be a hand over destination. When the outcome results in an inefficient neighbour relation the according cell relation may be blacklisted for handover (RL20)

RA4120BEN20GLA0

37


3GPP ANR configuration principle Neighbor Site eNB - B

Site eNB - A

UE connected

MME

New cell discovered New cell identified by ECGI

S1 : Request X2 Transport Configuration (ECGI)

relays request

S1: Request X2 Transport Configuration CM S1: Respond X2 Transport Configuration (IP@)

relays response

S1 : Respond X2 Transport Configuration (IP@) CM Add Site & Cell parameter of eNB-A

X2 Setup : IPsec, SCTP, X2-AP [site & cell info] CM

CM

Add Site & Cell Parameter of eNB-B

Neighbor Cell Tables in both eNB updated 38


RA4120BEN20GLA0

SCTP: Stream Control Transmission Protocol

RA4120BEN20GLA0

38


RL20

LTE ANR

Automated planning: NO configuration of any neighbor cell attributes •NetAct Optimizer and Configurator create the list of potential neighbour cells and related IP connectivity information •When UE reports an unknown PCI the source eNB looks for that PCI in look-up tables to find the IP@ of the site hosting the PCI reported UEs measurements taken into account to trigger the X2 connection •Once known target eNB IP@ the X2 connection is established and information between neighbours is exchanged Advantage: •Works with any UE (no need to report ECGI) •No neighbour site planning required

39


RA4120BEN20GLA0

Feature ID: LTE492

The resolution of PCI to IP-connectivity information is done by means of a PCI/RF/IP@ look-up table stored at the eNB, provided by O&M-configuration (NetAct Optimizer, NetAct Configurator). NetAct just provides in advance the mapping of IP@ to Physical Cell Ids.

RA4120BEN20GLA0

39

11 RA4120BEN20GLA0 LTE Deployment Scenarios v03

Recommend Documents