diameter-db

The "3GPP-Device-Trigger-Request" Diameter command code

The "3GPP-Device-Trigger-Request" Diameter command uses the command code "8388643".

It has the REQ and PXY bits.

It is part of the 3GPP T4 application.

It is defined in the 3GPP TS 29.337: Diameter-based T4 Interface for communications with packet data networks and applications 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)
277 Auth-Session-State Enumerated Required (1)
264 Origin-Host DiameterIdentity Required (1)
296 Origin-Realm DiameterIdentity Required (1)
293 Destination-Host DiameterIdentity Optional (up to 1)
283 Destination-Realm DiameterIdentity Required (1)
3102 User-Identifier Grouped Required (1)
3309 SM-RP-SMEA OctetString Required (1)
3004 Payload OctetString Required (1)
2401 Serving-Node Grouped Optional (up to 1)
2406 Additional-Serving-Node Grouped Optional
3007 Reference-Number Unsigned32 Optional (up to 1)
448 Validity-Time Unsigned32 Optional (up to 1)
3006 Priority-Indication Enumerated Optional (up to 1)
3202 Trigger-Action Unsigned32 Optional (up to 1)
628 Supported-Features Grouped Optional
284 Proxy-Info Grouped Optional
282 Route-Record DiameterIdentity Optional
Its CCF definition is the following:
< 3GPP-Device-Trigger-Request > ::= < Diameter-Header: 8388643, REQ, PXY, 16777311 > 
< Session-Id >
[ DRMP ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ User-Identifier }
{ SM-RP-SMEA }
{ Payload }
[ Serving-Node ]
* [ Additional-Serving-Node ]
[ Reference-Number ]
[ Validity-Time ]
[ Priority-Indication ]
[ Trigger-Action ]
* [ Supported-Features ]
* [ Proxy-Info ]
* [ Route-Record ]





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