Office Of The Dy GM (BROADBAND), DNW

Bangalore East Telephone Exchange Bldg

BANGALORE: 560005

To,
All Circle coordinators for Broadband
All Broadband Node incharges

No. Addl.GM(BB)/BBNW/BG/Guidelines/RNC-NODE B/2011-12 dated 4/7/2011

Sub: Guidelines for RNC-NODE B connectivity in 3G using ports on Multiplay NEs.

As per the instructions from Broadband Cell of BSNL CO circles / SSAs can use the
ports on the Multiplay NEs for the connectivity of RNC- NODE B of 3G Mobile
network. Since these NEs are carrying the traffic of Internet users, VPN users, ILL,
IPTV, WiMAX and IPTAX, circles / node in charges are requested to take care of the
following points while escalating the requests for RNC & NODE-B connectivity to
ensure smooth flow of traffic.

1. Clock server connection shall be made using port on the MPLS L3PE

2. RNC is to be preferably connected on the port of RPR T1 to ensure redundancy

in the connection. However, the same can be connected on T2 also. Since the
OCLANs are not in the Resilient Packet Ring RNC connection on OCLAN should be
avoided.

3. In order to establish connectivity of one RNC with the NODE-Bs on the other
Rings, T1 ports of other ring has to connected to RNC using external media. (Refer
block schematic on page no. 4)

Alternatively RNC need be connected on MPLS using L3PE port, for which feasibility
may be obtained from MPLS.

4. Node-B can be connected using FE / GE ports of RPR T1/T2 and OCLAN switches.

5. While connecting the Node B on the OCLAN switch following points are to be taken
care.
a. Uplink capacity of OCLAN shall be GE. Hence, action may be taken to
upgrade the uplink to GE before sending requests for NODE-B connection

b. No. of NODE-Bs proposed to be connected on the same OCLAN shall be

decided after assessing the total traffic from all the services on the OCLAN
uplink port. While assessing the requirement of uplink capacity, number of
DSLAMs connected and traffic thereon, traffic from the NEs on the cascaded
chain, no. of ILLs serviced etc., traffic from WiMAX BTS are to be taken
into account.

Page 1 of 5
 Example: Internet / IPTV traffic-- 60% of uplink(Mandatory); 600 Mbps
High speed ILL serviced, like NMEICT etc.,-- 155 Mbps

Remaining 200 Mbps capacity can be utilized for connecting 4

NODE-Bs. @ around 50 Mbps ultimate traffic per NODE-B
(14.4 Mbps X 3 sectors)
Apart from this traffic from WiMAX / IPTAX have to be
considered, if connected.

7. While utilizing the ports on RPR T1/ T2 and OCLAN it may be ensured that
sufficient spare ports (about 5) are kept for maintenance purposes.

8. RPR does not support single mode SFP for its FX port. So in most of the cases,
the OF cable/LAN cable from several Node-Bs to an available MADM and an
aggregated GE has to be brought to RPR. The selection of RPR/OCLAN for the
Node-B to be taken considering optimum BW utilization of the MADM ring.

9. As such, the options for extending Node-B FX/FE port to RPR/OCLAN/MADM

is by direct fiber or through CPE with FE port or through LAN cable in exchanges.
May be OF splitter can be tried where only one pair of fiber is available.(but
require 4 units for one site and corresponding SFP also)

NODE B SIDE CONNECTIVITY

OPTION 1 : FE OPTICAL OPTION 2 : FE Electrical
Requirement; Requirements;
1.SC LC or FC_LC or LC-LC Patch cord 1) Electrical Ethernet cable with RJ45
NodeB end is LC type and the other end can connector
be changed depend on the far end device
port
2.SFP module: wavelength depend on
connecting device

CONNECTING TO WMPT CARD OF BTS 3900

( Drawing: Courtesy Kerala Telecom)

Page 2 of 5
 NODE B BBU _ WMPT CARD FOR IP INERFACE

FE0 & FE1 PORTS CAN BE USED FOR CONNECTING

NODEB TO IP NETWORK

FE0 PORT: Fast Ethernet Electrical

Max Speed 100Mbps
Connector Type RJ45

FE1 PORT: Fast Ethernet Optical

Max Speed 100Mbps
Connector Type
LCconnector
SFP module Required

( Drawing: Courtesy Kerala Telecom)

10. Node-B may also be connected on FE port of the switch that is provided
for connecting RPR port to WiMAX BTS. However, this need be done with
the confurrence of WiMAX incharge. In such cases node incharge has to
furnish the port details of RPR where this switch is connected so that NOC
will take action to pass the VLAN of NODE-B on the same RPR port.

11. Trouble shooting : RNC-NODE B connectivity is established on Layer 2.

NOC will be able to check configuration on the Multiplay port, the status of port
& learning of MAC ID of 3G equipment on the downlink and uplink port of the
NE.

12. Speed on the ports where NODE-B is connected will be restricted to 50 Mbps at
port level.

Page 3 of 5
TYPICAL RNC-NODE B CONNECTIVITY DIAGRAM USING MULTIPLAY
PORTS

Page 4 of 5
 Template for sending requests to Bangalore NOC on bbnoc_mp@bsnl.in
For cases related Western region escalate to Pune Team on mpnocpune@gmail.com

3G-RNC NODE-B
CLOCK SERVER VLAN

CONNECTIVITY CONNECTIVITY

3G-RNC /NODE-B
CLOCK SERVER IP

DETAILS DETAILS

Contact details
PORT

PORT
T1/T2/OCLAN
RPR
BNG IP

VLAN
RPR T1/T2 IP
POLL

RPR T1/T2
LOCATION

LOCATION

incharge
/OCLAN IP
RPR T1/T2

of node
NOTE: When NODE-B is to be connected using OCLAN Port, following information shall
also be provided in addition to the above

1. Uplink capacity of OCLAN

2. In case of cascaded OCLANs, how many OCLANs are there in the chain
3. How many DSLAMs are connected to the OCLAN including the ones in the
cascading chain of OCLAN.
4. No. of WiMAX BTS configured on the OCLAN

ISSUED BY
Addl.GM(BB), BBNW
BANGALORE-560 005

Page 5 of 5