The Need of SDO Collaboration as an Enabler of SOA in NGN

2. 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

3. Outline • A Brief Overview of NGN • SOA/Web Services in NGN • Standardization Bodies • ITU-T OASIS Collaboration • Q&A

4. New World, Rules, Players, Opportunities Fundamental Disruptions Are Transforming Today’s Telecom Industry

5. The Multimedia Experience Security & Personalization The Freedomof Mobility What People Value A Next-Generation Network is Essential

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

7. Moving to Next-Generation Networks Today Tomorrow User Complexity User Simplification Intelligent, Enabled Next-Generation Network Simple Networks Personal … Mobile … Secure Communications

8. Pre-NGN Video Services (TV, movie, etc) Telephone Services Data Services (WWW, e-mail, etc) Video Services Network Telephone Services Network Data Services Network Services Transport Access NGN Internet Protocol Source: ITU-T Rapporteur NGN Based on ITU-T Y.2011 Vertical Regulation and Policy NGN Features and Policy Impacts • Packet-based network with QoS supportand 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 QoS • 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

9. Application Servers Application Servers Intelligent Infrastructure CSCF/SCM Call Server Call Server PDF PDF Internet Intranet Internet Intranet HLR/HSS Internet Intranet HLR/HSS Call Server MGCF Call Server MGCF Call Server MGCF GGSN PDG PDG MGW MGW Application Servers PDSN PDSN HA GGSN PSTN PDG MGW PDSN HA PSTN SGSN R4 BICN PSTN Call Server Call Server PDF Internet Intranet Internet Intranet SGSN HLR/HSS GSM UMTS WLAN DSL/Cable CDMA R4 BICN Call Server MGCF Call Server MGCF GGSN PDG PDG MGW MGW PDSN PDSN HA WLAN GSM UMTS DSL/Cable PSTN CDMA PSTN SGSN R4 BICN GSM UMTS WLAN DSL/Cable CDMA Convergence Infrastructure Convergence is in the Customer Services Architectural

10. 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

11. NGN Revisited • NGN is the Internet (Plus QoS) • QoS 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 VoIP? Is it a service or just another application? • All IP, SIP based communications • NGN main addressing scheme is a SIP address, User-Name@Provider-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

12. 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 (SG17) • Identity Management (No need to re-invent: SAML?) • OCAF model and components (OCAF Focus Group->new Q16/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

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

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

15. Standarization Landscape • International • ISO, IEC, WSC; ISO/IEC JTC1 • Regional • ATIS, TIA, TSACC, TTA, TTC, ARIB,CCSA, ETSI, ACIF, GSC • Internet • IETF, ISOC, ICANN • Forums Consortia • IEEE, 3GPPs, ATM, MPLS/FR, MEF, TMF • Regional Telecom Organization • APT, ATU, CITEL, RCC, CEPT, ETNO, • What is OASIS Role?

16. 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. Closing questions

18. Acknowledgment • Some slides came from my colleagues Marco Carugi and Sergio Fiszman. • Some material came from ITU-T SG 13 site