Diameter

Topics in this document:

• Diameter Base Protocol
• Diameter Gy Protocol
• Diameter Gx Protocol

Diameter Base Protocol

This sub-section describes how AAA Gateway maps the messages for Diameter Base Protocol defined in RFC-3588.

Section Compliance

Table 1-1 lists the compliance information for Diameter Base protocol sections.

Table 1-1: Diameter Base Protocol Section Compliance

Diameter Gy Protocol

This chapter describes how AAA Gateway maps the diameter messages for the Diameter Gy protocol defined in 3GPP TS 32.299 Version 12.0. For more information, see the 3GPP specification detail:

http://www.3gpp.org/ftp/Specs/html-info/32299.htm

Section Compliance

Table 2-1 lists the compliance information for Diameter Gy protocol sections.

Table 2-1: Diameter Gy Section Compliance

Diameter Session Commands

Table 2-2 lists the Diameter session commands supported by Diameter Gateway.

Table 2-2: Diameter Session Commands

Diameter Credit-Control Request Messages

Table 2-3 lists the Diameter credit-control request messages supported by Diameter Gateway.

Table 2-3: Diameter Credit-Control Request Messages

Gy Session Charging (IUT) Request AVPs

Table 2-4 lists the compliance information for Gy Session Charging attribute-value pairs (AVPs) for the session-based request operations, such as INITIATE, UPDATE, and TERMINATE (IUT).

Table 2-4: Gy Session Charging (IUT) Request AVPs

Multiple-Services-Credit-Control

Table 2-5 lists the compliance information for Multiple-Services-Credit-Control AVPs for the Gy Session Charging request operations.

Table 2-5: Multiple-Services-Credit-Control AVPs for Gy Session Charging Request

Gy Session Charging (IUT) Response AVPs

Table 2-6 lists the compliance information for Diameter Credit-Control-Answer AVPs for the Gy Session Charging response operations.

Table 2-6: Gy Session Charging (IUT) Response AVPs

Multiple-Services-Credit-Control

Table 2-7 lists the Multiple-Services-Credit-Control AVPs for the Gy Session Charging response operations.

Table 2-7: Multiple-Services-Credit-Control AVPs for Gy Session Charging Response

Gy Top-Up Request AVPs

Table 2-8 lists the compliance information for Gy Top-Up AVPs for the request operations.

Table 2-8: Gy Top-Up Request AVPs

Gy Top-Up Response AVPs

Table 2-9 lists the compliance information for Gy Top-Up AVPs for the response operations.

Table 2-9: Gy Top-Up Response AVPs

Gy Balance Query Request AVPs

Table 2-10 lists the compliance information for Gy Balance Query AVPs for the request operations.

Table 2-10: Gy Balance Query Request AVPs

Gy Balance Query Response AVPs

Table 2-11 lists the compliance information for Gy Balance Query AVPs for the response operations.

Table 2-11 Gy Balance Query Response AVPs

Gy Debit/Refund Request AVPs

Table 2-12 lists the compliance information for Gy Debit/Refund AVPs for the request operations.

Table 2-12: Gy Debit/Refund Request AVPs

Multiple-Services-Credit-Control

Table 2-13 lists compliance information for Multiple-Services-Credit-Control AVPs for Gy Debit/Refund request operations.

Table 2-13: Multiple-Services-Credit-Control AVPs for Gy Debit/Refund Request

Gy Debit/Refund Response AVPs

Table 2-14 lists the compliance information for Gy Debit/Refund AVPs for the response operations.

Table 2-14: Gy Debit/Refund Response AVPs

Multiple-Services-Credit-Control

Table 2-15 lists the compliance information for Multiple-Services-Credit-Control AVPs for Gy Debit/Refund response operations.

Table 2-15: Multiple-Services-Credit-Control AVPs for Gy Debit/Refund Response

Gy Price Enquiry Request AVPs

Table 2-16 lists the compliance information for Gy Price Enquiry AVPs for the request operations.

Table 2-16: Gy Price Enquiry Request AVPs

Multiple-Services-Credit-Control

Table 2-17 lists the compliance information for Multiple-Services-Credit-Control AVPs for Gy price enquiry request operations.

Table 2-17: Multiple-Services-Credit-Control AVPs for Gy Price Enquiry Request

Gy Price Enquiry Response AVPs

Table 2-18 lists the compliance information for Gy Price Enquiry AVPs for the response operations.

Table 2-18: Gy Price Enquiry Response AVPs

Multiple-Services-Credit-Control

Table 2-19 lists the compliance information for Multiple-Services-Credit-Control AVPs for Gy Price Enquiry response operations.

Table 2-19: Multiple-Services-Credit-Control AVPs for Gy Price Enquiry Response

Diameter Session Reauthorization Commands

Table 2-20 lists the compliance information for Diameter Session Reauthorization commands.

Table 2-20: Diameter Session Reauthorization Commands

Re-Auth-Request AVPs

Table 2-21 lists the compliance information for Re-Auth-Request (RAR) AVPs.

Table 2-21: Re-Auth-Request AVPs

Re-Auth-Answer AVPs

Table 2-22 lists the compliance information for Re-Auth-Answer (RAA) AVPs.

Table 2-22: Re-Auth-Answer AVPs

Diameter Session Termination Commands

Table 2-23 lists the compliance information for Diameter Session Termination commands.

Table 2-23: Diameter Session Termination Commands

Session-Termination-Request AVPs

Table 2-24 lists the compliance information for Session-Termination-Request (STR) AVPs.

Table 2-24: Session-Termination-Request AVPs

Session-Termination-Answer AVPs

Table 2-25 lists the compliance information for Session-Termination-Answer (STA) AVPs.

Table 2-25: Session-Termination-Answer AVPs

Diameter Gx Protocol

The Gx application is characterized as a specialized Diameter application for specific vendors. Within the context of the Diameter protocol over the Gx interface, the 7x50 (Policy and Charging Enforcement Function, PCEF) functions as a Diameter Client, whereas the Policy and Charging Rules Function (PCRF) serves as a Diameter Server. The Gx Diameter Application incorporates existing Command Codes from both the Diameter Base Protocol (as per RFC 6733) and the Diameter Credit Control Application (according to RFC 4006).

For its data representation in messaging structures (specifically, command codes), Gx employs Attribute-Value Pairs (AVPs).

The origins of AVPs in Gx are diverse, including:

• AVPs unique to Gx, as specified in the 3GPP Gx document TS 29.212.
• AVPs borrowed from other Diameter applications (e.g., RFC 4006, RFC 4005), other 3GPP specifications, the European Telecommunications Standards Institute (ETSI), and so forth.
• Attributes recycled from RADIUS (with AVP codes 0-255 earmarked for these reused attributes).
• AVPs that are vendor-specific.

The process to initiate and sustain the connection between the 7x50 (PCEF) and the PCRF is governed by the foundational Diameter protocol, outlined in RFC 3588/6733.

Gx AVP

This guide offers a summary of the Gx Attribute Value Pairs (AVP) supported by the 7750 SR. The implementation follows the specification on Gx Release v11.12, doc 3GPP 29212-bc0.doc.

Table 1 shows the conventions used in this guide.

Table 1-1: Attribute Conventions

AVPs

Certain AVPs are applicable in only one direction, while others are applicable to both directions.

AVPs sent by the 7750 SR are used to:

• inform the PCRF of the host creation/termination and the subscriber host identity in the 7750 SR
• inform the PCRF of the functionality supported in the 7750 SR
• report specific events related to the subscriber-host
• report the status of the rules
• report usage monitoring
• report status of the host (existent/non-existent)

AVPs sent by PCRF toward the 7750 SR are used to:

• install or activate policies
• request usage monitoring
• terminate the subscriber-host
• request status of the subscriber-host (existent/non-existent)

AVPs that apply to both directions are used for base Diameter functionality such as peering establishment, routing of the Diameter messages, session identification and reporting of catastrophic failures (OSI change).

Reserved Keywords in the 7750 SR

The reserved keywords used to identify referenced object type within the 7750 SR are listed in Table 1-2. See Table 1-4 for further reference.

Table 1-2: Reserved Keywords in the 7750 SR

Standard Diameter AVPs

AVPs apply in the following applications:

• Gx-PM-ESM — Policy Management for Enhanced Subscriber Management
• Gx-UM-ESM — Usage Monitoring for Enhanced Subscriber Management
• Gx-PM-AA — Policy Management for Application Assurance
• Gx-UM-AA — Usage Monitoring Application Assurance

The AVPs listed in following Table 1-3 that do not have an associated application are AVPs that are used for generic purposes and their use can extend through all applications.

Table 1-3: Description of Standard Diameter AVPs

Standard Diameter AVPs (format)

Table 1-4 lists standard diameter AVPs.

Incl/Excl – The attribute can be suppressed via CLI.

Flags (as set by the 7750 SR when the AVP is constructed):

• V — Vendor specific bit
• M — Mandatory bit
• P — This bit is always set to 0

UTF8String is a human-readable string using UTF-8 transformation format (which is for 7-bit encoding the same as US-ASCII).

OctetString is a basic data type which contains an arbitrary data. For example, Charging-Rule-Name AVP is OctetString according to RFC 6733 but in the 7750 SR it is displayed as readable string (UTF8String).

Flags for Gx specific AVPs are defined in RFC 6733, §4.5; 29.212, §5.3.

Flags for the Gx re-used AVPs are set as described in RFC 6733, §4.5 and in 3GPP 29.219, §5.4 — ‟The AVPs from Diameter base protocol are not included in Table 5.4, but they are re-used for the Gx reference point. Unless otherwise stated, re-used AVPs shall maintain their ‘M’, ‘P’ and ‘V’ flag settings. Where 3GPP RADIUS AVPs are re-used, unless otherwise stated, they shall be translated to Diameter AVPs as described in RFC 4005 [12] with the exception that the ‘M’ flag shall be set and the ‘P’ flag may be set”.

NA — This keyword (Not Advertised) denotes that the AVP is not originated by the 7750 SR and therefore the 7750 SR does not set the flag bits. However, the 7750 SR recognizes the AVPs and corresponding values listed in the table, regardless of the M-bit flags set by PCRF. However, if the V-bit is present in the received AVP, then the Vendor-Id filed in the AVP layout also must be present and set to the correct value because the AVP with V-bit set is identified by the <avp-id, vendor-id> pair.

Table 1-4: Standard Diameter AVPs (format)

Diameter-Based AVP Applicability

The following tables use the following symbols:

• 0 — The AVP must not be present in the message.
• 0+ — Zero or more instances of the AVP may be present in the message.
• 0-1 — Zero or one instance of the AVP may be present in the message. It is considered an error if there is more than one instance of the AVP.
• 1 — One instance of the AVP must be present in the message.
• 1+ — At least one instance of the AVP must be present in the message.
• N — The AVP is nested inside of a grouped AVP that is present in this message.

Table 7: Diameter-Based AVP Applicability

Gx AVP Applicability

Table 8: Gx AVP Applicability

Result Codes (Result-Code AVP)

Table 10: Result Codes (Result-Code AVP)

Rule Failure Codes (Rule-Failure-Code AVP)

Table 11: Rule Failure Codes (Rule-Failure-Code AVP)

Event Triggers (Event-Trigger AVP)

Table 12: Event Triggers (Event-Trigger AVP)

Termination Causes (Termination-Cause AVP)

Table 13: Termination Causes (Termination-Cause AVP)

Standards and Protocol Support

Access Node Control Protocol (ANCP)

draft-ietf-ancp-protocol-02, Protocol for Access Node Control Mechanism in Broadband Networks

RFC 5851, Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks

Application Assurance (AA)

3GPP Release 12, ADC rules over Gx interfaces

RFC 3507, Internet Content Adaptation Protocol (ICAP)

Asynchronous Transfer Mode (ATM)

AF-ILMI-0065.000 Version 4.0, Integrated Local Management Interface (ILMI)

AF-PHY-0086.001 Version 1.1, Inverse Multiplexing for ATM (IMA) Specification

AF-TM-0121.000 Version 4.1, Traffic Management Specification

GR-1113-CORE Issue 1, Asynchronous Transfer Mode (ATM) and ATM Adaptation Layer (AAL) Protocols Generic Requirements

GR-1248-CORE Issue 3, Generic Requirements for Operations of ATM Network Elements (NEs)

RFC 1626, Default IP MTU for use over ATM AAL5

RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5

Bidirectional Forwarding Detection (BFD)

draft-ietf-idr-bgp-ls-sbfd-extensions-01, BGP Link-State Extensions for Seamless BFD

RFC 5880, Bidirectional Forwarding Detection (BFD)

RFC 5881, Bidirectional Forwarding Detection (BFD) IPv4 and IPv6 (Single Hop)

RFC 5882, Generic Application of Bidirectional Forwarding Detection (BFD)

RFC 5883, Bidirectional Forwarding Detection (BFD) for Multihop Paths

RFC 7130, Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces

RFC 7880, Seamless Bidirectional Forwarding Detection (S-BFD)

RFC 7881, Seamless Bidirectional Forwarding Detection (S-BFD) for IPv4, IPv6, and MPLS

RFC 7883, Advertising Seamless Bidirectional Forwarding Detection (S-BFD) Discriminators in IS-IS

RFC 7884, OSPF Extensions to Advertise Seamless Bidirectional Forwarding Detection (S-BFD) Target Discriminators

Border Gateway Protocol (BGP)

draft-hares-idr-update-attrib-low-bits-fix-01, Update Attribute Flag Low Bits Clarification

draft-ietf-idr-add-paths-guidelines-08, Best Practices for Advertisement of Multiple Paths in IBGP

draft-ietf-idr-best-external-03, Advertisement of the best external route in BGP

draft-ietf-idr-bgp-flowspec-oid-03, Revised Validation Procedure for BGP Flow Specifications

draft-ietf-idr-bgp-gr-notification-01, Notification Message support for BGP Graceful Restart

draft-ietf-idr-bgp-ls-app-specific-attr-01, Application Specific Attributes Advertisement with BGP Link-State

draft-ietf-idr-bgp-optimal-route-reflection-10, BGP Optimal Route Reflection (BGP-ORR)

draft-ietf-idr-error-handling-03, Revised Error Handling for BGP UPDATE Messages

draft-ietf-idr-flowspec-interfaceset-03, Applying BGP flowspec rules on a specific interface set

draft-ietf-idr-flowspec-path-redirect-05, Flowspec Indirection-id Redirect - localised ID

draft-ietf-idr-flowspec-redirect-ip-02, BGP Flow-Spec Redirect to IP Action

draft-ietf-idr-link-bandwidth-03, BGP Link Bandwidth Extended Community

draft-ietf-idr-long-lived-gr-00, Support for Long-lived BGP Graceful Restart

draft-ietf-sidr-origin-validation-signaling-04, BGP Prefix Origin Validation State Extended Community

RFC 1772, Application of the Border Gateway Protocol in the Internet

RFC 1997, BGP Communities Attribute

RFC 2385, Protection of BGP Sessions via the TCP MD5 Signature Option

RFC 2439, BGP Route Flap Damping

RFC 2545, Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing

RFC 2858, Multiprotocol Extensions for BGP-4

RFC 2918, Route Refresh Capability for BGP-4

RFC 3107, Carrying Label Information in BGP-4

RFC 4271, A Border Gateway Protocol 4 (BGP-4)

RFC 4360, BGP Extended Communities Attribute

RFC 4364, BGP/MPLS IP Virtual Private Networks (VPNs)

RFC 4456, BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)

RFC 4486, Subcodes for BGP Cease Notification Message

RFC 4659, BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN

RFC 4684, Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)

RFC 4724, Graceful Restart Mechanism for BGP - helper mode

RFC 4760, Multiprotocol Extensions for BGP-4

RFC 4798, Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)

RFC 5004, Avoid BGP Best Path Transitions from One External to Another

RFC 5065, Autonomous System Confederations for BGP

RFC 5291, Outbound Route Filtering Capability for BGP-4

RFC 5396, Textual Representation of Autonomous System (AS) Numbers - asplain

RFC 5492, Capabilities Advertisement with BGP-4

RFC 5549, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop

RFC 5575, Dissemination of Flow Specification Rules

RFC 5668, 4-Octet AS Specific BGP Extended Community

RFC 6286, Autonomous-System-Wide Unique BGP Identifier for BGP-4

RFC 6793, BGP Support for Four-Octet Autonomous System (AS) Number Space

RFC 6810, The Resource Public Key Infrastructure (RPKI) to Router Protocol

RFC 6811, Prefix Origin Validation

RFC 6996, Autonomous System (AS) Reservation for Private Use

RFC 7311, The Accumulated IGP Metric Attribute for BGP

RFC 7607, Codification of AS 0 Processing

RFC 7674, Clarification of the Flowspec Redirect Extended Community

RFC 7752, North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP

RFC 7854, BGP Monitoring Protocol (BMP)

RFC 7911, Advertisement of Multiple Paths in BGP

RFC 7999, BLACKHOLE Community

RFC 8092, BGP Large Communities Attribute

RFC 8212, Default External BGP (EBGP) Route Propagation Behavior without Policies

RFC 8571, BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions

Broadband Network Gateway (BNG) - Control and User Plane Separation (CUPS)

3GPP 23.007, Restoration procedures

3GPP 29.244, Interface between the Control Plane and the User Plane nodes

3GPP 29.281, General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)

BBF TR-459, Control and User Plane Separation for a Disaggregated BNG

RFC 8300, Network Service Header (NSH)

Circuit Emulation

RFC 4553, Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP)

RFC 5086, Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN)

RFC 5287, Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS Networks

Ethernet

IEEE 802.1AB, Station and Media Access Control Connectivity Discovery

IEEE 802.1ad, Provider Bridges

IEEE 802.1ag, Connectivity Fault Management

IEEE 802.1ah, Provider Backbone Bridges

IEEE 802.1ak, Multiple Registration Protocol

IEEE 802.1aq, Shortest Path Bridging

IEEE 802.1ax, Link Aggregation

IEEE 802.1D, MAC Bridges

IEEE 802.1p, Traffic Class Expediting

IEEE 802.1Q, Virtual LANs

IEEE 802.1s, Multiple Spanning Trees

IEEE 802.1w, Rapid Reconfiguration of Spanning Tree

IEEE 802.1X, Port Based Network Access Control

IEEE 802.3ac, VLAN Tag

IEEE 802.3ad, Link Aggregation

IEEE 802.3ah, Ethernet in the First Mile

IEEE 802.3x, Ethernet Flow Control

ITU-T G.8031/Y.1342, Ethernet Linear Protection Switching

ITU-T G.8032/Y.1344, Ethernet Ring Protection Switching

ITU-T Y.1731, OAM functions and mechanisms for Ethernet based networks

Ethernet VPN (EVPN)

draft-ietf-bess-evpn-igmp-mld-proxy-05, IGMP and MLD Proxy for EVPN

draft-ietf-bess-evpn-irb-mcast-04, EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding - ingress replication

draft-ietf-bess-evpn-pref-df-06, Preference-based EVPN DF Election

draft-ietf-bess-evpn-prefix-advertisement-11, IP Prefix Advertisement in EVPN

draft-ietf-bess-evpn-proxy-arp-nd-08, Operational Aspects of Proxy-ARP/ND in EVPN Networks

draft-ietf-bess-pbb-evpn-isid-cmacflush-00, PBB-EVPN ISID-based CMAC-Flush

RFC 7432, BGP MPLS-Based Ethernet VPN

RFC 7623, Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)

RFC 8214, Virtual Private Wire Service Support in Ethernet VPN

RFC 8317, Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) an Provider Backbone Bridging EVPN (PBB-EVPN)

RFC 8365, A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)

RFC 8560, Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) Equivalents

RFC 8584, DF Election and AC-influenced DF Election

Frame Relay

ANSI T1.617 Annex D, DSS1 - Signalling Specification For Frame Relay Bearer Service

FRF.1.2, PVC User-to-Network Interface (UNI) Implementation Agreement

FRF.12, Frame Relay Fragmentation Implementation Agreement

FRF.16.1, Multilink Frame Relay UNI/NNI Implementation Agreement

FRF.5, Frame Relay/ATM PVC Network Interworking Implementation