# IUCS INTERFACE

There is separate management interface on RNC to give management information to centralized management infrastructure

Various traffic components on a 3G RNC are as under:

IV.   


# IUPS INTERFACE


# CONCLUSION

Wireless technologies are a way for mobile users to make free or cheap calls worldwide and save a lot of money due to the latest telephony applications and services. 3G networks have the advantage of being available on the move, unlike Wi-Fi, which is limited to a few meters around the emitting router. So, a user with a 3G phone and a 3G data plan is well-equipped for making free mobile calls. She will only have to download one of the free applications and install on her mobile phone and start making calls 
![Station ControllerThe Iu interface is an external interface that connects the RNC to the Core Network (CN).The Uu is also external, connecting the Node B with the User Equipment (UE).The Iub is an internal interface connecting the RNC with the Node B The Iur is an internal interface connecting two RNCs with each other.Reliance MEN network is acting as a IP mobile backhaul Transport connectivity between IuB interface at RNC & NodeBs II. 3G OVERVIEW In a 3G Setup The RNCs Connect to 3G Core components (Like MSC /STP / HLR / SGSN/CGSN) on a Core Data Network In a 3G Setup on the RNC Side The Interface from the RNC towards the Core voice infrastructure is called the IuCS Interface The IuCS talks to MSCs / STP / HLR etc for signaling purpose The IuCS talks to MGW (Media Gateway) for transmitting voice & video traffic Global Journal of Researches in The interface from RNC towards the Core Packet infrastructure is called the IuPS interface Through the IuPS interface the RNC talks to SGSN/CGSN The Interface from RNC to NodeB is the IuB Interface It carries both Voice + Video & Data on the same interface towards RNC from the NodeB devices 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 Management traffic flows on DCN Two RNC Vendor are selected Huawei for the RCOM Circles ZTE for the RTL Circle From the connectivity Architecture perspective there is no difference between two vendors There are total 45 RNC across 31 Locations RNC is connected to network through RNC Switches For HUW RNC the RNC Switch is Cisco 7606 / Cisco 3800 For ZTE RNCs the Confidential Slide RNC Switch is Cisco 3750 III.](image-2.png "")
![From the RDN CAS to RDN PE it goes on the existing connections o The VLANs from RNC to RDN PE are o Vlan 416 for Signaling i.e. IuCS -CP o Vlan 417 for Media i.e. IuCS -UP o Each instance has VRRP on RDN Confidential Slide b) 3G RNC : IuCS Traffic -Non Collocated Sites Wherever the RNC is not collocated with the RDN, the RNC is extended on the Transport Link as shown (e.g. Jamshedpur / Gwalior /Rourkela etc.) o Transport links (GEoSDH) are provisioned with 2CNO As per the requirement appropriate VC4s are allocated on the Transport network Rest of the architecture is same as the collocated RNC The IuR is InterRNC traffic o Where all the RNCs are Collocated the IuR traffic doesnot flow on RDN, it gets switched on RNC Switch itself o Where all the RNCs are not collocated the IuR traffic gets switched through the RDN (e.g. Faridabad)](image-3.png "o")
![c) 3G RNC : DCN Traffic -The RNCs have dual DCN interface towards the RNC DCN switch o For HUW RNC the interface is Electrical Gig o For ZTE RNC the interface is Electrical Gig The RNC DCN Switch is a L3 Device o It runs VRRP for redundancy towards DCN o And also towards the DCN ports of RNC The Uplinks from RNC DCN Switches are terminated on the DCN Switches in a redundant Fashion The RNC DCN Switch & DCN Switch runs VRRP protocol to give redundancy On the same RNC DCN Switch OMCR is connected At all RNC Locations Dual DCN Switches are present & functional Fast convergence triggering mechanism such as VRRP with BFD is proposed to be implemented at RNC to MEN connecting interfaces. VLAN Assignments Management VLAN for Node-B Management Vlan for both Huawei and ZTE Node-Bs -VLAN 56 Node-Bs under one BAN will be placed on a separate management VLAN (VLAN56). Management VLAN of Node-B to be passed start from the connecting interfaces of BN nodes till Parenting BAN in the corresponding ring. Service VLAN for Node-Bs Range of Service Vlan for both Huawei and ZTE Node-Bs -VLAN 1600 -1900 Each Node-B under one BAN is assigned with separate VLAN for services and attached with the common service VRF created in the BAN. Service VLAN of Node-to be passed start from the connecting interfaces of BN nodes till Parenting BAN in the corresponding ring. Scenario 1 BTS on fiber site -Node-B Connectivity At fiber BTS site MEN NE will be available and it will be part of MEN Ring. To keep the FE-FE-14 identical architecture for 3G , Port Number FE 08 to FE 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 SONode-B to RNC Scenario Node-B Connectivity Node-B is connected behind 1st Hop SDH and](image-4.png "")
![connectivity is OK, then Login into the RNC DCN Switch & follow the below mentioned guidelines Ping the Local DCN interfaces (1) o not pinging check the local connectivity o If pinging & problem persisting move to following steps Ping the Local DCN interfaces (2) o If not pinging check the local connectivity o If pinging & problem persisting move to following steps Ping the End Devices (3) o If not pinging escalate to NOC](image-5.png "")
			© 2012 Global Journals Inc. (US) The NodeBs{BTSs (Base Transceiver Stations)} are connected on Access DataNetwork to the RNCs (RadioNetwork Controller)