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

2.1 Automated Testing Suite (ATS)

Oracle Communications Automated Test Suite framework in CNC 2.22.1 release supports the following enhancement:

• Support for Parameterization in Policy Charging Function (PCF): With this feature ATS GUI has an option to either run 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.

2.2 Binding Support Function (BSF)

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

Release 22.1.4

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

Release 22.1.3

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

Release 22.1.2

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

Release 22.1.1

Support for PodDisruptionBudget Kubernetes Resource: PodDisruptionBudget (PDB) is a Kubernetes resource that allows redistribution of BSF pods to other worker nodes without impacting the BSF microservices. With Pod Disruption Budget (PDB) assigned for each BSF microservice type, Kubernetes maintains a minimum level of availability for replica set and service.

When the pods are evicted and deployed, each PDB is honoured. It helps to achieve the high availability of scalable application services in voluntary disruptions performed by cluster administrators to manage the cluster nodes.

For more information about this feature, see Oracle Communications Cloud Native Core Binding Support Function Installation and Upgrade Guide.

Release 22.1.0

• Support for Timer Configuration: With this feature, you can configure the timer values for the Authentication Request (AAR), Re-Auth-Request (RAR), Session-Termination-Request (STR), and Abort-Session-Request (ASR) messages using the CNC Console. For more information on how to configure the timer values using CNC Console, see the Oracle Communications Cloud Native Core Binding Support Function User Guide. For information on available APIs for this feature, see Oracle Communications Cloud Native Core Binding Support REST Specification Guide.
• SRV Lookup of SCP FQDN for XFCC Header Validation: With this feature, BSF supports the enhanced functionality where BSF as a producer can perform DNS SRV queries on the single virtual configured FQDN for SCP, and find the host SCPs that are authorized to send HTTP Request to BSF. For more information on this feature, see the "XFCC Header Validation" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.
• Support for Server Header: With this feature, BSF supports server header in the error responses received from Ingress Gateway and sent towards Egress Gateway. Using the server header, the user can find out if the error is generated either at the backend microservices or at the Ingress Gateway itself. For more information on this feature, see the "Support for Server Header" section in Oracle Communications Cloud Native Core Binding Support Function User Guide.

2.3 Cloud Native Core Console (CNC Console)

Cloud Native Core Console (CNC Console) 22.1.x has been updated with the following enhancement:

Release 22.1.3

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

Release 22.1.2

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

Release 22.1.1

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

Release 22.1.0

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

• Enhancements in Upgrade Sequence to support Console first upgrade order in multicluster deployment with Policy NF

  Cloud Native Core Console (CNC Console) framework is enhanced to support CNC Console upgrade followed by Network Function (NF) upgrade in a multicluster deployment. This enhancement is supported for CNC Policy from release 22.1.x onwards. For more information, see Oracle Communications Cloud Native Core Console Installation and Upgrade Guide.

• Supported Deployment Models: Following are the supported deployment models.

  Table 2-1 Deployment Details

  Feature	Single Instance or Multiple Instance of NF Support	BSF	NRF	SCP	SEPP	Policy	UDR
  Single Cluster	Single Instance	YES	YES	YES	YES	YES	YES
  	Multiple Instance	NO	NO	NO	NO	NO	NO
  	Upgrade Order (NF Upgrade followed by CNCC Upgrade)	YES	YES	YES	YES	YES	YES
  Multi Cluster	Single Instance	NO	NO	NO	NO	YES	NO
  	Multiple Instance	NO	NO	NO	NO	YES	NO
  	Upgrade Order (CNCC Upgrade first followed by NF Upgrade)	NO	NO	NO	NO	YES	NO

• Supports the latest version of NFs:
  CNC Console is compatible with the following NF version:

  • SCP 22.1.0
  • NRF 22.1.0
  • UDR 22.1.0
  • CNC Policy 22.1.0
  • BSF 22.1.0
  • SEEP 22.1.0

  For more information, see Oracle Communications Cloud Native Core Console Installation and Upgrade Guide.

2.4 Cloud Native Core DBTier (cnDBTier)

Release 22.1.3

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

Release 22.1.2

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

Release 22.1.1

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

• DBTier Rollback Support: Rollback from cnDBTier 22.1.1 to cnDBTier 1.10.x or 1.9.2 is supported.
• Oracle MySQL Cluster Database: DBTier supports Oracle MySQL Cluster Database - 8.0.28 with georeplication performance enhancements Phase 1.

Release 22.1.0

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

• DBTier Disaster Recovery Procedures Automation: DBTier Disaster Recovery procedures are automated to handle the failures in two site, three site, and four site georeplication. For more information about Disaster Recovery procedures, see Oracle Communications Cloud Native Core DBTier Disaster Recovery Guide.
• DBTier Upgrade Procedure Automation: DBTier Upgrade procedure is automated to ease and speed up the upgrade of DBTier. The startup probes and readiness probes are included to enable rolling restart using helm command. DBTier supports Pod Disruption Budget (PDB) to withstand disruption during platform upgrade. For more information about the upgrade procedure, see Oracle Communications Cloud Native Core DBTier Installation and Upgrade Guide.
• Supports TLS for Georeplication: DBTier supports TLS for georeplication channels between two mate sites. For more information about TLS procedure, see Oracle Communications Cloud Native Core DBTier User Guide.
• Rollback Support: Because MySQL downgrade from release 8.0.28 to 8.0.24 is not supported, you can not rollback cnDBtier from release 22.1.0 to 1.10.x.
• DBTier Backup Service: DBTier Backup Service which was a CRON job in the previous release is made as a deployment in the current release. For more information about DBTier Backup Manager, see Oracle Communications Cloud Native Core DBTier User Guide.
• DBTier Backup Transfer during Disaster Recovery: DBTier supports transfer of backup files from working DBTier cluster to failed DBTier cluster during automated Disaster Recovery procedures. This is performed using port 2022 in the SFTP protocol. For more information about Disaster Recovery procedures, see Oracle Communications Cloud Native Core DBTier Disaster Recovery Guide.
• Enhanced DBTier Replication Service: Additional Persistent Volume Claim (PVC) is added for cnDBTier replication service pods to store the backups transferred from one DBTier cluster to another DBTier cluster. For more information about DBTier replication service, see Oracle Communications Cloud Native Core DBTier User Guide.

2.5 Cloud Native Environment (CNE)

CNE Release 22.1.3

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

CNE Release 22.1.2

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

CNE Release 22.1.1

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

CNE Release 22.1.0

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

• Support for vCNE Upgrade on VMware: Oracle Communications Cloud Native Environment (OCCNE) supports upgrade of vCNE from release 1.10.0 to 22.1.0 on VMware to integrate vCNE on VMware with the OCCNE procedures. For more information about the upgrade procedure, see Oracle Communications Cloud Native Environment Installation and Upgrade Guide.
  All the functionality that is provided in Baremetal CNE and OpenStack CNE, is also available in VMware CNE. When OCCNE installed on VMware, OCCNE includes highly available VM-based load balancers, similar to those used when OCCNE is installed on OpenStack.
• Support for Common Services: The following common services were upgraded in this release:
  • Helm - 3.6.3
  • Kubernetes - 1.21.6
  • containerd - 1.4.4
  • Calico - 3.19.2
  • MetalLB - 0.10.2
  • Prometheus - 2.28.1
  • Grafana - 7.5.11
  • Jaeger - 1.22.0
  • Istio - 1.11.2
  • cert-manager - 1.2.0
• Alert Resolutions: The resolution steps for the OCCNE alerts are provided in Oracle Communications Cloud Native Environment User Guide.

  Note:

  In some cases where the steps needed to resolve an alert are extremely complex, and for alerts where the resolution can vary depending on what caused the alert, the user is instructed to contact Oracle customer support.

2.6 Cloud Native Core Policy (CNC Policy)

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

Release 22.1.4

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

Release 22.1.2

Support for Revalidating the Subscriptions on PDS on every N+ sessions: With this feature, PDS refetches the data and revalidates the subscription when the number of DNN sessions exceeds the configured limit.

For more information about this feature, see Oracle Communications Cloud Native Core Policy User Guide.

Release 22.1.1

Support for PodDisruptionBudget Kubernetes Resource: PodDisruptionBudget (PDB) is a Kubernetes resource that allows redistribution of CNC Policy pods to other worker nodes without impacting the CNC Policy microservices. With Pod Disruption Budget (PDB) assigned for each CNC Policy microservice type, Kubernetes maintains a minimum level of availability for replica set and service.

When the pods are evicted and deployed, each PDB is honoured. It helps to achieve the high availability of scalable application services in voluntary disruptions performed by cluster administrators to manage the cluster nodes.

For more information about this feature, see Oracle Communications Cloud Native Core Policy Installation and Upgrade Guide.

Release 22.1.0

• SBI Timer Handling: CNC Policy supports the SBI Timer for calculating the request timeout at both global and route levels. For more information on how to configure this feature using CNC Console, see the "SBI Timer Handling" section in Oracle Communications Cloud Native Core Policy User Guide.
• 3GPP-User-Location-Info in Rx RAR: CNC Policy uses the 3GPP-User-Location-Info in Rx RAR, when the UserLocation attribute is received on the SMF-N7 interface. For more information on how to configure this feature using CNC Console, see the "3GPP-User-Location-Info in Rx RAR" section in Oracle Communications Cloud Native Core Policy User Guide.
• Overload Control - Diameter Interface: CNC Policy 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, CNC Policy avoids entering to overload condition, detects overload conditions, and then take necessary actions to recover from overload situation. For more information on this feature and its configurations, see the "Overload Control - Diameter Interface" section in Oracle Communications Cloud Native Core Policy User Guide.
• Support for Model D: CNC Policy supports the Model D for indirect communication where producer discovery and selection is delegated to SCP. In Model D, PCF can act both as a consumer and producer. For more information on this feature, see the "NF Communication Profiles" section in Oracle Communications Cloud Native Core Policy User Guide.
• Randomization of Revalidation Time via Policy Blockly: CNC Policy supports setting the session revalidation time to a specific year, month, day, or time using the Policy blockly. In addition, it allows users to select a random revalidation time from the defined range. For more information on this feature, see the "PCF SM Category" section in Oracle Communications Cloud Native Core Policy Design Guide.
• Exiting Policy Evaluation via Policy Blockly: CNC Policy supports exiting the policy evaluation at any point in time using the End All blockly. For more information on this feature, see the Public Category section in Oracle Communications Cloud Native Core Policy Design Guide.
• Enhancement in PCRF-Core Metrics: CNC Policy supports the enhanced PCRF-Core metrics. The enhancement supports metrics with multiple dynamic dimensions. For more information on this feature, see the New PCRF Core Metrics section in Oracle Communications Cloud Native Core Policy User Guide.
• Session Retry with Binding Headers, NFSets, and Server Headers: CNC Policy supports enhanced session retry and alternate routing mechanisms that consider binding headers, NFSets, and server headers for choosing the next best alternate producer or/and SCP in indirect communication model. This feature also determines the action for CNC Policy when no retry is required and all attempts are exhausted by SCP. or more information on this feature, see the "NF Communication Profiles" section in Oracle Communications Cloud Native Core Policy User Guide.
• SRV Lookup of SCP FQDN for XFCC Header Validation: CNC Policy supports the enhanced functionality where PCF as a producer can perform DNS SRV queries on the single virtual configured FQDN for SCP, and find the host SCPs that are authorized to send HTTP Request to PCF. For more information on this feature, see the "XFCC Header Validation" section in Oracle Communications Cloud Native Core Policy User Guide.
• Sy Support on CNC Policy (PCF): CNC Policy supports fetching the subscriber counters for a subscriber from OCS over Sy reference point. When this feature is enabled, OCS notifies CNC Policy(PCF) for any change of counters status by sending an Diameter SNR. For more information on this feature, see the "Session Management configurations" section in Oracle Communications Cloud Native Core Policy User Guide.
• Support for Server Header: CNC Policy supports server header in the error responses received from Ingress Gateway and sent towards Egress Gateway respectively. Using the server header, the user can find out if the error is generated either at the backend microservices or at the Ingress Gateway itself. For more information on this feature, see the "Support for Server Header" section in Oracle Communications Cloud Native Core Policy User Guide.

2.7 Network Exposure Function (NEF)

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

Release 22.1.2

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

Release 22.1.1

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

Release 22.1.0

• Support for 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.
• Location Reporting: OCNEF provides the Location Reporting functionality to monitor and report the subscriber or User Equipment (UEs) location in 5G network. Any change in the subscriber location is considered as an event and OCNEF facilitates third-party applications or internal Application Functions (AFs) to get report about such events for the set duration. For more information about the feature, see Oracle Communications Cloud Native Core Network Exposure Function User Guide.
• Security Token Generation for API Invocation: 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.
• Integration with ATS: OCNEF is integrated with Oracle Communications Automated Testing Suite (ATS) to provide an end-to-end solution for deploying and testing OCNEF features. For more information about OCNEF ATS, see Oracle Communications Cloud Native Core Automated Test Suite Guide.

2.8 Network Repository Function (NRF)

Network Repository Function (NRF) 22.1.x has been updated with the following enhancement:

Release 22.1.4

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

Release 22.1.3

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

Release 22.1.2

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

Release 22.1.1

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

• Support for EmptyList in Discovery Response: When the feature is ENABLED and all the matching profiles for a discovery request are in "SUSPENDED" state, OCNRF modifies the profile state to "REGISTERED". The modified NFStatus is sent in the discovery response along with 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, 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 Kubernetes Resource: 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.

Release 22.1.0

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

• Support for SLF queries via SCP: OCNRF supports multiple SCP deployments for routing SLF queries. When OCNRF receives a discovery request which requires SLF lookup, it sends the SLF query via SCP based on the API root header configuration. The SCP peer configuration is performed in Egress Gateway for routing. For more information about the feature, see Oracle Communications Cloud Native Core Network Repository Function User Guide.
• SLF Selection from registered NFProfiles: OCNRF supports dynamic selection of SLF based on the registered UDRs having Nudr_GroupIDmap service. The SLF lookup is performed by sending the SLF Query to the UDR profiles registered with the OCNRF. For more information about the feature, see Oracle Communications Cloud Native Core Network Repository Function User Guide.
• Support for Preferred-Tai in Discovery: OCNRF supports filtering of NFProfiles based on preferred Tracking Area Identity (TAI). When OCNRF receives a discovery request with preferred-tai attribute, it processes the request based on the NFProfiles that can serve the TAI. For more information about the feature, see Oracle Communications Cloud Native Core Network Repository Function User Guide.
• Enhanced Log Format for Registration and Discovery Service: JSON format of Registration and Discovery Service Logs are updated for message attribute. Additionally, key log attributes are added for enhancing filtering capabilities for better troubleshooting experience. For more information about the OCNRF logs, see Oracle Communications Cloud Native Core Network Repository Function Troubleshooting Guide.

2.9 Network Slice Selection Function (NSSF)

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

Release 22.1.2

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

Release 22.1.1

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

Release 22.1.0

• Enhanced NSSF Database:

  a. NSSF Provisional Database: The Provisional Database contains configuration information. The configuration must be done on each site by the operator.

  b. NSSF State Database: State database maintains a running state and has information on subscriptions, pending notification, triggers, and availability data. This database is replicated and the same content is observed by NSSF georedundant sites.

  For more information, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation and Upgrade Guide.

• Support for NsAuditor Microservice: NSSF now supports NsAuditor microservice. It is a timed auditor that removes stale records from NSSF. In georedundant scenarios, tables in State Database (stateDB) maintain a column, siteId, which signifies the owner site of that record. There could be scenarios when similar records (for example, same subscription) might be owned by two sites. In such a case, the older record is a stale record. For more information, see Oracle Communications Cloud Native Core Network Slice Selection Function Installation and Upgrade Guide.
• Readiness support for in-service upgrade: OCNSSF 22.1.0 has readiness support for the in-service upgrade. This means further releases over and above 22.1.0 shall support in-service upgrade.

2.10 Service Communication Proxy (SCP)

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

Release 22.1.4

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

Release 22.1.3

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

Release 22.1.2

Enhanced Network Function (NF) Status Processing: This feature enables SCP to retain and create the routing rules of an NFProfile whose NFStatus is SUSPENDED. For more information about this feature, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.

Release 22.1.1

Support for PodDisruptionBudget Kubernetes Resource: PodDisruptionBudget (PDB) is a Kubernetes resource. It helps to achieve the high availability of scalable application services in voluntary disruptions performed by cluster administrators to manage the cluster nodes. For more information about this feature, see Oracle Communications Cloud Native Core Service Communication Proxy Installation and Upgrade Guide.

Release 22.1.0

• Support for 3GPP SBI Message Priority for Egress Congestion Control based on Producer Load: This feature enables consideration of message priority for egress congestion control based on the producer reported load. SCP considers the value of the 3gpp-Sbi-Message-Priority header and provided configurations to determine an action when the producer reported load goes beyond the configured threshold. For more information about this feature, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
• Support for HTTPS: With the support of HTTPS connections, SCP can accept secured ingress connection requests from a consumer NF and establish secured egress connections with a producer NF. HTTPS provides confidentiality and integrity protection to 5G Service Based Interface (SBI) messages. For more information about this feature, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
• Support for Model D Indirect 5G SBI Communication with Delegated Discovery: This feature enables consumer NFs to delegate the producer NF discovery procedure to SCP by adding discovery parameters to the service request. SCP performs NF discovery with NRF using the received discovery parameters. For more information about this feature, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
• Support for 5G SBI Roaming: This feature enables SCP to integrate with Security Edge Protection Proxy (SEPP) to route 5G Service Based Interface (SBI) roaming subscriber traffic outside the network to the required Public Land Mobile Network (PLMN). For more information about this feature, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.
• Routing Options Enhancements for Next Hop SCP and Notification or Callback Messages:

  This feature enhances the existing 5G SBI message routing configurations for inter-SCP routing scenarios. These configuration parameters that include timer values are applied when the consumer SCP routes a message request to the producer NF instance in another region through producer SCPs.

  This feature also supports a set of routing options such as timers, error codes, and so on, for notification or callback messages in addition to service types. For more information about this feature, see Oracle Communications Cloud Native Core Service Communication Proxy User Guide.

• SCP Performance and Capacity Improvements: SCP can support 231K Transaction Per Second (TPS) with scp-worker having large profile.

2.11 Security Edge Protection Proxy (SEPP)

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

Release 22.1.2

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

Release 22.1.1

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

Release 22.1.0

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

• Multiple PLMN Support For Local and Remote SEPP: This feature supports configuring multiple PLMN IDs for local and remote SEPP(s). With this feature, you can send and receive requests to and from multiple remote SEPPs at the same time. 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.
• Topology Hiding: Topology hiding, a 5G security feature, secures the address of the network elements by preventing attacks from unauthorized access or interruption of the network service. Topology Hiding conceals identity information from all messages leaving a PLMN. 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.
• Supports SEPP SCP Integration : 3GPP and operators prefer to use an Edge proxy for routing traffic outside the network. For example, Roaming traffic signaling, Contacting other networks for information about the subscribers. SEPP enables this functionality and SCP is predominantly routing traffic within the network. This feature enables SEPP to integrate with Service Communication Proxy (SCP) to route 5G Service Based Interface (SBI) roaming subscriber traffic within the network to the required Public Land Mobile Network (PLMN).
• Support 16k MPS on a Single Site: SEPP configuration is enhanced to support 16k MPS per site.

2.12 Unified Data Repository (UDR)

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

Release 22.1.2

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

Release 22.1.1

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

Release 22.1.0

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

• Support for User-Agent header: User-Agent header helps the producer Network Function (NF) to identify the consumer NF that has sent the request. With this feature, UDR supports validating User-Agent header in the ingress requests. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
• SubscriberDB: Support for NEF API: With this feature, UDR supports NEF data, data access, and provisioning APIs as defined in 3gpp 29.519. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
• SLF compliance with K8s1.20 & ASM 1.9.x: UDR is now compatible with Kubernetes 1.20.7 and ASM 1.9.8.
• SLF - Support Default Group-ID: With this feature, SLF supports default group ID for subscribers.When a subscriber is not provisioned in the Subscriber Location Function (SLF), the SLF responds with an error stating "Subscriber does not exist". This feature provides an option of not responding with an error but instead provides a default group or default NF for the subscribers that are not provisioned in the SLF. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
• Reduce DIAMETER gateway footprint to support benchmarked TPS on the cnUDR : UDR supports 25K Diameter Sh TPS.
• Diameter Pod Congestion control: UDR supports Diameter Pod Congestion to throttle and safeguard from overload conditions. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.
• Segregation of Provisioning and signalling traffic from Nudr-dr microservice : Nudr-dr now handles only signalling traffic and a new microservice Nudr-drprov service handles provisioning traffic. For more information, see Oracle Communications Cloud Native Core Unified Data Repository User Guide.