The "Spending-Limit-Answer" Diameter command code
The "Spending-Limit-Answer" Diameter command uses the command code "8388635".
It has the PXY bit.
It is part of the 3GPP Sy application.
It is defined in the 3GPP TS 29.219: Policy and charging control: Spending limit reporting over Sy reference point specification.
It contains the following AVPs:
| AVP code | AVP name | AVP type | AVP requirement |
|---|---|---|---|
| 263 | Session-Id | UTF8String | Fixed (1) |
| 301 | DRMP | Enumerated | Optional (up to 1) |
| 258 | Auth-Application-Id | AppId | Required (1) |
| 264 | Origin-Host | DiameterIdentity | Required (1) |
| 296 | Origin-Realm | DiameterIdentity | Required (1) |
| 268 | Result-Code | Enumerated | Optional (up to 1) |
| 297 | Experimental-Result | Grouped | Optional (up to 1) |
| 621 | OC-Supported-Features | Grouped | Optional (up to 1) |
| 623 | OC-OLR | Grouped | Optional (up to 1) |
| 628 | Supported-Features | Grouped | Optional |
| 2903 | Policy-Counter-Status-Report | Grouped | Optional |
| 281 | Error-Message | UTF8String | Optional (up to 1) |
| 294 | Error-Reporting-Host | DiameterIdentity | Optional (up to 1) |
| 279 | Failed-AVP | Grouped | Optional (up to 1) |
| 278 | Origin-State-Id | Unsigned32 | Optional (up to 1) |
| 292 | Redirect-Host | DiameterURI | Optional |
| 261 | Redirect-Host-Usage | Enumerated | Optional (up to 1) |
| 262 | Redirect-Max-Cache-Time | Unsigned32 | Optional (up to 1) |
| 284 | Proxy-Info | Grouped | Optional |
| 650 | Load | Grouped | Optional |
< Spending-Limit-Answer > ::= < Diameter-Header: 8388635, PXY, 16777302 >
< Session-Id >
[ DRMP ]
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
[ Result-Code ]
[ Experimental-Result ]
[ OC-Supported-Features ]
[ OC-OLR ]
* [ Supported-Features ]
* [ Policy-Counter-Status-Report ]
[ Error-Message ]
[ Error-Reporting-Host ]
[ Failed-AVP ]
[ Origin-State-Id ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ Load ]
| Update source | Insertion date |
|---|---|
| 3GPP | 2026-04-26 07:12 |
| Wireshark | 2026-04-26 07:12 |