Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
MN RG AR QoSB
1
2
4
3
5
6
7
Figure 103: Radio Bearer Signalling
No. Message Content / Parameters Remarks
1 1 st packet of a CoA, Destination, DSCP
given application
with a given DSCP
not yet in use
2 Dummy ping CoA, Destination, DSCP
packet generated
by RG with
parameters of
message 1
3 QoS Broker query CoA, Destination, DSCP
for
QoS
instructions
This packet will not be sent to the RG, but
its characteristics (CoA / Destination /
DSCP) transmitted to the RG.
This packet will be discarded by the AR, but
its information (CoA, Destination, DSCP)
will be used to query the QoS Broker.
The QoS Broker will consult the NVUP
information for that user, and if the DSCP is
allowed by the SLA, the QoS Broker
configures the AR to allow forwarding of
the next matching packets (DSCP, Dest,
CoA).
4 AR QoS BW, priority, DSCP, CoA If there are not enough resources available in
Configuration
that AR, nothing will be done.
5 RG QoS DSCP, Radio QoS traffic The QoS Broker performs the mapping
Configuration class to use, status
between DSCP codes and Radio QoS
classes.
6 Establishment of the radio bearer between
7 1 st packet,
transmitted by the
MN
MT and RG, using Radio QoS traffic class.
CoA, DSCP, CN Address This packet will initiate the resource
reservation on the CN access network.
Table 57: Message Specification
In the case of an incoming packet from AR to MT, this flow is simplified: messages 1 – 2 – 3 are not
used; but the rest of the process is the same.
5.2.9 Interface AR and RG
The interface between the AR and the RG has been described in details in the Radio Gateway software
Architecture.
D0103v1.doc 165 / 168