System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

(a) Login screen (b) Waiting <strong>for</strong> response (c) Probe not reachableFigure 6.6: Login view and connecting to the probe - Image a showsthe parameters <strong>for</strong> the configuration of the communication.Image b shows the status indicator while connectingto the probe. Image c shows the error displayed if theconnection could not be established.Beacon - Keep Connected to the ProbeThe Beacon class on the mobile client is implemented as a thread. This allowsto run the beacon in background and in parallel to other activities. The beaconis checked with a lower frequency defined in the config file to reduce theimpact on the system load. The beacon listens to the communication interface<strong>for</strong> incoming beacons send from the probe. The timestamp of the probeis <strong>for</strong>warded to the TabConfig view. The Beacon class monitors the countof missing beacons and resets the counter to zero whenever a new beacon arrives.If the counter <strong>for</strong> maximum missing beacons is exceeded the Beaconthread stops the current activity and switches to the login view. The count ofmaximum missing beacons can be configured in the configuration file.TabManager - Control via Tabbed NavigationWhen a client is successfully connected an instance of the TabManager classis created. The TabManager class extends the TabActivity class and actsas a content holder <strong>for</strong> the different views. Each view implemented as a tabis named with a “Tab” prefix to distinguish a normal view from a tab view.Extending the TabActivity class allows control of the interaction whenever aview is switched. To display the tabs on mobile devices with a lower resolution,the tab navigation can be scrolled horizontally.45
TabConfig - The Status ViewThe TabConfig is the first view created and added to the TabManager. Itdisplays in<strong>for</strong>mation about the connection to the probe, the data from thelast beacon received and the list of the component threads available with theircurrent state. This class is responsible <strong>for</strong> creating and initializing all tabs tobe displayed. For the configuration the TabComponentMap class is referenced.To create tabs the TabConfig requests the list of available components fromthe probe. When the list is received it is compared to the classes list ofthe TabComponentMap. Views matching the list received from the probe areinitialized and added as tab views to the TabManager.(a) Status screen (b) SLAM component (c) laser componentFigure 6.7: Tabbed navigation after login - At the top of each viewthe available tabs are displayed. Image a shows the statusview with in<strong>for</strong>mation about available components onthe probe. Image b shows the data from the SLAM componentand image c the data from the laser component.Component View - A Template <strong>for</strong> Tab ViewsTo present a component thread from the probe a corresponding componentview is defined on the client. The TabTemplate base class created capsulesall the overhead <strong>for</strong> communication with the probe. The idea of the baseclass is to offer simple functionality <strong>for</strong> creating and extending componentviews. Also it provides an implementation skeleton <strong>for</strong> a concrete implementation.When the onResume() method is called the base class requests thecorresponding component thread. Executing the onPause() method triggersa disconnect from the corresponding component thread. The TabTemplateimplements the TabTemplateInterface which <strong>for</strong>ces a concrete componentview to implement the processProperties() method <strong>for</strong> further processing.46
Page 1: Bringing System <s
Page 5 and 6: AbstractSystem <st
Page 7 and 8: output, so each component is offeri
Page 9 and 10: of the system and the decisions mad
Page 11 and 12: created a telelaboratory where two
Page 13 and 14: Like the telelaboratory there is a
Page 15 and 16: with a very high frequency which ma
Page 17 and 18: Due to improving technology the use
Page 19 and 20: Figure 4.1: ToBI platfor</s
Page 21 and 22: Figure 4.3: The architecture behind
Page 23 and 24: Figure 4.5: Typical instant messagi
Page 25 and 26: 5 System DesignThe
Page 27 and 28: Figure 5.2: Message exchange betwee
Page 29 and 30: Figure 5.4: Beacon running between
Page 31 and 32: Figure 5.5: Reading and processing
Page 33 and 34: data and only forw
Page 35 and 36: For example a developer can select
Page 37 and 38: Figure 5.13: Principle of tabbed na
Page 39 and 40: 6.1 The Communication InterfaceThe
Page 41 and 42: 6.2 The Probe - Implementation of t
Page 43 and 44: stop all active processes of the co
Page 45 and 46: is received containing the TAG of t
Page 47 and 48: The selected sensors give a good im
Page 49: 1 2 4 6 8 Listing 6.2: Example of t
Page 53 and 54: Each view adds a listener to the co
Page 55 and 56: LoginController which also observes
Page 57 and 58: tends the JPanel class. The templat
Page 59 and 60: 7 EvaluationIn the previous chapter
Page 61 and 62: Name Description CharactersSingleli
Page 63 and 64: Figure 7.1: Latency of receiving da
Page 65 and 66: For this thesis only a rough estima
Page 67 and 68: Laptop CPU load without Probe CPU l
Page 69 and 70: 8 ConclusionsIn the context of this
Page 71 and 72: 9 OutlookGiven this new tool its no
Page 74: BibliographyBurrell, A. and A. Soda
Page 77 and 78: 6.10 Main classes of the Java clien
Page 79 and 80: AppendixUse CasesUse Case 1: Connec
Page 81 and 82: Use Case 4: Disconnect from compone
Page 83 and 84: Use Case 9: Sending beacon to keep
Page 85 and 86: Figure 9.4: Latency of receiving da

System Introspection for System Analysis on Mobile Devices

Create successful ePaper yourself

Delete template?

Save as template?