2 Feature Descriptions

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

Note:

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

2.1 Automated Testing Suite (ATS) Framework

Release 25.1.100

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

2.2 Binding Support Function (BSF)

Release 25.1.100

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

  • Stale Binding Detection Audit, Report, and Recover: Service disruptions caused by network storms, system overload, database latency, or other factors can interrupt signaling between the Policy and BSF, impacting session binding. BSF provides a mechanism to revalidate the binding information of a PDU session, and recover stale bindings, ensuring session integrity. For more information, see "Stale Binding Detection Audit, Report, and Recover" section in "Oracle Communications Cloud Native Core, Binding Support Function User Guide".
  • Stale Binding Manual Detection Tool: Service disruptions caused by network storms, system overload, database latency, or other factors can interrupt signaling between Policy and BSF, impacting session binding. Currently, when binding is lost and Policy sessions are in a hung state, there is no way of knowing which sessions were lost or never received the binding. As a result, no action can be taken to solve this issue. The Binding Detection Tool addresses this by allowing manual queries of sessions created within a specific time frame in both Policy and BSF. For more information, see Oracle Communications Cloud Native Core, Binding Detection Tool User Guide.
  • Enhancements in menu.json for cnDBTier GRR Configuration: The BSF CNC Console GUI supports integration of read-only Georeplicaiton Recovery (GRR) cnDBTier APIs. With this, users can have specific information on cnDBTier statuses on the CNC Console. For more information, see the "Support for cnDBTier APIs in CNC Console" section in Oracle Communications Cloud Native Core, Binding Support Function User Guide.
  • Performance enhancement to achieve 54K TPS: In this release, BSF can achieve 54K TPS through performance optimizations. For more information, see the "BSF Benchmark Testing" section in Oracle Communications Cloud Native Core, Binding Support Function Benchmarking Guide.
  • Traffic Segregation: BSF 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 the "Traffic Segregation" 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-8864 Stale Binding Detection Audit, Report, and Recover
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-8840 SMPCF and BSF Stale Binding Manual Detection Tool
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-5795 Enhancements in menu.json for cnDBTier GRR Configuration
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-7763 Compatibility with two Webscale versions per release
Oracle Communications Cloud Native Core, Binding Support Function - 25K Active Subscribers Perpetual CCNC-4504 Performance enhancement to achieve 54K TPS
Oracle Communications Cloud Native Core, Advance Cloud Native Environment - 25K Active Subscribers perpetual CCNC-4443 Traffic Segregation

2.3 Cloud Native Environment (CNE)

Release 25.1.101

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 25.1.101 includes the following enhancement:

Support for Multus Thick Plugin for CNE deployments: With this feature, Multus Thick Plugin is installed whenever a new version of CNE is installed with CNLB enabled option. It is highly recommended to use Multus Thick Plugin based release for CNLB based CNE deployments. For more information, see Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.

Note:

  • Only CNE Releases 24.3.3 and above support Multus Thick Plugin based CNE deployments.
  • CNE 24.2.x releases do not support Multus Thick Plugin and are not recommended for CNLB deployments.

Release 25.1.100

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 25.1.100 includes the following enhancements:
  • Support for BareMetal CNE Deployment with Bare Minimum Servers (3 Worker Nodes): With this feature, CNE allows you to set up a BareMetal deployment with a minimal resources of three worker nodes. This setup is ideal for testing and getting started with CNE. For more information about installing and upgrading CNE with bare minimum servers, see the "Installing CNE using Bare Minimum Servers" and "Upgrading BareMetal CNE Deployed using Bare Minimum Servers" sections respectively in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • Hardware Agnostic Deployment Model for BareMetal CNE: Currently, CNE validates and supports BareMetal deployments on HP Gen10 and Oracle X8-2 servers only. With this release, CNE supports installing BareMetal CNE on any servers, thereby allowing the users to choose their servers based on their requirement. For more information about the prerequisites and updated procedure to install BareMetal CNE on other servers, see the "BareMetal Installation" section in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • Heterogenous Hardware Support for BareMetal CNE Deployment: Currently, BareMetal deployments support homogeneous hardware make, type, and version for worker nodes in a cluster. This means, all the worker nodes in a cluster must have the same type of hardware server, type, and version (for example, HP Gen 10 server with similar CPU, cores, RAM, and storage). With this feature, CNE supports heterogeneous hardware, wherein worker nodes in a cluster can have different server, type, and version. This provides more flexibility and options to manage hardware failure, expand existing deployment cluster, and tackle hardware End Of Life (EOL) and availability. For more information, 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.
  • Generic ToR Switch Configuration for BareMetal CNE: With this feature, CNE facilitates you to set up your BareMetal cluster using any ToR switch, by providing generic specifications, prerequisites, and configuration templates. For more information about configuring the ToR switches, see the "Configuring Top of Rack Switches" section in Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.
  • Traffic Segregation: With this enhancement, CNE provides an option to use Cloud Native Load Balancer (CNLB) without internal traffic segregation. This means CNLB can be configured to have a single interface to handle only external traffic. For more information about CNLB configuration, 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.16.2
    • Kubernetes - 1.31.1
    • Calico - 3.28.0
    • Istio - 1.23.0
    To get the complete list of third-party services and their versions, refer to the dependencies_25.1.100.tgz file provided as part of the software delivery package.

    Note:

    CNE constitutes a number of third-party services. For information about these third-party services, refer to the documents of the respective third-party services.

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

Table 2-2 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-6155 Support for BareMetal CNE Deployment with Bare Minimum Servers (3 Worker Nodes)
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-7674 Hardware Agnostic Deployment Model for BareMetal CNE
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-8297 Heterogenous Hardware Support for BareMetal CNE Deployment
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-7672 Generic ToR Switch Configuration for BareMetal CNE
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment - 25K Active Subscribers Perpetual CCNC-8079 Traffic Segregation
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment - 25K Active Subscribers Perpetual CCNC-1192 Multiple Network Interface per POD Support

Operations Services Overlay (OSO)

Release 25.1.103

Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.1.103 includes the following enhancements:
  • Support for new versions:
    • 25_1_common_oso:25.1.103
    • 25_1_oso_snapshot:25.1.103

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

Release 25.1.102

Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.1.102 includes the following enhancements:
Support for new versions:
  • 25_1_common_oso:25.1.102
  • 25_1_oso_snapshot:25.1.102

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

Release 25.1.101

Oracle Communications Cloud Native Core, Operations Services Overlay (OSO) 25.1.101 includes the following enhancements:
Support for new versions:
  • 25_1_common_oso:25.1.101
  • 25_1_oso_snapshot:25.1.101

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

Release 25.1.100

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

  • Support for Time Series Database (TSDB) Snapshot: Prometheus uses Time Series Database (TSDB) to store the collected metrics. With this feature, OSO allows the users to capture a snapshot at a specific point of time of the Prometheus data store without shutting down or disrupting the Prometheus instance. It is useful for taking backups, recovery, or even debugging purposes.

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

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

  • Support for new versions:
    • 25_1_common_pod is replaced with 25_1_common_oso.
    • 25_1_oso_snapshot:25.1.100

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

2.4 Cloud Native Core cnDBTier

Release 25.1.103

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

Release 25.1.102

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

Release 25.1.101

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

Release 25.1.100

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

  • Enhanced Georeplication Recovery using Parallel Backup Transfer and Restore: The backup transfer and restore mechanism used during a georeplication recovery involved additional data compression at the data node and serial backup transfer to the remote sites. This impacted the performance of georeplication recovery. With this feature, cnDBTier implements the following enhancements in backup transfer and restore thereby improving the performance and efficiency of georeplication recovery:
    • Avoids additional backup compression.
    • Supports parallel backup transfer from healthy cluster to georeplication recovery cluster.
    • Restores data node backups in parallel, as and when the backups are transferred from the healthy cluster to the georeplication recovery cluster.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

  • Support for TLS: With this enhancement, cnDBTier supports TLS for application SQL pods to establish secure connection for communication with Network Functions (NFs). When the TLS feature is enabled, cnDBTier performs or supports the following operations during communication with NFs:
    • The application SQL pod uses the certificates provided or configured to establish an encrypted connection for communication with NFs. This encrypted connection remains throughout the life cycle of the connection between NF and cnDBTier.
    • The system reestablishes the TLS connection between NFs and cnDBTier after a georeplication recovery. That is, when a georeplication recovery completes successfully, the system reestablishes the encrypted connection between the NFs and cnDBTier. This ensures that cnDBTier continues supporting TLS connection after a georeplication recovery.

    For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.

  • Monitoring Cluster Events to Determine Data Loss in Clusters: Network issues in the user environment led to cluster disconnections, which in turn resulted in the loss of cluster data. However, users were unable to monitor and identify the loss of data occurred due to network issues. With this feature, cnDBTier provides the following REST APIs to monitor cnDBTier cluster events to determine any data loss:
    • http://<base-uri>/db-tier/reset/parameter/cluster_restart_disconnect
    • http://<base-uri>/db-tier/reset/cluster/{cluster-name}/parameter/cluster_restart_disconnect
    • http://<base-uri>/db-tier/cluster/status
    • http://<base-uri>/db-tier/cluster/status/events/{numberOfLastEvents}
    • http://<base-uri>/db-tier/all/cluster/status/
    • http://<base-uri>/db-tier/all/cluster/status/events/{numberOfLastEvents}

    For more information about these APIs, see Oracle Communications Cloud Native Core, cnDBTier User Guide.

  • Storing NDB Logs in PVC: cnDBTier stores all NDB pod (ndbmgmd, ndbmysqld, ndbappmysqld) logs in PVC. These logs remain persistent even when the pods restart and they can be used to debug any data node related issues. However, ndbmtd logs were not stored in PVC. With this feature, cnDBTier stored ndbmtd logs in PVC, such that the logs remain available even after the pod is deleted. This feature is enabled in cnDBTier by default and doesn't require any configuration. For more information, see the "Storing NDB Logs in PVC" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
  • cnDBTier Automated Backup: MySQL doesn't allow schema change in a cluster when a backup is in progress. However, users were unable to check the ongoing backup processes in the cluster and schedule their upgrades for schema changes. With this release, cnDBTier provides the http://<base-uri>/db-tier/status/cluster/local/backup REST API to fetch the details of the data node backups that are in progress in the NDB cluster. For more information about this API, see the "cnDBTier Backup APIs" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
  • cnDBTier Scaling: With this release, cnDBTier automates the vertical scaling of PVCs using the dbtscale_vertical_pvc script. This simplifies the vertical scaling process and reduces human errors that may occur while performing the manual procedure. For more information about performing the vertical scaling using the dbtscale_vertical_pvc script, see the "cnDBTier Scaling" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
  • Support for New Versions of Software: cnDBTier has updated the version of Oracle MySQL Cluster Database to 8.4.3 in this release.

    Note:

    In db-monitor-svc script, the PVC and JVM-related metrics are disabled by default. This is due to PVC and JVM metrics fetch-time exceeding the Prometheus metrics fetch-timeout. This impacts the metrics fetch cycle.

    The following PVC metrics are disabled:

      • db_tier_pvc_read_write_speed
      • db_tier_pvc_is_accesible
      • db_tier_pvc_failure_count

    The following JVM metrics are disabled:

      • jvm_max_memory
      • jvm_free_memory
      • jvm_total_memory

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, Network Slice Selection Function- 25K Active Subscribers Perpetual CCNC-8876 Enhanced Georeplication Recovery using Parallel Backup Transfer and Restore
Oracle Communications Cloud Native Core, Network Slice Selection Function- 25K Active Subscribers Perpetual CCNC-5332 Support for TLS
Oracle Communications Cloud Native Core, Policy and Charging Rules Function - 25K Subscribers Perpetual CCNC-9356 Compatibility with two Webscale versions per release

2.5 Cloud Native Configuration Console (CNC Console)

Release 25.1.100

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

  • Multiple Admin Support for CNCC IAM Deployments: As CNC Console evolved from a simple interface for managing a single network function (NF) instance with one admin account to supporting multi-cluster deployments catering to multiple NF Instances including access management to observability applications, there was a need to have support for multiple admin users for managing the users across multiple customer operations teams.

    As part of this feature, CNC Console IAM is enhanced to support creation and management of multiple admin users in IAM using both internal and external IDPs (SAML and LDAP). For all the admin accounts managed in CNC Console, all the existing measurements, alarms, and logging mechanisms would be applicable to all admin users similar to the existing core users.

    There are default password policies defined for CNCC IAM users in the default realm. These policies are disabled by default and can be enabled, if needed.During the deployment, a default admin user is created. To create multiple CNCC IAM admin users, refer to the "Post Installation steps" section in Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide and Oracle Communications Cloud Native Configuration Console User Guide.

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

Table 2-4 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-9858 Multiple Admin support for CNCC IAM deployments
Oracle Communications Cloud Native Core, Cloud Native Environment - per 25K Subscribers Perpetual CCNC-8525 IAM Backend Upliftment

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

Release 25.1.100

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

  • Support to Increase the Certificate Management Capacity: OCCM is designed to manage certificates for multiple NFs. This feature increases the maximum number of supported certificates (both OCCM and NF certificates) to 200. For more information about certificate management, see the "Managing Certificates" section in Oracle Communications Cloud Native Core, Certificate Management User Guide. For more information, see "OCCM Configuration Maximum Limits", see the "OCCM Deployment Models" section in Oracle Communications Cloud Native Core, Certificate Management Installation, Upgrade, and Fault Recovery Guide.
  • Expired Certificate Handling: This feature enables OCCM to raise alert and stop the retry of CMP (Certificate Management Protocol) Identity (OCCM) certificate renewal. For the expired End Entity (NF) certificates, if OCCM is configured to sign the Certificate Management Protocol Version 2 (CMPv2) Key Update Request (KUR) using the certificate and key that is being renewed, then OCCM raises an alert indicating the expiry of the certificate and stop the retry of NF certificate renewal. For more information, see "Expired Certificate Handling" section in Oracle Communications Cloud Native Core, Certificate Management Troubleshooting Guide.
  • Bulk Migration of Certificates: With this feature, you can update the issuer configuration and endpoint by updating fields such as the server URL, recipient Distinguished Name (DN), and issuer DN. This update is performed by migrating the certificates in bulk from the current issuer to a newly created issuer with the required configuration. For more information, see "Bulk Migration of Certificates" section in Oracle Communications Cloud Native Core, Certificate Management User Guide.

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

Table 2-5 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-8810 Support to Increase the Certificate Management Capacity
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-8808 Expired Certificate Handling
Oracle Communications Cloud Native Core, Certificate Management - 25K Active Subscribers CCNC-6075 Bulk Migration of Certificates

2.7 Network Repository Function (NRF)

Release 25.1.100

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

  • Egress Gateway Pod Throttling: With the implementation of this feature, each Egress Gateway pods monitor 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. For more information, see the "Egress Gateway Pod Throttling" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.
  • Configuring the Stack Trace Depth: With this feature, NRF allows the users to configure the depth of the stack trace to be logged when a Java exception occurs. For more information, see the "Configuring the Stack Trace Depth" section in Oracle Communications Cloud Native Core, Network Repository Function Troubleshooting Guide.
  • Discovery Parameter Value Based Skip SLF Lookup: With this feature, NRF provides an option to configure a set of allowed values for the discovery query parameter. If the parameter is present in the discovery request and its value matches the configured values, the SLF lookup will be skipped. For more information about this feature, see "Discovery Parameter Value Based Skip SLF Lookup" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Traffic Segregation: NRF 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 the "Traffic Segregation" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

  • Support for Dual Stack: This feature enables NRF to operate seamlessly in a Kubernetes environment configured for both IPv4 and IPv6 protocols. It facilitates the coexistence and interoperability of IPv4 and IPv6 within Kubernetes clusters, allowing simultaneous communication using either of the protocols based on the deployment configuration. For more information, see "Dual Stack" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

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

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-7898 Discovery Parameter Value Based Skip SLF Lookup
Oracle Communications Cloud Native Core, Network Repository Function - 25K Active Subscribers Perpetual CCNC-4450 Traffic Segregation
Oracle Communications Cloud Native Core, Advance Networking - 25K Active Subscribers CCNC-1223 Support for Dual Stack

2.8 Network Slice Selection Function (NSSF)

Release 25.1.100

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

  • DNS SRV-Based Selection of NRF in NSSF: The DNS SRV-based selection feature enhances the Network Slice Selection Function (NSSF) by introducing dynamic Network Repository Function (NRF) selection through DNS SRV records. This update improves network resilience by allowing NSSF to dynamically switch to alternate NRFs in case of primary NRF failures, ensuring continuous service availability. For more information, see the "DNS SRV-Based Selection of NRF in NSSF" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

  • Deleting All Slices in a TAI Using PATCH Remove Operation: This feature enhances NSSF by enabling more flexible management of network slices in 5G networks. It allows the AMF to delete all slices for specific Tracking Areas (TAIs), TAILists, or TAIRanges using the PATCH operation. For more information, see the "Deleting All Slices in a TAI Using PATCH Remove Operation" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

  • Improved Error Response when All Slices are Removed: NSSF now provides clearer responses, such as returning 204 No Content when all slices in an area are removed, while still allowing slices to be re-added through PATCH or PUT operations. This enhancement improves granularity, efficiency, and control for slice management while aligning with 3GPP standards. For more information, see the "Deleting All Slices in a TAI Using PATCH Remove Operation" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

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

Table 2-6 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-4529 DNS SRV-Based Selection of NRF in NSSF
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-9140 Deleting All Slices in a TAI Using PATCH Remove Operation
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual CCNC-8381 Improved Error Response when All Slices are Removed
Oracle Communications Cloud Native Core, Network Slice Selection Function - 25K Active Subscribers Perpetual

CCNC-9228

CCNC-5077

 Compatibility with two Webscale versions per release

2.9 Service Communication Proxy (SCP)

Release 25.1.100

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

  • NF Discovery Response Cache Update Based on the Received Notifications: With this enhancement, SCP can automatically refresh its Model D discovery response cache in real-time based on notifications from the NRF whenever NF profile information is updated or changed. For more information, see the "NF Discovery Response Cache Update Based on the Received Notifications" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Verbose Logging for SCP: This enhancement introduces verbose logging specifically for the SCP-Loadmanager microservice within the data plane. For more information, see the "Verbose Logging for SCP" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Mediation Support for User Defined Variables in Rules and Trigger Points: This enhancement allows SCP to store information at a mediation trigger point and pass it to another mediation trigger point within the same transaction. This feature is especially beneficial for complex message manipulations, such as modifying a response based on the content of the initial request. For more information, see the "Mediation Support for User Defined Variables in Rules and Trigger Points" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Alternate Routing Configuration Based on Received Status Code 504, Expired Response Timeout and Connection Error: This feature allows you to manage alternate routing based on the response timeouts, that is, 504 errors from the upstream, and handles local errors such as timeout detected by SCP or connect errors effectively. For more information, see the "Alternate Routing Configuration Based on Received Status Code 504, Expired Response Timeout and Connection Error" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Support for 3GPP Defined NFs, Custom NFs, and Custom NF Services: SCP enhances its capability to support the addition of new 3GPP defined NFs, custom NFs, and custom NF services at runtime using REST APIs. Also, SCP allows you to configure timers for a service based on the operation type. For more information, see the "Support for 3GPP Defined NFs, Custom NFs, and Custom NF Services" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Support for 3GPP Timestamp Related Headers: This enhancement allows SCP to calculate the request timeout and total transaction lifetime by using the 3GPP-defined SBI Timestamp headers included in the SBI request messages. For more information, see the "Support for 3GPP Timestamp Related Headers" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
  • Traffic Segregation: SCP 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 the "Traffic Segregation" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.

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

Table 2-7 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-8267 NF Discovery Response Cache Update Based on the Received Notifications
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-8452 Verbose Logging for SCP
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-8150 Mediation Support for User Defined Variables in Rules and Trigger Points
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-8265 Alternate Routing Configuration Based on Received Status Code 504, Expired Response Timeout and Connection Error
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual

CCNC-7792

CCNC-7638

CCNC-4884

 Support for 3GPP Defined NFs, Custom NFs, and Custom NF Services
Oracle Communications Cloud Native Core, Service Communication Proxy - 25K Active Subscribers Perpetual CCNC-7767 Compatibility with two Webscale versions per release
Oracle Communications Cloud Native Core, Advanced Routing – 25K Active Subscribers Perpetual CCNC-8166 Support for 3GPP Timestamp Related Headers
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CCNC-4442 Traffic Segregation

2.10 Security Edge Protection Proxy (SEPP)

Release 25.1.102

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

Release 25.1.101

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

Release 25.1.100

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

  • Cat-3 Time Check for Roaming Subscribers Feature: In roaming scenarios, customers enter different time zones or regions, which must be verified. To ensure the same, SEPP uses PLMN-IDs (Public Land Mobile Network identifiers) to check if the subscriber has entered a new time zone.

    The SEPP compares the last recorded PLMN-ID from the subscriber's previous registration with the new PLMN-ID. By doing this, the SEPP can confirm if the subscriber has moved to a new time zone or area. This process ensures accurate monitoring and verification of subscriber movements while roaming. The process starts with the P-SEPP checking if the feature is enabled for the specified consumer Remote SEPP Set. This feature is specifically for AUSF UE Authentication messages and only works when the Subscription Permanent Identifier/Subscription Concealed Identifier (SUPI/SUCI) is included in the incoming message. When the SEPP receives the SBI request, it extracts key information, such as the SUPI/SUCI (UE ID), the Serving PLMN, and the Sender Timestamp. If the SUCI is present, the SEPP queries the UDM to get the corresponding SUPI. Once the SUPI is retrieved, the SEPP queries the UDR to check the subscriber’s authentication status. If the SUPI is already in the incoming message, the SEPP directly queries the UDM for the authentication status.

    For more information about the feature, see "Cat-3 Time Check for Roaming Subscribers Feature" section in 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.
  • Support for Dual Stack: This feature enables SEPP to operate seamlessly in a Kubernetes environment configured for both IPv4 and IPv6 protocols. It facilitates the coexistence and interoperability of IPv4 and IPv6 within Kubernetes clusters, allowing simultaneous communication using either of the protocols based on the deployment configuration. For more information about the feature, see the "IPv6 Dual Stack Support" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide and Oracle Communications Cloud Native Core, Security Edge Protection Proxy REST API Guide.
  • SEPP Message Feed Enhancement: SEPP supports copying of the incoming and outgoing messages passing through Ingress and Egress Gateways to a Data Director. The Data Director receives the messages from Gateways with a correlation-id and feeds the data securely to an external monitoring system. From Gateway Services 25.1.100, Gateway Services are enhanced to capture all messages within a transaction onto the same Kafka partition based on the keybasedKafkaProducer Helm configuration. If keybasedKafkaProducer is set to true, correlation-id metadata is used as the message key for the key-based Kafka producer. This ensures that the same transaction messages are routed to the same partition. If keybasedKafkaProducer is set to false, all the messages are distributed across all the available partitions in a round-robin order.

    For more information about the feature, see the "SEPP Message Feed Feature" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide, "Customizable Parameters" in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.

  • ASM Upgrade: Oracle SEPP leverages the Istio or Envoy service mesh (Aspen Service Mesh) for all internal and external communication. The ASM resource configurations are enhanced for required traffic management as per expected traffic flow. For more information about the feature, see the "Configuring SEPP to Support Aspen Service Mesh" section and "Customizable Parameters" 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-8 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, 5G Signaling Firewall - 25K Active Subscribers Perpetual CCNC-2830 Cat-3 Time Check for Roaming Subscribers Feature
Oracle Communications Cloud Native Core, Advance Networking - 25K Active Subscribers CCNC-5460 Support for Dual Stack
Oracle Communications Network Analytics Data Director, Service Communication Proxy Advanced Packet Processing - Network-Wide Message per Second CNCC-8557 SEPP Message Feed Enhancement
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual CNCC-3467 ASM Upgrade
Oracle Communications Cloud Native Core, Security Edge Protection Proxy - 25K Active Subscribers Perpetual

CCNC-2715

CCNC-2714

CCNC-2711

CCNC-2710

 Mano Compliance

ATS Features

SEPP ATS includes the following features or enhancements:

ATS Tagging Support Feature: This feature assists in running the feature files after filtering features and scenarios based on tags. By using this feature, the user can save time taken by manually navigating through several feature files. For more information, see the "ATS Tagging Support Feature" section in the Oracle Communications Cloud Native Core, Automated Testing Suite User Guide.

2.11 Unified Data Repository (UDR)

Release 25.1.100

Oracle Communications Cloud Native Core, Unified Data Repository (UDR) 25.1.100 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 the "Support for Post Operation for an Existing Subscription" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
  • Support for Georeplication Recovery APIs in CNC Console: With this enhancement, UDR can mark the disrupted cnDBTier cluster as failed, initiate georeplication recovery, and continuously monitor their status, ensuring seamless disaster recovery operations using CNC Console. For more information, see the "Support for Georeplication Recovery APIs in CNC Console" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
  • Traffic Segregation: UDR 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 the "Traffic Segregation" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.

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

Table 2-9 License names for feature mapping

License Name CCNC Number Feature Name
Oracle Communications Cloud Native Core, Unified Data Repository - 25K Active Subscribers CCNC-8066 Support for Post Operation for an Existing Subscription
Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual CCNC-7803 Compatibility with two Webscale versions per release
Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual CCNC-5906 Added support for Dns Static Entry
Oracle Communications Cloud Native Core, Subscriber Location Function - 25K Active Subscribers Perpetual CNCC-5797 Support for Georeplication Recovery APIs in CNC Console
Oracle Communications Cloud Native Core, Unified Data Repository - 25K Active Subscribers CNCC-4466 Support for 25K TPS on a single UDR instance
Oracle Communications Cloud Native Core, Advanced Cloud Native Environment – 25K Active Subscribers Perpetual CNCC-4446 Traffic Segregation