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 Data Richer Content Better Security Carrier APIs Cross Platform App Development

3. LTE IS MUCH FASTER LTE Latency One-Way 15ms Avg Data Rates LTE - 12Mbps 3g - 5Mbps Max Data Rates LTE - 86Mbps 3g - 28Mbps LTE Enables video sharing, video conferenceing, HD streaming Over 50% Faster

4. MORE SPECTRUM = MORE BANDWIDTH LTE Spectrum 1.4Mhz – 20Mhz Built for Data 3G Spectrum 1.25Mhz – 5Mhz Built for Voice 20 Mhz 1 Mhz 10 Mhz

5. LTE DELIVERS LOWER LATENCYKeep data in the cloud EDGE DL: 474 Kbps UL: 474 Kbps Evolved EDGE DL: 1.89 Mbps UL: 947 Kbps THEORETICAL LATENCY Release 7 HSPA+(5 MHz cxr) DL: 28 Mbps UL: 11.5 Mbps Release 8 HSPA+(10 MHz cxr) DL: 42 Mbps UL: 11.5 Mbps Release 9 HSPA+(10 MHz cxr) DL: 84 Mbps UL: 23 Mbps Rel. 10 HSPA+(20/10 MHz cxr) DL: 168 Mbps UL: 23 Mbps 65 ms 50 ms Rel. 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 ms EV-DO Rev A (1.4 MHz cxr) DL: 3.1 Mbps UL: 1.8 Mbps EV-DO Rev B(5 MHz cxr) DL: 14.7 Mbps UL: 5.4 Mbps HSPA HSPA+ LTE *64 QAM uplink is optional; Release 10 uplink is 200 Mbps with 16 QAM

7. Multipart Video

8. Real time gaming

9. Cloud-driven apps

12. 156 operators in 64 countries investing in LTE

14. Build apps that can be used globally

15. Apps can depend on data of LTE networks

17. Android App Development Best Practices

19. Bandwidth total usage

20. Latency required (ie. Map scrolling)

21. Reliability of data access

22. Security concerns

23. 2G, 3G, and LTE scenarios must be considered for data heavy apps

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

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-fetched Current Screen of App

33. Consider pushing data to apps during times of lower network activity

35. Streaming consumes more battery by increasing device radio power

37. Constant requests to the network will drain device batter life

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)

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

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.