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

2.1 Automated Testing Suite (ATS) Framework

Release 24.2.0

Oracle Communications Cloud Native Core, Automated Test Suite (ATS) framework 24.2.0 has been updated with the following enhancements:

  • ATS API Enhancement: With this enhancement, the Starting Jobs API can trigger builds that run all test cases and perform test cases based on specific features, scenarios, stages, groups, and tags. For more information, see "ATS API" in Oracle Communications Cloud Native Core, Automated Testing Suite Guide.

2.2 Binding Support Function (BSF)

Release 24.2.4

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

Release 24.2.3

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

Release 24.2.2

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

Release 24.2.1

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

Release 24.2.0

Oracle Communications Cloud Native Core, Binding Support Function (BSF) 24.2.0 has been updated with the following enhancements:

  • Enhancements to Error Response: The error responses used to earlier contain only the error description in the details field, which was insufficient to troubleshoot any error. Using the enhanced error response mechanism, BSF sends additional pieces of information such as server FQDN, NF service name, vendor name, and error ID, in the details field of the payload for the identification of the source of an error response. For more information, see "Error response enhancements" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.
  • Support for TLS 1.3: BSF supports TLS 1.3 for all functions and interfaces that are supported by TLS 1.2. With this feature, BSF supports the creation of TLS 1.3 and TLS 1.2 connections and mandatory ciphers and extensions. For more information, see "Support for TLS 1.3" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.
  • Alert for Stale Session Detection: New alerts are introduced in BSF 24.2.0 to support auditing of the stale sessions. For more information, see "BSF Alerts" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.
  • Validation Check for nfInstanceID: For fresh installation of BSF, nfInstanceId parameter in the ocbsf_custom_values_24.2.0.yaml file should be provided as UUID. During the upgrade, the original UUID or siteID used at the time of installation should be provided. The same global nfInstanceId should be used in the appProfiles as well. For more information,, see "Configuring Mandatory Parameters" section in Oracle Communications Cloud Native Core, Binding Support Function Installation, Upgrade, and Fault Recovery Guide.

BSF ATS 24.2.0 is updated with the following enhancement:

  • Support for Transport Layer Security: With the introduction of this feature, Jenkins servers have been upgraded to support HTTPS, ensuring a secure and encrypted connection when accessing the ATS dashboard. For more information, see "Deploy ATS with TLS Enabled" section in Oracle Communications Cloud Native Core, Automated Test Suite Guide.

2.3 Cloud Native Configuration Console (CNC Console)

Release 24.2.5

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

Release 24.2.4

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

Release 24.2.3

CNC Console 24.2.3 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.

Release 24.2.2

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

Release 24.2.1

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

Release 24.2.0

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

  • Support for TLS v1.3: Console supports TLS 1.3 for all consumer NFs, producer NFs, the Data Director, SBI Interfaces, and any interfaces that previously supported TLS 1.2. Console uses HTTPS with TLS encryption to establish secure connections with NFs. With this feature, Console supports creation of TLS v1.3 and TLS v1.2 connections and mandatory ciphers and extensions. For more information about this feature, see Oracle Communications Cloud Native Configuration Console User Guide.
  • One Manager CNC Console (M-CNCC) to manage NFs located in another M-CNCC Cluster: In a multicluster deployment, multiple M-CNCCs can exist, and NFs can be located in different M-CNCC clusters. This feature enables one M-CNCC to manage NFs located in another M-CNCC cluster.
  • Support for instance level access control: This feature enables CNC Console to enforce restrictions on users based on instances allocated to them. If users do not have any instance role assigned, they will not be able to access configuration of that instance. This restriction is in addition to the currently supported RBAC capabilities.
  • CNC Console integration with Common API Framework (CAPIF): CNC Console now supports CAPIF, allowing authentication and authorization of API and GUI requests, metrics, alerts, and KPIs. For more information, see the Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide and Oracle Communications Cloud Native Configuration Console User Guide.
  • Support for cnDBTier Geoereplication Recovery Procedures: Additional GUI screens have been enabled to perform cnDBTier Georeplication Recovery procedures on CNC Console GUI.
  • NF Versions Supported by CNC Console:
    • SCP 24.2.x
    • NRF 24.2.x
    • UDR 24.2.x
    • Policy 24.2.x
    • BSF 24.2.x
    • SEPP 24.2.x
    • NSSF 24.2.x
    • NEF 24.2.x
    • CAPIF 24.2.x
    • DD 24.2.x
    • NWDAF 24.2.x
    • OCCM 24.2.x

2.4 Cloud Native Core cnDBTier

Release 24.2.6

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

Release 24.2.5

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

Release 24.2.4

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

Release 24.2.3

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

Release 24.2.2

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

Release 24.2.1

Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) 24.2.1 includes the following enhancements:
  • cnDBTier Password Encryption: With this feature, cnDBTier provides an option to encrypt replication username and password stored in the database. This ensures that the passwords stored in the database are secure and are not exposed. When the password encryption feature is enabled, the replication username and password are encrypted throughout the life cycle of cnDBTier unless the feature is disabled. For more information about this feature, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

    Note:

    cnDBTier supports password encryption from 24.2.1 only. If you have enabled this feature (in the cutsom_values.yaml file) in the previous releases, cnDBTier doesn't support upgrade and rollback to 24.2.1. In such a case, disable password encryption in the previous release before performing an upgrade or rollback. For procedure to disable password encryption in the previous release, see the "Disabling Password Encryption" section in Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.
  • REST APIs to Perform Georeplication Recovery Using CNC Console: In this release, cnDBTier exposes the following REST APIs to CNC Console:
    • cnDBTier cluster details
    • Get failed cnDBTier clusters
    • Mark cnDBTier clusters as failed
    • Monitor georeplication recovery status
    • Start georeplication recovery

    CNC Console uses these REST APIs to integrate and facilitate users to perform and monitor georeplication recovery using CNC Console. For more information about the REST APIs and procedure to perform georeplication recovery using CNC Console, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide respectively.

  • Support for CNE Cloud Native Load Balancer (CNLB): With this release, cnDBTier supports network segregation using Cloud Native Load Balancer (CNLB) to effectively manage ingress and egress traffic flows. For more information about this feature, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.
  • Enhancement to Georeplication Recovery: With this enhancement, cnDBTier has improved the rate at which the backup files are transferred between sites during a georeplication recovery. This improvement is achieved by:
    • using Secure File Transfer Protocol (SFTP) instead of CURL to transfer backup files between sites.
    • configuring a separate parameter (numberofparallelbackuptransfer) to perform the parallel transfer of backups in the data nodes. For more information about this parameter, see the "Customizing cnDBTier" section in Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.
  • Support for New Versions of Software: Oracle MySQL Cluster Database version has been updated to 8.0.37.

2.5 Cloud Native Environment (CNE)

Release 24.2.6

New Versions of Common Services: The version of Ingress nginx is upgraded to 1.11.5.

To get the complete list of third-party services and their versions, refer to the dependencies_24.2.6.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.

Release 24.2.4

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

Release 24.2.3

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

Release 24.2.2

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

Release 24.2.1

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

New Versions of Common Services:

  • Rook - 1.15.2

To get the complete list of third-party services and their versions, refer to the dependencies_24.2.1.tgz file provided as part of the software delivery package.

Release 24.2.0

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

  • Cloud Native Load Balancer (CNLB): With this feature, CNE provides Cloud Native Load Balancer (CNLB), for managing ingress and egress network, as an alternate to the existing LBVM, lb-controller, and egress-controller solution. When this feature is enabled, CNE automatically uses CNLB to control ingress traffic. For managing the egress traffic, you must preconfigure the egress network details in the cnlb.ini file before installing CNE. This feature implements a least connection algorithm for IP Virtual Server (IPVS) based ingress distribution.

    For more information about enabling and configuring this feature, see Oracle Communications Cloud Native Core, Cloud Native Environment User Guide and Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.

    Considerations:
    • You can enable or disable this feature only during a fresh installation of CNE 24.2.0.
    • CNE continues to support the existing LBVM, lb-controller, and egress-controller solution for network segregation. If you are using the legacy solution in 24.1.x, you can upgrade to 24.2.0 without any issue. However, if you are freshly installing CNE 24.2.0, you must choose to enable either one of the solutions.

    Note:

    CNE 24.2.0 replaces Terraform with OpenTofu when you freshly install CNE with Cloud Native Load Balancer (CNLB). For vCNE instances deployed using Terraform, CNE 24.2.0 continues to use and support Terraform for upgrade and maintenance.
  • Support for Network Policies: With this feature, CNE provides the functionality to define network policies for common services. When network policies are defined on common service pods, the pods can only allow traffic based on the policies defined. This way, the common services are restricted to communicate to trusted sources only. You can enable or disable network policies at the time of installation or upgrade. Network policies are applicable only when CNE runs on LBVM, lb-controller, and egress-controller and not applicable if you are installing CNE with CNLB. For more information about this feature, see Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • New Versions of Common Services: The following common services are upgraded in this release:
    • Helm - 3.13.2
    • Kubernetes - 1.29.1
    • containerd - 1.7.13
    • Calico - 3.26.4
    • MetalLB - 0.14.4
    • Prometheus - 2.51.1
    • Grafana - 9.5.3
    • Jaeger - 1.52.0
    • Istio - 1.18.2
    • Kyverno - 1.9
    • cert-manager - 1.12.4
    To get the complete list of third-party services and their versions, refer to the dependencies_24.2.0.tgz file provided as part of the software delivery package.

OSO Release 24.2.5

Oracle Communications Operations Services Overlay 24.2.5 has been updated with the following enhancements:
  • Support for Time Series Database (TSDB) Snapshot: Prometheus uses Time Series Database (TSDB) to store the metrics. Along with metric storage, OSO allows the users to capture a snapshot at a specific point of time with the available data in the Prometheus data store. OSO allows to capture the snapshots without shutting down or disrupting the Prometheus instance. It is useful for taking backups, recovery, or even debugging purposes.

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

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

  • Support for new versions:
    • 24_2_common_pod:latest is replaced with 24_2_common_oso:24.2.5
    • 24_2_oso_snapshot:24.2.5
    For more information, see Oracle Communications Operations Services Overlay Installation and Upgrade Guide.

OSO Release 24.2.0

Oracle Communications Operations Services Overlay 24.2.0 has been updated with the following enhancements:

Support for new versions:
  • Prometheus is uplifted from version 2.50.1 to 2.52.0.
  • alertmanager is uplifted from version 0.26.0 to 0.27.0.
  • configmapreload is uplifted from version 0.12.0 to 0.13.0.
  • 24_1_common_pod is replaced with 24_2_common_pod.

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

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

Release 24.2.3

OCCM 24.2.3 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.

Release 24.2.2

OCCM 24.2.2 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.

Release 24.2.1

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

Release 24.2.0

Oracle Communications Cloud Native Core, Certificate Management (OCCM) 24.2.0 includes the following enhancements:
  • Support for Certificate Recreation: OCCM supports recreation of certificates using existing certificate configuration on the CNC Console GUI. The recreation is supported using the CMPv2 initialization request and response procedures.

    This feature does not support editing the certificate configuration.

2.7 Network Exposure Function (NEF)

Release 24.2.0

Oracle Communications Cloud Native Core, Network Exposure Function (NEF) 24.2.0 includes the following enhancements:

  • Deployment in OCI: Oracle Cloud Infrastructure (OCI) is a set of complementary cloud services that enable you to build and run a range of applications and services in a High Availability (HA) hosted environment. NEF can be installed or deployed into the OCI using the OCI Adaptor. OCI Adaptor provides a smooth integration of NEF observability and monitoring modules with OCI observability and management, enabling the users to have access of alerts, metrics, and KPIs on the OCI platform.

    For more information on deploying NEF in OCI, see Oracle Communications Cloud Native Core, Network Exposure Function User Guide, Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide, Oracle Communications Cloud Native Core, Network Exposure Function Troubleshooting Guide and Oracle Communications Cloud Native Core, OCI Adaptor Deployment Guide.

  • CAPIF Integration with the CNC Console: The integration of CAPIF with the CNC Console enables operator to configure and modify different services and features using the CNC Console. For more information, see the "Configuring Network Exposure Function using the CNC Console" section in Oracle Communications Cloud Native Core, Network Exposure Function User Guide and Oracle Communications Cloud Native Core, Network Exposure Function REST Specification Guide.
  • Support for CNC Top Level MIB in NEF: There are two MIB files which are used to generate the traps. These files are packaged and shared with the operator in order to fetch the traps in their environment. For more information, see the "Configuring Alert Manager for SNMP Notifier" section in Oracle Communications Cloud Native Core, Network Exposure Function User Guide.

2.8 Network Repository Function (NRF)

Release 24.2.5

NRF 24.2.5 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 24.2.4

NRF 24.2.4 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 Functions (NRF) 24.2.4 includes the following enhancements:
  • Egress Gateway Pod Throttling: With the implementation of this feature, each Egress Gateway pods monitors its incoming traffic and if the traffic exceeds the defined capacity, the excess traffic is not processed and gets rejected. This feature is applied at each pod and applicable to all the incoming requests irrespective of the message type.

    Note:

    This feature is enabled by default.

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

  • Metrics Enhancements:
    • Metric for NfProfile Size: This metric is introduced to identify the size of the registered NfProfiles.
    • Metric for NfDiscover response size: This metric is introduced to determine the size of the NfDiscover response.

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

Release 24.2.3

NRF 24.2.3 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 24.2.2

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

Release 24.2.1

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

  • DataSetId Enhancements: As per 3GPP TS 29.510 v17.7, NRF supports additional enumeration (ENUM) values within DataSetId enumeration. For more information, see the "DataSetId Enhancements" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide and NRF Compliance Matrix.
  • Retry Metrics for SLF Flow: The existing Subscriber Location Function feature is enhanced to track the number of SLF retries made by creating a metric, or updating an existing metric. For more information, see the "SLF Metrics" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

Release 24.2.0

Oracle Communications Cloud Native Core, Network Repository Functions (NRF) 24.2.0 includes the following enhancements:
  • Support for TLS 1.3: NRF supports TLS 1.3 for all Consumer NFs, Producer NFs, the Data Director, SBI Interfaces, and any interfaces that previously supported TLS 1.2. NRF uses HTTPS with TLS encryption to establish secure connections with NFs. With this feature, NRF supports creation of TLS v1.3 and TLS v1.2 connections and mandatory ciphers and extensions. For more information about the feature, see the "Support for TLS" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide and the "Ingress Gateway Microservice" and "Egress Gateway Microservice" sections in Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.
  • Error Log Messages Enhancements: NRF adds additional information to the existing “ERROR” log messages. This additional information can provide more details about the error which can help to identify the problem details, error generating entity, and subscriber information. For more information about the feature, see the "Error Log Messages Enhancements" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.
  • NFService Priority Update: NRF now updates the NFService level priority along with the NFProfile level priority while processing the discovery query. NRF updates the following:
    • NFProfile level priority considering the lowest NFProfile level priority of NFProfiles
    • NFService level priority considering the lowest NFService level priority of all NFServices

    For more information about this feature, see "NFService Priority Update" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Rerouting SLF Requests Using Alternate SCP and Alternate SLF: NRF allows you to configure maximum number of SLF attempts or an alternate SCP route to enhance the routing strategy and minimize the number of reroutes. When an error response is received from SLF, the subsequent reroutes to SLF can be performed using alternate SCP and SLF path. For more information about this feature, see the "Rerouting SLF Requests Using Alternate SCP and Alternate SLF" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.
  • Support for servingScope Attribute in NRF: As per 3GPP TS 29.510 specification, NRF supports the servingScope for NFProfiles and serving-scope for discovery query attribute. This attribute contains the list of geographical areas that the NF will serve to NRF. This attribute is used to efficiently manage the load distribution among all the producer NfInstances in a network.

    The serving scope is supported for the following service operations:

    • NFRegister
    • NFUpdate (Partial/Complete)
    • NFStatusSubscribe
    • NFDiscover

    For more information about this feature, see Oracle Communications Cloud Native Core, Network Repository Function Network Impact Report.

2.9 Network Slice Selection Function (NSSF)

Release 24.2.1

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

Release 24.2.0

Oracle Communications Cloud Native Core, Network Slice Selection Function (NSSF) 24.2.0 includes the following enhancements:
  • Auto-Population of Configuration Based on NSAvailability Update: This feature has been enhanced in this release by introducing a new set of system options that control its behavior. These options allow administrators to enable or disable the automatic configuration update feature. Additionally, the NSSF can now be configured to receive updates from all AMFs or only from a specified list of trusted AMFs. This flexibility provides granular control over the NSSF's behavior and ensures optimal network slice management. For more information, see "Auto-Population of Configuration Based on NSAvailability Update" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.
  • Enhanced "Update Service Operation" for NSSAI Availability Service of NSSF: With this enhancement, NSSF now validates NsAvailabilityData from AMFs against its configuration. Only authorized TAI-SNSSAI combinations matching both AMF and NSSF data are accepted, enhancing NSSF's control over processed network availability information. For more information, see "NSSAI Availability Service" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

2.10 OCI Adaptor

Release 24.2.1

OCI Adaptor 24.2.1 includes the following enhancement:
  • Uplifted the OCI Adapter Components: The following OCI Adaptor components are upgraded:
    • Management-agent is uplifted from 1.3.0 to 1.5.0.
    • Fluentd is uplifted from 1.4.1 to 1.5.0.
    • Metric-Server is uplifted from 0.6.4 to 0.7.2.
    • OTEL Collector is uplifted from 0.84.0 to 0.108.0.

Release 24.2.0

OCI Adaptor 24.2.0 includes the following enhancements:
  • Supports Configuring Scraping Interval for Application Metrics: OCI Adaptor allows you to configure scraping interval for application metrics. For more information, see the "Deploying OCI Adaptor" section in Oracle Communications Cloud Native Core, OCI Adaptor User Guide.
  • Supports creation of Compartment Admin using the terraforms: OCI Adaptor supports creation of Compartment Admin group in the OCI infrastructure using terraform script. For more information, see the "User Management Layer" section in Oracle Communications Cloud Native Core, OCI Deployment Guide.
  • Replaced Bastion Host VM with Bastion service: From this release, the Bastion Host VM is replaced with Bastion Service. This allows the users to connect with OKE cluster using CLI server. For more information, see the "Bastion Service" section in Oracle Communications Cloud Native Core, OCI Deployment Guide.
  • Supports Configuring App Dimension in metrics data: OCI Adaptor allows you to include app dimension to the metrics of CNC applications. For more information, see the "Deploying OCI Adaptor" section in Oracle Communications Cloud Native Core, OCI Adaptor User Guide.
  • Uplifted the OCI Adapter Components: The following OCI Adaptor components are upgraded:
    • Management-agent is uplifted from 1.0.0 to 1.3.0.
    • Fluentd is uplifted from 1.0.1 to 1.4.1.

2.11 Policy

Release 24.2.7

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

Release 24.2.6

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

Release 24.2.5

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

Release 24.2.4

Oracle Communications Cloud Native Core, Converged Policy 24.2.4 has been updated with the following enhancements:
  • Traffic Segregation: Policy supports end-to-end traffic segregation based on traffic types. This ensures that critical networks are not cross-connected or share the same routes, thereby preventing network congestion. For more information, see "Traffic Segregation" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • Message Feed for SBI Monitoring: In order to enable correlation of the internal and external (request/response) messages for all the transactions initiated by the producer and consumer NFs, Policy allows to copy the messages at Ingress and Egress Gateways. The analysis of these messages enable NFs to integrate with external 5G SBI monitoring system for call tracing/tracking and live debugging. For more information about this feature, see "Message Feed for SBI Monitoring" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

Release 24.2.3

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

Release 24.2.2

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

Release 24.2.1

Oracle Communications Cloud Native Core, Converged Policy 24.2.1 has been updated with the following enhancement:
  • Concurrency Handling at Bulwark Service to Reduce Processing Latency of Service Request: For concurrency handling of different service requests for the same key at the Policy microservice (SM service/PDS), Policy supports reducing the latency of processing different concurrent service requests by acquiring the lock from Bulwark service for failed requests earlier than the backoff timer, rather than waiting for backoff timer to expire. For more information, see "Concurrency Handling at Bulwark Service to Reduce Processing Latency of Service Request" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • Support for Prevention of Requests Accumulation at Undertow Worker Queue: This functionality helps in preventing accumulation of excessive requests at Undertow worker queue and it is supported by SM, PDS, Binding and Bulwark services. For more information, see "Support for Prevention of Requests Accumulation at Undertow Worker Queue" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

Release 24.2.0

Oracle Communications Cloud Native Core, Converged Policy 24.2.0 has been updated with the following enhancements:
  • Support for policyDecFailureReports Attribute: With this feature, PCF supports Policy Decision Error Handling for enabling the policyDecFailureReports attribute. For more information, see "Support for policyDecFailureReports Attribute" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • Enhancements to Error Response: Policy sends error responses to consumer NFs due to some exceptions, such as signaling, validations, and internal errors. These error responses have payloads containing the problem title, status, details, and cause of the error that are used to investigate the error. The details section is now enhanced with application error IDs. For more information about this feature, see "Error response enhancements" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • Enhancements to Concurrency Handling using Bulwark Service in PCRF: Policy uses the Bulwark service to handle the concurrent requests coming from other Policy services. In this release, Policy has been enhanced to support concurrency handling using bulwark service in PCRF for Rx messages. For more information, see "Support for Concurrency Handling using Bulwark Service in Policy" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • SM Service Pod Congestion Control: SM service supports Pod Congestion Control mechanism that helps to handle heavy traffic of incoming requests. It considers every incoming request and decides to either reject or accept it based on a defined request priority and the status of service congestion level. For more information, see "SM Service Pod Congestion Control" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • PDS Pod Congestion Control: PDS service supports Pod Congestion Control mechanism that helps to handle heavy traffic of incoming requests. It considers every incoming request and decides to either reject or accept it based on a defined request priority and the status of service congestion level. For more information, see "PDS Pod Congestion Control" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • Usage Monitoring Pod Congestion Control: Usage Monitoring service supports Pod Congestion Control mechanism that helps to handle heavy traffic of incoming requests. It considers every incoming request and decides to either reject or accept it based on a defined request priority and the status of service congestion level. For more information, see "Usage Monitoring Service Pod Congestion Control" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • Handling N28 and N36 Interfaces Context Information during Subscription Failures: With this feature, PCF supports the N28 and N36 context information such as subscription information, policy and charging related information to be stored in PDS database during subscription failures toward CHR or UDR. For more information, see "Handling N28 and N36 Interfaces Context Information during Subscription Failures" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • Support for Optimizing Database Encoding in PCRF Core: This feature will optimize encoding and decoding of the database fields of PCRF Cores services to reduce the size of data transferred during replication and improve the performance in the call flows. For more information, see "Support for Optimizing Database Encoding in PCRF Core" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

  • Validation Check for nfInstanceID: For fresh installation of Policy, nfInstanceId parameter in the occnp_custom_values_occnp_24.2.0.yaml file should be provided as UUID. During this upgrade, the original UUID or siteID used at time of installation should be provided. The same global nfInstanceId should be used in the appProfiles as well. For more information, see "Mandatory Configurations" section in Oracle Communications Cloud Native Core, Converged Policy Installation, Upgrade, and Fault Recovery Guide.

  • Support for Handling Reduced Capability Devices: Policy supports the handling of requests from reduced capability devices (RedCap) to support IoT ecosystem. Policy identifies the incoming request from the RedCap devices and interacts with PRE to make appropriate decisions for the reduced capability devices. For more information, see "Support for Handling Reduced Capability Devices" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • Support for End-to-End Log Identifier across Policy Services: This feature allows to use a unique identifier to every log message, which can be used to identify the set of logs belonging to a given session across all Policy services. For more information, see "Support for Unique Log Identifier Across Policy Services" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
  • PCRF Core GxSession Table Multichannel Replication Support: In order to overcome the replication limitations of the database, especially in a multisite environment, Policy supports slicing the GxSession database. With this database slicing, instead of the main database processing all the requests, some of the database operations are processed using sliced tables. For more information, see "Slicing in GxSession database for PCRF Core service" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.

2.12 Service Communication Proxy (SCP)

Release 24.2.5

SCP 24.2.5 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.

Release 24.2.4

SCP 24.2.4 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.

Release 24.2.3

SCP 24.2.3 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 24.2.2

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

Release 24.2.1

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

Support for 730K MPS: SCP supports traffic at the rate of 730K MPS. For more information, see "Model C - Testcase Scenario 6" in Oracle Communications Cloud Native Core, Service Communication Proxy Benchmarking Guide.

Release 24.2.0

Oracle Communications Cloud Native Core, Service Communication Proxy (SCP) 24.2.0 includes the following enhancements:
  • Support for Multiple 3gpp-Sbi-Binding Headers: With this enhancement, SCP supports multiple 3gpp-Sbi-Binding headers within a single Service-Based Interface (SBI) message, routing them as specified in 3GPP TS 29.500 without additional processing or interpretation. For more information, see "Support for Multiple 3gpp-Sbi-Binding Headers" in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Support for TLS 1.3: With this enhancement, SCP strengthens security by extending TLS 1.3 support to all SBI interfaces (consumer NFs, producer NF), the Data Director, and interfaces that previously supported TLS 1.2. SCP uses HTTPS with TLS encryption to establish secure connections with these components. For more information, see "Support for TLS 1.3" in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Georeplication Recovery API: With this enhancement, SCP can mark the disrupted cnDBTier cluster as failed, initiate georeplication recovery, and continuously monitor their status, ensuring seamless disaster recovery operations. For more information, see "Support for cnDBTier APIs in CNC Console" in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Verbose Logging Enhancement: This enhancement introduces verbose logging specifically for the SCPC-Notification microservice within the control plane. For more information, see "Verbose Logging for SCP" in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

2.13 Security Edge Protection Proxy (SEPP)

Release 24.2.5

SEPP 24.2.5 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 24.2.4

SEPP 24.2.4 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 24.2.3

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

Release 24.2.2

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

Release 24.2.1

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

Release 24.2.0

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

  • Support for Originating Network ID Header Validation, Insertion, and Transposition: This feature enables the insertion or transposition of either the 3gpp-Sbi-Originating-Network-Id header or the 3gpp-Sbi-Asserted-Plmn-Id header into SBI request messages. It is expected that the originator of a request can be easily identified, but there are some scenarios where the originating network information may not be conveyed in the SBI requests to the home network. In such scenarios, this feature infer the originating PLMN ID and populates the required header in the SBI request.

    The feature supports the following three functionalities:

    • Header Value Validation using Cat 2 Network ID Validation feature
    • Header Addition
    • Header Transposition

    For more information about the feature, see Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide, Oracle Communications Cloud Native Core, Security Edge Protection Proxy REST API Guide, and Oracle Communications Cloud Native Core, Security Edge Protection Proxy Troubleshooting Guide.

  • Supports Four-Site Georedundancy: Oracle Communications Cloud Native Core, Security Edge Protection Proxy (SEPP) now supports four-site georedundancy. SEPP offers a two, three, or four-sites georedundancy to ensure service availability when one of the SEPP sites is down. When SEPP is deployed as georedundant site, all the sites work in an active state and the same data is available at all the sites.

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

  • Support for Georeplication Recovery cnDBTier APIs in CNC Console: With this enhancement, Georeplication Recovery cnDBTier APIs are integrated into the CNC Console, and users can view specific cnDBTier statuses on the CNC Console.

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

  • Support for Common Service APIs in CNC Console: The configuration for Ingress Gateway and Egress Gateway APIs was earlier supported only using REST. With the implementation of this feature, SEPP now supports the configuration of Ingress Gateway and Egress Gateway APIs using the CNC Console.

    For more information about the feature, see the "Support for Common Service APIs in CNC Console" and "Configurations" sections in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

  • ATS APIs: The Application Programming Interface (API) feature provides APIs to perform routine ATS tasks as follows:
    • Start: To initiate one of the three test suites, such as Regression, New Features, or Performance.
    • Monitor: To obtain the progress of a test suite's execution.
    • Stop: To cancel an active test suite.
    • Get Artifacts: To retrieve the JUNIT format XML test result files for a completed test suite.

    For more information about the feature, see 'ATS Framework Features' section in Oracle Communications Cloud Native Core, Automated Testing Suite Guide.

2.14 Unified Data Repository (UDR)

Release 24.2.6

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

Release 24.2.5

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

Release 24.2.4

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

Release 24.2.3

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

Release 24.2.2

Oracle Communications Cloud Native Core, Unified Data Repository (UDR) 24.2.2 includes the following enhancements:
  • Support for Post Operation for an Existing Subscription: This feature enables UDR to support POST request that overwrites the existing subscription. For more information, see "Support for Post Operation for an Existing Subscription" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.

Release 24.2.1

Oracle Communications Cloud Native Core, Unified Data Repository (UDR) 24.2.1 includes the following enhancements:
  • Secure File Transfer Support for Subscriber Bulk Import Tool Enhancement: This feature is enhanced to support separate file paths for PDBI files and result log files. For more information, see "Secure File Transfer Support for Subscriber Bulk Import Tool Enhancement" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.

Release 24.2.0

Oracle Communications Cloud Native Core, Unified Data Repository (UDR) 24.2.0 includes the following enhancements:
  • Support for Automated PKI Integration: UDR supports automation of certificate lifecycle management in integration with Oracle Communications Certificate Manager (OCCM). This allows to automatically create, renew, and delete certificates for a given CA, with the possibility to track previously created certificates and renew/delete them when required. For more information about the feature, see "Support for Automated PKI Integration" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
  • Suppress Notification: This feature enables cnUDR to store the User-Agent header received in the POST request from cnPCRF in the subscription table. cnUDR compares the User-Agent header received during an update operation from cnPCRF with the stored User-Agent header. If the User-Agent header match, then the notification is suppressed. The notification is sent if the User-Agent headers do not match or if the there is no User-Agent header in the update request. For more information about the feature, see "Suppress Notification" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
  • Support for Common Service APIs in CNC Console: The configuration for common service APIs was earlier supported only using REST API. With the implementation of this feature, UDR now supports the configuration of Ingress Gateway and Egress Gateway parameters using the CNC Console. For more information about the feature, see "Support for Common Service APIs in CNC Console" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
  • Support for TLS v1.3: UDR supports TLS 1.3 for all Consumer NFs, Producer NFs, the Data Director, SBI Interfaces, and any interfaces that previously supported TLS 1.2. UDR uses HTTPS with TLS encryption to establish secure connections with NFs. With this feature, UDR supports creation of TLS v1.3 and TLS v1.2 connections and mandatory ciphers and extensions. For more information about the feature, see "Support for TLS" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
  • Error Logging Enhancement: With this feature, UDR sends additional information to the existing “ERROR” log messages to identify the cause of the issue and minimize the troubleshooting time. Additional attributes are added to the existing ERROR logs which get populated with appropriate values during failure scenarios. For more information about the feature, see "Error Logging Enhancement" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.