diameter-db

The "Message-Process-Request" Diameter command code

The "Message-Process-Request" Diameter command uses the command code "311".

It has the REQ and PXY bits.

It is part of the 3GPP MM10, 3GPP Sh applications.

It is defined in the 3GPP TS 29.140: Multimedia Messaging Service (MMS); MM10 interface based on Diameter protocol; Stage 3 specification.

It contains the following AVPs:

AVP code AVP name AVP type AVP requirement
263 Session-Id UTF8String Fixed (1)
260 Vendor-Specific-Application-Id Grouped Required (1)
277 Auth-Session-State Enumerated Required (1)
264 Origin-Host DiameterIdentity Required (1)
296 Origin-Realm DiameterIdentity Required (1)
293 Destination-Host DiameterIdentity Required (1)
283 Destination-Realm DiameterIdentity Required (1)
55 Event-Timestamp Time Required (1)
1103 Trigger-Event Enumerated Required (1)
1100 Served-User-Identity Grouped Required (1)
1 3GPP-IMSI UTF8String Optional (up to 1)
1104 Sender-Address UTF8String Optional (up to 1)
1105 Initial-Recipient-Address Grouped Required (1)
1110 Originating-Interface Enumerated Required (1)
1114 Service-Key UTF8String Optional (up to 1)
1111 Delivery-Report Enumerated Optional (up to 1)
1112 Read-Reply Enumerated Optional (up to 1)
1113 Sender-Visibility Enumerated Optional (up to 1)
284 Proxy-Info Grouped Optional
282 Route-Record DiameterIdentity Optional
Its CCF definition is the following:
< Message-Process-Request > ::= < Diameter-Header: 311, REQ, PXY > 
< Session-Id >
{ Vendor-Specific-Application-Id }
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
{ Event-Timestamp }
{ Trigger-Event }
{ Served-User-Identity }
[ 3GPP-IMSI ]
[ Sender-Address ]
{ Initial-Recipient-Address }
{ Originating-Interface }
[ Service-Key ]
[ Delivery-Report ]
[ Read-Reply ]
[ Sender-Visibility ]
* [ Proxy-Info ]
* [ Route-Record ]





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