Resources
Identity Use Cases & Scenarios.- FIDIS Deliverables.
- Identity of Identity.
- Interoperability.
- Profiling.
- Forensic Implications.
- HighTechID.
- D3.1: Overview on IMS.
- D3.2: A study on PKI and biometrics.
- D3.3: Study on Mobile Identity Management.
- D3.5: Workshop on ID-Documents.
- D3.6: Study on ID Documents.
- D3.7: A Structured Collection on RFID Literature.
- D3.8: Study on protocols with respect to identity and identification – an insight on network protocols and privacy-aware communication.
- D3.9: Study on the Impact of Trusted Computing on Identity and Identity Management.
- D3.10: Biometrics in identity management.
- D3.11: Report on the Maintenance of the IMS Database.
- D3.15: Report on the Maintenance of the ISM Database.
- D3.17: Identity Management Systems – recent developments.
- D12.1: Integrated Workshop on Emerging AmI Technologies.
- D12.2: Study on Emerging AmI Technologies.
- D12.3: A Holistic Privacy Framework for RFID Applications.
- D12.4: Integrated Workshop on Emerging AmI.
- D12.5: Use cases and scenarios of emerging technologies.
- D12.6: A Study on ICT Implants.
- D12.7: Identity-related Crime in Europe – Big Problem or Big Hype?.
- D12.10: Normality Mining: Results from a Tracking Study.
- Privacy and legal-social content.
- Mobility and Identity.
- Other.
- IDIS Journal.
- FIDIS Interactive.
- Press & Events.
- In-House Journal.
- Booklets
- Identity in a Networked World.
- Identity R/Evolution.
D3.1: Overview on IMS
 |
Title: Overview on IMS INTRODUCTION |
 |
Introduction
Developed Structure for the Database on IMS
The following structure is derived from “Identity Management Systems (IMS): Identification and Comparison Study” [ICP03]. Starting with the listed information about implementations of IMS in the study, a database structure was developed and discussed to meet two requirements within the FIDIS Network of Excellence (NoE):
to serve as a basic structure for the database in WP 8.3 (database on IMS)
to serve as guideline for the contributions of the FIDIS-partners in Chapter 5 of this deliverable.
Within the development of this structure, many additional data fields with additional information were discussed, e.g., specific information on identity management, password management and various other mechanisms listed in Chapter 7 of this deliverable.
To get a broader, less deep overview of IMS, these approaches will not be described in the initial version of this deliverable and the first version of the database. After the completion of this work the information available on IMS will be again discussed from the basis of the ideas mentioned above. The results of the final discussion upon the structure and the proposed steps of later development of the structure of the database will be documented within D8.3.
Product Oriented Classification of IMS
Using a more product oriented view we developed a new classification on IMS of the described three types (see Chapter 3 of this deliverable). This view is motivated by the following perception that in general there are three main classes of IMS:
Class 1: Pure IMS which main objective is to support or implement identity management functionality
Class 2: Systems/applications with another core functionality, but basing on and thereby supporting at least some identity management functionality
Class 3: Systems/applications which are independent from identity management functionality, but nevertheless offer at least some identity management functionality as add-on
Additionally there are systems/applications related to IMS that prepare the ground for identity management, e.g., anonymising services or tools for matching privacy preferences as well as some third party services. As they represent important concepts tightly connected to identity management functionality, they will also be briefly mentioned in this document.
Within those classes, subclasses can further be distinguished which focus on specific identity management functionalities meeting the requirements listed in Chapter 6 of this deliverable. They will be listed in Chapter 4.3 and examples of existing IMS for the introduced subclasses will be given.
| |
   |
|
| 8 / 31 |
