Your SlideShare is downloading. ×
BarbirThe Need of SDO Collaboration as an Enabler of SOA in NGN
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

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


Published on

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

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

Published in: Technology, Business

  • 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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1.  
  • 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. Fundamental Disruptions Are Transforming Today’s Telecom Industry New World, Rules, Players, Opportunities
  • 5. What People Value A Next-Generation Network is Essential The Multimedia Experience Security & Personalization The Freedom of Mobility
  • 6. Telecom Evolution Enterprise-Driven Hardware-Centric Broadband Wireline People to People Peripheral Security Proprietary Trusted Everything On Line, Simple, Intuitive, Secure Consumer-Driven Software-Centric Broadband Wireless Machine to Machine Embedded Open (hardware & software)
  • 7. Moving to Next-Generation Networks Personal … Mobile … Secure Communications Simple Networks Intelligent, Enabled Next-Generation Network User Complexity User Simplification Today Tomorrow
  • 8. NGN Features and Policy Impacts
    • Packet-based network with QoS 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 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
    Telephone Services Data Services (WWW, e-mail, etc) Video Services (TV, movie, etc) Telephone Services Network Data Services Network Pre-NGN Video Services Network NGN Vertical Regulation and Policy Source: ITU-T Rapporteur NGN Based on ITU-T Y.2011 Access Transport Services Internet Protocol
  • 9. Convergence
    • Convergence is in the Customer
    Architectural Services Infrastructure Internet Intranet Application Servers CDMA GSM UMTS WLAN DSL/Cable GGSN PDF HLR/HSS SGSN PDSN MGW PSTN Call Server MGCF HA PDG CSCF/SCM Intelligent Infrastructure R4 BICN Application Servers Internet Intranet CDMA GSM UMTS GGSN PDF HLR/HSS SGSN PDSN MGW PSTN Call Server MGCF HA PDG Call Server R4 BICN Internet Intranet WLAN DSL/Cable PDSN MGW PSTN Call Server MGCF PDG Call Server Internet Intranet CDMA GSM UMTS GGSN PDF HLR/HSS SGSN PDSN MGW PSTN Call Server MGCF HA PDG Call Server R4 BICN Internet Intranet WLAN DSL/Cable PDSN MGW PSTN Call Server MGCF PDG Call Server Application Servers
  • 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. Capabilities for NGN Open Service Environment
    • General requirements
      • Independence from network providers and manufacturers
      • Location, Network and Protocol transparency
      • Secure access to capabilities
    • Service coordination
      • Coordination with applications, tracking of capabilities, availability of capability state change information (role of BPEL?)
    • Service discovery
      • Scalable and secure User/Device-interest service discovery (UDDI)
    • Service registration
      • Features for registration of capabilities in directories accessible by other capabilities and applications
    • Development support
      • To construct, trial, deploy and remove applications
      • Component reusability, mixing-and-matching, life cycle support, dependency tracking, delivery-agnostic design
    • Interworking with service creation environments
  • 14. Identity Connecting users with services and with others (Federation) Whatever you’re doing (applications) Email Collaboration Voice Telephony ERP Smart Phone Wherever you are (across various access types) Whatever you’re using (devices) Video Web Apps
    • People have multiple identities, each within a specific context or domain
      • Work –
      • Family –
      • Hobby –
      • Volunteer –
    • Network Identity is essential
    • Need end-to-end trust model (SIP+SOAP)
    PC At your Desk Managed Office In the Air On the Road In Town PDA Cellular At Home
  • 15. 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
  • 16. Standarization Landscape
    • International
    • Regional
    • Internet
    • Forums Consortia
    • Regional Telecom Organization
    • What is OASIS Role?
  • 17. 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
  • 18. Closing questions
  • 19. Acknowledgment
    • Some slides came from my colleagues Marco Carugi and Sergio Fiszman.
    • Some material came from ITU-T SG 13 site
  • 20.