2 Feature Descriptions
This chapter provides a summary of new features and updates to the existing features for network functions released in Cloud Native Core release 3.25.2.1xx.0.
Note:
CCNC-XXXX is an internal identification number of the feature.2.1 Automated Testing Suite (ATS) Framework
Release 25.2.100
Oracle Communications Cloud Native Core, Automated Testing Suite (ATS)
Framework 25.2.100 includes the following enhancements:
- ATS API: This enhancement enables ATS to use tags and stages in the requests. For more information, see the "Starting Jobs" section in Oracle Communications Cloud Native Core Automated Testing Suite Guide.
- Parallel Test Execution: This enhancement enables ATS to run test cases of both new features and regression pipelines. For more information, see the "Merged Execution" section in Oracle Communications Cloud Native Core Automated Testing Suite Guide.
2.2 Binding Support Function (BSF)
Release 25.2.101
There are no new features or enhancements in this release.
Release 25.2.100
Oracle Communications Cloud Native Core, Binding Support Function (BSF) 25.2.100
includes the following enhancements:
- TLS 1.3 Support for Kubernetes API: BSF can be deployed in a Kubernetes cluster that supports TLS 1.3. For more information, see the "Installing BSF" section in Oracle Communications Cloud Native Core, Binding Support Function Installation, Upgrade, and Fault Recovery Guide.
- Support for Grafana 7.5.x: BSF supports Grafana version 7.5.x. For more information, see the "Software Requirements" section in Oracle Communications Cloud Native Core, Binding Support Function Installation, Upgrade, and Fault Recovery Guide.
- Disabling Audit on Controlled Shutdown: The controlled shutdown feature is enhanced with impact of disabling audit service during controlled shutdown. For more information see "Controlled Shutdown of an Instance" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.
- Rx enhancement to add custom AVP for direct lookup of N7 session: BSF supports to optimize the N7 session lookup for AAR-I messages in Rx call flows. BSF stores the cookie received in the binding registration request from Policy. Whenever BSF receives a AAR-I from an AF, it searches for the PCF identity of the Rx session and the cookie stored in the database. If the details are present, BSF shares it with Policy in a cookie along with the AAR-I request. For more information, see "Support for Optimizing N7 Session Lookup for AAR messages in Rx Call Flows" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.
- Burst rate limit modification and customization for WARN logs for All BSF services: In order to control the volume of logs, BSF allows to add a burst filter for logging against logs for all the microservices. The Burst filter provides a mechanism to control the rate at which LogEvents are processed by silently discarding events after the maximum limit has been reached. It enables to control the frequency and volume of warning messages generated. This ensures that excessive logging does not overwhelm the system or obscure critical information. For more information, see "Logging Support for Error Response" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.
- Performance Enhancement to Achieve 63K TPS: BSF now supports up to 63K TPS per BSF NF set in a three-site georedundant deployment for 32 million subscribers, 64 million bindings. Under normal conditions, each site handles 21K TPS, and during failure scenarios (loss of two of three sites), the remaining site supports 63K TPS. For more information, see the "BSF Call Model Deployed on a Three-site Setup with 63K TPS Traffic on One Site and ASM Enabled" section in Oracle Communications Cloud Native Core, Binding Support Function Benchmarking Guide.
The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.
Table 2-1 License names for feature mapping
| License Name | CCNC Number | Feature Name |
|---|---|---|
| Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual | CCNC-9144 | Support for TLS 1.3 on Internal API Communication |
| Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual | CCNC-10672 | Support for Grafana 7.5.x |
2.3 Cloud Native Core cnDBTier
Release 25.2.101
Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) 25.2.100 includes the following enhancement:
- Migration from SpringBoot to Micronaut:
cnDBTier supports Micronaut from 25.2.101 onwards. The URL for Prometheus scrape has changed from
/actuator/prometheusto/prometheus.
Release 25.2.100
Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) 25.2.100 includes the following enhancements:
-
Support for Automated Certificate Lifecycle Management: This feature enables automated TLS certificate lifecycle management for HTTPS, MySQL replication SQL pods and MySQL application SQL pods within the cnDBTier environment, ensuring secure and uninterrupted communication during certificate updates.
For more information on the Backup Status API, see the "Support for Automated Certificate Lifecycle Management" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
-
Support for Grafana 7.5.x and 9.5.x: This feature supports Grafana versions 7.5.x along with 9.5.x. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.
-
New Real Time Replication Status REST APIs Across All Sites: This feature enhancement provides the following new real time cnDBTier Replication Status APIs across all sites.
- http://base-uri/db-tier/replication/status/realtime
- http://base-uri/db-tier/replication/status/realtime/sitename/{siteName}
- http://base-uri/db-tier/replication/status/realtime/sitename/{siteName}/remotesitename/{remoteSiteName}
- http://base-uri/db-tier/replication/status/realtime/sitename/{siteName}/remotesitename/{remoteSiteName}/replgrourpid/{replGrourpId}
For more information on the Replication Status REST APIs, see the "cnDBTier APIs" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.
Table 2-2 License names for feature mapping
| License Name | CCNC Number | Feature Name |
|---|---|---|
| Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers | CCNC-8161 | Support for Automated Certificate Lifecycle Management |
| Oracle Communications Cloud Native Core, Unified Data Repository - 25K Active Subscribers Perpetual | CCNC-10676 | Support for Grafana 7.5.x and 9.5.x |
2.4 Cloud Native Configuration Console (CNC Console)
Release 25.2.100
Oracle Communications Cloud Native Configuration Console (CNC Console) 25.2.100 includes the following enhancements:
- Multiple Cluster Support for ASM Deployments: Console multiple cluster support for ASM deployments has now been enabled. The procedure to migrate from a single cluster, single instance deployment to a multiple cluster, multiple instance deployment has been documented. CNC Console ASM Helm charts have been included as part of the package. For more information, see Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide.
- TLS 1.3 Support for Kubernetes API : CNC Console can be deployed in a Kubernetes cluster that supports TLS 1.3. For more information, see Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide.
- CNC Console Installation and Upgrade Enhancements: CNC Console has introduced new Helm configuration options to enhance the installation and upgrade process. In cnDBTier georeplicated environment, all database schema creation now occurs upfront at the initial site, ensuring smoother replication and minimizing errors related to schema synchronization during deployment and upgrades. For more information, see Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide.
- Aligning MaxSurge and MaxUnavailable Parameter Values: CNC Console has
standardized the values of the
maxSurgeandmaxUnavailableparameters in the CNC Console Helm charts to control deployment behavior for various CNC Console microservices. This configuration optimizes resource usage by ensuring that no extra pods are created during updates, as additional resources do not contribute to service continuity. For more information, see Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide - Support for Grafana 7.5.x: CNC Console supports Grafana version 7.5.x. 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-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-9541 | Multiple Cluster Support for ASM Deployments |
| Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual | CCNC-9157 | TLS 1.3 Support for Kubernetes API |
| Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual | CCNC-11774 | CNC Console Installation and Upgrade Enhancements |
| Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual | CCNC-6007 | Aligning MaxSurge and MaxUnavailable Parameter Values |
| Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual | CCNC-10670 | Support for Grafana 7.5.x |
2.5 Cloud Native Environment (CNE)
Release 25.2.100
Oracle Communications Cloud Native Core, Cloud Native Environment (CNE)
25.2.100 includes the following enhancements:
- Secure DNS Zone Customization through CNLB: This feature enhances
the security and scalability of DNS requests by routing traffic based on domain zones,
such as OAM or Signaling. It isolates DNS traffic and forwards requests through Cloud
Native Load Balancers (CNLB) to external DNS servers, which are managed by the
customers.
For more information, see the "Secure DNS Zone Customization through CNLB" section in Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.
- Support for Grafana 7.5.x and 9.5.x: This feature supports Grafana versions 7.5.x along with 9.5.x. For more information, see the "Frequently Used Common Services" section in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
- Provision to Add Authentication to Container Registry: This
feature supports CNE container registry on Bastion hosts to add an authentication. Users
will be able to provide username and password at the time of installation of CNE. Values
are configured in the secrets.ini file which contains the sensitive information. Once
this feature is enabled user can login with the credentials to perform actions like
upload images (this is done automatically for CNE provisioned users). This feature is
optional, and will only work when username and password are provided in secrets.ini.
For more information, see the following sections in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
- Updating
cluster.tfvarsfor CNLB - Updating
cluster.tfvarsfor MetalLB - Environmental Variables
- Updating
- CNE support for CNLB nodes (OpenStack platform only): This feature
is applicable to CNLB only and can only be used when CNE is installed with the
cnlb_node_label option enabled. With this feature, users will be able to provision
special type of Kubernetes nodes "cnlb_nodes". Only these nodes will be configured to
run CNLB app pods. This feature is available on OpenStack platform only.
For more information, see "Limited Kubernetes Cluster Nodes for CNLB" section in Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.
- New Versions of Common Services: The following common services are
upgraded in this release:
- Helm - 3.18.2
- Kubernetes - 1.33.1
- containerd - 1.7.16
- Calico - 3.29.3
- MetalLB - 0.14.4
- Prometheus - 3.4.1
- OCI Grafana - 7.5.17
- Jaeger - 1.69.0
- Istio - 1.24.0
- Kyverno - 1.13.4
- cert-manager - 1.12.4
dependencies_25.2.100.tgzfile 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.
2.6 Oracle Communications Cloud Native Core, Certificate Management (OCCM)
Release 25.2.100
Oracle Communications Cloud Native Core, Certificate Management (OCCM) 25.1.200 includes the following enhancement:
- Certificate Screen Enhancement to Filter Certificates by Namespace Name: OCCM has introduced the ability to filter available certificates by the name of the namespace on the Certificates GUI. This value is taken from the namespace selected in the certificate output field. For more information, see "Managing Certificates" in Oracle Communications Cloud Native Core Certificate Management User Guide.
- Certificate Screen Enhancement to show Issuers in a Dropdown: OCCM has enhanced the certificates GUI to include a dropdown for the issuer field in certificate configuration. This enables users to select from a list of issuers instead of manually entering an issuer name. For more information, see "Managing Certificates" in Oracle Communications Cloud Native Core Certificate Management User Guide.
- Issuer and Certificate Screen Enhancement to show Namespaces in a Dropdown: OCCM has enhanced the issuers and certificates GUIs to include a dropdown for the namespace field in certificate configurations. This enables users to select from a list of namespaces instead of manually entering the namespace name. For more information, see "Managing Issuers" and "Managing Certificates" in Oracle Communications Cloud Native Core Certificate Management User Guide.
- Support for Grafana 7.5.x: OCCM now supports Grafana 7.5.x. For more information, see the "Additional Software Requirements" section in Oracle Communications Cloud Native Core Certificate Management 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, Certificate Management - 25K Active Subscribers | CCNC-9611 | Certificate Screen Enhancement to Filter Certificates by Namespace Name |
| Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers | CCNC-9609 | Certificate Screen Enhancement to show Issuers in a Dropdown |
| Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers | CCNC-11042 | Issuer and Certificate Screen Enhancement to show Namespaces in a Dropdown |
| Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers | CCNC-10678 | Support for Grafana 7.5.x |
2.7 Operations Services Overlay (OSO)
Release 25.2.101
Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.2.101 includes the following enhancement:
Support for new versions:
- Updated the version of oso_snapshot as 25.2.101.
- Updated the version of oso_alert_config as 25.2.101.
- Updated the version of oso_helm_test as 25.2.101.
For more information, see Oracle Communications Cloud Native Core, Operations Services Overlay Installation and Upgrade Guide.
Release 25.2.100
Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.2.100 includes the following enhancement:
Support for new versions:
- Updated the version of oso_snapshot as 25.2.100.
- Added the oso_alert_config version as 25.2.100.
For more information, see Oracle Communications Cloud Native Core, Operations Services Overlay Installation and Upgrade Guide.
2.8 Policy
Release 25.1.202
There are no new features or enhancements in this release.
Release 25.1.201
There are no new features or enhancements in this release.
Release 25.1.200
Oracle Communications Cloud Native Core, Converged Policy 25.1.200 includes the
following enhancements:
- Supports Reattempt after Back-off during N1N2 Communication: PCF supports multiple N1N2 Communication attempts after backoff that would help in successful delivery of URSP rules to UE. For more information, see the "Support Backoff during N1N2 Communication" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Support for ASM 1.21.6: Policy 25.1.200 supports Aspen Service Mesh (ASM) 1.21.6 version on Kubernetes 1.27 version from this release. For more information, see the "Configuring Policy to Support Aspen Service Mesh" section in Oracle Communications Cloud Native Core, Policy Installation, Upgrade, and Fault Recovery Guide.
- Support for Dual Stack: Using the dual stack mechanism, Policy communicates within services or deployments in a Kubernetes cluster using IPv4 or IPv6 or both simultaneously depending on the configured deployment mode. For more information about this feature, see the "Support for Dual Stack" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Support for NR vs EUTRA KPIs for N7 Interface: PCF application differentiate between NSA and SA call flows and provides KPI for N7 interface to differentiate between the NR and EUTRA radio access technology in the SM Service. The KPIs is visualized in Grafana dashboard. For more information, see the "Support for NR vs EUTRA KPIs for N7 Interface" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Pod protection by rate limiting at Ingress Gateway: Policy supports configuring Rate Limiting for Ingress Gateway service in order to provide pod protection by throttling inbound requests, that exceeds the configured rate. For more information, see "Pod Protection at Ingress Gateway" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Supports Traffic Detection on SMF-N7 and TDF using Sd Interface: PCF
supports the Sd interface on Session Management Function (SMF)-N7 that
enables it to communicate with the Traffic Detection Function (TDF). This
interface allows PCF to provide Application Detection and Control (ADC)
rules for traffic detection and enforcement at the TDF through Solicited
Application Reporting. For more information, see the "Supports Traffic
Detection on SMF-N7 and TDF using Sd Interface" section in Oracle Communications Cloud Native Core, Converged Policy User
Guide.
Important:
Custom support for traffic detection on SMF-N7 and TDF using the Sd interface is an experimental feature. It is subject to change and is not supported for production use (lab use only).
- Modifying PCF Capacity parameters Through CNC Console: This feature is updated to modify the capacity parameter of the PCF instance and Service instance in the NFProfile for PCF registration profile through CNC Console. For more information, see the "Integrating Policy with Different Network Functions" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Handling VoLTE Race Conditions Between AAR and STR Messages: Policy now handles concurrency or collisions between Authorization Authentication Request (AAR-I/AAR-U) and Session Termination Request (STR) messages. It also addresses race conditions arising from Update Notify triggers due to AAR-I/AAR-U and STR for removing PCC rules. For more information, see the "Handling Collision Between AAR and STR Messages During Update Notify Timeout" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Handling of Multiple N1 N2 Transfer Messages: If PCF receives more than one trigger while an N1N12 transfer is in progress and this feature is enabled, then it consolidates and stores the User Equipment Policy Set Identifiers (UPSIs) with UE Route Selection Policy (URSP) rules that needs to be transferred to UE. Once the UE notification is received for the in-progress N1N2 transfer, a final consolidation is performed. The consolidated UE policy actions are then sent to the UE in a single N1N2 transfer, assuming no fragmentation is required. Once the UE notification is received for the in-progress N1N2 transfer, final consolidation is performed and the consolidated UE policy actions are sent out to UE in a single (assuming no fragmentation is required) N1N2 transfer. For more information about this feature, see the "Handling of Multiple N1N2Transfer Messages" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Stale Binding Detection Audit, Report, and Recover: Service disruptions caused by network storms, system overload, database latency, or other events can impact signaling between Policy and the Binding Support Function (BSF), affecting session bindings. Policy validates binding association records in its database for associated PDU sessions and checks if the binding association exists in BSF. If the binding association is missing in BSF, Policy initiates binding association registration with BSF and restores the session. For more information, see the "Stale Binding Detection Audit, Report and Recover" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Support for Reduced Capability UEs in SM-Rx Flows: For voice and video calls by reduced capability devices on Voice over Long-Term Evolution (VoLTE) and Voice over New Radio (VoNR), Policy supports NR_REDCAP value for RAT Type over Rx interface. For more information, see the "Support for Handling Requests From Reduced Capability Devices" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
-
LDAP Timeout and Retry Mechanism: With this feature, Policy supports retry functionality towards external LDAP server. The operator must first enable the Retry Enabled flag to use this functionality. Then, the operator can configure the Max number of retries and Retries on errors/timeout to configure the multiple error codes including the error code for LDAP timeout (85). For more information about this feature, see the "LDAP Timeout and Retry Mechanism" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- PCF support to not send ASR while Notify-Update fails: This feature enables PCF to terminate a Policy Authorization/Rx session when it fails to update the required PCC (Policy and Charging Control) and session rules to the Session Management Function (SMF) for an Rx session of a PDU session. This lets the voice data packets or any other media type configured by user to be carried over default IMS QOS flow. For more information about this feature, see the "PCF support to not send ASR while Notify-Update fails" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Stale Requests Cleanup for Binding service: Policy supports identifying and removing stale requests from SM service or PCRF Core to Binding service. Binding service stops further processing of such stale requests and responses and sends a 504 (Gateway Timeout) error to SM service or PCRF Core. For more information, see the "Support for Stale Requests Cleanup" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Stale Requests Cleanup for Diameter Connector: Policy supports identifying and removing stale requests from Policy microservices such as SM service or PCRF Core to Diameter Connector. Diameter Connector stops further processing of such stale requests and responses and sends a 504 (Gateway Timeout) or 5454 error response SM service or PCRF Core. For more information, see the "Support for Stale Requests Cleanup" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Stale Requests Cleanup for User Service (CHF Connector or UDR Connector): Policy supports identifying and removing stale requests from PDS to User Service (UDR Connector or CHF Connector). User Service (UDR Connector or CHF Connector) stops further processing of such stale requests and responses and sends a 504 (Gateway Timeout response to PDS. For more information, see the "Support for Stale Requests Cleanup" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Stale Requests Cleanup for UE Policy service: Policy supports identifying and removing stale requests from Ingress Gateway, PDS, PRE, or Bulwark service to UE Policy service. UE Policy service stops further processing of such stale requests and responses and sends a 504 (Gateway Timeout) error to Ingress Gateway, PDS, PRE, or Bulwark service. For more information, see the "Support for Stale Requests Cleanup" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Congestion Control Resource Usage Calculation Using EMA Algorithm: The Congestion Control mechanism supports the Exponential Moving Average (EMA) algorithm for resource usage calculations. This algorithm calculates congestion resource usage by giving more weight to recent usage data, providing a more accurate representation of current resource utilization compared to a simple average across all data points. For more information, see the "Congestion Control Resource Usage Calculation Using EMA Algorithm" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Support for Pod Congestion Control: Starting with Release 25.1.200,
Policy now supports Pod Congestion Control across multiple services to
manage heavy incoming request traffic. This mechanism evaluates each
incoming request and decides whether to accept or reject it based on
predefined request priority and the current congestion level of the
service.
- User Service Pod Congestion Control: The User service supports Pod Congestion Control to manage high volumes of incoming requests. For more information, see the "User Service Pod Congestion Control" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Diameter Connector Pod Congestion Control: The Diameter Connector service supports Pod Congestion Control to manage high volumes of incoming requests. For more information, see the "Diameter Connector Pod Congestion Control" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Diameter Gateway Pod Congestion Control: The Diameter Gateway service supports Pod Congestion Control to manage high volumes of incoming requests. This feature has been updated to align with the common Congestion Control mechanism. Users must migrate data from the older configuration parameters to the current common Congestion Control feature. For more information about the data migration, see the "Diameter Pod Congestion Control" and "Congestion Control settings" sections in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- AM Service Pod Congestion Control: The AM service supports Pod Congestion Control to manage high volumes of incoming requests For more information, see the "AM Service Pod Congestion Control" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Notifier Service Pod Congestion Control: The Notifier service supports Pod Congestion Control to manage high volumes 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 the "Notifier Service Pod Congestion Control" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Single UE ID Implementation: Policy supports optimizing the query on PolicyDS database using configurable UE IDs. Also, Policy reports on the migration status of database records when the query type is switched based on UE IDs. For example, it reports the number of database records to be migrated when switching from Multi UE ID to Single UE ID. For more information, see "Optimizing PolicyDS Database Query With Configurable UE IDs" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Histogram Metrics for Signaling and DB Access Processing Latency in Binding Service: In order to provide sufficient insight into Binding service's performance for incoming requests, Policy includes histogram metrics for Binding service. These Histogram metrics enable Policy to observe data distribution by measuring the latency of multiple HTTP and database requests sent and received by Binding service. For more information, see the "Support for Signaling and DB Access Processing Latency Histogram Metrics" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Handling DB cluster disconnect: PCF Cluster DB State API is integrated with CNC Console for Policy, which enables to view the PCF cluster database state on cnDBTier database. This API displays the realtime status of the cluster state and NF database functional state in the cnDBTier database cluster. For more information, see the "Support for cnDBTier APIs in CNC Console" section in Oracle Communications Cloud Native Core, Converged Policy User Guide.
- Enhanced Logging Support for Error Responses: Policy has been enhanced to support verbose logging for microservices involved in SM call flows (create, update, delete, and notify) at their default log level (WARN) to provide sufficient visibility into issues within or across the external facing interfaces of the microservices. For more information about this feature, see the "Logging Support for Error Response" 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.
| License Name | CCNC Number | Feature Name |
|---|---|---|
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-9713 | Supports Reattempt after Back-off during N1N2 Communication |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-9615 | Support for ASM 1.21.6 |
| Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual | CCNC-9392 and CCNC-4995 | Support for Dual Stack |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-9173 | Support for NR vs EUTRA KPIs for N7 Interface |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-9108 | Pod protection by rate limiting at Ingress Gateway |
| Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual | CCNC-9088 | Supports Traffic Detection on SMF-N7 and TDF using Sd Interface |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-8499 | Integrating Policy with Different Network Functions |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-8399 | VoLTE Race Condition - Handling collision between AAR-STR, with UpdateNotify time out |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-8719 | PCF support to not send ASR while Notify-Update fails |
| Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual | CCNC-6293 | LDAP Timeout and Retry Mechanism |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers | CCNC-8304 | Handling of Multiple N1 N2 Transfer Messages |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers | CCNC-8725 | PCF and BSF stale Binding Detection AUDIT and Report and Recover |
2.9 Service Communication Proxy (SCP)
Release 25.2.102
There are no new features or enhancements in this release.
Release 25.2.101
There are no new features or enhancements in this release.
Release 25.2.100
Oracle Communications Cloud Native Core, Service Communication Proxy (SCP)
25.2.100 includes the following enhancements:
- LCM Automation: The Lifecycle Management (LCM) Automation feature optimizes deployment and upgrade processes of SCP by automating service account creation. This enhancement allows you to automatically create user-defined service accounts without any manual intervention. For more information, see the "LCM Automation" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
- TLS 1.3 Support for Kubernetes API: SCP can be deployed in a Kubernetes cluster that supports TLS 1.3. For more information, see the "TLS 1.3 Support for Kubernetes API" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
- Support for Grafana 7.5.x: SCP supports Grafana 7.5.x. For more information, see the "Software Requirements" section in Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide.
- Support for Sender NF Type based Routing Option Selection: SCP enhances
its routing options configuration to configure
senderNFTypeso that routing options selection criteria can also consider sender NF Type for selecting a routing option. In addition, SCP enhances its logic to identify notification sender to consider sender NF type in routing options selection criteria. For more information, see the "Support for Sender NF Type based Routing Option Selection" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. - Support for 1200 NF Profiles: SCP is enhanced to support 1200 NF profiles with a single Notification pod instance. For more information, see "SCP Services", "Upgrade", and "ASM Sidecar" sections in Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide.
The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.
Table 2-5 License names for feature mapping
| License Name | CCNC Number | Feature Name |
|---|---|---|
| Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual | CCNC-10664 | Support for Grafana 7.5.x |
| Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual | CCNC-9147 | TLS 1.3 Support for Kubernetes API |
| Oracle Communications Cloud Native Core, Automated Lifecycle Management - 25K Active Subscribers | CCNC-8293 | LCM Automation |
| Oracle Communications Cloud Native Core, Advanced Routing – 25K Active Subscribers Perpetual | CCNC-4404 and CCNC-5933 | Routing Options Enhancement for Notification Messages |
| Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual | CCNC-11246 | Support for 1200 NF Profiles |
2.10 Security Edge Protection Proxy (SEPP)
Release 25.2.100
Oracle Communications Cloud Native Core, Security Edge Protection Proxy (SEPP)
25.2.100 includes the following enhancements:
- NRF Selection Mechanisms Using nrf client: This feature allows the
SEPP to dynamically select NRF instances based on real-time availability and site
redundancy through DNS SRV configurations. In addition to the static configurations by
operators, the SEPP can now resolve NRFs using DNS SRV based Fully Qualified Domain
Names (FQDNs). The SEPP is configured with a primary NRF and multiple fallback NRFs,
which take over if the primary NRF becomes unreachable.
The nrf client uses the Alternate Route Service, which helps the SEPP find and select different Network Repository Functions (NRFs) by using DNS SRV-based lookups. This service allows the SEPP to translate Fully Qualified Domain Names (FQDNs) or virtual FQDNs into alternate NRF addresses. This setup enables the SEPP to prioritize and adjust connections to different NRFs based on specific service needs. For more information, see the "NRF Selection Mechanisms Using nrf client" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide and "Customizable Parameters" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.
- Integrating SEPP with 5G Network Intelligence Fabric (5G NIF): To route traffic to a Network Function, SEPP has traditionally relied on configurations or destination headers found in incoming SBI requests. For integration with the customized 5G Network Intelligence Fabric (5GNIF), SEPP must now discover this custom NF through the NRF, which holds this information. Once discovered, SEPP uses all existing routing mechanisms (such as alternate routing) to direct traffic to the identified 5GNIF instance. Additionally, SEPP is required to send copies of error messages, triggered by countermeasures or failed checks, to the 5GNIF for analytic purposes. For more information, see the "Integrating SEPP with 5G Network Intelligence Fabric (5G NIF)" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide and the "Customizable Parameters" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.
- TLS 1.3 Support for Kubernetes API: SEPP can be deployed in a Kubernetes cluster that supports TLS 1.3. For more information, see the "TLSv1.3 Support for Kubernetes API Server Communication" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.
- Support for Grafana 7.5.x: SEPP supports Grafana 7.5.x. For more information, see the "Software Requirements" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.
The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.
Table 2-6 License names for feature mapping
| License Name | CCNC Number | Feature Name |
|---|---|---|
| Oracle Communications Cloud Native Core, Advanced Routing – 25K Active Subscribers Perpetual | CCNC-8037 | Integrating SEPP with 5G Network Intelligence Fabric (5G NIF) |
| Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual | CCNC-10188 | NRF Selection Mechanisms Using nrf client |
| Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual | CCNC-9149 | TLS 1.3 Support for Kubernetes API Server Communication |
| Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual | CCNC-10674 | Support for Grafana 7.5.x |
2.11 Unified Data Repository (UDR)
Release 25.2.100
Oracle Communications Cloud Native Core, Unified Data Repository (UDR) 25.2.100
includes the following enhancements:
- Support for EIR International Mobile Equipment Identity Software Version (IMEISV) Fallback: The IMEISV Fallback feature enables the EIR to use the International Mobile Equipment Identity (IMEI) for validation and authorization purposes when the IMEISV is not provisioned for a device in the database. This feature ensures continuity of service, improving reliability, and user experience. For more information, see the "Support for EIR International Mobile Equipment Identity Software Version (IMEISV) Fallback" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
- Diameter Gateway Enhancement: This feature improves
Diameter Gateway protocol message handling and enables seamless
interoperability between 4G and 5G networks. This enhancement includes
optimized message routing and improved message delivery across multiple
sites. The following Diameter Gateway enhancements are introduced:
- Support for Outgoing Messages through Diameter Signaling Router (DSR) or Proxy in SH interface: The Diameter Gateway now supports outgoing messages, such as Push Notification Request (PNR) when a DSR or proxy is present between the Policy and Charging Rules Function (PCRF) peer and cnUDR.
- Support for Push Notification Request (PNR) Message Routing in Multiple Site
Deployments: This enhancement enables PNR message routing in
multiple site deployments when the direct connection to the peer is
unavailable. For example, if the connection between Site 1 and the
PCRF peer is unavailable, the message is automatically routed using
Site 2. This functionality is now implemented in cnUDR to prevent
message loss and ensure reliable communication across distributed
environment.
For more information, see the "Diameter Gateway Enhancement" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
- TLS 1.3 Support for Kubernetes API: UDR can be deployed in a Kubernetes cluster that supports TLS 1.3. For more information, see the "TLS 1.3 Support for Kubernetes API" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
- Support for Grafana 7.5.x Version: UDR supports Grafana 7.5.x version. For more information, see the "Software Requirements" section in Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.
The following table lists the license names for feature mapping. For additional licensing information, see Oracle Communications Cloud Native Core Licensing Information User Manual.
Table 2-7 License names for feature mapping
| License Name | CCNC Number | Feature Name |
|---|---|---|
| Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual | CCNC-10666 | Support for Grafana 7.5.x Version |
| Oracle Communications Cloud Native Core, 5G Equipment Identity Register - 25K Active Subscribers Perpetual | CCNC-10323 | Support for EIR International Mobile Equipment Identity Software Version (IMEISV) Fallback |
| Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual | CCNC-9995 | SLF Security Type-B Audit Compliance |
| Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual | CCNC-9511 | SLF Capacity and Performance validation for EOY25 forecast - 64M Sub with 67K TPS per segment (3 sites) |
| Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual | CCNC-9161 | TLSv1.3 Support for Kubernetes API Server Communication |
| Oracle Communications Cloud Native Core, Unified Data Repository - 25K Active Subscribers Perpetual | CCNC-8432 | Diameter Gateway Enhancement |