1 Introduction

This guide describes how to install or upgrade Oracle Communications Cloud Native Core, Unified Data Repository (UDR) in a cloud native environment.

Note:

  • This guide covers the installation instructions when Podman is the container platform with Helm as the Packaging Manager. For any other container platform, the operator must use the commands based on to their deployed container runtime environment.
  • kubectl commands can vary based on the platform deployment. Replace kubectl with Kubernetes environment-specific command line tool to configure Kubernetes resources through kube-api server. The instructions provided in this document are as per the CNE version of kube-api server.

Caution:

User, computer and applications, and character encoding settings may cause an issue when copy-pasting commands or any content from PDF. PDF reader version also affects the copy-pasting functionality. It is recommended to verify the pasted content especially when the hyphens or any special characters are part of the copied content.

1.1 Overview

UDR is a key component of the 5G Service Based Architecture (SBA). It is implemented as a cloud native function and offers a unified database for storing application, subscription, authentication, service authorization, policy data, session binding, and application state information.

Note:

The performance and capacity of the UDR system may vary based on the call model, feature or interface configuration, and underlying CNE and hardware environment, including but not limited to, the size of the json payload, operation type, and traffic model.
It provides:
  • an HTTP2 based RESTful interface and APIs to provision other Network Functions (NFs) data.
  • provisioning clients to access stored data.
As per the 3GPP specifications, UDR supports the following functionality:
  • Storage and retrieval of subscription data by UDM
  • Storage and retrieval of policy data by PCF
  • Storage and retrieval of structured data for exposure
  • Storage and retrieval of SLF information consumed by NRF
  • Application data (including Packet Flow Descriptions (PFDs) for application detection, AF request information for multiple UEs) by the NEF
  • Subscription and Notification feature
UDR:
  • leverages a common Oracle Communications Cloud Native Framework.
  • is compliant with 3GPP 29.505 Release 15 specification UDM data access.
  • is compliant with 3GPP 29.519 Rel 16(backward compatible with Rel 15) specification for PCF data access.
  • is compliant with 3GPP 29.519 Rel16 specification for NEF data access.
  • has tiered architecture providing separation between the connectivity, business logic and data layers.
  • uses MySQL NDB Cluster CGE edition as the backend database in the Data Tier.
  • registers with NRF in the 5G network, so the other NFs in the network can discover UDR through NRF.
  • registers UDR with services: DR-SERVICE and GROUP-ID-MAP.
Unstructured Data Storage Function (UDSF):
  • Supports storage and retrieval of unstructured data by any 5G NF. The specifications of UDSF is not defined by 3gpp.
  • This functionality is part of Oracle's 5G UDR solution.

Subscriber Location Function (SLF):

  • Supports Nudr-groupid-map service as defined by 3GPP
  • Registers with NRF for Nudr-groupid-map service
  • Is complaint with 3GPP Release 16 for APIs to be consumed by 5G NRF
  • Supports REST or JSON based provisioning APIs for SLF data
5G Equipment Identity Register (EIR) supports:
  • REST/JSON based provisioning of 5G EIR profile
  • Bulk import of 5G EIR subscriber data via PDBI interface
  • N5g-eir_EquipmentIdentityCheck Service API
  • 5G EIR as per 3GPP TS 29.511

1.2 References

Refer to the following documents while deploying UDR:

  • Oracle Communications Cloud Native Core, Unified Data Repository User Guide
  • Oracle Communications Cloud Native Core, Provisioning Gateway Guide
  • Oracle Communications Cloud Native Core, Cloud Native Environment Installation, Upgrade, and Fault Recovery Guide
  • Oracle Communications Cloud Native Core, Converged Policy Installation, Upgrade, and Fault Recovery Guide
  • Oracle Communications Cloud Native Core, Network Repository Function, Upgrade, and Fault Recovery Guide.
  • Oracle Communications Cloud Native Core, Network Function Data Collector User Guide
  • Oracle Communications Cloud Native Core, cnDBTier User Guide

1.3 Oracle Error Correction Policy

The table below outlines the key details for the current and past releases, their General Availability (GA) dates, the latest patch versions, and the end dates for the Error Correction Grace Period.

Table 1-1 Oracle Error Correction Policy

Release Number General Availability (GA) Date Latest Patch Version Error Correction Grace Period End Date
3.24.3 October 2024 24.3.0 October 2025
3.24.2 October 2024 24.2.1 July 2025
3.24.1 April 2024 24.1.0 April 2025
3.23.4 December 2023 23.4.1 December 2024

Note:

For a release, Sev1 and Critical Patch Update (CPU) patches are supported for 12 months. For more information, see Oracle Communications Cloud Native Core and Network Analytics Error Correction Policy.

1.4 Oracle Open Source Support Policies

Oracle Communications Cloud Native Core uses open source technology governed by the Oracle Open Source Support Policies. For more information, see Oracle Open Source Support Policies.