Moby Dick Consolidated System Integration Plan
Share Embed Flag
Download ePaper

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan Moby Dick Consolidated System Integration Plan

kt.agh.edu.pl
from kt.agh.edu.pl More from this publisher
27.03.2014 Views

D0103v1.doc Version 1 6.7.2003 PK,FK1,FK2 PK QueueConf DSCP InterfaceBW Bandwidth AgregNumb Borrow MinGRED MaxGRED DropNumb LimitGRED QueueID PK,FK1 FK2 Interface InterfaceID Address Active IsCoreInterface TotalBandwidth RefDisciplineID RefRouterID QueueID PK FK1 Router RouterID Active AvailBW Login Pass EnablePass Name RefBrokerID InterfaceID Broker PK Queue QueueID DSCP DropNumber SentNumber YellowMarked RedMArked Occupation OverLimits BurtSize Rate BufferSize YellowThreshold RedThreshold RefInterfaceID NetService PK DSCP Name RadioClass FK1 QueueID PK,FK1,FK2 PK RadioGW BrokerID Address Active RadioGWID CoreInterf NetInterf RefInterfaceID RefBrokerID Figure 77 - NetworkDB database format 4.4.3.3.2 NetStatus NetStatus database keeps information about the network state. It keeps information about network usage, as well as about authorized user profiles in this network. This database has the tables: - NVUP: Keeps the information about the NVUP of the registered user; - NetService: Has the authorized service list of the registered users; - Reservations: Keeps a list of network services in use by a network user; NVUP NetService Reservations PK NVUPID PK ServiceID PK ReservID NAI CoA Timeout FK1 SourceAddress DestAddress DSCP Timeout RefNVUPID Figure 78: NetStatus database SourceAddress DestAddress DSCP Timeout RefRouterID 4.5 AAAC Server Software Specification This document describes the modules within the AAAC Server and their interaction. D0103v1.doc 104 / 168

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

D0103v1.doc Version 1 6.7.2003<br />

PK,FK1,FK2<br />

PK<br />

QueueConf<br />

DSCP<br />

InterfaceBW<br />

Bandwidth<br />

AgregNumb<br />

Borrow<br />

MinGRED<br />

MaxGRED<br />

DropNumb<br />

LimitGRED<br />

QueueID<br />

PK,FK1<br />

FK2<br />

Interface<br />

InterfaceID<br />

Address<br />

Active<br />

IsCoreInterface<br />

TotalBandwidth<br />

RefDisciplineID<br />

RefRouterID<br />

QueueID<br />

PK<br />

FK1<br />

Router<br />

RouterID<br />

Active<br />

AvailBW<br />

Login<br />

Pass<br />

EnablePass<br />

Name<br />

RefBrokerID<br />

InterfaceID<br />

Broker<br />

PK<br />

Queue<br />

QueueID<br />

DSCP<br />

DropNumber<br />

SentNumber<br />

YellowMarked<br />

RedMArked<br />

Occupation<br />

OverLimits<br />

BurtSize<br />

Rate<br />

BufferSize<br />

YellowThreshold<br />

RedThreshold<br />

RefInterfaceID<br />

NetService<br />

PK DSCP<br />

Name<br />

RadioClass<br />

FK1 QueueID<br />

PK,FK1,FK2<br />

PK<br />

RadioGW<br />

BrokerID<br />

Address<br />

Active<br />

RadioGWID<br />

CoreInterf<br />

NetInterf<br />

RefInterfaceID<br />

RefBrokerID<br />

Figure 77 - NetworkDB database format<br />

4.4.3.3.2 NetStatus<br />

NetStatus database keeps information about the network state. It keeps information about network usage,<br />

as well as about authorized user profiles in this network. This database has the tables:<br />

- NVUP: Keeps the information about the NVUP of the registered user;<br />

- NetService: Has the authorized service list of the registered users;<br />

- Reservations: Keeps a list of network services in use by a network user;<br />

NVUP<br />

NetService<br />

Reservations<br />

PK<br />

NVUPID<br />

PK<br />

ServiceID<br />

PK<br />

ReservID<br />

NAI<br />

CoA<br />

Timeout<br />

FK1<br />

SourceAddress<br />

DestAddress<br />

DSCP<br />

Timeout<br />

RefNVUPID<br />

Figure 78: NetStatus database<br />

SourceAddress<br />

DestAddress<br />

DSCP<br />

Timeout<br />

RefRouterID<br />

4.5 AAAC Server Software Specification<br />

This document describes the modules within the AAAC Server and their interaction.<br />

D0103v1.doc 104 / 168

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!