Скачать презентацию 1 The Need of SDO Collaboration as Скачать презентацию 1 The Need of SDO Collaboration as

a8b002f9fbcbcff29b36926c587e7919.ppt

  • Количество слайдов: 19

1 1

The Need of SDO Collaboration as an Enabler of SOA in NGN Abbie Barbir, The Need of SDO Collaboration as an Enabler of SOA in NGN Abbie Barbir, Ph. D. Senior Advisor Strategic Standards Group Ottawa November 29, 2006 2

Outline § A Brief Overview of NGN § SOA/Web Services in NGN § Standardization Outline § A Brief Overview of NGN § SOA/Web Services in NGN § Standardization Bodies § ITU-T OASIS Collaboration § Q&A 3 © 2006 Nortel Networks. All Rights Reserved

Fundamental Disruptions Are Transforming Today’s Telecom Industry New World, Rules, Players, Opportunities 4 © Fundamental Disruptions Are Transforming Today’s Telecom Industry New World, Rules, Players, Opportunities 4 © 2006 Nortel Networks. All Rights Reserved

What People Value The Multimedia Experience Security & Personalization A Next-Generation Network is Essential What People Value The Multimedia Experience Security & Personalization A Next-Generation Network is Essential 5 © 2006 Nortel Networks. All Rights Reserved The Freedom of Mobility

Telecom Evolution Enterprise-Driven Consumer-Driven Hardware-Centric Software-Centric Broadband Wireline Broadband Wireless People to People Machine Telecom Evolution Enterprise-Driven Consumer-Driven Hardware-Centric Software-Centric Broadband Wireline Broadband Wireless People to People Machine to Machine Peripheral Security Embedded Proprietary Open (hardware & software) 6 Everything On Line, Simple, Intuitive, Secure © 2006 Nortel Networks. All Rights Reserved Trusted

Moving to Next-Generation Networks Today Tomorrow User Complexity Simple Networks 7 User Simplification Intelligent, Moving to Next-Generation Networks Today Tomorrow User Complexity Simple Networks 7 User Simplification Intelligent, Enabled Next-Generation Network Personal … Mobile … Secure Communications © 2006 Nortel Networks. All Rights Reserved

NGN Features and Policy Impacts § § Packet-based network with Qo. S support and NGN Features and Policy Impacts § § Packet-based network with Qo. S support and Security Separation between Services and Transport § Inter-working with legacy networks via open interfaces Access can be provided using many underlying technologies § Should be reflected in policy Decoupling of service provision from network Support wide range of services/applications § Converged services between Fixed/Mobile Broadband capabilities with end-to-end Qo. S Compliant with regulatory requirements § Emergency communications, security, privacy, lawful interception § ENUM Resources, Domain Names/ Internet Addresses § § § • Regularity Impacts ØRegulation ØTariff ØEmergency Services ØLegal Intercept ØIdentity ØDRM Pre-NGN Video Services (TV, movie, etc) Telephone Services Data Services (WWW, e-mail, etc) Services NGN Video Services Network Telephone Services Network Vertical Regulation and Policy 8 Data Services Network Transport Access Source: ITU-T Rapporteur NGN Based on ITU-T Y. 2011 Internet Protocol

Convergence Infrastructure Services HLR/ HSS Call Server HLR/ HSS MGCF Call Server MGCF MGW Convergence Infrastructure Services HLR/ HSS Call Server HLR/ HSS MGCF Call Server MGCF MGW Application Servers Intelligent Application Servers CSCF/SCM Infrastructure Application Servers PDF Internet Intranet PDF GGSN PSTN PDSN PSTN R 4 BICN Architectural GSM Internet Intranet Call Server MGCF PDSN PDG MGW HA SGSN UMTS CDMA GSM © 2006 Nortel Networks. All Rights Reserved PDG PDSN HA Convergence is in the Customer 9 Call Server PSTN WLAN DSL/Cable UMTS CDMA WLAN DSL/Cable

Requirements of Service Architecture • Everyone wants security from malicious attack • Service Providers Requirements of Service Architecture • Everyone wants security from malicious attack • Service Providers want: • Open service creation • One service infrastructure • Stickiness with Users • Performance against SLAs • Users want • Control of one set of services available everywhere • Choice of services from multiple sources • Performance guarantees / One number to call for support • Immediate activation / One bill to pay • Service Developers want a convenient level of abstraction • SOA/Web Services can play a lead role • Service Transporters want a slice of revenue for the services transiting their network (e. g. , roaming agreements for services) • Brokers will emerge to simplify life for Developers and Sellers 10 © 2006 Nortel Networks. All Rights Reserved

NGN Revisited § NGN is the Internet (Plus Qo. S) § Qo. S as NGN Revisited § NGN is the Internet (Plus Qo. S) § Qo. S as a differentiator depends on available Bandwidth § E. 164 numbering plan remains from old PSTN § No more central control § Wall green approaches will not work Based on end-to-end principle • Users reach other users via the IP address • Services can be offered anywhere and can be accessed from everywhere • What about Vo. IP? Is it a service or just another application? All IP, SIP based communications § NGN main addressing scheme is a SIP address, [email protected] Domain Services are performed at the edge (No Central Intelligence) § DNS is the only centralized resource on the Internet Possible customer services in an NGN context § Digital Identity § Terminals § Location and Presence § Addressing and Numbering § Biggest regulatory battle Digital Rights Management SOA/Web Services are good architectural fit if NGN to deliver on its promise § § § 11 © 2006 Nortel Networks. All Rights Reserved

Opening NGN: An essential topic going forward • How to open • Service Oriented Opening NGN: An essential topic going forward • How to open • Service Oriented Architecture (SOA) as framework ? • Web Services as implementation tool set ? • What to open/expose • Network capabilities <-> Applications ? • Network capabilities <-> Network capabilities ? • Various related work items in ITU-T NGN GSI • Open Service Environment capabilities • Web Services - scenarios, security (SG 17) • Identity Management (No need to re-invent: SAML? ) • OCAF model and components (OCAF Focus Group->new Q 16/13) • Relationships with other SDOs to be developed • OMA, OASIS, WS-I, Parlay, DMTF, … • A lot of interest in the market • Service Delivery Platforms, Middleware 12 © 2006 Nortel Networks. All Rights Reserved

People have multiple identities, each within a specific context or domain Work – me@company. People have multiple identities, each within a specific context or domain Work – [email protected] com Family – [email protected] family Hobby – [email protected] team Volunteer – [email protected] org Collaboration Identity Connecting users with services and with others (Federation) PC PDA Video Voice Telephony Smart Phone Whatever you’re using (devices) Cellular Whatever you’re doing (applications) Email Web Apps ERP Wherever you are At your Desk On the Road Managed Office At Home 14 • • In the Air (across various access types) In Town Network Identity is essential Need end-to-end trust model (SIP+SOAP) © 2006 Nortel Networks. All Rights Reserved

Standards Evolution National & Regional Global Competing Organizations Collaborating Vertically Integrated Horizontal, COTS, Open Standards Evolution National & Regional Global Competing Organizations Collaborating Vertically Integrated Horizontal, COTS, Open Source Long Development Time Short Development Time New forum per technology Merged / Integrated under SDO Tech-Specific Spectrum Tech & Service Neutral Spectrum 15 Everything On Line, Global, Horizontal, Open © 2006 Nortel Networks. All Rights Reserved

Standarization Landscape § International § ISO, IEC, WSC; ISO/IEC JTC 1 § Regional § Standarization Landscape § International § ISO, IEC, WSC; ISO/IEC JTC 1 § Regional § ATIS, TIA, TSACC, TTA, TTC, ARIB, CCSA, ETSI, ACIF, GSC § Internet § IETF, ISOC, ICANN § Forums Consortia § IEEE, 3 GPPs, ATM, MPLS/FR, MEF, TMF § Regional Telecom Organization § APT, ATU, CITEL, RCC, CEPT, ETNO, § What is OASIS Role? 16 © 2006 Nortel Networks. All Rights Reserved

ITU-T and OASIS Possible Collaboration § SOA/Web Services Security § Need a SOA Reference ITU-T and OASIS Possible Collaboration § SOA/Web Services Security § Need a SOA Reference Model (OASIS SOA-RM? ) § Important to use one Web Services protocol stack § Many contributions on Web Services Gateways for NGN/Mobility § Easier to bypass an OASIS specification than to bypass an ITU-T Recommendation § Can and will lead to a parallel stack § In Identity Management space, already seeing evidence of proprietary solutions that do not even consider SAML or any of the WS-Stack § Need to ensure that NGN use the same Web Services stack § There is a need of having WS-Security as an ITU-T Recommendation § Same like SAML (ITU-T X. 1141) and XACML (ITU-T X. 1142) § There is also a need for Interoperability § WS-I Basic Profile (BP) and Basic Security Profile (BSP) § Even if WS-I is dead, profiles are still viable (or not? ) § This is a golden time for OASIS and ITU-T to work together on the SOA/Web Services front 17 © 2006 Nortel Networks. All Rights Reserved

Closing questions 18 © 2006 Nortel Networks. All Rights Reserved Closing questions 18 © 2006 Nortel Networks. All Rights Reserved

Acknowledgment • • Some slides came from my colleagues Marco Carugi and Sergio Fiszman. Acknowledgment • • Some slides came from my colleagues Marco Carugi and Sergio Fiszman. Some material came from ITU-T SG 13 site 19 © 2006 Nortel Networks. All Rights Reserved

20 20