Public

MOP_BB5216_SINGLE_MODE_
GSM_NEW_SITE_G2_OSS_Proce
dure
Table of Contents
1 Propose of this document...................................................................2
2 Revision information...........................................................................2
3 In Scope.............................................................................................2
4 Main differences between Baseband DU and DUG20........................2
5 Workflow.............................................................................................4
6 Tool and Software Perquisites............................................................5
7 Conditions...........................................................................................6
7.1 New RXSTG structure........................................................................6
7.2 MOs which are not needed more for BBDU in BSC............................6
7.3 MOs which are changed but still represented in the BSC...................6
7.4 New MOs in BSC................................................................................7
8 Preparation Phase..............................................................................7
8.1 Collect CDD/CDR and ATND..............................................................7
9 Execution Phase.................................................................................7
10 Create Cell..........................................................................................8
11 Create MO at BSC..............................................................................8
12 License.............................................................................................10
13 Create ARNE G2..............................................................................10
14 Start Online Enrollment.....................................................................18
15 Delta Loading XML...........................................................................18
16 Adjustment, Update NE ID and Long Lat..........................................20
 17 Counter profile activation in OSS-RC...............................................22
18 Fallback procedure...........................................................................23
19 Health check and to consideration....................................................23
19.1 Take log after, check traffic and alarm..............................................23
19.2 SAE before migrate require to increase............................................23
19.3 Combase user have GSM role at OSS,............................................24
19.4 Sample Script for GSM Type............................................................24
19.5 Take log BB with dcgfm -k 1.............................................................24
19.6 Power setting between BSC and BB................................................24
19.7 TRX configuration standard..............................................................24
20 References.......................................................................................25

Propose of this document

This document acts as a how to Integrate new site with BB instructions for
implementing 2nd generation Baseband GSM

With continuous modification of this document according to the assumptions and

open questions finally a working Integrate new site method will be the result.

Revision information

PA1 First skeleton and main data earisia

A First version earisia

Public
 Public

In Scope

This current version is about how to Integrate new site use BaseBand 5216 in an
RBS 6320, where Abis over IP is already implemented, the TCU will be
reconfigure also, and synchronization for BB use IP Clock Ref SSU, ptp
associatedGrandmaster

Main differences between Baseband DU and DUG20

 It is capable for IP transmission, so TCU can be setting use bridge and

remove vlan and PSTUid at TCU
 IDB and OMT concept will be no longer supported, instead a MOM
structure should be used for BTS side configuration
 1xBB DU can handle multiple cells and each cells require one RXSTG,
instead of 1 common RXOTG like in case of DUG20
 Instead of RXOTG structure, an RXSTG structure should be defined in
the BSC, which is very different than RXOTG structure was
 RXSTRX and its subordinates will be defined automatically in the system
 CHGR and RXSTG relation will be handled through RXTCI only
 Start of RXSTG will be handled on the same way as before (RXESI,
RXBLE) however the SUBORD parameter is no longer applicable.
 BBDU concept will use the SECTOR parameter to make L2TP connection
between the BBDU and PGW, not the TGTransport any more
 BBDU has got direct connection to OSS. Configuration should be handled
from OSS, BTS related alarms will be sent to OSS, not to BSC any more
 ESB is not supported any more in case of BB DU
 All cables can be reused from configuration with DUG20 (instead of ESB),
but different cable length can be needed (in case of 6601 a longer power
cable will be needed)
 NUMREQBPC cannot be on SYSDEF value
 The Baseband 5216 supports 2 technologies at the same time. Even in
case of single standard radio and mixed mode radio configurations.

BSC Abis GRAT

cell A
CHGR 0
Sector TG 1 (3 x
CHGR 1
2)
GSM sector 1
 0
TRX TRX
1 0
TRX
1
CHGR 0
TRX
cell B 0 Sector TG 2 0
CHGR 1 TRX
1 1
TRX TRX
GSM sector 3
0 0
TRX TRX
1 1

GSM sector 2

CHGR 0
cell C 0 Sector TG 3
CHGR 1
1
TRX
0
TRX
1

Workflow
The different activities in the service are described in the chart below

Public
 Public

Collect data CDD adn ATND for New Site

Prepare Scripts Cell and MO

Create New Cell and MO for G2

Remote Pre-Check (Verify that all it works well)

Activities
Adjust cell use CNA in OSS-RC

Unlock and open halted MO/Cell of the G2 node in OSS-RC

Installation of the Baseband 52

Onsite integration

Add the G2 node in OSS-RC

Remote
  in OSS-RC
Update long lat at CNA
Activities

Synchronize the GSM  NE in the OSS-RC

 
Counter profile activation in OSS-RC

Pos-Check (Verify that all it works well)

Verification G2 node Ready for Service

Success?

Tool and Software Perquisites No Fall-back procedure

 SecureCRT

 WinFiol

 OSS
  Moshell or EMCLI must be installed in the PC, use the last

 SFTP server

 CDR and ATND

 Data Transcripts

 CXP9024418/4_R13FT (16B)

 OSS Ver O16B

 TCU Ver TCU 02_CXP 102 183_2_T15B maint3_R1M

 BSC G16B_IPA0

 License and SAE

Conditions
Current config DCS 6/6/6

1 New RXSTG structure

In the BSC the MO structure for new BBDU has changed. The following structure
should be used. More information can be found in Function Specification BTS
Logical Model G31 Error: Reference source not found

2 MOs which are not needed more for BBDU in BSC

SCGR, SC, RXOCON, RXOIS, RXODP and RXOMCTR Mo will be no longer
needed.

3 MOs which are changed but still represented in the BSC

 RXOTG will became RXSTG

 RXOCF will became RXSCF

 RXOTF will became RXSTF

 RXOTRX, RXOTX, RXORX, RXOTS will became RXSTRX, RXSTX,

RXSRX, RXSTS but all of them will be defined and parameterized
automatically by the RBS MOM

4 New MOs in BSC

 RXSAT MO will be a new MO representing the transmission side

Public
 Public

Preparation Phase
This phase describes the activities that should be performed before the Integrate
new site of the RBS. On this phase is collected the Kget dump of G1 node and
based on this dump are created scripts to integrate the G2 node.

5 Collect CDD/CDR and ATND

Sample data you can get from RND and Team Planning for DCS

CDD_Telkomsel_Swa ATND 2G Abis

p_SMR048MD1_1800.xlsx
IP_Telkomsel_Kalimantan_PA52.xlsx

Execution Phase
This phase describes the activities that should be performed during the
integration of the Baseband 5216. This phase is divided in Onsite activities and
Remote activities. These activities are:
 Pre-Check (Verify that all it works well)
 Adjust CNA for BSC Destination in OSS-RC
 Installation of the Baseband 52
 Onsite integration
 Checking RBS Status
 Connecting Clients and Pre-checks
 Auto integration G2 node (Baseband 52) using onsite configuration files
 Install configuration from RN, TN and final settings
 Add the G2 node in OSS-RC
 Running Enrollment comment
 Netconf configuration files
 Synchronize the G2 in the OSS-RC
 Counter profile activation in OSS-RC
Create Cell
Use Winfiol for Create Cell and same method with G21 model you just copy
paste data script, open new file and F4 for running to BSC destination

CDD_Telkomsel_Swa
p_BPP102MD1_1800.txt

Create MO at BSC

Define sector TG for BPP102E cell

RXMOI:MO=RXSTG-1550,RSITE=MD_VOLVO,SECTOR=BPP102E;

Modify default TG, AT and TF parameters if needed

RXMOC:MO=RXSTG-1550,CONFMD=FASTREC;
RXMOC:MO=RXSAT-1550,MBWDL=16000,MBWUL=16000,MCLTDL=5,MCLTUL=5,OVLTH=25;
RXALC:MO=RXSTG-1550,TGCOORD=OFF;

Define sector TG for BPP102F cell CHGR=0&-1

RXMOI:MO=RXSTG-1551,RSITE=MD_VOLVO,SECTOR=BPP102F_1;

Modify default TG, AT and TF parameters if needed

RXMOC:MO=RXSTG-1551,CONFMD=FASTREC;
RXMOC:MO=RXSAT-1551,MBWDL=16000,MBWUL=16000,MCLTDL=5,MCLTUL=5,OVLTH=25;
RXALC:MO=RXSTG-1551,TGCOORD=OFF;

Define sector TG for BPP102F 2 cell CHGR=2

RXMOI:MO=RXSTG-1552,RSITE=MD_VOLVO,SECTOR=BPP102F_2;
!Modify default TG, AT and TF parameters if needed;
RXMOC:MO=RXSTG-1552,CONFMD=FASTREC;
RXMOC:MO=RXSAT-1552,MBWDL=16000,MBWUL=16000,MCLTDL=5,MCLTUL=5,OVLTH=25;
RXALC:MO=RXSTG-1552,TGCOORD=OFF;

Define sector TG for BPP102G cell

Public
 Public

RXMOI:MO=RXSTG-1553,RSITE=MD_VOLVO,SECTOR=BPP102G;
!Modify default TG, AT and TF parameters if needed;
RXMOC:MO=RXSTG-1553,CONFMD=FASTREC;
RXMOC:MO=RXSAT-1553,MBWDL=16000,MBWUL=16000,MCLTDL=5,MCLTUL=5,OVLTH=25;
RXALC:MO=RXSTG-1553,TGCOORD=OFF;

Connect cell to new G31 TG

RXTCI:MO=RXSTG-1550,CELL=BPP102E,CHGR=0&1;
RXTCI:MO=RXSTG-1551,CELL=BPP102F,CHGR=0&1;
RXTCI:MO=RXSTG-1551,CELL=BPP102F,CHGR=2;
RXTCI:MO=RXSTG-1552,CELL=BPP102G,CHGR=0&1;

Bring Sector TGs into service to check Abis connectivity

RXESI:MO=RXSTG-1550;
RXESI:MO=RXSTG-1551;
RXESI:MO=RXSTG-1552;
RXESI:MO=RXSTG-1553;

RXBLE:MO=RXSTG-1550;
RXBLE:MO=RXSTG-1551;
RXBLE:MO=RXSTG-1552;
RXBLE:MO=RXSTG-1553;

Check IP connectivity
RRGSP:MO=RXSAT-1550;
RRGSP:MO=RXSAT-1551;
RRGSP:MO=RXSAT-1552;
RRGSP:MO=RXSAT-1553;

Activate cells
RLSTC:CELL=BPP102E,STATE=ACTIVE;
RLSTC:CELL=BPP102F,STATE=ACTIVE;
 RLSTC:CELL=BPP102G,STATE=ACTIVE;

Wait for resources to come up...

Check global state of MOs

RXMSP:MO=RXSTG-1550,SUBORD;
RXMSP:MO=RXSTG-1551,SUBORD;
RXMSP:MO=RXSTG-1552,SUBORD;
RXMSP:MO=RXSTG-1553,SUBORD;

Check configuration data

RXCDP:MO=RXSTG-1550&-1551&-1552&-1553;

Check cell resources

RLCRP:CELL=BPP102E&BPP102F&BPP102G;

License
Value of Product Number we get from planning, following configuration at site , or
package already set. Make sure license already install

get KeyFileManagement

G2_BPP102GD_1608
24_123420.xml

Ftp File xml at OSS use FTP tool

acc Lm=1,KeyFileManagement=1 installKeyFile

sftp://vx513238@10.164.92.196/home/vx513238/CO/License/G2_BPP103GD_160901_063013.xml

Pass: Password userOSS

check status : poli

Public
 Public

Table License for BB 5216 16B Single

BB5216_MixedMode_
LKF_PA3.xlsx

Create ARNE G2
Once the on-site integration configuration has ended, then, the G2 node must be
added into the OSS-RC. Follow the next steps:
 Open OSS Explorer
 Go to ONMR  Topology  Right button in “Site” and press “Add Site”

Fill in text box include siteID, location and Long lat

 Go to ONMR  Topology  Right button in “Site” and press “Add

Network Element”

Fill in text box Signature for Managed Element ID , “Type” set the value
RadioNode and in “Is managed” set the value TRUE.
Introduce the “Subnetwork”=AXE, in “Site”, put the name of the site , in
“Platform” RadioNode, in “Network Element version” 16B,Managed Functions
Select “Bts” and then press “Next”

Select in “ManagementNode” ONMR under “BSC destination” and press “Next”

button

Public
 Public

Introduce the O&M IP address of the G2 node and the FTP servers that you are
going to use for it. Press “Next”. It is really important includes the
FtpService=c-uplink-slave" AssociationType="ManagedElement_to_ftpUplink

FtpService=w-back-slave" AssociationType="ManagedElement_to_ftpBackupStore

FtpService=w-config-slave" AssociationType="ManagedElement_to_ftpConfigStore

FtpService=w-key-slave" AssociationType="ManagedElement_to_ftpLicenseKeyStore

FtpService=w-sws-slave" AssociationType="ManagedElement_to_ftpSwStore

Press “Next”
In this step, four protocols must be configured, NETCONF, SFTP, SNMP and
SSH. The information that must be fulfilled for each protocol is the following:

a) Protocol Type: NETCONF, Port:6513

b) Protocol Type: SFTP, Port:2024

Public
 Public

c) Protocol Type: SNMP, Port: 161, Version: v2c and Community String:
public.

It is really important to define this properly, wrong configuration in this

protocol could produce problems sending the alarms, etc.

d) Protocol Type: SSH, Port: 2023

Introduce the Ldap credential for theses nodes. User and password must be
defined by the OSS team and provided by them. With user combase and
Password : Ericsson , Type: Normal and

Type: SECURE

Public
 Public

Click Finish waiting until proses complete

Start Online Enrollment

Running command Enrollment
Acc SystemFunctions=1,SecM=1,CertM=1,NodeCredential=1
startOnlineEnrollment

Pass: NULL
 Print after running Enrollment

BPP102GD_VOLVO> lpr trust

===================================================================================

Proxy MO

===================================================================================

4827 SystemFunctions=1,SecM=1,CertM=1,TrustCategory=1

4828 SystemFunctions=1,SecM=1,CertM=1,TrustedCertificate=1

4829 SystemFunctions=1,SecM=1,CertM=1,TrustedCertificate=2

4830 SystemFunctions=1,SecM=1,CertM=1,TrustedCertificate=3

4831 SystemFunctions=1,SecM=1,CertM=1,TrustedCertificate=4

4832 SystemFunctions=1,SecM=1,CertM=1,TrustedCertificate=5

===================================================================================

Total: 6 MOs

BPP102GD_VOLVO>

Delta Loading XML

Running command Delta

Delta_NetConf_BPP1
02GD_VOLVO.xml

!ssh -o PubKeyAuthentication=no -o UserKnownHostsFile=/dev/null -o ForwardX11=no -p 830

rbs@10.235.230.47 -s netconf < /home/vx513238/earisia/Delta_NetConf_BPP102GD_VOLVO.xml

Pass: rbs

Print after Running

BPP102GD_VOLVO> authtrace combase

160919-00:36:39 10.235.230.47 16.0n MSRBS_NODE_MODEL_305.28792.61_3974 stopfile=/tmp/130

coli>/secm/authtrace combase

AA-trace: 2016-09-18 17:36:40.787708 Trace printing of authorization, parameter info:

primary ldap server IP: "10.164.92.228"

secondary ldap server IP: undefined

Public
 Public

server port: 636

connect options: [{tcpopts,[{ip,{10,235,230,47}},

{netns,<<"/var/run/netns/fib_3">>}]}]

DN for binding:
"cn=proxyagent,ou=proxyagent,ou=com,dc=ldap,dc=ran5,dc=telkomsel,dc=co,dc=id"

bind password (encrypted): {'EcimPassword',undefined,

"1:KA4tqkD/4Yh8j5M8ib981WbojJUVXCIj"}

base DN: "dc=ldap,dc=ran5,dc=telkomsel,dc=co,dc=id"

number of ca-certs: 6

node credentials available: true

A-trace: 2016-09-18 17:36:41.225634 Query aggregation process completed successfully

AA-trace: 2016-09-18 17:36:41.225780 Query result: {true,

["Bts_Application_Administrator",

"RBS_Application_Operator",

"ENodeB_Application_SecurityAdministrator",

"NodeB_Application_Administrator",

"ENodeB_Application_Administrator",

"SystemSecurityAdministrator",

"SystemAdministrator"]}

coli>

BPP102GD_VOLVO>

Check at OSS Comment Explorer NE should be SYNC

 NOTE: If the licenses are not present in the G2 node, then activate the
IntegrationUnlock.
acc IntegrationUnlock=1 activate

Make a backup
acc BrM=1,BrmBackupManager createBackup
y
After_setting

Restart the node manually after the Feature Activation completed

acc FieldReplacementUnit=1 restartUnit
1
0
0

Adjustment, Update NE ID and Long Lat

a). Adjust BSC destination and set action on faulty “continue..”

Waiting proses until complete

Public
 Public

b). After Adjust complete, create new planned area, update Long Lat and NEID
Column comments. and update long lat at Cell Level.
 All Cell need to update

Update NE and long Lat

Counter profile activation in OSS-RC

The Performance Management Support (PMS) in OSS,we will activate the
counters through OSS.

Public
 Public

Fallback procedure
Not requirement and not mentioned because new element

Health check and to consideration

6 Take log after, check traffic and alarm
• Limited set of alarm situations for TG/MO fault
• New alarm situation: SUSPECTED FAULTY (instead of legacy
PERMANENT FAULT)
• No administration for fault maps (no Fault Reports, no RXMFP on G31)
• Default TG coordination level
• Legacy generic functionality for printing of alarms is applicable for G31 as
well

At BPP102GD_VOLVO need to check

MD_VOLVO_LOG_AF
TER_MIGRATION_to_BB.log

get . abisTrxcOmlState
get . abisTrxRslState
get . abisTxState
get . abisRxState
get . abisTsState
get . arfcnMax|arfcnMin
get . bscMaxTxPower
get . bscTgIdentity
lst GsmSector
get . mixedmoderadio
alt
7 SAE before migrate require to increase

RESTRICTING BLOCK = RXSRPM

RESTRICTING BLOCK = RXSLS
RESTRICTING BLOCK = RXSLDF
RESTRICTING BLOCK = RXSLH 

8 Combase user have GSM role at OSS,

Profile for GSM should be “Bts_Application_Administrator”.

9 Sample Script for GSM Type

A_BPP102GD_VOLVO
.rar

10 Take log BB with dcgfm -k 1

11 Power setting between BSC and BB

Public
 Public

12 TRX configuration standard

References

CPI :
EN/LZN7180301  R1A    BSC G16B APZ 212 55/60C/60F with APG43L

EN/LZN 719 0031  R1L GSM RAN G16B

BB5216 GSM RAN in G2 E2E site Integrate new site