White Paper RWI reference model
From RwiWiki
Contents |
[edit] Overview
Many of you have been working in the past few years on different aspects of a RWI, be it on suitable architecture or underlying information models, protocols and mechanisms addressing one or the other facet of the overall problem domain. It is now time to put these efforts together and synthesise an overall architectural reference model for the RWI, which correctly represents the problem domain wide variety of applications we are dealing with. This would allow a first stock taking of current EC activities in this area, and provide a solid basis for further upcoming research and respective calls in the coming years to build upon. Consequently we would kindly ask you to share (reference) architectures you have developed in your projects with us. We do not ask you to disclose confidential information. Based on your inputs, we will define a draft architecture capturing the standard architectural design paradigm of components, communication and configurations (CCC):
- Components (static architecture): What are the major components in the architecture and how are they related?
- Communication (dynamic architecture): What are the main interactions / protocols among the components?
- Configurations (deployment): Which components / communications are present in a number of representative domains / applications? What are the valid configurations?
This will have to be done at all levels and specifically has to take cross-layer issues into account where they cannot be completely separated (separation of concerns). Other aspects that we try to capture are:
- What are the design goals that have motivated your design?
- What are underlying design principles that you found valuable or you came up with for the design of your architecture?
[edit] Status
The first phase of the work towards a RWI reference architecture was successfully completed by the end of 2010:
- A number of contributing projects was identified (ASPIRE, FZI Living Lab AAL, IoT-A, PECES, SemsorGrid4Env, SENSEI, SPITFIRE). Other projects are invited to contribute - please see How to get involved.
- The initial RWI reference architecture was defined (to be published as a book chapter, An Architectural Blueprint for a Real-World Internet, in the upcoming FIA 2011 book, Future Internet: Achievements and Promising Technology. The book chapter documents the mapping between the contributing projects and the initial RWI reference architecture.
The second phase of the work will finalize the reference architecture synthesized into a white paper and is expected to complete by the end of 2011.
[edit] How to get involved
Please send us your input, e.g. in form of a document, addressing the above questions or upload the documents on the RWI wiki space.
[edit] Timeline
The timeline for the 2011 RWI reference architecture is as follows:
- 01.01.11-31.12.11: Bi-weekly telephone conferences of the editorial team
- 30.11.11: First draft of white paper for comments
- 31.12.11: Final version of white paper
[edit] Contributions area
Contributions from the following projects:
- SENSEI: The SENSEI Real World Internet Architecture Download pdf
- ASPIRE:
- PECES:
- PROSENSE:
- 4WARD:
- C-CAST: Architecture paper Download pdf
- WISEBED: Architecture design deliverable [1]
- Section 1, pp 5 - 12
- Section 3.3, pp 69 - 80
- CuteLoop: Concept (pdf)
- iSurf: Overview (ppt)
- AWISSENET: Brochure (pdf)
- PARADISO:
- RESERVOIR:
- PrimeLife: Deliverables from "Activity 6: Infrastructure"
- ECRYPT II:
- M-Ciudad: Context Awareness in MCiudad: Download pdf
- VICTORY:
- SemSorGrid4Env: Architecture deliverable [2] Download pdf
