Changes between Version 6 and Version 7 of TITAN


Ignore:
Timestamp:
Oct 22, 2010, 9:13:06 AM (14 years ago)
Author:
mirco.rossi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TITAN

    v6 v7  
    77[[PageOutline(2-3,Table of Contents,inline)]]
    88== Introduction ==
    9 Titan is a framework for the distributed execution of context recognition algorithms within Body Area Network (BANs). The framework‘s central component is running on a mobile phone or a PC. It organizes and controls the execution of task plans which are distributed on the mobile phone, body worn devices, and smart objects in the environment of its user. A task plan describes what resources (sensors, processing units, and actuators) are needed to achive a specific context/activity recognition goal.
     9Titan is a framework for the distributed execution of context recognition algorithms within Body Area Network (BANs). The framework‘s central component is running on a PC or mobile phone. It organizes and controls the execution of service graphs which are distributed on the mobile phone, body worn devices, and smart objects in the environment of its user. A service graph describes what resources (sensors, processing units, and actuators) are needed to achive a specific context/activity recognition goal (similar to the SENSEI TaskPlan).
    1010
    11 The Titan framework integrates SENSEI’s resource-oriented approach to distributed processing within the sensor islands themselves. Similar to the Execution Manager (EM), Titan is coordinating the execution of a plan, monitors the executed session and adapts distributed processing to local changes in the network topology by reconfiguring sensor nodes within subseconds. Extending the concepts of the Execution Manager to the sensor islands enables to execute and monitor a plan more locally. The support of local task operation enforces the stability of the execution in case of failure or disconnection (Locality). 
     11The Titan framework integrates SENSEI’s resource-oriented approach to distributed processing within the sensor islands themselves. Similar to the Execution Manager (EM), Titan is coordinating the execution of a service graph, monitors the executed session and adapts distributed processing in the network topology by reconfiguring sensor nodes within subseconds. Extending the concepts of the Execution Manager to the sensor islands enables to execute and monitor a service graph more locally. The support of local service operation enforces the stability of the execution in case of failure or disconnection (Locality). 
    1212
    1313== Architectural Overview ==
    14 The Figure below shows the Integration of the Titan framework in the SENSEI system. The framework’s central component is both implemented in Java SE and Java ME (Personal Profile). It runs on every device supporting one of these two Java platforms. It has been tested on a Windows XP/Vista/7 Machine and on a HTC Touch HD running a Windows Mobile 6.1 OS and IBM J9 Java Virtual Machine. The Titan framework supports by now the following types of nodes: wireless sensor nodes running on TinyOS with the CC2420 radio stack (we used TelosB nodes), any device supporting Java ME Personal Profile (Java Titan Node), and Bluetooth nodes with a custom protocol.
     14The Figure below shows the Integration of the Titan framework in the SENSEI system. The framework’s central component is both implemented in Java SE and Java ME (Personal Profile). It runs on every device supporting one of these two Java platforms. It has been tested on a Windows XP/Vista/7 Machine and on a HTC Touch HD running a Windows Mobile 6.1 OS and IBM J9 Java Virtual Machine. The Titan framework supports by now the following types of nodes: wireless sensor nodes running on TinyOS with the CC2420 radio stack (we used TelosB nodes), any device supporting Java ME Personal Profile (Java Titan Node), and Bluetooth sensor nodes using RFCOMM to send the sensor data.
    1515
    1616[[Image(titan_arch.png, 40%, center)]]
    1717
    18 Every sensor node in the Titan framework provides certain resources (e.g. sensor, actuator, or processing resource). Titan is periodically scanning the network and registering the resources of the available nodes in the Titan Resource Directory. All context/activity recognition tasks are defined by a task plan (also called resource graph) in the Titan Task Plan Database. Titan can start such a recognition task, by mapping the task plan to the available resources found in the Titan Resource Directory.
     18Every sensor node in the Titan framework provides certain sercives(e.g. sensor, actuator, or processing resource). Titan is scanning the network and registering the services of the available nodes in the Titan Service Directory. All context/activity recognition tasks are defined by a service grpah in the Titan Service Graph Directory. Titan can start such a recognition task, by mapping the service graph to the available services found in the Titan Services Directory.
    1919
    20 The Titan framework is integrated as a Java REP to the SENSEI system. It registers to the SENSEI system as a Resource through the Resource Publish Interface (RPI). A Resource User (RU) can access Titan through the Resource Access Interface (RAI). Depending on the executed task plan, the Resource User receives data from the Titan Framework.
     20The Titan framework is integrated as a REP to the SENSEI system. It registers to the SENSEI system as a Resource through the Resource Publish Interface (RPI). A Resource User (RU) can access Titan through the Resource Access Interface (RAI). Depending on the executed service graph, the Resource User receives data from the Titan Framework.
    2121
    2222
    … …  
    3535The Java ME PersonalProfile code for the TITAN Network Manager is located in the TITAN_Mobile directory (Eclipse project). The TITAN Network Manager can be started by the ch.ethz.ee.ife.sensei.titanmanager.titan.mobile.TitanMobile::main(String[] args) method.
    3636
     37Currently the Java ME version cannot be directly accessed as a Titan REP. Workaround: Set-up a Titan Network Manager on a PC and connect the Java ME version as a "Titan Node Pool" (see bellow).
     38
    3739=== Installing the Nodes
     40
     41==== Titan Node Pool
     42
    3843
    3944==== TelosB Sensor Nodes
    … …  
    7580}}}
    7681
     82==== Bluetooth Sensors
     83
    7784
    7885== Test the TITAN Framewok==