Mobile Web Services T-110.456 Next Generation Cellular Networks 13.04.2005 Yrjö Raivio 28916V T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Contents • Motivation • Standardization bodies • Web Services Interoperability Organization (WS-I) • Web Services Discovery • Liberty Alliance Project • Drivers • Architecture • PAOS • Open Web Services Architecture • Examples • Conclusions T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Mobile Circle of Trust – Single Sign On T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Challenge with the Mobile Services Terminals xSP’s Mobile Operators Less services available. High integration cost for new xSP High integration costs for Lower value to the authentication, charging, to join operator portal. Less subscriber. personalization. revenue from services and traffic. Difficult to use services. Services not attractive to Lack of privacy. subscriber. Charging xSP 1 Presence, Location xSP 2 Fragmentation, Profile loss of mass- market appeal Messaging Application Authentication Development T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Solution: Web Services and Identity Management Terminals xSP’s Mobile Operators More value for the Easy integration. Easy for xSP to Easy integration. xSP more subscribers because more independent from operator. join operator portal. More services and better user Services more attractive revenue from services & traffic. experience. through single sign-on, Privacy protection. personalization, privacy. Charging xSP 1 Presence, Location xSP 2 Standard Profile WS (& IdM) Framework Messaging Application Authentication Development T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Next step: WEB services entering the phone Terminals xSP’s Mobile Operators Even more value for the Even more attractive subscriber/terminal services xSP 1 WS WS xSP 2 Framework Framework Application Development Web services T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Mobile Web Services Standardization bodies • W3C: XML, SOAP, WSDL • IETF: HTTP • OASIS: UDDI, WS-Security • WS-I: Interoperability of the basic functions • MS, IBM, Nokia • Liberty Alliance Project: • ID-FF, Identity Federation Framework • ID-SIS, Identity Service Interface Specifications • ID-WSF, Identity Web Services Framework • OMA/Mobile Web Services WG: Defines that the Mobile Web Services suit to the OMA Architecture • Java Community/J2ME Web Services - support for Java based mobile application development T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Web Services Interoperability Org. (WS-I) WS-I’s Work to Date Additional Management Portals Capabilities Business Process Composition/Orchestration Orchestration Composable Reliable Service WS-Security Transactionality Messaging Elements Messaging Endpoint Identification, Publish/Subscribe Description XML Schema, WSDL, UDDI, SOAP with Attachments Invocation XML, SOAP Transports HTTP, HTTPS, Others T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Web Services Discovery • Methods to find Web Services: • By being told about it out of band • Examples include obtaining the information from a service provider by e- mail, or by being dynamically informed about the service during an HTTP transaction (for example, by using the Liberty Reverse HTTP Binding for SOAP Specification) • Through a visit to a well-known location • Knowledge of this location can be, for example, shared out of band, discovered on a Web site, or shared as ‘metadata’ • By using a centralized directory, such as a UDDI (Universal Distribution, Discovery and Integration) directory • By using an identity-based discovery service • ID-WSF Discovery • How the service provider will find MY services such as Identity Provider, Payment, Messaging etc. T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Liberty Alliance Project • Need to be connected anytime, anyplace - without compromising security or control of personal information • Liberty Alliance provides the technology, knowledge and certifications to build identity into the foundation of mobile and Web-based communications • Not mobile specific but mobile aware • 150+ diverse member organizations, from banks to operators and service providers • Identity Management framework • To solve privacy issues • Link different identities (telco, internet) with each other • Authenticate and authorize transactions in non-trusted /unsecured environment • Facilitate easy of use-avoiding multiple registrations to services • Easy and standard interfacing to 3 rd parties using main stream Internet technologies (Web Services, XML/SOAP -> Liberty ID-FF/ID-WSF) T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Liberty Alliance Project - Architecture Liberty Identity Services Inter- Liberty Identity face Specifications (ID-SIS) Federation Framework (ID-FF) Enables interoperable identity services Security Assertion such as personal identity profile Markup Language (SAML) 2.0 service, contact book service, geo- location service, presence service etc. Enables identity federation and Liberty Identity Web Services management through features Framework (ID-WSF) such as Provides the framework for building • identity/account linkage interoperable identity services, permis- • simplified sign on sion based attribute sharing, identity • simple session management service description and discovery, and the associated security profiles. Liberty specifications build on existing standards (SAML, SOAP, WS-Security, XML, etc.) T-110.456 Next Generation Cellular Networks/13.04.2005/YR
PAOS – Reverse HTTP Binding for SOAP • Most devices equipped with HTTP client but not with HTTP server, like mobiles • However, mobile devices could offer valuable services to other parties, like calendar and profile service • Such services could be especially valuable when such devices interact with an HTTP-based server (or service) • When a user of a mobile terminal visits a web site, that web site could use some of the data from a personal profile service to personalize the offered content • The primary difference from the normal HTTP binding for SOAP is that here a SOAP request is bound to a HTTP response and vice versa • Hence the name Reversed HTTP binding for SOAP. The (informal) abbreviation for this binding specification is "PAOS" T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Personal Portal Service T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Open Web Services Architecture T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Operator control and Web Services • Today connections from the internet towards mobile devices or directly between them are blocked due to security risks and fear of losing control => Full utilization of WS not possible yet • Operators do not have any specific control points in the game, but they do have interesting data (location, profile, presence) and huge register base • Operators have not (yet) opened their services through WS IFs • Operators and banks are both interested about the Identity Provider (IDP) business; no common views, scattered solutions by operators, banks and governments • PAOS enables operator independent services but requires that terminal has the data! • Symbian terminals will soon have Web Services support T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Roles in the Service Business Web sites and Device roles: Applications roles: Service Web Service Consumers protocols Web Service Consumers Web Service Providers Web Service Mobile operator roles: Providers Web Service Provider Web Authentication Service Discovery Consumer Profile Location Charging Messaging Presence T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Examples • AOL developed Radio@AOL and Album@AOL services based on open WEB Services standards • Client can utilize platform WEB Services API’s • I.e. easier to develop • Less memory consumption • Amazon has opened WS API to their product catalogue • Piranha Java SW utilises this API and can check any product and price Amazon supports • Amazon gets 17% commission of 3rd party product turnover; 22% of Amazon incomes T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Demo: “WSP” on the mobile GPRS BT Pan Firewall Internet Gateway Web Server T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Conclusions • Mobile Web Services offer interesting opportunities for mobile service developers • Standardization setup is pretty complex, over engineered => de facto standards? • Banks and operators are competing with each other => scattered, nation wide identity solutions • Mobile operators have been too slow and have not utilized their strengths: Customer base, Trust, Authentication, Billing, Profile, Location, Messaging, Presence… • Open APIs needed – New business possibilities for all parties T-110.456 Next Generation Cellular Networks/13.04.2005/YR
Recommend
More recommend
