1 / 83

Mobile Applications and Services FALL 2011 - Mobile Platform Landscape -

fraley
Download Presentation

Mobile Applications and Services FALL 2011 - Mobile Platform Landscape -

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Navid Nikaein Mobile Communication Department Mobile Applications and Services FALL 2011 - Mobile Platform Landscape -

    2. Early Stage ©Navid Nikaein 2011 2

    3. Take-along Telephone back in 1973 ! ©Navid Nikaein 2011 3

    4. Wireless Evolution ©Navid Nikaein 2011 4

    5. Landscape of Mobile Platforms Mobile Internet/Web: A Little bit of history Wireless Evolution Mobile platform run time environment Implication of technology evolution Mobile OS App stores ©Navid Nikaein 2011 5

    6. Mobile Internet : A little bit of history ©Navid Nikaein 2011 6

    7. From PDA to Smartphone Apple Newton : 1st PDA introduced in 1992 Personal data management and personal productivity applications No phone capability Offline and regular synchronization/backup as the initial model Online (or at least occasional online) went through several stages: dial-up services (modem) for Internet connectivity IrDA for synchronization with other devices Bluetooth for synchronization with other devices cell phone data services (GPRS, EDGE, 3G, 3G+) as advanced dial-up Wi-Fi for using hotspots and home/office networks Smartphone seems to be the new term for PDA Advanced computing ability and connectivity than that of a contemporary basic featured phone Runs a complete OS SDK platform for application developments 7 ©Navid Nikaein 2011

    8. Limited on-line Access Objectives User : Easily enjoy Internet services on mobile phone Operators: A way to attract new users and increase revenue (per-packet billing) Combining access, content and service within operators’ domain Attractive in early stages and for several reasons Easier to implement and control Easier to develop market models However, often have a limited life-span Content and service maintenance is very expensive Content and service are operator-dependent (user may leave) Content and real world disconnection Example iMode WAP 1.x and WAP2.x (wireless application protocol) 8 ©Navid Nikaein 2011

    9. iMode Mobile internet platform Mixing access, content, and service Developped and deployed by DoCoMo 9 ©Navid Nikaein 2011

    10. iMode Successful in Japan not only for market but also for social reasons talking on the phone in the public is frowned data-oriented services (chatting, messaging) are important No other mobile operator was able to establish a working market Leverage Internet technologies (packet-switched ) IP, TCP, HTTP, java, ssl Micro web browser Compact HTML (cHTML), which is a subset of HTML Example in France Vodofone Live (J-Phone/J-Sky) by SFR and ORANGE iMode for Bouygues Télécom 10 ©Navid Nikaein 2011

    11. WAP Internet content and advanced data services on wireless clients no content landscape/environment as in iMode WAP started with zero content ! Designed for micro browsers Works across all wireless network technologies Standardized by the WAP Forum (founded in 1997 by Ericsson, Motorola, Nokia, and others) The WAP specification includes the following: WML (extended subset of HTML) WMLScript (incompatible with JavaScript) WBXML (binary encoding of XML) WBMP (derived from PNG but incompatible) Communication protocols (WCMP, WDP, WTP) New specifications for almost any Web standard ! 11 ©Navid Nikaein 2011

    12. WAP Protocol Stack 12 ©Navid Nikaein 2011

    13. WAP Three elements Clients Gateways or proxy Origin servers WAP Proxy Protocol Conversion: translate WAP protocols to standard-protocols Content encoding/decoding: offload processing activities for the mobile devices manage user profile (capabilities and preferences ) Caching DNS service 13 ©Navid Nikaein 2011

    14. Mobile Web Constant online access to the Internet from a mobile device /tablet Internet-connected applications, Browser-based access In 2008, mobile access to the Internet exceeded desktop computer-based access for the first time (ITU) Mobile web primarily make use of lightweight pages cHTML WML xHTML Many new mobile browsers are moving beyond these limitations by supporting range of web format e.g. HTML and CSS Interoperability issues due to platform fragmentation Mobile device Mobile OS Browsers 14 ©Navid Nikaein 2011

    15. System Evolution ©Navid Nikaein 2010 15

    16. Mobile Phone/Smartphone technologies Mobile/Cell phone technologies GSM as the main technology in Europe and everywhere else CDMA as the main technology in the U.S. 3G/3G+ for faster speeds (W-CDMA/UMTS/HSPA or CDMA2000) 4G for equivalent speed as the fast Ethernet (OFDMA/LTE) Several sub-technologies and sub-generations developed GPRS for GSM networks (often referred to as 2.5G) EDGE for GSM networks (often referred to as 2.75G) EV-DO for CDMA2000 networks Devices often are limited to one family of standards iPhone started as a GSM phone, now 3G/Wifi Kindle started with EV-DO and now 3G/Wifi for 150€ ! ©Navid Nikaein 2010 16

    17. Cellular Networks Cell sizes vary between 1 km and 40-50 km sometimes limited by technology design (timing issues) always limited by the low-power signals emitted by devices Base Stations forward traffic into the carrier network through a backhaul network in many cases using land lines (fiber optics) or dedicated wireless P2P or P2MP links in remote locations via specialized radio relays ©Navid Nikaein 2010 17

    18. Mobile Carriers Interconnectivity Mobile carriers handle traffic inside their networks through IP eXchange (IPX) network call traffic never has to leave the carrier network data traffic and inter-network calls have to leave the network IPX allows exchange of IP traffic between different mobile and fixed operators or ISP via NNI interface (developed by GSMA) Joining the Internet means to connect to a connected gateway mobile carriers often have few central gateway locations all mobile Internet traffic passes through these locations ©Navid Nikaein 2010 18

    19. Wireless Systems Evolution ©Navid Nikaein 2010 19 Number of mobile subscribers is ever increasing Number of mobile subscribers is ever increasing

    20. Network Evolution Evolution from separate packet-switched and circuit-switched core sub-domains to one common IP core New IP-based mobile core introduced in LTE: Toward ALL-IP-Architecture IPv4 towards IPv6 ©Navid Nikaein 2010 20

    21. Mobile Device Evolution Smart Phone and 3G handsets are growing at a faster pace that of ULC handsets Always connected multimedia capable handsets Exponential growth of smart phone ©Navid Nikaein 2010 21 Better and better system for higher and higher multimedia capable (close to PC) smart phoneBetter and better system for higher and higher multimedia capable (close to PC) smart phone

    22. Smartphone User Market Segmentation Media-Centric Usage Casual data use SMS/MMS usage PIM not nessecerily connected Mobile entertainements Mobile web browsing Third party applications Features Multimedia player High resolution screen Html browser High memeory capacity High resolution camara Wifi, BT, FM, Voice features Apple iPhone, Samsung Galaxy SII Productivity-centric Usage Robust data use SMS/MSM usage Integration with mail server Connected PIM Enteprise applications Mobile web browsing Information alert Features Qwerty keyboard Push data/ messaging (email Html browser Multimedia player Removable battery Wifi, BT, FM, Voice features Blackberry, WP, Samsung Blackjack ©Navid Nikaein 2010 22

    23. User Evolution Data-centric users are growing Both media- and productivity- centric Data traffic is expected to exceed the voice traffic In 2008, mobile access (laptop+smartphone) to the Internet exceeded desktop computer-based access for the first time (ITU) ©Navid Nikaein 2010 23

    24. User Evolution User Human Machine Community Heterogeneous user access anytime anywhere NFC, BT, WLAN, Wifi Direct, 2G/3G/4G Heterogeneous user mobility Fixed, nomadic, mobile Seamless Connectivity Service Content ©Navid Nikaein 2010 24 Emerging triology: connectivity – communication - contentEmerging triology: connectivity – communication - content

    25. Wireless Access WLAN Technology Specified protocols for data-link layer and Physical layer Approximate indoor (<70) and outdoor (<250) ranges are different 802.11b (2.4 GHz 300’ radius 11 Mbps) 802.11a (5 GHz 54 Mbps incompatible with b) 802.11g (2.4 GHz 54 Mbps backward compatible with b) WPAN 802.15.1 (BlueTooth, 2.4 Ghz 30’ radius) 802.15.3a (UWB – up to 500 Mbps over short distances) 802.15.4 (Zigbee, 250, 40, 20 kbps) 802.15.5 (MESH, 250, 40, 20 kbps) WiMAX 802.16 (WMAN, WIMAX, several Mbps) MBWA 802.20 (<3.5 GHz >1 Mbps @250 kph) NFC and RFID, within centimeters, contactless Femto-cell ©Navid Nikaein 2010 25

    26. Application Evolution ©Navid Nikaein 2010 26 Toward gigabit applicationsToward gigabit applications

    27. Wireless broadband Internet All IP High Data Rate High Mobility QoS/MOS Service User Experience Diversity of Equipments heterogeneous interoperability Lower cost per bit ©Navid Nikaein 2010 27 Multicarrier transmission and Adaptive transmission.Multicarrier transmission and Adaptive transmission.

    28. Mobile platform run time environment ©Navid Nikaein 2011 28

    29. Mobile Platforms Native runtime platforms Web-based runtime platforms Cross-runtime platforms Hybrid runtime platforms Example of Other Runtime environement ©Navid Nikaein 2011 29

    30. Native Mobile Platform 1 ©Navid Nikaein 2011 30

    31. Native Mobile Platform 2 ©Navid Nikaein 2011 31

    32. Web as a Platform Code is delivered on demand using Web standards HTML, CSS, JS, DOM, HTTP Web technologies are migrating into the OS HTTP support by the OS still is the exception and not the rule More complete packages are available (WebKit) WebOS treats Web technologies as the native API ChromeOS is using the browser as a platform browser = WebKit + user controls (a.k.a. chrome) ChromeOS and WebOS are not all that different (technically) ©Navid Nikaein 2011 32

    33. Web as a Platform ©Navid Nikaein 2011 33

    34. Curent Web Capabilities Web technology is rather limited in its device support keyboard/mouse perspective is built into numerous technologies output is visual and bitmapped Many Web pages rely on non-standardized technologies Flash for rich media (mostly video playback) Silverlight for Rich Internet Application (RIA) implementations Web technology is limited to online scenarios Google tried changing this with Google Gears (offline support) offline capabilities are now added in various places most Web-based apps by their very nature are online-oriented HTML5 /CSS3 and evolving set of technologies ? ©Navid Nikaein 2011 34

    35. Missing Pices Non-traditional interactions (multi-)touch screen for pointing interactions accelerometer for measuring device movement vibration for giving tactile feedback Access to device hardware camera, compass, … Access to additional information sources phone API for phone calls and messaging contacts, calendar, social networks, … Special graphics capabilities essential for advanced rendering (gaming, 3D visualization) non-traditional bitmapped displays such as e-ink ©Navid Nikaein 2011 35

    36. Cross-platform Runtime Build app with web tech, wrap it up, run Application and runtime compiled into a native application less dependency on installation status of the client only reasonable with a lightweight runtime PhoneGap acts mostly as glue for native functionality exposing currently unsupported functionality as JavaScript APIs the actual functionality is supported/implemented in the OS Other platforms : Worklight Appmobi Rhomobile Appcelerator widgetPad MoSync ©Navid Nikaein 2011 36

    37. PhoneGap ©Navid Nikaein 2011 37

    38. Hybrid Runtime Platform Write Once, run Anywhere ! Traditional HTML supports only static content initial browsers did not support scripting the browser wars made scripting very heavy Multimedia content was required for commercial content Java was an existing (but heavy) solution from enterprise IT Performance and not supported by iPhone Flash evolved from a more content-centric perspective Security issues and not currently supported by iPhone AIR engaging application beyond the browser across screen SilverLight a Windows web application Platform (similar to flash) Today's browsers are runtime environments themselves rich and fairly robust scripting environments more limited access to OS resources than add-ons Browser wars again appear here the Browser as a Platform (ChromeOS) ©Navid Nikaein 2011 38

    39. Java based Platform ©Navid Nikaein 2011 39 What is native application : An application designed to run in the computer/mobile environment (machine language and OS) being referenced. The term is used to contrast a native application with an interpreted one such as a Java application that is not native to a single platform. The term may also be used to contrast a native application with an emulated application, which was originally written for a different platform.What is native application : An application designed to run in the computer/mobile environment (machine language and OS) being referenced. The term is used to contrast a native application with an interpreted one such as a Java application that is not native to a single platform. The term may also be used to contrast a native application with an emulated application, which was originally written for a different platform.

    40. Embedded in the Browser Plugin architectures of browsers allow browser extensions Applet, and object Browsers must have the extension installed for content to work plugin installation is complicated and security-sensitive fallback can be implemented but often is too costly and not supported Browser plugins are not subject to the same security policies they run as native code (the plugin is installed as an OS-level library) vulnerabilities of the plugin turn into vulnerabilities of the browser More lightweight approaches may be required for mobile devices Flash Light is a version of Flash for limited devices JavaFX and JavaFX Mobile are intended to replace Applets/J2ME ©Navid Nikaein 2011 40

    41. Browser/Flash Platform ©Navid Nikaein 2011 41

    42. Standalone Runtime Removing the limitations of the browser essentially recreating Java's virtual machine approach often more friendly to Web technologies (built-in HTML/CSS/Scripting) Transitioning outside of a browser breaks the Web flow standalone apps mean that there is no back button it is harder to integrate these applications with others Most examples of standalone applications are black holes they are not supposed to connect to the fabric of the Web overcoming the black hole effect is easier in a browser ©Navid Nikaein 2011 42

    43. AIR / Flash Standalone Platform ©Navid Nikaein 2011 43

    44. Summary Devices, platforms, and technologies are evolving fast Web-based applications will see better support in the near future Mobile will probably follow the path of the Web ©Navid Nikaein 2011 44

    45. Implication of Technology Evolution on Mobile Devices ©Navid Nikaein 2011 45

    46. System and Service Evolution Convergence of several industries and explosion of standards have increased the complexity ©Navid Nikaein 2011 46 Previous to this presentation, I need to present the wireless standard evolution. Intro of MobAdvPrevious to this presentation, I need to present the wireless standard evolution. Intro of MobAdv

    47. Explosion of Standards ©Navid Nikaein 2011 47

    48. High end Phone Feature Evolution ©Navid Nikaein 2011 48 PIM: personal information managerPIM: personal information manager

    49. Mobile Device Hardware Evolution ©Navid Nikaein 2011 49

    50. Mobile Device Software Evolution ©Navid Nikaein 2011 50

    51. Mobile OS ©Navid Nikaein 2011 51

    52. OS Wars Does mobile market follows the PC market? There is a fragmentation in Mobile OS WP Symbian iOS Android Palm OS/ WebOS ©Navid Nikaein 2011 52

    53. Mobile OS Landscape Mass-market proprietary phones Closed /Featured / low cost phones Single processor (80% modem+20% Apps) Built-in applications No native SW after the production expcept for java Proprietary OS Example RTOS Niche-market Smartphones Open / smart / high end phones Dual processor (1xModem+1xApp) Built-in applications Native SW & Apps can be added ©Navid Nikaein 2011 53

    54. Windows Phone 7 History (http://en.wikipedia.org/wiki/Windows_Mobile) First on PDA, Pocket PC from 2000 -2002 based on Windows CE (kernel ) Windows mobile from 2003 - Jan 2010 Windows CE kernel + Windows Mobile OS Target mostly the professionals, now xbox, social, multimedia Windows Phone 7 from October 2010 Replacement of Windows Mobile Move to consumers with WP7, Xbox, multimedia, social network, advertising platform Endorsed by a large number of OEMs Samsung focus, LG Quantum, HTC surround, Dell Venue WP 8 expected in 2012 Non-brand specific and non open source SDK / APPs Windows Mobile: C/C++ SDK (Visual Studio), C# through .NET Windows Phone: entirely managed code (C#), Sliverlight Windows MarketPlace ©Navid Nikaein 2011 54

    55. Symbian History (http://en.wikipedia.org/wiki/Symbian_OS) Descendent of Psion’s graphical multitasking OS, called EPOC, based on ARM processor EPOC renamed to Symbian in 2000, and used 1st in Nokia communicator 9210 Versioning: Symbian 9.1/2/3 => Symbian 1/2/3/4 Endorsed by Nokia (for mid-range smartphone) and some other OEMs (SMEC, Samsung) Non-brand specific, brand owend Brand owned by Nokia, but still operating as a separate open-sporce driven foundation Symbian 3 is fully open-source Over engineered, not trivial for non-engineers SDK / Apps C++, now QT+ Nokia OVI store, and other brand specific store ©Navid Nikaein 2011 55

    56. iOS History (http://en.wikipedia.org/wiki/IOS_(Apple)) Started with iPhone 2G (Edge) in 2007 Then iPod touch later in 2007 Then iPhone 3Gs (UMTS) with faster HW OS ported on other devices and become iOS Initially no App Store, only Web Apps Jailbroken version enabled users to download hackers apps App store enabled by version 2G together with first SDK in 2008 Brand owned, very closed Scaled-down OS X, Touch version of MAC app framework SDK / Apps Objective-C, and C Apple App Store ©Navid Nikaein 2011 56

    57. Android History (http://en.wikipedia.org/wiki/Android_%28operating_system%29) Developed by Android inc., acquired by Google Closed until 2007, and opened in 2008 Open handset alliance in 2007 HW vendors, OEMs, operators, service providers Start from Android G1, now more than 50 models Praised as “the only open OS” at first Now the new “evil” Open OS, non brand-locked, open-source Endorsed by many OEMS Custom Linux kernel + new libs Google custom VM “Davlik” + java app framework SDK / App Originally: java-based: eclipse, ADT + emulator Now also an NDK (performance critical part of app) Android Market App inventor ©Navid Nikaein 2011 57

    58. History (http://en.wikipedia.org/wiki/Palm_OS, http://en.wikipedia.org/wiki/WebOS) A.K.A Garnet OS, used in Palm pilots, (1st PDA), ARM processor Enable touch-screen apps Successful App market long before App store PalmOS => Garnet OS => ALP => WebOS acquired by HP Brand-specific, owned by Palm inc. (HP) Linux + webkit + custom HTML+mojo JS FW SDK / APP PDK/C++, JS/HTML/CSS Nokia OVI and brand specific stores Palm OS / WebOS ©Navid Nikaein 2011 58

    59. MeeGo OS History (http://en.wikipedia.org/wiki/MeeGo) Maemo by Nokia Moblin branch from maemo by Intel Remerged between Maemo+ Moblin Open source Built on the top of Debian & Fedora Maemo/Moblin Linux distribution Linux+ middleware+QT+ Handset/netbook UX Telephony libs come from Nokia SDK/APP C++, custom framework Eclipse Brand app store ©Navid Nikaein 2011 59

    60. Others RIM Blackberry RTOS Custom VM Custom SDK, app store, Java Qualcom Brew RTOS Custom framework with DLL support Custom SDK, app store Native and Java Google Chrome OS Linux + webkit chorme core JS and web framework LiMo, openMoKo, Ophone, ©Navid Nikaein 2011 60

    61. Platform development Environnement ©Navid Nikaein 2011 61

    62. Mobile OS Timeline ©Navid Nikaein 2011 62

    63. Open OS Wars ©Navid Nikaein 2011 63

    64. Conclusion Fragmentation and application execution environment (AAE) Fragmentation is a big issue Previously for device manufacturer (OEM) to maintain their SW (cost) Now for application developer market How to develop an application and deploy it to many platforms The OS is not everything AAE on the top of OS ? Is HTML5 and Web app are the solution to this? Typekit, webworkers, web GL, webkit Most platforms are adopting the same browser core Webkit http://en.wikipedia.org/wiki/Comparison_of_web_browser_engines WAC, phonegap, AIR, are some examples http://www.wholesaleappcommunity.com/default.aspx ©Navid Nikaein 2011 64

    65. App Store Market ©Navid Nikaein 2011 65

    66. ©Navid Nikaein 2010 66

    67. Mobile Apps Stores Platform vendors using apps as a marketing angle Apps market the platform More apps = more use case => network effect Control points owned by platform vendors Walled-garden vs. real-world Merchandizing, distribution, fulfillment, transactions, policy, functionality may be cut off Key advantages Simple through a unique portal Safe through a trusted parties Platform vendors looking to provide access to the realworld while keeping the benefits of the app model ©Navid Nikaein 2011 67

    68. … a lot of players! ©Navid Nikaein 2010 68

    69. BMW App Store !! ©Navid Nikaein 2010 69

    70. App Store Comparison ©Navid Nikaein 2011 70

    71. Popular Mobile App Category: Q2 2011 ©Navid Nikaein 2011 71

    72. Main App Category ©Navid Nikaein 2011 72

    73. Hype Cycle 2009 ©Navid Nikaein 2010 73

    74. Hype Cycle 2010 ©Navid Nikaein 2010 74

    75. Hype Cycle 2011 ©Navid Nikaein 2010 75

    76. Mobile Cross-Platform Runtime Environment ©Navid Nikaein 2011 76

    77. Java Java is a runtime environment supported on many operating systems general-purpose, concurrent, class-based, object-oriented language Write once and run anywhere philosophy Strictly speaking, Java is three different things an object-oriented programming language an extensive set of class libraries as supporting environment the Java Virtual Machine (JVM) for executing Java Bytecode Sun defines and supports four editions of Java targeting different application environment Java card Java mico edition (JME) Java standard edition JSE Java enterprise edition JEE Java Applets are a special kind of Java apps running inside a browser (can be started from the Web) running inside a sandbox (security model for limiting OS access) ©Navid Nikaein 2011 77 GNU Compiler for Java, GNU Classpath, and DalvikGNU Compiler for Java, GNU Classpath, and Dalvik

    78. JavaFX Running on the top of JME shedding the JME brand Capable of running on multiple mobile operating systems including Symbian and Window mobile Java platform for creating rich internet applications (RIA) Common profile across all devices (i.e. desktop & mobile) Drag to install, a break away from the browser Drag a JavaFx widget/web app and drop it on the desktop Third party graphic integration (mainly adobe) More Web standards for developing content CSS as a way to specify the layout of content Scripting as a faster way for application development Success and support currently unclear ©Navid Nikaein 2011 78

    79. FLASH Multimedia on Web Started as an animation platform for content developers Multimedia platform for creating interactivity to web pages animation + video includes many of the functionality now developed in HTML5 traditionally used for advertising, game, and bidirectional streaming target Rich Internet Application (RIA) a software Framework : Web application => desktop application Robust scripting for desktop browsers (Actionscript) good strategy for deploying Flash as a browser add-on gets harder with the growing variety of browsers and platforms (iphone) Many accessibility issues on Flash-oriented sites navigation can be completely inaccessible content can be hidden from search engines content is less fluid than even the simplest HTML/CSS poor handling of sound ©Navid Nikaein 2011 79

    80. Adobe Integrated Runtime (AIR) Adobe AIR Cross-platform browser-less runtime environment for RIA Flash, Flex (SDK), Actionscript / HTML+Javascript, Ajax Desktop deeper integration Native process, microphone, printer APIs Native document/file handler UDP networking, Webkit HTML5/CSS3 Mass storage, drag-and-drop Socket server, P2P, TLS/SSL socket Large windows size, Input method editor IME API, multitouch and gestures Development Environment HTML/Ajax Dreamwears CSx or HTML editor and AIR SDK Adobe Flash Builder Flash CSx Support for Android platform ©Navid Nikaein 2011 80

    81. Comparison: Browser vs. Desktop ©Navid Nikaein 2011 81

    82. Sliverlight Web application framework that integrates multimedia graphics animation interactivity Provide a single runtime environment XAML + .NET FW CLI language Development tools Support Mobile devices Windows Phone 7 and Symbian S60 Features are similar to adobe Flash and AIR Both for embedded and standalone applications Include many HTML5 features Allow Rich Internet Application ©Navid Nikaein 2011 82

    83. EURECOM MEMBERS ©Navid Nikaein 2011 83

More Related