7.2 Commands
29.2723GPPEvolved Packet System (EPS)Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocolRelease 17TS
7.2.1 Introduction
This clause defines the Command code values and related ABNF for each command described in this specification.
7.2.2 Command-Code values
This clause defines Command-Code values for the S6a/S6d interface application and S13/S13′ interface application as allocated by IANA in the IETF RFC 5516 [32].
Every command is defined by means of the ABNF syntax IETF RFC 2234 [7], according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [61]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [61] shall apply.
The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node.
NOTE: The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with the IETF RFC 6733 [61].
The following Command Codes are defined in this specification:
Table 7.2.2/1: Command-Code values for S6a/S6d
|
Command-Name |
Abbreviation |
Code |
Clause |
|
Update-Location-Request |
ULR |
316 |
7.2.3 |
|
Update-Location-Answer |
ULA |
316 |
7.2.4 |
|
Cancel-Location-Request |
CLR |
317 |
7.2.7 |
|
Cancel-Location-Answer |
CLA |
317 |
7.2.8 |
|
Authentication-Information-Request |
AIR |
318 |
7.2.5 |
|
Authentication-Information-Answer |
AIA |
318 |
7.2.6 |
|
Insert-Subscriber-Data-Request |
IDR |
319 |
7.2.9 |
|
Insert-Subscriber-Data-Answer |
IDA |
319 |
7.2.10 |
|
Delete-Subscriber-Data-Request |
DSR |
320 |
7.2.11 |
|
Delete-Subscriber-Data-Answer |
DSA |
320 |
7.2.12 |
|
Purge-UE-Request |
PUR |
321 |
7.2.13 |
|
Purge-UE-Answer |
PUA |
321 |
7.2.14 |
|
Reset-Request |
RSR |
322 |
7.2.15 |
|
Reset-Answer |
RSA |
322 |
7.2.16 |
|
Notify-Request |
NOR |
323 |
7.2.17 |
|
Notify-Answer |
NOA |
323 |
7.2.18 |
For these commands, the Application-ID field shall be set to 16777251 (application identifier of the S6a/S6d interface application, allocated by IANA).
Table 7.2.2/2: Command-Code values for S13/S13′
|
Command-Name |
Abbreviation |
Code |
Clause |
|
ME-Identity-Check-Request |
ECR |
324 |
7.2.19 |
|
ME-Identity-Check-Answer |
ECA |
324 |
7.2.20 |
For these commands, the Application-ID field shall be set to 16777252 (application identifier of the S13/S13′ interface application, allocated by IANA).
Table 7.2.2/3: Command-Code values for S7a/S7d
|
Command-Name |
Abbreviation |
Code |
Clause |
|
Update-VCSG-Location-Request |
UVR |
8388638 |
7.2.21 |
|
Update-VCSG-Location-Answer |
UVA |
8388638 |
7.2.22 |
|
Insert-Subscription-Data-Request |
IDR |
319 |
7.2.9 |
|
Insert-Subscription-Data-Answer |
IDA |
319 |
7.2.10 |
|
Delete-Subscriber-Data-Request |
DSR |
320 |
7.2.11 |
|
Delete-Subscriber-Data-Answer |
DSA |
320 |
7.2.12 |
|
Reset-Request |
RSR |
322 |
7.2.15 |
|
Reset-Answer |
RSA |
322 |
7.2.16 |
|
Cancel-VCSG-Location-Request |
CVR |
8388642 |
7.2.23 |
|
Cancel-VCSG-Location-Answer |
CVA |
8388642 |
7.2.24 |
For these commands, the Application-ID field shall be set to 16777308 (application identifier of the S7a/S7d interface application, allocated by IANA).
7.2.3 Update-Location-Request (ULR) Command
The Update-Location-Request (ULR) command, indicated by the Command-Code field set to 316 and the "R" bit set in the Command Flags field, is sent from MME or SGSN to HSS.
Message Format
< Update-Location-Request> ::= < Diameter Header: 316, REQ, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ User-Name }
[ OC-Supported-Features ]
*[ Supported-Features ]
[ Terminal-Information ]
{ RAT-Type }
{ ULR-Flags }
[UE-SRVCC-Capability ]
{ Visited-PLMN-Id }
[ SGSN-Number ]
[ Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions ]
[ GMLC-Address ]
*[ Active-APN ]
[ Equivalent-PLMN-List ]
[ MME-Number-for-MT-SMS ]
[ SMS-Register-Request ]
[ SGs-MME-Identity ]
[ Coupled-Node-Diameter-ID ]
[ Adjacent-PLMNs ]
[ Supported-Services ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.4 Update-Location-Answer (ULA) Command
The Update-Location-Answer (ULA) command, indicated by the Command-Code field set to 316 and the ‘R’ bit cleared in the Command Flags field, is sent from HSS to MME or SGSN.
Message Format
< Update-Location-Answer> ::= < Diameter Header: 316, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
[ Result-Code ]
[ Experimental-Result ]
[ Error-Diagnostic ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ OC-Supported-Features ]
[ OC-OLR ]
*[ Load ]
*[ Supported-Features ]
[ ULA-Flags ]
[ Subscription-Data ]
*[ Reset-ID ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.5 Authentication-Information-Request (AIR) Command
The Authentication-Information-Request (AIR) command, indicated by the Command-Code field set to 318 and the ‘R’ bit set in the Command Flags field, is sent from MME or SGSN to HSS.
Message Format
< Authentication-Information-Request> ::= < Diameter Header: 318, REQ, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ User-Name }
[ OC-Supported-Features ]
*[Supported-Features]
[ Requested-EUTRAN-Authentication-Info ]
[ Requested-UTRAN-GERAN-Authentication-Info ]
{ Visited-PLMN-Id }
[ AIR-Flags ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.6 Authentication-Information-Answer (AIA) Command
The Authentication-Information-Answer (AIA) command, indicated by the Command-Code field set to318 and the ‘R’ bit cleared in the Command Flags field, is sent from HSS to MME or SGSN.
Message Format
< Authentication-Information-Answer> ::= < Diameter Header: 318, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
[ Result-Code ]
[ Experimental-Result ]
[ Error-Diagnostic ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ OC-Supported-Features ]
[ OC-OLR ]
*[ Load ]
*[Supported-Features]
[ Authentication-Info ]
[ UE-Usage-Type ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.7 Cancel-Location-Request (CLR) Command
The Cancel-Location-Request (CLR) command, indicated by the Command-Code field set to 317 and the ‘R’ bit set in the Command Flags field, is sent from HSS to MME or SGSN.
Message Format
< Cancel-Location-Request> ::= < Diameter Header: 317, REQ, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
{ User-Name }
*[Supported-Features ]
{ Cancellation-Type }
[ CLR-Flags ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.8 Cancel-Location-Answer (CLA) Command
The Cancel-Location-Answer (CLA) command, indicated by the Command-Code field set to 317 and the ‘R’ bit cleared in the Command Flags field, is sent from MME or SGSN to HSS.
Message Format
< Cancel-Location-Answer> ::= < Diameter Header: 317, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
*[ Supported-Features ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.9 Insert-Subscriber-Data-Request (IDR) Command
The Insert-Subscriber-Data-Request (IDR) command, indicated by the Command-Code field set to 319 and the ‘R’ bit set in the Command Flags field, is sent from HSS or CSS to MME or SGSN.
Message Format when used over the S6a or S6d application:
< Insert-Subscriber-Data-Request> ::= < Diameter Header: 319, REQ, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
{ User-Name }
*[ Supported-Features]
{ Subscription-Data}
[ IDR- Flags ]
*[ Reset-ID ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
Message Format when used over the S7a or S7d application:
< Insert-Subscriber-Data-Request> ::= < Diameter Header: 319, REQ, PXY, 16777308 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
{ User-Name }
*[ Supported-Features ]
*{ VPLMN-CSG-Subscription-Data }
*[ Reset-ID ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.10 Insert-Subscriber-Data-Answer (IDA) Command
The Insert-Subscriber-Data-Answer (IDA) command, indicated by the Command-Code field set to 319 and the ‘R’ bit cleared in the Command Flags field, is sent from MME or SGSN to HSS or CSS.
Message Format when used over the S6a or S6d application:
< Insert-Subscriber-Data-Answer> ::= < Diameter Header: 319, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
*[ Supported-Features ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ IMS-Voice-Over-PS-Sessions-Supported ]
[ Last-UE-Activity-Time ]
[ RAT-Type ]
[ IDA-Flags ]
[ EPS-User-State ]
[ EPS-Location-Information ]
[Local-Time-Zone ]
[ Supported-Services ]
*[ Monitoring-Event-Report ]
*[ Monitoring-Event-Config-Status ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
Message Format when used over the S7a or S7d application:
< Insert-Subscriber-Data-Answer> ::= < Diameter Header: 319, PXY, 16777308 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
*[ Supported-Features ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.11 Delete-Subscriber-Data-Request (DSR) Command
The Delete-Subscriber Data-Request (DSR) command, indicated by the Command-Code field set to 320 and the ‘R’ bit set in the Command Flags field, is sent from HSS or CSS to MME or SGSN.
Message Format when used over the S6a/S6d application:
< Delete-Subscriber-Data-Request > ::= < Diameter Header: 320, REQ, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
{ User-Name }
*[ Supported-Features ]
{ DSR-Flags }
[ SCEF-ID ]
*[ Context-Identifier ]
[ Trace-Reference ]
*[ TS-Code ]
*[ SS-Code ]
[ eDRX-Related-RAT ]
*[ External-Identifier ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
The SCEF-ID shall be present when the flag "Delete monitoring events" in DSR-Flags AVP is set.
Message Format when used over the S7a/S7d application:
< Delete-Subscriber-Data-Request > ::= < Diameter Header: 320, REQ, PXY, 16777308 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
{ User-Name }
*[ Supported-Features ]
{ DSR-Flags }
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.12 Delete-Subscriber-Data-Answer (DSA) Command
The Delete-Subscriber Data-Answer (DSA) command, indicated by the Command-Code field set to 320 and the ‘R’ bit cleared in the Command Flags field, is sent from MME or SGSN to HSS or CSS.
Message Format when used over the S6a/S6d application:
< Delete-Subscriber-Data-Answer> ::= < Diameter Header: 320, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
*[ Supported-Features ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ DSA-Flags ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
Message Format when used over the S7a /S7d application:
< Delete-Subscriber-Data-Answer> ::= < Diameter Header: 320, PXY, 16777308>
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
*[ Supported-Features ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.13 Purge-UE-Request (PUR) Command
The Purge-UE-Request (PUR) command, indicated by the Command-Code field set to 321 and the ‘R’ bit set in the Command Flags field, is sent from MME or SGSN to HSS.
Message Format
< Purge-UE-Request> ::= < Diameter Header: 321, REQ, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ User-Name }
[ OC-Supported-Features ]
[ PUR-Flags ]
*[ Supported-Features ]
[ EPS-Location-Information ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.14 Purge-UE-Answer (PUA) Command
The Purge-UE-Answer (PUA) command, indicated by the Command-Code field set to 321 and the ‘R’ bit cleared in the Command Flags field, is sent from HSS to MME or SGSN.
Message Format
< Purge-UE-Answer> ::= < Diameter Header: 321, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
*[ Supported-Features ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ OC-Supported-Features ]
[ OC-OLR ]
*[ Load ]
[ PUA-Flags ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.15 Reset-Request (RSR) Command
The Reset-Request (RSR) command, indicated by the Command-Code field set to 322 and the ‘R’ bit set in the Command Flags field, is sent from HSS or CSS to MME or SGSN.
Message Format when used over the S6a/S6d application:
< Reset-Request> ::= < Diameter Header: 322, REQ, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
*[ Supported-Features ]
*[ User-Id ]
*[ Reset-ID ]
[ Subscription-Data ]
[ Subscription-Data-Deletion ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
Message Format when used over the S7a /S7d application:
< Reset-Request> ::= < Diameter Header: 322, REQ, PXY, 16777308 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
*[ Supported-Features ]
*[ Reset-ID ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.16 Reset-Answer (RSA) Command
The Reset-Answer (RSA) command, indicated by the Command-Code field set to 322 and the ‘R’ bit cleared in the Command Flags field, is sent from MME or SGSN to HSS or CSS.
Message Format when used over the S6a/S6d application:
< Reset-Answer> ::= < Diameter Header: 322, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
*[ Supported-Features ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
Message Format when used over the S7a /S7d application:
< Reset-Answer> ::= < Diameter Header: 322, PXY, 16777308 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
*[ Supported-Features ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.17 Notify-Request (NOR) Command
The Notify-Request (NOR) command, indicated by the Command-Code field set to 323 and the ‘R’ bit set in the Command Flags field, is sent from MME or SGSN to HSS.
Message Format
< Notify-Request> ::= < Diameter Header: 323, REQ, PXY, 16777251 >
< Session-Id >
[ Vendor-Specific-Application-Id ]
[ DRMP ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ User-Name }
[ OC-Supported-Features ]
*[ Supported-Features ]
[ Terminal-Information ]
[ MIP6-Agent-Info ]
[ Visited-Network-Identifier ]
[ Context-Identifier ]
[Service-Selection]
[ Alert-Reason ]
[ UE-SRVCC-Capability ]
[ NOR-Flags ]
[ Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions ]
[ Maximum-UE-Availability-Time ]
*[ Monitoring-Event-Config-Status ]
[ Emergency-Services ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.18 Notify-Answer (NOA) Command
The Notify-Answer (NOA) command, indicated by the Command-Code field set to 323 and the ‘R’ bit cleared in the Command Flags field, is sent from HSS to MME or SGSN.
Message Format
< Notify-Answer> ::= < Diameter Header: 323, PXY, 16777251 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ OC-Supported-Features ]
[ OC-OLR ]
*[ Load ]
*[ Supported-Features ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.19 ME-Identity-Check-Request (ECR) Command
The ME-Identity-Check-Request (ECR) command, indicated by the Command-Code field set to 324 and the ‘R’ bit set in the Command Flags field, is sent from MME or SGSN to EIR.
Message Format
< ME-Identity-Check-Request > ::= < Diameter Header: 324, REQ, PXY, 16777252 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ Terminal-Information }
[ User-Name ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.20 ME-Identity-Check-Answer (ECA) Command
The ME-Identity-Check-Answer (ECA) command, indicated by the Command-Code field set to 324 and the ‘R’ bit cleared in the Command Flags field, is sent from EIR to MME or SGSN.
Message Format
< ME-Identity-Check-Answer> ::= < Diameter Header: 324, PXY, 16777252 >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Equipment-Status ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.21 Update-VCSG-Location-Request (UVR) Command
The Update-VCSG-Location-Request (UVR) command, indicated by the Command-Code field set to 8388638 and the "R" bit set in the Command Flags field, is sent from MME or SGSN to CSS.
Message Format
< Update-VCSG-Location-Request> ::= < Diameter Header: 8388638, REQ, PXY, >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
{ User-Name }
[ MSISDN ]
[ SGSN-Number ]
*[ Supported-Features ]
{ UVR-Flags }
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.22 Update-VCSG-Location-Answer (UVA) Command
The Update-VCSG-Location-Answer (UVA) command, indicated by the Command-Code field set to 8388638 and the ‘R’ bit cleared in the Command Flags field, is sent from CSS to MME or SGSN.
Message Format
< Update-VCSG-Location-Answer> ::= < Diameter Header: 8388638, PXY, >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
[ Result-Code ]
[ Experimental-Result ]
[ Error-Diagnostic ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
*[ Supported-Features ]
*[ VPLMN-CSG-Subscription-Data ]
[ UVA-Flags ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.23 Cancel-VCSG-Location-Request (CVR) Command
The Cancel-VCSG-Location-Request (CVR) command, indicated by the Command-Code field set to 8388642 and the ‘R’ bit set in the Command Flags field, is sent from CSS to MME or SGSN.
Message Format
< Cancel-VCSG-Location-Request> ::= < Diameter Header: 8388642, REQ, PXY, >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
{ User-Name }
*[Supported-Features ]
{ Cancellation-Type }
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
7.2.24 Cancel-VCSG-Location-Answer (CVA) Command
The Cancel-VCSG-Location-Answer (CVA) command, indicated by the Command-Code field set to 8388642 and the ‘R’ bit cleared in the Command Flags field, is sent from MME or SGSN to CSS.
Message Format
< Cancel-VCSG-Location-Answer> ::= < Diameter Header: 8388642, PXY, >
< Session-Id >
[ DRMP ]
[ Vendor-Specific-Application-Id ]
*[ Supported-Features ]
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]