Changes between Version 17 and Version 18 of TestbedOverview


Ignore:
Timestamp:
Oct 1, 2010, 8:23:43 AM (14 years ago)
Author:
zach
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TestbedOverview

    v17 v18  
    77The figure below shows the deployment architecture of the testbed. The central components of the testbed are deployed on a data center. These components provide services like the resource directory, security along with semantic query interfaces for applications. Embedded devices and sensor networks interact with the SENSEI system using web interfaces for registering and accessing resources. The entity that makes resources on devices or in sensor networks available to SENSEI is called a Resource End Point (REP). Finally, applications can be developed that discover and use these resources. Unlike middleware solutions, SENSEI uses a decoupled approach based on the web architecture. Resources are discovered by making resource directory lookups or semantic queries, but are accessed directly using the resulting URL(s). A management GUI is provided with the central components in order to manage and test the whole system. For more information about the SENSEI architecture, see the [http://www.sensei-project.eu/index.php?option=com_docman&task=doc_download&gid=83&Itemid=49 SENSEI White Paper]. 
    88
    9 [[Image(deployment-highlevel.jpg, 400px)]]
     9[[Image(deployment-highlevel.jpg, 500px)]]
    1010
    1111
    … …  
    1414In the SENSEI project we have identified a large number of technical and business roles played in the machine-to-machine ecosystem. Three of those roles are important when deploying a testbed of the SENSEI system: Resource Providers, System Framework Providers and Resource Users. These are logical roles, and the same entities might play multiple roles. Resource Providers operate the embedded devices and sensor networks used in a SENSEI system. SENSEI Framework Providers host the central components of the SENSEI system, usually located on one or more well-known servers. This Cookbook is organized by these roles played in the system.
    1515
     16 * '''TODO: Figure'''
     17
    1618== System Components ==
    1719
    18  * Framework Components
    19    1. Resource Directory
    20    1. Semantic Quert Resolver
    21    1. Entity Directory
    22    1. Execution Manager
     20The SENSEI system is made up of loosely coupled components which can be categorized by their purpose. Framework Components are hosted by System Framework Providers, and they provide the core functionality of the SENSEI architecture. Community Management Components provide security, authentication, privacy and billing functionality, usually also hosted by System Framework Providers. Resource Interaction Components are used by Resource Providers for making devices and sensor neworks available to the SENSEI system, and by Resource Users for interacting with the SENSEI system.
    2321
    24  * Comminity Management Components
    25    1. AAA
    26    1. Privacy and Billing
     22The main Framework Components include:
     23 * Resource Directory
     24 * Semantic Quert Resolver
     25 * Entity Directory
     26 * Execution Manager
    2727
    28  * Resource Interaction Components
    29    1. REPs
    30    1. Gateways
    31    1. Embedded REPs
    32    1. Management GUI
     28The main Comminity Management Components include:
     29 * AAA
     30 * Privacy and Billing
     31
     32The main Resource Interaction Components include:
     33 * REPs
     34 * Gateways
     35 * Embedded REPs
     36 * Management GUI
     37
    3338
    3439== Main Interfaces ==