70 likes | 231 Views
NGN : current and beyond. 21st CJK UNIOT -WG 20 11 .7 .11-13 TTC Yoshinori Goto(goto.yoshinori@lab.ntt.co.jp). NGN: current architecture. The current version of NGN architecture was published in April 2010. NGN: current status. NGN capability set 2 (Y.2007) covers 18 capabilities;
E N D
NGN : current and beyond 21st CJK UNIOT-WG 2011.7.11-13 TTC Yoshinori Goto(goto.yoshinori@lab.ntt.co.jp)
NGN: current architecture • The current version of NGN architecture was published in April 2010.
NGN: current status • NGN capability set 2 (Y.2007) covers 18 capabilities; • Transport connectivity, communication modes, transport network component, network attachment, IPv6, multicast, routing, QoS, identification/authentication/authorization, security, management, mobility management, codecs, operations/provisioning, interconnection/interworking, PSTN/ISDN emulation and simulation, IPTV (incl. QoE and security) and public interest • There would be unmet demands for future versions of NGN. • Because of this, SG13 is working on various new capabilities such as MCC, OSE/SIDE, USN, MOC, IOT, id-loc etc.
Items beyond current NGN • OSE/SIDE : OSE architecture was approved. SIDE architecture is being developed. Possible unification of OSE/SIDE will be considered. • Id-loc : Y.2022 (Y.FAid-loc-split) was consented. But neither Y.2007 nor Y.2012 covers this capability. In addition, network based scheme has not yet initiated. • RACF (Y.2111Rev2) : This revision tries to cover new capabilities such as interwork with non-NGN IP NW, 3GPP and 3GPPS, wholesale, time-shifted TV, QoS downgrading and IPTV service by invitation that are not fully considered in more general architecture. • DPI : Being discussed in Q17. • DSN : Being discussed in Q19. • IoT : IoT is in initial stage. • There are more,,,,
A new challenge for NGN • As NGN technologies become mature, the architecture becomes more complicate. • Inconsistent standard is no longer considered. • Consistency is a minimum requirement for standard (from industry viewpoint). • Checking consistency is a painful work. • Need to go through all the relevant outputs in detail. • Particularly, those who want to bring innovative ideas. • Spend a lot of time for this kind of useless debates,,,
SUN from NGN viewpoint • From discussion at NGN-GSI (TD741/NGN-GSI) • Beyond NGN • Succeeding some features of NGN, e.g. packet based network. • (Trying to) incorporate new features such as knowledgeable, context-aware, adaptable, autonomous and programmable. • Possible study approaches for SUN • SUN with alternative architecture: SUN is a different network architecture from NGN. • SUN as an evolution of NGN: NGN will evolve to SUN. • SUN as a collection of network technologies: SUN is not an architecture by itself. Alternative architecture? SUN SUN knowledgeable Context- aware Evolution ? autonomous adaptable NGN Collection of technologies?
Conclusions • The development of NGN is continued even after Y.2007 and Y.2012. • As NGN architecture becomes mature and complex, addition of new capabilities maintaining consistency is increasingly difficult. • We need a new way to avoid useless debates (to make everyone happy). • SUN as a separated concept from NGN could be a good vehicle for new ideas, although the basic concept is not fully agreed. • Some of current ongoing items for NGN could be considered as candidate items for SUN before incorporated in NGN.