2 Feature Descriptions

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

Note:

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

2.1 Automated Testing Suite (ATS) Framework

Release 25.1.200

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

  • ATS Helm Enhancements: This enhancement automates preinstallation and postinstallation steps of ATS deployment by eliminating the manual method.

  • Trace Validation Enhancements: The trace validation framework has been enhanced to incorporate configurable retry mechanisms, support duration validation for checking the execution time of microservices, and apply filters to any microservice within a sequence.
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 CSloud Native Core, Automated Test Tools and Scripts Suite - Node Perpetual CCNC-9803 ATS Helm Enhancements
Oracle Communications Cloud Native Core, Automated Test Tools and Scripts Suite - Node Perpetual CCNC-9801 Trace Validation Enhancements

2.2 Binding Support Function (BSF)

Release 26.1.201

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

Support for Diameter Message Retry: This enhancement extends Diameter Message Retry support for Rx-STR, Rx-RAR, and Rx-ASR messages in addition to the existing retry support for Rx-AAR. BSF can retry failed Diameter messages to alternate PCF or P-CSCF (AF) peers, or through alternate FQDN (DRA) peers, based on configurable error handling policies, retry counts, peer cycle back settings, and error originator conditions. The feature uses the Error Mapping Framework and enhanced Diameter Routing Table support with multiple server identifiers to determine alternate peer selection and retry behavior.

Configuration Status: Disabled by default.

For more information, see Diameter Session Retry in Oracle Communications Cloud Native Core, Binding Support Function User Guide.

Support for Stale Session Audit Retry: This enhancement enables BSF to retry stale session audits within the same audit cycle. When audit requests fail due to temporary errors or 404 responses, BSF can retry requests to an alternate PCF through an alternate SCP, using retry profiles and alternate-routing capabilities. It discovers the alternate PCF from NRF instances via the NF Discovery service.

Configuration Status: Disabled by default.

For more information, see Handling Stale Session in BSF in Oracle Communications Cloud Native Core, Binding Support Function User Guide.

Optimizing Lookup in BSF Management Service Database: This feature enables BSF to optimize storage and discovery lookup of PCF binding records. BSF stores new bindings in the pcf_binding_v2 table with VARCHAR-based binding data and uses dedicated IPv4, IPv6, and MAC address lookup tables. It falls back to legacy index-based lookup when necessary. Existing records are migrated lazily during Audit processing, allowing legacy and new records to coexist during migration.

Configuration Status: Enabled for a fresh installation; disabled after an upgrade.

For more information, see Optimizing Lookup in BSF Management Service Database in Oracle Communications Cloud Native Core, Binding Support Function User Guide.

Diameter Gateway Connection Repaving: This feature enables BSF to rebalance Diameter connections across Diameter Gateway pods when their distribution becomes uneven due to restarts, failovers, scaling, or network events. BSF performs controlled, staggered disconnections of existing external Diameter connections so that peers reconnect through the Layer-4 load balancer and are redistributed without restarting services or causing a complete outage.

Configuration Status: Disabled by default.

For more information, see Diameter Gateway Connection Repaving in Oracle Communications Cloud Native Core, Binding Support Function User Guide.

Stale Binding Manual Detection Tool Enhancements - pcf_binding_v2: Service disruption due to network storm, system overload, database latency, and other events can impact signaling between Policy and BSF. When binding is lost and Policy sessions are in a hung state, there is no way of knowing which sessions lost or never received the binding. As a result, no action can be taken to solve this issue. The Binding Detection Tool can be run manually to query the sessions in both Policy and BSF that were created in a specific time frame. The query results can be used to identify the stale sessions that impact the Policy sessions when binding is lost.

Configuration Status: Enabled by default.

For more information, see Oracle Communications Cloud Native Core, Binding Detection Tool User Guide.

Support for cnDBTier IP Family Reference and Gracefully Stop and Start Georeplication 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.

Configuration Status: Enabled by default.

For more information, see Support for cnDBTier APIs in CNC Console 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-2 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-10722 Support for Diameter Message Retry
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-10385 Support for Stale Session Audit Retry
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-13541 Optimizing Lookup in BSF Management Service Database
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-11391 Diameter Gateway Connection Repaving
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-13539 Stale Binding Manual Detection Tool enhancements - pcf_binding_v2
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-12506 Support for cnDBTier IP Family Reference and Gracefully Stop and Start Georeplication APIs in CNC Console

2.3 Cloud Native Environment (CNE)

Release 25.1.201

There are no new features or enhancements in this release.

Release 25.1.200

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 25.1.200 includes the following enhancements:
  • Support for Sensitive data storage: When installing or upgrading Cloud Native Environment (CNE), you must provide a secrets.ini file containing values for variables classified as sensitive.
    For more information, see the following sections in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide:
    • Deploying CNE Cluster in OpenStack Environment
    • Predeployment Configuration for VMware
    • Configuring secrets.ini and occne.ini files
    • Environmental Variables
  • Customizing GRUB password: GRUB password can be customized to do maintenance tasks on the boot process for every host of a cluster. Add or modify the occne_grub_password variable in the hosts.ini or occne.ini file according to your cluster. This is a mandatory parameter required to be configured during install or upgrade.
    Set the value of the occne_grub_password variable to the required password. Before setting a password, ensure that the password you choose comply to the following conditions:
    • Contain at least eight characters.
    • Contain uppercase and lowercase characters.
    • Contain at least special character except single and double quotes, ", ', \, %, &, and $.
    • Contain at least two digits.

    For more information, see the "Configuring GRUB Password" 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.17.1
    • Kubernetes - 1.32.0
    • containerd - 1.7.24
    • Calico - 3.29.1
    • MetalLB - 0.14.4
    • Prometheus - 3.2.0
    • Grafana - 9.5.3
    • Jaeger - 1.65.0
    • Istio - 1.18.2
    • Kyverno - 1.13.4
    • cert-manager - 1.12.4
    To get the complete list of third-party services and their versions, refer to the dependencies_25.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.

Operations Services Overlay (OSO)

Release 25.1.201

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

There are no new features or enhancements in this release.

Release 25.1.200

Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.1.200 includes the following enhancement:
  • Alert Automation: With this feature, OSO supports other NFs to install and update alert configurations using the Helm chart. For more information about the feature, see the "Alert Automation" section in Oracle Communications Cloud Native Core, Operations Services Overlay User Guide.

    For detailed instructions on configuring this feature, see the "Automated Configuration of NF Alerts" section in Oracle Communications Cloud Native Core, Operations Services Overlay Installation and Upgrade 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, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-9086 Alert Automation

2.4 Cloud Native Core cnDBTier

Release 25.1.201-6

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

Release 25.1.201-5

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

Release 25.1.201-4

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

Release 25.1.201-3

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

Release 25.1.201-2

Migration from SpringBoot to Micronaut:

cnDBTier supports Micronaut from 25.1.201-2 onwards. The URL for Prometheus scrape has changed from /actuator/prometheus to /prometheus.

Release 25.1.201-1

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

Release 25.1.201

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

Release 25.1.200

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

  • Support for cnDBTier Backup Status APIs in CNC Console: With this enhancement, cnDBTier NDB Backup status can be viewed on CNCC Console GUI. NF applications can check if the NDB cluster is performing a backup. This helps to prevent NF schema changes that may cause upgrade failures using the new screen. Additionally, a new API is added for this enhancement.

    For more information on the Backup Status API, see the "cnDBTier APIs" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.

  • cnDBTier Metrics reorganization: In the earlier implementation, metrics collection followed a centralized model where all metrics were gathered solely through the monitoring service. While functional, this approach led to performance bottlenecks. The monitoring service became heavily loaded, resulting in slow metrics retrieval and, at times, resource spillage in terms of CPU and memory consumption. To address these issues, the metrics collection process has been distributed. Wherever feasible, metrics are now offloaded to the respective microservices. This decentralization reduces the load on the central monitor service, significantly improving the efficiency and speed of metrics retrieval.

    As part of this new design, the infrastructure monitor component has been embedded as a permanent container within each relevant microservice. While this increases the overall resource footprint, it ensures a more scalable, responsive, and resilient monitoring framework.

    Note:

    With multiple distributed endpoints now serving metrics, Prometheus must be appropriately scaled/resourced to handle the increased load and maintain scraping efficiency.

    For more information on cnDBTier Metrics, see the "Metrics" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.

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

  • Support for HTTPS communication: The initial HTTPS implementation in cnDBTier lacked support for transitioning between HTTPS-disabled and HTTPS-enabled states. It also did not provide HTTPS functionality for CNLB. These limitations resulted in incomplete HTTPS support across different deployment scenarios. The current implementation addresses these limitations by providing comprehensive HTTPS support throughout cnDBTier. Enhancements include:
    • Seamless transition between HTTPS enabled and disabled states
    • Robust handling of HTTPS across all relevant components, including CNLB
    • Consistent and reliable secure communication in all configurations

    This update guarantees end-to-end HTTPS functionality, improving security and system consistency in various deployment scenarios. For more information about this feature enhancement, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native.

  • Support for Dual Stack: cnDBTier supports deployment on dual stack Kubernetes infrastructure, enabling communication over both IPv4 and IPv6. Using the dual stack mechanism, cnDBTier can establish and accept connections within pods and services using either IP family and interact seamlessly with external systems that support IPv4 and IPv6. In this setup, cnDBTier can use IPv4 or IPv6 for internal communication between its microservices, while external communication can be independently configured to use IP family. Additionally, the preferred IP family can be changed dynamically after deployment, providing enhanced flexibility in managing network configurations. For more information about this feature enhancement, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

  • cnDBTier Helm (MOP) Enhancements: Starting with version 25.1.200, cnDBTier supports the automated creation of service accounts, roles, and role bindings. While this functionality was available in older versions, the latest release introduces validation for manually created service accounts. Helm charts now verify whether a manually created service account has the required permissions.
    The configuration has also been restructured to support different service accounts, including:
    • Upgrade service account
    • Application service account
    • Multus service account

    For detailed configuration instructions, see Oracle Communications Cloud Native Core, cnDBTier 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-4 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual CCNC-9368 Support for ASM 1.21.6
Oracle Communications Cloud Native Core, Automated Lifecycle Management - 25K Active Subscribers CCNC-9100 cnDBTier Helm (MOP) Enhancements
Oracle Communications Cloud Native Core, Advance Networking - 25K Active Subscribers CCNC-8894 Support for Dual Stack

2.5 Cloud Native Configuration Console (CNC Console)

Release 25.1.204

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

Release 25.1.203

CNC Console 25.1.203 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts. For more information, see Critical Patch Updates, Security Alerts, and Bulletins.

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

Release 25.1.202

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

Release 25.1.201

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

Release 25.1.200

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

  • Lifecycle Management (LCM) Automation: Lifecycle Management (LCM) Automation optimizes the deployment and upgrade processes for CNC Console by reducing the steps required to initiate. The following automation enhancements are supported in this release:
    • Helm Enhancements for Service Account: An automated resource creation has been introduced to streamline Kubernetes resource management through Helm charts.
    • Helm Enhancements for NF Alert Configurations on OSO: CNC Console 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, the CNC Console performs Helm upgrades to apply or update the required alert rules. Both manual and automated configurations are supported.
    For more information, see Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide and Oracle Communications Cloud Native Configuration Console User Guide.
  • Support for ASM 1.21.6: CNC Console now supports Aspen Service Mesh (ASM) version 1.21.6. For more information, see Oracle Communications Cloud Native Configuration Console 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-5 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Automated Lifecycle Management - 25K Active Subscribers CCNC-9092 Lifecycle Management (LCM) Automation
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CNCC-8616 Support for ASM 1.21.6

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

Release 25.1.202

OCCM 25.1.202 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts. For more information, see Critical Patch Updates, Security Alerts, and Bulletins.

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

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

Release 25.1.201

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

Release 25.1.200

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

  • Updating Certificate Configurations: This feature enables updating essential fields in the certificate configuration. Based on changes to the end-entity certificate configuration, OCCM automatically recreates the certificate or applies updates during future renewals.

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

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CNCC-8148 Updating Certificate Configurations

2.7 Network Repository Function (NRF)

Release 25.1.206

NRF 25.1.206 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts. For more information, see Critical Patch Updates, Security Alerts, and Bulletins.

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

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

Release 25.1.205

NRF 25.1.205 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts. For more information, see Critical Patch Updates, Security Alerts, and Bulletins.

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

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

Release 25.1.204

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

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

Release 25.1.203

NRF 25.1.203 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts. For more information, see Critical Patch Updates, Security Alerts, and Bulletins.

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

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

Release 25.1.202

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

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

  • Support for 105.3K Ingress TPS with Management 2.1K, Discovery 103.26K TPS, SLF: 91.2K TPS, Notification 2990 TPS, and Forwarding 10% in Growth Mode: NRF supports processing up to 105.3K Transactions Per Second (TPS) in a growth environment configured with two sets, with each set accommodating upto 51.6K Discovery TPS and 45.2K SLF TPS utilization for enabling greater performance and scalability.

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

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

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

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

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

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

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

Release 25.1.200

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

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

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

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

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

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

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

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

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

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

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

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

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

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

2.8 Network Slice Selection Function (NSSF)

Release 25.1.202

NSSF 25.1.202 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts. For more information, see Critical Patch Updates, Security Alerts, and Bulletins.

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

Release 25.1.201

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

Release 25.1.200

Oracle Communications Cloud Native Core, Network Slice Selection Function (NSSF) 25.1.200 includes the following enhancements:
  • Support for Automated Certificate Lifecycle Management: NSSF now supports integration with Oracle Communications Cloud Native Core, Certificate Management (OCCM) to enable automated TLS certificate lifecycle management. This integration simplifies the secure communication setup by automating the issuance, renewal, and management of certificates used for establishing TLS connections between network functions (NFs).

    For more information, see the "Support for Automated Certificate Lifecycle Management" 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-7 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-3632 Support for Automated Certificate Lifecycle Management

2.9 OCI Adaptor

Release 25.1.200

Oracle Communications Cloud Native Core, OCI Adaptor 25.1.200 includes the following enhancement:
  • Uplifted the OCI Adaptor Components: The following OCI Adaptor components have been uplifted:
    • Management-agent is uplifted from 1.5.0 to 1.7.0.
    • Fluentd is uplifted from 1.5.0 to 1.6.0.
    • OTEL Collector is uplifted from 0.108.0 to 0.124.0.

2.10 Policy

Release 26.1.201

Oracle Communications Cloud Native Core, Converged Policy 26.1.201 includes the following enhancements:
  • Support to Write Remote Subscriber State Variables to Operator Specific Data (OSD): This feature enables Converged Policy to write values received from Online Charging System (OCS) provided counters into Operator Specific Data (OSD) in the UDR using Remote Subscriber State Variables. The values are written directly to operator specified paths within operator specific data. Remote subscriber state variables allow operators to synchronize session or charging state between policy engines and UDR, supporting use cases like OCS spending limits and dynamic policy enforcement.

    Configuration status: Disabled by default

    For more information, see "Support to Write Remote Subscriber State Variables to Operator Specific Data (OSD)" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Support for 3gpp-Sbi-NF-Peer-Info Header: This feature enables PCF to identify the source and destination Network Functions (NFs) or NF service instances in HTTP messages exchanged over Service Based Interfaces (SBIs). To indicate the sender and receiver of the HTTP message, all HTTP requests and HTTP responses must include the 3gpp-Sbi-NF-Peer-Info header with the source and destination of the corresponding HTTP request or response. The PCF must send the HTTP client and server peer identities in the 3gpp-Sbi-NF-Peer-Info custom HTTP header, as defined in 3GPP TS 29.500 Clause 5.2.3.2.

    Configuration status: Disabled by default

    For more information, see "Support for 3gpp-Sbi-NF-Peer-Info Header" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Optimize Database Lookup in SM Service: The Optimize Database Lookup in SM Service feature improves PCF capacity per instance by reducing the storage footprint, database load, database replication, and latency in the SM Service. These changes help reduce database read and write payload size, reduce replication overhead, and improve runtime performance.

    Configuration status: Enabled by default.

    For more information, see Optimize Database Lookup in SM Service section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • PCF Assume Positive Support for SM Service during Overload Condition: For SBI messages at Ingress Gateway, 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. To handle overload situation, Policy supports Reject action and Assume Positive support at SM service. During Reject action, messages are either rejected based on the priority of a message or 'n' percentage of messages are rejected. Where as Assume Positive action allows to suppress configured Egress Gateway flows towards producer like UDR and CHF for a request, but still resulting with a success responses.

    Configuration status: Disabled by default.

    For more information, see "PCF Assume Positive Support for SM Service during Overload Condition" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Supports pcfIpEndPoints in pcfBinding- BSF Registration: Supports pcfIpEndPoints in pcfBinding- BSF Registration request.

    Configuration status: Disabled by default.

    For more information, see "Supports pcfIpEndPoints in pcfBinding- BSF Registration" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Support for DNN Replacement in AM Policy: The existing Support for DNN replacement and SliceSupport feature in AM-PCF feature is enhanced with the following functionalities:
    • Sending multiple S-NSSAIs and DNNs in SMFSelectionData to AMF for an UE and its respective AM Policy Association.
    • Replacing S-NSSAI and DNN through Policy tables and Policy action by setting the S-NSSAI and corresponding DNN in the Policy written.
    • Overriding the DNN from VSA or adding DNN for S-NSSAI and the S-NSSAI in SMFSelectionData, if present or not present in VSA.
    • Updating the SMFSelectionData to AMF when receiving Update from AMF with change in allowed S-NSSAI.
    • Updating the SMFSelectionData to AMF when notification is received from UDR with change in VSA or any other attribute which evaluates by policy to update SMFSelectionData.
    • Providing unsupported DNN for S-NSSAI in SMFSelectionData
    • Handling error conditions when mandatory attributes are not received.
    Configuration status: Disabled by default.

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

  • SBI Message Priority (Requests towards NRF+ SM service Flow): PCF supports 3GPP-SBI-Message-Priority header in order to enable overload and congestion control through informed throttling decisions. Using 3GPP-SBI-Message-Priority header, PCF and the associated producers and consumers such as SCP and NRF can distinguish between high-priority and low-priority Service-Based Interface (SBI) messages.

    Configuration status: Disabled by default.

    For more information, see Support for SBI Message Priority Header section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • UE Policy Enhancements - Handling of AMF Updates with Change in AMF ID- Interaction with N1N2Communication Session Retry and backoff, with retry-after Timer: During mobility of the UEs, the UEs may have moved to different AMFs which can be in the same set, in a different AMF/NFSet, or the UE has moved to 4G/EPS. When PCF performs N1N2Transfer to send the UE Policy to UE, it is possible that due to mobility of UE, the UE was not reachable by AMF which had the N1N2Subscription. AMF pages the UE and if the UE is not reachable , it sends failure with "retryAfter" timer in the payload. PCF handles N1N2MessageTransferError by setting the cause attribute of the ProblemDetails structure to UE_NOT_REACHABLE (504 Gateway Timeout). retryAfter is used to stop sending the N1/N2 message until a timeout value, and to retry the N1/N2 message transfer request that was rejected after a timeout.

    Configuration status: Disabled by default.

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

  • Enhance support for Policy Authorization Service-QoS Monitoring(Create/Delete): PCF supports AF subscription to QoS Monitoring and, based on that subscription, notifies or reports to the AF about packet delay between the UPF and RAN. This report can be used to address use cases such as SLA compliance, monitoring real-time QoS, and adapting content delivery based on the network conditions.

    Configuration status: Disabled by default.

    For more information, see "Support for QoS Monitoring" section in Oracle Communications Cloud Native Core, Converged Policy User Guide

  • Enhanced logging (WARN level) for microservices involved in SM Call flows: Policy is enhanced to support logging for microservices involved in SM call flows, configurations targeting mainly LDAP, SOAP, Usage-Monitoring, and Diameter interfaces for asynchronous OCS Communications 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, Policy User Guide.

  • Remove index-based lookup for Binding service: In order to enhance the performance of the Binding database, Policy enables to replace index based queries with primary key or partition key based queries.

    Configuration status: Disabled by default.

    For more information, see the "Optimizing Lookup in Binding Service Database" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Security Context: The Security Context Feature improves the security posture of deployed workloads in policy by applying Kubernetes pod and container security context settings. A security context defines privilege and access control settings for a pod or container. These settings control how containers run, which user and group IDs are used, whether privilege escalation is allowed, which Linux capabilities are available, and whether the root filesystem is writable.

    Configuration status: Enabled by default.

    For more information, see the "Security Context" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

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

    Configuration status: Disabled by default.

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

  • Diameter Gateway Connection Repaving: With Diameter Gateway Connection Repaving feature provides a controlled mechanism to re-balance Diameter connections across the cluster without restarting services or causing a complete outage. It allows to force the disconnection of the existing external Diameter connections so that external peers reconnect through the Layer-4 load balancer and are re-distributed across available Diameter Gateway pods.

    Configuration status: Disabled by default.

    For more information, see "Diameter Gateway Connection Repaving" in the Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Optimizing Lookup in Binding Service Database: Policy supports to improve Binding Service database performance by replacing index-based lookups with more efficient lookup patterns using Primary key and Partition key lookups.

    Configuration status: Enabled by default.

    For more information, see "Optimizing Lookup in Binding Service Database " in the Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Stale Binding Manual Detection Tool enhancements - pcf_binding_v2: Service disruption due to network storm, system overload, database latency, and other events can impact signaling between Policy and BSF. When binding is lost and Policy sessions are in a hung state, there is no way of knowing which sessions lost or never received the binding. As a result, no action can be taken to solve this issue. The Binding Detection Tool can be run manually to query the sessions in both Policy and BSF that were created in a specific time frame. The query results can be used to identify the stale sessions that impact the Policy sessions when binding is lost.

    Configuration status: Enabled by default.

    For more information, see Oracle Communications Cloud Native Core, Binding Detection Tool 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.

  • Converged Policy Enhanced Blockly Utilities: Large policy configurations were difficult to search and navigate using standard Blockly features; therefore, Toolbox Search, Workspace Search, and Minimap plugins were added to provide faster access, better visibility, and efficient workspace navigation.​

    Configuration status: Enabled by default.

    For more information, see the "Blockly Plugin Integration for Policy Management Workspace in CM Service" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Handling of AnGWAddress in Traffic detection use case SMF-N7: When PCF receives SM Policy Context Create request from SMF with anGwIpv4Addr or anGwIpv6Addr (Access Network Gateway Address) populated, PCF forwards the same in AN-GW-Address AVP in an Sd TSR message to the TDF. The anGwAddr enables TDF to identify the control-plane IP address of the Access Network Gateway associated with the active TSR session

    Configuration status: Disabled by default.

    For more information, see the "Support of Traffic Detection on SMF-N7 and TDF using Sd Interface" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • cnPCF: SM-PCF Increase in Capacity > 55K TPS(upto 65K) per NFset: In order to enable greater performance and scalability, Policy supports processing up to 75K Transactions Per Second (TPS) for SM Call Flows on site1 in a growth environment configured with two sites in a GR setup.
  • cnPCF - AM-PCF Increase in Capacity >54K TPS(upto 65K) per NFset: In order to enable greater performance and scalability, Policy supports processing up to 75K Transactions Per Second (TPS) for AM and UE Call Flows on site1 in a growth environment configured with two sites in a GR setup.
  • Support for cnDBTier IP Family Reference and Gracefully Stop and Start Georeplication 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.

    Configuration status: Enabled by default.

    For more information, see the "Support for cnDBTier APIs in CNC Console" 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-8 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-11425 Optimize Database Lookup in SM Service
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-10649 Support for DNN Replacement in AM Policy

Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual

Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual

CCNC-4657

CCNC-11740

 Enhance support for Policy Authorization Service-QoS Monitoring(Create/Delete)
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-10598 UE Policy Enhancements - Handling of AMF Updates with Change in AMF ID- Interaction with N1N2Communication Session Retry and backoff, with retry-after Timer
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-8598 PCF support to display the text names of URSP and UPSI rules in logs
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-10019 PCF Assume Positive Support for SM Service during Overload Condition
Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual CCNC-5976 Support for 3gpp-Sbi-NF-Peer-Info Header
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-13549 Remove index-based lookup for Binding service
Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual CCNC-11008 Support to Write Remote Subscriber State Variables to Operator Specific Data (OSD)
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-1254 SBI Message Priority (Requests towards NRF+ SM service Flow)
Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual CCNC-1254 Handling of AnGWAddress in Traffic detection use case SMF-N7
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-9737 Enhanced logging (WARN level) for microservices involved in SM Call flows
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-11114 Supports pcfIpEndPoints in pcfBinding- BSF Registration
Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual CCNC-13547 Diameter Gateway Connection Repaving
Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual CCNC-11805 cnPCF - AM-PCF Increase in Capacity >54K TPS(upto 65K) per NFset -Part 1
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-13539 Stale Binding Manual Detection Tool enhancements - pcf_binding_v2
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-10021 Sponsored Data Connectivity Update Subscription Part 3/4 - CF - Performance and infodev support
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-11038 cnPCF: SM-PCF Increase in Capacity 65K to 75K TPS per NFset -Part 1/n -CF
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-11949 CnPCF - Disabling mTLS - (IntraDB pod communication - Option-1 - Remove ASM sidecars from DBTier pods)
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual - Security Context
Oracle Communications Cloud Native Core, Policy Control Function - per 25K Subscribers Perpetual CCNC-12506 Support for cnDBTier IP Family Reference and Gracefully Stop and Start Georeplication APIs in CNC Console

2.11 Service Communication Proxy (SCP)

Release 25.1.205

SCP 25.1.205 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts.

For more information, see Critical Patch Updates, Security Alerts, and Bulletins.

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

Release 25.1.204

SCP 25.1.204 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts.

For more information, see Critical Patch Updates, Security Alerts, and Bulletins.

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

Release 25.1.203

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

Release 25.1.202

SCP 25.1.202 is a Critical Patch Update. Critical Patch Updates provide security patches for supported Oracle on-premises products. They are available to customers with valid support contracts.

For more information, see Critical Patch Updates, Security Alerts, and Bulletins.

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

Release 25.1.201

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

Release 25.1.200

Oracle Communications Cloud Native Core, Service Communication Proxy (SCP) 25.1.200 includes the following enhancements:
  • Support for ASM 1.21.6: SCP supports Aspen Service Mesh (ASM) 1.21.6 from this release. For more information, see the "Configuring SCP to Support Aspen Service Mesh" section in Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide.
  • Support for Dual Stack: This enhancement introduces dual stack support for Aspen Service Mesh (ASM). For more information, see the "Support for Dual Stack" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Verbose Logging for SCP: This enhancement introduces verbose logging specifically for the SCP-Cache microservice within the data plane. For more information, see the "Verbose Logging for SCP" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Enhanced Notifications Handling: With the Enhanced Notifications Handling feature, SCP can alternate route notification requests even if the 3gpp-Sbi-Routing-Binding header does not contain the servName attribute. SCP obtains the target producer NF information from nfset and nfinst attributes of the notification request. In this case, SCP pegs the exact values of the producer NF type in ocscp_nf_type and ocscp_nf_service_type dimensions of the respective metrics. For more information, see the "Enhanced Notification Handling" and "Obtaining NF Information from Notification Requests" sections in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Application Framework Change: Spring Boot has been replaced with Micronaut as the framework for microservices. To facilitate internal communication between SCP microservices, the following services have been introduced:
    • <helm-release-name>-scp-worker-int: Handles internal Server-Sent Events (SSE) communications for SCP-Worker, specifically for requests initiated towards Network Repository Function (NRF) from SCP-nrfProxy and SCP-nrfProxy-oauth services for Model-D and OAuth.
    • Additional "-int" services: Manage all other internal SSE communications, except those handled by scp-worker-int, between corresponding non "-int" services. The following "-int" services are supported:
      • <helm-release-name>-scpc-alternate-resolution-int
      • <helm-release-name>-scpc-audit-int
      • <helm-release-name>-scpc-configuration-int
      • <helm-release-name>-scpc-notification-int
      <helm-release-name> will be prefixed in each service name. For example, if the Helm release name is ocscp, then the scpc-configuration-int microservice name will be "ocscp-scpc-configuration-int".
    This architecture ensures streamlined and efficient internal communication within the SCP microservices. You must exclude the service ports of these services while configuring ASM. For more information about service ports, see the "SCP Traffic IP Flow" section in Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide.

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

Table 2-9 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-9671 Application Framework Change
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-8832 Support for ASM 1.21.6
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-8122 Enhanced Notifications Handling
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-7610 Obtaining NF Information from Notification Requests
Oracle Communications Cloud Native Core, Advance Networking - 25K Active Subscribers CCNC-5190 Support for Dual Stack
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-5169 Verbose Logging for SCP
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-3627 Model-D Capacity Enhancement

2.12 Security Edge Protection Proxy (SEPP)

Release 25.1.204

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

Release 25.1.203

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

Release 25.1.202

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

Release 25.1.201

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

Release 25.1.200

Oracle Communications Cloud Native Core, Security Edge Protection Proxy (SEPP) 25.1.200 includes the following enhancements:
  • Cat-1 NRF Service API Query Parameters Validation:

    With this feature, SEPP supports filtering of request based on the specific NF Type combination.

    This feature leverages the requester-nf-type and target-nf-type details provided in the discovery request, allowing operators to configure and enforce fine-grained control over Cat-1 rules.

    Key benefits of the feature includes:
    • Controlled access: Restricts access to the nnrf-disc service based on NF types, blocking unauthorized requests.
    • Improved security: Blocks unapproved access, improves security and protects the system from unwanted or harmful interactions.
    • Targeted filtering: Enables operators to define rules based on NF types, providing precise control over which network functions can access the service.
    • Reduced risk: Acts as a firewall to reduce the chances of untrusted network functions connecting to important APIs, making the system safer.

      This feature enhances security by allowing only trusted network functions to access the NNRF-disc service.

      For more information, see the "Cat-1 NRF Service API Query Parameters Validation Feature" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide, Oracle Communications Cloud Native Core, Security Edge Protection Proxy REST Specification Guide, and Oracle Communications Cloud Native Core, Security Edge Protection Proxy Troubleshooting Guide.

  • LCI and OCI Headers in 5G Architecture: In the 5G architecture, frequent network overload due to substantial data exchanges between producer and consumer Network Functions (NFs) necessitates precise load balancing to prevent failures. Prompt communication of overload conditions from producer NFs to consumer NFs is essential for timely corrective actions. The LCI and OCI headers play a critical role by providing real-time insights into SEPP resources and facilitating efficient traffic management. These headers equip consumer NFs with critical load and overload information, optimizing traffic distribution and proactive measures during overload scenarios, ensuring a stable, high-performing 5G Core Network, even under heavy loads. For more information, see the "LCI and OCI Headers" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide and the "Customizable Parameters" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.
  • SEPP Dashboard Support for Detecting Vulnerable Messages:

    In earlier releases, SEPP metrics could not be filtered by the originating PLMN ID, making it difficult to segregate and identify the source of messages. This feature enhances the metrics by enabling segregation based on PLMN ID, thereby improving operational efficiency in tracking message origins.

    • CSEPP: The existing metric ocsepp_cn32f_requests_total has been enhanced to include source_plmn_id as a new dimension.
    • PSEPP: A new metric ocsepp_originating_network_request_success_total has been introduced, which includes peer_plmn as a dimension.
    For more information, see the "SEPP Dashboard Support for Detecting Vulnerable Messages" 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-10 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, 5G Signaling Firewall - 25K Active Subscribers Perpetua CCNC-6385 Cat-1 NRF Service API Query Parameters Validation
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-3460 LCI and OCI Headers
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CCNC-4307 SEPP Dashboard Support for Detecting Vulnerable Messages

2.13 Unified Data Repository (UDR)

Release 25.2.201

Oracle Communications Cloud Native Core, Unified Data Repository (UDR) 25.2.201 includes the following enhancements:
  • Support for Provisioning Logs: The Support for Provisioning Logs feature is enhanced to improve traceability and auditability in UDR. This enhancement introduces a ueIdentifier field in provisioning logs that associates each provisioning action with a specific subscriber identifier. In addition to this enhancement, the request field in each log entry is formatted as a single-line, properly escaped JSON string. Double quotes in the request are escaped, which allows for better compatibility with OpenSearch indexing and enables more robust search and filtering.

    Configuration Status: Disabled by default.

    For more information, see the "Support for Provisioning Logs" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.

  • EIR Export File Naming and Formatting: The EIR Export File Naming and Formatting feature provides flexibility when naming and formatting export files for subscriber data from the EIR database. With this feature, you can customize file names by setting a prefix, choosing a timestamp format, and adding a standardized header and footer to each file.

    Configuration Status: Enabled by default.

    For more information, see the "EIR Export File Naming and Formatting" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.

  • Cloud Service Archive (CSAR) Digital Signature: The CSAR Digital Signature feature digitally signs 5G CNC software packages to meet the requirements of the ETSI NFVSOL004 (V3.5.1) specification, Section 5.1, Option 1. This feature applies a cryptographic digital signature to each package to ensure authenticity and integrity during delivery and deployment. The digital signature verifies that the package has not been altered or corrupted by a third party at any stage, whether in transit or at rest, and helps maintain the integrity of 5G network functions throughout the deployment lifecycle.

    Configuration Status: Enabled by default.

    For more information, see the "Cloud Service Archive (CSAR) Digital Signature" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide and "Validate the Certificate Authority" section in Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.

  • Pod Protection for Backend Services: The Pod Protection for Backend Services feature enhances the resilience and reliability of UDR by introducing automated traffic management and rate limiting for backend service pods. With this feature, rate limiting mechanism is applied to backend 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: Enabled by default.

    For more information, see the "Pod Protection for Backend Services" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.

  • Four Site Georedundancy Support for SLF: This feature SLF supports georedundancy to ensure high availability and redundancy. It offers two-site, three-site, or four-site georedundancy to ensure service availability when one of the SLF site is down. When SLF is deployed as georedundant site, all sites operate in an active state, and the same data is available at all the sites.

    Configuration Status: Enabled by default.

    For more information, see the "Four Site Georedundancy Support for SLF" section in Oracle Communications Cloud Native Core, Unified Data Repository 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, Unified Data Repository 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, Subscriber Location Function - 25K Active Subscribers Perpetual CCNC-11750 Support for cnDBTier Georeplication Status Across All Sites APIs in CNC Console
Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual CCNC-11219 Four Site Georedundancy Support for SLF
Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual CCNC-10639 GSMA NESAS Product Assessment of 5G CNC - SPAD Support: UDR/SLF/EIR
Oracle Communications Cloud Native Core, Unified Data Repository - 25K Active Subscribers Perpetual CCNC-10582 cnUDR support 40M records in MySQL
Oracle Communications Cloud Native Core, 5G Equipment Identity Register - 25K Active Subscribers Perpetual CCNC-9537 EIR Export File Naming and Formatting
Oracle Communications Cloud Native Core, Unified Data Repository - 25K Active Subscribers Perpetual CCNC-9422 Support for Provisioning Logs
Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual CCNC-9396 SLF: Compatibility with Webscale 1.6 for step 2.1.2 (K8s 1.27 & ASM 1.14.x)
Oracle Communications Cloud Native Core, Automated Lifecycle Management - 25K Active Subscribers CCNC-4919 and CCNC-1198 Cloud Service Archive (CSAR) Digital Signature