1. Cloud Native Core Release Notes
  2. Feature Descriptions

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

2.1 Automated Testing Suite (ATS) Framework

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

  • Application Log Collection: Application Log Collection can be implemented by using either ElasticSearch or Kubernetes Logs. In both these implementations, logs are collected per scenario for the failed scenarios. For more information, see Oracle Communications Cloud Native Core Automated Testing Suite Guide.
  • ATS Jenkins Job Queue: This feature provides the support of queuing the second job if the current job is already running whether from the same pipelines or different pipelines. For more information, see Oracle Communications Cloud Native Core Automated Testing Suite Guide.
  • ATS System Name and Version Display on Jenkins GUI: With this feature, ATS system name and version are displayed on Jenkins GUI. For more information, see Oracle Communications Cloud Native Core Automated Testing Suite Guide.
  • PCAP Log Collection: PCAP Log Collection allows collecting the NF, SUT, or PCAP logs from the debug tool side car container. For more information, see Oracle Communications Cloud Native Core Automated Testing Suite Guide.

2.2 Binding Support Function (BSF)

Release 22.2.4

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

Release 22.2.3

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

Release 22.2.1

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

Release 22.2.0

Oracle Communications Cloud Native Core Binding Support Function (BSF) 22.2.0 has been updated with the following enhancements:

  • Overload Control - Diameter Interface: BSF supports the load shedding and overload control mechanisms for Diameter interface that reduce latency in overload situations and maintain the overall health of the system. With this feature, BSF avoids entering into overload condition, detects overload conditions, and then takes necessary actions to recover from the overload state. For more information on this feature and its configurations, see the "Overload Control - Diameter Interface" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.
  • Overload Control and Handling - SBI Interface: BSF supports the rate limiting and overload control for SBI interface that prevent service performance from degrading in an uncontrolled manner under heavy load. As BSF management service starts approaching its saturation or planned limit, response times typically grow high and throughput may degrade substantially. Under such conditions, it is desirable to shed load based on operator configuration, rather than cause all sessions and signaling flows to experience unacceptable response times or failures or downtime. For more information on this feature and its configurations, see the "Overload Control - SBI Interface" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.
  • Stale Session Handling with PCF Interaction: BSF supports the stale session handling feature as part of which the Audit service detects stale sessions automatically at regular intervals. During the audit, if the audit service finds records with a binding age greater than the configured value, it marks such records as suspected stale and notifies the BSF management service. Depending on the feature configurations, BSF may query PCF to confirm if the records are stale. If PCF confirms the record as stale, then BSF removes it from its local database. For more information on this feature and its configurations, see the "Stale Session Handling" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.
  • BSF Observability Enhancements: BSF metrics are enhanced to be adapted to the cloud-native infrastructure. For more information on this feature, see the "Binding Support Function Metrics" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.
  • Detection and Handling of Late Arrival Requests: BSF supports the detection and handling of late arrival requests to detect the response time for the components received in the headers from the PCF. For more information on how to configure this feature using CNC Console, see the "Detection and Handling of Late Arrival Requests" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.
  • CNCC Support for Multicluster Deployment: With this feature, BSF deployed in multiple Kubernetes clusters can be accessed using CNC Console. In a multicluster deployment, the CNC Console can manage BSF and OCCNE common services deployed in the remote Kubernetes clusters. For more information on this feature, see Oracle Communications Cloud Native Core Binding Support Function User Guide.
  • CNCC Support for Multiple Instance Deployment: With this feature, multiple instances of BSF deployed within a Kubernetes cluster can be accessed using CNC Console. In a Multiple instances deployment, the CNC Console can manage multiple BSF instances and OCCNE common services deployed within a Kubernetes cluster. For more information, see Oracle Communications Cloud Native Core Binding Support Function Guide.

2.3 Continuous Delivery Control Server (CDCS)

The CD Control Server (CDCS) is a Continuous Delivery (CD) solution for the Oracle CNC product line. CDCS acts as a centralized location from which to perform lifecycle operations for CNC 5G NFs, and OCCNE, at multiple sites within a customer's network. This is the initial release of the CD Control Server. For more information about the CD Control Server, see Oracle Communications Cloud Native Core CD Control Server User Guide and Oracle Communications Cloud Native Core CD Control Server Installation Guide.

CD Control Server is compatible with the following NF versions:
  • cnDBTier 22.2.0
  • SCP 22.2.0
  • SEPP 22.2.0

2.4 Cloud Native Core Console (CNC Console)

Oracle Communications Cloud Native Core Console (CNC Console) 22.2.0 has been updated with the following enhancement:

Release 22.2.2

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

Release 22.2.1

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

Release 22.2.0

  • Integrated NSSF with CNC Console: With this feature, Network Slice Selection Function (NSSF) can be integrated with the CNC Console. The integration allows the users to configure NSSF using the CNC Console. For more information, see Oracle Communications Cloud Native Core Console User Guide.
  • Support for Multicluster Deployment for NFs: CNC Console supports NF deployment across Kubernetes clusters using Manager CNC Console IAM (M-CNCC IAM), Manager CNC Console Core (M-CNCC Core), and Agent CNC Console Core (A-CNCC Core). In a multicluster deployment, the CNC Console can manage NFs and OCCNE common services deployed in the remote Kubernetes clusters. The multicluster deployment for the following NFs are supported:
    • SCP 22.2.0
    • NRF 22.2.0
    • UDR 22.2.0
    • SEPP 22.2.0
    • NSSF 22.2.0
    • BSF 22.2.0
    • POLICY 22.2.0 (Supports from 22.1.0 onwards)
    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.
  • Support for Multiple Instances of NFs within a cluster: CNC Console supports multiple instances of NFs within a Kubernetes cluster using Manager CNC Console IAM (M-CNCC IAM), Manager CNC Console Core (M-CNCC Core), and Agent CNC Console Core (A-CNCC Core). The multiple instances of the following NFs are supported:
    • SCP 22.2.0
    • NRF 22.2.0
    • UDR 22.2.0
    • BSF 22.2.0
    • POLICY 22.2.0 (Supports from 22.1.0 onwards)
    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.
  • Support for Ephemeral Storage: CNC Console supports the configuration of ephemeral containers for the temporary storage of data of instances. The Pods use ephemeral local storage for scratch space, caching, and logs. For more information about ephemeral storage resource requirements, 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.2.0
    • NRF 22.2.0
    • UDR 22.2.0
    • SEPP 22.2.0
    • NSSF 22.2.0
    • BSF 22.2.0
    • POLICY 22.2.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)

Release 22.2.5

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

Release 22.2.4

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

Release 22.2.3

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

Release 22.2.2

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

Release 22.2.1

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

Release 22.2.0

Oracle Communications Cloud Native Core DBTier (cnDBTier) 22.2.0 has been updated with the following enhancements:
  • Support for DBTier Dual Stack Support: DBTier is validated on an IPv6 mode in dual stack Kubernetes cluster. For more information about the parameter to configure IPv6, see Oracle Communications Cloud Native Core DBTier Installation and Upgrade Guide.
  • Support for DBTier roll back: Rollback is supported from DBTier version 22.2.x to release 22.1.x and release 1.10.x. For more information about the rollback, see Oracle Communications Cloud Native Core DBTier Installation and Upgrade Guide.
  • Support for TLS for Georeplication: DBTier TLS procedure is extended to provide manual steps to DBTier customer(s) to enable TLS support for the Georeplication channels between three and four mate sites. For more information about the TPS procedure, see Oracle Communications Cloud Native Core DBTier User Guide.
  • Support for DBTier Multus CNI: DBTier supports Multus Container Network Interface (CNI). For more information about the Multus CNI, see Oracle Communications Cloud Native Core DBTier Installation and Upgrade Guide.

2.6 Cloud Native Core Policy (CNC Policy)

Release 22.2.6

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

Release 22.2.5

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

Release 22.2.4

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

Release 22.2.3

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

Release 22.2.2

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

Release 22.2.1

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

Release 22.2.0

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

  • Overload Control and Handling - SBI Interface: CNC Policy supports the rate limiting and overload control for SBI interface that prevent service performance from degrading in an uncontrolled manner under heavy load. As CNC Policy microservices start approaching their planned limit, response times typically grow high and throughput may degrade substantially. Under such conditions, it is desirable to shed load based on operator configuration, rather than cause all sessions and signaling flows to experience unacceptable response times or failures or downtime. For more information on this feature and its configurations, see the "Overload Control - SBI Interface" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Support for Usage Monitoring in PCRF Core: CNC Policy supports Usage Monitoring service, an internal service that interacts with Policy PRE service to get usage monitoring related Policy decisions. Using this internal service, CNC Policy can apply usage monitoring control at session level. The usage can be defined as either volume or time of user plane traffic. Currently, Usage Monitoring service is supported for PCRF only. For more information, see "Usage Monitoring Service" in Oracle Communications Cloud Native Core Policy User Guide.
  • PCF Registration Status on NRF from CNC Console - CNC Policy GUI is enhanced to include a new page - NRF Status under the Status and Query page in the CNC Console. Using this page, users can get a consolidated status of the PCF registered with NRF and also displays the autonomously discovered NFs details like CHF and BSF . This new page displays the health status of primary and secondary NRFs, or alternate NRF as well. For more information on this feature and its configurations, see Oracle Communications Cloud Native Core Policy User Guide.

  • NetLoc Support: CNC Policy supports NetLoc which helps in fetching User Equipment (UE) time zone information and User location information from the access network. Such information is called Network Provided Location Information (NPLI). For more information on this feature and its configurations, see the "NetLoc Support" section in Oracle Communications Cloud Native Core Policy User Guide.

  • Subscription to Notification Support for Signaling Path Status: CNC Policy supports notification, subscription to notification, and cancellation of subscription to notification of 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.

  • SBI Timer Handling Enhancements: CNC Policy is enhanced to configure timer per message type on Nudr and Nnrf SBI interfaces. For more information on this feature and its configurations, see the "SBI Timer Handling Enhancements" section in Oracle Communications Cloud Native Core Policy User Guide.

  • UE Policy Enhancements: CNC Policy is enhanced to support UE Route Selection Policy (URSP) for transferring fragmented UE Policy and handling N1N2Message transfer Failure. For more information on this feature and its configurations, see the "UE Policy Enhancements" section in Oracle Communications Cloud Native Core Policy User Guide.

  • Support for Detection and Handling of Late Arrival Requests: CNC Policy is enhanced to support the detection and handling of late arrival functionality in BSF. For more information on this feature and its configurations, see the "PCF Support for Detection and Handling of Late Arrival Requests in BSF" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Support for Subscriber Notification - HTTP: CNC Policy supports Notifier service that allows CNC Policy to send notifications (HTTP messages) to the subscribers about their current data usage. This service is independent of deployment mode and can be enabled in all the supported deployment modes. For more information on this feature, see the "Notifier service" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Operator Specific Data support for 4G Subscriber over N36 Interface: With this feature, CNC Policy supports retrieving operator specific data from PCRF core on nUDR interface on receiving Gx query. For more information, see Oracle Communications Cloud Native Core Policy User Guide.
  • Session Retry with NF Sets: CNC Policy supports enhanced session retry and alternate routing mechanisms based on NRF Discovery and rediscovery for initial messages and DNS SRV based for subsequent messages in indirect communication model for AM and UE services. For more information on this feature, see the "Session Retry" section in Oracle Communications Cloud Native Core Policy User Guide.
  • Support for Stale Binding Detection in BSF: To support BSF to query PCF for suspected stale binding records, the Binding service has been made mandatory in the PCF mode of deployment. In BSF, whenever a binding record is detected as stale on the expiry of its binding age, BSF may send a query to PCF to confirm its status. To support this query to PCF, PCF is first required to send the Vendor-Specific-Attribute containing PCF Notification URL in the Binding Register request. When PCF sends the Vendor-Specific-Attribute in the register request, it is also required to provide the vendorID. For more information on this feature, see Oracle Communications Cloud Native Core Converged Policy User Guide.
  • CNCC Support for Multicluster Deployment: With this feature, CNC Policy deployed in multiple Kubernetes clusters can be accessed using CNC Console. In a multicluster deployment, the CNC Console can manage CNC Policy and OCCNE common services deployed in the remote Kubernetes clusters. For more information on this feature, see Oracle Communications Cloud Native Core Converged Policy User Guide.
  • CNCC Support for Multiple Instance Deployment: With this feature, multiple instances of CNC Policy deployed within a Kubernetes cluster can be accessed using CNC Console. In a Multiple instances deployment, the CNC Console can manage multiple CNC Policy instances and OCCNE common services deployed within a Kubernetes cluster. For more information, see Oracle Communications Cloud Native Core Converged Policy User Guide.

2.7 Cloud Native Environment (CNE)

Release 22.2.3

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

Release 22.2.2

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

Release 22.2.1

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

Release 22.2.0

Oracle Communications Cloud Native Environment (OCCNE) 22.2.0 has been updated with the following enhancements:
  • Encrypted Kubernetes Secrets with key renewal: OCCNE supports automatic encryption of all Secrets stored in the Kubernetes cluster. The key used to encrypt the secrets can be rotated as necessary. For more information about the feature, see Oracle Communications Cloud Native Environment User Guide.
  • Supports the Upgraded versions of Cloud Native Platform Services: OCCNE supports the following upgraded versions of cloud native platform services:
    • Helm - 3.8.0
    • Kubernetes - 1.22.5
    • containerd - 1.5.8
    • Calico - 3.20.3
    • MetalLB - 0.12.1
    • Rook (BM installations only) - 1.8.4
    • Prometheus - 2.32.1
    • Grafana - 7.5.11
    • Elasticsearch - 7.9.3
    • Kibana - 7.9.3
    • Jaeger - 1.28.0
    • Istio - 1.12.1
    • cert-manager - 1.6.1

2.8 Network Exposure Function (NEF)

Release 22.2.2

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

Release 22.2.1

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

Release 22.2.0

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

GMLC Based Location Monitoring: OCNEF is enhanced to support the Gateway Mobile Location Center (GMLC) Based Location Monitoring feature. This feature enables OCNEF to report the highly accurate location details of subscribers with their geographic information through GMLC. For more information about the feature, see Oracle Communications Cloud Native Core Network Exposure Function User Guide.

Support for Model-D Indirect Communication: OCNEF supports the Model-D of the indirect communication method. This feature enables OCNEF to configure the necessary discovery and selection parameters required to find a suitable producer NF for handling a service request through SCP. For more information about the feature, see Oracle Communications Cloud Native Core Network Exposure Function User Guide.

OCNEF Exposure Gateway Event Management: The OCNEF architecture is enhanced to support the Event Manager service that enables OCNEF to notify Application Functions (AFs) or other internal services about the events occurring at the Exposure Gateway. For more information about the feature, see Oracle Communications Cloud Native Core Network Exposure Function User Guide.

Support for PodDisruptionBudget: OCNEF supports the PodDisruptionBudget (PDB) Kubernetes resource to provide high availability of scalable application services. For more information about the PDB specifications, see Oracle Communications Cloud Native Core Network Exposure Function Installation Guide.

2.9 Network Repository Function (NRF)

OCNRF Release 22.2.3

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

OCNRF Release 22.2.2

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

OCNRF Release 22.2.1

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

OCNRF Release 22.2.0

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

  • Support for EmptyList in Discovery Response: When the feature is enabled, if all the matching profiles for a discovery request are in "SUSPENDED" state, OCNRF allows to change the profile state to "REGISTERED" by configuring a shorter validity period. For more information about the feature, see Oracle Communications Cloud Native Core Network Repository Function User Guide.

  • Support for Overload Control based on Percentage Discards: OCNRF supports overload control to protect the nfregister, nfdiscovery, and nfaccesstoken services from overload situations and maintain the overall health of the services. 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. For more information about the feature, see Oracle Communications Cloud Native Core Network Repository Function User Guide.

  • Support for PodDisruptionBudget: PodDisruptionBudget (PDB) is a Kubernetes resource that allows you to achieve high availability of scalable application services when the cluster administrators perform voluntary disruptions to manage the cluster nodes. For more information about the feature and the list of services supporting PDB, see Oracle Communications Cloud Native Core Network Repository Function Installation and Upgrade Guide.

  • Support for nfServiceList Map Attribute in NF Profile: OCNRF now supports nfServiceList attribute (as per 3GPP Specification 3GPP TS 29.510 v16.7.0) in the NFProfile data type to include the map of NF service Instances, where the "serviceInstanceId" attribute of the NFService object is used as the key of the map. This map attribute includes the services produced by the NF that can be discovered by other NFs, if any.
  • Support for Tai attribute for UPF Profiles: OCNRF supports User Plane Function (UPF) discovery based on discovery query parameter such as Tracking Area Identity (tai) and preferred Tracking Area Identity (preferred-tai). When OCNRF receives a discovery request with UpfInfo attribute, it processes the request based on the UPF profiles that can serve the TAI. For more information, see 3GPP Specification 3GPP TS 29.510 v16.7.0.
  • Support for 3gpp-Sbi-Correlation-Info header: OCNRF supports 3gpp-Sbi-Correlation-Info header to enable network analytic tools or probes to easily identify the messages exchanged for a given User Equipment (UE). The Network Function (NF) service consumer or NF service producer can include any one of the UE identifiers (such as imsi, msisdn, extiid) in its 3gpp-Sbi-Correlation-Info header. The identifier helps to identify the UE related to the HTTP request or response. For more information about the add3gppSbiCorrelationInfoHeader parameter, see Oracle Communications Cloud Native Core Network Repository Function User Guide.
  • Support for DNS NAPTR Update: OCNRF supports updating the Name Authority Pointer (NAPTR) record in Domain Name System (DNS) during Access and Mobility Functions (AMF) registration, update, and deregistration. For more information about the feature, see Oracle Communications Cloud Native Core Network Repository Function User Guide.
  • Support for Multicluster Deployment: With this feature, OCNRF deployed in multiple Kubernetes clusters can be accessed using CNC Console. In a multicluster deployment, the CNC Console can manage OCNRF and OCCNE common services deployed in the remote Kubernetes clusters. For more information on this feature, see For more information about single and multiple cluster deployments, see Oracle Communications Cloud Native Core Network Repository Function User Guide.
  • Support for Multiple Instance Deployment: With this feature, multiple instances of OCNRF deployed within a Kubernetes cluster can be accessed using CNC Console. In a Multiple instances deployment, the CNC Console can manage multiple OCNRF instances and OCCNE common services deployed within a Kubernetes cluster. For more information, see Oracle Communications Cloud Native Core Network Repository Function User Guide.

2.10 Network Slice Selection Function (NSSF)

Release 22.2.2

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

Release 22.2.1

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

Release 22.2.0

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

  • Support for CNC Console: Starting with this release, OCNSSF support CNC Console to configure the managed objects. For more information, see "Configuring OCNSSF Using CNC Console" in Oracle Communications Cloud Native Core Network Slice Selection Function User Guide.
  • Support for three-sites Georedundancy: OCNSSF supports up to three-sites Georedundancy to ensure service continuity when one of the OCNSSF sites is down. For more information, see "Georedundancy" in Oracle Communications Cloud Native Core Network Slice Selection Function User Guide.
  • Support for Multicluster Deployment: With this feature, OCNSSF deployed in multiple Kubernetes clusters can be accessed using CNC Console. In a multicluster deployment, the CNC Console can manage OCNSSF and OCCNE common services deployed in the remote Kubernetes clusters. For more information on this feature, see Oracle Communications Cloud Native Core Network Slice Selection Function User Guide.
  • Support for Multiple Instance Deployment: With this feature, multiple instances of OCNSSF deployed within a Kubernetes cluster can be accessed using CNC Console. In a Multiple instances deployment, the CNC Console can manage multiple OCNSSF instances and OCCNE common services deployed within a Kubernetes cluster. For more information on this feature, see Oracle Communications Cloud Native Core Network Slice Selection Function User Guide.
  • Support for PodDisruptionBudget: PodDisruptionBudget (PDB) is a Kubernetes resource that allows you to achieve high availability of scalable application services when the cluster administrators perform voluntary disruptions to manage the cluster nodes. For more information about the feature and the list of services supporting PDB, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation and Upgrade Guide.

2.11 Service Communication Proxy (SCP)

Release 22.2.4

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

Release 22.2.3

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

Release 22.2.2

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

Release 22.2.1

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

Release 22.2.0

Oracle Communications Cloud Native Core Service Communication Proxy (SCP) 22.2.0 has been updated with the following enhancements:
  • Support for SCP Deployment using Continuous Delivery Control Server (CDCS): In addition to SCP's Command Line Interface (CLI) deployment method, SCP can be deployed using Continuous Delivery Control Server (CDCS), which is a centralized server that automates SCP deployment processes such as downloading the SCP package, installation, upgrade, and rollback. For more information about CDCS, see Oracle Communications Cloud Native Core CD Control Server User Guide. For information about SCP deployment using CDCS, see Oracle Communications Cloud Native Core Service Communication Proxy Installation and Upgrade Guide.
  • Support for Alternate Routing Using Static Configuration: This feature enables operators to configure a pair or combination of primary NFs and their alternate NFs to define alternate producer NFs, which can be used in alternate NF selection when routing attempt to the primary NF fails. For more information, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
  • Aspen Service Mesh (ASM) Data Plane Configuration using Helm: This feature automates the process of ASM data plane configuration through Helm. For more information, see Oracle Communications Cloud Native Core Service Communication Proxy Installation and Upgrade Guide.
  • 5G SBI Message Mediation Support: The existing Mediation functionality is enhanced to enable 5G HTTP2 message manipulation techniques to allow modification of Hypertext Transfer Protocol (HTTP) headers and JSON body parameters. SCP manipulates the incoming HTTP message requests based on the configured rules and responds with the manipulated message to NFs. For more information, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
  • Global Egress Rate Limiting: This feature synchronizes and aggregates the egress rate data for multiple producer NFs among multiple SCP instances (up to three SCP instances). Based on the aggregated rate data, each SCP controls its traffic to ensure that the global configured egress rate is achieved. For more information, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
  • Support for Multicluster Deployment: With this feature, SCP deployed in multiple Kubernetes clusters can be accessed using CNC Console. In a multicluster deployment, the CNC Console can manage SCP and OCCNE common services deployed in the remote Kubernetes clusters. For more information on this feature, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
  • Support for Multiple Instances Deployment: With the support of multiple instance deployment, a single instance of the CNC Console can configure two instances of SCP deployments if both CNC Console and SCP instances are deployed in the same Kubernetes cluster with different namespaces. For more information, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.

2.12 Security Edge Protection Proxy (SEPP)

OCSEPP Release 22.2.2

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

OCSEPP Release 22.2.1

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

  • Support for Upgrade and Rollback: Oracle Communications Cloud Native Core Security Edge Protection Proxy (SEPP) supports upgrade and rollback from release 22.2.0 to 22.2.1. For more information about the upgrade procedure, see Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation and Upgrade Guide.

OCSEPP Release 22.2.0

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

  • Global Rate limiting on ingress gateway of OCSEPP: Global rate limiting, feature provided by Ingress Gateway (plmn-ingress-gateway and n32-ingress-gateway), secures the network when aggregated Ingress traffic from any registered NF instance 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. With this feature, OCSEPP allows the user to configure the acceptable traffic rate from a consumer NF instance as well as configure the maximum number of incoming messages in the given duration.

    For more information about the feature, see Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide and Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation Guide.

  • Support of SEPP deployment through CDCS: Along with the existing Command Line Interface deployment method, OCSEPP can be deployed using Continuous Delivery Control Server (CDCS), which is a centralized server that automates OCSEPP deployment processes. CD Automation feature solves the manual procedures and provides a continuous download, staging, and deployment model. For more information about CDCS, see Oracle Communications Cloud Native Core CD Control Server User Guide and Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation Guide.
  • Support for Multicluster Deployment: Multicluster is a method of deploying an application on or across multiple Kubernetes clusters for improving availability, isolation, and scalability. In a multicluster deployment, the CNC Console can manage OCSEPP deployed in the local or remote Kubernetes clusters.

    For more information about the feature, see Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide.

  • Support for PodDisruptionBudget: PodDisruptionBudget (PDB) is a Kubernetes resource that allows you to achieve high availability of scalable application services when the cluster administrators perform voluntary disruptions to manage the cluster nodes. OCSEPP supports pod disruption budget to enable the availability of minimum replicas for microservices. For more information about the feature, see Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation Guide.
  • Integrated Debug tool: The Debug Tool provides third-party troubleshooting tools for debugging the runtime issues for the lab and production environment. Following are the available tools:
    • tcpdump
    • ip
    • netstat
    • curl
    • ping
    • dig

    For more information about the tools, see Oracle Communications Cloud Native Core Security Edge Protection Proxy Troubleshooting Guide.

  • Support for Server Header: OCSEPP supports server header in the error responses generated for OCSEPP services. Using the server header, the user can find out if the error is generated either by the OCSEPP or some other NF. For more information about the feature, see Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide.
  • Support for Ephemeral Storage: OCSEPP supports the configuration of ephemeral containers for the temporary storage of data of your instances. The Pods use ephemeral local storage for scratch space, caching, and logs. For more information about ephemeral storage resource requirements, see Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation Guide.

2.13 Unified Data Repository (UDR)

Release 22.2.2

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

Release 22.2.1

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

Release 22.2.0

Oracle Communications Cloud Native Core Unified Data Repository (UDR) 22.2.0 has been updated with the following enhancements:
  • Support for LCI and OCI Header: With this feature, UDR supports Load Control Information (LCI) and Overload Control Information (OCI) Headers in Ingress Gateway and Egress Gateway. These headers convey the operating status of the producer resources to the consumer NFs. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
  • Segregation of Ingress Gateway for provisioning and signaling traffic: With this enhancement, UDR supports Ingress Gateway instances for signaling and provisioning. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
  • Support for Multicluster Deployment: With this feature, UDR and SLF deployed in multiple Kubernetes clusters can be accessed using CNC Console. In a multicluster deployment, the CNC Console can manage UDR and SLF and OCCNE common services deployed in the remote Kubernetes clusters. For more information on this feature, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
  • Support for Multiple Instances Deployment: With the support of multiple instance deployment, a single instance of the CNC Console can configure two instances of UDR and SLF deployments if both CNC Console and UDR and SLF instances are deployed in the same Kubernetes cluster with different namespaces. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
  • Support for Taints or Tolerations and Node selector: With this enhancement, UDR or SLF charts support configuring Taints or Tolerations and Node Selector. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
  • PDB Enhancements: With this enhancement, microservices such as app-info, perf-info, config-server, Nudr-config, and NRF-client support multiple pods (HA) and PDBs. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.