Baseband_5216_Overview........................

Charley Lang
BUGS PRS NRO
BASEBAND 521x
Engineering
Overview –
RASO

Baseband 5216 Overview | Ericsson Internal | 2016-02-18 | Page 2
› This presentation is for internal Ericsson use only and not
for external viewing
› Content specified is pre-release and may be subject to
change prior to GA
Disclaimer

Agenda
Introduction
Configuration
Integration
Security / Transport
Baseband HW / SW
Baseband O&M

Prepared for:
1200 Mhz antenna bandwidth

› New HW
– High capacity multi standard HW
› New SW platform
– New O&M interface to the Baseband board
– Aligned between standards:
› O&M & Security
› Common Access Technology
› Transport Network
› Synchronization
› The traffic features are to a large extent
not impacted
Main Differences
compared to DUS

Linux
Control System
LTE WCDMA
SW Architecture
Common Access Technology-CAT
Baseband 5212
Common
O&M GSM
Transport
Baseband 5216 Baseband T503 Baseband T605

Terminology
› MS = Multistandard
› ME = Managed Element
(one logical O&M node towards North Bound Interface (NBI) i.e. OSS)
› MS ME = Multistandard Managed Element
(An ME with capability to contain multiple MFs)
› MF = Managed Function
(represents one RAT towards NBI. MF L, MF W , MF G)
› MSSM = MS Single Mode.
(ME is sharing the same Support System with other ME)
› MSMM Radio = Multistandard Mixed Mode Radio
(Two or more MFs representing different RATs share the same Radio unit)
› MSMM Baseband = Multistandard Mixed Mode Baseband
(Two or more MFs representing different RATs share the same Baseband unit)
› 1 ME / 3 MF = Three MFs instantiated in one MS ME
(ENodeBFunction (LTE), NodeBFunction (WCDMA), BtsFunction (GSM) )
› SSMM Radio = Single Standard Mixed Mode Radio
(Two or more ME representing the same MF share the same Radio)
› MORAN = Multi Operator RAN
(SS MM Radio with two LTE ME serving different operators)
› RAT = Radio Access Technology
› SSR = Single Standard Radio
› MRSI = Multi RAT Single (O & M) Interface
ManagedElement ENodeBFunction
RadioNode with 1 ME containing 1 RAT
RadioNode with 1 ME containing 3 RATs
MRSI
BtsFunction NodeBFunction
ManagedElement
ENodeBFunction

terminology
ME
ME
SUP
MSSM
(shared support system)
RU
RU
MF x RU
MSMM Radio
BB5216 (L+G)
MSMM Baseband SUP
ME
BB5216 (W+G)
BB5216 (L)
MSME (incl MSMM BB and MSMM Radio)
RU
RU
RU
MF y
MF x
MF y
ME
ME
MORAN (SSMM)
MF L
MF L
RU
RU

Agenda
Introduction
Configuration
Integration
Baseband HW / SW
Baseband O&M

› Multi-standard Baseband HW unit :
– Same HW supports LTE, WCDMA and GSM (HWP1)
– Same HW can run two standards simultaneously, Mixed Mode Baseband
(HWP)
– Common O&M for all standards
› Dimensions:
– Height: 8U (350 mm) (same as DUS/DUL)
– Width: 31 mm (same as DUS/DUL)
– Depth: 280 mm (same as DUS/DUL)
› Weight:
– < 4 kg
› Power consumption, early estimates
– Max: 250 W
– Nominal: 210 W
General data
1 HWP = Hardware Prepared, Sw may not be ready

Interface name Connector Comment
Power ET20 No change
EC (Enclose Control) bus RJ-45 No change
LMT RJ-45 No change
TN A RJ-45 No change
IDL A, B Xcede New connector, CPRI & Ethernet
RI A-F SFP+ New support for 10.1 Gbps
TN B, C SFP+ New 10 Gbps Electrical/Optical Ethernet
SYNC RJ-45 New port name
Baseband 5216/5212
interfaces

› A number of ports have changed position on the board compared to
earlier boards. These interfaces are:
– Power
– SYNC (previously GPS)
– TN A, TN B and TN C
– RI A – F
– IDL A and IDL B (new interface)
› Due to this, new cable lengths are sometimes needed when upgrading from
DU to Baseband 5216.
HW changes – port
positions
P
o
w
e
r
S
Y
N
C
R
I
E
C
b
u
s
T
N
A
I
D
L
T
N
B
&
C
R
I
I
D
L
M
M
I
M
M
I
T
N
B
&
C
P
o
w
e
r
G
P
S
T
N
A
E
C
b
u
s
DUS41
Baseband 5216

DUS 31/41 – Baseband 5216
P
o
w
e
r
S
Y
N
C
R
I
E
C
b
u
s
T
N
A
I
D
L
T
N
B
&
C
R
I
I
D
L
M
M
I
M
M
I
T
N
B
&
C
P
o
w
e
r
G
P
S
T
N
A
E
C
b
u
s

The MOM for Baseband
nodes is ECIM compliant
› ECIM (Ericsson Common Information Model)
– Is a platform independent information model for
use by all Ericsson nodes.
– Has MO fragments that are used for things that
are common on all Ericsson nodes e.g. SwM,
PM counters, PM events, FM, Licenses,
Transport (TN), Sync. security, inventory,
backup & restore, etc.

DU Based nodes
CPP based MOM
ManagedElement
IpSystem
NodeBFunction
EquipmentSupport-
Function
MceFunction
NodeManagement-
Function
Equipment
TransportNetwork
Common fragments for all CPP based nodes
Node specific fragments
IpOam
ManagedElement-
Data
ResourceAllocation-
Function
SectorEquipment-
Function
SupportSystem-
Configuration
SwManagement
SystemFunctions

radio nodes
ECIM based MOM
ManagedElement
SystemFunctions
NodeBFunction
ENodeBFunction
BtsFunction
NodeSupport
Pm Fm
SwM
Transport
Common fragments for all ECIM based nodes
Node specific fragments
Equipment
…
EquipmentSupport
Function
Lm

› L16A Baseband 5216 and 5212 supports the following
Radio Node types:
– RBS 6101 - Multi-standard small outdoor base station.
– RBS 6102, Multi-standard high-capacity outdoor base station.
– RBS 6120 DAC, Multi-standard-flexible high-capacity hybrid radio
base station
– RBS 6201, Multi-standard indoor macro base station
– RBS 6202, Multi-standard indoor macro base station
– RBS 6301, Multi-standard outdoor main-remote base station
– RBS 6601, Multi-standard zero-footprint main-remote base station
– RBS 6131, Multi-standard outdoor base station
supported Node Types in
L/W 16A

› FDD:
– RUL01 B13
– RUS01, RUS02, RUS 03
– RRUS11, RRUS 12,RRUS 13, RRUS 31, RRUS 32, RRUS A2, RRUS A3
– AIR 11, AIR 21, AIR 32
– RIR12, RIR 13
– mRRUS12, mRRUS61
– RRUS01, RRUS 02, RRUS E2
– RRU 22F2, RRU 22F3, RRU 22F1
– Radio 2203, Radio 2217
› TDD
– RRUS 61, RRUS 62, RRUS 72, RRUS 82
– RRUL 62, RRUL 63, RRUL 81, RRUL, 82
– RRU 2208, RRU 2216, RRU 2218
› Other HW
– R503 (XMU03)
– AISG TMA
– AISG RET, FlexRET
– RIU
supported radios L/W 16A

16A Baseband SW / HW
SW Package Product Number
15B Baseband GA EP2 CXP 902 4418/1 R14ALD
16A Baseband UM2 CXP 902 4418/2 R5LM
16A Baseband UM3 CXP 902 4418/2 R7GU
16A Baseband UM4 CXP 902 4418/2 R9KF
16A Baseband UM5 CXP 902 4418/2 R11ND
16A Baseband GA CXP 902 4418/2 R11AGG
MOM
CXP 902 4263/1 R26DN
System Version
OSS-RC OSS15B EU09 + ECs
OSS-RC OSS16.0.7 + ECs
HW Delivery number R-State
Baseband 5216 KDU 137935/31 R1D or Later
Baseband 5212 KDU 137935/41 R5B
Baseband T605 KDU 137815/11 R1A
Baseband 16A reached GA on Dec. 7th 2015

Baseband HW
Configuration Roadmap
BB Configuration Primary BB HW Release
Single L 5216 15B
Single W 5216 16A
Single G 5216 16B
Single L 5212 16A
Single W 5212 16A
Single G 5212 16B
Single L+G 5216 16B
Single W+G 5216 16B
Single L+W 5216 16B
Dual L 5216 17A

Agenda
Introduction
Configuration
Integration
Baseband HW / SW
Baseband O&M

› New O&M interface compared to DU based nodes
› The new O&M interface is part of a new Ericsson
strategy for O&M and has already been
implemented for Baseband-T, the Pico RBS and
other non-RAN nodes
› For an OSS-RC user the way of working is similar
compared to DU based nodes, as most of the
interface changes are handled by OSS internally.
› The MOM structure is partly changed
Introduction

O&M interfaces for
baseband nodes
OSS / EM
Baseband Node
NBI
EM
NETCONF
ECLI
SNMP
› New North bound Interfaces between
OSS and the Radio Node:
– NETCONF (for MO management)
– ECLI (Ericsson CLI) (for MO management)
– SNMP (for alarms)
– HTTPS (for web pages)
– SFTP (for fetching logs, UP, ROP files)
› New Managed Object Model (MOM) based
on Ericsson Common Information Model
(ECIM)
› CORBA interfaces removed
HTTPS
SFTP
EM

OAM Security interface
overview
Baseband/Baseband T

OaM Node Access -
Configuration Services
Protocol At operator by
operator
At operator by
Ericsson
Production/RC Ericsson Lab
Netconf Access Access Access Access
COM-CLI Access Access Access Access
RBS CS-COLI No access Access Access Access
CLI (via Linux shell) No access No access No access
(Access before
VC enrollment)
Access
Internal web based tool Access Access Access Access
External tool e.g. MoShell Access Access Access Access
Emergency access Access Access Access Access
Web based boot mechanism as in EPIC Access Access Access Access
NB (Ethernet) interface LMT port (LMT/Console)

OaM Node Access -
Other Services
Protocol At operator by
operator
At operator by Ericsson
(requested by operator)
Repair center Production Ericsson Lab
CMPv2 client Access Access Access Access Access
SCEP client Access Access Access Access Access
OCSP client Access Access Access Access Access
SNMP Access Access Access Access
Diameter client Access Access Access Access Access
NTP client Access Access Access Access Access
LDAP client Access Access Access Access Access
SFTP client Access Access Access Access Access
FTPS client Access Access Access Access Access
Syslog client
(only security events)
Access Access Access Access Access
TFTP client No access No access No access No Access
(Access before
VC enrollment)
Access
NB (Ethernet) interface

Two new element
managers
RBS Element Manager and Cabinet Viewer are not applicable
for Radio Nodes. Instead two new EM tools are introduced.
EMCLI: uses the same base as
AMOS;
EM GUI: shows a graphical view
of the node; Currently planned for 16B

EMCLI opened from PC

› SW Management:
– SW Upgrade
– Backup handling
– HW inventory
– SW inventory
› New OSS tool for working with SW
Management: SHM (Software Hardware
Manager) instead of SMO
› SHM and SMO have very similar work
process
› The SW Management MOs have new
names for a baseband node compared to a
DU based node but the functionality is the
same
› OSS-RC will provide the inventory
information northbound through Bulk CM
for Radio Nodes
SW Management

Backup handling
› For baseband nodes a backup is called
BackUp (for DU based nodes a backup
is called ConfigurationVersion (CV))
› Data base handling changed:
– Baseband nodes: the data base is always
stored persistently on a disk
– DU based nodes: the data base is only stored
on RAM; a CV stores a snapshot of the data
base on a disk persistently
› Since the data is always stored on a disk
no configuration is lost at restart
The data base is always
stored persistently

› Handling of licenses for Radio Nodes is mostly same
as for DU based nodes with some improvements:
– Logical Fingerprint instead of HW dependent
– Common MOM instead of product specific
– SW – HW decoupling for flexibility
– LKF contains keys for functions implemented in
the give SW only
– All optional features have same look & feel from
license handling perspective
License Management
LKF
OSS
Operator sets
featureState = ACTIVATED

Agenda
Introduction
Configuration
Integration
Baseband HW / SW
Baseband Interfaces

Node only exposes necessary information
needed for operation
› No default user preinstalled
› Role based and target based access for shell
commands and Managed Object Classes
› No access to OS, OS prompt or file system
– Hardware rooted secure boot, Signed SW, No access
CMD line access to OS
› Encrypted OaM sessions by default
Improved security

› Node secured by default, exposing no vulnerable
interfaces
– Telnet, ftp protocol not used
– TLS protects access
– Protection applied to internal hardware interfaces such as
JTAG debug port
› ACL's (Access Control List) handle 7-tuple definitions
– Granular traffic management achieved
– Provides a basic level of security and protects the nodes
against unwanted and/or malicious traffic
› Virtual routing separates routed VLANS
– No visibility through separate routed VLANS
› Services enabled when needed
– No unnecessary exposure of interfaces
Improved security

› Ericsson guarantees genuine hardware through Vendor
Credentials
› Signed SW guaranties that only trustworthy genuine
services are deployed in the HW
› By deploying a node based on secure execution
environment, and installing operator certificate, governance
responsibility of the node is transferred to the operator.
Chain of trust
Ericsson
Vendor
Credentials
Ericsson
Signed
Software
Operator
certificate

OSS-RC Security Level
Legacy (WCDMA/LTE)
Security Level 1-3
pRBS GSM SIU 02
TCU 02
Baseband 521x / Baseband T
SL1 SL2 SL3 One security level One Security
level
One Security
level
One security level
File Transfer FTP or SFTP SFTP SFTP SFTP SFTP SFTP
Authentication Node password User specific
password
User specific password User specific
password
User specific
password
User specific password
Authorization - User specific
access rights
(AAQ)
User specific access rights
(LDAPS)
User specific
access rights
(LDAPS)
User specific
access rights
(LDAPS)
(LDAPS)
Management (CM, PM) Corba/IIOP Corba/SSLIOP Netconf /
SSH
Netconf
/TLS
Netconf
(16B)/SSH
Telnet or SSH Netconf /
SSH
Netconf /TLS
Authentication - User
specific
certs
User specific
certs
User
specific
passwd
User
specific
certs
User specific
passwd
User specific
passwd
User
specific
passwd
User specific
certificates
Authorization - Access or
No Access
User specific
access rights
(AAQ)
(LDAPS)
User specific
access rights
(LDAPS)
User specific
access rights
(LDAPS)
(LDAPS)
Terminal con. (commands) Telnet, SSH or serial
interface
SSH or Serial
interface
SSH SSH Telnet or SSH SSH TLS
Authentication Node password User specific
passwd
User specific password User specific
passwd
User specific
passwd
User
specific
passwd
User specific
certificates
Authorization - User specific
access rights
(AAQ)
(LDAPS)
User specific
access rights
(LDAPS)
User specific
access rights
(LDAPS)
(LDAPS)

Port list 16A
Function Destination
/source port
Service/
Version
Client/
Server
Direction
Basic port usage
ESI, Schema export 22/tcp SFTP/SSH Client Egress
DNS 53/udp, tcp DNS Client Bi-directional
NTP client, RFC5905 123/udp NTP v3/v4, SNTP Both Ingress
NTP frequency synchronization (source), RFC5905 123/udp NTP v3/v4, SNTP Both Egress
RFC3417, SNMP, OM Configurable 161/udp SNMP/v1,v2c,3 Server Ingress
RFC3417 SNMP alarm traps, OM Configurable 162/udp SNMP/v1,v2c,3 Client Egress
DS lookup, RFC1777, RFC1778, OM Configurable 389/tcp LDAP Client Egress
Baseband AI Interface, Maintenance User, ESI 443/tcp HTTPS Both Bi-directional
DS lookup, OM Configurable 636/tcp LDAPS Client Egress
NETCONF, RFC6242, OM Configurable, Not supported by OSS 830/tcp SSH/2.0 Server Ingress
ECLI, OM Configurable 2023/tcp SSH/2.0 Server Ingress
PM, ROP-files 2024/tcp SFTP Server Ingress
ESCI 4192/tcp SSH/2.0 Server Ingress
Ericsson support L3 5342/tcp - Client Bi-directional
Ericsson support L3 5343/tcp - Client Bi-directional
NETCONF, RFC5246, RFC5539 6513/tcp TLS/tls-1.2 Server Ingress
ECLI 9830/tcp TLS/tls-1.2 Server Ingress
ESCI 9831/tcp TLS/tls-1.2 Server Ingress
EMCLI, Windows-client callback 10001/tcp Server Egress
Please give your customer this list earlier so that the ports can be opened on time

Port list 16A
Function Destination
/source port
Service/ Version Client/ ServerDirection
RFC5905, NTP frequency synchronization (source) 32751-32766/udp NTP v3/v4, SNTP Client Ingress
Ephemeral port range 32768-40999/udp, tcp SFTP client Ingress
Ericsson support L1-L2 33079/udp - Server Egress
Used by traversing traceroute 33434- 33534/udp Traceroute - -
PM event streaming 51543/udp, tcp cell trace – tcp, UE
trace - udp
client Egress
Bidirectional Forwarding Detection
BFD control 3784/udp BFD Server Ingress
BFD control 3785/udp BFD Both Bi-directional
Precision Time Protocol
PTP Slave , IEEE1588-2008 319/udp PTP Both Bi-directional
PTP Slave , IEEE1588-2008 320/udp PTP Both Bi-directional
IP security
IPsec, RFC 7296 500/udp IKEv2 - Bi-directional
Real time security event log
Real Time Security Event
Log (RTSEL), RFC5424
514/udp Syslog Client Egress
Two-Way Active Measurement Protocol
TWAMP Light responder server 4000-4008/udp TWAMP Server Ingress

› Baseband 5216/5212 hardware is equipped
with 3 Ethernet ports for transport
– TN A: 1Gbps Electrical Ethernet (RJ45)
– TN B and TN C: 1Gbps/10Gbps Electrical/Optical
Ethernet (SFP+) (on 5212 TN C is 1G)
– All ports may be used simultaneously, either for
resiliency or for connecting site equipment
› Connectivity of site equipment may be
achieved using routing or bridging
› Completely flexible IP address and VLAN
configuration for all traffic types
› RPS is replaced by BFD
› Virtual Routing is supported as an enabler
for traffic separation
The new Transport

L16A Transport Content
Basic Features:
› Jumbo Frames
› Access Control Lists (IPv4)
› IP Loopback Interface (IPV4)
› Static Routing (IPv4)
› Ethernet Switching
› Bridged Virtual Interface (IPv4)
› Virtual Routers (IPv4, IPv6)
Optional Features:
› Egress Traffic Shaping (IPv4, IPv6)
› Multiple Ethernet Ports
› 10 GE port capability
› Bidirectional Forwarding Detection (IPv4)
› Static Routing (IPv6)
› TWAMP (IPv4, IPv6)
› IPsec (IPv4)
See Lighthouse and CPI for details.
Two-Way Active Measurement Protocol (TWAMP) in RFC 5357

Agenda
Introduction
Configuration
Integration
Baseband HW / SW
Baseband Interfaces

Configuration and
integration overview
Network
Provisioning
Node
Provisioning
Node
Commissioning
Node
Integration

OSS-RC Pre-Requisite
Network Provisioning
Baseband 521x

Network Diagram

› Define Number of Baseband Nodes
› Prepare SMRS
› Fetch Certificate Fingerprints
› Confirm CDP (CRL Distribution Point) and SAN (Subject
Alternative Name)
› Reconfigure CDP and SAN
› Enable COM
› Prepare SHM
› Prepare Vendor Certificate
› Prepare Netconf (COMUser)

Configuration
› Configuration files are used to build up the node Managed
Information Base (MIB).
› Initially, the Site Equipment File and Site Basic File must
be installed and configured.
› Additional configurations are handled from OSS.
Node Provisioning

› The purpose of the Site Installation File is to point to the
RBS Summary File, in order to connect to OSS.
Site Installation File
Node Provisioning

› The purpose of the RBS Summary File is to define the paths to other
configuration files used for integration of a node.
RBS Summary File
Node Provisioning

› Example
RBS Summary File
Node Provisioning

› The purpose of the Site Equipment File is mainly to handle
configuration of equipment.
› The most important part is to set up the first DU and the
TnPort on the DU, to enable Site Basic File to run, and set
up the connection to OSS.
› Additional equipment configuration can be modified from
OSS.
› Attribute default values can be modified in the Site
Equipment File.
Site Equipment File
Node Provisioning

› The following MOs below MO ManagedElement in the Site
Equipment Configuration File are configured:
Site Equipment File
Node Provisioning

› Part I: Create Baseband Unit/DU and set up connection to OSS
› Part II: Create and Configure Equipment
› Part III: Connect Equipment
Configuration Flow
Node Provisioning

› The purpose of the Site Basic File is to set the attributes that define
security management, system management, and transport network
configuration
› At least one maintenance user must be added at integration. The
maintenance user enables emergency access to the node. If no
Maintenance User is configured at integration, no maintenance user
can be configured after integration.
› The maintenance user configuration is part of the Site Basic File. A
maintenance user can be configured for a TLS client or an SSH client
log on, or both.
– For TLS client log on a trusted certificate and node credentials are needed.
– For SSH client log on username and password are needed.
› Use a TLS client if possible for the maintenance user log on. If not, the
SSH client is also acceptable.
Site Basic File
Node Provisioning

User Management
Node Provisioning

Enrollment & Node
Credential
Node Provisioning

Agenda
Introduction
Configuration
Integration
Baseband HW / SW
Baseband Interfaces

› The UAT of SL for BB 521x and T503/T605 was completed
last week. It will be ready around the beginning of 2016
after SFOA
› In the meantime, following manual process can be used
Integrate BB521x with
Smart Laptop Node Commissioning

Semi-Auto integration
GUI Node Commissioning

Auto integration help
screen Node Commissioning

Emergency access SW
Node Commissioning

› At power on the NL (Network Loader) starts and UP
plus config files are installed in the node
› Then the node reboots and the installed UP
(upgrade package) executes in Secure environment
and the config is set up
› During setup the operator certificate enrollment is
performed (through IPSec if configured), looking up
address in DNS and time is set using NTP
› During certificate enrollment the keys are generated
in secure environment and CSR (Certificate Signing
Request) is sent to CA
› Returned signed node certificate including CA pubs
file contains all needed trust certificates
› Based on fingerprints the needed trust certificates
are inserted into trust category(ies)
› Now the node has a connection to OSS from where
the final configuration is pushed to target
Semi-Auto integration
NTP
DNS
OSS
Node Integration

Baseband_5216_Overview........................

Baseband_5216_Overview........................

Recommended

Recommended

More Related Content

Similar to Baseband_5216_Overview........................

Similar to Baseband_5216_Overview........................ (20)

Recently uploaded

Recently uploaded (20)

Baseband_5216_Overview........................