LTE971

For internal use only!
Network Engineering Information

P7 Enabling RL30/25TD
Feature LTE971: Intra-LTE Mobility Offsets
Network Engineering
NWS LTE RA E2E SA NE LTE&Access
Ulm, 06.07.2011
For internal use
1 © Nokia Siemens Networks
LTE971 Intra-LTE Mobility Offsets
Table of Contents
• Introduction
Motivation & Feature Overview Note:
The listed bullets reflect the standardized
• Feature Details subchapters of Network Engineering Information
Functionality & eNB Implementation (NEI). Chapter sequence may slightly deviate among
different features.
• Dimensioning Aspects Not all subchapters may contain content at any time,
Impact on Capacity & Link Budget, as
Modeling in Dimensioning Tools • some subchapters may generally not apply
• Configuration Aspects for particular features and
• particular content can only be added after learnings
Parameters & O&M from trial or field deployments.
• Expected Benefits Related remarks are provided for each section.
Gains & Performance Impact Analysis
• Application Aspects
Use Cases & Application Scenarios
• Performance Aspects
Feature Monitoring (Counters & KPIs)
For internal use

2 © Nokia Siemens Networks P7 Enabling RL30/25TD, Ulm, 06.07.2011
LTE971 Intra LTE Mobility Offsets
Table of Contents
• Introduction
• Feature Details
• Dimensioning Aspects
• Configuration Aspects
• Expected Benefits
For internal use
LTE971 Feature team
• SFS
– Michael Güßregen Lead, SyS Telecom
– Claudia Vallentin SysS Telecom
– Aloney Lin SysS Telecom
– Xu, Bin-Tony SysS Telecom
– Jürgen Mayer SysS Telecom
– R. De Benedittis SysS Telecom
– Helmut Hofmeister RA O&M
– Herbert Feldhahn RA O&M
• EFS
– Walter Mayer CP U1
• NetEng
– Wiczanowski Marcin NE LTE
For internal use

LTE971 Content
• LTE971 introduces configurable offsets for the use by event-triggered
measurement report procedure
– Applies to measurement report procedure triggered by entry/leaving
conditions of events A3 and A5
– 3gpp TS 36.331, sec. 5.5
• 2 kinds of offsets introduced
3gpp gen. / 36.331 sec. 5.5 PDDB / CCPM
– Cell-specific offsets
cellIndividualOffset / Ocs cellIndOffServ
▪ Offset of serving cell:
▪ Offset of neighbor cell: cellIndividualOffset / Ocn cellIndOffNeigh
– Frequecy-specific offsets 3gpp gen. / 36.331 sec. 5.5 PDDB / CCPM
▪ Offset of carrier frequency of offsetFreq / Ofs offsetFreqIntra

serving cell:
▪ Offset of carrier frequency different offsetFreq / Ofn offsetFreqInter
from frequency of serving cell:
– Note: Carrier in this document = EUTRA measurement object =

object associated with particular EARFCN
For internal use
LTE971 Motivation
• The LTE971 offsets are expected to serve as optimization parameter/variables for
mobility and load optimization procedures which make use of A3 or A5 event-
triggered measurement reports
Client features:
Tool feature:
Conventional (manual) operation E.g. SON automation
LTE971
• Offsets introduced by LTE971 can be used by client

feature e.g. to
– Improve performance of intra-LTE HOs (A3 or A5 LTE533@RL30
event-triggered)
– Improve the coexistence performance of A3 and A5 LTExxx@RL50
event-triggered HOs
– Displace connections accross cells or frequency layers LTE1140@RL40
via enforced A3 or A5 event-triggered HOs
• RL30/25TD client feature of LTE971 is LTE533 Mobility Robustness

• RL40 client feature of LTE971 is LTE1140 Intra-frequency Load Balancing
For internal use

Table of Contents
• Introduction
• Feature Details
For internal use
LTE971 Impact on A3 event entry condition
• A3 event entry condition (impact on leaving condition is analogous):
Measurement server  cellIndOff Serv server  offsetFreqIntra server  a3Offset (...) 

Measurement candidate  cellIndOff Neighcandidate  offsetFreq(???)candidate  hysA3Offset (...)
• (???)=Intra if candidate on same carrier as server (same MeasObjectEUTRA)

– Otherwise, (???)=Inter (different MeasObjectEUTRA)
• (...) is determined by
– carrier of candidate (same/different MeasObjectEUTRA than server)
– TriggerQuantity in ReportConfig IE
• In RL30 Measurement is determined by TriggerQuantity in ReportConfigEUTRA IE

– TriggerQuantity=RSRQ is possible only for different MeasObjectEUTRA than server
– TriggerQuantity=RSRP always for same MeasObjectEUTRA as server
• A3 report is triggered upon A3 event entry condition is satisfied consecutively

during a3TimeToTrigger(...) time
– (...) is determined by carrier of candidate (same/different MeasObjectEUTRA than
server) and TriggerQuantity in ReportConfigEUTRA IE
For internal use
Measurement assessment
period (at UE)
RSRP/Q server
Δ > cellIndOffServ - cellIndOffNeigh +

offsetFreqIntra - offsetFreq(???) +
hysA3Offset(...) + a3Offset(...)
RSRP/Q candidate
Trigger of A3 event
a3TimeToTrigger(...) measurement report (at UE)
• High positive cellIndOffNeigh of candidate promotes A3 event triggers already at small Δ for
this candidate (even Δ<0). Conversely, ...
• High positive cellIndOffServ of server promotes A3 event triggers first at large Δ for any
candidate. Conversely, ...
• High positive offsetFreqInter of carrier different from serving promotes A3 event triggers
already at small Δ (even Δ<0) for any candidate on this carrier. Conversely, ...
• High positive offsetFreqIntra of serving carrier promotes A3 event triggers first at large Δ for
any candidate on any carrier different from serving. Conversely, ...
For internal use
• A5 event entry condition (impact on leaving condition is analogous):
Measurement candidate  CellIndOff Neighcandidate  OffsetFreq(???)candidate  hysThreshold 3(...)  Threshold 3a(...)
and
Measurement server  hysTheshold 3(...)  Threshold 3(...)
• (???)=Intra if candidate on same carrier as server (same MeasObjectEUTRA)

– Otherwise, (???)=Inter (different MeasObjectEUTRA)
• (...) is determined by
– carrier of candidate (same/different MeasObjectEUTRA than server)
– TriggerQuantity in ReportConfig IE
• In RL30 Measurement is determined by TriggerQuantity in ReportConfigEUTRA IE

– TriggerQuantity=RSRQ is possible only for different MeasObjectEUTRA than server
– TriggerQuantity=RSRP always for same MeasObjectEUTRA as server
• A5 report is triggered upon A5 event entry condition is satisfied consecutively during

a5TimeToTrigger(...) time
– (...) is determined by carrier of candidate (same/different MeasObjectEUTRA than server) and
TriggerQuantity in ReportConfigEUTRA IE
For internal use
Measurement assessment
period (at UE)
RSRP/Q server
Δ1 > hysThreshold3(...) – cellIndOffNeigh -

offsetFreq(???)
Threshold3a(...)
Threshold3(...)
Δ2 < -hysThreshold3(...)
RSRP/Q candidate
Trigger of A5 event
a5TimeToTrigger(...) measurement report (at UE)
• High positive cellIndOffNeigh of candidate promotes A5 event triggers already at small Δ1

(even Δ1<0) for this candidate. Conversely, ...
• High positive offsetFreqInter or offsetFreqIntra, depending whether candidate carrier different
or same as serving, both promote A5 event triggers already at small Δ1 (even Δ1<0) for any
candidate on corresponding carrier. Conversely, ...
• No impact of LTE971 on server condition (no occurrence of cellIndOffServ/Neigh and
offsetFreqInter/Intra)
For internal use
LTE971 Embedding in intra-LTE meas. config.
carrierFreq eNB data base
Config. <> serving
input carrier No
(freqEutra) LNCEL
• offsetFreqIntra
Single meas. config. in Yes • cellIndOffServ

MeasConfig IE
LNREL
• MeasObjectEUTRA LNREL
• cellIndOffNeigh
• carrierFreq LNREL
• cellIndOffNeigh
• offsetFreq • cellIndOffNeigh
• (...)
• cellsToAddModList LNHOIF
• physCellId |
LNHOIF
• offsetFreqInter
cellIndividualOffset
LNHOIF
• offsetFreqInter
Read carrier-specific
• (...) • offsetFreqInter
MOC
• (...)
• ReportConfigEUTRA (...)
• (...)
• QuantityConfigEUTRA
• (...)
For internal use
Config. <> serving
input carrier No
(freqEutra) LNCEL
• offsetFreqIntra
Single meas. config. in • cellIndOffServ

Read
MeasConfig IE
neighbor LNREL
• MeasObjectEUTRA relations LNREL
• cellIndOffNeigh
• carrierFreq MOCs of LNREL
• cellIndOffNeigh
• offsetFreq server • cellIndOffNeigh
• (...) carrier
• physCellId |
LNHOIF
• offsetFreqInter
LNHOIF
• offsetFreqInter
• (...)
• (...)
• (...)
For internal use
Config. <> serving
input carrier
(freqEutra) LNCEL
• offsetFreqIntra
Single meas. config. in Yes Read carrier- • cellIndOffServ

MeasConfig IE specific neighbor
relations MOCs LNREL
• MeasObjectEUTRA LNREL
• cellIndOffNeigh
• carrierFreq LNREL
• cellIndOffNeigh
• offsetFreq • cellIndOffNeigh
• (...)
• physCellId |
LNHOIF
• offsetFreqInter
LNHOIF
• offsetFreqInter
• (...)
• (...)
• (...)
For internal use
Table of Contents
• Introduction
• Feature Details
For internal use
LTE971 Impact on Dimensioning
Client features:
Tool feature:
E.g. SON automation
LTE971
• Radio & access Itfs: LTE971 itself does not have

any impact on radio interface and access
dimensioning
• Radio & access Itfs: Effect of (re-) configuration
of LTE971 is up to the client feature and can
have dimensioning impact
– Client feature LTE533 Mobility Robustness
impacts slightly X2 interface load
– Client feature LTE1140 Intra-frequency Load
Balancing (RL40) has to deal with RAC and radio
interface constraints
• Itf-N to NetAct: Configuration actions of LTE971 generate additional traffic
For internal use

Table of Contents
• Introduction
• Feature Details
For internal use
LTE971 CCPM / PDDB excerpt
Short Range / Default Parameter
Description Remark
Name Step-size Value scope
offsetFr Offset value applicable dB-6 – dB6, dB0 own cell The value in dB.
eqIntra to EUTRA serving step 1 (LNCEL) Value dB-24
(O) carrier frequency. dB-24 – dB-8, corresponds to -24
step 2 dB, dB-22
corresponds to -22
dB8 – dB24, dB and so on.
step 2
offsetFr Offset value applicable --||-- --||-- IF carrier/object --||--
eqInter to EUTRA neighbor relation
(O) carrier frequencies. (LNHOIF)
cellIndO Cell-individual offset of --||-- --||-- own cell Only if parameter is
ffServ serving cell for insertion (LNCEL) different from dB0
(O) into the cell list of eNB considers it for
corresponding meas. configuration.
MeasObjectEUTRA
cellIndO Cell-individual offset of --||-- --||-- cell neighbor Only parameters
ffNeigh neighbor cells for relation different from dB0 are
(O) insertion into the cell list (LNREL) considered by eNB
of corresponding for meas.
MeasObject EUTRA configuration up to a
limit of 32 cell
neighbor relations per
carrier frequency.
O = operator specific
For internal use
LTE971 Note on application
• Once the LTE971 parameters are (re-) configured in eNB data base, the
connection/UE measurements can be changed accordingly within RRC
Measurement Configuration procedure
– MeasConfig IE sent to UE
• Trigger to send to UE the changed RRC Measurement Configuration is up to the

client feature or up to the system
• By default, RRC Measurement Configuration is triggered only for new UE

contexts, i.e.
– Initial UE contexts (setup via RRC Connection Request procedure)
– Contexts from incoming HO (setup via RRC Connection Reconfiguration Complete
procedure or RRC Connection Re-establishment procedure to HO target cell)
• The RL30 client feature of LTE971 works with LTE533@RL30

default RRC Measurement Configuration trigger
• The RL40 client feature is likely to work with own LTE1140@RL40

trigger
For internal use
Table of Contents
• Introduction
• Feature Details
For internal use
LTE533/LTE971 Demo
Development:
Aleksandra Klyszcz
Anna Laurowska
Przemyslaw Gorszkowski
Marcin Malczewski
Jacek Tomasiak
Krzysztof Pluta
Krzysztof Kubiak (PO)
For internal use

Table of Contents
• Introduction
• Feature Details
For internal use
LTE971 Monitoring
• LTE971 is not on/off controllable via feature activation flag at eNB

– Client features of LTE971 can be on/off controllable (via NetAct license and/or
feature activation flag at eNB)
• No PM counters and KPIs are associated with LTE971

– PM counters and KPIs are to be associated with client features of LTE971
For internal use

Thank you
Nokia Siemens Networks
Network Engineering LTE&Access

NWS LTE RA E2E SA NE
Mobile: + 48 782 973 413

Marcin Wiczanowski e-mail: marcin.wiczanowski@nsn.com
For internal use

Backup
For internal use

LTE971 More on LNREL MOC
• MOC LNREL collects properties of neighbor relation to particular neighbor cell
• Intended to be linked to MOC LNADJL which collects properties of neighbor cell

itself
• However, live cycle of LNREL up to some degree independent of LNADJL

– corresponding LNADJL may not exist
– LNADJL without LNREL may exist
– LNREL not deleted automatically when linked LNADJL deleted
• Can be created
– either automatically by LTE782 ANR
– or manually via plan file
• Maximally 194 LNRELs per LNCEL can be set up
For internal use


LTE971

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

LTE971

Hochgeladen von

Copyright:

Verfügbare Formate

For internal use only!

Network Engineering Information

Feature LTE971: Intra-LTE Mobility Offsets

For internal use

For internal use

– Frequecy-specific offsets 3gpp gen. / 36.331 sec. 5.5 PDDB / CCPM

▪ Offset of carrier frequency of offsetFreq / Ofs offsetFreqIntra

– Note: Carrier in this document = EUTRA measurement object =

• Offsets introduced by LTE971 can be used by client

• RL30/25TD client feature of LTE971 is LTE533 Mobility Robustness

For internal use

Measurement server  cellIndOff Serv server  offsetFreqIntra server  a3Offset (...) 

• (???)=Intra if candidate on same carrier as server (same MeasObjectEUTRA)

• In RL30 Measurement is determined by TriggerQuantity in ReportConfigEUTRA IE

• A3 report is triggered upon A3 event entry condition is satisfied consecutively

Δ > cellIndOffServ - cellIndOffNeigh +

Measurement candidate  CellIndOff Neighcandidate  OffsetFreq(???)candidate  hysThreshold 3(...)  Threshold 3a(...)

• (???)=Intra if candidate on same carrier as server (same MeasObjectEUTRA)

• In RL30 Measurement is determined by TriggerQuantity in ReportConfigEUTRA IE

• A5 report is triggered upon A5 event entry condition is satisfied consecutively during

Δ1 > hysThreshold3(...) – cellIndOffNeigh -

• High positive cellIndOffNeigh of candidate promotes A5 event triggers already at small Δ1

Single meas. config. in Yes • cellIndOffServ

Single meas. config. in • cellIndOffServ

Single meas. config. in Yes Read carrier- • cellIndOffServ

• Radio & access Itfs: LTE971 itself does not have

• Itf-N to NetAct: Configuration actions of LTE971 generate additional traffic

For internal use

• Trigger to send to UE the changed RRC Measurement Configuration is up to the

• By default, RRC Measurement Configuration is triggered only for new UE

• The RL30 client feature of LTE971 works with LTE533@RL30

• The RL40 client feature is likely to work with own LTE1140@RL40

For internal use

• LTE971 is not on/off controllable via feature activation flag at eNB

• No PM counters and KPIs are associated with LTE971

For internal use

Nokia Siemens Networks

Network Engineering LTE&Access

Mobile: + 48 782 973 413

For internal use

For internal use

• MOC LNREL collects properties of neighbor relation to particular neighbor cell

• Intended to be linked to MOC LNADJL which collects properties of neighbor cell

• However, live cycle of LNREL up to some degree independent of LNADJL

• Maximally 194 LNRELs per LNCEL can be set up

For internal use

Das könnte Ihnen auch gefallen