Solution Design (India)

Functional Design Document

3G Backhaul For Bharti Low Level Design Approach NCR location

Document Edition: I

Design Document

Solution Design (India)

Copyright by ECI Telecom Ltd., 2014. All rights reserved worldwide. This is a legal agreement between you, the end user, and ECI Telecom Ltd. ( "ECI Telecom"). BY OPENING THE DOCUMENTATION AND/OR REVIEWING THE DOCUMENTATION AND/OR OPENING THE DISK PACKAGE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND BINDERS OR OTHER CONTAINERS) TO THE PLACE FROM WHICH YOU OBTAINED THEM. The information contained in the documentation and/or disk is proprietary and is subject to all relevant copyright, patent and other laws protecting intellectual property, as well as any specific agreement protecting ECI Telecom's rights in the aforesaid information. Neither this document nor the information contained in the documentation and/or disk may be published, reproduced or disclosed to third parties, in whole or in part, without the express, prior written permission of ECI Telecom. In addition, any use of this document, the documentation and/or the disk, or the information contained therein for any purposes other than those for which it was disclosed, is strictly forbidden. The documentation and/or disk and all information contained therein is owned by ECI Telecom and is protected by all relevant copyright, patent and other applicable laws and international treaty provisions. Therefore, you must treat the information contained in the documentation and/or the disk as any other copyrighted material (for example, a book or musical recording). Other Restrictions. You may not rent, lease, sell or otherwise dispose of the documentation and/or disk, as applicable. YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR ANY COPY IN WHOLE OR PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE. ALL RIGHTS NOT EXPRESSLY GRANTED ARE RESERVED BY ECI TELECOM. All trademarks mentioned herein are the property of their respective holders.

ECI Telecom Ltd. Proprietary

Page 2 of 22

Document Edition:

Design Document

Solution Design (India)

Document Control
Document History The following table records information regarding released editions of this document. Edition ID 1 Release Date 31/8/2010 Author Kalyan Mukherjee Description of Changes First Draft

Document Approvals This edition has been approved by: Title Approval-1 Approval -2 Name Signature Date

Open Issues This part of the document control section is used to record and track open issues and/or unresolved questions. As the development of this document proceeds, these issues and questions should be resolved and removed from the list. No. 1. 2. 3. Subject/Section Description

ECI Telecom Ltd. Proprietary

Page 3 of 22

Document Edition:

Design Document

Solution Design (India)

Table of Contents
1. Introduction .............................................................................................................................................. 6 1.1. Purpose ............................................................................................................................................... 6 1.2. Glossary .............................................................................................................................................. 6 1.3. Applicable Documents ........................................................................................................................ 6 2. Design Plan .............................................................................................................................................. 7 2.1. Versions .............................................................................................................................................. 7 3. The typical design of a 3G Network: ..................................................................................................... 8 3.1. What is a 3G Back-Haul? .................................................................................................................... 8 3.1.1. What are the dilemmas of conventional TDM? ............................................................................ 9 3.1.2. What are the dilemmas of deploying a full IP solution? ............................................................... 9 3.1.3. What should be the Ideal solution then? .................................................................................... 10 4. MPLS solution of ECI: ........................................................................................................................... 11 4.1. MOT (MPLS over Tranport Port): ...................................................................................................... 11 4.2. Tunnels and class of service: ............................................................................................................ 11 4.3. Default table of class of service for tunnels: ..................................................................................... 12 5. Physical topology of the network (NCR):............................................................................................ 13 5.1. Thumbrules for creating MPLS domain: ........................................................................................... 14 6. Creation of MPLS network domains and Ethernet PB network IDs Tunneling and Services: ...... 15 6.1. GUV network aggregation: ................................................................................................................ 15 6.1.1. MPLS domain and PB creation in GUV. .................................................................................... 15 6.1.2. Example of how the tunnelling will work in GUV:....................................................................... 16 6.1.3. Services: .................................................................................................................................... 16 6.2. MAL network aggregation: ................................................................................................................ 17 6.2.1. Homing of RNC: ......................................................................................................................... 17 6.3. APH Network Aggregation: ............................................................................................................... 18 6.4. OIE Network Aggregation: ................................................................................................................ 18 6.5. D-184 Network Aggregation: ............................................................................................................ 19 6.6. FMS Network Aggregation: ............................................................................................................... 19 6.7. NP2 Network Aggregation: ................................................................................................................ 19 7. IOP at the RNC location and at the aggregator locations: ................................................................ 20 8. Port Redundancy: .................................................................................................................................. 21 8.1. VRRP with IOP design: ..................................................................................................................... 21 8.2. Creation of the P2MP service: .......................................................................................................... 22

ECI Telecom Ltd. Proprietary

Page 4 of 22

Document Edition:

Design Document

Solution Design (India)

List of Figures/Presentations
Figure 1: Typical architecture of a 3G Back-Haul network: ...................................................... 8 Presentation 2: Presentation on MOT concept ........................................................................ 11 Presentation 3: Presentation on concept of tunnels. .............................................................. 11 Figure 4: Physical design of the network for NCR Core ......................................................... 13 Figure 5: MPLS domain creation in the GUV core. .................................................................. 15 Figure 6: Example of creation of tunnels. ................................................................................. 16 Figure 7: MAL network aggregation .......................................................................................... 17 Figure 8: MAL network remote homing ..................................................................................... 17 Figure 9: APH design of MOT..................................................................................................... 18 Figure 10: OIE design of MOT. ................................................................................................... 18 Figure 11: D-184 design of MOT. ............................................................................................... 19 Figure 12: FMS design of MOT. .................................................................................................. 19 Figure 13: NP2 design of MOT. .................................................................................................. 19 Figure 14: VRRP with IOP ........................................................................................................... 21

ECI Telecom Ltd. Proprietary

Page 5 of 22

Document Edition:

Design Document

Solution Design (India)

1. Introduction
1.1. Purpose
The purpose of this document is to provide a Low-Level design Idea for the 3G Back-haul for Bharti that is going to be done on the existing TDM overlay. This document will explain the following things. Physical design of the Bharti Network section in the 3-G backhaul. Logical MOT architecture of the network section. Tunnel architecture per class. Cos mapping and prioritization of the .1p bit. Service architecture. Traffic shaping.

1.2. Glossary
AIS BIT FC FICON FEC GFP NE RDI REI SD SES SF TIM UAT WTR Alarm Indication Signal Built In Test Fiber Channel Fiber Connection Forward Error Correction Generic Framing Procedure Network Element Remote Defect Indication Remote Error Indication Signal Degrade Severely Error Second Signal Fail Trace Identifier Mismatch Unavailable Time Wait To Restore

1.3. Applicable Documents

EMS BGF User Manual. Lightsoft User Manual.

ECI Telecom Ltd. Proprietary

Page 6 of 22

Document Edition:

Design Document

Solution Design (India)

2. Design Plan
2.1. Versions
Embedded Version: NMS Version: BGF: V8.12 V5.36 V11.3/V12

ECI Telecom Ltd. Proprietary

Page 7 of 22

Document Edition:

Design Document

Solution Design (India)

3.

The typical design of a 3G Network:

The network that needs to be designed for the back-haul of the 3G network is essentially based on the fact that there are various NodeBs (RF access interfaces) and these NodeBs are actually connected or should we say parented to a particular RNC (Radio Network Convergence) node. The work of the RNC is to actually aggregate all the access traffic and then actually send it across to the MSC or the location where the routing and switching of the traffic actually happens.

3.1. What is a 3G Back-Haul?

The work Back-Haul essentially means to support a type of transport for any kind of traffic. However in the case of 3G services this back-haul will be of a different nature as compared to the conventional TDM backhaul for existing Mobile services of 2G.

MSC RNC Core back haul

POP RNC Acces s BackHaul

RNC-1 (Radio Network Convergence)

RNC-2 (Radio Network Convergence) RNC POP Acces s BackHaul POP POP

POP

Node B Cluster

POP

Figure 1: Typical architecture of a 3G Back-Haul network: In the network the scope of back-hauling that differs from the conventional mode of transport TDM backhauling is as follows. 1. The transport has to be Bandwidth efficient. 2. The back-haul has to be optimized and prioritized with respect to traffic.

ECI Telecom Ltd. Proprietary

Page 8 of 22

Document Edition:

Design Document

Solution Design (India)

3. The back-haul should support redundancy at lower restoration rates and lower convergence rates however should not consume excessive resources to provide this redundancy. 4. At any point of time when the redundancy is not utilized the bandwidth should be utilized by the other services that are running on low class. 5. There should be a guaranteed Band-width for a service and there should be an excess Bandwidth dedication for the service which should have a status quo of availability in case the ring is having no failure.

3.1.1. What are the dilemmas of conventional TDM?

The following arguments may stand against deployment of conventional TDM for the said services above. a) Conventional TDM redundancy architectures are grossly BW consuming. b) There is no BW efficiency. c) There is less possibility of utilization of BW dedicated for protection for low priority traffic (except MSSPRING). The following arguments may stand for the deployment of conventional TDM for the services. a) Easy provisioning. b) Good redundancy and low convergence timings. c) Suites the need of the recent equipment developed.

3.1.2. What are the dilemmas of deploying a full IP solution?

The following arguments may stand for the deployment of IP. a) New technology. b) Resilient and scalable. The following arguments may stand against the deployment of full IP network. a) Higher convergence times. b) Convergence times are reduced but that is subject to a control frame budgeting which eats up part of the BW of the network. c) Need for deploying total new infrastructure. d) Need for man-power having knowledge of control plane architecture and L3 protocols. e) CLUI provisioning is there in most of the IP networking equipments which makes provisioning cumbersome.

ECI Telecom Ltd. Proprietary

Page 9 of 22

Document Edition:

Design Document

Solution Design (India)

3.1.3. What should be the Ideal solution then?

An ideal solution should be a platform that involves all advantages of Data L2/L3 networking without their limitations and also involved the advantages of the conventional TDM architecture. So as to say, it should have the following. 1. 2. 3. 4. 5. 6. 7. Ease of provisioning from GUI just like the TDM. Ease of understanding the concept. Efficient BW management. Low convergence in redundancy reroutes. Optimized BW solutions. BW sharing of the resources. Use of existing network infrastructures.

ECI Telecom Ltd. Proprietary

Page 10 of 22

Document Edition:

Design Document

Solution Design (India)

4.

MPLS solution of ECI:

The MPLS over transport solution of ECI meets all the above requirements of designing back-hauls for 3G. To have a brief over-view about the MPLS over transport let us consider its basic aspects. 1. Can be provisioned over the existing SDH infrastructure. 2. Can have efficient BW optimization. 3. Can have TDM like redundancies with very low convergence rates.

4.1. MOT (MPLS over Tranport Port):

The basic unit that one needs to consider after enabling the MPLS license in the card (MCS) of ECI ems is the creation of the MOT port. MOT stands for MPLS over transport port. MOT port is just like the EOS ports that were created before. The MOT port also has the following sub-objects. 1. VCG (Virtual Concatenated Group). 2. GFP. (Generic Framing Procedure, this is the encapsulation technology for passing L2 frames over SDH). 3. EOS (Ethernet over SDH object). The purpose of MOT and its functions are described in the PowerPoint presentation attached below.

MOT (MPLS over Transport).ppsx

Presentation 2: Presentation on MOT concept

4.2. Tunnels and class of service:

Tunnels are the logical paths that are created on the particular MOT port. The MOT port essentially will create a pipe of bulk Bandwidth, which as mentioned in the presentation above could be of NXVC4/NXVC3 or NXVC-12. On these MOT trails, which are already consisting of the total pipe BWs from the trail we create logical BW of a particular Cos. The concept of creating tunnels is explained in the presentation below.

Tunnels.ppsx

Presentation 3: Presentation on concept of tunnels.

ECI Telecom Ltd. Proprietary

Page 11 of 22

Document Edition:

Design Document

Solution Design (India)

4.3. Default table of class of service for tunnels:

The table below shows the default distribution of Class of services and its behavior in the Day-1 scenario. COS CIR Tunnel BW Tunnel BW Tunnel BW Tunnel BW Tunnel BW Tunnel BW Tunnel BW Tunnel BW PIR Comments

7 6

0 0 Port BW Shared Port BW Shared Port BW Shared Port BW Shared Port BW Shared Port BW Shared

High Class High Class

Low Class

Low Class

Low Class

Low Class

Low Class

Low Class

For the high class tunnels the CIR = the tunnel BW. This however is a guaranteed BW on a high priority. For the low class tunnels they also have a PIR = PORT BW which is shareable on the condition that other tunnels are not sending their guaranteed BW or some port BW is free. The PIR is relinquished as and when the other tunnels are sending their guaranteed BWs. Also in an event of acute congestion first the guaranteed CIR of high class is given precedence then the precedence is given to the guaranteed BW of the low class.

ECI Telecom Ltd. Proprietary

Page 12 of 22

Document Edition:

Design Document

Solution Design (India)

5.

Physical topology of the network (NCR):

This section displays the network topology

Figure 4: Physical design of the network for NCR Core The above figure is showing the design of the NCR Core for the 3G deployment of Bharti. The figure represents how the city is divided into 3 RNC locations as on today. The first approach is to divide the MPLS domain networks and PB networks for different MPLS interconnections. To do this demarcations following thumbrules are to be taken into the consideration.

ECI Telecom Ltd. Proprietary

Page 13 of 22

Document Edition:

Design Document

Solution Design (India)

5.1. Thumbrules for creating MPLS domain:

Each MPLS network domain can have 255 PEs maximum. Therefore care has to be taken that the total domain size of a particular MPLS domain doesnt increase 255 PEs in any case. Proper demarcation should be made between two MPLS networks. In order to stitch two MPLS networks there is a necessity of a PB coming in between. This will come into play when we are remote homing the MPLS locations to a particular RNC. Each AGG will be a part of a separate MPLS network and this will include the access parenting in the same network. Each core will have a core XDM-2k box that will house a protected MCS-10 which will be a PB element. Each PB element of MCS-10 would be of a different PB network ID and would solve the sole purpose of homing.

ECI Telecom Ltd. Proprietary

Page 14 of 22

Document Edition:

Design Document

Solution Design (India)

6. Creation of MPLS network domains and Ethernet PB network IDs Tunneling and Services:
In the sections below we will show how the demarcation is done on the basis of creation of MPLS network IDs and PB ID creations. We will take a case by case configurations of all the present scenarios to ensure that we dont exceed the capacity of 255 PEs in a PE network. Then there will be slides on how to create tunnels and bypasses. After this there will be slides on Service creation. a) For Local RNC homing. b) Fore remote RNC homing.

6.1. GUV network aggregation:

This section would show the approach towards the aggregation of the GUV aggregation point in the network. This will be divided into three parts. Creation of MPLS domains and the Core box. Creation of tunnels. Creation of service.

6.1.1. MPLS domain and PB creation in GUV.

The GUV network aggregation is presented with the Core boxes in the following file.

GUV aggregation.vsd

Figure 5: MPLS domain creation in the GUV core. The drawing contains the following sheet. MCS at the GUV Core box which acts as a PB for the sake of remote homing. The Aggregation sheets which are divided into two parts GUV AGG-1 and GUV-AGG-2. Each in different MPLS network IDs. Within the aggregation then there are further collector rings which are actually aggregating to the different sub-aggregations on MCS-30-X.

ECI Telecom Ltd. Proprietary

Page 15 of 22

Document Edition:

Design Document

Solution Design (India)

The MPLS Nw ID is different for different Main aggregators. (in this case GUV AGG-1 and GUV AGG-2 will have different MPLS network IDs). The sub aggregators extend the collector MOT rings which will have unique PE IDs. At any point of time the PE IDs have to be unique for every card in a single MPLS NW ID domain.

6.1.2. Example of how the tunnelling will work in GUV:

To understand how we will achieve the tunneling scheme we take the approach of taking one collector ring with one aggregator terminating on the core.

Creation of tunnels in GUV (Example).ppsx

Figure 6: Example of creation of tunnels. In the presentation there will be example of how tunnels are created. Please go through the animations and this will be the singular approach for all links and all MPLS instance.

6.1.3. Services:
In case of services there are two options Some of the node-bs would be homed to the Gurgaon RNC itself. Some of the Node Bs would be homed to an RNC that would be remote. For the local homing there is no challenge and we have to create a P2MP hub and spoke. For the remote homing the following approach is used. Consider a site in GUV that has to be homed to a remote RNC of VKP. In this case we will first create a EOS trail from the PE gateway of the GUV AGG to the PB element of the VKP core. First the P2MP h/s will terminate at the EOS endpoint of the GUV AGG. Then the traffic is carried by the EOS trail to the VKP core PB. There we make a VSI that will take out the traffic from an ETY port and give to the Core.

ECI Telecom Ltd. Proprietary

Page 16 of 22

Document Edition:

Design Document

Solution Design (India)

6.2. MAL network aggregation:

The figure below will show the aggregation of MOT rings in the MAL aggregation location. The attachment will show how to demarcate the MPLS cards in the MAL aggregation in terms of MPLS NW ID and in the terms of PE ID. The following care has been taken. Ample scope of scalability. Ample scope of service demarcation.

MAL aggregation.vsd

Figure 7: MAL network aggregation The creation of tunnels and services will be as per the design above.

6.2.1. Homing of RNC:

As shown in the figure MAL doesnt have an RNC. So the homing would be to nearest remote RNC. The MPLS P2MP services will be terminated in the MCS-10 boxes of MAL AGG-1 and MAL-AGG-2. From the MAL-AGG MCS cards the traffic is taken via a EOS trail to the remote RNC. The EOS trails are from the MPLS PE MCS of MAL to the MCS-10 PB at the RNC core location. The example is shown in the presentation below.

Remote homing example at MAL.ppsx

Figure 8: MAL network remote homing

ECI Telecom Ltd. Proprietary

Page 17 of 22

Document Edition:

Design Document

Solution Design (India)

6.3. APH Network Aggregation:

As per the information the MOT demarcation design for the APH cluster is shown. Remote homing may be done for SCC RNC by means of EOS trails.

APH aggregation.vsd

Figure 9: APH design of MOT. AI from ALU on this: There is an aggregation mentioned in the core diagram called BCL-18. However in the excel there is only BCS-45 and BCL 998. Which one is to be considered?

6.4. OIE Network Aggregation:

As per the information given in the Core drawing and the Excell sheet the MOT demarcation is made as follows for the Okhla Industrial estate design.

OIE aggregation.vsd

Figure 10: OIE design of MOT. AI on ALU on this In the figure of the Core there are two rings that are shown which are duplicated with APH. This discrepancy to be solved.

ECI Telecom Ltd. Proprietary

Page 18 of 22

Document Edition:

Design Document

Solution Design (India)

6.5. D-184 Network Aggregation:

As per the information given in the Core drawing and the Excell sheet demarcation is made as follows for the D-184 aggregator section in NCR region.

D-184 Aggregation and Collector.vsd

Figure 11: D-184 design of MOT.

6.6. FMS Network Aggregation:

As per the information given in the Core drawing and the Excell sheet demarcation the following will be the Plan for the FMS sector.

FMS aggregation.vsd

Figure 12: FMS design of MOT.

6.7. NP2 Network Aggregation:

As per the information in the Core drawing and the Excell sheet demarcation the following is the propsed plan for NP2 section.

NP2 Aggregation.vsd

Figure 13: NP2 design of MOT.

ECI Telecom Ltd. Proprietary

Page 19 of 22

Document Edition:

Design Document

Solution Design (India)

7.

IOP at the RNC location and at the aggregator locations:

The MCS-10 cards in the RNC location and the MCS-30-X card at the aggregator locations are protected by IOP. Following things are to be taken into consideration when we are doing the IOP. The main and SB cards should be in adjacent slots starting from the ODD numbers. If main is in i1 then SB should be in i2. The adjacent pairs should be i1&i2, i3&i4 and so on At any point to time it should not be i2&i3.

IOP will give card redundancy to the card. In an event there is a main card failure the traffic is all mirrored to the SB. At physical locations the physical ports will be connected by means of Y type cable with the access.

ECI Telecom Ltd. Proprietary

Page 20 of 22

Document Edition:

Design Document

Solution Design (India)

8.

Port Redundancy:

In addition to the card redundancy with IOP the port redundancy is achieved by the RF vendor. The RF vendor runs VRRP and gives input to both ports. VRRP PDUs are passed ok between our two switch ports. It is made sure that the MCS is a passive part in the VRRP.

8.1. VRRP with IOP design:

MCS SB MCS-MAIN L3 Switch (ERR)

VRRP Domain

Port-1

Port-1

Port-2

Port-2

L3 Switch (ERR)

Figure 14: VRRP with IOP As seen in the figure this will be the typical configuration at any point where traffic is being handed over to the erricson L3 switches. The IOP takes care or any card failure from ECI side. The VRRP takes care of any kind of port or media failure from the erricson side. This leads to greater redundancy.

ECI Telecom Ltd. Proprietary

Page 21 of 22

Document Edition:

Design Document

Solution Design (India)

8.2. Creation of the P2MP service:

The P2MP service domain is hub and spoke like but now in this case we will have to take two ETY ports in the PE towards the RNC and define them as hubs.

ECI Telecom Ltd. Proprietary

Page 22 of 22

Document Edition: