Changes between Version 19 and Version 20 of TestbedOverview
- Timestamp:
- Oct 7, 2010, 11:28:38 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TestbedOverview
v19 v20 21 21 22 22 The main Framework Components include: 23 * '''[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 RPI interface from REPs, and can be queried by Resource Users and other components over the RLI interface. Resource directories between different SENSEI domains can also be peered.23 * '''[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. 24 24 25 * Semantic Quert Resolver 26 * Entity Directory 27 * Execution Manager 25 * '''[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). 26 27 * '''[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. 28 29 * '''[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. 28 30 29 31 The main Comminity Management Components include: 30 * AAA 31 * Privacy and Billing 32 33 * '''[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. 34 35 * '''[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. 32 36 33 37 * '''TODO: Figure showing server components''' 34 38 35 39 The main Resource Interaction Components include: 36 * REPs 37 * Gateways 38 * Embedded REPs 39 * Management GUI 40 41 * '''Resource End Points''' - A Resource End Point (REP) is any implementation of SENSEI RAI interfaces accessible via a URL described in the Resource Directory. Several different REP implementations are provided by SENSEI. The [wiki:RpOverview Java REP Framework] is an extisible Java SE implementation of SENSEI interfaces. 42 43 * '''Gateways''' - In order to expose resources hosted in embedded sensor networks, entities called gateways are used to provide those resources as SENSEI REPs (thus implementing the RPI and RAI interfaces). In a native SENSEI island the sensor nodes also support IP, but realize a subset of the SENSEI interfaces with the Constrained Application Protocol (CoAP). The [wiki:NativeGateway Native SENSEI Gateway] proxies these resources to the rest of the SENSEI system. A [wiki:ZigbeeGateway ZigBee Gateway] has also been provided to expose ZigBee nodes in an island to the SENSEI system. 44 45 * '''Embedded REPs''' - Two different embedded REP implementations, compatible with the Native Gateway, have been realized. The [wiki:node-contiki Contiki REP] provides an implementation of the embedded REP for the popular Contiki embedded operating system. The [wiki:node-tinyos TinyOS REP] provides an realization of the embedded REP for the popular TinyOS on a TelosB compatible hardware platform. 46 47 * '''Management GUI''' - 40 48 41 49