Diameter Gy – Re-Auth-Request (RAR) command

Diameter Gy – RAR message format

This section describes the Diameter Gy RAR message format as defined in RFC 6733. Strikethrough formatted AVPs should not appear or are ignored in RAR.

A RAR message triggers an intermediate interrogation (CCR-U) with Reporting-Reason set to ‟Forced Reauthorization”.

 <RAR>  ::= < Diameter Header: 258, REQ, PXY > 
                    < Session-Id > 
                    { Origin-Host } 
                    { Origin-Realm } 
                    { Destination-Realm } 
                    { Destination-Host } 
                    { Auth-Application-Id } 
                    { Re-Auth-Request-Type }  
                    [ User-Name ]
[ Origin-State-Id ]
                  * [ Proxy-Info ]
                  * [ Route-Record ]
                  * [ AVP ]

Diameter Gy – RAR message top level AVPs

Diameter Gy RAR: top level AVP description provides a detailed description for each top level AVP present in a Diameter Gy RAR message.

Table 1. Diameter Gy RAR: top level AVP description
AVP code AVP name Description

258

Auth-Application-Id

Fixed value: 4 = Diameter Credit Control Application

263

Session-id

A session is a logical concept at the application layer that exists between the Diameter client and the Diameter server; it is identified via the Session-Id AVP.

Format:

<DiameterIdentity>;<high 32 bits>;<low 32 bits>

  • <DiameterIdentity> is the configured origin host

  • <high 32 bits> are encoded as the Diameter initialization time (the number of seconds since 1 January, 1970)

  • <low 32 bits> are encoded as a sequentially increasing number starting at 1

Example:

bng.nokia.com;1326398325;1

264

Origin-Host

Diameter Identity. Used as destination host in the next Diameter message.

Example: server.nokia.com

283

Destination-Realm

Diameter Identity.

Example: nokia.com

285

Re-Auth-Request-Type

Values:

0 = Authorize-Only

293

Destination-Host

Diameter Identity.

Example: bng.nokia.com

296

Origin-Realm

Diameter Identity. Used as destination realm in the next Diameter message.

Example: nokia.com

Table 2. Diameter Gy RAR: top level AVP format
AVP code AVP name Standard Data format Flags

258

Auth-Application-Id

RFC 6733/RFC 4006

Unsigned 32

M

263

Session-id

RFC 6733

UTF8 String

M

264

Origin-Host

RFC 6733

Diameter Identity

M

283

Destination-Realm

RFC 6733

Diameter Identity

M

285

Re-Auth-Request-Type

RFC 6733

Enumerated

M

293

Destination-Host

RFC 6733

Diameter Identity

M

296

Origin-Realm

RFC 6733

Diameter Identity

M