Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

System & Method for centralized directory containing personal information, and travel information for a traveller

IP.com Disclosure Number: IPCOM000029456D
Original Publication Date: 2004-Jun-29
Included in the Prior Art Database: 2004-Jun-29
Document File: 3 page(s) / 58K

Publishing Venue

IBM

Abstract

Given a traveller, it is difficult and sometimes impossible to have access to this person, to deliver any packet, Fax, directly contact him, even using mail box. So this article will outline how to define a traveller profile allowing different types of services to access it, including insurance services, security services, ... The profile would be centralized in a Directory, for example a LDAP server, and then provide, in an electronic way the required information.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 3

System & Method for centralized directory containing personal information, and travel information for a traveller

Given a traveller, it is difficult and sometimes impossible to have access to this person, to deliver any packet, Fax, directly contact him, even using mail box.

    The system & method is to define a traveller profile allowing different types of services to access it, including be insurance services, security services, communication services or transportation. People are travelling more and more, and when they arrive in a new hotel or residency, during the check in, they have to always provide the same kind of information, such as name, postal address, member card, passport number. The system & method centralizes this information in a Directory, for example a LDAP server, and then provide, in an electronic way, the reception of the hotel. The information could also be sent by Fax or by e-mail.

LDAP Background General-purpose design LDAP was designed to be a general-purpose directory, it had to be extensible. It uses an object-oriented, inheritance-based schema definition, which provides for easy extension to any reasonable use. There is a base schema as part of the LDAP specification, and there are other de facto standards for various services.

Protocol simplicity One of the most important aspects of LDAP development, and that which caused it to be adopted in lieu of DAP, is that it is a simple protocol and is relatively simple to implement and work with. This is borne out be the fact that LDAP is supported by most major programming languages.

Distributed architecture Using data replication, it is possible to replicate all or part of an LDAP directory to physically separate locations, which allows for highly-available data and puts the data as close as necessary to the client. Using referrals, data mastery of portions of the directory can be distributed across different LDAP servers.

Security A large focus of LDAP development has been security, with version 3 of the LDAP protocol bringing significant improvements. There are three basic aspects of securing the information in a directory: access, authentication, and authorization (AAA, or Triple-A). Access is the ability to connect to a service and can be restricted based on details like time of day or IP address, authentication is the ability to prove to the service that a client is a valid user, and authorization is the service providing or denying specific rights or capabilities to the client. LDAP actually provides the ability to encrypt, to control over access and authentication, with AAA through Access Control Lists (ACLs). Open standard
Because LDAP is an open standard maintained by the IETF, it can be used by any developers, companies, or administrators without fear of being tied to proprietary protocols or specific vendors, and allows the choice of implementation to be based on project details rather than interoperability concerns. Thi...