Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. NGN and its S tandardization September 27, 2006 NEC Corporation ITU-T NGN security requirements (Y.2701) editor Takashi Egawa NGN: Next Generation Network
  2. 2. NGN is coming! Evolution of enterprise networks Decrease of $/Bit Evolution of telecommunications FMC Next generation Internet WEB2.0 、 RSS Telecommunication- broadcast convergence NGN (Next Generation Networks) (Evolution of architecture and revolutionary services) needs meets seeds ・ Broadband/mobile gets popular ・ network is now a part of life ・ Expansion of biz-use net ・ Emerges net-based business ・ Opt/IP/mobile technologies ・ Intl. standardization individuals Business Technologies Needs Seeds Lifestyle changes New business changes Network business leap Starting of new evolution
  3. 3. Expectation and changes of NGN <ul><li>Increase of usability </li></ul><ul><li>Flourish of services </li></ul><ul><li>Easy to use, with ease </li></ul><ul><li>Simple/cheap </li></ul>For personal users For enterprise <ul><li>Rebuilding of business </li></ul><ul><li>New source of profit </li></ul><ul><li>CAPEX/OPEX decrease </li></ul><ul><li>Business area expansion </li></ul>For network providers NGN: enabling technology Revolution for layman/enterprise as well as network providers <ul><li>Infrastructure of biz </li></ul><ul><li>Biz.expansion base </li></ul><ul><li>Adoption to new biz models </li></ul><ul><li>Reliable/cheap </li></ul>
  4. 4. Agenda <ul><li>Why NGN? </li></ul><ul><li>Standardization process </li></ul><ul><li>ITU-T NGN </li></ul><ul><li>NGN standardization in Japan </li></ul>
  5. 5. <ul><li>Why NGN? </li></ul>
  6. 6. Technological necessity of NGN Does the Internet continue to evolve? Best-effort QoS: New applications are hard to develop Commercial quality real-time communications are difficult to provide TV conference, streaming, … Security/Reliability: Not carrier-grade Children/elders can’t apply patches everyday Mobility: the next bonanza will be in mobile gadgets Current (ordinary) IP assumes fixed network Discussions at Linux Symposium (2006) The Internet created various applications thanks to the freedom of end-users. Does it apply to IPTV, Web 2.0, or FMC?
  7. 7. Limitation from IP’s principle <ul><li>Routing table are updated in local manner; no network-wide, no equipment-wide sync  scalable and cheap, but no QoS guarantee becomes possible </li></ul><ul><li>No state in routers; minimize memory access  expandable and faster, but traffic engineering becomes unavailable </li></ul><ul><li>Very limited functions in networks  interoperable ‘Internet Protocol’, but no security, no QoS-awareness </li></ul>router router router Packet (header + payload) TE TE Routing table Principle of IP The problems tightly linked with IP principle and merits
  8. 8. IP Design Philosophy: Main Goals <ul><li>Effective multiplexed utilization of existing networks </li></ul><ul><ul><li>Packet switching, not circuit switching </li></ul></ul><ul><li>Continued communication despite network failures </li></ul><ul><ul><li>Routers don’t store state about ongoing transfers </li></ul></ul><ul><ul><li>End-hosts provide key communication services </li></ul></ul><ul><li>Support for multiple types of communication service </li></ul><ul><ul><li>Multiple transport protocols (e.g., TCP and UDP) </li></ul></ul><ul><li>Accommodation of variety of different networks </li></ul><ul><ul><li>Simple, best-effort packet delivery service </li></ul></ul><ul><ul><li>Packets may be lost, corrupted, or delivered out of order </li></ul></ul><ul><li>Distributed management of network resources </li></ul><ul><ul><li>Multiple institutions managing the network </li></ul></ul><ul><ul><li>Intradomain and interdomain routing protocols </li></ul></ul>Grosshauser (2002)
  9. 9. Characteristics of the Internet <ul><li>The Internet is </li></ul><ul><ul><li>Decentralized (loose confederation of peers) </li></ul></ul><ul><ul><li>Self-configuring (no global registry of topology) </li></ul></ul><ul><ul><li>Stateless (limited information in the routers) </li></ul></ul><ul><ul><li>Connectionless (no fixed connection between hosts) </li></ul></ul><ul><li>These attributes contribute </li></ul><ul><ul><li>To the success of the Internet </li></ul></ul><ul><ul><li>To the rapid growth of the Internet </li></ul></ul><ul><ul><li>… and the difficulty of controlling the Internet :< </li></ul></ul>Grosshauser (2002)
  10. 10. Operator Philosophy: Tension with IP <ul><li>Accountability of network resources </li></ul><ul><ul><li>But, routers don't maintain state about transfer </li></ul></ul><ul><ul><li>But, measurement isn’t part of the infrastructure </li></ul></ul><ul><li>Reliability/predictability of services </li></ul><ul><ul><li>But, IP doesn’t provide performance guarantees </li></ul></ul><ul><ul><li>But, equipment is not very reliable (no ‘five-9s’) Downtime: IP networks: 471min/year, POTS: <5min/year </li></ul></ul><ul><li>Fine-grained control over the network </li></ul><ul><ul><li>But, routers don’t do fine-grain resource allocation </li></ul></ul><ul><ul><li>But, network self-configures after failures </li></ul></ul><ul><li>End-to-end control over communication </li></ul><ul><ul><li>But, end hosts adapt to congestion </li></ul></ul><ul><ul><li>But, traffic may traverse multiple domains </li></ul></ul>Grosshauser (2002)
  11. 11. But operators cannot rely on PSTN services any more # of calls in Japan (from MIC’s white paper 2005) (1e8) (fiscal year) PDC mobile fixed Total In most developed countries, 2000 or around was the peak of telephone traffic
  12. 12. We must make Operator-friendly IP networks <ul><li>NTT: trial starts by the end of fiscal 2006 </li></ul><ul><li>KDDI: Fixed network becomes all-IP by fiscal 2007 </li></ul><ul><li>BT: by 2008 </li></ul><ul><li>Korea: long-distance is by 2007, local by 2010 </li></ul>IP traffic > telephone traffic Fiscal 2004: 34.1Gbps (in Japan: converted 533k Erlang using 64kbps/call) > -5%/year May 2006: 524Gbps (Public Internet in Japan) > 20%/year Timeline IP must be the base of future networks
  13. 13. NGN: best mix of packet and circuit <ul><li>&quot;Service Stratum&quot; for per-session control of packet transmission </li></ul><ul><li>Data is transmitted with IP packet for interoperability </li></ul><ul><li>All necessary functions are in the network (fat network approach) </li></ul><ul><ul><li>Operators can maintain every aspect of functions  increase reliability </li></ul></ul><ul><ul><li>All the terminals can do is just to call network’s functions  increase security </li></ul></ul><ul><ul><li>Control interface is open  promotes development of applications </li></ul></ul>NGN transport functions NGN service control functions Telephone Services Data Services (WWW, e-mail, etc) Video Services (TV, movie, etc) Internet Protocol (IP) Anything & Everything Everything (Any & All Network technologies) (Any/All Applications e.g. voice , data , video) Scope Of &quot;Internet&quot; &quot;Service Stratum&quot; (Session control by using SIP, etc.) &quot;Transport Stratum&quot; (managed IP network) ITU-T Y.2011 &quot;General principles and general reference model for Next Generation Networks&quot; Hourglass model of IP
  14. 14. 2. Standardization process
  15. 15. De jure standards v. De facto standards <ul><li>Open and fair process </li></ul><ul><li>Results are shared among all participants (usu. without charge) </li></ul><ul><li>Reflects broader opinions </li></ul>De jure standards <ul><li>Operated by highly motivated volunteers </li></ul><ul><li>Faster standardization </li></ul><ul><li>Currently very popular </li></ul>ITU, ISO, TTA, TTC, .. IETF, TMF, WiMAX, .. framework Individual components and technologies NGN framework includes regulations and policies (e.g., how to standardize emergency services, how to design market regulations considering network architecture)  De jure standards becomes important In NGN De facto standards
  16. 16. NGN related standard bodies ITU-T ETSI (EC) CCSA (China) TTA (Korea) APT (Asia Pacific) ATIS (USA) TIA (USA) ISACC (Canada) 3GPP TTC (Japan) ACIF (Aust) ARIB (Japan) 3GPP2 Close collaboration Regional De Jure SDOs & Partnership Projects TISPAN project standardize NGN, esp. VoIP. Release 1 issued in Dec. 2005. Standardize NGN in NGN-GSI, esp. SG13. Issued first recommendations in July 2006. De Facto SDOs IETF OMA WiMAX TMF aaa DSL Forum MSF … . SDO: Standard Development Organization International De Jure SDO Standardize IMS, NGN’s central module. Partnership Project among regional SDOs.
  17. 17. Timeline of NGN standardization NGN-JCA Focus Group IPTV NGN-GSI (Global Standards Initiative) Study Period 2005-2008 2004 2005 2006 2007 Study Period 2000-2004 ITU-T Focus Group NGN Collaboration among SG13,11,19 and other SGs Release 1 (architecture, VoIP) Release 2 (IPTV, FMC, etc.) (European NGN standards) Integrated in 2003 TIPHON SPAN ETSI (TISPAN) Release 1 (architecture, VoIP) Release 2 (IPTV, FMC, etc.) IMS based NGN architecture (3G mobile specs) 3GPP IMS Release6 IMS Release7 Collaboration on IMS (International NGN standards) We are here
  18. 18. Organization of ITU ITU-R ITU-T: Telecommunications ITU-D: developing country support ITU-R: Radio SG2 (numbering, etc.) SG4 (management) SG9 (cable net) SG15 (transport) SG17 (security & language) SG12 (QoS) SG3 (charging) SG5 (electromagnetic protection) SG6 (plant) SG11 (signaling) SG13 (NGN) SG16 (multimedia) SG19 (mobility) TSAG(steering) TSB (bureau) Q1 (project mngt) Q3 (func. architecture) Q6 (mobility & FMC) Q10 (satellite) Q12 (frame relay) Q8 (service & deployment) Q2 (requirements & scenarios) Q4 (QoS architecture) Q5 (net. management) Q7 (net. & service integration) Q9 (IPv6) Q11 (terminology) Q13 (public data net.) Q14 (multi service net.) Q15 (security) Q16 (commercial off-the shelf components ) NGN security requirements NGN authentication AAA Certificate management ITU Chair, vice chair Rapporteur, associate rapporteur editor Title:
  19. 19. ITU-T NGN standardization structure SG13 (NGN) 1. Planning and promotion of overall NGN standardization process (e.g., roadmap) 2. Development of core technology’s requirements that are used by other SGs to develop their recommendations (Stage 1) 3. Development of network architectures (Stage 2) SG11 Protocol and signaling (stage 3 ) SG19 Mobility SG 2 Numbering SG16 multimedia SG12 QoS SG4 Management SG17 Security and Languages Requirements OCAF-FG FG-IPTV FG(Focus Group) Special task force for particular areas NGN-GSI (Global Standards Initiative)
  20. 20. ITU-T NGN-GSI structure SG11 SG19 Other SGs SG13 Control and protocol Management Project management and scope Architecture Service Requirements, Capabilities and scenarios QoS and network capabilities Security NNAR (including ID) Charging Interwork and evolution Q1(WP1) 1 WP1/13 Q11(WP1) Q1(WP1) Q1 Q2 Q5 Topics Cooridnator 2 WP2/13 3 WP3/13 4 WP4/13 5 WP2/11 6 WP2/4 7 WP2/13 8 WP3/13 9 WP3/13 10 WP3/13 NNAR: Numbering, Naming, Addressing and Routing Q3(WP2) Q6(WP2) Q9(WP2) Q10(WP2) Q29/16 Q2(WP3) Q8(WP3) Q4(WP4) Q5(WP2) SG12 Q3(WP2) Q5(WP4) Q2 Q15(WP2) SG4 NGNMFG WP2/17 Q2(WP3) Q3 Q1/2 Q2(WP3) SG3 Q7(WP3) Working party chairman coordinates Question activities in 10 topics
  21. 21. ITU-T NGN Management standardization structure SG4 (Telecommunication Management) 1. Telecommunication service/networks/equipment management for NGN and other networks 2. Application and evolution of TMN framework 3. Test, measurement and other mngt-related issues Question 8 of SG4 Management framework of NGN (e.g., M.3060) SG13 NGN Requirements NGN Management Focus Group (Chair: Dave Sidor (Nortel), Vice Chair: Leen Mak (Lucent)) 1. Specifies NGN (esp. NGN Release 1) management related to FCAPS interfaces 2. Currently focusing on development and maintenance of NGN Management Specification Roadmap for Release 1 (maps existing/developing standards, analyses gaps, etc.) NGN-GSI (Global Standards Initiative) The roadmap of NGN Management FG is available at
  22. 22. 3. Important ITU-T NGN standards
  23. 23. ITU-T NGN Release1 Scope (Y.2000 supplement 1) Defines what is included in NGN Release 1 <ul><li>Network or Service provider selection </li></ul><ul><li>Prevention of unsolicited bulk telecommunications. </li></ul><ul><li>Malicious communication identification </li></ul><ul><li>User identifier presentation & privacy </li></ul><ul><li>Online services </li></ul><ul><li>Sensor Network services </li></ul><ul><li>Remote control/tele-action services </li></ul><ul><li>Broadcast Services </li></ul><ul><li>Hosted and transit services for enterprises </li></ul><ul><li>Information services </li></ul><ul><li>Location-based services </li></ul><ul><li>Presence and general notification services </li></ul><ul><li>3GPP Release 6 and 3GPP2 Release A OSA-based services </li></ul><ul><li>Virtual Private Network (VPN) services </li></ul><ul><li>Existing data services </li></ul><ul><li>Data retrieval services </li></ul>Data communication services <ul><li>Emergency Communications (including support of Early Warning): </li></ul><ul><li>Support for users with disabilities </li></ul><ul><li>Lawful Interception </li></ul><ul><li>Service unbundling </li></ul><ul><li>Number portability </li></ul>Public Interest Aspects <ul><li>Real-time Conversational Voice services </li></ul><ul><li>Messaging services </li></ul><ul><li>Push to talk over NGN (PoN) </li></ul><ul><li>Point-to-Point interactive multimedia services </li></ul><ul><li>Collaborative interactive communication services </li></ul><ul><li>Content delivery services </li></ul><ul><li>Push-based services </li></ul>Multimedia services <ul><li>Provides PSTN/ISDN equivalent services and interfaces on IP network infrastructure </li></ul>PSTN/ISDN Emulation services <ul><li>Provides PSTN/ISDN like services by using session control of IP networks </li></ul>PSTN/ISDN simulation services Service description Service Types
  24. 24. ITU-T NGN Release1 Requirements (Y.2201) (1/2) Defines requirements on these aspects (1/2) <ul><li>Management </li></ul><ul><li>Open service environment </li></ul><ul><ul><li>Service coordination </li></ul></ul><ul><ul><li>Interworking with service creation environments </li></ul></ul><ul><ul><li>Service discovery </li></ul></ul><ul><ul><li>Service registration </li></ul></ul><ul><ul><li>Development support </li></ul></ul><ul><li>Profile management </li></ul><ul><ul><li>User profile </li></ul></ul><ul><ul><li>Device profile </li></ul></ul><ul><li>Policy management </li></ul><ul><li>Service enablers </li></ul><ul><ul><li>Group management </li></ul></ul><ul><ul><li>Personal information management </li></ul></ul><ul><ul><li>Message handling </li></ul></ul><ul><ul><li>Multicast support </li></ul></ul><ul><ul><li>Presence </li></ul></ul><ul><ul><li>Location management </li></ul></ul><ul><ul><li>Push </li></ul></ul><ul><ul><li>Device management </li></ul></ul><ul><ul><li>Session handling </li></ul></ul><ul><ul><li>Web-based application support </li></ul></ul><ul><ul><li>Content processing </li></ul></ul><ul><ul><li>Data synchronization </li></ul></ul><ul><li>Numbering, naming and addressing </li></ul><ul><ul><li>General requirements for Numbering, Naming and Addressing </li></ul></ul><ul><ul><li>Numbering </li></ul></ul><ul><ul><li>Numbering, Naming and Addressing schemes </li></ul></ul><ul><ul><li>Name/Address resolution </li></ul></ul><ul><ul><li>Numbering, naming and addressing interworking </li></ul></ul><ul><li>Identification, authentication and authorization </li></ul><ul><ul><li>General requirements </li></ul></ul><ul><ul><li>Requirements for identification </li></ul></ul><ul><ul><li>Requirements for authentication </li></ul></ul><ul><ul><li>Requirements for authorization </li></ul></ul><ul><li>Security </li></ul><ul><li>Mobility management </li></ul><ul><li>OAM </li></ul><ul><ul><li>General OAM requirements </li></ul></ul><ul><li>Survivability </li></ul><ul><ul><li>Protection switching requirements </li></ul></ul><ul><ul><li>Rerouting requirements </li></ul></ul><ul><ul><li>Service resiliency requirements </li></ul></ul><ul><li>Transport connectivity </li></ul><ul><li>Communication modes </li></ul><ul><li>Media resource management </li></ul><ul><li>Codecs </li></ul><ul><li>Access network and network attachment </li></ul><ul><li>User networks </li></ul><ul><li>Interconnection, Interoperability and Interworking </li></ul><ul><ul><li>Interconnection </li></ul></ul><ul><ul><li>Interoperability </li></ul></ul><ul><ul><li>Interworking with non-NGN networks </li></ul></ul><ul><li>Routing </li></ul><ul><li>Quality of Service </li></ul><ul><ul><li>General QoS requirements </li></ul></ul><ul><ul><li>Network QoS classes </li></ul></ul><ul><ul><li>Service/Application Priority </li></ul></ul><ul><ul><li>QoS control </li></ul></ul><ul><ul><li>QoS Signalling </li></ul></ul><ul><ul><li>Performance measurement and management </li></ul></ul><ul><ul><li>Processing and traffic overload management </li></ul></ul><ul><li>Accounting and charging </li></ul>
  25. 25. ITU-T NGN Release1 Requirements (Y.2201) (2/2) <ul><li>NGN management capabilities shall support the aims of the NGN by: </li></ul><ul><li>1. Providing the ability to manage, through their complete life cycle, NGN components, both physical and logical. This includes resources in the transport stratum and the service stratum, access transport functions, interconnect components and user networks and terminals; </li></ul><ul><li>2. Providing the ability to manage NGN service components independently from the underlying NGN transport components and enabling organizations offering NGN services (potentially from different service providers) to build distinctive service offerings to customers; </li></ul><ul><li>3. Providing the management capabilities which enable organizations offering NGN services to offer users the ability to personalize user services and to create new services from NGN capabilities (potentially from different service providers); </li></ul><ul><li>(9 more requirements cont.) </li></ul>Defines requirements on these aspects (2/2) Requirements examples; on management 12 requirements are defined. Below are the first 3 <ul><li>PSTN/ISDN emulation and simulation </li></ul><ul><ul><li>PSTN/ISDN emulation requirements </li></ul></ul><ul><ul><li>PSTN/ISDN simulation requirements </li></ul></ul><ul><li>Public interest aspects </li></ul><ul><ul><li>Lawful interception </li></ul></ul><ul><ul><li>Malicious communication identification </li></ul></ul><ul><ul><li>Unsolicited bulk telecommunications </li></ul></ul><ul><ul><li>Emergency telecommunications </li></ul></ul><ul><ul><li>User identity presentation and privacy </li></ul></ul><ul><ul><li>Network or Service Provider selection </li></ul></ul><ul><ul><li>Users with disabilities </li></ul></ul><ul><ul><li>Number portability </li></ul></ul><ul><ul><li>Service unbundling </li></ul></ul><ul><li>Critical infrastructure protection </li></ul><ul><li>Non disclosure of information across NNI interfaces </li></ul><ul><li>Inter-provider exchange of user-related information </li></ul>
  26. 26. NGN functional architecture (Y.2012) <ul><li>Transport stratum for managed IP packet transfer, and Service stratum for session control and for additional services, are clearly separated. (Does not align with OSI model; e.g., transport stratum includes session) </li></ul><ul><li>Transport stratum: composed of Transport Function for IP packet transmission, NACF for user attachment (authentication, IP address assignment, etc.), and RACF for QoS </li></ul>From ITU-T Y.2012 (06/07) <ul><li>Service stratum: composed of SCF for IMS and PSTN/ISDN emulation, and support functions for developing applications </li></ul><ul><li>Terminal: for 3G terminals: IPv6, for traditional fixed-network terminals: IPv4 </li></ul><ul><li>3 rd Party applications for Open Mobile Alliance (OMA) works on Application Network Interface (ANI) </li></ul>NGN architecture overview Transport stratum Service stratum Management Functions A NI Transport Control Functions Network Attachment Control Functions Network Attachment Control Functions (NACF) NNI UNI Application Support Functions & Service Support Functions Applications Transport Functions End- User Functions Other Networks Service Control Functions (SCF) Transport User Profiles Control Media Management Resource and Admission Control Functions (RACF) Service User Service User Profiles T ransport User
  27. 27. Detailed functional architecture (Y.2012)
  28. 28. IMS (IP Multimedia Subsystem) overview <ul><li>Provides various SIP-based services </li></ul><ul><ul><li>Provides session control, charging, security functions </li></ul></ul><ul><ul><ul><li>Increase end-user’s experience by unifying registration, authentication and charging </li></ul></ul></ul><ul><ul><li>Provides interfaces to control transport functions </li></ul></ul><ul><ul><ul><li>QoS, media gateway, alignment of charging on transport functions and service functions </li></ul></ul></ul><ul><ul><li>Provides interfaces not only to operators, but 3 rd party application vendors </li></ul></ul><ul><li>Clearly defined SIP from operator’s point of view </li></ul><ul><ul><li>IETF SIP is not enough for network operators e.g., IETF SIP does not define the start and the end of charging </li></ul></ul><ul><li>ITU-T NGN refers 3GPP Release 7 IMS </li></ul>
  29. 29. IMS for NGN (Y.2021) <ul><li>CSCF (Call Session Control Function): SIP server, the core of this architecture. P-CSCF (Proxy CSCF) is a sip server that communicate with user terminals </li></ul><ul><li>Various functions are defined as the gateway to other networks </li></ul>
  30. 30. Per-session Resource and Admission Control Functions (Y.2111) <ul><li>End-user (terminal) requests SCF a session establishment </li></ul><ul><li>RACF manages the current network resources, and grant/reject the request to achieve QoS guarantee </li></ul><ul><ul><li>Relative QoS (e.g., diffserv’s CoS) is acceptable </li></ul></ul><ul><ul><li>Various message flow and protocols are defined, operators will choose </li></ul></ul><ul><li>ETSI NGN Release 1 defines RACF for access network only ITU-T defines core network RACF as well </li></ul>SCF SCF : Service Control Functions (IMS and PSTN/ISDN emulation function on IMS) RACF : Resource Admission Control Functions AP server SIP server … Access-RACF Resource control server PDF Core-RACF Resource control server PDF Access network (e.g, metro ethernet) Core networks (e.g., MPLS) Other NGN networks Session establish Request by SIP DIAMETER, etc.
  31. 31. Security Requirements (Y.2701) <ul><li>Border element on the edge protects inside NEs </li></ul><ul><ul><li>Security requirements are defined for outside NEs, inside NEs and Border Elements </li></ul></ul><ul><li>Does not define requirements on SIM </li></ul>CPE CPE-BE (home GW) Media BE Signaling BE NGN BE The Internet BE SIP server Various NEs OpS Other networks Trusted zone an NGN operator can trust Trust model
  32. 32. Session Border Controller (Y.2012 supplement 1) <ul><li>Defines S/BC functions for media path and signaling path </li></ul><ul><li>S/BC can be placed between any networks </li></ul><ul><li>This document is a supplement --- not mandatory </li></ul><ul><li>Traffic control for signalling messages </li></ul><ul><li>Authentication, Authorization, and Accounting (AAA) </li></ul><ul><li>Signalling protocol translation </li></ul><ul><li>Signalling protocol interworking </li></ul><ul><li>Session-based routing </li></ul><ul><li>DSP service control </li></ul><ul><li>End-user information hiding </li></ul><ul><li>Topology and infrastructure hiding </li></ul><ul><li>DoS protection </li></ul><ul><li>Signalling encryption and decryption </li></ul><ul><li>Support for ETS/TDR </li></ul><ul><li>Support for emergency calls </li></ul><ul><li>VPN bridging or mediation </li></ul><ul><li>Opening and closing of a pinhole (Firewall) </li></ul><ul><li>Policing and marking </li></ul><ul><li>Detection of inactivity </li></ul><ul><li>NAT and NAPT </li></ul><ul><li>Assisting remote NAT/NAPT traversal </li></ul><ul><li>Resource and admission control </li></ul><ul><li>IP payload processing </li></ul><ul><li>Performance measurement </li></ul><ul><li>Denial of service (DoS) detection and protection </li></ul><ul><li>Media encryption and decryption </li></ul><ul><li>Support for Emergency Telecommunications Service/Telecommunication for Disaster Relief (ETS/TDR) </li></ul><ul><li>Support for emergency calls </li></ul>Signaling path func. Media path func.
  33. 33. New services/capabilities discussed in ITU-T (1/2) Service Stratum Transport stratum End-user func. Other networks Management Applications UNI NGN <ul><li>Application </li></ul><ul><li>IPTV (-) </li></ul><ul><li>Multi-play by DSLAM (Poland) </li></ul><ul><li>UPT (C) </li></ul><ul><li>IMS based real-time conversation voice service (C) </li></ul><ul><li>Telematics (for ITS support) (K) </li></ul><ul><li>Service stratum related capabilities </li></ul><ul><li>Charging (K) </li></ul><ul><li>ID based applications (RFID support, etc.) (K) </li></ul><ul><li>Open service environment capabilities (K) </li></ul><ul><li>Web service based Convergence service (K) </li></ul><ul><li>Convergence terminals (K) </li></ul><ul><li>Transport stratum related capabilities </li></ul><ul><li>FMC (C) </li></ul><ul><li>VPN (K) </li></ul><ul><li>Multicast with MPLS-based QoS support (K) </li></ul><ul><li>Contents Conversion Service Scenario (K) </li></ul><ul><li>MPLS-based mobility and QoS (K) </li></ul>ANI (proposed country, K: Korea C: China)
  34. 34. New services/capabilities discussed in ITU-T (2/2) <ul><li>Service stratum related capabilities </li></ul><ul><ul><li>RFID; Describes RFID applications. Requirements for NGN will be added in the future </li></ul></ul><ul><ul><li>Open Service Environment Capabilities: Describes integrated ANI (application network interface) including 3GPP OSA. Requirements for NGN will be added in the future </li></ul></ul><ul><li>Transport stratum related capabilities </li></ul><ul><ul><li>FMC; documents on requirements, IMS-based architecture, Service scenario for NGN with PSTN-based access networks are under discussion </li></ul></ul><ul><ul><li>Multicast with MPLS-based QoS support: Requirements, architecture overview, information flow are under discussion </li></ul></ul><ul><li>Application related services </li></ul><ul><ul><li>IPTV discussion is moved to Focus Group on IPTV (~2006/07) </li></ul></ul><ul><li>Most new services are proposed by Korea and China in ITU-T </li></ul><ul><li># of experts are ITU-T is not enough, and most recommendations on these issues are not very mature </li></ul>
  35. 35. 4. NGN standardization in Japan
  36. 36. Structure of NGN Study/Standardization in Japan <ul><li>Next Generation IP Network Promotion Forum </li></ul><ul><li>Combines strength of operators, vendors, academies, domestic fora and application vendors to promote all-IP networks </li></ul><ul><li>Established in December 2005, 211 members (March 2006) </li></ul><ul><li>Promotes interoperability tests, demonstration experiment, information exchange as well as standardization based on R&D </li></ul><ul><li>Technological focus: QoS and function, dependability (security and safety), interoperability and interconnectivity </li></ul><ul><li>TTC (Telecommunication Technology Committee) </li></ul><ul><li>Develops NGN-related technical standards as a committee to establish telecommunication related standards and protocols </li></ul><ul><li>Created NGN architecture WG and NGN upstream SWG in April 2005 </li></ul><ul><li>Collaborates and contributes to ITU-T and various foreign fora such as 3GPP and 3GPP2 </li></ul>MIC (Ministry of Internal Affairs and Communications)
  37. 37. MIC-TTC coordination ITU-T Sectional Meeting NGN committee (SG11, SG13) NGN WG Leader: Prof. Koichi Asatani Leader: Naotaka Morita (NTT) Sub-leader: Hideaki Yamada (KDDI) Sub-leader: Takashi Egawa (NEC) 1. Ministry of Internal Affairs and Communications (Information and communication Technology Sub-counsil) Technical Assembly Strategy Committee 2. TTC NGN Architecture WG NGN upstream Sub-WG (SG13) Signaling WG Signaling upstream Sub-WG (SG11) Technical Study AG Global Collaboration AG NGN AG Leader: Naotaka Morita (NTT) Leader: Takuya Sawada (KDDI) Advisory Groups (AGs) CJK NGN-WG /w CCSA, TTA Integral operation Network Management Committee (SG4) Net. Management WG
  38. 38. Structure of Next Generation IP Network Promotion Forum Forum Chair: Tadao Saito (Prof. Emeritus, U-Tokyo) Vice-Chair: Ryuji Yamada (NTT) 、 Yasuhiko Ito (KDDI) Bureau (NiCT) Technology Group Chairman: Shigeki Goto (Waseda-U) R&D/Standardization Group Chair: Koichi Asatani (U-Kogakuin) Planning & Promotion Group Chair: Yuichi Matsushima (NiCT) <ul><li>Interconnectivity test planning, promotion and coordination, including the coordination with relevant fora </li></ul><ul><li>Studies regulatory issues of IP telephony, in particular QoS and functionality, safety and security, interconnectivity and interoperability as well as regulatory issues of other advanced services. Practices proving test, if necessary. </li></ul><ul><li>Promotes R&D and the standardization of its results by establishing basic strategies and promotion methods, and by practicing proving tests. R&D focuses not only on NGN R1&R2, but beyond R2. </li></ul><ul><li>Promotes deployment and information exchange of next generation IP networks. Publicize appropriate information through publications, symposiums and market promotions. Surveys domestic and international R&D trends. </li></ul>
  39. 40. Backup slides
  40. 41. ITU-T document list Experts agree that the document is mature Approved as ITU-T recommendation by Governments' voting TAP: 6~9 month for policy and regulation related recommendations AAP: 2 month for technical recommendations ITU-T recommendation approval process
  41. 42. ETSI TISPAN document list (1/5) - Status -           Pub : Published (before December 2005) -           App : Approved at TISPAN#9 (December 2005) -           AbC : Approval by correspondence after TISPAN#9 (deadline 20 January 2006) -           Plen: Approval expected at TISPAN#10 (February 2006) - Deliverable/Type of Document -           TR : ETSI Technical Report (enters the Publication process immediately after TISPAN approval) -           TS : ETSI Technical Specification (goes to Publication process immediately after TISPAN approval) -           ES : ETSI Standard (has to pass the Membership Approval Procedure before Publication) - Q.x/SG: identifies the Question in the SG Note: the &quot;Short title&quot; given is based on the Work Item title and is not the exact title of the ETSI TISPAN approved document.
  42. 43. ETSI TISPAN document list (2/5)
  43. 44. ETSI TISPAN document list (3/5)
  44. 45. ETSI TISPAN document list (4/5)
  45. 46. ETSI TISPAN document list (5/5)