Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
User
Profile
Policy
Acctg
DB
Charging
Module
AAAC
Server
DIAMETER
Server
Chrg
DB
Home
Agent
QoS
ASM
QoS
Broker
AAAC
Attendant
Audit
Trail
Auditing
Audit
Rpt
Figure 79: AAAC Server Architecture
The following sections describe the functionalities of each module and the interaction with other
modules within AAAC Server as well as with other MobyDick entities, if any. The interaction comprises
of message sequence and the respective parameters.
4.5.1 User Profile
This document first gives a specification of the user profile as used within the project Moby Dick and in
the second part it defines a set of user profiles to by used within the Moby Dick tests. The goal for these
test users is not to have a complete list of all possible test users with the variety of possibilities of how to
assign parameters to a QoS profile, but to define a well known set of profiles which allow to reproduce
integration tests since they are based on these profiles.
A user profile is a data record of user-specific data; it contains all the data associated with the user, e.g.
username, authentications data, service level agreements, charging info, policies etc.
The user profile is unique, every user who is able to access the network and use some application or
network services must have one user profile.
The information contained in the user profile could be divided in the following different groups:
• User specific information for authentication purpose: Username, password, secret key, etc.
• Service specific information for authorization purpose: Service level agreements, max
bandwidth, etc
• Charging / Tariff specific information for accounting purpose: Tariff group, etc.
4.5.1.1 User Profile Attributes
The information in the user profile is usually represented as attributes.
An attribute is consisting of the name of the attribute and a value, called an Attribute-Value Pair (AVP).
The user profile contains a set of mandatory attributes, which must be present, and a set of optional
attributes, which may be present. Mandatory attributes are set during the creation process of the user
profile with the user value or the default value. In the RADIUS and DIAMETER specification various
attributes are defined.
The user profile contains static attributes. The Static attributes are not being changed during a session.
Dynamic data and accounting data are stored in the session and accounting record. Maybe some (limited)
sections of the user profile could be dynamic. One example of this is a remaining budget in the case of a
prepaid user.
D0103v1.doc 105 / 168