Re-Auth Command Request

This section describes the Rx application Re-Auth command Request AVPs.

Command details:
  • Command name: Re-Auth
  • Code: 258
  • Proxiable: True
  • MDC name:MtxDiamRxRAMsg
Note: Unless otherwise noted, all AVPs are required and the maximum occurrence is "1".
Table 1. Re-Auth Request
AVP Name AVP Code MDC Field Name

(Struct Name)

 Description

Session-Id

 263

SessionId

Origin-Host

 264

SourceHost

Origin-Realm

 296

SourceRealm

Destination-Realm

 283

DestinationRealm

Destination-Host

 293

DestinationHost

Auth-Application-Id

 258

AuthApplicationId

In a Gx RAR, the AuthApplicationId = 16777238.

Specific-Action

 513

SpecificActionList

 Maximum occurs = 256

DRMP

 301

DiamRoutingMsgPriority

OC-Supported-Features

 621

OcSupportedFeatures

(MtxDiamOcSupportedFeaturesData)

-- OC-Feature-Vector

 622

-- OcFeatureVector

Access-Network-Charging-Identifier

 502

AccessNetworkChargingIdList

(MtxDiamAccessNetworkChargingIdData)

 Maximum occurs = 256

-- Access-Network-Charging-Identifier-Value

 503

-- AccessNetworkChargingIdValue

-- Flows

 510

-- FlowList

(MtxDiamFlowData)

 Maximum occurs = 256

-- -- Media-Component-Number

 518

-- -- MediaComponentId

-- -- Flow-Number

 509

-- -- FlowIdList

 Maximum occurs = 256

-- -- Content-Version

 552

-- -- ContentVersionList

 Maximum occurs = 256

-- -- Final-Unit-Action

 449

-- -- LastUnitAction

-- -- Media-Component-Status

 549

-- -- MediaComponentStatus

Access-Network-Charging-Address

 501

AccessNetworkChargingAddress

AN-GW-Address

 1050

AnGatewayAddressList

 Maximum occurs = 2

AN-Trusted

 1503

AnTrusted

Flows

 510

FlowList

(MtxDiamFlowData)

 Maximum occurs = 256

-- Media-Component-Number

 518

-- MediaComponentId

-- Flow-Number

 509

-- FlowIdList

 Maximum occurs = 256

-- Content-Version

 552

-- ContentVersionList

 Maximum occurs = 256

-- Final-Unit-Action

 449

-- LastUnitAction

-- Media-Component-Status

 549

-- MediaComponentStatus

Subscription-Id

 443

SubscriberIdList

(MtxSubscriberIdData)

 Maximum occurs = 256

-- Subscription-Id-Type

 450

-- Type

-- Subscription-Id-Data

 444

-- Id

Abort-Cause

 500

AbortReason

IP-CAN-Type

 1027

IpCanType

NetLoc-Access-Support

 2824

NetLocAccessSupport

RAT-Type

 1032

RatType

Sponsored-Connectivity-Data

 530

SponsoredConnectivityData

(MtxDiamSponsoredConnectivityDataData)

-- Sponsor-Identity

 531

-- SponsorId

-- Application-Service-Provider-Identity

 532

-- ApplicationServiceProviderId

-- Granted-Service-Unit

 431

-- AuthQuantity

(MtxQuantityData)

-- -- Tariff-Time-Change

 451

-- -- TariffTimeChange

-- -- CC-Time

 420

-- -- ActualDurationQuantity

-- -- CC-Money

 413

-- -- -- Unit-Value

 445

-- -- -- MonetaryQuantity

-- -- -- Currency-Code

 425

-- -- -- MonetaryType

-- -- CC-Total-Octets

 421

-- -- TotalDataQuantity

-- -- CC-Input-Octets

 412

-- -- InDataQuantity

-- -- CC-Output-Octets

 414

-- -- OutDataQuantity

-- -- CC-Service-Specific-Units

 417

-- -- Quantity

-- Used-Service-Unit

 446

-- UsedQuantity

(MtxUsedQuantityData)

In some situations, a Diameter client does not send the CC-Total-Octets AVP because the AVPs in the Used-Service-Unit grouped AVP are optional. If the CC-Total-Octets is not sent, you can configure the Diameter Gateway to set CC-Total-Octets to be the sum of the CC-Input-Octets and the CC-Output-Octets AVPs.

For more information, see the discussion about Diameter total octet calculation.

-- -- Reporting-Reason

 872

-- -- ReportingReason

-- -- Tariff-Change-Usage

 452

-- -- TariffChangeUsage

-- -- CC-Time

 420

-- -- ActualDurationQuantity

-- -- CC-Total-Octets

 421

-- -- TotalDataQuantity

-- -- CC-Input-Octets

 412

-- -- InDataQuantity

-- -- CC-Output-Octets

 414

-- -- OutDataQuantity

-- -- CC-Service-Specific-Units

 417

-- -- Quantity

-- -- Event-Charging-TimeStamp

 1258

-- -- EventChargingTimestampList

 Maximum occurs = 256

-- Sponsoring-Action

 542

-- SponsoringAction

3GPP-User-Location-Info

 22

TgppSubscriberLocationInfo

User-Location-Info-Time

 2812

SubscriberLocationInfoTime

3GPP-MS-TimeZone

 23

TgppDeviceTimeZone
Note:

The 3GPP-MS-TimeZone AVP should contain Binary-Coded Decimal values based upon the 3GPP TS 23.040 specification only. If the AVP does not conform to this rule, you can configure how the AVP is handled.

To configure AVP handling, answer the following question during engine configuration:

"How do you want to handle non-conforming 3GPP-MS-TimeZone AVP values?"

Valid values are:
  • reject — The packet is rejected with a 5004(INVALID_AVP_VALUE).
  • ignore — The AVP is ignored and the appropriate MDC field is not set; the event generated will have a utcOffset value of 0 and an EventTime timezone value of Z (UTC time).
  • process — The value is assumed to be a negative value in two's complement format.

RAN-NAS-Release-Cause

 2819

RanNasReleaseReasonList

 Maximum occurs = 256

3GPP-SGSN-MCC-MNC

 18

TgppSgsnMccMnc

TWAN-Identifier

 29

TwanId

TCP-Source-Port

 2843

TcpSourcePort

UDP-Source-Port

 2806

UdpSourcePort

UE-Local-IP-Address

 2805

DeviceLocalIpAddress

Origin-State-Id

 278

SourceStateId

Class

 25

ClassList

 Maximum occurs = 256

Proxy-Info

 284

ProxyInfoList

(MtxDiamProxyInfoData)

 Maximum occurs = 256

-- Proxy-Host

 280

-- ProxyHost

-- Proxy-State

 33

-- ProxyState

Route-Record

 282

RouteInfoList

 Maximum occurs = 256