From Wireless Technologies to Mobile Services The Specifications Development in OMA

Transcription

1 From Wireless Technologies to Mobile Services The Specifications Development in OMA Wen-Pai Lu Presenting to IEEE SVC Comsoc Seminar January 14, 2004

2 Agenda Motivation OMA Mission and Objective OMA Organizations Mobile Web Service Working Group Enterprise BOF References Slide 2 IEEE SCV ComSoc January 14, 2004

3 Challenges The standard groups 3GPP and 3GPPs IEEE IETF Etc. Slow revenue on Mobile Data services for mobile operators Everyone in the value chain is frustrated operators, internet providers, software vendors, consumers/users The problem is much deeper than standards Slide 3 IEEE SCV ComSoc January 14, 2004

4 Changing Environment Most Standard groups do this all for Mobile Operators Services & Applications Infrastructure Core RAN Current mobile wireless market conditions are forcing 3GPP and 3GPP2 to actively seek applications, services, and Web/Internet pieces for their solutions from outside their respective organizations. Slide 4 IEEE SCV ComSoc January 14, 2004

5 What do we need? OASIS W3C MWIF Mobile Payment... Liberty Alliance Web Services & Applications Infrastructure Core RAN Internet Opening up the top of existing service and application layers architecture may offer significant value to the mobile Internet Slide 5 IEEE SCV ComSoc January 14, 2004

6 System Integration and Engineering Efforts System Integration Internet Systems Engineering Infrastructure Core RAN Telephony Slide 6 IEEE SCV ComSoc January 14, 2004

7 Motivation Wireless Application Protocol (WAP) Open Mobile Architecture Initiative November 2001 Key enablers to stimulate growth Opportunities for all players in the value chain to success operators, manufacturers, developers, IT companies, and consumers Needs for open standards, and seamless interoperability in the industry Proposed to develop open API s for tools and software Key Elements: Open application development environment Open terminal-network and client-server interfaces Open terminal architecture Open service platform architecture Slide 7 IEEE SCV ComSoc January 14, 2004

8 System Architecture Applications API Corporate or ASP Network Web Service Operator Networks Terminal Underlying Networking Technologies Slide 8 IEEE SCV ComSoc January 14, 2004

9 Open Mobile Alliance - OMA Formed in June 2002 First TP Meeting in Rome in August 2002 Consolidation of several foras WAP Forum Location Interoperability Forum (LIF) SyncML Initiative MMS-IOP (Multimedia Messaging Interoperability Process) Wireless Village Mobile Gaming Interoperability Forum (MGIF) Mobile Wireless Internet Forum (MWIF) More than 300 companies mobile operators, device vendors, network suppliers, IT companies, software developers, and content and service providers Slide 9 IEEE SCV ComSoc January 14, 2004

10 OMA Missions Mission To facilitate global user adoption of mobile data services by specifying market driven mobile service enablers that ensure service interoperability across devices, geographies, service providers, operators, and networks, while allowing businesses to compete through innovation and differentiation. Purpose To grow the market for the entire mobile industry by removing barriers to interoperability, supporting a seamless and easy to use mobile experience for users and a market environment that encourages competition through innovation and differentiation Slide 10 IEEE SCV ComSoc January 14, 2004

11 OMA Goals Goals Deliver high quality, open technical specifications based upon market requirements.. Ensure OMA service enabler specifications provide interoperability across different devices, geographies, service providers, operators, and networks,.. Be the catalyst for the consolidation of standards activity within the mobile data service industry,.. Provide value and benefits to members in OMA from all parts of the value chain.. Slide 11 IEEE SCV ComSoc January 14, 2004

12 OMA Organizations Board Technical Plenary Location Operations & Processes Requirements Browser & Content Messaging Release Planning & Management Architecture Device Management Mobile Commerce & Charging Security Data Synchronization Mobile Web Services Interoperability Games Services Presence & Availability Slide 12 IEEE SCV ComSoc January 14, 2004 Developers Interests Push to Talk Over Cellular

13 OMA Organizations - Missions Operations and Processes Provides support on operational and process activities Release Planning & Management Planning and managing OMA Releases, defining OMA Releases based on OMA specifications and Interoperability Testing programs, and defines the Release planning process Slide 13 IEEE SCV ComSoc January 14, 2004

14 OMA Organizations Missions (cont.) Requirements Specifies and identifies interoperability and usability requirements within OMA Working Groups Architecture Defines the overall OMA architecture, enabling specification work in work groups and assuring, through review, adherence of specification work to OMA architecture Security Develops secure communication protocols between mobile clients and servers at transport and application layers, security and trust services provided by/to mobile clients and servers Interoperability Acts as a center of excellence to identify, specify and maintain the required processes, policies and test programs for ensuring interoperability for OMA specified enablers and end-to-end services Slide 14 IEEE SCV ComSoc January 14, 2004

15 OMA Organizations Missions (cont.) Browser & Content Responsible for the specification of application technologies used in the open mobile architecture Data Synchronization (SyncML) Continues the work originated in the former SyncML Initiative. Develops specifications for data synchronization, and the development of other similar specifications, including but not limited to SyncML technology Developers Interests collects and publishes data relevant to developers, provides a means for software developers to articulate and specify their needs to OMA and identifies missing or inconsistent developer interfaces Device Management (WAP & SyncML) Defines management protocols and mechanisms that enable robust management of the life cycle of the device and its applications over a variety of bearers. Continue works from WAP and SyncML Slide 15 IEEE SCV ComSoc January 14, 2004

16 OMA Organizations Missions (cont.) Games Services (MGIF) Develops interoperability specifications, APIs and protocols for network enabled gaming, as well as, enabling game developers to develop and deploy mobile games to efficiently interoperate with OMA platforms and enable cost reduction for game developers, game platform owners and service providers. Continue works from MGIF Location (LIF) Develops specifications to ensure interoperability of Mobile Location Services on an end-to-end basis Messaging Responsible for the specification of messaging and related enabling technologies Slide 16 IEEE SCV ComSoc January 14, 2004

17 OMA Organizations Missions (cont.) Mobile Commerce and Charging Brings industry players (companies, forums, etc.) closer together to get a more coordinated effort on m-commerce and to provide an overall m-commerce industry perspective Mobile Web Services Responsible for developing a specification that defines the application of web services within the OMA architecture and ensure that the specification provides for the application of web services that is converged with the work of external activities Presence and Availability Specify the service enablers to permit the deployment of interoperable mobile presence and availability services Push to Talk over Cellular develop application enabling specifications to permit the deployment of interoperable PoC services Slide 17 IEEE SCV ComSoc January 14, 2004

18 Mobile Web Services (MWS) Working Group Provide specifications and guidelines for Web Services (WS) technologies, implementations and deployments to integrate and interoperate within the OMA architecture. Ensure interoperability across servers and terminals supporting web services protocols through the use of standardized protocols. Slide 18 IEEE SCV ComSoc January 14, 2004

19 Current Status - MWS Release 1 Documents Current Release Documents for Review OMA Web Service Enabler (OWSER): Overview This also serves as Architecture document OMA Web Service Enabler (OWSER): Core Specifications Define the technology used OMA Web Service Enabler (OWSER): Network Identity Specifications OMA Web Service Enabler (OWSER) Best Practices: WSDL Style Guide OMA MWS Requirements OMA MWS Network Identity Requirements Enabler Test Requirements (ETR) for OWSER Enabler Release Definition (ERELD) for OWSER Slide 19 IEEE SCV ComSoc January 14, 2004

20 Service Oriented Architecture (SOA) A underlying technology that forms the basis for the OMA Web Service Enabler (OWSER) Web Service Registry Find Publish Web Service Requester Bind Web Service Provider Slide 20 IEEE SCV ComSoc January 14, 2004

21 OMA Web Service Enabler (OWSER) The capabilities that are common across most Web Services within OMA. Enabler capabilities can be implemented in various ways involving WSRs, WSPs, Web Service intermediaries, or legacy elements. Designed to be extensible Leverages works within the broader industry where applicable Slide 21 IEEE SCV ComSoc January 14, 2004

22 OWSER Phase 1 Capabilities WSR authentication WSR authorization Message and data confidentiality Message and data integrity Service Registry Management WSP registration Web Service publication Web Service discovery Web Service binding Slide 22 IEEE SCV ComSoc January 14, 2004

23 OWSWE Protocol Architecture WS Messaging WS Description WS Discovery SAML WS Security Canonical XML XML Encryption XML Signature SOAP XML + Namespaces + Information Set WSDL XML Schema UDDI Search Register subscribe Envelop (MIME) Transfer (HTTP) Transport Security (SSL, TLS) Transport (TCP/IP) Slide 23 IEEE SCV ComSoc January 14, 2004

24 Security Considerations in MWS Threats to be protected Inappropriate content modification Denial of service Eavesdropping man-in-the-middle attack masquerade attack replay attack Trojan Horse Note: These threats are considered most relevant in the initial version of the OWSER. Additional threats will be identified and provided Security Services Authentication Data Confidentiality Data Integrity Access Control Non-repudiation Slide 24 IEEE SCV ComSoc January 14, 2004

25 Network Identity Management in MWS Focus on Principles, the end users/subscribers Federated Network Identity Federate various personas of an individual without compromise of privacy or loss of ownership of the associated data User Identity Federation A notion of trusted or third party Identity Provider Sharing of the authentication event by a trusted party Protocol for User Identity Federation Interaction between identity provider and service provider Service based on Federated Identity Single Sign On Single Sign Out Detailed Network Identity Specification: OMA-OWSER-Network_Identity-Specification-V1_ D Slide 25 IEEE SCV ComSoc January 14, 2004

26 How OWSER Works Scenario 1 Public UDDI Internet 1c Publication 1a Service Registry 2b Discovery 2a Service Provider Domain OMA SE 1b 3 Invocation WSR Application(s) Application Provider Domain Slide 26 IEEE SCV ComSoc January 14, 2004

27 How OWSER Works Scenario 2 Public UDDI Internet 1c Discovery 2a Service Registry 1b Publication 1a Service Provider Domain WSR Application(s) 2b 3 Invocation OMA SE Application Provider Domain Slide 27 IEEE SCV ComSoc January 14, 2004

28 How OWSER Works Scenario 3 Public UDDI Internet 1c 2b WSR Application(s) Discovery 2a Service Registry 1a 1b Publication Service Provider Domain 3 WSR Invocation OMA SE Slide 28 IEEE SCV ComSoc January 14, 2004

29 Architectural Model Limited Capability Stack Web Service Stack Mobile Device A Web Service Requester/Proxy B Non-Visible Intermediary Web Service Provider Out of Scope Release 1 In Scope Release 1 Indirect Model = Interface A + Interface B Direct Model = Interface B Slide 29 IEEE SCV ComSoc January 14, 2004

30 OMA Architecture WG User Service Provider Framework Account Management And billing S3-1 Service Provider S1 Service provider portal S3-2 SLA management S3-3 Capability registry S2 Session Management Security Framework A1-1 Run time Framework U1 App App Presentation App Presentation Presentation Logic Logic Logic Application logic Transaction management Transport F1 Session Management A1-2 Content repurposing Capability exposure function Capability Capability Presentations Capability Presentations Presentations App Env Data sources resilience G1-1 G1-2 G1-3 G2-1 G2-2 OSS Service Provider Profiles Common Capabilities Slide 30 IEEE SCV ComSoc January 14, 2004

31 Enterprise OMA Concerns Service Provider centric Enterprise users have different needs from providers, IT vendors as well as consumers that create huge challenges Enterprise can create huge mobile market opportunity that will be significant for everyone Enterprise IT would adopt early if data solutions readily integrate into current IT environments Enterprise IT could help broaden & further accelerate mobile data adoption Slide 31 IEEE SCV ComSoc January 14, 2004

32 Enterprise BOF Scope of BOF Identifying and analyzing the challenges met today by enterprise when mobilizing their existing and new applications Providing technical recommendations to address these challenges: Through recommendations for ongoing and future OMA activities By providing a gap analysis on existing OMA enablers By proposing new enablers Through guidelines for the mobile industry Slide 32 IEEE SCV ComSoc January 14, 2004

33 Conclusion OMA is becoming the driver for mobile applications (service providers as well as enterprises) Most of the current specifications are the productions of previous foras MWS produces the first OMA documentations Applications focus will be more than just data e.g., Push to talk WG Slide 33 IEEE SCV ComSoc January 14, 2004

34 References Open Mobile Alliance Main Site Enabler Release Definition Enabler Test Requirement Overview Core Specification Network Identity Specification Best Practice: WSDL Style Guide Requirements Network Identity Requirements Requirements Review Report Network Review Requirements Review Report Architecture Review Report Slide 34 IEEE SCV ComSoc January 14, 2004

35 Slide 35 IEEE SCV ComSoc January 14, 2004