BarbirThe Need of SDO Collaboration as an Enabler of SOA in NGN
-
Upload
abbie-barbir -
Category
Technology
-
view
703 -
download
1
description
Transcript of BarbirThe 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© 2006 Nortel Networks. All Rights Reserved
Outline
A Brief Overview of NGN
SOA/Web Services in NGN
Standardization Bodies
ITU-T OASIS Collaboration
Q&A
4© 2006 Nortel Networks. All Rights Reserved
Fundamental Disruptions Are Transforming Today’s Telecom Industry
New World, Rules, Players, OpportunitiesNew World, Rules, Players, Opportunities
5© 2006 Nortel Networks. All Rights Reserved
What People Value
The MultimediaExperience
Security &Personalization
The Freedomof Mobility
A Next-Generation Network is EssentialA Next-Generation Network is Essential
6© 2006 Nortel Networks. All Rights Reserved
Enterprise-Driven
Hardware-Centric
Broadband Wireline
People to People
Peripheral Security
Proprietary
Telecom Evolution
Trusted
Everything On Line, Simple, Intuitive, Secure
Consumer-Driven
Software-Centric
Broadband Wireless
Machine to Machine
Embedded
Open (hardware & software)
7© 2006 Nortel Networks. All Rights Reserved
Personal … Mobile … Secure CommunicationsPersonal … Mobile … Secure Communications
Moving to Next-Generation Networks
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
TelephoneServices
DataServices (WWW,
e-mail, etc)
Video Services
(TV, movie, etc)
TelephoneServicesNetwork
DataServicesNetwork
Pre-NGN
VideoServicesNetwork
NGN
Vertical Regulation and Policy
Source: ITU-T Rapporteur NGNBased on ITU-T Y.2011
Access
Transport
Services Internet Protocol
• Regularity ImpactsRegulationTariffEmergency
ServicesLegal InterceptIdentityDRM
9© 2006 Nortel Networks. All Rights Reserved
Convergence
Architectural
Services
Infrastructure
Internet Intranet
Application Servers
CDMAGSM UMTS WLAN DSL/Cable
GGSN
PDFHLR/HSS
SGSN
PDSNMGW
PSTN
Call ServerMGCF
HAPDG
CSCF/SCM
Intelligent Infrastructure
R4 BICN
Application Servers
Internet Intranet
CDMAGSM UMTS
GGSN
PDFHLR/HSS
SGSN
PDSNMGW
PSTN
Call ServerMGCF
HA
PDG
Call Server
R4 BICN
Internet Intranet
WLANDSL/Cable
PDSNMGW
PSTN
Call ServerMGCF
PDG
Call Server
Internet Intranet
CDMAGSM UMTS
GGSN
PDFHLR/HSS
SGSN
PDSNMGW
PSTN
Call ServerMGCF
HA
PDG
Call Server
R4 BICN
Internet Intranet
WLANDSL/Cable
PDSNMGW
PSTN
Call ServerMGCF
PDG
Call Server
Application Servers
Convergence is in the Customer
10© 2006 Nortel Networks. All Rights Reserved
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© 2006 Nortel Networks. All Rights Reserved
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© 2006 Nortel Networks. All Rights Reserved
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
14© 2006 Nortel Networks. All Rights Reserved
IdentityConnecting users with services and with others (Federation)
At your Desk
Managed Office
Whatever you’re doing(applications)
In the Air
On the Road
Collaboration
Voice Telephony
ERP
In Town
PDA
Cellular
Smart Phone
Wherever you are(across various access types)
Whatever you’re using(devices)
At Home
Video
Web Apps
People have multiple identities, each within a specific context or domain
Work – [email protected] – [email protected] – [email protected] – [email protected]
• Network Identity is essential• Need end-to-end trust model (SIP+SOAP)
PC
15© 2006 Nortel Networks. All Rights Reserved
National & Regional
Competing Organizations
Vertically Integrated
Long Development Time
New forum per technology
Tech-Specific Spectrum
Standards Evolution
Global
Collaborating
Horizontal, COTS, Open Source
Short Development Time
Merged / Integrated under SDO
Tech & Service Neutral
Spectrum
Everything On Line, Global, Horizontal, Open
16© 2006 Nortel Networks. All Rights Reserved
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?
17© 2006 Nortel Networks. All Rights Reserved
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© 2006 Nortel Networks. All Rights Reserved
Closing questions
19© 2006 Nortel Networks. All Rights Reserved
Acknowledgment
• Some slides came from my colleagues Marco Carugi and Sergio Fiszman.• Some material came from ITU-T SG 13 site