Add RBS

DESCRIPTION

16/1551-HSC 105 50/1 Uen C1

Copyright

© Ericsson AB 2009–2011. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued 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.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 Contents

Contents

1 Introduction 1

2 RBS Autointegration Process 3

2.1 Prerequisites 6
2.2 Autointegration Process Stages 7
2.2.1 Template Preparations 7
2.2.2 Adding RBSs Using BSIM 8
2.2.3 Configuration Data Processing 9
2.2.4 Operation and Maintenance Connection Establishment and
Site Equipment Configuration 10
2.2.5 Configuration from OSS-RC 11
2.2.6 S1 Control Plane Establishment 11
2.2.7 Unlocking of Cells 12
2.2.8 Configuration Finished Notification 12
2.2.9 RBS Integrated and Activated 12
2.2.10 Configuration Backup 12
2.2.11 Testing RBSs 12
2.2.12 Completing the Security Configuration 13
2.2.13 Activating Licensed Features 13
2.3 Alternative Scenarios 13
2.3.1 License Key File Not Available 13
2.3.2 Transport Network Not Available 14
2.3.3 Field Technician Leaves Before Process Completed 14
2.3.4 Integration Cancelled 14
2.3.5 BSIM Not Used 14

3 Semi-Automated Integration Process 15

3.1 Prerequisites 17
3.2 Semi-Automated Integration Process Stages 18
3.2.1 OSS-RC Preparation 18
3.2.2 Configuration Files Preparation 20
3.2.3 Operation and Maintenance Connection Establishment and
Site Equipment Configuration 20
3.2.4 Downloading Security Related Files 22
3.2.5 Activating Licensed Features 22
3.2.6 S1 Configuration 22
3.2.7 Cell Network Configuration 22
3.2.8 Unlocking of Cells 23
3.2.9 RBS Integrated and Activated 23
3.2.10 Configuration Backup 23
3.2.11 Testing RBSs 23
3.3 Alternative Scenarios 23
3.3.1 License Key File Not Available 24

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

Add RBS

3.3.2 Transport Network Not Available 24

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 Introduction

1 Introduction

This document gives overviews of two alternative processes for integrating

RBSs with LTE networks:

• Adding RBSs using RBS autointegration

• Adding RBSs using semi-automated integration

Activities on the Operations Support System – Radio and Core (OSS-RC) and
at RBS sites are covered, and there are references to detailed instructions for
procedures. The integration process starts when configuration data is planned
but not defined in OSS-RC, and when the RBS hardware is installed at site
but not configured.

When the integration is completed the cells in the integrated RBS are unlocked
and ready to carry traffic.

Integrating an RBS includes setting the RBS parameters for:

• Management (operation and maintenance) communication

• RBS equipment configuration

• Interfacing site equipment

• The IP-transport network interfaces

• The radio network

• Security

• Licenses

Autointegration and Semi-Automated Integration Compared

The differences between autointegration and semi-automated integration are

summarized in Table 1:

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 1

Add RBS

Table 1 Autointegration and Semi-Automated Integration Compared

Type of RBS Integration Description
Autointegration OSS-RC stores configuration files for
automated download and activation in RBSs.
The integration is initiated by a technician at
site with a minimized amount of configuration
data.
With BSIM, Autointegration proceeds until the
cells are unlocked without intervention from
any personnel. Staff at OSS-RC are involved
only for planning and data preparation.
Preparations are performed from one tool
simplifying the activities for the user. The
generation and storage of the configuration
files are automated.
Semi-Automated integration RBS configuration files are prepared manually
and must be brought to site and loaded at site.
Staff at OSS-RC use several tools for data
preparation and preconfiguration.
After the configuration files are entered and
activated at site the OSS-RC staff must initiate
several stages of the integration before cells
are unlocked.

2 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 RBS Autointegration Process

2 RBS Autointegration Process

This section describes the overall process for RBS autointegration, including
prerequisites and references to detailed procedures for different stages. For an
overview of the autointegration functions, including parameters and services,
see document RBS Autointegration.

Figure 1 shows stages initiated by users and stages automated with information
exchanged between nodes in the system. Although not shown in the figure,
users are continuously notified about the progress of the process through the
Integrate RBS application and OSS-RC. Continuous lines indicate stages
always part of the process while broken lines indicate optional stages.

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 3

Add RBS

Integration OMC Field Integrate

Engineer Technician Technician OSS-RC RBS RBS MME SGW

1
2
3
4a 4b
4c
4d
4e
4f
4g
4h
4i
4j
4k
5
6
7
8
9
10
11a
11b

12
13
L0000046E

Figure 1 Stages of RBS Autointegration

Key to Figure

1 Template Preparations

2 Adding RBSs using Base Station Integration Manager (BSIM)

3 Configuration Data Processing

4 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 RBS Autointegration Process

4 Operation and Maintenance Connection Establishment and Site Equipment

Configuration:

a Autointegration initiation

b Initial parameter settings

c Internet Protocol (IP) parameters over Dynamic Host Configuration

Protocol (DHCP)

d Configuration files download

e Software upgrade

f License Key File (LKF) installation

g Preparation of security activation

h Site basic configuration activation

i Site equipment configuration activation

j Security activation

k OSS-RC Managed Information Base (MIB) synchronization

5 Configuration from OSS-RC

6 S1 Control Plane Establishment

7 Unlocking of Cells

8 Configuration Finished Notification

9 RBS Integrated and Activated

10 Configuration Backup

11 Testing RBSs

a Performing tests

b Store test record

12 Completing the Security Configuration

13 Activating Licensed Features

14 Integration Completed

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 5

Add RBS

2.1 Prerequisites
To add an RBS to the network using RBS autointegration, the following
conditions must be met:

• The license for BSIM in OSS-RC is installed and activated, see the
OSS-RC document License Key Administration in OSS-RC.

• Synchronization information over Network Time Protocol (NTP) is available;

not necessary for RBSs synchronized by Global Positioning System (GPS)
equipment.

• All services to use in OSS-RC are up and running and ready to be

accessed:

0 Active Library Explorer (ALEX)

0 BSIM

0 Common Explorer

0 DHCP server if basic IP configuration is distributed over DHCP

(alternatively a third-party product)

0 Domain Name System (DNS) (alternatively a third-party product)

0 Software Management Repository Services (SMRS) with individual

user accounts

• Additional services in OSS-RC are available depending on security

configuration:

0 Operation and Maintenance Security Administration Server (OMSAS)

0 Security Configuration Service (SCS)

0 Single Logon Server (SLS)

• The RBS is planned:

0 There is data for radio network and transport network configuration.

0 The transport network data contains IPsec related information such

as RBS inner IP addresses to configure integrated IP security for S1
and X2 (if IPsec is used).

0 There is data for neighboring LTE cells and for X2 connections to

neighboring LTE RBSs.

0 An LKF is prepared if there are licenses to be installed (no LKF

required if integration unlock is used for temporary access to features
and capacity).

0 An Upgrade Package (UP) is available if software must be upgraded.

6 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 RBS Autointegration Process

0 Antenna feeder delays and attenuations are calculated.

• Serving Gateway (SGW) nodes and the Mobility Management Entity (MME)
nodes are installed, enabled, and prepared with S1 termination points; DNS
resolution for MME IP addresses are entered in DNSs.

• MMEs are prepared with tracking areas.

• The transport network is available for Operations and Maintenance (O&M)

traffic, control plane traffic, and user plane traffic.

• The physical installations of all RBS hardware including antenna system

and power supply are completed and verified.

2.2 Autointegration Process Stages

This section describes the stages outlined in Figure 1.

2.2.1 Template Preparations

The integration engineer prepares the templates for configuration files. The
templates hold the network specific configuration data common for a large
number of RBS nodes, see indication 1 in Figure 2. In most cases, preparing
templates means making small adjustments to templates delivered with BSIM.
Existing templates can often be used when adding RBSs. In this event this
stage can be omitted.

To prepare templates, see the OSS-RC document OSS Utility Services, User
Guide.

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 7

Add RBS

OSS-RC
ONRM

SCS
Template files
1 3

OMSAS
2
BSIM
SMRS
4
DNS DHCP
Integration
Engineer

L0000099C

Figure 2 OSS-RC Preparations with BSIM

2.2.2 Adding RBSs Using BSIM

The integration engineer adds RBS configuration data to OSS-RC using BSIM
in OSS-RC, see indication 2 in Figure 2.

As a first step, the integration engineer selects a plan to reuse or specifies

the name of a plan for BSIM to create. Next the integration engineer adds
RBSs to the plan. Configuration data for RBSs is defined based on selected
template files containing parameter values and indications to request values in
the BSIM user interfaces. Configuration data for the transport network and the
radio network can, as an alternative to configuration template files, be defined
with bulk Configuration Management (CM) configuration files imported from an
external planning tool.

For each RBS there are also a number of options controlling what is, or is not,
included in the integration scenario:

• Automated or manual unlocking of cells

• Automated backup (configuration version) after integration

• Automated software upgrade of RBS

• Automated installation of licenses

• Automated activation of security level 2 or level 3

• Automated activation of integrated IP security for S1 and X2

8 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 RBS Autointegration Process

Configuration data processing starts when the integration engineer selects

in BSIM to prepare the RBSs for autointegration after having defined the
configuration data.

To add RBSs with BSIM, see the OSS-RC document BSIM, Base Station
Integration Manager, User Guide.

The integration engineer also prepares a DNS server with DNS resolution for
MMEs and eNodeBs, see RBS Autointegration.

2.2.3 Configuration Data Processing

BSIM in OSS-RC processes the input and uses services in the OSS-RC
infrastructure to prepare data and make it available for RBSs, see indication 3
in Figure 2. This includes the following automated processing:

• BSIM checks that all mandatory input data and files are present

• BSIM defines the RBSs and cells, and adds the information to the OSS-RC
Network Resource Model (ONRM)

• OMSAS creates security certificates enrollment data and stores an Initial

Security Container File (ISCF) on SMRS; the Security Configuration Service
(SCS) coordinates the communication between BSIM, ONRM, and OMSAS

• BSIM compiles parameter files for DNS servers

• If configuration over DHCP is used, then BSIM creates and stores RBS
parameters in DHCP servers, or, if third-party products are used for these
servers, compiles configuration files with the parameters

• BSIM creates and stores transport network data and radio network data for
each RBS in a planned area

• BSIM creates and stores configuration data for O&M communication and
RBS equipment on the SMRS, see document Configuration Files

• BSIM prepares the OSS-RC master server with an RBS site installation file
for each RBS; the files must be copied to be available at the RBS sites for
initiation of the autointegration; configuration over DHCP is an alternative to
site installation files

• The OSS-RC performance management support service updates the

statistics profiles and cell trace profiles with the new RBSs to be monitored

• BSIM listens for RBS notifications on the node discovery interface

BSIM shows the progress for the operator throughout the process. BSIM also
makes the result of each autointegration available for the operator in a log file.

These OSS-RC preparations can be done at any time before the integration
activities at RBS-sites start.

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 9

Add RBS

The DHCP server can alternatively be third-party products outside OSS-RC,

in which case BSIM exports configuration files for transferring configuration
data to the server.

When finished, the List of Network Elements in OSS-RC indicates RBSs

ready to be integrated.

2.2.4 Operation and Maintenance Connection Establishment and Site

Equipment Configuration
This stage is initiated by a field technician at the RBS site. When initiated a
number of automated steps establishes the O&M connection, upgrades the
software, installs licenses, activates security, and configures the site equipment.
The Integrate RBS application displays the progress of the automated steps.

This stage is divided in the following steps:

a The field technician initiates autointegration using the Integrate RBS

application, see document Integrating RBSs On-Site.

b The Integrate RBS application configures the RBS with the specified
IP configuration data by creating Managed Objects (MOs) and setting
attributes on MOs.

c If any IP parameter is not supplied by the field technician, then the RBS
retrieves data prepared on a DHCP server.

d The Autointegration RBS Summary file, Site Basic, and Site Equipment
files are obtained from the Software Management Repository Services
(SMRS) server in OSS-RC and stored on the RBS. Also, an ISCF, UP, and
an LKF are obtained if specified in the Autointegration RBS Summary file.

e If an UP is specified in the Autointegration RBS Summary file, then the

RBS is upgraded with this UP.

f If an LKF is specified in the Autointegration RBS Summary file, then it is

installed.

g If an ISCF is specified in the Autointegration RBS Summary file, then the

RBS prepares activation of S1 and X2 security (IPsec), and O&M security
based on the file. This includes the RBS sending certificate enrollment
requests to OMSAS in OSS-RC. OMSAS returns signed security certificates
to the RBS that installs them. This proceeds in parallel with steps below.

h The site basic configuration is activated by creating MOs and setting

attributes on MOs. Based on the site basic file this includes configuring the:

0 S1 and X2 interface including IPsec

0 Synchronization of real-time clock and system clock

0 Communication with various O&M servers

10 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 RBS Autointegration Process

i The site equipment configuration is activated by creating MOs and setting

attributes on MOs. This includes configuration of the following resources
based on the site equipment file and available licenses:

0 Antenna Line Device Configuration

0 Antenna system basic configuration

0 Cascaded RET Support

0 Radio units

0 RET Support

0 Support system

0 TMA Support

0 VSWR Antenna Supervision

j The RBS activates the prepared O&M security level. A successful

activation results in the wanted security level. That is, attributes
requestedSecurityLevel and operationalSecurityLevel have
the same value. Alternatively at least the minimum security level is
activated. The wanted and minimum security levels are provided during
preparations with BSIM.

If activation of the minimum security level fails, then the RBS repeats the
security preparation including retrieving an ISCF from SMRS.

k The RBS notifies OSS-RC that it is up and running. The RBS sends the
notification to different node discovery interfaces in OSS-RC depending
on security level.

OSS-RC starts synchronizing the MIB with the RBS.

2.2.5 Configuration from OSS-RC

OSS-RC configures the RBS termination points for S1 control and user plane,
the RBS termination points for X2 control plane, defines cells, defines internal
and external neighboring cells, and activates profiles with counters and cell
traces to run in the RBS. No human intervention is required.

2.2.6 S1 Control Plane Establishment

The connection of the RBS to the MME is established based on the completed
configuration. No human intervention is required.

This stage runs in parallel with the previous stage and can be completed before
the configuration from OSS-RC is completed.

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 11

Add RBS

2.2.7 Unlocking of Cells

OSS-RC activates the added RBS by unlocking the cells making them available
for user plane traffic.

When OSS-RC is prepared the integration engineer can choose to have cells
unlocked or locked as a result of the integration.

2.2.8 Configuration Finished Notification

The Integrate RBS application displays a pop-up window informing the field
technician that the integration is complete.

The RBS may not immediately be ready to carry traffic when the configuration
finished message is received. Cells must be unlocked and to unlock cells is an
option in BSIM. The RBS must also synchronize to the external clock source
before all resources are enabled and ready to carry traffic. In most cases the
RBS is synchronized within 15 min. When using Clock Source over NTP the
IP network must have sufficiently low delay variations. In some IP networks,
the delay variation between the RBS and the time server is low enough to lock
the RBS clock to the time server, but so high that it takes significantly longer
than 15 min to synchronize the RBS.

The configuration report generated by the RBS shows if the RBS is ready to
carry traffic.

2.2.9 RBS Integrated and Activated

The OSS-RC informs the Operation and Maintenance Center (OMC) technician
through the List of Network Elements, that the RBS is integrated and
activated.

2.2.10 Configuration Backup

OSS-RC makes a backup of the RBS configuration and stores it as a

Configuration Version (CV) on the SMRS file server in OSS-RC. When OSS-RC
is prepared, the integration engineer can choose not to create a CV as part
of the integration.

2.2.11 Testing RBSs

The field technician performs the following:

a Checks the hardware status, tests the external alarms, and tests user
plane traffic

b Completes the generated result report and stores it on the client and on an
FTP server

12 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 RBS Autointegration Process

For procedure, see document Integrating RBSs On-Site.

2.2.12 Completing the Security Configuration

The integration engineer completes the O&M security configuration.

If automated activation of security level 3 was included in the process above,

then this stage consist of configuring the push log function. Configure it to
automate the upload of the security log and the audit trail logs to an FTP
server, see Log Service

In addition, if automated activation of security level 2 was included in the

process above, then this stage also consist of changing the node password.
OSS-RC stores the node password to enable access to the node. A change
of password must always be synchronized with OSS-RC. To set or change
the node password, see Security for O&M Node Access and the OSS-RC
document Security System Administration, OSS-RC.

When automated activation of security was not included in the process above,
then the integration engineer manually configures the desired O&M security
level in the RBS, see Security for O&M Node Access and the OSS-RC
document Security System Administration, OSS-RC.

Ericsson recommends:

• Operating RBSs on security level 3

• Using the push log function to automate the upload of the security log and
the audit trail logs to an FTP server, see Log Service

For further security guidelines, see Security Management.

2.2.13 Activating Licensed Features

If an LKF was installed, the integration engineer checks the service state for
each installed license, see MOs under OptionalFeatures. The integration
engineer configures and activates inoperable features, see the feature
description for each feature.

2.3 Alternative Scenarios

This section describes alternative scenarios to the process described above.

2.3.1 License Key File Not Available

In this scenario the LKF is not available when the field technician is at the site.

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 13

Add RBS

The field technician knows, before starting integration that, no LKF is available
and that the integration includes configuration of licensed resources.

The field technician proceeds as follows:

• Activates the integration unlock function for temporary access to features

and capacity, see Integrating RBSs On-Site

• Continues the integration from Section 2.2.4 on page 10

2.3.2 Transport Network Not Available

In this scenario the transport network is not available when the field technician
is at the site. The autointegration is initiated according to Section 2.2.4 on
page 10, stage a, and proceeds until the first attempt to communicate over the
transport network. The field technician realizes by notifications from Integrate
RBS, that there is no transport network available. The field technician chooses
to leave the site without cancelling the integration.

When the transport network becomes available the autointegration continues

as described in Section 2.2 on page 7 but without the field technician involved.

2.3.3 Field Technician Leaves Before Process Completed

In this scenario the field technician leaves the site before the integration is
completed. The integration continues as described in Section 2.2 on page 7 but
without the activities initiated by the field technician.

2.3.4 Integration Cancelled

In this scenario the field technician cancels an ongoing integration anywhere
in the process stage described in Section 2.2.4 on page 10. The cancelling
action restores the RBS to the status it had before the integration was started
by restarting the RBS and reloading the basic CV.

2.3.5 BSIM Not Used

In this scenario the services in OSS-RC are prepared manually without BSIM.
SMRS, DHCP, and ARNE are all prepared manually. Configuration files must
be produced without support from OSS-RC.

Planned areas are activated manually as in semi-automated integration.

14 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 Semi-Automated Integration Process

3 Semi-Automated Integration Process

This section describes the overall process for integrating RBSs without support
from BSIM in OSS-RC, and with configuration files brought to the RBS site.
Prerequisites and references to detailed procedures for different stages are
included.

Figure 3 shows stages initiated by users and stages automated with information
exchanged between nodes in the system. Although not shown in the figure,
users are continuously notified about the progress of the process through the
Integrate RBS application and OSS-RC. Continuous lines indicate stages
always part of the process while broken lines indicate optional stages.

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 15

Add RBS

Integration OMC Field Integrate

Engineer Technician Technician OSS-RC RBS RBS MME SGW

1
2
3a
3b
3c
3d
3e
3f
3g
3h
4
5
6a
6b
7a 7b
8
9
10
11a
11b

L0000078D

Figure 3 Stages of Semi-Automated Integrations

Key to Figure

1 OSS-RC Preparation

2 Configuration Files Preparation

3 Operation and Maintenance Connection Establishment and Site Equipment

Configuration:

a Integration initiation

b Initial parameter settings

c IP parameters over DHCP

16 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 Semi-Automated Integration Process

d Software upgrade

e LKF installation

f Site basic configuration activation

g Site equipment configuration activation

h OSS-RC MIB synchronization

4 Downloading Security Related Files

5 Activating Licensed Features

6 S1 Configuration

a Activation of the S1 portion of the planned area

b Configuration of S1 data in the RBS

7 Cell Network Configuration

a Activation of the cell network portion of the planned area

b Configuration of cell network data in the RBS

8 Unlocking of Cells

9 RBS Integrated and Activated

10 Configuration Backup

11 Testing RBSs

a Performing tests

b Store test record

12 Integration Completed

3.1 Prerequisites
To add an RBS to the network using the semi-automated process, the following
conditions must be met:

• Synchronization information over NTP is available; not necessary for RBSs

synchronized by GPS equipment.

• All services to use in OSS-RC are up and running and ready to be

accessed:

0 SLS

0 ALEX

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 17

Add RBS

0 DNS (alternatively a third party product)

0 OMSAS

0 ARNE

• The RBS is planned:

0 There is data for radio network and transport network configuration.

0 There is data for neighboring LTE cells and for X2 connections to

neighboring LTE RBSs.

0 An LKF is prepared if there are licenses to be installed (no LKF

required if integration unlock is used for temporary access to features
and capacity).

0 An UP is available if software must be upgraded.

0 Antenna feeder delays and attenuations are calculated.

• The SGW nodes and the MME nodes are installed, enabled, and prepared
with S1 termination points.

• The transport network is available for O&M traffic, control plane traffic,
and user plane traffic.

• The physical installations of all RBS hardware including antenna system

and power supply are completed and verified.

3.2 Semi-Automated Integration Process Stages

This section describes the stages outlined in Figure 3.

3.2.1 OSS-RC Preparation

In this stage the integration engineer enters all configuration data for the RBS
in OSS-RC. While working only with BSIM in autointegration, the integration
engineer must work with several applications in this semi-automated process.
Figure 4 is an overview of applications sequentially configured by the integration
engineer.

18 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 Semi-Automated Integration Process

OSS-RC

ARNE ONRM

OSS Common
Explorer

SMRS

DNS
Integration
Engineer

DHCP

L0000100A

Figure 4 OSS-RC Preparations without BSIM

Table 2 shows tools and applications used, type of data, and references to
detailed instructions. The OSS-RC preparation can be done at any time before
the integration activities at RBS-sites start.

Table 2 OSS-RC Tools and Instructions

Type of Data Tools and OSS-RC Documents
Applications
IP O&M configuration in • An XML editor or tool • Add eRBS with BCT
(1)
OSS for the RBS to edit configuration Preparation Phase
files
• ARNE User Guide
• ARNE
• Add eRBS with BCT
Execution Phase
Transport network • An XML editor or an • Add eRBS with BCT
configuration for the external planning tool Preparation Phase
RBS including S1 and generating transport
X2 data network bulk CM • BCG, Bulk
configuration files. Configuration General,
Function Description
• OSS Common
Explorer • Add eRBS with BCT
Execution Phase

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 19

Add RBS

Type of Data Tools and OSS-RC Documents

Applications
Radio network • An XML editor or • Add eRBS with BCT
configuration for the an external planning Preparation Phase
RBS including cells tool generating radio
and relations between network bulk CM • BCG, Bulk
cells also in neighboring configuration files. Configuration General,
RBSs Function Description
• OSS Common
Explorer • Add eRBS with BCT
Execution Phase
DNS configuration for n/a COMInf Services
resolution and reverse Installation Instructions
resolution of tracking
area and the RBS See also the LTE
interfaces Mul, S1, and document RBS
X2. Autointegration.
DHCP configuration if n/a COMInf Services
DHCP is used for IP Installation Instructions
address allocation.
(1) Bulk Configuration Management for Transport Network Interface (BCT)

3.2.2 Configuration Files Preparation

The following RBS specific configuration files are prepared manually:

• RBS site installation

• Site basic file

• Site equipment file

For descriptions of file structures and configuration parameters, see

Configuration Files. The files are manually stored on the field technician's
computer to be brought to the RBS site. If LKFs and UPs must be installed as
part of the integration, then they also must be stored on the computer and
brought to site.

3.2.3 Operation and Maintenance Connection Establishment and Site

Equipment Configuration
This stage is initiated by a field technician at the RBS site. When initiated, a
number of automated steps establishes the O&M connection, upgrades the
software, installs licenses, and configures the site equipment. The Integrate
RBS application displays the progress of the automated steps.

Compared to autointegration, the difference here is that configuration files must

be supplied by the field technician locally on-site. The steps are:

20 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 Semi-Automated Integration Process

a The field technician initiates the integration using the Integrate RBS
application, see document Integrating RBSs On-Site. The prepared
configuration files must be accessible from the Integrate RBS application
as local files. If a software upgrade is planned and if licenses must be
installed, then an UP and a LKF must also be accessible from the Integrate
RBS application.

b The Integrate RBS application configures the RBS with the specified
IP configuration data by creating Managed Objects (MOs) and setting
attributes on MOs.

c If IP parameters were not supplied by the field technician, then the IP

configuration will be done using data prepared on a DHCP server.

d If an UP is specified in the Integrate RBS application, then the RBS is

upgraded with this UP.

e If an LKF is specified in the Integrate RBS application, then it is installed.

f The site basic configuration is activated by creating MOs and setting

attributes on MOs. Based on the site basic file this includes configuring the

0 S1 and X2 interface

0 Synchronization of real-time clock and radio interface

0 Communication with various O&M servers

g The site equipment configuration is activated by creating MOs and setting

attributes on MOs. This includes configuration of the following resources
based on the site equipment file and available licenses:

0 Antenna Line Device Configuration

0 Antenna System basic configuration

0 Cascaded RET Support

0 Radio units

0 RET Support

0 Support system

0 TMA Support

0 VSWR Antenna Supervision

h The RBS notifies OSS-RC that it is up and running and OSS-RC starts
synchronizing the MIB with the RBS.

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 21

Add RBS

3.2.4 Downloading Security Related Files

The integration engineer configures security functions depending on what is

selected for the node.

Security functions include the following:

• Security for O&M Node Access

• Integrated IP Security

For procedures from OSS-RC, see Security System Administration, OSS-RC.

Ericsson recommends:

• Configuring RBSs for security level 3

• Using the push log function to automate the upload of the security log and
the audit trail logs to an FTP server, see Log Service

For further security guidelines, see Security Management.

3.2.5 Activating Licensed Features

If an LKF was installed, the integration engineer checks the service state for
each installed license, see MOs under OptionalFeatures. The integration
engineer configures and activates inoperable features, see the feature
description for each feature.

3.2.6 S1 Configuration
The S1 interface is configured as follows:

a The integration engineer activates the planned area for the S1 configuration,
see the OSS-RC document PCA, Planned Configuration Administration,
User Guide

b The OSS-RC configures the S1 data in the RBS. The connection of the
RBS to the MME is established based on the completed configuration.

3.2.7 Cell Network Configuration

The cell data is configured as follows:

a The integration engineer activates the planned area for the cell network,
see the OSS-RC document PCA, Planned Configuration Administration,
User Guide

b The OSS-RC configures the cell network data in the RBS.

22 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08

 Semi-Automated Integration Process

3.2.8 Unlocking of Cells

The integration engineer activates the added RBS by unlocking the cells
making them available for user plane traffic, see the OSS-RC document CEX,
OSS Common Explorer, User Guide.

The RBS may not immediately be ready to carry traffic after the unlock
procedure. The RBS must synchronize to the external clock source before
all resources are enabled and ready to carry traffic. In most cases the RBS
is synchronized within 15 min. When using Clock Source over NTP the IP
network must have sufficiently low delay variations. In some IP networks, the
delay variation between the RBS and the time server is low enough to lock
the RBS clock to the time server, but so high that it takes significantly longer
than 15 min to synchronize the RBS.

The configuration report generated by the RBS shows if the RBS is ready to
carry traffic.

3.2.9 RBS Integrated and Activated

The OSS-RC informs the OMC technician through the List of Network
Elements, that the RBS is integrated and activated.

3.2.10 Configuration Backup

The integration engineer orders a backup of the RBS configuration. OSS-RC

takes a backup of the RBS configuration and stores it as a CV on the SMRS
file server in OSS-RC.

3.2.11 Testing RBSs

The field technician performs the following:

a Checks the hardware status, tests the external alarms, and tests user
plane traffic

b Completes the generated result report and stores it on the client and on an
FTP server

For detailed procedures, see document Integrating RBSs On-Site.

When finished, the List of Network Elements in OSS-RC indicates that the
RBS has been integrated, activated, and tested.

3.3 Alternative Scenarios

This section describes alternative scenarios to the process described above.

16/1551-HSC 105 50/1 Uen C1 | 2011-02-08 23

Add RBS

3.3.1 License Key File Not Available

In this scenario the LKF is not available when the field technician is at the site.

The field technician knows, before starting integration, that no LKF is available
and that the integration includes configuration of licensed resources.

The field technician proceeds as follows:

• Activates the integration unlock function for temporary access to features

and capacity, see Integrating RBSs On-Site

• Continues the integration from Section 3.2.3 on page 20

3.3.2 Transport Network Not Available

In this scenario the transport network is not available when the field technician
is at the site. The integration is initiated according to Section 3.2.3 on page 20,
stage a and proceeds until the first attempt to communicate over the transport
network. The field technician realizes by notifications from Integrate RBS, that
there is no transport network available. The field technician chooses to leave
the site without cancelling the integration.

When the transport network becomes available the integration continues as

described in Section 3.2 on page 18 but without the activities initiated by the
field technician.

24 16/1551-HSC 105 50/1 Uen C1 | 2011-02-08