1 Introduction
This document provides information on how to configure the Cloud Native Core Policy services and managed objects using REST API.
Overview
Oracle Communications Cloud Native Core Policy (CNC Policy) solution provides a standard policy design experience and ultimately consistent end-user experience. The Converged policy solution supports both 4G and 5G networks. In addition, the overlap in functionality between PCF and PCRF (e.g., need for a policy engine, policy design, Rx, similarity between Sy and Nchf_SpendingLimitControl, etc.), enables us to build micro-services that can be used to provide PCRF and PCF functionality. Even though it is a unified policy solution, you can still deploy the PCF and PCRF entirely independently.
The CNC Policy is a functional element for policy control decision and flows based charging control functionalities. The CNC Policy provides the following functions:
- Policy rules for application and service data flow detection, gating, QoS, and flow based charging to the Session Management Function (SMF)
- Access and Mobility Management related policies to the Access and Mobility Management Function (AMF)
- Provide UE Route Selection Policies (URSP) rules to UE via AMF
- Accesses subscription information relevant for policy decisions in a Unified Data Repository (UDR)
- Provides network control regarding the service data flow detection, gating, QoS and flow based charging towards the Policy and Charging Enforcement Function (PCEF).
- Receives session and media related information from the AF and informs AF of traffic plane events.
- Provisions PCC Rules to the PCEF via the Gx reference point.
- Session Management Service
- Access and Mobility Service
- Policy Authorization Service
- User Equipment (UE) Policy Service
- PCRF Core Service
Acronyms and Terminology
The following table provides information about the acronyms and the terminology used in the document.
Table 1-1 Acronyms and Terminology
Acronym | Definition |
---|---|
AMF | Access and Mobility Management Function |
BSF | Binding Support Function |
CHF | Charging Function |
CM | Configuration Management |
CUSTOMER_REPO | Docker registry address including the port number, if the docker registry has an associated port. |
IMAGE_TAG |
Image tag from release tar file. You can use any tag number. However, make sure that you use that specific tag number while pushing docker image to the docker registry. |
MCC | Mobile Country code |
METALLB_ADDRESS_POOL | Address pool which configured on metallb to provide external IPs . |
MNC | Mobile Network code |
NRF | Network Repository Function |
PCF | Policy Control Function |
CNPCRF | Cloud Native Policy and Charging Rules Function |
SAN | Storage Area Network |
SMF | Session Management Function |
UDR | Unified Data Repository |
References
You can refer to the following documents for information.
- Oracle Communications Cloud Native Policy Control Function Installation Guide
- https://developers.google.com/blockly
- 3GPP Technical Specification 29.512 v15.3.0, Session Management Policy Control Service, Stage 3, Release 15
- 3GPP Technical Specification 29.514 v15.3.0, Policy Authorization Service, Stage 3, Release 15
- 3GPP Technical Specification 29.507 v15.3.0, Access and Mobility Policy Control Service, Stage 3, Release 15
- 3GPP Technical Specification 29.525 v15.5.1, UE Policy Control Service, Stage 3, Release 15
- 3GPP Technical Specification 29.518 v15.5.1, Access and Mobility Management Services, Stage 3, Release 15