2

Baseband Radio Nod Node - Oper peratio ation n and and Configuration Radio Network

Objectives of Chapter 3 After this chapter the participants will be able to: 3

Expl Explai ain n the the Radi Radio o Net Netwo work rk in Base Baseba band nd 5216 5216

3.1 Explain the concept of cell and its relation relation to sector and antenna antenna system in RBS. 3.2 Introduce the new radio products in Ericsson Ericsso n radio system 3.3 Recognize the Managed Objects related to radio network configuration 3.4 Relate the Managed Objects Objects and figure out the changes according according to Ericsson Common Information Model (ECIM) 3.5 Edit and implement implement the files for on-site usage that would would create create the Radio network (Cells, (Cells, Cell relations) as applicable in an eNodeB, NodeB NodeB or BTS.

Logical Components of an LTE RBS  Antenna Unit Group X X X

X

X

X

X

X

X

TMA

TMA

 Antenna Unit Group

OSS-RC

RBS Synchronization

Mul

MBMS-GW M1

Sector  Cell

Sector 

Cell

Remote Radio

Cell

Cell

Cell

Cell

Evolved Packet Core S-GW

Radio

S-GW S-GW

S1-UP

Baseband MME

CPRI Connection

MME

Support System

Neighbor eNodeB Neighbor eNodeB

X2

S1-CP / M3

Neighbor IRAT RAN Network

MME

Neighbor IRAT Core Network

Scheduling, QoS, LA, PC Overview QCIs

ARPs

QoS Parameters

QoS Framework

Scheduling Power Control Link  Adaptation Resource assignments UL/DL

Baseband QCI - QoS Class Class Identifie Identifier  r   ARP –  ARP – Allocation and Retention Retention Priority

Channel feedback

TPC commands

High capacity radio system site MACRO

Baseband T Baseband Baseband R Fronthaul Backhaul

MICRO

PICO

Ericsson Radio System New HW

MINI-LINK 6352 Fronthaul 6392 Power 6610 MINI-LINK

Baseband

6363

6630

Power 6306 Enclosure 6306 MINI-LINK Enclosure 6110 6692

MINI-LINK 6691 MINI-LINK 6351

Radio 2203

Radio 2217

Baseband 5216

Radio 0208

Baseband 5212

Power 6302

Baseband R503

Router 6274

Router 6672

Router 6675

Radio Radio 2217 B1 Upper case Lower case Space Tx branches Rx branches Random Space 3GPP band number 

Radio 2217 used as example

Micro Radio

50%

Smaller & lighter

› New modular micro radio system › Macro feature parity, coordination › 4 liter and 5 kg installed

RBS 6402 Multiband concept 3GPP Module 1 3GPP Module 2 WiFi

2 RF modules for 3GPP Each module: 2-4 Bands One band per module selectable by SW out of 2-4 bands

 A few products per market supports all band combinations

Baseband R503 • Increased connectivity for new & existing radio units in large radio system configurations

• CPRI multiplexing and de-multiplexing • 16x SFP+ ports • Pluggable optical transceivers • Direct attach cables (electrical)

• Flexible • • • •

FPGA and ARM-based Upgradable Manageable Many possible locations in cabinet or at site

R503 supporting 3 LTE bands (Example) Electrical CPRI

DUS/ Baseband

LTE 2600 3x15MHz MIMO

Electrical CPRI

LTE (RBB22_1C) Optical CPRI

2x 10G CPRI Electrical or Optical CPRI

DUS or  Baseband

RUS01 B7

LTE (RBB22_1B)

RRUS12 B3

Optical CPRI

LTE (RBB22_1B)

RRUS11 B20

B   a  s   e  b   a n  d  R  5   0   3 

LTE 2600 3x15MHz MIMO LTE (RBB22_1C) Optical CPRI

LTE 1800 3x10MHz MIMO

RUS01 B7

LTE (RBB22_1B)

LTE 1800 3x10MHz MIMO

RRUS12 B3

LTE 800 3x10MHz MIMO

LTE 210 MHz Total Bandwidth

Optical CPRI

LTE (RBB22_1B)

RRUS11 B20

LTE third band Baseband R503 enabler to connect

LTE 800 3x10MHz MIMO

13-18 Cell – with Baseband R503 R/RU

B  a  s  e  b   a n  d   5  2  1   6 

9,8 G

B  a  s  e  b   a n  d  R  5   0   3 

R/RU R/RU

2.5G

R/RU R/RU

9,8 G 2.5G

R/RU

R/RU

2.5G

R/RU R/RU R/RU R/RU

R/RU

Example of Baseband R503 used as a MUX

B B  5  2  1   6 

B B R  5   0   3  B B R  5   0   3  B B R  5   0   3 

Up to 3 Baseband R503 connected to the same Baseband 5216

Baseband HW and SW Mixed Mode Baseband OSS RC

One IP, One Managed Element

Baseband 5216 LTE TN

WCDMA Common

•

TN = Transport •

•

Independent of radio standard

Common = Node handling •

Radio config (sectors and CPRI), Security, Sync, APC, Node O&M

Same Transport and Node handling as Single standard

ECIM Structure Managed Element

NodeSupport

ENodeBFunction

Transport

EUtranCellFDD

VlanPort

SectorCarrier Router

SectorEquipmentFunction

InterfaceIPv4

NodeBFunction ENodeBLocalCellGroup SectorEquipmentFunction

NodeBLocalCell

Router

InterfaceIPv4 NodeBSectorCarrier VlanPort

Radio Network Managed Object Model Cell Setup ManagedElement EnodeBFunction

Rcs

SecurityHandling  

EUtraNetwork

EUtranFrequency

EUtranCellFDD or  EUtranCellTDD

Paging

ExternalENodeB Function

NodeSupport

SectorCarrier

SectorEquipmentFunction

UeMeasControl

ExternalEUtranCellFDD or  ExternalEUtranCellTDD

Created as a part of the ANR function  Auto-created with default values

EUtranFreqRelation

EUtranCellRelation

MOs Related to IRAT Interworking EUtranCellFdd or  EUtranCellTdd

UtraNetwork

Cdma2000Network

Utran Frequency

Utran FreqRelation

External UtranCellFdd

Utran CellRelation

GeraNetwork

Geran FreqGroup Relation

Geran Frequency GeranCell Relation

Cdma2000 FreqBand

Cdma2000 Freq ExternalCdma 2000Cell

Geran FreqGroup

Cdma2000 FreqBand Relation

Cdma2000 FreqRelation Cdma2000 CellRelation

ExternalGeran Cell

EUTranCellFDD or EUTranCellTDD ManagedElement EnodeBFunction

Rcs

SecurityHandling  

EUtraNetwork

Paging

EUtranCellFDD or  EUtranCellTDD

NodeSupport

SectorCarrier  

Used to configure e.g. - Cell Identities - Bandwidth and Radio Channels - Maximum RF Output Power 

EUtranCellFDD or  EUtranCellTDD

- Cell User Capacity and QoS - Cell Availability - Scheduling and Interface Management - Cell Handover  - ....

SectorEquipmentFunction

Paging ManagedElement

EnodeBFunction

Rcs

SecurityHandling  

EUtraNetwork

Paging

EUtranCellFDD or  EUtranCellTDD

NodeSupport

SectorCarrier

Paging Used to configure e.g. - Default paging cycle - Delay and bandwidth used by paging functionality

This MO is auto-created, with default values, by the system

SectorEquipmentFunction

Sector Carrier  ManagedElement EnodeBFunction

Rcs

SecurityHandling  

EUtraNetwork

Paging

EUtranCellFDD or  EUtranCellTDD

SectorCarrier  Used to configure e.g. - NoOfRxAntennas - NoOfTxAntennas - partOfSectorPower 

NodeSupport

SectorCarrier

SectorEquipmentFunction

Sector Equipment ManagedElement EnodeBFunction

Rcs

SecurityHandling  

EUtraNetwork

Paging

EUtranCellFDD or  EUtranCellTDD

NodeSupport

SectorCarrier

SectorEquipmentFunction

SectorEquipmentFunction Has parameters like - Administrative state - Operational state (readOnly) - Sector maximum output power  - Sector frequency band (readOnly) - Reference to the rfBranch

This MO is created as a part of the Site Equipment Configuration

Security Handling ManagedElement EnodeBFunction

Rcs

SecurityHandlingg  

EUtraNetwork

Paging

NodeSupport

EUtranCellFDD or  EUtranCellTDD

SectorCarrier

SecurityHandling Used to configure e.g. - Ciphering algorithms - COUNT-C supervision

This MO is auto-created, with default values, by the system

SectorEquipmentFunction

UE Measurement Control ManagedElement EnodeBFunction

Rcs

SecurityHandling  

EUtraNetwork

Paging

EUtranCellFDD or  EUtranCellTDD

NodeSupport

SectorCarrier

UeMeasControl

UeMeasControl Used to configure e.g. - Cell quality threshold value - Best cell decision configuration - Bad coverage measurement configuration - UE report filtering

This MO is auto-created, with default values, by the system

SectorEquipmentFunction

Measurement and Report Related MOs ReportConfigEUtra InterFreqLb

ReportConfigEUtra IFBestCell

ManagedElement EnodeBFunction

ReportConfigEUtra BadCovPrim

ReportConfigA1Prim EUtranCellFDD or  EUtranCellTDD

ReportConfigEUtra BadCovSec

ReportConfigA1Sec UeMeasControl ReportConfigA5Anr 

ReportConfigA4

ReportConfigSearch

PmUeMeasControl

ReportConfigEUtra IntraFreqPm

ReportConfigB2 Cdma2000 ReportConfigCsfb Cdma2000

ReportConfigEUtra BestCell

 

ReportConfigA5

ReportConfigB2 Geran

ReportConfig CellA1A2

ReportConfig CellA6

ReportConfigB1 Geran

ReportConfig InterRatLb

ReportConfig CellA4

ReportConfigA5 Softlock

ReportConfigB2 Cdma2000 1XRtt

ReportConfig CsfbGeran

ReportConfigEUtra BestCellAnr 

ReportConfigB2Utra

ReportConfigB1Utra

ReportConfig EUtraInterFreqMbms

and ReportConfigA5DI Comp

ReportConfig CsfbUtra

ReportConfig Search

Connected Mode Mobility UE measures on serving cell and scans all neighboring intra-LTE cells (504 PCIs) -> No UE neighbor list for intra-LTE -> Detected ”good” cells are reported -> IRAT cell lists are used

HO?

eNB makes HO decision based on UE measurements

Best Cell Evaluation

Event?  Mn   Hysteresis A3   Ms  a3offset 

Serving cell 

Neighboring cell 

Measurement Configuration in UE RRC CONNECTION RECONFIGURATION (Measurement configuration) RRC CONNECTION RECONFIGURATION COMPLETE

•

Measurement objects (measObjectToAddModifyList, measObjectToRemoveList)

•

•

Reporting configurations (reportConfigToAddModifyList, reportConfigToRemoveList)

• • •

Reporting criterion: periodical or event-triggered reporting Reporting format: quantities (e.g. number of cells to report)

Measurement identity (measIdToAddModifyList, measIdToRemoveList)

• •

The objects which the UE shall perform the measurement on e.g. a carrier frequency or a list of neighbouring cell offsets or IRAT neighbouring cells.

List of measurement identities, each identity links one measurement object with one reporting configuration. This is the reference number in the measurement report.

Quantity configurations (quantityConfig)

• • •

The quantity the UE shall measure as well as the associated firing parameters. E.g. RSRP (Reference Signal Received Power) , RSRQ (Reference Signal Received Quality). One quantity for intra freq, one for inter and one for each RAT type

Intra LTE ANR Overview Cell A Type = LTE Phy-CID= 5 Global-CID =19

Cell A Type = LTE Phy-CID= 3 Global-CID =17

6) Look up a TN Layer address of the target eNB

RS PSS SSS E-CGI PCI

Reference Signal Primary Synchronization Signal Secondary Synchronization Signal E-UTRAN Cell Global Identity Physical Cell Id

7) Set up X2

 Automatic Neighbor Relation related MOs ManagedElement

EnodeBFunction

Used to configure e.g. - When to add and release N Cell (common to all types of  ANR)

An rF un ct ion Ut ra n

 Auto-created with default values

X2 setup related parameters : - Blacklisted eNodeBs Contains attributes related to X2 setup

AnrFunction

An rFu nct io nE Ut ran

AnrFunctionGeran

Parameters and constraints for LTE Automated Neighbor Relations (ANR) functions. e.g. - If Intra- and/or Inter- Frequency ANR activated - Thresholds (RSRP and RSRQ) for ANR consideration - Number of UEs that initiate the ANR

QoS Basic Framework QCI

Prio

LCG

DSCP

1

2

2

46

2

4

2

36

:

:

:

:

:

:

:

:

QoS parameters

9

9

3

12

QCI Table

0, 10-255

10

3

0

Standardized QCIs

Core Network  Q  C  I  

OSS-RC

QoS: Quality of Service QCI: QoS Class Identifier  DSCP: DiffServ Code Point LCG: Logical Channel Group

Scheduler  LCGs

QCI table

QoS translation

•QoS configuration

QoS Handling

DL Packet Forwarding (X2)

UL (S1) Transport Network

DL/UL (Radio interface) Radio Network

MOs related to QoS Configuration QCI

Prio

LCG

DSCP

1

2

1

46

2

4

1

36

:

:

:

:

:

:

:

:

9

9

1

14

0,10-255

10

1

0

Default config ManagedElement

EnodeBFunction 1..1

One per QCI entry (QCI 0 and 10-256 are called ”default” and have lower prio than 19) The attribute dscp is changed in order to map the QCI value to a new DSCP value.

EUtranCellFDD or  EUtranCellTDD

QciTable

10..10

4..4

QciProfilePredefined

LogicalChannelGroup

0..9 QciProfileOperatorPredefined

Uplink traffic separation is enabled with Logical Channel Groups.

These MOs are auto-created, with default values, by the system. May need to be changed for a different QoS handling.

MOM and WCDMA dependencies

MOM and Abis dependencies

GRAT MOM fragment GSM branch in Baseband Radio Node MOM

 Abis O&M BTS Logical Model G31

1

Managed Element

1

BtsFunction 0..(48)

0..(48)

GsmSector 

(Sector) TG

TG – Tranceiver Group SCF – Sector Central Function TF – Timing Function (GSM specific)  AT – Abis Transport TRXC – Tranceiver Controller  TS – Time Slot TX – Transmitter (Downlink Carrier Branch) RX – Receiver (Uplink Carrier Branch)

SCF

Legend: Common SW MO

0..1

TF  AT

AbisIp 0..12

0..12

Trx

TRXC

TX

 Abis MO in BSC  Abis MO in BSC and BTS

8

TS

GRAT MO

RX

› Main BTS parameters must be defined in MOM from OSS

GRAT MOM Configuration BtsFunction This is the root MO of the GSM MOM fragment. The BtsFunction MO represents the GSM functionality in the RBS. The functionality represented by BtsFunction MO can be significantly larger than what is modelled as one TG in the BSC.

BtsFunction attributes btsFunctionId

Description

This attribute respresents the key of the BtsFunction MO. It is used to identify a unique BtsFunction MO instance. Currently only one BtsFunction MO instance is supported per node.

Example

GRAT MOM Configuration GsmSector   A GsmSector is a geographical area with the RBS functionality used as one GSM cell. GsmSectors can be used in more than one GSM cell depending on BSC configuration. Usage within a GSM cell can be less than the entire GSM cell. The number of GsmSectors in t he node varies with deployment scenario. More than one GsmSector per node is common. The GsmSector groups a number of TRXs each represented by a Trx MO. Each TRX supports one GSM c arrier. Transport related data is configured in the AbisIp MO.

GsmSector attributes GsmSectorId

Description

This attribute respresents the key of the GsmSector MO. It is used to identify a unique GsmSector MO instance. This attribute is sent to the BSC for Sector TG to GsmSector correlation purposes.

Example

GsmSector1

GRAT MOM Configuration –Trx 1 (3) This MO represents a GSM TRX and corresponding functionality for a GSM carrier on Air interface. GSM uses narrowband (< 200 kHz bandwidth) channels in the air interface (one downlink and one uplink) handled by one TRX. A TRX handles normally 1 downlink carrier (TX) and 2 uplink carriers (RX) over a wide bandwidth by using frequency hopping. A Trx MO is connected to one sectorEquipmentFunction MO which represents the radio and antenna equipment.

Trx attributes

Description

arfcnMax { 0..1023 }

Specifies the number corresponding to the highest frequency for a GSM carrier that the Trx may use. Each frequency band have separate formulas for downlink (TX) and uplink (RX) to convert between ARFCN and the frequency. When Synth Hopping is activated, the exact frequency to be used in is ordered by BSC in runtime. By setting arfcnMin and arfcnMax to the Operator spectrum available for GSM, frequency re-planning can be made via the BSC wit hout affecting these parameters. …

arfcnMin { 0..1023 }

Specifies the number corresponding to the lowest frequency for a GSM carrier that the Trx may use.

Example

GRAT MOM Configuration –Trx 2 (3) Trx attributes

 

frequencyBand { 0, 2, 3, 5, 8 }

Description

Used for configuring the TRX frequency band. The frequency bands are according to 3GPP TS 37.104, Operating bands and Band Categories, (Band 0 is Ericsson defined). Possible Values: 0 = GSM 900 MHz (GSM) 2 = GSM 1900 MHz (PCS 1900) 3 = GSM 1800 MHz (DCS 1800) 5 = GSM 850 MHz (GSM 850) 8 = GSM 900 MHz Extended (E-GSM) Dependencies: Must match arfcnMin and arfcnMax.

noOfRxAntennas = 2 { 2 }

Specifies the number of RX antennas used by the TRX.

noOfTxAntennas = 1 { 1 }

Specifies the number of TX antennas used by the TRX.

sectorEquipmentFunctionRef 

A reference to SectorEquipmentFunction MO (LDN) instance. This MO represents the radio and antenna resources the TRX shall use.

GRAT MOM Configuration –Trx 3 (3) Trx attributes trxId

 

Description

This attribute respresents the key of the Trx MO, used to identify a unique Trx MO instance.

trxIndex { 0..126 }

This attribute is used both as OML L3 and OML/RSL/TFP/PGSL L2 address (TEI). The value of this attribute is set to trxId if it is a unique number between 0..126, otherwise the lowest unused number in range 0..126 is chosen.

rfBranchRxRef 

A list of references to MOs RfBranch and CcBranch instances, LDNs. These MOs represent the RF branches the TRX shall use for RX. If no reference is specified carrier allocation is based on the RF Branch MOM list (default behavior).

rfBranchTx

A reference to MO RfBranch instance, LDN. This MO represents the RF branch (MCPA) the TRX uses for TX. Identifies the RF branch (MCPA) that the PM counters are valid for.

rfBranchTxRef 

A reference to MO RfBranch instance, LDN. These MOs represents the RF branches (MCPA) the TRX shall use for TX. This can be used to group TRXs to a MCPA. If no reference is specified carrier allocation is based on the RF Branch MOM list (default behavior).

GRAT will use the returned attribute rfBranchId (add nodeUniqueRfPortId) to understand which carrier branches that are allocated to the same RfPort (MCPA). 1 RfBranch can be connected to one and only one RfPort

MOM View GsmSector 

Trx noOfTxAntennas=1 noOfRxAntennas=2

Trx

RfBranch

Sector Equipment Function

noOfTxAntennas=1 noOfRxAntennas=2

RfBranch TmaSubUnit

Trx RfBranch noOfTxAntennas=1 noOfRxAntennas=2

RfBranch RfBranch

TmaSubUnit

RfBranch RfPort=A

TmaSubUnit

RfPort=B

Baseband Radio Node MOM Summary Managed Element

1

Transport

Common Functions

GSM Specific

WCDMA Specific

LTE Specific

Router 

reference relation

InterfaceIPv4

0..1

AddressIPv4

Node Support

NodeBFunction

0..1

0..1

BtsFunction

NodeBLocal CellGroup

Iub

1

ENodeBFunction

Equipment 0..

RfBranch

CcBranch

0..12

0..1

AbisIp

NodeBLocalCell

AntennaUnit Group

Gsm Sector 

Trx

AdmState OperState, availabilityStatus bandwidthDL/UL (MHz) uarfcnDL/UL (UTRA ARFCN) numOfTx/RxAntennas partOfSectorPower (%) Sector Reference

SectorEquipmentF unction

AdmState OperState, availabilityStatus fqBand (E-UTRA band (1-32)) confOutputPower (W, configured) sectorPower (W, available power)

EUtranCell

AdmState OperState, availabilityStatus dlChannelBandwidth (kHz) earfcnDL/UL (E-UTRA ARFCN) noOfTx/RxAntennas partOfSectorPower (%)