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

Automated Testing Suite (ATS)

There are no new features or updates implemented in CNC 2.3.4 release.

Binding Support Function (BSF)

Binding Support Function (BSF) 1.9.0 is updated with the following enhancements:
  • Three-Site Georedundancy: BSF is enhanced to support the three-site Geographical Redundant (Georedundant) deployment. It offers, both three-site and two-site georedundancy to ensure service availability when one of the BSF sites is down. For more information, see "Georedundancy Support" in Oracle Communications Cloud Native Binding Support Function User's Guide.
  • Overload Control and Handling - SBI - phase 1: BSF supports overload management to prevent the performance of services from degrading, in an uncontrolled fashion under heavy load, using BSF REST APIs. For more information about the Overload Control and Handling, see "Overload Control and Handling - SBI " in Oracle Communications Cloud Native Binding Support Function User's Guide.
  • Support for ASM Helm Config: With this feature, orchestration of CNC Policy along with ASM resource configurations has been automated. Resources, such as PeerAuthentication, ServiceEntry, DestinationRule, and EnvoyFilter can be configured in an automated way, using ASM data plane configuration helm chart. For more information, see Oracle Communications Cloud Native Binding Support Function Installation Guide.
  • NF Set Registration: With this feature, each instance of BSF registers the NF Set with Network Repository Function, so that Service Communication Proxy (SCP) can perform the Alternate Routing. For more information, see "NRF Client Configuration" in Oracle Communications Cloud Native Binding Support Function Installation Guide.

Cloud Native Core Console (CNC Console)

Cloud Native Core Console (CNC Console) 1.7.1 has been updated with the following enhancement:

  • GUI Support the lastet version of SCP: CNCC GUI support for the latest version of SCP (1.12.0).

Cloud Native Core Console (CNC Console) 1.7.0 has been updated with the following enhancements:

  • OJET upgrade: CNC Console backend OJET is upgraded to the latest version, which enhances the GUI look and feel.
  • Integration with Aspen service mesh (ASM) 1.6.14-am4: Oracle CNC Console leverages the Istio or Envoy service mesh for all internal and external communication. ASM Version is updated to ASM 1.6.14-am4. For more information, see Oracle Communications Cloud Native Core Console Installation and Upgrade Guide.
  • Support the latest version of NFs: CNC Console is compatible with the latest version of the supported NFs:
    • SCP 1.12.0
    • NRF 1.12.0
    • UDR 1.12.0
    • POLICY 1.12.0
    • BSF 1.9.0

Cloud Native Core Policy (CNC Policy)

CNC Policy 1.12.1

Oracle Communications Cloud Native Core Policy (CNC Policy) 1.12.1 has been updated with the following enhancements:

  • Enhancement in Policy Conditions and Actions: The Policy conditions and actions have been updated in PCRF project. For more information, see Oracle Communications Cloud Native Core Policy Design Guide.

CNC Policy 1.12.0

Oracle Communications Cloud Native Core Policy (CNC Policy) 1.12.0 has been updated with the following enhancements:

  • Three-Site Georedundancy: CNC Policy is enhanced to support the three-site Geographical Redundant (Georedundant) deployment. It offers, both three-site and two-site georedundancy to ensure service availability when one of the Policy sites is down. For more information, see "Georedundancy Support" in Oracle Communications Cloud Native Core Policy User's Guide.
  • Export of Policies with Dependencies using GUI: CNC Policy is enhanced to support bulk export of Policy Managed Objects (MOs) and Policy Projects with their dependencies using CNC Console. For more information on the GUI enhancements, see "Import & Export" in Oracle Communications Cloud Native Core Policy User's Guide.
  • Overload Control and Handling - SBI - phase 1: CNC Policy supports overload management to prevent the performance of the Policy services from degrading in an uncontrolled fashion under heavy load, using Policy REST APIs. For more information about Overload Control and Handling, see "Overload Control and Handling - SBI" in Oracle Communications Cloud Native Core Policy User's Guide.
  • Support for ASM Helm Config: With this feature, orchestration of CNC Policy along with ASM resource configurations has been automated. Resources such as PeerAuthentication, ServiceEntry, DestinationRule, and EnvoyFilter can be configured in an automated way using ASM data plane configuration helm chart. For more information, see "Aspen Service Mesh Configurations" in Oracle Communications Cloud Native Core Policy Installation and Upgrade Guide.
  • NF Set Registration: With this feature, each instance of CNC Policy registers the NF Set with Network Repository Function (NRF), so that Service Communication Proxy (SCP) can perform Alternate Routing. For more information, see "NRF Client Configuration" in Oracle Communications Cloud Native Core Policy Installation and Upgrade Guide.
  • Handling of Stale Session Notification in PCRF-Core: With this enhancement, PCRF Core service is integrated with audit service. Using CNC Console, audit service related configurations can be done for Gx and Rx diameter sessions. For more information, see "Configuring CNC Policy using CNC Console" in Oracle Communications Cloud Native Core Policy User's Guide.
  • Notification Handling from PDS for PCRF-Core: With this enhancement, PCRF Core service will be able to process only update notification requests from nUDR and LDAP. Based on the requests, policy evaluation is done and appropriate policy rules are installed. For more information, see "Notification Handling from PDS for PCRF-Core" in Oracle Communications Cloud Native Core Policy User's Guide.
  • Enhancement in Policy Conditions and Actions: The Policy conditions and actions have been updated in PCRF project. For more information, see Oracle Communications Cloud Native Core Policy Design Guide.
  • OJET Upgrade: The CNC Console backend OJET is upgraded to the latest version, which enhances the GUI look and feel.

Cloud Native Diameter Routing Agent (CnDRA)

There are no new features or updates implemented in CNC 2.3.4 release.

Cloud Native Environment (CNE)

There are no new features or updates implemented in CNC 2.3.4 release.

CNC NF Data Collector

There are no new features or updates implemented in CNC 2.3.4 release.

Inter-Working Function (IWF)

There are no new features or updates implemented in CNC 2.3.4 release.

Service Communication Proxy (SCP)

SCP 1.12.1 has been updated with the following enhancement:
  • SCP can be upgraded to a new version and rolled back to a previous supported version as described in Oracle Communications Cloud Native Core Service Communication Proxy Installation and Upgrade Guide.
SCP 1.12.0 has been updated with the following enhancements:
  • Support for Multus Container Network Interface: SCP uses Multus Container Network Interface (CNI) plug-in to connect multiple network interfaces to pods in Kubernetes. After integrating Multus CNI with SCP, multiple interfaces can be created in a pod. For more information about the feature, see Oracle Communications Cloud Native Core Service Communication Proxy (SCP) User's Guide.
  • Support for Model C Indirect 5G SBI Communication: SCP uses Release 16 of Model C Indirect 5G SBI Communication format to enable consumer NFs to route service requests to producer NFs through SCP. For more information about the feature, see Oracle Communications Cloud Native Core Service Communication Proxy (SCP) User's Guide.
  • SCP ATS Enhancements: SCP ATS has been enhanced with the following:
    • Test Case Mapping to features and Display Total Counts-New features
    • Application Logs collection on rerun

    For more information about this enhancement, see Oracle Communications Cloud Native Core Automated Test Suite Guide

Security Edge Protection Proxy (SEPP)

Security Edge Protection Proxy (SEPP) 1.5.0 has been updated with the following enhancements:

  • SEPP support for Pod Tolerations and Node Selector : This feature pins the SEPP pods to a dedicated worked node by using node selector and pod toleration. While the node selector pins the SEPP pods to the dedicated worker node, the pod tolerations ensure that other NF pods do not use the worker node dedicated for SEPP. For more information about the configuration and customization of the enhancement, see Oracle Communications Cloud Native Core Security Edge Protection Proxy (SEPP) Installation Guide.
  • SEPP Integration with cnDBTier 1.8.0.: SEPP is now integrated with cnDBTier 1.8.0 in a containerized Oracle Communications Cloud Native Environment 1.8.1. For more information, see Oracle Communications Cloud Native Core Security Edge Protection Proxy (SEPP) Installation Guide.

Network Exposure Function (OCNEF)

OCNEF 1.3.1 has been updated with the following enhancement:
  • OCNEF Reformed Architecture: The OCNEF architecture has been reformed with the 3GPP defined services and components. For more information about OCNEF 1.3.1 architecture, see Oracle Communications Cloud Native Core Network Exposure Function User Guide.

  • Helm Based Configuration: OCNEF supports the helm based deployment model and provides the option to customize the deployment using the Custom Value file. For more information about OCNEF installation, see Oracle Communications Cloud Native Core Network Exposure Function Installation Guide
  • API Invoker Onboarding and Offboarding: OCNEF supports the API Invoker Onboarding and Offboarding functionality to manage the exposure of the service APIs to different applications. For more information about the feature, see Oracle Communications Cloud Native Core Network Exposure Function User Guide.
  • Security Token Generation: OCNEF supports the OAuth security method for service API invocation. This security procedure ensures that only authenticated service requests are directed to OCNEF for secures processing the requests. For more information about the feature, see Oracle Communications Cloud Native Core Network Exposure Function User Guide.
  • Location Reporting: OCNEF provides the Location Reporting functionality to provide the current or last known location of UEs in 5G network. For more information about the feature, see Oracle Communications Cloud Native Core Network Exposure Function User Guide.

Network Repository Function (NRF)

ATS for OCNRF 1.12.1 has been updated with a script to clean up SUT configuration if previous ATS pipeline got aborted. For more information, see Oracle Communications Cloud Native Core Automated Test Suite Guide.

OCNRF 1.12.0 has been updated with the following enhancement:
  • Three site geo-redundancy: OCNRF is enhanced to support three-sites geographical redundant (georedundant) deployment. It offers both three-sites and two-sites georedundancy to ensure service availability when one of the OCNRF sites is down. For more information about georedundancy, see Oracle Communications Cloud Native Core Network Repository Function User's Guide.
  • OCNRF Support for IPv6 (Single Stack): OCNRF supports communication on IPv6 addresses. OCNRF support IPv6 addresses, IPv6 prefix , and IPv6 Prefix Ranges as defined in 3GPP TS 29.571 and 3GPP TS 29.510. For more information about IPv6 support, see Oracle Communications Cloud Native Core Network Repository Function Installation and Upgrade Guide.
  • OCNRF support for Routing Indicator based SLF request: OCNRF supports more flexible NF configuration for discovery query with exception list. For more information about SLF lookup, see Oracle Communications Cloud Native Core Network Repository Function User's Guide.
  • Support for SIDF Registration and Discovery: OCNRF supports UDM registration, subscription, and discovery on the basis of service-name "Nudm-sucideconceal".

Network Slice Selection Function (NSSF)

OCNSSF 1.6.0 has been updated with the following enhancements:
  • Indirect communication support for NSSF: In indirect mode of communication, consumers and producers interact through SCP. The following two communication models are supported:
    • Model C - Indirect communication without delegated discovery.

    • Model D - Indirect communication with delegated discovery.

    For more information about communication models helm parameters, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation Guide.

    For more information on the feature description and REST API, see Oracle Communications Cloud Native Core Network Slice Selection Function User's Guide.

  • IPV6 Support for NSSF: NSSF supports IPv6 addresses for its interfaces. For more information, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation Guide.
  • Automatic DB Application User Creation: Along with a privilege user, NSSF supports applicationUser for database access, apart from privileged user. NSSF provides a helm option to create an application user based on the configurable parameter (global.ocnssfHookImage.createUser). When the helm parameter is set to true, ApplicationDbUser is created automatically. For more information, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation Guide.
  • Integration with Aspen service mesh (ASM) 1.6.14-am4: NSSF leverages the Istio or Envoy service mesh for all internal and external communication. ASM version is updated to ASM 1.6.14-am4. For more information, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation Guide.
  • Pod Affinity and Anti Affinity: NSSF has updated pod affinity and anti-affinity rules to check if all the service pods replicas are not spawned at the same node. This provides high availability when a node is down.

Unified Data Management (UDM)

There are no new features or updates implemented in CNC 2.3.4 release.

Unified Data Repository (UDR)

UDR 1.12.0 has been updated with the following enhancements:
  • Multiple Site Redundancy: UDR or SLF supports multiple site redundancy using the cnDBTier multisite deployment model. All sites of UDR are active and can handle traffic. The replication of database is handled by configuring DBTier for multiple site deployment.

    For more information about multisite setup, see "Creating Database User or Group" in Oracle Communications Cloud Native Core Unified Data Repository Installation and Upgrade Guide.

    For more information about multiple site redundancy, see "Multiple Site Redundancy" feature description in Oracle Communications Cloud Native Core Unified Data Repository User Guide.

  • Oauth 2.0 Configuration: Oauth 2.0 is a security feature provided to authenticate requests from valid consumer NFs. The consumer NFs request access token from the issuer, that is NRF, for a particular producer NF and uses this access token to send request to the respective producer NF.

    For more information about Oauth 2.0 feature, see "Oauth 2.0" in Oracle Communications Cloud Native Core Unified Data Repository User Guide.

  • KeyID Enhancement Integration: UDR integration in CNC Console is enhanced with the introduction of KeyID. Using CNC Console, the UDR users can configure KeyID in the Access Token Validation page. For more information on how to configure access tokens, see "Access Token Validation" section in Oracle Communications Cloud Native Core Unified Data Repository User Guide.

  • MGM APIs for UDM and SLF Data: MGM APIs allows the user to update the schema of UDM and SLF data stored on UDR. For more information about MGM APIs, see Oracle Communications Cloud Native Core Unified Data Repository REST Specification Guide.
  • IPv6 Support: UDR or SLF supports IPv6 addresses for its interfaces. For more information, see the "Configuring Unified Data Repository" section in Oracle Communications Cloud Native Core Unified Data Repository Installation and Upgrade Guide.

  • SLF ATS Lightweight Performance: Using this feature, the SLF ATS users can run performance test cases in Jenkins. For more information about SLF-ATS Lightweight Performance feature, see the "Executing UDR Test Cases using ATS" in Oracle Communications Cloud Native Core Automated Test Suite Guide.