1 / 60

NIB-II An Overview

NIB-II An Overview. Internet Access Methods. Dial-up Internet Connection A) PSTN i) Sancharnet (172233) ii) Netone (172222) B) ISDN (172225). Internet Access Methods. Leased Line. Internet Access Methods. Broadband

jcatchings
Télécharger la présentation

NIB-II An Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. NIB-II An Overview

  2. Internet Access Methods • Dial-up Internet Connection A) PSTN i) Sancharnet (172233) ii) Netone (172222) B) ISDN (172225)

  3. Internet Access Methods • Leased Line

  4. Internet Access Methods • Broadband To provide Cost- effective internet connection with higher speed by using the available copper media. Brandname : DATAONE It is considered in NIB – II Project 2.2

  5. NIB-II • NIB-II envisages four projects Project 1 : MPLS based IP Infrastructure in 71 cities Project 2.1 : Access Gateway platform Narrow band Project 2.2 : Access Gateway Platform Broadband Project 3 : Services Platform consisting of messaging, Provisioning, billing, customer care, enterprise management system and Data centres.

  6. NIB-II Services A)Internet Access Dialup access services / Leased Access Services Digital Subscriber Line (DSL) access services: Broadband “always-on-internet” access over copper cables Direct Ethernet access services: Broadband “always-on-internet” access using Fiber-to-the-building 6

  7. NIB-II Services B) Virtual Private Network (VPN) services Layer 2 MPLS VPN Services: Point-to-point connectivity between corporate LAN sites Layer 3 MPLS VPN Intranet and Extranet Services: LAN interconnectivity between multiple Corporate LAN sites Managed Customer Premises Equipment (CPE) Services 7

  8. NIB-II Services C) Value Added Services -Encryption Services -Firewall Services -Multicast Services -Network Address Translation (NAT) • Messaging Services • Internet Data Center Services at Bangalore, Delhi and Mumbai.

  9. NIB-II Services • Broad Band Services • Broadcast TV using IP Multicasting service • Multicast video streaming services • Interactive Distant learning using IP multicasting Services • Video on demand • Interactive gaming service

  10. Node Types • Total nodes are 71 • categorized as A1, A2, A3, A4, B1 & B2 nodes. • Project wise Deployment

  11. MPLS IP INFRASTRUCTURE (Project1)

  12. Why MPLS instead of TCP • In TCP/ IP, Routing information is in the form of packets, which are opened-up. So less secured. • In MPLS, Routing information is labeled down, so more secure.

  13. Project 1 Architecture • Two Layers : • 1. Core Layer - Constitutes high speed internet Backbone • Edge Layer • - Provide the customer access

  14. NIB-II CORE ROUTER A1 CITIES

  15. Jullundar Lucknow Jaipur Patna Indore Pune Ahmedabad Ernakulam Hyderabad NIB-II CORE ROUTER A1,A2,A3 CONNECTIVITY DIAGRAM STM-16 LINK A1 Nodes - 5 A1 Router A2+A3 Nodes - 9 A2 Router A3 Router Noida Kolkata Mumbai Chennai Banglore

  16. Allahabad Guwahati Chandigarh Lucknow Ranchi Patna Jullundar Jaipur Noida Bhubneshwar Ahmedabad Indore Kolkata Manglore Mumbai Nagpur Coimbtore Pune Chennai Banglore Raipur Ernakulam Vijaywada Hyderabad BSNL NIB-II CORE ROUTER A1,A2,A3 &A4 CONNECTIVITY DIAGRAM LEGENDS STM-16 LINK A1 Nodes - 5 STM-1 LINK A2+A3 Nodes - 9 A4 Nodes - 10 CISCO ROUTER JUNIPER ROUTER (Existing with BSNL)

  17. BSNL NIB-II CORE ROUTER A1,A2,A3 &A4 CONNECTIVITY DIAGRAM

  18. Edge Network (Customer Interface) Edge routers in 71 cities connected to the core layer either locally through the Gigabit Ethernet interfaces or remotely through dual homed STM-1 links. A1 Cities- Chennai ,Mumbai, Bangalore, Delhi and Kolkata. A2 Cities- Hyderabad, Pune and Ahmadabad. A3 Cities- Lucknow, Jullundhar, Jaipur, Indore, Ernakulam and patna. A4 Cities- Coimbatore, Chandigarh, Allahabad, Guwahati, Ranchi,Bhubaneshwar, Raipur, Mangalore, Nagpur and Vijayawada. B1 Cities- 21nodes B2 Cities- 26nodes

  19. Allahabad Guwahati Chandigarh Lucknow Patna Ranchi Jullundar Jaipur Noida Ahmedabad Bhubneshwar Indore Kolkata Mumbai Nagpur Coimbtore Pune Chennai Banglore Ernakulam Raipur Manglore Hyderabad Durgapur Dimapur Gwalior Madurai Trichy Palghat Trivandrum Trichur Kalikat Mehsana Ambala Vizag Rajmundary Siliguri Belgaum Kalyan Panjim Aurangabad Kolhapur Nashik Bhopal Tirupati Mysore Surat Faridabad Gurgaon Pondicherry Meerut Agra Dehradun Ludhiana Ferozpur Kanpur Noida Amritsar Shimla Jodhpur Hubli Jamshedpur Vadodara Rajkot Jabalpur Shilong Ghaziabad Varanasi Ajmer Vijaywada NIB-II A1,A2,A3,A4,B1& B2 ROUTER CONNECTIVITY DIAGRAM A1 Nodes - 5 A2+A3 Nodes - 9 A4 Nodes - 10 B1 + B2 Nodes - 47

  20. Devices in A1 Cities: • Core Router ------------ Cisco12416 • Edge Router ------------ Cisco 7613 Devices in A2 & A3 Cities: • Core Router ------------ Cisco12410 • Edge Router ------------ Cisco 7613 Devices in A4 Cities: • Core Router ------------ Juniper M40e • Edge Router ------------ Cisco 7613 Devices in B1&B2 Cities: • Edge Router ------------ Cisco 7613

  21. Components of Narrow Band Access Network • Narrowband band Remote Access Server • LAN Switch • eMS Server

  22. BROAD BAND ACCESS NETWORK (PROJECT 2.2)

  23. Services planned Through Broad band Network • Primary source of Internet bandwidth for retail users for applications such as Web browsing, e-commerce etc. • Multicast video services, video-on-demand etc. through the BRAS. • Allow Wholesale BRAS ports to be assigned to smaller ISPs through the franchisee model wherein the later has a separate network of DSLAMs, AAA, LDAP through a revenue scheme of BSNL. • Dial VPN (VPDN) user connects to NIB-II through the Narrow band RAS and is connected to its private network through a secure L2TP tunnel established between Narrowband RAS and Broadband RAS. • support for both prepaid and postpaid Broad band services.

  24. Components of Broad Band Access Network • Broad band Remote Access Server(BBRAS) • Gigabit and Fast Ethernet Aggregation Switches (LAN Switches). • Digital Subscriber Line Access Multiplexers (DSLAMs) • SSSS/SSSC (Subscriber Service Selection System/ Centre) • Servers for AAA, LDAP at NOC. • Provisioning and configuration management at NOC. • DSL CPEs

  25. Core Network interfaces • Content BB • Server Layer 2 GigE Aggregation SW NIB-II Broadband DSL Deployment SSSS Core NOTE: Items indicated in dotted router FE • line boxes are not part of Project 2.2 GigE Broadband FE RAS GigE GigE FE FE SDH RING GigE B1 city GigE B2 city LAN Switch Gig E & FE FE FE FE GE 48 Port 24 Port DSLAM DSLAM 480 Port 240 Port 120 Port 64 Port DSLAM DSLAM DSLAM DSLAM ADSL ADSL ADSL terminals ADSL terminals terminals terminals

  26. Architecture • The DSLAMs will in general be collocated with existing PSTN exchanges which provide last mile access to customers over copper wire up to average span lengths of 3 kms. • All DSLAMs will be aggregated through a FE interface except 480 port DSLAM, Which will be aggregated through Gigabit Ethernet Interface. • The 240 port DSLAM will have two number of FE interface. • The FX or GBIC module in DSLAM and LAN switch should be capable of driving upto 10km on a single mode fibre. • The SX or GBIC module in LAN Switch used for connecting Tier2 to Tier1 will support 40km. • In bigger cities like A1, A2, A3 and A4,one BBRAS per city will be deployed initially. • There will be no BBRAS at B1 and B2 cities. • The DSLAMs in B1.B2 and other lower hierarchical cities will be aggregated through Layer 2 switches, and will be connected to the nearest BBRAS of A cities on Ethernet over SDH. • The BRAS shall terminate the PPP sessions initiated by the customer and extend the connection further to MPLS VPN/ Internet as desired by the the customer.

  27. BRAS Classification Back plane Capacity Processing Capacity TEC GR Reference BRAS at A1 sites 8 Gbps full duplex 15 Million PPS GR/RAS-03/01 OCT 03-High End BRAS at A2 sites 4 Gbps full duplex 7 Million PPS GR/RAS-03/01 OCT 03-Medium End BRAS at A3 sites BRAS at A4 sites 3 Gbps full duplex 3 Million PPS GR/RAS-03/01 OCT 03-Low End BRAS classification

  28. City Type No of Cities* Customers Per BRAS Total BRAS Total Subscribers Year2 Total Qty Per City A1 3 20000 40000 60000 1 3 A2 3 12000 20000 32000 1 3 A3 7 10000 14000 24000 1 7 A4 10 6000 10000 16000 1 10 Total Number of BRAS 23 BRAS in 23 cities Year1

  29. DSLAM • The DSLAM will provide Access from 128Kbps to 8Mbps • The DSLAM will support for QOS features such as Committed Access Rate between CPE and DSLAM,Traffic Policing per port • The DSLAM will work satisfactory without any degradation in performance and without using any repeater/regenerator over a distance for various access speeds for 0.5mm copper pair.

  30. DSLAM Deployment Plan in 198 cities

  31. DSLAM Type Port Requirement per DSLAM Total DSLAMs Total DSLAM Ports Year1 Year2 Total Year1 Year2 Total 480 155 265 420 603 93465 159795 253260 240 78 132 210 675 52650 89100 141750 120 39 66 105 617 24063 40722 64785 64 20 33 53 348 6960 11484 18444 24 8 12 20 258 48 15 25 40 129 1935 3225 5160 Grand Total 2630 181137 307422 488559 2064 3096 5160 Year Wise Port Requirement for each DSLAM type

  32. City Type No of Cities Port Requirement per City Total Ports Requirement Year1 Year2 Total Year1 Year2 Total Others 129 31 49 80 3999 6321 10320 Grand Total 181137 307422 488559 Year Wise Port Requirement for each City A1 3 17880 30430 48310 53640 91290 144930 A2 3 8940 15215 24155 26820 45645 72465 36162 A3 6 6027 10251 16278 61506 97668 A4 10 3384 5754 9138 33840 57540 91380 B1 21 858 1454 2312 18018 30534 48552 B2 26 333 561 894 8658 14586 23244

  33. Subscriber Service Selection System/ Centre • All the customer’s profile shall be stored centrally. • The SSSS/SSSC will act as a portal into the Network, where advertisements, automatic Provisioning, and Service registration will take place. • The SSSS/SSSC will allow real time subscriber provisioning and usage collection data. • The SSSC will allow service provider to define new services, modify the existing one and even delete the offered services under authorised user name and password.

  34. Radius Server • RAS Support for RADIUS authentication and RADIUS Accounting • Irrespective of mode of access (such as Dial-up Internet access,outsourced remote access ,managed VPNs, Broadband etc),it will manage the Authentication of all users/customers- both locally and via proxy RADIUS- and deliver the appropriate level of service to each customer. • RADIUS will support interfacing with LDAP based authentication, billing and Provisioning systems. • It will include advanced proxy RADIUS support.It will be able to act as a proxy target server, and can forward proxy requests to other RADIUS servers. • It will load balance authentication requests between several SQL or LDAP databases, to eliminate the risk of a single point failure, and increase performance on busy networks. • The RADIUS will generate CDRs for the Billing system and the CDRs will contain the following information • The calling IP address allotted by the RADIUS • Start Time and Date • End Time and Date • Volume of data transmitted and port type.

  35. LDAP (Directory Server) • The Directory Server shall support unlimited number of read only consumers for authentication queries. • The Directory Server shall support Class of Service and Role based mechanism. • The Directory Server shall support Storage of Digital Certificates. • The LDAP and RADIUS will be able to handle a customer base of 8 Lakhs assuming a concurrency rate of 40% . • The authentication will not take more than 1 sec under the full load.

  36. eMS & provisioning for Broadband band Network • At each regional POP, there will be server running in clustered mode running element manager application of DSLAM, LAN Switch and DSLCPEs. • The element manager application of BBRAS and system management of SSSS/SSSC will be running at main NOC with Disaster Recovery at secondary NOC. • The Centralized Provisioning system will be running Centrally at NOC with with Disaster Recovery at secondary NOC. • Fault and Performance data of Broad band Network will be Collected by NMS deployed in Project1. • eMS shall support the inventory management, which is available in Project1. • For each service ,Provisioning of subscriber will be from a single interface.E.g. It will be possible to provision High speed internet services or VPN services from a single interface.

  37. IMPLEMENTATION OF OSS, MESSAGING,STORAGE,BILLING, EMS AND SECURITY SOLUTIONS (PROJECT 3)

  38. Messaging • Messaging Solution of NIB-II will provide the SMTP,POP3,IMAP4, WEBMAIL,WAPMAIL and Notifications services as a Class Of Service to all the customers of NIB-II and NIB-I. • Will support for Country wide roaming for dial up and message store access through any data centre. • The Messaging Server will support Wireless messaging and Directory services to WAP enabled phones and laptop users. • Message store will be content aware to support different types of services to be created by BSNL ranging from text email to multi-media messaging service . • Will provide Family Mailbox where the head of the family can manage options for Family members.options will include setting of allowed and block senders and recipients and control of Anti-SPAM settings.

  39. Messaging • Messaging solution shall provide flexible control of message aging to define the conditions under which messages are automatically erased. • Web mail interface will support multimedia message types for voice and fax mail, providing unified messaging interface in future. • Message Transfer Agent (MTA)s will be designed to handle peak loads without service degradation or message loss. • MTAs will be designed to handle large message queues.There will be capability available to analyze and manage large message queues generated due to unreachability of message store(internal) and mail exchangers of other ISPs(external) or SPAM. .

  40. Messaging Traffic Volumetric

  41. DISTRIBUTION OF MAIL BOXES

  42. Web Hosting • Web space (Data Storage) on servers based on UNIX and Microsoft for hosting HTML pages with browser. • Ftp access for uploading and downloading pages as per the plan. Restriction on simultaneous ftp sessions. • FrontPage etc.access for Web-publishing. • Multiple Email Ids per domain with flexible email quota, as per the plan. • Web Interface for centralised administration by user and administrators for services,usage reports, invoice and other reports. • It will provide access to customers for analysing the Web-site performance through analysis tools. • Interface for online registration of domain name.

  43. Web Collocation • Necessary Security measures will be implemented both from customer and BSNL’s perspective. • Billing for this will be done on the basis of usage. • One of the service differentiator will be bandwidth on which the server is collocated.

  44. Security Solution • AntiVirus solution : It will provide a mechanism to detect unknown virus.The solution will protect any Gateway and SMTP traffic from virus. • Notification: For mails containing repeated complaints regarding abuse from the same IP address,mail will be sent automatically to the technical contact of the assignee of that IP address. • Network Intrusion detection System: The NIDS will detect unauthorized internal/external intrusion attempts into the data centres of NIB-II and will enable to apply appropriate policies on the firewall so as to prevent such attacks in real time.Suitable alarms will also be sent to the Security Control Console. • Anti Control System: It is provided for Database servers, Messaging Stores, Web-Hosting Servers and NIDS. • Self-protection:Must be able to prevent hackers with root/administrator access from circumventing or shutting down the security engine. • Resource protection :Must allow controlling of access to all system resources including data files, devices, processes/services and audit files. • Rights delegation: Must provide the ability to designate specific users as administrators, auditors and password managers etc with appropriate rights. • Program Controls: Must provide protection against Back Doors and Trojan Horses.

  45. Objective of Operation Support System(OSS) • OSS will allow BSNL to carryout automation of majority of the processes needed in service definition & provisioning,service activation, authentication, authorisation and accounting,mediation,rating,billing and invoicing etc. including service assurance and customer care. • OSS shall provide an integrated view of all customers and services across the network for Customer life cycle management • .This includes a customizable web-based GUI client tools for configuration and setup.

  46. OSS END-TO-END COMPONENT IMPLEMENTATION

  47. Web Portal • Web Portal will be the gateway for customer and CSR based on their authorisations for accessing various system, services etc. • Portal will have an integration, with NMS,EMS and OSS for providing services to the BSNL’s customer service representatives(direct ,indirect,helpdesk, supervisor ) and account managers • Portal services Ranging from business, process,network, customer specific maps/views,trouble-ticketing,pre-sales query,post-sales order-booking ,order tracking ,trouble –shooting etc. • Portal will integrate with components like Service Provisioning, Order Management,Billing,Customer Care,EMS and Messaging etc.to provide a unified view of the network and services to the customers and CSRs for all the front office functions and some back office functions. • Order status and history provide both subscribers and the customer service representatives with sufficient data to fully manage and monitor the service selection and delivery process. • It will be possible to provide a user friendly interface for customers to plan and schedule their bandwidth for Band width on Demand services.

  48. Services Provided by portal to the customers • Customer registration services for both pre-paid and post-paid customer • Self-registration for getting information about products and services. • Self-registration for availing services such as post-paid dialup service based on telephone number authentication. • Shopping cart for procuring services. • Access to services such as messaging,web-hosting,storage and content-services etc.This will include on demand services like video on demand and online gaming etc. • Booking an order for services.Allow the user to submit,and track service requests online at any time. • View current bill status in real time including billed,unbilled and pre-billed services, payment-details and other related information • Reporting a problem by opening a fault docket and tracking its solution. • View the status of related network and services subscribed. • View the status of SLA compliance,SLA resolution and rebates applied through integration with billing and NMS.

  49. ORDER MANAGEMENT • OM will have • Customer Interface Management • Order Entry and Validation • Workflow Management Customer Interface Management &Order Entry and Validation: • Order will be entered through Web-portal by CSR or Customer directly. • CSR will accept the order after completion of signed order form by the customer.He will scan it and attach it with the online order form. • All orders will be checked against the feasibility from the RMS For all committed orders, check will be made for customers credit worthiness/default and the billing system will generate a unique ID for the customer. • It will be possible to query the status of order ,service,billing etc. on the basis of unique ID. • OM will track the order status. • OM will inform the billing system of successful provisioning or else it will roll back all the steps. • Record all the transactions between OM and customer. • Record the details of the services provisioned for the customer. • Purge customer data from RDBMS and LDAP databases based on pre-defined and configurable policies when the customer surrenders service.

More Related