Dual Baseband as one

Managed Element

Ericsson Internal | 2018-02-21

Content

— Dual Baseband as one ME, Overview

— Configurations
— Feature Support
— RAN Scalability

Ericsson Internal | 2018-02-21

Overview

Ericsson Internal | 2018-02-21

 Dual Baseband as one ME (Managed Element)
Overview
1/10GE S1 interconnect for
Backhaul and O&M traffic

Baseband

Baseband

20GE IDLe CPRI Fronthaul

OAM
disk
• Single O&M node, one O&M IP
access disk
One OAM access point to the ME. address
One Upgrade package per ME. •
IDLe Selected Configurations
One database per ME.
supported
Core Regular
Baseband Baseband
Ericsson Internal | 2018-02-21
Dual Baseband as one ME (Managed
Element )
— Dual Baseband as one ME supported in GWL18.Q4 and ENM 18.4 with Limited Availability, approved
Exemption Request required
— Part of VP Base Package for GSM, WCDMA and LTE
— Selected configurations verified and supported
— Configuration summary, details on following slides
— Multi standard GSM+LTE, WCDMA+LTE
— Single Standard LTE, LTE
— Single Standard WCDMA, WCDMA
— LTE feature limitations
— Elastic RAN the recommended solution for LTE RAN scalability

Ericsson Internal | 2018-02-21

Configurations

Ericsson Internal | 2018-02-21

Dual Baseband Configuration 1 (3)
Multistandard
— Baseband 6630 ME
CPRI
— Baseband 5216 support planned for 19.Q2 .
TN LTE
— 18 LTE cells + 3 NB-IOT cells (NB-IOT on Core . 12 cells LTE FDD + 3 cells NB-IOT, 24 GSM TRXes
only) GSM .
5212/5216
— Up to 24 LTE cells planned for 19.Q2 Core 6630

— 24 GSM TRXes IDLe

— 6 WCDMA cells
CPRI
— CPRI based Radio Units LTE
.
— Mixed Mode Radio via Shared CPRI . 6 cells LTE FDD, 6 cells WCDMA
WCDMA .
— One LTE eNodeB Regular 6630

— LTE legacy feature support limitations

— GSM and WCDMA feature parity

Ericsson Internal | 2018-02-21

Dual Baseband Configuration
Multistandard example
700-900MHz 1800-2100MHz 2600MHz
2T2R 4T4R 4T4R

Baseband 6630
Radio Radio Radio
Radio
2212 2242 4415
L + W (Regular) 2217

L + G (Core)
CPRI
L800 L900 + G900 + NB-IoT L1800 + U2100 L2600 FDD
2x20W 10MHz LTE 2x20W 10MHz L18 4x15W 30MHz 4x20W 20MHz
GSM 2-4 TRX U21 2x20W 10MHz
CPRI

Ericsson Internal | 2018-02-21

Dual Baseband Configuration 2(3)
LTE Single standard
— Baseband 6630 or Baseband 5216 (not a mix of them) ME
— Baseband 5212 and 6620 support planned for CPRI
TN .
19.Q2 LTE . 6 cells LTE TDD
— CPRI based Radio Units .
5212/5216
Core 5216

— LTE legacy feature support limitations IDLe

CPRI
— Mix of TDD, FDD and M-IOT planned for 19.Q2 .
LTE . 9 cells LTE TDD
.
Regular 5216

Ericsson Internal | 2018-02-21

Dual Baseband Configuration 3(3)
WCDMA Single Standard
— Baseband 6630 or Baseband 5216 (not a mix of them) ME
CPRI
— Baseband 6620 and 5212 planned to be supported in
TN .
19.Q2 WCDMA
. 18 cells WCDMA
— WCDMA feature parity .
5212/5216
Core 5216

IDLe
CPRI
.
WCDMA . 18 cells WCDMA
.
Regular 5216

Ericsson Internal | 2018-02-21

Feature Support

Ericsson Internal | 2018-02-21

LTE Feature Support, 18.Q4
Feature Parity with below exceptions
Features not supported Feature limitations
— Elastic RAN (candidate for 19.Q4) — Mixed Mode Radio between Baseband Units not
— Inter eNodeB Carrier Aggregation (X2 Based) supported
(candidate for 19.Q4) — NB-IOT supported on Core Baseband only
— eMBMS (planned to be supported on Regular Baseband in
— Shared RAN 19.Q2)
— LAA — GSM supported on Core Baseband only
— CBRS — UL Comp between Baseband Units not supported
— Mixed Mode Baseband R503 — Combined Cell between Baseband Units not
supported

Feature Parity plan based on market demand

Ericsson Internal | 2018-02-21
RAN Scalability

Ericsson Internal | 2018-02-21

Fully Scalable RAN architecture – Elastic RAN
ERAN network wide
- borderless tight coordination across entire network
- Each node can be co-ordinated with cells in 6 other
nodes in an E-RAN cluster
- L2 switching over fiber between basebands
ERAN within one physical site
- Connect two Basebands with an E5 cable
- Possiblity to run E-RAN and x2 coordination
features
- E-RAN with two nodes supported without L2
switch
ERAN is inherently Resilient
— restart domain no more than single BB

Ericsson Internal | 2018-02-21

 Elastic RAN Baseband Configuration
2 x Baseband ERAN Cluster = Two managed elements using IDLe link for tight
coordination. One Ethernet link for backhaul using in built router function

• Separate eNodeB - no inter node

dependency, providing scalability and
Backhaul CPRI Inter Baseband link robustness
(IDLe)
• All LTE Baseband configurations
Baseband 5216 00800, 01300, 01800, 03000
supported
RPM 777
IDL A-B 417/L Direct, local
Xcede - Xcede (2x10 Gbit/s 2 TX 2 RX)
• Combination of Inter eNodeB and E-
Baseband 6630
Baseband 6630
2x Ethernet / 00800, 01300, 01800*
RAN based Carrier Aggregation
supported

No additional HW required for D-RAN deployments

Ericsson Internal | 2018-02-21
 Dual Baseband as one Managed Element
Overview
1/10GE S1 interconnect for
Backhaul and O&M traffic

Baseband

Baseband

20GE IDLe CPRI Fronthaul

• Single O&M node
• Single Transport, terminated in
Core Baseband
OAM
disk disk
• Limited configurations
access
One OAM access point to the ME. supported
One Upgrade package per ME.
IDLe • Capacity does not fully scale
One database per ME.
Core Regular
with number of Basebands
Baseband Baseband • Core Baseband single point of
failure
Dual/Multiple Basebands in one node not preferred technical option
Ericsson Internal | 2018-02-21
Multiple Basebands @ physical site
Single vs Dual Baseband per logical node, Summary
Separate Basebands, Elastic RAN
TN Separate TN per node. Cascading via TN ports
between different basebands supported.
O&M Multiple Basebands consume multiple O&M IP Single O&M IP address
addresses
Resilience HW failure restricted to one Baseband
Configurations Supported with all Baseband types and
configuration, flexible deployment.
Capacity Two Basebands gives 2X capacity of one
Baseband
Coordination E-RAN may be combined with X2 based
features features in the same node
Dual-Baseband as one ME
IP termination on Core Baseband.
Core Baseband failure impacts the entire node
Limited support in 18.Q4. Huge number of potential
combinations of RANs, HW types.
Capacity does not scale in all dimensions with additional
Basebands in one eNodeB
Node-internal. E-RAN and X2 based CA currently not
supported.

Elastic RAN proven in field as a RAN scalability solution

Ericsson Internal | 2018-02-21