Feature Descriptions

Binding Support Function (BSF)

BSF 1.10.1 has been updated with the following enhancement:

Compatibility with OCCNE 1.9.1
BSF is compatible with OCCNE 1.9.1. For more information about OCCNE 1.9.1, see Oracle Communications Cloud Native Environment Installation Guide.

Binding Support Function (BSF) 1.10.0 is updated with the following enhancements:

Diameter Gateway Pod Congestion Control: BSF is enhanced with a congestion control mechanism for Diameter Gateway at pod level. With this new feature, configurations can be done through CNC Console or REST API to determine the congestion state of a pod and trigger congestion control. For more information, see "Diameter Gateway Pod Congestion Control" in Oracle Communications Cloud Native Core Binding Support Function User Guide.
SBI Error Codes: BSF is designed to handle Protocol, Application, and a few other additional defined errors for different scenarios. When BSF encounters error in processing a request, it sends error codes in the response message to the request. With this enhanced functionality, BSF allows users to configure error codes by adding customized values, for a defined condition, for the following fields:
- Error Description
- HTTP Status Code
- Application Error Code
For more information, see "SBI Error Codes" in Oracle Communications Cloud Native Core Binding Support Function User Guide.
Bulk Export: BSF is enhanced to support bulk export of BSF Managed Objects (MOs) and their dependencies using CNC Console. For more information on the enhancements on CNC Console for this feature, see "Configuring BSF using CNC Console" in Oracle Communications Cloud Native Core Binding Support Function User Guide.

Cloud Native Core Console (CNC Console)

Cloud Native Core Console (CNC Console) 1.8.1 has been updated with the following enhancement:

CNE 1.9.0 Metrics and Alerts Support: CNC Console Metrics, CNC Console KPIs, and CNC Console Alerts are updated to support CNE 1.9.0. For more information, see CNC Console Metrics, CNC Console KPIs, and CNC Console Alerts sections in Oracle Communications Cloud Native Core Console User Guide.
CNCC IAM Keycloak Upgraded from 10.0.2 to 15.0.2: The CNCC IAM Keycloak version is upgraded from 10.0.2 to 15.0.2. For more information, see Setting up CNC Console IAM section in Oracle Communications Cloud Native Core Console User Guide.

Cloud Native Core Console (CNC Console) 1.8.0 has been updated with the following enhancements:

CNC Console Multi–Cluster deployment support: In multi-cluster deployment, a single CNC Console can manage NF instances that access different Kubernetes clusters. The multi-cluster deployment provides the selection of the particular cluster at the top level of the CNC Console GUI. For more information, see Oracle Communications Cloud Native Core Console Installation and Upgrade Guide and Oracle Communications Cloud Native Core Console User Guide.

SEPP-CNC Console Integration: SEPP is integrated with CNC Console. The integration allows users to configure SEPP using the CNC Console. For more information, see Oracle Communications Cloud Native Core Console User Guide.

Cloud Native Diameter Routing Agent (CnDRA)

There are no new features or updates implemented in CNC 2.4.0 release.

Cloud Native Environment (CNE)

Oracle Communications Cloud Native Environment (OC-CNE) 1.9.0 has been updated with the following enhancements:

HA Load Balancing for vCNE: Redundant load balancers are now deployed for each external network, working as an active or standby pair. When the active load balancer fails, CNE detects the failure and automatically activate the standby load balancer. For more information, see Oracle Communications Cloud Native EnvironmentInstallation Guide and Oracle Communications Cloud Native Environment Upgrade Guide.
HA Prometheus: OC-CNE supports the deployment of redundant Prometheus instances. Each Prometheus collects metrics from all 5G NFs and OC-CNE common services. This redundant data collection prevents against gaps in metrics data if one of the redundant Prometheus instances fails, and during maintenance operations. For more information, see Oracle Communications Cloud Native Environment Installation Guide and Oracle Communications Cloud Native Environment Upgrade Guide.
Customer PKI Integration with Platform Service Mesh: The OCCNE platform service mesh can now use certificates from the customer's certificate authority (CA) when generating X.509 certificates for use in mTLS. The Intermediate CA issuer, where the customer generates a certificate at their CA and delivers it to OC-CNE for use as an intermediate CA, is the only supported issuer type in this release. For more information, see Oracle Communications Cloud Native Environment Installation Guide and Oracle Communications Cloud Native Environment Upgrade Guide.
Support for DB Tier 4-Site Replication: The cnDBTier is enhanced to support replication of the data stored in DB Tier to as many as 3 additional sites. Hence, it supports 4-Site, 3-Site, and 2-Site replication to ensure better service availability. For more information, see Oracle Communications Cloud Native Core DBTier User's Guide.
DBTier support for Non-georeplication SQL Nodes: The cnDBTier supports a separate statefulset of non-georeplication SQL nodes that is not part of georeplication configuration. The cnDBTier consists of two set of SQL nodes one which is configured for georeplication and the other to handle application traffic. The applications that utilize the MySQL connectivity service to connect to the MySQL NDB cluster will be using the non georeplication SQL nodes.
DBTier supports MySQL version 8.0.24: The cnDBTier supports Oracle MySQL Cluster Database version 8.0.24.

CNC NF Data Collector

There are no new features or updates implemented in CNC 2.4.0 release.

Cloud Native Core Policy (CNC Policy)

CNC Policy 1.14.1

CNC Policy 1.14.1 has been updated with the following enhancement:

Compatibility with OCCNE 1.9.1
CNC Policy is compatible with OCCNE 1.9.1. For more information about OCCNE 1.9.1, see Oracle Communications Cloud Native Environment Installation Guide.

CNC Policy 1.14.0

Oracle Communications Cloud Native Core Policy (CNC Policy) 1.14.0 has been updated with the following enhancements:

Support for 3GPP NF Sets and Binding Headers: CNC Policy supports the 3GPP NF Sets and Binding Headers in Direct and Indirect communication. For more information, see "Support for 3GPP NF Sets and Binding Headers" in Oracle Communications Cloud Native Core Policy User Guide.
Four-Site Georedundancy: CNC Policy is enhanced to support the four-site Geographical Redundant (Georedundant) deployment. It offers, four-site, three-site, and two-site georedundancy to ensure service availability when one of the Policy sites is down. For more information, see "Georedundancy Support" in Oracle Communications Cloud Native Core Policy User Guide.
Diameter Gateway Pod Congestion Control: CNC Policy is enhanced with a congestion control mechanism for Diameter Gateway at pod level. With this new feature, configurations can be done through CNC Console or REST API to determine the congestion state of a pod and trigger congestion control. For more information, see "Diameter Gateway Pod Congestion Control" in Oracle Communications Cloud Native Core Policy User Guide.
Topology Hiding for Diameter Gateway: CNC Policy provides support for topology hiding for diameter gateway. For more information, see "Topology Hiding for Diameter Gateway" in Oracle Communications Cloud Native Core Policy User Guide.
Enhancements in Policy Conditions and Actions: The Policy conditions and actions have been updated in PCRF project. For more information, see Oracle Communications Cloud Native Core Policy Design Guide.

Inter-Working Function (IWF)

There are no new features or updates implemented in CNC 2.4.0 release.

Service Communication Proxy (SCP)

SCP 1.14.0 has been updated with the following enhancements:

Multiple SCP Deployment in the Same Kubernetes Cluster
This feature allows you to deploy multiple SCP instances in the same Kubernetes cluster. Each SCP instance is deployed in a different namespace and is independent of each other. These SCP instances can use the same cnDBTier with a unique database name or a dedicated cnDBTier during the installation. For more information about this feature, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
Support for SCP Triplet Deployment
Using the Triplet Deployment model, you can configure three SCP instances as mates for georedundancy. Each SCP instance in a triplet is configured to manage the overall traffic expected for the triplet so that when two SCP instances are unavailable, the single SCP instance can manage the overall traffic. For more information about this feature, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
Support for SCP Upgrade and Rollback
SCP can be upgraded to a new version and rolled back to a previous supported version as described in Oracle Communications Cloud Native Core Service Communication Proxy Installation and Upgrade Guide.
Support for Disaster Recovery
SCP deployment and database can be recovered using the disaster recovery tasks. For more information, see Oracle Communications Cloud Native Core Service Communication Proxy Disaster Recovery Guide.
Support for scp-worker Large Profile
SCP supports the scp-worker service configuration with large profile. For more information, see the "Resource Requirements" in Oracle Communications Cloud Native Core Service Communication Proxy Installation and Upgrade Guide.
Multipart Message Support
The multipart message support is enable in SCP. For more information, see 3GPP Specifications.

Security Edge Protection Proxy (SEPP)

Security Edge Protection Proxy (SEPP) 1.6.x has been updated with the following enhancements:

Automated Test Suite (ATS) Integration and Enhancement:
SEPP provides Automated Test Suite for validating the functionalities. Jenkins plugin of Test Result Analyzer is also added. For more information about ATS integration, see Oracle Communications Cloud Native Core Automated Test Suite Guide.
CNC Console GUI Integration:
SEPP is integrated with CNC Console. This allows the user to configure SEPP Rest APIs using the CNC Console GUI. For more information about SEPP integration, see Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide.

Network Exposure Function (NEF)

There are no new features or updates implemented in CNC 2.4.0 release.

Network Repository Function (NRF)

OCNRF 1.14.1 has been updated with the following enhancement:

OCNRF Compatibility with OCCNE 1.9
OCNRF is compatible with OCCNE 1.9.0. For more information about OCCNE 1.9.0, see Oracle Communications Cloud Native Environment Installation Guide.
OCNRF Disaster Recovery Guide
Oracle Communications Cloud Native Core Network Repository Function Disaster Recovery Guideis delivered in NRF documentation package. The Disaster Recovery Guide describes scenario based procedures used to perform disaster recovery of Oracle Communications Network Repository Function (OCNRF) deployments. The OCNRF operators can take database's backup and restore them either on same or a different cluster. It uses OCNRF database for commands or instructions.

OCNRF 1.14.0 has been updated with the following enhancement:

NRF Roaming Support
This feature is to support the 3GPP defined inter-PLMN routing for NRF specific service operations like NFDiscover, AccessToken, NFStatusSubscribe, NFStatusUnSubscribe, and NFStatusNotify. For more information about roaming feature, see the "Roaming Support" chapter in Oracle Communications Cloud Native Core Network Repository Function User Guide.
NRF Forwarding Decision Per NF Type and NF Service Type
OCNRF Forwarding feature is enhanced to enable the users to define more controlled forwarding criteria for NFDiscover and AccessToken Service Requests from OCNRF to an intermediate NRF. The user can configure the preferred NF Type, the NF Services, or both for which forwarding is applicable. This provides the flexibility to regulate the traffic between the NRFs. For more information about forwarding feature, see the "OCNRF Forwarding" chapter in Oracle Communications Cloud Native Core Network Repository Function User Guide.
Support for R16 Parameters as per 29.510
Support for smfInfoList and smfInfo attribute as per 29.510-g70 for NFRegister, NFUpdate, NFStatusSubscribe, NfStatusNotify and NfDiscover.
Failure KPIs per Service Operation
Added new failure KPIs to measure the requests and responses per service operations For more information about KPIs, see Oracle Communications Cloud Native Core Network Repository Function User Guide.

Network Slice Selection Function (NSSF)

OCNSSF 1.7.0 has been updated with the following enhancements:

Feature Negotiation: OCNSSF now supports feature negotiation mechanism that is used to negotiate the optional features applicable between the NSSF and the NF Service Consumer, for the NSSF supported services. The following optional features have been added under the Feature Negotiation feature:

For more information about the applicable helm parameters, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation and Upgrade Guide.

For more information, see Oracle Communications Cloud Native Core Network Slice Selection Function User's Guide.
- Subscription Modification (SUBMOD): It's an optional feature under the Feature Negotiation feature that allows operators to modify subscriptions by supporting HTTP Patch on NsAvailability Subscription. To enable the SUBMOD feature, it is mandatory to enable the Feature Negotiation feature.
  For more information about the applicable helm parameters, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation and Upgrade Guide.
  
  For more information on the feature description, see Oracle Communications Cloud Native Core Network Slice Selection Function User's Guide.
- Empty Authorized NSSAI Availability Notification (EANAN): It's an optional feature that provides support for sending an empty array of Authorized NSSAI Availability Data when a notification trigger leads to a situation of no Tracking Area (TA) with Authorized NSSAI by the NSSF. To enable the EANAN feature, it is mandatory to enable the Feature Negotiation feature.
  For more information about the applicable helm parameters, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation and Upgrade Guide.
  
  For more information on the feature description, see Oracle Communications Cloud Native Core Network Slice Selection Function User's Guide.

Unified Data Management (UDM)

There are no new features or updates implemented in CNC 2.4.0 release.

Unified Data Repository (UDR)

UDR 1.14.0 has been updated with the following enhancements:

Overload Control: UDR supports overload management as it helps to control services downtime and ensures service availability during extreme overload conditions. It uses Ingress Gateway and perf-info microservices to control network congestion and handles the overload scenarios. For more information about this feature, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
Export and Import of UDR Configuration Data: With the implementation of export and import feature, UDR enable its users to perform bulk export and import of UDR configuration data using CNC Console. For more information about this feature, see the "Export & Import" section in Oracle Communications Cloud Native Core Unified Data Repository User Guide.
iXML to CSV converter for bulk import: With the introduction of CSV conversion tool, UDR enable its users to convert subscriber records in iXML format to CSV format. The iXML format is same as defined for 4G UDR. For more information, see the "Bulk Import Tool" section in Oracle Communications Cloud Native Core Unified Data Repository User Guide.
Diameter Gateway for UDR Sh interface: UDR provides a way to handle overload of backend microservices for different thresholds and types of overload scenarios. For more information, see the "Architecture" and "Metrics" sections in Oracle Communications Cloud Native Core Unified Data Repository Users Guide and "Configurable Parameters" section in Oracle Communications Cloud Native Core Unified Data Repository Installation and Upgrade Guide.
Integration with common NRF Client: UDR integration with NRF client project provides support for NFSetID and Locality configuration in NFProfile of UDR.

For more information about NRF Client integration, see the "Configuring Unified Data Repository" section in Oracle Communications Cloud Native Core Unified Data Repository Installation and Upgrade Guide.
Support for Database Backup and Recovery: UDR provides feature to enable its users to perform database backup and recovery under different scenarios like configuration database corrupted, configuration and subscribers database corrupted, single site failure etc. For information about how to overcome the identified disaster recovery scenarios, see Oracle Communications Cloud Native Core Unified Data Repository Disaster Recovery Guide.
Service Mesh Charts: UDR supports virtual service and Request Authentication CRDs in the Helm charts. For more information, see Oracle Communications Cloud Native Core Unified Data Repository Installation and Upgrade Guide.
Support of UDR MIBs: UDR provides MIB files for UDR alerts, which can be integrated with SNMP.
OAM Interface for Provisioning Gateway: UDR-ProvGw now provides an OAM interface using which configurations of Ingress Gateway, Egress Gateway, and Provisioning Gateway services can be configured using REST APIs. For more information, see Oracle Communications Cloud Native Core Provisioning Gateway Interface Specification Guide.