Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
FDTariffS2
UNSIGNED
TINYINT
UNSIGNED
TariffID (i.e. tariff) that
will be applied, when a
customer will use this
service in his FOREIGN
domain.
... No
… … … … …
FDTariffS6
TINYINT
UNSIGNED
... No
Table 20: Generic Moby Dick User Profile
In order to allow a user the usage of applications and services in both, home network and foreign
network, information about the user is necessary and services for authentication, authorization and
accounting purpose. An AAAC service provides the needed information to authenticate a user and to
establish authorized network service for a user. A main idea of a distributed AAAC service is that all data
associated with users are stored centralized in the user database. All data in this database associated with
the same user is called user profile of this user.
4.5.1.3 User Profile Distribution
A User Profile generally is stored in a repository “close” to the AAAC.h server. Within this context,
“closed” means that the AAAC.h server has all access capabilities to this repository required for
Authentication and Authorization process. So an interface to the user profiles is the access over the
AAAC.h to which a user has registered.
After the AAAC.h received an authentication and authorization request over AAA protocol for a usage of
an applications or a network service, the AAAC.h retrieves over this interface all needed information
from the user profile, in order to make a decision. If the decision is successful the home AAAC server
sends in the authentication and authorization response all attributes of the user profiles, which are needed
to provide the service to the user. Usually the authentication and authorization decision is made from
Home AAAC Server (decision enforcement point). Only the result of the decision and configuration data
are send to AAA entity (i.e. AAAC.f), which has generated the authentication and authorization request.
The whole user profile is never sent to other AAA entity for privacy and legal issues. Only AAAC.h has
full knowledge of the user profile.
The conveyance of user profile data over the AAA protocol must be secure. This means that at least data
integrity for the end-to-end communication is guaranteed.
4.5.1.4 User Profile Management
The User Profiles are stored in the user database of users Home Domain and also all management and
maintenance tasks for the user profiles are performed in the home domain. The management and
maintenance tasks involved: to create and to delete user profiles and to add, to modify and to delete static
attributes. The registration process for a new user creates the user profile. It is assumed that this process is
done “offline” and so it is out of the scope of Moby Dick. All these tasks are performed over the
management interface to user database. This interface is not standardized in the AAA infrastructure.
Usually the user database is stored either in database or in directory service. A user has no direct access to
this user profile.
To define and implement the management interface for the user database is out of the scope of the Moby
Dick project.
4.5.1.5 Network View of user Profile (NVUP) - Global SLAs
The following section describes an example NVUP.
Name
Service
Class
Relative
Priority
Service parameters
Typical Usage Description
SIG AF41 2 Unspecified Signalling (network usage)
D0103v1.doc 108 / 168