Changes between Version 22 and Version 23 of TestbedOverview


Ignore:
Timestamp:
Oct 21, 2010, 10:27:43 AM (14 years ago)
Author:
zach
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestbedOverview

    v22 v23  
    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(testbed.jpg, 500px)]]
     9[[Image(testbed.png, 500px)]]
    1010
    1111
     
    3333 * '''[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.
    3434
    35 [[Image(server-components.jpg, 350px)]]
     35[[Image(server-components.png, 350px)]]
    3636
    3737The main Resource Interaction Components include: