Process To Migrate A Dus41 To A Baseband 5216 Lte Rbs Into The Network.docx

process to migrate a DUS41 to a Baseband 5216 LTE RBS into the network. The procedure includes different parts or phases of the migration: 

Preparation Phase This phase describes the activities that should be performed before the migration of the RBS. Activities on this phase: - Collect Kget dump of G1 node - Prepare Migration Scripts (G2 Scripts)



Execution Phase This phase describes the activities that should be performed during the integration of the Baseband 52. This phase is divided in Onsite activities and Remote activities. These activities are: - Create backup on G1 node - Pre-Check - Export the references from G1 node in OSS-RC - Delete the references of the G1 node in OSS-RC - Installation of the Baseband 52 (replace the old DUS41 by the new Baseband 5216 and re-connect all the cabling to the proper ports) - Onsite integration o Checking RBS Status o Connecting Clients and Pre-checks o Autointegration G2 node (Baseband 52) using onsite configuration files (this includes the SiteBasic and SiteEquipment configuration, where is defined the Routing, LDAP setting and hardware (Cabinet, RRU/RU, SCU, PDU, TMA, RET…))

- Remote configuration from OSS-RC (RN, TN and final settings) o Add the G2 node in OSS-RC with the new configuration for the Baseband 5216. o BCM configuration files o Netconf configuration files o .mos configuration files o Synchronize the eNodeB in the OSS-RC o Counter profile activation in OSS-RC



Delivery Phase This phase describes the activities that should be performed after the integration of the Baseband 52, to verify that all configurations were performed correctly, that all MOs are enable and unlocked and that the Baseband 52 is performing traffic without any problem.

This procedure could be performed only if the collection of the entire configuration from the G1 nodes has been done previously and the new licenses have been generated for the fingerprint of the eNodeB. 1.1.1

Tools The following tools are at hand:

1.1.2

1.1.3

-

A PC to function as the processing environment for the client applications.

-

An Ethernet cable to connect the client computer to the RBS; typically a category 5 patch cable with 8P8C modular connectors (RJ-45) and TIA/EIA-568-A wiring (included in cable package NTM 503 46/100).

-

The PC must be set to the current date. The node uses the date and time of the computer until the node has established contact with the Network Time Protocol (NTP) server.

-

Moshell or EMCLI must be installed in the PC, last version is recommended, 11.0e.

-

SFTP server application installed on PC. The SFTP server is used for storage and transfer of configuration files to the node through the Local Maintenance Terminal (LMT) port.

Software Perquisites OSS-RC

O1525 or later

Upgrade Package

L15B_EP1 or later

Conditions The following conditions must be fulfilled: 

The physical installation of RBS is completed and verified, see Installing RBS.



All configuration data necessary for the integration are prepared: -

RBS configuration files have been generated and provided to the field technician. Deletion of the eNodeB in the OSS-RC

-

The LKFs have been generated and provided to the field technician. The Software Package has been provided to the field technician.