Topology for End-to-End Integration

Table of Contents

1 Scope
2 Network Planning
3 References:

Scope

This page describes an arbitrary topology which describes the relationships between the O-RAN network functions.

Such topology information is needed to define names and identifiers between the different network function and its NRCellDU objects across also software components.

Network Planning

Let’s create a small outdoor RAN with at least two overlapping cells for the e2e-integration use case.

Step #1: Select network center

As a first step we place into the center of the network a tower. Here a tower on the roof top of a building.

Step #2: Add six towers around

For our use case we would like to have two O-DUs on different towers. Based on an existing “network generation” tool which assumes a hexagon grid for the network, let’s place six towers around the center.

Step #3: logical connections

Let’s connect the towers. Please assume, that in the center of the network are the following components: SMO, 5G-Core, Near-RT-Ric, O-CU and enough cloud resources to host all O-DU. On the surrounding tower in this scenario, only O-RUs are placed.

Step #4: First O-RU placement

Let’s assume in this scenario an O-RU covers one third of the area around a tower - or an angle of 120°. Let’s assume further only one Cell is supported by an O-RU. The representation of a cell on the center tower is shown in the next figure.

Step #5: Complete the coverage around the center tower

When adding to further O-RUs the area around the tower is fully covered.

Step #6: Full network coverage

With 7 towers the RAN is constructed of 21 cells.

Step #7: Identify cells for the use case

The following figure high-lights the 2 cells used in the the e2e-integration use case. The have a small overlapping area (hand-over area). When we place a UE in the hand-over area. We can instruct the network via A1/E2 to ensure that this UE should be hand-overed to a certain cell to turn off the other cell for energy saving purposes.

Step #8: Identification of the NrCellDUs

The important information are the uuids of the objects:
Attention: this tree below was manual create from:
https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/391970817/o-ran-sc-e2e-integration-operational.json?api=v2

Please consider the json file as source of truth.

O-RAN-SC-E2E-Integration (network)                  [uuid: d2cf78dc-a3e9-595b-87f5-87592b117e7f]
└── O-RAN-NearRtRic-00                              [uuid: adf18ab2-27f8-59c3-9249-1d3ca1b41153]
    └── O-RAN-CU-00-00                              [uuid: 474eb696-7876-55f2-a25b-b7c076c55b42]
        ├── O-RAN-DU-00-00-00-00-00                 [uuid: 8cd84389-505d-5042-b3b8-42b1c8c64566]
        │   └── O-RAN-RU-00-00-00-03-02             [uuid: 0bf51acb-0c49-5cc6-96a8-d608b80bb78d]
        │       └── O-RAN-RU-00-00-00-00-00-00-CELL [uuid: ddd0a2c6-501f-5c05-a8c0-4ac9b463a729]
        └── O-RAN-DU-00-00-00-03-02                 [uuid: 7993707a-d664-55ea-9c93-3f2909d2ff08]
            └── O-RAN-RU-00-00-00-03-02             [uuid: 5071d7fb-a5a7-5def-a6f8-b697c4cf8e67]
                └── O-RAN-RU-00-00-00-03-02-00-CELL [uuid: ad7ffda6-12a2-5c31-8efd-1a342dda532d]

Assumption: we my need a “label” on TE&IV level: to be clarified including the mappings to ME.