4G LTE Presentation from O\'Reilly Android Open Confereence
Download as PPTX, PDF2 likes838 views
This document discusses the capabilities and opportunities of 4G LTE mobile networks. LTE networks have significantly faster data speeds compared to 3G, support richer content like HD video, and are being rolled out globally. Application developers should design their apps to dynamically adapt to different network conditions, cache data locally when possible, and take advantage of carrier APIs. As LTE adoption increases, it will drive higher mobile data usage and new opportunities for developers.
4G LTE Presentation from O\'Reilly Android Open Confereence
- 1. Building Killer Android Apps for 4G/LTE NetworksO’Reilly Android Open ConferenceAlex Gaber, Technical EvangelistOctober 11th, 2011
- 2. WHAT DOES 4G / LTE MEAN TO YOU?Faster DataRicher ContentBetter SecurityCarrier APIsCross Platform App Development
- 3. LTE IS MUCH FASTERLTE Latency One-Way15msAvg Data RatesLTE - 12Mbps3g - 5Mbps Max Data RatesLTE - 86Mbps3g - 28Mbps LTE Enables video sharing, video conferenceing, HD streamingOver 50% Faster
- 4. MORE SPECTRUM = MORE BANDWIDTHLTE Spectrum1.4Mhz – 20MhzBuilt for Data3G Spectrum1.25Mhz – 5MhzBuilt for Voice20 Mhz1 Mhz10 Mhz
- 5. LTE DELIVERS LOWER LATENCYKeep data in the cloudEDGEDL: 474 KbpsUL: 474 KbpsEvolved EDGEDL: 1.89 MbpsUL: 947 KbpsTHEORETICALLATENCYRelease 7 HSPA+(5 MHz cxr)DL: 28 MbpsUL: 11.5 MbpsRelease 8 HSPA+(10 MHz cxr)DL: 42 MbpsUL: 11.5 MbpsRelease 9 HSPA+(10 MHz cxr)DL: 84 MbpsUL: 23 MbpsRel. 10 HSPA+(20/10 MHz cxr)DL: 168 MbpsUL: 23 Mbps65 ms50 msRel. 10 LTE (20 MHz)(64QAM & carrier agg)DL: 1.2 Gbps (8x8)UL: 300 Mbps (4x4)*Release 8-9 LTE (20 MHz)2x2 or 4x4 MIMO (DL)DL: 150 Mbps (2x2) / 300 Mbps (4x4)UL: 50 Mbps (16 QAM) / 75 Mbps (64 QAM)*10 msEV-DO Rev A(1.4 MHz cxr)DL: 3.1 MbpsUL: 1.8 MbpsEV-DO Rev B(5 MHz cxr)DL: 14.7 MbpsUL: 5.4 MbpsHSPAHSPA+LTE*64 QAM uplink is optional; Release 10 uplink is 200 Mbps with 16 QAM
- 6. RICHER CONTENT ENABLEMENTHD Video
- 10. Fluid augmented realityLTE DEVICES ARE MORE AFFORDABLE
- 11. LTE IS BEING ROLLED OUT GLOBALLYEurope2010: Scandanavia, Eastern Europe2011: European Digital Dividend - Germany2012: 3G Upgrades to LTENorth America2010: Verizon, MetroPCS2011: AT&T, T-MobileAsia2011: India BWA Launches2012: China MobileLatin America2011: Potential Launches for fixed broadband113 LTE network commitments in 46 countries
- 12. 156 operators in 64 countries investing in LTE
- 13. At least 55 LTE networks in service by end 2012SIMPLIFIED WORLDWIDE ROAMINGLTE is a unifying standard with seamless international roaming
- 14. Build apps that can be used globally
- 15. Apps can depend on data of LTE networks
- 16. Emerging markets represent a huge opportunity for mobile appsMOBILE APPLICATION IMPACTData consumption will increase dramatically
- 17. Android App Development Best Practices
- 18. ALLOW FOR VARIABLE DATA USAGEProvide different versions of app based on type of network
- 20. Latency required (ie. Map scrolling)
- 21. Reliability of data access
- 23. 2G, 3G, and LTE scenarios must be considered for data heavy apps
- 24. Give users option within app to select bandwidth based on their data plan LTE DELIVERS BETTER SECURITYNetwork authentication (128 bit keys)
- 25. RAN encrypted data communication
- 26. User identity protection through IMSI / IMEI (transition from 10 digit MDN to 15 digit IMSI)
- 27. IPSec support for secure tunneled VPN and IP based communication
- 28. IPMS granular security per serviceDYNAMIC QUALITY OF SERVICEData plans are now metered and capped
- 29. Consumers need controls within apps for data consumptionPRE-FETCH DATA Push data to applications by anticipating what a user wants (ie Google Maps scrolling)
- 30. For users on costly data planes, do not pre-fetch
- 31. Offer options for media quality, optimize app to deliver best results based on the optionsData being pre-fetchedCurrent Screen of App
- 32. CACHE MORE DATASmartphones have lots of storage, use it
- 33. Consider pushing data to apps during times of lower network activity
- 34. Flush caches as appropriateFAVOR DOWNLOADING OVER STREAMINGConsider the end-user experience
- 35. Streaming consumes more battery by increasing device radio power
- 36. Devices will be jumping between 3G and LTE networks, which will cause a 3-8 second delayAVOID AGGRESSIVE BEHAVIORIf a GET request is denied, make your app pause and wait instead of hammering the network
- 37. Constant requests to the network will drain device batter life
- 38. Consider data push or syncing with reasonable demands on being currentCARRIERS OFFER API’SSMS API
- 39. MMS API
- 40. Terminal Status (is phone ‘on’ or ‘off’)
- 41. Location via Cell Tower Trilateralization
- 42. Allow for ‘sleeping’ LBS notifications
- 43. Avoid using GPS on devices which drains battery life
- 44. Carrier Billing APIs (www.wacapps.net)
- 45. 4,000 APIs listedECOSYSTEM IS GROWING
- 46. OpenPlug Studio Create native apps at the speed of ideasCross-Platform (iOS, Android, Windows Mobile, Symbian, …)
- 47. Web Development (AS/JS, XML, CSS) – 10x more productive than native SDK
- 48. Native User Experience - single code base, many variants, high performance
- 49. Native Code Extensions which allow using any native SDK feature
- 50. Monetisationthrough app stores - distribution and discoverabilityAlmanaque Anos 80 - #1 Paid App in Brazil
- 51. OpenPlug Studio Overview Programming modelRapid UI coding: XML-based, CSS
- 52. Scripting language: ActionScript or Javascript
- 53. Productive application framework: Adobe Flex 3.5 (subset for Mobile)
- 54. Generic device API: GPS, Camera, Comm., etc.
- 55. Built-in support for web services: REST, SOAP, Auth.
- 56. Native Code extension: C/C++, Java, ObjectiveC