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.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.
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.100
Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) 25.2.100 includes the following enhancements:
-
Application Service Mesh (ASM) for External Communication: This feature enables secure external communication through ASM (Application Service Mesh) by selectively applying Istio sidecar injection only to pods where external communication is involved. By selectively enforcing ASM policies, cnDBTier ensures the security and compliance of its external interfaces, while preserving high performance and simplifying manageability within the cnDBTier ecosystem.
For more information, see the "Application Service Mesh (ASM) for External Communication" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
-
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-8162 | Application Service Mesh (ASM) for External Communication |
| Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers | CCNC-8478 | 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.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.2.100
Oracle Communications Cloud Native Core, Converged Policy 25.2.100 includes the
following enhancements:
- Integration for Traffic Prioritization for NRF-Client and Egress Gateway on Policy: This feature provides the configurations to enable or disable both Traffic Prioritization for Egress-gateway and NRF-Client in Policy to support pod protection by throttling inbound requests if they are above configured rate. For more information, see the "NRF Client Configuration" section in Oracle Communications Cloud Native Core, Policy Installation, Upgrade, and Fault Recovery Guide.
- TLS 1.3 Support for Kubernetes API: Policy can be deployed in a Kubernetes cluster that supports TLS 1.3. For more information, see the "Installing Policy" section in Oracle Communications Cloud Native Core, Policy Installation, Upgrade, and Fault Recovery Guide.
- Support for Grafana 7.5.x: Policy supports Grafana version 7.5.x. For more information, see the "Software Requirements" section in Oracle Communications Cloud Native Core, Policy Installation, Upgrade, and Fault Recovery Guide.
- Support for Immediate Report Handling: Immediate Report Handling sends urgent notifications directly to the subscribed system as soon as a relevant change is detected. There is no need to wait for next polling cycle or batch update. This ensures the PCF receives up-to-date information in real-time, improving network efficiency and user experience. For more information see "Support for Immediate Report Handling for AM-Data and UE-Policy-Set on N36 Interface" section in Oracle Communications Cloud Native Core, Policy User Guide.
- Conflict Resolution for URSP Rules N1N2 transfer to UE: The feature integrates a conflict resolution mechanism into the Policy Control Function (PCF) to analyze and rectify UPSI/URSP rule conflicts in UE Policy actions obtained from PRE during policy evaluation. This process, guided by the selected conflict resolution strategy, ensures consistent policy actions and addresses discrepancies at the evaluation stage. For more information see "Conflict Resolution for URSP Rules N1N2 transfer to UE" section in Oracle Communications Cloud Native Core, Policy User 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, Policy User Guide.
- Enhancements to PRE metrics: Policy is enhanced with addition of "occnp_policy_project_state_change_total" and "occnp_policy_project_current_state" PRE metrics. For more information see "PRE Metrics" section in Oracle Communications Cloud Native Core, Policy User Guide.
- maxSurge and maxUnavailable Configuration in all Policy Services: Policy
allows to optimize management of Pods using
maxSurgeandmaxUnavailableparameters under the rollingUpdate and pdb categories incustom-values.yamlfile. For more information see the "Support for Optimized POD Management Using maxSurge and maxUnavailable During Policy Upgrade" section in Oracle Communications Cloud Native Core, Policy User Guide. - Optimizing N7 Session Lookup for AAR messages in Rx Call flow: Policy
supports to optimize the N7 session lookup for AAR-I messages in Rx call
flows. Whenever SM service receives a Create request for an Rx session over
N7 interface, if this feature is enabled, during binding registration, SM
service sends the session details such as
SmPolicyAssociationIdandcontextOwner (PCF-SM)in a cookieocnf-service-cookieto BSF. BSF stores the details sent in the cookie in BSF Management service database. Whenever Policy receives AAR-I request from BSF, the AAR-I request from BSF includes aOCNF-SERVICE-COOKIECustom AVP that contains the Rx session details such as session owner and the session identifier such asSmPolicyAssociationId(Primary Key). If the cookie-owner isPCF-SM, Diameter Gateway skips calling the Binding service for primary key lookup. It processes the details inOCNF-SERVICE-COOKIECustom AVP and decides whether to route the request to PCRF Core or for Diameter Connector. For more information, see "Optimizing N7 Session Lookup for AAR-I Messages in Rx Call Flows" section in Oracle Communications Cloud Native Core, Policy User Guide. - Enhanced logging (at WARN level) for microservices involved in PCRF & Diameter call flows: Policy generates enhanced logging for error responses during SM/Rx call flows at their default log level. It provides sufficient visibility into issues within or across the external facing interfaces. The current default log level for Policy microservices is WARN. For more information, see "Logging Support for Error Response" section in Oracle Communications Cloud Native Core, Policy User Guide.
- Burst rate limit modification and customization for WARN logs for all Policy microservices: In order to control the volume of logs, Policy 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, Policy User Guide.
- Stale Session Enhancement - replace PUT with GET UDR: Policy supports to configure whether to use PUT or GET operation during subscription revalidation with UDR. For more information, see "Handling Stale Data in PDS" section in Oracle Communications Cloud Native Core, Policy User Guide.
- Enhance support for Policy Authorization Service - Sponsored Data Connectivity (Chargeable Party)-Create Subscription for Usage Report: The Sponsored Data Connectivity (SDC) defines standard method for Application Function (AF) to provide usage threshold information and requests usage report for sponsored data used by the subscriber. PCF allocates usage monitoring keys, grants SMF usage threshold, and delivers them to AF usage report received from SMF when the threshold is reached or the session is terminated. PCF supports SDC when the AF or Network Exposure Function (NEF) provides this support through the Policy Authorization Service. It allows subscriber application traffic to be sponsored by an application service provider. For more information see "Support for Sponsored Data Connectivity When AF/NEF Provides the Support Over Policy Authorization Service" section in Oracle Communications Cloud Native Core, 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.
- CnPCF-3GPP-USER-LOC-INFO: NCGI Format Compliancy with 3GPP Rel18: Policy supports customizing the encoding of NR Cell Global Identity (NCGI/NR CGI) in 3GPP-User-Location-Info AVP in for Diameter Rx-RAR and Rx-STA messages, when 3GPP-User-Location-Info AVP is sent with Geographic Location Type value 5GS TAI and NCGI. For more information see "Support for Encoding of NCGI in 3GPP-User-Location-Info" section in Oracle Communications Cloud Native Core, 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-5 License names for feature mapping
| License Name | CCNC Number | Feature Name |
|---|---|---|
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-10660 | Support for Grafana 7.5.x |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-10101 | Stale Session Enhancement - replace PUT with GET UDR |
| Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual | CCNC-10091 | CnPCF-3GPP-USER-LOC-INFO: NCGI Format Compliancy with 3GPP Rel18 |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-9942 | Enhanced logging (at WARN level) for microservices involved in PCRF & Diameter call flows |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-9813 | Support for Immediate Report Handling |
| Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual | CCNC-9142 | TLS 1.3 Support for Kubernetes API |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-9118 | Enhance support for Policy Authorization Service - Sponsored Data Connectivity (Chargeable Party)-Create Subscription for Usage Report |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-9110 | Integration for Traffic Prioritization for NRF-Client and Egress Gateway on Policy |
| Oracle Communications Cloud Native Core, Policy Control Function - 25K Active Subscribers Perpetual | CCNC-5728 | Conflict Resolution for URSP Rules N1N2 transfer to UE |
| Oracle Communications Cloud Native Core, Policy and Charging Rules Function - per 25K Subscribers Perpetual | CCNC-9852 | Supports Traffic Detection on SMF-N7 and TDF using Sd Interface |
2.9 Service Communication Proxy (SCP)
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.
- Routing Options Enhancement for Notification Messages: SCP enhances its
routing options REST API configuration to configure
senderNFtypeso that routing options selection criteria can also consider sender NF Type for selecting a routing option. SCP enhances its logic to identify notification sender, which can be considered in routing options selection criteria for selecting a routing option for notification. For more information, see the "Routing Options Enhancement for Notification Messages" 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-6 License names for feature mapping
| License Name | CCNC Number | Feature Name |
|---|---|---|
| Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual | CCNC-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-7 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-8 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 |