Changes between Version 20 and Version 21 of TestbedOverview

Timestamp:

Oct 8, 2010, 6:27:06 AM (14 years ago)

Author:

zach

Comment:

--

TestbedOverview

@@ -45 +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.  
 
- * '''Management GUI''' -
+ * '''[wiki:RuManagementGui Management GUI]''' - The SENSEI Management GUI is used in order to manage, test and demonstrate a SENSEI system using a set of graphical web interfaces. Although the Management GUI acts as a Resource User in many aspects, it is included as part of the System Provider [wiki:SpVirtualMachine virtual machine] package because it plays an important management role for the framework components.
 
 
 == Main Interfaces ==
+
+Since the SENSEI architecture is designed to be distributed with loosely coupled components, the definition of interfaces between them is important. In this section a short overview is given of the most commonly used SENSEI interfaces. In this realization of the SENSEI system the interfaces are realized using a REST design with HTTP.
  
- * Common Interfaces
-   1. RPI
-   1. RLI
-   1. RAI
-   1. SQI
-   
- * Section on other advanced interfaces
+ * '''Resource Publication Interface (RPI)''' - This interface is provided by a Resource Directory in order for REPs to register, update or remove so-called [wiki:RpResDescription Resource Descriptions]. This publication and maintenance procedure is automatically handled by the Java REP and Gateway implementations.
+
+ * '''[wiki:RuRai Resource Access Interface (RAI)]''' - There is no single resource access interface in the SENSEI architecture, instead each resource description published by a REP includes information about the interface(s) available to access it, for example the URL and interface description. In order for Resource Users to easily access resources, a set of well-known resource interfaces have been defined for sensor, parameter, actuator and code-update resource types.   
+ 
+ * '''[wiki:RuRli Resource Lookup Interface (RLI)]''' - This interface is used by Resource Users and other components (e.g. the SQR) to find Resource Descriptions based on resource ID or other information contained in the Resource Description. 
+ 
+ * '''[wiki:RuSqr Semantic Query Interface (SQI)]''' - This interface is used by Resource Users to query for resources or entities of interest. Instead of using low-level information in resource descriptions as with the RLI, this interface accepts high-level declarative queries. After performing query analysis, one or more resource descriptions are returned. 
+
 
 == How does it work? ==
 
- * How does the testbed work?
+So how does the SENSEI system work in practice? The easiest way to find out is try it for yourself. First a System Provider is needed. There are two options: either the [wiki:SpUsingTestbed Pan-European testbed] can be used or you can host your own system. By default Resource Provider components like the Java REP and Gateways are configured to use the Pan-European testbed. Deploying your own system is also not too difficult, all the needed components including the Management GUI and included in a [wiki:SpVirtualMachine virtual machine image].
+
+Next some resources need to be connected to the system. The Resource User guide includes several different implementaions of resource end points. The easiest way to get started is to use the [wiki:RpRepDeployment Java REP], which creates dummy resources on a standard PC. The Java REP can then be extended with your own resources. If suitable sensor node hardware is available, then the [wiki:NativeGateway Native Gateway] can be used on a PC to interconnect sensor nodes running either [wiki:node-tinyos TinyOS] or [wiki:node-contiki Contiki]. In addition a [wiki:ZigbeeGateway ZigBee Gateway] is provided. 
+
+So how to use the resources now available in the SENSEI system? The easiest way to start is with a simple web browser. Most resources return their value upon an HTTP GET, so entering the URL or the resource in your browser will display the value. The [wiki:RuManagementGui Management GUI] is a more complete way to access resources, along with configuring the SENSEI system. Finally, as resources have simple REST HTTP interfaces, it is straightforward to create your own Resource User that looks up resources using e.g. the RLI interface and then accesses them with their RAI interface.