Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
D0103v1.doc Version 1 6.7.2003<br />
The parameters are described in the following table.<br />
Table 54: Log Message Specification<br />
Parameter Format AVP Code Remarks<br />
Logger-Id Octetstring 5101<br />
Unique identity of the entitiy<br />
which logs the events<br />
Log-Time Octetstring 5102<br />
The timestamp when the event<br />
is logged<br />
Event-Id Unsigned32 5103<br />
Identifies uniquely the event<br />
that is being logged<br />
User-Name UTF8String (in NAI format) 1 The identity of the user<br />
Care -of-Address Octetstring 5105 The IPv6 address of the MN<br />
DSCP Unsigned32 5107<br />
Destination-Address Octetstring 5106 The IPv6 address of the CN<br />
Result-Code Unsigned32 268<br />
The response code returned by<br />
the AAAC Server respectively<br />
the QoS Broker<br />
Table 55: Message description<br />
The following table shows the valid Event-Id.<br />
Event<br />
Event-Id<br />
Availability 1<br />
User-Registration Request 11<br />
User-Registration Response 12<br />
Service-Authorization Request 21<br />
Service-Authorization Response 22<br />
Table 56: Valid Events<br />
5.2.8 Bearer Management<br />
This chapter is based on the service authorization section, adapting the message flow to the Radio<br />
Gateway specificities.<br />
Basically, before sending packets from MN to RG, a radio bearer must be opened. The radio bearer will<br />
have a specific Radio QoS traffic class, which will determine its physical properties. The mapping<br />
between the packet DSCP and this Radio QoS traffic class is performed by the QoS Broker.<br />
D0103v1.doc 164 / 168