Changes between Version 27 and Version 28 of TestbedOverview


Ignore:
Timestamp:
Nov 1, 2010, 11:34:02 AM (14 years ago)
Author:
zach
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TestbedOverview

    v27 v28  
    55The SENSEI Pan-European testbed realizes the SENSEI system for integrating heterogeneous sensor networks with the Internet. This section gives an overview of the testbed deployment, its main components and the roles played by various entities involved with the testbed. Finally, a short description about how the testbed works is given.
    66
    7 The 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]. 
     7The 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 (RD), AAA along with the Semantic Query Resolver (SQR) 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
    99[[Image(testbed.png, 700px)]]
    … …  
    1212== Roles ==
    1313
    14 In 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.
     14In the SENSEI project we have identified a 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
    1616== System Components ==
    … …  
    1919
    2020The main Framework Components include:
    21  * '''[wiki:ResourceDirectory Resource Directory]''' - The Resource Directory acts as the repository about all the resources available in a SENSEI domain. It accepts resource publications over the Resource Publication Interface (RPI) from REPs, and can be queried by Resource Users and other components over the Resource Lookup Interface (RLI). Resource directories between different SENSEI domains can also be peered.
     21 * '''[wiki:ResourceDirectory Resource Directory]''' - The Resource Directory acts as the repository about all the resources available in a SENSEI domain. It accepts resource publications over the Resource Publication Interface (RPI) from REPs, and can be queried by Resource Users and other components over the Resource Lookup Interface (RLI). Resource directories in different SENSEI domains can also be peered.
    2222 
    2323 * '''[wiki:SQR Semantic Quert Resolver]''' - The Semantic Query Resolver provides a higher level interface to the SENSEI system by supporting the search for resources semantically. This is achieved using either simple or language-based queries over the Semantic Query Interface (SQI). 
    … …  
    2525 * '''[wiki:ED Entity Directory]''' - The Entity Directory holds context information about resources, complimenting the Resource Directory. Entity context information is either entered in the ED manually, or built-up automatically each time a REP includes an advanced research description when publishing to the RD.
    2626 
    27  * '''[wiki:ExecutionManager Execution Manager]''' - Rather than simply accessing single resources, the Execution Manager provides a way to specify execution plans, which describe a sequence of resource access or actuation steps.
     27 * '''[wiki:ExecutionManager Execution Manager]''' - The Execution Manager provides a way to specify execution plans, which describe a sequence of resource access or actuation steps.
    2828
    2929The main Comminity Management Components include:
    … …  
    3131 * '''[wiki:Aaa AAA]''' - The SENSEI AAA component provides access control for the entire SENSEI system. This includes both a security token service for providing identities, and a AAA service against which REPs and other components check access control rights for requesting resources. A section on [wiki:RepAaa REP access control] is also provided, describing how to use AAA from a REP.
    3232
    33  * '''[wiki:PrivacyAndBilling Privacy and Billing]''' - The Privacy and Billing component provides and alternative approach to the access control provided by the AAA component. A security token installed in the resource user (a Firefox pliug-in is also provided) is used to authenticate a resource user. In addition, an accounting service is provided, allowing access to be denied also due to insufficient funds.
     33 * '''[wiki:PrivacyAndBilling Privacy and Billing]''' - The Privacy and Billing component provides a complementary approach to the access control provided by the AAA component, with an accounting service that allows access to be denied due to insufficient funds. A security token installed in the resource user (a Firefox plug-in is also provided) is used to authenticate a resource user.
    3434
    3535[[Image(server-components.png, 300px)]]