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.26.1.2xx.0.

Note:

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

2.1 Automated Testing Suite (ATS) Framework

Release 26.1.201

Oracle Communications Cloud Native Core, Automated Test Suite (ATS) Framework 26.1.201 includes the following enhancements:

  • ATS Pod Logs: ATS pod logs are enhanced with different log categories to provide detailed and structured logging to improve the debugging and analysis process.

    Configuration Status: Enabled by default.

    For more information about this enhancement, see Oracle Communications Cloud Native Core Automated Testing Suite 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
Enable logging functionality for ATS for debugging purposes CCNC-12248 ATS Pod Logs

2.2 Cloud Native Environment (CNE)

Release 26.1.200

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 26.1.200 has been updated with the following enhancements:

  • Support for Log Externalization:

    CNE supports externalization of logs, allowing users to choose whether to deploy OpenSearch as part of a CNE installation or upgrade. When OpenSearch installation is disabled, Jaeger installation is also disabled.

    This feature is useful for deployments that store logging events outside the cluster. Users can optionally install the Fluentd log forwarding mechanism to egress logs from CNE. Currently, only the http_out plugin is supported for log egress.

    Configuration Status: Disabled by default.

    For more information, see the "Log Externalization Support" section in Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.

  • Support for VCD 10.6 Platform:

    CNE supports VMware Cloud Director (VCD) 10.6.0 for CNLB VMware deployments. Supported VCD versions are 10.4.3 and 10.6.0.

    For more information, see the "Installing vCNE on VMware Environment" section in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.

  • Deprecation of LBVM and Transition to Cloud-Native Load Balancers (CNLB):

    CNE supports Cloud-Native Load Balancers (CNLB) only and does not support LBVM-based ingress or egress. Clusters using LBVM with release 25.2.2xx cannot be upgraded to CNE 26.1.200.

    The following documents have been updated to remove references to the deprecated LBVM functionality:

    • Oracle Communications Cloud Native Core, Cloud Native Environment User Guide
    • Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide

  • Deprecation of Istio and Cert-manager Components:

    CNE no longer supports Istio or cert-manager. When upgrading from an N-1 or N-2 release to CNE 26.1.200, these components are automatically removed during the upgrade process.

    The following documents have been updated to remove references to the deprecated Istio and cert-manager components:

    • Oracle Communications Cloud Native Core, Cloud Native Environment User Guide
    • Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide

  • Support for CNLB Command Line Interface (cnlbctl):

    CNE introduces a command-line utility to support and simplify the management of CNLB-based functionality. The cnlbctl command-line interface is available for use from Bastion hosts and can perform several tasks to administer CNLB application management.

    Configuration Status: Enabled by default.

    For more information, see the "Using CNLB Command Line Utility" section in Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.

  • Support for Application Traffic to Bypass CNLB for Ingress and Egress Traffic:

    CNE extends egress bypass support to bare metal platforms. With this feature, users can configure services running on CNE to bypass CNLB when performing egress from the cluster.

    Configuration Status: Enabled by default.

    For more information, see the "Configuring CNLB Bypass for BareMetal Deployments" section in 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.20.0
    • Kubernetes - 1.35.2
    • podman - 5.6.0
    • containerd - 2.2.1
    • Calico - 3.30.6
    • MetalLB - 0.15.2
    • Prometheus - 3.9.0
    • OCI-Grafana - 7.5.17
    • Jaeger - 2.14.1
    • Kyverno - 1.16.1

To get the complete list of third-party services and their versions, refer to the dependencies_26.1.200.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 – 25K Active Subscribers Perpetual CCNC-4765 Log Externalization Support
Oracle Communications Cloud Native Core, Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-10037 Deprecation of LBVM and Transition to Cloud-Native Load Balancers (CNLB)
Oracle Communications Cloud Native Core, Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-5201 CNLB Support for FQDN Egress NAT Config
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-11801 Support for application traffic to Bypass CNLB for Ingress and Egress traffic
Oracle Communications Cloud Native Core, GitOps - Instance Perpetual CCNC-11034 OC-CNE Integration with GitOps - Support NFs for Integration

2.3 Operations Services Overlay (OSO)

Release 26.1.200

Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 26.1.200 has been updated with the following enhancements:

  • Secure Kafka Integration for Alert Forwarding: With this enhancement, the APM microservice now supports TLS-based communication with Kafka. Users can configure the APM service during deployment to establish a secure channel for forwarding alerts to Kafka, thereby improving data security and compliance. APM service also provides the provision of metrics and alerts, which get configured as targets to the OSO Prometheus at the time of installation.

    Configuration Status: Enabled by default.

    For more information, see the "Alert Forwarding to Kafka" section in Oracle Communications Cloud Native Core, Operations Services Overlay User Guide.

  • Support for Leapfrog Upgrade and Rollback: With this enhancement, OSO supports direct upgrades from up to three prior releases (N+3), reducing the need for sequential upgrades. Leapfrog upgrade support is limited to upgrades targeting 26.1.2xx. Versions earlier than those listed require a sequential upgrade path.

    Rollback is also supported for up to three prior releases (N-3) within the defined upgrade and rollback paths.

    Configuration Status: This is one time upgrade option, configuration status does not apply.

    For more information, see the "Supported Upgrade and Rollback Paths" section in Oracle Communications Cloud Native Core, Operations Services Overlay Installation and Upgrade Guide.

  • Deployment Strategy Change: With this enhancement, the default upgrade behavior for OSO Prometheus pods is updated to use the ReCreate deployment strategy instead of RollingUpdate. This change ensures that existing pods are terminated before new pods are created during an upgrade.

    Configuration Status: Set to "ReCreate" by default.

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

2.4 Cloud Native Core cnDBTier

Release 26.1.201

Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) 26.1.201 has been updated with the following enhancements

  • Preferred IP Family and georeplication Stop/Start using CNC Console:

    The CNC Console screens and corresponding cnDBTier APIs have been added to support IP preference selection for the replication channel and to gracefully stop and start georeplication on configured georeplication sites.

    This enhancement enables users to perform these operations directly from the CNC Console without requiring manual backend actions.

    Note: NF can use the latest menuCncc.json to enable the newly added screens.

    Configuration Status: Disabled by default.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide

  • Event Details APIs:

    cnDBTier now provides a new set of Event Details APIs hosted on db-monitor-svc to retrieve detailed cnDBTier event information. These APIs return event records that occurred within a caller-specified time window, using startTimestamp and endTimestamp in the request body, and include only events that fall within the defined range.

    To control response size and improve retrieval efficiency, the APIs implement pagination, where the caller specifies the number of events per page and the page number through path variables, enabling scalable navigation through large volumes of event data.

    Configuration Status: Enabled by default.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide

  • Deterministic and Controllable Automatic Georeplication Recovery (GRR):

    cnDBTier now supports deterministic and controllable Automatic Georeplication Recovery (Auto GRR). In earlier releases, Auto GRR always selected the healthy site with the lowest site_id as the backup source and did not allow users to disable automatic recovery during site reinstallation, limiting operational control. With this enhancement, users can enable or disable Auto GRR and specify a preferred backup site for recovery.

    New custom_values.yaml parameters:

    global.geoReplicationRecovery.autoGRR.enabled: Enables or disables automatic GRR. Default: true

    global.geoReplicationRecovery.preferredBackupSite: Specifies the preferred backup site for GRR.

    global.geoReplicationRecovery.backupSiteSelectionPolicy: Defines backup-selection behavior as STRICT or PREFERRED. Default: PREFERRED

    New REST APIs are also introduced to GET, UPDATE, and RESET the Auto GRR configuration.

    Configuration Status: Enabled by default.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide

  • Skip Exception Table Restoration

    cnDBTier now supports skipping data restoration for Exception Tables during the GRR process. A new GRR state, FETCH_RESTORE_EXCLUDED_SCHEMA_DETAILS, has been introduced, in which the failed site calls a REST API on the backup site to retrieve Exception Table details.

    The backup site identifies Exception Tables by checking mysql.ndb_replication for entries where conflict resolution is enabled and returns the relevant table details. Exception Tables are identified by the $EX suffix appended to the table name. The failed site stores these details in its Persistent Volume Claim (PVC) and uses the information during restoration to skip data restoration for the Exception Tables.

    Only the schema of Exception Tables is restored, not the data. After GRR completes, the Exception Tables exist with their structure intact but remain empty.

    Configuration Status: Enabled by default.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide

  • CSAR Digital Signature Feature:

    This release introduces digital signing of 5G CNC software packages in CSAR format to meet ETSI NFV-SOL004 V3.5.1 requirements, Section 5.1, Option 1.

    The feature applies a cryptographic digital signature to each package to ensure authenticity and integrity during delivery and deployment by verifying that the package has not been altered or corrupted by a third party, whether in transit or at rest. This protects the integrity of 5G network functions throughout the deployment lifecycle.

    Configuration Status: Enabled by default.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide

  • dbttriage Tool for cnDBTier Health Checks:

    cnDBTier now includes the dbttriage tool, which runs a suite of targeted diagnostic tests and provides streaming output along with a final summary report.

    The tool performs deeper health checks across cnDBTier sites, including checks for pods and services, replication and georeplication states, and related connectivity and validations. It is intended for DBAs and support engineers to run at one site to quickly validate the health of all database sites and identify common issues, such as pod health problems, replication service failures, or georeplication state inconsistencies.

    Configuration Status: Disabled by default.

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

  • dbtfastrecover Tool for Replication Recovery:

    cnDBTier now includes the dbtfastrecover tool, which helps restore interrupted bidirectional replication when db_replication_svc cannot recover the replication channel automatically.

    The tool identifies the latest applied epoch on the local site, selects the next available recovery epoch from the remote site, and configures the local replica to resume replication from the corresponding binary log file and position.

    It is intended for DBAs and support engineers to use when replication is broken and a full GRR can potentially be avoided. Post-recovery validation is still required because skipped epochs can result in data inconsistencies between sites.

    Configuration Status: Disabled by default.

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

  • Charset Migration from UTF8MB3 to UTF8MB4:

    The MySQL UTF8MB3 character set is deprecated and will be removed in a future NDB release. Therefore, cnDBTier tables are created with the UTF8MB4 character set starting with this release.

    During an upgrade, older tables created using UTF8MB3 are migrated to UTF8MB4 by recreating the tables with UTF8MB4 and repopulating them with the existing records. Because this migration increases the time spent in the pre-upgrade phase, the Helm upgrade must be run with the timeout flag specified in the cnDBTier upgrade guide.

    To perform the character set migration successfully, replication must be UP, and there must be no replication lag in any cnDBTier cluster at the time of the upgrade.

    For NF, schema definitions must explicitly specify the character set and must never use UTF8. UTF8MB4 is recommended when selecting among UTF8, UTF8MB3, and UTF8MB4.

    Configuration Status: Enabled by default.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide

  • Password Encryption Enhancement:

    In earlier releases, version 25.2.2xx and earlier, all sites were required to use a common shared password-encryption key. This restriction has now been removed.

    Each site can be configured with its own independent and unique password-encryption key, enabling password encryption to be independently enabled or disabled and supporting password rotation at the site level.

    This enhancement improves security through key isolation, provides greater flexibility in site-level configurations, and supports GRR when password-encryption keys differ across sites.

    Note: The password-encryption feature must be enabled only with cnDBTier 26.1.200 or later. It must not be enabled on earlier cnDBTier versions.

    Configuration Status: Disabled by default.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide

  • GRR Performance Improvement:

    To improve restoration performance during GRR, this release introduces additional and updated configuration parameters that enhance database-restoration efficiency.

    Configuration Status: Enabled by default.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide

Note: Network Function license provides cnDBTier capabilities.

2.5 Cloud Native Configuration Console (CNC Console)

Release 26.1.200

Oracle Communications Cloud Native Core, Cloud Native Configuration Console (CNC Console) 26.1.200 includes the following enhancements:

  • CNC Console Support for Open API JSON File:

    CNC Console supports the OpenAPI specification for CNC Console configuration. The occncc_configuration_openapi_<version>.json file is delivered as part of the CSAR package. The occncc_configuration_openapi_<version>.json file contains the OpenAPI specification for CNC Console configuration.

    For more information about this enhancement, see Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide.

  • CNC Console Deployment Using Flux Setup:

    CNC Console supports deployment through a centralized Flux CD setup. The setup uses Helm chart resources to automate deployment to target Kubernetes clusters. Deployment is driven by declarative manifests stored in Git, which helps ensure consistency and version control. This feature was validated with Flux version 2.4.0 and GitLab version v18.2.8-ee for Kubernetes-based environments.

    For more information about this enhancement, see the "CNC Console Deployment Using Flux CD Appendix" section Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide.

  • CNC Console IAM Backend Uplift:

    CNC Console includes an IAM backend uplift to address security issues, theme updates, and database schema changes. As part of this uplift, the core procedures for adding or updating passwords, creating and viewing users, configuring SAML IDP, generating access tokens, and managing user federation remained functionally unchanged. The UI screens were refreshed to align with the latest interface and design standards.

    For more information about this enhancement, see Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide and Oracle Communications Cloud Native Configuration Console User Guide.

  • CNCC Database Data Sync Script:

    dbtdatasync is a command-line utility that detects, compares, and synchronizes MySQL table data between georeplicated Kubernetes or OpenShift sites. It identifies schema-level and row-level differences, generates compressed dumps and SQL diff files, and supports schema-only validation.

    For more information about this enhancement, see the "Database Data Sync Script for CNC Console" section in Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide.

For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.

Note:

Network Function license provides CNC Console capabilities.

2.6 Oracle Communications Cloud Native Core, Certificate Management (OCCM)

Release 26.1.200

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

  • Issuer CA HealthCheck:

    This feature is a lightweight mechanism to regularly monitor the health of OCCM’s connectivity with configured issuers (CA) . It does so by configuring a special-purpose certificate termed a HealthCheck Certificate. This certificate is manually created per issuer and configured to renew on configurable interval (preferably daily). This feature enables OCCM to actively verify communication with the Certificate Authority (CA) by initiating certificate lifecycle operations using a dedicated health check certificate. Renewal success or failure events are displayed via a Grafana dashboard, providing real-time visibility into CA integration health. This acts as a proactive monitoring mechanism, helping detect and resolve issues before they impact NF certificates. Instead of performing manual CA health validation, the system:

    • Issues a controlled dummy certificate
    • Tracks issuance and renewal behavior
    • Publishes Prometheus metrics
    • Displays real-time status on Grafana dashboard

    This enhancement improves system observability without impacting existing certificate workflows. For information, see Oracle Communications Cloud Native Core, Certificate Management User Guide.

  • Enhancements using Helm Optimization

    This enhancement optimizes the deployment and upgrade steps for Oracle 5G NFs, reducing the number of steps customers perform in the field to bring up the NFs. For information, see 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-3 License Names for Feature Mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-5928 Issuer Health Check
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-9667 Enhancements via Helm Optimization

2.7 Network Repository Function (NRF)

Release 26.1.201

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

  • Setting SBI Message Priority: With this feature, support is introduced for setting and forwarding the 3gpp-Sbi-Message-Priority HTTP header as part of the 3GPP SBI Message Priority mechanism. Configuration options are provided to control how the priority header is applied and propagated across NF services.

    Configuration Status: Disabled by default.

    For more information, see the "Setting SBI Message Priority" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • NF Profile Count Enhancements: NRF supports a maximum of 1000 NF Profiles in a growth environment configured with two sets. This enhancement improves scalability and capacity for large-scale network deployments.

    Configuration Status: Enabled by default.

    For more information, see the "NRF Supported Services" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • NF Subscription Limit Enhancements: With this enhancement, NRF now supports a total of 2000 active NF Subscriptions per segment with Non-Growth and Growth deployment scenarios:

    • NRF Growth feature disabled: The entire 2000 active subscription capacity is available within a single set. NRF enforces that the total subscription count within the segment does not exceed this overall limit.
    • NRF Growth feature enabled: The total active subscription capacity when in a segment remains 2000, but the subscription allocation is distributed across two sets. The per-set subscription limits are determined by the Growth configuration defined for each set, and NRF ensures that the active subscription count in each set does not exceed its configured limit. Appropriate configuration has to be done to ensure combined subscription limit count in both the NRF sets does not exceed 2000.

    Configuration Status: Enabled by default.

    For more information, see the "NRF Supported Services" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide. For more information about the feature, see the "Subscription Limit" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Efficient Subscription Notification Processing: With this enhancement, each subscription microservice pod maintains subscription data in a local in-memory cache instead of retrieving it dynamically from the Cache Data Service (CDS) for every notification event. This improve notification processing efficiency and support higher subscription counts.

    Configuration Status: Enabled by default.

    For more details, see the "Efficient Subscription Notification Processing" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

    For more details about the feature, contact https://support.oracle.com.

  • Gzip Compression for Cache Data Microservice: This feature adds GZIP compression capabilities in the Cache Data Service (CDS) to reduce payload sizes and optimize bandwidth utilization between NRF microservices such as Discovery, Subscription, and CDS (in CDS-to-CDS communication). It enhances response efficiency for large data transfers by enabling compression at both client and server levels.

    Configuration Status: Enabled by default at server side and disabled at client side.

    For more details about this feature, see the "GZIP Compression for Cache Data Service" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Automatic Recovery of Missing NRF Database Records Across Georeplicated Sites: This feature introduces automatic recovery of missing or inconsistent records in supported database tables across georeplicated NRF sites. Using MySQL NDB replication, a subsequent update can recreate a missing record or synchronize an existing record on peer sites. The feature is enabled by default and requires no separate conflict-resolution mechanism.

    Configuration Status: Enabled by default.

    For more details, see the "Automatic Recovery of Missing NRF Database Records Across Georeplicated Sites" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Support for cnDBTier Georeplication Configuration and Control APIs in CNC Console: This enhancement introduces APIs to configure IP family preferences and manage georeplication lifecycle (start or stop) across sites in the cnDBTier. It enables users to control replication between site pairs, manage replication groups, and handle switchover readiness through the CNC Console, improving operational control.

    Configuration Status: Enabled by default.

    For more information, see the "cnDBTier APIs" 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.

Table 2-4 License Names for Feature Mapping

License Name License Number Feature Name
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-10163 Setting SBI Message Priority
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-11508 NF Profile Count Enhancements
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-11510 NF Subscription Limit Enhancements
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-13829 Efficient Subscription Notification Processing
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-13827 Gzip Compression for Cache Data Microservice
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-13825 Automatic Recovery of Missing NRF Database Records Across Georeplicated Sites
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-12615 Support for cnDBTier Georeplication Configuration and Control APIs in CNC Console

2.8 Network Slice Selection Function (NSSF)

Release 26.1.201

Oracle Communications Cloud Native Core Network Slice Selection Function (NSSF) 26.1.201 has been updated with the following enhancements:

  • Support to Handle Partial NF Profile Update Notifications From NRF: Enhanced NSSF to support NF_PROFILE_CHANGED notifications with partial updates (profileChanges) in addition to full profiles (nfProfile). This enables faster reaction to peer NSSF state changes (for example, nfStatus) and improves handover decisions in georedundant deployments, while ignoring non-relevant updates and maintaining backward compatibility.

    Configuration Status: Disabled by default.

    For more information, see the "Support to Handle Partial NF Profile Update Notifications From NRF" 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-5 License Names for Feature Mapping

License Name License Name Feature Name
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-6068 Support to Handle Partial NF Profile Update Notifications From NRF

2.9 OCI Adaptor

Release 26.1.200

Oracle Communications Cloud Native Core, OCI Adaptor 26.1.200 has been updated with the following enhancements:

  • Uplifted the OCI Adaptor Components: The following OCI Adaptor components have been uplifted:

    • Management-agent is uplifted from 1.12.0 to 1.13.0.
    • Fluentd is uplifted from 1.7.4 to 1.7.5.
    • OpenTelemetry Collector image uplifted from 0.124.0 to 0.155.0

  • Uplifted GDK/Micronaut dependency stack:

    • micronautVersion: 4.10.1-oracle-00001 to 4.10.16-oracle-00001
    • GDK BOM: 4.10.1.4 to 4.10.16

  • Removed Metrics Server from OCI Adaptor as it is no longer required and had multiple known vulnerabilities.

  • Updated image selection in the Terraform stack user inputs:

    • Removed Node pool Image from OKE Cluster Configuration.
    • Added CLI Server Image under CLI Server Configuration.

2.10 Service Communication Proxy (SCP)

Release 26.1.201

Oracle Communications Cloud Native Core, Service Communication Proxy (SCP) 26.1.201 includes the following enhancements:

  • Next Hop SCP Outlier Detection: SCP enhances its outlier functionality to detect the next-hop SCP as outlier by determining whether the error response received by consumer SCP-C actually originated from producer SCP-P or not. SCP performs this task by using the oc-3gpp-sbi-od-info header in non-2xx responses generated by SCP-P so SCP-C can determine whether producer SCP-P is healthy or unhealthy.

    Configuration Status: Enabled by default (only if the inter SCP Outlier Detection feature is enabled).

    For more information, see the "Next Hop SCP Outlier Detection" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

  • Runtime Update for SCP Profile Parameters: SCP supports modification of certain profile information Helm parameters using REST APIs and the CNC Console during runtime.

    Configuration Status: Enabled by default.

    For more information, see the "Runtime Update for SCP Profile Parameters" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

  • Support for Subscriber ID to Group ID Resolution: SCP supports subscriber ID to group ID resolution through the Subscriber Location Function (SLF) lookup functionality of Oracle Communications Cloud Native Core, Unified Data Repository (UDR). SCP performs NF discovery from NRF using the group ID instead of the subscriber ID.

    Configuration Status: Disabled by default.

    For more information, see the "Support for Subscriber ID to Group ID Resolution" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

  • SCP Capacity Enhancements: SCP enhances the capabilities of SCPC-Notification and SCPC-Audit microservices to process 3,000 NF profiles.

    For more information, see the "SCP Capacity Enhancements" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

  • Verbose Logging for SCP: SCP has enhanced verbose logging for the SCP-Worker, SCP-nrfProxy, and SCPC-Notification microservices. This feature defines a common log format to include required information to enhance debugging process for WARN and ERROR level logs.

    Configuration Status: Enabled by default.

    For more information, see the "Verbose Logging for SCP" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

  • TLS Support for SCP to cnDBTier Traffic: SCP supports secure database connections by using TLS 1.2 or TLS 1.3 and the corresponding cipher suites for the selected TLS version.

    Configuration Status: Disabled by default.

    For more information, see the "TLS Support for SCP to cnDBTier Traffic" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

  • Rate Limit Enhancements: SCP enhances its rate limit functionality to support up to 3500 local egress rate limit keys, up to 2400 global egress rate limit keys, and up to 900 ingress rate limit keys.

    Configuration Status: Enabled by default.

    For more information, see the "Rate Limiting" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

  • SCP Supports Webscale 1.6: SCP supports Webscale 1.6 with ASM 1.21.

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 License Name Feature Name
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-5411 and CCNC-12036 Next Hop SCP Outlier Detection
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-9661 and CCNC-12038 Runtime Update for SCP Profile Parameters
Oracle Communications Cloud Native Core, Enhanced Signaling Resiliency - 25K Active Subscribers Perpetual CCNC-9721 and CCNC-9723 Support for Subscriber ID to Group ID Resolution
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-11551, CCNC-10317, and CCNC-11088 SCP Capacity Enhancements
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-8450 and CCNC-7820 Verbose Logging for SCP
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-5337 TLS Support for SCP to cnDBTier Traffic
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-11549 Rate Limit Enhancements
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-9487 SCP Supports Webscale 1.6

2.11 Security Edge Protection Proxy (SEPP)

Release 26.1.200

Oracle Communications Cloud Native Core, Security Edge Protection Proxy (SEPP) 26.1.200 has been updated with the following enhancements:

  • SEPP Deployment Using Flux Setup:

    SEPP supported deployment through a centralized Flux CD setup. The deployment used Helm chart resources to automate deployment to target Kubernetes clusters. Declarative manifests stored in Git drove the deployment process, which helped maintain consistency and version control. This feature was validated with Flux version 2.4.0 and GitLab version v18.2.8-ee for Kubernetes-based environments.

    For more information, see the "SEPP Deployment Using Flux Setup Appendix" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.

  • SEPP Database Data Sync Script:

    dbtdatasync is a command-line utility that detects, compares, and synchronizes MySQL table data between georeplicated Kubernetes or OpenShift sites. It identifies schema-level and row-level differences, generates compressed dumps and SQL diff files, and supports schema-only validation.

    For more information, see the "SEPP Database Data Sync Script Appendix" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.

  • Support for cnDBTier APIs in CNC Console:

    With this enhancement, the CNC Console GUI displayed the Gracefully Stop Georeplication, Gracefully Start Georeplication, and IP Preference For Replication Channel APIs.

    Configuration Status: Enabled by default.

    For more information, see the "Support for cnDBTier APIs in CNC Console" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

  • Traffic Segregation Enhancement:

    This enhancement introduced end-to-end traffic segregation for SEPP. It classified and isolated traffic types such as OAM, SBI, and Kubernetes control traffic within a Kubernetes cluster. By using the Multus CNI plugin, SEPP microservice pods could attach to multiple network interfaces. This allowed each traffic type to use a separate network path. Egress traffic from SEPP pods could also be routed through dedicated non-default networks to third-party applications, instead of using a single external network. Cloud-native networking constructs and load balancing mechanisms in OCCNE supported this capability, improving traffic management, scalability, and network reliability.

    Configuration Status: Enabled by default.

    For more information, see the "Traffic Segregation Enhancement" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

  • Prometheus Alerts Published Directly to Kafka:

    This feature allowed OSO, the Application Processing Microservice, to send alerts outside the cluster as Kafka topics. During testing, the OSO memory profile was increased. The feature was validated by sending 200 alerts per second to OSO through Kafka for 15 minutes.

    For more information, see the "SEPP Resource Requirements" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide

  • SEPP Traffic Prioritization Using Egress Gateway Pod Protection Enhancement:

    Traffic prioritization configuration is now managed through REST-based controls instead of Helm-based configuration. A new CNC Console screen enables configuration of NRF client traffic prioritization, allowing users to define message priorities for all autonomous and on-demand NRF SBI messages.

    Configuration Status: Enabled by default.

    For more information, see the "SEPP Traffic Prioritization Using Egress Gateway Pod Protection Enhancement" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy 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-7 License Names for Feature Mapping

License Name License Name Feature Name
Oracle Communications Cloud Native Core, GitOps CCNC-9447 SEPP Deployment Using Flux Setup
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual - SEPP Database Data Sync Script
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual - Support for cnDBTier APIs in CNC Console
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-10383 Traffic Segregation Enhancement
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-11837 Prometheus Alerts Published Directly to Kafka
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-11373 SEPP Traffic Prioritization Using Egress Gateway Pod Protection Enhancement