Changes between Version 21 and Version 22 of TestbedOverview


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

--

Legend:

Unmodified
Added
Removed
Modified

  • TestbedOverview

    v21 v22  
    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, 500px)]]
     9[[Image(testbed.jpg, 500px)]]
    1010
    1111
    … …  
    1313
    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.
    15 
    16  * '''TODO: Figure showing roles'''
    1715
    1816== System Components ==
    … …  
    3533 * '''[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.
    3634
    37  * '''TODO: Figure showing server components'''
     35[[Image(server-components.jpg, 350px)]]
    3836
    3937The main Resource Interaction Components include: