System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

6.4.1 Mobile Devices - Playing with AndroidIn this thesis the operation system of choice is the android operation system(see chapter 4.3). Due to limited resources mentioned and the smaller displaysthe style of data presentation on a mobile device is not that easy. At the timeof this thesis, a mobile device is not capable of running a lot of threads atonce with a high frequency. The presentation of data received via the networkneeds to be implemented in a lightweight way. The use of high update ratesor expensive loops must be prevented.Figure 6.5: Class diagram of the mobile client with important elements- The entry point of the mobile client isthe ReSAIDroid class creating all needed elements.Tab activities itself are created and controlled by theTabManager.The client application on the mobile device is called ReSAIdroid (Remote SensorActuator Interface on Android). For the presentation of the data severalviews where implemented. A view on the android plat<strong>for</strong>m is called activity(see chapter 4.3). Each view is used to present a corresponding componentthread on the probe. There are three main elements on the android client.The first element is the starting screen that is used to configure several communicationparameters and executing a login process. The second element isa manager controlling the tabbed navigation and the third element is a selectedtab presenting a view. The mobile client uses a Constants class <strong>for</strong>commands similar constants of the probe. Figure 6.5 shows the main classesimplemented with an example of two tab classes created in the thesis. For43
1 2 4 6 8 Listing 6.2: Example of the view configuration on the client - Eachcomponent has a unique name, a corresponding elementon the probe and a local class name.mapping the component threads of the probe to the views of the client a specialTabComponentMap class was created containing several configuration lists.The classes list contains the connection between a view on the client anda component thread or dispatcher on the probe. This list is used to <strong>for</strong>wardan incoming message to the intended class by checking the TAG the receivedmessage contains. The name of a tab is connected to the corresponding classvia the tabName list. The tabPosition list is used to define the position of aview inside the tab navigation bar. These lists can be defined in the configurationfile placed on the file system of the client. Listing 6.2 shows an exampleof the view configuration inside the configuration file.ReSAIDroid - Starting the ApplicationThe entry point of the client on the mobile device is the ReSAIDroid classpresenting the initial view. This view allows to configure parameters needed<strong>for</strong> the communication by providing corresponding input (Figure 6.6). Atthe bottom of the view a status field displays in<strong>for</strong>mation about connectionstate and errors that occurred. The ReSAIDroid class creates an instance ofthe XmppCommunicator which establishes the connection to the probe. Whenexecuting the login process, the connection to the communication server isinitialized and the client executes the login process with the given parameters.If the connection is established the client sends a connect command to theprobe. A timer monitors the communicator <strong>for</strong> answers of the probe. Whenthe probe acknowledges the connection the beacon is started in background andthe current view switches to the TabManager. If the probe is not responding theconnection attempt is canceled and an error message is displayed in the statusfield. Once the connection is successfully established, the given parametersfrom the different inputs are saved to a local file <strong>for</strong> further connections.44
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: The selected sensors give a good im
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?