Presentation on theme: "19/09/2015 NGN related standardization issues: Service Platform 2004.05.10 TTA (Korea) GSC-9, Seoul 1 SOURCE: KT TITLE:NGN related standardization issues:"— Presentation transcript:
19/09/2015 NGN related standardization issues: Service Platform 2004.05.10 TTA (Korea) GSC-9, Seoul 1 SOURCE: KT TITLE:NGN related standardization issues: Service Platform AGENDA ITEM:5.3 CONTACT:Jinkyung Hwang, E-mail: firstname.lastname@example.org, TEL: +82-2-526-6830, FAX: +82-2-526-5262 GSC9/GTSC_012
GSC-9, Seoul NGN in Korea BcN (Broadband convergence Network) is a term generally used in Korea for NGN. Definition & Goal of BcN –Next Generation Convergence Network integrating communication, broadcasting and Internet and providing QoS-enabled multimedia services anywhere, anytime, and by any means (source: BcN Forum, Korea) –Goal: Constructing core /network infrastructure for realizing Broadband IT Korea by building Broadband converged network 20 million subscribers(50~100 Mbps) until year 2010 Scope –Open API, End-to-end QoS, Security, IPv6 –MPLS, DWDM, OXC –FTTH, HPi, WLAN, DMB, HDTV, RFID, Ubiquitous access Requirements for BcN –Features necessary for supporting Integrated Home network, Broadcasting, Multimedia contents and communications are added to the general requirements for NGN. NGN requirements at ITU-T (source: JRG-NGN) –IP connectivity independent underlying transport layer, Access independence, Roaming and nomadism, Open service environment, Evolution path from legacy network to NGN, Enhanced security, Separation of call and bearer control, Call and session control based on IETF protocols, Convergence of fixed and mobile networks
GSC-9, Seoul Service & Platform requirements Service Requirements of BcN –Seamless provision of existing PSTN services –Converged-type of application services –Customer Needs oriented Multimedia services –Standard Protocol and Open API based fluent service environment Service Platform requirements of BcN –High availability –Standard and Open interface and system architecture –Real-time processing –Scalability and Extensibility –Reliability –QoS-guaranteed –Carrier-grade and massive traffic
GSC-9, Seoul Application Evolution to NGN SS7-IN call based app. Internet-IN call based app. Internet call based app. Managed packet call based app. Managed packet call, data & contents based app. Voice & Data + Broadcast & Comm. + Wireless & Wirelined app. Service Evolution Service SCP, SSP, IP,.. SCP, PINT/SPIRITS-GW,. VoIP GK, GW, SGW, Feature server Softswitch, App.server, Media server Softswitch, AS, MS, Streaming server, Content server Service POP based AS, Fixed- mobile service AS, IP multimedia AS, Broadcast AS.. Platform Evolution Service Platform
GSC-9, Seoul Current status –Reference architecture development for BcN –Standard open interface enabling high revenue earning is the key issue Standardization activities in Korea TTA NGN Project Group (ToR) –NGN architecture and access –NGN open API –SoftSwitch –Sigtran VoIP-Forum (technical committees) –VoIP protocol and services –Wideband audio codec –Security –Next gen VoiP Codec –H.323 –Next gen VoIP –Interoperation Test –VoIP networking –Law and Regulation BcN Forum (technical committees) –Law and Regulation –Service –Convergent network –Wireline access/Wireless access –Terminal equipment –Interoperability –Standard reference model
GSC-9, Seoul Issues for discussion and collaboration Current NGN standards do not fully take into account the current environment where services are converged. –NGN call control related Signaling & API: IETF, ITU-T SG11, Parlay Architecture: ITU-T, 3GPP/2, ETSI, … Interoperability: MSF, IMPP, … –Home Network related ECHONET, HAVi, HomePNA, HomeRF, UPnP, UWB,.. –Broadcast related OpenCable, T-DMB, S-DMB, DVB-T, … –Fixed-Mobile convergence related –HPi, Mobile IP related –AAA, QoS, Security issues in convergence environment Wholistic approach in standards setting is required Call control is well defined but content, data (streaming) and broadcast control are very little touched upon in current NGN standards. Collaborations among SDOs are required. Enhanced functional architecture is required for converged service environment. Interoperability among different service platforms are also necessary for integrated services. Cooperation in Interoperability test needs to be encouraged among SDOs.