System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

To keep the connection to the probe the beacon (see chapter 5.1) is started asa background service (Figure 5.12). This service is started once a successfulconnection is established and sends the beacon to the probe with a frequencydefined in the configuration file. Like the probe the client counts the beaconsthat could not be received during runtime. The frequency <strong>for</strong> sending thebeacon is delayed to minimize the resources needed. Whenever the count <strong>for</strong>missing beacons defined in the configuration file is exceeded, the state of thecommunication will be set to disconnected and the application returns to thelogin view. A received beacon resets the counter to zero.(a) Monitoring the beacon(b) Resetting the beacon counterFigure 5.12: Checking and sending beacon - Diagram a shows theprocess of checking the beacon. A beacon is send untila maximum count is exceeded. If the maximum count isexceeded, the connection state is set to disconnected.Diagram b describes a new beacon received from theprobe. Once a beacon is received the beacon counter isset to zero.Due to the configuration of component threads available, the views displayedon the client are also configured by using a configuration file. To presentthe data even on a mobile device, the navigation style of choice is a tabbednavigation system (Burrell and Sodan, 2006) presenting each view inside asingle tab. Using a tabbed navigation facilitates switching between all offeredviews (Figure 5.13). The developer can decide which view he wants to see andviews not needed are hidden until requested. Also the component dispatcherof the probe only sends a list of component threads accessible by the client.The clients needs to check this list <strong>for</strong> matching views which gets loaded anddisplayed inside the tabbed navigation. For each component thread on theprobe a corresponding view on the client is designed.When the client has successfully connected the initial tab view presents in<strong>for</strong>mationabout the connection and the components offered by the probe. Thestate of the beacon is also displayed. This view will always be created and31
Figure 5.13: Principle of tabbed navigation - On the top several tabscan be select changing the content to be displayed.it is connected to the main dispatcher. The second view is connected to thelogging dispatcher showing all components available <strong>for</strong> logging. Whenever thecurrent tab changes, the client sends a disconnect to the last connected componentthread. After disconnecting a new request is send to the componentthread of the corresponding view (Figure 5.14).Figure 5.14: Disconnect last component and request new component- When the view is changed, the client sends a disconnectcommand to the currently requested componentthread. To request the component thread <strong>for</strong> the newview a connect command is send.32
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: For example a developer can select
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 and 50: 1 2 4 6 8 Listing 6.2: Example of t
Page 51 and 52: TabConfig - The Status ViewThe TabC
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?