Scope Document/MOP

Network Integration Activity McBSC

1 22/10/2019 © Nokia 2014

For internal use
 Table of Contents

• Introduction

• Limitation

• Checklist

• BTS configuration

• BSC Configuration

2 22/10/2019 © Nokia 2014

For internal use
 INTRODUCTION

• There is no TDM scope in McBSC.

• No DAP configuration required in McBSC, Here ETP PCU connection need to be create for data traffic.

• Customer can plan N/W for McBSC by 2 ways

• 1)1 VLAN concept(Where single VLAN IP N/W carry both M Plane & CP/UP traffic.

• 2)2 VLAN concept(Where 2 VLAN used,1 IP N/W for M &other for CP/UP)

• Static route creation(eep Interface) required to carry traffic for A interface.

• No need for configuring ET’s to ABIS/ATER/GB ,Its pre configured cards.

• ETME<Mutilcontroller ET for Ethernet ABIS> Meant for carrying ABIS traffic, Hence sites need to be attached with
ETME(Same as ET16 card for electrical E1”s)& ETS2 card for optical E1’s in BSC3i OR Flexi BSC.

3 22/10/2019 © Nokia 2014

For internal use
 INTRODUCTION

• ETMA<Mutlticontroller ET for A interface for carrying A traffic.

• Here in McBSC BCSU replaced with BCXU ,major change here we have separate unit for data traffic(PCUM-
Multicontroller packet control unit) Noramlly in BSC3i or Flexi BSC, PCU2D or PCU2E is a part of BCSU(Which we
can extend by 5 card in single BSCU unit)

• Depends upon the data traffic requirement we keep configure card as PCUM in same module.

4 22/10/2019 © Nokia 2014

For internal use
 Limitation

• One NSEI/PCU can be attached with single ETME’s only.

• ERROR(PCU NOT connected to ETP of the BCF) Means BTS can be attached with only those NSEI/PCU’s in
which ETP PCU connection made.

• ERROR(ETP-PCU connection already exist) Means Connection already established with some other ETME’s

• In static route creation, One Subnet can be attached with single ETME’s(EEP interface) only.

For example if one subnet contains 10 sites and half of the sites are attached with single ETME’s and half with other
ETME’s, Than only half of the sites can carry traffic in A interface, and all call on other sites get dropped at A
interface(Which leads call muting issue)

5 22/10/2019 © Nokia 2014

For internal use
 Check list at BSC End
• Association set creation.(ZOYX) by MML

• IP assignment for created association (ZOYP) by MML

For OMU ( Source address is BCXU’s IP configured for OMU) & destination address is Destination_IP (BTS_oam IP) ie Mplane IP.

For TRX (Source address is BCXU’s IP configured for CP/UP and destination address is Destination_IP (BTS_cp/up IP)

• Attaching created association with Lapd’s(ZWDP) Note: Here also SAPI&TEI values comes in picture.

• Activation of association set(ZOYS)

• BCF creation by MML(ZEFC) VLAN must be same for all sites created in a BSC, Mplane IP is BTS O&M IP and CP/UP ip is the
one which is used for TRX’s association creation.

• BTS/TRX creation by XML’s.

• External Alarm creation(ZEFX)

• Check whether S/W is attached(ZEWO:<BCF>:

• Static route creation of concern ETME’s eep IP with all ETMA’s(ZQKC).

6 22/10/2019 © Nokia 2014
For internal use
 BTS End Configuration

7 22/10/2019 © Nokia 2014

For internal use
1. Check the “Use Vlan “ Box
2. Specify the Vlan for management plane and Cp/Up as per datafill

8 22/10/2019 © Nokia 2014

For internal use
1. Specify the IP addresses as per datafill
2. Specify the Vlan for management plane and Cp/Up GW as per datafill

9 22/10/2019 © Nokia 2014

For internal use
1. Define both Vlans as defined for management and Cp/Up

10 22/10/2019 © Nokia 2014

For internal use
 Synchronization

11 22/10/2019 © Nokia 2014

For internal use
1. Define Synch for Time over Packet Top (IEEE 1588 ) as priority 1.
2. Check box “enable Top”
3. Define the Top master Ip address as below.
4. Keep the Optional parameters as it is, shown below.

12 22/10/2019 © Nokia 2014

For internal use
 BSC End Configuration

13 22/10/2019 © Nokia 2014

For internal use
Source IP for TRX and OMU

14 22/10/2019 © Nokia 2014

For internal use
 IP ADDRESSES
(ZOYV.. FOR DISPLAY of Association and ZDWQ for Lapd’s)

BCXU IP ADDRESS SOURCE ADDRESS1 : 10.114.42.77( omu –sig ) -- OMU Association

TRX Association SOURCE ADDRESS1 : 10.114.42.77( (trx-sig) --TRX Association (Don’t follow DF for this,All TRX’s
must be divided equally among all BCXU’s

Primary Destination Address TRX Association : BTS CP/UP IP ADDRESS

Primary Destination Address OMU Association : BTS O&M or M pane IP ADDRESS

Source and Destination port always same for all Association(for OMU it should be 49152,and TRX1 49153 and so
on…)
Netmask length for this N/W is standard ie /26

15 22/10/2019 © Nokia 2014

For internal use
 mcBSC End Configurations
1. Creation of BCF with separate M-plane and C/U-plane Ip’s as shown below : ZEF..

2. Creation of OMU SCTP Association Output:

a. Assign omusig Vlan BCXU IP as Source address 1 as per datafill
b. Assign BTS O&M ip as the primary destination IP as per datafill

16 22/10/2019 © Nokia 2014

For internal use
3. Creation of Trx SCTP Associations Output:

a. Assign Trx sig Vlan BCXU IP as source address 1 as per datafill

b. Assign Bts Cp/Up IP as the destination IP as per datafill

17 22/10/2019 © Nokia 2014

For internal use
 Static Route Creation
Requirements:
 ETME id of the BCF(ZEFO:)

 Find out EEP interface IP of same ETME’s(ZQRI:ETME,0;)

18 22/10/2019 © Nokia 2014

For internal use
 Static Route Creation

 Static route must be defined with site Subnet ip or M-Plane IP and ETME EEP IP to all ETMA’s configuring in
BSC.


19 22/10/2019 © Nokia 2014

For internal use
20 22/10/2019 © Nokia 2014
For internal use