Editing Diameter (protocol) (section)

=== Application-ID ===
Application-ID is used to identify for which Diameter application the message is applicable. The application can be an authentication application, an accounting application, or a vendor-specific application.

Diameter agents conforming to a certain Diameter extension publicize its support by including a specific value of in the Auth-Application-ID Attribute of the Capabilities-Exchange-Request (CER) and Capabilities-Exchange-Answer (CEA) command.

The value of the Application-ID field in the header is the same as any relevant Application-ID AVPs contained in the message. For instance, the value of the Application-ID and of the Auth-Application-ID Attribute in the Credit-Control-Request (CCR) and Credit-Control-Answer (CCA) Command for the Diameter Credit-Control Application is 4.<ref name=rfc4006>{{cite journal|title=RFC 4006 - Diameter Credit-Control Application
|journal=Proposed Standard|year=2005 |volume=Standards Track|doi=10.17487/RFC4006 |url=https://tools.ietf.org/html/rfc4006|last1=Hakala |first1=H. |last2=Mattila |first2=L. |last3=Stura |first3=M. |last4=Loughney |first4=J. |doi-access=free }}</ref>

{| class="wikitable sortable"
|-
!align=left|Application-ID!!Abbr.!!Full name!!Usage
|-
| 0||Base||Diameter Common Messages||Diameter protocol association establishment/teardown/maintenance
|-
| 16777216||Cx/Dx||3GPP Cx/Dx||IMS I/S-CSCF to HSS interface
|-
| 16777217||Sh||3GPP Sh||VoIP/IMS SIP Application Server to HSS interface
|-
| 16777236||Rx||3GPP Rx||Policy and charging control
|-
| 16777238||Gx||3GPP Gx||Policy and charging control
|-
| 16777251||S6a/S6d||3GPP S6a/S6d||LTE Roaming signaling
|-
| 16777252||S13||3GPP 13||Interface between EIR and MME
|-
| 16777255||SLg||3GPP LCS SLg||Location services
|-
| 16777345||S6t||3GPP S6t||Interface between SCEF and HSS
|}