Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
3 AA request usr:pwd@domain; BU
4 BU (see Mobile IP BU)
5 BACK (see Mobile IP BACK)
6 AA response 2x key(MN, AR), Profile SubSet, BACK
7a AA response 2x key(MN, AR), Profile SubSet, BACK
7b NVUP dump MN, AR, Profile SubSet (includes timeout)
8 AA response 1x key(MN, AR), Profile SubSet (codes),
BACK
9 Accounting Data CoA, HoAd?, DestIP, DSCP, Time, In/Out
Byte/Packet Counter
10 Accounting Data CoA, HoAd?, DestIP, DSCP, Time, In/Out
Byte/Packet Counter
Table 47: Registration Step 2 messages and Parameters
The protocols used are the same as in step 1.
5.2.2 Session setup and Service authorization
This chapter specifies part of the signalling for establishing a QoS “session”. It deals with authorizing a
flow pass through Moby Dick’s network, providing it QoS and configuring measurement parameters.
Previous phases (Authentication & Registration) are needed for the user to be allowed to send packets but
are not sufficient (except in some possible cases). The further (and last) step needed, “service
authorization”, is described here. Only the QoS Manager of the AR is involved in that process and is the
sole part considered in this chapter. In this section, we assume that registration has already been done and
that the needed subset of the user profile is in the AAAC.f. and this has already sent a subset of this
subset, the NVUP, to the QoSBroker. Also user’s identity is already known to the network and it could
tariff user’s packets. But we recall that the user is not yet authorized to send packets (except for some
possible exceptions).
Note that the notion of flow in these sentences is quite flexible. It represents a set of packets, which
trigger a non-default match on the AR classification unit. In typical terms, this will represent a (CoA,
Destination, DSCP) tuple, but can represent a (CoA, DSCP) or a (Destination, DSCP) tuple.
A service is just the network resources (BW and priority) that a flow can employ. It is identified by the
DSCP of the packets sent by the MN.
When a new service flow enters the access router the following can happen depending on the policy
decisions of the network operator.
• The service has previously been authorized, the AR forwards the packets.
• The service has not previously been authorized but the flow goes to a certain IP address (e.g.
VoIP Server for emergency calls or some predefined SP’s) in the foreign domain. The AR
forwards the flow.
• The service has not previously been authorized, but it has a DSCP=0 (B.E.). The AR either
forwards or stops the flow, according to overall network policy.
• The service has not previously been authorized; the AR begins an authorization process
(described below). If the process succeeds the AR forwards the packets, else it drops the flow.
The following MSC (Message Sequence Chart) applies to the following cases:
• An application starts sending packets. The AR detects a new service flow, it may perform the
following flow authorization.
The process can be summarized as follows:
Note that QoSBroker knows already user profile, as the user has already registered in the
network, and thus is implicitly authorized to use some services. In “session setup” time, the AR contacts
the QoSBroker in order to know about the network availability to allow some resource usage that is
described in the NVUP.
1. MT starts a flow. MT sends some packets to AR;
D0103v1.doc 151 / 168