eu-DOMAIN

A detailed description of the technological infrastructure is shown in Figure 1.

Each location has installed one or more service gateways. They form dynamic, local intelligence clusters and access points to existing local area networks, through which, two-way communication with other installations in the building (e.g. alarm systems, energy control, etc.) can be established.

Third party Service Provides may deliver web services via the eu-DOMAIN network and the service gateway directly to the user. The services can be either one-way service delivery or two-way interactive services. The provisioning platform also allows for provisioning of traditional one-way HTML content and for advanced semantic web searches.

Technical Features
The eu-DOMAIN infrastructure contains the following main components:

• Ambient Intelligence platform: Distribution of location specific, application specific and network intelligence pools and definition of information object classes is developed based on system architectural and security analysis.
• Web services provisioning and content delivery: Development of web provisioning tools, protocols, negotiation tools, billing and other components of the service and content delivery chain.
• Client architecture: Client architecture involves development and prototyping of service gateways for buildings and vehicles with location and application specific intelligence pools.
• Communication infrastructure: A prototype communication infrastructure will be created for use in system integration and demonstration of the eu-DOMAIN platform.
• Server architecture: A powerful eu-DOMAIN server park will provide the main network Ambient Intelligence functionality.

The following are the key principles on which the eu-DOMAIN architecture was based.

To support modifiability, the core of the eu-DOMAIN platform is a domain model which initially models basic concepts of eu-DOMAIN-based application. This domain model may be adapted – by extending a corresponding meta-model – to add new concepts supporting specific application domains. The domain model defines all application domain-related features, like data and operations, so that every part of the system is able to access them. The Domain Model is defined mainly as follows:

• The data structures, using XML Schema
• The operations, as Web Services, described by its WSDL documents
• One or more UDDI taxonomies used to catalogue and find the services. For example, there can be a taxonomy to catalogue the eu-DOMAIN domain model, and other for each one of the Content Providers. Or also different taxonomies for different eu-DOMAIN subsystems can be devised

When possible, functionality and data is accessible as web services. Externally, this supports interoperability and modifiability by easing integration with external content providers. Internally, this enables interoperability between implementation platforms such as Microsoft .NET and Java. Service Oriented Architecture is an approach to implement IT systems in which the basic element of the system is a service, which in turn is a software component offering some operations to the rest of the system.

To support heterogeneous devices, terminals, and content providers, the eu-DOMAIN is divided into three tiers containing devices, terminals and gateways, and servers and external services respectively.  Briefly, the tiers have the following responsibilities:

• The Device Tier contains devices which are sensors, actuators, and processors installed at a location. An example of a Device is a blood pressure monitoring device which is accessible via a serial line over Bluetooth. Devices communicate with the eu-DOMAIN platform solely through their connection to a Gateway. The eu-DOMAIN platform does not assume any specific protocols on behalf of devices.
• The Client Tier contains terminals and service gateways. Terminals provide the user interface to the eu-DOMAIN platform through web browsers. An example of a terminal is a PDA. Gateways are dedicated hardware boxes installed at a location. They are the mediator between devices and the Server Tier through physical connections to devices and through a network connection to the Server Tier, and are responsible for integrating devices into the platform.
• The Server Tier contains servers implementing the eu-DOMAIN platform functionality per se. Multiple eu-DOMAIN applications (such as facility management from different service providers or facility management and eHealth services) may run on the same eu-DOMAIN server deployment.

“Intelligence”, in the sense of being able to make decisions based on previous activities, data reported from different sensors, and the location of objects and people, is central to eu-DOMAIN and the eu-DOMAIN architecture. Intelligence is coupled to objects, people, and locations.

The application intelligence is responsible for managing the interpretation of input to the eu-DOMAIN components and evaluating actions for these inputs.

The main functional features of the application intelligence components can be summarised as follows:

• Multiple applications are able to run in parallel without posing any integration restrictions, i.e. the applications are able to be fully independent of each other.
• Events are able to “remember” previous states.
• Application intelligence can easily be extendable and provide a rich set of functions for managing the different inputs.
• It is possible to express the application intelligence using rule based programming. • Since the application intelligence is tailored for each application it uses well known languages for expressing the rules.
• The rule engine provides more than basic rule execution functionality. It also provides functionality for, e.g., prioritising rules and pruning.
• It is possible to extend the rule language with eu-DOMAIN-specific constructs.

The main component inside the Application Intelligence is the Rule Engine. This is where operative rules are evaluated against session events. The Rule Engine is programmable using an XSL-T transformation sheet.

Expected Project Outcomes

From the range of potentially exploitable products, three main outcomes were prioritized:

The eu-DOMAIN AmI service platform: The eu-DOMAIN Ambient Intelligence (AmI) Service Platform is a web based service that offers all eu-DOMAIN functionalities to service providers as described in Figure 2.

Figure 2 Logical overview of eu-DOMAIN service platform

In-JeT’s role in the project

In-JeT was the Technical Manager of the eu-DOMAIN project. We also participated in the workpackage on requirements engineering, conducted scenario thinking workshops and developed future scenarios for the use of the eu-DOMAIN platform. In-JeT was also in charge of the workpackage on validation and uptake. In this workpackage we validated the project outcomes together with users and developed market entry strategies and business models for healthcare and industrial products. On the dissemination and exploitation side, we were editors of the eu-DOMAIN website.

Partners

1. C International Ltd., UK (Coordinator)
2. Innova S.p.A., Italy
3. In-JeT ApS, Denmark (Technical Coordinator)
4. University of Aarhus, Dept. of Computer Science, Denmark
5. Foundation for Research and Technology – Hellas, Greece
6. CNet Svenska AB, Sweden
7. T-connect s.r.l., Italy
8. Software AG, Systems Group, Spain
9. Telefónica I+D, Spain
10. Grundfos Management A/S, Danmark
11. Eastern Birmingham Primary Care Trust, UK
12. LIWAS ApS (subsupplier)
13. ACit GmbH (subsupplier)

Funding

Co-funded by the European Commission 6th Framework Programme for Research