Changes between Version 12 and Version 13 of TITAN


Ignore:
Timestamp:
Oct 22, 2010, 11:35:49 AM (14 years ago)
Author:
mirco.rossi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TITAN

    v12 v13  
    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 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).
     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 achieve a specific context/activity recognition goal (similar to the SENSEI TaskPlan).
    1010
    1111The 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). 
    … …  
    1616[[Image(titan_arch.png, 40%, center)]]
    1717
    18 Every 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.
     18Every sensor node in the Titan framework provides certain services (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 graph 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
    2020The 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.
    … …  
    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
    37 Currently 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: "Titan Nodes").
     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 below: "Titan Nodes").
    3838
    3939=== Titan Node Pool
    40 A Titan Node Pool hosts a number of Titan Nodes (see below) and is connected to the Titan Newtork Manager through a TCP/IP connection. A Titan Node pool is addressed by a subnet-ID (e.g. ID=1, ID=0 is reserved for the Titan Network Manager), whereas Titan Nodes are adressed by the pool's subnet-ID and thier local ID (e.g. a Titan Node in the subnet 2 and with local ID 100 has a global adress 2100).
     40A Titan Node Pool hosts a number of Titan Nodes (see below) and is connected to the Titan Network Manager through a TCP/IP connection. A Titan Node pool is addressed by a subnet-ID (e.g. ID=1, ID=0 is reserved for the Titan Network Manager), whereas Titan Nodes are addressed by the pool's subnet-ID and thier local ID (e.g. a Titan Node in the subnet 2 and with local ID 100 has a global address 2100).
    4141
    4242==== Set-Up a Framework with Titan Node Pool
    … …  
    4646- in Java ME: start the application by the ch.ethz.ee.ife.sensei.titanmanager.titan.mobile.TitanMobile::main(String[] args) method. In the GUI start the router with the corresponding sub-net ID.
    4747
    48 2. Titan Network Manager: put the hostname of the Titan Node Pool in the ''TitanNodePool_HostNames'' located in the methode ch.ethz.ee.ife.sensei.titanmanager.titan.mobile.TitanMobile::main(String[] args) and start the Network Manager.
     482. Titan Network Manager: put the hostname of the Titan Node Pool in the ''TitanNodePool_HostNames'' located in the method ch.ethz.ee.ife.sensei.titanmanager.titan.mobile.TitanMobile::main(String[] args) and start the Network Manager.
    4949
    5050=== Installing the Nodes
    5151
    5252==== Titan Nodes
    53 Titan Nodes are virtual nodes running on a Java SE VM or Java ME PersonalProfile VM. Similar to the TelosB Sensor nodes, they provide services (e.g. sensors, actuators, or processing resources) for the SENSEI framework. Titan Nodes are hosted by the "Titan Network Manager" or by a "Titan Node Pool". The number of created nodes can be set before starting the Network Manager/Node Pool (see parameter  ''m_node_nr'' in the coresponging main method).The nodes will get ID 100,101,...
     53Titan Nodes are virtual nodes running on a Java SE VM or Java ME PersonalProfile VM. Similar to the TelosB Sensor nodes, they provide services (e.g. sensors, actuators, or processing resources) for the SENSEI framework. Titan Nodes are hosted by the "Titan Network Manager" or by a "Titan Node Pool". The number of created nodes can be set before starting the Network Manager/Node Pool (see parameter  ''m_node_nr'' in the corresponding main method).The nodes will get ID 100,101,...
    5454
    5555==== TelosB Sensor Nodes
    … …  
    8282where ''<ID>'' is in this case ''0'', and '''<COMPORT>''' the CommPort of the pluged-in device (use ''motelist'').
    8383
    84 Repeate the last step to install TITAN on the other nodes. Increase the ID number for every additional node (IDs must be unique!).
     84Repeat the last step to install TITAN on the other nodes. Increase the ID number for every additional node (IDs must be unique!).
    8585To run the Titan Network Manager with TelosB support:
    8686- Connect the Titan Communication Node to the machine, on which the TITAN Network Manager should run.
    … …  
    9393==== Bluetooth Sensors
    9494
    95 Bluetooth Sensors using the RFCOMM protocol to send the sensory data can be connected to the Titan framework. Use the ''BTSensor'' service provided by a Titan Node to get the data of a bluetooth sensor into the framework.
     95Bluetooth Sensors using the RFCOMM protocol to send their sensory data can be connected to the Titan framework. Use the ''BTSensor'' service provided by a Titan Node to get the data of a bluetooth sensor into the framework.
    9696
    9797
    … …  
    100100To test the framework you can use the ResourceUser-Client GUI located in the TitanDesktop Eclipse-Project: ch.ethz.ee.ife.sensei.titanresourceuser.TitanResourceUserMain. Start the TitanREP on a PC or mobile device as described above and run the RU-Client GUI.
    101101
    102 - Browse the TitanREP: Use the RU-Client to browse the TitanREP. All avaiable service graphs (acting as SENSEI Resources) can be shown.
     102- Browse the TitanREP: Use the RU-Client to browse the TitanREP. All available service graphs (acting as SENSEI Resources) can be shown.
    103103- Edit service graphs: A RU can edit/add/delete service graphs from the TitanREP. 
    104104- Start/Stop a service graph: A service graph can be started and stopped by a RU. RU's can subscribe to a running service graph to be notified of the results. Currently TITAN supports no parallel execution of service graphs.