Realistic Scenarios for System-Level Simulations of LTE Networks - - PowerPoint PPT Presentation

▶
realistic scenarios for
SMART_READER_LITE
LIVE PREVIEW

Realistic Scenarios for System-Level Simulations of LTE Networks - - PowerPoint PPT Presentation

Nov 12, 2023 49 likes •214 views

FP7 ICT-SOCRATES Realistic Scenarios for System-Level Simulations of LTE Networks with SON Features 7 th COST 2100 Committee Meeting February 16 th - 18 th 2009 Braunschweig, Germany Authors: Andreas Eisenbltter, atesio, Berlin Thomas

slide-1
SLIDE 1

FP7 ICT-SOCRATES

Realistic Scenarios for System-Level Simulations of LTE Networks with SON Features

7th COST 2100 Committee Meeting February 16th - 18th 2009 Braunschweig, Germany

Authors: Andreas Eisenblätter, atesio, Berlin Thomas Jansen, TU Braunschweig, Braunschweig Thomas Kürner, TU Braunschweig, Braunschweig Ulrich Türke, atesio, Berlin John Turk, Vodafone, Newbury

slide-2
SLIDE 2

WWW.FP7-SOCRATES.EU

  • 1. The SOCRATES Project
  • 2. Self-Organising Networks (SON)
  • 3. Self-Organisation in the interference coordination use case (ICO)
  • 4. Simulation requirements of the SOCRATES use cases
  • 5. Impact on simulation scenarios and data format
  • 6. SOCRATES simulation scenarios
  • 7. Conclusions

Outline

2/15

slide-3
SLIDE 3

WWW.FP7-SOCRATES.EU

  • Increase the network performance

– quality of service, system capacity,

throughput, …

  • Reduce the effort of human intervention

– automate optimisation processes – fast adaptation to network conditions

  • Reduce operating costs

– energy consumption – operational expenditure (OPEX)

  • Continuously collecting measurements

– UE measurements – Cell measurements – Information exchange between eNodeBs

Objectives of the SOCRATES-Project

Measurements (Gathering and processing) Self- Optimisation Self- Healing Self- Configuration Setting parameters Continuous loop Triggered by incidental events 3/15

slide-4
SLIDE 4

WWW.FP7-SOCRATES.EU

  • SOCRATES investigated 24 use cases

– Use cases address situations where self-organisation may be of benefit – Divided into 3 categories [1]

SON features considered for LTE

  • Self-Optimisation

– Interference

coordination

– Handover

  • ptimisation
  • Self-Configuration

– Automatic generation of

default parameters

– Intelligently selecting site

locations

  • Self-Healing

– Cell outage

management

– Coverage hole

management

[1] Reference: TD (08)616, “Use Cases, Requirements and Assessment Criteria for Future Self-Organising Radio Access Networks”, COST2100, Lille, France, October 2008

  • No generally accepted definition of what is considered to be SON
  • From 3GPP TS 32.500-800

Self-Organising Networks (SON) are introduced to reduce the operating expenditure (OPEX) associated with the management of a large number of nodes from more than one vendor SON functions can help to automate network planning, configuration and

  • ptimisation processes

4/15

slide-5
SLIDE 5

WWW.FP7-SOCRATES.EU

  • Triggers

– Low quality of service (QoS) – High ratio of blocked and dropped calls

  • Goal

– Ensure good cell edge performance – Minimise the impact of inter-cell interference – Maintain a fair balance between cell-edge

users performance and performance of the users closer to the cell-centre

– Consider QoS requirements regarding demanded type of service

  • Important network conditions

– User’s location (cell-edge, cell-centre) – User mobility – Type of service – …

Interference coordination as SON use case

4 2 6 Cell-Centre Cell-Edge 1 5 3 7

5/15

slide-6
SLIDE 6

WWW.FP7-SOCRATES.EU

  • We follow two different approaches to develop SON algorithms

– SON algorithm on top of soft frequency reuse scheme (Figure below) – Individual assignment of physical

resource blocks to the users depending on the actual interference situation

Interference coordination as SON use case

4 2 6 Cell-Centre Cell-Edge Cell-Edge Cell-Edge 1 5 3 7 Pedg (Ptot - Pedg) / 2 Number of PRB’s Transmit Power Frequency scheme Cell 1 Nedg (Ntot - Nedg) / 2

  • Main control parameters

– Physical resource block (PRB)

allocated per UE (DL & UL)

– PRB tx power per UE (DL & UL) – Reference symbol power – Antenna tilt – Beamforming

6/15

slide-7
SLIDE 7

WWW.FP7-SOCRATES.EU

  • Analytic evaluation

– Analyse performance of the algorithms analytically

  • Monte-Carlo Simulations

– Variation of network condition snapshots (not over time) – Reach statistical relevance

  • Short-term Dynamic Simulations

– Small short-term variations in the network condition – Analyse the algorithm performance to short-term changes

  • Dynamic Simulations

– Analyse the adaptability of the algorithms to realistic network condition

fluctuations over time

Radio Network Simulations

7/15

slide-8
SLIDE 8

WWW.FP7-SOCRATES.EU

Interference coordination: Simulations requirements

Simulation requirement Value Algorithm location Centralised or Distributed Number of considered cells 2 – 10 BTS Types Macro, Micro, Femto Level of simulation System-Level (Static and Dynamic) Information exchange Between neighbouring cells and SON functions (Handover optimisation, …) Time resolution ms Mobility Simple models Traffic Realistic models Network topologies Hexagonal and Realistic Exceptional events User concentration, High speed users, …

[2] Reference: SOCRATES Deliverable D2.3: “Assessment Criteria for Self-Organising Networks”, EU STREP SOCRATES (INFSO-ICT-216284), Version 1.0, July 2008

  • For the algorithm assessment a list of assessment criteria is defined [2]

8/15

slide-9
SLIDE 9

WWW.FP7-SOCRATES.EU

Simulation requirement Range Example use case (high requirement) Algorithm location Centralised, Distributed and/or Local Number of considered cells 1 – N * 100 cells Cell outage compensation BTS Types Macro, Micro, Femto SO of home eNodeB Level of simulation Static - Dynamic Load balancing Time resolution h - min - ms Admission control Mobility None - Full mobility Congestion control Traffic Simple - Realistic models Handover optimisation Network topologies Hexagonal / Realistic Interference coordination

Simulations requirements across all use cases

MORANS data format meets several requirements

9/15

slide-10
SLIDE 10

WWW.FP7-SOCRATES.EU

  • Control parameter changes during the simulations with high impact on

network condition

– Antenna tilts – Tx powers – Handover parameters

  • Drastic network condition changes by exceptional events

– System outage – High speed users (Train) – Traffic concentration (Football match, Exhibition, ...) – Home eNodeB may be switched off

  • Simulation scenarios and corresponding data formats need to cope with

these simulations requirements

SOCRATES Simulations requirements

10/15

slide-11
SLIDE 11

WWW.FP7-SOCRATES.EU

  • Developed in the MOMENTUM project
  • COST further developed MORANS
  • MORANS is a UMTS specific data

format

  • The format is generic and XML-based
  • Adjustments to LTE specifics and

SOCRATES simulations requirements mainly in highlighted areas

MORANS Data format

11/15

slide-12
SLIDE 12

WWW.FP7-SOCRATES.EU

  • Extended hardware requirements

– Home eNodeB – Relays / Repeater – Multi antenna arrays (MIMO, Beamforming) – Antennas from different network generations

mounted on one panel

Extensions to the MORANS data format

MME MME

1 2 3 4

eNodeB eNodeB eNodeB eNodeB S1 S1 S1 S1 X2 X2 X2

  • Multi-Layer data

– Needed for indoor scenarios /

  • utdoor-to-indoor / indoor-to-outdoor

– Separate propagation files for

different building levels

– Example use cases: Optimisation

  • f home eNodeB’s

Source: Google Earth 5.0

12/15

slide-13
SLIDE 13

WWW.FP7-SOCRATES.EU

  • Multi-Resolution data

– Desired to allow for different simulation accuracies – Example: Land-use class pixel-maps in different

resolutions

  • Network condition changes

– Scenario data is needed for the following cases – Cell outage – Coverage hole – Traffic concentration – High speed users – Switching home eNodeB on and off – Transform the network – Algorithms change network configuration (extended data needed) – Antenna configuration impacts signal propagation

Extensions to the MORANS data format

13/15

slide-14
SLIDE 14

WWW.FP7-SOCRATES.EU

  • Two settings defined for the project
  • 1. Berlin Area

– Size: 13 km * 13 km – Urban, Dense-Urban, Hot-Spot – Terrain height variation: ~ 20 m – Hundreds of cells

  • 2. Braunschweig Area

– Size: 40 km * 70 km – Dense-Urban, Urban, Sub-Urban – Terrain height variation: ~ 700 m

(Mountain Hartz)

– Hundreds of cells

SOCRATES simulation scenarios

Source: Google Earth 5.0

14/15

slide-15
SLIDE 15

WWW.FP7-SOCRATES.EU

  • The development of SON features entails various simulation requirements
  • Simulation scenarios need to provide

– Scenario data for changes over time – Network configuration – Network failure and repair – Demand patterns – Multi-Layer data – Multi-Resolution data

  • MORANS data format is an excellent starting point

– Adapt to LTE – Extended hardware requirements: MIMO, Beamforming, Home eNodeB – Higher network entities and interfaces: MME, S1 and X2

Conclusions

15/15

slide-16
SLIDE 16

Thank you very much for your attention

FP7 ICT-SOCRATES