diameter-db

The "GCS-Action-Request" Diameter command code

The "GCS-Action-Request" Diameter command is defined by and uses the command code "8388662".

It has the REQ and PXY bits.

It is part of the 3GPP MB2c application.

It is defined in the 3GPP TS 29.468: Group Communication System Enablers for LTE (GCSE_LTE); MB2 reference point; Stage 3 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)
277 Auth-Session-State Enumerated Required (1)
264 Origin-Host DiameterIdentity Required (1)
296 Origin-Realm DiameterIdentity Required (1)
283 Destination-Realm DiameterIdentity Required (1)
293 Destination-Host DiameterIdentity Optional (up to 1)
278 Origin-State-Id Unsigned32 Optional (up to 1)
284 Proxy-Info Grouped Optional
282 Route-Record DiameterIdentity Optional
628 Supported-Features Grouped Required (1)
3509 TMGI-Allocation-Request Grouped Optional (up to 1)
3512 TMGI-Deallocation-Request Grouped Optional (up to 1)
3504 MBMS-Bearer-Request Grouped Optional
932 Restart-Counter Unsigned32 Optional (up to 1)
Its CCF definition is the following:
< GCS-Action-Request > ::= < Diameter-Header: 8388662, REQ, PXY, 16777335 > 
< Session-Id >
[ DRMP ]
{ Auth-Application-Id }
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
[ Destination-Host ]
[ Origin-State-Id ]
* [ Proxy-Info ]
* [ Route-Record ]
{ Supported-Features }
[ TMGI-Allocation-Request ]
[ TMGI-Deallocation-Request ]
* [ MBMS-Bearer-Request ]
[ Restart-Counter ]





Update source Insertion date
3GPP 2026-04-26 07:12
Wireshark 2026-04-26 07:12