6 Diameter application for Cx interface
29.2293GPPCx and Dx interfaces based on the Diameter protocolProtocol detailsRelease 17TS
This clause specifies a Diameter application that allows a Diameter Multimedia server and a Diameter Multimedia client:
– to exchange location information
– to authorize a user to access the IMS
– to exchange authentication information
– to download and handle changes in the user data stored in the server
The Cx interface protocol is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (http://www.iana.org/assignments/enterprise-numbers) is 10415.
The Diameter application identifier assigned to the Cx/Dx interface application is 16777216 (allocated by IANA).
6.1 Command-Code values
This clause defines Command-Code values for this Diameter application.
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 [28]. Whenever the definition and use of an AVP is not specified in this document, what is stated in IETF RFC 6733 [28] shall apply.
NOTE: As the Diameter commands described in this specification have been defined based on the former specification of the Diameter base protocol, the Vendor-Specific-Application-Id AVP is still listed as a required AVP (an AVP indicated as {AVP}) in the command code format specifications defined in this specification to avoid backward compatibility issues, even if the use of this AVP has been deprecated in the new specification of the Diameter base protocol (IETF RFC 6733 [28]).
The command codes for the Cx/Dx interface application are taken from the range allocated by IANA in IETF RFC 3589 [12] as assigned in this specification. For these commands, the Application-ID field shall be set to 16777216 (application identifier of the Cx/Dx interface application, allocated by IANA).
The following Command Codes are defined in this specification:
Table 6.1.1: Command-Code values
|
Command-Name |
Abbreviation |
Code |
Clause |
|
User-Authorization-Request |
UAR |
300 |
6.1.1 |
|
User-Authorization-Answer |
UAA |
300 |
6.1.2 |
|
Server-Assignment-Request |
SAR |
301 |
6.1.3 |
|
Server-Assignment-Answer |
SAA |
301 |
6.1.4 |
|
Location-Info-Request |
LIR |
302 |
6.1.5 |
|
Location-Info-Answer |
LIA |
302 |
6.1.6 |
|
Multimedia-Auth-Request |
MAR |
303 |
6.1.7 |
|
Multimedia-Auth-Answer |
MAA |
303 |
6.1.8 |
|
Registration-Termination-Request |
RTR |
304 |
6.1.9 |
|
Registration-Termination-Answer |
RTA |
304 |
6.1.10 |
|
Push-Profile-Request |
PPR |
305 |
6.1.11 |
|
Push-Profile-Answer |
PPA |
305 |
6.1.12 |
6.1.1 User-Authorization-Request (UAR) Command
The User-Authorization-Request (UAR) command, indicated by the Command-Code field set to 300 and the ‘R’ bit set in the Command Flags field, is sent by a Diameter Multimedia client to a Diameter Multimedia server in order to request the authorization of the registration of a multimedia user.
Message Format
< User-Authorization-Request> ::= < Diameter Header: 300, REQ, PXY, 16777216 >
< 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 ]
{ Public-Identity }
{ Visited-Network-Identifier }
[ User-Authorization-Type ]
[ UAR-Flags ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.2 User-Authorization-Answer (UAA) Command
The User-Authorization-Answer (UAA) command, indicated by the Command-Code field set to 300 and the ‘R’ bit cleared in the Command Flags field, is sent by a server in response to the User-Authorization-Request command. The Experimental-Result AVP may contain one of the values defined in clause 6.2.
Message Format
< User-Authorization-Answer> ::= < Diameter Header: 300, PXY, 16777216 >
< 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 ]
[ Server-Name ]
[ Server-Capabilities ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.3 Server-Assignment-Request (SAR) Command
The Server-Assignment-Request (SAR) command, indicated by the Command-Code field set to 301 and the ‘R’ bit set in the Command Flags field, is sent by a Diameter Multimedia client to a Diameter Multimedia server in order to request it to store the name of the server that is currently serving the user.
Message Format
<Server-Assignment-Request> ::= < Diameter Header: 301, REQ, PXY, 16777216 >
< 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 ]
*[ Public-Identity ]
[ Wildcarded-Public-Identity ]
{ Server-Name }
{ Server-Assignment-Type }
{ User-Data-Already-Available }
[ SCSCF-Restoration-Info ]
[ Multiple-Registration-Indication ]
[ Session-Priority ]
[ SAR-Flags ]
[ Failed-PCSCF ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.4 Server-Assignment-Answer (SAA) Command
The Server-Assignment-Answer (SAA) command, indicated by the Command-Code field set to 301 and the ‘R’ bit cleared in the Command Flags field, is sent by a server in response to the Server-Assignment-Request command. The Experimental-Result AVP may contain one of the values defined in clause 6.2. If Result-Code or Experimental-Result does not inform about an error, the User-Data AVP shall contain the information that the S-CSCF needs to give service to the user.
Message Format
<Server-Assignment-Answer> ::= < Diameter Header: 301, PXY, 16777216 >
< Session-Id >
[ DRMP ]
{ Vendor-Specific-Application-Id }
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ OC-Supported-Features ]
[ OC-OLR ]
*[ Load ]
*[ Supported-Features ]
[ User-Data ]
[ Charging-Information ]
[ Associated-Identities ]
[ Loose-Route-Indication ]
*[ SCSCF-Restoration-Info ]
[ Associated-Registered-Identities ]
[ Server-Name ]
[ Wildcarded-Public-Identity ]
[ Priviledged-Sender-Indication ]
[ Allowed-WAF-WWSF-Identities ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.5 Location-Info-Request (LIR) Command
The Location-Info-Request (LIR) command, indicated by the Command-Code field set to 302 and the ‘R’ bit set in the Command Flags field, is sent by a Diameter Multimedia client to a Diameter Multimedia server in order to request name of the server that is currently serving the user.
Message Format
<Location-Info-Request> ::= < Diameter Header: 302, REQ, PXY, 16777216 >
< Session-Id >
[ DRMP ]
{ Vendor-Specific-Application-Id }
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Destination-Host ]
{ Destination-Realm }
[ Originating-Request ]
[ OC-Supported-Features ]
*[ Supported-Features ]
{ Public-Identity }
[ User-Authorization-Type ]
[ Session-Priority ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.6 Location-Info-Answer (LIA) Command
The Location-Info-Answer (LIA) command, indicated by the Command-Code field set to 302 and the ‘R’ bit cleared in the Command Flags field, is sent by a server in response to the Location-Info-Request command. The Experimental-Result AVP may contain one of the values defined in clause 6.2.
Message Format
<Location-Info-Answer> ::= < Diameter Header: 302, PXY, 16777216 >
< 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 ]
[ Server-Name ]
[ Server-Capabilities ]
[ Wildcarded-Public-Identity ]
[ LIA-Flags ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.7 Multimedia-Auth-Request (MAR) Command
The Multimedia-Auth-Request (MAR) command, indicated by the Command-Code field set to 303 and the ‘R’ bit set in the Command Flags field, is sent by a Diameter Multimedia client to a Diameter Multimedia server in order to request security information.
Message Format
< Multimedia-Auth-Request > ::= < Diameter Header: 303, REQ, PXY, 16777216 >
< Session-Id >
[ DRMP ]
{ Vendor-Specific-Application-Id }
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
[ Destination-Host ]
{ User-Name }
[ OC-Supported-Features ]
*[ Supported-Features ]
{ Public-Identity }
{ SIP-Auth-Data-Item }
{ SIP-Number-Auth-Items }
{ Server-Name }
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.8 Multimedia-Auth-Answer (MAA) Command
The Multimedia-Auth-Answer (MAA) command, indicated by the Command-Code field set to 303 and the ‘R’ bit cleared in the Command Flags field, is sent by a server in response to the Multimedia-Auth-Request command. The Experimental-Result AVP may contain one of the values defined in clause 6.2.
Message Format
< Multimedia-Auth-Answer > ::= < Diameter Header: 303, PXY, 16777216 >
< Session-Id >
[ DRMP ]
{ Vendor-Specific-Application-Id }
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ OC-Supported-Features ]
[ OC-OLR ]
*[ Load ]
*[ Supported-Features ]
[ Public-Identity ]
[ SIP-Number-Auth-Items ]
*[SIP-Auth-Data-Item ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.9 Registration-Termination-Request (RTR) Command
The Registration-Termination-Request (RTR) command, indicated by the Command-Code field set to 304 and the ‘R’ bit set in the Command Flags field, is sent by a Diameter Multimedia server to a Diameter Multimedia client in order to request the de-registration of a user.
Message Format
<Registration-Termination-Request> ::= < Diameter Header: 304, REQ, PXY, 16777216 >
< Session-Id >
[ DRMP ]
{ Vendor-Specific-Application-Id }
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ User-Name }
[ Associated-Identities ]
*[ Supported-Features ]
*[ Public-Identity ]
{ Deregistration-Reason }
RTR-Flags ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.10 Registration-Termination-Answer (RTA) Command
The Registration-Termination-Answer (RTA) command, indicated by the Command-Code field set to 304 and the ‘R’ bit cleared in the Command Flags field, is sent by a client in response to the Registration-Termination-Request command. The Experimental-Result AVP may contain one of the values defined in clause 6.2.
Message Format
<Registration-Termination-Answer> ::= < Diameter Header: 304, PXY, 16777216 >
< Session-Id >
< Session-Id >
[ DRMP ]
{ Vendor-Specific-Application-Id }
[ Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
[ Associated-Identities ]
*[ Supported-Features ]
*[ Identity-with-Emergency-Registration ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.11 Push-Profile-Request (PPR) Command
The Push-Profile-Request (PPR) command, indicated by the Command-Code field set to 305 and the ‘R’ bit set in the Command Flags field, is sent by a Diameter Multimedia server to a Diameter Multimedia client in order to update the subscription data and for SIP Digest authentication the authentication data of a multimedia user in the Diameter Multimedia client whenever a modification has occurred in the subscription data or digest password that constitutes the data used by the client.
Message Format
< Push-Profile-Request > ::= < Diameter Header: 305, REQ, PXY, 16777216 >
< Session-Id >
[ DRMP ]
{ Vendor-Specific-Application-Id }
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Host }
{ Destination-Realm }
{ User-Name }
*[ Supported-Features ]
[ User-Data ]
[ Charging-Information ]
[ SIP-Auth-Data-Item ]
[ Allowed-WAF-WWSF-Identities ]
*[ AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.1.12 Push-Profile-Answer (PPA) Command
The Push-Profile-Answer (PPA) command, indicated by the Command-Code field set to 305 and the ‘R’ bit cleared in the Command Flags field, is sent by a client in response to the Push-Profile-Request command. The Experimental-Result AVP may contain one of the values defined in clause 6.2.
Message Format
< Push-Profile-Answer > ::= < Diameter Header: 305, PXY, 16777216 >
< Session-Id >
[ DRMP ]
{ Vendor-Specific-Application-Id }
[Result-Code ]
[ Experimental-Result ]
{ Auth-Session-State }
{ Origin-Host }
{ Origin-Realm }
*[ Supported-Features ]
*[ AVP ]
[ Failed-AVP ]
*[ Proxy-Info ]
*[ Route-Record ]
6.2 Result-Code AVP values
This clause defines new result code values that must be supported by all Diameter implementations that conform to this specification. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and Result-Code AVP shall be absent.
6.2.1 Success
Result codes that fall within the Success category are used to inform a peer that a request has been successfully completed.
6.2.1.1 DIAMETER_FIRST_REGISTRATION (2001)
The HSS informs the I-CSCF that:
– The user is authorized to register this public identity;
– A S-CSCF shall be assigned to the user.
6.2.1.2 DIAMETER_SUBSEQUENT_REGISTRATION (2002)
The HSS informs the I-CSCF that:
– The user is authorized to register this public identity;
– A S-CSCF is already assigned and there is no need to select a new one.
6.2.1.3 DIAMETER_UNREGISTERED_SERVICE (2003)
The HSS informs the I-CSCF that:
– The public identity is not registered but has services related to unregistered state;
– A S-CSCF shall be assigned to the user.
6.2.1.4 DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED (2004)
The HSS informs to the S-CSCF that:
– The de-registration is completed;
– The S-CSCF name is not stored in the HSS.
6.2.1.5 Void
6.2.2 Permanent Failures
Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again.
6.2.2.1 DIAMETER_ERROR_USER_UNKNOWN (5001)
A message was received for a user or a wildcarded identity that is unknown.
6.2.2.2 DIAMETER_ERROR_IDENTITIES_DONT_MATCH (5002)
A message was received with a public identity and a private identity for a user, and the server determines that the public identity does not correspond to the private identity.
6.2.2.3 DIAMETER_ERROR_IDENTITY_NOT_REGISTERED (5003)
A query for location information is received for a public identity that has not been registered before. The user to which this identity belongs cannot be given service in this situation.
6.2.2.4 DIAMETER_ERROR_ROAMING_NOT_ALLOWED (5004)
The user is not allowed to roam in the visited network.
6.2.2.5 DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED (5005)
The identity has already a server assigned and the registration status does not allow that it is overwritten.
6.2.2.6 DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED (5006)
The authentication scheme indicated in an authentication request is not supported.
6.2.2.7 DIAMETER_ERROR_IN_ASSIGNMENT_TYPE (5007)
The identity being registered has already the same server assigned and the registration status does not allow the server assignment type or the Public Identity type received in the request is not allowed for the indicated server-assignment-type.
6.2.2.8 DIAMETER_ERROR_TOO_MUCH_DATA (5008)
The volume of the data pushed to the receiving entity exceeds its capacity.
NOTE: This error code is also used in 3GPP TS 29.329 [11].
6.2.2.9 DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA (5009)
The S-CSCF informs HSS that the received subscription data contained information, which was not recognised or supported.
6.2.2.10 Void
6.2.2.11 DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011)
A request application message was received indicating that the origin host requests that the command pair would be handled using a feature which is not supported by the destination host.
6.2.2.12 DIAMETER_ERROR_SERVING_NODE_FEATURE_UNSUPPORTED (5012)
This error is used when the HSS supports the P-CSCF-Restoration-mechanism feature, but none of the user serving node(s) supports it, as described by 3GPP TS 23.380 [24] clause 5.4.
6.3 AVPs
6.3.0 General
The following table describes the Diameter AVPs defined by 3GPP for the Cx interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415) if not otherwise indicated.
Table 6.3.0.1: Diameter Multimedia Application AVPs
|
AVP Flag rules |
||||||||
|
Attribute Name |
AVP Code |
Clause defined |
Value Type |
Must |
May |
Should not |
Must not |
May Encr. |
|
Visited-Network-Identifier |
600 |
6.3.1 |
OctetString |
M, V |
No |
|||
|
Public-Identity |
601 |
6.3.2 |
UTF8String |
M, V |
No |
|||
|
Server-Name |
602 |
6.3.3 |
UTF8String |
M, V |
No |
|||
|
Server-Capabilities |
603 |
6.3.4 |
Grouped |
M, V |
No |
|||
|
Mandatory-Capability |
604 |
6.3.5 |
Unsigned32 |
M, V |
No |
|||
|
Optional-Capability |
605 |
6.3.6 |
Unsigned32 |
M, V |
No |
|||
|
User-Data |
606 |
6.3.7 |
OctetString |
M, V |
No |
|||
|
SIP-Number-Auth-Items |
607 |
6.3.8 |
Unsigned32 |
M, V |
No |
|||
|
SIP-Authentication-Scheme |
608 |
6.3.9 |
UTF8String |
M, V |
No |
|||
|
SIP-Authenticate |
609 |
6.3.10 |
OctetString |
M, V |
No |
|||
|
SIP-Authorization |
610 |
6.3.11 |
OctetString |
M, V |
No |
|||
|
SIP-Authentication-Context |
611 |
6.3.12 |
OctetString |
M, V |
No |
|||
|
SIP-Auth-Data-Item |
612 |
6.3.13 |
Grouped |
M, V |
No |
|||
|
SIP-Item-Number |
613 |
6.3.14 |
Unsigned32 |
M, V |
No |
|||
|
Server-Assignment-Type |
614 |
6.3.15 |
Enumerated |
M, V |
No |
|||
|
Deregistration-Reason |
615 |
6.3.16 |
Grouped |
M, V |
No |
|||
|
Reason-Code |
616 |
6.3.17 |
Enumerated |
M, V |
No |
|||
|
Reason-Info |
617 |
6.3.18 |
UTF8String |
M, V |
No |
|||
|
Charging-Information |
618 |
6.3.19 |
Grouped |
M, V |
No |
|||
|
Primary-Event-Charging-Function-Name |
619 |
6.3.20 |
DiameterURI |
M, V |
No |
|||
|
Secondary-Event-Charging-Function-Name |
620 |
6.3.21 |
DiameterURI |
M, V |
No |
|||
|
Primary-Charging-Collection-Function-Name |
621 |
6.3.22 |
DiameterURI |
M, V |
No |
|||
|
Secondary-Charging-Collection-Function-Name |
622 |
6.3.23 |
DiameterURI |
M, V |
No |
|||
|
User-Authorization-Type |
623 |
6.3.24 |
Enumerated |
M, V |
No |
|||
|
User-Data-Already-Available |
624 |
6.3.26 |
Enumerated |
M, V |
No |
|||
|
Confidentiality-Key |
625 |
6.3.27 |
OctetString |
M, V |
No |
|||
|
Integrity-Key |
626 |
6.3.28 |
OctetString |
M, V |
No |
|||
|
Supported-Features |
628 |
6.3.29 |
Grouped |
V |
M |
No |
||
|
Feature-List-ID |
629 |
6.3.30 |
Unsigned32 |
V |
M |
No |
||
|
Feature-List |
630 |
6.3.31 |
Unsigned32 |
V |
M |
No |
||
|
Supported-Applications |
631 |
6.3.32 |
Grouped |
V |
M |
No |
||
|
Associated-Identities |
632 |
6.3.33 |
Grouped |
V |
M |
No |
||
|
Originating-Request |
633 |
6.3.34 |
Enumerated |
M,V |
No |
|||
|
Wildcarded-Public-Identity |
634 |
6.3.35 |
UTF8String |
V |
M |
No |
||
|
SIP-Digest-Authenticate |
635 |
6.3.36 |
Grouped |
V |
M |
No |
||
|
Digest-Realm |
104 NOTE 3 |
6.3.37 |
UTF8String |
M |
V |
No |
||
|
Digest-Algorithm |
111 NOTE 3 |
6.3.39 |
UTF8String |
M |
V |
No |
||
|
Digest-QoP |
110 NOTE 3 |
6.3.40 |
UTF8String |
M |
V |
No |
||
|
Digest-HA1 |
121 NOTE 3 |
6.3.41 |
UTF8String |
M |
V |
No |
||
|
UAR-Flags |
637 |
6.3.44 |
Unsigned32 |
V |
M |
No |
||
|
Loose-Route-Indication |
638 |
6.3.45 |
Enumerated |
V |
M |
No |
||
|
SCSCF-Restoration-Info |
639 |
6.3.46 |
Grouped |
V |
M |
No |
||
|
Path |
640 |
6.3.47 |
OctetString |
V |
M |
No |
||
|
Contact |
641 |
6.3.48 |
OctetString |
V |
M |
No |
||
|
Subscription-Info |
642 |
6.3.49 |
Grouped |
V |
M |
No |
||
|
Call-ID-SIP-Header |
643 |
6.3.49.1 |
OctetString |
V |
M |
No |
||
|
From-SIP-Header |
644 |
6.3.49.2 |
OctetString |
V |
M |
No |
||
|
To-SIP-Header |
645 |
6.3.49.3 |
OctetString |
V |
M |
No |
||
|
Record-Route |
646 |
6.3.49.4 |
OctetString |
V |
M |
No |
||
|
Associated-Registered-Identities |
647 |
6.3.50 |
Grouped |
V |
M |
No |
||
|
Multiple-Registration-Indication |
648 |
6.3.51 |
Enumerated |
V |
M |
No |
||
|
Restoration-Info |
649 |
6.3.52 |
Grouped |
V |
M |
No |
||
|
Session-Priority |
650 |
6.3.56 |
Enumerated |
V |
M |
No |
||
|
Identity-with-Emergency-Registration |
651 |
6.3.57 |
Grouped |
V |
M |
No |
||
|
Priviledged-Sender-Indication |
652 |
6.3.58 |
Enumerated |
V |
M |
No |
||
|
LIA-Flags |
653 |
6.3.59 |
Unsigned32 |
V |
M |
No |
||
|
OC-Supported-Features |
621 NOTE 4 |
6.3.60 |
Grouped |
M, V |
No |
|||
|
OC-OLR |
623 NOTE 4 |
6.3.61 |
Grouped |
M, V |
No |
|||
|
Initial-CSeq-Sequence-Number |
654 |
6.3.62 |
Unsigned32 |
V |
M |
No |
||
|
SAR-Flags |
655 |
6.3.63 |
Unsigned32 |
V |
M |
No |
||
|
Allowed-WAF-WWSF-Identities |
656 |
6.3.64 |
Grouped |
V |
M |
No |
||
|
WebRTC-Authentication-Function-Name |
657 |
6.3.65 |
UTF8String |
V |
M |
No |
||
|
WebRTC-Web-Server-Function-Name |
658 |
6.3.66 |
UTF8String |
V |
M |
No |
||
|
DRMP |
301 NOTE 5 |
6.3.67 |
Enumerated |
M, V |
No |
|||
|
Load |
NOTE 6 |
6.3.68 |
Grouped |
M, V |
No |
|||
|
RTR-Flags |
659 |
6.3.69 |
Unsigned32 |
V |
M |
No |
||
|
P-CSCF-Subscription-Info |
660 |
6.3.70 |
Grouped |
V |
M |
No |
||
|
Registration-Time-Out |
661 |
6.3.71 |
Time |
V |
M |
No |
||
|
Alternate-Digest-Algorithm |
662 NOTE 7 |
6.3.72 |
UTF8String |
V |
M |
No |
||
|
Alternate-Digest-HA1 |
663 NOTE 7 |
6.3.73 |
UTF8String |
V |
M |
No |
||
|
Failed-PCSCF |
664 |
6.3.74 |
Grouped |
V |
M |
No |
||
|
PCSCF-FQDN |
665 |
6.3.75 |
DiameterIdentity |
V |
M |
No |
||
|
PCSCF-IP-Address |
666 |
6.3.76 |
Address |
V |
M |
No |
||
|
NOTE 1: The AVP header bit denoted as ‘M’, indicates whether support of the AVP is required. The AVP header bit denoted as ‘V’, indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [28]. NOTE 1a: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. NOTE 2: Depending on the concrete command. NOTE 3: The value of these attributes is defined in IETF RFC 4590 [20]. NOTE 4: The value of these attributes is defined in IETF RFC 7683 [23]. NOTE 5: The value of this attribute is defined in IETF RFC 7944 [26]. NOTE 6: The value of this attribute is defined in IEFT RFC 8583 [27]. NOTE 7: The Alternate-Digest-HA1 AVP is defined in the same way as Digest-HA1 AVP in accordance with IETF RFC 7616 [29]. If the Alternate-Digest-HA1 AVP is present, the Digest-HA1 AVP shall also be present and the Digest-HA1 AVP shall contain the MD5 hash. The algorithm of the Alternate-Digest-HA1 AVP shall be determined by the Alternate-Digest-Algorithm AVP. |
||||||||
6.3.1 Visited-Network-Identifier AVP
The Visited-Network-Identifier AVP is of type OctetString. This AVP contains an identifier that helps the HSS to identify the visited network (e.g. the visited network domain name). Coding of octets is H-PLMN operator specific. The I-CSCF maps a received P-Visited-Network-ID onto an Octet String value that is consistently configured in I-CSCF and HSS to uniquely identify the visited network.
6.3.2 Public-Identity AVP
The Public-Identity AVP is of type UTF8String. This AVP contains the public identity of a user in the IMS. The syntax of this AVP corresponds either to a SIP URL (with the format defined in IETF RFC 3261 [3] and IETF RFC 2396 [4]) or a TEL URL (with the format defined in IETF RFC 3966 [8]). Both SIP URL and TEL URL shall be in canonical form, as described in 3GPP TS 23.003 [13].
6.3.3 Server-Name AVP
The Server-Name AVP is of type UTF8String. This AVP contains a SIP-URL (as defined in IETF RFC 3261 [3] and IETF RFC 2396 [4]), used to identify a SIP server (e.g. S-CSCF name).
6.3.4 Server-Capabilities AVP
The Server-Capabilities AVP is of type Grouped. This AVP contains information to assist the I-CSCF in the selection of an S-CSCF.
AVP format
Server-Capabilities ::= <AVP header: 603 10415>
*[Mandatory-Capability]
*[Optional-Capability]
*[Server-Name]
*[AVP]
6.3.5 Mandatory-Capability AVP
The Mandatory-Capability AVP is of type Unsigned32. Each value included in this AVP can be used to represent a single determined mandatory capability or a set of capabilities of an S-CSCF, as described in 3GPP TS 29.228 [1] (clause 6.7).
6.3.6 Optional-Capability AVP
The Optional-Capability AVP is of type Unsigned32. Each value included in this AVP can be used to represent a single determined optional capability or a set of capabilities of an S-CSCF, as described in 3GPP TS 29.228 [1] (clause 6.7).
6.3.7 User-Data AVP
The User-Data AVP is of type OctetString. This AVP contains the user data required to give service to a user. The exact content and format of this AVP is described in 3GPP TS 29.228 [1].
6.3.8 SIP-Number-Auth-Items AVP
The SIP-Number-Auth-Items AVP is of type Unsigned32.
When used in a request, the SIP-Number-Auth-Items indicates the number of authentication vectors the S-CSCF is requesting. This can be used, for instance, when the client is requesting several pre-calculated authentication vectors. In the answer message, the SIP-Number-Auth-Items AVP indicates the actual number of SIP-Auth-Data-Item AVPs provided by the Diameter server.
6.3.9 SIP-Authentication-Scheme AVP
The Authentication-Scheme AVP is of type UTF8String and indicates the authentication scheme used in the authentication of SIP messages. The following values are defined:
– "Digest-AKAv1-MD5": it indicates IMS-AKA authentication scheme.
NOTE 1: The S-CSCF uses the "Digest-AKAv1-MD5" authentication scheme towards the HSS for Digest-AKAv1 and Digest-AKAv2 versions. E.g. digest algorithms "AKAv1-MD5" and "AKAv2-SHA-256" require from the HSS the same procedures i.e. the same authentication information: random number RAND, authentication token AUTN, expected response XRES, cipher key CK and integrity key IK.
NOTE 2: The "AKAv1-MD5" digest AKA algorithm is only supported for backward compatibility.
– "SIP Digest": it indicates SIP Digest authentication scheme.
– "NASS-Bundled": it indicates NASS Bundled authentication scheme.
– "Early‑IMS‑Security": it indicates GPRS-IMS-Bundled authentication scheme.
– "Unknown": it indicates that the authentication scheme to be used is unknown at this point.
6.3.10 SIP-Authenticate AVP
The SIP-Authenticate AVP is of type OctetString and contains specific parts of the data portion of the WWW-Authenticate or Proxy-Authenticate SIP headers that are to be present in a SIP response.
It shall contain, binary encoded, the concatenation of the authentication challenge RAND and the token AUTN. See 3GPP TS 33.203 [3] for further details about RAND and AUTN. The Authentication Information has a fixed length of 32 octets; the 16 most significant octets shall contain the RAND, the 16 least significant octets shall contain the AUTN.
6.3.11 SIP-Authorization AVP
The SIP-Authorization AVP is of type OctetString and contains specific parts of the data portion of the Authorization or Proxy-Authorization SIP headers suitable for inclusion in a SIP request.
When included in an Authentication Request, it shall contain the concatenation of RAND, as sent to the terminal, and AUTS, as received from the terminal. RAND and AUTS shall both be binary encoded. See 3GPP TS 33.203 [3] for further details about RAND and AUTS. The Authorization Information has a fixed length of 30 octets; the 16 most significant octets shall contain the RAND, the 14 least significant octets shall contain the AUTS.
When included in an Authentication Request Response, it shall contain, binary encoded, the expected response XRES. See 3GPP TS 33.203 [3] for further details about XRES.
6.3.12 SIP-Authentication-Context AVP
The SIP-Authentication-Context AVP is of type OctectString.
6.3.13 SIP-Auth-Data-Item AVP
The SIP-Auth-Data-Item is of type Grouped, and contains the authentication and/or authorization information for the Diameter client.
AVP format
SIP-Auth-Data-Item :: = < AVP Header : 612 10415 >
[ SIP-Item-Number ]
[ SIP-Authentication-Scheme ]
[ SIP-Authenticate ]
[ SIP-Authorization ]
[ SIP-Authentication-Context ]
[ Confidentiality-Key ]
[ Integrity-Key ]
[ SIP-Digest-Authenticate ]
[ Framed-IP-Address ]
[ Framed-IPv6-Prefix ]
[ Framed-Interface-Id ]
* [ Line-Identifier ]
* [AVP]
6.3.14 SIP-Item-Number AVP
The SIP-Item-Number AVP is of type Unsigned32.
6.3.15 Server-Assignment-Type AVP
The Server-Assignment-Type AVP is of type Enumerated, and indicates the type of server update, request or notification being performed in a Server-Assignment-Request operation. The following values are defined:
NO_ASSIGNMENT (0)
This value is used to request from HSS the user profile assigned to one or more public identities and to retrieve the S-CSCF restoration information for a registered Public User Identity, without affecting the registration state of those identities.
REGISTRATION (1)
The request is generated as a consequence of a first registration of an identity.
RE_REGISTRATION (2)
The request corresponds to the re-registration of an identity or update of the S-CSCF Restoration Information.
UNREGISTERED_USER (3)
The request is generated in the following cases:
– The S-CSCF received a request for a Public Identity that is not registered, or
– An AS sent an originating request on behalf of a Public Identity that is not registered, or
– The S-CSCF identified a P-CSCF failure for a Public User Identity that is registered with only one Private User Identity and started the P-CSCF Restoration procedure including the P-CSCF Restoration Indication in the request to the HSS.
TIMEOUT_DEREGISTRATION (4)
The SIP registration timer of an identity has expired.
USER_DEREGISTRATION (5)
The S-CSCF has received a user initiated de-registration request.
TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME (6)
The request is generated in the following cases:
The SIP registration timer of an identity has expired. The S-CSCF keeps the user data stored in the S-CSCF and requests HSS to store the S-CSCF name.
The S-CSCF identified a P-CSCF failure for a Public User Identity that is registered with only one Private User Identity and started the PCRF-based P-CSCF Restoration procedure.
USER_DEREGISTRATION_STORE_SERVER_NAME (7)
The S-CSCF has received a user initiated de-registration request. The S-CSCF keeps the user data stored in the S-CSCF and requests HSS to store the S-CSCF name.
ADMINISTRATIVE_DEREGISTRATION (8)
The request is generated in the following cases:
– The S-CSCF, due to administrative reasons or network issues, has performed the de-registration of an identity.
– The S-CSCF identified a P-CSCF failure for a Public User Identity that is registered with more than one Private User Identity and started the P-CSCF Restoration procedure including the P-CSCF Restoration Indication in the request to the HSS.
The S-CSCF identified a P-CSCF failure for a Public User Identity that is registered with more than one Private User Identity and started the PCRF-based P-CSCF Restoration procedure.
AUTHENTICATION_FAILURE (9)
The authentication of a user has failed.
AUTHENTICATION_TIMEOUT (10)
The authentication timeout has occurred.
DEREGISTRATION_TOO_MUCH_DATA (11)
The S-CSCF has requested user profile information from the HSS and has received a volume of data higher than it can accept.
AAA_USER_DATA_REQUEST (12)
Used in the SWx protocol, defined in 3GPP TS 29.273 [18]. This value is not used in the Cx protocol.
PGW_UPDATE (13)
Used in the SWx protocol, defined in 3GPP TS 29.273 [18]. This value is not used in the Cx protocol.
RESTORATION (14)
Used in the SWx protocol, defined in 3GPP TS 29.273 [18]. This value is not used in the Cx protocol.
6.3.16 Deregistration-Reason AVP
The Deregistration-Reason AVP is of type Grouped, and indicates the reason for a de-registration operation.
AVP format
Deregistration-Reason :: = < AVP Header : 615 10415 >
{ Reason-Code }
[ Reason-Info ]
* [AVP]
6.3.17 Reason-Code AVP
The Reason-Code AVP is of type Enumerated, and defines the reason for the network initiated de-registration. The following values are defined:
PERMANENT_TERMINATION (0)
NEW_SERVER_ASSIGNED (1)
SERVER_CHANGE (2)
REMOVE_S-CSCF (3)
The detailed behaviour of the S-CSCF is defined in 3GPP TS 29.228 [1].
6.3.18 Reason-Info AVP
The Reason-Info AVP is of type UTF8String, and contains textual information to inform the user about the reason for a de-registration.
6.3.19 Charging-Information AVP
The Charging-Information is of type Grouped, and contains the addresses of the charging functions.
AVP format
Charging-Information :: = < AVP Header : 618 10415 >
[ Primary-Event-Charging-Function-Name ]
[ Secondary-Event-Charging-Function-Name ]
[ Primary-Charging-Collection-Function-Name ]
[ Secondary-Charging-Collection-Function-Name ]
*[ AVP]
6.3.20 Primary-Event-Charging-Function-Name AVP
The Primary-Event-Charging-Function-Name AVP is of type DiameterURI. This AVP contains the address of the Primary Online Charging Function. The receiving network element shall extract the FQDN of the DiameterURI in this AVP and may use it as content of the Destination-Host AVP for the Diameter accounting requests. The parent domain of the FQDN in the DiameterURI shall be used as Destination-Realm. The number of labels used for the Destination-Realm shall be determined before the Charging Information is provisioned and may be a configuration option.
NOTE: A FQDN is an absolute domain name including a subdomain and its parent domain. The subdomain and the parent domain contain one or more labels separated by dots.
6.3.21 Secondary-Event-Charging-Function-Name AVP
The Secondary-Event-Charging-Function-Name AVP is of type DiameterURI. This AVP contains the address of the Secondary Online Charging Function. The Destination-Host and Destination-Realm values for the Diameter accounting requests should be extracted from the DiameterURI in the way indicated in clause 6.3.20.
6.3.22 Primary-Charging-Collection-Function-Name AVP
The Primary-Charging-Collection-Function-Name AVP is of type DiameterURI. This AVP contains the address of the Primary Charging Data Function. The Destination-Host and Destination-Realm values for the Diameter accounting requests should be extracted from the DiameterURI in the way indicated in clause 6.3.20.
6.3.23 Secondary-Charging-Collection-Function-Name AVP
The Secondary-Charging-Collection-Function-Name AVP is of type DiameterURI. This AVP contains the address of the Secondary Charging Data Function. The Destination-Host and Destination-Realm for the Diameter accounting requests values should be extracted from the DiameterURI in the way indicated in clause 6.3.20.
6.3.24 User-Authorization-Type AVP
The User-Authorization-Type AVP is of type Enumerated, and indicates the type of user authorization being performed in a User Authorization operation, i.e. UAR command. The following values are defined:
REGISTRATION (0)
This value is used in case of the initial registration or re-registration. I-CSCF determines this from the Expires field or expires parameter in Contact field in the SIP REGISTER method if it is not equal to zero.
This is the default value.
DE_REGISTRATION (1)
This value is used in case of the de-registration. I-CSCF determines this from the Expires field or expires parameter in Contact field in the SIP REGISTER method if it is equal to zero.
REGISTRATION_AND_CAPABILITIES (2)
This value is used when the I-CSCF explicitly requests S-CSCF capability information from the HSS. The I-CSCF shall use this value when the user’s current S-CSCF, which is stored in the HSS, cannot be contacted and a new S-CSCF needs to be selected
6.3.25 Void
6.3.26 User-Data-Already-Available AVP
The User-Data-Already-Available AVP is of type Enumerated, and indicates to the HSS whether or not the S-CSCF already has the part of the user profile that it needs to serve the user. The following values are defined:
USER_DATA_NOT_AVAILABLE (0)
The S-CSCF does not have the data that it needs to serve the user.
USER_DATA_ALREADY_AVAILABLE (1)
The S-CSCF already has the data that it needs to serve the user.
6.3.27 Confidentiality-Key AVP
The Confidentiality-Key is of type OctetString, and contains the Confidentiality Key (CK).
6.3.28 Integrity-Key AVP
The Integrity-Key is of type OctetString, and contains the Integrity Key (IK).
6.3.29 Supported-Features AVP
The Supported-Features AVP is of type Grouped. If this AVP is present it may inform the destination host about the features that the origin host supports for the application. The Feature-List AVP contains a list of supported features of the origin host. The Vendor-Id AVP and the Feature-List-ID AVP shall together identify which feature list is carried in the Supported-Features AVP for the Application-ID present in the command header.
Where a Supported-Features AVP is used to identify features that have been defined by 3GPP, the Vendor-Id AVP shall contain the vendor ID of 3GPP. Vendors may define proprietary features, but it is strongly recommended that the possibility is used only as the last resort. Where the Supported-Features AVP is used to identify features that have been defined by a vendor other than 3GPP, it shall contain the vendor ID of the specific vendor in question.
If there are multiple feature lists defined by the same vendor and the same application, the Feature-List-ID AVP shall differentiate those lists from one another. The destination host shall use the value of the Feature-List-ID AVP to identify the feature list.
AVP format
Supported-Features ::= < AVP header: 628 10415 >
{ Vendor-Id }
{ Feature-List-ID }
{ Feature-List }
*[AVP]
6.3.30 Feature-List-ID AVP
The Feature-List-ID AVP is of type Unsigned32 and it contains the identity of a feature list.
6.3.31 Feature-List AVP
The Feature-List AVP is of type Unsigned32 and it contains a bit mask indicating the supported features of an application. When the bit set, indicates the corresponding feature is supported by the application. For the Cx application, the meaning of the bits has been defined in 7.1.1.
6.3.32 Supported-Applications AVP
The Supported-Applications AVP is of type Grouped and it contains the supported application identifiers of a Diameter node.
AVP format
Supported-Applications ::= < AVP header: 631 10415 >
*[ Auth-Application-Id ]
*[ Acct-Application-Id ]
*[ Vendor-Specific-Application-Id ]
*[ AVP ]
6.3.33 Associated-Identities AVP
The Associated-Identities AVP is of type Grouped and it contains the private user identities associated to an IMS subscription.
AVP format
Associated-Identities ::= < AVP header: 632, 10415 >
*[ User-Name ]
*[ AVP ]
6.3.34 Originating-Request AVP
The Originating-Request AVP is of type Enumerated. The following value is defined:
ORIGINATING (0)
This value indicates to the HSS that the request is related to an AS originating SIP request in the Location-Information-Request operation.
6.3.35 Wildcarded-Public-Identity AVP
The Wildcarded-Public-Identity AVP is of type UTF8String. This AVP contains a Wildcarded PSI or Wildcarded Public User Identity stored in the HSS. The syntax of the contents of this AVP is described in 3GPP TS 23.003 [13].
6.3.36 SIP-Digest-Authenticate AVP
The SIP-Digest-Authenticate is of type Grouped and it contains a reconstruction of either the SIP WWW-Authenticate or Proxy-Authentication header fields specified in IETF RFC 7616 [29].
AVP format
SIP-Digest-Authenticate ::= < AVP Header: 635 10415>
{ Digest-Realm }
[ Digest-Algorithm ]
{ Digest-QoP }
{ Digest-HA1}
[ Alternate-Digest-Algorithm ]
[ Alternate-Digest-HA1 ]
*[ AVP ]
6.3.37 Digest-Realm AVP
The Digest-Realm AVP is defined in IETF RFC 4740 [15].
6.3.38 Void
6.3.39 Digest-Algorithm AVP
The Digest-Algorithm AVP is defined in IETF RFC 4740 [15] and contains values as defined in IETF RFC 7616 [29].
NOTE: The MD5 algorithm is only supported for backward compatibility.
6.3.40 Digest-QoP AVP
The Digest-QoP AVP is defined in IETF RFC 4740 [15].
6.3.41 Digest-HA1 AVP
The Digest-HA1 AVP is defined in IETF RFC 4740 [15].
6.3.42 Line-Identifier AVP
The Line-Identifier AVP is of type OctetString. This AVP has Vendor Id ETSI (13019) and AVP code 500. This AVP contains a fixed broadband access line identifier associated with the user.
6.3.43 Wildcarded-IMPU AVP
The Wildcarded-IMPU AVP is of type UTF8String. This AVP contains a Wildcarded Public User Identity stored in the HSS. The syntax of the contents of this AVP is described in 3GPP TS 23.003 [13].
Note: This AVP is used by Sh interface as specified in the 3GPP TS 29.328 [16] and 3GPP TS 29.329 [11].
6.3.44 UAR-Flags AVP
The UAR-Flags AVP is of type Unsigned32 and it contains a bit mask. The meaning of the bits is defined in the following table:
Table 6.3.44.1: UAR-Flags
|
Bit |
Name |
Description |
|
0 |
IMS Emergency Registration |
This bit, when set, indicates that the request corresponds to an IMS Emergency Registration. |
|
Bits not defined in this table shall be cleared by the sending I-CSCF and discarded by the receiving HSS. |
||
6.3.45 Loose-Route-Indication AVP
The Loose-Route-Indication AVP is of type Enumerated and indicates to the S-CSCF whether or not the loose route mechanism is required to serve the registered Public User Identities. The following values are defined:
LOOSE_ROUTE_NOT_REQUIRED (0)
LOOSE_ROUTE_REQUIRED (1)
6.3.46 SCSCF-Restoration-Info AVP
The SCSCF-Restoration-Info AVP is of type Grouped and it contains the information required for an S-CSCF to handle the requests for a user.
AVP format
SCSCF-Restoration-Info ::= < AVP Header: 639, 10415>
{ User-Name }
1*{ Restoration-Info }
[ Registration-Time-Out ]
[ SIP-Authentication-Scheme ]
*[ AVP ]
6.3.47 Path AVP
The Path AVP is of type OctetString and it contains a comma separated list of SIP proxies in the Path header as defined in IETF RFC 3327 [17].
6.3.48 Contact AVP
The Contact AVP is of type OctetString and it contains the Contact Addresses and Parameters in the Contact header as defined in IETF RFC 3261 [11].
6.3.49 Subscription-Info AVP
The Subscription-Info AVP is of type Grouped and it contains the UE’s subscription information. The Contact AVP contains the Contact Address and Parameters in the Contact header of the subscription request.
AVP format
Subscription-Info ::= < AVP Header: 642, 10415>
{ Call-ID-SIP-Header }
{ From-SIP-Header }
{ To-SIP-Header }
{ Record-Route }
{Contact}
*[ AVP ]
6.3.49.1 Call-ID-SIP-Header AVP
The Call-ID-SIP-Header AVP is of type OctetString and it contains the information in the Call-ID header as defined in IETF RFC 3261 [11].
6.3.49.2 From-SIP-Header AVP
The From-SIP-Header AVP is of type OctetString and it contains the information in the From header as defined in IETF RFC 3261 [11].
6.3.49.3 To-SIP-Header AVP
The To-SIP-Header AVP is of type OctetString and it contains the information in the To header as defined in IETF RFC 3261 [11].
6.3.49.4 Record-Route AVP
The Record-Route AVP is of type OctetString and it contains a comma separated list of Record Route header(s) as defined in IETF RFC 3261 [11].
6.3.50 Associated-Registered-Identities AVP
The Associated-Registered-Identities AVP is of type Grouped and it contains the Private User Identities registered with the Public User Identity received in the request command.
AVP format
Associated-Registered-Identities ::= < AVP header: 647, 10415 >
*[ User-Name ]
*[ AVP ]
6.3.51 Multiple-Registration-Indication
The Multiple-Registration-Indication AVP is of type Enumerated and indicates to the HSS whether or not the request is related to a multiple registration. The following values are defined:
NOT_MULTIPLE_REGISTRATION (0)
MULTIPLE_REGISTRATION (1)
6.3.52 Restoration-Info AVP
The Restoration-Info AVP is of type Grouped and it contains the information related to a specific registration required for an S-CSCF to handle the requests for a user. The Contact AVP contains the Contact Address and Parameters in the Contact header of the registration request.
AVP format
Restoration-Info ::= < AVP Header: 649, 10415>
{ Path }
{ Contact }
[ Initial-CSeq-Sequence-Number ]
[ Call-ID-SIP-Header ]
[ Subscription-Info ]
[ P-CSCF-Subscription-Info ]
*[ AVP ]
6.3.53 Framed-IP-Address AVP
The Framed-IP-Address AVP is defined in IETF RFC 4005 [19].
6.3.54 Framed-IPv6-Prefix AVP
The Framed-IPv6-Prefix AVP is defined in IETF RFC 4005 [19], and it shall be encoded as defined in IETF RFC 3162 [22].
6.3.55 Framed-Interface-Id AVP
The Framed-Interface-Id AVP is defined in IETF RFC 4005 [19].
6.3.56 Session-Priority AVP
The Session-Priority AVP is of type Enumerated and indicates to the HSS the session’s priority. The following values are defined:
PRIORITY-0 (0)
PRIORITY-1 (1)
PRIORITY-2 (2)
PRIORITY-3 (3)
PRIORITY-4 (4)
PRIORITY-0 is the highest priority.
The value of the AVP when sent to the HSS is mapped from the value received by the CSCF as described in 3GPP TS 24.229 table A.162. The mapping is operator specific.
This AVP may be placed as close to the Diameter header as possible in order to potentially allow optimized processing at the receiver.
6.3.57 Identity-with-Emergency-Registration AVP
The Identity-with-Emergency-Registration AVP is of type Grouped and it contains a pair of private/public user identities which are emergency registered.
AVP format
Identity-with-Emergency-Registration ::= < AVP header: 651, 10415 >
{ User-Name }
{ Public-Identity }
*[ AVP ]
6.3.58 Priviledged-Sender-Indication AVP
The Priviledged-Sender-Indication AVP is of type Enumerated and indicates to the S-CSCF whether or not the Private User Identity shall be considered as a priviledged sender. The following values are defined:
NOT_PRIVILEDGED_SENDER (0)PRIVILEDGED_SENDER (1)
6.3.59 LIA-Flags
The LIA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.59.1.
Table 6.3.59.1: LIA-Flags
|
Bit |
Name |
Description |
|
0 |
PSI Direct Routing Indication |
This bit, when set, indicates the request corresponds to PSI Direct Routing, what implies that HSS returns an AS name in Server-Name AVP. |
|
NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving I-CSCF. |
||
6.3.60 OC-Supported-Features
The OC-Supported-Features AVP is of type Grouped and it is defined in IETF RFC 7683 [23]. This AVP is used to support Diameter overload control mechanism.
6.3.61 OC-OLR
The OC-OLR AVP is of type Grouped and it is defined in IETF RFC 7683 [23]. This AVP is used to support Diameter overload control mechanism.
6.3.62 Initial-CSeq-Sequence-Number AVP
The Initial-CSeq-Sequence-Number AVP is of type Unsigned32, and it contains the sequence number of the CSeq header field contained in the initial successful REGISTER request, as defined in IETF RFC 3261 [11].
6.3.63 SAR-Flags
The SAR-Flags AVP is of type Unsigned32 and it contains a bit mask. The meaning of the bits is defined in the following table:
Table 6.3.63.1: SAR-Flags
|
Bit |
Name |
Description |
|
0 |
P-CSCF Restoration Indication |
This bit, when set, indicates that the P-CSCF-Restoration-mechanism feature shall be executed, as described in 3GPP TS 23.380 [24], clause 5.4. This AVP is optionally present only when Server-Assignment-Type takes the value ADMINISTRATIVE_DEREGISTRATION or UNREGISTERED_USER. |
|
Note: Bits not defined in this table shall be cleared by the sending S-CSCF and discarded by the receiving HSS. |
||
6.3.64 Allowed-WAF-WWSF-Identities AVP
The Allowed-WAF-WWSF-Identities AVP is of type Grouped and contains the addresses of the WAFs and WWSFs allowed for the subscription.
AVP format
Allowed-WAF-WWSF-Identities :: = < AVP Header : 656 10415 >
*[ WebRTC-Authentication-Function-Name ]
*[ WebRTC-Web-Server-Function-Name ]
*[ AVP]
6.3.65 WebRTC-Authentication-Function-Name AVP
The WebRTC-Authentication-Function-Name AVP is of type UTF8String and contains the address of a WAF allowed for the subscription. For the format of the string see IETF draft-holmberg-sipcore-auth-id-01 [25].
6.3.66 WebRTC-Web-Server-Function-Name AVP
The WebRTC-Web-Server-Function-Name AVP is of type UTF8String and contains the address of a WWSF allowed for the subscription. For the format of the string see IETF draft-holmberg-sipcore-auth-id-01 [25].
6.3.67 DRMP AVP
The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [26]. This AVP allows the HSS/SLF and the S-CSCF/I-CSCF to indicate the relative priority of Diameter messages. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message.
6.3.68 Load
The Load AVP is of type Grouped and it is defined in IEFT RFC 8583 [27]. This AVP is used to support the Diameter load control mechanism.
6.3.69 RTR-Flags
The RTR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.69.1.
Table 6.3.69.1: RTR-Flags
|
Bit |
Name |
Description |
|
0 |
Reference Location Information change |
This bit, when set, indicates the request is sent due to change of Reference Location Information. |
|
NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving I-CSCF. |
||
6.3.70 P-CSCF-Subscription-Info AVP
The P-CSCF-Subscription-Info AVP is of type Grouped and it contains the P-CSCF”s subscription information. The Contact AVP contains the Contact Address and Parameters in the Contact header of the subscription request.
AVP format
P-CSCF-Subscription-Info ::= < AVP Header: 660, 10415>
{ Call-ID-SIP-Header }
{ From-SIP-Header }
{ To-SIP-Header }
{ Contact }
*[ AVP ]
6.3.71 Registration-Time-Out
The Registration-Time-Out AVP is of type Time (see IETF RFC 6733 [28]), and contains the point of time at which the UE’s registration expires.
6.3.72 Alternate-Digest-Algorithm AVP
The Alternate-Digest-Algorithm AVP contains algorithm values specified in IETF RFC 7616 [29].
NOTE: The MD5 algorithm is only supported for backward compatibility and can only be provided within the Digest-Algorithm AVP.
6.3.73 Alternate-Digest-HA1 AVP
The Alternate-Digest-HA1 AVP contains H(A1) value specified in IETF RFC 7616 [29].
6.3.74 Failed-PCSCF
The Failed-PCSCF AVP is of type Grouped and contains the FQDN and/or IP addresses of the failed P-CSCF.
AVP format
Failed-PCSCF ::= < AVP Header: 664, 10415>
[ PCSCF-FQDN ]
*[ PCSCF-IP-Address ]
*[ AVP ]
6.3.75 PCSCF-FQDN
The PCSCF-FQDN AVP is of type DiameterIdentity and contains the FQDN of the P-CSCF.
6.3.76 PCSCF-IP-Address
The PCSCF-IP-Address AVP is of type Address and contains the IPv4 or IPv6 address of the P-CSCF.
6.4 Use of namespaces
This clause contains the namespaces that have either been created in this specification, or the values assigned to existing namespaces managed by IANA.
6.4.1 AVP codes
This specification assigns the AVP values from the AVP Code namespace managed by 3GPP for its Diameter vendor-specific applications. See clause 6.3 for the assignment of the namespace in this specification.
6.4.2 Experimental-Result-Code AVP values
This specification has assigned Experimental-Result-Code AVP values 2001-2005 and 5001-5011. See clause 6.2.
6.4.3 Command Code values
This specification assigns the values 300-305 from the range allocated by IANA to 3GPP in IETF RFC 3589 [12].
6.4.4 Application-ID value
IANA has allocated the value 16777216 for the 3GPP Cx interface application.