System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

Figure 4.4: Life-cycle of an android activity - Each activity is initializedby calling the onCreate() method. Inactive activitiesare placed in the background of the operation system[From the Android Developer Guide]A client connects and opens a stream to a server and the server opens a streamback to that client. Once connected the server sends the rooster to the client.The rooster contains all other clients known to the client. When the rooster isloaded, the online presence is delivered to all clients of the rooster. Each clientreturns its own presence. Whenever a message is send to another client, themessage is send to the server which then <strong>for</strong>wards the message to the recipient.If the recipient is not in the domain of the server, the server negotiates a serverto-serverconnection to the recipients server which delivers the message to itsclient. Figure 4.5 shows a typical message session containing elements fromconnecting to a server and exchanging messages.This work uses the message stanza <strong>for</strong> data exchange between the probe andthe client (see chapter 6.1). The data exchanged is primarily using simpledata structures. Most of the data can be packed into an XML structure and17
Figure 4.5: Typical instant messaging session - 1) Establish connectionto the server “Montague.lit“. 2) Request roostercontaining known friend accounts. 3) Make own presenceavailable to contacts of the rooster. 4) Receivepresence of contacts from rooster. 5) Exchange messagewith another contact [From Saint-Andre (2005)]attached to a message stanza. Listing 4.1 shows a typical message stanza.A message contains the name of the sender, the recipient the message is <strong>for</strong>wardedto and the body containing the text to be send. XMPP also allows toextend these message with XML elements.XMPP Library <strong>for</strong> JavaThe probe and the client are both implemented in Java (see chapter 6). Touse XMPP within Java the SMACK 13 library is integrated. SMACK offers anopen source API with functionality <strong>for</strong> connecting to a server and exchangingmessages between different clients. There is also a port of the library <strong>for</strong> theandroid operation system. SMACK allows to extend the message stanza withvalue pairs added as properties.13 http://www.webcitation.org/5wiKn3W0C - SMACK library by ignite realtime18
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: Figure 4.3: The architecture behind
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 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
show all

System Introspection for System Analysis on Mobile Devices

Create successful ePaper yourself

Delete template?

Save as template?