Feature Descriptions

2.1 Continuous Delivery Control Server (CDCS)

Release 23.3.1

The following enhancements are made in release 23.3.1.

Support for updating Oracle Linux: CDCS allows to update the base Oracle Linux version for CDCS VMs and the host OS (when CDCS is installed on a BareMetal server) with the latest version. For more information about the Oracle Linux version, see the Oracle Communications CD Control Server Installation and Upgrade Guide.
Support for CNE releases: CDCS supports the installation and upgrade of CNE releases 22.4.x, 23.1.x, 23.2.x, and 23.3.x. A specific release can be installed by selecting the supported release versions while running the Install OCCNE and Upgrade OCCNE commands. For more information about selecting the versions, see the "Managing CNE" section in Oracle Communications CD Control Server User Guide.

Release 23.3.0

Oracle Communications CD Control Server (CDCS) 23.3.0 has been updated with the following enhancements:

Support for adding or removing worker nodes at managed sites: CDCS allows to add or remove worker nodes to CNE at a managed site. This feature is applicable to both production and staging sites, that run on Bare Metal infrastructure only.
For more information about adding or removing the worker nodes at managed sites, see the "Site Maintenance" section in Oracle Communications CD Control Server User Guide.
Support for Command Chaining: This feature enables the user to run multiple commands in a sequence. This feature helps to configure a list of commands to run in a specific order. Enter all the parameter values for the commands in the chain. The commands run sequentially. By default, when the first command completes successfully, the second command runs, and so on. If any command fails, the other commands configured in the chain don't run. (However, the user can select to skip the failed command and proceed with the next command.) A command chain can run immediately or at a specific time.
For more information about support for command chaining, see the "Command Chaining" section in Oracle Communications CD Control Server User Guide.
Support for Timeout parameter: With this enhancement, the user can configure the timeout parameter for certain commands, which takes more than the default time set by CDCS. The TIMEOUT value for any specific lifecycle operation is based on the NF documentation. Otherwise, use the default value of 5 minutes. The following commands have the timeout parameter:
- Uninstall NF
- NF Health Check
- Rollback NF Upgrade
- Install ATS Tests for NF
For more information about configuring the TIMEOUT parameter, see the "Managing NF Lifecycle " and "Managing NF Test (staging sites only)" sections in Oracle Communications CD Control Server User Guide.
Support for new commands: CDCS supports the following new commands:
- Delete OCCNE Release
- Delete ATS Tests for NF Release
- Uninstall ATS Tests for NF
- Remove Mate CDCS
For more information about the new commands, see the sections "Deleting CNE Release", "Deleting ATS Tests for NF Release", "Uninstalling ATS Tests for NF", and "Detaching an Active and Standby CDCS pair" in Oracle Communications CD Control Server User Guide.

CDCS UI enhancements: The enhancements in CDCS UI organize the commands in a folder based on operations to ease the use for operators. The main UI screen appears as follows:

Table 2-1 CDCS UI enhancements

Folder	Description
CDCS Configuration	Provides a list of commands used for configuring CDCS.
CDCS Lifecycle	Provides a list of CDCS lifecycle commands.
Production Sites	Provides a list of commands that operate on production sites.
Staging Sites	Provides a list of commands that operate on staging sites.
Site Maintenance	Provides a list of commands that perform maintenance operations at production and staging sites.
NF Lifecycle	Provides a list of NF lifecycle commands.
NF Test	Provides a list of NF ATS test lifecycle commands.
CDCS Internal	Contains the commands that operate on command chains.
Command Chaining	Contains the CDCS internal commands.

For more detailed information about the features released in 23.3.0, see Oracle Communications CD Control Server User Guide.

For more detailed information about the features released in CDCS 23.3.x, see Oracle Communications CD Control Server User Guide.

2.2 Cloud Native Configuration Console (CNC Console)

Release 23.3.2

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

Release 23.3.1

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

Release 23.3.0

Oracle Communications Cloud Native Configuration Console (CNC Console) 23.3.0 has been updated with the following enhancements:

Support for dual stack IPv4 deployment: Applications or NFs can establish connections with pods and services in a Kubernetes cluster using IPv4 or IPV6 by using the dual stack mechanism. CNC console uses IPv4 by default but can be configured to use either IPv4 or IPv6.
Support for IPv6 on IPv6 only infrastructure: CNC Console can be configured to work on an IPv6 only infrastructure.
NF Versions Supported by CNC Console: The following NF versions are supported in this release:
- SCP - 23.3.x
- NRF - 23.3.x
- UDR - 23.3.x
- POLICY - 23.2.x
- BSF - 23.2.x
- SEPP - 23.3.x
- NSSF - 23.3.x
- OCNADD - 23.3.x
- OCNWDAF - 23.3.x
- PROVGW - 23.3.x

2.3 Cloud Native Environment (CNE)

Note:

The procedure to update OpenStack credentials is revised in the 23.3.5 User Guide. If you are updating OpenStack credentials on other versions of 23.3.x, refer to the latest procedure from 23.3.5 Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.

Release 23.3.5

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

Release 23.3.4

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

Release 23.3.3

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 23.3.3 has been updated with the following enhancements:

Note:

The following feature was introduced in 23.3.2 which is an installation-only patch. Therefore, if you are upgrading to 23.3.3 release, be informed about the following feature that is already in place.

Fluent Bit replaced with Fluentd OpenSearch: With release 23.3.2, Fluent Bit is replaced with Fluentd OpenSearch. That is, log forwarding mechanism is changed from fluent-bit to fluentd-openSearch. The other changes in the OpenSearch stack are as follows:
- There are five OpenSearch data nodes created by default.
- CNE Environment upgrading from 23.3.1 requires OpenSearch Dashboard filters to be updated in saved queries.
OpenSearch and Fluentd Performance Considerations: OpenSearch and Fluentd are used for log ingestion. The performance of these services depends on the rate at which log forwarding happens, rate of ingestion, and log retention periods. It is advised to collect the aforementioned metrics from different components that are running in CNE cluster and ingesting logs to OpenSearch. The resources requirements of OpenSearch differs according to these metric collection.

Release 23.3.2

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 23.3.2 has been updated with the following enhancements:

Fluent Bit replaced with Fluentd OpenSearch: With this release, Fluent Bit is replaced with Fluentd OpenSearch. That is, log forwarding mechanism is changed from fluent-bit to fluentd-openSearch. Additionally, the system creates five OpenSearch data nodes by default.
OpenSearch and Fluentd Performance Considerations: OpenSearch and Fluentd are used for log ingestion. The performance of these services depends on the rate at which log forwarding happens, rate of ingestion, and log retention periods. It is advised to collect the aforementioned metrics from different components that are running in CNE cluster and ingesting logs to OpenSearch. The resources requirements of OpenSearch differs according to these metric collection.
New Versions of Common Services: Fluentd OpenSearch is upgraded to 1.16 in this release.
To get the complete list of third party services and their versions, refer to the dependencies_23.3.2.tgz file provided as part of the software delivery package.

Release 23.3.1

Oracle Communications Cloud Native Core, Cloud Native Environment (CNE) 23.3.1 has been updated with the following enhancements:

Secure Container Registry: CNE uses HTTPS to secure the container registry that runs on Bastion Host. With this implementation, Bastion Host container registry is enabled with TLS and all requests require https connectivity to communicate to the container registry.
Grafana Dashboards: In this release, CNE provisions Grafana dashboards to observe the functioning of CNE components. These dashboards provide metrics about Kubernetes clusters, Opensearch, PVCs, and Prometheus. The dashboards highlight spikes, functional drifts, and performance drifts in the cluster. As Grafana dashboards persist as config maps, users don't have to back up these dashboards during upgrades. For information about this feature, see Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.
New Versions of Common Services: The following common services are upgraded in this release:
- Helm - 3.12.0
- Kubernetes - 1.26.5
- containerd - 1.7.1
- Calico - 3.26.1
- MetalLB - 0.13.7
- Prometheus - 2.44.0
- Grafana - 9.5.3
- Jaeger - 1.45.0
- Istio - 1.18.2
- Kyverno - 1.9
- cert-manager - 1.11.0
- Oracle OpenSearch - 2.3.0
- Oracle OpenSearch Dashboard - 2.3.0
- Velero - 1.10
You can find the complete list of third party services and their versions in the dependencies_23.3.1.tgz file provided as part of the software delivery package.
Installation and Upgrade Consideration: In this release, the Bastions mirror UEKR7 along with UEKR6 YUM packages. Therefore, before installing 23.3.x or upgrading to 23.3.x, you must add mirroring of both OL8 UEKR6 and OL8 UEKR7 YUM channels from yum.oracle.com to the central-repository. For more information about configuring YUM repository, see Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide.

Operations Services Overlay (OSO)

Oracle Communications Operations Services Overlay (OSO) 23.3.1 has been updated with the following enhancements:

Support for Dualstack: Using the Dualstack mechanism, applications or NFs can establish connections with pods and services in a Kubernetes cluster using IPv4 or IPv6 or both simultaneously. Dualstack provides:
- coexistence strategy that allows hosts to reach IPv4 and IPv6 simultaneously.
- IPv4 and IPv6 allocation to the Kubernetes clusters during cluster creation. This allocation is applicable for all the Kubernetes resources unless explicitly specified during the cluster creation.
For more information about enabling Dualstack, see "Installation using CSAR" and "Using OSO with IPv6" sections in Oracle Communications Operations Services Overlay Installation and Upgrade Guide.
Support for new version of Prometheus: Prometheus is uplifted from 2.39.1 to 2.44.0.

2.4 Cloud Native Core cnDBTier

Release 23.3.3

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

Release 23.3.2

Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) 23.3.2 has been updated with the following features or feature enhancements:

dbtrecover Support for Georeplication Recovery Between Different cnDBTier Versions: With this feature, the dbtrecover script supports georeplication recovery between sites that are running on different cnDBTier versions. For more information about this feature, see the "Recovering Georeplication Sites Using dbtrecover" section in .
Considerations: Consider the following conditions before using the dbtrecover script for performing a georeplication recovery between sites running on different cnDBTier versions:
- The script supports georeplication recovery between sites only in the following cases:
  - The good site and the bad site (the site to be recovered) run the same cnDBTier version.
  - The good site runs a lower cnDBTier version. However, the cnDBTier release on both the good site and the bad site supports the same database replication REST API.
- The script doesn't support georeplication recovery between sites in the following cases:
  - The good site runs a cnDBTier version that is higher than the version on the bad site.
  - The good site runs a lower cnDBTier version and uses a different database replication REST API from the one used by the bad site.
- The following cnDBTier versions use the old database replication API:
  - cnDBTier versions below 22.4.2
  - cnDBTier version 23.1.0
- The following cnDBTier versions use the new database replication API:
  - cnDBTier versions greater than or equal to 22.4.2 and less than 23.1.0
  - cnDBTier version greater than or equal 23.1.1
Support for New Version of Spring Boot: Spring Boot is upgraded to 3.1.6 in this release.
TLS Support for Georeplication: TLS feature is not supported in this release.

Release 23.3.1

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

Release 23.3.0

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

REST APIs to display cnDBTier data on CNC Console: With this feature, cnDBTier exposes the following REST APIs to CNC Console:
- Site specific real time replication status
- Real-time overall replication status
- Real-time local cluster status
- cnDBTier version
These REST APIs will be used by CNC Console in the future releases to fetch cnDBTier data and display them on the CNC Console GUI. This way, cnDBTier facilitates users to integrate cnDBTier on CNC Console and allows users to perform cnDBTier read operations such as checking the status of cnDBTier clusters and georeplication on CNC Console. For more information about the feature and the REST APIs, see Oracle Communications Cloud Native Core, cnDBTier User Guide.
Secure transfer of backups to remote servers: With this release, cnDBTier provides the functionality to securely transfer the backups stored in the data nodes to remote sites using Secure File Transfer Protocol (SFTP). This ensures that the database backups are not lost due to purging in cnDBTier as the backups are retained in a remote storage. For more information about enabling and configuring this feature, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.
Support for new versions of software: The following software are upgraded in this release:
- Oracle MySQL Cluster Database - 8.0.34
- Spring Boot - 3.1.2

2.5 Network Exposure Function (NEF)

Release 23.3.2

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

Release 23.3.1

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

Release 23.3.0

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

Support for Device Trigger: This feature enables AFs to send device trigger requests to UEs to perform application-specific tasks such as initiating communication with AF. For more information, see Oracle Communications Cloud Native Core, Network Exposure Function User Guide and Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide.
Support for Converged SCEF-NEF for QoS: This feature enables converged SCEF-NEF model to set up an AF Session with the required QoS in the 4G system as a fallback solution in case AF session with QoS subscription fails in the 5G system. For more information, see Oracle Communications Cloud Native Core, Network Exposure Function User Guide and Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide.

2.6 Network Repository Function (NRF)

Release 23.3.2

Supports Service Level Priority with the same Service Names: The Preferred Locality priority handling has been enhanced to support service level priority with same service names. For service-name based discovery query, NRF updates the profile level priority and service level priority of the NF profile if there are multiple services in the NF profile with the same service name after processing the discovery query. For more information about the feature, see "Preferred Locality" in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

Release 23.3.1

Ingress Gateway Pod Protection: This feature is enhanced to support an additional congestion state parameter, Pending Message Count, for measuring the states. For more information about the feature, see "Ingress Gateway Pod Protection" in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

Release 23.3.0

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

Ingress Gateway Pod Protection: This feature protects the Ingress Gateway pods from getting overloaded due to uneven traffic distribution, traffic bursts, and congestion. It ensures the protection and mitigation of pods from entering an overload condition, while also facilitating necessary actions for recovery. For more information about the feature, see the "Ingress Gateway Pod Protection" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.
Pre and Post Install/Upgrade Infrastructure Validation: NRF validation checks are enhanced to support infrastructure validations for preinstallation and preupgrade to verify the NRF version, Kubernetes version, cnDBTier version, replication status, and alerts. For more information about the feature, see the "Pre and Post Install/Upgrade Validations" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.
Dynamic SLF Selection based on Extended Preferred Locality Feature Configuration: When Extended Preferred Locality feature is enabled, the sorting and prioritizing of the SLF or UDR profiles for SLF selection is performed based on the feature configuration. For more information about the feature, see the "Subscriber Location Function" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.
Dynamic SLF Selection based on Empty List Feature Configuration: When Empty List is enabled, the sorting and prioritizing of the SLF or UDR profiles for SLF selection is performed based on the feature configuration. For more information about the feature, see the "Subscriber Location Function" section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.
NRF Deployment using CDCS: In addition to NRF's Command Line Interface (CLI) deployment method, NRF can be deployed using Continuous Delivery Control Server (CDCS), which is a centralized server that automates NRF deployment processes such as downloading the NRF package, installation, upgrade, and rollback. For more information about CDCS, see Oracle Communications CD Control Server User Guide. For information about NRF deployment using CDCS, see Oracle Communications Cloud Native Core, Network Repository Function Installation, Upgrade, and Fault Recovery Guide.
Limiting the number of producers based on NF Set Ids: This feature allows NRF to limit the number of matching NF profiles from the first matching location(s) and other matching locations using the NF Set Ids. For more information about the feature, see "Preferred Locality Feature Set" in Oracle Communications Cloud Native Core, Network Repository Function User Guide.

2.7 Network Slice Selection Function (NSSF)

Release 23.3.1

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

Release 23.3.0

Oracle Communications Cloud Native Core, Network Slice Selection Function (NSSF) 23.3.0 has been updated with the following enhancements:

Support for User-Agent Header: This feature enables the usage of the User-Agent Header in every HTTP/2 request that NSSF sends over any Service-Based Interface (SBI) to a producer NF such as AMF or NRF. For more information, see "Support for User-Agent Header in NSSF" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.
Ingress Gateway Pod Protection: This feature protects the Ingress Gateway pods from getting overloaded due to uneven traffic distribution, traffic bursts, or congestion. It ensures the protection and mitigation of pods from entering an overload condition, while also facilitating necessary actions for recovery. For more information, see "Ingress Gateway Pod Protection for NSSF" section in Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide.

2.8 Service Communication Proxy (SCP)

Release 23.3.2

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

Release 23.3.1

Oracle Communications Cloud Native Core, Service Communication Proxy (SCP) 23.3.1 has been updated with the following enhancements:

Support for 620K MPS with Model C: Model C is tested with traffic at a rate of 620K MPS. For more information about this testcase scenario, see Oracle Communications Cloud Native Core, Service Communication Proxy Benchmarking Guide.

Release 23.3.0

Oracle Communications Cloud Native Core, Service Communication Proxy (SCP) 23.3.0 has been updated with the following enhancements:

Routing options enhancement to control SCP routing features: SCP allows the user to control the applicability of routing features by providing options to enable or disable rerouting at the NF service level. For more information, see "Routing Options Enhancement to Control SCP Routing Features" in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
TLS certificate configuration enhancement: This enhancement enables SCP to configure different Transport Layer Security (TLS) certificates on ingress and egress interfaces. It also allows the user to provide primary and secondary certificates for each interface. For more information, see "TLS Certificate Configuration Enhancement" in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
Support for OCCNE egress NAT: SCP supports egress NAT in Oracle Communications Cloud Native Core, Cloud Native Environment (CNE). For more information, see "Configuring Egress NAT for an NF" in Oracle Communications Cloud Native Core, Cloud Native Environment User Guide.

2.9 Security Edge Protection Proxy (SEPP)

Release 23.3.2

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

Release 23.3.1

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

Release 23.3.0

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

Alternate Routing based on the DNS SRV Record for Home Network Functions: This feature performs alternate routing of messages by querying SRV records with the DNS server to find an alternate producer NF and route the service request. SEPP supports retrieval of NRF, SCP, and Producer NFs' records using DNS SRV queries at plmn-egress-gateway. SEPP uses either NF Set or DNS SRV records to perform alternate routing. For more information about the feature, see the "Alternate Routing based on the DNS SRV Record for Home Network Functions" 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, Upgrade, and Fault Recovery Guide.
Rate Limiting for Egress Roaming Signaling per PLMN: This feature configures the egress request rate on N32F interface based on the destination PLMN IDs. This controls the messages sent out from the local SEPP to a Remote SEPP. With this feature, the number of egress requests to one or more PLMN IDs is restricted based on a configured count using token bucket algorithm.
For more information about the feature, see the "Rate Limiting for Egress Roaming Signaling per PLMN" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide, "Egress Rate Limiting Option Configuration" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy REST API Specification Guide, and the "Configuration Parameters" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide.
Cat-0 SBI Message Schema Validation Feature Enhancement: Cat-0 SBI Message Schema Validation Feature Enhancement: The Cat-0 SBI message schema validation feature now supports the SBI header validation. This feature supports stateless security counter measures, which enhances roaming partners to handle the security. For example, only valid requests are allowed to be processed at SEPP at lower layer.
For more information about the feature, see the "Cat-0 SBI Message Schema Validation Feature" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

2.10 Unified Data Repository (UDR)

Release 23.3.2

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

Release 23.3.1

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

Error Response Enhancement for SLF Lookup Request: The error response is enhanced to support error causes scenario for SLF lookup requests. SLF supports the "cause" attribute in the problem details for all error responses as per 3GPP 29.504 specification. The "cause" attribute in the problem details object of the HTTP error response payload is used to indicate the application-related information for that specific error occurrence. This enables the HTTP client to take appropriate action. For more information about the feature, see "Error Response Enhancement for SLF Lookup Request" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.

Release 23.3.0

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

Converged Quota Support for UDR: Converged Quota Support for UDR updates the data model to support storage of 4G policy quota and dynamic quota under sm-data/umData and sm-data/umDataLimits respectively from VSA. On-demand migration and Diameter-sh are enhanced to support converged quota. For more information about the feature, see "Converged Quota Support for UDR" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
NF Scoring for a Site Integration with CNC Console: UDR supports the Network Function (NF) Scoring feature to calculate the site score based on NF specific factors such as alerts. The NF Scoring feature helps the operator to determine the health of a site. In this release, the NF Scoring feature can be configured using CNC Console. For more information about the feature, see "NF Scoring for a Site" and “NF Scoring Configurations” sections in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
Diameter Connection Configuration: The Diameter Connection Configuration triggers a Connection Establishment Request (CER) from the Diameter Gateway pod to each of the configured diameter endpoints. This feature enables the distribution of the diameter connection in a controlled manner by balancing the diameter traffic evenly between the Diameter Gateway pods. This is achieved by adding peer node details as a configuration in the Diameter Gateway. For more information about the feature, see "Diameter Connection Configuration" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.
Network Policies: Network Policies are an application-centric construct that allows you to specify how a pod is allowed to communicate with various network entities. Network Policies create pod-level rules to control communication between the cluster's pods and services. It determines which pods and services can access one another inside the cluster. For more information about the feature, see "Network Policies" section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide and “Configuring Network Policies” section in Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.
Conflict Resolution: In a multisite deployment, UDR updates subscriber data on all the sites during replication down time. When the replication is restored and if there are any conflicts in the subscriber data updates, they are automatically resolved in all the database tables by MySQL NDB Cluster in cnDBTier. However, in some cases, automatic resolution by MySQL causes subscriber data conflicts and anomalies in the database model. This feature provides an application-defined resolution to resolve the subscriber data conflicts by adding a timestamp column to determine whether an update is required on the replica. For more information about the feature, see "Conflict Resolution" and section in Oracle Communications Cloud Native Core, Unified Data Repository User Guide.