27.03.2014 Views

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

D0103v1.doc Version 1 6.7.2003<br />

4.5.3.2 Accounting Messages<br />

4.5.3.2.1 The Accounting-Request (ACR)<br />

The Accounting-Request (ACR) command, indicated by the Command-Code field set to 271 and the<br />

Command Flags' 'R' bit set, is sent by a Diameter node (AR), acting as a client, in order to exchange<br />

accounting information with a peer (AAA server).<br />

::= < Diameter Header: 271, REQ, PXY ><br />

< Session-Id ><br />

{ Acct-Application-Id }<br />

{ Origin-Host }<br />

{ Origin-Realm }<br />

{ Destination-Realm }<br />

{ Accounting-Record-Type }<br />

{ Accounting-Record-Number }<br />

[ User-Name ]<br />

[ Accounting-Sub-Session-Id ]<br />

[ Accounting-RADIUS-Session-Id ]<br />

[ Accounting-Multi-Session-Id ]<br />

[ Accounting-Interim-Interval ]<br />

[ Origin-State-Id ]<br />

* [ AVP ]<br />

* [ Proxy -Info ]<br />

* [ Route-Record ]<br />

Session-Id is the session ID generated by the client at the time sending the AA request. Acct-Application-<br />

Id is the IANA assigned identifier.<br />

Origin-Host: Originator of the Diameter message<br />

Origin-Realm: Realm of the originator<br />

Destination-Realm: Destination realm (real of AAAC.h)<br />

Accounting-Record-Type: start, stop or interim<br />

Accounting-Record-Number: Unique number which identifies acc rec within one session starting with 0<br />

for acc start record<br />

The AAAC client may include:<br />

User-name, interim interval,<br />

The Accounting-Interim-Interval will set to a value equal to 3 minutes.<br />

4.5.3.2.2 The Accounting-Answer (ACA)<br />

The Accounting-Answer (ACA) command, indicated by the Command-Code field set to 271 and the<br />

Command Flags' 'R' bit cleared, is used to acknowledge an Accounting-Request command. The<br />

Accounting-Answer command contains the same Session-Id and MAY contains the same Accounting<br />

Description and Usage AVPs that were sent in the Accounting-Request command. If the CMS-Data AVP<br />

was present in the Accounting-Request, the corresponding ACA message MUST include the CMS-Data<br />

AVP signed by the responder to provide strong AVP authentication, which MAY be used for the purposes<br />

of repudiation.<br />

Only the target Diameter Server, known as the home Diameter Server, SHOULD respond with the<br />

Accounting-Answer command.<br />

::= < Diameter Header: 271, PXY ><br />

< Session-Id ><br />

{ Acct-Application-Id }<br />

{ Result-Code }<br />

{ Origin-Host }<br />

{ Origin-Realm }<br />

{ Accounting-Record-Type }<br />

{ Accounting-Record-Number }<br />

[ User-Name ]<br />

[ Accounting-Sub-Session-Id ]<br />

D0103v1.doc 119 / 168

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

Saved successfully!

Ooh no, something went wrong!