2 Feature Descriptions

This chapter provides a summary of new features and updates to the existing features for network functions released in Cloud Native Core release 3.25.1.1xx.0.

Note:

CCNC-XXXX is an internal identification number of the feature.

Automated Testing Suite (ATS) Framework

Release 25.1.100

There are no new features or feature enhancements in this release.

Binding Support Function (BSF)

Release 25.1.101

There are no new features or feature enhancements in this release.

Release 25.1.100

Oracle Communications Cloud Native Core, Binding Support Function (BSF) 25.1.100 includes the following enhancements:

  • Stale Binding Detection Audit, Report, and Recover: Service disruptions caused by network storms, system overload, database latency, or other factors can interrupt signaling between the Policy and BSF, impacting session binding. BSF provides a mechanism to revalidate the binding information of a PDU session, and recover stale bindings, ensuring session integrity. For more information, see "Stale Binding Detection Audit, Report, and Recover" section in "Oracle Communications Cloud Native Core, Binding Support Function User Guide".
  • Stale Binding Manual Detection Tool: Service disruptions caused by network storms, system overload, database latency, or other factors can interrupt signaling between Policy and BSF, impacting session binding. Currently, when binding is lost and Policy sessions are in a hung state, there is no way of knowing which sessions were lost or never received the binding. As a result, no action can be taken to solve this issue. The Binding Detection Tool addresses this by allowing manual queries of sessions created within a specific time frame in both Policy and BSF. For more information, see Oracle Communications Cloud Native Core, Binding Detection Tool User Guide.
  • Enhancements in menu.json for cnDBTier GRR Configuration: The BSF CNC Console GUI supports integration of read-only Georeplicaiton Recovery (GRR) cnDBTier APIs. With this, users can have specific information on cnDBTier statuses on the CNC Console. For more information, see the "Support for cnDBTier APIs in CNC Console" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.
  • Performance enhancement to achieve 54K TPS: In this release, BSF can achieve 54K TPS through performance optimizations. For more information, see the "BSF Benchmark Testing" section in Oracle Communications Cloud Native Core, Binding Support Function Benchmarking Guide.
  • Traffic Segregation: BSF supports end-to-end traffic segregation based on traffic types. This ensures that critical networks are not cross-connected or share the same routes, thereby preventing network congestion. For more information, see the "Traffic Segregation" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Table 2-1 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-8864 Stale Binding Detection Audit, Report, and Recover
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-8840 SMPCF and BSF Stale Binding Manual Detection Tool
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-5795 Enhancements in menu.json for cnDBTier GRR Configuration
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-7763 Compatibility with two Webscale versions per release
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-4504 Performance enhancement to achieve 54K TPS
Oracle Communications Cloud Native Core, Advance Cloud Native Environment - 25K Active Subscribers perpetual CCNC-4443 Traffic Segregation

Cloud Native Environment (CNE)

Release 25.1.101

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 25.1.101 includes the following enhancement:

Support for Multus Thick Plugin for CNE deployments: With this feature, Multus Thick Plugin is installed whenever a new version of CNE is installed with CNLB enabled option. It is highly recommended to use Multus Thick Plugin based release for CNLB based CNE deployments. For more information, see Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.

Note:

  • Only CNE Releases 24.3.3 and above support Multus Thick Plugin based CNE deployments.
  • CNE 24.2.x releases do not support Multus Thick Plugin and are not recommended for CNLB deployments.

Release 25.1.100

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 25.1.100 includes the following enhancements:
  • Support for BareMetal CNE Deployment with Bare Minimum Servers (3 Worker Nodes): With this feature, CNE allows you to set up a BareMetal deployment with a minimal resources of three worker nodes. This setup is ideal for testing and getting started with CNE. For more information about installing and upgrading CNE with bare minimum servers, see the "Installing CNE using Bare Minimum Servers" and "Upgrading BareMetal CNE Deployed using Bare Minimum Servers" sections respectively in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • Hardware Agnostic Deployment Model for BareMetal CNE: Currently, CNE validates and supports BareMetal deployments on HP Gen10 and Oracle X8-2 servers only. With this release, CNE supports installing BareMetal CNE on any servers, thereby allowing the users to choose their servers based on their requirement. For more information about the prerequisites and updated procedure to install BareMetal CNE on other servers, see the "BareMetal Installation" section in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • Heterogenous Hardware Support for BareMetal CNE Deployment: Currently, BareMetal deployments support homogeneous hardware make, type, and version for worker nodes in a cluster. This means, all the worker nodes in a cluster must have the same type of hardware server, type, and version (for example, HP Gen 10 server with similar CPU, cores, RAM, and storage). With this feature, CNE supports heterogeneous hardware, wherein worker nodes in a cluster can have different server, type, and version. This provides more flexibility and options to manage hardware failure, expand existing deployment cluster, and tackle hardware End Of Life (EOL) and availability. For more information, see Oracle Communications Cloud Native Core, Cloud Native Environment User Guide and Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • Generic ToR Switch Configuration for BareMetal CNE: With this feature, CNE facilitates you to set up your BareMetal cluster using any ToR switch, by providing generic specifications, prerequisites, and configuration templates. For more information about configuring the ToR switches, see the "Configuring Top of Rack Switches" section in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • Traffic Segregation: With this enhancement, CNE provides an option to use Cloud Native Load Balancer (CNLB) without internal traffic segregation. This means CNLB can be configured to have a single interface to handle only external traffic. For more information about CNLB configuration, see Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • New Versions of Common Services: The following common services are upgraded in this release:
    • Helm - 3.16.2
    • Kubernetes - 1.31.1
    • Calico - 3.28.0
    • Istio - 1.23.0
    To get the complete list of third-party services and their versions, refer to the dependencies_25.1.100.tgz file provided as part of the software delivery package.

    Note:

    CNE constitutes a number of third-party services. For information about these third-party services, refer to the documents of the respective third-party services.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Table 2-2 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-6155 Support for BareMetal CNE Deployment with Bare Minimum Servers (3 Worker Nodes)
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-7674 Hardware Agnostic Deployment Model for BareMetal CNE
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-8297 Heterogenous Hardware Support for BareMetal CNE Deployment
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-7672 Generic ToR Switch Configuration for BareMetal CNE
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment - 25K Active Subscribers Perpetual CCNC-8079 Traffic Segregation
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment - 25K Active Subscribers Perpetual CCNC-1192 Multiple Network Interface per POD Support

Operations Services Overlay (OSO)

Release 25.1.103

Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.1.103 includes the following enhancements:
  • Support for new versions:
    • 25_1_common_oso:25.1.103
    • 25_1_oso_snapshot:25.1.103

For more information, see Oracle Communications Cloud Native Core, Operations Services Overlay Installation and Upgrade Guide.

Release 25.1.102

Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.1.102 includes the following enhancements:
Support for new versions:
  • 25_1_common_oso:25.1.102
  • 25_1_oso_snapshot:25.1.102

For more information, see Oracle Communications Operations Services Overlay Installation and Upgrade Guide.

Release 25.1.101

Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.1.101 includes the following enhancements:
Support for new versions:
  • 25_1_common_oso:25.1.101
  • 25_1_oso_snapshot:25.1.101

For more information, see Oracle Communications Operations Services Overlay Installation and Upgrade Guide.

Release 25.1.100

Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.1.100 includes the following enhancements:

  • Support for Time Series Database (TSDB) Snapshot: Prometheus uses Time Series Database (TSDB) to store the collected metrics. With this feature, OSO allows the users to capture a snapshot at a specific point of time of the Prometheus data store without shutting down or disrupting the Prometheus instance. It is useful for taking backups, recovery, or even debugging purposes.

    For more information, see the "Support for Time Series Database (TSDB) Snapshot" section in Oracle Communications Operations Services Overlay User Guide.

    For more information about the procedure to take TSDB snapshots, see the "Creating Backup of Prometheus Time Series Database (TSDB) Using Snapshot Utility" section in Oracle Communications Operations Services Overlay Installation and Upgrade Guide.

  • Support for new versions:
    • 25_1_common_pod is replaced with 25_1_common_oso.
    • 25_1_oso_snapshot:25.1.100

    For more information, see Oracle Communications Operations Services Overlay Installation and Upgrade Guide.

Cloud Native Core cnDBTier

Release 25.1.103

There are no new features or feature enhancements in this release.

Release 25.1.102

There are no new features or feature enhancements in this release.

Release 25.1.101

There are no new features or feature enhancements in this release.

Release 25.1.100

Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) 25.1.100 includes the following enhancements:

  • Enhanced Georeplication Recovery using Parallel Backup Transfer and Restore: The backup transfer and restore mechanism used during a georeplication recovery involved additional data compression at the data node and serial backup transfer to the remote sites. This impacted the performance of georeplication recovery. With this feature, cnDBTier implements the following enhancements in backup transfer and restore thereby improving the performance and efficiency of georeplication recovery:
    • Avoids additional backup compression.
    • Supports parallel backup transfer from healthy cluster to georeplication recovery cluster.
    • Restores data node backups in parallel, as and when the backups are transferred from the healthy cluster to the georeplication recovery cluster.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

  • Support for TLS: With this enhancement, cnDBTier supports TLS for application SQL pods to establish secure connection for communication with Network Functions (NFs). When the TLS feature is enabled, cnDBTier performs or supports the following operations during communication with NFs:
    • The application SQL pod uses the certificates provided or configured to establish an encrypted connection for communication with NFs. This encrypted connection remains throughout the life cycle of the connection between NF and cnDBTier.
    • The system reestablishes the TLS connection between NFs and cnDBTier after a georeplication recovery. That is, when a georeplication recovery completes successfully, the system reestablishes the encrypted connection between the NFs and cnDBTier. This ensures that cnDBTier continues supporting TLS connection after a georeplication recovery.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

  • Monitoring Cluster Events to Determine Data Loss in Clusters: Network issues in the user environment led to cluster disconnections, which in turn resulted in the loss of cluster data. However, users were unable to monitor and identify the loss of data occurred due to network issues. With this feature, cnDBTier provides the following REST APIs to monitor cnDBTier cluster events to determine any data loss:
    • http://<base-uri>/db-tier/reset/parameter/cluster_restart_disconnect
    • http://<base-uri>/db-tier/reset/cluster/{cluster-name}/parameter/cluster_restart_disconnect
    • http://<base-uri>/db-tier/cluster/status
    • http://<base-uri>/db-tier/cluster/status/events/{numberOfLastEvents}
    • http://<base-uri>/db-tier/all/cluster/status/
    • http://<base-uri>/db-tier/all/cluster/status/events/{numberOfLastEvents}

    For more information about these APIs, see Oracle Communications Cloud Native Core, cnDBTier User Guide.

  • Storing NDB Logs in PVC: cnDBTier stores all NDB pod (ndbmgmd, ndbmysqld, ndbappmysqld) logs in PVC. These logs remain persistent even when the pods restart and they can be used to debug any data node related issues. However, ndbmtd logs were not stored in PVC. With this feature, cnDBTier stored ndbmtd logs in PVC, such that the logs remain available even after the pod is deleted. This feature is enabled in cnDBTier by default and doesn't require any configuration. For more information, see the "Storing NDB Logs in PVC" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
  • cnDBTier Automated Backup: MySQL doesn't allow schema change in a cluster when a backup is in progress. However, users were unable to check the ongoing backup processes in the cluster and schedule their upgrades for schema changes. With this release, cnDBTier provides the http://<base-uri>/db-tier/status/cluster/local/backup REST API to fetch the details of the data node backups that are in progress in the NDB cluster. For more information about this API, see the "cnDBTier Backup APIs" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
  • cnDBTier Scaling: With this release, cnDBTier automates the vertical scaling of PVCs using the dbtscale_vertical_pvc script. This simplifies the vertical scaling process and reduces human errors that may occur while performing the manual procedure. For more information about performing the vertical scaling using the dbtscale_vertical_pvc script, see the "cnDBTier Scaling" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
  • Support for New Versions of Software: cnDBTier has updated the version of Oracle MySQL Cluster Database to 8.4.3 in this release.

    Note:

    In db-monitor-svc script, the PVC and JVM-related metrics are disabled by default. This is due to PVC and JVM metrics fetch-time exceeding the Prometheus metrics fetch-timeout. This impacts the metrics fetch cycle.

    The following PVC metrics are disabled:

      • db_tier_pvc_read_write_speed
      • db_tier_pvc_is_accesible
      • db_tier_pvc_failure_count

    The following JVM metrics are disabled:

      • jvm_max_memory
      • jvm_free_memory
      • jvm_total_memory

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Table 2-3 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Network Slice Selection Function- 25K Active Subscribers Perpetual CCNC-8876 Enhanced Georeplication Recovery using Parallel Backup Transfer and Restore
Oracle Communications Cloud Native Core, Network Slice Selection Function- 25K Active Subscribers Perpetual CCNC-5332 Support for TLS
Oracle Communications Cloud Native Core, Policy and Charging Rules Function - 25K Subscribers Perpetual CCNC-9356 Compatibility with two Webscale versions per release

Cloud Native Configuration Console (CNC Console)

Release 25.1.100

Oracle Communications Cloud Native Configuration Console (CNC Console) 25.1.100 includes the following enhancements:

  • Multiple Admin Support for CNCC IAM Deployments: As CNC Console evolved from a simple interface for managing a single network function (NF) instance with one admin account to supporting multi-cluster deployments catering to multiple NF Instances including access management to observability applications, there was a need to have support for multiple admin users for managing the users across multiple customer operations teams.

    As part of this feature, CNC Console IAM is enhanced to support creation and management of multiple admin users in IAM using both internal and external IDPs (SAML and LDAP). For all the admin accounts managed in CNC Console, all the existing measurements, alarms, and logging mechanisms would be applicable to all admin users similar to the existing core users.

    There are default password policies defined for CNCC IAM users in the default realm. These policies are disabled by default and can be enabled, if needed.During the deployment, a default admin user is created. To create multiple CNCC IAM admin users, refer to the "Post Installation steps" section in Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide and Oracle Communications Cloud Native Configuration Console User Guide.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Table 2-4 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-9858 Multiple Admin support for CNCC IAM deployments
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-8525 IAM Backend Upliftment

Oracle Communications Cloud Native Core, Certificate Management (OCCM)

Release 25.1.100

Oracle Communications Cloud Native Core, Certificate Management (OCCM) 25.1.100 includes the following enhancements:

  • Support to Increase the Certificate Management Capacity: OCCM is designed to manage certificates for multiple NFs. This feature increases the maximum number of supported certificates (both OCCM and NF certificates) to 200. For more information about certificate management, see the "Managing Certificates" section in Oracle Communications Cloud Native Core, Certificate Management User Guide. For more information, see "OCCM Configuration Maximum Limits", see the "OCCM Deployment Models" section in Oracle Communications Cloud Native Core, Certificate Management Installation, Upgrade, and Fault Recovery Guide.
  • Expired Certificate Handling: This feature enables OCCM to raise alert and stop the retry of CMP (Certificate Management Protocol) Identity (OCCM) certificate renewal. For the expired End Entity (NF) certificates, if OCCM is configured to sign the Certificate Management Protocol Version 2 (CMPv2) Key Update Request (KUR) using the certificate and key that is being renewed, then OCCM raises an alert indicating the expiry of the certificate and stop the retry of NF certificate renewal. For more information, see "Expired Certificate Handling" section in Oracle Communications Cloud Native Core, Certificate Management Troubleshooting Guide.
  • Bulk Migration of Certificates: With this feature, you can update the issuer configuration and endpoint by updating fields such as the server URL, recipient Distinguished Name (DN), and issuer DN. This update is performed by migrating the certificates in bulk from the current issuer to a newly created issuer with the required configuration. For more information, see "Bulk Migration of Certificates" section in Oracle Communications Cloud Native Core, Certificate Management User Guide.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Table 2-5 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-8810 Support to Increase the Certificate Management Capacity
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-8808 Expired Certificate Handling
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-6075 Bulk Migration of Certificates

Network Repository Function (NRF)

Release 25.1.204

Oracle Communications Cloud Native Core, Network Repository Function (NRF) 25.1.204 includes the following enhancements:

No new features or feature enhancements have been introduced in this release.

Release 25.1.203

Oracle Communications Cloud Native Core, Network Repository Function (NRF) 25.1.203 includes the following enhancements:

No new features or feature enhancements have been introduced in this release.

Release 25.1.202

Oracle Communications Cloud Native Core, Network Repository Function (NRF) 25.1.202 includes the following enhancements:
  • Egress Gateway Pod Protection Using Rate Limiting: This feature applies a rate limiting mechanism to Egress Gateway pods, allowing them to process a predefined number of requests. When the request rate exceeds the configured threshold, the pods protect themselves by either rejecting additional requests with a custom error code or allowing them, based on the configuration.

    For more information about this feature, see the "Egress Gateway Pod Protection Using Rate Limiting" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Support for 106K Ingress TPS with 91.2K SLF TPS in Growth Mode: NRF supports processing up to 106K Transactions Per Second (TPS) in a growth environment configured with two sets, with each set accommodating upto 53K Ingress TPS and 45.6K SLF TPS utilization for enabling greater performance and scalability.

    For more information, see the "Benchmark Testing" section in Oracle Communications Cloud Native Core, Network Repository Function Benchmarking Guide.

  • NF Profile Count Enhancements: NRF supports a maximum of 600 NF Profiles in a growth environment configured with two sets, with each set accommodating up to 300 NF Profiles. This enhancement improves scalability and capacity for large-scale network deployments.

    For more information, see the "NRF Supported Services" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide. For more information on NF Profiles supported per set in a Growth environment with two sets, see the section "Benchmark Testing" in Oracle Communications Cloud Native Core, Network Repository Function Benchmarking Guide.

  • Support for ASM 1.21.6: NRF supports the Aspen Service Mesh (ASM) 1.21.6 version on Kubernetes 1.27 version from this release.

    For more information, see the "Configuring NRF to Support ASM" section in Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-10061 Support for ASM 1.21.x
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-10371 Egress Gateway Pod Protection Using Rate Limiting
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-11110 NF Profile Count Enhancements
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-10184 Support for 106K Ingress TPS with 91.2K SLF TPS in Growth Mode

Release 25.1.200

Oracle Communications Cloud Native Core, Network Repository Function (NRF) 25.1.200 includes the following enhancements:
  • Ingress Gateway Pod Protection Using Rate Limiting: This feature applies a rate limiting mechanism to Ingress Gateway pods, allowing them to process a predefined number of requests. When the request rate exceeds the configured threshold, the pods protect themselves by either rejecting additional requests with a custom error code or allowing them, based on the configuration.

    For more information about this feature, see the "Ingress Gateway Pod Protection Using Rate Limiting" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Writing Messages of the Same Transaction in the Same Kafka Partition: This feature ensures that NRF copies request and response messages of the same transaction to the same Kafka partition when sending messages to Data Director. This reduces latency in processing transaction data. The feature uses the correlation-id (a unique identifier) as the message key to correlate messages for a transaction.

    For more information about this feature, see the "NRF Message Feed" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • NRF Message Feed Enhancements: The following additional message attributes are included in the metadata list, along with existing attributes:
    • source-ip
    • destination-ip
    • source-port
    • pod-instance-id
    • destination-port

    For more information about this feature, see the "NRF Message Feed" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • NF Profile Size Limit: This feature allows to specify the maximum limit of the NF Profile size that can be registered with NRF. The NF Profile size is evaluated during the NfRegister or NfUpdate service operation, and if the profile size is within the configured maximum limit, the service operation is allowed. If the profile size breaches the configured thresholds, the service operation gets rejected.

    For more information about this feature, see the "NF Profile Size Limit" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Pod Level Traffic Rejections (Overload Control Enhancements): With this enhancement, NRF rejects the incoming requests at pod level for percentage-based overload control by removing the dependency on cache-based coordination across pods. When the overload control level is breached, the number of requests to be rejected is calculated based on the requests received at each Ingress Gateway pod. This ensures a more accurate and consistent request rejection even in scenarios with low Transactions Per Second (TPS) and uneven traffic distribution.

    For more information about this feature, see the "Pod Level Traffic Rejections" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Support for cnDBTier Backup Status APIs in CNC Console: With this enhancement, cnDBTier backup status APIs are integrated into the CNC Console. Users can view cnDBTier backup status APIs, such as the current timestamp, backup in progress, and next scheduled backup on CNC Console.

    For more information, see the "Support for cnDBTier APIs in CNC Console" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-5363 NRF Message Feed Enhancements
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-6080 Writing Messages of the Same Transaction in the Same Kafka Partition
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-9424 Ingress Gateway Pod Protection Using Rate Limiting

Network Slice Selection Function (NSSF)

Release 25.1.100

Oracle Communications Cloud Native Core, Network Slice Selection Function (NSSF) 25.1.100 includes the following enhancements:

  • DNS SRV-Based Selection of NRF in NSSF: The DNS SRV-based selection feature enhances the Network Slice Selection Function (NSSF) by introducing dynamic Network Repository Function (NRF) selection through DNS SRV records. This update improves network resilience by allowing NSSF to dynamically switch to alternate NRFs in case of primary NRF failures, ensuring continuous service availability. For more information, see the "DNS SRV-Based Selection of NRF in NSSF" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

  • Deleting All Slices in a TAI Using PATCH Remove Operation: This feature enhances NSSF by enabling more flexible management of network slices in 5G networks. It allows the AMF to delete all slices for specific Tracking Areas (TAIs), TAILists, or TAIRanges using the PATCH operation. For more information, see the "Deleting All Slices in a TAI Using PATCH Remove Operation" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

  • Improved Error Response when All Slices are Removed: NSSF now provides clearer responses, such as returning 204 No Content when all slices in an area are removed, while still allowing slices to be re-added through PATCH or PUT operations. This enhancement improves granularity, efficiency, and control for slice management while aligning with 3GPP standards. For more information, see the "Deleting All Slices in a TAI Using PATCH Remove Operation" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Table 2-6 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-4529 DNS SRV-Based Selection of NRF in NSSF
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-9140 Deleting All Slices in a TAI Using PATCH Remove Operation
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-8381 Improved Error Response when All Slices are Removed
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual

CCNC-9228

CCNC-5077

 Compatibility with two Webscale versions per release

Service Communication Proxy (SCP)

Release 25.2.102

There are no new features or enhancements in this release.

Release 25.2.101

There are no new features or enhancements in this release.

Release 25.2.100

Oracle Communications Cloud Native Core, Service Communication Proxy (SCP) 25.2.100 includes the following enhancements:
  • LCM Automation: The Lifecycle Management (LCM) Automation feature optimizes deployment and upgrade processes of SCP by automating service account creation. This enhancement allows you to automatically create user-defined service accounts without any manual intervention. For more information, see the "LCM Automation" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • TLS 1.3 Support for Kubernetes API: SCP can be deployed in a Kubernetes cluster that supports TLS 1.3. For more information, see the "TLS 1.3 Support for Kubernetes API" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Support for Grafana 7.5.x: SCP supports Grafana 7.5.x. For more information, see the "Software Requirements" section in Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide.
  • Support for Sender NF Type based Routing Option Selection: SCP enhances its routing options configuration to configure senderNFType so that routing options selection criteria can also consider sender NF Type for selecting a routing option. In addition, SCP enhances its logic to identify notification sender to consider sender NF type in routing options selection criteria. For more information, see the "Support for Sender NF Type based Routing Option Selection" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Support for 1200 NF Profiles: SCP is enhanced to support 1200 NF profiles with a single Notification pod instance. For more information, see "SCP Services", "Upgrade", and "ASM Sidecar" sections in Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Table 2-7 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-10664 Support for Grafana 7.5.x
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-9147 TLS 1.3 Support for Kubernetes API
Oracle Communications Cloud Native Core, Automated Lifecycle Management - 25K Active Subscribers CCNC-8293 LCM Automation
Oracle Communications Cloud Native Core, Advanced Routing – 25K Active Subscribers Perpetual CCNC-4404 and CCNC-5933 Routing Options Enhancement for Notification Messages
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-11246 Support for 1200 NF Profiles

Security Edge Protection Proxy (SEPP)

Release 25.2.100

Oracle Communications Cloud Native Core, Security Edge Protection Proxy (SEPP) 25.2.100 includes the following enhancements:
  • NRF Selection Mechanisms Using nrf client: This feature allows the SEPP to dynamically select NRF instances based on real-time availability and site redundancy through DNS SRV configurations. In addition to the static configurations by operators, the SEPP can now resolve NRFs using DNS SRV based Fully Qualified Domain Names (FQDNs). The SEPP is configured with a primary NRF and multiple fallback NRFs, which take over if the primary NRF becomes unreachable.

    The nrf client uses the Alternate Route Service, which helps the SEPP find and select different Network Repository Functions (NRFs) by using DNS SRV-based lookups. This service allows the SEPP to translate Fully Qualified Domain Names (FQDNs) or virtual FQDNs into alternate NRF addresses. This setup enables the SEPP to prioritize and adjust connections to different NRFs based on specific service needs. For more information, see the "NRF Selection Mechanisms Using nrf client" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide and "Customizable Parameters" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.

  • Integrating SEPP with 5G Network Intelligence Fabric (5G NIF): To route traffic to a Network Function, SEPP has traditionally relied on configurations or destination headers found in incoming SBI requests. For integration with the customized 5G Network Intelligence Fabric (5GNIF), SEPP must now discover this custom NF through the NRF, which holds this information. Once discovered, SEPP uses all existing routing mechanisms (such as alternate routing) to direct traffic to the identified 5GNIF instance. Additionally, SEPP is required to send copies of error messages, triggered by countermeasures or failed checks, to the 5GNIF for analytic purposes. For more information, see the "Integrating SEPP with 5G Network Intelligence Fabric (5G NIF)" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide and the "Customizable Parameters" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.
  • TLS 1.3 Support for Kubernetes API: SEPP can be deployed in a Kubernetes cluster that supports TLS 1.3. For more information, see the "TLSv1.3 Support for Kubernetes API Server Communication" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.
  • Support for Grafana 7.5.x: SEPP supports Grafana 7.5.x. For more information, see the "Software Requirements" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Table 2-8 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Advanced Routing – 25K Active Subscribers Perpetual CCNC-8037 Integrating SEPP with 5G Network Intelligence Fabric (5G NIF)
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-10188 NRF Selection Mechanisms Using nrf client
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-9149 TLS 1.3 Support for Kubernetes API Server Communication
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-10674 Support for Grafana 7.5.x

Unified Data Repository (UDR)

Release 25.1.202

There are no new features or enhancements made in this release.

Release 25.1.201

There are no new features or enhancements made in this release.

Release 25.1.200

Oracle Communications Cloud Native Core, Unified Data Repository (UDR) 25.1.200 includes the following enhancements:
  • Lifecycle Management (LCM) Based Automation: This feature optimizes the deployment or upgrade steps. This is achieved by automating service account creation that enables you to create user-defined service account automatically without performing any manual steps. For more information, see the "Lifecycle Management (LCM) Based Automation" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide and Oracle Communications Cloud Native Core, Provisioning Gateway Installation Guide.
  • Support for Export of Policy Data in Comma Separated Value (CSV) Format: This feature enables the Subscriber Export Tool to export the 5G and 4G subscriber policy data, which includes the profile data and policy data (am-data, sm-data, and ue-policy-set) in CSV file format from cnUDR. The converted subscriber data in CSV file format is used by the Subscriber Bulk Import Tool to import the subscriber data along with its policy data on an another instance of cnUDR. For more information, see the "Support for Export of Policy Data in Comma Separated Value (CSV) Format" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
  • Support for Dual Stack: With this feature, cnUDR and Provisioning Gateway can be deployed on a dual stack Kubernetes infrastructure. Using the dual stack mechanism, cnUDR and Provisioning Gateway establish and accept connections within pods and services in a Kubernetes cluster using IPv4 or IPv6. For more information, see the "Support for Dual Stack" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide and Oracle Communications Cloud Native Core, Provisioning Gateway Installation Guide.
  • Support for cnDBTier Backup Status APIs in CNC Console: With this enhancement, UDR can view the cnDBTier backup status, such as the current timestamp, backup in progress, and next scheduled backup using CNC Console. For more information, see the "cnDBTier Backup Status" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
  • Ingress Gateway Pod Protection Using Rate Limiting: With this feature, rate limiting mechanism is applied for Ingress Gateway pods. This mechanism allows pods to process a predefined number of requests. When the request rate exceeds the threshold, the pods take action to protect themselves. Depending on the configuration, the pods either reject the additional requests with a custom error code or allows the request. For more information, see the "Ingress Gateway Pod Protection Using Rate Limiting" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
  • Support for ASM 1.21.6: UDR 25.1.200 supports Aspen Service Mesh (ASM) 1.21.6 version on Kubernetes 1.27 version from this release. For more information, see the "Configuring UDR to Support Aspen Service Mesh" section in Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.

The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Table 2-9 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual CCNC-10117 SLF capacity growth on 23.4.1 (Signalling TPS = 50K ; Provisioning TPS = 1.2K , Sub Cap: 64M)
Oracle Communications Cloud Native Core, Advance Networking - 25K Active Subscribers CCNC-9467 Support for Dual Stack
Oracle Communications Cloud Native Core, Automated Lifecycle Management - 25K Active Subscribers CCNC-9151 Lifecycle Management (LCM) Based Automation
Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual CCNC-9133 Support for ASM 1.21.6
Oracle Communications Cloud Native Core, Automated Lifecycle Management - 25K Active Subscribers CCNC-9094 Lifecycle Management (LCM) Based Automation
Oracle Communications Cloud Native Core, Unified Data Repository - 25K Active Subscribers Perpetual CCNC-5480 Support for Export of Policy Data in Comma Separated Value (CSV) Format
Oracle Communications Cloud Native Core, Unified Data Repository - 25K Active Subscribers - Ingress Gateway Pod Protection Using Rate Limiting