2. Auto-integration in LTE
Welcome to this eLearning module ”Auto-integration in LTE”. This short module covers auto-integration of RBS in Ericsson’s LTE radio access network.
Auto Integration allows RBSs to be integrated with minimal involvement of the site technician.
As the name of the module implies, an introduction to the Auto-integration of the LTE RBSs will be made. The examples and explanations focus on the eNodeB; however, the concept is similar to WCDMA RBS integration also.
Ericsson
Academy
LEARN, SHARE, GROW

3. What’s in it for YOU?
If you work with LTE you will definitely make use of the knowledge
Part of the Self Organizing Network (S O N) concept in LTE
DNS
Site Integrator
OSS-RC
How? Where?
If you work with LTE network configuration or with rollout activities, you will definitely come across the auto-integration concept. This module ensures that you have a good overview of the Autointegration procedure. This knowledge will empower you to talk with more confidence on how Ericsson’s implementation looks like. Furthermore, this module gives you a base to research further, if you need further implemetnation details.
Autointegration of RBS is part of the Self Organizing Network (SON) concept in LTE. The SON includes Self planning, Self Configuring, Self Optimizing and Self Healing concepts. Autointegration of RBS implements the ”Self Configuring” concept in the vision of SON.
In this module, you will get a semi-technical overview of how the implementation of Auto-integration of RBS is possible in Ericsson’s LTE radio access network.
Remember .... to make the auto-integration work, there are quite a few bits that have to fall in place.
And you are in the right module to get the overview of those dependencies.

4. Objectives Learning Objectives List the advantages of Auto-integration
State what needs to be configured in the eNodeB
Describe the functions of the nodes/applications involved for:
Auto-integration with “Integrate RBS” application
Auto-integration with eNIS application
Auto-integration for small cell deployments (pico and micro RBSs)
Understand the role of On-site integrator and the OSS-RC engineer
This module is an introductory module that explains the concept of how Auto-integration of LTE RBS works. It does not ,however, detail the use of tools and parameters to make the Auto-integration work.
Note also that there is Auto integration in WCDMA and GSM also, but the explanation/example includes the LTE eNodeBs.
After completion of this course module the student should be able to:
List the advantages of Auto-integration feature.
State what needs to be configured in the eNodeB
Describe the functions of the nodes and applications involved in the Auto-integration. Three cases are considered:
Auto-integration with a “Integrate RBS” application. Another name that is also used is “Auto-integration with a laptop”
Auto-integration with a “e NIS” ntegrate RBS” application. Another common name to describe this case is “Auto-integration without a laptop” or even “Auto-integration with an Android-based mobile phone”
Some considerations in small cell deployement with Ericsson’s Pico and Micro RBSs are also explained.
The listener should understand the role of the site-integrator and the OSS-RC personnel during the different auto-integration procedures. 4

5. Agenda Introduction Auto-integration with a Laptop
Auto-integration without a Laptop
Auto-integration in small cell deployment
The agenda for this module is presented here.
We will start with an initial introduction. We shall then dig deeper into three auto-integration cases.
There will be quizzes that will summarize the main concepts. Similarly, links to other sites where more information can be obtained will also be provided.
It is important that in the three cases, the first case will be more detailed. For the other cases, it is assumed than the participant has already understood the first case. In other words, the differences are highlighted for second and third cases.
Quiz / Summary / More information

6. Introduction Introduction.
In this section we shall get an overview of the integration phases of the eNodeB.
Then, the advantages of auto-integration are laid out.
Different ways of auto-integration implementation is listed.
And finally, the Base Station Integration Manager (or B SIM)- the application (or tool) that is used to carry out Auto-integration, is presented.

7. Integration- what is the goal?
MME
LTE EPC
SGw
IP network
RBS
Before tackling Auto-integration, let us understand what integration of an eNodeB means.
The core-network in LTE is the Evolved Packet Core or EPC. It has among other nodes the MME (Mobility Management Entity) and the SAE Gateway. The RBS needs to be integrated to them for the S1-interface!
The Operation and Maintenance network consists of many servers, routers and the OSS-RC. These servers are are collectively referred to as the Common O&M Instrastructure or (COM INF). RBS needs to establish the Mul interface to this O&M domain.
RBS will reach these two clouds from two separate IP networks.
The RBS is physically installed.
The RBS is then integrated to the O&M network.
Now the RBS sets up the S1 interface.
Cells are unlocked and it is possible to carry traffic from the RBS.
Other RBSs will also join, very likely to the same IP clouds. The X2 interface between the RBSs are realized via the traffic IP network.
That is integration.

8. eNodeB Integration Phases
Start
End
Radio network
Radio and transport
Define radio and transport parameters
From the OMC
Transport network
Site Equipment
RBS HW
Site Equipment
At the RBS Site
Site Basic
Site Basic Configuration
O&M Access and NW Sync
The diagram here shows what need to be configured in an eNodeB to get it fully operational. This is an important diagram to understand since it is closely linked to the integration files that will be explained later in the presentation.
At the Node Production Center, NPC, a Basic Package software is loaded in the RBS, together with an operator independent system configuration.
At the RBS site, site preparation is done, and then the RBS is physically installed. When the RBS is powered on, it already has the software and configuration required to continue the integration.
The first goal is to get the RBS linked to the Operation and Maintenance network, where OSS- RC and various other servers are present. The RBS itself needs a network specific IP address with which it can reach those O&M servers. The fact that the RBS might be faraway from the O&M servers means that the same physical link will be shared for the Traffic interfaces,(i.e. S1 and X2), and the O&M interface (or Mul).
The Site Basic Configuration involves making O&M access for the RBS, together with specifying the Network Sync source reference. Two files "Site Installation" and "Site Basic" are used to create this configuration phase.
Site Equipment configuration is the definition of the ”RBS hardware”. It includes the external alarms set-up and battery back-up. Most importantly, it is during this stage that the antenna and sector related configuration are made. Sector will be used by the Cell at the end of the configuration process. The Rbs Site Equipment file is used to create this phase of the configuration.
The Transport Network and Radio Network configuration includes the S1 and X2 interfaces setup, and the cellular configuration respectively. These are performed from the Operation and Maintenance center, OMC. Once these are completed, the cells are unlocked so that User Equipment can camp on to them.
Basic CV
A Basic SW package is loaded
At the NPC
Basic Package

9. AutoIntegration: High Level Workflow
RBS Auto-integration
Network Design
OSS-RC Preparation
OSS-RC Pre- config
On-site Integration
Testing
Network Operation
This is a high-level flow of what Auto Integration involves. Here the assumption is that the autointegration will be performed with a laptop, although the procedure is very similar even without one.
For RBS Auto-integration to work, there are preparations that need to be made in the OSS-RC and the O&M network. The details of these preparations vary depending on what type of integration method is desired. We will look at the each of these steps a bit in detail later on in the module.
One observation we can already make here is that the on-site integrator relies on the preparations made on the OSS-RC and the network, and he/she does not require any coordination with the OSS-RC personnel for his/her work.
Before the preparations for the auto-integration can happen, the network design phase should prepare the parameters that each RBS should have. After the auto-integration, the Network Operations can begin.
RBS physical hardware installation can be performed anytime before the on-site integration, but preferably after the OSS-RC preparations are finished.
RBS HW Installation

10. Benefits of Auto-Integration
Simplify project coordination
Configuration data stored in the OSS-RC/ COMINF domain
no need to transfer files to the site technician
Site technician not dependent on OSS-RC personnel to make verification tests
Overall time spent on the site is less
RBS Autointegration simplifies project coordination. OSS-RC engineer and on-site engineer do not have to coordinate their work in real-time for each RBS integration.
Configuration data is stored by OSS-RC and automatically retrieved by the RBSs. This simplifies exchanging configuration files between the network and the site integrators. The integrator at the RBS site is the only person involved during the integration - finishing with unlocked cells ready to carry traffic.
The on-site integration is not dependent on staff presence at OSS-RC for verification or traffic commissioning tests.
For the operator, the amount of time spent on site by its personnel equates to reduced OPEX. Auto-integration significantly reduces time required for each integration.
Note that there are various degrees of auto-integration supported; from full autointegration to semi-autointegration.

11. RBS Auto-Integration Methods
Auto integration with a laptop
Fully automated (auto integration with DHCP)
Semi automated (auto integration without DHCP)
Auto integration without a laptop
Manual Binding
Auto binding
Auto integration of Pico (e.g. RBS 6401) and Micro (e.g.RBS 6501) RBSs
Considerations:
IpSec
IPv6
Wi-Fi module (in Pico RBS case)
TCU/SIU
We already know what configuration is required in the RBS. But how does one perform those configuration?
There are three ways to perform auto-integration.
In Auto Integration with a laptop, the On-site technician only requires very limited information to initiate the configuration of the RBS. There are several variants, but let us take two cases here:
• Auto Integration with Dynamic Host Configuration Protocol (DHCP): The on-site technician only requires the eNodeB name, userName and password for a FTP (also called SMRS) server and the vLanID for O&M traffic to initiate the complete auto integration process. All the necessary data are downloaded from the servers.
• Auto Integration without Dynamic Host Configuration Protocol (DHCP): Since the DHCP cannot provide the IP for the node in this case, an additional file executed by the on-site technician provides the information that would otherwise have been provided by the DHCP. The rest of the configuration is downloaded from the network, based on what had been prepared in advance by the OSS-RC engineer.
There are variants also here, for example- the transport network configuration is automated, but the radio is not. These cases are also referred to as the semi-automated procedures.
Auto integration without laptop requires simply a smart-phone and an app called Ericsson Network Integration Service (e NIS). Of course, the OSS-RC must have been prepared in advance with configuration parameters beforehand for it to work. We will investigate this case later in this presentation.
There are two sub-variants within this case- with manual binding and auto-binding. We will only look at the auto-binding procedure.
Pico RBS (RBS 6401) and Micro RBS (RBS 6501) are parts of small cell solution. Because of the environments where they are expected to be integrated, they are treated with an own bullet here.
Note that integration requirements also need to be taken into account.
• If IP security (or IpSec) is required, there are certain procedural and infrastructure requirements.
• If IP version 6 is to be used, procedure is the same, however, IP v4 is used as an example here.
- The Pico RBS also has a Wi-Fi module, which means that the WiFi integration should also be kept in mind. However, we will not handle the WiFi chapter here.
- An RBS site might be connected to the transport network with a Site Integration Unit (SIU) or a TCU (Transport Connection Unit)- which are also part of the site. We shall not deal with their integration in this module.
These requirements are not considered here in this module, although IpSec in the contexts of small cell deployment are slightly covered.
Extra:
In Manual Integration, the On-site technician is given a set of files with which he/she makes the "on-site" configuration, and lets the OSS-RC know when the on-site configuration is completed. The OSS-RC engineer then defines the RBS in OSS-RC and prepares the transport network and the radio network data, and activates the configuration. Upgrade and License installation can be performed either on-site (then the required files should be with the site technician) or remotely from the OSS. The on-site technician performs traffic tests when the cells have been unlocked.
We notice that the there is quite a coordination needed between the on-site and OSS-RC personnel in the manual integration.

12. BSIM for AutoIntegration
Licensed application in OSS-RC – view in Common Explorer
Two functions:
Add an RBS to OSS-RC
Auto integration
Since Base Station Integration Manager (BSIM) is used for auto- integrating RBSs, a brief introduction is given here.
BSIM is a licensed feature in the OSS-RC. It is started from the Common Explorer.
BSIM is used as an interface to add the RBS to the OSS-RC and then specify the configuration in the OSS-RC and push it to the node. The BSIM interface also coordinates the Autointegration procedure if that option is chosen.
A function within BSIM is responsible for working with templates. Templates are generic scripts with "substitution variables" which maybe replaced with node-specific parameters.
In this module, the procedure for creating user-defined templates in BSIM is not included.
Note that BSIM itself can generate configuration files and store them in the relevant servers during auto-integration preparation!
Uses “templates” containing non site specific parameters to minimise amount of input data
When a node is added, OSS generates the site configuration files

13. Auto-Integration with a Laptop
Let us look at the Auto-integration with a Laptop case.

14. Auto-integration with a Laptop
OSS- RC
What is required?
OSS-RC
BSIM
SMO
PCA
ARNE
SMRS
DHCP
DNS
At the site:
RBS
Laptop
COMINF Servers
SMRS
DHCP
DNS
O&M Network
What is required to make Auto-integration work? The minimum one requires for a full auto-integration are:
On the network side,
-the OSS-RC with the BSIM application is mandatory.
Besides creating the configuration files, BSIM coordinates various applications in and outside of the OSS-RC for auto-integration to work.
-The Software Management Organizer coordinates the software related activities.
-The Planned Configuration Administration function works with preparing the transport and radio network configuration for the RBS using Bulk Configuration Management files.
-ARNE or Add Remove Network Element defines the RBS in the OSS-RC.
In the Common Infrastructure, there are a few servers that will be used in the auto-integration procedure. Here we assume auto-integration without Ipsec.
-SMRS: Software Management Repository Server where configuration files, software and licenses would be stored
-DHCP : The Dynamic Host Configuration Protocol could provide the IP address for the RBS, together with some other info that would be required during the integration process.
-DNS : Domain Name Server is primarily used to provide the IP address of the MME. Of course, it may also be used to resolve domain names to IP address.
- A laptop at the site for the on-site technician.
RBS

15. OSS-RC Preparation BSIM OSS-RC Preparation OSS-RC RBS Auto-integration
OSS-RC Pre- config
On-site Integration
Testing
OSS-RC Preparation
Template files preparation:
ARNE
Site Installation
Site Basic
Site Equipment
Auto-integration Summary file
Bulk CM
DNS
DHCP
OSS-RC
Template
files
In this stage the OSS-RC engineer prepares all the necessary files in the OSS-RC. These files will be used in the next stages by the BSIM application in the OSS-RC.
Template files are ordinary application-specific configuration files that have “substitution variables”. These variables will be substituted with user entries. After substitution, these template files are used to configure the LTE Radio Access Network.
Examples of template files are ARNE, Site Installation, Site Basic, Site Equipment, Auto- integration Summary file, Bulk CM, DNS and DHCP.
• The ARNE file would define the RBS in the OSS-RC
• The Site Installation would be used by the RBS to configure the basic IP configuration, in case the DHCP is not used.
• Site Basic and Site Equipment would configure the RBS. These files would eventually end up in the SMRS server together with the Auto-integration summary file, which specifies where these files are located in the SMRS server. During the integration process, RBS would fetch these files from the SMRS and execute them.
• Bulk CM files configure the radio- and transport network. These files would be used by the PCA application in the OSS-RC.
OSS-RC Engineer
BSIM

16. OSS-RC Preconfiguration
RBS Auto-integration
OSS-RC Preparation
OSS-RC Pre- config
On-site Integration
Testing
“Options”:
• Automated or manual unlocking of cells
• Automated backup after integration
• Automated software upgrade of RBS
• Automated installation of licenses
OSS-RC Pre-configuration
User enters data in BSIM, including the integration “options”
In BSIM/OSS:
ARNE (ONRM) in OSS-RC is configured
BSIM sends configuration files/data to servers
RBS Site Installation file and DNS files prepared in OSS-RC
If DHCP is used, configures DHCP
The TN and RN created in the Planned Configuration
BSIM starts listening for RBS notifications
BSIM
DHCP
OSS-RC
SMRS
ONRM
After all the necessary files are prepared, the pre-configuration phase starts, using the BSIM in the OSS-RC .
The templates are chosen, and the substitution variables filled in. The BSIM takes the user inputs either in the Graphical User Interface or from a file.
When the process is completed, the RBSs are added in the OSS-RC, and the configuration data are processed. Configuration files are created and stored in the relevant servers for the RBSs to retrieve later. In the BSIM, the integration “options” are also specified!
BSIM now listens for RBS notifications. The integration at the site can begin at anytime after this.
BSIM shows the progress for the OSS user through out the process. Of course there are logs related to autointegration that may be consulted for troubleshooting.
Details on what happens in the BSIM:
BSIM checks that all mandatory input data and files are present.
BSIM adds the RBSs in the OSS-RC. That means the ARNE function.
BSIM creates and stores site configuration data for O&M communication and RBS equipment on the SMRS. A site-installation file for each RBS is stored locally in the OSS-RC, and could be required if DHCP is not used during integration.
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, BSIM compiles configuration files with the parameters. DNS configuration files might also be compiled.
BSIM creates and stores transport network data and radio network data for each RBS internally in a planned area.

17. On-Site Integration On-site Integration Field Technician
RBS Auto-integration
OSS-RC Preparation
OSS-RC Pre- config
On-site Integration
Testing
DHCP
On-site Integration
Initiated by the field technician with the RBS Element Manager (“Integrate RBS” function)
RBS contacts the relevant servers
Servers send relevant data to the RBS
Planned Configuration is activated in OSS-RC
Integration “options” executed
RBS is ready for service!
Autointegrations functions are implemented
SMRS
ONRM
What is the role of the site-integrator?
: on-site integration and traffic testing.
Of course, the RBS must be physically installed and all the power and cables already in place before integration can begin.
The on-site integration is performed by the responsible site integrator at the RBS site. In the case of "Integration with a laptop" scenario, he/she initiates the "Integrate RBS" application in the RBS, and provides a few parameter inputs- for example, if DHCP is used, the RBS name, the username/password to the SMRS server and the VLANId. This starts the automated integration chain!
Configuration data is transferred to the RBS and activated, finishing with unlocked cells.
Remember, that the options could include:
• Upgrading the RBS
• Installing a license file
• Unlocking of the cells
• Making a configuration backup (also called the configuration version, or simply the CV)
Press on the "Autointegration functions" to understand the details of the automated procedure.
BSIM
Field Technician

18. Testing Testing Field Technician RBS Auto-integration
OSS-RC Preparation
OSS-RC Pre- config
On-site Integration
Testing
Testing
Performed primarily by the field technician
Test data sessions, external alarms
Integration reports generated manually updated with test results
Further troubleshooting with OSS-RC tools if needed
In the test phase, the field technician verifies the function of the RBS before leaving the site.
Test data sessions in each cell and verification of the site specific external alarms are sufficient tests.
Integration reports are generated and can be manually updated with test results and other comments before being uploaded to a central archive.
Further test and fault localization of the RBS can be performed remotely using test functions in OSS-RC, for example, OSS Common Explorer, Alarm List Viewer, Network Status Display, and Advanced Managed Object Scripting - AMOS.
This concludes the full “Autointegration of RBS with a laptop” process.
Field Technician

19. Auto-Integration without a Laptop
Assuming we have understood the previous case "Auto-integration with a laptop", let us proceed to check the differences in “Auto-integration without a laptop” scenario. This is also referred to as the “Auto-integration with ENIS”, “auto-integration with a mobile phone”.

20. RBS Auto-integration without a Laptop
OSS
OSS-RC
BSIM
SMO
PCA
ARNE (ONRM)
What is required?
OSS-RC
BSIM
SMO
PCA
ARNE
SMRS server
DHCP
DNS
Mail server
Auto-integration Web server (AIWS)
At the site:
RBS
Android phone /ENIS
COMINF Servers
COMINF Servers
SMRS
HTTP (AIWS)
DHCP
DNS
O&M Network
Mail Server
What is required to implement "Auto-integration without a laptop"?
Three additional components are added from an infrastructure point of view:
A mail-server is required
An Auto integration web application server (This is often referred to as the AIWS)
ENIS application on the Android phone
Note that the IpSec implementation is not considered here, and thus the infrastructure required for it are left out.
RBS

21. RBS Auto-Integration without a Laptop- Site Perspective
9/11/
9/11/
RBS Auto-Integration without a Laptop- Site Perspective
Install RBS
Read and send bar codes from app
Turn on power on RBS
Monitor integration progress via LED
read
Mail Server
read
Let us see what the site integrator does if ”RBS Auto Integration without laptop” iis performed.
The RBS is physically installed by the installers. The integration has not started yet. However, the OSS-RC and the network are already prepared with configuration data for this RBS.
Now the integrator comes to the site.
The e-NIS app is used for reading (or scanning) hardware serial number and the site name. (Note it is possible to enter these information manually.) These information are sent to the mail-server. The network will indicate to the smart phone when the network is ready.
The RBS can now be powered-on.
Pre-prepared configuration in the network will be sent down to the RBS.
But how will the integrator know when the integration is complete?
The integrator simply monitors the progress through the LED's on the Digital Unit.
As seen here, only a very few parameters needs to be fed in at the site through the eNIS app. The RBS and O&M network then take care of the rest!!!
To enable auto-integration, some preparations are required in the O&M network. A more detailed diagram on what happens in the network and the OSS-RC are explained in the next slide.
HW:
SerialNumber=69204FXCG3284
O&M Network / OSS-RC
Apply configuration
NRJ-13: Uen, Rev PA1 21 21

22. Auto-integration without a Laptop ..1
Transport / Radio Config
OSS-RC 1.
OSS-RC Engineer prepares in the Base Station Integration Manager (BSIM) the following config files:
RBS Auto-integration Summary file
Site Installation
Site Basic
Site Equipment
DHCP/DNS prep
BSIM 1
COMINF Servers
DHCP
DNS
SMRS
HTTP (AIWS)
Mail Server
From a network perspective the preparation starts with BSIM (the Base System Integration Manager). B S I M, will indicate that it is an Auto-integration without a laptop, and that security will not be required! (This is the assumption right now.)
At this time, the RBS is not in the picture.
Just like in the previous “Auto integration with a Laptop” case, the OSS-RC engineer will prepare the required templates and input files.

23. Auto-integration without a Laptop ..2
2. RBS added in OSS-RC.
Config files created/copied to SMRS:
Site Basic
Site Equipment
RBS Autointegration summary
3. Configuration binding
Site engineer sends RBS Hardware ID/Serial No. and the RBS logical name to the secure mail server.
Mail server forwards the info to the BSIM
BSIM links the hardware id to the RBS logical name
4. SiteInstallation file is copied over to Auto Intergation Web Server (AIWS)
Transport / Radio Config
OSS-RC
BSIM
COMINF Servers 2 4
DHCP
DNS
SMRS
HTTP (AIWS)
Mail Server 3
BSIM will add the node in OSS-RC triggering the preparations in the network.
The RBS will be added in the OSS-RC, and a planned configuration is ready for the RBS once it becomes ready.
Configuration files created in the previous step are then copied to the respective servers. For example, the SMRS gets the Site Basic, Site Equipment and the RBS summary file.
<After the Step 2>
Now, the onsite integrator goes to the site, and initiates the configuration binding procedure.
Note that the configuration binding process can be both manual or automatic.
In the manual case, the on-site technician can call the OSS-RC personnel and provide the RBS logical name and the serial number. OSS-RC engineer can, through BSIM, can perform the configuration binding.
In the case of automatic configuration binding, as is assumed in this diagram, the eNIS application scans the hardware, provides the RBS logical name and sends them to the Mail-Server, which then send those info to the OSS-RC.

24. Auto-integration without a Laptop ..3
Transport / Radio Config
OSS-RC
5. The eNB is Powered on
6. VLAN Scanning + DHCP
DHCP options contains
NTP server address
AIWS server address
7. Use HTTPs to log in to the AIWS
Fetch Site Installation file
Extract unique SMRS username and password from Site Installation file
Get new OAM IPv4 address
BSIM
COMINF Servers
DHCP
DNS
SMRS
HTTP (AIWS) 6
Mail Server
Note that the NTP (Network time protocol) server will also be contacted to get the node time. The NTP server could be implemented in the COMINF. 7 5

25. Auto-integration without a Laptop ..4
8. Use SFTP with unique username and password to SMRS and fetch the configuration files
Site Basic File
Site Equipment File
RBS summary File
Upgrade Control File
9. Execute the scripts downloaded
If the upgrade needs to be performed,it is done now
10. Establish OAM connection to OSS-RC
OSS-RC informed of the RBS
Get Transport and Radio Network Configuration fromthe OSS-RC
Transport / Radio Config
OSS-RC
BSIM
COMINF Servers
DHCP
DNS
SMRS
HTTP (AIWS)
Mail Server
This diagram is the same as the previous case. Everything is automated here.
At the end of the procedure, the cells will be able to carry traffic.
Throughout the process the on-site integrator monitors the LEDs in the RBS to get information of the integration status!!! 8 10 9

26. Auto-Integration in small cell deployment
Let us now look at the sepcial considerations that small cell deployment entail.

27. Pico and Micro RBS considerations
Trusted Network
MME
SGW
RNC
LTE / WCDMA
Untrusted Network
RBS 6401
SeGW
OAM
IPSec
Wi-Fi
Why are Pico RBS and Micro RBSs special? Why are they being treated with a separate module here?
Let us get some background on these RBSs first.
Pico cells are implemented with Ericsson’s RBS 6401 or RBS Microcells are implemented with RBS 6501.
Pico and Micro RBSs are integral bits of Ericsson’s small cell solution => they support WCDMA, LTE and Pico also has an optional Wi-Fi module
These RBSs are meant to be deployed rapidly “everywhere” and in large numbers. Examples include in train stations, malls, cafés, restaurants, malls, stadium.
It means that the RBS will probably end up in an untrusted public IP network
It is most likely that the operator would want an IPSec because of the untrusted network.
Once integrated, the local Operation and Maintenance interface of these RBSs should be disabled.
These small cell RBSs should self configure, as sending personnel to the site to perform configuration would be too complicated and expensive
To fulfill these requirements, the “auto-integration without a laptop” procedure is performed, however, there are some other special considerations:
IpSec is assumed almost all the time. That means that the security Gateway (SeGW) should exist, together with the security certificate registration authority in the O&M domain..
BSIM should support mass deployment of RBSs.

28. RBS Self Establishment Process overview
RBS Self-Establishment, mRBS, AT&T
RBS Self Establishment Process overview
Network Provisioning
Node Provisioning
Node Commissioning
Node Integration
Prepare NW Infrastructure
Prepare for Node Configuration
Node Specific Configuration
Autonomous Node Integration
Deploy and configure / re-configure servers
Pre-configure individual / batch of nodes using templates
Bind physical RBS id to logical configuration
Power up RBS
At infra structure changes
Large group of nodes
Per node, or group of nodes
Per node
This is a slide that is used to define small cell deployment. A careful examination indicates that this diagram is similar to what we have already seen in the previous cases.
In short the network preparation must be performed before integration of the RBS can happen. In the preparation phase, the BSIM supports the batch configuration for small cells deployment.
The node integration is completely autonomous, just like in the other two cases we have seen. In fact, small cell deployment is similar to “Auto-integration without a laptop”, but with Security implementation. 28

29. Step 1: Initial secure connection to trusted “core”
Trusted Network
MME
SGW
RNC
LTE / WCDMA
Untrusted Network
RBS 6401
SeGW
O&M Network
IPSec RA
OSS
DHCP
DNS
Let us assume that the Network/node provisioning, have been done as a pre-requisite. The installer goes to the site, scans the hardware, scans the work order to get the RBS logical name, and sends the information via eNIS to the mail server.
He (or she) powers on the RBS to trigger the node auto-integration.
The RBS performs vlan scanning to find public DHCP server
The public DHCP server provides the an ”outer” IP address for temporary RBS IPSec tunnel, together with a Security Gateway (SeGW) address
The SeGW has been provided IP address by the operator’s trusted DHCP server meant for RBS O&M. IP address of the operator DNS is also provided.
RBS will set up temporary IPSec tunnel to securely fetch ’permanent’ RBS inner addresses fromthe SeGw.

30. Step 2: Secure download of data
Trusted Network
Untrusted Network
RBS 6401
SeGW
SMRS
IPSec
AIWS
DNS RA
DHCP
DNS
We talked about outer IP and Inner IP addresses. These are terms related to the Tunnel mode implementation of IpSec in Ericsson RAN. Outer IP addresses are used between the RBS and the SeGw, and are used for routing in the untrusted cloud. Inner IP addresses are encrypted, together with data, and are not visible in the untrusted network.
At this point the RBS has an Ipsec tunnel, although a temporary one, to the Security Gateway. Now the RBS downloads the relevant software and configuration using the Ipsec tunnel already prepared.
1. The RBS finds the AIWS via the core DNS
2. Information about needed services downloaded securely
3. Operator credentials downloaded
4. Software securely downloaded.
5. RBS self configures and deletes temporary IPSec tunnel

31. Step 3: Setup permanent secure connections
MME
SGW
RNC
LTE / WCDMA
Trusted Network
Untrusted Network
RBS 6401
SeGW
IPSec
OSS
O&M Network
IPSec
DNS RA
What does the RBS do now? At this point , it has already upgraded itself and execurted the site scripts.
1. Set up permanent IPSec tunnels for OAM interface
2. Set up permanent IPSec tunnel for traffic interface
3. Announce availability of RBS to the OSS.
4. Then the rest of the configuration process is similar to the previous cases. That means, for the LTE case:
a) OSS-RC will activate the alrready prepared configuration for the RBS.
b) RBS will ask the DNS for the IP of the MME.
c) With the IP provided frm the DNS, the signalling connection to the MME is established.
d) Cells are unlocked.
5. At this time, the local maintenance port of the RBS (also called the ”LMT port”) is also disabled- so that O&M access to the RBS in that unsecure site is disabled.
If you want, you may click on the link to get the details of the secure connection set-up.
Details of the secure connection setup procedure

32. Summary
We have now gone through the three auto-integration cases. There were a lot of slides and information. Let us just recap what we went through.

33. Summary Describe the functions of the nodes/applications involved for:
Auto-integration with “Integrate RBS” application (with a laptop)
Auto-integration with eNIS application (without a laptop)
Auto-integration considerations for small cell (pico and micro RBSs) deployment
Understand the role of On-site integrator and the OSS-RC engineer
DNS
Site Integrator
OSS-RC
How? Where?
The objectives in this module were to understand the auto-integration on overview level- in a semi-technical depth.
We looked at three auto-integration cases:
Auto-integration with “Integrate RBS” application (with a laptop)
Auto-integration with eNIS application (without a laptop)
Auto-integration considerations for small cell (pico and micro RBSs) deployment
During those processes we also got an overview on the roles of the network personnel and the site-integrator.
The OSS-RC engineer prepares the network for RBS integration via the BSIM application.
On-site integrator initiates the auto-integration procedure
The actual integration is then coordinated between the RBS and the network.

34. Quiz 34 34

35. Auto-integration in LTE

36. More Information CPI store Product catalogue
For more in-depth instructor led training, visit Academy Site /MyLearning and search for “LTE L14 Configuration”
The OSS-RC and the RBS CPI libraries have technical and more detailed information on how the Autointegration is implemented.
In the LTE RBS CPI, the folder “Integration” has a few descriptions on RBS integration, including the Autointegration with laptop (that is using Integrate RBS tool) and Autointegration without laptop (that means the ENIS tool).
In the OSS-RC CPI, the document ”BSIM, Base Station Integration Manager, User Guide” explains the role of the BSIM in the Autointegration procedure, and how one may use the BSIM tool. Similarly, the “PICO OSS-RC Description, End to End Description” describes how to prepare the OSS-RC for Pico RBS deployment.
Product catalogue is also a rich source of information. Search for LTE to get LTE specific information and documentation, including Autointegration.
Similarly, an Instructor Led Training ”LTE L14 Configuration” describes the complete eNodeB integration, including the Auto-integration. Enroll yourself through the MyLearning site. 36 36

38. Auto-Integration Functions
Retrieving IP configuration over DHCP
Fetching configuration files, Upgrade Packages (UPs), and License Key File (LKF) from SMRS server in the network using SFTP
Upgrading the RBS software
Creating the site configuration
Informing the OSS-RC, downloading and activating configuration information
DNS communication to set-up the S1
Back to the slides

39. Step 1: Initial Secure connection to Trusted “Core”- details
Public Transport Network
Operator Secure Network
RBS
Public DHCP Service
Public
DNS Service
SEG
Operator Core DNS
Operator Core DHCP
VLAN scan
DHCP Query for IPv4 address, Public DNS IPv4 IP address, and SEG IP address
Look up SEG DNS name
Setup temporary OAM IPsec tunnel – IKE_SA_INIT exchange
DHCP SOLICIT / REPLY
RBS send IKE_AUTH – Authenticate with Vendor Certificate
SEG sends IKE_AUTH with RBS inner IP address, Operator Core DNS IP address
Network/node provisioning, node commissioning done before small RBS onsite
Switch on RBS to trigger auto-integration
Scan to find public DHCP server
Download outer IP address for temporary RBS IPSec tunnel + SEG address
Set up temporary IPSec tunnel to securely fetch ’permanent’ RBS inner addresses
Automatic Process

40. Step 2: Secure Download of Data- details
Public Transport Network
Operator Secure Network
OSS Infrastructure
Operator Core DNS
RBS
SMRS
AIWS RA
DNS lookup of AIWS name
Connect to AIWS, get Registration Authority (RA), Master Server (MS) and SMRS address, SMRS UID and PWD, configuration file
Certificate enrollment to get the Operator Certificate, authentication using Vendor Certificate
Download SW (SFTP)
Initial Software Installation
RBS self configures based on initial configuration file. Tear down temporary OAM IPsec Tunnel
The RBS finds the AIWS via the core DNS
Information about needed services downloaded securely
Operator credentials downloaded
Software securely downloaded.
RBS self configures and deletes temporary IPSec tunnel
Automatic Process

41. Step 3: Setup Permanent Secure Connections
Public Transport Network
Operator Secure Core
RBS
SEG
Operator Core DNS
Operator Core DHCP
OSS Nodes
OSS Master Server
Setup OAM IPsec tunnel using the operator cert. Get Internal IP, DNS server address, via IKEv2
DHCP Exchange
Setup Traffic IPsec tunnel using the operator cert. Get Internal IP via IKEv2)
DHCP Exchange
DNS lookups
Announce presence to OSS Master Server, send RBS OAM IP address, traffic IP address, node serial (CORBA)
Back to the slides
The final stage of the integration into the untrusted environment is to setup the permanent IP Sec tunnels – these can be to the same SEG used for the initial temporary tunnel or to a different, ’serving’, SEG, if wanted.
In addition, the OAM and traffic IPSEC tunnels may be to the same or different ’serving’ SEGs.
And the small RBS can terminate the IPSec tunnels using two or one outer IP address, depending on the operator requirement.
Once completed, the RBS will announce its presence to the OSS.
Set up permanent IPSec tunnels for OAM interface
Set up permanent IPSec tunnel for traffic interface
Announce availability of RBS to the OSS