1 / 15

NGN- Interconnection

NGN- Interconnection. S. K. Gupta, Advisor (CN&IT) Telecom Regulatory Authority of India. Agenda. NGN- Interconnection Issues. Way forward. NGN- Interconnection issues. Interconnection among networks is necessary to ensure end-to-end services to the subscribers

Download Presentation

NGN- Interconnection

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. NGN- Interconnection S. K. Gupta, Advisor (CN&IT) Telecom Regulatory Authority of India

  2. Agenda NGN- Interconnection Issues • Way forward TRAI

  3. NGN- Interconnection issues • Interconnection among networks is necessary to ensure end-to-end services to the subscribers • TDM based interconnection is simple and well defined • Multiservice IP Based interconnection is complex • Well defined regulatory framework to ensure effective interconnection among service providers is necessary to promote competition and reduce entry barriers TDM based interconnection • Hierarchical points of interconnection • Use of standard SS7 signaling • Interconnection to primarily support voice calls • Pre-determined routing of calls based on dialed numbers NGN based interconnection • Flat interconnection • Use of different signaling and protocols to support multiple services • Interconnection needs to supports multiple services • Dynamic policy based traffic routing TRAI

  4. NGN- Interconnection issues Present Networks Compatibility mainly addressed by service specific networks NGN Compatibility at UNI, NNI is crucial due to high flexibility TRAI

  5. NGN- Interconnection issues • NGN is considered as converged network aggregating different functionalities of existing network with common IP backbone • It looks simple in theory but implementation is complex • Challenges : • Interoperability among networks using multiple protocols • Implementing open interface between application & network and delivering end-to-end service with defined QoS parameters TRAI

  6. NGN- Interconnection issues • Point of interconnection • Centralized vs. Hierarchical • Peer to Peer vs. Interconnect Exchange • Support for existing TDM Networks • Time frame for co-existence of TDM & NGN before complete migration to NGN • Revised Interconnect Offer • Model of physical Interconnection Interconnection evolution • TDM- TDM • TDM – NGN • NGN – NGN Related Issues • Point of centralized interconnection • Ensuring security at interconnect point • Funding and management of interconnect exchange • Ensuring QoS at interconnection • Effective resource management TRAI

  7. NGN- Interconnection issues • Signaling requirement • Support for signaling protocols to suit present network requirements and future service requirement at interconnection. Presently SS7 is standard signaling protocol in TDM networks. • Signaling has to be deliberated at • Network-Network Interface (NNI) level • User -Network Interface level (UNI) • Application- Network Interface (ANI) level • Between Gateway and Session Border Controller (SBC) Typical NGN Signaling • NNI : SIP-1, BICC and H.323 • Physical interface : SDH or Gigabit Ethernet • Within Networks : MPLS, RPR • ANI: SIP, INAP, SMTP, FTP • Media Gateway: H.248 • Media Signaling Gateways : SIGTRAN TRAI

  8. NGN- Interconnection issues • Compatibility Issue: • Different protocols used in NGN has been developed with different approach • Number of functionalities have been left as optional • Ensuring end-to-end services using optional protocol functionalities by few vendors may be difficult • Protocol translation for such optional facilities by session border controller is a challenge H.323 • It is umbrella specification defined by ITU and consists of • H.225 RAS Signalling • H.245 Control Signaling • H. 450 Supplementary services • Other standards for voice and video SIP • It is created by Internet Engineering Task Force (IETF) as RFC 2543 • Provide advance signalling and control functionalities • Uses RTP/RTCP for real time data transmission 8 05/11/2014 TRAI

  9. NGN: Session Border Controller • NGN network require: • Physical Interpretabilities with different networks using different interfaces • Isolation of network from others in case of attacks/networks related problem • Support for variety of protocols for different services • Flexibility of designing network topology and resource management within network • Facilitate effective communication with other network Session Border Controller is a Solution 9 05/11/2014 TRAI

  10. NGN: Session Border Controller Role of SBC • Managing signaling and media paths for a multimedia session • Scalability of wider range of applications over networks • Provide comprehensive security and ways to monetize running services • Regulatory provisions such as Lawful interception • Honoring SLAs with peers and customers • SBC is ideally situated to interconnect disparate networks and provides following capabilities: • Connectivity • Network Address Translation • Security • Policy Enforcement and QoS control • Regulatory Compliance • Billing TRAI

  11. NGN: Session Border Controller • SBC deployment approaches in service providers networks includes : • Service provider-to- service Provider Interconnect • Service Provider-to-Enterprise Peering • Service Provider-to-Residential Interconnect Source: www.cisco.com TRAI

  12. NGN- Interconnection issues • NGN may enable more services leading to additional functional flexibility . • Numbering/addressing to be used in NGN shall complement and support existing numbering scheme. • National numbering plans may need modification. NGN should support: • Number portability • Carrier Selection etc. Probable NGN addressing : • IPv4 /IPv6 addresses • Domain Name Server • Uniform Resource Identifier (URI) etc. TRAI

  13. NGN- Interconnection issues • Measurement and accounting of traffic : • NGN-NGN • Application provider- NGN • NGN - End user for different applications • Charging on functional and application basis Inter-operator Compensation : • Charging for QoS, BW, application at interconnect points Typical NGN charging : • CPNP , Bill and Keep, QoS based Charging • Volume and Hit based charging NGN Charging challenges: • Lower cost more functionality • Sharing of Intelligent networks • Benefits of distinction between transport and services • Reconciliation of application / content providers charges in • “on-deck” scenario • “ off-deck” scenario TRAI

  14. Way Forward • Need for close coordination of relevant groups to develop region specific understanding on parameter left for country specific needs/ future requirement • Development of local certifying agencies / test labs for interface approval • Mandate use of only approved interfaces in NGN networks • Close coordination with vendors to overcome bottleneck and foster competition. TRAI

  15. Thank You S K Gupta , Advisor, TRAI Mahanagar Doorsanchar Bhawan, J.L. Nehru Marg, New Delhi – 110002 Ph. +91-11- 23217914 (O) +91-11- 23211998 (Fax) advcn@trai.gov.in TRAI

More Related