Preface

This guide serves as a protocol implementation compliance statement (PICS) for Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE) HTTP/2 Gateway for 5G. 5G CHF supports Nchf interfaces for converged charging and spending limit control for policy. Interactions with Network Repository Function is also listed in this document.

Audience

This guide is intended for system administrators, product integrators, and developers. Readers must be familiar with the following:

• Elastic Charging Engine

• 5G Service based Network Function architecture

• 5G Charging Function interfaces

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Diversity and Inclusion

Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.

How to Read the Status in Section Compliance Sections

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

If the status says	It means
Supported	Application supports functionality. Application supports the attribute and is mapped to ECE 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. You can optionally leverage this attribute for storing in the event, and to make charging decisions.
Supported with Extensions	Application supports functionality with extension. Application supports the attribute and may be leveraged optionally for selecting 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 may optionally leverage available extensions in the charging flow to achieve the intended functionality. You can optionally leverage this attribute for storing in the event, and for making charging decisions.
Not Supported	Application does not support the functionality. Application does not support the attribute.
Not Applicable	The section is not applicable for the implementation.
Informational	This section is for informational purpose only in the specifications document.