No: 66-07/CNP / MNGT / 09 /51 Dt: 21/12/2009

Transcription

1 Core Network Planning Cell, 614, Bharat Sanchar Bhavan, Janpath New Delhi: No: 66-07/CNP / MNGT / 09 /51 Dt: 21/12/2009 Sub: Presentation by CNP Cell to Management Committee of BSNL board on Analysis of NIB-II MPLS network along with Recommendation for MNGT 1. A presentation was given by Core Network Planning (CNP) cell indicating the broad points observed while carrying out the analysis of the NIB-II MPLS with respect to traffic generating trends of different access networks such as broadband, IP TAX, Wi- Max, GSM, Enterprise etc which are riding on NIB-II MPLS network. 2. The analysis has provided critical insight into the traffic generating capacity of these access networks. The presentation also included the connectivity requirement of different access networks for the next three years along with broad recommendation related to planning of the different access network. 3. The analysis also indicated about the multiplicity of IP / MPLS network being deployed with project planned by each business vertical. To optimize CAPEX and OPEX, Optimization and sharing have to be an integral part of planning. 4. All the recommendations, as spelt out in the presentation, were approved by the Management Committee of BSNL Board in its 34 th Meeting held on 9 th December The copy of the presentation is enclosed herewith for information of all field units. Encl: As above (71 slides) (SANJEEV VERMA) Dy, General Manager (Core Network Planning IV) Copy To: [1] All CGM (Telecom Circles / Metro Districs / Projects / Regions / BBNW / QA / Inspection Circle / Training Centres) for information please (Through Intranet) [2] PGMs /GMs of BSNL Corporate Office (Through Intranet) Page 1 of 37

2 Annexure I Analysis of NIB II MPLS Network 24 November 2009 Core Network Planning 1 Approach Followed Bottom Up Approach Target Users One-to-One Discussion Optimize CAPEX and OPEX Identify who are the users? What are their Requirements? Internal: Different Access Networks such as broadband, GSM, Wi-Max, IP TAX, Class V NGN, FTTX (GPON / GEPON),SSTP External: Enterprise users: For provisioning of VPN circuits, Internet Leased Line For Internal user: Discussion done with respective GM Network planning. For External user: Discussion done with GM (Business Strategy) E at Corporate Office / Field. The current expansion is not a green field deployment A realistic picture on traffic as on day is available for different type of traffic A balanced approach (mix of realistic and visionary) is followed. 24 November 2009 Core Network Planning 2 Core Network Planning Page 2 of 37

3 !!! BSNL has multiple Data Networks Need for Centralized approach!!! Project No of Routers Remarks NIB -II GSM Phase V GSM Phase VI CDR Project Tx NMS (Planned) 150 Around 300 Around 300 (Exp) Around 500 Around 500 MPLS enabled MPLS enabled MPLS Enabled IP Enabled IP Enabled 1. NIB-II The smallest in number is catering to maximum load. 2. There is a need for having a centralized approach to optimize CAPEX and OPEX. 3. Every project tends to plan its own IP network Not a judicious approach 4. GSM Phase VI deployment can leverage on GSM Phase V and NIB-II MPLS network 5. Huge network deployed as part of CDR. 24 November 2009 Core Network Planning 3 Important facts about NIB II MPLS Unified Transport Review of integration philosophy Hierarchical connectivity Actual traffic far less than that anticipated MPLS acting as an unified IP transport layer for voice, video and data. Predominantly for facilitating inter-city flow of traffic The general philosophy followed for Connectivity of different access network has been dictated purely from the interface requirement in the absence of any relevant traffic details. It should, henceforth be, dictated purely from traffic. MPLS network complements the metro area aggregation network Very important. Different access network shall aggregate the traffic using aggregation network and only aggregated interface shall connect with the MPLS. The interface utilization of existing edge connectivity is only 15-20% Realistic assessment of traffic for expansion of existing and deployment of future access networks 24 November 2009 Core Network Planning 4 Core Network Planning Page 3 of 37

4 Agenda Review of Integration Philosophy Hierarchical Connectivity Internal Users: Analysis of Traffic from Different Access Network Broadband (DSL) + Class V NGN + FTTx IP TAX Wi-MAX GSM Other Access Networks External Users: Enterprise User Summary of Expansion Future Line of Action (Through MNGT) 24 November 2009 Core Network Planning 5 Review of Integration Philosophy of MPLS Network 24 November 2009 Core Network Planning 6 Core Network Planning Page 4 of 37

5 Broad Components of MPLS Network PE Router P Router Akin to Local Exchange Subscriber termination point Different Access network such as broadband, GSM, wi-max etc gets terminated here. Connectivity on Gigabit Ethernet (GE) interface based on the traffic generating capacity of different network Akin to Level 1 TAX Carries out transit function. High Speed transfer of packet from one city to Other City National Highway 24 November 2009 Core Network Planning 7 Let s re-fresh L2 TAX Connectivity If Small X-ges are connected directly to TAX, the TAX Capacity requirement increases Along with dramatic fall in X-A X-B X-C Its utilization X-D Tandem X-E X-F X-G RLU This is an aggregated interface E-10 B OCB Level II TAX RLU RLU RSU RSU RSU Why the Small X-ges are first aggregated at Tandem and not connected directly to Level II TAX? This ensures optimal utilization of aggregated interface. Individual X-ge are not capable of generating traffic equivalent to one E1 (minimum connectivity) Tandem acts as an aggregation Layer. Tandem Complements TAX in ensuring optimal connectivity 24 November 2009 Core Network Planning 8 Core Network Planning Page 5 of 37

6 MPLS Edge Connectivity is Similar to L2 TAX Connectivity GPON / GEPON Project X-A X-B X-C MGW IP TAX FTTX This is an aggregated interface X-D Tandem Level II TAX Metro Aggregation Network MPLS PE This is an aggregated interface X-E X-F X-G DSLAM LMG BTS -WiMAX RLU E-10 B OCB RLU RLU RSU RSU RSU Multiplay Project Class V NGN Wi-MAX (Rural and Urban) RPR / Ethernet based aggregation Network deployed in Multiplay 24 November 2009 Core Network Planning 9 MPLS Edge Connectivity is Similar to L2 TAX Connectivity What done for Level 2 TAX? Minimum Connectivity is E1. Small X-ges, which are not capable of generating traffic equivalent to one E1 are aggregated using Tandem. This ensures optimal utilization of E1 interface Tandem Complements TAX in ensuring optimal connectivity What shall be done for Edge Connectivity? Minimum Connectivity is Gigabit Ethernet (GE) Small access network, which are not capable of generating traffic equivalent to one GE are aggregated using Metro Area Aggregation Network. This ensures optimal utilization of GE interface it is costly Metro Area aggregation network complements MPLS network in ensuring optimal connectivity 24 November 2009 Core Network Planning 10 Core Network Planning Page 6 of 37

7 Hierarchical Connectivity 24 November 2009 Core Network Planning 11 Hierarchical Connectivity NOC AAA LDAP Billing Provisioning MPLS PE Router Core IP/MPLS Network MPLS PE Router City A IP Network Gateway Metro Area Aggregation Network Edge Connectivity: This interface to be dimensioned purely from Traffic anticipated from Set of customers IP Network Gateway Metro Area Aggregation Network City B GPON / GEPON DSLAM LMG MGW BSC / RNC Examples of IP Network Gateway: BNG Set of Customers ASN SGSN, GGSN 24 November 2009 Core Network Planning 12 Core Network Planning Page 7 of 37

8 Analysis of Traffic From Different Access Networks 24 November 2009 Core Network Planning 13 Broadband 24 November 2009 Core Network Planning 14 Core Network Planning Page 8 of 37

9 Current Status (as on 31/10/2009) DSL Capacity = 8.5 Mn Broadband Connections =4.52 Mn Disabled Customers = 1 Mn Active Customers = 3.52 Mn Loading w.r.t Active customers = 41% Concurrent connections = 0.61Mn No of BNGs = 175 (128*) Utilization of BNGs : Session handling capacity 8926/48000 = 18.6 % Link Utilization = 12% International bandwidth (utilization 70%) = 45 Gbps Average BW per prov customer = 7 kbps Average BW per concurrent customer = 60 kbps *: Commissioned 24 November 2009 Core Network Planning 15 Broadband Customer Funnel 22% are disabled 78% 12% 60 Kbps Per concurrent customer Provisioned Customers (100) Active Customers (78) Concurrent (12) BW = 0.72 Mbps 24 November 2009 Core Network Planning 16 Core Network Planning Page 9 of 37

10 Parameter Targetted Customer Growth (11 th Five Year Plan) Status as on 31/03/09 MOU for Target for Target for Cumulative Total Wireline WLL Mobile NGN 0 Total Broadband (Fixed) Broadband (Wireless) TAX Circuits (Kc) OF Cable (Rkm) * 13,528 5,95,392 28,500 30,000 30,000 6,83,892 All figures in Lakhs unless specified 14 Mn broadband customers by November 2009 Core Network Planning 17 Major Drivers for Increased Traffic Increase in Concurrency Bandwidth intensive Service Required for leveraging FTTX Pre-Paid broadband Service: Class V NGN IP TAX Traffic Focus on Content which has higher simultaneous usage during peak hour Focus on On-demand content Broadcast content (Multicast) doesn t generate much traffic With GPON / GEPON + VDSL2+, other than HSI, VoIP and VPN we don t have any other service Will increase volumes and hence total traffic What about average customer traffic? Will leverage on the DSL infrastructure But focus has to beyond VoIP Multi-media applications Incremental TAX traffic will expected to flow through this. However the same will not be significant as current average loading of TAX is around 67%. 24 November 2009 Core Network Planning 18 Core Network Planning Page 10 of 37

11 BB Cust (Today) Scenario Analysis BB Cust (Planned) Increase in fold Avg usage (Today) AvgUsage (Planned) Increase in usage Gross Increase in Traffic 4.5 Mn 14 Mn kbps 7 kbps Mn 14 Mn kbps 14 Kbps Mn 14 Mn kbps 21 Kbps Mn 14 Mn kbps 28 Kbps Mn 14 Mn kbps 35 kbps Mn 14 Mn kbps 50 kbps The average usage of around 21 kbps per customer is taken for planning purpose 2. This will require 9 times increase in trafficwith 3 times increase in customer base in the next three years A challenging proposition? 24 November 2009 Core Network Planning 19 Parameters for dimensioning BNG : Concurrency rate (Present 13.5%) = 40 % Average BW per customer Calculation: = 21 kbps Customers 1 BNG can handle = 1.25 L Maxm traffic in 1 BNG = 2.62 Gbps 14 Mn customers require = 112 BNGs 25% over provision = 140 BNGs BNGs already planned upto Ph II = 175 Further Expansion of BNG not required in Phase - III 24 November 2009 Core Network Planning 20 Core Network Planning Page 11 of 37

12 Broad Dimensioning Criteria Parameter Current Planned Customer base Concurrency AvgBW per cust Edge Connectivity No of BNGs Link Utilization (2GE) 4.5 Mn 13.5% 7 kbps 2 GE %** 14 Mn(Mar 12) 40% 21 kbps 3 GE* 175??? Note: *: Planned initially in A type cities. Progressively for B type cities **: This will fall further to 6-8% with the commissioning of balance 47 BNGs (as part of Phase II) 24 November 2009 Core Network Planning 21 Executive Summary - I Current Loading is Low Existing Edge Connectivity sufficient for the next 2-3 yrs Focussed Strategy on IP TV Service: The DSL port loading is around 41%. With current rate of growth (1.5 lakhspm), the network will be loaded 90% in another 27 months (more than 2 years) The current BNG is sufficient to handle more than 14 Mn broadband customers Each BNG is presently connected on 2 GE interface to MPLS PE The average Traffic loading of this link is around 12% No new connectivity of BNG is required with MPLS PE Router for the next three four yrs. Provision is made for additional 1 GE connectivity in top 20 cities for further increase in traffic. The low traffic in broadband is predominantly due to slow off take of IP TV service. Focussed Strategy on IP TV including On demand content. The services to be strengthened inthe existing 98 cities before venturing into new cities. Optimizing Broadcast content to ensure seamless experience to user. 24 November 2009 Core Network Planning 22 Core Network Planning Page 12 of 37

13 Executive Summary - II RPR Aggregation Network in top 98 cities: Enterprise segment can leverage on that for Ethernet connectivity to customer. Phase III Expansion Around 3 Mnports planned. The planned expansion to take care of above points. Alignment of the expansion as per the NGN framework approved by the Management Committee. International Bandwidth Expansion has to be done in the IGW locations. Core connectivity to be augmented to nx10gbps in the top cities. Other Points Project 3 LDAP Capacity: To be in sync with the access capacity available as part of DSL, FTTX and Wi-MAX. (Project 3 CDR Project) issue to be sorted out. 24 November 2009 Core Network Planning 23 IP TAX 24 November 2009 Core Network Planning 24 Core Network Planning Page 13 of 37

14 Current Status Total TAX Circuits = 8.5 Mn Average Loading = 67% Loading of Level I TAX = 90% Existing (As on 31/10/2009): TDM PSTN = Mn GSM = Mn CDMA = 5.4 Mn IP NGN = 0 Total telephone customers as on 31/10/2009 = Mn 24 November 2009 Core Network Planning 25 Macro Level Dimensioning of IP TAX Total Connections (expected)* Contention ratio (1:10) No of active circuits Local Calls around 25% So no of active circuits in TAX Existing Capacity =150 Mn (131 Mn) = 15 Mn (13 Mn) = Mn (9.75 Mn) = 8.5 Mn Additional Capacity required = 2.75 Mn (1.25 Mn) Note: *: By March The above calculation assumes that all the connections are on TDM infrastructure & thus banks on TAX circuits. 2. The scenario has changed with the introduction of IP in GSM Ph V. 3. Thus the requirement of IP TAX will come down further considering GSM GSM calls are 70% of the total GSM calls. 24 November 2009 Core Network Planning 26 Core Network Planning Page 14 of 37

15 IP TAX Deployment Plan Phase I Total Cities = 265 Cities with 4 KC (0.5 Gbps) = 79 Cities with 8 KC (1 Gbps) = 67 Remaining Cities =119 Note: A Total of 3 Mncircuits planned to be deployed in the first phase. 2.2 Mnto M/s ZTE and 0.9 Mnto M/s ITI M/s Huawei The above loading is at the maximum utilization with no compression. However, as the compression is implemented the bandwidth requirement is expected to be reduced by 40%. 24 November 2009 Core Network Planning 27 Traffic Flow and Trends The intra-circle traffic shall be catered by the existing TAX capacity we are not replacing but augmenting TAX network?? Also this traffic will come down as TDM PSTN is migrated to NGN. Because of GSM expansion and Landline surrender / migration to NGN, the traffic will further come down. In the current scenario, the utilization of IP TAX will be significant only in top 20 cities 24 November 2009 Core Network Planning 28 Core Network Planning Page 15 of 37

16 IP TAX Traffic Flow Scenario Other TDM networks GSM (UptoPhase IV) CDMA Phase V GSM and onwards TDM TAX (L1 + LII)/ Tandem Pure TDM to TDM traffic Can be carried Through existing TAX network except L1, where Loading Is 90%. LE LE LE LE Existing TDM Local Switch IP TAX This link will carry incremental inter Circle traffic and traffic where One end is TDM PSTN and other End is IP NGN, GSM (Phase V onwards) NGN (DSL, FTTX, LMG etc) 24 November 2009 Core Network Planning 29 IP TAX Connectivity in A Cities (L1 TAX) L1 TAX / Tandem L1 TAX / Tandem E1s MGW MGW Soft Switch GE Ethernet Switch GE Soft Switch MGW Core IP/MPLS Network MGW MGW MGW MGW 24 November 2009 Core Network Planning 30 Core Network Planning Page 16 of 37

17 IP TAX Connectivity in B Cities MPLS Nation wide Core GE MPLS Layer E1s GE GE L2 TAX MGW 10 G RPR RPR Aggregation Layer GE PE Router BNG RPR Tier 1 Switch RPR Tier 2 Switch DSLAM 24 November 2009 Core Network Planning 31 IP TAX Connectivity in OC Cities Core router BNG To nearest A/B cities where RPR Tier 1 Switch is there BB Tier 1 LAN Switch GigE FE SDH RING OC city OC city RPR OC Switch MGW L2 TAX E1s MGW GE X-ge A GE X-ge C X-ge B GE X-ge D ADSL terminals ADSL terminals 24 November 2009 Core Network Planning 32 Core Network Planning Page 17 of 37

18 Executive Summary of IP TAX Utilization in the Current Scenario will be low IP TAX planning was done more than three years back (Aug 06). During this period, lot of changes have happened particularly in the landline + GSM In the current scenario, loading of 3 Mnis not expected on immediate basis except may be in top cities. So, Connectivity will be on shared basis Loading will further come down How to increase loading of IP TAX? The direct connectivity will be done only in top cities. In other cities, it will leverage on the existing broadband connectivity. As we migrate towards Class V NGN, loading of IP TAX will also come down. This will also come down as landline gets surrendered in favour of GSM. Can we explore the alternate usage of IP TAX infrastructure Maintenance issues can be solved through replacement of TDM TAX Circuits What is the Policy on that? The Media Gateway used for GSM Phase VI expansion??? Whole sale service to other TDM operators The order of Phase II may have to be re-looked Phase II into from the actual loading of 3 MnCircuits planned in Phase I 24 November 2009 Core Network Planning 33 Wi-MAX 24 November 2009 Core Network Planning 34 Core Network Planning Page 18 of 37

19 Wi-Max Project Roll Out Plan Wi-MAX Urban Rural (Procurement) Procurement Franchisee Phase I (1000 BTSs) Phase II (6863 BTSs) Kerala IComm Punjab Huawei Soma (Guj, MH AP) EOI other Circles HCL Info (592 BTS) N + E Gemini (408) S+W L1: -Gemini (Juniper) L2: ZTE L3: ICOMM L4: Vipula- Alvarion A type (1000 BTS): 6 Circles B Type (700 BTS): 6 Circles C Type (500 BTS): 4 Circles 24 November 2009 Core Network Planning 35 Key Concern Areas in the Wi-Max deployment Predominantly Rural deployment Majority of the procurement based deployment is happening in Rural areas. Infrastructure will be established but what about Rural specific contents. Urban Roll out is slow Franchisee based except in Kerala and Punjab Only 2500 customers in three states (GUJ, MH and AP) Three cities: Ahemdabad, Panjim and Vizag Status of Pilot deployment A 10 city pilot deployment on 802.1d technology was done What is the status of the pilot? How many customers? All this demand a progressive way of establishing Core connectivity Mn Wi-Max user Is taken from the Core side 24 November 2009 Core Network Planning 36 Core Network Planning Page 19 of 37

20 Initial Macro Level Planning of Wi-Max Network 1 ASN = 100 BTS. 1 BTS (Capacity in No of customers) = 100 No of ASNs across the Network = 100 BW between ASN and MPLS = 1 Gbps Total Pipe = 100 Gbps Current Avg utilization = 7 kbps No of Users it can take = 14 Mn Current Status: User Base = 2500 BW = 10 Mbps The MPLS connectivity is significantly high 24 November 2009 Core Network Planning 37 Executive Summary of Wi-Max Current connectivity is not in sync with the traffic. The current plan of 100 ASNs provides 100 Gbps pipe towards MPLS. This will be a huge pipe with severe under loading. So, we need to follow a progressive approach Why you require more ASNs? Progressive Approach Either from the traffic perspective or from interoperability The current 18 ASNs can caterfrom the traffic perspective for around 2 Mn Wi-Max user Thus the current plan of 100 ASNs has to be re-looked into. In case, few more ASNs are required from inter-op perspective (for new OEMs not part of initial 18), the number to be worked out purely from the traffic. These ASNs be deployed near the international Gateway Location (Mumbai, Chennai, Bangalore, Noida or Kolkatta) and aggregated with the existing ASNs Instead of deploying back-end infrastructure (ASN: 100 Nos) at one go, deploy as you grow. The current 18 ASNs can take care of 2 Mnusers. 24 November 2009 Core Network Planning 38 Core Network Planning Page 20 of 37

21 GSM Network Traffic 24 November 2009 Core Network Planning 39 Salient Points of GSM Network UptoPhase IV, infrastructure is TDM based IP Connectivity introduced at the Core Equipment Level in Ph V TDM / EoSused at the Access Network Level UptoPhase IV, a total of 36 Mncapacity deployed, TDM based The connectivity is extended using TDM TAX circuits In Phase VI, under Service equivalency, migration to IP based network is planned progressively. In Phase V, the IP connectivity was introduced at the level of Core equipments such as Media Gateway (MGW) A separate MPLS infrastructure deployed / planned in each Zone This will carry intra-circle voice and intra-circle signalling traffic BTS / Node B BSC / RNC is on E1s. BSC / RNC Media Gateway is on E1s BSC / RNC SGSN is on Ethernet over SDH (Point to Point) Inter-Circle Call riding on NIB-II MPLS Data is handed at One per Zone The inter-circle voice traffic will ride on NIB-II MPLS along with inter-circle signaling traffic for connectivity to SSTP. The connectivity between NIB-II and GSM MPLS network is done at Gateway location per Circle. 8 in NZ, 5 in EZ, 9 in SZ and 8 in WZ. The Data connectivity at GGSN One per Zone Kolkatta, Chandigarh, Pune and Chennai 24 November 2009 Core Network Planning 40 Core Network Planning Page 21 of 37

22 Circle Wise GSM Connections (As on 31/10/09) Circle* GSM Conn Circle GSM Conn A& N 0.09Mn MP 1.86 Mn AP 3.86 Mn Maharashtra 3.87 Mn Assam 0.96 Mn NE-I + II Mn Bihar 2.07 Mn Orissa Mn Chattisgarh 0.83 Mn Punjab Mn Gujarat 2.64 Mn Rajasthan Mn Haryana 2.17 Mn TN Mn HP 1.07 Mn Uttaranchal Mn J&K 0.89 Mn UP - East Mn Jharkhand Mn UP-West Mn Karnataka Mn West Bengal Mn Kerala 3.11 Mn Kolkatta Mn Chennai Total Connections: Capacity planned / deployed upto Ph V Capacity Planned in Phase VI 1.15 Mn IP Capacity: 9 Mn for South Zone 9 Mn for West Zone 13.5 Mn for N + E Zone Note: *: Source: CP&M Monthly DEL report = Mn = Mn (36 Mn TDM based) = 93 Mn 24 November 2009 Core Network Planning 41 GSM Traffic Distribution MSC (100) GSM MPLS N/w Intra-MSC GMGW of Other Circle MSC in Same Circle Inter-MSC LI TAX of PSTN (10+20) GMGW of the Circle To Other operator This traffic will get Migrated to MPLS N/w as the Legacy MSC is Replaced With (MGW + MSC S) As part of service equivalency Legacy MSC (uptoph IV) NIB -II MPLS N/w TDM 24 November 2009 Core Network Planning 42 Core Network Planning Page 22 of 37

23 Traffic Calculation (Voice) For Ph V and onwards Assumptions: (From Ph VI Tender) Average traffic per customer = 50 merl Incoming = 25 merl Outgoing = 25 merl GSM GSM = 70% GSM PSTN = 10% PSTN GSM = 20% Traffic Calculation: 1. Traffic from 1 Mn customers = 50,000 Erlg 2. Traffic in IP (@ 70% utilization) a) 50000X50/( *.7) = 3.5 Gbps simplex = 1.75 Gbps duplex 3. Traffic distributed among GSM, NIB and TDM 4. Peak expected traffic in NIB Core around = 0.8 Gbps full duplex 24 November 2009 Core Network Planning 43 Avg Throughput(GGSN - SGSN) in Mbps Zone Circle Nov 08 Apr 09 Circle Nov 08 Apr 09 South North East West AP TN Kerala CHTD Karnataka HR UP E PB+HP+JK UPW +UAL Rajasthan AS+NEI+NEII WB+AN BR + JKND CLTD OR MH GJ MP + CHG As can be seen, Data Traffic is hardly anything at this instant. The Loading of existing SGSN is low (Capacity ( = 100 Mbps) 24 November 2009 Core Network Planning 44 Core Network Planning Page 23 of 37

24 Wireless Growth (In 09-10)* April '09 May ' 09 June '09 July '09 Aug '09 Sept '09 Countrywide Addition BSNL Share *: Source: TRAI Report 1. Total of Mn added in the last 6 months. 2. BSNL Share = Mn, As %age = 8.1% 3. Average additions of 1.1 Mn per month in the Last 6 months 4. In 08-09, BSNL share was 7%, 9.1 Mn out of Mn (All lines ) 24 November 2009 Core Network Planning 45 GSM - NIB-II II MPLS Connectivity Project Zone Vendor IP Capacity NIB-II MPLS Remarks Phase V South M/s Huawei 9 Mn Gbps Phase V West M/s Alcatel 9 Mn Gbps Phase V North M/s Ericsson Phase V East M/s Ericsson 8 Mn 8+8 Gbps 1+1 GE at Chandigarh. Other 7 places at 2* STM Mn 6+6 Gbps 2+1GE at Kol. Other 4 places at 2 * STM-1 Note: - A 31 Gbps Pipe built up between GSM Network and NIB-II Network The above connectivity can cater to 35 Mn customers on GSM IP platform under fully loaded condition. Provision is made for additional 35 Mn customers on GSM IP platform. (either expansion or under service equivalency). Further expansion in selected cities depending upon actual traffic. 24 November 2009 Core Network Planning 46 Core Network Planning Page 24 of 37

25 Executive Summary of the Recommendation - I Optimize MPLS Deployment IP Connectivity of Access Network (BTS / Node B BSC / RNC MSC / SGSN) Data Traffic is negligible Leverage on IP TAX infrastructure No need for separate MPLS infrastructure as part of Phase VI. Leverage on MPLS infrastructure as part of Phase V and NIB-II MPLS. Presently the voice is on TDM and Data is on EoS. The current packet connectivity on SDH shall be migrated to Packet based network progressively. The same can be implemented using existing Metro Area Aggregation Network, as and when the same is planned. The current GPRS / EDGE traffic is insignificant. The same is expected to increase with launch of 3G Focussedapproach on 3G Top few cities. For connectivity to PSTN for new network, leverage on IP TAX. Explore Usage of Media Gateway deployed as part of IP TAX. Leverage on Existing Infrastructure (GSM + IP TAX) for future expansion 24 November 2009 Core Network Planning 47 Executive Summary of the Recommendation - II North Zone GSM MPLS Network of M/s Ericsson Connectivity with NIB-II MPLS at Chandigarh, Ambala, Jammu, Lucknow, Noida, Shimla, Jaipurand Jullundhur. East Zone GSM MPLS Network of M/s Ericsson Connectivity with NIB-II MPLS at Kolkatta, Patna, Shillong, Guwahati and Sambalpur West Zone South Zone GSM MPLS Network of M/s Alcatel M/s CISCO Connectivity with NIB-II MPLS at Pune, Nagpur, Ahemdabad, Surat, Bhopal, Indore, Raipur and Durg (Parented to Raipur) GSM MPLS Network of M/s Huawei Connectivity with NIB-II MPLS at Hyderabad, Vijayawada, BGL, Mysore, Chennai, Coimbatore, Ernakulem, Madurai and TVM The initial connectivity will be on 1+1 GE interface to be augmented to 2+1 GE depending on the traffic. 24 November 2009 Core Network Planning 48 Core Network Planning Page 25 of 37

26 Other Networks 24 November 2009 Core Network Planning 49 Connectivity to Other Access Networks CDR Project Around 500 Routers are deployed covering all SSA. Expected Peak loading around 30%. We can spare some Routers through consolidation. These Routers are planned to be connected on STM-1 on dual mode basis Project delayed. Still in PoCStage. Focus on early commissioning of the same. SSTP Ku band VSAT CDMA PDSN Tax NMS SSTP Switches deployed in 24 cities The present connectivity is on Fast Ethernet Interface The same is planned to be connected on Gigabit Ethernet interface the peak traffic presently is only 20 Mbps. Connectivity with Ku-band Router at Bangalore The physical connectivity is through n*64 / E1 / FE One link per VPN customer is used between PE Router and Ku-band Router One per Zone Connectivity on 1+1 GE interface Routers / Switches at SSA connected on E1s Regional NMS connected on STM-1 24 November 2009 Core Network Planning 50 Core Network Planning Page 26 of 37

27 Enterprise Users 24 November 2009 Core Network Planning lakhleased lines and 19,475 VPN Circuits Current Status Distribution of MPLS VPN Circuits 44% are 64 kbps 25% are 128 kbps 10% are 256 kbps 8% are 512 kbps 8.5 % are > 1 Mbps Huge Growth in Leased Line AvgRevenue per Cktis Rs 90,000 pm 40% increase in revenue with 30% decrease in tariif Revenue of Rs 960 Cr in for LL / VPN. The revised fig for is Rs 1650 Cr. Revenue in the first six months is Rs 620 Cr. This indicates majority of the circuit is 64 kbps and 128 kbps VPN Growth in the Last three Years 700 ckts pm 19,255 circuits provisioned from Jan 06 to Dec 08 5,651 circuits provisioned from Jan 09 to Aug 09 Average monthly additions around 700 ckts pm VPN Loading in the top 25 cities are significant 25 Cities are there where Loading is > 35% 58 Cities are there where Loading is < 20% Average Loading is 24%. 24 November 2009 Core Network Planning 52 Core Network Planning Page 27 of 37

28 VPN Site Wise Loading Top 25 Cities Site Name %age Loading Site Name %age Loading Ahemdabad Bhubaneshwar Bangalore Surat Ernakulem Bangalore Hyderabad Hyderabad Mumbai Patna Pune Jabalpur Kolkatta Rajkot Chennai Jaipur Hubli Ambala Chennai Delhi Ahemdabad Gurgaon Dehradun Trichy Mumbai Madurai Ernakulem Mangalore Chennai Noida Coimbatore Indore November 2009 Core Network Planning 53 Site Wise Loading Bottom 26 Cities Site Name %age Loading Site Name %age Loading Gwalior Dhanbad 7.66 Patiala Kharagpur 7.66 Ananthapur Solapur 7.66 Alwar Raichur 6.51 Trichur Sagar 6.51 Nellore Eluru 6.12 Amritsar Sambalpur 5.36 Durgapur Anand 4.6 Shillong 10.2 Mumbai Karvar 9.2 Dhule 3.83 Moradabad 9.2 Nanded 3.83 Jammu 8.98 Bangalore Jhansi 8.43 Ferozepur 3.3 Jamshedpur 8.24 Ahemdabad- 3 - Palghat 8.24 Hyderabad November 2009 Core Network Planning 54 Core Network Planning Page 28 of 37

29 Growth in the data market expected to be driven by MPLS VPN and High Speed Data & Internet (HSDI) Rs. Cr. 12,000 10,000 Enterprise data market break up by product ( ) 8,000 6,807 13% ,422 5,782 Legacy Packet Leased Line CAGR -5% 10% Share of BSNL ~95% ~13% Trends Will continue to be used by select verticals (e.g. BFSI) for running core apps till such time switching costs remain high Preferred for high bandwidth P2P links Mainstay for international data connectivity 6,000 4,000 3,618 2,587 Hi Speed Data and Internet 14% ~44% ISDN & VSAT used for data connectivity backup DSL primary source of internet connectivity for small & SOHO 2, ,373 1,689 CY ,954 CY 2013 MPLS VPN 19% 2% Gaining popularity for transport of distributed data owing to lower TCO Expected to take share from legacy packet as customers upgrade their data networks Source: Frost & Sullivan, IDC, Gartner, Ovum, Analyst Reports, BCG analysis 24 November 2009 Core Network Planning 55 BSNL is currently a strong player in the data market Owing to dominant share in the NPLC and HSDI markets BSNL is the joint #3 player in the enterprise data services market Predominant share in NPLC No presence in IPLC today TCL 22% BSNL Reliance Bharti 36% 24% 24% TCL Reliance 64% 28% Reliance Bharti 19% 17% TCL MTNL Total 100% 12% 5% Bharti Total 100% 8% BSNL 17% Tulip Sify HCL Others 6% 5% 5% 9% Total 100% Share in enterprise data market 1 (%) HSDI dominance due to high fixed line penetration Negligible presence in MPLS VPN BSNL 44% Tulip 28% Sify 22% Bharti 26% Reliance 21% Reliance 14% Bharti 12% HCL 6% TCL 11% TCL 5% Others 6% BSNL 2% Others 4% Total 100% Total 100% This denotes the share in the entire enterprise data services market corporate + SMB Note: Market shares for FY Source: Frost & Sullivan, Analyst Reports, BCG analysis 24 November 2009 Core Network Planning 56 Core Network Planning Page 29 of 37

30 Key points For the Enterprise Segment for VPN Future trend towards Ethernet and VPN Focus more on 2Mbps and above for VPN No MAN in Delhi and Mumbai Leverage on the MAN in Other Cities More and More customers will demand Ethernet as the preferred interface MPLS VPN will be preferred over LL because of lower TCO. Customer need to be educated and convinced on the same. Presently most of the Circuits are 64 kbps and 128 kbps They require lot of intermediate elements such as MUX, MLLN equipment etc Mtce issues Migrating to 2 Mbps will make implementation and maintenance smoother This results in very long last mile This even go upto25-30 Km Multiple POPs in Delhiand Mumbai End-to-End infrastructure: Local lead, Tx back-haul + Router In Other cities, MANhas been built up as part of Multiplay project. Leverage on the same for provisioning of Ethernet connectivity 24 November 2009 Core Network Planning 57 CPE CPE City A MPLS MLLN: Complement Each Other V M U X V M U X D X C V M U X City B D X C V M U X Other Cities V I R T U A L POP CPE CPE V M U X V M U X D X C V M U X V M U X D X C V M U X Other Cities P H Y S I C A L City A City B POP 24 November 2009 Core Network Planning 58 Core Network Planning Page 30 of 37

31 Virtual POP Vs Physical POP Parameter Local Lead MLLN Cost Back-haul Cost Router Cost Link performance Commissioning time OPEX Virtual POP Extended to nearest City (B) -Longer From City A to City B on MLLN - higher Zero Zero Same Similiar Lesser Physical POP Confined to City A itself - Shorter MLLN confined to City A only - Lesser Minimum 2 STM-1s Around 26 lacs Improved due to redundancy Similiar Higher due to deployment of Router Note: 1. In both the models, the issue predominantly comes in the last mile. In case of Virtual POP, every VMUX is already connected with nearest DXC on E1 and practically there is no such maintenance issue once the link is commissioned. 2. The average loading of MLLN Network is 38% spanning 1800 SDCAs 24 November 2009 Core Network Planning 59 Additional POPs where LL is Around 1000 Circuits Circles POP Present Addtl POP Circles POP Present Addtl POP AP 8 1 (Guntur) NE I 1 0 Assam 4 0 NE II 0 0 Bihar 4 0 Orissa 3 0 Jharkhand 3 0 Punjab 7 0 Gujrat 5 0 Rajasthan 5 0 Haryana 3 1 (Karnal) Tamilnadu 7 - HP 1 0 UP-East 6 0 J&K 2 0 Up-West 6 0 Karnataka 7 0 Uttaranchal 2 0 Kerala 5 0 West Bengal 3 0 MP 5 0 Chennai TD 4 0 Chattisgarh 2 0 Kolkatta TD 4 0 Maharashtra 9 0 Only two Cities are there where Additional POP may be required. Further - Delhi And Mumbai will require multiple POPs (4 each) for geographical diversity 24 November 2009 Core Network Planning 60 Core Network Planning Page 31 of 37

32 Additional POPs where LL is Around Circuits Circles POP Present Addtl POP Circles POP Present Addtl POP AP 8 2 (Kurnool, NL) NE I 1 0 Assam 4 0 NE II 0 0 Bihar 4 0 Orissa 3 0 Jharkhand 3 0 Punjab 7 2 (Bathinda, Pathankot) Gujrat 5 0 Rajasthan 5 2 (Bikaner, Srigangangr) Haryana 3 2 (Hissar, Rohtak) Tamilnadu 7 - HP 1 0 UP-East 6 0 J&K 2 0 Up-West 6 1 (Bareilly 713) Karnataka 7 2 (Shimoga, Tumkur) Uttaranchal 2 1 (Nainital) Kerala 5 5 West Bengal 3 1 (Asansol) MP 5 0 Chennai TD 4 0 Chattisgarh 2 0 Kolkatta TD 4 0 Maharashtra 9 0 Around 20 POPs additionally.. This makes the total no of Routers to November 2009 Core Network Planning 61 Executive Recommendation for Enterprise User Expansion in Top Cities New POPs Leverage on MLLN infrastructure Expansion may have to be done in the existing cities only. This can be done through re-arrangement of cards from smaller cities. 10 POPs will be required predominantly at Mumbai and Delhi 20 addtlpops for Cities where LL is > 500 circuits for offering improved SLA to customer. MLLN spans 1800 SDCAs with plan to cover remaining 800. All MLLN Nodes are Virtual Nodes. Deploy MAN in Delhi and Mumbai Leverage on existing MAN in Other 98 Cities DSL for Lower bandwidth MAN has to be built up in Delhi and Mumbai Technologies such as RPR / FTTX / Carrier Ethernet can be explored. In top 98 cities, leverage on the MAN deployed as part of Multiplay. Phase III expansion to provision for Ethernet interface for enterprise user DSL also can be positioned for providing VPN service in smaller cities and also for providing lower bandwidth. Each DSLAM acts as MPLS POP, more than 2000 cities 24 November 2009 Core Network Planning 62 Core Network Planning Page 32 of 37

33 Summary of Expansion 24 November 2009 Core Network Planning 63 Details of Interface Requirement A type Cities Project POI Existing Interface per POI Broadband 166 at 106 locations GSM 29 locations IP TAX 20 locations* Wi-Max 22 locations SSTP 24 locations A1 DLI, MUM A1-3 A2-3 A3-6 A *1 6*1 4*1 2* PN -4, Other-2 2GE at CHN and DLI 2 RP, NGP, CBT, VYD, MYS, CHD,GWH, 2, Other , IND=0 RP,NGP,GW H,CBT = RNC, GWH, CHD = 2, Other = 0 2*FE 2 2 2, PN=0 2, IND= 0 NGP,GWH, CBT = 2 CDR 104 loc 0 8*STM-1 8*STM-1 8*STM-1 8*STM-1 All interfaces in GE unless specified 24 November 2009 Core Network Planning 64 Core Network Planning Page 33 of 37

34 Details of Interface Requirement B type Cities Project POI Existing Interface per POI B1 B2 Broadband 166 at 106 locations GSM 29 locations 0 SU,TVM,MYS, MD,BP,JAM, NDA,= 2, Other 0 AMB, SMB,SML, IP TAX 19 locations* 0 BP,Agra,Rajkot=2 Ambala, Cuttack = 2 Wi-Max 0 NDA, BP, TVM, LDH, AMR= 2, Other =0 SSTP 24 locations 2* FE BP,Agra,Rajkot, JAM,Shillong =2 Calicut,Trichur= 2, Other = 0 AMB, SHM, CUT, Dimapur= 2 CDR 104 locations 0 4*STM-1 4*STM-1 All interface in GE unless specified 24 November 2009 Core Network Planning 65 Summary of Other Requirements For Enterprise User International Gateway router Expansion in Top cities through rearrangement of cards new POPs Deployment of Metro Area Aggregation Network in Mumbai and Delhi to reduce last mile. Leveraging on existing RPR Metro Area Aggregation Network in top 98 cities Required in Mumbai, Chennai and Bangalore. One high end Router already there. One more set of IGW IGW PE Router per City may be required Total 6 Routers. Core Connectivity New Core Routers to be deployed in top Cities with 10GE connectivity and nx10ge with Bangalore, Mumbai and Chennai. Total routers = Existing Core Routers to continue the way as it is. 24 November 2009 Core Network Planning 66 Core Network Planning Page 34 of 37

35 Line of Action 24 November 2009 Core Network Planning 67 Executive Summary of the Recommendation For Internal User The interface requirement can be taken care by existing spare GE interface / Spare Slots. 6 Routers required for IGW to be deployed in Mumbai, Chennai and Bangalore For Enterprise User Expansion in Top cities through rearrangement of Cards new POPs Core Connectivity New Core Routers to be deployed in Cities with 10GE connectivity and nx10ge with Bangalore, Mumbai and Chennai Existing Core Routers to continue the way as it is Other Points Unification of Data Network. No separate deployment of MPLS network in GSM Phase VI Any expansion shall inevitably look into the loading of existing deployment. Optimization & Sharing to be an integral part of Planning 24 November 2009 Core Network Planning 68 Core Network Planning Page 35 of 37

36 Proposal for MNGT Cancellation of Existing Tender There have been major changes in the Quantity / SOR. So, cancel the existing tender. Reassess the Requirement after One Year Minor Expansion The current requirement has come down drastically in the wake of low traffic from different access network. Reassess the traffic trend after one year (Dec 2010) Core Routers: 40 high end. Through tender Edge Routers: Few routers / interfaces in the existing router can be purchased on existing vendor / RQ / leverage on CDR infrastructure. Limit the number of OEMs to circumvent interop issue. 24 November 2009 Core Network Planning 69 Business Strategy: BSNL has always been aggressive in pricing (Low Cost) What needs to be done? Focus on BSNL Network instead of individual project or business vertical specific network. End-to-end visibility while planning Periodic assessment of utilization of network Nodal Cell: CNP cell for any IP / MPLS Network incl expansion on existing IP / MPLS network. Action Item BSNL How do we sustain this Model With continuous fall in Tariffs, Operating Margin are severely impacted. To maintain Profitability, sustained effort in reducing Network cost is one of the key elements Optimization and Sharing Optimization & Sharing to be an integral part of any planning across business verticals. Optimize CAPEX and OPEX through sharing of Network & effective inventory Management. Build as you grow. Step towards Integrated, Complementary and Value enhancement mode 24 November 2009 Core Network Planning 70 Core Network Planning Page 36 of 37

37 THANK YOU For Any Clarification, Pls Contact: SANJEEV VERMA DGM (CNP IV) Mob: November 2009 Core Network Planning 71 ************************************************************************ Core Network Planning Page 37 of 37