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

Note:

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

2.1 Automated Testing Suite (ATS) Framework

Release 25.2.202

Oracle Communications Cloud Native Core, Automated Testing Suite (ATS) Framework 25.2.202 includes the following enhancements:
  • Token-based Authentication for Prometheus:

    This enhancement enables ATS to communicate with Prometheus which requires service account token based authentication and with TLS. Service account should be given necessary role-based access control (RBAC) permissions for authorization.

    For more information, see the "ATS Feature Activation and Deactivation" section in Oracle Communications Cloud Native Core Automated Testing Suite Guide.

  • Support for Dual Stack:

    The dual stack mechanism establishes connections with REST APIs and ATS GUI in a Kubernetes cluster using IPv4 or IPv6 or both simultaneously.

    For more information, see the "ATS API" section in Oracle Communications Cloud Native Core Automated Testing Suite Guide.

Parent topic: Feature Descriptions

2.2 Binding Support Function (BSF)

Release 25.2.200

Oracle Communications Cloud Native Core, Binding Support Function (BSF) 25.2.200 includes the following enhancements:
  • Support for SBI Message Priority:

    BSF supports adding 3gpp-Sbi-Message-Priority header to all the requests that it sends out and also in all the responses that it receives from other NFs. Using 3gpp-Sbi-Message-Priority header in requests such as REGISTER, DEREGISTER, or DISCOVERY, BSF and the associated producers and consumers such as SCP, NRF, PCF, AF, and NEF can distinguish between high-priority and low-priority Service Based Interface (SBI) messages.

    Configuration Status: Disabled by default.

    For more information, see the "Support for SBI Message Priority Header" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.

  • Support for cnDBTier Georeplication Status Across All Sites API in CNC Console:

    This enhancement allows Georeplication Status Across All Sites APIs to be integrated into the CNC Console, and users can view the georeplication status for the site to the mated sites along with the replication group status on the CNC Console.

    For more information, see "cnDBTier APIs" in Oracle Communications Cloud Native Core, Binding Support Function User Guide.

  • Support for Even CPUs Profile:

    The Kubernetes CPU Manager is configured with the static or shared CPU policy to reduce deployment failures, mitigate noisy-neighbor effects, and ensure consistent CPU availability for critical network function (NF) workloads in the 5G Core environment. As part of this feature, resource profiling got updated to allocate an even number of CPUs to all BSF services and the Istio sidecar, optimizing guaranteed CPU resources per service.

    Configuration Status: Enabled by default.

    For details on the resource requirements for installing BSF, see "Resource Requirements" section in Oracle Communications Cloud Native Core, Binding Support Function Installation, Upgrade, and Fault Recovery Guide.

  • Application Framework Change: Spring Boot has been replaced with Micronaut as the framework for microservices (except Alternate Route Service, Ingress gateway or Egress gateway micro services).

    For more information, see the "Application Framework Change" 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-1345 Support for SBI Message Priority
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-11758 Support for cnDBTier Georeplication Status Across All Sites APIs in CNC Console
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-11677 Support for Even CPUs Profile

Parent topic: Feature Descriptions

2.3 Cloud Native Environment (CNE)

Release 25.2.200

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 25.2.200 includes the following enhancements:

  • CNE API Server public endpoint:

    This feature provides an option to expose the Kubernetes API server as a public endpoint. The public endpoint is secured using mutual TLS (mTLS) authentication and provides admin-level access to the cluster. This capability supports use cases such as enabling GitOps workflows, while maintaining robust security controls.

    Configuration Status: Disabled by default.

    For more information, see the "Enabling Public Endpoint for CNE (Kubernetes) API Server" section in Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.

  • CNLB Support for Egress and Ingress Bypass (OpenStack Only):

    This feature allows applications to use network attachments that route traffic directly through the native Multus interface, effectively bypassing CNLB.

    Note:

    This feature requires a fresh CNE installation and is available exclusively on the OpenStack platform.

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the "CNLB Bypass Configuration" section in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.

  • CNLB Connection Synchronization:

    Connection synchronization is now supported between active and standby CNLB application pods. This enhancement preserves live CNLB connections during switchover events, delivering seamless user experience and preventing connection drops.

    Configuration Status: Disabled by default.

    For more information on Connection synchronization, see the following sections in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide:

    • For enabling and disabling connection tracking feature, see "Managing Connection Tracking Feature" subsection in the "Configuring Cloud Native Load Balancer (CNLB)" section.
    • For configurable parameters, see "CNLB Manager Environment Variables" table in the "Configuring Cloud Native Load Balancer (CNLB)" section.
  • Dedicated Nodes for CNLB:

    CNE now supports the creation of dedicated nodes reserved exclusively for CNLB. These nodes do not host any other workloads, except observability workloads. It is recommended to use this feature in conjunction with the Heterogeneous Nodes enhancement for optimal deployment flexibility.

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the "CNLB Deployment Strategies" section in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.

  • Support for Heterogeneous Node Types:

    Clusters can now be created with up to three different OpenStack VM flavors (small, medium, and large). This enhancement allows for optimized resource allocation within a cluster. For CNLB workloads, using the small flavor is recommended to maximize efficiency and resource utilization.

    Note:

    This feature requires a fresh CNE installation and is available only on the vCNE platform in this release.

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the "CNLB Deployment Strategies" 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.19.1
    • Kubernetes - 1.34.2
    • containerd - 2.1.4
    • Calico - 3.30.3
    • MetalLB - 0.15.2
    • Prometheus - 3.6.0
    • OCI-Grafana - 7.5.17
    • Jaeger - 1.72.0
    • Istio - 1.18.2
    • Kyverno - 1.15.0
    • cert-manager - 1.12.4
    To get the complete list of third-party services and their versions, refer to the dependencies_25.2.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, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-11487 Support for Heterogeneous Node Types
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-11459 CNLB Support for Egress and Ingress Bypass (OpenStack Only)
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-11342 cnLB optimization to increase the performance on Ingress or Egress or Mix per Service IP for OpenStack -25.2.200
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-11172 Dedicated Nodes for CNLB
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-10453 CNLB Connection Synchronization

Parent topic: Feature Descriptions

2.4 Operations Services Overlay (OSO)

Release 25.2.201

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

  • 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.

Configuration Status: This feature is enabled by default.

For more details, about this feature, see the "Alert Forwarding to Kafka" section in Oracle Communications Cloud Native Core, Operations Services Overlay 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, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-10339 Secure Kafka Integration for Alert Forwarding

Release 25.2.200

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

  • Alert Forwarding to Kafka: With this feature, OSO introduces an Alert Processing Microservice (APM) that receives HTTP-based alerts from OSO(Alert manager), converts them into Kafka-compatible JSON messages, and sends the alerts to a designated Kafka partition. TLS is not supported for Kafka messages.

Note:

In this release, TLS is not supported for Kafka messages.

Configuration Status: Disabled by default

For more details, about this feature, see the "Alert Forwarding to Kafka" section in Oracle Communications Cloud Native Core, Operations Services Overlay 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, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-10339 Alert Forwarding to Kafka

Parent topic: Feature Descriptions

2.5 Cloud Native Core cnDBTier

Release 25.2.201

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

  • Support for Parallel Restart of cnDBTier Pods

    This release introduces the ability to create, delete, and update pods within a StatefulSet concurrently rather than sequentially. This significantly reduces maintenance windows and rollout times while ensuring stability and data integrity. Users can utilize this functionality by running the dbtupgrade_parallel_restart script.

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the "Performing a Parallel Restart of cnDBTier Pods" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.

  • Enhanced Georeplication Monitoring in CNC Console

    A new screen in the CNC Console provides a centralized interface to monitor and verify georeplication status across all configured sites.

    To support this UI enhancement, the following REST APIs are now available:
    • http://base-uri/ocdbtier/faultrecovery/start
    • http://base-uri/ocdbtier/v1/backup/status
    • http://base-uri/ocdbtier/replication/status/realtime
    • http://base-uri/ocdbtier/replication/status/realtime/{siteName,remoteSiteName}

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the following sections:
    • For the REST APIs, see the "cnDBTier APIs for CNC Console" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
    • For the enhanced CNC Console screen, see the "Monitoring Georeplication Recovery Status Using CNC Console" section in Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

  • Georeplication Recovery (GRR) Performance Improvement

    To support for both manual and automated recovery, improved site selection, and better monitoring for seamless cnDBTier replication restoration, the following configuration parameters have been updated:

    Added the following global configuration parameters to support backup restoration process in Georeplication Recovery in the Global Parameters section:
    • /global/additionalndbconfigurations/ndb/MaxFKBuildBatchSize with default value 512
    • /global/additionalndbconfigurations/ndb/MaxUIBuildBatchSize with default value 512
    Updated the default values for the following parameters:
    • global/ndb/restoreparallelism from 128 to 1024
    • ndb/resources/requests/memory from 16Gi to 18Gi
    • api/resources/limits/CPU from 8 to 4
    • api/resources/requests/CPU from 8 to 4
    • db-replication-svc/resources/limits/CPU from 1 to 1.1
    • db-replication-svc/resources/requests/CPU from 0.6 to 1
    • db-backup-manager-svc/resources/limits/cpu from 1 to 1.1
    • db-backup-manager-svc/resources/requests/cpu from 1 to 1.1

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the "Customizing cnDBTier" section in Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

  • Automated Horizontal Scaling of NDB Pods

    The procedure for scaling ndbappmysqld pods has been updated to utilize the dbtscale_ndbmtd_pods script. This tool automates the expansion of cnDBTier clusters, allowing for seamless scaling of NDB data pods to meet increased capacity demands.

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the "Horizontal Scaling of ndbmtd pods using dbtscale_ndbmtd_pods" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.

  • Addition of cnDBTier Georedundant Site

    The procedure to add cnDBTier georedundant mate site has been updated to include the procedure to scale db replication service deployments and ndbmysqld pods.

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the "Scaling of db replication service deployments and ndbmysqld pod" section in Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

  • Schema and Data Consistency Georeplication Audit

    In a cnDBTier deployment, georeplicated database sites can be monitored using the dbtaudit script. This command-line utility allows administrators to audit site status, review replication health, and ensure overall compliance across distributed database clusters.

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the "Auditing georeplicated database sites using dbtaudit script" section in Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

  • Aspen Service Mesh (ASM) for External Communication:

    This feature enables secure external communication through ASM (Application Service Mesh) by selectively applying Istio sidecar injection only to pods where external communication is involved. By selectively enforcing ASM policies, cnDBTier ensures the security and compliance of its external interfaces, while preserving high performance and simplifying manageability within the cnDBTier ecosystem.

    Configuration Status: Disabled by default.

    For more information, see the "Aspen Service Mesh (ASM) for External Communication" section in Oracle Communications Cloud Native Core, cnDBTier 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, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-11640 Parallel Restart of cnDBTier Pods
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-11227 Georeplication Performance Improvement
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-10389 Automated Horizontal Scaling of NDB Pods

Parent topic: Feature Descriptions

2.6 Cloud Native Configuration Console (CNC Console)

Release 25.2.201

There are no new features or enhancements in this release.

Release 25.2.200

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

  • CNC Console IAM Backend Upliftment:

    CNC Console has performed an IAM backend upliftment to resolve security issues, theme updates, and handle database schema changes. As a part of this upliftment, the core procedures for adding or updating passwords, creating and viewing users, configuring SAML IDP, generating access tokens, and managing user federation remain functionally unchanged. However, the UI screens have been refreshed to align with the latest interface and design standards.

    Configuration Status: Enabled by default.

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

  • Application Framework Change:Spring Boot has been replaced with Micronaut as the framework for microservices.

    Configuration Status: Always enabled (no additional configuration required).

  • Support for Additional cnDBTier APIs: CNC Console now supports additional cnDBTier APIs for replication status across all cnDBTier sites. This enhancement is NF dependent and must be enabled in their respective NF configurations.

    Configuration Status: Enabled by default.

    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 Disabling mTLS/TLS for cnDBTier Internal Pod Communication:

    CNC Console supports configuring ASM for external traffic only, effectively disabling mTLS for internal communication between cnDBTier pods. This enhancement provides more granular control over sidecar injection, allowing you to select from three modes: None, All, and External. This replaces the previous binary configuration. CNC Console now supports integration with cnDBTier configured in external mode.

    Configuration Status: Disabled by default.

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, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-10855 CNC Console IAM Backend Upliftment
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-10849 Support for Migration from Springboot to Micronaut
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CNCC-11861 Support for Additional cnDBTier APIs
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-11968 Support for Disabling mTLS/TLS for cnDBTier Internal Pod Communication

Parent topic: Feature Descriptions

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

Release 25.2.200

Oracle Communications Cloud Native Core, Certificate Management (OCCM) 25.2.200 includes the following enhancement:

  • Support for Certificate Cloning: OCCM supports the certificate cloning functionality. It streamlines how users create new certificates by allowing them to clone or duplicate an existing certificate’s configuration. This significantly reduces manual entry, minimizes errors, and ensures consistency across certificate deployments.

    Configuration Status: Enabled by default

    For more information, see Oracle Communications Cloud Native Core, Certificate Management User Guide.

  • Support for Deleting Certificate Configuration and Secret: OCCM has enhanced the delete certificate functionality support deleting the certificate and Kubernetes secret simultaneously. This enables the user to delete the associated Kubernetes secret along with the certificate configuration in a single action.

    Configuration Status: Always enabled (no additional configuration required)

    For more 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-7 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-10321 Support for Certificate Cloning
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-10622 Support for Deleting Certificate Configuration and Secret

Parent topic: Feature Descriptions

2.8 Network Repository Function (NRF)

Release 25.2.201

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

  • Support for TLSv1.3 on Internal API Communication: With the implementation of this feature, NRF can be deployed in a Kubernetes cluster that supports TLS 1.3.

    Configuration Status: Disabled by default.

    For more information about this feature, see the "Support for TLSv1.3 on Internal API Communication" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Rerouting SLF Requests Based on Server Header Value: With this enhancement, NRF can extract unique identifiers for SLF or UDR instances directly from the response's server header (for example, identifiers in formats like UDR-udr1-instanceid or SCP-scp-p.xyz.com). By comparing these identifiers to a dynamically or statically configured list of available SLF and UDR instances, the NRF can select an alternative instance that has not yet been attempted. The first part of the server header determines whether the entry refers to a UDR or SCP. NRF extracts the instanceId from UDR entries, compares it against the current list of available UDRs, and excludes instances that have already been attempted from further retries. This approach minimizes redundant routing, improves efficiency, and strengthens the resilience and continuity of network services.

    Configuration Status: Disabled by default.

    For more information, see the "Rerouting SLF Requests Based on Server Header Value" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Simultaneous Support for HTTP and HTTPS Connections: NRF supports HTTP and HTTPS connections simultaneously with peer NFs for incoming (as in server) and outgoing (as in client) traffic.

    Configuration Status: Disabled by default.

    For more information, see the "Simultaneous Support for HTTP and HTTPS Connections" 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 1500 NF Subscriptions per segment with Non-Growth and Growth deployment scenarios:
    • Growth feature disabled: The entire 1500 subscription capacity is available within a single set. NRF enforces that the total subscription count within the segment does not exceed this overall limit.
    • Growth feature enabled: The total subscription capacity when in a segment remains 1500, 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 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 doesn't exceed 1500.

    Configuration Status: Disabled by default.

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

  • Support for cnDBTier Georeplication Status Across All Sites APIs in CNC Console: This enhancement allows Georeplication Status Across All Sites APIs to be integrated into the CNC Console, and users can view the georeplication status for the site to the mated sites along with the replication group status on the CNC Console.

    Configuration Status: Enabled by default.

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

  • Support for OpenAPI JSON in CSAR: With this enhancement, the existing OpenAPI specifications provided in YAML format are transitioned to JSON format to improve compatibility with external tools, API change tracking across releases, and ensures a consistent and standardized API specification format.

    For more information, see the "Pushing the Images to Customer Docker Registry" and "Pushing the NRF Images to OCI Docker Registry" sections in Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

  • Support for Grafana 7.5.x: NRF supports Grafana 7.5.x.

    For more information, see the "Software Requirements" section in Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.

  • Application Framework Change: Spring Boot has been replaced with Micronaut as the framework for NRF microservices.

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

Table 2-8 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-9155 Support for TLSv1.3 on Internal API Communication
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-1366 Rerouting SLF Requests Based on Server Header Value
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-9475 Simultaneous Support for HTTP and HTTPS Connections
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-11943 NF Subscription Limit Enhancements
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-10429 NF Profile Count Enhancements
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-11756 Support for cnDBTier Georeplication Status Across All Sites APIs in CNC Console
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-12139 Support for OpenAPI JSON in CSAR
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-10662 Support for Grafana 7.5.x
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-9591 Application Framework Change

Parent topic: Feature Descriptions

2.9 Network Slice Selection Function (NSSF)

Release 25.2.200

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

  • Application Framework Change: Spring Boot has been replaced with Micronaut as the framework for microservices. With this migration, support for the latency metric *_latency_seconds has been deprecated.

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see the “NSSF Metrics” section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

  • NRF Client Retry and Health Check: The NRF Client Health Check continuously assesses the health of NRF instances to ensure high availability and seamless failover, especially in georedundant environments. It includes configurable intervals, intelligent health status updates, and a retry mechanism to minimize service disruption.

    Configuration Status: Enabled by default.

    For more information, see “NRF Client Retry and Health Check” section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

  • Support for TLSv1.3 on Internal API Communication: NSSF supports TLSv1.3 (in addition to TLSv1.2) for secure communication with the Kubernetes API server.

    Configuration Status: Disabled by default.

    For more information, see “Support for TLSv1.3 on Internal API Communication” section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

  • Support for Dual Stack: Using the dual stack mechanism, NSSF communicates within services or deployments in a Kubernetes cluster using IPv4 or IPv6 or both simultaneously depending on the configured deployment mode.

    Configuration Status: Always enabled (no additional configuration required)

    For more information, see “Support for Dual Stack” section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

  • Support for Disabling mTLS/TLS for cnDBTier Internal Pod Communication: CNC Console supports configuring ASM for external traffic only, effectively disabling mTLS for internal communication between cnDBTier pods. This enhancement provides more granular control over sidecar injection, allowing you to select from three modes: None, All, and External. This replaces the previous binary configuration. CNC Console now uses external mode to integrate with cnDBTier and you can deploy cnDBTier without ASM sidecars for internal pod communication.

    Configuration Status: Enabled by default.

    For more information, see “Configuring NSSF to Support Aspen Service Mesh” section in Oracle Communications Cloud Native Core, Network Slice Selection Function Installation, Upgrade, and Fault Recovery Guide.

  • Support for ASM 1.21.6: NSSF supports Aspen Service Mesh (ASM) 1.21.6 from this release.

    For more information, see “Configuring NSSF to Support Aspen Service Mesh” section in Oracle Communications Cloud Native Core, Network Slice Selection Function Installation, Upgrade, and Fault Recovery Guide.

  • Support for Grafana 7.5.x: NSSF supports Grafana version 7.5.x.

    Configuration Status: Enabled by default.

    For more information, see “Software Requirements” section in Oracle Communications Cloud Native Core, Network Slice Selection 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.

Table 2-9 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-11959 Support for Disabling mTLS/TLS for cnDBTier Internal Pod Communication
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-11377 NSSF: Support for ASM 1.21.6
Oracle Communications Cloud Native Core, Advance Networking - 25K Active Subscribers CCNC-11118 Support for Dual Stack
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-10668 Support for Grafana 7.5.x
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-10361 NSSF: S-nssai to be configured at PLMN level
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-9884 Application Framework Change
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-9153 Support for TLSv1.3 on Internal API Communication
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-9234 NRF Client Retry and Health Check

Parent topic: Feature Descriptions

2.10 OCI Adaptor

Release 25.2.200

Oracle Communications Cloud Native Core, OCI Adaptor 25.2.200 includes the following enhancement:
  • Uplifted the OCI Adaptor Components: The following OCI Adaptor components have been uplifted:
    • Management-agent is uplifted from 1.7.0 to 1.12.0.
    • Fluentd is uplifted from 1.6.0 to 1.7.4.
    • Metric-server is uplifted from 0.7.2 to 0.8.0.

Parent topic: Feature Descriptions

2.11 Policy

Release 25.2.201

Oracle Communications Cloud Native Core, Converged Policy 25.2.201 includes the following enhancements:
  • Enhancement to Overload control Handling in SM Service: At SBI Gateway side, to handle the load shedding conditions, messages are either rejected based on the priority of a message or 'n' percentage of messages are rejected. With this limited capability even messages which are important but may not be carrying higher priority can get discarded. Rejecting the N7 message causes UE and SMF to keep retrying. The N7 messages spike during outage because of the retry of the rejected messages. The spike is caused by UE and MME re-attempting PDU Session Establishment Request. To mitigate this issue, Policy supports load shedding at the Policy micro service’s level (SM service).

    Configuration status: Disabled by default

    For more information, see the "Overload Control at Policy Microservices" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Immediate Report Handling support for SM-Data on N36: Immediate Report Handling sends urgent notifications directly to the subscribed system as soon as a relevant change is detected. There is no need to wait for next polling cycle or batch update. This ensures the PCF receives up-to-date information in real-time, improving network efficiency and user experience. Policy supports Immediate Report Handling support for SM-Data on N36 for specific subscriber data in SM Data along with AM data and UEPolicy data categories.

    Configuration status: Disabled by default

    For more information, see the "Configuring Policy to Support Aspen Service Mesh" section in Oracle Communications Cloud Native Core, Policy Installation, Upgrade, and Fault Recovery Guide.

  • PCF timer-expiry support when Subscribing to Notifications from UDR as per 29.519: Converged Policy supports to manage the validity and expiry of Policy Data Subscriptions, as defined in 3GPP TS 29.519 Clause 5.4.2.10. It uses the expiry attribute within the PolicyDataSubscription data structure. It detects when a subscription is approaching expiry and prompt re-subscription for Operator Specific data.

    Configuration status: Disabled by default.

    For more information, see "Expiry Handling for Policy Data Subscriptions" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Support for DNN Replacement and Slice Support in AM Policy: PCF supports DNN replacement when UE operates using local configuration or when the operator policies are used to replace a UE requested DNN with another DNN used only internally in the network.

    Configuration status: Disabled by default.

    For more information, see the "Support for DNN Replacement and Slice Support in AM Policy" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Policy Support for Dynamic AMF Subscription and N1N2 Message Routing on GUAMI Update: Policy supports handling AMF changes upon receiving a different GUAMI during an update for a UE Policy Association.

    Configuration status: Disabled by default.

    For more information, see the "Policy Support for Dynamic AMF Subscription and N1N2 Message Routing on GUAMI Update" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Support for Sponsored Data Connectivity When AF/NEF Provides the Support Over Policy Authorization Service: The Sponsored Data Connectivity (SDC) defines standard method for Application Function (AF) to provide usage threshold information and requests usage report for sponsored data used by the subscriber. PCF allocates usage monitoring keys, grants SMF usage threshold, and delivers the usage report received from SMF to AF when the threshold is reached or the session is terminated. PCF installs PCC Rules on SMF that tracks the usage and provides a report when the usage threshold is reached or when a session is terminated for the sponsored data.

    Configuration status: Disabled by default.

    For more information, see Support for Sponsored Data Connectivity When AF/NEF Provides the Support Over Policy Authorization Service section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Support of pcfIpEndPoints with Only Port and Protocol in pcfBinding- BSF Registration: Policy supports to provide the list of PCF IpEndpoints inside the PcfBinding request body in the binding registration request sent to BSF.

    Configuration status: Disabled by default.

    For more information, see the "PCF Session Management" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Support to Display the Text Names of URSP and UPSI Rules in Logs: This feature enhances monitoring capabilities by ensuring that application logs for the UE and PRE services display both the name and the corresponding identifiable hexadecimal ID (UUID) for each User Plane Subscription Information (UPSI) and User Routing Selection Policy (URSP).

    Configuration status: Disabled by default.

    For more information, see the "Support to Display the Text Names of URSP and UPSI Rules in Logs" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Policy Support for the Even CPUs Profile:The Kubernetes CPU Manager is configured with the static or shared CPU policy to reduce deployment failures, mitigate noisy-neighbor effects, and ensure consistent CPU availability for critical network function (NF) workloads in the 5G Core environment. This feature updates resource profiling to allocate an even number of CPUs to all Policy services and the Istio sidecar, optimizing guaranteed CPU resources per service.

    Configuration status: Enabled by default.

    For details on enabling and configuring Aspen Service Mesh (ASM) based installation, see the "Configuring Policy to Support Aspen Service Mesh" section in Oracle Communications Cloud Native Core, Converged Policy Installation, Upgrade, and Fault Recovery Guide.

  • Optimizing N7 Session Lookup for AAR Messages in Rx Call Flow: Policy supports to optimize the N7 session lookup for AAR-I messages in Rx call flows. Whenever SM service receives a Create request for an Rx session over N7 interface, if this feature is enabled, during binding registration, SM service sends the session details such as SmPolicyAssociationId and contextOwner (PCF-SM) in a cookie ocnf-service-cookie to BSF. BSF stores the details sent in the cookie in BSF Management service database. Whenever Policy receives AAR-I request from BSF, the AAR-I request from BSF includes a OCNF-SERVICE-COOKIE Custom AVP that contains the Rx session details such as session owner and the session identifier such as SmPolicyAssociationId (Primary Key). If the cookie-owner is PCF-SM, Diameter Gateway skips calling the Binding service for primary key lookup. It processes the details in OCNF-SERVICE-COOKIE Custom AVP and decides whether to route the request to PCRF Core or for Diameter Connector.

    Configuration status: Disabled by default.

    For more information, see the "Optimizing N7 Session Lookup for AAR-I Messages in Rx Call Flows" section in Oracle Communications Cloud Native Core, Policy User Guide.

  • Support for USER_LOCATION_CH Event Trigger: Policy provides the capability to handle User Location Change (USER_LOCATION_CH) network event through enablement of the optional feature AggregatedUELocChanges as defined in 3GPP TS 29.512.

    Configuration status: Disabled by default.

    For more information, see the "Support for USER_LOCATION_CH Event Trigger" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Enhanced logging (at WARN level) for microservices involved in PCRF & Diameter: Policy is enhanced to support logging for Diameter (CnPCRF-Gx, CnPCRF-Sy, CnPCF-Sy, and PCRF-Sd) at their default log level (WARN) to provide sufficient visibility into issues within or across the external facing interfaces of the microservices.

    Configuration status: Disabled by default.

    For more information, see the "Logging Support for Error Response" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Pod Protection at Ingress Gateway Using Rate Limiting: Policy supports configuring Rate Limiting for Ingress Gateway service in order to provide pod protection by throttling inbound requests, if they are above configured rate. From release 25.2.201, Policy also supports congestion control and message priority capabilities also for Ingress Gateway in order to provide pod protection.

    Configuration status: Disabled by default.

    For more information, see the Pod Protection at Ingress Gateway Using Rate Limiting section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Support for cnDBTier Georeplication Status Across All Sites API in CNC Console: This enhancement allows Georeplication Status Across All Sites APIs to be integrated into the CNC Console, and users can view and users can view the georeplication status of all the configured sites in the CNC Console.

    Configuration status: Enabled by default.

    For more information, see "cnDBTier APIs" in the Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Application Framework Change: Spring Boot has been replaced with Micronaut as the framework for microservices.

    For more information, see the "Application Framework Change" section in Oracle Communications Cloud Native Core, Converged Policy 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-10 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual CCNC-10017 Enhancement to Overload control Handling in SM Service
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual CCNC-9811 Immediate Report Handling support for SM-Data on N36
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual CCNC-5920 PCF timer-expiry support when Subscribing to Notifications from UDR as per 29.519
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual CCNC-7938 Support for DNN Replacement and Slice Support in AM Policy
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual CCNC-3816 Policy Support for Dynamic AMF Subscription and N1N2 Message Routing on GUAMI Update
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual CCNC-10352 Support for Sponsored Data Connectivity When AF/NEF Provides the Support Over Policy Authorization Service
Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual CCNC-11114 Support of pcfIpEndPoints with Only Port and Protocol in pcfBinding- BSF Registration
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual CCNC-8598 Support to Display the Text Names of URSP and UPSI Rules in Logs
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual

CCNC-11679

CCNC-11675

 Policy Support for the Even CPUs Profile
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual CCNC-5388 Support for USER_LOCATION_CH Event Trigger
Oracle Communications Cloud Native Core, Converged Policy - 25K Active Subscribers Perpetual CCNC-9956 Enhanced logging (at WARN level) for microservices involved in PCRF & Diameter

Parent topic: Feature Descriptions

2.12 Service Communication Proxy (SCP)

Release 25.2.201

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

  • CNLB Bypass: SCP has enhanced its capabilities to support the CNLB bypass feature using the Network Attachment Definitions (NADs) configuration under the 'network attachment' and 'cnlb' annotations.

    Configuration Status: Disabled by default.

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

  • Disabling mTLS to Establish Communication between SCP and cnDBTier: SCP enables you to disable Mutual Transport Layer Security (mTLS) to establish communication between SCP and cnDBTier on an ASM setup.

    Configuration Status: Disabled by default.

    For more information, see the "Disabling mTLS to Establish Communication between SCP and cnDBTier" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

  • NF Discovery Enhancements: SCP enhances its NF discovery mechanism by providing configurations to enhance delegated discovery response by adding NFs based on reverse lookup on the set IDs of NFs present in the delegated discovery responses. It also supports load balancing and alternate routing by updating the priority and capacity of NFs.

    Configuration Status: Disabled by default.

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

  • NF Selection Enhancements: SCP enhances its NF selection using NF selection mode configuration that modifies the selection of NFs by consumer NFs for routing. SCP can perform load balancing between the NFs in an NF set for the service requests.

    Configuration Status: Disabled by default.

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

  • Topology Source Information Enhancements: SCP enhances its Topology Source Information REST API to learn NF profiles from both NRF and local configuration for any NF type at the same time.

    Configuration Status: Enabled by default.

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

  • Support for Custom Roaming Proxy: SCP is enhanced to support Custom Roaming Proxy that intercepts ingress roaming traffic from the local SEPP before forwarding it to SCP, and intercepts egress roaming traffic from SCP before forwarding it to the local SEPP in the local PLMN.

    Configuration Status: Disabled by default.

    For more information, see the "Support for Custom Roaming Proxy" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

  • Token-based Authentication for Prometheus: This enhancement enables ATS to communicate with Prometheus which requires service account token based authentication and with TLS. Service account should be given necessary role-based access control (RBAC) permissions for authorization.

    Configuration Status: Disabled by default.

    For more information, see the "ATS Feature Activation and Deactivation"" and "Downloading the ATS Package"" sections in Oracle Communications Cloud Native Core Automated Testing Suite Guide.

  • Support for Even CPUs Profile: The Kubernetes CPU Manager is configured with the static or shared CPU policy to reduce deployment failures, mitigate noisy-neighbor effects, and ensure consistent CPU availability for critical Network Function (NF) workloads in the 5G Core environment. As part of this feature, resource profiling got updated to allocate an even number of CPUs to all SCP services, optimizing guaranteed CPU resources per service.

    Configuration Status: Enabled by default.

    For more information about resource requirements for installing SCP, see the "Resource Requirements" section in Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide.

  • Viewing cnDBTier Replication Status: cnDBTier provides the Georeplication Status Across All Sites functionality to view the replication status across all cnDBTier clusters using the CNC Console. This functionality displays the names of local and remote sites along with their corresponding replication status.

    Configuration Status: Enabled by default.

    For more information, see the "Viewing cnDBTier Replication Status" section in Oracle Communications Cloud Native Core, Service Communication 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-11 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-11481 CNLB Bypass
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-11687 Support for Even CPUs Profile
Oracle Communications Cloud Native Core, Enhanced Signaling Resiliency - 25K Active Subscribers Perpetual CCNC-8785 NF Discovery Enhancements
Oracle Communications Cloud Native Core, Enhanced Signaling Resiliency - 25K Active Subscribers Perpetual CCNC-8787 NF Selection Enhancements
Oracle Communications Cloud Native Core, Advanced Routing - 25K Active Subscribers Perpetual CCNC-9787 Support for Custom Roaming Proxy
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-11955 Disabling mTLS to Establish Communication between SCP and cnDBtier
Oracle Communications Cloud Native Core, Automated Test Tools and Scripts Suite - Node Perpetual CCNC-10867 Token-based Authentication for Prometheus
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-11748 Viewing cnDBTier Replication Status
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-10574 Transactional Model D Capacity of 650K MPS Per SCP Instance

Parent topic: Feature Descriptions

2.13 Security Edge Protection Proxy (SEPP)

Release 25.2.200

Oracle Communications Cloud Native Core, Security Edge Protection Proxy (SEPP) 25.2.200 includes the following enhancements:

  • Hosted SEPP Feature: The Hosted SEPP feature enhances Oracle’s Hosted SEPP deployment by enabling multi tenancy support. This feature introduces the ability to handle multiple Fully Qualified Domain Names (FQDNs) and certificates for different tenants, providing improved flexibility in inter network communications and partner routing. With the new model, the SEPP can handle multiple identities, facilitating seamless connectivity to different roaming and hosted partners using different FQDNs. This eliminates the constraints of using a single FQDN for all connections, thus improving the efficiency of traffic routing and reducing the need for manual intervention.

    Configuration Status: Disabled by default.

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

  • Support for Max-Response Timer Header: The feature enables the SEPP to validate, add, or modify timestamp headers in both ingress and egress request paths. Once enabled, it prevents delays and service degradation by enforcing a maximum allowable response time, ensuring that requests are processed within an acceptable time window. Any messages that exceed the defined response time threshold are automatically rejected, which enhances the overall efficiency and responsiveness of the network. The feature works by embedding timestamps in the headers of messages sent from the AMF to the SEPP.

    Configuration Status: Disabled by default.

    For more information, see the "Support for Max-Response Timer Header in SEPP" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

  • Support for PLMN Validation in Get Access Token Requests for Roaming Subscribers: This feature enhances validation and error handling for OAuth Token Request (GET_Access_Token) messages, ensuring only valid, authenticated requests with correct PLMN IDs are processed. SEPP validates incoming requests against negotiated PLMN IDs, ensuring they match local network requirements and content type specifications. Mandatory parameters are enforced, and invalid requests trigger error responses, which are logged for further analysis. Valid requests are forwarded to the local NF, while metrics and logs are captured to monitor system performance. Alerts are triggered based on error rates, enabling proactive issue resolution.

    Configuration Status: Enabled by default.

    For more information, see the "Support for PLMN Validation in Get Access Token Requests for Roaming Subscribers" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

  • Error Response and Logging Enhancement for SEPP: In the enhanced error response mechanism, SEPP now includes additional context in error messages, such as the server FQDN, NF service name, vendor name, and a unique error ID. This makes it easier to identify the exact cause of errors. Further, the logging enhancements introduce new attributes in error logs, including status, title, detailed descriptions, and sender/receiver information, enabling quicker identification of issues and reducing downtime during fault resolution. The Error Response and Logging Enhancement feature improves SEPP's ability to capture and communicate error details, aiding in faster troubleshooting.

    Configuration Status: Disabled by default.

    For more information, see the "Error Response and Logging Enhancement for SEPP" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide, and "Customizable Parameters" in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.

  • Lifecycle Management (LCM) Based Automation: Lifecycle Management (LCM) Automation optimizes the deployment and upgrade processes of SEPP by reducing the steps required to initiate. The following automation enhancements are supported in this release:

    • Helm Enhancements for Service Account: This enhancement allows you to automatically create user-defined service accounts without any manual intervention.

    • Helm Enhancements for NF Alert Configurations on OSO: SEPP leverages the oso-alr-config Helm chart, introduced in the OSO package, to apply alert rules through Helm upgrades. While the oso-alr-config Helm chart is deployed automatically during the OSO installation, SEPP performs Helm upgrades to apply or update the required alert rules. Both manual and automated configurations are supported.

      Configuration Status: Disabled by default.

      For more information, see the "Lifecycle Management (LCM) Based Automation" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

  • Support for bypassing ASM sidecars: The integration of Aspen Service Mesh (ASM) within the internal NF POD has drawbacks. To improve performance, SEPP now allows bypassing ASM sidecars for intra-namespace traffic. Additionally, operational issues in PRINS mode on the N32 interface, when routed through ASM, prompted the removal of ASM from the N32 gateways in the SEPP deployment. While ASM will still be used for inter-NF communication where necessary, these changes are part of enabling the one-sided ASM in SEPP.

    Configuration Status: Disabled by default.

    For more information, see the "Configuring SEPP to Support Aspen Service Mesh" 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: With the implementation of this feature, rate limiting mechanism is applied for Egress 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.

    Configuration Status: Disabled by default.

    For more information, see the "SEPP Traffic Prioritization using Egress Gateway Pod Protection" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

  • SEPP and NRF Communication: This feature enables SEPP to set NRF configuration eliminating the need to manually create routes post installation, including automatic route creation to remove REST-based routing overhead. It enables real-time NF status and capacity information, helping SEPP select healthy, available services for reliable communication, with dynamic updates, retry and rerouting support, and no delay in inter-PLMN NRF traffic. Additionally, it supports dynamic NF registration and deregistration, support for both HTTP and HTTPS NRF instances, static and virtual NRF instances, and route correction in case SCP is deployed, allowing for scalable and flexible network configuration in a cloud-native 5G environment.

    Configuration Status: Enabled by default.

    For more information, see the "SEPP and NRF Communication" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

  • Support for cnDBTier Georeplication Status Across All Sites API in CNC Console: With this enhancement, cnDBTier Georeplication Status Across All Sites can be viewed on CNC Console GUI.

    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.

  • Support for OpenAPI JSON Specification: With this enhancement, the existing OpenAPI specifications provided in YAML format are transitioned to JSON format to improve compatibility with external tools, API change tracking across releases, and ensures a consistent and standardized API specification format.

    Configuration Status: Enabled by default.

  • Application Framework Change: Springboot has been replaced with Micronaut as the framework for SEPP microservices.

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-12 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-11292 Hosted SEPP
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-4970 Support for Max-Response Timer Header in SEPP
Oracle Communications Cloud Native Core, 5G Signaling Firewall - 25K Active Subscribers Perpetual CCNC-10940 Support for PLMN Validation in Get Access Token Requests for Roaming Subscribers
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-8485 Error Response and Logging Enhancement for SEPP
Oracle Communications Cloud Native Core, Automated Lifecycle Management - 25K Active Subscribers CCNC-9692 Lifecycle Management (LCM) Based Automation
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-10348 Support for bypassing ASM sidecars
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-11373 SEPP Traffic Prioritization using Egress Gateway Pod Protection
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-11760 Support for cnDBTier Georeplication Status Across All Sites API in CNC Console
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-11465 Application Framework Change

Parent topic: Feature Descriptions