1 / 18

Developing Physical Architecture of NGN- a methodology

Explore the methodology for developing the physical architecture of Next Generation Networks (NGN) to achieve seamless interoperability, enhance knowledge creation, and boost competitiveness. Understand the functional and physical entities, reference points, and interfaces crucial for NGN implementation and deployment. Learn how a structured approach can mitigate interoperability risks and optimize investment.

dewees
Download Presentation

Developing Physical Architecture of NGN- a methodology

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. FORUM ON NEXT GENERATION STANDARDIZATION (Colombo, Sri Lanka, 7-10 April 2009) Developing Physical Architecture of NGN- a methodology R. K. Siddhartha Director, Dept. of Telecommunications, INDIA

  2. NGN -Interoperability is crucial “A packet based networkable to provide telecommunication services and able to make use of multiple broadband, QoS-enabled transport technologies and in which service related functions are independent from underlying transport related technologies. It enables unfettered access for users to networks and to competing service providers and/or services of their choice. It supports generalized mobility which will allow consistent and ubiquitous provision of services to users” -Ref. ITU-T Y.2001

  3. ITU mark program • a Catalyst for Interoperability standards in ITU Recommendations - intrinsic interoperability in standards • Can be feedback mechanism for fixing up standards for including attributes of interoperability • Boost to indigenization of the Telecom Equipments • Enhance Knowledge creation process • Increase Competitiveness

  4. Resolution 76 • that providing for interoperability should be the ultimate aim of future ITU-T Recommendations • Considered : the difficulties of equipment level interoperability • Noted : need to assist developing countries in facilitating solutions which will exhibit interoperability and reduce the cost of systems and equipment procurement by operators • Instructed : Study Groups to identify ITU recommendations in light of interoperability

  5. Paradigm Shift ! Physical Entity Resolution 76 ITU Mark Equipment testing

  6. Functional Architecture [Ref. ITU-T Y.2012]

  7. Need for Physical Architecture • Physical architecture will decrease interoperability risk • Achieving seamless interoperability at the basic-level is crucial • Functional architecture is for Implementers/ developers not for Operators & N/W designers • Modular Architecture- -Implementation/ Deployment ease -Vendor independence -Optimize investment

  8. Functional Entities Application support functions & service support function S-6: S Authentication & authorisation FE S-5: Service user profile FE S-14: Media Resource broker FE S-1: Serving call Session control FE S-13: Media Resource Control FE [Ref. ITU-T Y.2012]

  9. Reference Points & Interfaces • Ref. points (Service control functions) • S-1 (S-CSC-FE) - S-13 (MRC-FE) -----------------SIP • S-1 (S-CSC-FE) - S-5(SUP-FE), S-6(SAA-FE)---- Diameter • Reference points (ASF/SSF) • S-1 (S-CSC-FE) - ASF/SSF---------SIP • S-5 (SUP-FE) - ASF/SSF------------Diameter • S-6 (SAA-FE) – ASF/SSF-----------Diameter • S-13 (MRC-FE) – ASF/SSF---------SIP, HTTP, VoiceXML, MSCML • S-14 (MRB-FE) – ASF/SSF---------SIP, HTTP, SOAP

  10. Functional Entities-Physical Entities S-1: Serving call session control FE (S-CSC-FE) S-5: Service user profile FE (SUP-FE) S-6: Service authentication & authorisation FE (SAA-FE) S-13: Media resource control FE (MRC-FE) S-14: Media Resource broker FE (MRB-FE) Application support functions and service support functions Proxy & Registrar Server Home Subscriber Server (HSS) Media Server Application Server

  11. A Section of Possible Physical Architecture of NGN for Interop To other Physical Entities of NGN network Toother Physical Entities Of NGN Network Proxy & Registrar Server Application Server IOPt III Home Subscriber Server IOPt I IOPt II Media Server

  12. Interop Req. for Application Server IOPt for Application Server + + = IOPt II IOPt III IOPt I Total of Three Interfaces

  13. Vertical Cut API --- PHY Protocols IOPt

  14. Types of Application Server towards network Using OSA towards network Using CAMEL OSA-SCS IM-SSF SIP AS

  15. Y.phy_arch_ngn “Architectural realizations and open interfaces in NGN” • Recommendation for Interoperability • Basic Physical architecture showing physical elements of NGN • Open interfaces are spelled for each element

  16. Proposed Structure Y.phy_arch_ngn Physical Architecture of NGN Each element defined for Interoperability Each Interface with vertical cut layers Each protocol dressed up for Interoperability • Four tier document

  17. ITU Mark & Y.phy-arch-ngn • Can be a Seed document for Interoperability Standards & testing in NGN • Target – 50% of elements of NGN are standardized as physical entities it can help achieving objectives of NGN (Y. 2oo1) • Digital Opportunity Index will be improved in developing countries

  18. Thank You !

More Related