"End-to-end Interoperability and Mobile Services"


Published on

"End-to-end Interoperability and Mobile Services" Presentation to the Chinese National Science Academy, January 2003.

Published in: Technology
  • 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

No notes for slide

"End-to-end Interoperability and Mobile Services"

  1. 1. End-to-End and Interoperability John Loughney Research Manager 8 January 20031 © NOKIA 2001 Competence_Area_Forums.ppt
  2. 2. Vision DSL Multi-radio mobile access GSM/GPRS Session mobility WLAN Access to SIP services WCDMA For phones, laptops and PDAs Same authentication Same end-to-end security Same applications Same service provider2 © NOKIA 2001 Competence_Area_Forums.ppt Same bill
  3. 3. Thriving vs. Withering Services • Other potental titles • Maximizing Service Potential Require Interoperability • New service take-off requires interoperability • Useful services require interoperability • Non-interoperability = withering service • Implications • Need large pool of potential users • Interoperability is key • User uncertainty of outcome is a problem. • No need to have group solutions at the beginning of the graph. • Simple services available to a large pool can create complex behaviors. • Interoperability with non-mobile devices • Network Layer Interoperability • Service Layer Interoperability3 © NOKIA 2001 Competence_Area_Forums.ppt
  4. 4. Global SMS Growth USA (AWS, Cingular, T-Mobile, Verizon) 1Q2002: 820 Million SMS’s 2Q2002: 1,600 Million SMSs The main reason behind the numbers is interoperability.4 © NOKIA 2001 Competence_Area_Forums.ppt
  5. 5. IP Building Blocks Are Needed • Trends • Initial implementations of IP support specific services • Soon multiple applications using IP stack (not at same time) • Multiple applications using IP stack concurrently • What is needed • IPv6 in every phone • Open API’s • Interoperability5 © NOKIA 2001 Competence_Area_Forums.ppt
  6. 6. How Data Services Can Fail • Mobile services should be: • Services on the move -> always on services – enables reachability • Person-to-person services • Service should be the same with or without operators • Radio Bearer Independent • But • Charging models may prevent service usage • Parallel services may not be possible initially, impacting usability • Implementations not supporting this • Interoperability issues • Need short period for any transition periods • Get majority of terminals supporting TCP/IP • Are walled-gardens needed to protect operators • Interoperability can be a revenue stream • What risks are there to Nokia if terminals are not interoperable?6 © NOKIA 2001 Competence_Area_Forums.ppt
  7. 7. Threats • Multiple technologies, multiple deployments create user & operator confusion. • Business model problems – Walled Gardens proliferate. • Incompatible IP versions • 3GPP uses IPv6 • 3GPP2 uses IPv4 • Interworking problem? • Incompatible SIP versions, may be related to business models • IETF SIP (i.e. – supported by Microsoft) • 3GPP SIP • 3GPP2 SIP • Many of these points are inter-related. • Market segmentation may lead to slow user pickup.7 © NOKIA 2001 Competence_Area_Forums.ppt
  8. 8. Data Revenues8 © NOKIA 2001 Competence_Area_Forums.ppt
  9. 9. UK WAP use: 340m pages / month • By ComputerWire • Posted: 31/10/2002 at 09:29 GMT • WAP mobile internet usage on the UKs networks topped 340 million page impressions in September, according to the Mobile Data Association. The figures may well come as surprise to WAP skeptics, who have largely viewed the technology as failing to inspire much consumer interest after its initial hype. • The MDA will report figures monthly on behalf of the UKs four GSM operators: Orange, O2, Vodafone and T-Mobile. It also plans to releases quarterly figures for the number of WAP-enabled handsets in circulation on the four networks.9 © NOKIA 2001 Competence_Area_Forums.ppt
  10. 10. 10 © NOKIA 2001 Competence_Area_Forums.ppt
  11. 11. Evolution to WAP 2.0 • Mobile browsing is based on WAP 2.0: TCP/IP and xHTML • xHTML provides fully graphical content presentation • TCP/IP creates discontinuity: Browsing and MMS require WAP gateway upgrade. • TCP/IP is important enabler for rich 2.5-3G multimedia services • Content handling framework, e.g. XHTML –> WML • TCP/IP enables higher bandwidth and max MMS message size • TCP/IP provides greater security e.g. for banking services • Nokia TCP/IP phones will be available worldwide 2Q/2003 • We can say that "We expect TCP/IP to happen end-to-end around mid-2003."11 © NOKIA 2001 Competence_Area_Forums.ppt
  12. 12. Why xHTML • WAP and W3C are collaborating on markup language convergence • Convergence platform is XHTML Basic • XHTML is next-generation version of HTML based on XML • Basic content can be shared across mobile phones, PDAs, desktop computers, TVs & pagers WML XML TV PC PDA ... WML XHTML Basic XML HTML12 © NOKIA 2001 Competence_Area_Forums.ppt
  13. 13. Conclusions Need interoperable services. • Enabling convergence will boost the Mobile Services business. • Technologies are available (IP, SIP) • Initially focus on enabling these technologies as opposed to finding the killer application or service. • Need IP stack in every phone -> TCP/IP is there, let’s use it But • Careful design to avoid incompatibility of different versions • IPv4/IPv6 • IMS-SIP, Internet SIP • How to execute IP connectivity over different bearers. • Allow different business models, but not with incompatibility.13 © NOKIA 2001 Competence_Area_Forums.ppt