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

2.1 Automated Testing Suite (ATS) Framework

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

Release 22.3.1

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

Release 22.3.0

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

  • ATS Maintenance Scripts: ATS Maintenance Scripts are used to take a backup of the ATS custom folders and Jenkins pipeline, view the configuration and restore the Jenkins pipeline, and install or uninstall ATS and Stubs. For more information, see Oracle Communications Cloud Native Core Automated Testing Suite Guide.

2.2 Binding Support Function (BSF)

Release 22.3.4

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

Release 22.3.2

Oracle Communications Cloud Native Core Binding Support Function (BSF) 22.3.2 has been updated with the following enhancements:
  • Enable Controlled Shutdown of an Instance: CNC BSF supports controlled shutdown feature to provide the partial or complete isolation of the site from the network so that the operator can perform necessary recovery procedures when required. For more information on this feature and its configurations, see the "Enable controlled shut down of an instance" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.
  • Enhancements to Aspen Service Mesh (ASM) Sidecar configuration: The ASM Sidecar configuration is enhanced with the addition of Authorization Policy (AP) and Virtual Service (VS) CRDs to the Data Plane. The Service Mesh Authorization Policies at the ingress side-car associated with a server are used to filter requests originating from the clients using one of the identifiers (SPIFFE, FQDN or NF-type) contained within the client certificate. For more details, see the, "Aspen Service Mesh Configurations" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.

Release 22.3.0

Oracle Communications Cloud Native Core Binding Support Function (BSF) 22.3.0 has been updated with the following enhancements:
  • Active Session Counter: BSF facilitates counting the number of active sessions for a configurable time period. Also, it enables displaying the number of active sessions at any given time. For more information on this feature and its configurations, see the "Support for Active Sessions Counter" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.
  • Support for User-Agent Header: BSF supports the user-agent header, which helps the producer Network Function (NF) to identify the consumer NF that has sent the request. For more information on this feature and its configurations, see the "Support for User-Agent Header" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.

2.3 Continuous Delivery Control Server (CDCS)

Oracle Communications Cloud Native Core Continuous Delivery Control Server (CDCS) 22.3.x has been updated with the following enhancements:

CDCS Release 22.3.1

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

CDCS Release 22.3.0

Oracle Communications Cloud Native Core Continuous Delivery Control Server (CDCS) 22.3.0 has been updated with the following enhancements:

  • Support for a Staging Site: CDCS supports staging sites that are non-production sites where customers can install or upgrade NFs without affecting production traffic. For more information about the staging sites, see the "Managing Staging Sites" section in Oracle Communications Cloud Native Core CD Control Server User Guide.
  • Support for ATS Tests: Automated test suites (ATS) are provided by each NF as a way to perform automated testing for each NF. Depending on the NF, the following automated tests may be provided:
    • Feature tests
    • Regression tests
    • Performance tests

    In this release, CDCS adds the ability to run ATS tests. Each NF releases an ATS CSAR with each release. ATS CSARs must be downloaded to CDCS, and installed at a Staging Site. Additionally, the NF CSAR itself must be downloaded and installed at the same Staging Site before the ATS tests can be run. For more information about the testing NF ATS, see the "Testing NFs" section in Oracle Communications Cloud Native Core CD Control Server User Guide.

  • Support for NF Uninstallation: CDCS adds the ability to uninstall any NF that has been installed by CDCS, or has otherwise been identified through the Update NF Inventory command. For more information about uninstalling NF, see the "Uninstalling NF" section in Oracle Communications Cloud Native Core CD Control Server User Guide.
  • Support for Sending Email notification: CDCS sends an email notification to configured email addresses when any command is run on CDCS. For more information about configuring an email, see the "Adding Email Address to Notification List" section in Oracle Communications Cloud Native Core CD Control Server User Guide.
  • Signed Artifact Verification: CDCS supports verifying cryptographically signed artifacts in CSARs. As NF releases include these signed artifacts in their CSARs, CDCS will automatically perform signature verification when the CSAR is downloaded. NF CSARs that only provide checksums can still be downloaded, but only checksum verification will be performed. For more information about verifying the artifact, see the "Installing CDCS" section in Oracle Communications Cloud Native Core CD Control Server Installation and Upgrade Guide.
CD Control Server is compatible with the following NF versions:
  • CNC Console 22.3.0
  • cnDBTier 22.3.0
  • SCP 22.3.0
  • SEPP 22.3.0

2.4 Cloud Native Core Console (CNC Console)

Oracle Communications Cloud Native Core Console (CNC Console) 22.3.x has been updated with the following enhancement.

Release 22.3.2

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

Release 22.3.1

Oracle Communications Cloud Native Core Console (CNC Console) 22.3.1 has been updated with the following enhancement:
  • Added new API prefix at Console for EIR mode in UDR/SLF: To enable the EIR mode of UDR in CNC Console, new API prefix is introduced in CNC Console. For information about EIR Prefix, see the "CNC Console KPIs" and "CNC Console Metrics" sections in Oracle Communications Cloud Native Core User Guide.

Release 22.3.0

Oracle Communications Cloud Native Core Console (CNC Console) 22.3.0 has been updated with the following enhancement:
  • Support for CNC Console Deployment using Continuous Delivery Control Server (CDCS): In addition to CNC Console's Command Line Interface (CLI) deployment method, CNC Console can be deployed using the Continuous Delivery Control Server (CDCS), which is a centralized server that automates CNC Console deployment processes such as downloading the CNC Console package, installation, upgrade, and rollback. For more information about CDCS, see Oracle Communications Cloud Native Core CD Control Server User Guide. For information about CNC Console deployment using CDCS, see the "Overview" section in Oracle Communications Cloud Native Core Console Installation and Upgrade Guide.
  • Supports Single Helm chart for CNC Console Deployment: Until the current release, CNC Console was using two helm charts to deploy CNCC IAM and M-CNCC Core or A-CNCC Core components. With this feature, CNC Console will be able to deploy all the components as part of a single helm chart deployment. For more information about the Single Helm chart for CNC Console Deployment, see Oracle Communications Cloud Native Core Console Installation and Upgrade Guide.
  • Compliance with ASM 1.9.x and Kubernetes 1.20: CNC Console deployment has been enhanced to be in compliance with ASM 1.9.x and Kubernetes 1.20. For more information, see Oracle Communications Cloud Native Core Console Installation and Upgrade Guide.
  • Supports the Latest Version of NFs: CNC Console is compatible with the following NF versions:
    • SCP 22.3.0
    • NRF 22.3.0
    • UDR 22.3.0
    • SEPP 22.3.0
    • NSSF 22.3.0
    • BSF 22.3.0
    • POLICY 22.3.0

    For more information, see the "CNC Console Deployment Modes" section in Oracle Communications Cloud Native Core Console Installation and Upgrade Guide and Oracle Communications Cloud Native Core Console User Guide.

2.5 Cloud Native Core DBTier (cnDBTier)

Oracle Communications Cloud Native Core DBTier (cnDBTier) 22.3.x has been updated with the following enhancements:

Release 22.3.4

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

Release 22.3.3

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

Release 22.3.2

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

Release 22.3.1

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

Release 22.3.0

Oracle Communications Cloud Native Core DBTier (cnDBTier) 22.3.0 has been updated with the following enhancements:
  • DBTier Scaling: DBTier supports horizontal and vertical scaling of MySQL Application PODs for improved performance. For more information about the feature, see "DBTier Scaling" in Oracle Communications Cloud Native Core DBTier User Guide.
  • DBTier Support for Multi Channel Georeplication: DBTier supports multichannel georeplication feature that improves the georeplication performance between sites by replicating multiple databases parallelly. As a part of this feature, the DBTier site addition procedure has been updated to support multichannel georeplication feature. This feature also introduces the procedure to convert a single replication channel group to multiple channel replication group. For more information about the feature, see Oracle Communications Cloud Native Core DBTier User Guide.
  • DBTier Rollback Procedure: DBTier supports rollback from DBTier version 22.3.x to release 22.2.x and release 22.1.x. For more information on the rollback procedures, see Oracle Communications Cloud Native Core DBTier Disaster Recovery Guide.
  • TLS Security Scan: Manual procedure to run TLS Security has been introduced in this release. This procedure will be integrated in the CI/CD pipeline in the next release.
  • New Versions of MySQL Cluster Software: Oracle MySQL Cluster Database - 8.0.30 software is upgraded in this release.

2.6 Cloud Native Environment (CNE)

Oracle Communications Cloud Native Environment (OCCNE) 22.3.x has been updated with the following enhancements:

Release 22.3.3

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

Release 22.3.1

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

Release 22.3.0

Oracle Communications Cloud Native Environment (OCCNE) 22.3.0 has been updated with the following enhancements:
  • Virtual CNE Load Balancer Support for TLS: 5G Network Functions use TLS to encrypt communications between themselves. However, until the current release, the load balancers used in virtualized OCCNE deployments were not supporting TLS and blocked the TCP and HTTP connections. Now, OCCNE load balancers support TLS-encrypted protocols, such as HTTPS. This enables the load balancers to establish and manage TLS on TCP and HTTP connections.
  • Enhanced Virtual CNE Load Balancer Switchover Performance: In case of an Active Load Balancer VM (LBVM) failure, the system took excessive time to switchover between an active and standby Load balancer. Now, the LBVM switchover time has been considerably improved. In most cases, the switchover time is reduced by at least 75%.
  • Bastion Host Liveness Alerts: New alerting rules have been defined in OCCNE to raise alerts when a Bastion Host becomes unavailable. For more information on these alerts, see Oracle Communication Cloud Native Environment User Guide.
  • Supports New Version of Common Services: CNE is now compatible with the following common services versions:
    • Helm - 3.8.2
    • Kubernetes - 1.23.7
    • containerd - 1.6.4
    • Calico - 3.22.3
    • MetalLB - 0.12.1
    • Prometheus - 2.36.1
    • Grafana - 7.5.11
    • Jaeger - 1.28.0
    • Istio - 1.13.2
    • cert-manager - 1.6.2

Operation Service Overlays (OSO)

Operation Service Overlays (OSO) 22.3.x has been updated with the following enhancements:

Release 22.3.2
Operation Service Overlays (OSO) 22.3.2 has been updated with the following enhancements:
  • New Versions of Services: The following services are upgraded in this release:

    • Prometheus - 2.39.1
    • configmap-reload - 0.8.0
Release 22.3.1
Operation Service Overlays (OSO) 22.3.1 has been updated with the following enhancements:
  • New Versions of Services: The following services are upgraded in this release:

    • NGINX Ingress Controller - 1.3.1
    • configmap-reload - 0.7.0
Release 22.3.0

Operation Service Overlays (OSO) 22.3.0 has been updated with the following enhancements:

  • Restoration of OSO non-HA Prometheus version: The previous version of OSO used Prometheus Operator to implement HA Prometheus (High Availability Prometheus). Prometheus Operator requires the creation of CRD definitions to operate. The customers were unable to create CRD definitions as ClusterRole permissions are required to create CRD definitions. To overcome these restrictions, OSO 22.3.0 has excluded Prometheus Operator and has restored the non-HA Prometheus version. For information on OSO installation, see Oracle Communications Operations Services Overlay (OSO) Installation Guide.

  • New Versions of Services: The following services are upgraded in this release:

    • Prometheus - 2.36.1
    • Grafana - 7.5.11

2.7 Cloud Native Core Policy (CNC Policy)

Release 22.3.4

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

Release 22.3.3

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

Release 22.3.2

Oracle Communications Cloud Native Core Policy 22.3.2 has been updated with the following enhancements:
  • Subscriber Tracing Support for AM Policy Service: CNC PCF supports subscriber tracing for AM policy that allows defining a list of subscribers that you may require to troubleshoot the NFs and trace the logs. For more details, see the "Subscriber Activity Logging" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Subscriber Tracing Support for UE Policy Service: CNC PCF supports subscriber tracing for UE policy that allows defining a list of subscribers that you may require to troubleshoot the NFs and trace the logs. For more details, see the "Subscriber Activity Logging" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Handling Stale Data in PDS for AM Service and UE Policy Service: This feature leverages the resetContext and revalidation functionalities in PDS to handle the stale PDS subscriber data when there are multiple sessions for AM Service or UE Policy Service. For more details, see "Handling Stale Data in PDS" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Limiting the Number of Sessions for AM Service and UE Policy Service: This feature enables to configure the Max Session Limit Per User for a subscriber when Enable Max Session Limit flag is enabled for a policy service. This avoids duplicate and stale data in the respective policy service databases (such as AMPolicyAssociations and UEPolicyAssociations). For more details, see "Limiting the Number of Sessions" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Stale Session Detection and Handling in UE Service: The Existing stale session detection and handling functionality in CNC Policy is enhanced to identify and remove the stale sessions for UE Policy Service. A UE Policy Association on PCF is considered as stale when the association exists in PCF, but has no corresponding session on the AMF. When a UE Policy Association is detected as stale, the UE Policy Service deletes the association from the database. For more details on Stale Session Detection and Handling in UE Service, see "Stale Session Handling" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Support for MSISDN/GPSI lookup Key to Fetch N36 (Nudr) Record: CNC Policy supports MSISDN or GPSI as N36 key. For more information, see "PCF User Connector'' section in Oracle Communications Cloud Native Core Policy User Guide.

Release 22.3.1

Oracle Communications Cloud Native Core Policy 22.3.1 has been updated with the following enhancements:
  • Enhancements to Aspen Service Mesh (ASM) Sidecar configuration: The ASM Sidecar configuration is enhanced with the addition of Authorization Policy (AP) and Virtual Service (VS) CRDs to the Data Plane. The Service Mesh Authorization Policies at the ingress side-car associated with a server are used to filter requests originating from the clients using one of the identifiers (SPIFFE, FQDN or NF-type) contained within the client certificate.

    For more details, see the "Aspen Service Mesh Configurations" section in Oracle Communications Cloud Native Core Policy Installation Guide.

  • Support for enabling or disabling controlled shutdown feature: CNC Policy supports enabling or disabling controlled shutdown feature. To enable the feature, set the value of enableControlledShutdown flag to true in the custom.yaml file.

    For more details, see the "Controlled Shutdown Configuration" section in Oracle Communications Cloud Native Core Policy Installation Guide.

Release 22.3.0

Oracle Communications Cloud Native Core Policy 22.3.0 has been updated with the following enhancements:

  • Subscription to Notification Support for Signaling Path Status: CNC Policy supports notification, subscription to notification, and cancellation of the subscription to notification for signaling path status. For more information on this feature and its configurations, see the "Subscription to Notification Support for Signaling Path Status" section in Oracle Communications Cloud Native Core Policy User Guide.

  • Enable Controlled Shutdown of an Instance: CNC Policy supports controlled shutdown feature to provide the partial or complete isolation of the site from the network so that the operator can perform necessary recovery procedures when required. For more information on this feature and its configurations, see the "Enable controlled shut down of an instance" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Support for SessionRuleErrorHandling: CNC Policy supports SessionRuleErrorHandling which helps in deciding whether to retain the old session rule, re-install, modify, or remove the session rule. For more information on this feature and its configurations, see the "Support for SessionRuleErrorHandling" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Optimizing Policy Table: Policy table has been enhanced and optimized to have more tables, rows, and columns for the services. For more information on this feature and its configurations, see the "Policy Table" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Support for local configuration of UDR, CHF, NF profile: CNC Policy has implemented new APIs which allow the users to configure UDR/CHF/AMF/BSF NF profile through CM Service API. For more information on this feature and its configurations, see the "NF Profile" section in Oracle Communications Cloud Native Core Policy REST API Guide.
  • Convert PCRF-Core to SpringBoot: The Cloud native PCRF-Core application has been converted from Java to SpringBoot application. For more information on PCRF Core Metrics, see the "PCRF Core Metrics" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Support for Retrying Binding Registration on BSF and generating Alarm to Operator: CNC Policy supports the enhanced binding registration functionality between SM Service and BSF with the Retry Binding Registration on BSF feature. It retries BSF registrations until a maximum number of attempts are reached or the response error code does not match with any of the configured error codes. For more information on this feature and its configurations, see the "Support for Retrying Binding Registration on BSF and generating Alarm to Operator" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Enhancement to use Cached NRF Discovery Responses: Starting with release 22.3.0, PCF is enhanced to maintain a cache of the NF Profiles discovered through the NRF discovery with their query parameters. This functionality enables PCF to use the cached NRF discovery responses in case of NRF discovery failure and expired or suspended NF producers. CNC Policy provides an option to configure the cache per interface,with the default value astrue. For more information on this feature and its configurations, see the "Support for Cached NRF Discovery Responses" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Support for Sd Interface: CNC Policy supports the Sd interface that enables it to communicate with the Traffic Detection Function (TDF). The Sd interface allows provisioning of the Application Detection and Control (ADC) rules from CNC Policy for traffic detection and enforcement at the TDF through Solicited Application Reporting. For more information on this feature and its configurations, see the "Support for Sd Interface" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Support for Concurrency Handling using Bulwark Service: CNC Policy supports the Bulwark service to handle the concurrent requests coming from other Policy services. The Bulwark service integrates with the SM service to handle the concurrent requests for the SM Create and Delete procedures. The SM service integration with Bulwark service handles the concurrent requests for the same subscriber in a concurrent and efficient manner. For more information on this feature and its configurations, see the "Support for Concurrency Handling using Bulwark Service" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Audit support for Binding service: CNC Policy supports the Audit configurations for the Binding service. For more information about the enhanced configuration, see the "Configuring CNC Policy Using CNC Console" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Enhanced Session Viewer User Interface: The Session Viewer user interface in CNC Console for Policy has been enhanced better user experience. For more information, see the "Configuring CNC Policy Using CNC Console" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Perf-Info Capacity Configuration: CNC Policy allows you to configure the capacity for the perf-info service using the Custom Values YAML file during the installation. For more information about the configurations, see the "Customizing CNC Policy" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Enhanced PRE Logs for Policy Table Evaluation: CNC Policy provides enhanced troubleshooting by including table name, column name, and row value in the PRE Logs instead of the Hex ID of the table, column, and row. For more information about the configurations, see the "Logs" section in Oracle Communications Cloud Native Core Policy Troubleshooting Guide.

2.8 Network Exposure Function (NEF)

Oracle Communications Cloud Native Core Network Exposure Function (NEF) 22.3.x has been updated with the following enhancements:

Release 22.3.2

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

Release 22.3.1

Oracle Communications Cloud Native Core Network Exposure Function (NEF) 22.3.1 has been updated with the following enhancement:
  • Support for Update AF Session with QoS: The OCNEF QoS (Quality of Service) is enhanced to support the PUT and PATCH operations that enable the operators to modify existing QoS subscriptions. For more information about the feature, see the "Support for AF Session with QoS"section in Oracle Communications Cloud Native Core Network Exposure Function User Guide.

Release 22.3.0

Oracle Communications Cloud Native Core Network Exposure Function (NEF) 22.3.0 has been updated with the following enhancements:
  • Support for AF Session with ASQoS: The OCNEF architecture is enhanced to support the QoS (Quality of Service) service that enables the operators to provide quality-related specifications to the 5G Network Functions (NFs). The NFs process the provisioned data to support the services as specified by the operators and send notifications. For more information about the feature, see "Support for AF Session with AsQoS" in Oracle Communications Cloud Native Core Network Exposure Function User Guide.
  • Support for Distributed Architecture: The OCNEF architecture allows the operators to install OCNEF and OCCAPIF components in separate Kubernetes namespaces. For more information about the architecture, see the "OCNEF Architecture" in the Oracle Communications Cloud Native Core Network Exposure Function User Guide.

2.9 Network Repository Function (NRF)

Oracle Communications Cloud Native Core Network Repository Functions (NRF) 22.3.x has been updated with the following enhancements.

OCNRF Release 22.3.2

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

OCNRF Release 22.3.1

Oracle Communications Cloud Native Core Network Repository Functions (NRF) 22.3.1 has been updated with the following enhancement:

  • Support for Parameterization in NRF-ATS: With this feature NRF-ATS GUI has an option to either run the test cases with default product configuration or with custom configuration. You can provide values for the input and output parameters needed for the test cases to be compatible with SUT configuration. You can update the key-value pair values in the global.yaml and feature.yaml files for each of the feature files so that it is compatible with SUT configuration. For more information about the feature, see the "NRF-NewFeatures Pipeline" section in Oracle Communications Cloud Native Core Automated Testing Suite Guide.

OCNRF Release 22.3.0

Oracle Communications Cloud Native Core Network Repository Functions (NRF) 22.3.0 has been updated with the following enhancements:
  • Support for four-site Georedundancy: OCNRF is enhanced to support four-sites Geographical Redundant (Georedundant) deployment. It offers, four-sites, three-sites, and two-sites georedundancy to ensure service availability when one of the OCNRF sites is down. For more information about the feature, see the "OCNRF Georedundacy" section in Oracle Communications Cloud Native Core Network Repository Function User Guide.
  • Support for Notification Retries: OCNRF supports notification retry mechanism in case of failures in sending Notification message. Based on the configured Notification Retry Profile, the OCNRF attempts to re-send the Notification message on failures until the retry attempt is exhausted. For more information about the feature, see "Notification Retry" section in Oracle Communications Cloud Native Core Network Repository Function User Guide.
  • Support for HA and PDB for NRF Auditor POD: OCNRF supports two pods of Auditor microservice to provide High Availability (HA) and PodDisruptionBudget (PDB) functionality. For more information about the feature and the list of services supporting HA and PDP, see "PodDisruptionBudget Kubernetes Resource" section in Oracle Communications Cloud Native Core Network Repository Function Installation and Upgrade Guide.
  • Support for R16 NFs CBCF and NSSAAF: OCNRF supports the following 3GPP TS 29.510 Release 16 nfTypes:
    • Network Slice Specific Authentication and Authorization Function (NSSAAF)
    • Cell Broadcast Center Function (CBCF)
    • Mobility Management Entity (MME)
    • Interrogating Call Session Control Function (ICSCF)
    • Security Assurance Specification (SCSAS)
    • Diameter Routing Agent (DRA)
    • UE Capability Management Function (UCMF)
    • Steering of Roaming Application Function (SOR_AF)
    • Secured Packet Application Function (SPAF)
    • Service Capability Exposure Function (SCEF)
    • IP Multimedia Subsystem Application Server (IMS_AS)

    For more information about the nfTypes, see "Supported NF Types" section in Oracle Communications Cloud Native Core Network Repository Function User Guide.

  • Support for NRF Access Policies to Restrict Ingress and Egress Traffic: OCNRF provides network access policies to enforce access restrictions for all the applicable data flows except communication from Kubernetes node to pod for invoking container probe. For more information about configuring the network policies, see the "Configuring Network Policies" section in Oracle Communications Cloud Native Core Network Repository Function Installation and Upgrade Guide.

2.10 Network Slice Selection Function (NSSF)

Oracle Communications Network Slice Selection Function (NSSF) 22.3.x has been updated with the following enhancements:

NSSF Release 22.3.2

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

NSSF Release 22.3.1

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

NSSF Release 22.3.0

Oracle Communications Network Slice Selection Function (NSSF) 22.3.0 has been updated with the following enhancements:

  • Support for Autopopulation of Configuration Based on NsAvailability Update: Currently, the data received from Nnssf_NSSAIAvailability update is not replicated to the provisional configuration (site-specific database). However, the data are crucial, as they are used in Nnssf_NSSelection service's operations. The operator is required to configure not only the allowed S-NSSAI information from the AMF but also the restricted S-NSSAIs per TAC per PLMN. After this enhancement, the operator need not configure the allowed S-NSSAIs. It will be updated automatically based on the NsAvailability update from the AMF. The operator is required to configure only the restricted S-NSSAI information per TAC per PLMN. For more information, see "Autopopulation of Configuration Based on NsAvailability Update" in Oracle Communications Cloud Native Core Network Slice Selection Function User Guide.
  • Handover from EPS to 5G: This feature allows slice allocation to subscribers when they move from 4G to 5G network. For more information, see "Handover from EPS to 5G" in Oracle Communications Cloud Native Core Network Slice Selection Function User Guide.

2.11 Networks Data Analytics Function (NWDAF)

OCNWDAF Release 22.0.0

This is the first release of Oracle Communications Network Data Analytics Functions (OCNWDAF).

OCNWDAF provides the following features:
  • Data collection from AMF, SMF, and NRF: OCNWDAF interacts with 5G NFs over the Service Based Interface (SBI) directly or through NEF for the data collection. For more information about the data collection by OCNWDAF, see "OCNWDAF Interfaces" section in Oracle Communications Networks Data Analytics Function User Guide.
  • Analytics Generation: OCNWDAF generates various kind of analytics reports for providing analytics information to the consumer NFs. It supports the following types of analytics information:
    • Slice Load level information
    • UE Mobility information
    • UE Abnormal Behavior information (Unexpected UE location)

    For more information about each type of analytics, see the "OCNWDAF Analytics" section in Oracle Communications Networks Data Analytics Function User Guide.

2.12 Service Communication Proxy (SCP)

Oracle Communications Cloud Native Core Service Communication Proxy (SCP) 22.3.x has been updated with the following enhancements.

Release 22.3.4

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

Release 22.3.3

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

Release 22.3.2

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

Release 22.3.1

Oracle Communications Cloud Native Core Service Communication Proxy (SCP) 22.3.1 has been updated with the following enhancements:
  • SCP Observability Enhancement: SCP adds the "User-Agent" header to the SCP originated message requests to NRF. The format of the "User-Agent" header is defined using the userAgentHeaderFormat REST API parameter. This enhancement enables SCP to support User-Agent formats and includes consumer NFs identity as dimensions in SCP metrics, alerts, and logs. The following dimensions are introduced as part of this enhancement to filter SCP metrics based on the consumer NF information: ocscp_consumer_host, ocscp_consumer_nf_instance_id, and ocscp_consumer_nf_type. For more information, see "5G SBI Message Routing" in Oracle Communications Cloud Native Core Service Communication Proxy User Guide.

  • Compliance with ASM 1.11.8 and Kubernetes 1.23.x: SCP deployment has been enhanced to be in compliance with ASM 1.11.8 and Kubernetes 1.23.x. For more information, see Oracle Communications Cloud Native Core Service Communication Proxy Installation and Upgrade Guide.

Release 22.3.0

Oracle Communications Cloud Native Core Service Communication Proxy (SCP) 22.3.0 has been updated with the following enhancements:
  • Enhanced NF Status Processing: The existing Network Function (NF) Status Processing feature is enhanced to enable SCP to route 5G Service Based Interface (SBI) message requests to the SUSPENDED target producer NF if the REGISTERED alternate producer NFs are unavailable or respond with an error code that qualifies for rerouting. For more information, see "Enhanced NF Status Processing" in Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
  • Ingress Rate Limiting Using the User-Agent Header: The existing Ingress Rate Limiting feature is enhanced to enable SCP to use the User-Agent or XFCC header in the ingress message request to identify the consumer NF and apply ingress rate limiting at the ingress side. For more information, see "Ingress Rate Limiting" in Oracle Communications Cloud Native Core Service Communication Proxy User Guide.

2.13 Security Edge Protection Proxy (SEPP)

Oracle Communications Cloud Native Core Security Edge Protection Proxy (SEPP) 22.3.x has been updated with the following enhancements:

SEPP Release 22.3.2

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

SEPP Release 22.3.1

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

SEPP Release 22.3.0

Oracle Communications Cloud Native Core Security Edge Protection Proxy (SEPP) 22.3.0 has been updated with the following enhancements:

  • SBI Message Mediation Support: The 5G SBI Message Mediation Support feature at SEPP allows Mobile Network Operators (MNO)s to resolve the inter-op issues between PLMNs by manipulating the inter-PLMN messages. The SEPP must use the mediation service to support message mediation. The MNO shall rely on mediation service capabilities to provision the mediation rules. The SEPP shall support the following mediation trigger points to invoke mediation service:
    • Ingress inter-PLMN and core network messages
    • Egress inter-PLMN
    For more information about the feature, see the "5G SBI Message Mediation Support" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide and the "Configuration Parameters" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.
  • Topology Hiding Phase 3: SEPP provides message filtering and policing on inter-PLMN control plane interfaces and topology hiding. Topology hiding is a security feature in 5G that secures the address of the network elements and can prevent attacks intended for unauthorized access to network elements or interruption of the network service. The purpose of the feature is to enable topology hiding of information from the home or visited PLMN to the visited or Home PLMN. Topology hiding conceals identity information from all messages leaving a PLMN. Topology hiding Phase 3 supports the topology hiding of both body and header of the message. For more information about the feature,see the "Topology Hiding" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide and the "Configuration Parameters" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.
  • Support of TLS for Roaming Hubs and IPX Providers: Oracle SEPP is deployed by both Mobile Network Operators (MNO) and Internetwork Packet Exchange (IPX) providers. The roaming hub feature allows the user to deploy OCSEPP in either 5GC SEPP NF mode or Roaming Hub mode. For more information about the feature, see the "Support of TLS for Roaming Hubs and IPX Providers" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide and the "Overview" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.
  • Support for Upgrade and Rollback through CDCS: In addition to SEPP's Command Line Interface (CLI) deployment method, SEPP can be deployed using the Continuous Delivery Control Server (CDCS), which is a centralized server that automates SEPP deployment processes of the upgrade and rollback. For more information about the feature, see the "Upgrading SEPP" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.
  • Overload control feature: OCSEPP supports overload control to protect the pn32f-svc microservice from overload situations and maintain the overall health of the service. This feature helps you to protect, mitigate, and avoid entering into an overload condition, detect overload conditions, and take necessary actions to recover from overload on the basis of CPU and memory usage. N32 Ingress Gateway allows or discards incoming requests, based on the overload threshold applied or on the basis of SBI message priority. For more information about the feature, see the "Overload Control Feature" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide and the "Configuration Parameters" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.
  • Global Rate Limiting on Egress Gateway of SEPP: Global rate limiting feature is provided by Egress Gateway (plmn egress-gateway and n32-egress-gateway). With this feature, OCSEPP secures the network when aggregated egress traffic exceeds the allowed traffic rate limit. If the traffic exceeds the allowed traffic rate limit, OCSEPP does not process the traffic and responds with an error code. Egress global rate limiting the functionality of the OCSEPP allows the user to configure the acceptable egress traffic rate to any registered NF instance. For more information about the feature, see the "Global Rate Limiting on Egress Gateway of SEPP" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide and the "Configuration Parameters" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.

  • Security Counter Measure Service API Validation feature: There are certain 5G SBI messages which need not traverse networks (example: AMF and SMF interactions, NRF registration requests). The feature blocks these kinds of messages from traversing networks. The Security Counter Measure Service API Validation feature allows the operator to configure the allowed service APIs at the SEPP. The feature intends to support this in two ways:
    • Check the combination of METHOD and Service requested (Example: POST cannot be used in combination with a particular service).
    • Allows only certain SBI messages to either egress or ingress the network (Example: AMF to UDM messages). For more information about the feature,see the "Security Counter Measure Service API Validation" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide and the "Configuration Parameters" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.
  • Helm Test: Helm Test feature validates the installation of SEPP and determines if the Network Function (NF) is ready to accept traffic. For more information about the feature, see the "Performing Post installation Helm test" section and the "Configuration Parameters" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.
  • Helm Validation Framework: The helm validation framework is added to validate the values in custom_values.yaml file with JSON schemas. If the custom-values.yaml file has some incorrect values or not the expected values, this framework will catch the issues initially before starting the deployment or upgrade and display appropriate errors. Using this enhancement, the user can be sure that the deployment happened with the correct expected value. For more information about the feature, see the "Helm Validation Framework" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide and the "Configuration Parameters" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.
  • Enhancement in Subject Alternate Name (SAN) Validation: SAN (Subject Alternate Names) validates whether the SAN in the SEPP certificate matches with the sender FQDN received in the capability-exchange message. Previously (before SEPP Release 22.3.0), the SAN validation is a mandatory configuration for the regular SEPP deployments. With this enhancement, the SAN validation has become optional. The user now has the flexibility to either perform the validation on SAN or avoid validation as per the environment. For more information about the feature, see the "Enhancement in Subject Alternate Name (SAN) Validation" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide and the "Configuration Parameters" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.

2.14 Unified Data Repository (UDR)

Oracle Communications Cloud Native Core Unified Data Repository (UDR) 22.3.x has been updated with the following enhancements:

Release 22.3.4

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

Release 22.3.3

Oracle Communications Cloud Native Core Unified Data Repository (UDR) 22.3.3 has been updated with the following enhancements:
  • Support for Subscriber Location Function (SLF) - Periodic Export of Subscriber Database: This feature supports periodic exporting of SLF subscriber data into Comma Separated Value (CSV) file format using the Subscriber Export Tool. The Subscriber Export Tool is scheduled for daily runs and is deployed as a stand-alone tool. It also supports dynamic configuration of periodicity of export. For more information about the feature, see "Supports Periodic Export of SLF Subscriber Database", see Oracle Communications Cloud Native Core Unified Data Repository User Guide.

Release 22.3.2

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

Release 22.3.1

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

Release 22.3.0

Oracle Communications Cloud Native Core Unified Data Repository (UDR) 22.3.0 has been updated with the following enhancements:
  • Support for 5G EIR Signaling: This feature introduces 5G Equipment Identity Register (EIR) functionality in the UDR. UDR will support a separate deployment mode for 5G EIR. For more information about the feature, see "Support for 5G EIR Signaling" in Oracle Communications Cloud Native Core Unified Data Repository User Guide. 5G EIR supports:
    • REST/JSON based provisioning of 5G EIR profile
    • Provisioning of 5G EIR entries via CNC Console or REST API
    • N5g-eir_EquipmentIdentityCheck Service API. N5g-eir is the service-based interface as defined by 3GPP
    • NRF registration of the EIR service
    • EIR Access Log for black and grey listed Permanent Equipment Identifier (PEI)
    • Bulk Import of 5G EIR subscriber data via PDBI interface
  • Support for 5G EIR Bulk Provisioning: 5G EIR supports bulk provisioning of subscriber data via the batch files. This feature provides the capability of processing the batch files containing Eagle EPAP supported PDBI provisioning commands that enable deployment of 5G EIR in stand-alone mode. Bulk Import tool can be used to provision EIR subscribers using PDBI format. For more information about the feature, see "Support for 5G EIR Bulk Provisioning" and "Bulk Import Tool for EIR" in Oracle Communications Cloud Native Core Unified Data Repository User Guide.
  • Subscriber Activity Logging: This feature enhances the logging functionality by UDR to support subscriber-specific logging. This enables the operators to log the subscriber activity for the configured list of subscribers. You can define a list of subscribers for which the logging is required, and this can be controlled irrespective of the log level that is enabled for UDR. You can collect the message exchanges, subscriber specific decision making, and logic handling for specific subscribers. For more information about the feature, see "Subscriber Activity Logging" in Oracle Communications Cloud Native Core Unified Data Repository User Guide.