LZT1381958 - Field Maintenance

Baseband Radio Node - Field
Maintenance
STUDENT BOOK
LZT1381958 R1A
LZT1381958 R1A
Baseband Radio Node - Field Maintenance
DISCLAIMER
This book is a training document and contains simplifications.

Therefore, it must not be considered as a specification of the system.
The contents of this document are subject to revision without notice

due to ongoing progress in methodology, design and manufacturing.
Ericsson shall have no liability for any error or damage of any kind
resulting from the use of this document.
This document is not intended to replace the technical

documentation that was shipped with your system. Always refer to
that technical documentation during operation and maintenance.
© Ericsson AB 2017
This document was produced by Ericsson.
 The book is to be used for training purposes only and it is strictly

prohibited to copy, reproduce, disclose or distribute it in any
manner without the express written consent from Ericsson.
This Student Book, LZT1381958, R1A supports course number
LZU1082513.
-2 - © Ericsson AB 2017 LZT1381958 R1A

Table of Contents
Table of Contents
1 RADIO ACCESS NETWORK, ERICSSON RADIO SYSTEM

AND RBS SITE OVERVIEW .........................................................7
1 INTRODUCTION .............................................................................. 8
2 MOBILE STANDARDS ..................................................................... 8
2.1 GSM RAN SYSTEM INTRODUCTION ........................................... 8
2.1.1 GSM RAN SYSTEM .................................................................... 9
2.2 WCDMA RAN SYSTEM INTRODUCTION ..................................... 9
2.2.1 WCDMA RAN SYSTEM ............................................................ 10
2.3 LTE SYSTEM INTRODUCTION................................................... 11
2.3.1 LTE RAN SYSTEMS ................................................................. 11
3 RADIO TRENDS ............................................................................. 12
4 ERICSSON RADIO SYSTEM (ERS) ............................................... 15
4.1 ERICSSON RADIO SYSTEM HARDWARE ................................. 16
4.1.1 FEATURES OF NEW BASEBAND AND RADIO

PRODUCTS ......................................................................................... 19
4.1.2 BASEBAND 6620 AND BASEBAND 6630 ................................ 23
4.1.3 BASEBAND 6502 ...................................................................... 25
4.1.4 BASEBAND 6303 ...................................................................... 25
4.1.5 BASEBAND C608 ..................................................................... 27
4.1.6 BASEBAND P614 ..................................................................... 28
4.1.7 RADIO....................................................................................... 30
4.1.8 ENCLOSURE FOR THE BASEBAND 52XX UNIT .................... 35
4.2 ERICSSON RADIO SYSTEM SOFTWARE ARCHITECTURE ..... 36
5 OTHER EQUIPMENT AT A RADIO NODE SITE ............................ 36
6 SUMMARY ..................................................................................... 44
2 CUSTOMER PRODUCT INFORMATION ........................................ 45
LZT1381958 R1A © Ericsson AB 2017 -3 -

1 CUSTOMER PRODUCT INFORMATION ....................................... 46
1.1 CPI FOR BASEBAND BASED RADIO NODE- WHERE TO

FIND THEM? ........................................................................................ 47
1.2 CPI STRUCTURE ........................................................................ 48
1.2.1 THE SEARCH FUNCTION ........................................................ 49
1.2.2 HARDWARE RELATED CPI DOCUMENTS ............................. 51
1.2.3 ALARM RELATED CPI DOCUMENTS ...................................... 52
2 TOOL KITS ..................................................................................... 53
2.1 MAINTENANCE TOOL SET......................................................... 55
3 SUMMARY ..................................................................................... 56
3 WORKING WITH A BASEBAND RADIO NODE AS A FIELD

MAINTENANCE PERSONNEL ................................................... 57
1 OVERVIEW..................................................................................... 58
2 CONNECTING THE LAPTOP TO BASEBAND 52XX LOCALLY .... 58
2.1 WHAT IS REQUIRED BEFORE GOING TO THE SITE? ............. 59
2.2 PHYSICAL CONNECTION .......................................................... 60
2.3 IP ADDRESS ............................................................................... 60
2.4 CONNECTION VERIFICATION ................................................... 60
2.5 EMCLI INSTALLATION ................................................................ 61
3 MANAGED OBJECT MODEL (MOM) IN BASEBAND 52XX ........... 62
4 GSM AND WCDMA MOM (MANAGED OBJECT MODEL) ............. 66
5 EMCLI ............................................................................................. 67
5.1 FIELD MAINTENANCE COMMANDS WITH EMCLI .................... 67
6 EMGUI ............................................................................................ 68
6.1 ALARM LIST VIEWER ................................................................. 68
6.2 ALARM VIEW .............................................................................. 69
7 FAULT MANAGEMENT .................................................................. 70
7.1 FAULT HANDLING ...................................................................... 71

Table of Contents
7.2 STATE HANDLING ...................................................................... 72
7.3 AUTOMATIC RECOVERY ........................................................... 72
7.4 ALARM HANDLING ..................................................................... 74
7.4.1 ALARM LIST ............................................................................. 74
7.4.2 ALARM SEVERITY ................................................................... 75
7.4.3 ALARM OPERATIONAL PROCEDURAL INFORMATION

(OPI) 76
7.4.4 ALARM LOG ............................................................................. 77
8 LOGS AVAILABLE AT THE SITE ................................................... 78
9 BACKUP HANDLING ...................................................................... 79
9.1.1 FAILSAFE BACKUP FUNCTION .............................................. 81
10 LIGHT EMITTING DIODES (LEDS) AND MAINTENANCE

MODE .................................................................................................. 82
10.1 MAINTENANCE MODE ............................................................. 82
10.1.1 TECHNICIAN PRESENT ........................................................ 83
10.1.2 FULL MAINTENANCE MODE (LOCKED) ............................... 84
10.1.3 HW RESET MODE.................................................................. 84
11 HARDWARE OPERATIONS ......................................................... 84
11.1 LOCK A HARDWARE UNIT ....................................................... 87
11.2 UNLOCK UNIT ........................................................................... 87
11.3 RESTART UNIT ......................................................................... 88
11.4 REPLACE UNIT ......................................................................... 89
12 HANDLING FAULTY UNITS ......................................................... 89
12.1 HANDLING FAULTY EQUIPMENT ............................................ 90
13 PREVENTIVE MAINTENANCE..................................................... 91
14 SUMMARY.................................................................................... 92
4 ACRONYMS AND ABBREVIATIONS ............................................. 93
5 INDEX ............................................................................................ 103

6 TABLE OF FIGURES ..................................................................... 105

Radio Access Network, Ericsson Radio System and RBS site overview
1 Radio Access Network, Ericsson Radio

System and RBS site overview
Objectives
After this chapter the participants will be able to:

1 Explain on an overview level the RAN site concept for RBS
1.1 Explain the basic GSM, WCDMA and LTE Radio Access Network
1.2 Explain briefly the Ericsson Radio System
1.3 Outline the different radio site components, including the
Baseband products, and the radio products
Figure 1-1: Objectives of Chapter 1

1 Introduction
This chapter will give an overview presentation of the GSM, WCDMA and LTE
architecture; functionalities of the different nodes, the various interfaces used to
connect from one node to another.
This part of the course will also present the changes that happened over the past
years in the mobile network. Mobile broadband traffic has caused a huge effect
on this changes and upgrades in the mobile network.
Mobile broadband traffic is growing faster than ever, especially in high-density

areas such as city centers, business parks, transportation hubs and public venues.
Such locations are the focus for rapidly rising levels of mobile data traffic driven
by the growing use of smartphones and tablets, both indoors and outdoors. To
meet these demands, operators are deploying a mixture of 3G, 4G and, in the near
future, 5G in a variety of frequency bands, as well as small cells and Wi-Fi. In
order to serve all these radio technologies efficiently from existing cell sites,
operators are going to need a new approach to radio site design and building
practice.
2 Mobile Standards
2.1 GSM RAN System Introduction
Core Network
Network
BSC: Base Station Controller
TRC: Transcoder Center/Controller MSS GSN
Management
BTS: Base Transceiver System Environment
OSS-RC: Operation Support System – Radio Core
ENM: Ericsson Network Manager External
MS: Mobile Station Management
A A System
Gb
Gb
TRC OSS-
RC/ENM
A-ter
BSC
Radio Access TRC/
BSC
Network
Um Um
Abis
Abis Abis
BTS
MS BTS BTS
MS
Figure 1-2: GSM RAN Overview

The GSM Radio Access Network (RAN) consists of Base Station Controller
(BSC), Transcoder Controller (TRC) which can be standalone or combined with
BSC, Radio Base Stations (RBS), the Operation Support System for Radio and
Core (OSS-RC) or the Ericsson Network Manager (ENM), and the Operation and
Maintenance Common Infrastructure (COMINF).
2.1.1 GSM RAN System

The Base Station Controller (BSC) manages all the radio-related functions of a
GSM network. It is essentially a high-capacity switch that provides functions
such as MS handover, radio channel assignment, and the collection of cell
configuration data. A number of BSCs may be controlled by each MSC.
The BSC could be standalone with remote connection to or combined with

Transcoder Controller, TRC. The interface from the standalone TRC to the BSC
is called A-ter.
On the other hand, the Evo Controller 8200 is a multi-controller. The Evo
Controller 8200 is a vital component of the RAN evolution strategy. It combines
the functions of the GSM base station controller (BSC) and the UMTS radio
network controller (RNC) in one common network controller. The Evo Controller
8200/MULTI provides the possibility to combine BSC, RNC and Wi-Fi
controllers with a few common building blocks. Smart MBB capabilities can also
be added into the same Evo C cabinet. For CDMA networks, an all-IP base
station controller for supporting voice, and a high-capacity network controller for
EV-DO packet data.
The BSC/Evo C is connected to the core network via the A interface, and the
Mobile Station, MS, is connected to the RBS via the Um interface (the radio
interface). Internally within RAN, the RBSs connect to the BSC/Evo C via the
Abis interface Abis over IP interface.
Operation Support System for Radio and Core (OSS-RC) is a set of software for
handling operation and maintenance tasks for the WCDMA Network. OSS-RC
supports Core network and radio network for both 2G and 3G. OSS-RC gives a
consolidated view of RAN information such as alarms, configurations and basic
performance.
The Operation & Maintenance Common INFrastructure (COMINF) is a type of

infrastructure solution required for the Operation and Maintenance Intranet.
OMINF is intended for O&M data traffic only.
2.2 WCDMA RAN System Introduction

The WCDMA Radio Access Network (RAN) consists of Radio Network
Controllers (RNC), Radio Base Stations (RBS), the Operation Support System
for Radio and Core (OSS-RC) and the Operation and Maintenance Common
Infrastructure (COMINF). The Radio Access Network Aggregator is optional.
The RAN is connected and controlled by the Core Network (CN).

Core Network
Network
MSC-S SGSN
Management
Iu-cs Iu-ps Environment
RNC: Radio Network Controller
UE: User Equipment Management
Iu Iu System
Iur Mur Mun

RNC RNC OSS-
RC/ENM
Mub
Radio Access
Network
Uu Uu
Iub
Iub Iub
NodeB
UE NodeB NodeB
UE
Figure 1-3: WCDMA RAN Overview
2.2.1 WCDMA RAN System

The main tasks of the RNC is to manage Radio Access Bearers for user data
transport, manage and optimize the radio network resources and control mobility
while the RBS provides the actual radio resources and maintains the radio links.
The RNC is connected to the core network via the Iu interface, and the User
Equipment (UE) is connected to the RBS via the Uu interface (the radio air
interface). Internally within RAN, the RNC's are interconnected via the Iur
interface and the RBS's to the RNC via the Iub interface.
An optional product is the RXI 800, which will be a stand-alone IP router. At the
moment, and for the first implementation of ATM-based WCDMA RAN, this
product will play the role of an ATM aggregator of the hundreds of RBS’s E1
interfaces to concentrate them to a few lines to the RNC. In this way the
transmission costs will be reduced dramatically.
handling O&M tasks for the WCDMA RAN. The OSS-RC is designed for
handling daily network operation and maintenance tasks. It complements the
Software Hardware Manager (SHM) functions implemented in the nodes to
create a complete Network Element (NE) management environment for the
network.
- 10 - © Ericsson AB 2017 LZT1381958 R1A


infrastructure solution required for the Operation and Maintenance. All NEs in
the WCDMA O&M system are interconnected by the O&M Intranet, which is an
IP-based network reserved for data transfer and signaling. To carry and route IP
traffic between the NEs and the OSS-RC, the O&M Intranet needs to be
supported by using equipment, such as network routers, switches and hubs. This
is provided in the OSS-RC product as the COMINF.
2.3 LTE System Introduction

The LTE Radio Access Network (RAN) consists of Radio Base Stations (RBS),
the Operation Support System for Radio and Core (OSS-RC) and the Operation
and Maintenance Common Infrastructure (COMINF).
eNodeB: Evolved Node B EPC

EPC: Evolved Packet Core
GW: Gateway
PDN
Network
HSS: Home Subscriber Server HSS
Serving
GW
Management
MME: Mobility Management Entity MME GW
PDN: Packet Data Network Environment
UE: User Equipment Management
System
S1 S1 Mun
S1
OSS-
RC/ENM
Mul
eNodeB Radio Access

Network
X2
X2
Uu Uu
X2
eNodeB
UE eNodeB
UE
Figure 1-4: LTE RAN Overview
2.3.1 LTE RAN Systems

The main tasks such as management of Radio Access Bearers for user data
transport, managing and optimizing the radio network resources and control
mobility, while the RBS provides the actual radio resources and maintains the
radio links.
Ericsson's LTE RBS types implement the 3GPP eNodeB concept, also known as
eNB. The eNodeB is connected to the core network via the S1 interface, and the
User Equipment (UE) is connected to the RBS via the Uu interface (the radio
interface). Internally within RAN, the RBS’s are interconnected via the X2
interface. In idle mode the UE is responsible for mobility while in active mode
LZT1381958 R1A © Ericsson AB 2017 - 11 -

the eNodeB does the work.
handling operation and maintenance tasks for the LTE Network. OSS-RC
supports Core network and radio network for 2 G, 3G and 4G. OSS-RC gives a
consolidated view of network information such as alarms, configurations and
performance indicators. OSS-RC also provides several interfaces for easy
integration with other network management environments. Operators in network
management centers use OSS-RC to perform network management tasks.

infrastructure solution required for the Operation and Maintenance to cater for
GSM, WCDMA and LTE. All NEs in the O&M system are interconnected by the
O&M Intranet, which is an IP-based network reserved for data transfer and
signaling. To carry and route IP traffic between the NEs and the OSS-RC, the
O&M Intranet needs to be supported by using equipment, such as network
routers, switches and hubs. This is provided in the OSS-RC product as the
COMINF. The IP transport network has no functions specifically for LTE. The
RBS is the only E-UTRAN specific node in the LTE network carrying and
controlling payload traffic.
3 Radio Trends
With the high pace of innovation in the device and application industry, mobile
broadband users expect ubiquitous coverage and ever increasing download
speeds.
To enable this growth we already see operators running Multi-Standard

configurations in their networks and we also see an increasing number of
frequency bands per site being deployed, effectively adding a linear increase in
capacity with spectrum.
Multi-standard Multi-band Multi-layer

now and more on the way is becoming the norm
5000
MHZ
3500
MHZ
LTE
CA
2600
MHZ FDD/TDD
WCDMA/HSPA
1800
GSM/EDGE MHZ
800 MHZ
Driving the requirements for radio network transformation
Figure 1-5: Radio Trends

There is undoubtedly also an increasing interest in TDD spectrum, fuelled by the

availability of large bandwidths, including unlicensed spectrum, and LTE
features enabling carrier aggregation over FDD and TDD.
Spectrum already in use is being re-farmed to make space for new technologies
and thereby more efficient spectrum utilization.
In the near future we also see Multi-layer becoming the norm with both indoor
and outdoor small cells integrated in the network and coordinated with the macro
layer to maximize the total capacity and provide improved user experience.
The networks today and going forward will be about multi-standard, multi-band
and multi-layer.
Already today, many operators have 3 technologies, GSM, HSPA, and LTE.
Ericsson was early and still put a lot of focus on multi-standard offerings.
The future is also about adding more bands for capacity and the growing demand
for user experience. We think that a majority of the operators will have a 5 band
deployment in the coming years.
Further, to get the maximum performance out of each band, we believe that most
if not all of the bands will have a multi-layered deployment, i.e. a combination of
macro and small cells.
GSM
HSPA
5.0 GHz
LTE
UNLICENSED
2600
TDD
CARRIER
AGGREGATION
2100
1800
900
COORDINATED
MACRO & SMALL 800
CELLS
Figure 1-6: 3xMulti Networks
One of the most important areas of our software is to maximize the coordination
between the bands, layers and standards. This is also why we focus a lot on
carrier aggregation and small cells features in our roadmaps. The strong
momentum of carrier aggregation (and the fact that devices support more and
more bands) and coordination leads to that the best performance will be achieved
having the same vendor in a certain area. It is a clear drawback to mix vendors on
different bands and/or technologies.

Operators will need to manage a complex mix of radio standards, bands and
layers over time, and Ericsson is pacing such emphasis on the successful delivery
of a 3xMulti radio network evolution with best performance, robust mobility and
maximum spectrum efficiency.
Operators typically already have multiple radio technology standards in operation

(most commonly GSM, WCDMA-HSPA and LTE). Even as new standards are
introduced, all these standards are likely to continue to coexist for many years to
come. With multi-standard mixed mode solution, operators will be able to spread
their capital and operating costs across all generations of radio technology and
shift traffic handling capacity to the technology that needs it. Hardware- and
energy-efficiency will be greatly enhanced.
As operators roll out 4G LTE networks, and begin developing their strategies for
introducing 5G technology, many are keen to re-farm spectrum currently used for
2G and 3G networks to the newer, more efficient mobile broadband technologies
as soon as possible. Thin Layer GSM is a solution to enable an efficient, high-
performance and future-ready GSM network that enables operators to re-farm
much of their 2G spectrum to 3G and 4G to meet the growing demand for mobile
broadband. Such a ‘Thin Layer’ GSM network will be able to handle remaining
2G voice traffic and M2M traffic within much smaller spectrum demands and
remain in operators’ networks for a long time.
With multiple radio bands in service in their networks, it will be vital for
operators to maximize the spectrum efficiency and utilization of these bands. .
With features like Carrier Aggregation for LTE and Dual Band Multi-Carrier for
HSPA, the network is able to deliver higher throughput, capacity, coverage and
therefore enhanced user experience from existing frequency allocations. Carrier
Aggregation for LTE can combine both FDD and TDD frequencies as well as
licensed and unlicensed frequencies. Dual Band Multi Carrier for HSPA enables
band combination of low band and high band for extended coverage reach and
improved spectrum efficiency.
Centralized Spectrum Multi Standard

RAN Refarming Mixed Mode
Baseband GSM network
Multi- efficiency
Polling
No GSM Ericsson
standard unique HW
GSM
Single
standard
Multi
standard Radio System
automation
LTE Carrier HSPA Dual Load

Aggregation Band Management
Multi-band Multi Carrier
Small Cell Small Cell Integrated Small

Portfolio Coordination Cells
Multi-layer
Figure 1-7: 3xMulti Solutions

Maximizing performance in traffic hotspots and indoor areas will require a multi-
layered combination of macro and small cells. This will make radio coordination
features among the bands, layers and standards vitally important, with a strong
need for radio performance, traffic management and load balancing as well as
SON automation. The higher the level of integration and coordination, the greater
is the efficiency gains.
As operators strive to deliver excellent mobile broadband performance in the

busiest parts of their networks – city centers, business parks, transport hubs,
public venues and hub sites – they will need to deploy extreme capacity sites to
efficiently serve the growing volumes of 2G, 3G, 4G, and future 5G, mobile
traffic. Ericsson Radio System's modular architecture flexibly expands to
changing demands with multi-standard, multi-band and multi-layer technology. It
all but eliminates site acquisition issues, delivering three times the capacity
density with 50 percent improvement in energy efficiency. The new portfolio
reduces total cost of ownership (TCO) by 20%.
4 Ericsson Radio System (ERS)

The Ericsson Radio System is an evolution of RBS 6000 and provides all
necessary components for a successful deployment of a heterogeneous network.
All hardware and software are compatible with RBS 6000. The products range
from systems for macro coverage to products specifically targeted for small cell
deployment.
A Site is not one radio only or one digital unit only. It is a complete
system with all functions.
RADIO
ENCLOSURE
FRONT-
BACKHAUL
HAUL
SITE SMALL BASEBAND POWER CONTROLLER

CELL
Figure 1-8: Ericsson Radio System
The Ericsson Radio System has a modular design, where the different units are
used in many different configurations.
The modular design, where the modules are reused across the Ericsson Radio
System family, gives obvious advantages in terms of logistics, installation, spare
part handling etc.

An Ericsson Radio System node is built-up by different building blocks:
1. Site
2. Radio
3. Small cells
4. Fronthaul
5. Baseband and integrated transport
6. Backhaul
7. Power
8. Enclosure including climate system
9. Controller
The Ericsson Radio System software architecture is scalable, from indoor small
cells (e.g. DOT) to the largest most complex mega-city deployment (e.g. C-
RAN). Ericsson Radio System software scales from an island of indoor small
cells, to clusters of macro & small cells that are tightly coordinated in a
Coordinated RAN (C-RAN) deployment, always providing the best end user
experience.
4.1 Ericsson Radio System Hardware

With the Radio System we are moving from a cabinet based Radio Base Station
solution to a modular system that can be adapted to specific operator needs,
enabling Multi-band, Multi-standard and Multi-layer sites in distributed,
centralized, or any other type of configuration. Cabinet or enclosure is still part of
a flexible component in the Radio System just like e.g. the Power or Baseband
modules.

Baseband 5212 Baseband 5216 Baseband R503
Baseband
baseband Baseband Radio Interconnect
portfolio
Baseband T605 Baseband Main Unit 6601
Baseband Transport Interconnect Baseband Main Unit
Figure 1-9: Baseband portfolio
This is the Baseband portfolio that supports Ericsson Radio System.
Baseband 52xx
Provides the baseband processing resources for the encoding and decoding of the
uplink and downlink radio signals, the radio control processing, the radio network
synchronization, environmental control, the IP interface and the O&M interface
for the radio basestation.
 Base-band processing for the uplink and downlink of LTE, WCDMA and
GSM
 The 3GPP interfaces for radio network elements i.e. S1, X2, Iub, and
Abis for traffic control and the O&M interface for the node (Mul and
Mub)
 Synchronization from the transport network connection or external GPS
 IP connectivity
 Site Local Area Network (LAN) and maintenance interface
 Direct connection to the Radios or connection to the Radios via a front

haul connection
Baseband R
If more capacity for CPRI connectivity is needed, a so-called Baseband R can be

added between the Baseband and the Radios
 Increased connectivity for new & existing radio units in large radio
system configurations

 CPRI multiplexing and de-multiplexing
Baseband T605:
 Baseband unit for advanced routing functionality & traffic aggregation
 Flexible synchronization support & RAN Grand Master for synchronization of
small cells
Baseband Main Unit
 Indoor 1.5 HU 19 inch enclosure that can house 2 Baseband boards
 Mix and match Baseband 5212, Baseband 5216, Baseband R503 or

Digital Unit (DUx) to provide the optimal capacity & configuration of
GSM, WCDMA or LTE .
From a capacity perspective for instance the board can handle 8000 connected
users and 24 cells can be connected to it. It can handle 960 MHz of antenna
bandwidth. The board supports Massively-parallel processing which is world
leading multi-core architecture of processor cores
Radio Baseband 6303
Radio 2203 / 2205
Baseband 6630
Baseband 6620
Micro-Baseband 6502
Baseband Enhanced Outdoor Baseband

baseband
portfolio
Baseband C608 Baseband P614
Baseband Interconnect Baseband PIM Mitigation
Figure 1-10: Enhanced Baseband portfolio
Baseband C
If interconnection between Baseband 52x is required.
Baseband P
It provides PIM mitigation which will reduce PIM that occurs inside and outside
the antenna system, both from static and dynamic PIM sources and for different
band combinations

Baseband is part of the Ericsson Radio System and provides the baseband
processing resources for the encoding and decoding of the uplink and downlink
radio signals, the radio control processing, the radio network synchronization, the
IP interface and the O&M interface for the Ericsson Radio System.
Baseband brings together LTE FDD & TDD, WCDMA and GSM onto the same
hardware and software architecture, providing operators with unparalleled
flexibility and scalability.
4.1.1 Features of new Baseband and Radio products

With the new radios and baseband as a complement to the existing portfolio
together with the complete Ericsson offerings, Ericsson’s is targeting to provide
the best customer value.
4.1.1.1 Baseband
From a capacity perspective, there is a huge increase compared to the existing

Digital units. For instance, one board can handle 8000 connected users and 24
cells can be connected to it. It can handle 960 MHz of antenna bandwidth. So if
you have a 20 MHz LTE carrier and have 2x2 MIMO (2 MIMO streams) for 3
sectors you would consume 20 x 2 x 3 MHz is 120 MHz antenna bandwidth
capacity leaving with 840 MHz.
The board supports Massively-parallel processing which is world leading multi-

core architecture of 256 processor cores.
› Massively-parallel processing system
› High-capacity hardware
– Up to 8000 connected users
– Up to 24 cells
– 960 MHz antenna bandwidth
› Multi-standard hardware
– LTE, WCDMA, GSM
› Mixed operation
– LTE FDD/TDD, WCDMA, GSM
› Common O&M for all standards
Figure 1-11: High Capacity Baseband

One board is Multi-standard capable and can be programmed via software to

support LTE, WCDMA or GSM. Different radio standards can run
simultaneously on the same ‘ONE’ board which is called mixed mode. Both LTE
FDD and TDD can be run at the same time together with one of the other major
radio standards.
There is one common O&M for handling all standards.
The baseband has a central functional role in the Ericsson Radio System.
The Baseband is divided into 3 different product groups namely Baseband X,

Baseband RX and Baseband TX where the X is a number series. The minimum
that is required it the Baseband X.
Figures below shows the characteristics for Baseband 5212 and Baseband 5216.
› LTE (FDD & TDD supported)

– 4000 connected users*
– 600 Mbps Downlink & 300 Mbps
Uplink*
– Up to 12 cells & 480 MHz antenna
bandwidth*
– Up to 1000 VoIP*
› WCDMA
– 576 CE Downlink & 960 CE Uplink
– 252 Mbps Downlink & 84 Mbps Uplink
– Up to 12 cell carriers
› GSM
– Up to 24 TRX
› 48 VDC with ~170 W normal use & ~200

W max** *Hardware prepared
Figure 1-12: Baseband 5212

› LTE (FDD & TDD supported)

– 8000 connected users*
– 1.2 Gbps Downlink & 600 Mbps
Uplink*
– Up to 24 cells & 960 MHz antenna
bandwidth*
– Up to 2000 VoIP & 144 SE/TTI
pooled*
› WCDMA
– 1152 CE Downlink & 1920 CE EUL
Uplink
– 336 Mbps Downlink & 168 Mbps
Uplink
– Up to 24 cell carriers
› GSM
– Up to 24 TRX in a mixed mode
configuration *Hardware prepared
Figure 1-13: Baseband 5216
The Baseband RX can be used towards the radio side in case the operator wants
to increase connectivity for radio units that a single Baseband can handle, for
CPRI multiplexing and de-multiplexing and for media conversion electrical < - >
optical.
› Increased connectivity for existing

radio units in large RBS
configurations
› CPRI multiplexing and de-

multiplexing
– 16x SFP+ ports
› Pluggable optical transceivers
› Direct attach cables (electrical)

– Typical 50W – 48VDC power feed
› Flexible
– Upgradable
– Manageable
– Many possible locations in cabinet or
at site
Figure 1-14: Baseband R503
Port lay out is different and the number of CPRI ports are different the Baseband
6630 has the same technology capacity and capabilities as the Baseband 5216,
Baseband 6620 is equivalent to the 5212

Baseband T605 are optional hardware units for advanced routing functionality &
traffic aggregation. Baseband T605 provide one IP pipe to the mobile backhaul
network, as well as benefiting from the same O&M interface northbound as the
Baseband 5212/5216, fully integrated into the network management suite,
Ericsson Network Manager and OSS-RC.
In addition, Baseband T605 provide flexible synchronization support & RAN

Grand Master for synchronization of small cells, Ethernet bridge and IP router
functions. Multiple simultaneous bridging or routing instances is possible
together with rapid fault detection and failover to an alternative transport link via
BFD.
• alit
› Flexible synchronization support › Baseband unit for advanced
& RAN Grand Master for routing functionality & traffic
synchronization (macro and small aggregation
cells)
› Dual power feed
› Abis over IP support for legacy
GSM › 8 x E1/T1 ports (TDM)
› 5 x 1/10G ports (SFP/SFP+)
› OAM interface security, element
management and network › 4 x 1G ports (SFP)
management same as › 4 x 1G RJ45 electrical ports
Baseband 5212/5216 › 15 Gbps IMIX forwarding
capacity
Figure 1-15: Baseband T605 Transmission capabilities
Baseband T605 follows the 19” building standard, it comes with an easily
removable fan tray allowing it to be standalone in a 19” rack or to fit in exiting
Ericsson Enclosures.
Baseband T605 is a Heterogeneous Network ready solution that supports
multi-layer and by that increases cellular capacity and coverage.

4.1.2 Baseband 6620 and Baseband 6630
› Optimized for main-remote configurations

– 19 inch wide, 1U high, <350mm deep
– 15 SFP/SFP+ for CPRI inter-connect to Radio Units reducing the need for Baseband
R503
– 2 optical 1/10Gbps SFP/SFP+ ports and 2 electrical 1Gbps RJ45 ports
– Eight External Alarm ports
– Dual 48V DC power feeding
– Self-contained environmental control & field replaceable fan unit
Figure 1-16: Baseband 6630/6620
Baseband 6620/6630 follows our new radio system 19” building practice. This
means that the Baseband 663076620 is fully sealed and contains its own climate
control.
Baseband 6620 is part of the Ericsson Radio System and has a 19-inch, 1 HU
building practice. It has the same capacity and mixed mode capabilities as the
Baseband 5212. Baseband 6620 is stand-alone and has its own climate control. It
also has support for 15 CPRI ports.
It is typically recommended for new installations where a 19-inch building

practice is used. Baseband 6620 equals 19 inch Baseband Main Unit + Baseband
5212 + Baseband R503.
Baseband 6630 is part of the Ericsson Radio System and has a 19-inch, 1 HU
building practice. It has the same capacity and mixed mode capabilities as the
Baseband 5216. Baseband 6630 is stand-alone and has its own climate control. It
also has support for 15 CPRI ports.
It is typically recommended for new installations where a 19-inch building

practice is used. Baseband 6630 equals 19 inch Baseband Main Unit + Baseband
5216 + Baseband R503

Ports Quantity Comments

Power 2 -48V
EC 1 RJ45
LMT 1 RJ45
TN 2+2 2 x 10G (SFP/SFP+)
2 x 1G (RJ45)
IDLe 2 XCede
CPRI 15 SFP/SFP+
Sync 1 RJ45
External alarms 8 2 x RJ45
SAU 1
Figure 1-17: Baseband 6320 and 6330 Front Panel Interfaces
Baseband 6630/20 is standalone and has 15 CPRI ports & dual power feeding.
Main
Unit Baseband Baseband
6620/30 6601 5212/16 R503
6620/30
› Baseband 6630/20 is standalone & has its own

climate control › The RBS 6000 chassis is mandatory for Baseband
› Baseband 6630/20 has 15 CPRI ports & dual 5216/12
power feeding › Baseband R503 needed to increase number of CPRI
ports
› Baseband 6630 will have approximately 50W
lower power consumption compared to the
corresponding Baseband Main Unit (6601) +
Baseband 5216 + Baseband R503
configuration
HWAC to enable more than 6 CPRI ports
Figure 1-18: Comparison

4.1.3 Baseband 6502

Baseband 6502 is a multi-standard baseband unit that is optimized for micro sites
and works seamlessly with Ericsson Radio System micro radios (Radio
2203/2205). It can be integrated with the Radio 2203/2205, used on the Ericsson
Rail or used on sites with distributed radios and baseband architectures.
It is visually attractive, less than 5 liters in size. It can be AC or DC powered and

it supports power-over Ethernet for the MINI-LINK all-outdoor unit enabling
highly integrated all outdoor micro site solutions. As it is an integral part of
Ericsson Radio System there is full coordination with the macro cells.
Baseband 6502 can be used for micro and radio dot system.
Baseband 6303 can be used for macro system.
›
›
99 mm
›
–
6502
267 mm
›
›
› 200 mm
›
BASEBAND
6502
›
›
›
Figure 1-19: Baseband 6502 – MICRO
4.1.4 Baseband 6303

Baseband 6303 enables operators to densify their macro network where available
site space is an issue. It enables the operator to build ‘true’ zero footprint Macro
sites. It is a multi-standard powerful outdoor baseband unit with similar capacity
as the Baseband 5212 that can be installed on the Ericsson Rail system with one-
bolt installation.

It is visually attractive, less than 5 liters in size. It can be AC or DC powered and

it supports power-over Ethernet for the MINI-LINK all-outdoor unit. Together
with the rail-mounted Power 6302 solution, this allows operators to build sites
without enclosure; quickly and compact.
›
›
BASEBAND
6303
BASEBAND
›
–
–
–
›
–
› 92 mm
›
›
›
*
›
›
›
›
Figure 1-20: Baseband 6303 – MACRO
Baseband 63-series has zero footprint. Expand LTE by adding a 2nd 6303 (elastic
RAN), Multi-standard and Mixed mode by adding 2nd 6303 (inbuilt router) .
Baseband 6303
Baseband 6303 Enclosure 6340

Flexibility to use entire
Baseband portfolio
Slightly larger than 6303 but
more cost efficient when
2x Baseband required
Figure 1-21: 63-series (zero footprint)

4.1.5 Baseband C608

Baseband C608 is an integral part of the Ericsson Radio System and acts as a
baseband interconnect for Elastic RAN. With our Elastic RAN solution it
possible to build a borderless network where all baseband are interconnected to
maximize efficiency and end-user experience.
Baseband unit for low latency L2 interconnecting to enable

LTE Elastic RAN feature
Same HW format as Baseband T605, horizontal 19 inch
12 x 1/10G SFP/SFP+ ports
4 x 1/10G SFP/SFP+ ports
One O&M – moves transport demarcation point avoiding
specialized cables
Same O&M interface as multi-standard baseband
User interface is common and functional support from
Ericsson management system is the same
*
› Fully verified by Ericsson as end-to-end Elastic RAN
solution
Figure 1-22: New Baseband C608
New Baseband C608 for L2 interconnecting to enable elastic RAN which is the
optimal coordination across the network for D-RAN and C-RAN.

E5 X2
Baseband 5216
i/f TP latency Baseband 5216 S1
IDLe 10G 60uS
Baseband
X2 10G 30 – 60ms C608
S1 10G 30 - 60ms Baseband 5216
› Baseband 5216 x 3 using IDLe DAC or IDLe › Latency max 60uS between Baseband 5216
Optocables and Baseband C608 › Configuration is manual using vlans, similar scripts
› Distance between basebands 1 – 200m can be used for Baseband C608
› 3 x 18 collaborating › X2 connection between all Baseband 52x is required
Figure 1-23: Elastic RAN: small hub > 2 x Baseband 5216
To connect more than three basebands using the interconnect links a very low
latency layer 2 switch is required, to achieve the maximum coordination. The
Baseband C608 is a powerful switch that is used to interconnect the distributed
and centralized Basebands in the network. It supports 12x 10 Gbps ports. 1x 10
Gbps port is required per baseband for Carrier Aggregation. Future expansion is
possible by adding another Baseband C608 to support UL-CoMP.
It is an integral part of Ericsson Radio System, fully manageable with the existing
network management system. The system interface and cabling are optimized to
inter-connect Ericsson baseband products
4.1.6 Baseband P614

Baseband P614 mitigates passive inter modulation (PIM) and operates in the
digital domain by analyzing the downlink and uplink digital streams on the CPRI
links between the baseband and radio. It uses intelligent algorithms to mitigate
the PIM disturbances in the uplink signal before it is decoded in the baseband
unit. It can mitigate PIM, both created inside or outside the antenna system from
static and dynamic PIM sources and also different band combinations. By doing
so it:
 Improves network performance
 Reduce trouble-shooting effort
 Enables new band activation on challenging sites
It is a 19-inch unit with 1 HU in height and is end-to-end integrated in Ericsson

Radio System and its management system.

New Baseband P614 has 6 incoming CPRI ports towards Baseband and 6 output
CPRI ports towards Radio.
The PIM mitigation unit will reduce PIM that occurs inside and outside the
antenna system, both from static and dynamic PIM sources and for different band
combinations
› The Passive Intermodulation (PIM) mitigation unit will reduce PIM that
occurs inside and outside the antenna system, both from static and
dynamic PIM sources and for different band combinations.
– Two Baseband P614 units can be inter-connected to double number of
ports or increase the computational power
– Baseband P614 has 6 incoming CPRI ports towards Baseband and 6
output CPRI ports towards Radio
– Integrated with Ericsson Radio System
› Supported by OSS-RC and *
ENM
Figure 1-24: New Baseband P614
Passive intermodulation occurs when two or more signals are present in a passive
non-linear device or element. The signals will mix or multiply with each other to
generate other signals that are related to the first ones. This can cause interference
in the band & sensitivity degradation.

All non-linearity in materials

around the radio at site may
generate PIM such as loose RF
connectors, poor quality
connectors and RF feeders,
damaged connectors, objects in
front of antennas etc.
The issue of Passive
UL UL
Intermodulation (PIM) is becoming
703 733 758 821 832 862
a larger problem at operators, B28B B20

Frequency (MHz)
mainly due to the increasingly

complex frequency allocations
Figure 1-25: A Passive intermodulation (PIM) Mitigation Unit
Description f2 f1 f2
The PIM mitigation unit will reduce

2f 1-f 2 2f 2-f 1 2f 1-f 2 2f 2-f 1
PIM that occurs inside and outside 3f 1-2f 2 3f 2-2f 1 3f 1-2f 2 3f 2-2f 1
the antenna system, both from IM5
Rx
IM3
Tx
IM5 IM5
Rx Tx
IM5
static and dynamic PIM sources

and for different band
combinations Baseband Radio Radio
Baseband Baseband Radio
Benefit
Improved network performance
Figure 1-26: Passive Intermodulation (PIM) Mitigation
4.1.7 Radio
Ericsson has introduced a set of new radio units as a part of the new Ericsson
Radio System hardware.

Radio 2217 Radio 2212 Radio 2216/2218 Radio 0208
Dualband
Singleband
Radio 4415 Radio 2203 Radio 2205
Figure 1-27: Ericsson Radio System Radio
Figure 1-28: Radio that Fit
With these new technologies and innovations, Ericsson is able to reduce both the
size and weight of the Radio units by around 50% compared with the previous
generations of radios resulting in the industry’s most compact radio.
The small size and light weight, combined with new mounting method, is an
enabler for densification of sites towards multi-band, multi-standards and multi-
layer scenarios without an excessive increase in overall site foot print and weight.
The rail system provides great flexibility in terms of installation. The rail can
extend horizontally or vertically and units can be rotated into virtually any
position. For instance, installations can be made with connector protruding from
the radios making it possible to install the radios very low down, e.g. a wall.

› Multiple mounting options

› Simplified site acquisition
› Minimize footprint
› Fast installation and expansion
› Airflow innovation
Figure 1-29: Rail System
This will help operators to simplify site acquisition as for instance building
permits might be easier to get if certain installation requirements are met.
Reducing the size and weight of the radio units is really helpful and it does solve
future site challenges combined with the new innovative rail system, allowing a
dense and space saving mounting of various modules at site, we see a great
improvement over current solutions
Introduced as well is the One-bolt installation practice as shown in the upper right
corner of Figure 1-29. At the site, you start by installing the rail on a wall or pole.
When that is done, you simply hang a radio off the rail and lock it down with a
single bolt. In this way, a radio can be mounted in less than a minute. A complete
installation of 3 radios today takes around 3 hours. Installing 3 of these new rail
mounted radios takes less than 1 hour to complete, so 1/3 of the installation time.
In addition to radios for macro coverage, Ericsson is also launching a new

modular and small form factor micro radio, the Radio 2203.

› New modular micro radio system

› Macro feature parity, coordination
50%
› 4 liter and 5kg installed
Smaller & lighter
Figure 1-30: Micro Radio
The concept is built upon a radio core, a support system, and an optional
integrated antenna. The support system comprises the power supply, the
mounting bracket, and the fan. Radio 2203 is only 4 liters and weighs 5 kilos
installed.
The architecture is modular enabling easy addition of additional units for multi-
band or multi-branch support in either expanded support systems or even on a
micro rail, similar to the concept introduced for the macro radios. Special care
has been taken to provide means for visually non-intrusive mounting by
simplifying the concealing of interconnect and cabling.
Comparing with the current generation of micro radios, Ericsson has reduced the
size and the weight by 50% and also significantly reduced the power
consumption making Radio 2203 a very competitive and useful product for small
cell or DAS applications.
4.1.7.1 Existing Radio Units
The new Ericsson Radio System Baseband 52xx units can continue to coexist
with the existing radio units. The existing radio units and remote radio units are
shown in the figure below.

Existing RBS 6000 Radio
RUS 01 RUS 02 RUS 03 RRUS 01 RRUS 11 RRUS 61 RRUS 02
RRUS 12 RRUS 13 RRUS 62 RRUS A2/A3 RRUS 32 RRUS 72 RRUS 82 mRRU
Figure 1-31: Radio Unit/Remote Radio Unit Multi-Standard (R/RRUS)
The details and features of these units may be found in the Customer Product
Information (CPI).
Antenna Integrated Radio (AIR)
An AIR unit consists of two Radio Units (RUs) integrated with an antenna. It is
intended to be used in a Main-Remote configuration in the same fashion as
conventional Remote Radio Units (RRUs).
The antenna in the AIR unit is a dual-polarized antenna. The active part of the
AIR unit consists of two RUs integrated into the same enclosure as the antenna.
The active part can be connected to the RBS main unit. The passive part of the
AIR unit allows connection to an existing RBS with the AIR unit functioning as a
standard antenna. The use of the passive part is optional.
The AIR unit is intended to be installed outdoors on a pole, mast, or wall.
The active and passive parts of the antenna in the AIR unit can simultaneously be
used for different radio network access standards. Each part has the Remote
Electrical Tilt (RET) function and can be electrically tilted independent of the
electrical tilt of the other antenna part.
The AIR unit can also be mechanically tilted by using the down tilt installation
kit.
The active part of AIR 11 has 2 TX branches and 2 RX branches with a dual-
polarized antenna (two antennas).
The active part of AIR 21 has 2 TX branches and 4 RX branches with two
columns of dual-polarized antennas (four antennas).
The active part of AIR 32 is an integrated 4-branch radio unit and a dual column,
dual-polarized antenna.

AIR 11 AIR 21 AIR 32

Figure 1-32: Antenna Integrated Radio (AIR)
The details of the AIR products are available in the Customer Product
Information.
4.1.8 Enclosure for the Baseband 52xx unit
› 19 inch indoor main unit for baseband
› Mix and match

– Baseband 5212
– Baseband 5216
– Baseband R503
– Baseband T503
– RBS 6000 DUG, DUS & TCU
› Provide the optimal capacity & configuration of GSM,

WCDMA or LTE and combinations thereof
Figure 1-33: Baseband Main Unit 6601
The new Baseband 52xx can fit in any existing enclosure. RBS 6601 is shown as
an example in the figure below.
As the figure suggests, the Baseband unit could be put in the existing RBS 6601
enclosure, together with Baseband R503 o. Alternatively, other existing macro
RBS 6000 enclosures may also be used.

4.2 Ericsson Radio System Software Architecture

With Ericsson Radio System software architecture, all the radio technologies
share the same middleware and control system. The new software architecture is
based on Linux OS. The software architecture is hardware independent.
Baseband T and Baseband 52x all share the same code base. The architecture is
component base; the common components are transport, O&M.
Operations Support System
Evo Controller
O&M LTE WCDMA GSM Transport

Security
Netconf
SNMP
CLI
Middleware
Control System
Linux
Baseband 5212 Baseband 5216 Baseband T503 Baseband R503 Baseband T605
Figure 1-34: Ericsson Radio System Software
How to work with the Baseband unit is explained in Chapter 3.
5 Other equipment at a Radio Node site

The Baseband processing unit (e.g. Baseband 52 or the Digital Unit), the Radio
Units (e.g. Radio 2203 or RUS12 or RRUS12) and the antenna units are primary
components at a radio site. However, they are not the only ones.
Figure 1-35: What can one find in a site?

The power system, battery backup solution, transmission equipment, external

alarms are some of the other components that could be at the site. Depending on
the solution and nature of the site, there is a subset of equipment.
Figure 1-36: A macro site example
Let us take an example of the energy systems and battery offerings from Ericsson
and therefore possible to find at a radio node site.
Figure 1-37: Energy Systems and Batteries

Telecommunication networks are evolving and expanding; as a result the

supporting power infrastructure needs to be robust, cost effective and scalable.
Efficient Energy Solutions can assist operators in growing their business in a
sustainable way. Increasing energy efficient in a network not only reduces
operational running costs and maximizes revenue, but also increases
economically benefit and enhances ethical and Ericsson’s Corporate Social
Responsibility.
Ericsson’s Efficient Energy Solution (EES) is an end-to-end offering that assists

operators to address specific power, energy and environmental concerns. The
fundamental value proposition of Ericsson’s Efficient Energy Solution is to make
it easier for operators to address the many complex and confusing challenges of
optimizing energy usage in a telecommunications network and to maximize
traffic out from power in.
As the offering in the figure above suggests, there could be quite a range of
equipment at a Radio Node site, depending on the type of site/solution. If the site
has a number of Digital Units or Baseband units, all the units share the
infrastructure. It is likely that Ericsson Site Controller (ESC) is used for the
management of these units- and even remotely.
The antenna system, connected to the radio unit or remote radio unit, can consist
of a number of solutions, as the figure below suggests.
Figure 1-38: Antenna Systems
Some important concepts related to the Antenna System are described below.

5.1.1.1 Antenna
The antenna transmits and receives Radio Frequency (RF) signals distributed
through a feeder cable to the node.
In LTE, for example, the types of antennas are as follows:

 Directional antennas are used to cover one or several sectors from a
common node. The antenna beam is directed away from the tower
covering a specific area.
 Omnidirectional antennas cover an area of a circle surrounding the
tower placed in the middle of a sector.
The figure below shows some examples of antenna and near products currently
used today.
Ericsson Andrew
Kathrein
Powerwave
RET
TMA Feeder
Feeder
Figure 1-39: Antennas & Near Products
The pictures above show a variety of different types of antenna such as Omni and
Sector, single and tri-band antennas. Some of them also have Manual Electrical
Tilt, MET, to which Remote Electrical Tilt Units could be connected.
5.1.1.2 Tower Mounted Amplifier
The TMA amplifies RF signals on the receive path, before the signals are
transmitted to the node. The TMA increases uplink coverage by compensating for
RF cable loss between the radio unit and the antenna. The signals from the
Transmitting (TX) node are filtered but not amplified before being sent to the
antenna.
TMAs allow long feeders and high-power amplifiers in the downlink,

contributing to balanced downlink and uplink signals.
TMA configurations supported include:

 Golden feeder TMA. This type of TMA is an external TMA and is

not supplied with DC from the node and cannot be monitored.
 TMAs with an AISG 2.0 interface that communicates with the node
on the antenna feeder using the Iuant interface protocol. These TMAs
can report gain values and fault conditions to the node and also
control RET equipment on an RS-485 interface. This TMA is power
supplied by the node and has the possibility to supply RET units with
DC power.
The DDDTMA consists of double dual duplex TMA (Tower Mounted Amplifier)
units for the support of two antenna branches. Each TMA unit supports one
combined Rx/Tx antenna and is connected to a single combined Rx/Tx RBS
feeder. The TMA thus has two antenna ports and two Rx/Tx feeder ports.
The figure below shows the different implementations of a TMA.
TX/RXA TX/RXB TX/RXA TX/RXB
DX1 DX2
DX1 DX2
Jumper D D
T T D D
M DTMA M T ASC T
M M
A A A A
Feeder
TX RXA TX RXB DX1 DX2
DDTMA
Figure 1-40: Tower Mounted Amplifier (TMA)
A dual duplex TMA unit has low insertion loss in the RBS DL band and a high
gain with a low noise figure in the RBS UL band. The TMA unit thus improves
the system noise figure of the RBS Rx chain and thereby the reception sensitivity.
The TMA unit also provides a prescribed attenuation of signals outside of the
UMTS UL and DL bands.
The TMA unit has 5 ports, which consist of:

 Two antenna ports; these ports are used for both RF signals (Rx/Tx) and
for supervision of the antenna.
 Two RBS feeder ports; the RBS feeders are used for distribution of both
RF signals and DC power. For the later models both ports could
communicate while on the first model only one RBS port is used for
communication RBS-TMA.
 One EXT AUX unit port; the EXT AUX port is used for control and
powering of an optional AUX unit.

The TMA is supervised, and power is supplied to it, by the RU in the RBS, via
the RF feeder.
The TMA also supports the RET function in the antenna. The TMA shall be
mounted close to the antenna and connected via feeder cables to the RBS.
The main features of the TMA are:

 Compensation for feeder loss
 Adjustable pre amplification of RX signals
 Increased coverage
 Antenna Supervision
5.1.1.3 Remote Electrical Tilt (RET)
The RET provides electrical tilt for tuning and optimizing the network by
adjusting the vertical lobe-angle of the antenna. The RET is implemented in both
the node and the OSS. Antennas connected to the node can be adjusted from a
remote location, for example, from an Operation and Maintenance Center. A site
visit is not required.
The RET (implemented in the ARET hardware) communicates by the Iuant

protocol.
The RIU can be installed on feeder "A" between the radio unit and the antenna. If
both a TMA and an RIU exist in an antenna system, the RET control is
performed by the RIU.
The figure below shows the connection possibilities for a RET.

Figure 1-41: Remote Electrical Tilt, RET
The RET unit is a separate unit from the antenna and is connected via a cable to
the TMA for DC supply and control signaling.
5.1.1.4 Ericsson Psi Coverage
Ericsson Psi Coverage is an Ericsson unique innovation providing a solution for

cost-efficient broadband coverage in areas with light to medium traffic volume.
Psi Coverage includes only one RRU (Remote Radio Unit) for entire 3 sector
site, which is at least 2 fewer RRU’s compared to alternative solutions.
There are different ways to implement the Psi-coverage. Here is an example how
a physical connection could look like. Notice how only one Radio Unit is
sufficient to support three sectors.

Figure 1-42: Psi Coverage
The TTMF (Triple Phase Shift TMA) splits the downlink (TX) signal to antennas
in three sectors. The uplink signals (RX A and RX B) from all sectors are
frequency shifted before they are combined and sent to the radio unit. The TTMF
reduces the number of physical units from four to one and eliminates six jumper
cables compared to a classic Psi-Coverage site.
The main benefits for the operator are a substantial reduction in power
consumption and other costs compared to a traditional 3 sector site while
providing similar downlink and uplink peak rates and performance.

6 Summary
The participants should now be able to:

1 Explain on an overview level the RAN site concept for RBS
1.1 Explain the basic GSM, WCDMA and LTE Radio Access Network
1.2 Explain briefly the Ericsson Radio System
1.3 Outline the different radio site components, including the
Baseband products, and the radio products
Figure 1-43: Summary of Chapter 1

Customer Product Information
2 Customer Product Information
Objectives

2 Use the Customer Product Information (CPI)
2.1 Explain the CPI library structure of the node
2.2 Find information in the CPI Library with use of regular expression
2.3 List the important documents in the CPI for maintaining a Baseband
52 based Radio Node
2.4 Locate correct OPI to solve alarms
2.5 Know what different Tool Kits exist and how to order them

1 Customer Product Information

The Customer Product Information (CPI) presents the information products
available for all of Ericsson products, including the Baseband based Radio Nodes
and the RBS 6000 family. Each documentation library contains the CPI necessary
for the life cycle of the corresponding product.
All Ericsson CPI can be accessed online and either browsed on screen using the
Active Library Explorer (ALEX) or printed. CPI is accessed through the Ericsson
e-business portal on the Ericsson Extranet https://ebusiness.ericsson.net/.
A user id and a password are required to access the CPI Extranet service. Access
is provided by the Key Account Managers (KAMs) at the Ericsson Local
companies.
To be able to access the site you need to check the following:
 Your company allows access to secure sites (HTTPS) through its firewall
 Your computer has either Microsoft Internet Explorer 6.0 or higher
 Your browser has the necessary plug-ins to view or download PDF and
Microsoft Office files
If you are unsure about any of these prerequisites, then ask your local IS/IT
support or help desk.
Within Ericsson, CPI is available on CPI Store, using the Alex Library Explorer
(ALEX) browser, which has the following requirements:
 Microsoft Internet Explorer 6.0 or later
 Firefox 1.0 or later
 Mozilla 1.7 or later
 Adobe Reader plug-in
 Google Chrome 16.0 or later
ALEX for Windows has the following browser requirements:
 Microsoft Internet Explorer 6.0 or later
 Adobe Reader plug-in
To access Excel files, either of the following must be installed in the computer.
 Microsoft Office Excel 2007 or later
 an earlier version of Microsoft Office Excel and Microsoft Office

Compatibility Pack for Word, Excel, and PowerPoint File Formats

ALEX supports the retrieval of document files in both HTML and PDF format.
For PDF files, the software application used for display is Acrobat Reader 3.1 or
higher. The CPI library is viewed by using the Active Library Explorer (hosted
by a web server or a stand-alone PC) together with standard web browsers.
› CPI is the technical information that the customer needs to

handle Ericsson products throughout the product lifecycle.
› CPI can be accessed online and either browsed on screen

using the Active Library Explorer (ALEX) or used in printed
form.
› CPI is accessed through the Ericsson e-business portal on

the Ericsson Extranet by customers.
https://ebusiness.ericsson.net.
Figure 2-2: What is CPI?
1.1 CPI for Baseband based Radio Node- where to find them?
The figure below illustrates the ALEX Database for the whole RBS family – and
it comprises which not only the Digital Unit based RBSs (in the RBS 6000 series)
and the Baseband unit based Multi-Standard Radio Nodes.
Figure 2-3: Active Library Explorer (ALEX) structure in RAN
In the figure above, the Ericsson Radio System Hardware libraries in ALEX is
shown, which, as explained in Chapter 1, includes a variety of units. The
Ericsson Radio System Software consists of the GSM, WCDMA and LTE radio
network, together with the transmission products.

On the right, in the figure above, the Site products are shown- to show that there
is a customer product information for all the products.
The CPI for the Baseband Radio Node may be found under the LTE, WCDMA
and GSM (from 16B) RAN, as shown in the figure below.
Figure 2-4: Baseband Radio Node Libraries
The Baseband Radio Node is the same library and is applicable for the LTE,
WCDMA and GSM (from 16B).
1.2 CPI Structure

The structure of the customer documentation inside the Baseband CPI is shown
in the figure below.

Figure 2-5: CPI Library Structure
The CPI contains all the information relevant for managing the LTE, WCDMA
and GSM Radio node. For a Field Maintenance personnel, the alarm and
hardware handling documents are the most relevant. “Product Overview”,
“Installation” “O&M Tools”, “Fault Management”, “Hardware Management”
directories are the most used.
1.2.1 The Search function

In the ALEX CPI, the search function could be used to find the correct
documentation(s) fast.

Figure 2-6: Search in ALEX
In the figure above, the term “emergency” (not CAPS lock sensitive) is being
searched in the Search field, and all the documents that have Emergency are
displayed.
Some simple rules while searching are listed below:
Spacing: Spaces between words in the search pattern are treated as a

logical AND, that is, both words must be present somewhere in a
document to make a match.
Wildcards: Wildcard symbols expand the scope of a search. The

Document View search function supports the following wildcard
characters:
◦A question mark (?) representing any single character
◦An asterisk (*) representing an unlimited number of characters in a word
Wildcards can be used in all types of Document View searches, except

phrase search.
Phrase Search: Multiple words entered in the search field (for

example, CPI for RBS), are treated as a phrase only when placed within
quotation marks ("). Phrase search is supported only in Instant document
search for HTML documents, not, however, for PDF or Excel
documents.

Logical Symbols: Logical symbols define the relationships between

words or groups of words and can be used to expand or limit the scope of
the search. A logical symbol must be preceded by a space, otherwise it is
treated as part of the search term.
| Extends the search and retrieves items containing any of the words it
separates (logical OR)
- Limits the search and retrieves items that do not contain the term
following it (logical NOT)
Logical symbols are supported only in Instant document search. In

Advanced document search, the logical operators can be selected in the
input form.
Since Managed Object concept is used in the Operation and Maintenance of the
Baseband node, the folder “Managed Object Management” is very useful as one
gets more used to the radio node.
Figure 2-7: Managed Object Model (MOM)
In the MOM document, the parameters (also called “attributes”) of MO types are
shown, together with “actions” and counters that are relevant for that MO-type
are shown. In the example above, the MO Cabinet and its attributes are shown.
1.2.2 Hardware related CPI documents

Some of the documents related to hardware management, which are used
frequently by the Field Maintenance personnel are listed in the figure below.

Figure 2-8: Hardware Management
It is not the intention to describe each of these documents here. However, the
Field Maintenance personnel is encouraged to be aware what these documents
contain.
1.2.3 Alarm related CPI documents

When an alarm is issued, it has an alarm slogan. For each alarm that may be
raised in the Baseband node, there is a related Operating Instruction, which the
operator should follow to solve it.

Figure 2-9: Alarm Management
In the example above, an alarm called “A Fallback Operation Will Soon Be

Started” could have come up (to warn that upgrade is not confirmed yet, and
there might be a rollback if the operator does not do something now.)
2 Tool Kits
Personnel working with installation or maintenance tasks must have the proper
tools to be able to make a proper job with a high standard.
› Contact the Ericsson Local company within your country for

assistance and ordering support
› Tool sets
– Personal Tool set (LTT 601 135/1)
– Personal Tool Kit, Light (LTT 601 156/1
– Maintenance Tool set (LTT 601 137/1)
Figure 2-10: Tools - How to order

Product Name Description Product No.

Personal tools LTT 601 135/1
Tool set
Personal tool kit, light LTT 601 156/1
Crimping tool for earth
Tool set LTT 601 86
grounding
Torque set 5-25 Nm LTT 601 140/1
Torque wrench with
3/8-inch drive 20-100 Nm LTT 601 141/1
ratchet head
7/16 jumper Tool for connecting the
connector tool jumper connectors on LSB 107 30/1
the filter unit
Open-ended head 32 mm LSB 107 12/5
Figure 2-11: Ericsson Tool Kits
The personal tool set is specially designed for site installation and relevant to all
types of RBS cabinets.as shown in Figure 2-11 above and the inventory list is just
below that.
Personal Tool set (LTT 601 135/1)
Figure 2-12: Tool set for Installation

Description Qty Description Qty
Tool case 1 File round 1
First aid kit 1 Hack saw 1
Static control wrist strap 1 Saw blade, 12" 24tpi (10pcs) 1
Ear muffs 1 Socket set 3/8" 10-19mm,incl bits 1
Eye protectors 1 Socket 16mm 1
Gloves, size L 1 Socket 18mm 1
Gloves, size XL 1 Hexagon socket 8mm for 3/8" wrench 1
Cable cutter < 95mm 2 1 Hexagon socket 4mm for 3/8" wrench 1

Side cutting plier 8160 1 Screwdriver for Bits 1

Slip joint plier 1 Screwdriver TORX no. 10 1
Plate shears, straight 1 Screwdriver TORX no. 15 1
Knife 1 Screwdriver TORX no. 20 1
Wire stripper 0,2-6,0mm 1 Screwdriver TORX no. 25 1
Cable shield cutter, 25-150 1 Screwdriver TORX no. 30 1
sq.mm
Pen hammer 1 Screwdriver, 0.4x2,5x60 1
Spirit level 200mm, magnetic 1 Screwdriver, PZ 2 1
Termination tool, Krone 1 Slotted socket 27 / 32mm 1
Tool for cable ties 1 Extension bar 3/8" x 250mm 1
Measuring tape, 6m 1 Set of U-wrench 1
File 6" flat 1 U-wrench, 21-23mm 1
File half-round 1 U-wrench, 24-27mm 1
Multimeter, kit 1 Torx bit TT 30 1
QMA Extractor 1
2.1 Maintenance Tool Set

The maintenance tool set is specially designed to maintain the RBS equipment
and relevant to all types of RBS cabinets. The inventory list is just below that.
Maintenance Tool set (LTT 601 137/1)
Figure 2-13: Tool set for Maintenance

Description Qty Description Qty
Tool case 1 Socket 18mm for 3/8" wrench 1

First aid kit 1 Double flex wrench, 6 - 7mm 1

Static control wrist strap 1 Hexagon socket 8mm for 3/8" wrench 1
Penlight, mini with head band for 1 Hexagon socket 4mm for 3/8" wrench 1
lamp holding
Side cutting plier 8160 1 Screwdriver for Bits 1
Snip nose pliers 1 Screwdriver TORX no. 8 1
Adjustable spanner l= 220mm 1 Screwdriver TORX no. 10 1
Wire stripper 0,2-6,0mm 1 Screwdriver TORX no. 15 1
RU-extractor handle, RU-extractor 1 Screwdriver TORX no. 20 1
button 35mm
Termination tool, Krone 1 Screwdriver TORX no. 25 1
Tool for cable ties 1 Screwdriver TORX no. 30 1
Slip joint plier 1 Screwdriver, 0.4x2,5x60 1
Extractor tool for QMA-connectors 1 Slotted socket 27 / 32mm 1
Multimeter 1 Nutdriver 5mm ( L=150mm) 1
Powercable tool (LTE) 1 Pen hammer 1
Socket set 3/8" 8-19mm, incl bits 1 Torx bit TT 30 1 1
Socket 16mm for 3/8" wrench 1 Clutching tongs 1
3 Summary

2 Use the Customer Product Information (CPI)
2.1 Explain the CPI library structure of the node
2.2 Find information in the CPI Library with use of regular expression
2.3 List the important documents in the CPI for maintaining a Baseband
52 based Radio Node
2.4 Locate correct OPI to solve alarms
2.5 Know what different Tool Kits exist and how to order them

Working with a Baseband Radio Node as a Field Maintenance Personnel
3 Working with a Baseband Radio Node as a

Field Maintenance Personnel
Objectives
3 Perform maintenance procedures on the node
3.1 Explain the Baseband radio node hardware architecture
3.2 Identify the Baseband radio node connection interfaces
3.3 Explain the maintenance procedures
3.4 Explain how to handle faulty units
3.5 Connect to a Baseband radio node
3.6 Learn how to install and use the EMCLI
3.7 Learn some basic commands used in EMCLI that are relevant for a Field
Maintenance personnel
3.8 Learn how to install and use the EMGUI
3.9 Learn the basic principle of the Managed Object Model (MOM)
3.10 Be able to read and explain the alarms
3.11 Interpret LEDs on the Baseband and Radio units
3.12 Extract the logs from the Baseband Radio Node

1 Overview
The Baseband 52xx based eNodeBs or nodeBs, once integrated are usually
managed from the Operation and Support System (OSS) site remotely. However,
there might be times when Field Maintenance personnel would be required to
perform operations at the site.
This chapter provides the practical aspects related to handling a Baseband 52xx
based Radio Node (BTS, nodeB or eNodeB). (BTS support is included from
G16B software only.)
In the WCDMA W16A and LTE L16A software release timeframe, the most
likely user interface with which the Baseband 52 nodes are managed is the
EMCLI. This chapter gives an introduction to the basic concepts and commands
related to handling the Baseband node relevant for Field Maintenance personnel.
TN TN
MMI B&C A Power
RI IDL EC bus GPS
LMT
DUS 41
Baseband 52xx
LMT
RI IDL MMI
SYNC TN TN EC bus Power
B&C A
Figure 3-2: Interfaces on a Baseband 52xx (compared to Digital Unit)
Note that the integration/commissioning procedure and details are not described
here.
2 Connecting the Laptop to Baseband 52xx Locally

There are two primary ways a user at the site may access the Baseband 52xx
node- as a maintenance user or as a user defined in the LDAP.
A maintenance user is a special operator. The maintenance user gets all roles for
accessing the supported Operation and Maintenance interfaces.
LDAP connectivity is not required for the maintenance user to log in.

A maintenance user can be configured for a TLS client log on 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.
The first maintenance user must be added at integration. Additional maintenance

users can be added at integration or later on.
A maintenance user can only be changed, added, or removed by other

maintenance user after integration. The last maintenance user cannot be removed.
An LDAP defined user can also login to the node, however, a connection to the
LDAP server is required. The user, when defined in the LDAP, is tied to a (set
of) role(s), which enable/prohibit how much he/she may do against the Baseband
node. These permissions to either read/write/execute various procedures are
referred to as the rules.
2.1 What is required before going to the site?

The following is expected on the laptop which will connect to the Baseband 52xx
node.
› A computer with terminal emulation software and Web-

browser
› An Ethernet cable
› An Electrostatic Discharge (ESD) wrist strap
› A USB adapter (optional)
Figure 3-3: Pre-requisites for connecting a laptop at the site
 Terminal Emulation software is required for running the EMCLI. The

Web-browser allows access to a HTML page in the Baseband node from
where logs and node management software could be downloaded.
 An Ethernet cable to connect the client computer to the LMT port;

typically, a category 5 patch cable with 8P8C modular connectors (RJ-
45) and TIA/EIA-568 A to B wiring (TSR 391 2041/250, included in
cable package NTM 503 46/100).
 An Electrostatic Discharge (ESD) wrist strap (LTT 601 136/1) is used to

protect the radio equipment.

 A USB adapter (to be used if the client computer does not have an
Ethernet connector)
Additionally, the IP address and the username/password should also be known

before leaving for the site.
2.2 Physical connection

The laptop is connected to the Baseband board as shown in the figure below:
Figure 3-4: Connecting the laptop at the site
As the figure illustrates, the Ethernet Cable connects the LMT (Local
Maintenance Terminal) port of the Baseband unit to the laptop.
2.3 IP Address
The laptop should be in the same subnet as the Baseband’s LMT port. Since there
is no serial port, this address must be known beforehand!
If one did know the IP address of the Baseband, then the IP in the laptop should
be changed to be in the same subnet as the Baseband board.
The default IP address (before integration is done) on the Baseband unit is

169.254.2.2/24. The IP address on the laptop could therefore be 169.254.2.1/24
2.4 Connection Verification

To verify that the IP and physical connectivity are fine, one can open a web-
browser to the Baseband unit, as shown in the figure below.

Figure 3-5: EMCLI Installation
This is the page (https://<IP>/em/index.html) through which the EMCLI will be

installed.
2.5 EMCLI Installation
Figure 3-6: Element Manager Launcher
The site https://<IP>/em/index.html takes one to the Element Manager Launcher.

This is the site from where the Element Management Command Line Interface
(EMCLI) may be downloaded and installed. Installation instructions are also
provided. Note that there are pre-requisites software and certificates that must be
fulfilled before being able to use the EMCLI.
The installation procedure and details are provided on the User Description
EMCLI that is available in the CPI.
Once installed, the user just has to provide the IP address (at the site, this address
would be 169.254.2.2) and the EMCLI could be pressed to start the EMCLI
session.
The installation of the EMCLI is done via the Element Management Launcher, as
explained earlier. The Cygwin application is only installed once.

Figure 3-7: EMCLI – Opening window
3 Managed Object Model (MOM) in Baseband 52xx

A Managed Object Model (MOM) is a structured collection of configuration
information that defines the Operations and Maintenance (O&M) capability on a
Managed Element (ME). The MOM is defined as a set of classes, containing
attributes representing the configuration, and actions representing the operations
that can be invoked by the user. Using a MOM allows for co-ordination of the
O&M interfaces to Ericsson network equipment. It also enables consistent
product behavior across those interfaces, because of the benefits of model driven
software development.
The MOM is a static blueprint for the creation of the actual object model. A
browsable HTML version of the MOM is delivered as part of the CPI for the ME.
A MIM (Management Information Model), in Ericsson modeling terminology, is

the XML representation of the MOM as an artifact for design or deployment use.
The Managed Object Classes (MOCs) defined in the MOM are instantiated with
real data on a deployed ME. A MOC becomes Managed Objects (MOs) also
known as MO instances, holding configuration and state data. The data is used by
the running system and stored in a database. The collection of MOs is called the
MIB. The MIB controls the configuration of an ME and its O&M functionality.
The MOs are monitored and manipulated by a management system or by a user

through the provided interfaces. The read-only attributes in the MOs describe
configuration state and operational values. The writable attributes control the
operation and configuration for the particular network resource. The model does
not define how an MO or network resource is implemented, only what can be
seen in the interface.

GUI tool; CLI tool; EMCLI; OSS
Core MP
NetConf, ECLI
MIO MIO MIO MIO
MO
EO EO EO EO EO
EO RO
EO : Entity Object
FRO: Façade Resource Object
MAO: Management Adaptation Object
RO RO RO MIO: Management Information Object
MP = Main Processor
DP= Device Processor
MP / DP
Figure 3-8: MO implementation
The MO approach allows a single common representation to be used by different

parts of the managed element (ME) that offer O&M functionality, reducing
software errors and inconsistencies. As the end user of the node, just knowing
the Managed Objects (MOs) is enough without needing to know how the
MIO/EO/RO are implemented or communicate to each other.
The figure below shows the top-level MOCs and an example of what could
contain in one of the branches (SystemFunctions).

ManagedElement
Transport NodeSupport
EquipmentSupportFunction
Equipment “ ”
NodeBFunction
SystemFunctions
ENodeBFunction
System Security Performance Software Inventory Fault

Management Management Management Management Management
ECIM Local PM Event Software File

SNMP Authorization Management Management Management
Time LDAP Subscriber + Hardware Inventory File Transfer

Management Authentication Equipment Trace Management Protocol Mgmt
Certificate HealthCheck Backup + Restore

Management Management Management
Only for illustration
Local License
Authentication Management
Figure 3-9: Managed Object Model in a Baseband 52xx Radio Node
The figure shows that at the top in the Managed Object Model (MOM) is the
MOC ManagedElement. The Transport, Equipment, SystemFunctions,
NodeSupport and EquipmentSupportFunction Managed Objects are shared by the
implementation of the any of the Radio Access Technology. The “GSM” (BSS),
NodeB (WCDMA) and eNodeB (LTE) application layer MOs are independent of
each other.
The figure above further illustrates what type of information may be represented
under one of the branches SystemFunctions.
Just like the SystemFunctions branch, another example is given below- the MOs
under the Equipment branch.

Figure 3-10: MOM Example –Hardware
The MO Class FieldReplaceableUnit represents both the Baseband unit and the
radio unit.
Managed Information Base (MIB) is the set of MOs used by the running
system on a given ME. Managing the ME using the O&M interface is achieved
by interaction with the instance model. The following operations can be
performed:
 Create and delete MOs
 Set and read the MOs and the data they hold
 Invoke operations provided by the MOs
This interaction can be done directly through the Ericsson Element Management
Command-Line Interface (EMCLI)., or through applications in the OSS.

4 GSM and WCDMA MOM (Managed Object Model)
Figure 3-11: Baseband Radio Node MOM for WCDMA
Figure 3-12: Baseband Radio Node MOM for GSM

All Abis traffic is carried in the form of LAPD frames. Thus the LAPD frames
contain both Operation and Maintenance Link (OML) and Radio Signaling Link
(RSL) signaling as well as traffic data. An LAPD frame is identified by its
Terminal Endpoint Identifier-values (TEI) and Service Access Point Identifier-
values (SAPI). The TEI-value defines Sector Central Function (SCF) or
Transceiver (TRX). The SAPI-value defines the type of information the frame
contains.
The transport profiles are used by Abis transport to setup needed transport
sessions for all unlocked TRXs in the GSM Sector. The transport sessions for one
or more TRX carry signaling (OML and RSL) and payload (CS, CSD, and PS).
An Abis transport instance is identified by its key attribute, abisIpId on MO

AbisIp , given at instance creation.
5 EMCLI
EMCLI is a text-based Operation and Maintenance (O&M) client that provides
external access to the node and the Managed Information Base (MIB) and the
Managed Object Model (MOM). EMCLI communicates with the node over a
secure channel.
EMCLI can be used from management applications in the OSS environment or

on a stand-alone laptop, for example on-site.
The EMCLI service provides a set of commands that are part of the
administrative interface. These are used to configure, manage, and maintain the
node in the network by manipulating Managed Objects (MO). It is a complement
to other management tools.
5.1 Field Maintenance commands with EMCLI

Since the EMCLI commands work with Managed Objects, the commands listed
here are some standard MO procedures on the objects that are more applicable to
Field operations.

Managed Objects
Fault Handling
Node> lt all
Node> al
Node> pr
Node> lg Performance
Node> get
dcg Node> pst
lget, hget
Node> invh Node> pgets
st
invl Node> pget
Node> set
Node> pmr
bl / deb
Documentation
Node> acc Node> mom
mcc
Node> h
Node> cr
Node> del
Figure 3-13: EMCLI Command examples
In the figure above some of the commands that EMCLI uses are shown. Note
that it is assumed that the user is allowed to execute any command, which might
not be the case.
Since the documentation command “h” is very well documented (with relevant
examples), the commands are not explained here. A detailed description could be
obtained by the command “h <command>”- for example, to find out on
how/when to use the command “mcc”, the user can type “h mcc”
6 EMGUI
Element Management Graphical User Interface or EMGUI is an element
management tool used for simple trouble shooting and is a complement to the
other management tools available. It is started from a web browser either through
Operations Support System (OSS), or through a stand-alone computer on-site.
The IP address for the node is used to contact the web server in the node.
To be able to use the tool it is necessary that user credentials and a valid
certificate for authentication are stored and imported to the browser. User
credentials are fetched by logging in to the Single Logon Server (SLS). Trusted
certificate is fetched by logging in to the Trusted certificate Distribution Point
Service (TDPS) server. A secure connection to the node is set up over HTTPS
and a small web app is downloaded from the web server on the node.
6.1 Alarm List Viewer

When entering the EMGUI, the alarm list view is visible. All the active alarms
for the node are listed in a table as shown in the figure below.

Figure 3-14: EMGUI – Alarm List View
The alarms are, by default, sorted on severity, with highest severity on top. It is
possible however to reverse the order, or to switch attribute by clicking on the
table column header.
The color code of each alarm, shown to the far left of the table, corresponds to
the severity level. This is based on the value of attribute activeSeverity in MO
FmAlarm. The alarm counter above the table shows current number of alarms of
each severity.
The table column headers represent alarm attributes containing useful

information of the alarm. What kind of information they consist of is further
explained in the MOM. The following attributes are shown:
 Fm Alarm Id
 Active Severity
 Specific Problem
 Source
 Additional Text
 Last Event Time
Each alarm has an Operating Instruction (OPI) that is named after the value of the
Specific Problem for that alarm. The OPI contains an instruction describing how
the problem raising the alarm, can be solved.
All Enum values are converted to String values according to values in the MOM.
6.2 Alarm View

The Alarm View page shows detailed information about a certain alarm, see the
figure below.

Figure 3-15: EMGUI – Alarm View
All the attributes related to the alarm are listed. The MIB data and the LDN
related to the source of the alarm are also shown. The schematic image indicates
from which hardware unit the alarm is raised from.
Automatic update of the page is not available which means that the reload button
on the browser needs to be used in order to update the web page.
7 Fault Management
A fault is the inability of a unit to perform a required function, excluding
problems that occur due to maintenance, lack of external resources, or planned
actions.
The following concepts apply to fault management:

› Fault Handling
› Detection
› Localization
› Isolation
› Recovery
› Reporting
› Alarm Handling
› External Alarms
Figure 3-16: Fault Management Overview
 Fault Handling: The RBS ability to first detect, perform

recovery attempt, and report a system fault.
 Alarm Handling: Faults that the system is unable to recover
from automatically will render an alarm. When the fault is
remedied by the operator, the alarm will be cleared and become
inactive or ceased.
 External Alarms: Alarms issued from external alarm ports for
supervision of site equipment not controlled by the RBS, for
example fire alarms or site intrusion alarms.
7.1 Fault Handling

The fault handling process includes detecting and analyzing system faults. If the
attempt to automatically resolve the issue fails, the fault is reported as an alarm.
The fault handling process in the RBS can be divided into the following basic
activities:
 Detection: Detects a failure by means of supervision or automatic test

function
 Localization: Pinpoints the failed unit
 Isolation: Takes the failed unit out of service
 Recovery: Brings the system back into normal operation by performing

an appropriate automatic recovery action, for example, a restart of a
hardware unit. (Restore Board procedure can be used for severe faults,
when other recovery attempts fail.)

 Reporting: Reports the fault using an alarm (if recovery actions were not
successful). Reporting also includes writing to appropriate logs and
handling of the optical indicators.
7.2 State Handling

An important fault management function is to propagate state values among
resources, depending on the services that are running. State handling includes
state propagation from server to client objects, to maintain a correct and
consistent view of the states of all resources in the system.
The state propagation service is primarily used to suppress alarm reports. A

resource that initially detects a fault condition, issues a primary alarm. The state
propagation service updates all dependent resources, to prevent them from
issuing primary alarms due to the same fault.
State propagation is also used to set correct state attributes in the dependent
resources, primarily for operational state and availability state.
Note: Secondary alarms may be raised on MOs EUtranCellFDD or

EUtranCellTDD, as a result of a primary equipment alarm. It is always
recommended to check for secondary alarms when a primary alarm has been
raised.
7.3 Automatic Recovery

For faults where a recovery action can resolve the issue, the node automatically
tries to recover from the fault before raising an alarm. If recovery is successful,
no alarm is generated.
The possible recovery actions include, but are not limited to, the following
actions:
 Main Processor (MP) program restart
 MP program group restart
 Field Replaceable Unit (FRU) warm restart
 FRU cold restart
 FRU cold restart with test
Enumeration RestartRank in the MOM provides information about the different

restart ranks.
For faults requiring an FRU restart as the recovery action, the node performs
three recovery attempts before raising an alarm. The purpose of having three
attempts is to limit the traffic impact of the recovery action.

If any fault appears within five minutes after each recovery action, the following
escalation sequence is performed:
 FRU warm restart
 FRU cold restart
 FRU cold restart with test
If there is more than five minutes between the fault indications, no recovery
escalation is performed.
If a user logs on to the node and any fault appears within five minutes after the
third restart attempt, alarm System General Problem is raised. The operator is
able to control the node and the automatic recovery procedure is stopped. This is
the first scenario in the figure below.
Scenario 1
Scenario 3
Scenario 2
Figure 3-17: Auto recovery
If no user logs on to the node and any fault appears within five minutes after the
third restart attempt, alarm Rollback Escalation Started is raised. If no user logs
on to the node within one hour, the node automatically restores from the latest
backup.
If any fault appears within five minutes after the start, an FRU warm restart is
performed and the escalation sequence of FRU restarts is performed again. If any
fault appears within five minutes after the third restart attempt, alarm Rollback
Escalation Started is raised. If no user logs on to the node within one hour, the
node automatically restores from the next backup according to the following list:

 Backup created after the latest upgrade
 Backup created before the latest upgrade
 No automatic restore from backup. The node is in state initial start
The node automatically restores from the next backup according to attribute
BrmBackupLabelStore.restoreEscalationList.
The automatic recovery procedure is performed until a user logs on to the node or
until the node is in state initial start. This is scenario 2 in the figure above.
The operator is able to control the node if logged on to the node within one hour
after alarm Rollback Escalation Started is raised. No automatic rollback is
performed. At user log in, alarm Rollback Escalation Started ceases, and alarm
System General Problem is raised. This is the Scenario 3 in the figure above.
7.4 Alarm Handling

The alarms are modelled through the MO FmAlarm. If this MO does not exist, it
means that there are no active alarms.
Figure 3-18: MO: FmAlarm
7.4.1 Alarm List

A summary of the active alarms can be retrieved from the node from the MO
Fm=1.

Figure 3-19: MO: Fm=1
Information included in the Fm=1 is a summary of the alarm situation in the node
at the time of giving the command.
Instead of the alarm summary, it is, of course, possible to print the alarm list-
which includes a list of individual alarms. The EMCLI command “al” or “ala” or
“alt” may be used to print the active alarms. The alarm details list (e.g from
“ala” output) contains attribute information about the specified alarm, including
source, additional text, probable cause, and so on- similar to what one gets from
the MO FmAlarm.
When the alarm is originally raised, information about the alarm is contained in
the FmAlarm.originalAdditionalText, if applicable. This is the
additional text set when the alarm was raised and it does not change during the
alarm lifetime. If applicable, updated info about the alarm is contained in the
FmAlarm.additionalText, which is updated when the alarm details change,
for example when the severity level changes. If there are no changes on the
alarm, then it has the same value as the
FmAlarm.originalAdditionalText.
7.4.2 Alarm Severity

Different alarms require different levels of attention from the operator. The
FmAlarm.activeSeverity alarm attribute is used for this purpose.
For each alarm, the severity is defined by the following attributes in MO

FmAlarmType:
 FmAlarmType.configuredSeverity - the severity level configured

by the operator. If the operator configures this, then this value overrides
any value set by the system and this is the severity level that is always
reported.
 For each raised alarm, an instance of the MO FmAlarm is created. The

severity of an active alarm is defined by the following attributes of the
respective instance of the MO FmAlarm

 FmAlarm.originalSeverity - the severity level originated when

the alarm was raised.
 FmAlarm.activeSeverity - the alarm current level of severity,

which may escalate or diminish during the lifetime of the alarm. This can
be:
o The same as the FmAlarm.originalSeverity, if the alarm

severity level was not changed by the system and if the operator
did not configure the attribute
FmAlarmType.configuredSeverity.
o The severity level set by the system during the alarm lifetime,
other than the FmAlarm.originalSeverity, if it changed
under certain circumstances and if the operator did not configure
attribute FmAlarmType.configuredSeverity.
o The same as attribute FmAlarmType.configuredSeverity,

if the operator configured this.
The following definitions are made, from the highest to lowest severity level:
Severity Guideline Examples

CRITICAL Risk of severe or permanent damage • Fire
to the node is possible (site or
equipment)
MAJOR Node is prevented from providing full • Loss of cells.
service • Problem with high
temperature
MINOR Does not affect service but corrective • Degraded cells.
action should be taken to prevent a • HW problem.
more serious fault • Problem with low
temperature.
WARNING Potential or impending fault that • Loss of redundant HW.

affects service • HW is about to fail in
the future
Figure 3-20: Alarm Severities
7.4.3 Alarm Operational Procedural Information (OPI)

Every alarm that may be raised has a corresponding Operational Procedural
Instruction (also called Operating Instructions / Alarm Instruction).
When an alarm is raised there is a field called “Specific Problem” This is the
alarm slogan and also the name of the OPI to follow to solve the alarm.
The figure below shows an OPI to solve the alarm listed earlier.

Figure 3-21: Alarm OPIs
It is always advised to read the Alarm Description section, as it explains the

possible reason for the alarm, the impact of the alarm and other related (primary
or secondary) alarms associated to the alarm being investigated.
7.4.4 Alarm Log

The Alarm Log contains all the node alarm state changes and is used to monitor
the alarms. It contains timestamps for when the alarm was raised and when it
ceased.
Figure 3-22: Alarm Log Printout- lga

With EMCLI, it is possible to use the command “lga” to look at the alarm log.
Note that this command allows the use of “time filter” to sort alarms.
8 Logs available at the site

Retrieving the logs is usually performed from the OSS site. However, in case it
is required to collect the logs at the site, there are two primary ways to do it:
› Using the EMCLI

– “dcgm”
– SFTP server must be running on the PC
› Use the Emergency Access (EA) GUI

– SFTP server must be installed/running on the PC
– “ESI package”
Figure 3-23: Collecting Logs
The Operating Instruction “Data Collection Guideline” available in the CPI

explains how exactly to collect the logs.
What type of information that may be retrieved from the log? The following
table gives a summary of the logs.
Log Name Managed Object What it contains
AiLog Log Logs all AutoIntegration events.
AvailabilityLog LogM Logs the node availability. Used

for In-Service Performance (ISP)
analysis.
AlarmLog Log Logs all alarm state changes.
AuditTrailLog Log Logs operator commands, that is

EMCLI, Ericsson CLI, and
NETCONF commands.
ESI LogM Ericsson Support Information
(ESI) package
SecurityLog Log Logs all node security violations.
SwmLog Log Software Management log.
TnApplicationLog Log Logs TN internal state and event

information.
TnNetworkLog Log Logs network events.
Figure 3-24: Logs Overview

AiLog : Logs all Auto Integration events. It is useful for troubleshooting the
integration issues.
Availability Log: Logs the node availability. Used for In-Service Performance
(ISP) analysis.
AlarmLog: Logs all alarm state changes.
Audit Trail Log: Logs operator commands, that is EMCLI, Ericsson CLI, and
NETCONF commands. All operator commands are logged, except get
operations. The get operations are:
 EMCLI command get
 Ericsson CLI command show
 NETCONF commands get and get-config
Ericsson Support Information (ESI) package: The ESI package contains logs
and other data to be used by Ericsson for analyzing the problem in case of node
failure.
Security Log: Logs all node security violations.
SwmLog: Software Management Log. It logs Software Management events, for

example upgrade and backup.
TnApplicationLog: It logs transport network internal state and event

information. It is used for troubleshooting the node.
TnNetworkLog: It logs network events. It is used for troubleshooting.
9 Backup Handling
The backup and restore function supports network maintenance. It backs up
Software version, configuration, and other data and can restore such backups.
The backups in the node can be exported to an external backup server to increase
robustness against failures in the node. The backups can be created, exported, and
deleted manually or automatically. The operator can configure automatic backups
as single, periodic, or periodic calendar-based scheduled backup events.
Housekeeping is configured for automatically and manually created backups to
limit the number of stored backups in the node.
The restore function can be manually or automatically initiated. If a system

malfunctions, backup restore is used to revert to a previous SW or data
configuration. If a system fails, backup restore is used as an automatic recovery
mechanism.

Backup and Restore functions are normally managed from the OSS. However, it
is important for a Field Engineer to understand the common procedures
associated with them. Note that there are other operations also possible which
are not listed here.
EMCLI command Short Description

>cvls List the backups in the node,
including the software info
>cvcu Display the current backup
information only
>cvmk Make a new backup
>cvrm Remove an existing backup
>cvre Restore a backup
>cvget Export a backup to the PC from
where the EMCLI is being run
>cvput Transfer a backup (zip file) from
the PC to the node.
> acc BrmFailsafeBackup To initiate the FailSafe backup
activate (or deactivate) mode (or to exit the failsafe
mode)
Figure 3-25: Backup and Restore Management (BRM) Functions
In the figure below, example of the printout from cvls and cvcu are shown.
Figure 3-26: Brm command examples: cvcu / cvls

9.1.1 Failsafe Backup Function

The failsafe backup function can be used when reconfiguring sensitive parts of
the node. The failsafe backup function protects from losing the O&M access to
the node.
Before activating the function, the operator sets a rollback timer (or 20 minutes
with default configuration). When the failsafe backup function is activated, the
system creates a temporary backup and starts the rollback timer. This backup is
used if the rollback timer expires and the system automatically restores. After an
automatic restore from backup the failsafe backup function is automatically
deactivated.
The procedure is explained in the figure below.
3. Operator changes
4. Restore if
MO set / create / delete
usageState = BUSY
1. Activate 4. Deactivate
acc BrmFailsafeBackup=1 activate acc BrmFailsafeBackup=1 deactivate
x t
db db 5. Running on
2. Backup created 5. Previously created Backup from 2.
backup deleted
e.g. Failsafe_backup_time
timeoutLength = x (1 – 86400s, 1200s default)

timeoutRemaining = timeoutLength - elapsed t
Figure 3-27: Failsafe Backup Function
If the operator has performed a successful reconfiguration, the operator

deactivates the failsafe backup function within the predefined rollback time
period.
If there is a restart while the failsafe backup function is active, the rollback timer
is stopped. After the restart the rollback timer continues the countdown.
When the failsafe backup function is deactivated, the rollback timer is stopped
and the backup created at the function activation is removed.

10 Light Emitting Diodes (LEDs) and Maintenance

Mode
The various units at the site have a number of visual indicators that suggest the
working status of the individual unit. The indicators include colored LEDs. As a
field engineer, not only are the colors important to understand, but also the way
the LEDs flash. The CPI “Indicators, Buttons, and Switches” explain the detail
on how each unit should/would flash on various modes.
A simple explanation on the Baseband 52xx would flash is shown for illustration
in the figure below.
Symbol Explanation Color States of the Interpretation

LED
Fault Red OFF / No Fault /
ON Hardware Fault
Status Yellow OFF / Normal /
ON Internal or external faults
Maintenance Blue OFF / Normal /
ON / Full Maintenance Mode /
Slow flashing / Maint Mode Initiated /
Flickering Alarm Suppressed Mode
Operational Green OFF / No Power /
ON / Operational /
Flashing or Dependent resource
Flickering missing or loading
Figure 3-28: LEDs on the Baseband Unit
As the figure indicates, a normal working Baseband 52xx Unit should have the
green LED steady- indicating it is operational. Any other state indicates a
problem.
The red LED, if present, indicates a hardware fault. Similarly, the yellow LED
should also be off.
Blue (Maintenance) LED, if lit, indicates a maintenance state. However, the way
the LED flashes indicates various modes.
10.1 Maintenance Mode

Maintenance mode is entered either by locking hardware unit (if possible for that
unit) from an Element Management tool, or by using the Maintenance button on
the unit. The Baseband Units and the (Remote) Radio Unit all have a
maintenance button to allow the field engineer to initiate hardware procedures at
the site without having to rely on the OSS personnel.
The following figure explains the result of pressing the maintenance button.

Figure 3-29: Maintenance Mode button
The figure provides a generic description of what happens when the maintenance
button is pressed in different duration.
The Baseband supports the “Technician present”, “Full Maintenance”, “HW

Reset” and “No Maintenance” states.
The radio units support “Alarm Supressed” (only in RU, not in RRU),
“Technician present” (only in RRU, not in RU), “Full Maintenance”, “HW
Reset” and “No Maintenance” modes.
10.1.1 Technician Present

The Technician Present mode and its alarm FieldTechnicianPresent, is used to
avoid remote changes of the maintenance modes when a technician is present on-
site.
As soon as the maintenance button is pressed, less than 7 seconds, the Technician
Present mode is activated.
Clear Mode

The Technician Present mode and alarm are cleared by pressing the maintenance
button, less than 7 seconds, a second time.
For RUs, the Technician Present mode is cleared automatically, if the

maintenance button is pressed for less than 2 seconds, as the RU is not entering
any mode in this case.
It is also possible to set and clear Technician Present mode and alarm through
element management tools.
10.1.2 Full Maintenance Mode (Locked)

The Full Maintenance mode (also referred to as Locked for WCDMA and LTE)
is used to suppress all traffic and all alarms in the node to be able to perform
maintenance on the unit. The board (Baseband unit or the Radio Unit) is in a
Mull Maintenance mode when the maintenance button is pressed for more than 2,
but less than 7 seconds. The blue optical indicator changes from flickering to
flashing slowly. (The maintenance button should be released during “flashing
slowly” stage- the blue optical indicator stops flashing and remains constant. The
unit is now locked and in Full Maintenance mode with Technician Present mode
active (if Technician Present mode is supported)).
10.1.3 HW Reset Mode

The HW Reset function (also referred to as Restart in WCDMA and LTE) is used
to restart the unit. If the maintenance button is pressed for more than 7 seconds,
all the optical indicators turn off and then on again for at least one second as the
unit restarts. The operator just has to release the button and wait until the green
optical indicator is constant. The unit restarts in its initial state.
11 Hardware Operations
Procedures, if not directly related to working with the hardware unit, described
here are most likely carried from the OSS domain. Of course, they may also be
performed locally at the site. The user who performs these procedures must have
the proper authority and rights to carry out these actions.
Since EMCLI is most likely to be used for reconfiguring the node, the Managed
Objects (MOs) that represent the hardware should be understood.
In the figure below, the Managed Object Classes that are under the Equipment
branch are shown.

Figure 3-30: Managed Objects related to Hardware
Adding a new unit or creating physical changes in the eNodeB and nodeB are
either creating/deleting these MOs or changing the parameters.
Figure 3-31: Antenna system

The figure above shows how the physical connection could look like from the
Baseband (shown as the DU) to the Antenna. The AIR connection is also shown.
The relation of the hardware units to the corresponding Managed Objects are
shown below.
Unit Managed Object

Baseband FieldReplaceableUnit
Baseband T FieldReplaceableUnit
Radio FieldReplaceableUnit
Baseband R FieldReplaceableUnit
AIR FieldReplaceableUnit and RET
RET AntennaNearUnit and RetSubUnit
Battery Fuse Unit (BFU) PowerDistribution and BatteryBackup
Power Distribution Unit (PDU) PowerSupply and PowerDistribution
Power Supply Unit (PSU) PowerSupply
Figure 3-32: Hardware Units vs. MO
How exactly to work (define, lock, replace) with a hardware unit is explained in
the CPI document “Manage Hardware Equipment”.
› Add Baseband › Configure Maximum Total Tilt

› Add Radio or Baseband R › Configure Minimum Total Tilt
› Lock Unit › Configure VSWR Alarm Threshold Values
› Unlock Unit › Add Iuant TMA
› Restart Unit › Delete Iuant TMA
› Replace Unit › Replace Iuant TMA
› Restore Unit › Lock Iuant TMA
› Configure Primary Node › Unlock Iuant TMA
› Configure Secondary Node › Restart luant TMA
› Reconfigure Primary Node to Secondary Node › Perform Self-Test on Iuant TMA
› Reconfigure Secondary Node to Primary Node › Add RET
› “ ” › Delete RET
› Add Support System Unit › Replace RET
› Configure Climate System and Climate System Variants › Lock RET
› Configure Multiple Support Systems in Cascaded Chain › Unlock RET
› Configure External Alarms › Restart RET
› Perform Battery Test on Shared Battery › Perform a Self-Test on RET
› Perform Battery Test on Non-Shared Battery › Calibrate RET
› Read Battery Test Results › Configure Electrical Antenna Tilt
› Examples of Battery Backup › Upload Antenna Configuration File to RET
› Add Antenna Unit › Configure Cascaded or Multiple RETs
› Delete Antenna Unit › Download Firmware on Antenna Near Unit
› Replace Antenna Unit › Configure AIR
› Add RF Branch › Configure Cascading RETs in AIR
› Configure RF Branch › Swap RET Control in AIR
› Configure Mechanical Antenna Tilt Attribute
Figure 3-33: Use Cases- Check the CPI “Manage Hardware Equipment”

Of all the uses cases described in the CPI, the following procedures are
explained- as example.
11.1 Lock a Hardware Unit

Locking the unit is often part of the procedure to act on generated alarms.
Depending on which MO is related to the alarm, lock the unit as follows:
1.Set the administrativeState attribute for the related MO to LOCKED.

The EMCLI command “bl” could be used.
> pr fieldrep > get fieldrep.*unit=2
> bl fieldrep.*=2
Radio unit!
> st fieldrep.*=2
Figure 3-34: Lock a Radio Unit
When LOCKED, the traffic on the unit is ceased and no new alarms are
generated. All alarms generated earlier by the unit are ceased. It is still possible to
perform Operation and Maintenance (O&M) on the board, provided the unit is
still installed and included in the current configuration. The optical indicators
indicate full maintenance mode. See the document “Indicators, Buttons, and
Switches”.
11.2 Unlock Unit

Unlocking the unit is often part of the procedure to act on generated alarms.
Depending on which MO is related to the alarm, unlock the unit as follows:

1.Set the administrativeState attribute for the related MO to

UNLOCKED. The EMCLI command “deb” may be used.
2.Verify that the status of the operationalState is ENABLED. Command

“st” would print the information.
If the unit is disabled, investigate the reason for this by examining the
availabilityStatus attribute, which contains details about the
operationalState.
Any active alarms on the unit are generated. The optical indicators indicate that
the unit is in operational mode. See Indicators, Buttons, and Switches.
11.3 Restart Unit

1.Initiate the restartUnit action for the attribute for the related MO and
specify RestartRank and RestartReason.
Note: Only Baseband and Baseband T supports different restart ranks.
2.If a hardware fault is suspected on the unit, select RestartRank

RESTART_COLDWTEST to start a recommended hardware test on the unit.
3.For logging reasons, enter attribute restartInfo. The attribute is an

optional free-text field where extra information can be added.
> acl fieldreplaceableUnit
> get FieldReplaceableUnit=1 > acc fieldreplaceableUnit=1 restartUnit
Baseband !
Figure 3-35: Restarting a Baseband unit

11.4 Replace Unit

1. Lock the unit first.
2. Replace the unit according to the instructions for the unit type. Be sure
to use the proper tools.
3. Unlock the unit.
12 Handling Faulty Units

What is the procedure for handling faulty equipment and replacement parts?
The Site Failure Note (SFN) must be used while handling the Faulty units and
replacement parts. (SFN replaces the previously used Repair Delivery Note
(RDN Blue Tag)). When returning a faulty unit, it is mandatory to attach a filled
out SFN.
Figure 3-36: Site Failure Note

12.1 Handling Faulty Equipment

Do not expose units to extreme temperature variations caused by, for example,
direct sunlight, or to high levels of humidity. Condensation and extreme heat can
damage hardware or lead to hardware failure. Unpack the replacement unit in the
intended operating environment.
Note: Replacement units must be kept in their ESD protective bag and original
cardboard box until they are ready to be installed at site.
Exercise care when handling units. Avoid touching components on printed

circuits or connector pins. Damage to components or connector pins can lead to
hardware failure.
Do the following:
1. Check the packing material of the replacement unit. If the packing is

damaged, check the unit. If the unit appears damaged, return it to the
service center for repair or replacement.
2. Complete the SFN, giving all the information about the suspected fault.
3. Put the filled out SFN with the hardware unit being returned to the repair
center. How exactly to fill the SFN is described in the CPI “Handling
Faulty Equipment”
4. Pack the unit suspected to be faulty in the packing material from the
replacement part in the following order:
1. ESD Bag
2. SFN
3. Shock-absorbent padding
4. Box
(Suspected)
Faulty Unit
Figure 3-37: Packing Replacement Part
1. Make sure that the outside of the box is marked “FAULTY UNIT”, and
has a list of the contents.
2. Return the packaged unit to the local Ericsson repair center, making sure
that the handling and delivery method complies with any local
procedures.

13 Preventive Maintenance
By putting an operational procedure for preventive maintenance (on hardware),
operators can avoid unexpected problems.
Depending on the type of the radio site and the equipment present there, Ericsson
has a guideline on how these preventive maintenance procedures should be
carried out. These procedures are described in the CPI.
One such example for RBS 6601 (with Baseband or Digital Unit) unit is shown in
the figure below:
Figure 3-38: Preventive Maintenance
Note that the suggested procedures for radio units, AIR, RRU are slightly
different. The maintenance intervals suggested could also vary slightly.

14 Summary
3 Perform maintenance procedures on the node
3.1 Explain the Baseband Radio Node hardware architecture
3.2 Identify the Baseband Radio Node connection interfaces
3.3 Explain the maintenance procedures
3.4 Explain how to handle faulty units
3.5 Connect to a Baseband Radio node
3.6 Learn how to install and use the EMCLI
3.7 Learn some basic commands used in EMCLI that are relevant for a Field
Maintenance personnel
3.8 Learn how to install and use the EMGUI
3.9 Learn the basic principle of the Managed Object Model (MOM)
3.10 Be able to read and explain the alarms
3.11 Interpret LEDs on the Baseband and Radio units
3.12 Extract the logs from the Baseband Radio Node

Acronyms and Abbreviations
4 Acronyms and Abbreviations
3GPP 3rd Generation Partnership Project

ACIR Adjacent Channel Interference Ratio
ACK Acknowledgement
ACLR Adjacent Channel Leakage Ratio
ACP Automatic Cell Planning
ACS Adjacent Channel Selectivity
AES Advanced Encryption Standard
AGW Access Gateway
AIF Auto-Integration Function
AIR Automated Integration of RBS
AISG Antenna Interface Standards Group
AM Acknowledged Mode
AMBR Aggregate Maximum Bit Rate
A-MPR Additional Maximum Power Reduction
ANR Automated Neighbor Relation
APAC Asia Pacific
API Application Programming Interface
APN Access Point Name
ARP Allocation and Retention Priority
ARQ Automatic Repeat Request
ARW Add RBS Wizard
AS Access Stratum
AS Application Server
A-SBG Access SBG
ASC Antenna System Controller
ASD Automatic SW Download
ASSL Adjacent Subcarrier Set Leakage
ASSR Adjacent Subcarrier Set Rejection
BCCH Broadcast Control Channel
BCH Broadcast Channel
BEM Block Edge Masks
BM-SC Broadcast-Multicast Service Center
BS Base Station
BSR Buffer Status Report
BW Bandwidth
C/I Carrier-to-Interference Power Ratio
CA Certificate Authority

CAPEX Capital Expenditure

CAZAC Constant Amplitude Zero Auto-Correlation
CCCH Common Control Channel
CCE Control Channel Elements
CDD Cyclic Delay Diversity
CDF Cumulative Distribution Function
CDMA Code Division Multiple Access
CE Carrier Ethernet
CEPT The European Conference of Postal and Telecommunications Administrations
CFR Channel Feedback Report
CM Configuration Management
CMAS Commercial Mobile Alert System
CMC Connection Mobility Control
CMDB Configuration Management Data Base
CN Core Network
COMINF Common O&M Infrastructure
CO-OP Cooperative Open-OSS Project (interface also called Itf-P2P)
CORBA Common Object Request Broker Architecture
CP Cyclic Prefix
CP Control Plane
CPC Continous Packet Connectivity
C-plane Control Plane
CQI Channel Quality Indicator
CRC Cyclic Redundancy Check
C-RNTI Cell RNTI
CS Circuit Switched
CSCF Call Session Control Function
CSFB Circuit Switched FallBack
CSV Comma-Separated Values
CTR Cell TRace
CW Codeword
CW Continuous-wave
DCCH Dedicated Control Channel
DCH Dedicated Channel
DCI Downlink Control Information
DCN Data Communication Network
DFT Discrete Fourier Transform
DFT-S-OFDM DFT Spread OFDM
DHCP Dynamic Host Configuration Protocol
DL Downlink
DL-SCH Downlink Shared Channel
DNS Domain Name Service
DRB Data Radio Bearer
DRX Discontinuous Reception
DSCP Differentiated Services Code Point
DTCH Dedicated Traffic Channel
DTX Discontinuous Transmission
DwPTS Downlink Pilot Time Slot
EBS Event Based Statistics
ECC Electronic Communications Committee
ECGI E-UTRAN Cell Global Identifier

ECM EPS Connection Management

E-DCH Enhanced DCH
EHPLMN Equivalent Home PLMN
EMEA Europe, Middle East and Africa
EMM EPS Mobility Management
eNB E-UTRAN NodeB
eNode B E-UTRAN NodeB
EPC Ericsson Policy Control
EPC Evolved Packet Core
EPS Evolved Packet System (E-UTRAN and EPC)
E-RAB E-UTRAN Radio Access Bearer
ESM EPS Subscription Manager
ETSI European Telecommunications Standards Institute
ETWS Earth Quake and Tsunami Warning System
E-UTRA Evolved UTRA
E-UTRAN Evolved UTRAN, used as synonym for LTE in the document.
EV-DO Evolution - Data Optimized
EVM Error Vector Magnitude
FCC Federal Communications Commission
FDD Frequency Division Duplex
FDM Frequency Division Multiplexing
FDMA Frequency Division Multiple Access
FEC Forward Error Correction
FFS For Further Study
FFT Fast Fourier Transform
FM Fault Management
FMX Fault Management Expert
FQDN Fully Qualified Domain Name
FS Frame Structure
FTP File Transfer Protocol
GBR Guaranteed Bit Rate
GCL Generalized Chirp Like
GE Gigabit Ethernet
GERAN GSM EDGE Radio Access Network
GINR Gain to Interference and Noise Ratio
GGSN Gateway GPRS Support Node
GMPLS Generalized Multi-Protocol Label Switching
GNSS Global Navigation Satellite System
GP Guard Period
GPRS General Packet Radio Service
GSM Global System for Mobile communication
GTP GPRS Tunneling Protocol
GTP-C GTP Control
GTP-U GTP User Data Tunneling
GUI Graphical user Interface
GUTI Globally Unique Temporary Identifier
GW Gateway
HA-CS High Availability Cluster Solution
HARQ Hybrid ARQ
HO Handover
HOM Higher Order Modulation

HPLMN Home PLMN

HRPD High Rate Packet Data
HSDPA High Speed Downlink Packet Access
HS-DSCH High Speed Downlink Shared Channel
HSPA High Speed Packet Access
HSS Home Subscriber Server
HSUPA High Speed Uplink Packet Access
HTTP Hypertext Transfer Protocol
HW Hardware
IASA Inter-Access Anchor
ICIC Inter-Cell Interference Coordination
I-CSCF Interrogating CSCF
ID Identifier
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
IFFT Inverse FFT
IMEI International Mobile Equipment Identity
IMT IP Multimedia Telephony
IMS IP Multimedia subsystem
IMSI Individual Mobile Subscriber Identity
IMT International Mobile Telecommunications
IP Internet Protocol
IRAT Inter Radio Access Technology
IS Integrated Site
ISI Inter Symbol Interference
ISM IMS Subscription Manager
ITU International Telecommunications Union
ITU-R ITU Radio communication Sector
IWS CDMA200 InterWorking Solution
JSR Java Specification Request
KPI Key Performance Indicator
LB Load Balancing
LCID Logical Channel ID
LCR Low Chip Rate
LCR-TDD Low Chip Rate TDD
LDC Linear Dispersion Code
LDPC Low-Density Parity-check Code
LED Light Emitting Diode
LTE Long Term Evolution, used as synonym for E-UTRAN in the document.
MAC Medium Access Control
MBA Management Based Activation
MBMS Multimedia Broadcast Multicast Service
MBR Maximum Bit Rate
MBSFN Multicast Broadcast Single Frequency Network
MCCH Multicast Control Channel
MCE Multi-cell/multicast Coordination Entity
MCH Multicast Channel
MCS Modulation and Coding Scheme
MEF Mobile Entertainment Forum
MGC Media Gateway Controller
MGW Media Gateway

MIB Master Information Block

MIB Management Information Base
MIMO Multiple Input Multiple Output
ML-PPP Multilink point to point protocol
MM Multi Mediation
MM Mobility Management
MME Mobility Management Entity
MMS Multimedia Messaging Service Managed Objects interface (MOCI)
MMTel Multi Media Telephony
MOCI Managed Object Configuration Interface
MOP Maximum Output Power
MPLS Multiple Protocol Label Switching
MPR Maximum Power Reduction
MS Management Services
MSAP MCH Subframe Allocation Pattern
MTAS Multimedia Telephony Application Server
MTCH Multicast Traffic Channel
MU-MIMO Multiple User-MIMO
mUPE MBMS UPE
NACK Negative Acknowledgement
NAS Non-Access Stratum
NCC Network Color Code
NCL Neighbour Cell List
NCLI Node Command Line Interface
NCS Neighbouring Cell Support
NE Network Element
NEM Network Element Manager
NGMN Next Generation Mobile Networks
NGSA Next Generation Service Assurance
NH Next Hop Key
NM Network Management
NMS Network Management System
NMX Network level deployment of expert rules
NOC Network Operations Center
NR Neighbor cell Relation
NRT Non Real Time
N-SBG Network SBG
O&M Operation and Maintenance
OAM Operations Administration and Management
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
OMC Operation and Maintenance Center
OOB Out Of Band
OPEX Operating Expenditures
OSS Operation and Support System
OSS-RC Operation and Support System Radio and Core
OTN Operator Terminal Network
P(N)CCH Paging (and Notification) Control Channel
P2P Peer-to-Peer
PA Power Amplifier
PAPR Peak to Average Power Ratio

PAR Peak to Average Ratio

PARC Per Antenna Rate Control
PBBTE Provider Backbone Bridge Traffic Engineering
PBC Power and Battery Cabinet
PBCH Physical Broadcast CHannel
PBN Packet Backbone Network
PBR Prioritized Bit Rate
PCC Policy Charging Control
PCCH Paging Control Channel
PCEF Policy Charging Enforcement Function
PCFICH Physical Control Format Indicator CHannel
PCH Paging Channel
PCI Physical Cell ID
PCRF Policy Control and Charging Rules Function
P-CSCF Proxy - Call Session Control Function
PDCCH Physical Downlink Control CHannel
PDCP Packet Data Convergence Protocol
PDN Packet Data Network
PDP Packet Data Protocol
PDSCH Physical Downlink Shared CHannel
PDSN Packet Data Serving Node is a component of a CDMA2000 mobile network
PDU Protocol Data Unit
P-GW PDN Gateway
PHICH Physical Hybrid ARQ Indicator CHannel
PHR Power Headroom Report
PHS Personal Handy-phone System
PHY Physical layer
PLMN Public Land Mobile Network
PM Performance Management
PMCH Physical Multicast CHannel
PMI Precoding Matrix Indicator
PMIP Proxy Mobile IP
PnP Plug and Play
PoP Point of Presence
PRACH Physical Random Access CHannel
PRB Physical Resource Block
P-RNTI Paging RNTI
PS Packet Switched
PSC Packet Scheduling
P-SCH Primary Synchronization Channel
PSD Power Spectrum Density
PSK Pre-Shared Keys
PSTN Public Switched Telephone Network
PTT Push to Talk
PUCCH Physical Uplink Control CHannel
PUSCH Physical Uplink Shared Channel
QAM Quadrature Amplitude Modulation
QCI QoS Class Identifier
QoS Quality of Service
QPP Quadrature Permutation Polynomial
QPSK Quadrature Phase Shift Keying

RA Random Access
RA Registration Authority
RAC Radio Admission Control
RACH Random Access Channel
RAN Radio Access Network
RANAP RAN Application Part
RA-RNTI Random Access RNTI
RAT Radio Access Technology
RB Radio Bearer
RB Resource Block
RBC Radio Bearer Control
RBG Radio Bearer Group
RBS Radio Base Station
RET Remote Electrical Tilt
RF Radio Frequency
RFC Request For Comment
RI Rank Indicator
RLC Radio Link Control
RM Rate Matching
RNC Radio Network Controller
RNL Radio Network Layer
RNTI Radio Network Temporary Identifier
ROHC Robust Header Compression
ROP Recording Output Periods
RPLMN Registered PLMN
RRC Radio Resource Control
RRM Radio Resource Management
RRU Radio Remote Unit
RS Reference Symbols
RS Reference Signal
RSN Retransmission SN
RT Real Time
RTCP RTP Control Protocol
RTP Real Time Transport Protocol
RTSP Real Time Streaming Protocol
RU Resource Unit
RX Receiver
S1-MME S1 for the control plane
S1-U S1 for the user plane
SAE System Architecture Evolution
SAP Service Access Point
SB Scheduling Block
SBC Session Border Controller
SBG Session Border Gateway
SCCH Shared Control Channel
SCCP Signaling Connection Control Part
SCEP Simple Certificate Enrolment Protocol
SC-FDMA Single Carrier – Frequency Division Multiple Access
SCH Synchronization Channel
S-CSCF Serving CSCF
SCTP Streaming Control Transmission Protocol

SDF Service Data Flow

SDH Synchronous Digital Hierarchy
SDMA Spatial Division Multiple Access
SDP Session Description Protocol
SDU Service Data Unit
SeGW Security Gateway
SEM Spectrum Emission Mask
SFN System Frame Number
SFP Small Form factor Pluggable
S-FTP Secure File transfer protocol
SGSN Serving GPRS Support Node
S-GW Serving Gateway
SI System Information
SIB System Information Block
SINR Signal to Interference and Noise Ratio
SIP Session Initiation Protocol
SI-RNTI System Info RNTI
SISO Single Input Single Output
SLA Service Level Agreement
SLO Service Level Objectives
SM Session Management
SMO Software Manager Organizer
SMRS Software Management Repository
SMS Short Message Service
SN Sequence Number
SNF Service Network Framework
SNR Signal to Noise Ratio
SON Self Organizing Networks
SOX Simple Outline XML
S-PARC Selective PARC
SPID Subscriber Profile ID for RAT/Frequency Priority
SQL Structured Query Language
SR Scheduling Request
SRB Signaling Radio Bearer
SRVCC Single Radio Voice Call Continuity
S-SCH Secondary Synchronization Channel
SSH Secure Shell
SSL Secure Sockets Layer
SSLIOP IIOP over SSL
SU Scheduling Unit
SU-MIMO Single-User MIMO
SW Soft Ware
TA Tracking Area
TAS Telephony Application Server
TAU Tracking Area Update
TB Transport Block
TBD To Be Decided
TCP Transmission Control Protocol
TDD Time Division Duplex
TF Transport Format
TFCI Transport Format Combination Indicator

TFP Traffic Forwarding Policy

TFT Traffic Flow Template
TLA Three Letter Acronym
TLP TEMS LinkPlanner
TM Transparent Mode
TMA Tower Mounted Amplifier
TMO T-Mobile International AG
TNL Transport Network Layer
TPC Transmit Power Control
TSP Ericsson Telecom Server Platform
TTI Transmission Time Interval
TX Transmitter
UCI Uplink Control Information
UE User Equipment
UETR UE TRace
UL Uplink
UL-SCH Uplink Shared Channel
UM Unacknowledged Mode
UMTS Universal Mobile Telecommunication System
UP User Plane
UPE User Plane Entity
U-plane User plane
UpPTS Uplink Pilot Time Slot
URA UTRAN Routing Area
UTRA UMTS Terrestrial Radio Access
UTRAN UMTS Terrestrial Radio Access Network
VoIP Voice over IP
VPLMN Visited PLMN
VRB Virtual Resource Block
WAP Wireless Access Protocol
WAPECS Wireless Access Policy for Electronic Communications Services
WCDMA Wideband Code Division Multiple Access
WDM Wavelength Division Multiplexing
X2-C X2-Control plane
X2-U X2-User plane
XML Extensible Markup Language
1XRTT operating mode of CDMA2000
1x (the number of 1.25MHz channels) Radio Transmission Technology

Intentionally Blank

Index
5 Index
3rd Generation Partnership Project, 13, 19 Multiple Input Multiple Output, 21

Antenna, 42 Network Element, 12
Antenna XE "Antenna" Interface XE Operation and Maintenance, 11, 12, 13, 14,
"Interface" Standards Group, 42 19, 21, 22, 24, 38, 51, 64, 65, 67, 69, 83,
Automated Integration of RBS, 36, 37, 88, 93 89
Circuit Switched, 69 Operation and Support System, 11, 12, 13,
Code Division Multiple Access, 11 14, 24, 43, 60, 67, 69, 70, 80, 82, 84, 86
Common O&M Infrastructure, 11, 13, 14 Operation and Support System Radio XE
Core Network, 11 "Radio" and Core, 11, 12, 13, 14, 24
Downlink, 42 Packet Switched, 69
E-UTRAN NodeB, 13 Radio, 3, 9, 10, 11, 12, 13, 14, 17, 18, 20, 24,
Evolution - Data Optimized, 11 28, 29, 30, 36, 37, 41, 42, 43, 44, 48, 49,
Evolved UTRA, 14 50, 52, 56, 57, 73, 85, 93
Evolved UTRAN, used as synonym for LTE in Radio XE "Radio" Access Network, 3, 10,
the document., 14 11, 12, 13, 18, 20, 24, 28, 29, 30, 49, 50
Extensible Markup Language, 64 Radio XE "Radio" Base Station, 3, 9, 11, 12,
Frequency Division Duplex, 15, 16, 21, 22 13, 14, 17, 36, 37, 42, 43, 48, 49, 52, 56,
Global System for Mobile communication, 3, 57, 73, 93
4, 10, 11, 14, 15, 16, 19, 20, 21, 22, 49, 50, Radio XE "Radio" Frequency, 41, 42, 43
51, 66, 68, 69 Radio XE "Radio" Network Controller, 11, 12
Hardware, 5, 85, 86 Radio XE "Radio" Remote Unit, 44, 85, 93
High Speed Packet Access, 15, 16 Receiver, 22, 23, 36, 43, 45
Integrated Site, 48 Reference Signal, 42
Interface, 42 Reference Symbols, 42
Internet Protocol, 4, 11, 12, 13, 14, 19, 21, Remote Electrical Tilt, 36, 42, 43, 44
24, 62, 63, 70 Resource Unit, 43, 58, 85, 86
Light Emitting Diode, 84 Secure Shell, 61
Long Term Evolution, used as synonym for Self Organizing Networks, 17
E-UTRAN in the document., 3, 10, 13, 14, Soft Ware, 81
15, 16, 19, 20, 21, 22, 28, 41, 49, 50, 51, System Frame Number, 91, 92
58, 60, 66, 86 Time Division Duplex, 15, 16, 21, 22
Management Information Base, 64, 67, 69, Tower Mounted Amplifier, 41, 42, 43, 44, 45
72 Transmitter, 22, 36, 41, 45
Management Services, 11 Universal Mobile Telecommunication System,
Master Information Block, 64, 67, 69, 72 11, 42

Uplink, 30, 42 Wideband Code Division Multiple Access, 3,

User Equipment, 12, 13 4, 10, 11, 12, 13, 14, 16, 19, 20, 21, 22, 49,
50, 51, 60, 66, 68, 86

Table of Figures
6 Table of Figures
Figure 1-1: Objectives of Chapter 1 ................................................................................................ 7

Figure 1-2: GSM RAN Overview ..................................................................................................... 8
Figure 1-3: WCDMA RAN Overview.............................................................................................. 10
Figure 1-4: LTE RAN Overview ..................................................................................................... 11
Figure 1-5: Radio Trends .............................................................................................................. 12
Figure 1-6: 3xMulti Networks......................................................................................................... 13
Figure 1-7: 3xMulti Solutions ......................................................................................................... 14
Figure 1-8: Ericsson Radio System ............................................................................................... 15
Figure 1-9: Baseband portfolio ...................................................................................................... 17
Figure 1-10: Enhanced Baseband portfolio ................................................................................... 18
Figure 1-11: High Capacity Baseband........................................................................................... 19
Figure 1-12: Baseband 5212 ......................................................................................................... 20
Figure 1-13: Baseband 5216 ......................................................................................................... 21
Figure 1-14: Baseband R503 ........................................................................................................ 21
Figure 1-15: Baseband T605 Transmission capabilities ................................................................ 22
Figure 1-16: Baseband 6630/6620 ................................................................................................ 23
Figure 1-17: Baseband 6320 and 6330 Front Panel Interfaces ..................................................... 24
Figure 1-18: Comparison ............................................................................................................. 24
Figure 1-19: Baseband 6502 – MICRO ......................................................................................... 25
Figure 1-20: Baseband 6303 – MACRO ........................................................................................ 26
Figure 1-21: 63-series (zero footprint) .......................................................................................... 26
Figure 1-22: New Baseband C608 ................................................................................................ 27
Figure 1-23: Elastic RAN: small hub > 2 x Baseband 5216 ........................................................... 28
Figure 1-24: New Baseband P614 ................................................................................................ 29
Figure 1-25: A Passive intermodulation (PIM) Mitigation Unit ........................................................ 30
Figure 1-26: Passive Intermodulation (PIM) Mitigation .................................................................. 30
Figure 1-27: Ericsson Radio System Radio ................................................................................... 31
Figure 1-28: Radio that Fit ............................................................................................................ 31
Figure 1-29: Rail System............................................................................................................... 32
Figure 1-30: Micro Radio............................................................................................................... 33
Figure 1-31: Radio Unit/Remote Radio Unit Multi-Standard (R/RRUS) ......................................... 34
Figure 1-32: Antenna Integrated Radio (AIR) ................................................................................ 35
Figure 1-33: Baseband Main Unit 6601 ......................................................................................... 35
Figure 1-34: Ericsson Radio System Software .............................................................................. 36
Figure 1-35: What can one find in a site? ...................................................................................... 36
Figure 1-36: A macro site example ............................................................................................... 37
Figure 1-37: Energy Systems and Batteries .................................................................................. 37
Figure 1-38: Antenna Systems ...................................................................................................... 38

Figure 1-39: Antennas & Near Products........................................................................................ 39

Figure 1-40: Tower Mounted Amplifier (TMA) ............................................................................... 40
Figure 1-41: Remote Electrical Tilt, RET ....................................................................................... 42
Figure 1-42: Psi Coverage ............................................................................................................ 43
Figure 1-43: Summary of Chapter 1 .............................................................................................. 44
Figure 2-1: Objectives of Chapter 2 .............................................................................................. 45
Figure 2-2: What is CPI? ............................................................................................................... 47
Figure 2-3: Active Library Explorer (ALEX) structure in RAN ......................................................... 47
Figure 2-4: Baseband Radio Node Libraries ................................................................................. 48
Figure 2-5: CPI Library Structure .................................................................................................. 49
Figure 2-6: Search in ALEX .......................................................................................................... 50
Figure 2-7: Managed Object Model (MOM) ................................................................................... 51
Figure 2-8: Hardware Management .............................................................................................. 52
Figure 2-9: Alarm Management..................................................................................................... 53
Figure 2-10: Tools - How to order ................................................................................................. 53
Figure 2-11: Ericsson Tool Kits ..................................................................................................... 54
Figure 2-12: Tool set for Installation .............................................................................................. 54
Figure 2-13: Tool set for Maintenance........................................................................................... 55
Figure 3-1: Objectives of Chapter 3 .............................................................................................. 57
Figure 3-2: Interfaces on a Baseband 52xx (compared to Digital Unit) .......................................... 58
Figure 3-3: Pre-requisites for connecting a laptop at the site ......................................................... 59
Figure 3-4: Connecting the laptop at the site ................................................................................. 60
Figure 3-5: EMCLI Installation ....................................................................................................... 61
Figure 3-6: Element Manager Launcher ........................................................................................ 61
Figure 3-7: EMCLI – Opening window........................................................................................... 62
Figure 3-8: MO implementation ..................................................................................................... 63
Figure 3-9: Managed Object Model in a Baseband 52xx Radio Node ........................................... 64
Figure 3-10: MOM Example –Hardware ........................................................................................ 65
Figure 3-11: Baseband Radio Node MOM for WCDMA................................................................. 66
Figure 3-12: Baseband Radio Node MOM for GSM ...................................................................... 66
Figure 3-13: EMCLI Command examples ..................................................................................... 68
Figure 3-14: EMGUI – Alarm List View.......................................................................................... 69
Figure 3-15: EMGUI – Alarm View ................................................................................................ 70
Figure 3-16: Fault Management Overview .................................................................................... 71
Figure 3-17: Auto recovery............................................................................................................ 73
Figure 3-18: MO: FmAlarm ........................................................................................................... 74
Figure 3-19: MO: Fm=1................................................................................................................. 75
Figure 3-20: Alarm Severities ........................................................................................................ 76
Figure 3-21: Alarm OPIs ............................................................................................................... 77
Figure 3-22: Alarm Log Printout- lga ............................................................................................. 77
Figure 3-23: Collecting Logs ......................................................................................................... 78
Figure 3-24: Logs Overview .......................................................................................................... 78
Figure 3-25: Backup and Restore Management (BRM) Functions ................................................ 80
Figure 3-26: Brm command examples: cvcu / cvls ....................................................................... 80
Figure 3-27: Failsafe Backup Function .......................................................................................... 81
Figure 3-28: LEDs on the Baseband Unit ...................................................................................... 82
Figure 3-29: Maintenance Mode button......................................................................................... 83
Figure 3-30: Managed Objects related to Hardware ...................................................................... 85
Figure 3-31: Antenna system ........................................................................................................ 85
Figure 3-32: Hardware Units vs. MO ............................................................................................. 86
Figure 3-33: Use Cases- “ q ” ..................................... 86

Table of Figures
Figure 3-34: Lock a Radio Unit...................................................................................................... 87

Figure 3-35: Restarting a Baseband unit ....................................................................................... 88
Figure 3-36: Site Failure Note ....................................................................................................... 89
Figure 3-37: Packing Replacement Part........................................................................................ 90
Figure 3-38: Preventive Maintenance............................................................................................ 91

Intentionally Blank

LZT1381958 - Field Maintenance

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LZT1381958 - Field Maintenance

Uploaded by

Copyright:

Available Formats

Baseband Radio Node - Field

This book is a training document and contains simplifications.

The contents of this document are subject to revision without notice

This document is not intended to replace the technical

This document was produced by Ericsson.

 The book is to be used for training purposes only and it is strictly

-2 - © Ericsson AB 2017 LZT1381958 R1A

1 RADIO ACCESS NETWORK, ERICSSON RADIO SYSTEM

2 MOBILE STANDARDS ..................................................................... 8

2.1 GSM RAN SYSTEM INTRODUCTION ........................................... 8

2.1.1 GSM RAN SYSTEM .................................................................... 9

2.2 WCDMA RAN SYSTEM INTRODUCTION ..................................... 9

2.2.1 WCDMA RAN SYSTEM ............................................................ 10

2.3 LTE SYSTEM INTRODUCTION................................................... 11

2.3.1 LTE RAN SYSTEMS ................................................................. 11

3 RADIO TRENDS ............................................................................. 12

4 ERICSSON RADIO SYSTEM (ERS) ............................................... 15

4.1 ERICSSON RADIO SYSTEM HARDWARE ................................. 16

4.1.1 FEATURES OF NEW BASEBAND AND RADIO

4.1.2 BASEBAND 6620 AND BASEBAND 6630 ................................ 23

4.1.3 BASEBAND 6502 ...................................................................... 25

4.1.4 BASEBAND 6303 ...................................................................... 25

4.1.5 BASEBAND C608 ..................................................................... 27

4.1.6 BASEBAND P614 ..................................................................... 28

4.1.8 ENCLOSURE FOR THE BASEBAND 52XX UNIT .................... 35

4.2 ERICSSON RADIO SYSTEM SOFTWARE ARCHITECTURE ..... 36

5 OTHER EQUIPMENT AT A RADIO NODE SITE ............................ 36

2 CUSTOMER PRODUCT INFORMATION ........................................ 45

LZT1381958 R1A © Ericsson AB 2017 -3 -

1 CUSTOMER PRODUCT INFORMATION ....................................... 46

1.1 CPI FOR BASEBAND BASED RADIO NODE- WHERE TO

1.2 CPI STRUCTURE ........................................................................ 48

1.2.1 THE SEARCH FUNCTION ........................................................ 49

1.2.2 HARDWARE RELATED CPI DOCUMENTS ............................. 51

1.2.3 ALARM RELATED CPI DOCUMENTS ...................................... 52

2 TOOL KITS ..................................................................................... 53

2.1 MAINTENANCE TOOL SET......................................................... 55

3 WORKING WITH A BASEBAND RADIO NODE AS A FIELD

2 CONNECTING THE LAPTOP TO BASEBAND 52XX LOCALLY .... 58

2.1 WHAT IS REQUIRED BEFORE GOING TO THE SITE? ............. 59

2.2 PHYSICAL CONNECTION .......................................................... 60

2.3 IP ADDRESS ............................................................................... 60

2.4 CONNECTION VERIFICATION ................................................... 60

2.5 EMCLI INSTALLATION ................................................................ 61

3 MANAGED OBJECT MODEL (MOM) IN BASEBAND 52XX ........... 62

4 GSM AND WCDMA MOM (MANAGED OBJECT MODEL) ............. 66

5.1 FIELD MAINTENANCE COMMANDS WITH EMCLI .................... 67

6.1 ALARM LIST VIEWER ................................................................. 68

6.2 ALARM VIEW .............................................................................. 69

7 FAULT MANAGEMENT .................................................................. 70

7.1 FAULT HANDLING ...................................................................... 71

-4 - © Ericsson AB 2017 LZT1381958 R1A

7.2 STATE HANDLING ...................................................................... 72

7.3 AUTOMATIC RECOVERY ........................................................... 72

7.4 ALARM HANDLING ..................................................................... 74

7.4.1 ALARM LIST ............................................................................. 74

7.4.2 ALARM SEVERITY ................................................................... 75

7.4.3 ALARM OPERATIONAL PROCEDURAL INFORMATION

7.4.4 ALARM LOG ............................................................................. 77

8 LOGS AVAILABLE AT THE SITE ................................................... 78

9 BACKUP HANDLING ...................................................................... 79

9.1.1 FAILSAFE BACKUP FUNCTION .............................................. 81

10 LIGHT EMITTING DIODES (LEDS) AND MAINTENANCE