cellular networks and mobile computing coms 6998-11, fall 2012

67
Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012 Instructor: Li Erran Li ([email protected]) http://www.cs.columbia.edu/ ~lierranli/coms6998-11Fall2012 / 10/9/2012: Mobile Cloud

Upload: avalon

Post on 26-Feb-2016

36 views

Category:

Documents


3 download

DESCRIPTION

Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012. Instructor: Li Erran Li ( [email protected] ) http://www.cs.columbia.edu/ ~lierranli/coms6998-11Fall2012/ 10/ 9 /2012: Mobile Cloud Platform Services. Announcements. iOS assignment 2 due Oct 16 th Revised syllabus - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile ComputingCOMS 6998-11, Fall 2012

Instructor: Li Erran Li ([email protected])

http://www.cs.columbia.edu/~lierranli/coms6998-11Fall2012/

10/9/2012: Mobile Cloud Platform Services

Page 2: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

2

Announcements

• iOS assignment 2 due Oct 16th

• Revised syllabus – Please email me if you want to present one of

them instead of the originally assigned• Windows Phones available for project use– On loan from Microsoft, please take good care of

them

10/9/12

Page 3: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

3

Syllabus• Mobile App Development (lecture 2,3)

– Mobile operating systems: iOS and Android – Development environments: Xcode, Eclipse with Android SDK– Programming: Objective-C and android programming

• System Support for Mobile App Optimization (lecture 4,7)– Mobile device power models, energy profiling and ebug debugging– Core OS topics: virtualization, storage and OS support for power and context management

• Interaction with Cellular Networks (lecture 1,5, 8) – Basics of 3G/LTE cellular networks– Mobile application cellular radio resource usage profiling– Measurement-based cellular network and traffic characterization

• Interaction with the Cloud (lecture 6,9)– Mobile cloud computing platform services: push notification, iCloud and Google Cloud Messaging– Mobile cloud computing architecture and programming models

• Mobile Platform Security and Privacy (lecture 10,11,12)– Mobile platform security: malware detection, attacks and defenses– Mobile data and location privacy: attacks, monitoring tools and defenses

10/9/12

Page 4: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

4

Mobile Cloud Platform Services• Social network services• Compute and storage

– Syncing and storage service (iCloud)– Amazon EC2 infrastructure and platform services

• Proxy service (Kindle Split Browser)• Push notification service• Location based service

– Track service (supporting location based services)• Recognition services

– Speech to text/text to speech service– Natural language processing service (open Siri API for 3rd party

applications in the future)10/9/12

Page 5: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

5

Outline• Social network services– Demo: add social feature to the calculator app

• iCloud service – Demo: add iCloud feature to the calculator app

• Push notification service– Apple push notification service

• Demo: add push notification to the calculator app– Google GCM

• Demo: add push notification to the calculator app– Thialfi: reliable push notification system

• Track service

10/9/12

Page 6: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

6

Social Network Services• iOS social framework in core service layer• Facebook, twitter account needs to be configured• Social Framework includes a controller called

SLComposeViewController– An instance must be created: SLComposeViewController *socialController =

[SLComposeViewController composeViewControllerForServiceType:socialNetwork];• Calling the API

if([SLComposeViewController isAvailableForServiceType:socialNetwork]){ SLComposeViewControllerCompletionHandler __block completionHandler=^(SLComposeViewControllerResult result){ [socialController dismissViewControllerAnimated:YES completion:nil];

switch(result){ case SLComposeViewControllerResultCancelled: default: NSLog(@"Cancelled....."); break; case SLComposeViewControllerResultDone: NSLog(@"Posted...."); break; } }; 10/9/12

Page 7: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

7

Social Network Services (Cont’d)[socialController addImage:[UIImage

imageNamed:@"CollatzFractal.png"]];[socialController setInitialText:@"Solve the 3x+1 math puzzle."];[socialController addURL:[NSURL

URLWithString:@"http://en.wikipedia.org/wiki/Collatz_conjecture"]];

[socialController setCompletionHandler:completionHandler];

[self presentModalViewController:socialController animated:YES];}

10/9/12

Page 8: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

8

Social Network Services (Cont’d)Also support http request to social networksNSDictionary *parameters = @{@"message": @"My first iOS 6 Facebook posting "}; NSURL *feedURL = [NSURL URLWithString:@"http://www.facebook.com/erran"]; SLRequest *feedRequest = [SLRequest requestForServiceType:SLServiceTypeFacebook requestMethod:SLRequestMethodGET // requestMethod:SLRequestMethodPOST URL:feedURL parameters:parameters]; feedRequest.account = facebookAccount; [feedRequest performRequestWithHandler:^(NSData *responseData, NSHTTPURLResponse *urlResponse, NSError *error) { // Handle response NSString *response = [[NSString alloc] initWithData:responseData

encoding:NSUTF8StringEncoding]; NSLog(@"feedRequest response, status code: %d, data:%@", urlResponse.statusCode,

response); }];

10/9/12

Page 9: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Yale CS 434/534 9

iCloudFundamentally: nothing more than a URL of a shared directory• Two storage models

– iCloud document storage: store user documents and app data in the user’s iCloud account

– iCloud key-value data storage: share small amounts of noncritical configuration data among instances of your app

• iCloud-specific entitlements required– Select your app target in Xcode– Select the Summary tab– In the Entitlements section, enable the Enable Entitlements

checkbox

10/4/12

Page 10: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Yale CS 434/534 10

iCloud (Cont’d)• Check availability: URLForUbiquityContainerIdentifier:• All files and directories stored in iCloud must be managed by a file

presenter object, and all changes you make to those files and directories must occur through a file coordinator object. A file presenter is an object that adopts the NSFilePresenter protocol

• Explicitly move files to iCloud• Be prepared to handle version conflicts for a file• Make use of searches to locate files in iCloud• Be prepared to handle cases where files are in iCloud but not fully

downloaded to the local device; this might require providing the user with feedback

• Use Core Data for storing live databases in iCloud; do not use SQLite

10/4/12

Page 11: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

11

Apple Push Notification Architecture Overview

• iOS device maintains a persistent TCP connection to a Apple Push Notification Server(APNS)

10/9/12

A push notification from a provider to a client application

Multi-providers to multiple devices

Page 12: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

12

Apple Push Notification Architecture Overview (Cont’d)

• What if devices uninstalled the app?– Feedback service

• Providers poll to obtain list of device tokens for their applications

• What if devices are offline?– QoS service

• QoS stores the notification• It retains only the last notification received from a provider• When the offline device reconnects, the QoS forwards the

stored notification to the device• QoS retains a notification for a limited period before deleting it

10/9/12

Page 13: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

13

Push Notification

• Push notification– Delivery is best effort and is not guaranteed– Max size is 256 bytes– Providers compose a JSON dictionary object • This dictionary must contain another dictionary

identified by the key aps– Action:• An alert message to display to the user• A number to badge the application icon with• A sound to play

10/9/12

Page 14: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

14

Device Token• Device token is analogous to a phone number

– Contains information that enables APNs to locate the device– Client app needs to provide the token to its provider– Device token should be requested and passed to providers every time your application

launches

10/9/12

Page 15: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

15

Apple Push Notification Programming Example

• Provisioning: https://developer.apple.com/ios/manage/provisioningprofiles/howto.action– Generate Certification Signing Request (CSR) using Keychain

Access• Save to disk: PushChat.certSigningRequest• Export the private key as “PushChatKey.p12” and enter a passphrase

– Make an App ID in iOS Provisioning Portal• Check the Enable for Apple Push Notification service box• click on the Configure button for the Development Push SSL Certificate• click Download to get the certificate – it is named

“aps_development.cer”10/9/12

Page 16: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

16

Apple Push Notification Programming Example (Cont’d)

• Client code1. - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary

*)launchOptions2. {3. // Let the device know we want to receive push notifications4. [[UIApplication sharedApplication] registerForRemoteNotificationTypes:5. (UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound |

UIRemoteNotificationTypeAlert)];6. 7. return YES;8. }

9. - (void)application:(UIApplication*)application didReceiveRemoteNotification:(NSDictionary*)userInfo10. {//userInfo contains the notification11. NSLog(@"Received notification: %@", userInfo);12. }

13. - (void)application:(UIApplication*)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData*)deviceToken

14. {15. NSLog(@"My token is: %@", deviceToken);16. }

10/9/12

Page 17: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

17

Apple Push Notification Programming Example (Cont’d)

• Server code1. $devicetoken ='f05571e4be60a4e11524d76e4366862128f430522fb470c46fc6810fffb07af7’;2. // Put your private key's passphrase here:3. $passphrase = 'PushChat';4. // Put your alert message here:5. $message = 'Erran: my first push notification!';

6. $ctx = stream_context_create();7. Stream_context_set_option($ctx, 'ssl', 'local_cert', 'ck.pem');8. stream_context_set_option($ctx, 'ssl', 'passphrase', $passphrase);

9. // Open a connection to the APNS server10. $fp = stream_socket_client(11. 'ssl://gateway.sandbox.push.apple.com:2195', $err,12. $errstr, 60, STREAM_CLIENT_CONNECT|STREAM_CLIENT_PERSISTENT, $ctx);

13. if (!$fp)14. exit("Failed to connect: $err $errstr" . PHP_EOL);

15. echo 'Connected to APNS' . PHP_EOL;

16. // Create the payload body17. $body['aps'] = array(18. 'alert' => $message,19. 'sound' => 'default'20. );

21. // Encode the payload as JSON22. $payload = json_encode($body);

23. // Build the binary notification24. $msg = chr(0) . pack('n', 32) . pack('H*', $deviceToken) . pack('n', strlen($payload)) . $payload;

25. // Send it to the server26. $result = fwrite($fp, $msg, strlen($msg));

27. if (!$result)28. echo 'Message not delivered' . PHP_EOL;29. else30. echo 'Message successfully delivered' . PHP_EOL;

31. // Close the connection to the server32. fclose($fp);

10/9/12

Page 18: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Google Cloud Messaging (Cont’d)

• Push notification problems– Network firewalls prevent servers from directly sending messages to

mobile devices• GCM solution

– Maintain a connection between device and Google GCM server– Push server updates to apps on the device via this connection– Optimize this connection to minimize bandwidth and battery consumption

(e.g. adjusting the frequency of keep alive messages)• Send-to-sync messages vs. messages with payload• An application can send messages to one or more devices (multicast)

9/18/12

GCM Servers

Page 19: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Google Cloud Messaging (Cont’d)

C2DM is deprecated, accepts no new usersStep 1• Create a Google API project from

Google APIs console pagehttps://code.google.com/apis/console/#project:908058729336– Enable GCM service– Obtain an API key– Create new server key– Install helper libraries

9/18/12

Page 20: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Google Cloud Messaging (Cont’d)

Step 2• Write the Android app

– Copy gcm.jar file into your app classpath

– Configure manifest file for SDK version, permission

– Add broadcast receiver– Add intent service– Write

my_app_package.GCMIntentService class

– Write main activity

9/18/12

import com.google.android.gcm.GCMRegistrar;… GCMRegistrar.checkDevice(this); GCMRegistrar.checkManifest(this); final String regId = GCMRegistrar.getRegistrationId(this); if (regId.equals("")) { GCMRegistrar.register(this, SENDER_ID); } else { Log.v(TAG, "Already registered"); }

Page 21: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Google Cloud Messaging (Cont’d)Step 3• Write server-side app

– Copy gcm-server.jar file from the SDK’s gcm-server/dist directory to your server class path

– Create a servlet that can be used to receive client’s GCM registration ID

– Create a servlet to unregister registration ID

– Use com.google.android.gcm.server.Sender helper class from GCM library to send a message to client

9/18/12

import com.google.android.gcm.server.*;

Sender sender = new Sender(myApiKey);Message message = new Message.Builder().build();MulticastResult result = sender.send(message, devices, 5);

Page 22: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Thialfi: A Client Notification Servicefor Internet-Scale Applications

Atul Adya, Gregory Cooper, Daniel Myers, Michael Piatek

Google Seattle

Page 23: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

23

A Case for NotificationsProblem: Ensuring cached data is fresh across

users and devices

Courtesy: Adya et al.10/9/12

Page 24: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

24

Common Application Patterns

• Clients poll to detect changes– Simple and reliable, but slow and inefficient

• Push updates to the client– Fast but complex– Add backup polling to get reliability– Tail latencies can be high: masks bugs– Application-specific protocol

sacrifice reliability

10/9/12 Courtesy: Adya et al.

Page 25: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

25

Solution: Thialfi

• Scalable: tracks millions of clients and objects• Fast: notifies clients in less than a second• Reliable: even when entire data centers fail• Easy to use: deployed in Chrome Sync, Contacts,

Google Plus

10/9/12 Courtesy: Adya et al.

Page 26: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

26

Thialfi Outline

• Thialfi’s abstraction: reliable signaling

• Delivering notifications in the common case

• Detecting and recovering from failures

• Evaluation and experience

10/9/12 Courtesy: Adya et al.

Page 27: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

27

Thialfi Overview

Thialfi client library

Register X Notify X

ClientData center

X: C1, C2

Client C1 Client C2

Thialfi Service

Update XRegister

Register

Update XApplication backend

Notify X Notify X

10/9/12 Courtesy: Adya et al.

Page 28: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

28

Thialfi Abstraction

• Objects have unique IDs and version numbers, monotonically increasing on every update

• Delivery guarantee– Registered clients learn latest version number– Reliable signal only: cached object ID X at version Y

10/9/12 Courtesy: Adya et al.

Page 29: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

29

Why Signal, Not Data?

• Developers want reliable, in-order data delivery

• Adds complexity to Thialfi and application, e.g.,– Hard state, arbitrary buffering– Offline applications flooded with data on wakeup

• For most applications, reliable signal is enough– Invoke polling path on signal: simplifies integration

10/9/12 Courtesy: Adya et al.

Page 30: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

30

API Without Failure Recovery

Thialfi Service Publish(objectId, version)

ClientLibrary

Register(objectId)Unregister(objectId)

Notify(objectId, version)

10/9/12 Courtesy: Adya et al.

Page 31: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

31

Thialfi Outline

• Thialfi’s abstraction: reliable signaling

• Delivering notifications in the common case

• Detecting and recovering from failures

• Evaluation and experience

10/9/12 Courtesy: Adya et al.

Page 32: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

32

Architecture

ClientBigtable

• Matcher: Object ID registered clients, version• Registrar: Client ID registered objects, notifications

Client

Registrar

MatcherObjectBigtable

Data center

Notifications Application Backend

Registrations, notifications,acknowledgments

Client library

10/9/12 Courtesy: Adya et al.

• Each server handles a contiguous range of keys, • Each server maintains an in-memory version• Bigtable: log structured, fast write

Page 33: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

33

C1: x, v7C2: x, v7C1: x, v5C2: x,

x: v5; C1, C2x: v7; C1, C2x: v7; C1, C2

x

Life of a Notification

ClientBigtable

C1: x, v7

C2: x, v7

Notify: x, v7

Client C2

MatcherObjectBigtable

Data center

Publish(x, v7)x, v7

Ack: x, v7

Registrar

10/9/12 Courtesy: Adya et al.

Page 34: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

34

Thialfi Outline

• Thialfi’s abstraction: reliable signaling

• Delivering notifications in the common case

• Detecting and recovering from failures

• Evaluation and experience

10/9/12 Courtesy: Adya et al.

Page 35: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

35

Data center lossServer state loss/schema migrationPartial storage unavailability

Possible Failures

ClientLibrary

ClientBigtable Registrar

MatcherObjectBigtable

ClientBigtable Registrar

MatcherObjectBigtable

. . .

Data center 1 Data center nThialfi Service

ClientStore

Client restartClient state loss

Publish Feed

Network failures

10/9/12 Courtesy: Adya et al.

Page 36: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

36

Failures Addressed by Thialfi

• Client restart• Client state loss• Network failures• Partial storage unavailability• Server state loss / schema migration• Publish feed loss• Data center outage

10/9/12 Courtesy: Adya et al.

Page 37: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

37

Main Principle: No Hard State

• Thialfi remains correct even if all state is lost– All registrations– All object versions

• Detect and reconstruct after failures using:– ReissueRegistrations() client event– Registration Sync Protocol– NotifyUnknown() client event

10/9/12 Courtesy: Adya et al.

Page 38: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

38

Recovering Client Registrations

Registrar

MatcherObjectBigtable

x

y

x yReissueRegistrations()

Register(x); Register(y)

ReissueRegistrations: Not a burden for applications– Application stores objects in its cache, or – Object list is implicit, e.g., bookmarks for user X

10/9/12 Courtesy: Adya et al.

Page 39: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

39

Registrar

MatcherObjectBigtable

Register: x, y

Syncing Client Registrations

x

y

Hash(x, y)x y

• Goal: Keep client-registrar registration state in sync• Every message contains hash of registered objects• Registrar initiates protocol when detects out-of-sync• Allows simpler reasoning of registration state

Reg syncHash(x, y)

10/9/12 Courtesy: Adya et al.

Merkle tree for syncing large number of objects

Page 40: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

40

Recovering From Lost Versions

• Versions may be lost, e.g. schema migration

• Refreshing from backend requires tight coupling

• Inform client with NotifyUnknown(objectId) – Client must refresh, regardless of its current state

10/9/12 Courtesy: Adya et al.

Page 41: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

41

Thialfi Outline

• Thialfi’s abstraction: reliable signaling

• Delivering notifications in the common case

• Detecting and recovering from failures

• Evaluation and experience

10/9/12 Courtesy: Adya et al.

Page 42: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

42

Notification Latency Breakdown

Notification latency (ms)0

100

200

300

Matcher to Registrar RPC (Batched)

Matcher Bigtable Read

Matcher Bigtable Write (Batched)

Bridge to Matcher RPC (Batched)

App Backend to Bridge

Batching accounts for significant fraction of latency10/9/12 Courtesy: Adya et al.

Page 43: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

43

Thialfi Usage by ApplicationsApplication Language Network

ChannelClient Lines of Code(Semi-colons)

Chrome Sync C++ XMPP 535Contacts JavaScript Hanging GET 40

Google+ JavaScript Hanging GET 80Android Application Java C2DM +

Standard GET300

Google BlackBerry Java RPC 340

10/9/12 Courtesy: Adya et al.

Page 44: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

44

Some Lessons Learned

• Add complexity at the server, not the client– Deploy at server: minutes. Upgrade clients: years+

• Asynchronous events, not callbacks– Spontaneous events occur: need to handle them

• Initial applications have few objects per client– Earlier use of polling forces such a model

10/9/12 Courtesy: Adya et al.

Page 45: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

45

Thialfi Summary

• Fast, scalable notification service• Reliable even when data centers fail• Two key ideas simplify failure handling– Deliver a reliable signal, not data– No hard state: reconstruct after failure

• Deployed in Chrome Sync, Contacts, Google+

10/9/12 Courtesy: Adya et al.

Page 46: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

46

Outline

• Speech to text service demo• Push notification service– Apple push notification service– Google C2DM(not covered in this lecture)– Thialfi: reliable push notification system

• Track service

10/9/12

Page 47: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

47

Location-Based Applications• Many phones already have the ability to

determine their own location– GPS, cell tower triangulation, or proximity to WiFi

hotspots

• Many mobile applications use location information

10/9/12 Courtesy: Maya et al.

Page 48: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

48

TrackTime-ordered sequence of location readings

Latitude: 37.4013Longitude: -122.0730Time: 07/08/10 08:46:45.125

10/9/12 Courtesy: Maya et al.

Page 49: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

49

Application: Personalized Driving Directions

Goal: Find directions to new gymTake US-101 North

10/9/12 Courtesy: Maya et al.

Page 50: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

50

A Taxonomy of ApplicationsPersonal Social

Current location

Driving directions, Nearby restaurants

Friend finder, Crowd scenes

Past locations

Personal travel journal, Geocoded photos

Post-it notes, Recommendations

Tracks Personalized Driving Directions, Track-Based Search

Ride sharing, Discovery, Urban sensing

Class of applications enabled by StarTrack

10/9/12 Courtesy: Maya et al.

Page 52: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

52

System Challenges

1. Handling error-prone tracks

2. Flexible programming interface

3. Efficient implementation of operations on tracks

4. Scalability and fault tolerance10/9/12 Courtesy: Maya et al.

Page 53: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

53

Challenges of Using Raw Tracks

Advantages of Canonicalization:– More efficient retrieval and comparison operations– Enables StarTrack to maintain a list of non-duplicate tracks

10/9/12 Courtesy: Maya et al.

Page 54: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

54

StarTrack API

Track Collections (TC): Abstract grouping of tracks– Programming Convenience– Implementation Efficiency• Prevent unnecessary client-server message exchanges− Enable delayed evaluation− Enable caching and use of in-memory data structures

Pre-filter tracks Manipulate tracks Fetch tracks

10/9/12 Courtesy: Maya et al.

Page 55: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

55

StarTrack API: Track Collections

TC JoinTrackCollections (TC tCs[], bool removeDuplicates) TC SortTracks (TC tC, SortAttribute attr) TC TakeTracks(TC tC, int count) TC GetSimilarTracks (TC tC, Track refTrack, float simThreshold) TC GetPassByTracks (TC tC, Area[] areas) TC GetCommonSegments(TC tC, float freqThreshold)

Track[] GetTracks (TC tC, int start, int count)

Manipulation

Retrieval

Creation TC MakeCollection(GroupCriteria criteria, bool removeDuplicates)

10/9/12 Courtesy: Maya et al.

Page 56: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

56

API Usage: Ride-Sharing Application// get user’s most popular track in the morning

TC myTC = MakeCollection(“name = Maya”, [0800 1000], true);TC myPopTC = SortTracks(myTC, FREQ);Track track = GetTracks(myPopTC, 0, 1);

// find tracks of all fellow employeesTC msTC = MakeCollection(“name.Employer = MS”, [0800 1000], true);

// pick tracks from the community most similar to user’s popular trackTC similarTC = GetSimilarTracks(msTC, track, 0.8);Track[] similarTracks = GetTracks(similarTC, 0, 20);

// Verify if each track is frequently traveled by its respective ownerUser[] result = FindOwnersOfFrequentTracks(similarTracks);

10/9/12 Courtesy: Maya et al.

Page 57: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

57

Efficient Implementation of Operations

• StarTrack exploits redundancy in tracks for efficient retrieval from database– Set of non-duplicate tracks per user– Separate table of unique coordinates

• StarTrack builds specialized in-memory data-structures to accelerate the evaluation of some operations– Quad-Trees for geographic range searches– Track Trees for similarity searches

10/9/12 Courtesy: Maya et al.

Page 58: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

58

S1-4

S5 S6-7

Track Similarity

Tracks A, B

s1

s2

s3

s4

s5

Track D

s8

s9

Track C

s6 s7

Limited database support for computing track similarity

SIM (A ,C )=¿S1−4∨ ¿|S1−4|+|S5|+¿S6−7∨¿¿

¿

SIM (A , B)=¿S1−5∨ ¿|S1−5|

¿

10/9/12 Courtesy: Maya et al.

Page 59: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

59

Track Tree

s1 s2 s3 s4 s5 s6 s7 s8 s9

S1-2 S6-7 S8-9

S1-3

S1-4

S1-5Tracks A, B

s1

s2

s3

s4

s5

Track Ds8

s9

Track Cs6 s7 1) Create leaf nodes for all

segments

2) Merge nodes based on # of tracks that go through adjacent segments

10/9/12 Courtesy: Maya et al.

Page 60: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

60

Evaluation• Performance of our Track Tree approach• Performance of 2 sample applications– Ride-sharing– Personalized Driving Directions

• Configuration– Synthetically generated tracks– Up to 9 StarTrack Servers + 3 Database Servers– Server Configuration:

• 2.6 GHz AMD Opteron Quad-Core Processors• 16 GB RAM

10/9/12 Courtesy: Maya et al.

Page 61: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

61

Evaluation: Track Tree• Evaluation of GetSimilarTracks

• Alternative approaches:– Database filteringPre-filter tracks that intersect ref track at database– In-memory filteringPre-filter tracks that intersect ref track in memory – In-memory brute forceCompute similarity between each track and ref track in memory

10/9/12 Courtesy: Maya et al.

Page 62: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

62

Get Similar Tracks – Query Time

0 10 20 30 40 50 60 70 80 90 1000.1

1

10

100

1000

10000

Number of tracks (thousands)

Que

ry T

ime

(ms)

Track Tree

In-Memory Filtering

In-Memory Brute Force

Database Filtering

10/9/12 Courtesy: Maya et al.

Page 63: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

63

Track Tree Construction Costs

0 20 40 60 80 1000

30

60

90

120

150

180

Number of Tracks (thousands)

Time (s)

Memory (MB)

10/9/12 Courtesy: Maya et al.

Page 64: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

64

Performance of ApplicationsRide Sharing

- Track Collection on multiple users- Calls to GetSimilarTracks- 30 requests/s at about 170 ms

Personalized Driving Directions

- Track Collection for single user at a time- Calls to GetCommonSegments- 30 requests/s at about 100 ms (uncached)- 250 requests/s at about 55 ms (cached)

0 10 20 30 400

100200300400500600

Request Rate (per second)

Resp

onse

Tim

e (m

s)

150 175 200 225 2500

20406080

100120

Request Rate (per second)

Resp

onse

Tim

e (m

s)

10/9/12 Courtesy: Maya et al.

Page 65: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

65

Related Work• Management of tracks has been studied by the database

community– Storage of tracks as 3-dimensional objects – Specialized indexing schemes (Quad-Trees, R-Trees, etc.)

• CarTel Project (MIT) – Provides an infrastructure for collecting traces, relying on a relational database using spatial queries

• Access and sharing of data in StarTrack is similar to that provided by social networks, where users’ data is shared by applications; Similar access control policies could be employed to ensure privacy in StarTrack.

10/9/12 Courtesy: Maya et al.

Page 66: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

66

Summary

• StarTrack is a scalable service designed to manage tracks and facilitate the construction of track-based applications

• Important Design Features– Canonicalization of Tracks– API based on Track Collections– Use of Novel Data Structures

10/9/12 Courtesy: Maya et al.

Page 67: Cellular Networks and Mobile Computing COMS 6998-11, Fall 2012

Cellular Networks and Mobile Computing (COMS 6998-11)

67

Questions?

10/9/12