2 Deployment Model

The Oracle Cloud Infrastructure (OCI) deployment infrastructure provides a flexible management system that allows you to create objects required during the instance deployment procedure prior to or during that deployment.

CNC NF on OKE

In the initial phase, the integration architecture requirements target deploying CNC Applications in two regions, with each region having one Availability Domain (AD) and a Fast Connect to the cloud operator's on-premise deployment.

Availability Domains and regions physically host the OCI. A region is a localized geographic area, and an AD is one or more data centers located within a region. Oracle cloud regions are globally distributed data centers that provide secure and high-performance local environments.

• ADs are isolated from each other, fault-tolerant, and unlikely to fail simultaneously or be impacted by the failure of another AD. If the OCI Region supports multiple ADs per OCI Region, configure the cloud services using multiple ADs to ensure HA (recommended).
• A Fault Domain (FD) is created by grouping the hardware and infrastructure within an AD. Each AD contains three FDs. FDs provide anti-affinity by allowing instance distribution so that the instances are not on the same physical hardware within a single AD.

The following diagram is a high-level architectural deployment showcasing the deployment of Oracle CNC Applications in one AD and two regions with OCI Fast Connect towards the operator's data centre. Each Oracle AD comprises three FDs. However, the diagram does not depict the same for brevity.

You can deploy 3GPP-based Oracle CNC Applications in OKE clusters running on OCI in public cloud regions. OCI Region comprises multiple Availability Domains, including numerous FDs within ADs. Some of the allowed deployment models for CNF NFs include the following:

• One Region with One AD or One Region with multiple ADs
• Multiple regions with One AD and multiple regions with multiple ADs

Cloud operators may choose an appropriate deployment based on the cost, redundancy requirements and so on.

Figure 2-1 Deployment of Oracle CNC NFs in One AD and Two Regions

Two Regions Each with One Availability Domain

The following diagram depicts the deployment of a CNC Applications across two OCI regions with one OCI Availability Domain (AD) used in each region. The customer owns the OCI tenancy.

Each AD hosts the CNC NF in a separate OKE Cluster. CNC NF is deployed based on an active-active redundancy model in both regions.

CNC Applications residing in the OCI regions are provisioned by the operator using a Bastion Service which is reachable over the public internet.

Cross Data Centre Replication (XDCR) is enabled on the cnDBTier, thus enabling one region's failure to be seamlessly handled by the resources of the other OCI region.

The 5G NFs on the Operator's on-premises reach the CNC Applications in the OCI Regions over Fast Connect.

Figure 2-2 CNC NF deployment on OCI Public Cloud with one AD and two Regions

Account and Tenancy

The customer owns OCI tenancy and a portfolio of CNC 5G applications deployed on the OCI public cloud. CNC supports a two-site NF deployment in the initial phase, where a 'site' corresponds to an AD. Each OCI Region has one to three ADs.

A two-site NF deployment includes two OCI regions with one AD in each region or one OCI region with two ADs in the same region.

CNC NF Deployment Layout

This section describes the deployment of 3GPP CNC Applications as an NFset in the customer's OCI tenancy spanning two OCI regions.

The below diagram below depicts a hierarchical 3GPP NF set deployment layout in OCI regions grouped by compartments:

• Each OCI region comprises a root compartment and a "5G Core Network Compartment".
• Within the "5G Core Network Compartment", each CNC NF is placed in a separate "NFType Compartment".
• The NFType compartments are logically grouped across OCI regions, thus helping count the resources of NF or NF-set.
• Access policies such as read, use, and inspect are configured at the parent "5G Core Network Compartment" level.
• Users can avail access policies such as read, use, inspect, and manage at the "NFType Compartment" level.
• Separating each NF into a separate compartment enables the operator to use the Tenancy Explorer and obtain a count of the total resources used by each NF Type across this tenancy.
• By default, each NF OKE cluster is hosted in one single namespace (although the operator can host Console, CNC NF, cnDBTier, and OCI Adaptor in separate namespaces). Replication is enabled between the cnDBTier of each NF within an NFType compartment.

The diagram below displays a sample deployment layout of a 3GPP NF set across OCI regions grouped by compartments:

Figure 2-3 NF Deployment Layout Hierarchy

Note:

Georedundancy setup is optional. CNC NF deployment on OCI supports both Georedundant and Non-Georedundant deployments.