Monetization Web Docs | Tridens Technology – AAA Gateway

Docs: Diameter

Mon, 01 Jan 0001 00:00:00 +0000

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

Section Number	Section	Status	Notes
1	Introduction	Not applicable	-
1.1	Diameter Protocol	Not applicable	-
1.1.1	Description of the document set	Not applicable	-
1.2	Approach to extensibility	Not applicable	-
1.2.1	Defining new attribute-value pairs	Not applicable	-
1.2.2	Creating new AVPs	Not applicable	-
1.2.3	Creating new authentication apps	Not applicable	-
1.2.4	Creating new accounting apps	Not applicable	-
1.2.5	Application authentication	Not applicable	-
1.3	Terminology	Not applicable	-
2	Protocol overview	Not applicable	-
2.1	Transport	Supported	Supports TCP and SCTP
2.1.1	SCTP guidelines	Supported	-
2.2	Securing diameter messages	Not supported	-
2.3	Diameter application compliance	Supported	-
2.4	Application identifiers	Supported	-
2.5	Connections vs Sessions	No requirement	-
2.6	Peer table	Supported	-
2.7	Realm-based routing table	Not applicable	-
2.8	Role of diameter agents	Not applicable	-
2.8.1	Relay agents	Not applicable	-
2.8.2	Proxy agents	Not applicable	-
2.8.3	Redirect agents	Not applicable	-
2.8.4	Translation agents	Not applicable	-
2.9	End-to-end security framework	Not supported	-
2.10	Diameter path authorization	Not supported	-
3	Diameter header	Supported	-
3.1	Command codes	Supported	-
3.2	Command code ABNF specification	No requirement	-
3.3	Diameter command naming conventions	Supported	-
4	Diameter AVPs	Supported	-
4.1	AVP header	Supported	-
4.1.1	Optional header elements	Supported	-
4.2	Basic AVP	Supported	-
4.3	Derived AVP data formats	Supported	-
4.4	Grouped AVP values	Supported	-
4.4.1	Example AVP with grouped data type	No requirement	-
4.5	Diameter base protocol AVPs	Supported	-
5	Diameter peers	No requirement	-
5.1	Peer connections	Supported	-
5.2	Diameter peer discovery	Not supported	Diameter Gateway does not support routing, proxy, or relay
5.3	Capabilities exchange	Supported	-
5.3.1	Capabilities-Exchange-Request	Supported	-
5.3.2	Capabilities-Exchange-Answer	Supported	-
5.3.3	Vendor-Id AVP	Supported	-
5.3.4	Firmware-Revision AVP	Supported	-
5.3.5	Host-IP-Address AVP	Not supported	-
5.3.6	Supported-Vendor-Id AVP	Supported	-
5.3.7	Product-Name AVP	Supported	-
5.4	Disconnecting peer connections	Partially supported	Diameter Gateway only responds to messages, does not generate them
5.4.1	Disconnect-Peer-Request	Partially supported	Diameter Gateway only responds to messages, does not generate them
5.4.2	Disconnect-Peer-Answer	Partially supported	Diameter Gateway only responds to messages, does not generate them
5.4.3	Disconnect-Cause AVP	Partially supported	Diameter Gateway only responds to messages, does not generate them
5.5	Transport failure detection	Supported	-
5.5.1	Device-Watchdog-Request	Supported	-
5.5.2	Device-Watchdog-Answer	Supported	-
5.5.3	Transport failure algorithm	Supported	-
5.5.4	Failover and failback procedures	Partially supported	-
5.6	Peer state machine	Supported	-
5.6.1	Incoming connections	Supported	-
5.6.2	Events	Supported	-
5.6.3	Actions	Supported	-
5.6.4	The election process	Supported	-
6	Diameter message processing	No requirement	-
6.1	Diameter request routing overview	No requirement	-
6.1.1	Originating a request	Supported	-
6.1.2	Sending a request	Supported	-
6.1.3	Receiving requests	Supported	-
6.1.4	Processing local requests	Not supported	-
6.1.5	Request forwarding	Not supported	-
6.1.6	Request routing	Not applicable	-
6.1.7	Redirecting requests	Not applicable	-
6.1.8	Relaying and proxying requests	Not applicable	-
6.2	Diameter answer processing	Supported	-
6.2.1	Processing received answers	Supported	-
6.2.2	Relaying and proxying answers	Not applicable	Configurable per Diameter Gateway instance
6.3	Origin-Host AVP	Supported	Configurable per Diameter Gateway instance
6.4	Origin-Realm AVP	Supported	-
6.5	Destination-Host AVP	Supported	-
6.6	Destination-Realm AVP	Supported	-
6.7	Routing AVPs	Not applicable	-
6.7.1	Route-Record AVP	Not applicable	-
6.7.2	Proxy-Info AVP	Not applicable	-
6.7.3	Proxy-Host AVP	Not applicable	-
6.7.4	Proxy-State AVP	Not applicable	-
6.8	Auth-Application-Id AVP	Supported	-
6.9	Acct-Application-Id AVP	Not applicable	-
6.10	Inband-Security-Id AVP	Supported	Supports only 0, where 0 specifies NO_INBAND_SECURITY
6.11	Vendor-Specific-Application-Id AVP	Supported	-
6.12	Redirect-Host AVP	Not applicable	-
6.13	Redirect-Host-Usage AVP	Not applicable	-
6.14	Redirect-Max-Cache-Time AVP	Not applicable	-
6.15	E2E-Sequence AVP	Not applicable	-
7	Error handling	Supported	-
7.1	Result-Code AVP	Supported	-
7.1.1	Informational	Supported	-
7.1.2	Success	Supported	-
7.1.3	Protocol errors	Supported	-
7.1.4	Transient Failures	Supported	-
7.1.5	Permanent Failures	Supported	-
7.2	Error bit	Supported	-
7.3	Error-Message AVP	Not supported	-
7.4	Error-Reporting-Host AVP	Not supported	-
7.5	Failed-AVP AVP	Supported	-
7.6	Experimental-Result AVP	Supported	-
7.7	Experimental-Result-Code AVP	Supported	-
8	Diameter user sessions	No requirement	-
8.1	Authorization session state machine	Supported	-
8.2	Accounting session state machine	Not applicable	-
8.3	Server-Initiated Re-Auth	Supported	-
8.3.1	Re-Auth-Request	Supported	-
8.3.2	Re-Auth-Answer	Supported	-
8.4	Session termination	Supported	-
8.4.1	Session-Termination-Request	Supported	-
8.4.2	Session-Termination-Answer	Supported	-
8.5	Aborting a session	Not supported	-
8.5.1	Abort-Session-Request	Not supported	-
8.5.2	Abort-Session-Answer	Not supported	-
8.6	Inferring session termination from Origin-State-Id	Not supported	-
8.7	Auth-Request-Type AVP	Not applicable	-
8.8	Session-Id AVP	Supported	-
8.9	Authorization-Lifetime AVP	Not applicable	-
8.10	Auth-Grace-Period AVP	Not applicable	-
8.11	Auth-Session-State AVP	Not applicable	-
8.12	Re-Auth-Request-Type AVP	Not applicable	-
8.13	Session-Timeout AVP	Not applicable	-
8.14	User-Name AVP	Not applicable	-
8.15	Termination-Cause AVP	Supported	-
8.16	Origin-State-Id AVP	Not supported	-
8.17	Session-Binding AVP	Not applicable	-
8.18	Session-Server-Failover AVP	Not applicable	-
8.19	Multi-Round-Time-Out AVP	Not applicable	-
8.20	Class AVP	Not applicable	-
8.21	Event-Timestamp AVP	Supported	-
9	Accounting	Not applicable	-
9.1	Server directed model	Not applicable	-
9.2	Protocol messages	Not applicable	-
9.3	Application document requirements	Not applicable	-
9.4	Fault resilience	Not applicable	-
9.5	Accounting records	Not applicable	-
9.6	Correlation of accounting records	Not applicable	-
9.7	Accounting Command-Codes	Not applicable	-
9.7.1	Accounting-Request	Not applicable	-
9.7.2	Accounting-Answer	Not applicable	-
9.8	Accounting AVPs	Not applicable	-
9.8.1	Accounting-Record-Type AVP	Not applicable	-
9.8.2	Acct-Interim-Interval AVP	Not applicable	-
9.8.3	Accounting-Record-Number AVP	Not applicable	-
9.8.4	Acct-Session-Id AVP	Not applicable	-
9.8.5	Acct-Multi-Session-Id AVP	Not applicable	-
9.8.6	Accounting-Sub-Session-Id AVP	Not applicable	-
9.8.7	Accounting-Realtime-Required AVP	Not applicable	-
10	AVP occurrence table	No requirement	-
10.1	Base protocol command AVP Table	No requirement	-
10.2	Accounting AVP Table	No requirement	-
11	IANA Considerations	No requirement	-
11.1	AVP header	No requirement	-
11.1.1	AVP code	No requirement	-
11.1.2	AVP flags	No requirement	-
11.2	Diameter header	No requirement	-
11.2.1	Command codes	No requirement	-
11.2.2	Command Flags	No requirement	-
11.3	Application identifiers	No requirement	-
11.4	AVP Values	No requirement	-
11.4.1	Result-Code AVP Values	No requirement	-
11.4.2	Accounting-Record-Type AVP Values	No requirement	-
11.4.3	Termination-Cause AVP Values	No requirement	-
11.4.4	Redirect-Host-Usage AVP Values	No requirement	-
11.4.5	Session-Server-Failover AVP Values	No requirement	-
11.4.6	Session-Binding AVP Values	No requirement	-
11.4.7	Disconnect-Cause AVP Values	No requirement	-
11.4.8	Auth-Request-Type AVP Values	No requirement	-
11.4.9	Auth-Session-State AVP Values	No requirement	-
11.4.10	Re-Auth-Request-Type AVP Values	No requirement	-
11.4.11	Accounting-Realtime-Required AVP Values	No requirement	-
11.5	Diameter TCP/SCTP port numbers	No requirement	-
11.6	Naming authority pointer (NAPTR) Service Fields	No requirement	-
12	Diameter Protocol Related Configurable Parameters	Supported	-
13	Security considerations	Not supported	-
13.1	IPsec usage	Not supported	-
13.2	TLS usage	Not supported	-
13.3	Peer-to-Peer Considerations	Not supported	-
14	References	No requirement	-
14.1	Normative References	No requirement	-
14.2	Informative References	No requirement	-
15	Acknowledgements	No requirement	-
Appendix A	Diameter service template	No requirement	-
Appendix B	NAPTR example	No requirement	-
Appendix C	Duplicate detection	Supported	-

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

Section Number	Section	Status	Notes
1	Scope	Not applicable	-
2	References	Not applicable	-
3	Definitions, symbols and abbreviations	Not applicable	-
3.1	Definitions	Not applicable	-
3.2	Symbols	Not applicable	-
3.3	Abbreviations	Not applicable	-
4	Architecture considerations	Supported	-
4.1	High level architecture	Supported	-
4.1.0	General	Supported	-
4.1.1	Charging related transfer requirements	Supported	-
5	3GPP charging applications requirements	Supported	-
5.1	Offline charging scenarios	Supported	-
5.1.1	Basic principles	Supported	-
5.1.1.0	Introduction	Supported	-
5.1.1.1	Event based charging	Supported	-
5.1.1.2	Session based charging	Supported	-
5.1.2	Basic operation	Supported	-
5.2	Online charging scenarios	Supported	-
5.2.0	Introduction	Supported	-
5.2.1	Basic principles	Supported	-
5.2.2	Charging scenarios	Supported	-
5.2.2.0	Introduction	Supported	-
5.2.2.1	Immediate event charging (IEC)	Supported	-
5.2.2.1.1	Decentralized unit determination and centralized rating	Not supported	-
5.2.2.1.2	Centralized unit determination and centralized rating	Supported	-
5.2.2.1.3	Decentralized unit determination and decentralized rating	Not supported	-
5.2.2.1.4	Further options	Supported	-
5.2.2.2	Event charging with unit reservation (ECUR)	Supported	-
5.2.2.2.1	Decentralized unit determination and centralized rating	Not supported	-
5.2.2.2.2	Centralized unit determination and centralized rating	Supported	-
5.2.2.2.3	Decentralized unit determination and decentralized rating	Not supported	-
5.2.2.3	Session charging with reservation	Supported	-
5.2.2.3.1	Decentralized unit determination and centralized rating	Not supported	-
5.2.2.3.2	Centralized unit determination and centralized rating	Supported	-
5.2.2.3.3	Decentralized unit determination and decentralized rating	Not supported	-
5.2.3	Basic operations	Supported	-
5.3	Other requirements	Supported	-
5.3.1	Re-authorization	Supported	-
5.3.2	Threshold based re-authorization triggers	Supported	-
5.3.3	Termination action	Supported	-
5.3.4	Account expiration	Not supported	-
6	3GPP charging applications – protocol aspects	Supported	-
6.1	Basic principles for diameter offline charging	Supported	-
6.1.0	Introduction	Supported	-
6.1.1	Event based charging	Supported	-
6.1.2	Session based charging	Supported	-
6.1.3	Offline charging error cases - diameter procedures	Supported	-
6.1.3.1	Charging data function (CDF) connection failure	Supported	-
6.1.3.2	No reply from CDF	Supported	-
6.1.3.3	Duplicate detection	Supported	-
6.1.3.4	CDF detected failure	Supported	-
6.2	Message contents for offline charging	Not supported	-
6.2.1	Summary of offline charging message formats	Not supported	-
6.2.1.1	General	Not supported	-
6.2.1.2	Structure for the accounting message formats	Not supported	-
6.2.2	Accounting-Request message	Not supported	-
6.2.3	Accounting-Answer (ACA) message	Not supported	-
6.3	Basic principles for diameter online charging	Supported	-
6.3.1	Online specific Credit-Control application requirements	Supported	-
6.3.2	Diameter description on the Ro reference point	Supported	-
6.3.2.1	Basic principles	Supported	-
6.3.3	Immediate event charging (IEC)	Supported	-
6.3.4	Event charging with unit reservation (ECUR)	Supported	-
6.3.5	Session charging with unit reservation (SCUR)	Supported	-
6.3.6	Error cases and scenarios	Supported	-
6.3.6.0	Introduction	Supported	-
6.3.6.1	Duplicate detection	Supported	-
6.3.6.2	Reserve units/Debit units operation failure	Supported	-
6.3.7	Support of tariff changes during an active user session	Supported	-
6.3.7.1	Support of tariff changes using the tariff switch mechanism	Supported	-
6.3.7.2	Support of tariff changes using Validity-Time attribute-value pair (AVP)	Not supported	-
6.3.8	Support of re-authorization	Supported	-
6.3.9	Support of failure handling	Supported	-
6.3.10	Support of failover	Supported	-
6.3.11	Credit pooling	Not supported	-
6.4	Message formats for online charging	Supported	-
6.4.1	Summary of online charging message formats	Supported	-
6.4.1.1	General	Supported	-
6.4.1.2	Structure for the Credit-Control message formats	Supported	-
6.4.2	Credit-Control-Request message	Supported	-
6.4.3	Credit-Control-Answer message	Supported	-
6.4.4	Re-Auth-Request message	Supported	-
6.4.5	Re-Auth-Answer message	Supported	-
6.4.6	Capabilities-Exchange-Request-message	Supported	-
6.4.7	Capabilities-Exchange-Answer message	Supported	-
6.4.8	Device-Watchdog-Request message	Supported	-
6.4.9	Device-Watchdog-Answer message	Supported	-
6.4.10	Disconnect-Peer-Request message	Partially supported	-
6.4.11	Disconnect-Peer-Answer message	Partially supported	-
6.4.12	Abort-Session-Request message	Not supported	-
6.4.13	Abort-Session-Answer message	Not supported	-
6.5	Other procedural description of the 3GPP charging applications	Supported	-
6.5.1	Re-Authorization	Supported	-
6.5.1.1	Idle timeout	Supported	-
6.5.1.2	Change of charging conditions	Not supported	-
6.5.1.3	Reporting quota usage	Not supported	-
6.5.1.4	Quota consumption	Not supported	-
6.5.2	Threshold based Re-Authorization triggers	Supported	-
6.5.3	Termination action	Supported	-
6.5.4	Quota consumption time	Supported	-
6.5.5	Service termination	Not supported	-
6.5.6	Envelope reporting	Not supported	-
6.5.7	Combinational quota	Not supported	-
6.5.8	Online control of offline charging information	Supported	-
6.5.9	Support of multiple service	Supported	-
6.6	Bindings of the operation to protocol application	Supported	-
6.6.0	General	Supported	-
6.6.1	Bindings of charging data transfer to accounting	Supported	-
6.6.2	Bindings of debit/reserve units to Credit-Control	Supported	-
7	Summary of used attribute-value pairs (AVPs)	Not applicable	-
7.1	Diameter attribute-value pairs (AVPs)	Not applicable	-
7.1.0	General	Not applicable	-
7.1.1	Accounting-Input-Octets AVP	Not supported	-
7.1.2	Void	Not applicable	-
7.1.3	Accounting-Output-Octets AVP	Not supported	-
7.1.4	Void	Not applicable	-
7.1.5	Acct-Application-Id AVP	Supported	-
7.1.6	Auth-Application-Id AVP	Supported	-
7.1.7	Called-Station-Id AVP	Supported	-
7.1.8	Event-Timestamp AVP	Supported	-
7.1.9	Multiple-Services-Credit-Control AVP	Supported	-
7.1.10	Rating-Group AVP	Supported	-
7.1.11	Result-Code AVP	Supported	-
7.1.12	Service-Context-Id AVP	Supported	-
7.1.13	Service-Identifier AVP	Supported	-
7.1.14	Used-Service-Unit AVP	Supported	-
7.1.15	User-Name AVP	Supported	-
7.1.16	Vendor-Id AVP	Supported	-
7.1.17	User-Equipment-Info AVP	Supported	-
7.2	3GPP specific AVPs	Not supported	-
7.2.0	General	Not supported	-
7.2.1	Access-Network-Information AVP	Not supported	-
7.2.1A	Access-Transfer-Information AVP	Not supported	-
7.2.1B	Access-Transfer-Type AVP	Not supported	-
7.2.2	Account-Expiration AVP	Not supported	-
7.2.3	Accumulated-Cost AVP	Not supported	-
7.2.4	Adaptations AVP	Not supported	-
7.2.5	Additional-Content-Information AVP	Not supported	-
7.2.6	Additional-Type-Information AVP	Not supported	-
7.2.7	Address-Data AVP	Not supported	-
7.2.8	Address-Domain AVP	Not supported	-
7.2.9	Address-Type AVP	Not supported	-
7.2.10	Addressee-Type AVP	Not supported	-
7.2.11	AF-Correlation-Information AVP	Supported	-
7.2.12	Alternate-Charged-Party-Address AVP	Not supported	-
7.2.13	AoC-Cost-Information AVP	Not supported	-
7.2.14	AoC-Format AVP	Not supported	-
7.2.15	AoC-Information AVP	Supported	-
7.2.16	AoC-Request-Type AVP	Supported	-
7.2.17	AoC-Service AVP	Not supported	-
7.2.18	AoC-Service-Obligatory-Type AVP	Not supported	-
7.2.19	AoC-Service-Type AVP	Not supported	-
7.2.20	AoC-Subscription-Information AVP	Not supported	-
7.2.21	Applic-ID AVP	Not supported	-
7.2.22	Application-provided-Called-Party-Address AVP	Not supported	-
7.2.23	Application-Server AVP	Not supported	-
7.2.24	Application-Server-Information AVP	Not supported	-
7.2.25	Associated-Party-Address AVP	Not supported	-
7.2.26	Associated-URI AVP	Not supported	-
7.2.27	Authorised-QoS AVP	Not supported	-
7.2.28	Aux-Applic-Info AVP	Not supported	-
7.2.29	Base-Time-Interval AVP	Supported	-
7.2.29A	Basic-Service-Code AVP	Not supported	-
7.2.29B	Bearer-Capability AVP	Not supported	-
7.2.30	Bearer-Service AVP	Not supported	-
7.2.30A	Basic service set identifier (BSSID) AVP	Not supported	-
7.2.31	Called-Asserted-Identity AVP	Not supported	-
7.2.32	Called-Party-Address AVP	Not supported	-
7.2.33	Calling-Party-Address AVP	Not supported	-
7.2.34	Carrier-Select-Routing-Information AVP	Not supported	-
7.2.35	Cause-Code AVP	Not supported	-
7.2.36	CG-Address AVP	Supported	-
7.2.37	Change-Condition AVP	Supported	-
7.2.38	Change-Time AVP	Not supported	-
7.2.38A	Charge-Reason-Code AVP	Not supported	-
7.2.39	Charged-Party AVP	Not supported	-
7.2.39A	Charging-Characteristics-Selection-Mode AVP	Not supported	-
7.2.40	Class-Identifier AVP	Not supported	-
7.2.41	Client-Address AVP	Not supported	-
7.2.41A	CN-Operator-Selection-Entity AVP	Not supported	-
7.2.42	Content-Class AVP	Not supported	-
7.2.43	Content-Disposition AVP	Not supported	-
7.2.44	Content-Length AVP	Not supported	-
7.2.45	Content-Size AVP	Not supported	-
7.2.46	Content-Type AVP	Not supported	-
7.2.46A	CSG-Access-Mode AVP	Supported	-
7.2.46B	CSG-Membership-Indication AVP	Supported	-
7.2.47	Current-Tariff AVP	Not supported	-
7.2.48	CUG-Information AVP	Not supported	-
7.2.49	Data-Coding-Scheme AVP	Not supported	-
7.2.50	DCD-Information AVP	Supported	-
7.2.51	Deferred-Location-Event-Type AVP	Not supported	-
7.2.52	Delivery-Report-Requested AVP	Not supported	-
7.2.53	Destination-Interface AVP	Not supported	-
7.2.54	Diagnostics AVP	Supported	-
7.2.55	Domain-Name AVP	Not supported	-
7.2.56	DRM-Content AVP	Not supported	-
7.2.57	Dynamic-Address-Flag AVP	Supported	-
7.2.57A	Dynamic-Address-Flag-Extension AVP	Not supported	-
7.2.58	Early-Media-Description AVP	Not supported	-
7.2.59	Envelope AVP	Supported	-
7.2.60	Envelope-End-Time AVP	Supported	-
7.2.61	Envelope-Reporting AVP	Supported	-
7.2.62	Envelope-Start-Time AVP	Supported	-
7.2.62A	ePDG-Address AVP	Not supported	-
7.2.63	Event AVP	Not supported	-
7.2.64	Event-Charging-TimeStamp AVP	Supported	-
7.2.65	Event-Type AVP	Not supported	-
7.2.66	Expires AVP	Not supported	-
7.2.67	File-Repair-Supported AVP	Not supported	-
7.2.67A	Forwarding-Pending AVP	Not supported	-
7.2.67B	From-Address AVP	Not supported	-
7.2.68	GGSN-Address AVP	Supported	-
7.2.69	IM-Information AVP	Supported	-
7.2.70	Incremental-Cost AVP	Not supported	-
7.2.70A	Instance-Id AVP	Not supported	-
7.2.71	Interface-Id AVP	Not supported	-
7.2.72	Interface-Port AVP	Not supported	-
7.2.73	Interface-Text AVP	Not supported	-
7.2.74	Interface-Type AVP	Not supported	-
7.2.74A	IMS-Application-Reference-Identifier AVP	Not supported	-
7.2.75	IMS-Charging-Identifier AVP	Not supported	-
7.2.76	IMS-Communication-Service-Identifier AVP	Not supported	-
7.2.76A	IMS-Emergency-Indicator AVP	Not supported	-
7.2.77	IMS-Information AVP	Supported	-
7.2.77A	IMS-Visited-Network-Identifier AVP	Not supported	-
7.2.78	IMSI-Unauthenticated-Flag AVP	Not supported	-
7.2.79	Incoming-Trunk-Group-ID AVP	Not supported	-
7.2.79A	Initial-IMS-Charging-Identifier AVP	Not supported	-
7.2.80	Inter-Operator-Identifier AVP	Not supported	-
7.2.80A	IP-Realm-Default-Indication AVP	Not supported	-
7.2.80B	ISUP-Cause AVP	Not supported	-
7.2.80C	ISUP-Cause-Diagnostics AVP	Not supported	-
7.2.80D	ISUP-Cause-Location AVP	Not supported	-
7.2.80E	ISUP-Cause-Value AVP	Not supported	-
7.2.80F	ISUP-Location-Number AVP	Not supported	-
7.2.81	LCS-APN AVP	Not supported	-
7.2.82	LCS-Client-Dialed-By-MS AVP	Not supported	-
7.2.83	LCS-Client-External-ID AVP	Not supported	-
7.2.84	LCS-Client-ID AVP	Not supported	-
7.2.85	LCS-Client-Name AVP	Not supported	-
7.2.86	LCS-Client-Type AVP	Not supported	-
7.2.87	LCS-Data-Coding-Scheme AVP	Not supported	-
7.2.88	LCS-Format-Indicator AVP	Not supported	-
7.2.89	LCS-Information AVP	Supported	-
7.2.90	LCS-Name-String AVP	Not supported	-
7.2.91	LCS-Requestor-ID AVP	Not supported	-
7.2.92	LCS-Requestor-ID-String AVP	Not supported	-
7.2.92A	Local-GW-Inserted-Indication AVP	Not supported	-
7.2.93	Local-Sequence-Number AVP	Not supported	-
7.2.94	Location-Estimate AVP	Not supported	-
7.2.95	Location-Estimate-Type AVP	Not supported	-
7.2.96	Location-Type AVP	Not supported	-
7.2.97	Low-Balance-Indication AVP	Supported	-
7.2.97A	Low-Priority-Indicator AVP	Not supported	-
7.2.97B	MBMS-Charged-Party AVP	Not supported	-
7.2.98	MBMS-GW-Address AVP	Not supported	-
7.2.99	MBMS-Information AVP	Supported	-
7.2.100	MBMS-User-Service-Type AVP	Not supported	-
7.2.101	Media-Initiator-Flag AVP	Not supported	-
7.2.102	Media-Initiator-Party AVP	Not supported	-
7.2.103	Message-Body AVP	Not supported	-
7.2.104	Message-Class AVP	Not supported	-
7.2.105	Message-ID AVP	Not supported	-
7.2.106	Message-Size AVP	Not supported	-
7.2.107	Message-Type AVP	Not supported	-
7.2.108	MM-Content-Type AVP	Not supported	-
7.2.109	MMBox-Storage-Requested AVP	Not supported	-
7.2.110	MMS-Information AVP	Supported	-
7.2.111	MMTel-Information AVP	Supported	-
7.2.111A	MMTel-Service-Type AVP	Not supported	-
7.2.111B	MSC-Address AVP	Not supported	-
7.2.111C	MTC-IWF-Address AVP	Not supported	-
7.2.111D	Neighbour-Node-Address AVP	Not supported	-
7.2.112	Next-Tariff AVP	Not supported	-
7.2.112A	NNI-Information AVP	Not supported	-
7.2.112B	NNI-Type AVP	Not supported	-
7.2.113	Node-Functionality AVP	Not supported	-
7.2.114	Node-Id AVP	Supported	-
7.2.115	Number-Of-Diversions AVP	Not supported	-
7.2.116	Number-Of-Messages-Sent AVP	Not supported	-
7.2.117	Number-Of-Participants AVP	Not supported	-
7.2.118	Number-Of-Received-Talk-Bursts AVP	Not supported	-
7.2.119	Number-Of-Talk-Bursts AVP	Not supported	-
7.2.120	Number-Portability-Routing-Information AVP	Not supported	-
7.2.121	Offline-Charging AVP	Supported	-
7.2.122	Online-Charging-Flag AVP	Not supported	-
7.2.123	Originating-IOI AVP	Not supported	-
7.2.124	Originator AVP	Not supported	-
7.2.125	Originator-Address AVP	Not supported	-
7.2.126	Originator-Interface AVP	Not supported	-
7.2.127	Originator-Received-Address AVP	Not supported	-
7.2.128	Originator-SCCP-Address	Not supported	-
7.2.128A	Outgoing-Session-Id AVP	Not supported	-
7.2.129	Outgoing-Trunk-Group-ID AVP	Not supported	-
7.2.185	SDP-TimeStamps AVP	Not supported	-
7.2.186	SDP-Type AVP	Not supported	-
7.2.186A	Session-Direction AVP	Not supported	-
7.2.187	Served-Party-IP-Address AVP	Not supported	-
7.2.188	Void	Not applicable	-
7.2.189	Service-Data-Container AVP	Supported	-
7.2.190	Service-ID AVP	Not supported	-
7.2.191	Service-Generic-Information AVP	Supported	-
7.2.192	Service-Information AVP	Supported	-
7.2.193	Service-Mode AVP	Not supported	-
7.2.194	Service-Specific-Data AVP	Not supported	-
7.2.195	Service-Specific-Info AVP	Supported	-
7.2.196	Service-Specific-Type AVP	Not supported	-
7.2.197	Void	Not applicable	-
7.2.198	Serving-Node-Type AVP	Supported	-
7.2.199	SGSN-Address AVP	Supported	-
7.2.199A	SGW-Address AVP	Not applicable	-
7.2.200	SGW-Change AVP	Supported	-
7.2.201	SIP-Method AVP	Not supported	-
7.2.202	SIP-Request-Timestamp AVP	Not supported	-
7.2.203	SIP-Request-Timestamp-Fraction AVP	Not supported	-
7.2.204	SIP-Response-Timestamp AVP	Not supported	-
7.2.205	SIP-Response-Timestamp-Fraction AVP	Not supported	-
7.2.205A	SM-Device-Trigger-Indicator AVP	Not supported	-
7.2.205B	SM-Device-Trigger-Information AVP	Not supported	-
7.2.206	SM-Discharge-Time AVP	Not supported	-
7.2.207	SM-Message-Type AVP	Not supported	-
7.2.208	SM-Protocol-Id AVP	Not supported	-
7.2.208A	SM-Sequence-Number AVP	Not supported	-
7.2.209	SM-Status AVP	Not supported	-
7.2.210	SM-User-Data-Header AVP	Not supported	-
7.2.211	SMS-Information AVP	Supported	-
7.2.212	SMS-Node AVP	Not supported	-
7.2.212A	SMS-Result AVP	Not supported	-
7.2.213	SM-Service-Type AVP	Not supported	-
7.2.214	SMSC-Address AVP	Not supported	-
7.2.214A	Start-of-Charging AVP	Not supported	-
7.2.215	Start-Time AVP	Supported	-
7.2.215A	Status-Code AVP	Not supported	-
7.2.216	Stop-Time AVP	Supported	-
7.2.217	Submission-Time AVP	Not supported	-
7.2.218	Subscriber-Role AVP	Not supported	-
7.2.219	Supplementary-Service AVP	Not supported	-
7.2.219A	TAD-Identifier AVP	Not supported	-
7.2.220	Talk-Burst-Exchange AVP	Not supported	-
7.2.221	Talk-Burst-Time AVP	Not supported	-
7.2.222	Talk-Burst-Volume AVP	Not supported	-
7.2.223	Tariff-Information AVP	Not supported	-
7.2.224	Tariff-XML AVP	Not supported	-
7.2.224A	Teleservice AVP	Not supported	-
7.2.225	Terminating-IOI AVP	Not supported	-
7.2.226	Time-First-Usage AVP	Not supported	-
7.2.227	Time-Last-Usage AVP	Not supported	-
7.2.228	Time-Quota-Mechanism	Supported	-
7.2.229	Time-Quota-Threshold AVP	Supported	-
7.2.230	Time-Quota-Type AVP	Supported	-
7.2.231	Time-Stamps AVP	Not supported	-
7.2.232	Time-Usage AVP	Not supported	-
7.2.233	Traffic-Data-Volumes AVP	Supported	-
7.2.233A	Transcoder-Inserted-Indication AVP	Not supported	-
7.2.233B	Transit-IOI-List AVP	Not supported	-
7.2.234	Token-Text AVP	Not supported	-
7.2.235	Trigger AVP	Supported	-
7.2.236	Trigger-Type AVP	Supported	-
7.2.237	Trunk-Group-ID AVP	Not supported	-
7.2.237A	Void	Not applicable	-
7.2.237B	Void	Not applicable	-
7.2.237C	TWAN-User-Location-Info AVP	Not supported	-
7.2.238	Type-Number AVP	Not supported	-
7.2.239	Unit-Cost AVP	Not supported	-
7.2.240	Unit-Quota-Threshold AVP	Supported	-
7.2.240A	User-CSG-Information AVP	Not supported	-
7.2.241	User-Participating-Type AVP	Not supported	-
7.2.242	User-Session-Id AVP	Not supported	-
7.2.242A	VCS-Information AVP	Not supported	-
7.2.242B	VLR-Number AVP	Not supported	-
7.2.243	Volume-Quota-Threshold AVP	Supported	-
7.2.244	Void	Not applicable	-
7.2.245	Void	Not applicable	-
7.2.246	Void	Not applicable	-
7.2.247	Void	Not applicable	-
7.2.248	Void	Not applicable	-
7.2.249	Void	Not applicable	-
7.2.250	Void	Not applicable	-
7.3	3GPP2 access specific AVPs	Not applicable	-
7.4	Fixed access specific AVPs	Not applicable	-

Diameter Session Commands

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

Table 2-2: Diameter Session Commands

Diameter Command	Status	Notes
Credit-Control-Request	Supported	-
Credit-Control-Answer	Supported	-

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

Diameter Gy Message	Status	Notes
Session Charging	Supported	-
Top-Up	Supported	-
Balance-Query	Supported	Supports both summary and detailed Balance-Query modes
Debit/Refund	Supported	-
Price Enquiry	Supported	-

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

Diameter AVP	Status	Notes
Session-Id	Supported	-
Service-Context-Id	Supported	-
CC-Request-Type	Supported	1 - INITIATE 2 - UPDATE 3 - TERMINATE
CC-Request-Number	Supported	-
Event-Timestamp	Supported	-
Subscription-Id	Supported	-
– Subscription-Id-Data	Supported	-
– Subscription-Id-Type	Supported	-
Termination-Cause	Supported	-
Service-Information	Supported	-
– PS-Information	Supported	-
– – Called-Station-Id	Supported	-
– – SGSN-Address	Supported	-
– – GGSN-Address	Supported	-
– – MS-TimeZone-3GPP	Supported	-
– – Diagnostics	Supported	-
User-Name	Not supported	Subscription-Id-Data AVP is used instead
Multiple-Services-Credit-Control	Supported	See Table 2-5 for more information.

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

Diameter AVP	Status	Notes
Service-Identifier	Supported	-
Rating-Group	Supported	-
Requested-Service-Unit	Supported	-
– CC-Time	Supported	-
– CC-Money	Not supported	-
– CC-Total-Octets	Supported	-
– CC-Input-Octets	Supported	-
– CC-Output-Octets	Supported	-
– CC-Service-Specific-Units	Supported	-
Used-Service-Unit	Supported	-
– CC-Time	Supported	-
– CC-Money	Not supported	-
– CC-Total-Octets	Supported	-
– CC-Input-Octets	Supported	-
– CC-Output-Octets	Supported	-
– CC-Service-Specific-Units	Supported	-

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

Diameter AVP	Status	Notes
Session-Id	Supported	-
Result-Code	Supported	-
CC-Request-Type	Supported	-
CC-Session-Failover	Supported	-
Credit-Control-Failure-Handling	Supported	-
Multiple-Services-Credit-Control	Supported	See Table 2-7 for more info

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

Diameter AVP	Status	Notes
Requested-Service-Unit	Supported	Contains the AVPs submitted in the message request.
Granted-Service-Unit	Supported	-
– CC-Time	Supported	-
– CC-Money	Not supported	-
– CC-Total-Octets	Supported	-
– CC-Input-Octets	Supported	-
– CC-Output-Octets	Supported	-
– CC-Service-Specific-Units	Supported	-
– Cost-Information	Supported	-
– – Unit-Value	Supported	-
– – – Value-Digits	Supported	-
– – – Exponent	Supported	-
– – Currency-Code	Supported	-
ORA-Customer-Cost-Information	Supported	-
– ORA-Subscriber-Id	Supported	-
– ORA-Cost-Information	Supported	-
– – Unit-Value	Supported	-
– – – Value-Digits	Supported	-
– – – Exponent	Supported	-
– – ORA-Balance-Element-Id	Supported	-
ORA-Remaining-Balance	Supported	-
– ORA-Balance-Element	Supported	-
– – ORA-Balance-Element-Id	Supported	-
– – Unit-Value	Supported	-
– – – Value-Digits	Supported	-
– – – Exponent	Supported	-
– – ORA-Balance-Item	Supported	-
– ORA-Subscriber-Id	Supported	-
ORA-Credit-Threshold-Breach	Supported	-
– ORA-Balance-Element-Id	Supported	-
– ORA-Current-Balance	Supported	-
– ORA-Fixed-Threshold-Values	Supported	-
– – ORA-Fixed-Threshold	Supported	-
ORA-Percentage-Threshold-Values	Supported	-
– ORA-Percentage-Threshold	Supported	-
– ORA-Breach-Direction	Supported	0 - THRESHOLD_BREACH_UP
		1 - THRESHOLD_BREACH_DOWN
Final-Unit-Indication	Partially supported	TERMINATE and REDIRECT are supported.
Validity-Time	Supported	-
Result-Code	Supported	-

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

Diameter AVP	Status	Notes
CC-Request-Type	Supported	4 - EVENT_REQUEST
Requested-Action	Supported	4 - TOP-UP
Subscription-Id	Supported	-
– Subscription-Id-Type	Supported	-
– Subscription-Id-Data	Supported	-
Event-Timestamp	Supported	-
Rating-Group	Supported	-
Service-Identifier	Supported	-
ORA-Account-Topup	Supported	-
– ORA-Recharge-Reference	Supported	-
– ORA-Balance	Supported	-
– – ORA-Balance-Element-Id	Supported	-
– – Unit-Value	Supported	-
– – – Value-Digits	Supported	-
– – – Exponent	Supported	-
– – ORA-Validity-Start-Time	Supported	-
– – ORA-Validity-End-Time	Supported	-
– – ORA-Validity-Start-Relative	Supported	-
– – – ORA-Validity-Offset	Supported	-
– – – ORA-Validity-Unit	Supported	0 - SECONDS
		1- MINUTES
		2 - HOURS
		3 - DAYS
		4 - MONTHS
		5 - ACC_CYCLE
		6 - BILL_CYCLE
		7 - ABSOLUTE
		8 - INFINITE
– – ORA-Validity-End-Relative	Supported	-
– – – ORA-Validity-Offset	Supported	-
– – – ORA-Validity-Unit	Supported	0 - SECONDS
		1- MINUTES
		2 - HOURS
		3 - DAYS
		4 - MONTHS
		5 - ACC_CYCLE
		6 - BILL_CYCLE
		7 - ABSOLUTE
		8 - INFINITE
– – ORA-First-Usage-Validity	Supported	-
– – – ORA-Validity-Offset	Supported	-
– – – ORA-Validity-Unit	Supported	0 - SECONDS
		1- MINUTES
		2 - HOURS
		3 - DAYS
		4 - MONTHS
		5 - ACC_CYCLE
		6 - BILL_CYCLE
		7 - ABSOLUTE
		8 - INFINITE
– – ORA-Extend-Bucket-Validity	Supported	0 - FALSE
		1 - TRUE
– – Service-Identifier	Supported	-
– – Rating-Group	Supported	-
Multi-Services-Indicator	Not supported	Does not apply

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

Diameter AVP	Status	Notes
ORA-Remaining-Balance	Supported	-
– ORA-Balance-Element	Supported	-
– ORA-Applicable-Services	Supported	-
– – Service-Identifier	Supported	-
– – Rating-Group	Supported	-
– ORA-Balance-Element	Supported	-
– – Unit-Value	Supported	-
– – – Value-Digits	Supported	-
– – – Exponent	Supported	-
– – ORA-Balance-Item	Supported	-
– – – Unit-Value	Supported	-
– – – – Value-Digits	Supported	-
– – – – Exponent	Supported	-
– – – ORA-Validity-Start-Time	Supported	-
– – – ORA-Validity-End-Time	Supported	-
– – ORA-Earliest-Expiry-Time	Supported	-
CC-Session-Failover	Supported	-
Credit-Control-Failure-Handling	Supported	-

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

Diameter AVP	Status	Notes
CC-Request-Type	Supported	4 - EVENT_REQUEST
Requested-Action	Supported	5 - BALANCE_QUERY
Event-Timestamp	Supported	-
Subscription-Id	Supported	-
– Subscription-Id-Data	Supported	-
– Subscription-Id-Type	Supported	-
Service-Identifier	Supported	-
Rating Group	Supported	-
ORA-Balance-Query-Mode	Supported	1- Summary
		2 - Detailed
Multi-Services-Indicator	Not supported	Does not apply

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

Diameter AVP	Status	Notes
Service-Identifier	Supported	Returned only when it is set in the original request; indicates the corresponding product for which the Balance query is returned.
Rating-Group	Supported	Returned only when it is set in the original request; indicates the corresponding product for which the Balance query is returned.
ORA-Balance-Details	Supported
– ORA-Balance-Element	Supported
—- ORA-Balance-Element-Id	Supported
—- Unit-Value	Supported
—— Value-Digits	Supported
—— Exponent	Supported
—- ORA-Earliest-Expiry-Time	Supported
—- ORA-Balance-Item	Supported
—— Unit-Value	Supported
——– Value-Digits	Supported
——– Exponent	Supported
—— ORA-Validity-Start-Time	Supported
—— ORA-Validity-End-Time	Supported
—— ORA-Consumed-Reservation-Amount	Supported
——– Value-Digits	Supported
——– Exponent	Supported
—— ORA-Active-Reservation-Amount	Supported
——– Value-Digits	Supported
——– Exponent	Supported
—- ORA-Credit-Floor	Supported
—— Value-Digits	Supported
—— Exponent	Supported
—- ORA-Credit-Ceiling	Supported
—— Value-Digits	Supported
—— Exponent	Supported
—- ORA-Percent-Credit-Threshold	Supported
—— ORA-Threshold-Value	Supported
—- ORA-Fixed-Credit-Threshold	Supported
—— ORA-Threshold-Value	Supported
CC-Session-Failover	Supported
Credit-Control-Failure-Handling	Supported

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

Diameter AVP	Status	Notes
Session-Id	Supported	-
Service-Context-Id	Supported	-
CC-Request-Type	Supported	-
CC-Request-Number		-
Refund-Information	Supported	-
CC-Correlation-Id	Supported	-
Destination-Host	Not supported	-
User-Name	Not supported	Subscription-Id-Data AVP is used instead
CC-Sub-Session-Id	Not supported	-
Acct-Multi-Session-Id	Not supported	-
Origin-State-Id	Not supported	-
Event-Timestamp	Supported	-
Subscription-Id	Supported	-
– Subscription-Id-Data	Supported	-
– Subscription-Id-Type	Supported	-
Requested-Action	Supported	0 - DIRECT_DEBITING
		1 - REFUND_ACCOUNT.
		For more information, see: RFC 4006 Section 8.41
Multiple-Services-Indicator	Supported	Always expected to be True
Service-Parameter-Info	Not supported	-
User-Equipment-Info	Not supported	-
Proxy-Info	Not supported	-
Route-Record	Not supported	-
Service-Information	Supported	-
– PS-Information	Supported	-
– – Called-Station-Id	Supported	-
– – MS-TimeZone-3GPP	Supported	-
Multiple-Services-Credit-Control	Supported	See Table 2-13

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

Diameter AVP	Status	Notes
Service-Identifier	Supported	-
Rating-Group	Supported	-
Requested-Service-Unit	Supported	-
– CC-Time	Supported	-
– CC-Money	Supported	-
– – Unit-Value		-
– – – Value-Digits		-
– – – Exponent	Supported	-
– – Currency-Code	Supported	-
CC-ORA-Balance-Element	Supported	-
– – Unit-Value		-
– – – Value-Digits		-
– – – Exponent	Supported	-
– – ORA-Balance-Element-Id	Supported	-
CC-Total-Octets	Supported	-
CC-Input-Octets	Supported	-
CC-Output-Octets	Supported	-
CC-Service-Specific-Units	Supported	-

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

Diameter AVP	Status	Notes
Session-Id	Supported	-
Result-Code	Supported	-
Remaining-Balance	Supported	-
Cost-Information	Supported	-
ORA-Customer-Cost-Information	Supported	-
CC-Session-Failover	Supported	-
Credit-Control-Failure-Handling	Supported	-
Direct-Debiting-Failure-Handling	Supported	-
Multiple-Services-Credit-Control	Supported	See Table 2-15

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

Diameter AVP	Status	Notes
Result-Code	Supported	-
Service-Identifier	Supported	-
Rating-Group	Supported	-
Refund-Information	Supported	Only for refund
Granted-Service-Units	Supported	Supplied only in a debit response
Requested-Service-Unit	Supported	Contains the AVPs submitted in the message request
ORA-Remaining-Balance	Supported	-
ORA-Customer-Cost-Information	Supported	-
ORA-Cost-Information	Supported	-
ORA-Subscriber-Id	Supported	-
ORA-Balance-Element	Supported	-
ORA-Balance-Element-Id	Supported	-
CC-Time	Supported	-
CC-Money	Supported	-
Unit-Value	Supported	-
Value-Digits	Supported	-
Exponent	Supported	-
Currency-Code	Supported	-
CC-Total-Octets	Supported	-
CC-Input-Octets	Supported	-
CC-Output-Octets	Supported	-
CC-Service-Specific-Units	Supported	-

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

Diameter AVP	Status	Notes
Session-Id	Supported	-
Service-Context-Id	Supported	-
CC-Request-Type	Supported	-
CC-Request-Number	Supported	-
Destination-Host	Not supported	-
User-Name	Not supported	Subscription-Id-Data AVP is used instead.
CC-Sub-Session-Id	Not supported	-
Acct-Multi-Session-Id	Not supported	-
Origin-State-Id	Not supported	-
Event-Timestamp	Supported	-
Subscription-Id	Supported	-
– Subscription-Id-Data	Supported	-
– Subscription-Id-Type	Supported	-
Requested-Action	Supported	3 - PRICE_ENQUIRY
Multiple-Services-Indicator	Supported	Always expected to be True
Service-Information	Supported	-
– PS-Information	Supported	-
– – Called-Station-Id	Supported	-
– – SGSN-Address	Supported	-
– – GGSN-Address	Supported	-
– – MS-TimeZone-3GPP	Supported	-
– – Diagnostics	Supported	-
Service-Parameter-Info	Not supported	-
CC-Correlation-Id	Not supported	-
User-Equipment-Info	Not supported	-
Proxy-Info	Not supported	-
Multiple-Services-Credit-Control	Supported	See Table 2-17

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

Diameter AVP	Status	Notes
Multiple-Services-Credit-Control	Supported	-
– Service-Identifier	Supported	-
– Rating-Group	Supported	-
– Requested-Service-Unit	Supported	-
– – CC-Time	Supported	-
– – CC-Input-Octets	Supported	-
– – CC-Output-Octets	Supported	-
– – CC-Total-Octets	Supported	-

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

Diameter AVP	Status	Notes
Session-Id	Supported	-
Result-Code	Supported	-
Multiple-Services-Credit-Control	Supported	See Table 2-19
Cost-Information	Supported	-
– Unit-Value	Supported	-
– – Value-Digits	Supported	-
– – Exponent	Supported	-
– Currency-Code	Supported	-
CC-Session-Failover	Supported	-
Credit-Control-Failure-Handling	Supported	-

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 AVP	Status	Notes
– Service-Identifier	Supported	-
– Rating-Group	Supported	-
– Requested-Service-Unit	Supported	-
– – CC-Time	Supported	-
– – CC-Input-Octets	Supported	-
– – CC-Output-Octets	Supported	-
– – CC-Total-Octets	Supported	-
– ORA-Customer-Cost-Information	Supported	-
– – ORA-Subscriber-Id	Supported	-
– – ORA-Cost-Information	Supported	-
– – – Unit-Value	Supported	-
– – – – Value-Digits	Supported	-
– – – – Exponent	Supported	-
– – – ORA-Balance-Element-Id	Supported	-

Diameter Session Reauthorization Commands

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

Table 2-20: Diameter Session Reauthorization Commands

Diameter Command	Status	Notes
Re-Auth-Request (RAR)	Supported	-
Re-Auth-Answer (RAA)	Supported	-

Re-Auth-Request AVPs

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

Table 2-21: Re-Auth-Request AVPs

Diameter AVP	Status	Notes
Session-Id	Supported	-
Origin-Host	Supported	-
Origin-Realm	Supported	-
Destination-Host	Supported	-
Destination-Realm	Supported	-
Origin-State-Id	Supported	-
Service-Identifier	Supported	-
Rating-Group	Supported	-

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 AVP	Status	Notes
Session-Id	Supported	-
Origin-Host	Supported	-
Origin-Realm	Supported	-
Result-Code	Supported	-

Diameter Session Termination Commands

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

Table 2-23: Diameter Session Termination Commands

Diameter Command	Status	Notes
Session-Termination-Request	Supported	-
Session-Termination-Answer	Supported	-

Session-Termination-Request AVPs

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

Table 2-24: Session-Termination-Request AVPs

Diameter AVP	Status	Notes
Session-Id	Supported	-

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 AVP	Status	Notes
Session-Id	Supported	-
Result-Code	Supported	-
Failed-AVP	Supported	-

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

Attribute	Description
0	This attribute must not be present in packet.
0+	Zero or more instances of this attribute may be present in packet.
0-1	Zero or one instance of this attribute may be present in packet.
1	Exactly one instance of this attribute must be present in packet.

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

Reserved Keywords	Used in AVP	Comments
ingr-v4	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
ingr-v6	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
egr-v4	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
egr-v6	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
in-othr-v4	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
in-othr-v6	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
sub-id	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
sla-profile	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
sub-profile	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
inter-dest	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
cat-map	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
aa-functions	adc-rule-name, charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.
aa-functions:app	charging-rule-name	Used to identify the AA app-profile directly in the charging-rule-name AVP in a charging-rule-install. See Table 1-4 and Table 1-5.
aa-functions:aso	charging-rule-name	Used to identify the AA ASO characteristic and value directly in a charging-rule-name AVP in a charging rule-install. Table 1-4 and Table 1-5.
aa-functions:urlparam	charging-rule-name	Used to identify the AA Sub HTTP URL parameter directly in a charging-rule-name AVP in a charging rule-install. See Table 1-4 and Table 1-5.
aa-functions:subscope	charging-rule-name	Used to identify the AA Sub scope directly in a charging-rule-name AVP in a charging rule-install. See Table 1-4 and Table 1-5.
aa-um	charging-rule-name	Used to identify referenced object type within 7x50. See Table 1-3.

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

AVP ID	AVP Name	Section Defined	Application	Description
5	NAS-Port	RFC 2865 / §5.5		See the 7750 SR and VSR RADIUS Attributes Reference Guide.
8	Framed-IP-Address	RFC 4005 / §6.11.1		This AVP specifies the IPv4 address of the subscriber host. The IPv4 address is obtained before Gx session establishment. The IPv4 address cannot be assigned to the subscriber host by PCRF via Gx but is instead used only for reporting.
18	3GPP-SGNS-MCC-MNC	29.061		For GTP S11 Access contains the value configured under configure>subscriber-mgmt>gtp>serving-network.
22	3GPP-User-Location-Info	29.061		In CCR-I, this contains the User Location Information as signaled in the incoming GTP-C message for GTP Access hosts.
				For a CCR-U triggered by either USER_LOCATION_CHANGE (ULC), ECGI_CHANGE, or TAI_CHANGE will include ULI values as follows:
				- If the trigger was ULC and the ULI contains anything other than ECGI or TAI, the ULI is signaled as received in GTP.
				- If the trigger was ULC and either TAI or ECGI changed from its last known value, both TAI and ECGI will be included.
				- If the trigger was ECGI_CHANGE and ECGI changed from its last known value, ECGI is included.
				- If the trigger was TAI_CHANGE and TAI change from its last known value, TAI is included.
25	Class	RFC 2865 / §5.25		This attribute is available to be sent by the PCRF to the 7750 SR and is echoed unmodified by the 7750 SR to the PCRF. The 7750 SR does not interpret this attribute locally.
30	Called-Station-Id	RFC 2865 / §5.30	RFC 4005 / §4.5	See the 7750 SR and VSR RADIUS Attributes Reference Guide.
31	Calling-Station-ID	RFC 4005 / §4.6		See the 7750 SR and VSR RADIUS Attributes Reference Guide.
55	Event-Timestamp	RFC 6733 / §8.21		This AVP records the time that this event occurred on the 7750 SR, in seconds since January 1, 1900 00:00 UTC.
61	NAS-Port-Type	RFC 2865 / §5.41	RFC 4005 / §4.4	RFC 4603
				See the 7750 SR and VSR RADIUS Attributes Reference Guide.
87	NAS-Port-Id	RFC 2869 / §5.17	RFC 4005 / §4.3	See the 7750 SR and VSR RADIUS Attributes Reference Guide.
92	NAS-Filter-Rule	RFC 4849	Gx-PM-ESM	See the 7750 SR and VSR RADIUS Attributes Reference Guide.
				This AVP is nested within the Charging-Rule-Definition AVP.
97	Framed-IPv6-Prefix	RFC 4005 / §6.11.6		This AVP specifies the IPv6-prefix and prefix-length that is assigned to the host via SLAAC (Router Advertisement) to the WAN side of the user.
				The IPv6-prefix and prefix-length is obtained before Gx session establishment.
				The facilities to provide the IPv6-prefix and prefix-length to the subscriber-host are DHCP server/local pools, RADIUS or LUDB.
				The IPv6-prefix/prefix-length cannot be assigned to the subscriber host by PCRF via Gx. Instead the IPv6-prefix and prefix-length is the one being reported to the PCRF during the host instantiation phase.
123	Delegated-IPv6-Prefix	RFC 4818		This attribute carries the Prefix (ipv6-prefix/prefix-length) assigned to the host via DHCPv6 (IA-PD) for the LAN side of the user (IPoE, PPPoE).
				The IPv6-prefix/prefix-length is obtained before Gx session establishment.
				The facilities to provide the IPv6-prefix/prefix-length to the subscriber-host are DHCP server/local pools, RADIUS or LUDB.
				The IPv6-prefix/prefix-length cannot be assigned to the subscriber host by PCRF via Gx. Instead the IPv6-prefix and prefix-length is the one being reported to the PCRF during the host instantiation phase.
257	Host-IP-Address	RFC 6733 / §5.3.5		This AVP is used to inform a Diameter peer of the sender’s IP address.
				The IPv4 address used is the one configured in the diameter-peer-policy. If none is configured, then system-ip address is used.
258	Auth-Application-Id	RFC 6733 / §6.8		This AVP indicates supported Diameter applications.
				The application support is exchanged in CER/CEA when the peering sessions is established.
				The diameter base protocol does not require application ID because its support is mandatory.
				The Gx application ID value is 16777238 and it is advertised in Auth-Application-Id AVP within the grouped Vendor-Specific-Application-Id AVP in CER message.
				In addition, each Gx specific message carries Auth-Application-Id AVP with the value of 16777238.
260	Vendor-Specific-Application-Id	RFC 6733 / §6.11		This is a Grouped AVP that is used to advertise support of a vendor-specific Diameter application in CER/CEA messages. Gx is one such application. This AVP contains the Vendor-Id AVP of the application and the auth-application-id AVP.
263	Session-id	RFC 6733 / §8.8		This AVP must be present in all messages and it is used to identify a specific IP-Can session. IP-Can session corresponds to a subscriber host, which can be DHCPv4/v6, PPPoX or ARP host. Session-id AVP is unique per host.
				Dual stack host (IPoE or PPPoX) share a single session-id.
264	Origin-Host	RFC 6733 / §6.3		This AVP must be present in all messages and it is used to identify the endpoint (Diameter peer) that originated the message.
265	Supported-Vendor-Id	RFC 6733 / §5.3.6		This AVP is used in CER/CEA messages to inform the peer that the sender supports a subset of the vendor-specific AVPs defined by the vendor identified in this AVP.
266	Vendor-Id	RFC 6733 / §5.3.3		The value of this AVP is the IANA assigned code to a specific vendor.
				This AVP may be part of the Vendor-Specific-Application-Id AVP, Failed-AVP AVP, Experimental-Result AVP to identify the vendor associated with the relevant message/AVP.
				In case of a standalone Vendor-Id AVP (outside of any grouped AVP) that is conveyed in CER/CEA messages, it is envisioned that this AVP along with the Product-Name AVP and the Firmware-Revision AVP may provide useful debugging information.
267	Firmware-Revision	RFC 6733 / §5.3.4		The SR OS version is reported.
268	Result-Code	RFC 6733 / §7.1		This AVP indicates whether a particular request was completed successfully or an error occurred.
				All answer messages in Diameter/Gx must include one Result-Code AVP or Experimental-Result AVP.
269	Product-Name	RFC 6733 / §5.3.7		This AVP specifies the vendor-assigned name.
278	Origin-State-Id	RFC 6733 / §8.16		This AVP is used to inform the PCRF of the loss of the state on the 7750 SR side. Its value monotonically increases each time the PCRF is rebooted with the loss of the previous state.
				Because Gx sessions are not persistent in the 7750 SR, Origin-State-Id increases each time the 7750 SR is rebooted.
279	Failed-AVP	RFC 6733 / §7.5		This is a Grouped AVP that provides debugging information in cases where a request is rejected or not fully processed because of the erroneous information in specific AVP. The value of the Result-Code AVP will provide information about the reason for the Failed-AVP AVP. The Failed-AVP AVP contains the entire AVP that could not be processed successfully.
281	Error-Message	RFC 6733 / §7.3		This AVP provides more information of the failure that is indicated in the Result-Code AVP.
282	Route Record	RFC 6733 / §6.7.1		This AVP identifies the peer from which the request is received and is used for routing loop detection. An SR node inserts the origin-host of the peer in the Route-Record AVP of all transit request messages.
283	Destination-Realm	RFC 6733 / §6.6		This AVP represents the realm to which this message is to be routed.
285	Re-Auth-Request-Type	RFC 6733 / §8.12		This AVP is mandatory in RAR requests. The content of this AVP is ignored by the 7750 SR.
293	Destination-Host	RFC 6733 / §6.5		This AVP represents the host to which this message is to be sent.
				The value of this AVP can be explicitly configured.
				In case that it is omitted, the DRA (Diameter relay-agent) that receives the message selects the destination host to which the message is sent.
295	Termination-Cause	RFC 6733 / §8.15		This AVP is used to indicate the reason why a session was terminated on the 7750 SR.
296	Origin-Realm	RFC 6733 / §6.4		This AVP contains the realm of the originator of message. In the 7750 SR, the Origin-Realm is explicitly configured per Diameter peer.
297	Experimental-Result	RFC 6733 / §7.6		This is a Grouped AVP that indicates whether a particular vendor-specific request completed successfully or whether an error occurred. It contains a vendor-assigned value representing the result of processing a request.
				The result-code AVP values defined in Diameter Base RFC (6733, §7.1) are also applicable to Experimental-Result AVP.
				For a list of Gx-specific Experimental-Result-Code values supported in the 7750 SR, see Table 10. For Gx application, the Vendor-Id AVP is set to 10415 (3GPP).
				All answer messages defined in vendor-specific application must include either one Result-Code AVP or one Experimental-Result AVP.
298	Experimental-Result-Code	RFC 6733 / §7.7	29.214 / §5.5	This AVP specifies vendor-assigned (3GPP — Gx) values representing the result of processing the request.
				For a list of the 7750 SR supported values for Gx see Table 1-10.
302	Logical-Access-Id	ETSI TS 283 034 / §7.3.3	BBF TR-134 (§7.1.4.1)	This AVP contains information describing the subscriber agent circuit identifier corresponding to the logical access loop port of the Access Node from which the subscriber’s requests are initiated, namely: circuit-id from DHCPv4 Option (82,1) circuit-id from PPPoE tag (0x105, 0x00000de9 [dsl forum], 0x01 — DSL Forum TR-101) interface-id from DHCPv6 option 18. The Vendor-Id in CER is set to ETSI (13019).
313	Physical-Access-Id	ETSI TS283 034 / §7.3.14	BBF TR-134 (§7.1.4.1)	This AVP contains information about the identity of the physical access to which the user device is connected, namely: remote-id from DHCPv4 Option (82,2) remote-id from PPPoE tag (0x105, 0x00000de9 [dsl forum], 0x02 — DSL Forum TR-101) remote-id from DHCPv6 option 37. The Vendor-Id in CER is set to ETSI (13019).
412	CC-Input-Octets	RFC 4006 / §8.24	Gx-UM-ESM Gx-UM-AA	This AVP contains the number of requested, granted or used octets from the user.
414	CC-Output-Octets	RFC 4006 / §8.25	Gx-UM-ESM Gx-UM-AA	This AVP contains the number of requested, granted or used octets toward the user.
415	CC-Request-Number	RFC 4006 / §8.2		This AVP identifies each request within one session. Each request within a session has a unique CC-Request-Number that is used for matching requests with answers.
416	CC-Request-Type	RFC 4006 / §8.3		This AVP identifies the request type: INITIAL_REQUEST (CCR-I) UPDATE_REQUEST (CCR-U) TERMINATION_REQUEST (CCR-T)
418	CC-Session-Failover	RFC 4006 / §8.4		This AVP controls whether the secondary peer will be used in case that the primary peer is unresponsive (peer failover behavior). The unresponsiveness is determined by the timeout of the previously sent message. If this AVP is not supplied via PCRF, the locally configured options in the 7750 SR will determine the peer failover behavior. For further details on the peer failover behavior, see “Gx Fallback Function” section in the Gx Configuration Guide.
421	CC-Total-Octets	RFC 4006 / §8.23	Gx-UM-ESM Gx-UM-AA	This AVP contains the number of requested, granted or used octets regardless of the direction (sent or received).
427	Credit-Control-Failure-Handling	RFC 4006 / §8.14		This AVP controls whether the subscriber is terminated or instantiated with default parameters in case that the PCRF is unresponsive. The unresponsiveness is determined by the timeout of the previously sent message. If this AVP is not supplied via PCRF, the locally configured options in the 7750 SR determines the behavior. For further details, see the “Gx Fallback Function” section in the Gx Configuration Guide.
431	Granted-Service-Unit	RFC 4006 / §8.17	Gx-UM-ESM Gx-UM-AA	This grouped AVP is sent by PCRF to the 7750 SR for usage monitoring purposes. When the granted amount of units is consumed by the user, a report is sent from the 7750 SR to the PCRF. The amount of consumed units can be measured on three different levels: Session level (host level) PCC rule level (credit category in the 7750 SR) ADC rule level (AA level in the 7750 SR)
433	Redirect-Address-Type	RFC 4006 / §8.38	Gx-PM-ESM	This AVP specifies the address type of the HTTP redirect server. URL (2) type is the only address type supported in the 7750 SR.
435	Redirect-Server-Address	RFC 4006 / §8.39	Gx-PM-ESM	This AVP specifies the URL string of the redirect server.
443	Subscription-Id	RFC 4006 / §8.46		This AVP is of type Grouped and is used to identify the subscriber host in the 7750 SR. The nested AVPs are subscription-id-data and subscription-id-type.
444	Subscription-Id-Data	RFC 4006 / §8.48		This AVP is part of the subscription-id AVP and is used to identify the host by: Circuit-id Dual-stack-remote-id Imei Imsi Mac of the host Msisdn Subscriber-id Username (ppp-username or a string returned in the Username attribute via RADIUS or NASREQ) Subscription type (subscription-id-type AVP) has to be explicitly set via CLI. The data will be formatted according to the type set. For GTP S11 access, the value under configure>subscriber-mgmt>diameter-application-policyapplication-policy-name>gxavp-subscription-id is ignored and the session always includes two subscription-Id AVPs for both IMSI and MSISDN.
446	Used-Service-Unit	RFC 4006 / §8.19	Gx-UM-ESM Gx-UM-AA	This AVP is of type Grouped and it represents the measured volume threshold for usage monitoring control purposes. It is sent in the Usage-Monitoring-Report AVP from the 7750 SR to the PCRF when the granted unit threshold is reached or in response to a usage-report request from the PCRF.
450	Subscription-Id-Type	RFC 4006 / §8.47		This AVP is used to determine which type of identifier is carried by the subscription-id AVP. The following formats (types) are supported in the 7750 SR: E.164 format (ITU-T E.164) IMSI format (ITU-T E.212) NAI format (RFC 2486) Private format
458	User-Equipment-Info	RFC 4006 / §8.49		This is a Grouped AVP that carries information about the identity and the capabilities of the host.
459	User-Equipment-Info-Type	RFC 4006 / §8.50		This AVP is nested within the User-Equipment-Info AVP. The following types are supported in the 7750 SR: IMEISV – contains the IMEI and software version according to 3GPP TS 23.003 document. MAC address Eui64 based on 48-bit MAC address with 0xfffe inserted in the middle. Modified_eui64 — similar to eui64 but with inverted ‛u’ bit as defined in: http://standards.ieee.org/develop/regauth/tut/eui64.pdf and RFC 4291. The equipment type must be explicitly set through the CLI. For GTP S11 access, the configuration is ignored and always uses IMEISV.
460	User-Equipment-Info-Value	RFC 4006 / §8.51		This AVP carries the value that is defined by the User-Equipment-Info-Type AVP.
507	Flow-Description	29.214 / §5.3.8	Gx-PM-ESM	This AVP is nested within Flow-Information AVP. It identifies traffic within the PCC rule based on the 5 tuple.
511	Flow-Status	29.214 / §5.3.11	Gx-PM-ESM	This AVP is used to set the service gating action for the service represented by the PCC rule. It is nested inside of Charging-Rule-Definition AVP. Supported values are: ENABLED (2) DISABLED (3) The service identified by PCC rule is by default enabled (Flow-Status = ENABLED). If explicitly configured within the PCC rule, it must be accompanied with one or more additional actions. Otherwise, the entire PCC rule instantiation fails. Flow-Status = DISABLED can be the sole action within the PCC rule. Traffic associated with this action, is dropped.
515	Max-Requested-Bandwidth-DL	29.214 / §5.3.14	Gx-PM-ESM	Depending on the context in which it is configured (nested), this AVP represents the egress PIR of a queue or a policer.
516	Max-Requested-Bandwidth-UL	29.214 / §5.3.15	Gx-PM-ESM	Depending on the context in which it is configured (nested), this AVP represents the ingress PIR of a queue or a policer.
554	Extended-Max-Requested-BW-DL	29.214 / §5.3.52	Gx-PM-ESM	For higher rate requirements, this AVP can be used in place of the Max-Requested-Bandwidth-DL AVP.
555	Extended-Max-Requested-BW-UL	29.214 / §5.3.52	Gx-PM-ESM	For higher rate requirements, this AVP can be used in place of the Max-Requested-Bandwidth-UL AVP.
628	Supported-Features	29.229 / §6.3.29	29.212 / §5.4.1	This is a Grouped AVP that is used during Gx session establishment to inform the destination host about the required and optional features that the origin-host supports. One instance of Supported-Features AVP is needed per Feature-List-id.
629	Feature-List-Id	29.229 / §6.3.30		This AVP contains the identity of a feature list. This AVP allows differentiation between multiple feature lists in case that an application has multiple feature lists defined.
630	Feature-List	29.229 / §6.3.31		This AVP contains a bitmask indicating the supported feature in Gx. The Gx features in the Feature-List AVP are defined in 3GPP TS 29.212, §5.4.1.
909	RAI	29.061		For GTP S11 access, this contains the RAI if it was signaled in GTP.
1001	Charging-Rule-Install	29.212 / §5.3.2		This AVP is of type Grouped and is used to enforce overrides, install NAS filter inserts and install or modify PCC rules in the node as instructed by PCRF.
1002	Charging-Rule-Remove	29.212 / §5.3.3		This AVP is of type Grouped and is used to remove PCC rules from an IP CAN session.
1003	Charging-Rule-Definition	29.212 / §5.3.4		This AVP is of type Grouped and is used for rule overrides, NAS filter inserts or PCC rules installation. It contains nested AVPs that define the overrides (rate changes of a subscriber, a queue or a policer, and so on), NAS filter insert or a completely new PCC rule definition.
1005	Charging-Rule-Name	29.212 / §5.3.6		This AVP is used to reference a predefined rule in the node, name the PCC rule which is defined through Charging-Rule-Definition AVP, and report rule/override status in case of a rule/override activation failure.
1006	Event-Trigger	29.212 / §5.3.7		This AVP can be sent from the PCRF to subscribe to a particular event in the 7750 SR.
1010	Precedence	29.212 / §5.3.11	Gx-PM-ESM	This AVP is carried within a PCC rule definition (Charging-Rule-Definition) and it determines the order in which PCC rules are installed for the subscriber-host.
1014	ToS-Traffic-Class	29.214 / §5.3.15	Gx-PM-ESM	This AVP is nested within Flow-Information AVP. It identifies traffic within the PCC rule based on DSCP bits.
1016	QoS-Information	29.212 / §5.3.16	Gx-PM-ESM	This AVP has a multi-faceted function: As part of PCC rule definition in CCA or RAR, this AVP is used to rate-limit a flow. The AVP defines QoS overrides that can be submitted from PCRF to the SR OS router in a CCA or RAR message. The AVP defines APN Uplink and Downlink Aggregate Maximum Bitrate (AMBR) in a CCA or RAR message.
1018	Charging-Rule-Report	29.212 / §5.3.18		This AVP is of type Grouped and is used to report the status of PCC rules in the 7750 SR.
1019	PCC-Rule-Status	29.212 / §5.3.19		This AVP describes the status of the rules as active or inactive and is nested within the Charging-Rule-Report AVP.
1025	Guaranteed-Bitrate-DL	29.212 / §5.3.25	Gx-PM-ESM	Depending on the context in which it is configured (nested), this AVP represents the egress CIR of a queue or a policer.
1026	Guaranteed-Bitrate-UL	29.212 / §5.3.26	Gx-PM-ESM	Depending on the context in which it is configured (nested), this AVP represents the ingress CIR of a queue or a policer.
1027	IP-CAN-Type	29.212 / §5.3.27		This AVP indicates the type of Connectivity Access Network in which the user is connected.
1028	QoS-Class-Identifier	29.212 / §5.3.17		This AVP identifies a QoS forwarding class within the router.
1031	Rule-Failure-Code	29.212 / §5.3.38		This AVP is sent from the router to the PCRF within a Charging-Rule-Report or ADC-Rule-Report AVP to identify the reason a rule is being reported.
1032	RAT-Type	29.212 / §5.3.31		This AVP identifies the radio access technology used for this connection.
1040	APN-Aggregate-Max-Bitrate-DL	29.212		When received in an RAR or CCA, this value can be mapped to a local egress QoS override.
1045	Session-Release-Cause	29.212 / §5.3.33	Gx-PM-ESM	Gx-PM-AA
1050	AN-GW-Address	29.212 / §5.3.49		This AVP is the system IPv4 address of the 7750 SR.
1058	Flow-Information	29.212 / §5.3.53	Gm-PM-ESM	This is a Grouped AVP carrying information about traffic identification with the PCC rule. This AVP is nested within Charging-Rule-Definition AVP.
1065	PDN-Connection-ID	29.212		For GTP S11, the access value contains the APN as received in GTP.
1066	Monitoring-Key	29.212 / §5.3.59	Gx-UM-ESM	Gx-UM-AA
1067	Usage-Monitoring-Information	29.212 / §5.3.60	Gx-UM-ESM	Gx-UM-AA
1068	Usage-Monitoring-Level	29.212 / §5.3.61	Gx-UM-ESM	Gx-UM-AA
1069	Usage-Monitoring-Report	29.212 / §5.3.62	Gx-UM-ESM	Gx-UM-AA
1070	Usage-Monitoring-Support	29.212 / §5.3.63	Gx-UM-ESM	Gx-UM-AA
1080	Flow-Direction	29.212 / §5.3.65	Gx-PM-ESM	This AVP is nested within the Flow-Information AVP. It identifies the direction in which the PCC rule is applied (ingress or egress).
1085	Redirect-Information	29.212 / §5.3.82	Gx-PM-ESM	This is a Grouped AVP that contains HTTP redirect information.
1086	Redirect-Support	29.212 / §5.3.83	Gx-PM-ESM	This AVP is nested inside of Redirect-Information AVP.
1088	TDF-Application-Identifier	29.212 / §5.3.77	Gx-UM-AA	This AVP is of type OctetString.
1092	ADC-Rule-Install	29.212 / §5.3.85	Gx-PM-AA	Gx-UM-AA
1093	ADC-Rule-Remove	29.212 / §5.3.86	Gx-PM-AA	Gx-UM-AA
1094	ADC-Rule-Definition	29.212 / §5.3.87	Gx-PM-AA	Gx-UM-AA
1096	ADC-Rule-Name	29.212 / §5.3.89	Gx-PM-AA	Gx-UM-AA
1097	ADC-Rule-Report	29.212 / §5.3.90	Gx-PM-AA	Gx-UM-AA
2848	Extended-APN-AMBR-DL	29.212 / §5.3.134		For higher rate requirements, this AVP can be used in place of the APN-Aggregate-Max-Bitrate-DL AVP.
2849	Extended-APN-AMBR-UL	29.212 / §5.3.135		For higher rate requirements, this AVP can be used in place of the APN-Aggregate-Max-Bitrate-UL AVP.
2850	Extended-GBR-DL	29.212 / §5.3.136	Gx-PM-ESM	For higher rate requirements, this AVP can be used in place of the Guaranteed-Bitrate-DL AVP.
2851	Extended-GBR-UL	29.212 / §5.3.137	Gx-PM-ESM	For higher rate requirements, this AVP can be used in place of the Guaranteed-Bitrate-UL AVP.

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)

AVP ID	AVP Name	Incl/ Excl	Type	Flags	Limits	Format
5	NAS-Port	Yes	Unsigned32	M	4 octets	See the 7750 SR and VSR RADIUS Attributes Reference Guide.
8	Framed-IP-Address	No	OctetString	M	4 octets	Example: ip-address 10.11.12.13 Framed-IP-Address = 0a0b0c0d As defined in RFC 4005, §6.11.1.
22	3GPP-User-Location-Info	Yes	OctetString	V	—	Vendor-Id = 10415 (3GPP) See 3GPP TS 29.061 for encoding details.
30	Called-Station-Id	Yes	UTF8String	M	64 chars	Example: Called-Station-Id = mac:ssid or mac only if ssid is not available.
31	Calling-Station-ID	Yes	UTF8String	M	64 chars	Example: llid
55	Event-Time stamp	No	Time	M	4 octets	See the 7750 SR and VSR RADIUS Attributes Reference Guide.
61	NAS-Port-Type	Yes	Enumerated	M	4 octets	The values for this attribute are defined in the RFC 2865, 4005 and 4603. See the 7750 SR and VSR RADIUS Attributes Reference Guide.
87	NAS-Port-Id	Yes	UTF8String	M	253 octets	See the 7750 SR and VSR RADIUS Attributes Reference Guide.
92	NAS-Filter-Rule	NA	UTF8String	NA	Max 10 attributes per message or max 10 filter entries per message.	See the 7750 SR and VSR RADIUS Attributes Reference Guide.
97	Framed-IPv6-Prefix	No	OctetString	M	—	SLAAC wan-host <ipv6-prefix/prefix-length> with prefix-length 64 The AVP layout is: <1 octet Reserved> <1 octet Length> <max 16 octets for Prefix>
123	Delegated-IPv6-Prefix	No	OctetString	M	—	<ipv6-prefix/prefix-length> with prefix-length [48 to 64] The AVP layout is: <1 octet Reserved> <1 octet Length> <max 16 octets for Prefix>
257	Host-IP-Address	No	Address	M	—	IPv4 Address
258	Auth-Application-Id	No	Unsigned32	M	—	Example: Gx Auth-Application-Id = 16777238
260	Vendor-Specific-Application-Id	No	Grouped	M	—	This AVP contains the Vendor-Id AVP and Auth-Application-Id AVP. For Gx, the Vendor-Id = 10415 (3GPP) and the Auth-Application-Id = 16777238.
263	Session-id	No	UTF8String	M	102 bytes	The session-id must be globally and eternally unique. The format of the session-id is the following: ;<high 32 bits>;<low 32 bits> In the 7750 SR the session-id is defined as: diameter-identity;boxuptime; seq-number Example: router.workstation.be;1391362206;1
264	Origin-Host	No	DiameterIdentity	M	80 bytes	Example: Origin-Host = host-name-1@domain-name-1
265	Supported-Vendor-Id	No	Unsigned32	M	—	IANA assigned vendor number: 3GPP — 10415 ETSI — 13019 Tridens — 6527
266	Vendor-Id	No	Unsigned32	M	—	IANA assigned vendor number: 3GPP — 10415 ETSI — 13019 Tridens — 6527 BBF — 3561
267	Firmware-Revision	No	Unsigned32	—	—	Reference to the major/minor release version. Example: 805 — Release 8R5
268	Result-Code	No	Unsigned32	M	—	See Table 10 for Error Codes.
269	Product-Name	No	UTF8String	—	—	Vendor-assigned name for the product. Example: ‟SR OS”
278	Origin-State-Id	No	Unsigned32	M	—	Example: Origin-State-Id = 10
279	Failed-AVP	No	Grouped	M	—	This AVP contains the AVP that could not be processed successfully.
281	Error-Message	No	UTF8String	—	—	String describing the cause of the failure.
282	Route-Record	No	DiameterIdentity	M	80 bytes	Example: Route-Record: host-1
283	Destination-Realm	No	DiameterIdentity	M	80 bytes	Example: Destination-Realm = domain.com
285	Re-Auth-Request-Type	No	Enumerated	NA	—	This AVP is always received in RAR message and it is never sent by the 7750 SR.
293	Destination-Host	No	DiameterIdentity	M	80 bytes	Operator configurable.
295	Termination-Cause	No	Enumerated	M	—	For a list of the 7750 SR supported values for Gx see Table 1-13.
296	Origin-Realm	No	DiameterIdentity	M	80 bytes	Example: Origin-Realm = origin-domain.com
297	Experimental-Result	No	Grouped	M	—	A grouped AVP containing: Vendor-Id AVP Experimental-Result-Code AVP Example: Experimental-Result = {Vendor-Id = 10415 (3GPP) Experimental-Result-Code = DIAMETER_PCC_RULE_EVENT (5142)}
298	Experimental-Result-Code	No	Unsigned32	M	—	For a list of the 7750 SR supported values for Gx see Table 1-10.
302	Logical-Access-Id	Yes	OctetString	V	—	Vendor ID = 13019 (ETSI)
313	Physical-Access-Id	Yes	UTF8String	V	—	Vendor ID = 13019 (ETSI)
412	CC-Input-Octets	No	Unsigned64	M	—	Example: CC-Input-Octets = 1000000
414	CC-Output-Octets	No	Unsigned64	M	—	Example: CC-Output-Octets = 1000000
415	CC-Request-Number	No	Unsigned32	M	—	Monotonically increasing from 0 for all requests within one session.
416	CC-Request-Type	No	Enumerated	M	—	Example: CC-Request-Type = 1 (CCR-i) 3. CC-Request-Type = 2 (CCR-u) CC-Request-Type = 3 (CCR-t)
418	CC-Session-Failover	No	Enumerated	M	—	FAILOVER_NOT_SUPPORTED (0) FAILOVER_SUPPORTED (1) Example: CC-Session-Failover = 1
421	CC-Total-Octets	No	Unsigned64	M	—	Example: CC-Total-Octets = 2000000
427	Credit-Control-Failure-Handling	No	Enumerated	M	—	TERMINATE (0) CONTINUE (1) RETRY_AND_TERMINATE (2) Example: Credit-Control-Failure-Handling = 1
431	Granted-Service-Unit	No	Grouped	M	—	This AVP can contain the following AVPs: CC-Total-Octets CC-Input-Octets CC-Output-Octets
433	Redirect-Address-Type	No	Enumerated	M	—	Example: Redirect-Address-Type = 2 (URL type)
435	Redirect-Server-Address	No	UTF8String	M	255 chars	Example: Redirect-Server-Address = http://www.operator.com/portal.php&
443	Subscription-Id	Yes	Grouped	M	—	This AVP contains the following AVPs: Subscription-Id-Type Subscription-Id-Data
444	Subscription-Id-Data	Yes	UTF8String	M	—	Example: Username — Subscription-Id-Data = user1@domain.com







446	Used-Service-Unit	No	Grouped	M	—	This AVP contains the following AVPs: CC-Total-Octets CC-Input-Octets CC-Output-Octets
450	Subscription-Id-Type	Yes	Enumerated	M	—	Example: Subscription-Id-Type = 0 (end_user_e164) Subscription-Id-Type = 1 (end_user_imsi)

458	User-Equipment-Info	Yes	Grouped	M	—	This AVP contains the following AVPs: User-Equipment-Info-Type User-Equipment-Info-Value
459	User-Equipment-Info-Type	Yes	Enumerated	—	—	Example: User-Equipment-Info-Type = 0 (emissive) User-Equipment-Info-Type =1 (mac)

460	User-Equipment-Info-Value	Yes	OctetString	—	—	—
507	Flow-Description	No	IPFilterRule (RFC6733, §4.3.1)	NA,M	—	The IPFilterRule format within PCC rule in the 7750 SR has the following syntax: action dir proto from src to dst Example: Flow-Description = allow in 6 from 192.168.7.0/24 3000-40000 to 172.16.10.0/26 10000-20000
511	Flow-Status	No	Enumerated	NA,M	—	Example: Flow-Status = 3 — matched traffic inside of the PCC rule is dropped.
515	Max-Requested-Bandwidth-DL	No	Unsigned32	NA, V	—	Vendor-Id = 10415 (3GPP) Example: Max-Requested-Bandwidth-DL = 1000 — 1 Mb/s in overrides
516	Max-Requested-Bandwidth-UL	No	Unsigned32	NA, V	—	Vendor-Id = 10415 (3GPP) Example: Max-Requested-Bandwidth-UL = 1000 — 1 Mb/s for overrides
554	Extended-Max-Requested-BW-DL	NA	Unsigned32	NA, V	—	Vendor-Id = 10415 (3GPP) Example: Extended-Max-Requested-BW-DL = 1000 — 1 Mb/s
555	Extended-Max-Requested-BW-UL	NA	Unsigned32	NA, V	—	Vendor-Id = 10415 (3GPP) Example: Extended-Max-Requested-BW-UL = 1000 — 1 Mb/s
628	Supported-Features	No	Grouped	V	—	This AVP contains the following AVPs: Vendor-Id Feature-List-Id Feature-List
629	Feature-List-Id	No	Unsigned32	V	—	Vendor-Id = 10415 (3GPP) Example: Feature-List-Id = 2
630	Feature-List	No	Unsigned32	V	—	Vendor-Id = 10415 (3GPP) Example: Feature-List = 128
909	RAI	Yes	Octetstring	V	12 octets	Vendor-Id = 10415 (3GPP) See 3GPP TS 29.061 for encoding details.
1001	Charging-Rule-Install	No	Grouped	NA, V	—	Vendor-Id = 10415 (3GPP) This AVP contains the following AVPs: Charging-Rule-Definition Charging-Rule-Name
1002	Charging-Rule-Remove	No	Grouped	NA, V	—	Vendor-Id = 10415 (3GPP) This AVP contains the following AVP: Charging-Rule-Name
1003	Charging-Rule-Definition	No	Grouped	NA, V	—	Vendor-Id = 10415 (3GPP) This AVP contains the following nested AVPs: Charging-Rule-Name, QoS-Information, NAS-Filter-Rule, Alc-NAS-Filter-Rule-Shared, AA-Functions
1005	Charging-Rule-Name	No	OctetString	V,M	100 chars for PCC rules (defined via Charging-Rule-Definition AVP) 128 chars for overrides. Vendor-Id = 10415 (3GPP)
1006	Event-Trigger	No	Enumerated	V	—	Vendor-Id = 10415 (3GPP)
1010	Precedence	No	Unsigned32	NA, M	0 to 65535	Vendor-Id = 10415 (3GPP) Example: Precedence = 100
1014	Tos-Traffic-Class	No	OctetString	NA, M	—	Encoded as two octets. The first octet contains the IPv4 Type-of-Service or the IPv6 Traffic-Class field and the second octet contains the ToS/Traffic Class mask field. The only supported mask is 11111100 (6 bits denoting DSCP support). Example: ToS-Traffic-Class = 00101000 11111100 — DSCP AF11
1016	QoS-Information	NA	Grouped	NA, V	—	Vendor-Id 10415 (3GPP) When used to signal a flow rate limiter in a PCC rule, this AVP contains the following nested AVPs: Max-Requested-Bandwidth-UL, Max-Requested-Bandwidth-DL, Guaranteed-Bitrate-UL, Guaranteed-Bitrate-DL
1018	Charging-Rule-Report	No	Grouped	V,M	—	Vendor-Id = 10415 (3GPP) This AVP contains the following nested AVPs: Charging-Rule-Name, PCC-Rule-Status, Rule-Failure-Code
1019	PCC-Rule-Status	No	Enumerated	V,M	—	Vendor-Id = 10415 (3GPP) Supported values in the 7750 SR: 1 – inactive Example: PCC-Rule-Status = 0 — rule is active
1025	Guaranteed-Bitrate-DL	NA	Unsigned32	NA,V	—	The units of this parameter are kb/s for overrides and b/s when used within PCC rules. The rate accounts for the IP header and above (no Layer 2 header). Vendor-Id = 10415 (3GPP) Example: Guaranteed-Bandwidth-DL = 1000 — 1 Mb/s in overrides Guaranteed-Bandwidth-DL = 1000000 — 1 Mb/s in PCC rules
1026	Guaranteed-Bitrate-UL	NA	Unsigned32	V	—	The units of this parameter are kb/s for overrides and b/s when used within PCC rules. The rate accounts for the IP header and above (no Layer 2 header). Vendor-Id = 10415 (3GPP) Example: Guaranteed-Bandwidth-UL = 1000 — 1 Mb/s in overrides Guaranteed-Bandwidth-UL = 1000000 — 1 Mb/s in PCC rules
1027	IP-CAN-Type	Yes	Enumerated	V	—	Vendor-Id = 10415 (3GPP) Example: IP-CAN-Type = 2 — xDSL IP-CAN-Type = 5 — 3GPP-EPS
1028	QoS-Class-Identifier	NA	Enumerated	NA,M	—	Vendor-Id = 10415 (3GPP) Example: QoS-Class-Identifier = 3 — maps to FC EF.
1031	Rule-Failure-Code	No	Enumerated	V,M	—	Vendor-Id = 10415 (3GPP) Example: Rule-Failure-Code = 1 — UNKNOWN_RULE_NAME
1032	RAT-Type	Yes	Enumerated	V	—	Vendor-Id = 10415 (3GPP) Example: RAT-Type = 0 — WLAN RAT-Type = 1004 — EUTRAN
1040	APN-Aggregate-Max-Bitrate-DL	Yes	Unsigned32	V	2^32-1 b/s	Vendor-Id = 10415 (3GPP) Rate in bits per second (b/s) Example: APN-Aggregate-Max-Bitrate-DL = 100000000 (100 Mb/s)
1041	APN-Aggregate-Max-Bitrate-UL	Yes	Unsigned32	V	2^32-1 b/s	Vendor-Id = 10415 (3GPP) Rate in bits per second (b/s) Example: APN-Aggregate-Max-Bitrate-UL = 10000000 (10 Mb/s)
1045	Session-Release-Cause	NA	Enumerated	V,M	—	Vendor-Id = 10415 (3GPP) This AVP is only received by the 7750 SR and it is never sent by the 7750 SR. 0 — UNSPECIFIED-REASON 1 — UE_SUBSCRIPTION_REASON This value is used to indicate that the subscription of UE has changed (for example, removed) and the session needs to be terminated. 2 — INSUFFICIENT_SERVER_ RESOURCES This value is used to indicate that the server is overloaded and needs to abort the session. Example: Session-Release-Cause = 0
1050	AN-GW-Address	Yes	IPv4Address	V	—	Vendor-Id = 10415 (3GPP) Example: AN-GW-Address = 10.10.10.10
1058	Flow-Information	No	Grouped	V	—	Vendor-Id = 10415 (3GPP) The following AVPs can be nested inside: Flow-Description, ToS-Traffic-Class, Flow-Direction
1065	PDN-Connection-ID	Yes	UTF8String	V	100 chars	Vendor-Id = 10415 (3GPP) For example: PDN-Connection-ID = example-apn.mnc001.mcc001.gprs
1066	Monitoring-Key	No	OctetString	NA,V	32 bytes	Vendor-Id = 10415 (3GPP) Category name configured in the 7750 SR, a string used for session monitoring or a Monitoring-Key AVP set in PCC rule definition with the Charging-Rule-Definition AVP. Example: Monitoring-Key = monitor-pcc-rule-1
1067	Usage-Monitoring-Information	No	Grouped	V	—	Vendor-Id = 10415 (3GPP) This AVP contains the following nested AVPs: Monitoring-Key, Granted-Service-Unit, Used-Service-Unit, Usage-Monitoring-Level, Usage-Monitoring-Report, Usage-Monitoring-Support
1068	Usage-Monitoring-Level	No	Enumerated	V	—	Vendor-Id = 10415 (3GPP) The following values are defined: 0 – session_level 1 – pcc_rule_level 2 – adc_rule_level Example: Usage-Monitoring-Level = 0 — usage monitoring is performed based on sla-profile (IP-CAN session level) of the host.
1069	Usage-Monitoring-Report	No	Enumerated	V	—	Vendor-Id = 10415 (3GPP) Example: Usage-Monitoring-Report = 0 (usage_monitoring_report_required)
1070	Usage-Monitoring-Support	No	Enumerated	NA,V	—	Vendor-Id = 10415 (3GPP) Example: Usage-Monitoring-Support = 0 — usage_ monitoring_disabled
1080	Flow-Direction	No	Enumerated	NA,M	—	Vendor-Id = 10415 (3GPP) Example: Flow-Direction = 1 — egress Flow-Direction = 2 — ingress
1085	Redirect-Information	No	Grouped	NA,V	—	Vendor-Id = 10415 (3GPP) This AVP can contain the flowing AVPs: Redirect-Support, Redirect-Address-Type, Redirect-Server-Address
1086	Redirect-Support	No	Enumerated	NA,V	—	Vendor-Id = 10415 (3GPP) Example: Redirect-Support = 1 — redirection is enabled
1088	TDF-Application-Identifier	OctetString	NA,V	32 chars	Vendor-Id = 10415 (3GPP) Example: 0_rated, BitTorrent
1092	ADC-Rule-Install	No	Grouped	NA,V	—	Vendor-Id = 10415 (3GPP) This AVP contains the following nested AVPs: ADC-Rule-Definition
1093	ADC-Rule-Remove	Grouped	NA,V	—	Vendor-Id = 10415 (3GPP) This AVP contains the following nested AVPs: ADC-Rule-Name
1094	ADC-Rule-Definition	No	Grouped	NA,V	—	Vendor-Id = 10415 (3GPP) This AVP contains the following nested AVPs: ADC-Rule-Name, MonitoringKey, TDF-Application-Id, AA-Functions
1096	ADC-Rule-Name	No	OctetString	V	17 chars for prefix/separator (optional) plus 32 chars for name	Vendor-Id = 10415 (3GPP) Example: For app-profile and ASO changes: ADC-Rule-Name = ‟AA-Functions: AdcRuleWithAAFtn”
1097	ADC-Rule-Report	No	Grouped	V	—	Vendor-Id = 10415 (3GPP) This AVP contains the following nested AVPs: ADC-Rule-Name, PCC-Rule-Status, Rule-Failure-Code
2848	Extended-APN-AMBR-DL	NA	Unsigned32	NA, V	—	The units of this parameter are kb/s. Vendor-Id = 10415 (3GPP) Example: Extended-APN-AMBR-DL = 1000 — 1 Mb/s
2849	Extended-APN-AMBR-UL	NA	Unsigned32	NA, V	—	The units of this parameter are kb/s. Vendor-Id = 10415 (3GPP) Example: Extended-APN-AMBR-UL = 1000 — 1 Mb/s
2850	Extended-GBR-DL	NA	Unsigned32	NA, V	—	The units of this parameter are kb/s. Vendor-Id = 10415 (3GPP) Example: Extended-GBR-DL = 1000 — 1 Mb/s
2851	Extended-GBR-UL	NA	Unsigned32	NA, V	—	The units of this parameter are kb/s. Vendor-Id = 10415 (3GPP) Example: Extended-GBR-UL = 1000 — 1 Mb/s

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

AVP ID	AVP Name	CER	CEA	DPR	DPA	DWR	DWA	ASR	ASA
257	Host-IP-Address	1	1+	0	0	0	0	0	0
258	Auth-Application-Id	1	0+	0	0	0	0	1	0
260	Vendor-Specific-Application-Id	0+	0+	0	0	0	0	0	0
263	Session-id	0	0	0	0	0	0	1	1
264	Origin-Host	1	1	1	1	1	1	1	1
265	Supported-Vendor-Id	1+	0+	0	0	0	0	0	0
266	Vendor-Id	1	1	0	0	0	0	0	0
267	Firmware-Revision	1	0-1	0	0	0	0	0	0
268	Result-Code	0	1	0	1	0	1	0	1
269	Product-Name	1	1	0	0	0	0	0	0
273	Disconnect-Cause	0	0	1	0	0	0	0	0
278	Origin-State-Id	1	0-1	0	0	0	0-1	0-1	0-1
279	Failed-AVP	0	0-1	0	0-1	0	0-1	0	0-1
281	Error-Message	0	0	0	0	0	0	0	0
283	Destination-Realm	0	0	0	0	0	0	1	0
293	Destination-Host	0	0	0	0	0	0	1	0
294	Error-Reporting-Host	0	0	0	0	0	0	0	0-1
296	Origin-Realm	1	1	1	1	1	1	1	1

Gx AVP Applicability

Table 8: Gx AVP Applicability

AVP ID	AVP Name	CCR	CCA	RAR	RAA
5	NAS-Port	0-1	0	0	0
8	Framed-IP-Address	0-1	0	0	0-1
18	3GPP-SGNS-MCC-MNC	0-1	0	0	0-1
22	3GPP-User-Location-Info	0-1	0	0	0
30	Called-Station-Id	0-1	0	0	0
31	Calling-Station-ID	0-1	0	0	0
55	Event-Timestamp	0-1	0-1	0-1	1
61	NAS-Port-Type	0-1	0	0	0
87	NAS-Port-Id	0-1	0	0	0
92	NAS-Filter-Rule	0	0+	0+	0
97	Framed-IPv6-Prefix	0-1	0	0	0-1
123	Delegated-IPv6-Prefix	0-1	0	0	0-1
258	Auth-Application-Id	1	1	1	0
263	Session-id	1	1	1	1
264	Origin-Host	1	1	1	1
266	Vendor-Id	0	N	0	0
268	Result-Code	0	1	0	0-1
278	Origin-State-Id	1	0-1	0-1	1
279	Failed-AVP	0-1	0+	0	0-1
281	Error-Message	0-1	0-1	0	0-1
282	Route-Record	0+	0	0+	0
283	Destination-Realm	1	0	1	0
285	Re-Auth-Request-Type	0	0	1	0
293	Destination-Host	0-1	0	1	0
295	Termination-Cause	0-1	0	0	0
296	Origin-Realm	1	1	1	1
297	Experimental-Result	0	0-1	0	0-1
298	Experimental-Result-Code	0	N	0	N
302	Logical-Access-Id	0-1	0	0	0
313	Physical-Access-Id	0-1	0	0	0
412	CC-Input-Octets	N	N	N	0
414	CC-Output-Octets	N	N	N	0
415	CC-Request-Number	1	1	0	0
416	CC-Request-Type	1	1	0	0
418	CC-Session-Failover	0	0-1	0	0
421	CC-Total-Octets	N	N	N	0
427	Credit-Control-Failure-Handling	0	0-1	0	0
431	Granted-Service-Unit	0	0-1	N	0
433	Redirect-Address-Type	0	N	N	0
433	Redirect-Server-Address	0	N	N	0
443	Subscription-Id	1-2	0	0	0
444	Subscription-Id-Data	N	0	0	0
446	Used-Service-Unit	N	0	0	0
450	Subscription-Id-Type	N	0	0	0
458	User-Equipment-Info	0-1	0	0	0
459	User-Equipment-Info-Type	N	0	0	0
460	User-Equipment-Info-Value	N	0	0	0
507	Flow-Description	0	N	N	0
511	Flow-Status	0	N	N	0
515	Max-Requested-Bandwidth-DL	0	N	N	0
516	Max-Requested-Bandwidth-UL	0	N	N	0
554	Extended-Max-Requested-BW-DL	0	N	N	0
555	Extended-Max-Requested-BW-UL	0	N	N	0
628	Supported-Features	0-1	0+	0	0
629	Feature-List-Id	N	N	0	0
630	Feature-List	N	N	0	0
909	RAI	0-1	0	0	0
1001	Charging-Rule-Install	0	0+	0+	0
1002	Charging-Rule-Remove	0	0+	0+	0
1003	Charging-Rule-Definition	0	N	N	0
1005	Charging-Rule-Name	N	N	N	N
1006	Event-Trigger	0+	0+	0+	0
1010	Precedence	0	N	N	0
1014	ToS-Traffic-Class	0	N	N	0
1016	QoS-Information	0-1	0-1, N	0-1, N	0
1018	Charging-Rule-Report	0+	0	0	0+
1019	PCC-Rule-Status	N	0	0	N
1025	Guaranteed-Bitrate-DL	0	N	N	0
1026	Guaranteed-Bitrate-UL	0	N	N	0
1027	IP-CAN-Type	0-1	0	0	0-1
1028	QoS-Class-Identifier	0	N	N	0
1031	Rule-Failure-Code	N	0	0	N
1032	RAT-Type	0-1	0	0	0-1
1033	Event-Report-Indication	0	0	0-1	0
1040	APN-Aggregate-Max-Bitrate-DL	N	N	N	0
1041	APN-Aggregate-Max-Bitrate-UL	N	N	N	0
1045	Session-Release-Cause	0	0	0-1	0
1050	AN-GW-Address	0-1	0	0	0-1
1058	Flow-Information	0	0+	0+	0
1065	PDN-Connection-ID	0-1	0	0	0
1066	Monitoring-Key	N	N	N	0
1067	Usage-Monitoring-Information	0+	0+	0+	0
1068	Usage-Monitoring-Level	0	N	N	0
1069	Usage-Monitoring-Report	0	N	N	0
1070	Usage-Monitoring-Support	0	N	N	0
1080	Flow-Direction	0	N	N	0
1085	Redirect-Information	0	0-1	0-1	0
1086	Redirect-Support	0	N	N	0
1088	TDF-Application-Identifier	0	N	N	0
1092	ADC-Rule-Install	0	0+	0+	0
1093	ADC-Rule-Remove	0	0	0	0
1094	ADC-Rule-Definition	0	0	0	0
1096	ADC-Rule-Name	N	N	N	N
1097	ADC-Rule-Report	0+	0+	0	0+
2848	Extended-APN-AMBR-DL	0	N	N	0
2849	Extended-APN-AMBR-UL	0	N	N	0
2850	Extended-GBR-DL	0	N	N	0
2850	Extended-GBR-UL	0	N	N	0

Result Codes (Result-Code AVP)

Table 10: Result Codes (Result-Code AVP)

Result Code Id	Result Code Name	Description
Success
2001	DIAMETER_SUCCESS	The request was successfully completed.
Protocol Errors
3001	DIAMETER_COMMAND_UNSUPPORTED	Rx: treated as an error. Tx: not supported.
3002	DIAMETER_UNABLE_TO_DELIVER	Rx: peer failover procedure on the Diameter base level is invoked. After the same response (3002) is received from all eligible peers, the application level (NASREQ/Gx/Gy) is notified. The message can then be retransmitted one last time with the destination-host AVP cleared. For a message to be retransmitted on the application level, server failover procedure must be enabled. Tx: diameter base replies with 3002 if it cannot route the received request message to its destination (this applies to Diameter multi-chassis configuration).
3003	DIAMETER_REALM_NOT_SERVED	Rx: treated as an error. Tx: not supported.
3004	DIAMETER_TOO_BUSY	Rx - The peer failover procedure on the Diameter base level is invoked. After the same response (3004) is received from all eligible peers, the application level (NASREQ, Gx, Gy) is notified. The message can then be retransmitted one last time with the destination-host AVP cleared. For a message to be retransmitted on the application level, server failover procedure must be enabled. Tx: not supported.
3005	DIAMETER_LOOP_DETECTED	Rx: treated as an error. Tx: not supported.
3006	DIAMETER_REDIRECT_INDICATION	Rx: treated as an error. Tx: not supported.
3007	DIAMETER_APPLICATION_UNSUPPORTED	Rx: treated as an error. Tx: not supported.
3008	DIAMETER_INVALID_HDR_BITS	Rx: treated as an error. Tx: not supported.
3009	DIAMETER_INVALID_AVP_BITS	Rx: treated as an error. Tx: not supported.
3010	DIAMETER_UNKNOWN_PEER	Rx: treated as an error. Tx: not supported.
Permanent Failures
5001	DIAMETER_AVP_UNSUPPORTED	Rx: treated as an error. Tx: Reception of an unrecognized AVP with M-bit set triggers a response (RAA) message that contains the Result-Code AVP whose value is set to DIAMETER_AVP_UNSUPORTED, and the Failed-AVP AVP containing the offending AVP.
5002	DIAMETER_UNKNOWN_SESSION	Rx: treated as an error. Tx: In case that a message from PCRF is received for a non-existing session, the 7750 SR replies with this value.
5004	DIAMETER_INVALID_AVP_VALUE	Rx: treated as an error. Tx: Reception of an AVP with invalid value triggers a response message (RAA) that contains the Result-Code AVP whose value is set to DIAMETER_INVALID_AVP_VALUE, and the Failed-AVP containing the AVP that caused the error.
5005	DIAMETER_MISSING_AVP	Rx: treated as an error. Tx: not supported.
5007	DIAMETER_CONTRADICTING_AVPS	Rx: treated as an error. Tx: not supported.
5008	DIAMETER_AVP_NOT_ALLOWED	Rx: treated as an error. Tx: not supported.
5009	DIAMETER_AVP_OCCURS_TOO_MANY_TIMES	Rx: treated as an error. Tx: not supported.
5010	DIAMETER_NO_COMMON_APPLICATION	Rx: treated as an error. Tx: not supported.
5011	DIAMETER_UNSUPPORTED_VERSION	Rx: treated as an error. Tx: As an example, a RAA message carries this AVP as a response to a RAR message that was received by a SR OS node while the Gx session was in a session terminating state. A session terminating state is considered a state where the SR OS node is waiting for a CCA-T message as a response to a previously initiated CCR-T message by the SR OS node.
5012	DIAMETER_UNABLE_TO_COMPLY	Rx: treated as an error. Tx: For example, a RAA message carries this AVP as a response to a RAR message that was received by a SR OS node while the Gx session was in a session terminating state. A session terminating state is considered a state where the SR OS node is waiting for a CCA-T message as a response to a previously initiated CCR-T message by the SR OS node.
5013	DIAMETER_INVALID_BIT_IN_HEADER	Rx: treated as an error. Tx: not supported.
5014	DIAMETER_INVALID_AVP_LENGTH	Rx: treated as an error. Tx: not supported.
5015	DIAMETER_INVALID_MESSAGE_LENGTH	Rx: treated as an error. Tx: not supported.
5016	DIAMETER_INVALID_AVP_BIT_COMBO	Rx: treated as an error. Tx: not supported.
5017	DIAMETER_NO_COMMON_SECURITY	Rx: treated as an error. Tx: not supported.
Gx Specific Permanent Failures
5140	DIAMETER_ERROR_INITIAL_PARAMETERS	Rx: treated as an error. Tx: not supported.
5141	DIAMETER_ERROR_TRIGGER_EVENT	Rx: treated as an error. Tx: not supported.
5142	DIAMETER_PCC_RULE_EVENT	Rx: treated as an error. Tx: not supported.
5148	DIAMETER_ADC_RULE_EVENT	Rx: treated as an error. Tx: not supported.

Rule Failure Codes (Rule-Failure-Code AVP)

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

Rule Failure Code Id	Rule Failure Name	Description
1	UNKNOWN_RULE_NAME	Rx: treated as an error. Tx: not supported.
4	GW/7750 SR_MALFUNCTION	This value indicates the problem related to the value carried in the AVP. For example, the value references a non-existing object (rule), the value is out of bounds or any other unexpected error. The error-message AVP in CCR/RAA carried on the top level or Failed-AVP provides more information about the event for debugging purposes.
5	RESOURCE_LIMITATION	Rx: treated as an error. Tx: not supported.
14	TDF_APPLICATION_IDENTIFIER_ERROR	Rx: treated as an error. Tx: not supported.

Event Triggers (Event-Trigger AVP)

Table 12: Event Triggers (Event-Trigger AVP)

Event Trigger Id	Event Trigger Name	Description
2	RAT_CHANGE	For GTP S11 access, this is triggered if a new RAT Type is received in GTP.
13	USER_LOCATION_CHANGE	For WLAN-GW, this is triggered for any UE location change. For GTP S11 access, this is triggered if a ULI was received in GTP with either non-ECGI/TAI values or a ECGI/TAI value that changed.
14	NO_EVENT_TRIGGERS	Sent in CCA and RAR by the PCRF to indicate that PCRF does not require any Event Trigger notification except for those events that do not require subscription and are always provisioned.
18	UE_IP_ADDRESS_ALLOCATE	When used in a CCR command, this value indicates that the 7750 SR generated the request because a client’s IPv4 address is allocated. The Framed-IP-Address, Framed-IPv6-Prefix, Delegated-IPv6-Prefix or Alc-IPv6-Address AVPs is provided in the same request. This event trigger is reported when the corresponding event occurs, even if the event trigger is not provisioned by the PCRF.
19	UE_IP_ADDRESS_RELEASE	When used in a CCR command, this value indicates that the 7750 SR generated the request because a client’s IP address/prefix is released. The Framed-IP-Address, Framed-IPv6-Prefix, Delegated-IPv6-Prefix or Alc-IPv6-Address AVPs is provided in the same request. This event trigger shall be reported when the corresponding event occurs, even if the event trigger is not provisioned by the PCRF.
21	AN_GW_CHANGE	This value is sent by the PCRF to inform the Diameter client in the SR to trigger a notification for every subscriber during a switchover in a multi-chassis configuration. This notification contains the IP address of the newly active BNG (AN_GW_ADDRESS) sent in a CCR-U message. If the Diameter client in the SR OS node is not armed with this event-trigger, the subscriber switchover is not reported to the PCRF.
22	SUCCESSFUL_RESOURCE_ALLOCATION	Not supported.
26	TAI_CHANGE	For GTP S11 access, this is triggered if a ULI is signaled in GTP with a TAI that changed from the last value received.
27	ECGI_CHANGE	For GTP S11 access, this is triggered if a ULI is signaled in GTP with a ECGI that changed from the last value received.
33	USAGE_REPORT	This value is used in a CCA and RAR commands by the PCRF when requesting usage monitoring on the 7750 SR. The PCRF also provides in the CCA or RAR command the Usage-Monitoring-Information AVPs including the Monitoring-Key AVP and the Granted-Service-Unit AVP. When used in a CCR command, this value indicates that the 7750 SR generated the request to report the accumulated usage for one or more monitoring keys. The 7750 SR provides the accumulated usage volume using the Usage-Monitoring-Information AVPs including the Monitoring-Key AVP and the Used-Service-Unit AVP.

Termination Causes (Termination-Cause AVP)

Table 13: Termination Causes (Termination-Cause AVP)

Termination Cause Id	Termination Cause Name	Description	Reference
1	DIAMETER_LOGOUT	Example reasons: Clear subscriber via CLI, PADT Received	[RFC 3588][RFC 6733]
2	DIAMETER_SERVICE_NOT_PROVIDED	Example reason: Subscriber-host is terminated via force-NACK received via RADIUS CoA	[RFC 3588][RFC 6733]
3	DIAMETER_BAD_ANSWER	Example reason: Problem with initial parameters during sub-host instantiation while Gx fallback is disabled or default subscriber parameters are not available.	[RFC 3588][RFC 6733]
4	DIAMETER_ADMINISTRATIVE	Example reasons: Host deleted via RADIUS DISCONNECT, Service shutdown for PPPoE subscriber	[RFC 3588][RFC 6733]
5	DIAMETER_LINK_BROKEN	Example reasons: SAP is deleted, SHCV check fails	[RFC 3588][RFC 6733]
8	DIAMETER_SESSION_TIMEOUT	Example reason: When idle timeout for the subscriber-host is enabled and its value is reached.	[RFC 3588][RFC 6733]

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

FRF2.2, PVC Network-to-Network Interface (NNI) Implementation Agreement

ITU-T Q.933 Annex A, Additional procedures for Permanent Virtual Connection (PVC) status management

Generalized Multiprotocol Label Switching (GMPLS)

draft-ietf-ccamp-rsvp-te-srlg-collect-04, RSVP-TE Extensions for Collecting SRLG Information

RFC 3471, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description

RFC 3473, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions

RFC 4204, Link Management Protocol (LMP)

RFC 4208, Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model

RFC 4872, RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery

RFC 5063, Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart - helper mode

gRPC Remote Procedure Calls (gRPC)

cert.proto Version 0.1.0, gRPC Network Operations Interface (gNOI) Certificate Management Service

file.proto Version 0.1.0, gRPC Network Operations Interface (gNOI) File Service

gnmi.proto Version 0.7.0, gRPC Network Management Interface (gNMI) Service Specification

PROTOCOL-HTTP2, gRPC over HTTP2

system.proto Version 1.0.0, gRPC Network Operations Interface (gNOI) System Service

Intermediate System to Intermediate System (IS-IS)

draft-ietf-isis-mi-02, IS-IS Multi-Instance

draft-kaplan-isis-ext-eth-02, Extended Ethernet Frame Size Support

ISO/IEC 10589:2002 Second Edition, Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473)

RFC 1195, Use of OSI IS-IS for Routing in TCP/IP and Dual Environments

RFC 2973, IS-IS Mesh Groups

RFC 3359, *Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate System

RFC 3719, Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS)

RFC 3787, Recommendations for Interoperable IP Networks using Intermediate System to Intermediate System (IS-IS)

RFC 4971, Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information

RFC 5120, M-ISIS: Multi Topology (MT) Routing in IS-IS

RFC 5130, A Policy Control Mechanism in IS-IS Using Administrative Tags

RFC 5301, Dynamic Hostname Exchange Mechanism for IS-IS

RFC 5302, Domain-wide Prefix Distribution with Two-Level IS-IS

RFC 5303, Three-Way Handshake for IS-IS Point-to-Point Adjacencies

RFC 5304, IS-IS Cryptographic Authentication

RFC 5305, IS-IS Extensions for Traffic Engineering TE

RFC 5306, Restart Signaling for IS-IS - helper mode

RFC 5307, IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)

RFC 5308, Routing IPv6 with IS-IS

RFC 5309, Point-to-Point Operation over LAN in Link State Routing Protocols

RFC 5310, IS-IS Generic Cryptographic Authentication

RFC 6119, IPv6 Traffic Engineering in IS-IS

RFC 6213, IS-IS BFD-Enabled TLV

RFC 6232, Purge Originator Identification TLV for IS-IS

RFC 6233, IS-IS Registry Extension for Purges

RFC 6329, IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging

RFC 7775, IS-IS Route Preference for Extended IP and IPv6 Reachability

RFC 7794, IS-IS Prefix Attributes for Extended IPv4 and IPv6 Reachability

RFC 7987, IS-IS Minimum Remaining Lifetime

RFC 8202, IS-IS Multi-Instance - single topology

RFC 8570, IS-IS Traffic Engineering (TE) Metric Extensions - delay metric

RFC 8919, IS-IS Application-Specific Link Attributes

Internet Protocol (IP) — Fast Reroute

draft-ietf-rtgwg-lfa-manageability-08, Operational management of Loop Free Alternates

RFC 5286, Basic Specification for IP Fast Reroute: Loop-Free Alternates

RFC 7431, Multicast-Only Fast Reroute

RFC 7490, Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)

Internet Protocol (IP) — General

draft-grant-tacacs-02, The TACACS+ Protocol

RFC 768, User Datagram Protocol

RFC 793, Transmission Control Protocol

RFC 854, Telnet Protocol Specifications

RFC 1350, The TFTP Protocol (revision 2)

RFC 2347, TFTP Option Extension

RFC 2348, TFTP Blocksize Option

RFC 2349, TFTP Timeout Interval and Transfer Size Options

RFC 2428, FTP Extensions for IPv6 and NATs

RFC 2784, Generic Routing Encapsulation (GRE)

RFC 2818, HTTP Over TLS

RFC 2890, Key and Sequence Number Extensions to GRE

RFC 3164, The BSD syslog Protocol

RFC 4250, The Secure Shell (SSH) Protocol Assigned Numbers

RFC 4251, The Secure Shell (SSH) Protocol Architecture

RFC 4252, The Secure Shell (SSH) Authentication Protocol - publickey, password

RFC 4253, The Secure Shell (SSH) Transport Layer Protocol

RFC 4254, The Secure Shell (SSH) Connection Protocol

RFC 4511, Lightweight Directory Access Protocol (LDAP): The Protocol

RFC 4513, Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms - TLS

RFC 4632, Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan

RFC 5082, The Generalized TTL Security Mechanism (GTSM)

RFC 5246, The Transport Layer Security (TLS) Protocol Version 1.2 - TLS client, RSA public key

RFC 5656, Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer - ECDSA

RFC 5925, The TCP Authentication Option

RFC 5926, Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)

RFC 6398, IP Router Alert Considerations and Usage - MLD

RFC 6528, Defending against Sequence Number Attacks

RFC 7011, Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information

RFC 7012, Information Model for IP Flow Information Export

RFC 7230, Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing

RFC 7231, Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content

RFC 7232, Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests

RFC 7301, Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension

Internet Protocol (IP) — Multicast

cisco-ipmulticast/pim-autorp-spec01, Auto-RP: Automatic discovery of Group-to-RP mappings for IP multicast - version 1

draft-ietf-bier-pim-signaling-08, PIM Signaling Through BIER Core

draft-ietf-idmr-traceroute-ipm-07, A “traceroute” facility for IP Multicast

draft-ietf-l2vpn-vpls-pim-snooping-07, Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)

RFC 1112, Host Extensions for IP Multicasting

RFC 2236, Internet Group Management Protocol, Version 2

RFC 2365, Administratively Scoped IP Multicast

RFC 2375, IPv6 Multicast Address Assignments

RFC 2710, Multicast Listener Discovery (MLD) for IPv6

RFC 3306, Unicast-Prefix-based IPv6 Multicast Addresses

RFC 3376, Internet Group Management Protocol, Version 3

RFC 3446, Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)

RFC 3590, Source Address Selection for the Multicast Listener Discovery (MLD) Protocol

RFC 3618, Multicast Source Discovery Protocol (MSDP)

RFC 3810, Multicast Listener Discovery Version 2 (MLDv2) for IPv6

RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address

RFC 3973, Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised) - auto-RP groups

RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches

RFC 4604, Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast

RFC 4607, Source-Specific Multicast for IP

RFC 4608, Source-Specific Protocol Independent Multicast in 232/8

RFC 4610, Anycast-RP Using Protocol Independent Multicast (PIM)

RFC 4611, Multicast Source Discovery Protocol (MSDP) Deployment Scenarios

RFC 5059, Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM)

RFC 5186, Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction

RFC 5384, The Protocol Independent Multicast (PIM) Join Attribute Format

RFC 5496, The Reverse Path Forwarding (RPF) Vector TLV

RFC 6037, Cisco Systems’ Solution for Multicast in MPLS/BGP IP VPNs

RFC 6512, Using Multipoint LDP When the Backbone Has No Route to the Root

RFC 6513, Multicast in MPLS/BGP IP VPNs

RFC 6514, BGP Encodings and Procedures for Multicast in MPLS/IP VPNs

RFC 6515, IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPNs

RFC 6516, IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane and Selective Provider Multicast Service Interface (S-PMSI) Join Messages

RFC 6625, Wildcards in Multicast VPN Auto-Discover Routes

RFC 6826, Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Path

RFC 7246, Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context

RFC 7385, IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points

RFC 7716, Global Table Multicast with BGP Multicast VPN (BGP-MVPN) Procedures

RFC 7761, Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)

RFC 8279, Multicast Using Bit Index Explicit Replication (BIER)

RFC 8296, Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks - MPLS encapsulation

RFC 8401, Bit Index Explicit Replication (BIER) Support via IS-IS

RFC 8444, OSPFv2 Extensions for Bit Index Explicit Replication (BIER)

RFC 8487, Mtrace Version 2: Traceroute Facility for IP Multicast

RFC 8534, Explicit Tracking with Wildcard Routes in Multicast VPN - (C-,C-) wildcard

RFC 8556, Multicast VPN Using Bit Index Explicit Replication (BIER)

Internet Protocol (IP) — Version 4

RFC 791, Internet Protocol

RFC 792, Internet Control Message Protocol

RFC 826, An Ethernet Address Resolution Protocol

RFC 951, Bootstrap Protocol (BOOTP) - relay

RFC 1034, Domain Names - Concepts and Facilities

RFC 1035, Domain Names - Implementation and Specification

RFC 1191, Path MTU Discovery - router specification

RFC 1519, Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy

RFC 1534, Interoperation between DHCP and BOOTP

RFC 1542, Clarifications and Extensions for the Bootstrap Protocol

RFC 1812, Requirements for IPv4 Routers

RFC 1918, Address Allocation for Private Internets

RFC 2003, IP Encapsulation within IP

RFC 2131, Dynamic Host Configuration Protocol

RFC 2132, DHCP Options and BOOTP Vendor Extensions

RFC 2401, Security Architecture for Internet Protocol

RFC 3021, Using 31-Bit Prefixes on IPv4 Point-to-Point Links

RFC 3046, DHCP Relay Agent Information Option (Option 82)

RFC 3768, Virtual Router Redundancy Protocol (VRRP)

RFC 4884, Extended ICMP to Support Multi-Part Messages - ICMPv4 and ICMPv6 Time Exceeded

Internet Protocol (IP) — Version 6

RFC 2464, Transmission of IPv6 Packets over Ethernet Networks

RFC 2529, Transmission of IPv6 over IPv4 Domains without Explicit Tunnels

RFC 3122, Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification

RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

RFC 3587, IPv6 Global Unicast Address Format

RFC 3596, DNS Extensions to Support IP version 6

RFC 3633, IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6

RFC 3646, DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

RFC 3736, Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6

RFC 3971, SEcure Neighbor Discovery (SEND)

RFC 3972, Cryptographically Generated Addresses (CGA)

RFC 4007, IPv6 Scoped Address Architecture

RFC 4193, Unique Local IPv6 Unicast Addresses

RFC 4291, Internet Protocol Version 6 (IPv6) Addressing Architecture

RFC 4443, Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification

RFC 4861, Neighbor Discovery for IP version 6 (IPv6)

RFC 4862, IPv6 Stateless Address Autoconfiguration - router functions

RFC 4890, Recommendations for Filtering ICMPv6 Messages in Firewalls

RFC 4941, Privacy Extensions for Stateless Address Autoconfiguration in IPv6

RFC 5007, DHCPv6 Leasequery

RFC 5095, Deprecation of Type 0 Routing Headers in IPv6

RFC 5722, Handling of Overlapping IPv6 Fragments

RFC 5798, Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 - IPv6

RFC 5952, A Recommendation for IPv6 Address Text Representation

RFC 6092, Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service - Internet Control and Management, Upper-Layer Transport Protocols, UDP Filters, IPsec and Internet Key Exchange (IKE), TCP Filters

RFC 6106, IPv6 Router Advertisement Options for DNS Configuration

RFC 6164, Using 127-Bit IPv6 Prefixes on Inter-Router Links

RFC 8021, Generation of IPv6 Atomic Fragments Considered Harmful

RFC 8200, Internet Protocol, Version 6 (IPv6) Specification

RFC 8201, Path MTU Discovery for IP version 6

Internet Protocol Security (IPsec)

draft-ietf-ipsec-isakmp-mode-cfg-05, The ISAKMP Configuration Method

draft-ietf-ipsec-isakmp-xauth-06, Extended Authentication within ISAKMP/Oakley (XAUTH)

RFC 2401, Security Architecture for the Internet Protocol

RFC 2403, The Use of HMAC-MD5-96 within ESP and AH

RFC 2404, The Use of HMAC-SHA-1-96 within ESP and AH

RFC 2405, The ESP DES-CBC Cipher Algorithm With Explicit IV

RFC 2406, IP Encapsulating Security Payload (ESP)

RFC 2407, IPsec Domain of Interpretation for ISAKMP (IPsec DoI)

RFC 2408, Internet Security Association and Key Management Protocol (ISAKMP)

RFC 2409, The Internet Key Exchange (IKE)

RFC 2410, The NULL Encryption Algorithm and Its Use With IPsec

RFC 3526, More Modular Exponential (MODP) Diffie-Hellman group for Internet Key Exchange (IKE)

RFC 3566, The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec

RFC 3602, The AES-CBC Cipher Algorithm and Its Use with IPsec

RFC 3706, A Traffic-Based Method of Detecting Dead Internet Key Exchange (IKE) Peers

RFC 3947, Negotiation of NAT-Traversal in the IKE

RFC 3948, UDP Encapsulation of IPsec ESP Packets

RFC 4106, The Use of Galois/Counter Mode (GCM) in IPsec ESP

RFC 4210, Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)

RFC 4211, Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)

RFC 4301, Security Architecture for the Internet Protocol

RFC 4303, IP Encapsulating Security Payload

RFC 4307, Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)

RFC 4308, Cryptographic Suites for IPsec

RFC 4434, The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)

RFC 4543, The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH

RFC 4868, Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPSec

RFC 4945, The Internet IP Security PKI Profile of IKEv1/ISAKMP, IKEv2 and PKIX

RFC 5019, The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments

RFC 5280, Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile

RFC 5282, Using Authenticated Encryption Algorithms with the Encrypted Payload of the IKEv2 Protocol

RFC 5903, ECP Groups for IKE and IKEv2

RFC 5998, An Extension for EAP-Only Authentication in IKEv2

RFC 6379, Suite B Cryptographic Suites for IPsec

RFC 6380, Suite B Profile for Internet Protocol Security (IPsec)

RFC 6712, Internet X.509 Public Key Infrastructure – HTTP Transfer for the Certificate Management Protocol (CMP)

RFC 6960, X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP

RFC 7296, Internet Key Exchange Protocol Version 2 (IKEv2)

RFC 7321, Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)

RFC 7383, Internet Key Exchange Protocol Version 2 (IKEv2) Message Fragmentation

RFC 7427, Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)

RFC 7468, Textual Encodings of PKIX, PKCS, and CMS Structures

Label Distribution Protocol (LDP)

draft-pdutta-mpls-ldp-adj-capability-00, LDP Adjacency Capabilities

draft-pdutta-mpls-ldp-v2-00, LDP Version 2

draft-pdutta-mpls-mldp-up-redundancy-00, Upstream LSR Redundancy for Multi-point LDP Tunnels

draft-pdutta-mpls-multi-ldp-instance-00, Multiple LDP Instances

draft-pdutta-mpls-tldp-hello-reduce-04, Targeted LDP Hello Reduction

RFC 3037, LDP Applicability

RFC 3478, Graceful Restart Mechanism for Label Distribution Protocol - helper mode

RFC 5036, LDP Specification

RFC 5283, LDP Extension for Inter-Area Label Switched Paths (LSPs)

RFC 5443, LDP IGP Synchronization

RFC 5561, LDP Capabilities

RFC 5919, Signaling LDP Label Advertisement Completion

RFC 6388, Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths

RFC 6512, Using Multipoint LDP When the Backbone Has No Route to the Root

RFC 6826, Multipoint LDP in-band signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths

RFC 7032, LDP Downstream-on-Demand in Seamless MPLS

RFC 7473, Controlling State Advertisements of Non-negotiated LDP Applications

RFC 7552, Updates to LDP for IPv6

Layer Two Tunneling Protocol (L2TP) Network Server (LNS)

draft-mammoliti-l2tp-accessline-avp-04, Layer 2 Tunneling Protocol (L2TP) Access Line Information Attribute Value Pair (AVP) Extensions

RFC 2661, Layer Two Tunneling Protocol “L2TP”

RFC 2809, Implementation of L2TP Compulsory Tunneling via RADIUS

RFC 3438, Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers: Internet Assigned Numbers Authority (IANA) Considerations Update

RFC 3931, Layer Two Tunneling Protocol - Version 3 (L2TPv3)

RFC 4719, Transport of Ethernet Frames over Layer 2 Tunneling Protocol Version 3 (L2TPv3)

RFC 4951, Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) “failover”

Multiprotocol Label Switching (MPLS)

draft-ietf-mpls-lsp-ping-ospfv3-codepoint-02, OSPFv3 CodePoint for MPLS LSP Ping

RFC 3031, Multiprotocol Label Switching Architecture

RFC 3032, MPLS Label Stack Encoding

RFC 3270, Multi-Protocol Label Switching (MPLS) Support of Differentiated Services - E-LSP

RFC 3443, Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks

RFC 4023, Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)

RFC 4182, Removing a Restriction on the use of MPLS Explicit NULL

RFC 5332, MPLS Multicast Encapsulations

RFC 5884, Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)

RFC 6374, Packet Loss and Delay Measurement for MPLS Networks - Delay Measurement, Channel Type 0x000C

RFC 6424, Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels

RFC 6425, Detecting Data Plane Failures in Point-to-Multipoint Multiprotocol Label Switching (MPLS) - Extensions to LSP Ping

RFC 6790, The Use of Entropy Labels in MPLS Forwarding

RFC 7510, Encapsulating MPLS in UDP

RFC 7746, Label Switched Path (LSP) Self-Ping

RFC 7876, UDP Return Path for Packet Loss and Delay Measurement for MPLS Networks - Delay Measurement

RFC 8029, Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures

Multiprotocol Label Switching — Transport Profile (MPLS-TP)

RFC 5586, MPLS Generic Associated Channel

RFC 5921, A Framework for MPLS in Transport Networks

RFC 5960, MPLS Transport Profile Data Plane Architecture

RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers

RFC 6378, MPLS Transport Profile (MPLS-TP) Linear Protection

RFC 6426, MPLS On-Demand Connectivity and Route Tracing

RFC 6427, MPLS Fault Management Operations, Administration, and Maintenance (OAM)

RFC 6428, Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile

RFC 6478, Pseudowire Status for Static Pseudowires

RFC 7213, MPLS Transport Profile (MPLS-TP) Next-Hop Ethernet Addressing

Network Address Translation (NAT)

draft-ietf-behave-address-format-10, IPv6 Addressing of IPv4/IPv6 Translators

draft-ietf-behave-v6v4-xlate-23, IP/ICMP Translation Algorithm

draft-miles-behave-l2nat-00, Layer2-Aware NAT

draft-nishitani-cgn-02, Common Functions of Large Scale NAT (LSN)

RFC 4787, Network Address Translation (NAT) Behavioral Requirements for Unicast UDP

RFC 5382, NAT Behavioral Requirements for TCP

RFC 5508, NAT Behavioral Requirements for ICMP

RFC 6146, Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers

RFC 6333, Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion

RFC 6334, Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite

RFC 6887, Port Control Protocol (PCP)

RFC 6888, Common Requirements For Carrier-Grade NATs (CGNs)

RFC 7753, Port Control Protocol (PCP) Extension for Port-Set Allocation

RFC 7915, IP/ICMP Translation Algorithm

Network Configuration Protocol (NETCONF)

RFC 5277, NETCONF Event Notifications

RFC 6020, YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)

RFC 6022, YANG Module for NETCONF Monitoring

RFC 6241, Network Configuration Protocol (NETCONF)

RFC 6242, Using the NETCONF Protocol over Secure Shell (SSH)

RFC 6243, With-defaults Capability for NETCONF

RFC 8342, Network Management Datastore Architecture (NMDA) - Startup, Candidate, Running and Intended datastores

RFC 8525, YANG Library

RFC 8526, NETCONF Extensions to Support the Network Management Datastore Architecture - operation

Open Shortest Path First (OSPF)

RFC 1586, Guidelines for Running OSPF Over Frame Relay Networks

RFC 1765, OSPF Database Overflow

RFC 2328, OSPF Version 2

RFC 3101, The OSPF Not-So-Stubby Area (NSSA) Option

RFC 3509, Alternative Implementations of OSPF Area Border Routers

RFC 3623, Graceful OSPF Restart Graceful OSPF Restart - helper mode

RFC 3630, Traffic Engineering (TE) Extensions to OSPF Version 2

RFC 4203, OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)

RFC 4222, Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion Avoidance

RFC 4552, Authentication/Confidentiality for OSPFv3

RFC 4576, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)

RFC 4577, OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)

RFC 5185, OSPF Multi-Area Adjacency

RFC 5187, OSPFv3 Graceful Restart - helper mode

RFC 5243, OSPF Database Exchange Summary List Optimization

RFC 5250, The OSPF Opaque LSA Option

RFC 5309, Point-to-Point Operation over LAN in Link State Routing Protocols

RFC 5340, OSPF for IPv6

RFC 5642, Dynamic Hostname Exchange Mechanism for OSPF

RFC 5709, OSPFv2 HMAC-SHA Cryptographic Authentication

RFC 5838, Support of Address Families in OSPFv3

RFC 6549, OSPFv2 Multi-Instance Extensions

RFC 6987, OSPF Stub Router Advertisement

RFC 7684, OSPFv2 Prefix/Link Attribute Advertisement

RFC 7770, Extensions to OSPF for Advertising Optional Router Capabilities

RFC 8362, OSPFv3 Link State Advertisement (LSA) Extensibility

RFC 8920, OSPF Application-Specific Link Attributes

OpenFlow

TS-007 Version 1.3.1, OpenFlow Switch Specification - OpenFlow-hybrid switches

Path Computation Element Protocol (PCEP)

draft-alvarez-pce-path-profiles-04, PCE Path Profiles

draft-dhs-spring-pce-sr-p2mp-policy-00, PCEP extensions for p2mp sr policy

draft-ietf-pce-segment-routing-08, PCEP Extensions for Segment Routing

RFC 5440, Path Computation Element (PCE) Communication Protocol (PCEP)

RFC 8281, PCEP Extensions for PCE-initiated LSP Setup in a Stateful PCE Model

RFC 8321, Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE

Point-to-Point Protocol (PPP)

RFC 1332, The PPP Internet Protocol Control Protocol (IPCP)

RFC 1377, The PPP OSI Network Layer Control Protocol (OSINLCP)

RFC 1661, The Point-to-Point Protocol (PPP)

RFC 1662, PPP in HDLC-like Framing

RFC 1877, PPP Internet Protocol Control Protocol Extensions for Name Server Addresses

RFC 1989, PPP Link Quality Monitoring

RFC 1990, The PPP Multilink Protocol (MP)

RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP)

RFC 2153, PPP Vendor Extensions

RFC 2516, A Method for Transmitting PPP Over Ethernet (PPPoE)

RFC 2615, PPP over SONET/SDH

RFC 2686, The Multi-Class Extension to Multi-Link PPP

RFC 2878, PPP Bridging Control Protocol (BCP)

RFC 4638, Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE)

RFC 5072, IP Version 6 over PPP

Policy Management and Credit Control

3GPP TS 29.212 Release 11, Policy and Charging Control (PCC); Reference points - Gx support as it applies to wireline environment (BNG)

RFC 4006, Diameter Credit-Control Application

RFC 6733, Diameter Base Protocol

Pseudowire

draft-ietf-l2vpn-vpws-iw-oam-04, OAM Procedures for VPWS Interworking

MFA Forum 9.0.0, The Use of Virtual trunks for ATM/MPLS Control Plane Interworking

MFA Forum 12.0.0, Multiservice Interworking - Ethernet over MPLS

MFA Forum 13.0.0, Fault Management for Multiservice Interworking v1.0

MFA Forum 16.0.0, Multiservice Interworking - IP over MPLS

RFC 3916, Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)

RFC 3985, Pseudo Wire Emulation Edge-to-Edge (PWE3)

RFC 4385, Pseudo Wire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN

RFC 4446, IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)

RFC 4447, Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)

RFC 4448, Encapsulation Methods for Transport of Ethernet over MPLS Networks

RFC 4619, Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) Networks

RFC 4717, Encapsulation Methods for Transport Asynchronous Transfer Mode (ATM) over MPLS Networks

RFC 4816, Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport Service

RFC 5085, Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires

RFC 5659, An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge

RFC 5885, Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)

RFC 6073, Segmented Pseudowire

RFC 6310, Pseudowire (PW) Operations, Administration, and Maintenance (OAM) Message Mapping

RFC 6391, Flow-Aware Transport of Pseudowires over an MPLS Packet Switched Network

RFC 6575, Address Resolution Protocol (ARP) Mediation for IP Interworking of Layer 2 VPNs

RFC 6718, Pseudowire Redundancy

RFC 6829, Label Switched Path (LSP) Ping for Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6

RFC 6870, Pseudowire Preferential Forwarding Status bit

RFC 7023, MPLS and Ethernet Operations, Administration, and Maintenance (OAM) Interworking

RFC 7267, Dynamic Placement of Multi-Segment Pseudowires

RFC 7392, Explicit Path Routing for Dynamic Multi-Segment Pseudowires - ER-TLV and ER-HOP IPv4 Prefix

Quality of Service (QoS)

RFC 2430, A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)

RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers

RFC 2597, Assured Forwarding PHB Group

RFC 3140, Per Hop Behavior Identification Codes

RFC 3246, An Expedited Forwarding PHB (Per-Hop Behavior)

Remote Authentication Dial In User Service (RADIUS)

RFC 2865, Remote Authentication Dial In User Service (RADIUS)

RFC 2866, RADIUS Accounting

RFC 2867, RADIUS Accounting Modifications for Tunnel Protocol Support

RFC 2868, RADIUS Attributes for Tunnel Protocol Support

RFC 2869, RADIUS Extensions

RFC 3162, RADIUS and IPv6

RFC 4818, RADIUS Delegated-IPv6-Prefix Attribute

RFC 5176, Dynamic Authorization Extensions to RADIUS

RFC 6911, RADIUS attributes for IPv6 Access Networks

RFC 6929, Remote Authentication Dial-In User Service (RADIUS) Protocol Extensions

Resource Reservation Protocol — Traffic Engineering (RSVP-TE)

draft-newton-mpls-te-dynamic-overbooking-00, A Diffserv-TE Implementation Model to dynamically change booking factors during failure events

RFC 2702, Requirements for Traffic Engineering over MPLS

RFC 2747, RSVP Cryptographic Authentication

RFC 2961, RSVP Refresh Overhead Reduction Extensions

RFC 3097, RSVP Cryptographic Authentication – Updated Message Type Value

RFC 3209, RSVP-TE: Extensions to RSVP for LSP Tunnels

RFC 3473, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions - IF_ID RSVP_HOP object with unnumbered interfaces and RSVP-TE graceful restart helper procedures

RFC 3477, Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)

RFC 3564, Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering

RFC 3906, Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels

RFC 4090, Fast Reroute Extensions to RSVP-TE for LSP Tunnels

RFC 4124, Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering

RFC 4125, Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering

RFC 4127, Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering

RFC 4561, Definition of a Record Route Object (RRO) Node-Id Sub-Object

RFC 4875, Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)

RFC 4950, ICMP Extensions for Multiprotocol Label Switching

RFC 5151, Inter-Domain MPLS and GMPLS Traffic Engineering – Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions

RFC 5712, MPLS Traffic Engineering Soft Preemption

RFC 5817, Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks

Routing Information Protocol (RIP)

RFC 1058, Routing Information Protocol

RFC 2080, RIPng for IPv6

RFC 2082, RIP-2 MD5 Authentication

RFC 2453, RIP Version 2

Segment Routing (SR)

draft-bashandy-rtgwg-segment-routing-uloop-06, Loop avoidance using Segment Routing

draft-ietf-idr-bgp-ls-segment-routing-ext-16, BGP Link-State extensions for Segment Routing

draft-ietf-idr-bgp-ls-segment-routing-msd-09, Signaling MSD (Maximum SID Depth) using Border Gateway Protocol Link-State

draft-ietf-idr-segment-routing-te-policy-09, Advertising Segment Routing Policies in BGP

draft-ietf-isis-mpls-elc-10, Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS - advertising ELC

draft-ietf-lsr-flex-algo-08, IGP Flexible Algorithm

draft-ietf-ospf-mpls-elc-12, Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF - advertising ELC

draft-ietf-rtgwg-segment-routing-ti-lfa-01, Topology Independent Fast Reroute using Segment Routing

draft-ietf-spring-conflict-resolution-05, Segment Routing MPLS Conflict Resolution

draft-ietf-spring-segment-routing-policy-08, Segment Routing Policy Architecture

draft-ietf-teas-sr-rsvp-coexistence-rec-02, Recommendations for RSVP-TE and Segment Routing LSP co-existence

draft-voyer-pim-sr-p2mp-policy-02, Segment Routing Point-to-Multipoint Policy

draft-voyer-spring-sr-p2mp-policy-03, SR Replication Policy for P2MP Service Delivery

RFC 8287, Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes

RFC 8476, Signaling Maximum SID Depth (MSD) Using OSPF - node MSD

RFC 8491, Signaling Maximum SID Depth (MSD) Using IS-IS - node MSD

RFC 8660, Segment Routing with the MPLS Data Plane

RFC 8661, Segment Routing MPLS Interworking with LDP

RFC 8663, MPLS Segment Routing over IP - BGP SR with SR-MPLS-over-UDP/IP

RFC 8665, OSPF Extensions for Segment Routing

RFC 8666, OSPFv3 Extensions for Segment Routing

RFC 8667, IS-IS Extensions for Segment Routing

RFC 8669, Segment Routing Prefix Segment Identifier Extensions for BGP

Simple Network Management Protocol (SNMP)

RFC 1157, A Simple Network Management Protocol (SNMP)

RFC 1215, A Convention for Defining Traps for use with the SNMP

RFC 1901, Introduction to Community-based SNMPv2

RFC 3410, Introduction and Applicability Statements for Internet Standard Management Framework

RFC 3411, An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks

RFC 3412, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)

RFC 3413, Simple Network Management Protocol (SNMP) Applications

RFC 3414, User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)

RFC 3415, View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

RFC 3416, Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)

RFC 3417, Transport Mappings for the Simple Network Management Protocol (SNMP) - SNMP over UDP over IPv4

RFC 3584, Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework

RFC 3826, The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model

Simple Network Management Protocol (SNMP) - Management Information Base (MIB)

draft-ietf-snmpv3-update-mib-05, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)

draft-ietf-isis-wg-mib-06, Management Information Base for Intermediate System to Intermediate System (IS-IS)

draft-ietf-mboned-msdp-mib-01, Multicast Source Discovery protocol MIB

draft-ietf-mpls-ldp-mib-07, *Definitions of Managed Objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP)

draft-ietf-mpls-lsr-mib-06, Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base Using SMIv2

draft-ietf-mpls-te-mib-04, Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base

draft-ietf-ospf-mib-update-08, OSPF Version 2 Management Information Base

draft-ietf-vrrp-unified-mib-06, Definitions of Managed Objects for the VRRP over IPv4 and IPv6 - IPv6

ianaaddressfamilynumbers-mib, IANA-ADDRESS-FAMILY-NUMBERS-MIB

ianagmplstc-mib, IANA-GMPLS-TC-MIB

ianaiftype-mib, IANAifType-MIB

ianaiprouteprotocol-mib, IANA-RTPROTO-MIB

IEEE8021-CFM-MIB, IEEE P802.1ag(TM) CFM MIB

IEEE8021-PAE-MIB, IEEE 802.1X MIB

IEEE8023-LAG-MIB, IEEE 802.3ad MIB

LLDP-MIB, IEEE P802.1AB(TM) LLDP MIB

RFC 1212, Concise MIB Definitions

RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II

RFC 1724, RIP Version 2 MIB Extension

RFC 2021, Remote Network Monitoring Management Information Base Version 2 using SMIv2

RFC 2115, Management Information Base for Frame Relay DTEs Using SMIv2

RFC 2206, RSVP Management Information Base using SMIv2

RFC 2213, Integrated Services Management Information Base using SMIv2

RFC 2494, Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type

RFC 2514, Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management

RFC 2515, Definitions of Managed Objects for ATM Management

RFC 2578, Structure of Management Information Version 2 (SMIv2)

RFC 2579, Textual Conventions for SMIv2

RFC 2580, Conformance Statements for SMIv2

RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol

RFC 2819, Remote Network Monitoring Management Information Base

RFC 2856, Textual Conventions for Additional High Capacity Data Types

RFC 2863, The Interfaces Group MIB

RFC 2864, The Inverted Stack Table Extension to the Interfaces Group MIB

RFC 2933, Internet Group Management Protocol MIB

RFC 3014, Notification Log MIB

RFC 3165, Definitions of Managed Objects for the Delegation of Management Scripts

RFC 3231, Definitions of Managed Objects for Scheduling Management Operations

RFC 3273, Remote Network Monitoring Management Information Base for High Capacity Networks

RFC 3419, Textual Conventions for Transport Addresses

RFC 3498, Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures

RFC 3592, Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type

RFC 3593, Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals

RFC 3635, Definitions of Managed Objects for the Ethernet-like Interface Types

RFC 3637, Definitions of Managed Objects for the Ethernet WAN Interface Sublayer

RFC 3877, Alarm Management Information Base (MIB)

RFC 3895, Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types

RFC 3896, Definitions of Managed Objects for the DS3/E3 Interface Type

RFC 4001, Textual Conventions for Internet Network Addresses

RFC 4022, Management Information Base for the Transmission Control Protocol (TCP)

RFC 4113, Management Information Base for the User Datagram Protocol (UDP)

RFC 4220, Traffic Engineering Link Management Information Base

RFC 4273, Definitions of Managed Objects for BGP-4

RFC 4292, IP Forwarding Table MIB

RFC 4293, Management Information Base for the Internet Protocol (IP)

RFC 4631, Link Management Protocol (LMP) Management Information Base (MIB)

RFC 4878, Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces

RFC 7420, Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) Module

SFLOW-MIB Version 1.3 (Draft 5), sFlow MIB

Timing

GR-1244-CORE Issue 3, Clocks for the Synchronized Network: Common Generic Criteria

GR-253-CORE Issue 3, SONET Transport Systems: Common Generic Criteria

IEEE 1588-2008, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems

ITU-T G.781, Synchronization layer functions

ITU-T G.813, Timing characteristics of SDH equipment slave clocks (SEC)

ITU-T G.8261, Timing and synchronization aspects in packet networks

ITU-T G.8262, Timing characteristics of synchronous Ethernet equipment slave clock (EEC)

ITU-T G.8264, Distribution of timing information through packet networks

ITU-T G.8265.1, Precision time protocol telecom profile for frequency synchronization

ITU-T G.8275.1, Precision time protocol telecom profile for phase/time synchronization with full timing support from the network

RFC 3339, Date and Time on the Internet: Timestamps

RFC 5905, Network Time Protocol Version 4: Protocol and Algorithms Specification

Two-Way Active Measurement Protocol (TWAMP)

RFC 5357, A Two-Way Active Measurement Protocol (TWAMP) - server, unauthenticated mode

RFC 5938, Individual Session Control Feature for the Two-Way Active Measurement Protocol (TWAMP)

RFC 6038, Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features

RFC 8545, Well-Known Port Assignments for the One-Way Active Measurement Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP) - TWAMP

RFC 8762, Simple Two-Way Active Measurement Protocol - Unauthenticated

Virtual Private LAN Service (VPLS)

RFC 4761, Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling

RFC 4762, Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling

RFC 5501, Requirements for Multicast Support in Virtual Private LAN Services

RFC 6074, Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)

RFC 7041, Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Backbone Bridging

RFC 7117, Multicast in Virtual Private LAN Service (VPLS)

Voice and Video

DVB BlueBook A86, Transport of MPEG-2 TS Based DVB Services over IP Based Networks

ETSI TS 101 329-5 Annex E, QoS Measurement for VoIP - Method for determining an Equipment Impairment Factor using Passive Monitoring

ITU-T G.1020 Appendix I, Performance Parameter Definitions for Quality of Speech and other Voiceband Applications Utilizing IP Networks - Mean Absolute Packet Delay Variation & Markov Models

ITU-T G.107, The E Model - A computational model for use in planning

ITU-T P.564, Conformance testing for voice over IP transmission quality assessment models

RFC 3550, RTP: A Transport Protocol for Real-Time Applications - Appendix A.8

RFC 4585, Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)

RFC 4588, RTP Retransmission Payload Format

Wireless Local Area Network (WLAN) Gateway

3GPP TS 23.402, Architecture enhancements for non-3GPP accesses - S2a roaming based on GPRS

Yet Another Next Generation (YANG)

RFC 6991, Common YANG Data Types

RFC 7950, The YANG 1.1 Data Modeling Language

RFC 7951, JSON Encoding of Data Modeled with YANG

Yet Another Next Generation (YANG) - OpenConfig Modules

openconfig-aaa.yang version 0.4.0, OpenConfig AAA Module

openconfig-aaa-radius.yang version 0.3.0, OpenConfig AAA RADIUS Module

openconfig-aaa-tacacs.yang version 0.3.0, OpenConfig AAA TACACS+ Module

openconfig-acl.yang version 1.0.0, OpenConfig ACL Module

openconfig-bfd.yang version 0.1.0, OpenConfig BFD Module

openconfig-bgp.yang version 3.0.1, OpenConfig BGP Module

openconfig-bgp-common.yang version 3.0.1, OpenConfig BGP Common Module

openconfig-bgp-common-multiprotocol.yang version 3.0.1, OpenConfig BGP Common Multiprotocol Module

openconfig-bgp-common-structure.yang version 3.0.1, OpenConfig BGP Common Structure Module

openconfig-bgp-global.yang version 3.0.1, OpenConfig BGP Global Module

openconfig-bgp-neighbor.yang version 3.0.1, OpenConfig BGP Neighbor Module

openconfig-bgp-peer-group.yang version 3.0.1, OpenConfig BGP Peer Group Module

openconfig-bgp-policy.yang version 4.0.1, OpenConfig BGP Policy Module

openconfig-if-aggregate.yang version 2.0.0, OpenConfig Interfaces Aggregated Module

openconfig-if-ethernet.yang version 2.0.0, OpenConfig Interfaces Ethernet Module

openconfig-if-ip.yang version 2.0.0, OpenConfig Interfaces IP Module

openconfig-if-ip-ext.yang version 2.0.0, OpenConfig Interfaces IP Extensions Module

openconfig-interfaces.yang version 2.0.0, OpenConfig Interfaces Module

openconfig-isis.yang version 0.3.0, OpenConfig IS-IS Module

openconfig-isis-policy.yang version 0.3.0, OpenConfig IS-IS Policy Module

openconfig-isis-routing.yang version 0.3.0, OpenConfig IS-IS Routing Module

openconfig-lacp.yang version 1.1.0, OpenConfig LACP Module

openconfig-lldp.yang version 0.1.0, OpenConfig LLDP Module

openconfig-local-routing.yang version 1.0.1, OpenConfig Local Routing Module

openconfig-network-instance.yang version 0.8.0, OpenConfig Network Instance Module

openconfig-mpls.yang version 2.3.0, OpenConfig MPLS Module

openconfig-mpls-rsvp.yang version 2.3.0, OpenConfig MPLS RSVP Module

openconfig-mpls-te.yang version 2.3.0, OpenConfig MPLS TE Module

openconfig-packet-match.yang version 1.0.0, OpenConfig Packet Match Module

openconfig-platform.yang version 0.12.2, OpenConfig Platform Module

openconfig-platform-fan.yang version 0.1.1, OpenConfig Platform Fan Module

openconfig-platform-linecard.yang version 0.1.2, OpenConfig Platform Linecard Module

openconfig-relay-agent.yang version 0.1.0, OpenConfig Relay Agent Module

openconfig-routing-policy.yang version 3.0.0, OpenConfig Routing Policy Module

openconfig-system-logging.yang version 0.3.1, OpenConfig System Logging Module

openconfig-system-terminal.yang version 0.3.0, OpenConfig System Terminal Module

openconfig-telemetry.yang version 0.5.0, OpenConfig Telemetry Module

openconfig-vlan.yang version 2.0.0, OpenConfig VLAN Module

Docs: Radius

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

RADIUS Protocol
RADIUS Accounting Protocol
RADIUS Disconnect Protocol

RADIUS Protocol

This section give information on how AAA Gateway maps the RADIUS access-control messages for the RADIUS protocol defined in RFC-2865 and RFC-2869.

Section Compliance

The Table 1-1 below lists the compliance information for the RADIUS protocol sections in RFC-2865.

Table 1-1: RFC-2865 Section Compliance

Section Number	Section	Status	Notes
1	Introduction	Not applicable	-
1.1	Specification of Requirements	Not applicable	-
1.2	Terminology	Not applicable	-
2	Operation	Partially supported	-
2.1	Challenge/Response	Supported	-
2.2	Interoperation with PAP and CHAP	Not supported	-
2.3	Proxy	Not applicable	-
2.4	Why UDP?	Not applicable	-
2.5	Retransmission Hints	Supported	-
2.6	Keep-Alives Considered Harmful	Supported	-
3	Packet Format	Supported	-
4	Packet Types	Supported	-
4.1	Access-Request	Supported	-
4.2	Access-Accept	Supported	-
4.3	Access-Reject	Supported	-
4.4	Access-Challenge	Supported	-
5	Attributes	Supported	-
5.1	User-Name	Supported	-
5.2	User-Password	Supported	-
5.3	CHAP-Password	Supported	-
5.4	NAS-IP-Address	Supported	-
5.5	NAS-Port	Supported	-
5.6	Service-Type	Supported	-
5.7	Framed-Protocol	Supported	-
5.8	Framed-IP-Address	Supported	-
5.9	Framed-IP-Netmask	Supported	-
5.10	Framed-Routing	Supported	-
5.11	Filter-Id	Supported	-
5.12	Framed-MTU	Supported	-
5.13	Framed-Compression	Supported	-
5.14	Login-IP-Host	Supported	-
5.15	Login-Service	Supported	-
5.16	Login-TCP-Port	Supported	-
5.17	(unassigned)	Supported	-
5.18	Reply-Message	Supported	-
5.19	Callback-Number	Supported	-
5.20	Callback-Id	Supported	-
5.21	(unassigned)	Supported	-
5.22	Framed-Route	Supported	-
5.23	Framed-IPX-Network	Supported	-
5.24	State	Supported	-
5.25	Class	Supported	-
5.26	Vendor-Specific	Supported	-
5.27	Session-Timeout	Supported	-
5.28	Idle-Timeout	Supported	-
5.29	Termination-Action	Supported	-
5.30	Called-Station-Id	Supported	-
5.31	Calling-Station-Id	Supported	-
5.32	NAS-Identifier	Supported	-
5.33	Proxy-State	Supported	-
5.34	Login-LAT-Service	Supported	-
5.35	Login-LAT-Node	Supported	-
5.36	Login-LAT-Group	Supported	-
5.37	Framed-AppleTalk-Link	Supported	-
5.38	Framed-AppleTalk-Network	Supported	-
5.39	Framed-AppleTalk-Zone	Supported	-
5.40	CHAP-Challenge	Supported	-
5.41	NAS-Port-Type	Supported	-
5.42	Port-Limit	Supported	-
5.43	Login-LAT-Port	Supported	-
5.44	Table of Attributes	Supported	-
6	IANA Considerations	No requirement	-
6.1	Definition of Terms	No requirement	-
6.2	Recommended Registration Policies	No requirement	-
7	Examples	Supported	-
7.1	User Telnet to Specified Host	Supported	-
7.2	Framed User Authenticating with CHAP	Supported	-
7.3	User with Challenge-Response card	Not supported	-
8	Security Considerations	Not supported	-
9	Change Log	No requirement	-
10	References	No requirement	-
11	Acknowledgements	No requirement	-
12	Chair’s Address	No requirement	-
13	Authors’ Addresses	No requirement	-
14	Full Copyright Statement	No requirement	-

The following Table 1-2 provides a list of the compliance information for the RADIUS protocol sections in RFC-2869.

Table 1-2: RFC-2869 Section Compliance

Section Number	Section	Status	Notes
1	Introduction	Not applicable	-
1.1	Specification of Requirements	Not applicable	-
1.2	Terminology	Not applicable	-
2	Operation	Partially supported	-
2.1	RADIUS support for Interim Accounting Updates	Not supported	-
2.2	RADIUS support for Apple Remote Access Protocol	Not supported	-
2.3	RADIUS Support for Extensible Authentication Protocol (EAP)	Supported	-
2.3.1	Protocol Overview	Supported	-
2.3.2	Retransmission	Supported	-
2.3.3	Fragmentation	Not supported	-
2.3.4	Examples	Supported	-
2.3.5	Alternative Uses	Supported	-
3	Packet Format	Supported	-
4	Packet Types	Supported	-
5	Attributes	Partially supported	-
5.1	Acct-Input-Gigawords	Not supported	-
5.2	Acct-Output-Gigawords	Not supported	-
5.3	Event-Timestamp	Not supported	-
5.4	ARAP-Password	Not supported	-
5.5	ARAP-Features	Not supported	-
5.6	ARAP-Zone-Access	Not supported	-
5.7	ARAP-Security	Not supported	-
5.8	ARAP-Security-Data	Not supported	-
5.9	Password-Retry	Not supported	-
5.10	Prompt	Not supported	-
5.11	Connect-Info	Not supported	-
5.12	Configuration-Token	Not supported	-
5.13	EAP-Message	Supported	-
5.14	Message-Authenticator	Supported	-
5.15	ARAP-Challenge-Response	Not supported	-
5.16	Acct-Interim-Interval	Not supported	-
5.17	NAS-Port-Id	Supported	-
5.18	Framed-Pool	Not supported	-
5.19	Table of Attributes	Not supported	-
6	IANA Considerations	No requirement	-
7	Security Considerations	Supported	-
7.1	Message-Authenticator Security	Supported	-
7.2	EAP Security	Supported	-
7.2.1	Separation of EAP server and PPP authenticator	Not supported	-
7.2.2	Connection hijacking	Not supported	-
7.2.3	Man in the middle attacks	Not supported	-
7.2.4	Multiple databases	Not supported	-
7.2.5	Negotiation attacks	Not supported	-
8	References	No requirement	-
9	Acknowledgements	No requirement	-
10	Chair’s Address	No requirement	-
11	Authors’ Addresses	No requirement	-
12	Full Copyright Statement	No requirement	-

Access-Request AVPs

Here is a Table 1-3 with the compliance information for Access-Request attribute-value pairs (AVPs).

Table 1-3: Access-Request AVPs

RADIUS AVP	Status	Notes
User-Name	Supported	-
User-Password	Supported	-
CHAP-Password	Supported	-
CHAP-Challenge	Supported	-
NAS-IP-Address	Supported	-
NAS-Port	Supported	-
NAS-Port-Type	Supported	-
NAS-Identifier	Supported	-
Service-Type	Supported	-
Framed-Protocol	Supported	-
Framed-IP-Address	Supported	-
Framed-IP-Netmask	Supported	-
Framed-MTU	Supported	-
Framed-Compression	Supported	-
Login-IP-Host	Supported	-
Callback-Number	Supported	-
Called-Station-Id	Supported	-
Calling-Station-Id	Supported	-
State	Supported	-
Proxy-State	Supported	-
Login-LAT-Service	Supported	-
Login-LAT-Node	Supported	-
Login-LAT-Group	Supported	-
Login-LAT-Port	Supported	-
Vendor-Specific	Supported	-
EAP-Message	Supported	-
Message-Authenticator	Supported	-

Access-Accept AVPs

Below is the compliance information for Access-Accept AVPs.

Table 1-4: Access-Accept AVPs

RADIUS AVP	Status	Notes
User-Name	Supported	-
Service-Type	Supported	-
Framed-Protocol	Supported	-
Framed-IP-Address	Supported	-
Framed-IP-Netmask	Supported	-
Framed-Routing	Supported	-
Framed-Route	Supported	-
Framed-IPX-Network	Supported	-
Framed-AppleTalk-Link	Supported	-
Framed-AppleTalk-Network	Supported	-
Framed-AppleTalk-Zone	Supported	-
Filter-Id	Supported	-
Framed-MTU	Supported	-
Framed-Compression	Supported	-
Login-IP-Host	Supported	-
Login-Service	Supported	-
Login-TCP-Port	Supported	-
Reply-Message	Supported	-
Callback-Number	Supported	-
Callback-Id	Supported	-
Class	Supported	-
Session-Timeout	Supported	-
Idle-Timeout	Supported	-
Termination-Action	Supported	-
State	Supported	-
Proxy-State	Supported	-
Login-LAT-Service	Supported	-
Login-LAT-Node	Supported	-
Login-LAT-Group	Supported	-
Login-LAT-Port	Supported	-
Port-Limit	Supported	-
Vendor-Specific	Supported	-
Acct-Session-Id	Supported	-
EAP-Message	Supported	-
Message-Authenticator	Supported	-

Access-Reject AVPs

Table 1-5 has a list of the compliance information for Access-Reject AVPs.

Table 1-5: Access-Reject AVPs

RADIUS AVP	Status	Notes
User-Name	Supported	-
Reply-Message	Supported	-
Class	Supported	-
Proxy-State	Supported	-
Vendor-Specific	Supported	-
Acct-Session-Id	Supported	-
EAP-Message	Supported	-
Message-Authenticator	Supported	-

Access-Challenge AVPs

Table 1-6 contains the compliance information for Access-Challenge AVPs.

Table 1-6: Access-Challenge AVPs

RADIUS AVP	Status	Notes
Reply-Message	Supported	-
Session-Timeout	Supported	-
Idle-Timeout	Supported	-
State	Supported	-
Proxy-State	Supported	-
Vendor-Specific	Supported	-
EAP-Message	Supported	-
Message-Authenticator	Supported	-

RADIUS Accounting Protocol

This section provides details on how AAA Gateway maps the RADIUS accounting messages for the RADIUS protocol defined in RFC-2866.

Section Compliance

Below is a list of the compliance information for the RADIUS Accounting protocol sections in RFC-2866.

Table 2-1 RFC-2866 Section Compliance

Section Number	Section	Status	Notes
1	Introduction	Not applicable	-
1.1	Specification of Requirement	Not applicable	-
1.2	Terminology	Not applicable	-
2	Operation	Supported	-
2.1	Proxy	Not supported	-
3	Packet Format	Supported	-
4	Packet Types	Supported	-
4.1	Accounting-Request	Supported	-
4.2	Accounting-Response	Supported	-
5	Attributes	Supported	-
5.1	Acct-Status-Type	Supported	-
5.2	Acct-Delay-Time	Supported	-
5.3	Acct-Input-Octets	Supported	-
5.4	Acct-Output-Octets	Supported	-
5.5	Acct-Session-Id	Supported	-
5.6	Acct-Authentic	Supported	-
5.7	Acct-Session-Time	Supported	-
5.8	Acct-Input-Packets	Supported	-
5.9	Acct-Output-Packets	Supported	-
5.10	Acct-Terminate-Cause	Supported	-
5.11	Acct-Multi-Session-Id	Supported	-
5.12	Acct-Link-Count	Supported	-
5.13	Table of Attributes	Supported	-
6	IANA Considerations	Supported	-
7	Security Considerations	Supported	-
8	Change Log	Not applicable	-
9	References	No Requirement	-
10	Acknowledgements	No requirement	-

Accounting-Request AVPs

The following table contains the description of how ECE supports Accounting-Request attribute-value pairs (AVPs).

Table 2-2 Accounting-Request AVPs

RADIUS Accounting AVP	Status	Notes
User-Name	Supported	This is mandatory AVP.
NAS-IP-Address	Supported	This is mandatory AVP.
NAS-Identifier	Supported	This is mandatory AVP.
NAS-Port-Type	Supported	-
Class	Supported	-
Service-Type	Supported	-
Framed-Protocol	Supported	-
Framed-IP-Address	Supported	-
Framed-IP-Netmask	Supported	-
Framed-MTU	Supported	-
Framed-Compression	Supported	-
Login-IP-Host	Supported	-
Callback-Number	Supported	-
Called-Station-Id	Supported	-
Calling-Station-Id	Supported	-
Proxy-State	Supported	-
Login-LAT-Service	Supported	-
Login-LAT-Node	Supported	-
Login-LAT-Group	Supported	-
Login-LAT-Port	Supported	-
CHAP-Challenge	Supported	-
Acct-Status-Type	Supported	This is mandatory AVP.
Acct-Delay-Time	Supported	-
Acct-Input-Octets	Supported	-
Acct-Output-Octets	Supported	-
Acct-Session-Id	Supported	This is mandatory AVP.
Acct-Authentic	Supported	-
Acct-Session-Time	Supported	-
Acct-Input-Packets	Supported	-
Acct-Output-Packets	Supported	-
Acct-Terminate-Cause	Supported	-
Acct-Multi-Session-Id	Supported	-
Acct-Link-Count	Supported	-
Vendor-Specific	Supported	-

Accounting-Response AVPs

The Accounting-Response message does not have any AVPs.

RADIUS Disconnect Protocol

This section describes how AAA Gateway maps the RADIUS disconnect messages for the RADIUS protocol defined in RFC-3576.

Section Compliance

Below is the the compliance information for the RADIUS Disconnect protocol sections in RFC-3576.

Table 3-1 RFC-3576 Section Compliance

Section Number	Section	Status	Notes
1	Introduction	-	-
1.1	Applicability	-	-
1.2	Requirements Language	-	-
1.3	Terminology	-	-
2	Overview	-	-
2.1	Disconnect Messages (DM)	-	-
2.2	Change-of-Authorization Messages (CoA)	-	-
2.3	Packet Format	-	-
3	Attributes	-	-
3.1	Error-Cause	-	-
3.2	Table of Attributes	-	-
4	IANA Considerations	-	-
5	Security Considerations	-	-
5.1	Authorization Issues	-	-
5.2	Impersonation	-	-
5.3	IPsec Usage Guidelines	-	-
5.4	Replay Protection	-	-
6	Example Traces	-	-
7	References	-	-
7.1	Normative References	-	-
7.2	Informative References	-	-
8	Intellectual Property Statement	-	-
9	Acknowledgements	-	-
10	Author’s Addresses	-	-
11	Full Copyright Statement	-	-

Disconnect-Request AVPs

The following Table 3-2 lists the compliance information for Disconnect-Request attribute-value pairs (AVPs).

Table 3-2: Disconnect-Request AVPs

RADIUS AVP	Status	Notes
User-Name	Supported	-
User-Password	Supported	-
CHAP-Password	Supported	-
CHAP-Challenge	Supported	-
NAS-IP-Address	Supported	-
NAS-Port	Supported	-
NAS-Port-Type	Supported	-
NAS-Identifier	Supported	-
Service-Type	Supported	-
Framed-Protocol	Supported	-
Framed-IP-Address	Supported	-
Framed-IP-Netmask	Supported	-
Framed-MTU	Supported	-
Framed-Compression	Supported	-
Login-IP-Host	Supported	-
Callback-Number	Supported	-
Called-Station-Id	Supported	-
Calling-Station-Id	Supported	-
State	Supported	-
Proxy-State	Supported	-
Login-LAT-Service	Supported	-
Login-LAT-Node	Supported	-
Login-LAT-Group	Supported	-
Login-LAT-Port	Supported	-
Vendor-Specific	Supported	-
EAP-Message	Supported	-
Message-Authenticator	Supported	-

Disconnect-Response AVPs

The Disconnect-Response message have no AVPs.

Docs: 5G CHF

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Introduction
- How To Interpret The Status In The Compliance Sections
Charging Function - Charging Service
- Section Compliance
- Response Codes
Charging Function - Spending Limit Control Service
- Section Compliance
- Response Codes
Charging Function - Interactions with Network Repository Function (NRF)
- Section Compliance
CHF-CDR Format

Introduction

The 5G CHF includes Nchf interfaces to enable converged charging and spending limit control for policy management. Interactions with the Network Repository Function are also outlined here.

How To Interpret The Status In The Compliance Sections

The following table describes the meaning of the status in section compliance sections.

Status	Meaning
Supported	Application supports functionality. Application supports the attribute and is mapped to the charging function. The attribute is received in the request and used in the charging flows. This attribute is sent in the response as indicated by the specifications. Optionally, you can utilize this attribute for event storage and to inform charging decisions.
Supported with Extensions	Application supports functionality with extension. The application supports the attribute and can be optionally utilized to select a price. The attribute is received in the request and is not used in the out-of-the-box charging flow. The attribute may or may not be sent in the response. You have an option to leverage available extensions in the charging flow to achieve the intended functionality. You can also prefer to use this attribute for storing in the event, and for making charging decisions.
Not Supported	Application does not support the functionality or the attribute.
Not Applicable	The section is not applicable for the implementation.
Informational	This section serves solely for informational purposes.

Charging Function – Charging Service

Section Compliance

The table below contains the description of the section compliance of the 5G System Charging Service 3GPP TS 32.291 v16.5.1 (2020-09):

Table 1-1: 5G System Charging Service 3GPP TS 32.291 v16.5.1 (2020-09) Section Compliance

Section Number	Section	Status	Notes
1	Scope	Informational	-
2	References	Informational	-
3	Definitions, symbols and abbreviations	Informational	-
4	Overview	Supported	-
5	Services offered by CHF	Supported	-
5.1	Introduction	Supported	-
5.2	Nchf_ConvergedCharging service	Supported	-
5.2.1	Service description	Supported	-
5.2.2	Service operations	Supported	-
5.2.2.1	Introduction	Supported	-
5.2.2.2	Nchf_ConvergedCharging_Create Operation	Supported	-
5.2.2.3	Nchf_ConvergedCharging_Update Operation	Supported	-
5.2.2.4	Nchf_ConvergedCharging_Release Operation	Supported	-
5.2.2.5	Nchf_ConvergedCharging_Notify Operation	Supported	-
5.3	Nchf_OfflineOnlyCharging service	Supported	-
5.3.1	Service description	Supported	-
5.3.2	Service operations	Supported	-
5.3.2.1	Introduction	Supported	-
5.3.2.2	Nchf_OfflineOnlyCharging_Create Operation	Supported	-
5.3.2.3	Nchf_OfflineOnlyCharging_Update Operation	Supported	-
5.3.2.4	Nchf_OfflineOnlyCharging_Release Operation	Supported	-
6	API Definitions	Supported	-
6.1	Nchf_ConvergedCharging Service API	Supported	-
6.1.1	Introduction	Supported	-
6.1.2	Usage of HTTP	Supported	-
6.1.2.1	General	Supported	-
6.1.2.2	HTTP standard headers	Supported	-
6.1.2.2.1	General	Supported	-
6.1.2.2.2	Content type	Supported	-
6.1.2.3	HTTP custom headers	Supported	Only 3gpp-Sbi-Target-apiRoot header is supported among custom headers.
6.1.2.3.1	General	Supported	-
6.1.3	Resources	Supported	-
6.1.3.1	Overview	Supported	-
6.1.3.2	Resource: Charging Data	Supported	-
6.1.3.2.1	Description	Supported	-
6.1.3.2.2	Resource Definition	Supported	-
6.1.3.2.3	Resource Standard Methods	Supported	-
6.1.3.2.3.1	POST	Supported	ChargingDataRequest and ChargingDataResponse. The response includes one of the following codes: For success 201 (created). For failure ProblemDetails include - 400, 403, 404.
6.1.3.2.4	Resource Custom Operations	Not Applicable	-
6.1.3.3	Resource: Individual Charging Data	Supported	-
6.1.3.3.1	Description	Supported	-
6.1.3.3.2	Resource Definition	Supported	-
6.1.3.3.3	Resource Standard Methods	Not Applicable	-
6.1.3.3.4	Resource Custom Operations	Supported	-
6.1.3.3.4.1	Overview	Supported	-
6.1.3.3.4.2	Operation: update	Supported	-
6.1.3.3.4.2.1	Description	Supported	-
6.1.3.3.4.2.2	Operation Definition	Supported	ChargingDataRequest and ChargingDataResponse. The response includes one of the following codes: For success 200 (OK). For failure ProblemDetails include - 400, 403, 404.
6.1.3.3.4.3	release	Supported	-
6.1.3.3.4.3.1	Description	Supported	-
6.1.3.3.4.3.2	Operation Definition	Supported	ChargingDataRequest and ChargingDataResponse. For success the response will be 204 (No content). For failure ProblemDetails include - 404.
6.1.4	Custom Operations without associated resources	Not Applicable	-
6.1.5	Notifications	Supported	-
6.1.5.1	General	Supported	-
6.1.5.2	Event Notification	Supported	-
6.1.5.2.1	Description	Supported	-
6.1.5.2.2	Target URI	Supported	-
6.1.5.2.3	Standard Methods	Supported	-
6.1.5.2.3.1	POST	Supported	ChargingDataRequest and ChargingDataResponse. For success the response will be 204 (No content). For failure ProblemDetails include - 404.
6.1.6	Data Model	Supported	-
6.1.6.1	General	Supported	-
6.1.6.2	Structured data types	Supported	-
6.1.6.2.1	Common Data Type	Supported	-
6.1.6.2.1.1	Type ChargingDataRequest	Supported
	subscriberIdentifier	Supported with Extensions
	nfConsumerIdentification	Supported with Extensions
	invocationTimeStamp	Supported
	invocationSequenceNumber	Supported
	retransmissionIndicator	Supported with Extensions
	oneTimeEvent	Supported with Extensions
	oneTimeEventType	Supported with Extensions
	notifyUri	Supported with Extensions
	supportedFeatures	Supported
	serviceSpecificationInfo	Supported with Extensions
	multipleUnitUsage	Supported with Extensions
	triggers	Supported
6.1.6.2.1.2	Type ChargingDataResponse	Supported
	invocationTimeStamp	Supported
	invocationResult	Supported with Extensions
	invocationSequenceNumber	Supported
	sessionFailover	Supported
	supportedFeatures	Supported with Extensions
	multipleUnitInformation	Supported with Extensions
	triggers	Supported
6.1.6.2.1.3	Type ChargingNotifyRequest	Supported with Extensions
	notificationType	Supported with Extensions
	reauthorizatoinDetails	Supported with Extensions
6.1.6.2.1.4	Type NFIdentification	Supported with Extensions
	nodeFunctionality	Supported with Extensions
	nFName	Supported with Extensions
	nFIPv4Address	Supported with Extensions
	nfIPv6Address	Supported with Extensions
	nFFqdn	Supported with Extensions
	nFPLMNID	Supported with Extensions
6.1.6.2.1.5	Type MultipleUnitUsage	Supported
	ratingGroup	Supported
	requestedUnit	Supported
	usedUnitContainer	Supported
6.1.6.2.1.6	Type InvocationResult	Supported with Extensions
	error (ProblemDetails)	Supported with Extensions
	failureHandling	Supported with Extensions
6.1.6.2.1.7	Type Trigger	Supported	See 6.1.6.3.6 for supported Trigger types.
	triggerType	Supported with Extensions
	triggerCategory	Supported with Extensions
	timeLimit (DurationSec)	Supported with Extensions
	volumeLimit	Supported with Extensions
	volumeLimit64	Supported with Extensions
	maxNumberOfccc	Supported with Extensions
6.1.6.2.1.8	Type MultipleUnitInformation	Supported
	resultCode	Supported
	ratingGroup	Supported
	grantedUnit	Supported
	triggers	Supported
	validityTime (DurationSec)	Supported with Extensions
	quotaHandlingTime (DurationSec)	Supported
	finalUnitIndication	Supported
	timeQuotaThreshold	Supported
	volumeQuotaThreshold	Supported with Extensions
	unitQuotaThreshold	Supported with Extensions
6.1.6.2.1.9	Type RequestedUnit	Supported
	time	Supported
	totalVolume	Supported
	uplinkVolume	Supported
	downLinkVolume	Supported
	serviceSpecificUnits	Supported
6.1.6.2.1.10	Type UsedUnitContainer	Supported
	serviceId	Supported
	quotaManagementIndicator	Supported
	triggers	Supported
	triggerTimeStamp	Supported with Extensions
	time	Supported with Extensions
	totalVolume	Supported
	uplinkVolume	Supported
	downlinkVolume	Supported
	serviceSpecificUnits	Supported
	eventTimeStamps	Supported with Extensions
	localSequenceNumber	Supported with Extensions
6.1.6.2.1.11	Type GrantedUnit	Supported
	tariffTimeChange	Supported
	time	Supported
	totalVolume	Supported
	uplinkVolume	Supported
	downlinkVolume	Supported
	serviceSpecificUnits	Supported
6.1.6.2.1.12	Type FinalUnitIndication	Supported
	finalUnitAction	Supported
	restrictionFilterRule	Not Supported
	filterId	Not Supported
	redirectServer	Supported
6.1.6.2.1.13	Type RedirectServer	Supported
	redirectAddressType	Supported
	redirectServerAddress	Supported
6.1.6.2.1.14	Type ReauthorizationDetails	Supported
	service (serviceId)	Supported
	ratingGroup	Supported
	quotaManagementIndicator	Supported
6.1.6.2.1.15	Void	Not applicable
6.1.6.2.1.16	Type ChargingNotifyResponse	Not Supported
	invocationResult	Not Supported
6.1.6.2.2	5G Data Connectivity Specified Data Type	Supported	-
6.1.6.2.2.1	ChargingDataRequest	Supported	The out of the box charging flow does not process records for 5G roaming.
6.1.6.2.2.2	ChargingDataResponse	Supported with Extensions	The out of the box charging flow does not process records for 5G roaming.
6.1.6.2.2.3	MultipleUnitUsage	Supported with Extensions	-
6.1.6.2.2.4	MultipleUnitInformation	Supported with Extensions	-
6.1.6.2.2.5	UsedUnitContainer	Supported with Extensions	-
6.1.6.2.2.6	PDUSessionChargingInformation	Supported with Extensions	uetimeZone is used as the request time for the event.
6.1.6.2.2.7	UserInformation	Supported with Extensions	-
6.1.6.2.2.8	PDUSessionInformation	Supported with Extensions	-
6.1.6.2.2.9	PDUContainerInformation	Supported with Extensions	-
6.1.6.2.2.10	NetworkSlicingInfo	Supported with Extensions	-
6.1.6.2.2.11	PDUAddress	Supported with Extensions	-
6.1.6.2.2.12	ServingNetworkFunctionID	Supported with Extensions	-
6.1.6.2.2.13	RoamingQBCInformation	Supported with Extensions	-
6.1.6.2.2.14	MultipleQFIcontainer	Supported with Extensions	-
6.1.6.2.2.15	RoamingChargingProfile	Supported with Extensions	The out of the box charging flow does not process records for 5G roaming.
6.1.6.2.2.16	QFIContainerInformation	Supported with Extensions	All are supported only in request, not supported in response
6.1.6.2.2.17	RANSecondaryRATUsageReport	Supported with Extensions	-
6.1.6.2.2.18	QosFlowsUsageReport	Supported with Extensions	-
6.1.6.2.2.19	MAPDUSessionInformation	Supported with Extensions	-
6.1.6.2.3	SMS Specified Data Type	Supported with Extensions	-
6.1.6.2.3.1	ChargingDataRequest	Supported with Extensions	-
6.1.6.2.3.2	SMSChargingInformation	Supported with Extensions	-
6.1.6.2.3.3	OriginatorInfo	Supported with Extensions	-
6.1.6.2.3.4	RecipientInfo	Supported with Extensions	-
6.1.6.2.3.5	SMAddressInfo	Supported with Extensions	-
6.1.6.2.3.6	RecipientAddress	Supported with Extensions	-
6.1.6.2.3.7	MessageClass	Supported with Extensions	-
6.1.6.2.3.8	SMAddressDomain	Supported with Extensions	-
6.1.6.2.3.9	SMInterface	Supported with Extensions	-
6.1.6.2.4	5G connection and mobility Specified Data	Not Supported	-
6.1.6.2.4.1	ChargingDataRequest	Not Supported	-
6.1.6.2.4.2	ChargingDataResponse	Not Supported with Extensions	-
6.1.6.2.4.3	Type RegistrationChargingInformation	Not Supported
	registrationMessagetype	Not Supported
	userInformation	Not Supported
	userLocationinfo	Not Supported
	uetimeZone	Not Supported
	rATType	Not Supported
	5gMMCapability	Not Supported
	mICOModeIndication	Not Supported
	smsIndication	Not Supported
	taiList	Not Supported
	serviceAreaRestriction	Not Supported
	requestedNSSAI	Not Supported
	allowedNssai	Not Supported
	rejectedNSSAI	Not Supported
	-	Not Supported
6.1.6.2.4.4	Type N2ConnectionChargingInformation	Not Supported
	n2ConnectionMessageType	Not Supported
	userInformation	Not Supported
	userLocationinfo	Not Supported
	uetimeZone	Not Supported
	rATType	Not Supported
	amfUeNgapId	Not Supported
	ranUeNgapId	Not Supported
	ranNodeId	Not Supported
	restrictedRatList	Not Supported
	forbiddenAreaList	Not Supported
	serviceAreaRestriction	Not Supported
	restrictedCnList	Not Supported
	allowedNssai	Not Supported
	rrcEstCause	Not Supported
	-	Not Supported
6.1.6.2.4.5	Type LocationReportingChargingInformation	Not Supported
	locationReportingMessageType	Not Supported
	userInformation	Not Supported
	userLocation	Not Supported
	infouetimeZone	Not Supported
	presenceReportingAreaInformation	Not Supported
	rATType	Not Supported
	-	Not Supported
6.1.6.2.5	Exposure Function Northbound API Specified	Not Supported
	-	Not Supported
6.1.6.2.5.1	Type ChargingDataRequest	Not Supported

6.1.6.2.5.1a	Type ChargingDataResponse	Not Supported

6.1.6.2.5.2	Type NEFChargingInformation	Not Supported
	groupIdentifier	Not Supported
	aPIDirection	Not Supported
	aPITargetNetworkFunction	Not Supported
	aPIResultCode	Not Supported
	aPIName	Not Supported
	aPIReference	Not Supported
	aPIContent	Not Supported

6.1.6.2.6	Network Slice Management (NSM) Specified Data Type	Not Supported

6.1.6.2.6.1	Type ChargingDataRequest	Not Supported
	tenantIdentifier	Not Supported
	mnSConsumerIdentifier	Not Supported
	nSMChargingInformation	Not Supported

6.1.6.2.6.2	Type ChargingDataResponse	Not Supported

6.1.6.2.6.3	Type NSMChargingInformation	Not Supported
	managementOperation	Not Supported
	idNetworkSliceInstance	Not Supported
	listOfServiceProfileChargingInformation	Not Supported
	managementOperationStatus	Not Supported
	operationalState	Not Supported
	administrativeState	Not Supported

6.1.6.2.6.4	Type ServiceProfileChargingInformation	Not Supported
	serviceProfileIdentifier	Not Supported
	sNSSAIList	Not Supported
	latency	Not Supported
	availability	Not Supported
	resourceSharingLevel	Not Supported
	jitter	Not Supported
	reliability	Not Supported
	maxNumberofUEs	Not Supported
	coverageArea	Not Supported
	uEMobilityLevel	Not Supported
	delayToleranceIndicator	Not Supported
	dLThptPerSlice	Not Supported
	dLThptPerUE	Not Supported
	uLThptPerSlice	Not Supported
	uLThptPerUE	Not Supported
	maxNumberofPDUsessions	Not Supported
	kPIMonitoringList	Not Supported
	supportedAccessTechnology	Not Supported
	v2XCommunicationModeIndicator	Not Supported
	addServiceProfileChargingInfo	Not Supported

6.1.6.2.6.5	Type Throughput	Not Supported
	guaranteedThpt	Not Supported
	maximumThpt	Not Supported

6.1.6.2.7	NS performance and analytics Specified Data Type	Not Supported
6.1.6.2.7.1	Type ChargingDataRequest	Not Supported
	tenantIdentifier	Not Supported
	nSPAChargingInformation	Not Supported
6.1.6.2.7.2	Type ChargingDataResponse	Not Supported
6.1.6.2.7.3	Type UsedUnitContainer	Not Supported
	nSPAContainerInformation	Not Supported
6.1.6.2.7.4	Type NSPAChargingInformation	Not Supported
	singleNSSAI	Not Supported
6.1.6.2.7.5	Type NSPAContainerInformation	Not Supported
	latency	Not Supported
	throughput	Not Supported
	maximumPacketLossRate	Not Supported
	serviceExperienceStatisticsData	Not Supported
	theNumberOfPDUSessions	Not Supported
	theNumberOfRegisteredSubscribers	Not Supported
	loadLevel	Not Supported
6.1.6.3	Simple data types and enumerations	Supported
6.1.6.3.1	Introduction	Supported
6.1.6.3.2	Simple data types	Supported with Extensions
	Diagnostics	Supported with Extensions
	IPFilterRule	Supported with Extensions
	N2ConnectionMessageType	Supported with Extensions
	LocationReportingMessageType	Supported with Extensions
6.1.6.3.3	Enumeration: NotificationType	Supported
6.1.6.3.4	Enumeration: NodeFunctionality	Supported
6.1.6.3.5	Enumeration: ChargingCharacteristicsSelectionMode	Supported
6.1.6.3.6	Enumeration: TriggerType	Supported	FINAL, RAT_CHANGE, and TARIFF_TIME_CHANGE are supported. Other trigger types are supported with extensions.
6.1.6.3.7	Enumeration: FinalUnitAction	Supported
6.1.6.3.8	Enumeration: RedirectAddressType	Supported
6.1.6.3.9	Enumeration: TriggerCategory	Supported
6.1.6.3.10	Enumeration: QuotaManagementIndicator	Supported
6.1.6.3.11	Enumeration: FailureHandling	Supported
6.1.6.3.12	Enumeration: SessionFailover	Supported
6.1.6.3.13	Enumeration: 3GPPPSDataOffStatus	Supported
6.1.6.3.14	Enumeration: ResultCode	Supported
6.1.6.3.15	Enumeration: PartialRecordMethod	Supported
6.1.6.3.16	Enumeration: RoamerInOut	Supported
6.1.6.3.17	Void	Supported
6.1.6.3.18	Enumeration: SMMessageType	Supported
6.1.6.3.19	Enumeration: SMPriority	Supported
6.1.6.3.20	Enumeration: DeliveryReportRequested	Supported
6.1.6.3.21	Enumeration: InterfaceType	Supported
6.1.6.3.22	Enumeration: ClassIdentifier	Supported
6.1.6.3.23	Enumeration: SMAddressType	Supported
6.1.6.3.24	Enumeration: SMAddresseeType	Supported
6.1.6.3.25	Enumeration: SMServiceType	Supported
6.1.6.3.26	Enumeration: ReplyPathRequested	Supported
6.1.6.3.27	Enumeration: DnnSelectionMode	Supported
6.1.6.3.28	Enumeration: EventType	Supported
6.1.6.3.29	Enumeration: MICOModeIndication	Supported
6.1.6.3.30	Enumeration: RegistrationMessageType	Supported
6.1.6.3.31	Enumeration: SmsIndication	Supported
6.1.6.3.32	Enumeration: APIDirection	Supported
6.1.6.3.33	Enumeration: ManagementOperation	Supported
6.1.6.3.34	Enumeration: ManagementOperationStatus	Supported
6.1.6.4	Data types describing alternative data types or combinations of data types	Not Applicable
6.1.6.5	Binary data	Not Applicable
6.1.7	Error handling	Supported
6.1.7.1	General	Supported
6.1.7.2	Protocol Errors	Not Applicable
6.1.7.3	Application errors	Supported
6.1.8	Feature negotiation	Not Supported
6.2	Nchf_OfflineOnlyCharging Service API	Supported
6.2.1	Introduction	Supported
6.2.2	Usage of HTTP	Supported
6.2.3	Resources	Supported
6.2.3.1	Overview	Supported
6.2.3.2	Resource: Charging Data	Supported
6.2.3.2.1	Description	Supported
6.2.3.2.2	Resource Definition	Supported
6.2.3.2.3	Resource Standard Methods	Supported
6.2.3.2.3.1	POST	Supported	ChargingDataRequest and ChargingDataResponse. The response includes one of the following codes: For success 201 (created). For failure ProblemDetails include - 400, 403, and 404.
6.2.3.2.4	Resource Custom Operations	Not Applicable
6.2.3.3	Resource: Individual Offline Only Charging Data	Supported
6.2.3.3.1	Description	Supported
6.2.3.3.2	Resource Definition	Supported
6.2.3.3.3	Resource Standard Methods	Not Applicable
6.2.3.3.4	Resource Custom Operations	Supported
6.2.3.3.4.1	Overview	Supported
6.2.3.3.4.2	Operation: update	Supported
6.2.3.3.4.2.1	Description	Supported
6.2.3.3.4.2.2	Operation Definition	Supported	ChargingDataRequest and ChargingDataResponse. The response includes one of the following codes: For success 200 (OK). For failure ProblemDetails include - 400, 403, and 404.
6.2.3.3.4.3	Operation: release	Supported
6.2.3.3.4.3.1	Description	Supported
6.2.3.3.4.3.2	Operation Definition	Supported	ChargingDataRequest and ChargingDataResponse. For success the response will be 204 (No content). For failure ProblemDetails include - 404.
6.2.4	Custom Operations without associated resources	Not Applicable
6.2.5	Data Model	Supported
6.2.5.1	General	Supported
6.2.5.2	Structured data types	Supported
6.2.5.2.1	Common Data Type	Supported
6.2.5.2.1.1	Type ChargingDataRequest	Supported
	subscriberIdentifier	Supported
	nfConsumerIdentification	Supported
	invocationTimeStamp	Supported with Extensions
	invocationSequenceNumber	Supported
	serviceSpecificationInformation	Supported
	multipleUnitUsage	Supported with Extensions
	triggers	Supported with Extensions	See 6.2.5.3.5 for supported Trigger types.
6.2.5.2.1.2	Type ChargingDataResponse	Supported
	invocationTimeStamp	Supported
	invocationResult	Supported
	invocationSequenceNumber	Supported
	sessionFailover	Supported
	triggers	Supported with Extensions
6.2.5.2.1.3	Type MultipleUnitUsage	Supported
	ratingGroup	Supported
	usedUnitContainer	Supported
6.2.5.2.1.4	Type UsedUnitContainer	Supported
	serviceId	Supported
	triggers	Supported
	triggerTimeStamp	Supported
	time	Supported
	totalVolume	Supported with Extensions
	uplinkVolume	Supported
	downlinkVolume	Supported
	serviceSpecificUnits	Supported
	eventTimeStamps	Supported with Extensions
	localSequenceNumber	Supported with Extensions
6.2.5.2.1.5	Type Trigger	Supported with Extensions
	triggerType	Supported with Extensions
	triggerCategory	Supported with Extensions
	timeLimit (DurationSec)	Supported with Extensions
	volumeLimit64	Supported with Extensions
	eventLimit	Supported with Extensions
	maxNumberOfccc	Supported with Extensions
6.2.5.2.2	5G Data Connectivity Specified Data Type	Supported
6.2.5.2.2.1	Type ChargingDataRequest	-	Same as 6.1.6.2.2.1
6.2.5.2.2.2	Type ChargingDataResponse	-	Same as 6.2.5.2.1.2
6.2.5.2.2.3	Type MultipleUnitUsage	-	Same as 6.2.5.2.1.3
6.2.5.2.2.4	Type UsedUnitContainer	-	Same as 6.2.5.2.1.4
6.2.5.2.2.5	Type PDUSessionChargingInformation	-	Same as 6.1.6.2.2.6
6.2.5.2.2.6	Type UserInformation	-	Same as 6.1.6.2.2.7
6.2.5.2.2.7	Type PDUSessionInformation	-	Same as 6.1.6.2.2.8
6.2.5.2.2.8	Type PDUContainerInformation	-	Same as 6.1.6.2.2.9
6.2.5.2.2.9	Type NetworkSlicingInfo	-	Same as 6.1.6.2.2.10
6.2.5.2.2.10	Type PDUAddress	-	Same as 6.1.6.2.2.11
6.2.5.2.2.11	Type ServingNetworkFunctionID	-	Same as 6.1.6.2.2.12
6.2.5.2.2.12	Type RoamingQBCInformation	-	Same as 6.1.6.2.2.13
6.2.5.2.2.13	Type MultipleQFIcontainer	-	Same as 6.1.6.2.2.14
6.2.5.2.2.14	Type RoamingChargingProfile	-	Same as 6.1.6.2.2.15
6.2.5.2.2.15	Type QFIContainerInformation	-	Same as 6.1.6.2.2.16
6.2.5.2.2.16	Type RANSecondaryRATUsageReport	-	Same as 6.1.6.2.2.17
6.2.5.2.2.17	Type QosFlowsUsageReport	-	Same as 6.1.6.2.2.18
6.2.5.3	Simple data types and enumerations	Supported
6.2.5.3.1	Introduction	Supported
6.2.5.3.2	Simple data types	-	Same as 6.1.6.3.2
6.2.5.3.3	Enumeration: ChargingCharacteristicsSelectionMode	-	Same as 6.1.6.3.5
6.2.5.3.4	Enumeration: NodeFunctionality	Supported
6.2.5.3.5	Enumeration: TriggerType	Supported	FINAL, RAT_CHANGE and TARIFF_TIME_CHANGE are supported. Other trigger types are supported with extensions.
6.2.5.3.6	Enumeration: ResultCode	Supported
6.2.5.3.7	Enumeration: 3GPPPSDataOffStatus	-	Same as 6.1.6.3.13
6.2.5.3.8	Enumeration: PartialRecordMethod	-	Same as 6.1.6.3.15
6.2.5.3.9	Enumeration: RoamerInOut	-	Same as 6.1.6.3.16
6.2.5.3.10	Enumeration: SubscriberIdentityType	-	Same as 6.1.6.3.17
6.2.6	Error handling	Supported
6.2.6.1	General	Supported
6.2.6.2	Protocol Errors	Not Applicable
6.2.6.3	Application errors	Supported
6.2.7	Feature negotiation	Not Supported
7	Bindings of CDR field, Information Element and Resource Attribute	Supported
7.0	General	Supported
7.1	Bindings of common CDR field, Information Element and Resource Attribute	Supported
7.2	Bindings for 5G data connectivity	Supported
7.3	Bindings for SMS charging	Not Supported
7.4	Bindings for 5G connection and mobility	Not Supported
7.5	Bindings for Exposure Function Northbound API charging	Not Supported
7.6	Bindings for NS performance and Analytics charging	Not Supported
8.0	Security	Not Supported	OAuth2 is not supported.

Response Codes

Table 1-2: Response Codes

Response codes	Description
201 Created (Create)	The creation of a Charging Data resource is confirmed, and a representation of that resource is returned. The Charging Data resource is created and returned successfully. The representation of created resource is identified via Location header field in the 201 response.
200 OK (Updates)	The modification of a Charging Data resource is confirmed, and a representation of that resource is returned. The Charging Data resource which is modified and returned successfully.
204 No Content (Release)	The Charging Data resource matching the ChargingDataRef is modified and then released.
400 Bad Request	CHARGING_FAILED: The HTTP request is rejected because the set of session or subscriber information needed by the CHF for charging or CDR creation is incomplete or erroneous or not available (for example, Rating Group, subscriber information). RE_AUTHORIZATION_FAILED: The HTTP request is rejected because the set of information needed by the NF Consumer (CTF) to report the usage is incomplete or erroneous or not available.
403 Forbidden	CHARGING_NOT_APPLICABLE: The HTTP request is rejected by the CHF since it has been determined that the service can be granted to the end user without any charging or CDR creation. END_USER REQUEST_DENIED: The HTTP request is denied by the CHF due to restrictions or limitations related to the end-user. QUOTA_LIMIT_REACHED: The HTTP request denied by the CHF because the end user’s account could not cover the requested service. If the request contained used units they are deducted, if applicable. END_USER_REQUEST_REJECTED: The HTTP request rejected by the CHF due to end-user restrictions or limitations.
404 Not Found	USER_UNKNOWN: The HTTP request is rejected because the end user specified in the request cannot be served by the CHF.
500 Internal Server Error	Common Application Error

Charging Function – Spending Limit Control Service

Section Compliance

The table provided below outlines the compliance of sections within the 5G System Charging Service as per 3GPP TS 29.594 v16.3.0 (2020-09).

Table 2-1: 5G System Charging Service 3GPP TS 29.594 v16.3.0 (2020-09) Section Compliance

Section Number	Section	Status	Notes
1	Scope	Informational	-
2	References	Informational	-
3	Definitions and abbreviations	Informational	-
4	Nchf_SpendingLimitControl Service	Supported	-
4.1	Service Description	Supported	-
4.1.1	Overview	Supported	-
4.1.2	Service Architecture	Supported	-
4.1.3	Network Functions	Supported	-
4.1.3.1	Charging Function (CHF)	Supported	-
4.1.3.2	NF Service Consumers	Supported	-
4.2	Service Operations	Supported	-
4.2.1	Introduction	Supported	-
4.2.2	Nchf_SpendingLimitControl_Subscribe service operation	Supported	-
4.2.2.1	General	Supported	-
4.2.2.2	Initial spending limit retrieval	Supported	-
4.2.2.3	Intermediate spending limit report retrieval	Supported	-
4.2.3	Nchf_SpendingLimitControl_Unsubscribe service operation	Supported	-
4.2.3.1	General	Supported	-
4.2.3.2	Unsubscribe from spending limit reporting	Supported	-
4.2.4	Nchf_SpendingLimitControl_Notify service operation	Supported	-
4.2.4.1	General	Supported	-
4.2.4.2	Spending limit report	Supported	-
4.2.4.3	Subscription termination request by CHF	Not Supported	-
5	Nchf_SpendingLimitControl Service API	Supported	-
5.1	Introduction	Supported	-
5.2	Usage of HTTP	Supported	-
5.2.1	General	Supported	-
5.2.2	HTTP standard headers	Supported	-
5.2.2.1	General	Supported	-
5.2.2.2	Content type	Supported	-
5.2.3	HTTP custom headers	Supported	Only 3gpp-Sbi-Target-apiRoot header is supported among custom headers.
5.3	Resources	Supported	-
5.3.1	Resource Structure	Supported	-
5.3.2	Resource: Spending Limit Retrieval Subscriptions (Collection)	Supported	-
5.3.2.1	Description	Supported	-
5.3.2.2	Resource Definition	Supported	-
5.3.2.3	Resource Standard Methods	Supported	-
5.3.2.3.1	POST	Supported	POST request with SpendingLimitContext to create a new individual spending limit retrieval subscription. POST Response to contain SpendingLimitStatus as 201 (Created), ProblemDetails with 400 (Bad Request).
5.3.2.4	Resource Custom Operations	Not Applicable	-
5.3.3	Resource: Individual Spending Limit Retrieval Subscription (Document)	Supported	-
5.3.3.1	Description	Supported	-
5.3.3.2	Resource definition	Supported	-
5.3.3.3	Resource Standard Methods	Supported	-
5.3.3.3.1	PUT	Supported	PUT request with SpendingLimitContext to modify the existing individual spending limit retrieval subscription. POST Response to contain SpendingLimitStatus as 200 (OK), ProblemDetails with 400 (Bad Request).
5.3.3.3.2	DELETE	Supported	DELETE request. DELETE Response to contain 204 (No Content). Successful case: The individual spending limit subscription matching the subscriptionId was deleted.
5.4	Customer Operations without associated resources	Not Applicable	-
5.5	Notifications	Supported	-
5.5.1	General	Supported	Terminate is not supported
5.5.2	Spending limit notification	Supported	-
5.5.2.1	Description	Supported	-
5.5.2.2	Target URI	Supported	-
5.5.2.3	Standard Methods	Supported	-
5.5.2.3.1	POST	Supported	POST request with SpendingLimitStatus for the policy counters. POST Response to contain 204 (no Content) and the receipt of the notification is acknowledged.
5.5.3	Subscription Termination	Not Supported	-
5.5.3.1	Description	Supported	-
5.5.3.2	Target URI	Supported	-
5.5.3.3	Standard Methods	Supported	-
5.5.3.3.1	POST	Supported	POST request with SubscriptionTerminationInfo for deletion of a resource. POST Response to contain 204 (no Content) and the receipt of the notification is acknowledged.
5.6	Data Model	Supported	-
5.6.1	General	Supported	-
5.6.2	Structured data types	Supported	-
5.6.2.1	Introduction	Supported	-
5.6.2.2	Type SpendingLimitContext	Supported	-
5.6.2.3	Type SpendingLimitStatus	Supported	-
5.6.2.4	Type PolicyCounterInfo	Supported	-
5.6.2.5	Type PendingPolicyCounterStatus	Supported	-
5.6.2.6	Type SubscriptionTerminationInfo	Not Supported	-
5.6.3	Simple data types and enumerations	Supported	-
5.6.3.1	Introduction	Supported	-
5.6.3.2	Simple data types	Supported	-
5.6.3.3	Enumeration: TerminationCause	Not Supported	-
5.7	Error handling	Supported	-
5.7.1	General	Supported	-
5.7.2	Protocol Errors	Not Applicable	-
5.7.3	Application Errors	Supported	-
5.8	Feature negotiation	Not Supported	-
5.9	Security	Not Supported	OAuth2 is not supported.

Response Codes

Table 2-2 Response Codes

Response codes	Description
201 Created	SUCCESS: The spending limit subscription was created, and spending limit reports are provided.
200 OK	The individual spending limit subscription was modified, and spending limit reports are provided.
204 No Content	Please see individual operations
400 Bad Request	USER_UNKNOWN: The subscriber specified in the request is not known at the CHF and the subscription cannot be created. NO_AVAILABLE_POLICY_COUNTERS: There are no policy counters available for the subscriber at the CHF
500 Internal Server Error	Common Application Error

Charging Function – Interactions with Network Repository Function (NRF)

Section Compliance

The table below provides a description of the services supported by CHF as a consumer Network Function for its interaction with NRF, in accordance with the 5G System Network Function Repository Services in 3GPP TS 29.510 v16.5.0 (2020-09).

Table 3-1: Services Supported by CHF as a Consumer Network Function

Section Number	Section	Status	Notes
5	Services Offered by the NRF	Supported
5.1	Introduction	Supported	Only NFManagement Service with operations NFRegister, NFUpdate, NFDeregister, and NFListRetrieval are supported.
5.2	Nnrf_NFManagement Service	Supported
5.2.1	Service Description	Supported
5.2.2	Service Operations	Supported
5.2.2.1	Introduction	Supported
5.2.2.2	NFRegister	Supported
5.2.2.2.1	General	Supported
5.2.2.2.2	NF (other than NRF) registration to NRF	Supported
5.2.2.3	NFUpdate	Supported
5.2.2.3.1	General	Supported
5.2.2.3.2	NF Heart-Beat	Supported
5.2.2.4	NFDeregister	Supported
5.2.2.4.1	General	Supported
5.2.2.5	NFStatusSubscribe	Not Supported
5.2.2.6	NFStatusNotify	Not Supported
5.2.2.7	NFStatusUnsubscribe	Not Supported
5.2.2.8	NFListRetrieval	Supported
5.2.2.8.1	General	Supported
5.2.2.9	NFProfileRetrieval	Not Supported
5.2.2.9.1	General	Not Supported

CHF-CDR Format

The table below outlines the compliance status of the fields within the 3GPP Charging Function Call Detail Record (CHF-CDR) from the 3GPP TS 32.298 version 16.5.0 specification.

Table 4-1: CHF-CDR Format

Field	Status
Record Type	Supported
Recording Network Function ID	Not supported
Charging Session Identifier	Supported
Subscriber Identifier	Supported
NF Consumer Information	Supported
NF Functionality	Supported
NF Name	Supported
NF Address	Supported
NF PLMN ID	Supported
Triggers	Supported
SMF Triggers	Supported
List of Multiple Unit Usage	Supported
Rating Group	Supported
Used Unit Container	Supported
Service Identifier	Supported
Quota management Indicator	Supported
Local Sequence Number	Supported
Time	Supported
Uplink Volume	Supported
Downlink Volume	Supported
Total Volume	Supported
Service Specific Units	Supported
Event Time Stamp	Supported
Rating Indicator	Supported
Triggers	Supported
SMF Triggers	Supported
Trigger Time Stamp	Supported
PDU Container Information	Supported
UPF ID	Supported
Record Opening Time	Supported
Duration	Supported
Record Sequence Number	Supported
Cause for Record Closing	Supported
Local Record Sequence Number	Supported
Record Extensions	Not supported
Service Specification Information	Supported
PDU Session Charging Information	Supported
Roaming QBC Information	Supported
SMS Charging Information	Supported
Registration Charging Information	Not supported
N2 connection charging Information	Not supported
Location reporting charging Information	Not supported