Académique Documents
Professionnel Documents
Culture Documents
Date: 08-02-2011
Agenda
IuCS Interface
IuPS Interface
DCN Interface
IuB Interface
Troubleshooting Guidelines
Confidential
Slide 2
RDN
RIN
RGN
Confidential
MEN
DCN
Slide 3
3G Functional Entities
Confidential
Slide
3G Overview
In a 3G Setup
The NodeBs { BTSs (Base
Transceiver Stations) } are
connected on Access Data
N t
Network
k to
t the
th RNCs
RNC (R
(Radio
di
Network Controller)
Confidential
Slide 5
3G Overview Continued
In a 3G Setup on the RNC Side
The
Th Interface
I
f
from
f
the
h RNC towards
d the
h C
Core voice
i iinfrastructure
f
iis called
ll d
the IuCS Interface
The interface from RNC towards the Core Packet infrastructure is called the
IuPS interface
The IuCS talks to MSCs / STP / HLR etc for signaling purpose
y) for transmitting
g voice & video traffic
The IuCS talks to MGW ((Media Gateway)
It carries both Voice + Video & Data on the same interface towards RNC from the NodeB
devices
There
e e is
s sepa
separate
ate management
a age e t interface
te ace o
on RNC
C to g
give
e management
a age e t
information to centralized management infrastructure
In the upcoming
g slides we will see how these are mapped in RCOM
Confidential
Slide 6
3G Overview in RCOM
Various traffic components on
a 3G RNC are as under:
The Voice Traffic (IuCS)
flows on RDN
The Packet data traffic
(IuPS) flow on RIN
The NodeB traffic comes to
RNC on the MEN
The
Th Management
M
t traffic
t ffi
flows on DCN
Confidential
Slide 7
3G in RCOM
In a 3G RNC Setup
Two
T
RNC V
Vendor
d are selected
l
d
Confidential
Slide 8
Phase-1
Assam
- 399
Bihar
- 629
Delhi
- 2886
Himachal Pradesh - 87
Jammu & Kashmir - 440
Kolkata - 1650
Madhya Pradesh - 698
Mumbai - 2660
North East - 478
Orissa - 478
Punjab - 872
Rajasthan
j
- 795
West Bengal - 321
Confidential
Slide
Confidential
Slide 10
Confidential
Slide 11
Date: 08-02-2011
Confidential
Slide 13
Confidential
Where all the RNCs are Collocated the IuR traffic does
not flow on RDN, it gets switched on RNC Switch itself
Where all the RNCs are not collocated the IuR traffic gets
switched through the RDN (e.g. Faridabad)
Slide 14
Confidential
Slide 15
Confidential
Slide 16
Confidential
Slide 17
Node-B
Node
B to RNC Connectivity
Date: 08-02-2011
Confidential
Slide
VLAN Assignments
Confidential
Slide
Confidential
Slide
Connectivity
between- ZTE
Node-B
B
Network Topology
ZTE RNC & Node
Confidential
Slide
At fiber BTS site MEN NE will be available and it will be part of MEN Ring.
To keep the identical architecture for 3G , Port Number FE-08
FE 08 to FE-14
FE 14 are
proposed ( in case the proposed ports are in use, circle FA deploy team to
assign new ports) for connecting the Node-B to MEN switch.
These ports will be configured as a trunk port. By default Node-B management
VLAN 56 will be allowed and service VLAN to be configured against the Node-B
service SO
Confidential
Slide
Scenario 2
Node-B Connectivity
Node-B is connected behind 1st Hop SDH and another Node-B connected
behind 2nd Hop PDH card.
For making connectivity from 1st Hop Node-B to Take-off site NE, it has been
proposed to install the CX-200 at 1st Hop BTS location below SDH MW
connecting to L1 card or IMAP card of SDH NE.
To make this CX-200
CX 200 RFS and to carry the Node
Node-B
B service and Management
traffic , bearer needs to be created between this CX-200 to take off site
Confidential
Slide
Scenario 2 contd..
Node-B
Connectivity
For making connectivity from 2nd Hop Node-B to Take-off site NE, Node-B will
connect to ethernet card. Also the PDH will connect to CX-200D installed at 1st
HOP BTS location to carry this traffic to RNC
However FA_DEPOY_CIRCLE team has to provide the correct interface details
of take-offsite NE for each Node B provisioning.
Confidential
Slide
Scenario 3
Node-B Connectivity
Two PDH HOPs are terminating on CX-200 installed at 1st Hop BTS location
FA_DEPLOY_Circle team to give the correct Interface details of take-off site and
respective Node-B service SO
Confidential
Slide
Scenario 4
Node-B
Connectivity
The IP Radio link terminating on Fiber BTS MEN NE
Node B will connect directly to IP Radio for 1st HOP and 2nd Hop Node-B will
connect to PDH Ethernet card
card.
The bearer to be provisioned in each Hop based on availability of bandwidth. In
case of IP Radio the bandwidth required other than 2G BTS to be converted to
IP radio
Confidential
Slide
Scenario 5
Node-B Connectivity
The IP Radio link will terminate on Fiber BTS MEN NE and Tail-End NEs are
PDH MW
Deployed CX-200D below IP radio for serving more than one PDH link
IP Radio has 4 number of ethernet ports , In case of Ethernet port requirement is
more than four then we are proposing to commission CX-200D below IP radio
Confidential
Slide
Scenario 6
Node-B
Connectivity
To provision CX200D at BTS location for bearer provisioning
For bearer creation we are proposing 60Mbps bandwidth on each hop, In case
60Mbps is not available
available, provisioining can be made based on available
bandwidth, provided at leaset 2Mbps*no. of NodeBs downstream is available
Confidential
Slide
Scenario 7
Node-B
Connectivity
To provision CX200D at BTS location for bearer provisioning
For bearer creation we are proposing 60Mbps bandwidth on each hop, In case
60Mbps is not available
available, provisioining can be made based on available
bandwidth, provided at leaset 2Mbps*no. of NodeBs downstream is available
FA_DEPLOY_CICLE has to map correct port of take off site for provisioning the
Node-Bs service vlans
Confidential
Slide
Scenario 8
Node-B Connectivity
Confidential
Slide
Scenario 9
Node-B
Connectivity
This Scenario is same like the scenario number 8. CX-200D is proposed below
each SDH NE
F providing
For
idi th
the protection
t ti tto thi
this TX route,
t M
Manuall B
Bearer SO tto be
b raised
i db
by
circle team from last point to aggregation location for total amount of bandwidth.
Confidential
Slide
Confidential
Slide
BW to be provisioned
in Microwave SDH
Bandwidth
Provisioning
BW tto b
be provisioned
i i
d in
i IP Radio
R di & Microwave
Mi
PDH
Maximum Available Bandwidth (As per NPE-MW guideline)
Confidential
Slide
Confidential
Port No. 1
Port No. 2
Port No. 3
Port No. 4
Slide
Confidential
Slide
Troubleshooting Guidelines
Date: 08-02-2011
Troubleshooting Guidelines
Following are the generic troubleshooting guidelines
Check the physical cabling
Check the indicators lights of connectivity are glowing at both the ends of the
connectivity in subject
If found ok, ask the RNC team to ping as per the required service
If issues
i
follow
f ll
th
the d
detailed
t il d troubleshooting
t bl h ti guidelines
id li
given
i
b
below
l
Confidential
Slide 38
Confidential
Slide 39
If nott pinging
i i check
h k th
the llocall connectivity
ti it
If pinging & problem persisting move to following
steps
Confidential
Slide 40
If nott pinging
i i check
h k th
the llocall
connectivity
If pinging & problem persisting move to
following steps
Pi the
Ping
th Local
L
l DCN iinterfaces
t f
(2)
Confidential
To summarize we discussed
IuCS Interface
IuPS Interface
DCN Interface
Troubleshooting Guidelines
Summary
Confidential
Slide 42
Thank you
y
Date: 08-02-2011