-- [35] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements", December 2020
-- [36] O-RAN ALLIANCE, "O-RAN Working Group 1 Use Cases Detailed Specification v13.00," February 2024
-- [37] O-RAN ALLIANCE, "O-RAN Working Group 2 Non-RT RIC & A1 Interface: Use Cases and Requirements v05.00," November 2021
-- [38] O-RAN ALLIANCE, "O-RAN Working Group 3 Use Cases and Requirements v01.00", July 2021
-- [39] 3GPP TS 23.501: "System architecture for the 5G System (5GS)", December 2020
-- [40] 3GPP TS 38.306: "User Equipment (UE) radio access capabilities", December 2021
-- [41] 3GPP TS 23.502: "Procedures for the 5G System (5GS)", December 2023
-- [42] O-RAN ALLIANCE, "Certification and Badging Processes and Procedures", April 2022
-- [43] Void
-- [44] 3GPP TS 28.554, "Management and orchestration; 5G end to end Key Performance Indicators (KPI)", June 2023
-- [45] ETSI TS 103 786, "Environmental Engineering (EE); Measurement method for energy efficiency of wireless access network equipment; Dynamic energy performance measurement method of 5G Base Station (BS) "
-- [46] O-RAN ALLIANCE, "O-RAN Working Group 1 Network Energy Saving Use Cases", Technical Report v02.00, June 2023
-- [47] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2", December 2023
-- [48] 3GPP TS 36.101: "User Equipment (UE) radio transmission and reception"
-- [49] RFC 5357: "A Two-Way Active Measurement Protocol (TWAMP)"
-- [50] RFC 6985: "IMIX Genome: Specification of Variable Packet Sizes for Additional Testing"
-
-## 2.2 Informative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are not necessary for the application of the present document, but they assist the user with regard to a particular subject area.
-
-[i.1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”.
-
-# 3 Definition of terms, symbols and abbreviations
-
-## 3.1 Terms
-
-For the purposes of the present document, the terms [given in [i.1] and the following] apply:
-
-| | |
-|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| C-Plane | Control Plane: refers specifically to real-time control between O-DU and O-RU, and should not be confused with the UE’s control plane |
-| Near-RT RIC | Near-Real-Time RAN Intelligent Controller: an O-RAN Network Function (NF) comprised of the Near-RT RIC platform and Near-RT RIC Applications (xApps) [10]. |
-| Non-RT RIC | Non-Real-Time RAN Intelligent Controller: a functionality within SMO comprised of the Non-RT RIC Framework and the Non-RT RIC Applications (rApps) that manages the content carried across the A1 interface [10]. |
-| NSA | Non-Stand-Alone network mode that supports operation of SgNB attached to MeNB |
-| O-CU-CP | O-RAN Central Unit – Control Plane: a logical node hosting the RRC and the control plane part of the PDCP protocol [10]. |
-| O-CU-UP | O-RAN Central Unit – Control Plane: a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol. |
-| O-DU | O-RAN Distributed Unit: a logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split [10].. |
-| O-RU | O-RAN Radio Unit: a logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP’s “TRP” or “RRH” but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction) [10]. |
-| PTP | Precision Time Protocol (PTP) is a protocol for distributing precise time and frequency over packet networks. PTP is defined in the IEEE Standard 1588. |
-| PBCH | Physical Broadcast Channel applies for LTE and NR air interface |
-| PDCCH | Physical Downlink Control Channel applies for LTE and NR air interface |
-| SA | Stand-Alone network mode that supports operation of SUT attached to a 5G Core Network |
-| SCS | OFDM Sub Carrier Spacing |
-| S-Plane | Synchronization Plane: Data flow for synchronization and timing information between nodes |
-| SSB | Synchronization Signal Block, in 5G PBCH and synchronization signal are packaged as a single block |
-| U-Plane | User Plane: refers to IQ sample data transferred between O-DU and O-RU |
-
-## 3.2 Symbols
-
-Void
-
-## 3.3 Abbreviations
-
-For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply:
-
-| | |
-|-------|------------------------------------------------------------------------|
-| 5GS | 5G System |
-| CFI | Control format indicator |
-| DL | Downlink: data flows from the core network towards the UE |
-| DoS | Denial of service |
-| DUT | Device under Test |
-| E2E | End-to-End |
-| eNB | 3GPP Evolved Node B (LTE base station) |
-| EPS | Evolved Packet System |
-| FFS | For further study |
-| gNB | 3GPP Next-generation Node B (5G NR base station) |
-| IMS | IP Multimedia Subsystem |
-| IOT | Interoperability Testing |
-| IUT | Interface under Test |
-| KPI | Key performance indicator |
-| MCS | Modulation and coding scheme |
-| OTA | Over the air |
-| PDSCH | Physical downlink shared channel |
-| PRB | Physical resource block (12 x Resource Elements per PRB) |
-| PUSCH | Physical uplink shared channel |
-| QUIC | Quick UDP Internet Connections |
-| SUT | System under test |
-| TCP | Transmission Control Protocol: connection-oriented IP protocol |
-| TIFG | O-RAN Test and Integration Focus Group |
-| UDP | User Datagram Protocol: connectionless IP protocol |
-| UE | User Equipment: terminology for a mobile device/terminal in LTE and NR |
-| UL | Uplink: data flows from the UE towards the core network |
-| VoLTE | Voice over LTE |
-| VoNR | Voice over NR |
-| ViLTE | Video over LTE |
-
-# 4 Testing methodology and configuration
-
-## 4.0 Testing methodology introduction
-
-This clause describes the common testing methods and configurations which shall be used in the subsequent clauses. To ensure fair and comparable test results among various test campaigns, consistent test setups should be utilized. The test conditions should reflect the realistic operational environment as much as possible to ensure meaningful and as close to real-world results as possible. The present document harmonizes the test conditions, methodologies, and procedures; but the test configuration (parameters) of DUT/SUT is not specified in this document. However, it is required to record the complete test configuration used in the test report to enable the test to be reproduced if needed, and for the test results to potentially be used for other purposes, e.g. benchmarking or comparison.
-
-There are several design areas in RAN, where the vendors can differentiate such as RF performance (e.g. receiver sensitivity, PA design), radio link adaptation algorithms (e.g. radio channel estimation, MCS selection, MIMO mode selection, transmission mode selection, UL power control), scheduling and overhead management (e.g. number of control channels). These different approaches result in competitive advantages leading to differences in end-to-end performance which can be assessed with the tests defined in this document. Hence, it is not possible to set pass/fail criteria for all the tests, but the pass/fail criteria are set whenever possible, e.g. in the functional tests in Clause 5. The expected performance values are also indicated for reference network configurations.
-
-Unless otherwise stated in this document, the tests are suitable for both laboratory as well as field environments. All laboratory tests should be conducted over a cable, or in case of OTA tests, inside a shielded box/room, to ensure repeatability. In the laboratory, radio signal strength (i.e. attenuation) on the 5G NR path and/or 4G LTE path can be modified by using variable attenuators. The end-user device, if used, should be placed inside a shielded box to avoid interference from external signals. The laboratory environment should allow for stable and repeatable testing conditions, and it is more suitable for benchmarking. On the other hand, the field environment allows for the evaluation of complex scenarios with realistic radio channel variations and behavior of the network (e.g. inter-cell interference and handovers). Field tests should be performed over the air (OTA). In the field, radio signal strength should be modified by placing the UE in different positions inside the cell.
-
-Unless otherwise stated in this document, the same operating system (e.g. Windows 10) with default settings and configuration should be utilized for both ends (i.e. the host applications at end-user device (test UE) and application (traffic) server) in order to ensure a consistent test environment.
-
-Unless otherwise stated in this document, the tests are applicable to both TDD and FDD.
-
-Unless otherwise stated in this document, the following network architectures [26] depicted in Figure 4-1 below should be addressed and supported:
-
-- 4G LTE – Option 1
-- 5G NR standalone (5G SA) - Option 2
-- 5G NR non-standalone (5G NSA) - Option 3 / Option 3a / Option 3x
-
-
-
-The diagram illustrates two network architectures side-by-side. The left side, labeled '4G LTE – Option 1', shows a blue rectangular box labeled 'EPC' connected by a dashed red line to a blue oval labeled '4G LTE'. The '4G LTE' oval is connected by a dashed red line to a small icon of a mobile device (UE). The right side, labeled '5G SA – Option 2', shows a blue rectangular box labeled '5GC' connected by a dashed red line to a blue oval labeled '5G NR'. The '5G NR' oval is connected by a dashed red line to a small icon of a mobile device (UE).
-
-Diagram showing two network architectures: 4G LTE – Option 1 and 5G SA – Option 2. Option 1 shows an EPC connected to a 4G LTE base station, which is connected to a UE. Option 2 shows a 5GC connected to a 5G NR base station, which is connected to a UE.
-
-
-
-Figure 4-1: Three network architecture diagrams for 5G NSA. Option 3 shows EPC connected to 4G LTE, which is connected to 5G NR, which is connected to UE. Option 3a shows EPC connected to 4G LTE, which is connected to 5G NR, which is connected to UE, with a direct line from EPC to 5G NR. Option 3x shows EPC connected to 4G LTE, which is connected to 5G NR, which is connected to UE, with a direct line from EPC to 4G LTE.
-
-Figure 4-1: The network architectures supported in this document - red dashed lines indicate control plane while blue solid lines indicate user plane.
-
-## 4.1 System under test
-
-### 4.1.0 System under test overview
-
-The whole O-RAN system is the System under Test (SUT) and can be viewed as an integrated black box in the context of E2E testing [11], i.e. the internal functionality and architecture of SUT is out of scope. All involved O-RAN functions and interfaces shall properly interoperate together, and an end-to-end communication link shall be established between the end-user device and the application server or another end-user device. The testing of interoperability and conformance of the internal functions of the SUT is out of scope for this document. The SUT shall be in service mode and run in their normal operation state. The E2E KPIs are defined across the whole end-to-end communication link between the end-user device and the application (traffic) server or another end-user device – see Figure 4-2.
-
-
-
-Figure 4-2: A block diagram showing the end-to-end communication link. UE is connected to O-RAN System via Uu interface. O-RAN System is connected to 3GPP Core via S1, NG interface. 3GPP Core is connected to 3GPP Services and Other Services. A large double-headed arrow labeled 'End to end (E2E) KPIs' spans from UE to the services. A bracket below the O-RAN System block labels it as 'System under Test (SUT)'.
-
-Figure 4-2: The O-RAN system as System under Test (SUT) and E2E KPIs
-
-The end-to-end communication link includes O-RAN as well as non-O-RAN (e.g. core, end-user device) components which could negatively affect the end-to-end performance, e.g. limited capability of the test UEs and/or the application servers to generate/receive enough data traffic, or a bottleneck in the transport network. All these unwanted contributions should be avoided or at least minimized in order to measure unbiased KPIs. In addition, there may be a performance difference between different vendors and chipsets depending on their level of maturity. Commercial (production grade) devices (e.g. test UE) should be used whenever possible, ensuring the tests are sufficiently documented, stable and repeatable. Furthermore, the 4G/5G core or core emulator may influence the test results, particularly throughput, registration and deregistration latency, and service scale. Therefore, the choice of an 4G/5G Core (real or emulated) should be taken consciously. For this reason, the 4G/5G core shall be documented in the test setup. Ideally, this core should be reference tested prior to executing any E2E tests, to ensure that the test results represent RAN performance instead of exposing core performance limitations.
-
-All O-RAN components [10] (such as O-CU-CP and O-CU-UP, O-DU, O-RU) and interfaces [10] (such as Open Fronthaul, X2) included in the System under Test should have been tested against their respective conformance and interoperability O-RAN specifications if they are available. For multi-cell and handover scenarios, the SUT can contain more O-RUs, O-DUs, O-CU-CPs and O-CU-UPs.
-
-#### 4.1.1 Load and Stress Interfaces to SUT
-
-A key priority of load and stress testing is to exercise the performance of the SUT near or exceeding full capacity. The capacity of the O-DU and O-CU within the SUT may be such that applying all traffic necessary to reach full capacity may require many O-RUs which may not always be feasible. Figure 4-3 defines additional traffic insertion points where traffic may be applied directly at the Open Fronthaul or F1 Interfaces to the SUT in order to provide additional background UE stack traffic along with application of test traffic at the Uu interface to O-RU(s) in the SUT. This should allow for adequate stress on the complete SUT for execution of the E2E test scenarios.
-
-
-
-The diagram illustrates the interfaces for applying incremental traffic to the System Under Test (SUT). At the top, a large double-headed arrow labeled 'End to end (E2E) KPIs' spans from the UE to the 3GPP Services. Below this, the 'O-RAN System (SUT)' is shown as a central block containing multiple O-RUs (O-RU #1 to O-RU #n) and O-DUs (O-DU #1 to O-DU #m). Each O-RU is connected to an O-DU via an 'OpenFH' (Open Fronthaul) interface. Each O-DU is connected to an O-CU via an 'F1' interface. The O-CU is connected to the '3GPP Core' via 'S1, NG' interfaces. The '3GPP Core' is connected to '3GPP Services' and 'Other Services'. On the left, a 'UE' is connected to the O-RUs via a 'Uu' interface. Below the UE, there are two optional test points: 'UE+O-RU (Optional)' connected to the OpenFH interface, and 'UE+O-DU (Optional)' connected to the F1 interface.
-
-Diagram of interfaces for applying incremental traffic to System Under Test (SUT).
-
-Figure 4-3: Interfaces for applying incremental traffic to System Under Test for Load and Stress scenarios
-
-## 4.2 Test and measurement equipment and tools
-
-All the tests shall be performed in a non-intrusive manner; that is, in a manner in which the SUT is not required to support any functionality or mode of operation beyond that required for normal operation in a production network. The SUT is not expected to be used as test tools when deployed in a production network, and therefore it should not be used as test tools during end-to-end testing.
-
-All the measurement equipment and tools used in the tests shall be properly calibrated and configured in advance in order to minimize the influence of the test equipment on the measurements results. The parameters (e.g. attenuation) of cables, attenuators, splitters, combiners, etc. shall be also measured in advance and compensated for in the final measurement results.
-
-Table 4-1 Test and measurement equipment and tools
-
-| Test tool | Description |
-|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Real UE and/or UE emulator | The UE (Real UE or UE emulator) is used to establish stateful end-to-end connection and to generate or receive data traffic.
The real UE used in this context as a test tool is typically a UE which is designed for commercial or testing applications with certain test and diagnostic functions enabled for test and measurement purposes. Such test and diagnostic functions should not affect the performance.
The real UE requires a SIM card (real or emulated) which is pre-provisioned with subscriber profiles. A UE emulator or multiple real UEs can be used in multi-UE test scenarios requiring multiple UEs sessions. The UE is connected with the SUT either via RF cables or via an over the air (OTA) connection. In a lab environment, the UE should be placed inside an RF shielded box/room in order to avoid interference from external signals.
|
-
-| Test tool | Description |
-|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | The logging tool connected to the UE is used to capture measurements and KPI logs for test validation and reporting. |
-| UE + O-RU emulator | The UE + O-RU emulator is used to establish stateful connections and to generate or receive data traffic directly at the Open fronthaul connection to an O-DU within the O-RAN SUT.
The UE + O-RU emulator is typically designed for testing applications with certain test and diagnostic functions enabled for test and measurement purposes
The UE + O-RU emulator is used to create background traffic driven by multiple stateful UE stacks for purposes of increasing the load on the O-DU in addition to the E2E traffic applied at the Uu interface to the SUT
|
-| UE + O-DU emulator | The UE + O-DU emulator is used to establish stateful connections with, and to generate or receive data and signaling traffic directly at the F1 connection to the O-CU within the O-RAN SUT.
The UE + O-DU emulator is typically designed for testing applications with certain test and diagnostic functions enabled for test and measurement purposes.
The UE + O-DU emulator is used to create background traffic driven by multiple UE connections for purposes of increasing the load on the O-CU in addition to the E2E traffic applied at the Uu interface to the SUT
|
-| 4G/5G Core or Core emulator | The 4G/5G core or core emulator is used to terminate 4G/5G NAS sessions, and to support core network procedures required for RAN (SUT) testing. 4G/5G core or core emulator must support end-to-end connection and data transfer between Application server and Real UE/UE emulator. |
-| IMS Core or IMS Core emulator | The IMS Core or IMS core emulator is used to support voice and video calling services like VoLTE, ViLTE, VoNR, Video over NR and EPS Fallback using protocols like SIP and RTP. IMS core or IMS core emulator should interface with the 4G/5G core to setup dedicated bearers/QoS Flows to support voice and video calling services. |
-| Application (traffic) server | The application (traffic) server is used as an endpoint for generation and/or termination of various data traffic streams to/from Real UE(s)/UE emulator. The application server should be capable to generate data traffic for the services under test.
The application server should be placed as close as possible to the core/core emulator, and connected to the core/core emulator via a transport link with sufficient capacity.
|
-| Protocol analyzer | The protocol analyzer is used for test results verification, and for troubleshooting and root cause analysis of failed tests. Note that if IPsec encryption is applied at the network interface, then it would not be possible to use the protocol analyzer without decryption of IPsec. |
-| Network impairment emulator | The network impairment emulator is used for tests which require insertion of impairment (packet delay and/or jitter) at the network interface (e.g. Open fronthaul). |
-| RF attenuators and/or Fading generator | RF attenuators are used for tests which require radio signal attenuation. Fading generators can be used to simulate specific radio channel conditions (e.g. Urban, Rural, High Speed Train). |
-| RF shielded box/room | The RF shielded box/room is used for over the air (OTA) connectivity between the UE and SUT in the lab environment. The RF shielded box/room should support reliable MIMO testing, if MIMO is required. |
-| Packet generation tool / DoS emulator | The packet generation tool / Denial of Service (DoS) emulator is used for DoS traffic generation of security tests. The tool must support crafting network traffic on network layers from 2 to 7, which conform to network protocols such as: Ethernet, IP, UDP, TCP, PTP, eCPRI, TLS, HTTP/HTTPS. The tool is intended to be deployable in various network segments (communication planes) according to the testing needs. |
-
-| Test tool | Description |
-|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Packet capture tool | The packet capture tool is used to capture samples of data traffic for validation, analysis, and troubleshooting. In the case of security test cases it can be used to capture samples of legitimate traffic, which then can be used as templates for fuzzing attacks. The tool must support capturing network traffic on network layers from 2 to 7, which conform to network protocols such as: Ethernet, IP, UDP, TCP, PTP, eCPRI, TLS, QUIC, HTTP/HTTPS. The tool is intended to be deployable in various network segments (communication planes) according to the testing needs. |
-| Network tap | A network tap is a hardware or software device which provides access and visibility to the data flowing across a computer network. |
-| Fuzzing tool | The protocol fuzzing tool is used for unexpected protocol input generation of security tests. The tool must support mutating and replaying of captured network traffic on network layers from 2 to 7, which conform to network protocols such as: Ethernet, IP, UDP, TCP, PTP, eCPRI, TLS, HTTP/HTTPS. The tool is intended to be deployable in various network segments (communication planes) according to the testing needs. |
-| Vulnerability scanning tool | The vulnerability scanning tool is used for blind exploitation of well-known vulnerabilities during security tests. The tool should rely on cyclically updated database of known vulnerabilities based on Common Vulnerabilities and Exposures (CVE) and should support scanning network services running on TCP/IP stack of protocols. The tool is intended to be deployable in various network segments (communication planes) according to the testing needs. |
-| NFV benchmarking and resource exhaustion tool | The Network Function Virtualization (NFV) tool is used for O-Cloud system performance measurement and resource exhaustion type of DoS attack generation. This tool should be able to be deployed on any types of O-Cloud environment (public or private) with testing VNF(s) and/or CNF(s) support. |
-| Energy meter | The energy meter measures the cumulative energy consumption over a period of time. The unit of measurement is Watt-hours or Joules. |
-
-## 4.3 Test report
-
-Tests should be described in the test report with sufficient detail to allow the tests to be reproducible by different parties and to enable benchmarking and comparison. The unified reporting of test results is important for benchmarking and comparison of results. The following common **minimum set of configuration parameters and information** about the test environment shall be reported in each test report [3]:
-
-NOTE: 3GPP specifications for 4G LTE are part of the 36.xxx series, while 3GPP specifications for 5G NR are part of the 38.xxx series.
-
-Deployment scenario:
-
-- Deployment architecture (e.g. indoor hotspot, macro/micro, dense urban, urban, rural)
-- Number of cells and their layout (incl. a mapping between O-CUs, O-DUs, O-RUs and cells)
-
-Cell configuration parameters of each cell (if the parameters are not common to all cells):
-
-- Downlink/Uplink Carrier frequency (MHz)
-- Downlink/Uplink EARFCN [48, Clause 5.7.3] or NR-ARFCN [18, Clause 5.4.2.1]
-- (Aggregated) Channel bandwidth (MHz) and transmission bandwidth configuration (i.e. number of Physical Resource Blocks (PRBs)) [48, Clause 5.6] [18, Clause 5.3]
-- Duplex mode (e.g. FDD, TDD)
-
-- TDD configuration parameters for 4G LTE, if applied
- - Uplink-downlink configuration [25, Table 4.2-2]
- - Special subframe configuration [25, Table 4.2-1]
-- TDD configuration parameters for 5G [21, Clause 11.1], if applied
- - Pattern 1 and Pattern 2
- - slot configuration period (parameter *dl-UL-TransmissionPeriodicity*) (msec)
- - number of consecutive slots with only downlink symbols at the start of the period (parameter *nrofDownlinkSlots*)
- - number of consecutive downlink symbols within the slot which follows the downlink slots (parameter *nrofDownlinkSymbols*)
- - number of consecutive slots with only uplink symbols at the end of the period (parameter *nrofUplinkSlots*)
- - number of consecutive uplink symbols within the slot which precedes the uplink slots (parameter *nrofUplinkSymbols*)
-- Subcarrier spacing (SCS) (15, 30, 60, 120 or 200 kHz) [20, Table 4.2-1]
-- Cyclic prefix (CP) (normal or extended) [20, Table 4.2-1]
-- SSB periodicity (ms) [21, Clause 4.1]
-
-SU/DUT and UE configuration parameters:
-
-- Number of supported MIMO layers at both SUT and UE sides
-- Antenna configuration (number of Tx/Rx antenna elements, e.g. 4T4R) at both SUT and UE sides
-- Transmit power at antenna connectors at SUT (dBm)
-- Antenna gains at SUT (dBi)
-
-Information about test environment:
-
-- List of utilized test and measurement equipment and tools (incl. logging tools, test UE(s)) including the type and version. The Operating Systems (incl. the version) used at end-user device and application server should be noted as well. If TCP performance has been measured, the setting of TCP configuration parameters should be also noted.
-- Information about the SUTs (e.g. O-RU, O-DU, O-CU-CP, O-CU-UP) including the type, parameters, configuration, SW and HW versions, Interface profiles (e.g. Open fronthaul IOT profile [12]).
-
-The template for the test report for general use in reporting E2E test results can be found in Annex A. Any E2E testing for the purpose of seeking an O-RAN E2E Badge must comply with the processes, procedures and report templates defined in [42]. Photos and figures should also be taken as part of the test report in order to illustrate the test environment. Additional parameters and counters are specified in the description of each test in the subsequent clauses.
-
-## 4.4 Data traffic
-
-This clause describes the full buffer and finite buffer traffic models that are utilized in some of the tests in this document.
-
-The **full buffer traffic model** is characterized by a constant number of users in the cell during the test, wherein the buffers of the users' data flows always have unlimited amount of data to transmit. The model is preferred due to its simplicity.
-
-In the **finite buffer traffic model**, a user is assigned a finite payload to transmit or receive when it arrives. The user arrival process of this model captures the fact that the users in the network are not simultaneously active at the same time, but they rather become active when they start a data session that require the download/upload of data. Examples of models are FTP traffic model 1/2/3 [14] largely used in 3GPP simulations.
-
-Data throughput can be measured at different protocol layers. Each network protocol layer adds extra overhead (header information), thereby reducing the data throughput available to the layer above. The highest throughput is provided at the physical layer including user data and the overhead from higher protocol layers. The data throughput at the RLC (Radio Link Control) layer is independent from radio-specific overhead and therefore well-suited for comparison with other access technologies. The application layer throughput is the net throughput seen by user applications operating on top of either UDP, TCP or QUIC – for example, the typical FTP overhead is around 3-5%, typical HTTP overhead is around 30% compared to RLC throughput. Unless otherwise stated in this document, the reported throughput (user data rate) shall consider all the overhead (control channels, reference signals).
-
-UDP (User Datagram Protocol), TCP (Transmission Control Protocol) and QUIC (Quick UDP Internet Connections) are typical transport layer protocols utilized in the tests.
-
-**UDP** is a simple, connection-less transport layer protocol which does not guarantee error-checking and recovery. UDP throughput is more suitable for benchmarking as it is not affected by the system configuration parameters. UDP is also faster, lighter (less overhead) and more efficient than TCP.
-
-**TCP** is reliable, connection-oriented transport layer protocol which includes error-checking and recovery, and guarantees data delivery with preserved order of data packets. The performance of a TCP connection can be impacted by various factors such as end-to-end latency, number of retransmissions, packet loss, and TCP configuration parameters such as window size, window scale, timestamps, etc. [6]. The default values of TCP configuration parameters can also vary in different Operation Systems (incl. different versions of the same OS) which are used at the end-user device (test UE) and application (traffic) server. It is recommended to use the same OS (incl. the version) with default setting at the end-user device (test UE) and application server. Since the settings and behavior of TCP connections cannot be easily unified and normalized, the measurement of TCP performance is recommended only as an illustrative indicator, and UDP performance should be used for the benchmarking and assessment of system performance.
-
-**QUIC** (Quick UDP Internet Connections) is a general-purpose transport layer protocol built on top of UDP to support the next generation of application layer protocols. QUIC provides features like connection establishment, congestion control, stream multiplexing and forward error correction to provide a secure and reliable connection-oriented protocol over UDP. QUIC is being used as the standard transport mechanism for HTTP/3.
-
-In addition, the following application layer protocols are utilized in the tests.
-
-**Hypertext Transfer Protocol (HTTP)** is the application layer protocol used in the internet. HTTP is a stateless protocol which follows the request-response model between client and the server. The client places a request for a resource to the server, and the server responds back to the client with requested resource and/or the appropriate response code. HTTP's support for headers between the client-server makes this protocol simple, extensible, and powerful.
-
-**Session Initiation Protocol (SIP)** is an application layer signalling protocol for real-time sessions like IP telephony. This is a text-based protocol which allows negotiation between two end points to initiate a session, maintain the session and terminate the session. SIP is the default signalling protocol used in the telecom network for VoLTE, ViLTE, VoNR and Video over NR.
-
-**Real-time Transport Protocol (RTP)** is an application layer protocol used to transmit real-time data such as audio and video over IP network. RTP is the default data plane protocol used in the telecom network for services like VoLTE, ViLTE, VoNR and Video over NR. RTP does not guarantee Quality of Service but works in conjunction with Real Time Control Protocol (RTCP) to detect and convey packet loss and jitter information.
-
-**File Transfer Protocol (FTP)** is an application layer protocol to transfer files on a computer network. FTP follows a client-server model where the client can upload the file to the server, or download the file from the server. FTP protocol uses two separate connections between the client and the server – one for control and the other one for data or transfer of file. FTP along with multiple variants of the protocol have become the de-facto standards to transfer file on the internet.
-
-## 4.5 Mobility classes
-
-The following classes of mobility shall be used for the applicable tests [13]:
-
-- Stationary: 0 km/h
-- Pedestrian: 0 km/h to 10 km/h (typical value 4 km/h)
-- Vehicular: 10 km/h to 120 km/h (typical value 50 km/h)
-- High speed vehicular: 120 km/h to 500 km/h (typical value 150 km/h)
-
-High speed vehicular speeds close to 500 km/h are mainly used for high speed trains.
-
-## 4.6 Radio conditions
-
-The radio signal quality is described by the radio parameters such as RSRP and SINR. These radio parameters are defined differently in LTE and 5G NR.
-
-- **LTE RSRP** (Reference Signal Received Power) [7] is defined as the linear average over the power contributions (in [W]) of the resource elements that carry cell-specific reference signals (CRS) within the considered measurement frequency bandwidth. The RSRP is reported from UE back to SUT. The reporting range of RSRP is defined from -140dBm to -44dBm [8].
-- **LTE SINR** (Signal to Noise and Interference Ratio) has not been formerly defined in the 3GPP specification. The UE does not send the results back to SUT. The SINR is measured and used only in UE. Specific implementations may vary, and it is up to the manufacturer to decide, how to implement this measurement. This is making difficult to compare results of different devices. In [7], SINR is defined as the linear average over the power contribution (in [W]) of the resource elements carrying cell-specific reference signals divided by the linear average of the noise and interference power contribution (in [W]) over the resource elements carrying cell-specific reference signals within the same frequency bandwidth.
-- **5G SS-RSRP** (Synchronization Signal based Reference Signal Received Power) [7] is defined as the linear average over the power contributions (in [W]) of the resource elements that carry secondary synchronization (SS) signals. SS-RSRP is the equivalent of the RSRP parameter used in LTE systems. The reporting range of SS-RSRP is defined from -140dBm to -40dBm [9].
-- **5G SS-SINR** [7] is defined as the linear average over the power contribution (in [W]) of the resource elements carrying secondary synchronisation signals divided by the linear average of the noise and interference power contribution (in [W]) over the resource elements carrying secondary synchronisation signals within the same frequency bandwidth. The SS-SINR is reported from UE back to SUT. The reporting range of SS-SINR is defined from -23dB to 40dB.
-
-It is worth to note that in 5G, the Channel State Information Reference Signal (CSI-RS) can also be used for RSRP and SINR measurements. Due to different transmit powers of CSI-RS and SS, CSI-RS-based SINR and RSRP measurement values are usually greater than SS-based SINR and RSRP.
-
-The minimum coupling loss (MCL) [2] between O-RU (antenna) and UE shall be ensured:
-
-- **Macro cell** deployment scenario (wide area BS): MCL = 70dB corresponding to minimal O-RU (antenna) to UE distance along the ground equal to around 35 m
-- **Small cell** (micro cell) deployment scenario (medium range BS): MCL = 53dB corresponding to minimal O-RU (antenna) to UE distance along the ground equal to around 5 m
-- **Pico cell** deployment scenario (local area BS): MCL = 45dB corresponding to minimal O-RU (antenna) to UE distance along the ground equal to around 2 m
-
-The radio parameters (RSRP, SINR) should be measured across the entire range covering scenarios from cell centre to cell edge. Based on the test results, the RSRP and SINR distribution statistics can be calculated and described as a cumulative distribution function (CDF) curve. According to the CDF curve, the four types of radio conditions can be defined as: excellent
-
-(95%-100%), good (80%-90%), fair (40%-60%) and poor (5%-15%) [3]. Table 4-2 shows the RSRP and SINR thresholds for various radio conditions. Table 4-2 RSRP and SINR thresholds for various radio conditions
-
-Note that the RSRP values should primarily be used for UL assessments, and the SINR values for DL assessment.
-
-**Table 4-2 RSRP and SINR thresholds for various radio conditions**
-
-| Radio conditions | RSRP (dBm)
SS-RSRP (dBm) | DL SINR (dB)
DL SS-SINR (dB) | |
-|----------------------------|--------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Excellent
(cell centre) | > -75 | > 25 | - Utilization of the highest possible MCS, transport block size and MIMO rank
- Peak performance measurements
- Negligible interference from neighbor cells
|
-| Good | -75 to -90
(typical value = -85) | 15 to 20
(typical value = 17) | |
-| Fair | -90 to -105
(typical value = -95) | 5 to 10
(typical value = 7) | |
-| Poor
(cell edge) | < -105
(typical value = -110) | < 5
(typical value = 3) | - Minimum performance measurements
- Strong interference from neighbor cells
|
-
-There are many different factors that influence signal strength and quality during the field testing; these factors include, but are not limited, to the following:
-
-- Proximity to the cellular tower (antenna)
-- Load in neighbor cells
-- Surrounding physical barriers (mountains, buildings, etc.)
-- Weather conditions
-
-## 4.7 Inter-cell interference
-
-Some tests in this document are conducted either in a single cell scenario without any inter-cell interference, or in a multi-cell scenario where the serving cell is surrounded by neighboring cells generating traffic load (interference on the serving cell) in the downlink or uplink directions.
-
-Generating a realistic traffic load is important for meaningful results. As the number of real UEs are always a limiting factor, artificial (dummy) traffic load and interference generation may be used.
-
-In the **single cell scenario**, the serving cell is isolated, and all the surrounding neighbor cells are turned off (neither control nor data channels are used).
-
-In the **multi-cell scenario**, all the neighbor cells are turned on. The following load setups shall be used:
-
-- Load 0%** - all the surrounding neighbor cells are turned on without any data traffic and end-user device attached. Inter-cell interference is generated only on control channels (broadcasting, synchronization channels) without any inter-cell interference on data channels.
-- Load 30%** - all the surrounding neighbor cells are turned on with data traffic. Inter-cell interference is generated both on control and data channels. The level of interference on data channel is controlled by the amount of data traffic. The interference level of 30% in downlink means that 30% of downlink PRBs are randomly occupied with a dummy traffic. In uplink, this interference level corresponds to 3dB rise of IoT (Interference over Thermal) noise at the receiver side (i.e. SUT's antenna(s)). The received interference noise from the UEs of neighbor cells uplink transmission should lead to 3dB rise of receiver's noise power [3].
-- Load 50%** - all the surrounding neighbor cells are turned on with data traffic. Inter-cell interference is generated both on control and data channels. The level of interference on data channel is controlled by the amount of data traffic. The interference level of 50% in downlink means that 50% of downlink PRBs are randomly occupied with a dummy
-
-traffic. In uplink, this interference level corresponds to 5dB rise of IoT (Interference over Thermal) noise at the receiver side (i.e. SUT's antenna(s)).
-
-- **Load 70%** - all the surrounding neighbor cells are turned on with data traffic. Inter-cell interference is generated both on control and data channels. The level of interference on data channel is controlled by the amount of data traffic. The interference level of 70% in downlink means that 70% of downlink PRBs are randomly occupied with a dummy traffic. In uplink, this interference level corresponds to 7dB rise of IoT (Interference over Thermal) noise at the receiver side (i.e. SUT's antenna(s)).
-- **Load 100%** - fully loaded multi-cell scenario generating the highest possible inter-cell interference. All the surrounding neighbor cells are turned on with data traffic. Inter-cell interference is generated both on control and data channels. The level of interference on data channel is controlled by the amount of data traffic. The interference level of 100% in downlink means that 100% of downlink PRBs are occupied with a dummy traffic. In uplink, this interference level corresponds to 9dB rise of IoT (Interference over Thermal) noise at the receiver side (i.e. SUT's antenna(s)).
-
-## 4.8 Spectral efficiency
-
-The spectral (or spectrum) efficiency (SE) is an important criterion for fair performance assessment and benchmarking of different systems when various transmission bandwidths, duplex modes (FDD/TDD) and TDD DL/UL configurations are normalized.
-
-The spectral efficiency is calculated by dividing the data throughput by the aggregated channel bandwidth (incl. guard bands) in DL or UL assuming single user and FDD duplex mode. The corresponding link frame structure is fully (100%) utilized in frequency and time domains.
-
-$$SE_{FDD\_DL} [bps/Hz] = \frac{DL\ data\ throughput\ [bps]}{DL\ channel\ bandwidth\ [Hz]}$$
-
-$$SE_{FDD\_UL} [bps/Hz] = \frac{UL\ data\ throughput\ [bps]}{UL\ channel\ bandwidth\ [Hz]}$$
-
-In case of TDD where the same spectrum is used at different times for the uplink and downlink, the spectral efficiency is in addition multiplied by the fraction of resources (slots and symbols, not including switching gap) allocated to the particular link direction within 10ms radio frame.
-
-$$SE_{TDD\_DL} [bps/Hz] = \frac{DL\ data\ throughput\ [bps]}{channel\ bandwidth\ [Hz]} * \frac{number\ of\ total\ symbols\ per\ frame}{number\ of\ DL\ symbols\ per\ frame}$$
-
-$$SE_{TDD\_UL} [bps/Hz] = \frac{UL\ data\ throughput\ [bps]}{channel\ bandwidth\ [Hz]} * \frac{total\ number\ of\ symbols\ per\ frame}{number\ of\ UL\ symbols\ per\ frame}$$
-
-# 5 Functional tests
-
-## 5.0 Functional tests introduction
-
-This clause describes the tests evaluating and assessing the functionality of the radio access network from a network end-to-end perspective. The focus of the testing is on the end-user functionality based on 3GPP and O-RAN specifications. Pass-fail criteria are defined for the tests wherever possible.
-
-The general test methodologies and configurations are mentioned in Clause 4.
-
-Unless otherwise stated in the clause, the tests are suitable and can be conducted in both laboratory as well as field environments, with pros and cons of both environments as described in Clause 4.
-
-The following end-to-end functional tests are defined in this clause as an extension of the NGMN testing framework [3]:
-
-**Table 5-1: E2E Functionality Test Case Summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|------------------------------------------------------------------|------------------|-----------------------|-----|-----|
-| | | | LTE | NSA | SA |
-| Test ID | E2E Functionality Assessment | | | | |
-| 5.1 | LTE/5G NSA Attach and detach of single UE | Accessibility | Y | Y | N/A |
-| 5.2 | LTE/5G NSA Attach and detach of multiple UEs | Accessibility | Y | Y | N/A |
-| 5.3 | 5G SA Registration and deregistration of single UE | Accessibility | N/A | N/A | Y |
-| 5.4 | Intra O-DU mobility | Mobility | N/A | Y | Y |
-| 5.5 | Inter O-DU mobility | Mobility | N/A | Y | Y |
-| 5.6 | Inter O-CU mobility | Mobility | N/A | Y | Y |
-| 5.7 | 5G SA registration and deregistration to Single network slices | Accessibility | N/A | N/A | Y |
-| 5.8 | 5G SA registration and deregistration to multiple network slices | Accessibility | N/A | N/A | Y |
-| 5.9 | Idle Mode Intra- O-DU mobility | Mobility | N/A | N/A | Y |
-| 5.10 | Idle Mode Inter- O-DU mobility | Mobility | N/A | N/A | Y |
-| 5.11 | Idle Mode Inter- O-CU mobility | Mobility | N/A | N/A | Y |
-| 5.12 | 5G/4G Inter-System mobility - 5GS to EPS handover | Mobility | Y | N/A | Y |
-| 5.13 | 5G/4G Inter-System mobility - EPS to 5GS handover | Mobility | Y | N/A | Y |
-
-The test description, setup and procedures are detailed in the following clauses for each test case.
-
-## 5.1 LTE/5G NSA attach and detach of single UE
-
-### 5.1.1 Test description and applicability
-
-The purpose of this test is to validate E2E O-RAN C-plane functionality with a single UE. These tests are valid for either LTE or 5G NSA. In this test scenario, the successful attach and detach procedure shall be validated by the “Power ON” and “Power OFF” of a single UE, as described in the following specifications:
-
-- 1) LTE Attach as per 3GPP TS 23.401 [29], Clause 5.3.2.1 E-UTRAN Initial Attach
-- 2) LTE Detach as per 3GPP TS 23.401 [29], Clause 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN
-- 3) 5G NSA Attach as per 3GPP TS 23.401 [29], Clause 5.3.2.1 E-UTRAN Initial Attach and 3GPP TS 37.340 [30] Clause 10.2.1 EN-DC (Secondary Node Addition)
-- 4) 5G NSA Detach as per 3GPP 23.401, Clause 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN and 3GPP TS 37.340 [30] Clause 10.4.1 EN-DC (Secondary Node Release) [29]
-
-The test procedure shall be performed in excellent radio conditions for 10 iterations. Attach success rate, detach success rate, and attach latency shall be measured and captured.
-
-### 5.1.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e. isolated cell without any inter-cell interference – see Clause 4.7) with a stationary UE (real or emulated) placed under excellent radio conditions as defined in Clause 4.6, using LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA) as the metric. Within the cell there shall be only one active UE. The test is suitable for lab as well as field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The test environment should be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside an RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of the cell close to the radiated SUT's antenna(s), where excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA) as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.6) should not be exceeded.
-
-Please refer to Figure 6-1 for the E2E test setups for LTE and 5G NSA.
-
-### 5.1.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The UE (real or emulated UE) is placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA) in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Start the logs to capture the call flow and signalling messages
-- 5) "Power ON" the UE to attach to the LTE or 5G NSA cell. Wait for a successful attach.
-- 6) "Power OFF" the connected UE to detach from the network. Wait for a successful detach.
-- 7) Stop and save the test logs. The logs shall be captured and kept for test result reference and measurements
-- 8) Repeat steps 4 to 7, for 10 times and record the KPIs mentioned in Clause 5.1.4.
-
-### 5.1.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- KPIs mentioned in Table 5-2 and Table 5-3
-
-Validate the successful procedures from the collected logs. Expected success rate for Attach/Detach and Secondary Node Addition/Release KPI is 100%. The attach-detach procedure shall pass 10 consecutive times to mark the test case as passing. The gap analysis shall be provided for the measured and the expected target KPIs.
-
-- LTE Attach-Detach test case validation and KPI measurements
- - Validate successful attach 10 times with LTE cell (Refer to 3GPP TS 23.401 [29], Clause 5.3.2.1 E-UTRAN Initial Attach). In the UE logs or applications installed on UE, check that UE is attached to correct cell (example PCI, Global eNB ID, ARFCN as per test configuration)
- - Measure the attach success rate by validating attach request and attach complete for each iteration. Record the attach success rate in Table 5-2
- - Measure the attach latency by calculating the time between attach request to attach complete. Capture the latency for each iteration and sort the latency value observed for each iteration in ascending order. Record the Minimum, Average (Sum of all latency value/ Total Iterations, Total Iterations are 10 in this case) and Maximum latency value observed in Table 5-3
-
-- Validate successful detach/attach with LTE cell (Refer to 3GPP TS 23.401 [29], Clause 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN). Signalling connection release shall be validated from message flow (UE context release and RRC connection release messages). Measure the detach success rate by validating detach request and detach accept for each iteration. Record the detach success rate in Table 5-2
-- 5G NSA Attach-Detach test case validations and KPI measurements
- - Validate successful multiple attaches with 5G NSA cell (3GPP TS 23.401 [29], Clause 5.3.2.1 E-UTRAN Initial Attach and 3GPP TS 37.340 [30] Clause 10.2.1 EN-DC for Secondary Node Addition)). In the UE logs or applications installed on UE, check that UE is attached to correct cell (example PCI, Global eNB ID/Global gNB, ARFCN/NR-ARFCN as per test configuration for LTE /5G cells )
- - Measure the attach success rate by validating attach request and attach complete for each iteration. Also measure the secondary node addition success rate by validating the SgNB addition request and SgNB reconfiguration complete as per flow 3GPP TS 37.340 [30] Clause 10.2.1 EN-DC for each iteration. Record the attach success rate and secondary node addition success rate in Table 5-2
- - Validate successful detach attach (LTE Detach and 5G Secondary Node release) with 5G NSA cell (Refer to 3GPP TS 23.401 [29], Clause 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN and 3GPP TS 37.340 [30] Clause 10.4.1 EN-DC for Secondary Node Release)). Signalling connection release shall be validated the from message flow (UE context release and RRC connection release messages). 5G secondary node shall also get released successfully. Measure the detach success rate by validating detach request and detach accept for each iteration. Record the detach success rate in Table 5-2
-
-**Table 5-2 KPI to be captured for single UE attach-detach test case**
-
-| LTE KPI | | 5G NSA KPI | | |
-|---------------------|---------------------|---------------------|---------------------|----------------------------|
-| Attach Success Rate | Detach Success Rate | Attach Success Rate | Detach Success Rate | SgNB addition Success rate |
-| | | | | |
-
-**Table 5-3 Latency KPI for attach**
-
-| LTE Attach Time (millisecond) | | |
-|-------------------------------|---------|---------|
-| Minimum | Maximum | Average |
-| | | |
-
-## 5.2 LTE/5G NSA attach and detach of multiple UEs
-
-### 5.2.1 Test description and applicability
-
-The purpose of this test is to validate E2E O-RAN C-plane functionality with multiple UEs. These tests are valid for either LTE or 5G NSA. In this test scenario, the successful attach and detach procedure shall be validated by the “Power ON” and “Power OFF” of multiple (at least 2) UEs, as described in the following specifications:
-
-- 1) LTE Attach as per 3GPP TS 23.401 [29], Clause 5.3.2.1 E-UTRAN Initial Attach
-- 2) LTE Detach as per 3GPP TS 23.401 [29], Clause 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN
-- 3) 5G NSA Attach as per 3GPP TS 23.401 [29], Clause 5.3.2.1 E-UTRAN Initial Attach and 3GPP TS 37.340 [30] Clause 10.2.1 EN-DC (Secondary Node Addition)
-- 4) 5G NSA Detach as per 3GPP 23.401, Clause 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN and 3GPP TS 37.340 [30] Clause 10.4.1 EN-DC (Secondary Node Release) [29]
-
-The test procedure shall be performed in excellent radio conditions for 10 iterations. Attach success rate, detach success rate, and attach latency shall be measured and captured.
-
-### 5.2.2 Test setup and configuration
-
-The network setup is a single cell scenario (i.e. isolated cell without any inter-cell interference – see Clause 4.7) with multiple stationary UEs (real or emulated) placed under excellent radio conditions as defined in Clause 4.6, using LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA) as the metric. The test is suitable for lab as well as field environments. The minimum number of UEs which are used shall be two (2).
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report, including the chosen number of UEs.
-
-**Laboratory setup:** The radio conditions experienced by the UEs can be modified using variable attenuators/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The test environment should be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA) as defined in Clause 4.6) for the UEs, but the minimum coupling loss (see Clause 4.6) should not be exceeded. The UEs should be placed inside an RF shielded box or RF shielded room if the UEs are not connected via cable.
-
-**Field setup:** The multiple UEs are placed in the centre of the cell close to the radiated SUT's antenna(s), where excellent radio conditions (LTE RSRP and 5G SS-RSRP as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.6) should not be exceeded.
-
-Please refer to Figure 6-1 for the E2E test setups for LTE and 5G NSA.
-
-### 5.2.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The multiple UEs (real or emulated) are placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA) in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA as applicable for the test scenario, and there shall not be any connectivity issues.
-- 4) Start the logs to capture the call flow and signalling messages.
-- 5) "Power ON" the multiple connected UEs to attach to the LTE or 5G NSA cell. Wait for the successful attach of all UEs.
-- 6) "Power OFF" the multiple UEs to detach from the network. Wait for the successful detach of all UEs
-- 7) Stop and save the test logs. The logs shall be captured and kept for test result reference and measurements
-- 8) Repeat steps 4 to 7, for a total of 10 times and record the KPIs mentioned in Clause 5.2.4
-
-### 5.2.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- KPIs mentioned in Table 5-4 and Table 5-5
-
-Validate the successful procedures for each UE from the collected logs. Expected success rate for Attach/Detach and Secondary Node Addition/Release KPI is 100%. The attach-detach procedure shall pass 10 consecutive times for all UEs to mark the test case as passing. The gap analysis shall be provided for the measured and the expected target KPIs.
-
-- LTE Attach-Detach test case validations and KPI measurements
- - Validate successful attach of each UE 10 times with LTE cell (Refer to 3GPP TS 23.401 [29], Clause 5.3.2.1 E-UTRAN Initial Attach). In the UE logs or applications installed on UE, check that UE is attached to correct cell (example PCI, Global eNB ID, ARFCN as per test configuration)
- - Measure the attach success rate by validating attach request and attach complete for each iteration. Record the attach success rate in Table 5-4 for each UE.
- - Measure the attach latency by calculating the time between Attach Request to attach complete. Capture the latency for each iteration and sort the latency value observed for each iteration in ascending order. Record the Minimum, Average (Sum of all latency value/ Total Iterations, Total Iterations are 10 in this case) and Maximum latency value observed in Table 5-5 for each UE
- - Validate successful detach attach with LTE cell (Refer to 3GPP TS 23.401 [29], Clause 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN). Signalling connection release shall be validated from message flow (UE context release and RRC connection release messages). Measure the detach success rate by validating detach request and detach accept for each iteration. Record the detach success rate in Table 5-4
-- 5G NSA Attach-Detach test cases validations and KPI measurements
- - Validate successful multiple UE attach with 5G NSA cell (3GPP TS 23.401 [29], Clause 5.3.2.1 E-UTRAN Initial Attach and 3GPP TS 37.340 [30] Clause 10.2.1 EN-DC for Secondary Node Addition)). In the UE logs or applications installed on UE, check that UE is attached to correct cell (example PCI, Global eNB ID/Global gNB, ARFCN/NR-ARFCN as per test configuration for LTE /5G cells )
- - Measure the attach success rate by validating attach request and attach complete for each iteration. Also measure the secondary node addition success rate by validating the SgNB addition request and SgNB reconfiguration complete as per flow 3GPP 37.340 Clause 10.2.1 EN-DC for each iteration. Record the attach success rate and secondary node addition success rate in Table 5-4 for each UE
- - Validate successful detach attach (LTE Detach and 5G Secondary Node release) with 5G NSA cell (Refer to 3GPP TS 23.401 [29] Clause, 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN and 3GPP TS 37.340 [30] Clause 10.4.1 EN-DC for Secondary Node Release)). Signalling connection release shall be validated from the message flow (UE context release and RRC connection release messages). 5G secondary node shall also get released successfully. Measure the detach success rate by validating detach request and detach accept for each iteration. Record the detach success rate in Table 5-4 for each UE.
-
-**Table 5-4 KPI to be captured for multi-UE attach-detach test case**
-
-| LTE KPI | | 5G NSA KPI | | |
-|---------------------|---------------------|---------------------|---------------------|----------------------------|
-| Attach Success Rate | Detach Success Rate | Attach Success Rate | Detach Success Rate | SgNB addition Success rate |
-| | | | | |
-
-**Table 5-5 Latency KPI for multi-UE attach**
-
-| |
-|-------------------------------|
-| LTE Attach Time (millisecond) |
-|-------------------------------|
-
-| Minimum | Maximum | Average |
-|---------|---------|---------|
-| | | |
-
-## 5.3 5G SA registration and deregistration of single UE
-
-### 5.3.1 Test description and applicability
-
-The purpose of the test is to verify the full registration and deregistration procedure with a single UE. The test also verifies the PDU session establishment and release procedures.
-
-The test focuses on the procedure of 'Initial registration' as defined in 3GPP TS 23.502 [28] Clause 4.2.2.2.2.
-
-The test focuses on the procedure of 'UE-initiated deregistration' as defined in 3GPP TS 23.502 [28] Clause 4.2.2.3.2.
-
-This test also validates PDU session establishment and release procedures.
-
-The test validates the 3GPP standard registration/deregistration procedure and the latency of the procedure. Bi-directional data transmission shall be observed before the deregistration procedure to verify the stability of the network slice.
-
-### 5.3.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e. isolated cell without any inter-cell interference – see Clause 4.7) with a stationary UE (real or emulated) placed under excellent radio conditions as defined in Clause 4.6, using SS-RSRP as the metric. Within the cell there shall be only one active UE. The application server should be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with enough capacity so as not to limit the expected data throughput. The UE, RAN, and 5G Core shall support the network slicing, at least for one Single Network Slice Selection Assistance Information (S-NSSAI). The test is suitable for lab as well as field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The test environment should be setup to achieve excellent radio conditions (using SS-RSRP as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside an RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (SS-RSRP as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.6) should not be exceeded.
-
-Please refer to Figure 6-1 for E2E test setup for 5G SA.
-
-### 5.3.3 Test procedure
-
-Below are the test procedure steps
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) Power on the UE and the UE shall send REGISTRATION REQUEST message. UE shall successfully register to the 5G SA network.
-- 3) Full-buffer UDP bi-directional data transmission (see Clause 4.4) between the application server and UE is initiated.
-- 4) The registration procedure messages shall be captured, and the latency of the registration procedure shall be measured and recorded in Table 5-6. The duration of the test shall be at least 3 minutes when the throughput is stable. The PDU session establishment procedure messages shall also be captured and verified.
-
-- 5) Power off the UE and UE shall send DEREGISTRATION REQUEST message. UE shall successfully deregister from the 5G SA network.
-- 6) The deregistration procedure messages shall be captured, and the latency of deregistration procedure shall be measured and recorded in Table 5-6. The PDU session release procedure messages shall also be captured and verified.
-- 7) Repeat steps 2 to 6, for a total of 10 times and record the KPIs mentioned in Table 5-6.
-
-### 5.3.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- Latency KPI mentioned in Table 5-6
-
-Validate from collected logs registration (as per 3GPP TS 23.502 [28] Clause 4.2.2.2.2) and deregistration (as per 3GPP TS 23.502 [28] Clause 4.2.2.3.2) procedures and also validate 'UE Requested PDU Session Establishment for Non-roaming and Roaming with Local Breakout case' as defined in 3GPP TS 23.502 [28] Clause 4.3.2.2.1, and the procedure of 'PDU Session Release for UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout case' as defined in 3GPP TS 23.502 [28] Clause 4.3.4.2. The procedure shall pass 10 consecutive times to mark the test case as passing. The gap analysis shall be provided for the measured and the expected target KPIs.
-
-The Registration Time latency is measured by calculating the time between Registration Request to Registration Complete; The Deregistration Time latency is measured by calculating the time between Deregistration Request to Signaling Connection Release. Capture the latency for each iteration and sort the latency value observed for each iteration in ascending order. Record the Minimum, Average (Sum of all latency value/ Total Iterations, Total Iterations are 10 in this case) and Maximum latency value observed in Table 5-6.
-
-**Table 5-6 5G SA registration/deregistration latency KPI record table of single UE**
-
-| KPI | Repeat Times | | | | | | | | | | Calculation | | |
-|--------------------------------------------------|--------------|---|---|---|---|---|---|---|---|----|-------------|---------|---------|
-| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Minimum | Maximum | Average |
-| Registration Time (single slice) (millisecond) | | | | | | | | | | | | | |
-| Deregistration Time (single slice) (millisecond) | | | | | | | | | | | | | |
-
-## 5.4 Intra O-DU mobility
-
-### 5.4.1 Test description and applicability
-
-The purpose of the test is to verify intra O-CU, intra O-DU handover of a UE. The test validates the O-CU, O-DU, and O-RU functionality in handling inter-cell mobility when two O-RUs are connected to an O-DU. The test measures the DL / UL throughput variations, handover latency, handover interruption and packet loss during the mobility. Test scenarios are classified into two groups as Standalone (SA) and Non-Standalone (NSA).
-
-Intra O-DU mobility with SA shall follow 3GPP TS 38.401 [29], Clause 8.2.1 and 3GPP TS 38.473 [32], Clause 8.3.4 for the call flow. Intra O-DU mobility with NSA shall follow 3GPP TS 38.401 [29], Clause 8.2.1, 3GPP TS 38.473 [32], Clause 8.3.4 and 3GPP TS 37.340 [30] for the call flow.
-
-### 5.4.2 Test setup and configuration
-
-In NSA mode, the test setup consists of one 4G cell (MeNB) and two 5G cells (SgNB). Each 5G cell is associated with a single O-DU, connected to a single O-CU, refer to Figure 5-1 for the test setup topology. The test environment shall have a single UE with active data traffic. The application server should be placed as close as possible to the core and connected to the core via a transport link with enough capacity.
-
-
-
-Diagram of Intra O-DU mobility test bed for NSA mode of operation. It shows a UE moving between 5G Cell 1 and 5G Cell 2, which are connected to an O-RU. The O-RU is connected to an O-DU, which is connected to an O-CU. The O-CU is connected to an eNB (CU & DU) via an X2 interface. The eNB is connected to a 4G EPC via an S1 interface. The 4G EPC contains an MME and an SGW. The SGW is connected to an Application Server. The O-DU is also connected to a gNB O-CU via an F1 interface.
-
-**Figure 5-1 Intra O-DU mobility test bed for NSA mode of operation.**
-
-In SA, the test setup consists of two 5G cells, each one associated with the same O-DU and O-CU connected to a 5G core network (see Figure 5-2 for the test setup topology). The test environment shall have a single UE with active data traffic. The application server should be placed as close as possible to the core and connected to the core via a transport link with enough capacity.
-
-
-
-Figure 5-2: Intra O-DU mobility test bed for SA mode of operation. The diagram shows a gNB O-DU connected to a gNB O-CU via an F1 interface. The gNB O-CU is connected to a 5G CN (containing AMF and UPF) via an NG C/U interface. The 5G CN is connected to an Application Server. The gNB O-DU is connected to a gNB O-RU, which is shown as a radio tower. The gNB O-RU covers two cells, 5G Cell 1 and 5G Cell 2. A UE (User Equipment) is shown moving from 5G Cell 1 to 5G Cell 2, indicated by an arrow.
-
-**Figure 5-2 Intra O-DU mobility test bed for SA mode of operation.**
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio conditions of the UE are initially set to excellent using RSRP as the metric. The minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside and RF shielded box or RF shielded room if the UE is not connected via cable. The UE handover between the cells can be achieved by changing the radio signal strength of the source and target cells using variable attenuators.
-
-**Field setup:** The drive route with source and target cells should be defined. The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (using RSRP as the metric as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.5) should not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route from source cell to target cell.
-
-### 5.4.3 Test procedure
-
-Below are the NSA mode steps
-
-- 1) The 4G and 5G cell setups are configured following Clause 5.4.2.
-- 2) All the three cells are configured according to the test configuration. The cells are activated and unloaded.
-- 3) Both 5G cells are configured as neighbors to each other, so that the UE can trigger measurement events for handover.
-- 4) The source (cell 1) and target (cell 2) 5G cells for intra O-DU mobility shall be depicted as in Figure 5-1.
-- 5) The test UE is under source 5G cell coverage.
-- 6) Power on the UE and UE shall successfully complete the LTE attach followed by successful SgNB addition to source 5G cell.
-- 7) The full-buffer UDP bi-directional data transmission (see Clause 4.4) from the application server is initiated.
-- 8) The UE shall move from the source 5G cell to the target 5G cell to trigger a handover.
-
-Below are the SA Mode steps
-
-- 1) The 5G cell setup is configured following Clause 5.4.2.
-- 2) Configure two 5G cells within an O-DU according to the test configuration. The cells are activated and unloaded.
-- 3) Both 5G cells are configured as neighbors to each other, so that the UE can trigger measurement events for handover.
-- 4) The source and target 5G cells for intra O-DU mobility shall be depicted as in Figure 5-2.
-
-- 5) The test UE is under source cell coverage.
-- 6) Power on the UE and UE shall successfully register to source 5G cell.
-- 7) The full-buffer UDP bi-directional data transmission (see Clause 4.4) from the application server is initiated.
-- 8) The UE shall move from source cell to target cell to perform handover.
-
-### 5.4.4 Test requirements (expected results)
-
-The intra O-DU handover call flow shall be verified for both NSA and SA use cases. Following functionalities shall also be validated:
-
-- PDU Session is established when full-buffer bi-directional data transmission is initiated. (Only in SA Mode)
-- Handover is successful.
-
-In addition to the common minimum set of configuration parameters defined (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-SUT/Application server side:
-
-- Transmit downlink throughput measured at application server in time (average per second)
-- Received uplink throughput measured at application server in time (average per second)
-- Uplink packet loss percentage during handover.
-- Uplink BLER, MCS, MIMO rank (RI) on PUSCH in time (average per second)
-
-UE side:
-
-- Radio parameters such as RSRP, RSRQ, SINR on PDSCH in time (average per second)
-- Downlink BLER, MCS, MIMO rank (RI) on PDSCH in time (average per second).
-- Received Downlink throughput (L1 and L3 PDCP layers) in time (average per second).
-- Downlink packet loss percentage during handover
-- Uplink throughput (L1 and L3 PDCP layers) in time (average per second)
-- Channel utilization, i.e. Number allocated/occupied downlink and uplink RBs in time (per TTI/average per second) and Number of allocated/occupied slots in time.
-- KPIs related to Handover failure, Call drop, Handover latency, Handover interruption time.
-
-## 5.5 Inter O-DU mobility
-
-### 5.5.1 Test description and applicability
-
-The purpose of the test is to verify intra O-CU, inter O-DU handover of a UE. The test validates the O-CU, O-DU functionality in handling Inter O-DU handover. The test measures the DL / UL throughput variations, handover latency, handover interruption and packet loss during the handover procedure. Test scenarios are classified into two groups as SA (Standalone) and NSA (Non-Standalone).
-
-Inter O-DU mobility with SA shall follow 3GPP TS 38.401 [31], Clause 8.2.1 and Inter O-DU mobility with NSA shall follow 3GPP TS 38.401[31], Clause 8.2.2 for the call flow.
-
-3GPP 38.401 v15.7.0 has introduced a new CR 0104, which has modified the initial part of call flow for Clause 8.2.2. The ORAN system supporting 3GPP specification later than v15.7.0 shall follow Clause 8.2.2 of 3GPP TS 38.401 v15.7.0 or later to verify the inter O-DU handover.
-
-### 5.5.2 Test setup and configuration
-
-In Non-Standalone Mode, the test setup consists of one 4G Cell (MeNB) and two 5G cells (SgNB). Each 5G Cell is associated with different O-DUs, connected to the same O-CU. The test environment shall have a single UE with active data traffic. The application server should be placed as close as possible to the core and connected to the core via a transport link with enough capacity.
-
-
-
-Diagram of Inter O-DU mobility test bed for NSA mode of operation. It shows a 4G eNB (CU & DU) connected to a 4G EPC (MME, SGW) and an Application Server. The eNB is connected to two 5G gNB O-RUs via X2 interfaces. Each gNB O-RU is connected to its own gNB O-DU via F1 interfaces. Both gNB O-DUs are connected to a single gNB O-CU. The gNB O-CU is connected to the 4G EPC via an S1 interface. A UE is shown moving from one gNB O-RU to another.
-
-Figure 5-3 Inter O-DU mobility test bed for NSA mode of operation.
-
-In standalone Mode, the test setup consists of two 5G cells, each one associated with a different O-DU, connected to the same O-CU. The test environment shall have a single UE with active data traffic. The application server should be placed as close as possible to the core and connected to the core via a transport link with enough capacity.
-
-
-
-Diagram of Inter O-DU mobility test bed for SA mode of operation. It shows two gNB O-RUs connected to their respective gNB O-DUs via F1 interfaces. Both gNB O-DUs are connected to a single gNB O-CU. The gNB O-CU is connected to a 5G CN (AMF, UPF) via an NG C/U interface. The 5G CN is connected to an Application Server. A UE is shown moving from one gNB O-RU to another.
-
-Figure 5-4 Inter O-DU mobility test bed for SA mode of operation
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio
-
-conditions of UE are initially set to excellent. The minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside RF shielded box or RF shielded room if the UE is not connected via cable. The UE handover between the cells can be achieved by changing radio signal strength of source and target cells using variable attenuators.
-
-**Field setup:** The drive route with source and target cells should be defined. The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRP as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.5) should not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route from source cell to target cell.
-
-### 5.5.3 Test procedure
-
-In Non-Standalone Mode
-
-- 1) The 4G and 5G cell setups are configured following Clause 5.5.2.
-- 2) All the three cells are configured according to the test configuration. The cells are activated and unloaded.
-- 3) Both 5G cells are configured neighbors to each other, so that UE can trigger measurement events for handover.
-- 4) The test UE is under source O-DU cell coverage.
-- 5) Power on the UE and the UE shall successfully complete the LTE attach followed by successful SgNB addition to source O-DU.
-- 6) The full-buffer UDP data transmission (see Clause 4.4) from the application server is initiated.
-- 7) The UE shall move from source O-DU to target O-DU to perform handover.
-
-In Standalone Mode
-
-- 1) The 5G cell setup is configured following Clause 5.5.2.
-- 2) All the 5G cells are configured according to the test configuration. The cells are activated and unloaded.
-- 3) Both 5G cells are configured neighbors to each other, so that UE can trigger measurement events for handover.
-- 4) The test UE is under source O-DU cell coverage.
-- 5) Power on the UE and the UE shall successfully register to source O-DU cell.
-- 6) The full-buffer UDP data transmission (see Clause 4.4) from the application server is initiated.
-- 7) The UE shall move from source O-DU to target O-DU to perform handover.
-
-### 5.5.4 Test requirements (expected results)
-
-The inter O-DU handover call flow shall be verified for both NSA and SA use cases. Following functionalities shall also be validated:
-
-- PDU Session is established when full-buffer bi-directional data transmission is initiated. (Only in SA Mode)
-- Handover is successful.
-
-In addition to the common minimum set of configuration parameters defined (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-SUT/Application server side:
-
-- Transmit downlink throughput measured at application server in time (average per second)
-- Received uplink throughput measured at application server in time (average per second)
-
-- Uplink packet loss percentage during handover.
-- Uplink BLER, MCS, MIMO rank (RI) on PUSCH in time (average per second)
-
-UE side:
-
-- Radio parameters such as RSRP, RSRQ, SINR on PDSCH in time (average per second)
-- Downlink BLER, MCS, MIMO rank (RI) on PDSCH in time (average per second).
-- Received Downlink throughput (L1 and L3 PDCP layers) in time (average per second).
-- Downlink packet loss percentage during handover
-- Uplink throughput (L1 and L3 PDCP layers) in time (average per second)
-- Channel utilization, i.e. Number allocated/occupied downlink and uplink RBs in time (per TTI/average per second) and Number of allocated/occupied slots in time.
-- KPIs related to Handover failure, Call drop, Handover latency, Handover interruption time.
-
-## 5.6 Inter O-CU mobility
-
-### 5.6.1 Test description and applicability
-
-The purpose of the test is to verify inter O-CU handover of the UE. The test validates the O-CU, O-DU functionality in handling inter O-CU mobility connected to same 5G Core Network (in SA) or Master eNB (in NSA). The test measures the DL / UL throughput variations, handover latency, handover interruption and packet loss during the mobility. Test scenarios are classified into two groups as Standalone (SA) and Non-Standalone (NSA).
-
-Inter O-CU mobility with SA- Xn based Handover call flow shall follow 3GPP TS 38.401 [31], Clause 8.9.4 and Clause 8.9.5. Inter O-CU mobility with NSA shall follow 3GPP TS 37.340 [30], Clause 10.5.1 for the call flow.
-
-### 5.6.2 Test setup and configuration
-
-In non-standalone mode, the test setup consists of a 4G cell (MeNB) and two 5G cells (SgNB), each 5G cell is associated with a different O-DU and O-CU connected to the same 4G core network, refer to Figure 5-5 for the test setup topology. The test environment shall have single UE with active data traffic. The application server should be placed as close as possible to the core and connected to the core via a transport link with enough capacity.
-
-
-
-```
-
-graph TD
- UE[UE] --> gNB_O_RU1[gNB O-RU]
- gNB_O_RU1 --> MeNB[MeNB CU & DU]
- gNB_O_RU2[gNB O-RU] --> MeNB
- MeNB -- X2 --> gNB_O_CU1[gNB O-CU]
- MeNB -- X2 --> gNB_O_CU2[gNB O-CU]
- gNB_O_CU1 -- F1 --> gNB_O_DU1[gNB O-DU]
- gNB_O_CU2 -- F1 --> gNB_O_DU2[gNB O-DU]
- gNB_O_CU1 -- S1 --> MME[MME]
- gNB_O_CU2 -- S1 --> MME
- MME --> SGW[SGW]
- SGW --> AppServer[Application Server]
- subgraph 4G_EPC [4G EPC]
- MME
- SGW
- end
- subgraph NSA_Environment [NSA Environment]
- gNB_O_RU1
- gNB_O_RU2
- UE
- end
-
-```
-
-Diagram of the test setup for NSA mode of operation. It shows a UE moving between two gNB O-RUs connected to a central MeNB (CU & DU). The MeNB is connected to a 4G EPC (MME and SGW), which is further connected to an Application Server. Two gNB O-CUs are shown, each connected to an O-DU and to the MeNB via X2 interfaces. The O-CUs are also connected to the 4G EPC via S1 interfaces.
-
-Figure 5-5 Inter O-CU mobility test bed for NSA mode of operation
-
-In standalone mode, the test setup consists of two 5G cells, each one associated with a different O-DU and O-CU connected to same 5G Core network (see Figure 5-6 for the test setup topology). The test environment shall have a single UE with active data traffic. The application server should be placed as close as possible to the core and connected to the core via a transport link with enough capacity.
-
-
-
-Figure 5-6: Inter O-CU mobility test bed for SA mode of operation. The diagram shows two gNB O-DUs connected to two separate gNB O-CUs via F1 interfaces. Both gNB O-CUs are connected to a 5G Core Network (5G CN) via NG C/U interfaces. The 5G CN contains an AMF and a UPF. An Application Server is connected to the UPF. Two gNB O-RUs are shown, each connected to one of the gNB O-DUs. A UE is shown moving between the two gNB O-RUs, indicated by a double-headed arrow. An Xn interface is shown between the two gNB O-CUs.
-
-**Figure 5-6 Inter O-CU mobility test bed for SA mode of operation.**
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio conditions of UE are initially set to excellent. The minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside RF shielded box or RF shielded room if the UE is not connected via cable. The UE handover between the cells can be achieved by changing radio signal strength of source and target cells using variable attenuators.
-
-**Field setup:** The drive route with source and target cells should be defined. The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRP as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.5) should not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route from source cell to target cell.
-
-### 5.6.3 Test procedure
-
-In Non-Standalone Mode
-
-- 1) The 4G and 5G cell setups are configured following Clause 5.6.2.
-- 2) Configure two 5G cells connected to different O-DU and O-CU according to the test configuration. The cells are activated and unloaded.
-- 3) 5G cells are configured as neighbors to 4G cell, so that UE can trigger measurement events for mobility.
-- 4) The source cell (source O-DU and source O-CU) is the cell where UE is initially placed as depicted in Figure 5-5.
-- 5) Power on the UE and the UE shall successfully complete the LTE attach followed by successful SgNB addition to source 5G cell.
-- 6) The full-buffer UDP bi-directional data transmission (see Clause 4.4) from the application server is initiated.
-
-- 7) The UE shall move from source 5G cell to target 5G cell.
-
-#### In Standalone Mode
-
-- 1) The 5G cell setup is configured following Clause 5.6.2.
-- 2) Configure two 5G cells connected to different O-DU and O-CU according to the test configuration. The cells are activated and unloaded.
-- 3) Both 5G cells are configured neighbors to each other, so that UE can trigger measurement events for handover.
-- 4) The source cell (source O-DU and source O-CU) is the cell where UE is initially placed as depicted in Figure 5-6.
-- 5) Power on the UE and UE shall successfully register to source 5G cell.
-- 6) The full-buffer UDP bi-directional data transmission (see Clause 4.4) from the application server is initiated.
-- 7) The UE shall move from source cell to target cell to perform handover.
-
-### 5.6.4 Test requirements (expected results)
-
-The inter O-CU handover call flow shall be verified for NSA use case. Following functionalities shall also be validated:
-
-- PDU Session is established when full-buffer bi-directional data transmission is initiated. (Only in SA Mode)
-- Handover is successful.
-
-In addition to the common minimum set of configuration parameters defined (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment
-
-#### UE side:
-
-- Radio parameters such as RSRP, RSRQ, SINR on PDSCH in time (average per second)
-- Downlink BLER, MCS, MIMO rank (RI) on PDSCH in time (average per second).
-- Received Downlink throughput (L1 and L3 PDCP layers) in time (average per second).
-- Downlink packet loss percentage during handover
-- Uplink throughput (L1 and L3 PDCP layers) in time (average per second)
-- Channel utilization, i.e. Number allocated/occupied downlink and uplink RBs in time (per TTI/average per second) and Number of allocated/occupied slots in time.
-- KPIs related to Handover failure, Call drop, Handover latency, Handover interruption time.
-
-#### SUT/Application server side:
-
-- Transmit downlink throughput measured at application server in time (average per second)
-- Received uplink throughput measured at application server in time (average per second)
-- Uplink packet loss percentage during handover.
-- Uplink BLER, MCS, MIMO rank (RI) on PUSCH in time (average per second)
-
-## 5.7 Registration and deregistration to a single network slice
-
-### 5.7.1 Test description and applicability
-
-The purpose of the test is to verify the full procedure of the registration and deregistration to the single eMBB network slice in the 5G SA network.
-
-The test focuses on the procedure of 'Initial registration' as defined in 3GPP 23.502 Clause 4.2.2.2.2, with a single eMBB network slice. The network slice information (i.e., Network Slice Selection Assistance Information, NSSAI) defined in Table 5-7 shall be verified within the 3GPP standard registration procedure.
-
-The test focuses on the procedure of 'UE-initiated deregistration' as defined in 3GPP 23.502 Clause 4.2.2.3.2, with a single eMBB network slice. Even though the network slice information is not included in the deregistration procedure, the mandatory IEs defined in Table 5-7 shall be verified within the 3GPP standard deregistration procedure.
-
-The granularity of slice awareness is in PDU session level, so this test also verifies the PDU session establishment and release procedures.
-
-The test measures not only the 3GPP standard registration/deregistration procedure but also the latency of the procedure. The bi-directional data transmission shall be involved before the deregistration procedure to verify the stability of the network slice.
-
-### 5.7.2 Test setup and configuration
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The minimum attenuation of radio signal should be set to achieve the excellent radio conditions (RSRQ as defined in Clause 4.6), but the minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRQ as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.6) should not be exceeded.
-
-Please refer to Figure 5-2 for E2E test setup for 5G SA.
-
-### 5.7.3 Test procedure
-
-Below are the test procedure steps
-
-- 1) The NR cells shall be configured in the initial conditions defined in Session 5.7.2.
-- 2) Only one eMBB S-NSSAI (i.e., Slice/Service Type (SST) = 0x01) under the NSSAI shall be configured in UE, RAN, and 5G Core.
-- 3) Power on the UE and UE shall send REGISTRATION REQUEST message. The only one requested S-NSSAI shall be included in the message with the configured value in step 2. And UE shall successfully register to the 5G SA network.
-- 4) The full-buffer UDP bi-directional data transmission (see Clause 4.4) between UE and the application server is initiated.
-- 5) The registration procedure messages shall be captured to verify the mandatory IEs defined in Table 5-7, and the latency of registration procedure shall be measured and recorded in Table 5-9. The duration of the test should be at least 3 minutes when the throughput is stable. The PDU session establishment procedure messages shall also be captured and verified.
-- 6) Power off the UE and UE shall send DEREGISTRATION REQUEST message. And UE shall successfully de-register from the 5G SA network.
-
-- 7) The deregistration procedure messages shall be captured to verify the mandatory IEs defined in Table 5-8, and the latency of deregistration procedure shall be measured and recorded in Table 5-9. The PDU session release procedure messages shall also be captured and verified.
-- 8) Repeat steps 3 to 7, 10 times and record the KPI mentioned in Table 5-9.
-
-### 5.7.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- Mandatory IEs mentioned in Table 5-7, and Table 5-8
-- Latency KPI mentioned in Table 5-9
-
-Validate from collected logs registration (as per 3GPP 23.502 Clause 4.2.2.2.2) and deregistration (as per 3GPP 23.502 Clause 4.2.2.3.2) procedure and also validate ‘UE Requested PDU Session Establishment for Non-roaming and Roaming with Local Breakout case’ as defined in 3GPP 23.502 Clause 4.3.2.2.1, and the procedure of ‘PDU Session Release for UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout case’ as defined in 3GPP 23.502 Clause 4.3.4.2.
-
-Table 5-7 defines the verification steps along with validation of mandatory IEs for 5G SA registration procedure in single eMBB network slice.
-
-**Table 5-7 5G SA Registration verification with mandatory IEs in single eMBB network slice**
-
-| St. | Procedure | Msg Flow | Expected Output |
-|-----|-------------------------------|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 1 | RRCSetupComplete | UE → SUT | Verify that UE sends only one S-NSSAI in IE s-nssai-List and SST = ‘0x01’ in the S-NSSAI to SUT. |
-| 2 | Registration Request | UE → AMF | Verify that UE sends only one S-NSSAI in IE Requested NSSAI to 5G AMF, and IE 5GS registration type = ‘initial registration’, SST = ‘0x01’ in the S-NSSAI. |
-| 3 | Initial Context Setup Request | AMF → SUT | Verify that 5G AMF sends only one S-NSSAI in IE Allowed NSSAI and S-NSSAI (under parent IE PDU Session Resource Setup Request Item ) to SUT, and SST = ‘0x01’ in the S-NSSAI. |
-| 4 | Registration Accept | AMF → UE | Verify that 5G AMF sends only one S-NSSAI in IE Allowed NSSAI and Configured NSSAI to UE, SST = ‘0x01’ in the S-NSSAI and IE Rejected NSSAI shall not exist. |
-
-Table 5-8 defines the verification steps along with validation of mandatory IEs for 5G SA deregistration procedure in single eMBB network slice.
-
-**Table 5-8 5G SA Deregistration verification with mandatory IEs in single eMBB network slice**
-
-| St. | Procedure | Msg Flow | Expected Output |
-|-----|------------------------|----------|------------------------------------------------------------------------------|
-| 1 | Deregistration Request | UE → AMF | Verify that UE sends IE Deregistration type = 'Switch Off' to 5G AMF. |
-
-Table 5-9 defines the KPI record table of registration/ registration testing in single eMBB network slice.
-
-**Table 5-9 Single eMBB Network Slice KPI record table**
-
-| KPI | Repeat Times | | | | | | | | | | Calculation | | |
-|--------------------------------------------------|--------------|---|---|---|---|---|---|---|---|----|-------------|---------|---------|
-| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Minimum | Maximum | Average |
-| Registration Time (single slice) (millisecond) | | | | | | | | | | | | | |
-| Deregistration Time (single slice) (millisecond) | | | | | | | | | | | | | |
-
-## 5.8 Registration and deregistration to multiple network slices
-
-### 5.8.1 Test description and applicability
-
-The purpose of the test is to verify the full procedure of the registration and deregistration to multiple network slices (i.e., eMBB, URRLC, MIoT, V2X) in the 5G SA network.
-
-The test focuses on the procedure of 'Initial registration' as defined in 3GPP 23.502 Clause 4.2.2.2.2, with multiple network slices. The network slice information (i.e., Network Slice Selection Assistance Information, NSSAI) defined in Table 5-10 shall be verified within the 3GPP standard registration procedure.
-
-The test focuses on the procedure of 'UE-initiated deregistration' as defined in 3GPP 23.502 Clause 4.2.2.3.2, with multiple network slices. Even though the network slice information is not included in the deregistration procedure, and also the mandatory IEs defined in Table 5-11 shall be verified within the 3GPP standard deregistration procedure.
-
-The granularity of slice awareness is in PDU session level, so this test also verifies the PDU session establishment and release procedures.
-
-The test measures not only the 3GPP standard registration/deregistration procedure but also the latency of the procedure. The bi-directional data transmission shall be involved before the deregistration procedure to verify the stability of the network slice.
-
-### 5.8.2 Test setup and configuration
-
-The network setup is single cell scenario (i.e. isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated UE) placed in the excellent radio conditions as defined in Clause 4.6 – RSRQ should be considered in case of downlink. Within the cell there should be only one active UE. The application server(s) should be placed as close as possible to the core/core emulator and connected to the core/core emulator via transport link with enough capacity not limiting the expected data throughput. The test is suitable for lab as well as field environment. The UE, RAN, and 5G Core shall support the multiple Network Slice Selection Assistance Information (S-NSSAI). At least two network slices of eMBB, URRLC, MIoT, V2X shall be covered for this test. The test is suitable for lab as well as field environment.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The minimum attenuation of radio signal should be set to achieve the excellent radio conditions (RSRQ as defined in Clause 4.6), but the minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRQ as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.6) should not be exceeded.
-
-Please refer to Figure 5-2 in section 5.4.2, for E2E test setup for 5G SA.
-
-### 5.8.3 Test procedure
-
-Below are the test procedure steps
-
-- 1) The NR cells shall be configured in the initial conditions defined in Session 5.8.2.
-- 2) Multiple S-NSSAI (i.e., Slice/Service Type (SST) = 0x01/0x02/0x03/0x04) under the NSSAI shall be configured in UE, RAN, and 5G Core.
-- 3) Power on the UE and UE shall send REGISTRATION REQUEST message. The multiple requested S-NSSAI shall be included in the message with the configured value in step 2. And UE shall successfully register to the 5G SA network.
-- 4) The full-buffer UDP bi-directional data transmission (see Clause 4.4) between UE and the application server is initiated in eMBB network slice if eMBB network slice is covered.
-- 5) The full-buffer UDP bi-directional data transmission (see Clause 4.4) between UE and the application server is initiated in URRLC network slice if URRLC network slice is covered.
-- 6) The full-buffer UDP bi-directional data transmission (see Clause 4.4) between UE and the application server is initiated in mIoT network slice if mIoT network slice is covered.
-- 7) The full-buffer UDP bi-directional data transmission (see Clause 4.4) between UE and the application server is initiated in V2X network slice if V2X network slice is covered.
-- 8) The registration procedure messages shall be captured to verify the mandatory IEs defined in Table 5-10, and the latency of registration procedure shall be measured and recorded in Table 5-12. The duration of the test should be at least 3 minutes when the throughput is stable. The PDU session establishment procedure messages shall also be captured and verified for the network slices of eMBB/URRLC/MIoT/ V2X.
-- 9) Power off the UE and UE shall send DEREGISTRATION REQUEST message. And UE shall successfully de-register from the 5G SA network.
-- 10) The deregistration procedure messages shall be captured to verify the mandatory IEs defined in Table 5-11, and the latency of deregistration procedure shall be measured and recorded in Table 5-12. The PDU session release procedure messages shall also be captured and verified for the network slices of eMBB/URRLC/MIoT/ V2X.
-- 11) Repeat steps 3 to 10, 10 times and record the KPI mentioned in Table 5-12.
-
-### 5.8.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- Mandatory IEs mentioned in Table 5-10, and Table 5-11
-
-- Latency KPI mentioned in Table 5-12
-
-Validate from collected logs registration (as per 3GPP 23.502 Clause 4.2.2.2.2) and deregistration (as per 3GPP 23.502 Clause 4.2.2.3.2) procedure and also validate ‘UE Requested PDU Session Establishment for Non-roaming and Roaming with Local Breakout case’ as defined in 3GPP 23.502 Clause 4.3.2.2.1 for multiple network slices of eMBB/URRLC/MIoT/ V2X, and the procedure of ‘PDU Session Release for UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout case’ as defined in 3GPP 23.502 Clause 4.3.4.2 for multiple network slices of eMBB/URRLC/MIoT/ V2X.
-
-Table 5-10 defines the verification steps along with validation of mandatory IEs for 5G SA registration procedure in multiple network slices.
-
-**Table 5-10: 5G SA Registration verification with mandatory IEs in multiple network slices**
-
-| St. | Procedure | Msg Flow | Expected Output |
-|-----|-------------------------------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 1 | RRCEstablishmentComplete | UE → SUT | Verify that UE sends multiple S-NSSAI in IE s-nssai-List and SST = ‘0x01/0x02/0x03/0x04’ in the S-NSSAI to SUT. |
-| 2 | Registration Request | UE → AMF | Verify that UE sends multiple S-NSSAI in IE Requested NSSAI to 5G AMF, and IE 5GS registration type = ‘initial registration’, SST = ‘0x01/0x02/0x03/0x04’ in the S-NSSAI. |
-| 3 | Initial Context Setup Request | AMF → SUT | Verify that 5G AMF sends multiple S-NSSAI in IE Allowed NSSAI and S-NSSAI (under parent IE PDU Session Resource Setup Request Item ) to SUT, and SST = ‘0x01/0x02/0x03/0x04’ in the S-NSSAI. |
-| 4 | Registration Accept | AMF → UE | Verify that 5G AMF sends multiple S-NSSAI in IE Allowed NSSAI and Configured NSSAI to UE, SST = ‘0x01/0x02/0x03/0x04’ in the S-NSSAI and IE Rejected NSSAI shall not exist. |
-
-Table 5-11 defines the verification steps along with validation of mandatory IEs for 5G SA deregistration procedure in multiple network slices.
-
-**Table 5-11: 5G SA Deregistration verification with mandatory IEs in multiple network slices**
-
-| St. | Procedure | Msg Flow | Expected Output |
-|-----|------------------------|----------|------------------------------------------------------------------------------|
-| 1 | Deregistration Request | UE → AMF | Verify that UE sends IE Deregistration type = ‘Switch Off’ to 5G AMF. |
-
-Table 5-12 defines the KPI record table of registration/ registration testing in multiple network slices.
-
-**Table 5-12: Multiple Network Slices KPI record table**
-
-| KPI | Repeat Times | | | | | | | | | | Calculation | | |
-|-----------------------------------------------------|--------------|---|---|---|---|---|---|---|---|----|-------------|---------|---------|
-| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Minimum | Maximum | Average |
-| Registration Time (multiple slices) (millisecond) | | | | | | | | | | | | | |
-| Deregistration Time (multiple slices) (millisecond) | | | | | | | | | | | | | |
-
-## 5.9 Idle Mode Intra O-DU mobility
-
-### 5.9.1 Test description and applicability
-
-The purpose of the test is to verify O-CU, idle mode intra O-DU mobility of a UE. The test validates the O-CU, O-DU, O-RU functionality in handling inter-cell mobility when two O-RU connected to an O-DU. Test scenarios are classified into two groups as Standalone (SA) Intra-frequency cell reselection and as Standalone (SA) Inter-frequency cell reselection.
-
-Idle mode Intra O-DU mobility shall follow 3GPP 38.133, Clause 4.2.2.3 and Clause 4.2.2.4 for intra-frequency and inter-frequency cell selection measurement, respectively. And 3GPP 38.304, Clause 5.2.2 for the state transition.
-
-### 5.9.2 Test setup and configuration
-
-In SA, the test setup consists of two 5G cells, each one associated with same O-DU and O-CU connected to 5G Core network, refer Figure 5-7 for the test setup topology. The test environment shall have single UE in Idle mode.
-
-
-
-Figure 5-7: Idle Mode Intra O-DU mobility test bed for SA mode of operation. The diagram shows a UE moving between two cells, 5G Cell 1 and 5G Cell 2, which are part of a gNB O-RU. The gNB O-RU is connected to a gNB O-DU via an F1 interface. The gNB O-DU is connected to a gNB O-CU via an NG C/U interface. The gNB O-CU is connected to a 5G CN (Core Network) which contains an AMF and a UPF. The UPF is connected to an Application Server.
-
-**Figure 5-7 Idle Mode Intra O-DU mobility test bed for SA mode of operation.**
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The radio conditions of UE are initially set to excellent. The minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside RF shielded box or RF shielded room if the UE is not connected via cable. The UE mobility between the cells can be achieved by changing radio signal strength of source and target cells using variable attenuators.
-
-**Field setup:** The drive route with source and target cells should be defined. The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRP as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.5) should not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route from source cell to target cell.
-
-### 5.9.3 Test procedure
-
-Below are the SA Mode Intra-frequency steps
-
-- 1) The 5G cell setup is configured following Clause 5.9.2.
-- 2) Configure two 5G cells (cell 1 and cell 2) of same frequency within an O-DU according to the test configuration. The cells are activated and unloaded.
-- 3) Both 5G Cells are configured neighbours to each other, so that UE can use it for cell re-selection.
-- 4) The source and target 5G cells for intra O-DU mobility shall be depicted as in Figure 5-7.
-- 5) The test UE is under source cell coverage.
-- 6) Power on the UE and UE shall successfully register to source 5G cell.
-- 7) Wait till the UE goes in idle mode as per UE inactivity timer and then move the UE from source cell to target cell.
-- 8) Once UE moves to new cell, make an MO data call.
-- 9) Repeat the above test steps for 10 iterations.
-
-Below is the SA Mode Inter-frequency steps
-
-- 1) The 5G cell setup is configured following Clause 5.9.2.
-- 2) Configure two 5G cells (cell 1 and cell 2) on different frequencies within an O-DU according to the test configuration. The cells are activated and unloaded.
-- 3) Both 5G Cells are configured neighbours to each other, so that UE can use it for cell re-selection.
-- 4) The source and target 5G cells for intra O-DU mobility shall be depicted as in Figure 5-7.
-- 5) The test UE is under source cell coverage.
-- 6) Power on the UE and UE shall successfully register to source 5G cell.
-- 7) Wait till the UE goes in idle mode as per UE inactivity timer and then move the UE from source cell to target cell, move the UE from source cell to target cell.
-- 8) Once UE moves to new cell, make an MO data call.
-- 9) Repeat the above test steps for 10 iterations.
-
-### 5.9.4 Test requirements (expected results)
-
-The Idle mode intra O-DU cell reselection shall be verified for both intra-frequency and inter-frequency. Also verify call setup latency on a target cell with reference to RRC connection call flow defined in 3GPP 38.133, Clause 5.3.3.1. Following functionalities are also validated to declare the verdict.
-
-- Cell re-selection is successful on target cell.
-- RRC connection establishment is successful on a target cell.
-
-In addition to the common minimum set of configuration parameters defined (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-SUT side:
-
-- Idle mode mobility time from UE, in idle mode at source to UE in idle mode to target.
-
-UE side:
-
-- Radio parameters such as RSRP, RSRQ.
-- KPI's related to Cell re-selection failure, idle mode mobility time from UE in idle mode at source to UE in idle mode to target.
-
-The cell re-selection failure can be found out by checking if the cell re-selection is successful or not. The Idle to Connected on a target cell Time latency is measured by calculating the time between RRC\_Idle mode to RRC\_Connected state when UE moves to new cell after initiating an MO call. Capture the cell re-selection success/failure and latency for each iteration and sort the latency value observed for each iteration in ascending order. Record the Minimum, Average (Sum of all latency value/ Total Iterations, Total Iterations are 10 in this case) and Maximum latency value observed in below tables:
-
-**Table 5-13 5G Cell Re-selection Success and Failure KPI**
-
-| KPI | Repeat Times | | | | | | | | | |
-|---------------------------|--------------|---|---|---|---|---|---|---|---|----|
-| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
-| Cell Re-selection Success | | | | | | | | | | |
-| Cell Re-selection Failure | | | | | | | | | | |
-
-## 5.10 Idle mode Inter O-DU mobility
-
-### 5.10.1 Test description and applicability
-
-The purpose of the test is to verify intra O-CU, idle mode inter O-DU mobility of a UE. The test validates the O-CU, O-DU, O-RU functionality in handling inter-cell mobility. Test scenarios are classified into two groups as Standalone (SA) Intra-frequency cell reselection and as Standalone (SA) Inter-frequency cell reselection.
-
-Idle mode Inter O-DU mobility shall follow 3GPP 38.133, Clause 4.2.2.3 and Clause 4.2.2.4 for intra-frequency and inter-frequency cell selection measurement, respectively. And 3GPP 38.304, Clause 5.2.2 for the state transition.
-
-### 5.10.2 Test setup and configuration
-
-In standalone Mode, the test setup consists of two 5G cells, each one associated with different O-DU, connected to same O-CU. The test environment shall have single UE in Idle mode.
-
-
-
-Diagram of Inter O-DU mobility test bed for SA mode of operation. It shows two gNB O-DUs connected to a central gNB O-CU via F1 interfaces. The gNB O-CU is connected to a 5G CN (containing AMF and UPF) via an NG CU interface. The 5G CN is also connected to an Application Server. Two gNB O-RUs are shown, each connected to one of the gNB O-DUs. A UE is shown moving between the coverage areas of the two gNB O-RUs.
-
-**Figure 5-8 Inter O-DU mobility test bed for SA mode of operation**
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The radio conditions of UE are initially set to excellent. The minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside RF shielded box or RF shielded room if the UE is not connected via cable. The UE mobility between the cells can be achieved by changing radio signal strength of source and target cells using variable attenuators.
-
-**Field setup:** The drive route with source and target cells should be defined. The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRP as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.5) should not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route from source cell to target cell.
-
-### 5.10.3 Test procedure
-
-Below are the SA Mode Intra-frequency steps
-
-- 1) The 5G cell setup is configured following Clause 5.10.2.
-- 2) All the 5G cells are configured according to the test configuration. The cells are activated and unloaded
-- 3) Both 5G Cells are configured neighbours to each other, so that UE can use it for cell re-selection.
-- 4) The source and target 5G cells for inter O-DU mobility shall be depicted as in Figure 5-8.
-- 5) The test UE is under source cell coverage.
-- 6) Power on the UE and UE shall successfully register to source 5G cell.
-- 7) Wait till the UE goes in idle mode as per UE inactivity timer and then move the UE from source cell to target cell.
-- 8) Once UE moves to new cell, make an MO data call.
-- 9) Repeat the above test steps for 10 iterations.
-
-Below is the SA Mode Inter-frequency steps
-
-- 1) The 5G cell setup is configured following Clause 5.10.2.
-- 2) All the 5G cells are configured according to the test configuration. The cells are activated and unloaded.
-
-- 3) Both 5G Cells are configured neighbours to each other, so that UE can use it for cell re-selection.
-- 4) The source and target 5G cells for inter O-DU mobility shall be depicted as in Figure 5-8.
-- 5) The test UE is under source cell coverage.
-- 6) Power on the UE and UE shall successfully register to source 5G cell.
-- 7) Wait till the UE goes in idle mode as per UE inactivity timer and then move the UE from source cell to target cell.
-- 8) Once UE moves to new cell, make an MO data call.
-- 9) Repeat the above test steps for 10 iterations.
-
-### 5.10.4 Test requirements (expected results)
-
-The Idle mode inter O-DU cell reselection shall be verified for both intra-frequency and inter-frequency. Also verify call setup latency on a target cell with reference to RRC connection call flow mentioned in 3GPP 38.133, Clause 5.3.3.1. Following functionalities are also validated to declare the verdict.
-
-- RRC connection establishment is complete.
-- Cell re-selection is successful.
-
-In addition to the common minimum set of configuration parameters defined (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-SUT side:
-
-- Idle mode mobility time from UE, in idle mode at source to UE in idle mode to target.
-
-UE side:
-
-- Radio parameters such as RSRP and RSRQ (average per second)
-- KPI's related to Cell re-selection failure, Idle mode mobility time from UE, in idle mode at source to UE in idle mode to target
-
-The cell re-selection failure can be found out by checking if the cell re-selection is successful or not. The Idle to Connected on a target cell Time latency is measured by calculating the time between RRC\_Idle mode to RRC\_Connected state when UE moves to new cell after initiating an MO call. Capture the cell re-selection success/failure and latency for each iteration and sort the latency value observed for each iteration in ascending order. Record the Minimum, Average (Sum of all latency value/ Total Iterations, Total Iterations are 10 in this case) and Maximum latency value observed in below tables:
-
-**Table 5-14 5G Cell Re-selection Success and Failure KPI**
-
-| KPI | Repeat Times | | | | | | | | | |
-|---------------------------|--------------|---|---|---|---|---|---|---|---|----|
-| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
-| Cell Re-selection Success | | | | | | | | | | |
-| Cell Re-selection Failure | | | | | | | | | | |
-
-## 5.11 Idle mode Inter O-CU mobility
-
-### 5.11.1 Test description and applicability
-
-The purpose of the test is to verify inter O-CU mobility of the UE. The test validates the O-CU, O-DU functionality in handling inter O-CU mobility connected to same 5G Core Network (in SA). The test validates the O-CU, O-DU, O-RU functionality in handling inter-cell mobility. Test scenarios are classified into two groups as Standalone (SA) Intra-frequency cell reselection and as Standalone (SA) Inter-frequency cell reselection.
-
-Idle mode Inter O-CU mobility shall follow 3GPP 38.133, Clause 4.2.2.3 and Clause 4.2.2.4 for intra-frequency and inter-frequency cell selection measurement, respectively. And 3GPP 38.304, Clause 5.2.2 for the state transition.
-
-### 5.11.2 Test setup and configuration
-
-In Standalone mode, the test setup consists of two 5G cells, each one associated with a different O-DU and O-CU connected to same 5G Core network, refer Figure 5-9 for the test setup topology. The test environment shall have single UE.
-
-
-
-Diagram of the Inter O-CU mobility test bed for SA mode of operation. It shows two gNB O-DUs connected to their respective gNB O-CUs via F1 interfaces. Both gNB O-CUs are connected to a central 5G CN (containing AMF and UPF) via NG C/U interfaces. The 5G CN is also connected to an Application Server. Two gNB O-RUs are shown, each connected to one of the gNB O-DUs. A UE is shown moving between the two gNB O-RUs, indicated by a double-headed arrow. An Xn interface is shown between the two gNB O-CUs.
-
-Figure 5-9 Inter O-CU mobility test bed for SA mode of operation
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The radio conditions of UE are initially set to excellent. The minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside RF shielded box or RF shielded room if the UE is not connected via cable. The UE handover between the cells can be achieved by changing radio signal strength of source and target cells using variable attenuators.
-
-**Field setup:** The drive route with source and target cells should be defined. The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRP as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.5) should not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route from source cell to target cell.
-
-### 5.11.3 Test procedure
-
-Below are the SA Mode Intra-frequency steps
-
-- 1) The 5G cell setup is configured following Clause 5.11.2.
-- 2) Configure two 5G cells (cell 1 and cell 2) connected to different O-DU and O-CU according to the test configuration. The cells are activated and unloaded.
-- 3) Both 5G Cells are configured neighbors to each other, so that UE can use it for cell re-selection.
-- 4) The source cell (source O-DU and source O-CU) is the cell where UE is initially placed as depicted in Figure 5-9.
-- 5) Power on the UE and UE shall successfully register to source 5G cell.
-- 6) Wait till the UE goes in idle mode as per UE inactivity timer and then move the UE from source cell to target cell.
-- 7) Once UE moves to new cell, make an MO data call.
-- 8) Repeat the above test steps for 10 iterations.
-
-Below are the SA Mode Inter-frequency steps
-
-- 1) The 5G cell setup is configured following Clause 5.11.2.
-- 2) Configure two 5G cells (cell 1 and cell 2) connected to different O-DU and O-CU according to the test configuration. The cells are activated and unloaded.
-- 3) Both 5G Cells are configured neighbors to each other, so that UE can use it for cell re-selection.
-- 4) The source cell (source O-DU and source O-CU) is the cell where UE is initially placed as depicted in Figure 5-9.
-- 5) Power on the UE and UE shall successfully register to source 5G cell.
-- 6) Wait till the UE goes in idle mode as per UE inactivity timer and then move the UE from source cell to target cell.
-- 7) Once UE moves to new cell, make an MO data call.
-- 8) Repeat the above test steps for 10 iterations.
-
-### 5.11.4 Test requirements (expected results)
-
-The Idle mode inter O-CU cell reselection shall be verified for both intra-frequency and inter-frequency. Also verify call setup latency on a target cell with reference to RRC connection call flow mentioned in 3GPP 38.133, Clause 5.3.3.1. Following functionalities are also validated to declare the verdict.
-
-- RRC connection establishment is complete.
-- Cell re-selection is successful.
-
-In addition to the common minimum set of configuration parameters defined (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-SUT side:
-
-- Idle mode mobility time from UE, in idle mode at source to UE in idle mode to target.
-
-UE side:
-
-- Radio parameters such as RSRP and RSRQ (average per second)
-- KPI's related to Cell re-selection failure, Idle mode mobility time from UE, in idle mode at source to UE in idle mode to target
-
-The cell re-selection failure can be found out by checking if the cell re-selection is successful or not. The Idle to Connected on a target cell Time latency is measured by calculating the time between RRC\_Idle mode to RRC\_Connected state when UE moves to new cell after initiating an MO call. Capture the cell re-selection success/failure and latency for each iteration and sort the latency value observed for each iteration in ascending order. Record the Minimum, Average (Sum of all latency value/ Total Iterations, Total Iterations are 10 in this case) and Maximum latency value observed in below tables:
-
-**Table 5-15 5G Cell Re-selection Success and Failure KPI**
-
-| KPI | Repeat Times | | | | | | | | | |
-|---------------------------|--------------|---|---|---|---|---|---|---|---|----|
-| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
-| Cell Re-selection Success | | | | | | | | | | |
-| Cell Re-selection Failure | | | | | | | | | | |
-
-## 5.12 5G/4G Inter-System Mobility - 5GS to EPS handover
-
-### 5.12.1 Test description and applicability
-
-The purpose of this test is to validate inter-system handovers between 5G and LTE systems as defined in 3GPP TS 38.300 [47]. In this test scenario, inter-system handover from 5G Standalone (i.e. connected with 5GC) to LTE Standalone (i.e. connected with EPC) is validated. The test validates the O-CU-CP/O-CU-UP, O-DU, and O-RU functionality in handling Inter-RAT mobility from 5G to LTE. This scenario covers handover of UE from 5G to LTE when UE is registered in 5G and moves from 5G coverage area to LTE coverage area. This scenario is applicable for LTE and 5G SA.
-
-The test focuses on the procedure of ‘5GS to EPS handover using N26 interface’ as defined in 3GPP TS 23.502 [41] Clause 4.11.1.2.1.
-
-### 5.12.2 Test setup and configuration
-
-The test setup shall include 5G End to End system (5G SUT and 5G Core (5GC)) and LTE E2E system (4G SUT and 4G Core (EPC)). 5G and 4G core shall be interconnected for Inter System mobility (N26 interface between the MME and AMF) and shall supports a combined anchor point for 4G and 5G, i.e. SMF+PGW-C and UPF+PGW-U. The LTE SUT connects to a 4G-5G interconnected core over the 4G interfaces, i.e. S1 to provide 4G LTE service to make E2E LTE system and the O-CU-CP/O-CU-UP, O-DU and O-RU connect to a 4G-5G interconnected core over the 5G interfaces, i.e. N2 and N3 to make E2E 5G SA system. The 4G and 5G SUTs and the components shall comply to the O-RAN specifications. This test needs a real or emulated UE. The test setup (UE, 4G SUT, 5G SUT, 5G and 4G Core) should include tools which have the ability to collect traces on the elements and/or packet captures of communication between the elements. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for. The 4G SUT, 5G SUT and their components (O-RU, O-DU and O-CU-CP/O-CU-UP) should have the right configuration and software load.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio conditions of the UE are initially set to excellent using RSRP as the metric. The minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside and RF shielded box or RF shielded room if the UE is not connected via cable. The UE handover between the cells can be achieved by changing the radio signal strength of the source 5G cell and target 4G cell using variable attenuators.
-
-**Field setup:** The drive route with source and target cells should be defined. The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (using RSRP as the metric as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.5) should not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route from source 5G cell and target 4G cell.
-
-### 5.12.3 Test procedure
-
-Below are the 5G to LTE Inter System handover steps
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) 5G and LTE cells are configured as neighbours to each other, so that the UE can trigger measurement events for Inter System handover.
-- 3) The test UE is under source 5G cell coverage.
-- 4) Power on the UE and UE shall successfully register to source 5G cell.
-- 5) The full-buffer UDP bi-directional data transmission (see Clause 4.4) from the application server is initiated.
-- 6) The UE shall move from source 5G cell and target 4G cell to perform handover.
-
-### 5.12.4 Test requirements (expected results)
-
-The Inter System handover call flow shall be verified between 5G and LTE systems. Following functionalities shall also be validated:
-
-- PDU Session is established when full-buffer bi-directional data transmission is initiated with 5G source cell
-- Handover is successful.
-
-In addition to the common minimum set of configuration parameters defined (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-SUT/Application server side:
-
-- Transmit downlink throughput measured at application server in time (average per second)
-- Received uplink throughput measured at application server in time (average per second)
-- Uplink packet loss percentage during handover.
-- Uplink BLER, MCS, MIMO rank (RI) on PUSCH in time (average per second)
-
-UE side:
-
-- Radio parameters such as RSRP, RSRQ, SINR on PDSCH in time (average per second)
-- Downlink BLER, MCS, MIMO rank (RI) on PDSCH in time (average per second).
-- Received Downlink throughput (L1 and L3 PDCP layers) in time (average per second).
-- Downlink packet loss percentage during handover
-- Uplink throughput (L1 and L3 PDCP layers) in time (average per second)
-- Channel utilization, i.e. Number allocated/occupied downlink and uplink RBs in time (per TTI/average per second) and Number of allocated/occupied slots in time.
-- KPIs related to Handover failure, Call drop, Handover latency, Handover interruption time.
-
-## 5.13 5G/4G Inter-System Mobility - EPS to 5GS handover
-
-### 5.13.1 Test description and applicability
-
-The purpose of this test is to validate inter-system handovers between 5G and LTE systems as defined in 3GPP TS 38.300 [47]. In this test scenario, inter-system handover from LTE Standalone (i.e. connected with EPC) to 5G Standalone (i.e. connected with 5GC) is validated. The test validates the O-CU-CP/O-CU-UP, O-DU, and O-RU functionality in handling Inter-RAT mobility from LTE to 5G. This scenario covers handover of UE from 5G to LTE when UE is registered in LTE and moves from LTE coverage area to 5G coverage area. This scenario is applicable for LTE and 5G SA.
-
-The test focuses on the procedure of 'EPS to 5GS handover using N26 interface' as defined in 3GPP TS 23.502 [41] Clause 4.11.1.2.2.
-
-### 5.13.2 Test setup and configuration
-
-The test setup shall include 5G End to End system (5G SUT and 5G Core (5GC)) and LTE E2E system (4G SUT and 4G core (EPC)). 5G and 4G core shall be interconnected for Inter System mobility (N26 interface between the MME and AMF) and shall support a combined anchor point for 4G and 5G, i.e. SMF+PGW-C and UPF+PGW-U. The 4G SUT connects to a 4G-5G interconnected core over the 4G interfaces, i.e. S1 to provide 4G LTE service to make E2E LTE system and the O-CU-CP/O-CU-UP, O-DU and O-RU connect to a 4G-5G interconnected core over the 5G interfaces, i.e. N2 and N3 to make E2E 5G SA system. The 4G and 5G SUTs and the components shall comply to the O-RAN specifications. This test needs Real or emulated UE. The test setup (UE, 4G SUT, 5G SUT, 5G and 4G Core) should include tools which have the ability to collect traces on the elements and/or packet captures of communication between the elements. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for. The 4G SUT, 5G SUT and their components (O-RU, O-DU and O-CU-CP/O-CU-UP) need to have the right configuration and software load.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio conditions of the UE are initially set to excellent using RSRP as the metric. The minimum coupling loss (see Clause 4.6) should not be exceeded. The UE should be placed inside and RF shielded box or RF shielded room if the UE is not connected via cable. The UE handover between the cells can be achieved by changing the radio signal strength of the source 4G cell and target 5G cell using variable attenuators.
-
-**Field setup:** The drive route with source and target cells should be defined. The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (using RSRP as the metric as defined in Clause 4.6) should be observed. The minimum coupling loss (see Clause 4.5) should not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route from source 4G cell and target 5G cell.
-
-### 5.13.3 Test procedure
-
-Below are the LTE to 5G Inter System handover steps
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) LTE and 5G cells are configured as neighbours to each other, so that the UE can trigger measurement events for Inter System handover.
-- 3) The test UE is under source 4G cell coverage.
-- 4) Power on the UE and UE shall successfully register to source 4G cell.
-- 5) The full-buffer UDP bi-directional data transmission (see Clause 4.4) from the application server is initiated.
-
-- 6) The UE shall move from source 4G cell and target 5G cell to perform handover.
-
-### 5.13.4 Test requirements (expected results)
-
-The Inter System handover call flow shall be verified between LTE and 5G systems. Following functionalities shall also be validated:
-
-- PDU Session is established when full-buffer bi-directional data transmission is initiated with LTE source cell
-- Handover is successful
-
-In addition to the common minimum set of configuration parameters defined (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-SUT/Application server side:
-
-- Transmit downlink throughput measured at application server in time (average per second)
-- Received uplink throughput measured at application server in time (average per second)
-- Uplink packet loss percentage during handover.
-- Uplink BLER, MCS, MIMO rank (RI) on PUSCH in time (average per second)
-
-UE side:
-
-- Radio parameters such as RSRP, RSRQ, SINR on PDSCH in time (average per second)
-- Downlink BLER, MCS, MIMO rank (RI) on PDSCH in time (average per second).
-- Received Downlink throughput (L1 and L3 PDCP layers) in time (average per second).
-- Downlink packet loss percentage during handover
-- Uplink throughput (L1 and L3 PDCP layers) in time (average per second)
-- Channel utilization, i.e. Number allocated/occupied downlink and uplink RBs in time (per TTI/average per second) and Number of allocated/occupied slots in time.
-
-KPIs related to Handover failure, Call drop, Handover latency, Handover interruption time.
-
-# --- 6 Performance tests
-
-## 6.0 Performance tests introduction
-
-This clause describes the tests evaluating and assessing the **performance of radio access network from network end-to-end perspective** (see Clause 4.1). The focus of the testing is on the end-user performance which is compared against the target and expected performance values. The pass and fail thresholds are defined for the test wherever possible.
-
-The general test methodologies and configurations are mentioned in Clause 4.
-
-Unless otherwise stated in the clause, the tests are suitable and can be performed in both laboratory as well as field testing environments, with pros and cons for each environment. The specific lab and field test setups are mentioned in each test.
-
-The following end-to-end performance tests are defined in this clause as an extension of NGMN testing framework [3]:
-
-Table 6-1: E2E Performance Test Case summary
-
-| Test case | | Applicable technology | | |
-|-----------|---------------------------------------------------------|-----------------------|-----|----|
-| | | LTE | NSA | SA |
-| Test ID | E2E Performance Assessment | | | |
-| 6.2 | Downlink peak throughput | Y | Y | Y |
-| 6.3. | Uplink peak throughput | Y | Y | Y |
-| 6.4 | Downlink throughput in different radio conditions | Y | Y | Y |
-| 6.5 | Uplink throughput in different radio conditions | Y | Y | Y |
-| 6.6 | Bidirectional throughput in different radio conditions | Y | Y | Y |
-| 6.7 | Downlink coverage throughput (link budget) | Y | Y | Y |
-| 6.8 | Uplink coverage throughput (link budget) | Y | Y | Y |
-| 6.9 | Downlink aggregated cell throughput (cell capacity) | Y | Y | Y |
-| 6.10 | Uplink aggregated cell throughput (cell capacity) | Y | Y | Y |
-| 6.11 | Impact of fronthaul latency on downlink peak throughput | Y | Y | Y |
-| 6.12 | Impact of fronthaul latency on uplink peak throughput | Y | Y | Y |
-| 6.13 | Impact of midhaul latency on downlink peak throughput | N/A | Y | Y |
-| 6.14 | Impact of midhaul latency on uplink peak throughput | N/A | Y | Y |
-| 6.15 | End-to-end user plane latency | Y | Y | Y |
-
-Future versions of this specification may add additional end-to-end performance tests not currently addressed in this version, for example:
-
-- Downlink throughput with inter-cell interferences (multi-cell, single UE scenario)
-- Uplink throughput with inter-cell interferences (multi-cell, single UE scenario)
-- Downlink drive throughput (multi-cell, single UE scenario)
-- Uplink drive throughput (multi-cell, single UE scenario)
-- Impact of fronthaul compression scheme on downlink peak throughput (single cell, single UE scenario)
-- Impact of fronthaul compression scheme on uplink peak throughput (single cell, single UE scenario)
-- Resource scheduling (single cell, multi-UE scenario)
-
-## 6.1 Expected throughput calculation
-
-### 6.1.1 4G LTE
-
-The 4G LTE expected theoretical downlink or uplink throughput at the physical layer can be calculated using the following formula:
-
-$$L1 \text{ throughput [Mbps]} = 10^{-6} \cdot \sum_{j=1}^J \left( v_{Layer}^j \cdot Q_m^j \cdot R \cdot \frac{N_{PRB}^{BW,j} \cdot 12}{T_s} \cdot (1 - OH^j) \cdot DLUL_{ratio} \right)$$
-
-where
-
-- $J$ is the number of aggregated LTE component carriers.
-
-- $R$ is the coding rate corresponding to channel quality (CQI and SINR). The maximum coding rate is 0.9258.
-
-For the j-th component carrier:
-
-- $v_{Layers}$ is the number of MIMO layers. The maximum is 4 (8 in LTE-Advanced) in downlink and 1 (4 in LTE - Advanced) in uplink.
-- $Q_m$ is the modulation order, which is equal to 2 for QPSK, 4 for 16QAM, 5 for 32QAM, 6 for 64QAM, 8 for 256QAM.
-- $N_{PRB}^{BW}$ is the number of PRBs allocated in bandwidth BW – see Table 6-2.
-
-**Table 6-2 The number of PRBs allocated in bandwidth**
-
-| | | | | | | |
-|-----------------|-----|----|----|----|----|-----|
-| Bandwidth [MHz] | 1.4 | 3 | 5 | 10 | 15 | 20 |
-| Number of PRBs | 6 | 13 | 25 | 50 | 75 | 100 |
-
-- $OH$ is overhead for control channels and signalling (i.e., Reference Signal, PSS, SSS, PBCH, PDCCH, etc. in downlink or SRS, PUCCH, PRACH in uplink) within a period of 1 sec – see Table 6-3 for downlink.
-
-**Table 6-3 Overhead as a function of bandwidth, no. of antenna ports and CFI**
-
-| Bandwidth | 1.4 MHz | | 3 MHz | | 5 MHz | | 10 MHz | | 15 MHz | | 20 MHz | |
-|-------------------|---------|------|-------|------|-------|------|--------|------|--------|------|--------|------|
-| CFI | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 |
-| 1 TX (ant. ports) | 0.16 | 0.21 | 0.14 | 0.18 | 0.12 | 0.17 | 0.12 | 0.16 | 0.11 | 0.16 | 0.11 | 0.16 |
-| 2 TX (ant. ports) | 0.20 | 0.24 | 0.17 | 0.22 | 0.16 | 0.21 | 0.15 | 0.20 | 0.15 | 0.20 | 0.15 | 0.20 |
-| 4 TX (ant. ports) | 0.25 | 0.29 | 0.22 | 0.26 | 0.21 | 0.25 | 0.20 | 0.25 | 0.20 | 0.25 | 0.20 | 0.24 |
-
-- $T_s$ is the average OFDM symbol duration in a subframe, and it is equal to $T_s = 10^{-3}/14$ for normal Cyclic Prefix (14 OFDM symbols per slot) or $T_s = 10^{-3}/12$ for extended CP (12 OFDM symbols per slot).
-- $DLUL_{ratio}$ is a ratio of the symbols allocated for DL or UL data to total number of symbols in a frame (10ms) – predefined patterns (uplink-downlink configuration, special subframe configuration) for DL/UL allocation in [25]. In case of FDD mode, the $DLUL_{ratio}$ is equal to 1.
-
-Example of calculation of expected downlink throughput for the following system configuration:
-
-- MIMO 2x2 $\rightarrow v_{Layers} = 2$
-- BW = 20 MHz $\rightarrow N_{PRB}^{BW}=100$
-- Normal CP
-- CFI = 1 $\rightarrow OH = 0.15$
-- no carrier aggregation $\rightarrow J = 1$
-- MCS = 28 and modulation 64QAM $\rightarrow Q_m = 6$ and $R = 0.9258$
-- TDD with uplink-downlink configuration = 1 (i.e., DSUUD) and special subframe configuration = 7 (i.e., 10:2:2) $\rightarrow DLUL_{ratio} = (14 \cdot 2 + 10)/(14 \cdot 5) = 0.543$
-
-$$L1 \text{ throughput [Mbps]} = 10^{-6} \cdot \sum_{j=1}^1 \left( 2 \cdot 6 \cdot 0.9258 \cdot \frac{100 \cdot 12}{\frac{10^{-3}}{14}} \cdot (1 - 0.15) \cdot 0.543 \right) = 86.1 \text{ Mbps}$$
-
-### 6.1.2 5G NR
-
-The 5G NR expected theoretical downlink or uplink throughput at physical layer (UE category is not assumed) can be calculated using the following formula [15]:
-
-$$L1 \text{ throughput [Mbps]} = 10^{-6} \cdot \sum_{j=1}^J \left( v_{Layers}^j \cdot Q_m^j \cdot f^j \cdot R \cdot \frac{N_{PRB}^{BWj,\mu} \cdot 12}{T_s^\mu} \cdot (1 - OH^j) \cdot DLUL_{ratio} \right)$$
-
-where
-
-- $J$ is the total number of component carriers (CC) in a band or band combination. The maximum number is 16 [23].
-- $R$ is the coding rate corresponding to channel quality (CQI, SINR), and it is calculated as *Target\_code\_rate* [22]/1024. For LDPC code the maximum coding rate is 948/1024.
-
-For the j-th component carrier:
-
-- $v_{Layers}$ is the number of MIMO layers. The maximum is 8 in downlink and 4 in uplink [23].
-- $Q_m$ is the modulation order, which is equal to 2 for QPSK, 4 for 16QAM, 5 for 32QAM, 6 for 64QAM, 8 for 256QAM.
-- $f$ is the scaling factor [24] which can take the values 0.4, 0.75, 0.8 or 1. The scaling factor is signalled per band and per band combination as per UE capability signalling.
-- $OH$ is the overhead of control channels and signalling within a period of 1 sec, and it is equal to:
- - 0.14 for frequency range 1 (FR1) for DL
- - 0.18 for frequency range 2 (FR2) for DL
- - 0.08 for frequency range 1 (FR1) for UL
- - 0.10 for frequency range 2 (FR2) for UL
-- $\mu$ is 5G NR numerology (sub-carrier spacing) which can take the values from 0 to 4 [20]. The number of slots per frame and sub-carrier spacing vary with numerology – see Table 6-4.
-
-**Table 6-4 5G NR numerology**
-
-| 5G NR numerology $\mu$ | Sub-carrier spacing (SCS) | Number of slots per frame | Number of symbols per slot | Total number of symbols per frame |
-|------------------------|---------------------------|---------------------------|----------------------------|-----------------------------------|
-| 0 | 15 kHz | 10 | 14 (normal CP) | 140 |
-| 1 | 30 kHz | 20 | 14 (normal CP) | 280 |
-| 2 | 60 kHz | 40 | 14 (normal CP) | 560 |
-| | 60 kHz | 40 | 12 (extended CP) | 480 |
-| 3 | 120 kHz | 80 | 14 (normal CP) | 1120 |
-| 4 | 240 kHz | 160 | 14 (normal CP) | 2240 |
-
-- $T_s^\mu$ is the average OFDM symbol duration in a subframe for numerology $\mu$ , and it is equal to $T_s^\mu = 10^{-3}/(14 \cdot 2^\mu)$ for normal Cyclic Prefix (14 OFDM symbols per slot) or $T_s^\mu = 10^{-3}/(12 \cdot 2^\mu)$ for extended CP (12 OFDM symbols per slot).
-- $N_{PRB}^{BW,\mu}$ is the number of PRBs allocated in bandwidth BW with numerology $\mu$ - see Table 6-5.
-
-**Table 6-5 The max. number of PRBs for each supported bandwidth and 5G NR numerology $\mu$ [18], [19]**
-
-| $\mu$ | Channel bandwidth BW [MHz] | | | | | | | | | | | | | |
-|-------|----------------------------|----|----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|
-| | 5 | 10 | 15 | 20 | 25 | 30 | 40 | 50 | 60 | 80 | 90 | 100 | 200 | 400 |
-| 0 | 25 | 52 | 79 | 106 | 133 | 160 | 216 | 270 | N/A | N/A | N/A | N/A | N/A | N/A |
-| 1 | 11 | 24 | 38 | 51 | 65 | 78 | 106 | 133 | 162 | 217 | 245 | 273 | N/A | N/A |
-| 2 | N/A | 11 | 18 | 24 | 31 | 38 | 51 | 65 | 79 | 107 | 121 | 135 | N/A | N/A |
-
-| | | | | | | | | | | | | | | |
-|---|-----|-----|-----|-----|-----|-----|-----|----|-----|-----|-----|-----|-----|-----|
-| 3 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | 66 | N/A | N/A | N/A | 132 | 264 | N/A |
-| 4 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | 32 | N/A | N/A | N/A | 66 | 132 | 264 |
-
-- $DLUL_{ratio}$ is a ratio of the symbols allocated for DL or UL data to total number of symbols in a time period (periodicity) in TDD mode – predefined slot formats in [21]. In case of FDD mode, the $DLUL_{ratio}$ is equal to 1.
-
-Example of calculation of expected downlink throughput for the following system configuration:
-
-- SCS = 15kHz → $\mu = 0$
-- MIMO 2x2 → $v_{Layers} = 2$
-- BW = 20 MHz → $N_{PRB}^{BW,\mu} = 106$
-- Normal CP
-- no carrier aggregation → $J = 1$
-- MCS = 28 and modulation 64QAM → $Q_m = 6$ and Target code rate = 948
-- scaling factor $f = 1$
-- downlink throughput and FR1 → OH = 0.14
-- TDD configuration 4:1 (DDDDSU), i.e., four DL slots (slot format 0 [21]), one Special slot (slot format 32 [21]) and one UL slot (slot format 1 [21]) where slot format 0 means allocation of all 14 symbols for DL, slot format 1 means allocation of all 14 symbols for UL, slot format 32 means allocation of 10 symbols for DL, 2 symbols for Guard Period, 2 symbols for UL → $DLUL_{ratio} = (14 \cdot 4 + 10) / 14 \cdot 6 = 0.7857$
-
-$$L1 \text{ throughput [Mbps]} = 10^{-6} \cdot \sum_{j=1}^1 \left( 2 \cdot 6 \cdot 1 \cdot 948/1024 \cdot \frac{106 \cdot 12}{\frac{10^{-3}}{14 \cdot 2^0}} \cdot (1 - 0.14) \cdot 0.7857 \right) = 133.6 \text{ Mbps}$$
-
-## 6.2 Downlink peak throughput
-
-### 6.2.1 Test description and applicability
-
-The purpose of the test is to measure the peak (i.e., maximum achievable) user data throughput in the downlink direction (i.e., data transmitted from application (traffic) server to UE). A stationary UE is placed under excellent radio conditions inside an isolated cell.
-
-### 6.2.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., an isolated cell without any inter-cell interference – see Clause 4.7) with a stationary UE (real or emulated UE) placed under excellent radio conditions as defined in Clause 4.6 – using SINR as the metric since this is a downlink test. Note that in this case of a single cell scenario, SINR is in fact SNR as inter-cell interference is not present. Within the cell there shall be only one active UE downloading data from the application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with sufficient capacity so as not to limit the expected data throughput. The test is suitable for both lab and field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (SINR as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded. The UE shall be placed inside an RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT’s antenna(s), where excellent radio conditions (SINR as defined in Clause 4.6) shall be observed. The minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-
-
-Figure 6-1: The test setups of 4G, 5G NSA and 5G SA. The diagram shows three network architectures. Top: 4G setup where a UE connects via Uu to a 4G eNB (part of the O-RAN System under test), which connects via S1 to a 3GPP Core 4G EPC, which then connects to an Application server providing 3GPP and Other services. Middle: 5G NSA setup where a UE connects via Uu to both a 4G eNB (anchor) and a 5G en-gNB (both part of the O-RAN System under test). The 4G eNB connects via S1 to a 3GPP Core 4G EPC EN-DC NSA, and the 5G en-gNB connects via S1 to the same core. The core connects to an Application server. An X2 interface is shown between the 4G eNB and 5G en-gNB. Bottom: 5G SA setup where a UE connects via Uu to a 5G gNB (part of the O-RAN System under test), which connects via NG to a 3GPP Core 5GC SA, which then connects to an Application server providing 3GPP and Other services.
-
-Figure 6-1 The test setups of 4G, 5G NSA and 5G SA
-
-### 6.2.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated UE) is placed under excellent radio conditions (cell centre close to radiated SUT's antenna) using SINR thresholds as indicated in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The downlink full-buffer UDP and TCP data transmission (see Clause 4.4) from the application server shall be verified by adjusting the connection settings (cabled environment) or UE position (OTA environment). The UE under excellent radio conditions that is achieving peak user throughput shall see stable utilization of the highest possible downlink MCS, downlink transport block size and downlink MIMO rank (number of layers). These KPIs shall also be verified.
-- 4) The UE shall be turned off or set to airplane mode, to empty the buffers. The downlink full-buffer UDP data transmission from the application server to the UE is started. The UE shall receive the data from the application server.
-- 5) All the required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below is measured and captured at the UE and Application server sides using logging/measurement tools. The duration of the test shall be at least 3 minutes when the throughput is stable. The location and position of the UE shall remain unchanged during the entire measurement duration (capture of log data).
-- 6) The capture of log data is stopped. The downlink full-buffer UDP data transmission from the application server is stopped.
-- 7) [Optional] Steps 4 to 6 are repeated for downlink full-buffer TCP data transmission.
-
-### 6.2.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and Application layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e., Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-Application server side:
-
-- Transmitted downlink throughput (Application layer) (average sample per second)
-
-When the UE is under excellent radio conditions (cell centre), the stable utilization of the highest possible downlink MCS, downlink transport block size and downlink MIMO rank shall be observed. The UE shall also receive the data with minimum downlink BLER.
-
-Table 6-6 gives an example of the test results record (median and standard deviation from the captured samples shall be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G paths. The spectral efficiency (see Clause 4.8) shall be calculated for benchmarking and comparison purposes to minimize the influence of different configured parameters such as bandwidth and TDD DL/UL ratio.
-
-**Table 6-6 Example record of test results (median and standard deviation from the captured samples)**
-
-| | UDP | TCP |
-|-------------------------------------------|-----|-----|
-| Received L1 DL throughput [Mbps] | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| Received Application DL throughput [Mbps] | | |
-| UE RSRP [dBm] | | |
-| UE RSRQ [dB] | | |
-| UE SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL PRB number | | |
-| PDSCH BLER [%] | | |
-
-The following figures shall be also included in the test report, and the stable behavior shall be observed and evaluated.
-
-- Received UDP downlink throughput (L1 and Application layer) vs Time duration
-- PDSCH SINR vs Time duration
-- Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots vs Time duration
-
-The gap analysis shall be provided for the measured and the expected target downlink throughputs which can be calculated based on the procedures from Clause 6.1.
-
-## 6.3 Uplink peak throughput
-
-### 6.3.1 Test description and applicability
-
-The purpose of the test is to measure the peak (i.e., maximum achievable) user data throughput in uplink direction (i.e., data transmitted from UE to application (traffic) server). The stationary UE is placed under excellent radio conditions inside the isolated cell.
-
-### 6.3.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated UE) placed under excellent radio conditions as defined in Clause 4.6 – using RSRP as the metric since this is an uplink test. Within the cell there shall be only one active UE uploading data to the application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with sufficient capacity so as not to limit the expected data throughput. The test is suitable for both lab and field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (RSRP as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded. The UE shall be placed inside an RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRP as defined in Clause 4.6) shall be observed. The minimum coupling loss (see Clause 4.5) shall not be exceeded.
-
-The test setups of 4G, 5G NSA and 5G SA are mentioned in Figure 6-1.
-
-### 6.3.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated UE) is placed under excellent radio condition (cell centre close to radiated SUT's antenna) using RSRP thresholds as indicated in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The uplink full-buffer UDP and TCP data transmission (see Clause 4.4) from UE to the application server shall be verified by adjusting the connection settings (cabled environment) or UE position (OTA environment). The UE under excellent radio conditions that is achieving peak user throughput shall see stable utilization of the highest possible uplink MCS and uplink transport block size. These KPIs shall also be verified.
-- 4) The UE shall be turned off or set to airplane mode, if possible, to empty the buffers. The uplink full-buffer UDP data transmission from UE to the application server is started. The application server shall receive the sent data.
-- 5) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at UE, SUT and Application server sides using logging/measurement tools. The duration of test shall be at least 3 minutes when the throughput is stable. The location and position of the UE shall remain unchanged during the entire measurement duration (capture of log data).
-- 6) The capture of log data is stopped. The uplink full-buffer UDP data transmission from UE to the application server is stopped.
-
-- 7) The UE shall be turned off or set to airplane mode, to empty the buffers. The uplink full-buffer TCP data transmission from UE to the application server is started, and Step 5 is repeated.
-
-### 6.3.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PUSCH BLER, PUSCH MCS (average sample per second)
-- Transmit power on PUSCH
-- Transmitted uplink throughput (Application layer) (average sample per second)
-- Channel utilization, i.e., Number allocated/occupied uplink PRBs and Number of allocated/occupied slots (average sample per second)
-
-SUT side (if capture of logs is possible):
-
-- Radio parameters such as PUSCH SINR (average per second)
-- PUSCH BLER (average sample per second)
-
-Application server side:
-
-- Received uplink throughput (L1 and Application layers) (average sample per second)
-
-When the UE is in excellent radio condition (cell centre), the stable utilization of the highest possible uplink MCS and uplink transport block size shall be observed and evaluated. The SUT shall also receive the data with the minimum uplink BLER.
-
-Table 6-7 gives an example of the test results record (median and standard deviation from the measured samples shall be provided for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G. The spectral efficiency (see Clause 4.8) shall be calculated for benchmarking and comparison to minimize the influence of different configured parameters such as bandwidth and TDD DL/UL ratio.
-
-**Table 6-7 Example record of test results (median and standard deviation from the measured samples)**
-
-| | UDP | TCP |
-|-------------------------------------------|-----|-----|
-| Received L1 UL throughput [Mbps] | | |
-| L1 UL Spectral efficiency [bps/Hz] | | |
-| Received Application UL throughput [Mbps] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| PUSCH transmit power [dBm] | | |
-| PUSCH MCS | | |
-| UL RB number | | |
-| PUSCH BLER [%] | | |
-
-The following figures shall be also included in the test report, and the stable behavior shall be observed and evaluated.
-
-- Received UDP uplink throughput (L1 and Application layers) vs Time duration
-
-- UE RSRP vs Time duration
-- Number of allocated/occupied uplink PRBs and Number of allocated/occupied slots vs Time duration
-
-The gap analysis shall be provided for the measured and the expected target uplink throughputs which can be calculated based on the procedures from Clause 6.1.
-
-## 6.4 Downlink throughput in different radio conditions
-
-### 6.4.1 Test description and applicability
-
-The purpose of the test is to measure the user experienced data throughput in the downlink direction while varying received radio signal quality (strength). The UE is placed in different stationary points inside the isolated cell.
-
-### 6.4.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated UE) placed in different radio conditions as defined in Clause 4.6 - SINR shall be considered in case of downlink. Note that in this case of single cell scenario, SINR is in fact SNR as inter-cell interferences are not present. The UE is sequentially placed in different radio conditions ranging from good to poor. Note that the testing of peak downlink throughput in excellent radio conditions is already covered in Clause 6.2 and so is skipped in this clause. Within the cell there shall be only one active UE in time downloading data from the application (traffic) server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with sufficient capacity so as not to limit the expected data throughput. The test is suitable for lab as well as field environment.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio conditions of UE are initially set to good. The minimum coupling loss (see Clause 4.6) shall not be exceeded. The change in radio conditions of UE, from excellent through fair and good to poor, is achieved by increasing the attenuation of radio signal. The UE shall be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The test points with good, fair, and poor radio conditions (as defined in Clause 4.6) shall be defined inside the serving cell. The minimum coupling loss (see Clause 4.5) shall not be exceeded. The UE is initially placed where good radio conditions (SINR as defined in Clause 4.6) shall be observed. The change in radio conditions is achieved by moving the UE inside the serving cell from close to cell centre (with good radio conditions) to cell edge (with poor radio conditions).
-
-The test setups of 4G, 5G NSA and 5G SA are mentioned in Figure 6-1.
-
-### 6.4.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated UE) is placed under good radio conditions (close to cell centre) using SINR thresholds as indicated in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The downlink full-buffer UDP and TCP data transmission (see Clause 4.4) from the application server shall be verified by adjusting the connection settings (cabled environment) or UE position (OTA environment) to achieve good radio conditions.
-- 4) The UE shall be turned off or set to airplane mode, to empty the buffers. The downlink full-buffer UDP data transmission from the application server to the UE is started. The UE shall receive the data from the application server.
-
-- 5) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at UE and Application server sides using logging/measurement tools. The duration of test shall be at least 3 minutes when the throughput is stable. The location and position of the UE shall remain unchanged during the entire measurement duration (capture of log data).
-- 6) The capture of log data is stopped. The downlink full-buffer UDP data transmission from the application server is stopped.
-- 7) The radio conditions of UE are changed to fair using SINR thresholds as indicated in Clause 4.6. The steps 4 to 6 are repeated.
-- 8) The radio conditions of UE are changed to poor (cell edge) radio condition using SINR thresholds as indicated in Clause 4.6. Steps 4 to 6 are repeated.
-- 9) [Optional] Steps 4 to 8 are repeated for downlink full-buffer TCP data transmission.
-
-### 6.4.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1, and Application layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e., Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-Application server side:
-
-- Transmitted downlink throughput (Application layer) (average sample per second)
-
-As the UE moves from good (close to cell centre), to fair, and to poor (cell edge) radio conditions, the changing radio conditions shall cause the UE to report lower CQI and MIMO rank which results in assignment of lower MCS and lower data throughput in the downlink.
-
-Table 6-8 gives an example of the test results record (median and standard deviation from the captured samples shall be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G paths. The spectral efficiency (see Clause 4.8) shall be calculated for benchmarking and comparison to minimize the influence of different configured parameters such as bandwidth and TDD DL/UL ratio.
-
-**Table 6-8 Example record of test results (median and standard deviation from the captured samples)**
-
-| | Good | Fair | Poor
(cell edge) |
-|-------------------------------------------|-----------|-----------|---------------------|
-| | UDP / TCP | UDP / TCP | UDP / TCP |
-| Received L1 DL throughput [Mbps] | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | |
-| Received Application DL throughput [Mbps] | | | |
-| UE RSRP [dBm] | | | |
-| UE PDSCH SINR [dB] | | | |
-
-| | | | |
-|----------------|--|--|--|
-| MIMO rank | | | |
-| PDSCH MCS | | | |
-| DL RB number | | | |
-| PDSCH BLER [%] | | | |
-
-The following figures shall be also included in the test report, and the stable behavior shall be observed and evaluated.
-
-- Received UDP downlink throughput (L1 and Application layer) vs Time duration
-- PDSCH SINR vs Time duration
-- Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots vs Time duration
-
-The gap analysis shall be provided for the measured and the expected target downlink throughputs which can be calculated based on the procedures from Clause 6.1.
-
-## 6.5 Uplink throughput in different radio conditions
-
-### 6.5.1 Test description and applicability
-
-The purpose of the test is to measure the user experienced data throughput in uplink while varying received radio signal quality (strength). The UE is placed in different stationary points inside the isolated cell.
-
-### 6.5.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated UE) placed in different radio conditions as defined in Clause 4.6 - RSRP shall be considered in case of uplink. The UE is gradually placed in different radio conditions from good (close to cell centre) to poor (cell edge – coverage limited cell edge in case of single cell scenario). Note that the testing of peak uplink throughput in excellent radio conditions is already covered in Clause 6.3 and so is skipped in this clause. Within the cell there shall be only one active UE in time uploading data to the application (traffic) server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with sufficient capacity so as not to limit the expected data throughput. The test is suitable for both lab and field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio conditions of UE are initially set to good. The minimum coupling loss (see Clause 4.6) shall not be exceeded. The change in radio conditions of UE, from good to fair to poor, is achieved by increasing the attenuation of radio signal. The UE shall be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The test points with good, fair, and poor radio conditions (as defined in Clause 4.6) shall be identified inside the serving cell. The minimum coupling loss (see Clause 4.5) shall not be exceeded. The UE is initially placed where good radio conditions (RSRP as defined in Clause 4.6) shall be observed. The change in radio conditions is achieved by moving the UE inside the serving cell from close to cell centre (with good radio conditions) to cell edge (with poor radio conditions).
-
-The test setups of 4G, 5G NSA and 5G SA are illustrated in Figure 6-1.
-
-### 6.5.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-
-- 2) The UE (real or emulated UE) is placed under good radio condition (close to cell centre) using RSRP thresholds as indicated in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The uplink full-buffer UDP and TCP data transmission (see Clause 4.4) from UE to the application server shall be verified by adjusting the connection settings (cabled environment) or UE position (OTA environment) to achieve good radio conditions.
-- 4) The UE shall be turned off or set to airplane mode, to empty the buffers. The uplink full-buffer UDP data transmission from UE to the application server is started. The application server shall receive the data from UE.
-- 5) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at UE, SUT and application server side using logging/measurement tools. The duration of test shall be at least 3 minutes when the throughput is stable. The location and position of the UE shall remain unchanged during the entire measurement duration (capture of log data).
-- 6) The capture of log data is stopped. The uplink full-buffer UDP data transmission from UE to the application server is stopped.
-- 7) The radio conditions of UE are changed to fair using RSRP thresholds as indicated in Clause 4.6. The steps 4 to 6 are repeated.
-- 8) The radio conditions of UE are changed to poor (cell edge) radio condition using RSRP thresholds as indicated in Clause 4.6. Steps 4 to 6 are repeated.
-- 9) [Optional] Steps 4 to 8 are repeated for uplink full-buffer TCP data transmission.
-
-### 6.5.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PUSCH BLER, PUSCH MCS (average sample per second)
-- Transmit power on PUSCH
-- Transmitted uplink throughput (Application layer) (average sample per second)
-- Channel utilization, i.e., Number allocated/occupied uplink PRBs and Number of allocated/occupied slots (average sample per second)
-
-SUT side (if capture of logs is possible):
-
-- Radio parameters such as PUSCH SINR (average per second)
-- PUSCH BLER (average per second)
-
-Application server side:
-
-- Received uplink throughput (L1 and Application layers) (average sample per second)
-
-Table 6-9 gives an example of the test results record (median and standard deviation from the captured samples shall be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G paths. The spectral efficiency (see Clause 4.8) shall be calculated for benchmarking and comparison to minimize the influence of different configured parameters such as bandwidth and TDD DL/UL ratio.
-
-**Table 6-9 Example record of test results (median and standard deviation from the measured samples)**
-
-| | Good | Fair | Poor
(cell edge) |
-|-------------------------------------------|-----------|-----------|---------------------|
-| | UDP / TCP | UDP / TCP | UDP / TCP |
-| Received L1 UL throughput [Mbps] | | | |
-| L1 UL Spectral efficiency [bps/Hz] | | | |
-| Received Application UL throughput [Mbps] | | | |
-| UE RSRP [dBm] | | | |
-| UE PDSCH SINR [dB] | | | |
-| PUSCH transmit power [dBm] | | | |
-| PUSCH MCS | | | |
-| UL RB number | | | |
-| PUSCH BLER [%] | | | |
-
-The following figures shall be also included in the test report, and the stable behavior shall be observed and evaluated.
-
-- Received UDP uplink throughput (L1 and Application layers) vs Time duration
-- UE RSRP vs Time duration
-- Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots vs Time duration
-
-The gap analysis shall be provided for the measured and the expected target uplink throughputs which can be calculated based on the procedures from Clause 6.1.
-
-## 6.6 Bidirectional throughput in different radio conditions
-
-### 6.6.1 Test description and applicability
-
-The purpose of the test is to measure the user experienced data throughput in both downlink and uplink in parallel while varying received radio signal quality (strength). The UE is placed in different stationary points inside the isolated cell. The test also includes the measurement of peak (maximum achievable) data throughput of UE located in the excellent radio conditions, and cell edge coverage data throughput of UE located at the cell edge in the poor radio conditions.
-
-### 6.6.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated) placed in different radio conditions as defined in Clause 4.6 –RSRP shall be considered in this case. The UE is gradually placed in different radio conditions from excellent (cell centre) to poor (cell edge – coverage limited cell edge in case of single cell scenario). Within the cell there shall be only one active UE in time simultaneously downloading data from and uploading data to the application (traffic) server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with sufficient capacity so as not to limit the expected data throughput. The test is suitable for both lab and field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio conditions of UE are initially set to excellent. The minimum coupling loss (see Clause 4.6) shall not be exceeded. The
-
-change in radio conditions of UE, from excellent through fair and good to poor, is achieved by increasing the attenuation of radio signal. The UE shall be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The test points with excellent, good, fair, and poor radio conditions (as defined in Clause 4.6) shall be identified inside the serving cell. The minimum coupling loss (see Clause 4.5) shall not be exceeded. The UE is initially placed in the cell center close to the SUT’s antenna(s), where excellent radio conditions (using RSRP as the metric as defined in Clause 4.6) shall be observed. The change in radio conditions is achieved by moving the UE inside the serving cell from cell centre (with excellent radio conditions) to cell edge (with poor radio conditions).
-
-The test setups of 4G, 5G NSA and 5G SA are illustrated in Figure 6-1.
-
-### 6.6.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated) is placed under excellent radio conditions as using RSRP thresholds as indicated in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The simultaneous downlink and uplink full-buffer UDP and TCP data transmission (see Clause 4.4) shall be verified by adjusting the connection settings (cabled environment) or UE position (OTA environment). The UE under excellent radio conditions that is achieving peak uplink and downlink user throughput shall see stable utilization of the highest possible MCS, downlink block size and MIMO rank (number of layers). These KPIs shall also be verified.
-- 4) The UE shall be turned off or set to airplane mode, to empty the buffers. The simultaneous downlink and uplink full-buffer UDP data transmissions are started. Both the UE and application server shall receive the data.
-- 5) All the required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below are measured and captured at UE, SUT and application server side using logging/measurement tools. The duration of test shall be at least 3 minutes when the throughput is stable. The location and position of the UE shall remain unchanged during the entire measurement duration (capture of log data).
-- 6) The capture of log data is stopped. The simultaneous downlink and uplink full-buffer UDP data transmissions are stopped.
-- 7) The radio conditions of UE are changed to good as defined by both SINR and RSRP in Clause 4.6, if possible. The steps 4 to 6 are repeated.
-- 8) The radio conditions of UE are changed to fair as defined by both SINR and RSRP in Clause 4.6, if possible. The steps 4 to 6 are repeated.
-- 9) The radio conditions of UE are changed to poor (cell edge) radio condition as defined by both SINR and RSRP in Clause 4.6, if possible. The steps 4 to 6 are repeated.
-- 10) [Optional] Steps 4 to 9 are repeated for simultaneous downlink and uplink full-buffer TCP data transmission.
-
-### 6.6.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-UE side (real or emulated):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, PUSCH BLER, PUSCH MCS (average sample per second)
-- DL MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-
-- Transmit power on PUSCH
-- Received downlink throughput (L1, and Application layers) (average sample per second)
-- Transmitted uplink throughput (Application layer) (average sample per second)
-- Channel utilization, i.e., Number allocated/occupied PRBs and Number of allocated/occupied slots in both downlink and uplink directions (average sample per second)
-
-SUT side (if capture of logs is possible):
-
-- Radio parameters such as PUSH SINR (average per second)
-
-Application server side:
-
-- Received uplink throughput (L1 and Application layers) (average sample per second)
-- Transmitted downlink throughput (Application layer) (average sample per second)
-
-When the UE is under excellent radio conditions (cell centre), the stable utilization of the highest possible MCS and transport block size in both uplink and downlink direction shall be observed and evaluated. The UE and SUT shall also receive the data with the minimum downlink and uplink BLER, respectively.
-
-Table 6-10 gives an example of the test results record (median and standard deviation from the captured samples shall be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G paths. The spectral efficiency (see Clause 4.8) shall be calculated for benchmarking and comparison to minimize the influence of different configured parameters such as bandwidth and TDD DL/UL ratio.
-
-**Table 6-10 Example record of test results (median and standard deviation from the captured samples)**
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|-------------------------------------------|----------------------------|-----------|-----------|---------------------|
-| | UDP / TCP | UDP / TCP | UDP / TCP | UDP / TCP |
-| Received L1 UL throughput [Mbps] | | | | |
-| L1 UL Spectral efficiency [bps/Hz] | | | | |
-| Received Application UL throughput [Mbps] | | | | |
-| Received L1 DL throughput [Mbps] | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| Received Application DL throughput [Mbps] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| PUSCH transmit power [dBm] | | | | |
-| DL MIMO rank | | | | |
-| DL MCS | | | | |
-| UL MCS | | | | |
-| DL RB number | | | | |
-| UL RB number | | | | |
-| DL PDSCH BLER [%] | | | | |
-| UL PUSCH BLER [%] | | | | |
-
-The following figures shall be also included in the test report, and the stable behavior shall be observed and evaluated.
-
-- Received UDP uplink throughput (L1 and Application layer) vs Time duration
-- Received UDP downlink throughput (L1 and Application layer) vs Time duration
-- UE RSRP vs Time duration
-- UE PDSCH SINR vs Time duration
-- Number of allocated/occupied downlink PRBs and Number of allocated/occupied downlink slots vs Time duration
-- Number of allocated/occupied uplink PRBs and Number of allocated/occupied uplink slots vs Time duration
-
-The bidirectional DL and UL throughputs shall be compared with unidirectional downlink (Clause 6.4) and uplink (Clause 6.5) throughputs. Assuming the same test conditions (radio conditions), the bidirectional and unidirectional throughputs are expected to be equal.
-
-The gap analysis shall be provided for the measured and the expected target downlink and uplink throughputs which can be calculated based on the procedures from Clause 6.1.
-
-## 6.7 Downlink coverage throughput (link budget)
-
-### 6.7.1 Test description and applicability
-
-The purpose of the test is to measure the downlink user data throughput (i.e., data transmitted from application (traffic) server to UE) when radio conditions of UE change gradually. Test is verified by moving UE from center to edge of the isolated cell on the main lobe of SUT's antenna until UE loses the coverage (call drop). Test assesses link adaptation and effect on scheduling, CQI, MCS, Number of layers (MIMO Rank) assignment etc. during the movement of UE from excellent radio conditions to poor radio conditions.
-
-### 6.7.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with UE (real or emulated) slowly moving in the main lobe of SUT's antenna out from cell centre to cell edge until UE loses the coverage (call drop). The drive route inside the cell shall be defined to cover the whole range of SINR values from excellent (cell center) to poor (cell edge) radio conditions as defined in Clause 4.6. Note that in case of single cell scenario SINR is in fact SNR as inter-cell interferences are not present. Within the cell there shall be only one active UE downloading UDP/TCP data from the application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with sufficient capacity so as not to limit the expected data throughput. The test is suitable for both lab and field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio conditions of UE are initially set to excellent. The minimum coupling loss (see Clause 4.6) shall not be exceeded. The movement of UE out from cell centre to cell edge can be achieved by gradually increasing the attenuation of radio signal to cover the whole range of SINR from excellent through good and fair to poor (as defined in Clause 4.6) until UE loses the coverage (call drop). The UE shall be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The drive route inside the isolated cell shall be defined to cover the whole range of SINR values from excellent (cell center) through good and fair to poor (cell edge) (as defined in Clause 4.6) until UE loses the coverage (call drop). The UE is placed in the centre of cell close to the radiated SUT's antenna(s). The minimum coupling loss (see Clause 4.5) shall not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route out from cell centre to cell edge until UE loses the coverage (call drop) – see Figure 6-2.
-
-
-
-Diagram illustrating the testing of link budget in the field setup. A base station (O-RU) is shown on the left, and a User Equipment (UE) is shown on the right. A dashed line with an arrow indicates the drive route of the UE, moving from the cell center towards the cell edge. The area covered by the antenna is shaded in light gray.
-
-Figure 6-2 Testing of link budget in the field setup
-
-### 6.7.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated) is placed under excellent radio condition (cell centre) using SINR thresholds as indicated in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The downlink full-buffer UDP and TCP data transmission (see Clause 4.4) from the application server shall be verified. The excellent radio conditions experiencing peak user throughput is identified with stable utilization of the highest possible downlink MCS, downlink transport block size and downlink MIMO rank (number of layers). These KPIs shall also be verified.
-- 4) The UE shall be turned off or set to airplane mode, to empty the buffers. The downlink full-buffer UDP data transmission from the application server to the UE is started. The UE shall receive the data from the application server.
-- 5) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at UE and Application server sides using logging/measurement tools.
-- 6) In the field setup, the UE is moved along the defined drive route out from cell centre (excellent radio conditions) to cell edge (poor radio conditions) on the main lobe of SUT’s antenna and with constant speed of around 30km/h until UE loses the coverage (call drop).
-- 7) In the lab setup, the attenuation between the antenna connectors of O-RU and UE is gradually increased until UE loses the coverage (call drop).
-- 8) The capture of log data is stopped. The downlink full-buffer UDP data transmission from the application server to UE is stopped.
-- 9) [Optional] Steps 5 to 7 are repeated for downlink full-buffer TCP data transmission.
-
-### 6.7.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-UE side (real or emulated):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-
-- Received downlink throughput (L1 and Application layers) (average sample per second)
-- Downlink transmission mode (average sample per second)
-- Channel utilization, i.e., Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-- GPS coordinates (latitude, longitude) in the field setup
-
-Application server side:
-
-- Transmitted downlink throughput (Application layer) (average sample per second)
-
-Initially when the UE is in the excellent radio conditions (cell centre), the stable utilization of the highest possible downlink MCS, downlink transport block size and downlink MIMO rank shall be observed and evaluated. The UE shall also receive the data with the minimum downlink BLER. As the UE moves out from excellent radio conditions (cell centre), the radio conditions of the UE change gradually from excellent through good and fair to poor (see Clause 4.6). The changing radio conditions may cause UE reporting lower CQI and MIMO rank which results in assignment of lower MCS and lower data throughput in downlink. Such a behavior shall be observed and evaluated.
-
-Note that the test results can be affected by the various coverage enhancing features (e.g., transmit/receive diversity) at SUT and/or at UE sides. The used coverage enhancement features shall be also listed in the test report.
-
-The following figures shall be included in the test report, and the behavior shall be evaluated. In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G paths. The spectral efficiency (see Clause 4.8) shall be calculated for benchmarking and comparison to minimize the influence of different configured parameters such as bandwidth and TDD DL/UL ratio.
-
-- Received UDP downlink throughput (L1 and Application layer) vs PDSCH SINR (all the samples as well as average curve with median values)
-- Received UDP L1 downlink spectral efficiency vs PDSCH SINR (all the samples as well as average curve with median values)
-- Cumulative distribution function of PDSCH SINR
-- Cumulative distribution function of PDSCH MCS
-- Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots vs PDSCH SINR (all the samples as well as average curve with median values)
-
-In the field environment, the cell coverage distance in meters (i.e., a straight line from the cell site) that corresponds to the cell-edge downlink application throughput of 6 Mbps for LTE and 50 Mbps for 5G NR shall be recorded.
-
-## 6.8 Uplink coverage throughput (link budget)
-
-### 6.8.1 Test description and applicability
-
-The purpose of the test is to measure the uplink user data throughput (i.e., data transmitted from UE to application (traffic) server) when radio conditions of UE change gradually. Test is verified by moving UE from center to edge of the isolated cell on the main lobe of SUT's antenna until UE loses the coverage (call drop). Test assesses link adaptation and effect on scheduling, uplink transmit power (power control), CQI, MCS, etc. during the movement of UE from excellent radio conditions to poor radio conditions.
-
-### 6.8.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with UE (real or emulated) slowly moving in the main lobe of SUT's antenna out from cell centre to cell edge until UE loses the coverage (call drop). The drive route inside the cell shall be defined to cover the whole range of RSRP values from excellent (cell center) to
-
-poor (cell edge) radio conditions as defined in Clause 4.6. Within the cell there shall be only one active UE uploading UDP/TCP data to application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with sufficient capacity so as not to limit the expected data throughput. The test is suitable for both lab and field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The radio conditions of UE are initially set to excellent. The minimum coupling loss (see Clause 4.6) shall not be exceeded. The movement of UE out from cell centre to cell edge can be achieved by gradually increasing the attenuation of radio signal to cover the whole range of RSRP from excellent through good and fair to poor (as defined in Clause 4.6) until UE loses the coverage (call drop). The UE shall be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The drive route inside the isolated cell shall be defined to cover the whole range of RSRP values from excellent (cell center) through good and fair to poor (cell edge) (as defined in Clause 4.6) until UE loses the coverage (call drop). The UE is placed in the centre of cell close to the radiated SUT's antenna(s). The minimum coupling loss (see Clause 4.5) shall not be exceeded. The change in radio conditions is achieved by moving the UE along the drive route out from cell centre to cell edge until UE loses the coverage (call drop) – see Figure 6-2.
-
-### 6.8.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated) is placed under excellent radio condition (cell centre) using RSRP thresholds as indicated in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The uplink full-buffer UDP and TCP data transmission (see Clause 4.4) from UE to the application server shall be verified. The UE under excellent radio conditions that is achieving peak user throughput should see stable utilization of the highest possible uplink MCS and uplink transport block size. These KPIs shall also be verified.
-- 4) The UE shall be turned off or set to airplane mode, to empty the buffers. The uplink full-buffer UDP data transmission from the application server to the UE is started. The application server shall receive data from the UE.
-- 5) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at UE, SUT and Application server sides using logging/measurement tools.
-- 6) In the field setup, the UE is moved along the defined drive route out from cell centre (excellent radio conditions) to cell edge (poor radio conditions) on the main lobe of SUT's antenna and with constant speed of around 30km/h until UE loses the coverage (call drop).
-- 7) In the lab setup, the attenuation between the antenna connectors of O-RU and UE is gradually increased until UE loses the coverage (call drop).
-- 8) The capture of log data is stopped. The uplink full-buffer UDP data transmission from UE to the application server is stopped.
-- 9) [Optional] Steps 4 to 7 are repeated for uplink full-buffer TCP data transmission.
-
-### 6.8.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-UE side (real or emulated):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-
-- PUSCH BLER, PUSCH MCS (average sample per second)
-- Transmit power on PUSCH (average sample per second)
-- Transmitted uplink throughput (Application layer) (average sample per second)
-- Channel utilization, i.e., Number allocated/occupied uplink PRBs and Number of allocated/occupied slots (average sample per second)
-- GPS coordinates (latitude, longitude) in the field setup
-
-SUT side (if capture of logs is possible):
-
-- Radio parameters such as PUSCH SINR (average per second)
-- PUSCH BLER (average per second)
-
-Application server side:
-
-- Received uplink throughput (L1 and Application layers) (average sample per second)
-
-Initially when the UE is in the excellent radio conditions (cell centre), the stable utilization of the highest possible uplink MCS and uplink transport block size shall be observed and evaluated. The SUT shall also receive the data with the minimum uplink BLER. As the UE moves out from excellent radio conditions (cell centre), the radio conditions of the UE change gradually from excellent through good and fair to poor (see Clause 4.6). With deteriorating channel conditions and increasing path loss, SUT shall start experiencing worse PUSCH/PUCCH BLER. To compensate the path loss and limit PUSCH/PUCCH BLER, SUT shall command the UE to increase PUSCH/PUCCH transmit power through closed loop Transmit Power Control (TPC) feature. The number of HARQ retransmissions may be also increased. If the power control does not reduce PUSCH/PUCCH BLER below a threshold, SUT shall schedule UE with lower MCS and lower MIMO rank in uplink which results in lower uplink data throughput. The UE moving further away from SUT can cause radio link failure and call drop (due to UL Max RLC retransmissions, failure in CQI decoding, low uplink SINR, etc.) which results in triggering of RRC connection re-establishment procedure. Such a behavior shall be observed and evaluated.
-
-Note that the test results can be affected by the various coverage enhancing features (e.g., transmit/receive diversity) at SUT and/or at UE sides. The used coverage enhancement features shall be also listed in the test report.
-
-The following figures shall be included in the test report, and the behavior shall be evaluated. In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G paths. The spectral efficiency (see Clause 4.8) shall be calculated for benchmarking and comparison to minimize the influence of different configured parameters such as bandwidth and TDD DL/UL ratio.
-
-- Received UDP uplink throughput (L1 and Application layer) vs RSRP (all the samples as well as average curve with median values)
-- Received UDP L1 uplink spectral efficiency vs RSRP (all the samples as well as average curve with median values)
-- PUSCH transmit power vs RSRP
-- Cumulative distribution function of RSRP
-- Cumulative distribution function of PUSCH MCS
-- Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots vs RSRP (all the samples as well as average curve with median values)
-
-In the field environment, the cell coverage distance in meters (i.e., a straight line from the cell site) that corresponds to the cell-edge uplink application throughput of 0.5 Mbps for LTE and 5 Mbps for 5G NR shall be recorded.
-
-## 6.9 Downlink aggregated cell throughput (cell capacity)
-
-### 6.9.1 Test description and applicability
-
-The purpose of the test is to validate the downlink aggregated cell throughput (downlink cell capacity) when the UEs are distributed in a uniform or non-uniform way inside a cell. This test also captures the influence of MU-MIMO feature on aggregated cell throughput. However, the test does not require support of MU-MIMO or massive MIMO. The aggregated cell throughput depends on the multiple factors like spatial distribution of UEs inside a cell, radio conditions of UEs, test configuration supported by both UE and SUT, etc. The test covers two spatial distribution scenarios of test UEs, i.e., uniform distribution and non-uniform distribution.
-
-### 6.9.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., an isolated cell without any inter-cell interference – see Clause 4.7) with 10 stationary UEs (real or emulated UEs) in total where 1 UE shall be placed in excellent radio conditions, 2 UEs in good radio conditions, 4 UEs in fair radio conditions and 3 UEs in poor radio conditions. The radio conditions are defined in Clause 4.6 – SINR (range of values) shall be considered in case of downlink. Note that in this case of single cell scenario, SINR is in fact SNR as inter-cell interferences are not present.
-
-The UEs can be distributed in the following spatial distribution scenarios (see Figure 6-3):
-
-- a) **uniform distribution:** ten UEs are placed uniformly with a spatial separation in both horizontal and vertical directions. Uniform distribution maximizes the potential of MU-MIMO, because the spatially separated UEs can be served by different beams at the same time. The channel experienced by each UE is spatially uncorrelated which reduces the inter-beam interference. In addition, selecting orthogonal precoders will further reduce the inter-beam interference.
-- b) **non-uniform distribution:** the UEs are grouped in clusters. The UEs in the cluster experience very similar radio conditions. In addition, the UEs in the cluster cannot be spatially separated and served by different beams at the same time. This distribution scenario restricts the scheduling options of SUT resulting in lower aggregated cell throughput.
-
-Figure 6-3 also shows impact of different types of beamforming (namely horizontal beamforming, vertical beamforming, and 3D beamforming) on aggregated cell throughput. The number of vertical beams is usually lower compared to horizontal beams, i.e., the number of UEs which can be spatially separated and served by different vertical beams at the same time is also lower resulting in lower aggregated cell throughput compared to horizontal beamforming. The typical scenario for vertical beamforming is a high-rise building where each floor can be covered by different vertical beams. For example, in Figure 6-3 a), UEs 2 and 4 are located in the coverage of the same horizontal beam thus cannot be served at the same time, while in Figure 6-3 b), the same UEs 2 and 4 are located in the coverage of two different vertical beams thus can be served at the same time.
-
-
-
-**Legend:**
-
-- Excellent radio conditions
-- Good radio conditions
-- Fair radio conditions
-- Poor radio conditions
-
-**Scenarios:**
-
-- a) uniform distribution with horizontal beamforming:** Shows 10 UEs distributed across three horizontal beams (beam 1, beam 2, beam 3). UEs are numbered 1-9 with one unnumbered UE.
-- b) uniform distribution with vertical beamforming:** Shows 10 UEs distributed across three vertical beams (beam 1, beam 2, beam 3).
-- c) uniform distribution with 3D beamforming:** Shows 10 UEs distributed across four 3D beams (beam 1, beam 2, beam 3, beam 4).
-- d) non-uniform distribution with horizontal beamforming:** Shows 10 UEs clustered non-uniformly across three horizontal beams (beam 1, beam 2, beam 3).
-
-Figure 6-3: Four diagrams (a, b, c, d) showing UE distribution scenarios in a cell with different beamforming types. A legend indicates radio conditions: Excellent (white), Good (green), Fair (yellow), and Poor (blue). White box icon Green box icon Yellow box icon Blue box icon
-
-**Figure 6-3 The distribution scenarios of UEs inside the cell using horizontal, vertical or 3D beamforming**
-
-Within the cell there shall be 10 active UEs in total downloading data from the application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with sufficient capacity so as not to limit the expected data throughput. The test is suitable for both lab and field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UEs can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. It is recommended to use a UE emulator to properly distribute the UEs inside a cell according to the selected distribution scenario. The minimum coupling loss (see Clause 4.6) shall not be exceeded. The UEs shall be placed inside an RF shielded box or RF shielded room if the UEs are not connected via cables.
-
-**Field setup:** The UEs shall be distributed inside a cell according to selected distribution scenario. The minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 6.9.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) Ten UEs (real or emulated) are placed inside a serving cell according to uniform distribution scenario, and in radio conditions using SINR thresholds as indicated in Clause 4.6 – 1 UE shall be placed in excellent radio conditions, 2 UEs in good radio conditions, 4 UEs in fair radio conditions and 3 UEs in poor radio conditions. The UEs are powered on and attached to the network.
-- 3) The downlink full-buffer UDP and TCP data transmissions (see Clause 4.4) from the application server to all UEs shall be verified.
-- 4) The UEs shall be turned off or set to airplane mode, to empty the buffers. The downlink full-buffer UDP data transmissions from the application server to all UEs are started. All UEs shall receive the data from application server.
-- 5) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at all UEs and Application server using logging/measurement tools. The duration of the test shall be at least 3 minutes when the throughput is stable. The location and position of the UEs shall remain unchanged during the entire measurement duration (capture of log data).
-- 6) The capture of log data is stopped. The downlink full-buffer UDP data transmission from the application server to UEs is stopped.
-- 7) [Optional] Steps 5 to 6 are repeated for downlink full-buffer TCP data transmissions.
-- 8) [Optional] Non-uniform spatial distribution scenario of UEs is setup. Steps 3 to 7 are repeated.
-
-### 6.9.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and Application layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e., Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-- GPS coordinates (latitude, longitude) in the field setup
-
-Application server side:
-
-- Transmitted downlink throughput (Application layer) (average sample per second)
-
-Table 6-11 gives an example of the test results record. The median and standard deviation shall be calculated from the captured samples for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G paths. The spectral efficiency (see Clause 4.8) shall be calculated for benchmarking and comparison to minimize the influence of different configured parameters such as bandwidth and TDD DL/UL ratio.
-
-**Table 6-11 Example record of test results (median and standard deviation is calculated from the captured samples)**
-
-| | |
-|--------------------------------------------------------|------------------------------------------------------------------------------------------|
-| Spatial distribution scenario [uniform/non-uniform] | |
-| For each UE (UE 1 to UE 10) - | |
-| | UDP / [optional] TCP |
-| Received L1 DL throughput [Mbps] | median and standard deviation |
-| L1 DL Spectral efficiency [bps/Hz] | median and standard deviation |
-| Received Application layer DL throughput [Mbps] | median and standard deviation |
-| UE RSRP [dBm] | median and standard deviation |
-| UE PDSCH SINR [dB] | median and standard deviation |
-| MIMO rank | median and standard deviation |
-| PDSCH MCS | median and standard deviation |
-| DL RB number | median and standard deviation |
-| PDSCH BLER [%] | median and standard deviation |
-| For entire cell | |
-| | UDP / [optional] TCP |
-| Aggregated cell L1 DL throughput [Mbps] | sum of Received L1 DL throughputs – sum of medians (UE 1 to UE 10) |
-| Aggregated cell Application layer DL throughput [Mbps] | sum of Received Application layer DL throughputs – sum of medians (UE 1 to UE 10) |
-| Aggregated DL RB number | sum of DL RB numbers – sum of medians (UE 1 to UE 10) |
-
-In addition, the used spatial distribution scenario(s) shall be properly described and depicted.
-
-The following figures shall be also included in the test report, and the stable behavior shall be observed and evaluated.
-
-- received aggregated UDP/TCP downlink throughput at UE side (L1 and Application layers) vs Time duration [sec]
-
-For each UE (UE1 to UE10):
-
-- UE PDSCH SINR vs Time duration [sec]
-- Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots vs Time duration [sec]
-
-## 6.10 Uplink aggregated cell throughput (cell capacity)
-
-### 6.10.1 Test description and applicability
-
-The purpose of the test is to validate the uplink aggregated cell throughput (uplink cell capacity) when the UEs are distributed in a uniform or non-uniform way inside a cell. This test also captures the influence of MU-MIMO feature on aggregated cell
-
-throughput. The aggregated cell throughput depends on the multiple factors like spatial distribution of UEs inside a cell, radio conditions of UEs, test configuration supported by both UE and SUT, etc. The test covers two spatial distribution scenarios of test UEs, i.e., uniform distribution and non-uniform distribution.
-
-### 6.10.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., an isolated cell without any inter-cell interference – see Clause 4.7) with 10 stationary UEs (real or emulated UEs) in total where 1 UE shall be placed in excellent radio conditions, 2 UEs in good radio conditions, 4 UEs in fair radio conditions and 3 UEs in poor radio conditions. The radio conditions are defined in Clause 4.6 – RSRP (range of values) shall be considered in case of uplink.
-
-The UEs can be distributed in the following spatial distribution scenarios (see Figure 6-3):
-
-- a) **uniform distribution:** ten UEs are placed uniformly with a spatial separation in both horizontal and vertical directions. Uniform distribution maximizes the potential of MU-MIMO, because the spatially separated UEs can be served by different beams at the same time. The channel experienced by each UE is spatially un-correlated which reduces the inter-beam interference.
-- b) **non-uniform distribution:** the UEs are grouped in clusters. The UEs in the cluster experience very similar radio conditions. In addition, the UEs in the cluster cannot be spatially separated and served by different beams at the same time. This distribution scenario restricts the scheduling options of SUT resulting in lower aggregated cell throughput.
-
-Within the cell there shall be 10 active UEs in total uploading data to the application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via a transport link with sufficient capacity so as not to limit the expected data throughput. The test is suitable for both lab and field environments.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a fading generator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. It is recommended to use a UE emulator to properly distribute the UEs inside a cell according to selected distribution scenario. The minimum coupling loss (see Clause 4.6) shall not be exceeded. The UEs shall be placed inside an RF shielded box or RF shielded room if the UEs are not connected via cables.
-
-**Field setup:** The UEs shall be distributed inside a cell according to selected distribution scenario. The minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 6.10.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) Ten UEs (real or emulated) in total are placed inside a serving cell according to uniform distribution scenario, and in radio conditions using RSRP thresholds as indicated in Clause 4.6 - 1 UE shall be placed in excellent radio conditions, 2 UEs in good radio conditions, 4 UEs in fair radio conditions and 3 UEs in poor radio conditions. The UEs are powered on and attached to the network.
-- 3) The uplink full-buffer UDP and TCP data transmissions (see Clause 4.4) from all UEs to application server shall be verified.
-- 4) The UEs shall be turned off or set to airplane mode, to empty the buffers. The uplink full-buffer UDP data transmissions from all UEs to the application server are started. The application server shall receive data from all UEs.
-- 5) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at all UEs, SUT and Application server using logging/measurement tools.
-
-- 6) The capture of log data is stopped. The uplink full-buffer UDP data transmissions from the UEs to application server are stopped.
-- 7) [Optional] Steps 4 to 6 are repeated for uplink full-buffer TCP data transmissions.
-- 8) [Optional] Non-uniform spatial distribution scenario of UEs is setup. Steps 3 to 7 are repeated.
-
-### 6.10.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PUSCH BLER, PUSCH MCS (average sample per second)
-- Transmit power on PUSCH (average sample per second)
-- Transmitted uplink throughput (Application layer) (average sample per second)
-- Channel utilization, i.e., Number allocated/occupied uplink PRBs and Number of allocated/occupied slots (average sample per second)
-- GPS coordinates (latitude, longitude) in the field setup
-
-SUT side (if capture of logs is possible):
-
-- Radio parameters such as PUSCH SINR (average per second)
-- PUSCH BLER (average per second)
-
-Application server side:
-
-- Received uplink throughput (L1 and Application layers) (average sample per second)
-
-Table 6-12 gives an example of the test results record (median and standard deviation from the captured samples shall be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G paths. The spectral efficiency (see Clause 4.8) shall be calculated for benchmarking and comparison to minimize the influence of different configured parameters such as bandwidth and TDD DL/UL ratio.
-
-**Table 6-12 Example record of test results (median and standard deviation from the captured samples)**
-
-| | For each UE (UE 1 to UE 10) |
-|-----------------------------------------------------|-----------------------------------------------------------|
-| | UDP / TCP |
-| Spatial distribution scenario [uniform/non-uniform] | |
-| Received L1 UL throughput [Mbps] | |
-| Aggregated cell L1 UL throughput [Mbps] | sum of Received L1 UL throughput (UE 1 to UE 10) |
-| L1 UL Spectral efficiency [bps/Hz] | |
-| Received Application UL throughput [Mbps] | |
-| Aggregated cell App. UL throughput [Mbps] | sum of Received App. UL throughput (UE 1 to UE 10) |
-| UE RSRP [dBm] | |
-| UE PDSCH SINR [dB] | |
-| PUSCH transmit power [dBm] | |
-
-| | |
-|-------------------------|--------------------------------------------|
-| | For each UE (UE 1 to UE 10) |
-| | UDP / TCP |
-| PUSCH MCS | |
-| UL RB number | |
-| Aggregated UL RB number | sum of UL RB number (UE 1 to UE 10) |
-| PUSCH BLER [%] | |
-
-In addition, the used spatial distribution scenario(s) shall be properly described and depicted.
-
-The following figures shall be also included in the test report, and the stable behavior shall be observed and evaluated.
-
-- received total UDP/TCP uplink throughput at Application server (L1 and Application layers) vs Time duration
-
-For each UE:
-
-- UE RSRP vs Time duration
-- number of allocated/occupied uplink PRBs and Number of allocated/occupied slots vs Time duration
-
-## 6.11 Impact of fronthaul latency on downlink peak throughput
-
-### 6.11.1 Test description and applicability
-
-The purpose of the test is to evaluate the user peak downlink throughput as a function of the fronthaul transport latency (i.e., one-way transmission delay between O-RU and O-DU at OpenFH (CUSM-plane interface), and to identify the maximum applicable fronthaul transport latency. Since the fronthaul transport latency corresponds with the distance (fiber length) between O-RU and O-DU, the results of test can be also used to identify the maximum distance (fiber length) with an acceptable degradation of user peak downlink throughput.
-
-### 6.11.2 Test setup and configuration
-
-The network setup is single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated UE) placed in the excellent radio condition as defined in Clause 4.6 - SINR shall be considered in case of downlink. Within the cell there shall be only one active UE downloading data from the application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via transport link with sufficient capacity not limiting the expected data throughput. The test is suitable for lab as well as field environment.
-
-The reference measurement points of the fronthaul latency (R1/R4 – Transmit/Receive interface at O-DU (CU-plane); R2/R3 – Receive/Transmit interfaces at O-RU (CU-plane)) [16] are shown in Figure 6-4. Transmission delay between O-RU and O-DU are specified as T12 (downlink direction) and T34 (uplink direction). Transmission delay shall be symmetrical and equal in both directions. The transmission delay encompasses only the time from when a bit leaves the sender (R1/ R3) until it is received at the receiver (R2/ R4).
-
-
-
-Figure 6-4: Definition of reference measurement points for fronthaul latency. The diagram shows an O-DU and an O-RU connected by two paths. The top path goes from R1 on the O-DU to R2 on the O-RU with latency T12. The bottom path goes from R4 on the O-DU to R3 on the O-RU with latency T34. Total latency T1a is defined as T12 + T2a, and total latency Ta4 is defined as Ta3 + T34. Reference points Ra and Rb are indicated on the O-RU side.
-
-Figure 6-4 Definition of reference measurement points for fronthaul latency [16]
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The minimum attenuation of radio signal shall be set to achieve the excellent radio conditions (SINR as defined in Clause 4.6), but the minimum coupling loss (see Clause 4.6) shall not be exceeded. The UE shall be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (SINR as defined in Clause 4.6) shall be observed. The minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-In this test, a method to vary the fronthaul latency shall be used. In both laboratory and field setups, Figure 6-5, the fronthaul latency may be modified by using of various lengths of fibre (assuming typical delay of fibre around 5 us per kilometre) or by using of a network impairment emulator inserted between O-RU and O-DU. It is necessary to know/measure the transmission delays produced by all fronthaul transport components between O-RU and O-DU to properly calculate the total fronthaul latency (T12/T34).
-
-
-
-Figure 6-5: The fronthaul transport latency test setups for 4G, 5G NSA and 5G SA. The diagram shows three test setups. The top setup is for 4G, showing a UE connected to a 4G O-RU, which is connected to an 'Inserted latency' block, which is connected to a 4G O-DU/CU. This is part of an 'O-RAN System under test'. The 4G O-DU/CU is connected via S1 to a 3GPP Core 4G EPC, which is connected to an Application server. The 'OpenFH latency' is measured between the 4G O-RU and the 4G O-DU/CU. The middle setup is for 5G NSA, showing a UE connected to both a 4G O-RU and a 5G O-RU. The 4G O-RU is connected to a 4G O-DU/CU via an 'Inserted latency' block, and the 5G O-RU is connected to a 5G O-DU/O-CU via an 'Inserted latency' block. Both are part of an 'O-RAN System under test'. The 4G O-DU/CU is connected via S1 to a 3GPP Core 4G EPC EN-DC NSA, and the 5G O-DU/O-CU is connected via X2 to the 4G O-DU/CU. The 'OpenFH latency' is measured between the O-RUs and the O-DUs/O-CUs. The bottom setup is for 5G SA, showing a UE connected to a 5G O-RU, which is connected to an 'Inserted latency' block, which is connected to a 5G O-DU/O-CU. This is part of an 'O-RAN System under test'. The 5G O-DU/O-CU is connected via NG to a 3GPP Core 5G SA, which is connected to an Application server. The 'OpenFH latency' is measured between the 5G O-RU and the 5G O-DU/O-CU.
-
-Figure 6-5 The fronthaul transport latency test setups of 4G, 5G NSA and 5G SA
-
-### 6.11.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated) is placed in the excellent radio condition (cell centre) as defined by SINR in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The downlink full-buffer UDP and TCP data transmission (see Clause 4.4) from the application server shall be verified. The excellent radio conditions experiencing peak user throughput is identified with stable utilization of the highest possible downlink MCS, downlink transport block size and downlink MIMO rank (number of layers). The utilization of these KPIs shall be also verified.
-- 4) The fronthaul latency (one-way transmission delay between O-DU and O-RU) shall be set to its minimum value.
-- 5) The UEs shall be turned off or set to airplane mode, to empty the buffers. The downlink full-buffer UDP data transmission from the application server to the UE is started. The UE shall receive the data from application server.
-- 6) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at UE and Application server using logging/measurement tools.
-- 7) The capture of log data is stopped. The downlink full-buffer UDP data transmission from the UE to application server is stopped.
-- 8) The fronthaul latency is increased by 20 us if no degradation of user peak downlink throughput was observed in the previous measurement. As soon as a degradation of user peak downlink throughput will be observed, the fronthaul latency is increased only by 5 us to capture fine-grained log data.
-- 9) Steps 5 to 8 are repeated until the total degradation of user peak downlink throughput is less than 30%. The KPIs measured with the minimum fronthaul latency are used as a baseline (100%) for calculation of the degradation.
-- 10) [Optional] Steps 4 to 9 are repeated for downlink full-buffer TCP data transmission.
-
-### 6.11.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1, and Application layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e., Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-- GPS coordinates (latitude, longitude) in the field setup
-
-Application server side:
-
-- Transmitted downlink throughput (Application layer) (average sample per second)
-
-When the UE is in the excellent radio conditions (cell centre), the stable utilization of the highest possible downlink MCS, downlink transport block size and downlink MIMO rank shall be observed and evaluated. The UE shall also receive the data with the minimum downlink BLER.
-
-Table 6-13 gives an example of the test results record (median and standard deviation from the captured samples shall be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G.
-
-**Table 6-13 The example of record of test results (median and standard deviation from the captured samples)**
-
-| | For each measured fronthaul latency value |
-|-----------------------------------------------------------|-------------------------------------------|
-| | UDP / TCP |
-| Total fronthaul transport latency (T12/T34) [us] | |
-| Received L1 DL throughput [Mbps] | |
-| Degradation of Received L1 DL throughput [%] # | |
-| Received Application DL throughput [Mbps] | |
-| UE RSRP [dBm] | |
-| UE RSRQ [dB] | |
-| UE PDSCH SINR [dB] | |
-| MIMO rank | |
-| PDSCH MCS | |
-| DL PRB number | |
-| PDSCH BLER [%] | |
-
-# The “Received L1 DL throughput” measured with the minim fronthaul latency is used as a baseline (100%) for calculation of the degradation
-
-The following figures shall be also included in the test report.
-
-- Received UDP/TCP downlink throughput (L1 and Application layers) vs Total fronthaul latency (T12/T34)
-
-## 6.12 Impact of fronthaul latency on uplink peak throughput
-
-### 6.12.1 Test description and applicability
-
-The purpose of the test is to evaluate the user peak uplink throughput as a function of the fronthaul transport latency (i.e., one-way transmission delay between O-RU and O-DU at OpenFH (CUSM-plane interface), and to identify the maximum applicable fronthaul transport latency. Since the fronthaul transport latency corresponds with the distance (fiber length) between O-RU and O-DU, the results of test can be also used to identify the maximum distance (fiber length) with an acceptable degradation of user peak uplink throughput.
-
-### 6.12.2 Test setup and configuration
-
-The network setup is single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated UE) placed in the excellent radio condition as defined in Clause 4.6 – RSRP shall be considered in case of uplink. Within the cell there shall be only one active UE uploading data to the application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via transport link with sufficient capacity not limiting the expected data throughput. The test is suitable for lab as well as field environment.
-
-The reference measurement points of the fronthaul latency (R1/R4 – Transmit/Receive interface at O-DU (CU-plane); R2/R3 – Receive/Transmit interfaces at O-RU (CU-plane)) [16] are shown in Figure 6-4. Transmission delay between O-RU and O-DU are specified as T12 (downlink direction) and T34 (uplink direction). Transmission delay shall be symmetrical and equal in both directions. The transmission delay encompasses only the time from when a bit leaves the sender (R1/ R3) until it is received at the receiver (R2/ R4).
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The minimum attenuation of radio signal shall be set to achieve the excellent radio conditions (RSRR as defined in Clause 4.6), but the minimum coupling loss (see Clause 4.6) shall not be exceeded. The UE shall be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRP as defined in Clause 4.6) shall be observed. The minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-In this test, a method to vary the fronthaul latency shall be used. In both laboratory and field setups, Figure 6-5, the fronthaul latency may be modified by using of various lengths of fibre (assuming typical delay of fibre around 5 us per kilometre) or by using of a network impairment emulator inserted between O-RU and O-DU. It is necessary to know/measure the transmission delays produced by all fronthaul transport components between O-RU and O-DU to properly calculate the total fronthaul latency (T12/T34).
-
-### 6.12.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated) is placed in the excellent radio condition (cell centre) as defined by RSRP in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The uplink full-buffer UDP and TCP data transmission (see Clause 4.4) from UE to the application server shall be verified. The excellent radio conditions experiencing peak user throughput is identified with stable utilization of the highest possible uplink MCS and uplink transport block size. The utilization of these KPIs shall be also verified.
-- 4) The fronthaul latency (one-way transmission delay between O-DU and O-RU) shall be set to its minimum value.
-- 5) The UEs shall be turned off or set to airplane mode, to empty the buffers. The uplink full-buffer UDP data transmission from UE to the application server is started. The application server shall receive data from UE.
-- 6) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at UE, SUT and Application server using logging/measurement tools.
-- 7) The capture of log data is stopped. The uplink full-buffer UDP data transmission from application server to UE is stopped.
-- 8) The fronthaul latency is increased by 20 us if no degradation of user peak uplink throughput was observed in the previous measurement. As soon as a degradation of user peak uplink throughput will be observed, the fronthaul latency is increased only by 5 us to capture fine-grained log data.
-- 9) Steps 5 to 8 are repeated until the total degradation of user peak uplink throughput is less than 30%. The KPIs measured with the minimum fronthaul latency are used as a baseline (100%) for calculation of the degradation.
-- 10) [Optional] Steps 4 to 9 are repeated for uplink full-buffer TCP data transmission.
-
-### 6.12.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PUSCH BLER, PUSCH MCS (average sample per second)
-- Transmit power on PUSCH (average sample per second)
-- Transmitted uplink throughput (Application layer) (average sample per second)
-
-- Channel utilization, i.e., Number allocated/occupied uplink PRBs and Number of allocated/occupied slots (average sample per second)
-- GPS coordinates (latitude, longitude) in the field setup
-
-SUT side (if capture of logs is possible):
-
-- Radio parameters such as PUSCH SINR (average per second)
-- PUSCH BLER (average per second)
-
-Application server side:
-
-- Received uplink throughput (L1 and Application layers) (average sample per second)
-
-When the UE is in excellent radio condition (cell centre), the stable utilization of the highest possible uplink MCS and uplink transport block size shall be observed and evaluated. The SUT shall also receive the data with the minimum uplink BLER.
-
-Table 6-14 gives an example of the test results record (median and standard deviation from the captured samples shall be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G.
-
-**Table 6-14 The example of record of test results (median and standard deviation from the captured samples)**
-
-| | For each measured fronthaul latency value |
-|-----------------------------------------------------------|-------------------------------------------|
-| | UDP / TCP |
-| Total fronthaul transport latency (T12/T34) [us] | |
-| Received L1 UL throughput [Mbps] | |
-| Degradation of Received L1 UL throughput [%] # | |
-| Received Application UL throughput [Mbps] | |
-| UE RSRP [dBm] | |
-| UE RSRQ [dB] | |
-| UE PDSCH SINR [dB] | |
-| PUSCH transmit power [dBm] | |
-| PUSCH MCS | |
-| UL PRB number | |
-| PUSCH BLER [%] | |
-
-# The “Received L1 UL throughput” measured with the minim fronthaul latency is used as a baseline (100%) for calculation of the degradation
-
-The following figures shall be also included in the test report.
-
-- Received UDP/TCP uplink throughput (L1 and Application layers) vs Total fronthaul latency (T12/T34)
-
-## 6.13 Impact of midhaul latency on downlink peak throughput
-
-### 6.13.1 Test description and applicability
-
-The purpose of the test is to evaluate the user peak downlink throughput as a function of the midhaul transport latency (i.e., one-way transmission delay between O-DU and O-CU at F1 interface). Since the midhaul transport latency corresponds with the distance (fiber length) between O-DU and O-CU, the results of test can be also used to identify the maximum distance (fiber length) with an acceptable degradation of user peak downlink throughput. Note that the midhaul transport exists only if O-DU and O-CU are not a combined entity, and the interface F1 between O-DU and O-CU is exposed. The test does not support LTE network architecture because an interface providing means for interconnecting LTE O-DU/DU and LTE CU has
-
-not been specified yet neither in 3GPP nor in O-RAN ALLIANCE. Note that W1 interface [33] has been specified only for 5G NSA Options 4 and 7 network architectures. The test is suitable only for 5G NSA (Option 3/3a/3x) and 5G SA network architectures as defined in 4.
-
-### 6.13.2 Test setup and configuration
-
-The network setup is single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated UE) placed in the excellent radio condition as defined in Clause 4.6 - SINR shall be considered in case of downlink. Within the cell there shall be only one active UE downloading data from the application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via transport link with sufficient capacity not limiting the expected data throughput. The test is suitable for lab as well as field environment.
-
-The midhaul latency encompasses only the time from when a bit leaves O-CU until it is received at O-DU.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The minimum attenuation of radio signal shall be set to achieve the excellent radio conditions (SINR as defined in Clause 4.6), but the minimum coupling loss (see Clause 4.6) shall not be exceeded. The UE shall be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT’s antenna(s), where excellent radio conditions (SINR as defined in Clause 4.6) shall be observed. The minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-In this test, a method to vary the midhaul transport latency shall be used. In both laboratory and field setups, Figure 6-6, the midhaul transport latency may be modified by using of a network impairment emulator or fiber spool or etc., inserted between O-DU and O-CU. It is necessary to know/measure the transmission delays produced by all midhaul transport components between O-DU and O-CU to properly calculate the total midhaul latency.
-
-
-
-Figure 6-6: The midhaul transport latency test setups of 5G NSA and 5G SA. The diagram shows two network architectures. The top part shows the 5G NSA setup where a UE connects to a 4G O-RU, which is connected via OpenFH to a 4G O-DU/CU. The 4G O-DU/CU connects to a 3GPP Core (4G EPC EN-DC NSA) via S1 and X2 interfaces. The 3GPP Core connects to an Application server via 3GPP services and Other services. The bottom part shows the 5G SA setup where a UE connects to a 5G O-RU/O-DU, which is connected via F1 to an Inserted latency block, which is then connected via F1 to a 5G O-CU. The 5G O-CU connects to a 3GPP Core (5G SA) via NG. The 3GPP Core connects to an Application server via 3GPP services and Other services. In both cases, the 'Midhaul latency' is indicated between the O-RU/O-DU and the O-CU. The 'O-RAN System under test' is highlighted with a dashed blue box in both diagrams.
-
-Figure 6-6 The midhaul transport latency test setups of 5G NSA and 5G SA
-
-### 6.13.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated) is placed in the excellent radio condition (cell centre) as defined by SINR in Clause 4.6. The UE is powered on and attached to the network.
-
-- 3) The downlink full-buffer UDP and TCP data transmission (see Clause 4.4) from the application server shall be verified. The excellent radio conditions experiencing peak user throughput is identified with stable utilization of the highest possible downlink MCS, downlink transport block size and downlink MIMO rank (number of layers). The utilization of these KPIs shall be also verified.
-- 4) The midhaul latency (one-way transmission delay between O-DU and O-CU) shall be set to its minimum value.
-- 5) The UEs shall be turned off or set to airplane mode, to empty the buffers. The downlink full-buffer UDP data transmission from the application server to UE is started. The UE shall receive the data from application server.
-- 6) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at UE and Application server using logging/measurement tools.
-- 7) The capture of log data is stopped. The downlink full-buffer UDP data transmission from application server is stopped.
-- 8) The midhaul latency is increased by 1000 us if no degradation of user peak downlink throughput was observed in the previous measurement. As soon as a degradation of user peak downlink throughput will be observed, the midhaul latency is increased only by 250 us to capture fine-grained log data.
-- 9) Steps 5 to 8 are repeated until the total degradation of user peak downlink throughput is less than 30%. The KPIs measured with the minimum fronthaul latency are used as a baseline (100%) for calculation of the degradation.
-- 10) [Optional] Steps 4 to 9 are repeated for downlink full-buffer TCP data transmission.
-
-### 6.13.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1, and Application layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e., Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-- GPS coordinates (latitude, longitude) in the field setup
-
-Application server side:
-
-- Transmitted downlink throughput (Application layer) (average sample per second)
-
-When the UE is in the excellent radio conditions (cell centre), the stable utilization of the highest possible downlink MCS, downlink transport block size and downlink MIMO rank shall be observed and evaluated. The UE shall also receive the data with the minimum downlink BLER.
-
-Table 6-15 gives an example of the test results record (median and standard deviation from the captured samples shall be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G.
-
-**Table 6-15 The example of record of test results (median and standard deviation from the captured samples)**
-
-| | For each measured midhaul latency value |
-|-----------------------------------------------------------|-----------------------------------------|
-| | UDP / TCP |
-| Total midhaul transport latency [us] | |
-| Received L1 DL throughput [Mbps] | |
-| Degradation of Received L1 DL throughput [%] # | |
-| Received Application DL throughput [Mbps] | |
-| UE RSRP [dBm] | |
-| UE RSRQ [dB] | |
-| UE PDSCH SINR [dB] | |
-| MIMO rank | |
-| PDSCH MCS | |
-| DL PRB number | |
-| PDSCH BLER [%] | |
-
-# The “Received L1 DL throughput” measured with the minim fronthaul latency is used as a baseline (100%) for calculation of the degradation
-
-The following figures shall be also included in the test report.
-
-- Received UDP/TCP downlink throughput (L1 and Application layers) vs Total midhaul latency.
-
-## 6.14 Impact of midhaul latency on uplink peak throughput
-
-### 6.14.1 Test description and applicability
-
-The purpose of the test is to evaluate the user peak uplink throughput as a function of the midhaul transport latency (i.e., one-way transmission delay between O-DU and O-CU at F1 interface). Since the midhaul transport latency corresponds with the distance (fiber length) between O-DU and O-CU, the results of test can be also used to identify the maximum distance (fiber length) with an acceptable degradation of user peak uplink throughput. Note that the midhaul transport exists only if O-DU and O-CU are not a combined entity, and the interfaces between O-DU and O-CU are exposed. The test does not support LTE network architecture because an interface providing means for interconnecting LTE O-DU/DU and LTE CU has not been specified yet neither in 3GPP nor in O-RAN ALLIANCE. Note that W1 interface [33] has been specified only for 5G NSA Options 4 and 7 network architectures. The test is suitable only for 5G NSA (Option 3/3a/3x) and 5G SA network architectures as defined in 4.
-
-### 6.14.2 Test setup and configuration
-
-The network setup is single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated UE) placed in the excellent radio condition as defined in Clause 4.6 - RSRP shall be considered in case of uplink. Within the cell there shall be only one active UE uploading data to application server. The application server shall be placed as close as possible to the core/core emulator and connected to the core/core emulator via transport link with sufficient capacity not limiting the expected data throughput. The test is suitable for lab as well as field environment.
-
-The midhaul latency encompasses only the time from when a bit leaves O-DU until it is received at O-CU.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The minimum attenuation of radio signal shall be set to achieve the excellent radio
-
-conditions (RSRP as defined in Clause 4.6), but the minimum coupling loss (see Clause 4.6) shall not be exceeded. The UE shall be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRP as defined in Clause 4.6) shall be observed. The minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-In this test, a method to vary the midhaul transport latency shall be used. In both laboratory and field setups, Figure 6-6, the midhaul transport latency may be modified by using of a network impairment emulator or fiber spool or etc., inserted between O-DU and O-CU. It is necessary to know/measure the transmission delays produced by all midhaul transport components between O-DU and O-CU to properly calculate the total midhaul latency.
-
-### 6.14.3 Test procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated) is placed in the excellent radio condition (cell centre) as defined by RSRP in Clause 4.6. The UE is powered on and attached to the network.
-- 3) The uplink full-buffer UDP and TCP data transmission (see Clause 4.4) from UE to the application server shall be verified. The excellent radio conditions experiencing peak user throughput is identified with stable utilization of the highest possible uplink MCS and uplink transport block size. The utilization of these KPIs shall be also verified.
-- 4) The midhaul latency (one-way transmission delay between O-DU and O-CU) shall be set to its minimum value.
-- 5) The UEs shall be turned off or set to airplane mode, to empty the buffers. The uplink full-buffer UDP data transmission from UE to application server is started. The application server shall receive the data from UE.
-- 6) All the required performance data (incl. the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at UE, SUT and Application server using logging/measurement tools.
-- 7) The capture of log data is stopped. The uplink full-buffer UDP data transmission from the UE to application server is stopped.
-- 8) The midhaul latency is increased by 1000 us if no degradation of user peak uplink throughput was observed in the previous measurement. As soon as a degradation of user peak uplink throughput will be observed, the midhaul latency is increased only by 250 us to capture fine-grained log data.
-- 9) Steps 5 to 8 are repeated until the total degradation of user peak uplink throughput is less than 30%. The KPIs measured with the minimum fronthaul latency are used as a baseline (100%) for calculation of the degradation.
-- 10) [Optional] Steps 4 to 9 are repeated for uplink full-buffer TCP data transmission.
-
-### 6.14.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be recorded and reported for the performance assessment.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, CQI, PDSCH SINR (average sample per second)
-- PUSCH BLER, PUSCH MCS (average sample per second)
-- Transmit power on PUSCH (average sample per second)
-- Transmitted uplink throughput (Application layer) (average sample per second)
-- Channel utilization, i.e., Number allocated/occupied uplink PRBs and Number of allocated/occupied slots (average sample per second)
-
-- GPS coordinates (latitude, longitude) in the field setup
-
-SUT side (if capture of logs is possible):
-
-- Radio parameters such as PUSCH SINR (average per second)
-- PUSCH BLER (average per second)
-
-Application server side:
-
-- Received uplink throughput (L1 and Application layers) (average sample per second)
-
-When the UE is in excellent radio condition (cell centre), the stable utilization of the highest possible uplink MCS and uplink transport block size shall be observed and evaluated. The SUT shall also receive the data with the minimum uplink BLER.
-
-Table 6-16 gives an example of the test results record (median and standard deviation from the captured samples shall be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR shall be reported. In case of 5G NSA and dual connectivity (EN-DC), the values shall be provided separately for both LTE and 5G.
-
-**Table 6-16 The example of record of test results (median and standard deviation from the captured samples)**
-
-| | For each measured midhaul latency value |
-|-----------------------------------------------------------|-----------------------------------------|
-| | UDP / TCP |
-| Total midhaul transport latency [us] | |
-| Received L1 UL throughput [Mbps] | |
-| Degradation of Received L1 UL throughput [%] # | |
-| Received Application UL throughput [Mbps] | |
-| UE RSRP [dBm] | |
-| UE RSRQ [dB] | |
-| UE PDSCH SINR [dB] | |
-| PUSCH transmit power [dBm] | |
-| PDSCH MCS | |
-| UL PRB number | |
-| PUSCH BLER [%] | |
-
-# The “Received L1 UL throughput” measured with the minimum fronthaul latency is used as a baseline (100%) for calculation of the degradation
-
-The following figures shall be also included in the test report.
-
-- Received UDP/TCP uplink throughput (L1 and Application layers) vs Total midhaul latency.
-
-## 6.15 End-to-end user plane latency
-
-### 6.15.1 Test description and applicability
-
-The purpose of the test is to evaluate the end-to-end user plane round-trip time (RTT), packet loss, and packet delay variation between UE and application server (see Clause 4.1.0). For this purpose, the Two-Way Active Measurement Protocol (TWAMP) as defined in RFC 5357 [49] is used. The advantage of round-trip time measurements is that accurate time sync between UE and application server is not required.
-
-The end-to-end RTT encompasses the following delays:
-
-- propagation delay – time it takes for packets to travel through transport medium (e.g. air, fiber optical cable)
-- processing delay - time taken by intermediate transport devices (e.g. routers, switches) to process the packets
-
-- queuing delay – time the packets spend in the queues
-
-Hence, the RTT is affected by transport medium, length of transport links, number and types of intermediate transport devices, etc. In addition, the RTT can be also affected by uplink pre-scheduling and DRX (Discontinuous Reception), but DRX is out of scope of this test. Uplink pre-scheduling involves allocating resources for uplink transmission in advance. This can reduce RTT by ensuring that the UE has immediate access to the uplink channel when needed.
-
-### 6.15.2 Test setup and configuration
-
-The network setup is single cell scenario (i.e. isolated cell without any inter-cell interference – see Clause 4.7) with stationary UE (real or emulated UE) placed in the excellent radio condition (to avoid retransmissions due to poor radio conditions) as defined in Clause 4.6. Within the cell there is only one active stationary UE. The application server should be placed as close as possible. The test is suitable for both lab and field environments.
-
-The end-to-end round-trip time is measured with TWAMP as defined by RFC 5357 [49]. The test shall be run with Ethernet frame sizes of 128B (resulting in a TWAMP payload size of 41B), 587B (resulting in a TWAMP payload size of 500B), and the maximum Ethernet frame size that does not cause fragmentation, respectively. Optionally, further test runs can be done with other payload sizes or, if supported by the TWAMP implementation, with IMIX (Internet Mix) as specified in RFC 6985 [50]. The recommended packet frequency is 10 packets per second. The chosen packet frequency shall be documented.
-
-NOTE: For the commonly used maximum Ethernet frame size of 1518B (equivalent to an MTU packet size of 1500B), the maximum TWAMP payload size is 1431B. This payload size shall not be exceeded to prevent fragmentation when using IPv4.
-
-The control-client and session-sender (commonly combined as a TWAMP-client), as specified in RFC 5357 [49], are connected to the UE and the server and session-reflector (commonly combined as a TWAMP-server), as specified in RFC 5357 [49], are connected to the application server.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions of UE can be modified by a variable attenuator/fading generator inserted between the antenna connectors of O-RU and UE. The minimum attenuation of radio signal should be set to achieve the excellent radio conditions (RSRP and SINR values as defined in Clause 4.6), but the minimum coupling loss (see Clause 4.6) shall not be exceeded. The UE should be placed inside RF shielded box or RF shielded room if the UE is not connected via cable.
-
-**Field setup:** The UE is placed in the centre of cell close to the radiated SUT's antenna(s), where excellent radio conditions (RSRP and SINR values as defined in Clause 4.6) shall be observed. The minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 6.15.3 Test Procedure
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The UE (real or emulated) is placed in excellent radio condition (cell centre) as defined by RSRP and SINR values in Clause 4.6. The UE is powered on and attached to the network. The user-plane connection with application server is verified.
-- 3) UL pre-scheduling features are disabled.
-- 4) TWAMP session is initiated and runs for at least 3 minutes. The TWAMP throughput shall not load the serving cell more than 5% in uplink and downlink. The RTT for each packet shall be captured.
-- 5) Step 4 is repeated at least 3 times.
-- 6) UL pre-scheduling is enabled. Steps 4 to 5 are repeated.
-- 7) Additionally, a UDP bidirectional traffic stream is introduced, so that the serving cell is 70% loaded in uplink and downlink. Steps 3 to 6 are repeated.
-
-### 6.15.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters should be recorded and reported for the performance assessment.
-
-- Test setup including parameters of transport links (length, media type, number and type of intermediate transport devices)
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, SINR (average sample per second)
-- Packet loss rate for each run (3 x 3 minutes) and payload size
-- Packet delay variation for each run (3 x 3 minutes) and payload size
-- Min/Max/Mean round-trip time for each run (3 x 3 minutes) and payload size
-
-The Table 6-17 gives examples of the test results record for unloaded and loaded scenarios. (mean and standard deviation from the captured samples should be calculated for each metric). In case of 5G SA and NSA, SS-RSRP and SS-SINR should be reported. In case of 5G NSA and dual connectivity (EN-DC), the values should be provided separately for both LTE and 5G.
-
-**Table 6-17: The example of record of test results for unloaded serving cell**
-
-| | | Unloaded serving cell | | 70% loaded serving cell | |
-|---------------------------|--------------------------------|-----------------------|----------------------|-------------------------|----------------------|
-| | | UL pre-scheduling off | UL pre-scheduling on | UL pre-scheduling off | UL pre-scheduling on |
-| Median UE RSRP [dBm] | | | | | |
-| Median UE SINR [dB] | | | | | |
-| 128B Ethernet frame size | Min RTT [ms] | | | | |
-| | Max RTT [ms] | | | | |
-| | Mean RTT [ms] | | | | |
-| | Standard deviation of RTT [ms] | | | | |
-| | Packet loss rate [%] | | | | |
-| 587B Ethernet frame size | Min RTT [ms] | | | | |
-| | Max RTT [ms] | | | | |
-| | Mean RTT [ms] | | | | |
-| | Standard deviation of RTT [ms] | | | | |
-| | Packet loss rate [%] | | | | |
-| 1426B Ethernet frame size | Min RTT [ms] | | | | |
-| | Max RTT [ms] | | | | |
-| | Mean RTT [ms] | | | | |
-| | Standard deviation of RTT [ms] | | | | |
-| | Packet loss rate [%] | | | | |
-
-# 7 Services tests
-
-## 7.0 Services tests introduction
-
-As a part of O-RAN testing, the present document is aimed at ensuring the O-RAN system can work in a telecom network, by inter-working with the other sub-systems to provide End-to-End services. This clause of the document outlines the services which should be tested to validate that the O-RAN system can be deployed and optimized to deliver great end user service experience in a telecom network.
-
-The services which need to be tested are broadly classified as data service(s), video streaming service(s), voice service(s), video calling service(s) in the eMBB slice and services supported using other slices like URLLC and mMTC. This clause of the document also tests different scenarios, such as handover, and different radio conditions, to assess the impact of these scenarios on the end user service(s) experience.
-
-## 7.1 Data services tests
-
-### 7.1.0 Data services test introduction
-
-Data services form one of the basic services supported as of today on a telecom network. This usage includes everything from web browsing, uploading/downloading content, to traffic generated by all the different applications on the end user device. These services form an integral part of data traffic on a telecom network. This clause is comprised of two test scenarios, which include web browsing and file upload/download.
-
-Along with the monitoring and validation of these services through user experience KPIs, the O-RAN systems should also be monitored. The end user service experience can also be impacted by some of the features available on the O-RAN system. Some of these features have been listed below. As a part of the data services testing, details of these features shall be included in the test report to provide a comprehensive view of the setup used for testing. If additional features or functionalities have been enabled during this testing that impact the end user experience, those shall be included in the test report as well.
-
-- Control Channel Beamforming
-- Connected Mode DRX
-- Massive MIMO
-- Coordinated Multi Point (DL and UL)
-- 256QAM Support (DL and UL)
-- SSB Power Boost
-- Beam Management
-- DL Common Channel Beamforming
-- Single-User MIMO Beamforming (DL and UL)
-- Multi-User MIMO Beamforming (DL and UL)
-- Single-User MIMO, TM Switching
-- Multi-User MIMO, TM Switching
-- TDD configuration support
-- RAN Slicing Framework (NR Low/Mid/High)
-- RACH Enhancements (PRACH Format 0)
-
-- PF (Proportional Fairness) Scheduling
-- QoS Scheduling
-- Minimal Bit Rate Scheduling
-- Link Adaptation (DL and UL)
-- Uplink Data Compression UDC
-- PUSCH Frequency Hopping
-
-Refer to the summary table below for a list of test cases and applicable technology.
-
-**Table 7-1: Data Service Test Case summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|----------------------|------------------|-----------------------|-----|----|
-| | | | LTE | NSA | SA |
-| Test ID | Data service | | | | |
-| 7.1.1 | Web Browsing | Service | Y | Y | Y |
-| 7.1.2 | File upload/download | Service | Y | Y | Y |
-
-### 7.1.1 Web Browsing
-
-##### 7.1.1.1 Test Description
-
-Web browsing forms an integral part of the 4G and 5G data network traffic, and this test case is applicable to both NSA and SA deployments. The testing shall be performed for each applicable technology supported by the system under test, according to table 7-34. HTTP is the protocol used for web browsing and this protocol can be transported over TCP/TLS or UDP/QUIC. These tests will include scenarios which will include both these protocols. Testing may be performed using HTTP/TLS/TCP or HTTP/QUIC/UDP or both these protocols as applicable.
-
-Web browsing KPI
-
-- DNS Resolution time – Time measured from when the client sends a DNS query to when the DNS responds with an IP address in milliseconds/seconds. This KPI should be recorded if DNS is used.
-- Time To First Byte (TTFB) – Time measured from when the client makes the HTTP request to when the first byte of the page is received in milliseconds/seconds.
-- Page Load Time – Time measured from when the client places the request to when the page is completely loaded in seconds.
-
-##### 7.1.1.2 Test Setup
-
-The SUT in this test case shall be O-eNB along with O-RU, O-DU and O-CU-CP/O-CU-UP for NSA deployments or the O-RU, O-DU and O-CU-CP/O-CU-UP for SA deployments. The O-RAN setup should support the ability to perform this testing in different radio conditions as defined in Clause 4.6. The 4G/5G core will be required to support the basic functionality to authenticate and register an end user device and to setup a PDN connection/PDU session. The 4G core will be used for O-RAN NSA testing, whereas 5G core will be used for O-RAN SA testing. The 4G/5G core may be a completely emulated, partially emulated or a real non-emulated core. The application server should support web browsing and be accessible from the 4G/5G core. This application server(s) should support protocols, such as HTTP/TCP or HTTP/QUIC as applicable. The end user device (UE) used for testing may be a real UE or an emulated one. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This could be a built-in capability of the emulated/non-emulated network elements and end user device(s) or external tool(s). If some of the network elements or
-
-application servers are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP shall have the correct configuration and software load. Tools which emulate latency shall be used and configured on the O-RAN system (between O-RU, O-DU and O-CU-CP/O-CU-UP) to emulate real-world deployment conditions as applicable. The end user device shall be configured with the correct user credentials to be able to register and authenticate with the O-RAN system and the 4G/5G core. The end user device also shall be provisioned with the correct application, such as the web browser to perform the tests. The 4G/5G core network shall be configured to support the end user device used for testing. This includes supporting registration, authentication and PDN connection/PDU session establishment for this end user device. The application server should be configured to support web browsing, along with support for HTTP/TCP and/or HTTP/QUIC protocols as applicable. Web browsing has several variables which can impact the KPIs and in order to reduce the impact of these variables and make the test outcomes consistent, it is recommended to set up a static web page of ~1.8-2MB size. The size of the web page is comparable to the average size of web pages on the public Internet. A static web page shall not change the content on repeated requests, thus making the test results consistent and repeatable. The locations where the radio conditions are excellent, good, fair and poor shall be identified within the serving cell.
-
-All the elements in the network, including the O-RAN system, 4G/5G core, and the application server should have the ability to capture traces to validate the successful execution of the test cases. The end user device should have the capability to capture traces/packets to calculate the web browsing KPIs. Optionally, the network may have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. All these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system, which shall be connected to the 4G/5G core which in turn shall have connectivity to the application server.
-
-##### 7.1.1.3 Test Methodology/Procedure
-
-Ensure the end user device, O-RAN system, 4G/5G core and the application server have all been configured as outlined in Clause 7.1.1.2. All traces and packet captures need to be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the end user device in excellent radio condition and ensure it registers with the 4G/5G core for data services.
-- 2) Once the registration is complete, the end user device shall establish a PDU session with the 5G core (SA) or PDN connection with the 4G core (NSA).
-- 3) Open the browser or application on the end user device and start a web browsing session to a web content using HTTP/TCP and/or HTTP/QUIC protocol. If the intent is to execute this test case for both protocols, then this step shall be performed twice, once for web content using HTTP/TCP followed by web content using HTTP/QUIC protocol.
-- 4) Validate the end user can get the content from the application server and view it on the end device. For every test collect the KPIs included in Clause 7.1.1.1.
-- 5) Clear the browser cache on the end user device between tests.
-- 6) Repeat the test multiple times (>10 times) and gather results.
-- 7) Repeat the above steps 1 through 6 for the good, fair and poor radio conditions.
-
-##### 7.1.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDN connection/PDU session setup by the end user device without any errors. This is a prerequisite before these tests can be validated.
-
-The end user device may be able to view the web browsing content for the web browsing test, with the content being viewable and readable. Use the packet captures to validate there is no packet drop or out of sequence packets which could impact customer experience and point to a misconfigured or flawed system.
-
-Calculate the web browsing KPIs included in Clause 7.1.1.1 and include it in the test report. In a lab setup, the use of DNS may be bypassed by using IP Addresses instead of domain names. However, the DNS resolution time KPI shall be recorded if a DNS is used for testing. The average range of values for these KPIs are included below for guidance, taking into consideration the size of the web page (~2MB). These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which could impact the KPIs, example: use of the Internet to connect to remote servers/hosts could add additional latency and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure within the SUT.
-
-- DNS Resolution time (conditional mandatory) – < 1 second
-- Time To First Byte (TTFB) – < 3 seconds
-- Page Load Time – < 12 seconds
-
-As a part of gathering test data and reporting, ensure the minimum configuration parameters (see Clause 4.3) are included in the test report. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput for the duration of the page download (L1 and L3 PDCP layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-The table below gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-2 Example of Test Report for Web Browsing Testing**
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|---------------------------------------------|----------------------------|-----------------------|-----------------------|-----------------------|
-| | HTTP over
TCP/QUIC | HTTP over
TCP/QUIC | HTTP over
TCP/QUIC | HTTP over
TCP/QUIC |
-| DNS Resolution Time (Conditional mandatory) | | | | |
-| Time To First Byte (TTFB) | | | | |
-| Page Load Time | | | | |
-| L1 DL throughput [Mbps] | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| L3 DL PDCP throughput [Mbps] | | | | |
-| Application DL throughput [Mbps] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| MIMO rank | | | | |
-| PDSCH MCS | | | | |
-| DL RB number | | | | |
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------|----------------------------|-----------------------|-----------------------|-----------------------|
-| | HTTP over
TCP/QUIC | HTTP over
TCP/QUIC | HTTP over
TCP/QUIC | HTTP over
TCP/QUIC |
-| UE CQI | | | | |
-| UE RSRQ | | | | |
-| UE PMI | | | | |
-| UE RSSI | | | | |
-| UE Buffer status | | | | |
-| UE Packet delay | | | | |
-| PDSCH BLER [%] | | | | |
-
-The web browsing experience can also be impacted by some of the features available (see Clause 7.1) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which could impact the end user's web browsing experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.1.2 File upload/download
-
-#### 7.1.2.1 Test Description
-
-File Transfer Protocol (FTP) is a simple application layer protocol used to transfer file between remote locations. FTP, along with different flavours of the protocols, form one of the fundamental methods to upload/download a file on the internet. This test case is applicable to both NSA and SA deployments and shall be performed twice, once for NSA deployment and once for SA deployment as applicable. This scenario tests the end user experience to upload/download files to/from an FTP server over an O-RAN system. The KPIs used to measure the user experience have been included below
-
-- 1) Download throughput – This is the average application layer throughput to download the file in kbps
-- 2) Upload throughput – This is the average application layer throughput to upload the file in kbps.
-- 3) Time taken to Download file – This is the time required to download the file in seconds.
-- 4) Time taken to Upload file – This is the time required to upload the file in seconds.
-
-#### 7.1.2.2 Test Setup
-
-The SUT in this test case would be O-eNB along with O-RU, O-DU and O-CU-CP/O-CU-UP for NSA deployments or the O-RU, O-DU and O-CU-CP/O-CU-UP for SA deployments. The O-RAN setup should support the ability to perform this testing in different radio conditions as defined in Clause 4.6. A 4G/5G core will be required with the basic functionality to authenticate and register an end user device and to setup a PDN connection/PDU session. The 4G core will be used for O-RAN NSA testing, whereas 5G core will be used for O-RAN SA testing. The 4G/5G core may be a completely emulated, partially emulated or a real non-emulated core. An FTP server acts as an application server for this test case. The end user device (UE) used for testing may be a real UE or an emulated one. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This could be a built-in capability of the emulated/non-emulated network element(s) or external tool(s). Optionally, if some of the network elements are located remotely, either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP shall have the correct configuration and software load. Tools which emulate latency shall be used and configured on the O-RAN system (between O-RU, O-DU and O-CU-CP/O-CU-UP) to emulate real-world deployment conditions. The end user device shall be configured with the correct user credentials to be able to register and authenticate with the O-RAN system and the 4G/5G core. The end user device also shall be provisioned with the correct application, such as an FTP client, to upload and download files. The 4G/5G core network shall be configured to support the end user device used for testing. This includes supporting registration, authentication and PDN connection/PDU session establishment for this end user device. The FTP server should host large files (>1 GB) which can be used for the
-
-download/upload testing. The locations where the radio conditions are excellent, good, fair and poor shall be identified within the serving cell.
-
-All the elements in the network, such as the O-RAN system, 4G/5G core and the application server should have the ability to capture traces to validate the successful execution of the test cases. The end user device should have the capability to capture traces/packets to calculate the file upload/download KPIs. Optionally, the network may have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. All these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system, which shall be connected to the 4G/5G core which in turn shall have connectivity to the application server.
-
-#### 7.1.2.3 Test Methodology/Procedure
-
-Ensure the end user device, O-RAN system, 4G/5G core and the FTP server have all been configured as outlined in Clause 7.1.2.2. All traces and packet captures need to be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the end user device in excellent radio condition and ensure it registers with the 4G/5G core for data services.
-- 2) Once the registration is complete, the end user device shall establish a PDU session with the 5G core (SA) or PDN connection with the 4G core (NSA).
-- 3) Open the application on the end user device and upload the test file to the FTP server. Make a note of the time taken to upload the file and the average upload throughput.
-- 4) Next use the same application on the end user device to download a different test file from the FTP server. Make a note of the time taken to download the file and the average download throughput.
-- 5) Clear all the buffers and caches on the client and the server. Delete the test files – downloaded file on the client and the uploaded file on the FTP server.
-- 6) Repeat the test multiple times (>10 times) and gather results.
-- 7) Repeat the above steps 1 through 6 for the good, fair and poor radio conditions.
-
-#### 7.1.2.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDN connection/PDU session setup by the end user device without any errors. This is a prerequisite before these tests can be validated.
-
-Validate the end user device can upload/download the complete file to/from the FTP server without interruption. Validate there isn't a drop in throughput while uploading/downloading the file to/from the FTP server. Use the packet captures to validate there is no packet drop or out of sequence packets which could impact customer experience and point to a misconfigured or flawed system.
-
-Calculate the file upload/download KPIs included in Clause 7.1.1.1 and include them in the test report. There are no target values for these KPIs as they are dependent on multiple factors used in the test configuration. Some comments on each of the KPIs are included below.
-
-- Download throughput – This value should be comparable to the results of the downlink throughput test performed in Clause 6.2 and Clause 6.4.
-- Upload throughput – This value should be comparable to the results of the uplink throughput test performed in Clause 6.3 and Clause 6.5.
-- Time taken to Download file – This value should be comparable to the value calculated using the formula included below
-- Time taken to Upload file – This value should be comparable to the value calculated using the formula included below.
-
-$$time\ taken\ to\ upload/download\ [seconds] = \frac{Size\ of\ file\ in\ GB \times 1000 \times 1000 \times 8}{uplink/downlink\ throughput\ [kbps]}$$
-
-These KPI values included in Clause 7.1.2.1 shall be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and L3 PDCP layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-The table below gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-3 Example Test Report for File Upload/Download Testing**
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------------------------|----------------------------|-------------------------|-------------------------|-------------------------|
-| | File
Upload/Download | File
Upload/Download | File
Upload/Download | File
Upload/Download |
-| Upload/Download Throughput (kbps) | | | | |
-| Time taken to Upload/Download File | | | | |
-| L1 DL throughput [Mbps] | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| L3 DL PDCP throughput [Mbps] | | | | |
-| Application DL throughput [Mbps] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| MIMO rank | | | | |
-| PDSCH MCS | | | | |
-| DL RB number | | | | |
-| UE CQI | | | | |
-| UE RSRQ | | | | |
-| UE PMI | | | | |
-| UE RSSI | | | | |
-| UE Buffer status | | | | |
-| UE Packet delay | | | | |
-| PDSCH BLER [%] | | | | |
-
-The file upload/download experience can also be impacted by some of the features available (see Clause 7.1) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which could impact the end user's file upload/download experience should be included in the test report to provide a comprehensive view of the testing.
-
-## 7.2 Video streaming tests
-
-### 7.2.0 Video streaming tests introduction
-
-Video makes up a major part of the internet traffic today and there is a similar trend even on the mobile data traffic. Mobile video accounts for close to two-thirds of the total mobile data traffic and is expected to increase in the coming years. Video streaming has evolved over time with newer and better audio and video codecs. The protocols used to stream the video packets has also been evolving over time, with Adaptive Bit Rate (ABR) being the most common protocol used for streaming video on the internet today. There are multiple flavours of ABR, but at the crux they all use HTTP protocol over TCP/TLS or UDP/QUIC to transfer audio-video packets to a client. A video streaming server which supports ABR hosts multiple versions of the same video content with each version of the video being encoded at different resolution and quality, hence different bit rates. The client uses the ABR protocol to get the list of all available versions of the requested video content and picks the best video content based on the available bandwidth on the client side. The ABR client continuously monitors the network condition and dynamically adjusts the quality and resolution of the video stream to match the available bandwidth.
-
-The ABR protocol provides the user with the best video streaming experience based on the available bandwidth between the client and the content server. This however adds a lot of variables to the streaming session
-
-- An ABR client may start with a lower resolution video and progressively switch to higher resolution video as it better estimates the bandwidth available at the client.
-- An ABR client might notice an improvement in the bandwidth and request a higher resolution/quality video content, thus improving the video quality mid-stream.
-- An ABR client might notice a degradation in the bandwidth and request a lower resolution/quality video content, thus deteriorating the video quality mid-stream.
-
-These variables make it challenging to quantify the video streaming experience of an end user. There have been many tools and organizations which have defined different methods and algorithms to quantify the end user experience including QoE (Quality of Experience), SVQ (Streaming Video Quality), Video Multimethod Assessment Fusion (VMAF) etc. In this document we recommend using the Mean Opinion Score (MOS) as defined by ITU P.1203.3 to quantify the quality of experience of the end user. This mechanism however limits the testing to H.264 video encoder with a resolution of HD quality (1080p resolution – 1920 x 1080 pixels) or below.
-
-#### Video Streaming KPIs
-
-- Video start time or Time to load first video frame – Time from when the video was selected to play to when the video starts playing in seconds.
-- Number of video stalls/buffering (Optional) – Number of times the video stalled or started buffering during the course of video streaming. This KPI has already been considered by ITU P.1203.3 to provide a cumulative MOS score.
-- Duration of stalls in the video (Optional) – The cumulative duration of all the stalls during the course of video streaming in seconds. This KPI has already been considered by ITU P.1203.3 to provide a cumulative MOS score.
-- Video MOS score – MOS score for the video streaming session as defined by ITU P.1203.3.
-
-Along with the monitoring and validation of these services using user experience KPIs, the O-RAN systems also shall be monitored. The end user service experience can also be impacted by some of the features available on the O-RAN system. Some of these features have been included in the list below. As a part of the video streaming testing, details of these features shall be included in the test report to provide a comprehensive view of the setup used for testing. If additional features or functionalities have been enabled during this testing that impact the end user experience, those shall be included in the test report as well.
-
-- NR to LTE PS Redirection/Cell Reselection/Handover
-- Intra-frequency / Inter-Frequency Cell Reselection/Handover
-- NR Coverage-Triggered NR Session Continuity
-- LTE-NR & NR-NR Dual Connectivity and NR Carrier Aggregation
-
-- Direct data forwarding between NG-RAN and E-UTRAN nodes for inter-system mobility
-- Standard QCI Bearers Support
-- Control Channel Beamforming
-- Massive MIMO
-- 256QAM Support (DL and UL)
-- Beam Management
-- TDD configuration support
-- PF (Proportional Fairness) Scheduling
-- Link Adaptation (DL and UL)
-- Application Aware QoS
-
-Please see below summary table of test cases and applicable technology.
-
-**Table 7-4: Video Streaming Service Test Case Selection summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|------------------------------------------------------------------------------------------|------------------|-----------------------|-----|-----|
-| | | | LTE | NSA | SA |
-| Test ID | Video Streaming | | | | |
-| 7.2.1 | Video Streaming – Stationary Test | Service | Y | Y | Y |
-| 7.2.2 | Video Streaming – Handover between same Master eNB but different O-RUs – Intra O-DU | Service | N/A | Y | N/A |
-| 7.2.3 | Video Streaming – Handover between same MeNB but different O-DUs – Intra O-CU/Inter O-DU | Service | N/A | Y | N/A |
-| 7.2.4 | Video Streaming – Handover between same MeNB but different O-CUs – Inter O-CU | Service | N/A | Y | N/A |
-| 7.2.5 | Video Streaming – Handover between different MeNB while staying connected to same SgNB | Service | N/A | Y | N/A |
-
-### 7.2.1 Video Streaming – Stationary Test
-
-#### 7.2.1.0 Test Overview
-
-This scenario tests the video experience of a user streaming video over 4G and 5G network when the end user device is stationary.
-
-##### 7.2.1.1 Test Description
-
-Majority of the video streaming on the internet today uses ABR (Adaptive Bit Rate) streaming using HTTP protocol over TCP/TLS or UDP/QUIC. Within this test, the user’s video streaming experience when connected to a telecom network over O-RAN system. This test case is applicable to both NSA and SA deployment, and will shall be performed twice, once for NSA deployment and once for SA deployment as applicable.
-
-##### 7.2.1.2 Test Setup
-
-The SUT in this test case would be 4G O-eNB along with 5G E2E system (O-RU, O-DU and O-CU-CP/O-CU-UP) for NSA deployments or the 5G E2E system (O-RU, O-DU and O-CU-CP/O-CU-UP) for SA deployments. The O-RAN setup should support the ability to perform this testing in different radio conditions as defined in Clause 4.6. A 4G/5G core will be required to support the basic functionality to authenticate and register an end user device in order to setup a PDN connection/PDU
-
-session. The 4G core will be used for O-RAN NSA testing, whereas 5G core will be used for O-RAN SA testing. The 4G/5G core may be a completely emulated, partially emulated or a real non-emulated core. The application server(s) for this testing should support video streaming using ABR protocol over HTTP/TCP and/or HTTP/QUIC as applicable. The end user device (UE) used for testing may be a real UE or an emulated one. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This could be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements or the application server are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The O-eNB and (O-RU, O-DU and O-CU-CP/O-CU-UP) shall have the correct configuration and software load. Tools which emulate latency shall be used and configured on the O-RAN system (between O-RU, O-DU and O-CU-CP/O-CU-UP) to emulate real-world deployment conditions. The end user device shall be configured with the correct user credentials to be able to register and authenticate with the O-RAN system and the 4G/5G core. The end user device also shall be provisioned with the correct application, such as a video streaming client, to perform the tests. The 4G/5G core network shall be configured to support the end user device used for testing. This includes supporting registration, authentication, and PDN connection/PDU session establishment for this end user device. The locations where the radio conditions are excellent, good, fair and poor shall be identified within the serving cell.
-
-All the elements in the network, including the O-RAN system, 4G/5G core, and the application server should have the ability to capture traces to validate the successful execution of the test cases. The end user device should have the capability to capture traces/packets to calculate the video streaming KPIs. Optionally, the network may have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. All these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system, O-RAN system shall be connected to the 4G/5G core which in turn shall have connectivity to the application server.
-
-##### 7.2.1.3 Test Methodology/Procedure
-
-Ensure the end user device, O-RAN system, 4G/5G core and the application server have all been configured as outlined in Clause 7.2.1.2. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the end user device in excellent radio condition and ensure it registers with the 4G/5G core for data services.
-- 2) Once the registration is complete, the end user device shall establish a PDN Session with the 4G core or PDU session with the 5G core.
-- 3) Open the video streaming client on the end user device and start a video streaming session over HTTP/TCP protocol and let the video stream for at least 120 seconds.
-- 4) Optionally, repeat the test by streaming a video session over the HTTP/QUIC protocol and stream the video content for at least 120 seconds.
-- 5) Repeat the test multiple times (> 10 times) and gather results.
-- 6) Repeat the above steps 1 through 5 for the good, fair and poor radio conditions.
-
-##### 7.2.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDN connection/PDU session setup by the end user device without any errors. This is a prerequisite before these tests can be validated.
-
-Validate the end user device can start streaming the video without delays and watch the video content. Ensure the video can stream without stalls or intermittent buffering. Use the packet captures to validate there is no packet drop or out of sequence packets which could impact customer experience and point to a misconfigured or flawed system.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which could impact the KPIs, example: use of the Internet to connect to remote servers/hosts could add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure within the SUT.
-
-- Video Start time or Time to load first video frame – ~1.5 seconds
-- Number of video stalls/buffering – < 1
-- Duration of stalls in the video – < 5 seconds
-- Video MOS Score – > 3.5
-
-The values for the end user video streaming KPIs defined in Clause 7.2 shall be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report for the testing performed in different radio conditions to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-The table below gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-5 Example Test Report for Video Streaming – Stationary Test**
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|
-| | Video Streaming
over TCP/QUIC | Video Streaming
over TCP/QUIC | Video Streaming
over TCP/QUIC | Video Streaming
over TCP/QUIC |
-| Video Start Time | | | | |
-| Number of Video Stalls/buffering | | | | |
-| Duration of stalls in the video | | | | |
-| Video MOS Score | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| MIMO rank | | | | |
-| PDSCH MCS | | | | |
-| DL RB number | | | | |
-| UE CQI | | | | |
-| UE RSRQ | | | | |
-| UE PMI | | | | |
-| UE RSSI | | | | |
-| UE Buffer status | | | | |
-| UE Packet delay | | | | |
-| PDSCH BLER [%] | | | | |
-
-The end user video streaming experience can also be impacted by some of the features available (see Clause 7.2) on the 4G O-eNB and 5G system (O-RU, O-DU and O-CU-CP/O-CU-UP). The details of these features, along with any other
-
-features/functionality which could impact the end user's video streaming experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.2.2 Video Streaming – Handover between same Master eNB but different O-RUs – Intra O-DU
-
-#### 7.2.2.0 Test Overview
-
-This test scenario validates the user's video streaming experience when the end user device (UE) is connected over NSA to a 4G core and is in the process of a handover between two O-RAN subcomponents (two O-RUs) on the Secondary gNB while remaining connected to the same Master eNB. The VoLTE or VoNR services cannot be used to test handover of secondary gNB, video streaming is used for this testing. This test scenario is only applicable in an NSA deployment.
-
-##### 7.2.2.1 Test Description
-
-The 5G O-RAN system has multiple sub-components, including the O-RU, O-DU and the O-CU-CP/O-CU-UP. This setup leads to multiple handover scenarios when the O-RAN system is connected as a Secondary gNB in an NSA deployment. This scenario tests the end user's video streaming experience when the end user device is connected over NSA to the 4G core and performs a handover between O-RUs which are connected to the same O-DU (and O-CU-CP/O-CU-UP) on the Secondary gNB – Intra O-DU handover. The end user device remains connected to the same Master eNB through the entire handover process. This handover is agnostic to the 4G core as the handover occurs on the O-RAN system. This test assesses the impact of the video streaming service on the end user device in this handover scenario by monitoring the end user video streaming KPIs included in Clause 7.2. This test case streams video using ABR protocol over HTTP/TCP and/or HTTP/QUIC.
-
-##### 7.2.2.2 Test Setup
-
-The SUT in this test case are the Master eNB and a Secondary gNBs. The Master eNB will be an O-eNB and the Secondary gNB will constitute of a pair of O-RUs – O-RU1 and O-RU2, which will connect to the same O-DU and O-CU-CP/O-CU-UP. The O-eNB, O-RUs, O-DU and O-CU-CP/O-CU-UP shall comply with the O-RAN specifications. A 4G core will be required to support the basic functionality to authenticate and register an end user device, to set up a PDN connection. The 4G core may be a completely emulated, partially emulated or a real non-emulated core. The application server(s) for this testing should support video streaming using ABR protocol over HTTP/TCP and/or HTTP/QUIC as applicable. The end user device (UE) used for testing may be a real UE or an emulated one. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This could be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements or application server(s) are located remotely, either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The O-eNB shall have the correct configuration and software load. The pair of O-RUs (O-RU1 and O-RU2) shall be connected to the O-DU and O-CU-CP/O-CU-UP and all the components shall have the correct configuration and software load. Tools which emulate latency shall be used and configured on the O-RAN system (between O-RU, O-DU and O-CU-CP/O-CU-UP) to emulate real-world deployment conditions. The end user device shall be configured with the correct user credentials to be able to register and authenticate with the O-RAN system and the 4G core. The end user device also shall be provisioned with the correct application, such as a video streaming client to perform the tests. The 4G core network shall be configured to support the end user device used for testing. This includes supporting registration, authentication and PDN connection establishment for this end user device.
-
-All the elements in the network, including the O-RAN system, 4G core, and the application server should have the ability to capture traces to validate the successful execution of the test cases. The end user device should have the capability to capture traces/packets to calculate the video streaming KPIs. Optionally, the network may have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. All these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system(O-eNB, O-RUs, O-DU and O-CU-CP/O-CU-UP), O-RAN system shall be connected to the 4G core which in turn shall have connectivity to the application server.
-
-##### 7.2.2.3 Test Methodology/Procedure
-
-Ensure the end user device, O-RAN system, 4G core, and the application server have all been configured as outlined in Clause 7.2.2.2. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the end user device and ensure it registers with the 4G core for data services over NSA by connecting over the O-eNB as Master eNB and O-RU1 of the O-RAN system as secondary gNB.
-- 2) Once the registration is complete, the end user device shall establish a PDN connection with the 4G core.
-- 3) Open the video streaming client on the end user device and start a streaming session over HTTP/TCP protocol.
-- 4) Once the video streaming session has started, move the device so it can handover from O-RU1 to O-RU2 on the Secondary gNB while it continues to use the O-eNB as the Master eNB.
-- 5) Allow the end user device to stream video through the entire handover process. Measure the KPIs included in Clause 7.2 for this video streaming session.
-- 6) Optionally, repeat steps 1 through 5 for a video streaming session which uses HTTP/QUIC protocol for streaming.
-- 7) Repeat the test multiple times (> 10 times) and gather results.
-
-##### 7.2.2.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDN connection setup by the end user device without any errors using the Master eNB and O-RU1, O-DU and O-CU-CP/O-CU-UP as the Secondary gNB. This is a prerequisite before these tests can be validated.
-
-Validate the end user device can start streaming the video without delays and watch the video content through the entire handover process. Ensure there are no stalls, downgrading of video quality or intermittent buffering of the video content, especially during the handover process. Use the packet captures to validate there are no packet drops or out of sequence packets which could impact customer experience and point to a misconfigured or flawed system.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which could impact the KPIs, example: use of the Internet to connect to remote servers/hosts could add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure within the SUT.
-
-- Video Start time or Time to load first video frame – ~1.5 seconds
-- Number of video stalls/buffering – < 1
-- Duration of stalls in the video – < 5 seconds
-- Video MOS Score – > 3.5
-
-The values for the end user video streaming KPIs defined in Clause 7.2 shall be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and L3 PDCP layers) (average sample per second)
-- Downlink transmission mode
-
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-The table below gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-6 Example Test Report for Video Streaming – Handover between same Master eNB but different O-RUs – Intra DU handover**
-
-| | Video Streaming over HTTP/TCP | Video Streaming over HTTP/QUIC |
-|------------------------------------|-------------------------------|--------------------------------|
-| Video Start Time | | |
-| Number of Video Stalls/buffering | | |
-| Duration of stalls in the video | | |
-| Video MOS Score | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user video streaming experience can also be impacted by some of the features available (see Clause 6.2) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which could impact the end user’s video streaming experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.2.3 Video Streaming – Handover between same MeNB with different O-DUs – Intra O-CU/Inter O-DU
-
-#### 7.2.3.0 Test Overview
-
-This test scenario validates the user’s video streaming experience when the UE is connected over NSA to a 4G core and the UE is in the process of a handover between two O-RAN subcomponents (two O-RUs and O-DUs) on the Secondary gNB while remaining connected to the same Master eNB. The VoLTE or VoNR services cannot be used to test handover of secondary gNB, video streaming is used for this testing. This test scenario is only applicable in an NSA deployment.
-
-##### 7.2.3.1 Test Description
-
-The 5G O-RAN system has multiple sub-components, including the O-RU, O-DU and the O-CU-CP/O-CU-UP. This setup leads to multiple handover scenarios when the O-RAN system is connected as a Secondary gNB in an NSA deployment. This scenario tests the end user’s video streaming experience when the end user device is connected over NSA to the 4G core and
-
-performs a handover between O-RUs which are connected to different O-DUs, which in turn are connected to the same O-CU-CP/O-CU-UP on the Secondary gNB – Intra O-CU/Inter O-DU handover. The end user device remains connected to the same Master eNB through the entire handover process. This handover is agnostic to the 4G core as the handover occurs on the O-RAN system. This test assesses the impact of the video streaming service on the end user device in this handover scenario by monitoring the KPIs included in Clause 7.2 This test case streams video using ABR protocol over HTTP/TCP and/or HTTP/QUIC.
-
-##### 7.2.3.2 Test Setup
-
-The SUT in this test case shall be the Master eNB and a Secondary gNBs. The Master eNB will be an O-eNB and the Secondary gNB will constitute of a pair of O-RUs – O-RU1 and O-RU2, which are connected to a pair of O-DUs -DU1 and O-DU2, which are connected to the same O-CU-CP/O-CU-UP. The O-eNB, O-RUs, O-DUs and O-CU-CP/O-CU-UP shall comply with the O-RAN specifications. The 4G core will be required to support the basic functionality to authenticate and register an end user device, to set up a PDN connection. The 4G/5G core may be a completely emulated, partially emulated or a real non-emulated core. The application server(s) for this testing should support video streaming using ABR protocol over HTTP/TCP and/or HTTP/QUIC as applicable. The end user device (UE) used for testing may be a real UE or an emulated one. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This may be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements or application server(s) are located remotely either in a cloud or on the Internet, the additional latency should be calculated and accounted for.
-
-The O-eNB shall have the correct configuration and software load. The pair of O-RUs (O-RU1 and O-RU2) shall be connected to the pair of O-DUs (O-DU1 and O-DU2), where O-RU1 is connected to O-DU1 and O-RU2 is connected to O-DU2. Both the O-DUs, O-DU1 and O-DU2 shall be connected to the same O-CU-CP/O-CU-UP. All the O-RAN components (O-RUs, O-DUs and O-CU-CP/O-CU-UP) shall have the correct configuration and software load. The end user device shall be configured with the correct user credentials to register and authenticate with the Master eNB and the 4G core. The end user device also shall be provisioned with the correct application, such as a video streaming client, to perform the tests. The 4G core network shall be configured to support end user device used for testing. This includes supporting registration, authentication and PDN connection establishment for this end user device.
-
-All the elements in the network like O-RAN system, 4G core and the application server should have the ability to capture traces to validate the successful execution of the test cases. The end user device should have the capability to capture traces/packets to calculate the video streaming KPIs. Optionally, the network may have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. All these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system (O-eNB, O-RUs, O-DUs and O-CU-CP/O-CU-UP), O-RAN system shall be connected to the 4G core which in turn shall have connectivity to the application server.
-
-##### 7.2.3.3 Test Methodology/Procedure
-
-Ensure the end user device, O-RAN system, 4G core and the application server have all been configured as outlined in Clause 7.2.3.2. All traces and packet captures need to be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the end user device and ensure it registers with the 4G core for data services over NSA by connecting over the O-eNB as Master eNB and O-RU1 of the O-RAN system as secondary gNB.
-- 2) Once the registration is complete, the end user device shall establish a PDN connection with the 4G core.
-- 3) Open the video streaming client on the end user device and start a streaming session over HTTP/TCP protocol.
-- 4) Once the video streaming session has started, move the device so it can handover from O-RU1 to O-RU2 (and in turn O-DU1 to O-DU2) on the Secondary gNB, while it continues to use the O-eNB as the Master eNB.
-- 5) Allow the end user device to stream video through the entire handover process. Measure the KPIs included in Clause 7.2 for this video streaming session.
-- 6) Optionally, repeat steps 1 through 5 for a video streaming session which uses HTTP/QUIC protocol for streaming.
-
-- 7) Repeat the test multiple times (> 10 times) and gather results.
-
-##### 7.2.3.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDN connection setup by the end user device without any errors using the O-eNB as Master eNB and O-RU1, O-DU1 and O-CU-CP/O-CU-UP as the Secondary gNB. This is a prerequisite before these tests can be validated.
-
-Validate the end user device can start streaming the video without delays and watch the video content through the entire handover process. Ensure there are no stalls, downgrading of video quality, or intermittent buffering of the video content, especially during the handover process. Use the packet captures to validate there are no packet drops or out of sequence packets which could impact customer experience and point to a misconfigured or flawed system.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which could impact the KPIs, example: use of the Internet to connect to remote servers/hosts could add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure within the SUT.
-
-- Video Start time or Time to load first video frame – ~1.5 seconds
-- Number of video stalls/buffering – < 1
-- Duration of stalls in the video – < 5 seconds
-- Video MOS Score – > 3.5
-
-The values for the end user video streaming KPIs defined in Clause 7.2 need to be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-The table below gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-7 Example Test Report for Video Streaming – Handover between same Master eNB but different O-RUs and O-DUs – Intra O-CU/Inter O-DU handover**
-
-| | Video Streaming over HTTP/TCP | Video Streaming over HTTP/QUIC |
-|------------------------------------|-------------------------------|--------------------------------|
-| Video Start Time | | |
-| Number of Video Stalls/buffering | | |
-| Duration of stalls in the video | | |
-| Video MOS Score | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-
-| | Video Streaming over HTTP/TCP | Video Streaming over HTTP/QUIC |
-|------------------|-------------------------------|--------------------------------|
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user video streaming experience can also be impacted by some of the features available (see Clause 7.2) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which could impact the end user's video streaming experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.2.4 Video Streaming – Handover between same MeNB with different O-CUs – Inter O-CU
-
-#### 7.2.4.0 Test Overview
-
-This test scenario validates the user's video streaming experience when the end user device (UE) is connected over NSA to a 4G core and is in the process of a handover between two Secondary gNB (O-RUs, O-DUs and O-CU-CP/O-CU-UPs) while remaining connected to the same Master eNB. The VoLTE or VoNR services cannot be used to test handover of secondary gNB, video streaming is used for this testing. This test scenario is only applicable in an NSA deployment.
-
-##### 7.2.4.1 Test Description
-
-This scenario tests the impact of a handover on the video streaming service. The end user device is connected over NSA to the 4G core and streaming video, while it performs a handover of the Secondary gNB (O-RU, O-DU and O-CU-CP/O-CU-UP) to a new Secondary gNB (O-RU, O-DU and O-CU-CP/O-CU-UP), i.e. an Inter O-CU handover, while still being connected to the same Master eNB. This test assesses the impact of the video streaming service on the end user device in this handover scenario by monitoring the end user video streaming KPIs included in Clause 7.2. This test case streams video using ABR protocol over HTTP/TCP and/or HTTP/QUIC.
-
-##### 7.2.4.2 Test Setup
-
-The SUT in this test case shall be the O-eNB which are the Master eNB and a pair of Secondary gNBs – O-RU1, O-DU1, O-CU-CP/O-CU-UP1 and O-RU2, O-DU2, O-CU-CP/O-CU-UP2. The O-eNB, O-RUs, O-DUs and O-CU-CP/O-CU-UPs shall comply with the O-RAN specifications. A 4G core will be required to support the basic functionality to authenticate and register an end user device to set up a PDN connection. The 4G/5G core may be a completely emulated, partially emulated or a real non-emulated core. The application server(s) for this testing should support video streaming using ABR protocol over HTTP/TCP and/or HTTP/QUIC as applicable. The end user device (UE) used for testing may be a real UE or an emulated one. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This may be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the Internet, the additional latency should be calculated and accounted for.
-
-The O-eNB, pair of gNBs (O-RUs, O-DUs and O-CU-CP/O-CU-UPs) shall have the correct configuration and software load. The pair of gNBs shall be connected as follows – O-RU1 will be connected to O-DU1, which in turn will be connected to O-CU-CP/O-CU-UP1 and similarly O-RU2 will be connected to O-DU2, which in turn will be connected to O-CU-CP/O-CU-UP2. The end user device shall be configured with the correct user credentials to be able to register and authenticate with the
-
-Master eNB and the 4G core. The end user device also shall be provisioned with the correct application, such as a video streaming client, to perform the tests. The 4G core network shall be configured to support end user device used for testing. This includes supporting registration, authentication and PDN connection establishment for this end user device.
-
-All the elements in the network, including the O-RAN (O-eNB and gNBs), 4G core, and the application server should have the ability to capture traces to validate the successful execution of the test cases. The end user device should have the capability to capture traces/packets to calculate the video streaming KPIs. Optionally, the network may have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. All these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system (O-eNB and gNBs), O-RAN system shall be connected to the 4G core which in turn shall have connectivity to the application server.
-
-##### 7.2.4.3 Test Methodology/Procedure
-
-Ensure the end user device, O-RAN system, 4G core and the application server have all been configured as outlined in Clause 7.2.4.2. All traces and packet captures need to be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the end user device and ensure it registers with the 4G core for data services over NSA by connecting over the O-eNB as Master eNB and O-RU1, O-DU1, O-CU-CP/O-CU-UP1 as secondary gNB.
-- 2) Once the registration is complete, the end user device shall establish a PDN connection with the 4G core.
-- 3) Open the video streaming client on the end user device and start a streaming session over HTTP/TCP protocol.
-- 4) Once the video streaming session has started, move the device so the secondary gNB is handed over from O-RU1 to O-RU2 (i.e. from O-RU1, O-DU1 and O-CU-CP/O-CU-UP1, to O-RU2, O-DU2 and O-CU-CP/O-CU-UP2), while it continues to use the O-eNB as the Master eNB.
-- 5) Allow the end user device to stream video through the entire handover process. Measure the KPIs included in Clause 7.2 for this video streaming session.
-- 6) Optionally, repeat steps 1 through 5 for a video streaming session which uses HTTP/QUIC protocol for streaming.
-- 7) Repeat the test multiple times (> 10 times) and gather results.
-
-##### 7.2.4.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDN connection setup by the end user device without any errors using the Master eNB and the O-RU1, O-DU1 and O-CU-CP/O-CU-UP1 as secondary gNB. This is a prerequisite before these tests can be validated.
-
-Validate the end user device can start streaming the video without delays and watch the video content through the entire handover process. Ensure there are no stalls, downgrading of video quality, or intermittent buffering of the video content, especially during the handover process. Use the packet captures to validate there are no packet drops or out of sequence packets which could impact customer experience and point to a misconfigured or flawed system.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which could impact the KPIs, example: use of the Internet to connect to remote servers/hosts could add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure within the SUT.
-
-- Video Start time or Time to load first video frame – ~1.5 seconds
-- Number of video stalls/buffering – < 1
-- Duration of stalls in the video – < 5 seconds
-- Video MOS Score – > 3.5
-
-The values for the end user video streaming KPIs defined in Clause 7.2 need to be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-The table below gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-8 Example Test Report for Video Streaming – Handover between same Master eNB but different O-RUs – Inter CU handover**
-
-| | Video Streaming over HTTP/TCP | Video Streaming over HTTP/QUIC |
-|------------------------------------|-------------------------------|--------------------------------|
-| Video Start Time | | |
-| Number of Video Stalls/buffering | | |
-| Duration of stalls in the video | | |
-| Video MOS Score | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user video streaming experience can also be impacted by some of the features available (see Clause 7.2) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which could impact the end user’s video streaming experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.2.5 Video Streaming – Handover between different MeNB while staying connected to same SgNB
-
-#### 7.2.5.0 Test Overview
-
-This test scenario validates the user's video streaming experience when the end user device (UE) is connected over NSA to a 4G core and the UE is in the process of a handover between two Master eNBs (two O-eNB) while staying connected to the same Secondary gNB (O-RU, O-DU and O-CU-CP/O-CU-UP). The VoLTE or VoNR services cannot be used to test handover of secondary gNB, video streaming is used for this testing. This test scenario is only applicable in an NSA deployment.
-
-##### 7.2.5.1 Test Description
-
-This scenario tests the impact of a handover on the video streaming service. The end user device is connected over NSA to the 4G core and streaming video while it performs handover of the Master eNB to a new Master eNB, i.e. O-eNB1 to O-eNB2, while staying connected to the same Secondary gNB (O-RU, O-DU and O-CU-CP/O-CU-UP). This test assesses the impact of the video streaming service on the end user device in this handover scenario by monitoring the end user video streaming KPIs included in Clause 7.2. This test case streams video using ABR protocol over HTTP/TCP and/or HTTP/QUIC.
-
-#### 7.2.5.2 Test Setup
-
-The SUT in this test case shall be a pair of O-eNBs (O-eNB1 and O-eNB2) which act as Master eNBs and a Secondary gNBs – (O-RU, O-DU and O-CU-CP/O-CU-UP). The pair of O-eNBs, O-RU, O-DU and O-CU-CP/O-CU-UP shall comply with the O-RAN specifications. A 4G core will be required to support the basic functionality to authenticate and register an end user device to set up a PDN connection. The 4G/5G core may be a completely emulated, partially emulated or a real non-emulated core. The application server(s) for this testing should support video streaming using ABR protocol over HTTP/TCP and/or HTTP/QUIC as applicable. The end user device (UE) used for testing may be a real UE or an emulated one. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This may be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the Internet, the additional latency should be calculated and accounted for.
-
-The pair of O-eNBs (O-eNB1 and O-eNB2) and the gNB (O-RU, O-DU and O-CU-CP/O-CU-UP) shall have the correct configuration and software load. Tools which emulate latency shall be used and configured on the O-RAN system (between O-RU, O-DU and O-CU-CP/O-CU-UP) to emulate real-world deployment conditions. The end user device shall be configured with the correct user credentials to be able to register and authenticate with the O-RAN (O-eNBs and gNB) and the 4G core. The end user device also shall be provisioned with the correct application, such as a video streaming client, to perform the tests. The 4G core network shall be configured to support end user device used for testing. This includes supporting registration, authentication and PDN session establishment for this end user device.
-
-All the elements in the network like O-RAN system, 4G core and the application server should have the ability to capture traces to validate the successful execution of the test cases. The end user device should have the capability to capture traces/packets to calculate the video streaming KPIs. Optionally, the network may have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. All these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system (O-eNBs and gNB), O-RAN system shall be connected to the 4G core which in turn shall have connectivity to the application server.
-
-#### 7.2.5.3 Test Methodology/Procedure
-
-Ensure the end user device, O-RAN system, 4G core and the application server have all been configured as outlined in Clause 7.2.5.2. All traces and packet captures need to be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the end user device and ensure it registers with the 4G core for data services over NSA by connecting over the O-eNB1 as Master eNB and O-RU, O-DU and O-CU-CP/O-CU-UP as Secondary gNB.
-- 2) Once the registration is complete, the end user device shall establish a PDN connection with the 4G core.
-
-- 3) Open the video streaming client on the end user device and start a streaming session over HTTP/TCP protocol.
-- 4) Once the video streaming session has started, move the end user device so it performs a handover of the Master eNB from O-eNB1 to O-eNB2, while staying connected to the same Secondary gNB i.e. O-RU, O-DU and O-CU-CP/O-CU-UP.
-- 5) Allow the end user device to stream video through the entire handover process. Measure the KPIs included in Clause 7.2 for this video streaming session.
-- 6) Optionally, repeat steps 1 through 6 for a video streaming session which uses HTTP/QUIC protocol for streaming.
-- 7) Repeat the test multiple times (> 10 times) and gather results.
-
-#### 7.2.5.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDN connection setup by the end user device without any errors using O-eNB1 as the Master eNB and the O-RU, O-DU and O-CU-CP/O-CU-UP as secondary gNB. This is a prerequisite before these tests can be validated.
-
-Validate the end user device can start streaming the video without delays and watch the video content through the entire handover process. Ensure there are no stalls, downgrading of video quality, or intermittent buffering of the video content, especially during the handover process. Use the packet captures to validate there are no packet drops or out of sequence packets which could impact customer experience and point to a misconfigured or flawed system.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which could impact the KPIs, example: use of the Internet to connect to remote servers/hosts could add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure within the SUT.
-
-- Video Start time or Time to load first video frame – ~1.5 seconds
-- Number of video stalls/buffering – < 1
-- Duration of stalls in the video – < 5 seconds
-- Video MOS Score – > 3.5
-
-The values for the end user video streaming KPIs defined in Clause 7.2 need to be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-The table below gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-9 Example Test Report for Video Streaming – Handover between Master eNB while staying connected to the same Secondary gNB**
-
-| | Video Streaming over TCP/QUIC | Video Streaming over TCP/QUIC |
-|------------------|-------------------------------|-------------------------------|
-| Video Start Time | | |
-
-| | Video Streaming over TCP/QUIC | Video Streaming over TCP/QUIC |
-|------------------------------------|-------------------------------|-------------------------------|
-| Number of Video Stalls/buffering | | |
-| Duration of stalls in the video | | |
-| Video MOS Score | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user video streaming experience can also be impacted by some of the features available (see Clause 7.2) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which could impact the end user's video streaming experience should be included in the test report to provide a comprehensive view of the testing.
-
-## 7.3 Voice Services – Voice over LTE (VoLTE) tests
-
-### 7.3.0 VoLTE tests introduction
-
-Voice service forms another basic service which is provided to a customer on a telecom network. Even though the earlier 2G/3G networks provide voice service through a circuit-switched network, the present document focuses on voice service provided using a packet switched network and specifies test cases to validate the Voice over LTE service in different scenarios. The KPIs which shall be monitored to assess the voice service are included below
-
-- CSSR – Call Setup Success Rate % – Total number of calls which were successful by the total number of calls made as a percentage.
-- CST – Call Setup Time – Time taken from the initial SIP INVITE to when the SIP 180 Ringing is received in seconds.
-- MOS Score – Mean Opinion Score for the voice call and shall be measured on both ends of the Voice call – mobile originated and mobile terminated.
-- Mute Rate – Percentage of calls which were muted in both directions (calls with RTP loss of > 3-4s in both directions are considered muted call). This KPI shall be measured on both ends of the voice call – mobile originated & mobile terminated and counted only once per call.
-- One Way Calls – Percentage of calls which were muted in any one direction (calls with RTP loss of > 3-4s in one direction only are considered one-way calls). This KPI shall be monitored on both ends of the voice call – mobile originated & mobile terminated and counted only once per call.
-
-- RTP Packet Loss % - Number of RTP packets which were dropped/lost in uplink/downlink direction as a percentage of total packets. This KPI shall be measured on both ends of the voice call – mobile originated and mobile terminated.
-
-Along with the monitoring and validation of these services utilizing user experience KPIs, the O-RAN systems also shall be monitored. The end user service experience can also be impacted by some of the features available on the O-RAN system. Some of these features have been included below. As a part of the voice services testing, details of these features shall be included in the test report to get a comprehensive view of the setup used for testing. If additional features or functionalities have been enabled during this testing that impact the end user voice experience, these shall be included in the test report as well.
-
-- RLC in Unacknowledged Mode
-- Robust Header Compression
-- DRX
-- Dynamic GBR Admission Control
-- TTI Bundling
-- VoLTE Inactivity Timer
-- Frequency Hopping
-- Multi-Target RRC Connection Re-Establishment
-- VoLTE HARQ
-- Coordinated Multi Point (DL and UL)
-- VoLTE Quality Enhancement
-- Packet Loss Detection
-- Voice Codec Aware scheduler
-- NR to LTE PS Redirection/Cell Reselection/Handover
-- LTE to NR PS Redirection/Cell Reselection/Handover
-
-Table 7-10 provides a summary of test cases and applicable technology.
-
-**Table 7-10: VoLTE Test Case Selection summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|-----------------------------------------------------|------------------|-----------------------|-----|-----|
-| | | | LTE | NSA | SA |
-| Test ID | Voice service (VoLTE) | | | | |
-| 7.3.1 | VoLTE Stationary Test | Service | Y | N/A | N/A |
-| 7.3.2 | VoLTE handover Test | Service | Y | N/A | N/A |
-| 7.3.3 | Voice Service – LTE to NR / NR to LTE handover test | Service | Y | N/A | Y |
-
-### 7.3.1 VoLTE Stationary Test
-
-#### 7.3.1.0 Test Overview
-
-This scenario tests the voice service experience on an LTE network – Voice over LTE (VoLTE) when the end user device is stationary.
-
-##### 7.3.1.1 Test Description
-
-With penetration of LTE, VoLTE has become the primary method of providing voice service. VoLTE uses IP packets to send and receive voice packets, with the IP packets being transferred over LTE. IMS forms an important part of VoLTE as it is used to setup control and data plane needed for VoLTE communication. As voice service is latency sensitive, the 4G core interacts with the IMS core to setup different bearers for Voice traffic – QCI-5 for VoLTE control plane and QCI-1 for VoLTE data plane. This test case is applicable when UE is connected over an O-RAN system to a 4G core in an NSA deployment.
-
-##### 7.3.1.2 Test Setup
-
-The SUT in this test case is an O-eNB which includes the Master eNB and may include a Secondary gNB. As most of the current NSA deployment use the 4G eNB to provide voice services, the use of a secondary gNB is optional. The Secondary gNB is included in this test scenario, but it is only applicable if the gNB plays a role in establishing the control plane or data plane for a voice call. The O-eNB, gNB and the components within these shall comply with the O-RAN specifications. The O-RAN setup should support the ability to perform this testing in different radio conditions as defined in Clause 4.6. A 4G core shall be used to support the basic functionality to authenticate and register an end user device in order to setup a PDN connection. An IMS core is used to register the end user device to support voice services on a 4G network. The 4G and IMS cores can be a completely emulated, partially emulated or real non-emulated core. At least two end user devices (UE) shall be used, which may be real UEs or emulated, and both shall support voice service using VoLTE. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the voice call. Going forward in this clause, these end user devices will be referred to as MO end user device and MT end user devices to represent the role they plan in the voice call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The Master eNB, Secondary gNB and their components (O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP) shall have the right configuration and software load. The end user device shall be configured with the right user credentials to be able to register and authenticate with the O-RAN system and the 4G core. The end user devices shall be provisioned with the user credentials to attach to the 4G core and register with the IMS core to perform a voice call using VoLTE. The 4G core network and IMS core shall be configured to support end user devices used for testing including supporting registration, authentication and PDN connection establishment for these end user devices. This also includes provisioning the IMS core to support registration of the end user devices to make voice calls over VoLTE, and dynamically setting up dedicated bearers for voice calls. The locations where the radio conditions are excellent, good, fair and poor shall be identified within the serving cell.
-
-All the elements in the network like O-RAN system, 4G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the VoLTE KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system(O-eNBs and gNBs), O-RAN system shall be connected to the 4G core which in turn shall have connectivity to the IMS Core.
-
-##### 7.3.1.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 4G core and the IMS Core have all been configured as outlined in Clause 7.3.1.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same O-RAN (i.e. same O-eNB), 4G and IMS core to perform the end-to-end voice call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices in excellent radio condition and ensure both end user devices connect to the 4G core over the Master O-eNB and optionally secondary gNB.
-- 2) Ensure both the MO and MT end user devices can establish a PDN connection with the 4G core. Once the PDN connection has been setup, both the end user devices shall register with the IMS core to support voice services.
-- 3) Use the MO end user device to call the MT end user device. Validate the MT end user device can receive and answer the call.
-
-- 4) Continue to have two-way voice communication on the voice call for at least 5 minutes before terminating it.
-- 5) Repeat the test multiple times (>10 times) and gather results.
-- 6) Repeat the above steps 1 through 5 for the MO and MT end user devices in good, fair, and poor radio conditions.
-
-##### 7.3.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful PDN connection setup by the end user devices without any errors using the Master eNB and optionally the secondary gNB. Verify both the end user devices can register with the IMS core for voice services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a voice call between each other by dynamically setting up a QCI-1 bearer to transfer voice packets over RTP. Ensure the Call Setup Time is reasonable, the voice quality from both parties are clear and audible without one-way or intermittent muting. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's voice experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote network nodes can add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % –> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-These end user voice KPI values included in Clause 7.3 shall be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report for the testing performed in different radio conditions to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-Table 7-11 gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-11 Example Test Report for Voice over LTE Testing – Stationary Test**
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|-------------------------|----------------------------|-------------|-------------|---------------------|
-| | VoLTE MO/MT | VoLTE MO/MT | VoLTE MO/MT | VoLTE MO/MT |
-| Call Setup Success Rate | | | | |
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------------------------|----------------------------|-------------|-------------|---------------------|
-| | VoLTE MO/MT | VoLTE MO/MT | VoLTE MO/MT | VoLTE MO/MT |
-| Call Setup time | | | | |
-| MOS Score | | | | |
-| Mute Rate | | | | |
-| One Way Call | | | | |
-| RTP Packet Loss | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| MIMO rank | | | | |
-| PDSCH MCS | | | | |
-| DL RB number | | | | |
-| UE CQI | | | | |
-| UE RSRQ | | | | |
-| UE PMI | | | | |
-| UE RSSI | | | | |
-| UE Buffer status | | | | |
-| UE Packet delay | | | | |
-| PDSCH BLER [%] | | | | |
-
-The end user VoLTE experience can also be impacted by some of the features available (see Clause 7.3) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which can impact the end user's voice service experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.3.2 VoLTE Handover Test
-
-This test clause is FFS
-
-### 7.3.3 Voice Service - LTE and NR handover tests
-
-#### 7.3.3.0 Test Overview
-
-This test scenario validates the user's voice experience when the UE is in a voice call and performs a handover from LTE network to a 5G network and vice versa. This test scenario is applicable for a 5G SA deployment.
-
-#### 7.3.3.1 Test Description
-
-Voice service is one of the basic services provided on the telecommunication network. Voice service on the 4G network is provided using VoLTE. Similarly, voice service on the 5G network is provided using packet switch technology called Voice over New Radio (VoNR). As 5G network is being deployed by a telecommunication service provider, the service provider can need to support 4G and 5G network, and thus support VoLTE, VoNR and the handover between the two voice services. This scenario tests the end user's voice experience when the end user device performs a handover from VoLTE to VoNR and vice versa.
-
-#### 7.3.3.2 Test Setup
-
-The SUT in this test case is an O-eNB along with a gNB (O-RU, O-DU and O-CU-CP/O-CU-UP). An interworking 4G-5G core (referred to as 4G-5G core going forward) which supports a combined anchor point for 4G and 5G, i.e. SMF+PGW-C and UPF+PGW-U is required. The eNB connects to a 4G-5G core over the 4G interfaces like S1 to provide 4G LTE service and the O-CU-CP/O-CU-UP, O-DU and O-RU will connect to a 4G-5G core over the 5G interfaces like N2 and N3 to provide 5G SA service. The O-eNB, and the components within these shall comply with the O-RAN specifications. The 4G-5G core shall support the basic functionality to authenticate and register an end user device in order to setup a PDN connection/PDU session. An IMS core is required to register the end user device to support voice services on a 4G and 5G network. The 4G and 5G core will interwork using the N26 interface between the MME and AMF to support seamless handover. Use of the N26 interface is recommended to ensure better customer experience when the end user device performs a handover between 4G and 5G. The 4G-5G and IMS cores can be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support voice service using VoLTE, VoNR and the capability to handover from VoLTE to VoNR and vice versa. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the voice call. Going forward in this clause, these end user devices are referred to as MO end user device and MT end user devices to represent their role in the voice call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely, either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The O-eNB, gNB and their components (O-RU, O-DU and O-CU-CP/O-CU-UP) shall have the right configuration and software load. The end user devices shall be configured with the right user credentials to be able to register and authenticate with the O-RAN system and the 4G-5G core. The end user devices shall be provisioned with the user credentials to support attach procedure to the 4G-5G core, registering to the IMS core and performing a voice call using VoLTE and VoNR. This includes supporting registration, authentication and PDN connection/PDU Session establishment for these end user devices. This also includes provisioning the IMS core to support registration of the end user devices to make voice calls over VoLTE and VoNR, and dynamically setting up dedicated bearers/QoS Flows for voice calls.
-
-All the elements in the network like O-RAN system, 4G-5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the VoLTE and VoNR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system(eNBs and gNBs), O-RAN system shall be connected to the 4G-5G core, which in turn shall have connectivity to the IMS Core.
-
-#### 7.3.3.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 4G-5G core and the IMS Core have all been configured as outlined in clause 7.3.3.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the eNB and gNB to connect to the same 4G-5G and IMS core to perform the end-to-end voice call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-The below items 1 to 8 define the steps to perform a VoLTE to VoNR handover, followed by VoNR to VoLTE handover
-
-- 1) Power on the two end user devices and ensure both of the end user devices can connect to the 4G-5G core over the O-eNB.
-- 2) Ensure both the MO and MT end user devices can establish a PDN connection with the 4G-5G core. Once the PDN connection has been setup, both the end user devices shall register with the IMS core to support voice services.
-- 3) Use the MO end user device to call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 4) Once the two-way call has been setup and communication is going back and forth between the two end user devices, move the MO device to the O-RU coverage of the gNB, thus forcing a handover from 4G to 5G, forcing a VoLTE to VoNR handover. Continue two-way voice communication through the handover process and terminate the call once the handover process is complete. Measure the voice KPIs included in Clause 7.3.
-
-- 5) At this point in time, the MO end user device is in 5G coverage and registered to the 4G-5G core. The MT end user device is in 4G coverage and registered to the 4G-5G core. Both end user devices should still be registered to the IMS core.
-- 6) Use the MO end user device to call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 7) Once the two-way call has been setup and communication is going back and forth between the two end user devices, move the MO device to the O-eNB coverage, thus forcing a handover from 5G to 4G, forcing a VoNR to VoLTE handover. Continue two-way voice communication through the handover process and terminate the call once the handover process is complete. Measure the voice KPIs included in Clause 7.3.
-- 8) Repeat the test multiple times (> 10 times) and gather results.
-
-#### 7.3.3.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDN connection setup by the end user devices without any errors using the O-eNB when in 4G coverage. Similarly, use traces to validate successful registration and PDU session setup by the end user device without any errors using O-RU, O-DU and O-CU-CP/O-CU-UP when in 5G coverage. Also verify both the end user devices can register with the IMS core for voice services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a voice call between each other by dynamically setting up a QCI-1/5QI-1 bearer to transfer voice packets over RTP. Ensure the Call Setup Time is reasonable, the voice quality from both parties is clear and audible without one-way or intermittent muting. Ensure the voice quality is not impacted during the handover process – VoLTE to VoNR and VoNR to VoLTE. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting issues, especially during the handover process. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's voice experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio conditions without the interference of external factors which can impact the KPIs. Example: use of internet to connect to remote network nodes can add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % –> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-The end user voice KPI values included in Clause 7.3 shall be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report for the testing performed in different radio conditions to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and L3 PDCP layers) (average sample per second)
-- Downlink transmission mode
-
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-Table 7-12 gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-12 Example Test Report for Voice service handover testing – LTE and NR**
-
-| | VoLTE to VoNR handover | VoNR to VoLTE handover |
-|------------------------------------|------------------------|------------------------|
-| Call Setup Success Rate | | |
-| Call Setup time | | |
-| MOS Score | | |
-| Mute Rate | | |
-| One Way Call | | |
-| RTP Packet Loss | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user VoLTE/VoNR experience can also be impacted by some of the features available (see Clause 7.3) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which can impact the end user’s voice service experience should be included in the test report to provide a comprehensive view of the testing.
-
-## 7.4 Voice Service – EPS Fallback tests
-
-### 7.4.0 Voice service - EPS fall back tests introduction
-
-Voice service is one of the basic services which must be supported on every telecom network. Upgrade of telecom network occurs in phases, and this is no different for 5G. The telecom network may not be able to support voice service on 5G during this phase for multiple reasons – the 5G network may not be deployed nationwide, or 5G network may not be tuned to support voice service or the devices may not be able to support voice service on 5G. However, there can be no interruption to voice service during this transition phase. EPS fallback is the method used to support voice services during this phase, where voice services are continued to be supported on the legacy LTE network using VoLTE by forcing the device to fallback to LTE to make or receive a call. The KPIs which shall be monitored to assess the voice service are included below
-
-- CSSR – Call Setup Success Rate % – Total number of calls which were successful by the total number of calls made as a percentage.
-- CST – Call Setup Time – Time taken from the initial SIP INVITE to when the SIP 180 Ringing is received in seconds.
-- MOS Score – Mean Opinion Score for the voice call. This KPI shall be measured on both ends of the Voice call – mobile originated and mobile terminated.
-- Mute Rate % – Percentage of calls which were muted in both directions (calls with RTP loss of > 3-4s in both directions are considered muted call). This KPI shall be measured on both ends of the Voice call – mobile originated and mobile terminated and counted only once per call.
-- One Way Calls % – Percentage of calls which were muted in any one direction (calls with RTP loss of > 3-4s in one direction only are considered one-way calls). This KPI shall be monitored on both ends of the Voice call – mobile originated and mobile terminated and counted only once per call.
-- RTP Packet Loss % - Number of RTP packets which were dropped/lost in uplink/downlink direction as a percentage of total packets. This KPI shall be measured on both ends of the Voice call – mobile originated and mobile terminated.
-
-Along with the monitoring and validation of these services utilizing user experience KPIs, the O-RAN systems also shall be monitored. The end user service experience can also be impacted by some of the features available on the O-RAN system. Some of these features have been included below. As a part of the voice services testing, details of these features shall be included in the test report to get a comprehensive view of the setup used for testing. If additional features or functionalities have been enabled during this testing that impact the end user voice experience, these shall be included in the test report as well.
-
-- EPS Fallback for IMS Voice
-- NR to EPS Mobility
-- RLC in Unacknowledged Mode
-- Robust Header Compression
-- DRX
-- Dynamic GBR Admission Control
-- TTI Bundling
-- VoLTE Inactivity Timer
-- Frequency Hopping
-- Multi-Target RRC Connection Re-Establishment
-- VoLTE HARQ
-- Coordinated Multi Point (DL and UL)
-- VoLTE Quality Enhancement
-- Packet Loss Detection
-- Voice Codec Aware scheduler
-
-Please see Table 7-13 for a summary of test cases and applicable technology.
-
-**Table 7-13: EPS Fallback Test Case Selection summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|------------------------------------|------------------|-----------------------|-----|----|
-| | | | LTE | NSA | SA |
-| Test ID | Voice service - EPS Fallback | | | | |
-| 7.4.1 | EPS Fallback (N26 and without N26) | Service | Y | N/A | Y |
-
-### 7.4.1 EPS Fallback Test
-
-#### 7.4.1.0 Test Overview
-
-This scenario tests the voice service when an end user device (UE) is in 5G SA coverage and performs an EPS fallback to 4G to make or receive a voice call.
-
-##### 7.4.1.1 Test Description
-
-This clause tests the voice service on a 5G SA network when it uses EPS fallback mechanism to fallback to the LTE network and use VoLTE to support voice service. This testing only applies to 5G SA deployment and in this scenario the UE is connected to the 5G SA Core and registered with the IMS core for voice service. When the end user device (UE) wants to make a voice call or receive a voice call, the network informs the device to fallback to the LTE network to make/receive the voice call. The EPS fallback does increase the Call Setup Time due to the time needed to fallback before making/receiving the voice call.
-
-There are two mechanisms in which EPS fallback is supported on the 5G core, and the methodology used impacts the time taken to perform the fallback to LTE, and hence impacts the Call Setup Time. The two mechanisms that may be used to perform EPS fallback are included below. These two mechanisms do change the test setup, but do not change the testing procedure.
-
-- With N26 interface – The AMF in the 5G core communicates with the MME in the 4G over the N26 interface. In this scenario the UE performs a handover from the 5G network to the 4G network.
-- Without N26 interface – The AMF in the 5G core does not communicate directly with the 4G core, instead uses the UDM/HSS to store and transfer relevant session information to the 4G core. In this scenario the UE performs a Release with Redirect from the 5G network to the 4G network.
-
-##### 7.4.1.2 Test Setup
-
-The SUT in this test case is an O-eNB along with a gNB (O-RU, O-DU and O-CU-CP/O-CU-UP). An interworking 4G-5G core (referred to as 4G-5G core going forward) which supports a combined anchor point, i.e. SMF+PGW-C and UPF+PGW-U is required. The O-eNB connects to a 4G-5G core over the 4G interfaces like S1 to provide 4G LTE service and the gNB (O-RU, O-DU and O-CU-CP/O-CU-UP) will connect to the 4G-5G core over the 5G interfaces like N2 and N3 to provide 5G SA service. The O-eNB, gNB and the components within these shall comply with the O-RAN specifications and support EPS fallback. The 4G-5G core will support the basic functionality to authenticate and register an end user device in order to setup a PDN connection/PDU session. The IMS core will support registration of the end user device and will be integrated with the 4G-5G core to support voice services over VoLTE and EPS fallback. The 4G-5G core will interwork either using the N26 interface or without using N26 interface depending on the desired core network configuration. The existence of the N26 interface does reduce the EPS fallback time, reducing Call Setup Time and provides better end user experience. The 4G-5G and IMS cores may be a completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which either can be real UEs or emulated, and both shall support voice service using VoLTE and EPS fallback procedure. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the voice call. For the sake of clarity, these end user devices will be addressed as UE-1 and UE-2 in this clause. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The O-eNB, gNB and their components (O-RU, O-DU and O-CU-CP/O-CU-UP) shall have the right configuration and software load. The end user device shall be configured with the right user credentials to be able to register and authenticate with the O-RAN system and the 4G-5G core. The end user devices shall be provisioned with the user credentials to attach to the 4G-5G core and register with the IMS core to perform voice call using VoLTE and EPS fallback. The 4G-5G core network and IMS core shall be configured to support voice service on the end user devices used for testing, which includes dynamically setting up dedicated bearers for voice calls.
-
-All the elements in the network like O-RAN system, 4G-5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the VoLTE KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system(O-eNBs and gNBs), O-RAN system shall be connected to the 4G-5G core which in turn shall have connectivity to the IMS Core.
-
-##### 7.4.1.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 4G-5G core and the IMS Core have all been configured as outlined in Clause 7.4.1.2. In this test scenario, one of the end user device will be connected over the 4G O-eNB to the 4G-5G core, while the other end user device will be connected over 5G gNB (O-RU, O-DU and O-CU-CP/O-CU-UP) to the 4G-5G core. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices and ensure UE-1 is in LTE coverage, and UE-2 is in the 5G coverage. Validate both end user devices register to the 4G-5G core.
-- 2) Once the registration is complete, UE-1 and UE-2 shall establish a PDN connection and PDU session respectively with the 4G-5G core. Once the PDN connection and PDU session have been setup, both the end user devices shall register with the IMS core to support voice services.
-- 3) Use UE-1 as the MO end user device to call UE-2. Validate the UE-2 performs EPS fallback to LTE to receive the call.
-- 4) Answer the call on UE-2 and continue to have two-way communication for at least 5 minutes and terminate the call. Measure the voice KPIs included in Clause 7.4.
-- 5) At this point UE-2 should have completed the call and moved back to connect to the 4G-5G Core over 5G gNB.
-- 6) Use UE-2 as the MO end user device to call UE-1. Validate the UE-2 performs EPS fallback to LTE before making the call.
-- 7) Answer the call on UE-1 and continue to have two-way communication for at least 5 minutes and terminate the call. Measure the voice KPIs included in Clause 7.4.
-- 8) Repeat the test multiple times (>10 times) and gather results.
-
-##### 7.4.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate end user device UE-1 can perform a successful registration and PDN connection setup while using the O-eNB in LTE coverage. Similarly, use the traces to validate end user device UE-2 can perform a successful registration and PDU session setup while using gNB in 5G coverage. Verify both the end user devices can register with the IMS core for voice services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a voice call between each other by dynamically setting up a QCI-1 bearer to transfer voice packets over RTP. Validate the device which is in the 5G coverage falls back to 4G before receiving or making a voice call, in other words the EPS fallback procedure was executed successfully. The Call Setup Time will be higher than VoLTE due to the delay associated with executing the EPS fallback procedure. Even though this test case does not directly impact the quality of the voice call, for the sake of consistency, ensure the voice quality from both parties are clear and audible without one-way or intermittent muting. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's voice experience.
-
-The average range of values for the KPIs are included in Table 7-14 for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote network nodes can add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-**Table 7-14 Typical Voice KPI values in controlled environments with good radio conditions**
-
-| KPI | With N26 Interface | Without N26 Interface |
-|----------------------------------|--------------------|-----------------------|
-| CSSR – Call Setup Success Rate % | >99% | >99% |
-| CST – Call Setup Time | 3.5s | 4 s |
-| MOS Score | 3.5 | 3.5 |
-| Mute Rate % | < 1% | < 1% |
-| One Way Call % | < 1% | < 1% |
-| RTP Packet Loss % | < 1% | < 1% |
-
-These end user voice KPI values included in Clause 7.3 shall be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-Table 7-15 gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-15 Example Test Report for Voice Service Testing – EPS Fallback**
-
-| | VoLTE MO | VoLTE MT |
-|------------------------------------|----------|----------|
-| Call Setup Success Rate | | |
-| Call Setup time | | |
-| MOS Score | | |
-| Mute Rate | | |
-| One Way Call | | |
-| RTP Packet Loss | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-
-| | VoLTE MO | VoLTE MT |
-|------------------|----------|----------|
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user VoLTE experience can also be impacted by some of the features available (see Clause 7.3) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which can impact the end user's voice service experience should be included in the test report to provide a comprehensive view of the testing.
-
-## 7.5 Voice Service – Voice over NR (VoNR) tests
-
-### 7.5.0 VoNR test introduction
-
-Voice services on 5G are called Voice over New Radio (VoNR). VoNR also packetizes voice and uses IP packets for voice communication. On the Core and IMS side, VoNR is very similar to VoLTE. VoNR also uses the IMS system for voice service, and the IMS interacts with the 5G core to set up a separate bearer for voice service. This clause tests the voice service over VoNR in different scenarios. The KPIs which shall be monitored to assess the voice service are included below
-
-- CSSR – Call Setup Success Rate % – Total number of calls which were successful by the total number of calls made as a percentage.
-- CST – Call Setup Time – Time taken from the initial SIP INVITE to when the SIP 180 Ringing is received in seconds.
-- MOS Score – Mean Opinion Score for the voice call. This KPI shall be measured on both ends of the Voice call – mobile originated and mobile terminated.
-- Mute Rate % – Percentage of calls which were muted in both directions (calls with RTP loss of > 3-4s in both directions are considered muted call). This KPI shall be measured on both ends of the Voice call – mobile originated and mobile terminated and counted only once per call.
-- One Way Calls % – Percentage of calls which were muted in any one direction (calls with RTP loss of > 3-4s in one direction only are considered one-way calls). This KPI shall be monitored on both ends of the Voice call – mobile originated and mobile terminated and counted only once per call.
-- RTP Packet Loss % - Number of RTP packets which were dropped/lost in uplink/downlink direction as a percentage of total packets. This KPI shall be measured on both ends of the Voice call – mobile originated and mobile terminated.
-
-End user voice service experience can also be impacted by some of the features available on the O-RU, O-DU and O-CU-CP/O-CU-UP. Some of these features have been included below. As a part of the voice services testing, details of these features shall be included in the test report to get a comprehensive view of the setup used for testing. If additional features or functionalities have been enabled during this testing that impact the end user voice experience, these shall be included in the test report as well.
-
-- Basic Voice over NR
-- RLC in Unacknowledged Mode
-- Robust Header Compression
-- DRX
-- Dynamic GBR Admission Control
-- TTI Bundling
-
-- Automated Neighbor Relations ANR
-- Connected mode mobility (Handover)
-- idle mode reselection
-- Intra-frequency Cell Reselection/Handover
-- Inter-frequency Redirection/Cell Reselection/Handover
-- NR Coverage-Triggered NR Session Continuity
-
-Please see Table 7-16 for a summary of test cases and applicable technology.
-
-**Table 7-16: VoNR Test Case summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|---------------------------------------|------------------|-----------------------|-----|----|
-| | | | LTE | NSA | SA |
-| Test ID | Voice service - Voice over NR (VoNR) | | | | |
-| 7.5.1 | Voice over NR Test – stationary | Service | N/A | N/A | Y |
-| 7.5.2 | VONR – Intra O-DU handover | Service | N/A | N/A | Y |
-| 7.5.3 | VONR – Intra O-CU/Inter O-DU handover | Service | N/A | N/A | Y |
-| 7.5.4 | VONR – Inter O-CU handover | Service | N/A | N/A | Y |
-
-### 7.5.1 Voice over NR Test
-
-#### 7.5.1.0 Test Overview
-
-This test scenario validates the user’s voice experience when the end user device is in 5G coverage and the user makes a voice call over NR – VoNR.
-
-##### 7.5.1.1 Test Description
-
-This clause tests VoNR user experience on an O-RAN system. VoNR is similar to VoLTE where it uses IP packets to send and receive voice packets, with the IP packets being transferred over NR or 5G radio. Just like VoLTE, IMS is used to set up the control and data plane for the voice communication. As voice service is latency sensitive, the 5G core interacts with the IMS core to set up different QoS flows for voice traffic – 5QI-5 for VoNR control plane and 5QI-1 for VoNR data plane. This test case is applicable when end user device (UE) is connected over a 5G SA network.
-
-##### 7.5.1.2 Test Setup
-
-The SUT in this test case is a gNB (O-RU, O-DU and O-CU-CP/O-CU-UP) which is used to test the voice service. A 5G SA Core is required to support basic functionality to authenticate and register the end user device to establish a PDU session. An IMS core is required to register the end user device to support voice services on a 5G network. The 5G and IMS cores may be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support voice service using VoNR. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the voice call. Going forward in this clause, these end user devices will be referred to as MO end user device and MT end user device to represent their role in the voice call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The O-RU, O-DU and O-CU-CP/O-CU-UP shall have the right configuration and software load. The SUT shall be set up to run this testing in different radio conditions as outlined in Clause 4.6. The end user device shall be configured with the right user credentials to be able to register and authenticate with the O-RAN system and the 5G core. The end user devices shall be provisioned with the user credentials to register and setup PDU session with the 5G core and register with the IMS core to perform voice call using VoNR. The 5G core network and IMS core shall be configured to support voice service on the end user devices used for testing, which includes the ability to dynamically set up QoS Flows for voice calls. The locations where the radio conditions are excellent, good, fair and poor shall be identified within the serving cell.
-
-All the elements in the network like O-RAN system, 5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the VoNR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system(O-RU, O-DU and O-CU-CP/O-CU-UP), O-RAN system shall be connected to the 5G core which in turn shall have connectivity to the IMS Core.
-
-##### 7.5.1.3 Test Methodology/Procedure
-
-Ensure the end user device, O-RAN system, 5G core and the IMS core have all been configured as outlined in Clause 7.5.1.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same O-RAN system, 5G and IMS core to perform the end-to-end voice call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices in excellent radio condition and ensure both devices register with the 5G core for voice services over SA by connecting over the O-RAN (O-RU, O-DU and O-CU-CP/O-CU-UP).
-- 2) Once the registration is complete, the MO and MT end user devices shall establish a PDU session with the 5G core. Once the PDU session has been setup, both the end user devices shall register with the IMS core to support voice services.
-- 3) Use the MO end user device to call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 4) Continue to have two-way voice communication on the voice call for at least 5 minutes before terminating it.
-- 5) Repeat the test multiple times (> 10 times) and gather results.
-- 6) Repeat the above steps 1 through 5 for good, fair, and poor radio conditions.
-
-##### 7.5.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup by the end user devices without any errors over O-RU, O-DU and O-CU-CP/O-CU-UP. Also validate both the end user devices can register with the IMS core for voice services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a voice call between each other by dynamically setting up a 5QI-1 bearer to transfer voice packets over RTP. Ensure the Call Setup Time is reasonable, the voice quality from both parties are clear and audible without one-way or intermittent muting. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's voice experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote servers/hosts can add latency, jitter and reliability issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % → 99%.
-- CST – Call Setup Time – < 2.5s
-
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-As a part of gathering data, ensure the minimum configuration parameters included in Clause 4.3 are included in the test report. The information in Table 7-17 should also be included in the test report to provide a comprehensive view of the test setup.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and L3 PDCP layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-17 Example Test Report for VoNR – Stationary Testing**
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------------------------|----------------------------|------------|------------|---------------------|
-| | VoNR MO/MT | VoNR MO/MT | VoNR MO/MT | VoNR MO/MT |
-| Call Setup Success Rate | | | | |
-| Call Setup Time | | | | |
-| MOS Score | | | | |
-| Mute Rate % | | | | |
-| One Way Call % | | | | |
-| RTP Packet Loss % | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| MIMO rank | | | | |
-| PDSCH MCS | | | | |
-| DL RB number | | | | |
-| UE CQI | | | | |
-| UE RSRQ | | | | |
-| UE PMI | | | | |
-| UE RSSI | | | | |
-| UE Buffer status | | | | |
-| UE Packet delay | | | | |
-| PDSCH BLER [%] | | | | |
-
-The end user voice service experience can also be impacted by some of the features available (see Clause 7.5) on the O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which can impact the end user's voice service experience should be included in the test report to provide a comprehensive view of the testing.
-
-#### 7.5.2 VoNR – Intra O-DU handover
-
-This test scenario validates the user's voice experience when the end user device (UE) is on a VoNR call and performs a handover between two O-RUs which connect to the same O-DU (Intra O-DU handover)
-
-##### 7.5.2.1 Test Description
-
-The 5G O-RAN system has multiple components such as the O-RU, O-DU and the O-CU-CP/O-CU-UP. This setup leads to multiple handover scenarios between the O-RAN components. This scenario tests the end user's voice experience during the handover between two O-RUs which are connected to the same O-DU (and O-CU-CP/O-CU-UP), hence an Intra O-DU handover. This handover will be agnostic to the 5G core as the handover occurs on the O-RAN system. This test assesses the impact on the end user's voice service in this handover scenario by monitoring the KPIs included in Clause 7.5.
-
-##### 7.5.2.2 Test Setup
-
-The SUT in this test case is a pair of O-RUs which connect to the same O-DU and O-CU-CP/O-CU-UP (refer Clause 5.4). This O-RAN setup is used to test the voice service during a handover. A 5G SA Core is required to support basic functionality to authenticate and register the end user device to establish a PDU session. An IMS core is required to register the end user device to support voice services on a 5G network. The 5G and IMS cores may be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support voice service using 5G – Voice over NR(VoNR). The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the voice call. Going forward in this clause, these end user devices will be referred to as MO end user device and MT end user device to represent their role in the voice call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The pair of O-RUs (O-RU1 and O-RU2) shall be connected to the O-DU and O-CU-CP/O-CU-UP and all the components shall have the right configuration and software load. The end user devices shall be configured with the right user credentials to be able to register and authenticate with the O-RAN system and the 5G core. The end user devices shall be provisioned with the user credentials to register and setup PDU session with the 5G core and register with the IMS core to perform voice call using VoNR. The 5G core network and IMS core shall be configured to support voice service on the end user devices used for testing, which includes the ability to dynamically set up QoS Flows for voice calls.
-
-All the elements in the network-like O-RAN system, 5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the VoNR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system(O-RUs connected to O-DU and O-CU-CP/O-CU-UP), O-RAN system shall be connected to the 5G core which in turn shall have connectivity to the IMS Core.
-
-##### 7.5.2.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 5G core and the IMS Core have all been configured as outlined in Clause 7.5.2.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same O-RAN system, 5G and IMS core to perform the end-to-end voice call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices and ensure both devices register with the 5G core for voice services over SA by connecting over the O-RAN (O-RU, O-DU and O-CU-CP/O-CU-UP). Ensure both the MO & MT end user devices are in the coverage area of the same O-RU – O-RU1.
-
-- 2) Once the registration is complete, the MO and MT end user devices shall establish PDU session with the 5G core. Once the PDU session has been setup, both the end user devices shall register with the IMS core to support voice services.
-- 3) Use the MO end user device to call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 4) Once the call has been setup, move the MO end user device from the coverage area of O-RU1 to coverage area of O-RU2, triggering a handover from O-RU1 to O-RU2.
-- 5) Continue the two-way voice communication between MO and MT end user devices until the handover procedure is complete before terminating the voice call.
-- 6) Repeat the test (steps 1 through 5) multiple times (> 10 times) and collect results.
-
-##### 7.5.2.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup by the end user devices without any errors over O-RU, O-DU and O-CU-CP/O-CU-UP. Also validate both the end user devices can register with the IMS core for voice services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a voice call between each other by dynamically setting up a 5QI-1 bearer to transfer voice packets over RTP. Ensure the Call Setup Time is reasonable, the voice quality from both parties is clear and audible without one-way or intermittent muting for the duration of the call, especially during the handover process. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's voice experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio conditions without the interference of external factors which can impact the KPIs. Example: use of internet to connect to remote servers/hosts can add latency, jitter and reliability issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % –> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-As a part of gathering data, the minimum configuration parameters in Clause 4.3) shall be included in the test report. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and L3 PDCP layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-18 Example Test Report for VoNR – Intra O-DU Handover**
-
-| | VoNR MO | VoNR MT |
-|------------------------------------|---------|---------|
-| Call Setup Success Rate | | |
-| Call Setup Time | | |
-| MOS Score | | |
-| Mute Rate % | | |
-| One Way Call % | | |
-| RTP Packet Loss % | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user voice service experience can also be impacted by some of the features available (see Clause 7.5) on the O-RUs, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which can impact the end user’s voice service experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.5.3 VoNR – Intra O-CU/Inter O-DU handover
-
-This test scenario validates the user’s voice experience when the end user device (UE) is on a VoNR call and performs a handover between O-RUs which connect to different O-DUs, which in turn are connected to the same O-CU-CP/O-CU-UP (Intra O-CU/Inter O-DU handover)
-
-##### 7.5.3.1 Test Description
-
-The 5G O-RAN system has multiple components such as the O-RU, O-DU and the O-CU-CP/O-CU-UP. This setup leads to multiple handover scenarios between the O-RAN components. This particular scenario tests the end user’s voice experience during the handover between two O-RUs, where the O-RUs are connected to different O-DUs which in turn are connected to the same O-CU-CP/O-CU-UP, hence an Intra O-CU/Inter O-DU handover. This handover will be agnostic to the 5G core as the handover occurs on the O-RAN system. This test assesses the impact on the end user’s voice service in this handover scenario by monitoring the KPIs included in Clause 7.5.
-
-##### 7.5.3.2 Test Setup
-
-The SUT in this test case is a pair of O-RUs which connect to a different pair of O-DUs which in turn connect to the same O-CU (refer Clause 4.5). This O-RAN setup is used to test the voice service during a handover. A 5G SA Core is required to support basic functionality to authenticate and register the end user device to establish a PDU session. An IMS core is required
-
-to register the end user device to support voice services on a 5G network. The 5G and IMS cores can be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support voice service using VoNR. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the voice call. Going forward in this clause, these end user devices are referred to as MO end user device and MT end user device to represent their role in the voice call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely, either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The pair of O-RUs (O-RU1 and O-RU2) shall be connected to a pair of O-DUs (O-DU1 and O-DU2) and O-CU-CP/O-CU-UP. As for the O-RU to O-DU connection, O-RU1 shall connect to O-DU1, and O-RU2 shall connect to O-DU2, and both O-DUs shall connect to the same O-CU-CP/O-CU-UP. All the O-RAN components shall have the correct configuration and software load. The end user devices shall be provisioned with the user credentials to register and setup a PDU session with the 5G core and register with the IMS core to perform voice calls using VoNR. The 5G core network and IMS core shall be configured to support voice service on the end user devices used for testing, which includes the ability to dynamically set up QoS Flows for voice calls.
-
-All the elements in the network like O-RAN system, 5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the VoNR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system(O-RUs connected to O-DU and O-CU), O-RAN system shall be connected to the 5G core, which in turn shall have connectivity to the IMS Core.
-
-##### 7.5.3.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 5G core and the IMS core have all been configured as outlined in Clause 7.5.3.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same O-RAN system, 5G and IMS core to perform the end-to-end voice call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices and ensure both devices register with the 5G core for voice services over SA by connecting over the O-RAN (O-RU, O-DU and O-CU). Both the MO & MT end user devices shall be in the coverage area of the same O-RU – O-RU1.
-- 2) Once the registration is complete, the MO and MT end user devices shall establish a PDU session with the 5G core. Once the PDU session has been setup, both the end user devices shall register with the IMS core to support voice services.
-- 3) Use the MO end user device to call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 4) Once the call has been setup, move the MO end user device from the coverage area of O-RU1 to coverage area of O-RU2, thus causing a handover from O-RU1 to O-RU2, and O-DU1 to O-DU2.
-- 5) Continue the two-way voice communication between the end user devices until the handover procedure is complete before terminating the voice call.
-- 6) Repeat the test (steps 1 through 5) multiple times (> 10 times) and gather results.
-
-##### 7.5.3.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup by the end user devices without any errors over O-RU, O-DU and O-CU. Also validate both the end user devices can register with the IMS core for voice services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a voice call between each other by dynamically setting up a 5QI-1 bearer to transfer voice packets over RTP. Ensure the Call Setup Time is reasonable, the voice quality from both parties is clear and audible
-
-without one-way or intermittent muting through the duration of the call, especially during the handover process. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's voice experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio conditions without the interference of external factors which can impact the KPIs. Example: use of internet to connect to remote servers/hosts can add latency, jitter and reliability issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % –> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-As a part of gathering data, ensure the minimum configuration parameters in see Clause 4.3 are included in the test report. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-19 Example Test Report for VoNR – Intra O-CU/Inter O-DU Handover**
-
-| | VoNR MO | VoNR MT |
-|------------------------------------|---------|---------|
-| Call Setup Success Rate | | |
-| Call Setup Time | | |
-| MOS Score | | |
-| Mute Rate % | | |
-| One Way Call % | | |
-| RTP Packet Loss % | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-
-| | VoNR MO | VoNR MT |
-|------------------|---------|---------|
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user voice service experience can also be impacted by some of the features available (see Clause 7.5) on the O-RUs, O-DU and O-CU. The details of these features, along with any other features/functionality which can impact the end user's voice service experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.5.4 VoNR – Inter O-CU handover
-
-This test scenario validates the user's voice experience when the end user device (UE) is on a VoNR call and performs a handover between O-RUs which connect to different O-DUs and different O-CUs (Inter O-CU Inter O-DU handover)
-
-#### 7.5.4.1 Test Description
-
-The 5G O-RAN system has multiple components such as the O-RU, O-DU and the O-CU. This setup leads to multiple handover scenarios between the O-RAN components. This particular scenario tests the end user's voice experience during the handover between two O-RUs, where the O-RUs are connected to different O-DUs which in turn are connected to different O-CUs, hence an Inter O-CU Inter O-DU handover. This handover occurs on the O-RAN system and the 5G core is aware of the handover as it needs to send data to a new O-CU as a part of the handover process. This test assesses the impact on the end user's voice service in this handover scenario by monitoring the KPIs included in Clause 7.5.
-
-#### 7.5.4.2 Test Setup
-
-The SUT in this test case is a pair of O-RAN subsystems, a set of O-RU, O-DU and O-CU which interconnects with another set of O-RU, O-DU and O-CU (refer Clause 5.6). This O-RAN setup is used to test the voice service during a handover. A 5G SA Core is required to support basic functionality to authenticate and register the end user device to establish a PDU session. An IMS core is required to register the end user device to support voice services on a 5G network. The 5G and IMS cores can be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support voice service using VoNR. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the voice call. Going forward in this clause, these end user devices are referred to as MO end user device and MT end user device to represent their role in the voice call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The pair of O-RAN (O-RAN1 and O-RAN2) subsystems shall be connected – O-RU1 shall be connected to O-DU1, which in turn shall be connected to O-CU1 and similarly O-RU2 shall be connected to O-DU2, which in turn shall be connected to O-CU2. The O-CU1 and O-CU2 nodes shall be connected to each other and the 5G core. All the O-RAN components shall have the correct configuration and software load. The end user devices shall be configured with the correct user credentials to be able to register and authenticate with the O-RAN system and the 5G core. The end user devices also shall be provisioned with the user credentials to register and setup PDU session with the 5G core and register with the IMS core to perform voice call using VoNR. The 5G core network and IMS core shall be configured to support voice service on the end user devices used for testing, which includes the ability to dynamically set up QoS Flows for voice calls.
-
-All the elements in the network like O-RAN system, 5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the VoNR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with
-
-each other – the end user device shall be able to connect to O-RAN system(O-RUs connected to O-DUs which are connected to the O-CUs), O-RAN system shall be connected to the 5G core which in turn shall have connectivity to the IMS Core.
-
-#### 7.5.4.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 5G core and the IMS Core have all been configured as outlined in Clause 7.5.4.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same O-RAN system, 5G and IMS core to perform the end-to-end voice call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices and ensure both devices register with the 5G core for voice services over SA by connecting over the O-RAN1 system (O-RU1, O-DU1 and O-CU1). Both the MO & MT end user devices shall be in the coverage area of the same O-RU – O-RU1.
-- 2) Once the registration is complete, the MO and MT end user devices shall establish a PDU session with the 5G core. Once the PDU session has been setup, both the end user devices shall register with the IMS core to support voice services.
-- 3) Use the MO end user device to call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 4) Once the call has been setup, move the MO end user device from the coverage area of O-RU1 to coverage area of O-RU2, thus causing a handover from O-RAN1 to O-RAN2 subsystem - O-RU1 to O-RU2, O-DU1 to O-DU2 and O-CU1 to O-CU2.
-- 5) Continue the two-way voice communication between MO and MT end user devices until the handover procedure is complete before terminating the voice call.
-- 6) Repeat the test (steps 1 through 5) multiple times (> 10 times) and gather results.
-
-#### 7.5.4.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup by the end user devices without any errors over O-RU, O-DU and O-CU. Also validate both the end user devices can register with the IMS core for voice services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a voice call between each other by dynamically setting up a 5QI-1 bearer to transfer voice packets over RTP. Ensure the Call Setup Time is reasonable, the voice quality from both parties is clear and audible without one-way or intermittent muting through the duration of the call, especially during the handover process. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's voice experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio conditions without the interference of external factors which can impact the KPIs. Example: use of internet to connect to remote servers/hosts can add latency, jitter and reliability issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % –> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-As a part of gathering data, ensure the minimum configuration parameters in Clause 4.3) are included in the test report. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and L3 PDCP layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-20 Example Test Report for VoNR – Inter O-CU Handover**
-
-| | VoNR MO | VoNR MT |
-|------------------------------------|---------|---------|
-| Call Setup Success Rate | | |
-| Call Setup Time | | |
-| MOS Score | | |
-| Mute Rate % | | |
-| One Way Call % | | |
-| RTP Packet Loss % | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user voice service experience can also be impacted by some of the features available (see Clause 7.5) on the O-RUs, O-DUs and O-CU. The details of these features, along with any other features/functionality which can impact the end user's voice service experience should be included in the test report to provide a comprehensive view of the testing.
-
-## 7.6 Video Service – Video over LTE (ViLTE) tests
-
-### 7.6.0 ViLTE test introduction
-
-Voice service has been one of the basic services provided on the mobile device since launch. With increasing LTE penetration and the availability of higher speeds, video calls are slowly replacing voice calls. With the launch of 5G which promises much higher throughput, the shift towards using video calls is only going to get faster. This clause of the present document validates the user's video calling experience in different conditions on the LTE network. This clause of the present document only applies to the video calling service provided by the telecom service provider, which uses the telecom operator's IMS core to establish dedicated bearer to provide superior video calling experience. The KPIs which shall be monitored to assess the video service are included below
-
-- CSSR – Call Setup Success Rate % – Total number of calls which were successful by the total number of calls made as a percentage.
-- CST – Call Setup Time – Time taken from the initial SIP INVITE to when the SIP 180 Ringing is received in seconds.
-- MOS Score – Mean Opinion Score for the video call. This shall be measured on both ends of the video call – mobile originated and mobile terminated.
-- Mute Rate % – Percentage of video calls which were muted or video freezes in both directions (calls with RTP loss of > 3-4s in both directions are considered muted call). This KPI shall be measured on both ends of the video call – mobile originated and mobile terminated and counted only once per call.
-- One Way Calls % – Percentage of video calls which were muted, or video is not transmitted in any one direction only (video calls with RTP loss of > 3-4s in one direction only are considered one-way calls). This KPI shall be monitored on both ends of the Video call – mobile originated and mobile terminated and counted only once per call.
-- RTP Packet Loss % - Number of RTP packets which were dropped/lost in uplink/downlink direction as a percentage of total packets. This KPI shall be measured on both ends of the Video call – mobile originated and mobile terminated.
-
-Along with the monitoring and validation of these services utilizing user experience KPIs, the O-RAN systems also shall be monitored. The end user service experience can also be impacted by some of the features available on the O-RAN system. Some of these features have been included below. As a part of the video calling services testing, details of these features shall be included in the test report to get a comprehensive view of the setup used for testing. If additional features or functionalities have been enabled during this testing that impact the end user voice experience, those need be included in the test report as well.
-
-- RLC in Unacknowledged Mode
-- Robust Header Compression
-- DRX
-- Dynamic GBR Admission Control
-- TTI Bundling
-- VoLTE Inactivity Timer
-- Frequency Hopping
-- Multi-Target RRC Connection Re-Establishment
-- VoLTE HARQ
-- Coordinated Multi Point (DL and UL)
-- VoLTE Quality Enhancement
-- Packet Loss Detection
-
-- Voice Codec Aware scheduler
-- NR to LTE PS Redirection/Cell Reselection/Handover
-- LTE to NR PS Redirection/Cell Reselection/Handover
-
-Table 7-21 provides a summary of test cases and applicable technology.
-
-**Table 7-21: ViLTE Test Case summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|-----------------------------------------------------|------------------|-----------------------|-----|-----|
-| | | | LTE | NSA | SA |
-| Test ID | Video service- Video over LTE (ViLTE) | | | | |
-| 7.6.1 | ViLTE Stationary Test | Service | Y | N/A | N/A |
-| 7.6.2 | ViLTE handover Test (intra) | Service | Y | N/A | N/A |
-| 7.6.3 | Video Service – LTE to NR / NR to LTE handover test | Service | Y | N/A | Y |
-
-### 7.6.1 ViLTE Stationary Test
-
-This test scenario validates the user’s video calling experience when the end user device (UE) is in LTE coverage and performs a video call.
-
-##### 7.6.1.1 Test Description
-
-Telecom service providers are providing video calling service to their customers and it has been gaining popularity replacing voice calls. Video over LTE (ViLTE) uses the same mechanism as VoLTE, i.e. IP packets to send and receive video & audio packets, with the IP packets being transferred over LTE. Just like VoLTE, IMS is used to setup control and data plane needed for ViLTE communication. As two-way video service is latency sensitive, the EPC core interacts with the IMS core to setup different bearers for Video traffic – QCI-5 for ViLTE control plane and QCI-2 for ViLTE data plane. This test case is applicable when UE is connected over an NSA network. This clause tests ViLTE user experience on an O-RAN system.
-
-##### 7.6.1.2 Test Setup
-
-The SUT in this test case is an O-eNB which includes the Master eNB and can include a Secondary gNB. As most of the current NSA deployment use the 4G eNB to provide video calling services, the use of a secondary gNB is optional. The Secondary gNB is included in this test scenario, but it is only applicable if the gNB plays a role in establishing the control plane or data plane for a video call. The O-eNB, gNB and the components within these shall comply with the O-RAN specifications. The O-RAN setup should support the ability to perform this testing in different radio conditions as defined in Clause 4.6. A 4G core is used to support the basic functionality to authenticate and register an end user device in order to setup a PDN connection. An IMS core is used to register the end user device to support video calling services on a 4G network. The 4G and IMS cores can be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support video calling service using ViLTE. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the video call. Going forward in this clause, these end user devices will be referred to as MO end user device and MT end user devices to represent the role they plan in the video call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This could be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The Master eNB, Secondary gNB and their components (O-eNB, O-RU, O-DU and O-CU) shall have the right configuration and software load. The end user device shall be configured with the right user credentials to be able to register and authenticate with the O-RAN system and the 4G core. The end user devices shall be provisioned with the user credentials to attach to the 4G core and register with the IMS core to perform a video call using ViLTE. The 4G core network and IMS core shall be configured to support end user devices used for testing including supporting registration, authentication and PDN connection
-
-establishment for these end user devices. This also includes provisioning the IMS core to support registration of the end user devices to make video calls over ViLTE. The locations where the radio conditions are excellent, good, fair and poor shall be identified within the serving cell.
-
-All the elements in the network like O-RAN system, 4G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the VoLTE KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system(O-eNBs and gNBs), O-RAN system shall be connected to the 4G core which in turn shall have connectivity to the IMS Core.
-
-##### 7.6.1.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 4G core and the IMS Core have all been configured as outlined in Clause 7.6.1.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same O-RAN (i.e. same O-eNB), 4G and IMS core to perform the end-to-end video call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices in excellent radio condition and ensure both end user devices connect to the 4G core over the Master O-eNB and optionally secondary gNB.
-- 2) Ensure both the MO and MT end user devices can establish a PDN connection with the 4G core. Once the PDN connection has been setup, both the end user devices shall register with the IMS core to support video calling services.
-- 3) Use the MO end user device to video call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 4) Continue to have two-way voice and video communication on the video call for at least 5 minutes before terminating it.
-- 5) Repeat the test multiple times (>10 times) and gather results.
-- 6) Repeat the above steps 1 through 5 for the MO and MT end user devices in good, fair and poor radio conditions.
-
-##### 7.6.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful PDN connection setup by the end user devices without any errors using the Master eNB and optionally the secondary gNB. Verify both the end user devices can register with the IMS core for video services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a video call between each other by dynamically setting up a QCI-2 bearer to transfer voice and video packets over RTP. Ensure the Call Setup Time is reasonable, the video and voice quality from both parties are clear and audible without one-way or intermittent muting or video freezing. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting, video freezing or video lag issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's video calling experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote network nodes can add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % –> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-These end user video calling KPI values included in Clause 7.6 shall be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report for the testing performed in different radio conditions to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and L3 PDCP layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-Table 7-22 gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-22 Example Test Report for Video over LTE Testing – Stationary Test**
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------------------------|----------------------------|-------------|-------------|---------------------|
-| | ViLTE MO/MT | ViLTE MO/MT | ViLTE MO/MT | ViLTE MO/MT |
-| Call Setup Success Rate | | | | |
-| Call Setup time | | | | |
-| MOS Score | | | | |
-| Mute Rate | | | | |
-| One Way Call | | | | |
-| RTP Packet Loss | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| MIMO rank | | | | |
-| PDSCH MCS | | | | |
-| DL RB number | | | | |
-| UE CQI | | | | |
-| UE RSRQ | | | | |
-| UE PMI | | | | |
-| UE RSSI | | | | |
-| UE Buffer status | | | | |
-| UE Packet delay | | | | |
-| PDSCH BLER [%] | | | | |
-
-The end user ViLTE experience can also be impacted by some of the features available (see Clause 7.6) on the O-eNB, O-RU, O-DU and O-CU. The details of these features, along with any other features/functionality which can impact the end user's video calling service experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.6.2 ViLTE Handover Test
-
-This test clause is for FFS.
-
-### 7.6.3 ViLTE - LTE to NR handover test
-
-This test scenario validates the user's video calling experience when the UE is in video call on LTE and performs a handover from LTE network to a 5G network and vice versa. This test scenario is applicable for a 5G SA deployment.
-
-##### 7.6.3.1 Test Description
-
-Voice service is one of the basic services provided on the telecommunication network. Video service on the 4G network was provided using ViLTE. Similarly, video service on the 5G network is provided using packet switch technology called Video over New Radio. As 5G network is being deployed by a telecommunication service provider, the service provider can need to support 4G and 5G network, and thus support Video over LTE, Video over NR and the handover between the two video calling services. This scenario tests the end user's video calling experience when the end user device performs a handover from video over LTE to Video over NR and vice versa.
-
-#### 7.6.3.2 Test Setup
-
-The SUT in this test case is an O-eNB along with a gNB (O-RU, O-DU and O-CU). An interworking 4G-5G core (referred to as 4G-5G core going forward) which supports a combined anchor point for 4G and 5G, i.e. SMF+PGW-C and UPF+PGW-U is required. The eNB connects to a 4G-5G core over the 4G interfaces like S1 to provide 4G LTE service and the O-CU, O-DU and O-RU will connect to a 4G-5G core over the 5G interfaces like N2 and N3 to provide 5G SA service. The O-eNB, gNB and the components within these shall comply with the O-RAN specifications. The 4G-5G core shall support the basic functionality to authenticate and register an end user device in order to setup a PDN connection/PDU session. An IMS core is required to register the end user device to support video calling services on a 4G and 5G network. The 4G and 5G core will interwork using the N26 interface between the MME and AMF to support seamless handover. Use of the N26 interface is recommended to ensure better customer experience when the end user device performs a handover between 4G and 5G. The 4G-5G and IMS cores can be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support video calling service using ViLTE, Video over NR and the capability to handover from ViLTE to Video over NR and vice versa. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the video call. Going forward in this clause, these end user devices are referred to as MO end user device and MT end user devices to represent their role in the video call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The O-eNB, gNB and their components (O-RU, O-DU and O-CU) shall have the right configuration and software load. The end user devices shall be configured with the right user credentials to be able to register and authenticate with the O-RAN system and the 4G-5G core. The end user devices shall be provisioned with the user credentials to support attach procedure to the 4G-5G core, registering to the IMS core and performing a video call over LTE and NR. This includes supporting registration, authentication and PDN connection/PDU Session establishment for these end user devices. This also includes provisioning the IMS core to support registration of the end user devices to make video calls over ViLTE and Video over NR, which includes dynamically setting up dedicated bearers/QoS Flows for video calls.
-
-All the elements in the network like O-RAN system, 4G-5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the ViLTE and Video over NR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall
-
-have connectivity with each other – the end user device shall be able to connect to O-RAN system(O-eNBs and gNBs), O-RAN system shall be connected to the 4G-5G core which in turn shall have connectivity to the IMS Core.
-
-#### 7.6.3.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 4G-5G core and the IMS Core have all been configured as outlined in Clause 7.6.3.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the O-eNB and gNB to connect to the same 4G-5G and IMS core to perform the end-to-end video call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-The steps to perform a video over LTE to video over NR handover, followed by video over NR to video over LTE handover are shown below.
-
-- 1) Power on the two end user devices and ensure both end user devices connect to the 4G-5G core over the O-eNB.
-- 2) Ensure both the MO and MT end user devices can establish a PDN connection with the 4G-5G core. Once the PDN connection has been established, both the end user devices shall register with the IMS core to support video calling services.
-- 3) Use the MO end user device to video call the MT end user device. Validate the MT end user device can receive and answer the video call.
-- 4) Once the two-way call has been setup and communication is going back and forth between the two end user devices, move the MO device to the O-RU coverage of the gNB, thus forcing a handover from 4G to 5G, and forcing a ViLTE to Video over NR handover. Continue two-way voice and video communication through the handover process and terminate the call once the handover process is complete. Measure the video KPIs included in Clause 7.6.
-- 5) At this point in time, the MO end user device is in 5G coverage and registered to the 4G-5G core. The MT end user device is in 4G coverage and registered to the 4G-5G core. Both end user devices should still be registered to the IMS core.
-- 6) Use the MO end user device to video call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 7) Once the two-way call has been setup and communication is going back and forth between the two end user devices, move the MO device to the O-eNB coverage, thus forcing a handover from 5G to 4G, and forcing a Video over NR to ViLTE handover. Continue the two-way voice and video communication through the handover process and terminate the call once the handover process is complete. Measure the video KPIs included in Clause 7.6.
-- 8) Repeat the test multiple times (> 10 times) and gather results.
-
-#### 7.6.3.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDN connection setup by the end user devices without any errors using the O-eNB when in 4G coverage. Similarly, use traces to validate successful registration and PDU session setup by the end user device without any errors using O-RU, O-DU and O-CU when in 5G coverage. Also validate both the end user devices can register with the IMS core for voice services. This is a prerequisite before these tests can be validated.
-
-Validate the end user devices can make a video call between each other by dynamically setting up a QCI-2/5QI-2 bearer to transfer voice and video packets over RTP. Ensure the Call Setup Time is reasonable, the video and voice quality from both parties are clear and audible without one-way or intermittent muting or video freezing. Ensure the voice and video quality is not impacted during the handover process – ViLTE to Video over NR and Video over NR to ViLTE. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting, video freezing or video lag issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's video calling experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote network nodes can add latency, jitter and packet loss issues to the
-
-connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % -> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-These end user video calling KPI values included in Clause 7.6 shall be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report for the testing performed in different radio conditions to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-Table 7-23 gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-23 Example Test Report for Video over LTE Testing – Handover Test**
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------------------------|----------------------------|-------------|-------------|---------------------|
-| | ViLTE MO/MT | ViLTE MO/MT | ViLTE MO/MT | ViLTE MO/MT |
-| Call Setup Success Rate | | | | |
-| Call Setup time | | | | |
-| MOS Score | | | | |
-| Mute Rate | | | | |
-| One Way Call | | | | |
-| RTP Packet Loss | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| MIMO rank | | | | |
-| PDSCH MCS | | | | |
-| DL RB number | | | | |
-| UE CQI | | | | |
-| UE RSRQ | | | | |
-| UE PMI | | | | |
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------|----------------------------|-------------|-------------|---------------------|
-| | ViLTE MO/MT | ViLTE MO/MT | ViLTE MO/MT | ViLTE MO/MT |
-| UE RSSI | | | | |
-| UE Buffer status | | | | |
-| UE Packet delay | | | | |
-| PDSCH BLER [%] | | | | |
-
-The end user ViLTE experience can also be impacted by some of the features available (see Clause 7.6) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which can impact the end user's video calling service experience should be included in the test report to provide a comprehensive view of the testing.
-
-## 7.7 Video Service – EPS Fallback
-
-### 7.7.0 Video service – EPS fallback test introduction
-
-Video service is quickly replacing voice service and turning into one of the basic services offered by telecommunication service providers. Upgrade of telecom network occurs in phases, and this is no different for 5G. The telecom network may not be able to support video calling service on 5G during this phase for multiple reasons – the 5G network may not be deployed nationwide, or 5G network may not be tuned to support voice/video service or the devices may not be able to support video/voice service on 5G. EPS fallback is the method used to support voice/video services during this transition phase, where voice/video services are continued to be supported on the legacy LTE network using video over LTE (ViLTE). This clause of the document only applies to the video calling service provided by the telecom service provider, which uses the telecom operator's IMS core to establish dedicated bearer to provide superior video calling experience. The KPIs which shall be monitored to assess the video calling service are included below
-
-- CSSR – Call Setup Success Rate % – Total number of calls which were successful by the total number of calls made as a percentage.
-- CST – Call Setup Time – Time taken from the initial SIP INVITE to when the SIP 180 Ringing is received in seconds.
-- MOS Score – Mean Opinion Score for the video call. This KPI shall be measured on both ends of the video call – mobile originated and mobile terminated.
-- Mute Rate % – Percentage of video calls which were muted or video freezes in both directions (calls with RTP loss of > 3-4s in both directions are considered muted call). This KPI shall be measured on both ends of the video call – mobile originated and mobile terminated and counted only once per call.
-- One Way Calls % – Percentage of video calls which were muted, or video is not transmitted in any one direction only (video calls with RTP loss of > 3-4s in one direction only are considered one-way calls). This KPI shall be monitored on both ends of the Voice call – mobile originated and mobile terminated and counted only once per call.
-- RTP Packet Loss % - Number of RTP packets which were dropped/lost in uplink/downlink direction as a percentage of total packets. This KPI shall be measured on both ends of the Voice call – mobile originated and mobile terminated.
-
-Along with the monitoring and validation of these services utilizing user experience KPIs, the O-RAN systems also shall be monitored. The end user service experience can also be impacted by some of the features available on the O-RAN system. Some of these features have been included below. As a part of the voice services testing, details of these features shall be included in the test report to get a comprehensive view of the setup used for testing. If additional features or functionalities have been enabled during this testing that impact the end user voice experience, these shall be included in the test report as well.
-
-- EPS Fallback for IMS Voice
-- NR to EPS Mobility
-
-- RLC in Unacknowledged Mode
-- Robust Header Compression
-- DRX
-- Dynamic GBR Admission Control
-- TTI Bundling
-- VoLTE Inactivity Timer
-- Frequency Hopping
-- Multi-Target RRC Connection Re-Establishment
-- VoLTE HARQ
-- Coordinated Multi Point (DL and UL)
-- VoLTE Quality Enhancement
-- Packet Loss Detection
-- Voice Codec Aware scheduler
-
-Please see Table 7-24 for a summary table of test cases and applicable technology.
-
-**Table 7-24: Video EPS Fallback Test Case summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|----------------------------|------------------|-----------------------|-----|----|
-| | | | LTE | NSA | SA |
-| Test ID | Video Service-EPS Fallback | | | | |
-| 7.7.1 | EPS Fallback Test | Service | Y | N/A | Y |
-
-### 7.7.1 Video Service – EPS Fallback testing
-
-This scenario tests the video calling service when an end user device (UE) is in 5G SA coverage and performs EPS fallback to 4G to make or receive a video call.
-
-##### 7.7.1.1 Test Description
-
-This clause tests the video service on a 5G SA network when it uses EPS fallback mechanism to fallback to the LTE network to use video over LTE to support video calling service. This testing only applies to 5G SA deployment and in this scenario the UE is connected to the 5G SA Core and registered with the IMS core for video calling service. As video calling service is not supported on 5G yet, the UE is forced to fallback to 4G when it makes/receives a video call. The EPS fallback does increase the Call Setup Time due to the time needed to fallback before making/receiving the video call.
-
-There are two mechanisms in which EPS fallback is supported on the 5G core, and the methodology used impacts the time taken to perform the fallback to LTE, and hence impacts the Call Setup Time. The two mechanisms that may be used to perform EPS fallback are included below. These two mechanisms do change the test setup, but does not change the testing procedure.
-
-- With N26 interface – The AMF in the 5G core communicates with the MME in the 4G over the N26 interface. In this scenario the UE performs a handover from the 5G network to the 4G network.
-- Without N26 interface – The AMF in the 5G core does not communicate directly with the 4G core, instead uses the UDM/HSS to store and transfer relevant session information to the 4G core. In this scenario the UE performs a Release with Redirect from the 5G network to the 4G network.
-
-##### 7.7.1.2 Test Setup
-
-The SUT in this test case is an O-eNB along with a gNB (O-RU, O-DU and O-CU-CP/O-CU-UP). An interworking 4G-5G core (referred to as 4G-5G core going forward) which supports a combined anchor point, i.e. SMF+PGW-C and UPF+PGW-U is required. The O-eNB connects to a 4G-5G core over the 4G interfaces like S1 to provide 4G LTE service and the gNB (O-RU, O-DU and O-CU-CP/O-CU-UP) will connect to the 4G-5G core over the 5G interfaces like N2 and N3 to provide 5G SA service. The O-eNB, gNB and the components within these shall comply with the O-RAN specifications and support EPS fallback. The 4G-5G core will support the basic functionality to authenticate and register an end user device in order to setup a PDN connection/PDU session. The IMS core will register the end user device and will be integrated with the 4G-5G core to support video calling services over LTE (ViLTE) and EPS fallback. The 4G-5G core will interwork either using the N26 interface or without using N26 interface depending on the desired core network configuration. The existence of the N26 interface does reduce the EPS fallback time, hence reducing Call Setup Time and provides better end user experience. The 4G-5G and IMS cores may be a completely emulated, partially emulated or real non-emulated core. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support video calling service using ViLTE and EPS fallback procedure. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the video call. For the sake of clarity, these end user devices will be addressed as UE-1 and UE-2 in this clause. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The O-eNB, gNB and their components (O-RU, O-DU and O-CU-CP/O-CU-UP) shall have the right configuration and software load. The end user device shall be configured with the right user credentials to be able to register and authenticate with the O-RAN system and the 4G-5G core. The end user devices shall be provisioned with the user credentials to attach to the 4G-5G core and register with the IMS core to perform video call using ViLTE and EPS fallback. The 4G-5G core network and IMS core shall be configured to support video calling service on the end user device used for testing, which includes dynamically setting up dedicated bearers for video calls.
-
-All the elements in the network like O-RAN system, 4G-5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the ViLTE KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to O-RAN system(O-eNBs and gNBs), O-RAN system shall be connected to the 4G-5G core which in turn shall have connectivity to the IMS Core.
-
-#### 7.7.1.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 4G-5G core and the IMS Core have all been configured as outlined in Clause 7.7.1.2. In this test scenario, one of the end user devices (UE-1) will be connected over the 4G O-eNB to the 4G-5G core, while the other end user device (UE-2) will be connected over 5G gNB (O-RU, O-DU and O-CU-CP/O-CU-UP) to the 4G-5G core. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices and ensure UE-1 is in LTE coverage, and UE-2 is in the 5G coverage. Validate both end user devices register to the 4G-5G core.
-- 2) Once the registration is complete, UE-1 and UE-2 shall establish a PDN connection and PDU session respectively with the 4G-5G core. Once the PDN connection and PDU session have been setup, both the end user devices shall register with the IMS core to support video calling services.
-- 3) Use UE-1 as the MO end user device to video call UE-2. Validate the UE-2 performs EPS fallback to LTE to receive the video call.
-- 4) Answer the call on UE-2 and continue to have two-way audio/video communication for at least 5 minutes and terminate the call. Measure the voice KPIs included in Clause 7.7.
-- 5) At this point UE-2 should have completed the video call and moved back to connect to the 4G-5G Core over 5G gNB (i.e. O-RU).
-
-- 6) Use UE-2 as the MO end user device to call UE-1. Validate the UE-2 performs EPS fallback to LTE before making the video call.
-- 7) Answer the call on UE-1 and continue to have two-way communication for at least 5 minutes and terminate the call. Measure the voice KPIs included in Clause 7.7.
-- 8) Repeat the test multiple times (>10 times) and gather results.
-
-#### 7.7.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate end user device UE-1 can perform a successful registration and PDN connection setup while using the O-eNB in LTE coverage. Similarly, use the traces to validate end user device UE-2 can perform a successful registration and PDU session setup while using gNB in 5G coverage. Verify both the end user devices can register with the IMS core for voice services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a video call between each other by dynamically setting up a QCI-2 bearer to transfer voice and video packets over RTP. Validate the device which is in the 5G coverage falls back to 4G before receiving or making a video call, in other words the EPS fallback procedure was executed successfully. The Call Setup Time will be higher than Video over LTE due to the delay associated with executing the EPS fallback procedure. Even though this test case does not directly impact the quality of the video call, for the sake of consistency, ensure the voice and video quality from both parties are clear and audible without one-way or intermittent muting and video freezing. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting, video freezing and video lag issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's video calling experience.
-
-The average range of values for the KPIs are included in Table 7-25 for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote network nodes can add latency, jitter and packet loss issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-**Table 7-25 Typical Video KPI values in controlled environments with good radio conditions**
-
-| KPI | With N26 Interface | Without N26 Interface |
-|----------------------------------|--------------------|-----------------------|
-| CSSR – Call Setup Success Rate % | >99% | >99% |
-| CST – Call Setup Time | 3.5s | 4 s |
-| MOS Score | 3.5 | 3.5 |
-| Mute Rate % | < 1% | < 1% |
-| One Way Call % | < 1% | < 1% |
-| RTP Packet Loss % | < 1% | < 1% |
-
-These end user video calling KPI values included in Clause 7.7 shall be included in the test report along with the minimum configuration parameters included in Clause 4.3. The following information should also be included in the test report for the testing performed to provide a comprehensive view of the test setup.
-
-End user device side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Received downlink throughput (L1 and L3 PDCP layers) (average sample per second)
-- Downlink transmission mode
-
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-Table 7-26 gives an example of the test report considering the mean and standard deviation of all test results that have been captured.
-
-**Table 7-26 Example Test Report for Video Calling Service Testing – EPS Fallback**
-
-| | EPS Fallback MO | EPS Fallback MT |
-|------------------------------------|-----------------|-----------------|
-| Call Setup Success Rate | | |
-| Call Setup time | | |
-| MOS Score | | |
-| Mute Rate | | |
-| One Way Call | | |
-| RTP Packet Loss | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user ViLTE experience can also be impacted by some of the features available (see Clause 7.7) on the O-eNB, O-RU, O-DU and O-CU-CP/O-CU-UP. The details of these features, along with any other features/functionality which can impact the end user’s video calling experience should be included in the test report to provide a comprehensive view of the testing.
-
-## 7.8 Video Service – Video over NR
-
-### 7.8.0 Video over NR test introduction
-
-Video calling service is slowly replacing voice as a basic calling service. The improvement in end user throughput on LTE has facilitated the move from voice call to video, and the high speeds on 5G is only going to accelerate this migration process. This clause of the document validates the user’s video calling experience in different conditions on the 5G network. This clause of the document only applies to the video calling service provided by the telecom service provider, which uses the telecom operator’s IMS core to establish dedicated QoS flows to provide superior video calling experience. The KPIs which shall be monitored to assess the video calling service are included below
-
-- CSSR – Call Setup Success Rate % – Total number of calls which were successful by the total number of calls made as a percentage.
-
-- CST – Call Setup Time – Time taken from the initial SIP INVITE to when the SIP 180 Ringing is received in seconds.
-- MOS Score – Mean Opinion Score for the video call. This KPI shall be measured on both ends of the video call – mobile originated and mobile terminated.
-- Mute Rate % – Percentage of video calls which were muted or video freezes in both directions (calls with RTP loss of > 3-4s in both directions are considered muted call). This KPI shall be measured on both ends of the video call – mobile originated and mobile terminated and counted only once per call.
-- One Way Calls % – Percentage of video calls which were muted, or video is not transmitted in any one direction only (video calls with RTP loss of > 3-4s in one direction only are considered one-way calls). This KPI shall be monitored on both ends of the Voice call – mobile originated and mobile terminated and counted only once per call.
-- RTP Packet Loss % - Number of RTP packets which were dropped/lost in uplink/downlink direction as a percentage of total packets. This KPI shall be measured on both ends of the Voice call – mobile originated and mobile terminated.
-
-End user video calling service experience can also be impacted by some of the features available on the SUT (O-RU, O-DU and O-CU-CP/O-CU-UP). Some of these features have been included below. As a part of the video calling services testing, details of these features shall be included in the test report to get a comprehensive view of the setup used for testing. If additional features or functionalities have been enabled during this testing that impact the end user voice experience, these shall be included in the test report as well.
-
-- Basic Voice over NR
-- RLC in Unacknowledged Mode
-- Robust Header Compression
-- DRX
-- Dynamic GBR Admission Control
-- TTI Bundling
-- Automated Neighbor Relations ANR
-- Connected mode mobility (Handover)
-- idle mode reselection
-- Intra-frequency Cell Reselection/Handover
-- Inter-frequency Redirection/Cell Reselection/Handover
-- NR Coverage-Triggered NR Session Continuity
-
-Please see Table 7-27 for a summary of test cases and applicable technology.
-
-**Table 7-27: Video over NR Test Case summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|----------------------------------------|------------------|-----------------------|-----|----|
-| | | | LTE | NSA | SA |
-| Test ID | Video service- Video over NR | | | | |
-| 7.8.1 | Video over NR Test – stationary | Service | N/A | N/A | Y |
-| 7.8.2. | Video – Intra O-DU handover | Service | N/A | N/A | Y |
-| 7.8.3 | Video – Intra O-CU/Inter O-DU handover | Service | N/A | N/A | Y |
-| 7.8.4 | Video – Inter O-CU handover | Service | N/A | N/A | Y |
-
-### 7.8.1 Video over NR – Stationary Testing
-
-This test scenario validates the user's video calling experience when the end user device (UE) makes a video call on the 5G network.
-
-##### 7.8.1.1 Test Description
-
-This clause of the document tests video over NR user experience on an O-RAN system. Video over NR is similar to ViLTE where it uses IP packets to send and receive audio/video packets, with the IP packets being transferred over NR or 5G radio. Just like ViLTE, IMS is used to setup the control and data plane for the video communication. As video calling service is latency sensitive, the 5G core interacts with the IMS core to setup different QoS flows for video traffic – 5QI-5 for control plane and 5QI-1 and 5QI-2 for data plane. This test case is applicable when UE is connected over a 5G SA network.
-
-##### 7.8.1.2 Test Setup
-
-The SUT as defined in Clause 4.1.0 is used to test the video calling service. A 5G SA Core is required to support basic functionality to authenticate and register the end user device to establish a PDU session. An IMS core is required to register the end user device to support video calling services on a 5G network. The 5G and IMS cores may be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be a real UEs or emulated, and both shall support video calling service using Video over NR. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the video call. Going forward in this clause, these end user devices will be referred to as MO end user device and MT end user device to represent their role in the video call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The SUT shall have the right configuration and software load. The SUT shall be setup to run this testing in different radio conditions as outlined in Clause 4.6. The end user device shall be configured with the right user credentials to be able to register and authenticate with the SUT and the 5G core. The end user devices shall be provisioned with the user credentials to register and setup PDU session with the 5G core and register with the IMS core to perform video call using Video over NR. The 5G core network and IMS core shall be configured to support video calling service on the end user devices used for testing, which includes the ability to dynamically set up QoS Flows for video calls. The locations where the radio conditions are excellent, good, fair and poor shall be identified within the serving cell.
-
-All the elements in the network like SUT, 5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the Video over NR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to SUT(O-RU, O-DU and O-CU-CP/O-CU-UP), SUT shall be connected to the 5G core which in turn shall have connectivity to the IMS Core.
-
-##### 7.8.1.3 Test Methodology/Procedure
-
-Ensure the end user devices, O-RAN system, 5G core and the IMS core have all been configured as outlined in Clause 7.8.1.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same O-RAN system, 5G and IMS core to perform the end-to-end video call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices in excellent radio condition and ensure both devices register with the 5G core for video calling services over SA by connecting over the SUT (O-RU, O-DU and O-CU-CP/O-CU-UP).
-- 2) Once the registration is complete, the MO and MT end user devices shall establish a PDU session with the 5G core. Once the PDU session has been setup, both the end user devices shall register with the IMS core to support video calling services.
-- 3) Use the MO end user device to video call the MT end user device. Validate the MT end user device can receive and answer the call.
-
-- 4) Continue to have two-way audio/video communication on the video call for at least 5 minutes before terminating it.
-- 5) Repeat the test multiple times (> 10 times) and gather results.
-- 6) Repeat the above steps 1 through 5 for good, fair and poor radio conditions.
-
-##### 7.8.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup by the end user devices without any errors over SUT. Also validate both the end user devices can register with the IMS core for video calling services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a video call between each other by dynamically setting up a 5QI-1 and 5QI-2 bearer to transfer voice and video packets over RTP. Ensure the Call Setup Time is reasonable, the voice and video quality from both parties are clear and audible without one-way or intermittent muting and video freezing. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting, video freezing or video lag issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer’s voice experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio condition without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote servers/hosts can add latency, jitter and reliability issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % –> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-As a part of gathering data, ensure the minimum configuration parameters included in Clause 4.3 are included in the test report. The information in Table 7-28 should also be included in the test report to provide a comprehensive view of the test setup.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-28 Example Test Report for Video over NR – Stationary Testing**
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|-------------------------|----------------------------|------------------------|------------------------|------------------------|
-| | Video over NR
MO/MT | Video over NR
MO/MT | Video over NR
MO/MT | Video over NR
MO/MT |
-| Call Setup Success Rate | | | | |
-| Call Setup Time | | | | |
-| MOS Score | | | | |
-| Mute Rate % | | | | |
-
-| | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------------------------|----------------------------|------------------------|------------------------|------------------------|
-| | Video over NR
MO/MT | Video over NR
MO/MT | Video over NR
MO/MT | Video over NR
MO/MT |
-| One Way Call % | | | | |
-| RTP Packet Loss % | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| MIMO rank | | | | |
-| PDSCH MCS | | | | |
-| DL RB number | | | | |
-| UE CQI | | | | |
-| UE RSRQ | | | | |
-| UE PMI | | | | |
-| UE RSSI | | | | |
-| UE Buffer status | | | | |
-| UE Packet delay | | | | |
-| PDSCH BLER [%] | | | | |
-
-The end user video calling service experience can also be impacted by some of the features available (see Clause 7.8) on the SUT. The details of these features, along with any other features/functionality which can impact the end user's video calling service experience should be included in the test report to provide a comprehensive view of the testing.
-
-#### 7.8.2 Video over NR – Intra O-DU handover
-
-This test scenario validates the user's video calling experience when the end user device (UE) is on a video call over NR and performs a handover between O-RUs which connect to the same O-DU (Intra O-DU handover).
-
-##### 7.8.2.1 Test Description
-
-The 5G O-RAN system has multiple components such as the O-RU, O-DU and the O-CU-CP/O-CU-UP. This setup leads to multiple handover scenarios between the O-RAN components. This scenario tests the end user's video calling experience during the handover between two O-RUs which are connected to the same O-DU (and O-CU-CP/O-CU-UP), hence an Intra O-DU handover. This handover will be agnostic to the 5G core as the handover occurs on the O-RAN system. This test assesses the impact on the end user's voice service in this handover scenario by monitoring the KPIs included in Clause 7.8.
-
-##### 7.8.2.2 Test Setup
-
-The SUT in this test case is a pair of O-RUs which connect to the same O-DU and O-CU-CP/O-CU-UP. This O-RAN setup is used to test the video calling service during a handover (refer Clause 5.4). A 5G SA Core is required to support basic functionality to authenticate and register the end user device to establish a PDU session. An IMS core is required to register the end user device to support video calling services on a 5G network. The 5G and IMS cores may be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support video calling service using 5G – Video over NR. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the video call. Going forward in this clause, these end user devices will be referred to as MO end user device and MT end user device to represent their role in the video call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool.
-
-Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The pair of O-RUs (O-RU1 and O-RU2) shall be connected to the O-DU and O-CU-CP/O-CU-UP and all the components shall have the right configuration and software load. The end user devices shall be configured with the right user credentials to be able to register and authenticate with the O-RAN system and the 5G core. The end user devices shall be provisioned with the user credentials to register and setup PDU session with the 5G core and register with the IMS core to perform video call using Video over NR. The 5G core network and IMS core shall be configured to support video service on the end user devices used for testing, which includes the ability to dynamically set up QoS Flows for voice calls.
-
-All the elements in the network like SUT, 5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the Video over NR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to SUT SUT shall be connected to the 5G core which in turn shall have connectivity to the IMS Core.
-
-##### 7.8.2.3 Test Methodology/Procedure
-
-Ensure the end user devices, SUT, 5G core and the IMS core have all been configured as outlined in Clause 7.8.2.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same SUT, 5G and IMS core to perform the end-to-end video call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices and ensure both devices register with the 5G core for video calling services over SA by connecting over the SUT. Ensure both the MO & MT end user devices are in the coverage area of the same O-RU – O-RU1.
-- 2) Once the registration is complete, the MO and MT end user devices shall establish PDU session with the 5G core. Once the PDU session has been setup, both the end user devices shall register with the IMS core to support voice services.
-- 3) Use the MO end user device to video call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 4) Once the call has been setup, move the MO end user device from the coverage area of O-RU1 to coverage area of O-RU2, triggering a handover from O-RU1 to O-RU2.
-- 5) Continue the two-way video and voice communication between MO and MT end user devices until the handover procedure is complete before terminating the video call.
-- 6) Repeat the test (steps 1 through 5) multiple times (> 10 times) and gather results.
-
-##### 7.8.2.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup by the end user devices without any errors over SUT. Also validate both the end user devices can register with the IMS core for video calling services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a video call between each other by dynamically setting up a 5QI-1 and 5QI-2 bearer to transfer voice and video packets over RTP. Ensure the Call Setup Time is reasonable, the voice and video quality from both parties are clear and audible without one-way or intermittent muting and video freezing, for the duration of the call, especially during the handover process. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting, video freezing or video lag issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's voice experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio conditions without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote servers/hosts can add latency, jitter and reliability issues to the
-
-connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % –> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-As a part of gathering data, the minimum configuration parameters in Clause 4.3 shall be included in the test report. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-29 Example Test Report for Video over NR – Intra O-DU Handover**
-
-| | Video over NR MO | Video over NR MT |
-|------------------------------------|------------------|------------------|
-| Call Setup Success Rate | | |
-| Call Setup Time | | |
-| MOS Score | | |
-| Mute Rate % | | |
-| One Way Call % | | |
-| RTP Packet Loss % | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-
-| | Video over NR MO | Video over NR MT |
-|----------------|------------------|------------------|
-| PDSCH BLER [%] | | |
-
-The end user video calling service experience can also be impacted by some of the features available (see Clause 7.8) on the SUT. The details of these features, along with any other features/functionality which can impact the end user's video calling service experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.8.3 Video over NR – Intra O-CU/Inter O-DU handover
-
-This test scenario validates the user's video calling experience when the end user device (UE) is on a video call and performs a handover between O-RUs which connect to different O-DUs which in turn are connected to the same O-CU-CP/O-CU-UP (Intra O-CU/Inter O-DU handover)
-
-#### 7.8.3.1 Test Description
-
-The 5G O-RAN system has multiple components such as the O-RU, O-DU and the O-CU-CP/O-CU-UP. This setup leads to multiple handover scenarios between the O-RAN components. This particular scenario tests the end user's video calling experience during the handover between two O-RUs, where the O-RUs are connected to different O-DUs which in turn are connected to the same O-CU-CP/O-CU-UP, hence an Intra O-CU/Inter O-DU handover. This handover will be agnostic to the 5G core as the handover occurs on the O-RAN system. This test assesses the impact on the end user's voice service in this handover scenario by monitoring the KPIs included in Clause 7.8.
-
-#### 7.8.3.2 Test Setup
-
-The SUT in this test case is a pair of O-RUs which connect to a different pair of O-DUs, which in turn connect to the same O-CU-CP/O-CU-UP (refer Clause 4.5). This O-RAN setup is used to test the video service during a handover. A 5G SA Core is required to support basic functionality to authenticate and register the end user device to establish a PDU session. An IMS core is required to register the end user device to support voice services on a 5G network. The 5G and IMS cores can be completely emulated, partially emulated or real non-emulated. At least two end user devices (UE) shall be used, which can be real UEs or emulated, and both shall support video calling service using Video over NR. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the video call. Going forward in this clause, these end user devices are referred to as MO end user device and MT end user device to represent their role in the voice call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The pair of O-RUs (O-RU1 and O-RU2) shall be connected to a pair of O-DUs (O-DU1 and O-DU2) and O-CU-CP/O-CU-UP. As for the O-RU to O-DU connection, O-RU1 shall connect to O-DU1, and O-RU2 shall connect to O-DU2, and both O-DUs connect to the same O-CU-CP/O-CU-UP. All the O-RAN components shall have the correct configuration and software load. The end user devices shall be provisioned with the user credentials to register and setup PDU session with the 5G core and register with the IMS core to perform video calls using Video over NR. The 5G core network and IMS core shall be configured to support video calling service on the end user devices used for testing, which includes the ability to dynamically set up QoS Flows for video calls.
-
-All the elements in the network like SUT, 5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the Video over NR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to SUT, SUT shall be connected to the 5G core which in turn shall have connectivity to the IMS Core.
-
-#### 7.8.3.3 Test Methodology/Procedure
-
-Ensure the end user devices, SUT, 5G core and the IMS Core have all been configured as outlined in Clause 7.8.3.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same SUT, 5G and IMS core to perform the end-to-end video call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices and ensure both devices register with the 5G core for video calling services over SA by connecting over the SUT. Both the MO & MT end user devices shall be in the coverage area of the same O-RU – O-RU1.
-- 2) Once the registration is complete, the MO and MT end user devices shall establish a PDU session with the 5G core. Once the PDU session has been setup, both the end user devices shall register with the IMS core to support video calling services.
-- 3) Use the MO end user device to video call the MT end user device. Validate the MT end user device can receive and answer the call.
-- 4) Once the video call has been setup, move the MO end user device from the coverage area of O-RU1 to coverage area of O-RU2, thus causing a handover from O-RU1 to O-RU2, and O-DU1 to O-DU2.
-- 5) Continue the two-way video and voice communication between the end user devices until the handover procedure is complete before terminating the video call.
-- 6) Repeat the test (steps 1 through 5) multiple times (> 10 times) and gather results.
-
-##### 7.8.3.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup by the end user devices without any errors over SUT. Also validate both the end user devices can register with the IMS core for video calling services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a video call between each other by dynamically setting up a 5QI-1 and 5QI-2 bearer to transfer voice and video packets over RTP. Ensure the Call Setup Time is reasonable, the voice and video quality from both parties are clear and audible without one-way or intermittent muting and video freezing, through the duration of the call, especially during the handover process. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which could cause voice muting, video freezing or video lag issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's voice experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio conditions without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote servers/hosts can add latency, jitter and reliability issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % –> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-As a part of gathering data, ensure the minimum configuration parameters in Clause 4.3 are included in the test report. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-30 Example Test Report for Video over NR – Intra O-CU/Inter O-DU Handover**
-
-| | Video over NR MO | Video over NR MT |
-|------------------------------------|------------------|------------------|
-| Call Setup Success Rate | | |
-| Call Setup Time | | |
-| MOS Score | | |
-| Mute Rate % | | |
-| One Way Call % | | |
-| RTP Packet Loss % | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user video calling service experience can also be impacted by some of the features available (see Clause 7.8) on the SUT. The details of these features, along with any other features/functionality which can impact the end user’s video calling service experience should be included in the test report to provide a comprehensive view of the testing.
-
-### 7.8.4 Video over NR – Inter O-CU handover
-
-This test scenario validates the user’s video calling experience when the end user device (UE) is on a video call and performs a handover between O-RUs which connect to different O-DUs and different O-CU-CP/O-CU-UPs (Inter O-CU handover)
-
-#### 7.8.4.1 Test Description
-
-The 5G O-RAN system has multiple components such as the O-RU, O-DU and the O-CU-CP/O-CU-UP. This setup leads to multiple handover scenarios between the O-RAN components. This particular scenario tests the end user’s video calling experience during the handover between two O-RUs, where the O-RUs are connected to different O-DUs which in turn are connected to different O-CU-CP/O-CU-UPs, hence an Inter O-CU handover. This handover occurs on the O-RAN system and
-
-the 5G core is aware of the handover as it needs to send data to a new O-CU-CP/O-CU-UP as a part of the handover process. This test assesses the impact on the end user's voice service in this handover scenario by monitoring the KPIs included in Clause 7.8.
-
-#### 7.8.4.2 Test Setup
-
-The SUT in this test case is a pair of O-RAN sub-systems, a set of O-RU, O-DU and O-CU-CP/O-CU-UP which interconnects with another set of O-RU, O-DU and O-CU-CP/O-CU-UP (refer Clause 5.6). This O-RAN setup is used to test the video calling service during a handover. A 5G SA Core is required to support basic functionality to authenticate and register the end user device to establish a PDU session. An IMS core is required to register the end user device to support video services on a 5G network. The 5G and IMS cores can be completely emulated, partially emulated or real non-emulated cores. At least two end user devices (UE) shall be used, which can be a real UEs or emulated, and both shall support video calling service using Video over NR. The end user devices will serve as Mobile Originated (MO) and Mobile Terminated (MT) end user devices forming the two ends of the video call. Going forward in this clause, these end user devices are referred to as MO end user device and MT end user device to represent their role in the video call. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This can be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the internet, the additional latency should be calculated and accounted for.
-
-The pair of O-RAN (O-RAN1 and O-RAN2) sub-systems shall be connected – O-RU1 shall be connected to O-DU1, which in turn shall be connected to O-CU-CP/O-CU-UP1 and similarly O-RU2 shall be connected to O-DU2, which in turn shall be connected to O-CU-CP/O-CU-UP2. The O-CU-CP/O-CU-UP1 and O-CU-CP/O-CU-UP2 nodes shall be connected to each other and the 5G core. All the O-RAN components shall have the correct configuration and software load. The end user devices shall be configured with the correct user credentials to be able to register and authenticate with the O-RAN system and the 5G core. The end user devices shall be provisioned with the user credentials to register and setup PDU session with the 5G core and register with the IMS core to perform video call using Video over NR. The 5G core network and IMS core shall be configured to support video calling service on the end user devices used for testing, which includes the ability to dynamically set up QoS Flows for video calls.
-
-All the elements in the network like SUT, 5G core and the IMS Core should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the Video over NR KPIs. Optionally, the network can have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. Finally, all these different components shall have connectivity with each other – the end user device shall be able to connect to SUT, SUT shall be connected to the 5G core which in turn shall have connectivity to the IMS Core.
-
-#### 7.8.4.3 Test Methodology/Procedure
-
-Ensure the end user devices, SUT, 5G core and the IMS Core have all been configured as outlined in Clause 7.8.4.2. In this test scenario, both the mobile originated and mobile terminated end user devices will use the same SUT, 5G and IMS core to perform the end-to-end video call. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the two end user devices and ensure both devices register with the 5G core for video calling services over SA by connecting over the O-RAN1 sub-system (O-RU1, O-DU1 and O-CU-CP/O-CU-UP1). Both the MO & MT end user devices shall be in the coverage area of the same O-RU – O-RU1.
-- 2) Once the registration is complete, the MO and MT end user devices shall establish a PDU session with the 5G core. Once the PDU session has been setup, both the end user devices shall register with the IMS core to support video calling services.
-- 3) Use the MO end user device to video call the MT end user device. Validate the MT end user device can receive and answer the video call.
-- 4) Once the call has been setup, move the MO end user device from the coverage area of O-RU1 to coverage area of O-RU2, thus causing a handover from O-RAN1 to O-RAN2 sub-system - O-RU1 to O-RU2, O-DU1 to O-DU2 and O-CU-CP/O-CU-UP1 to O-CU-CP/O-CU-UP2.
-
-- 5) Continue the two-way video and voice communication between MO and MT end user devices until the handover procedure is complete before terminating the video call.
-- 6) Repeat the test (steps 1 through 5) multiple times (> 10 times) and gather results.
-
-#### 7.8.4.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup by the end user devices without any errors over SUT. Also validate both the end user devices can register with the IMS core for video calling services. This is a prerequisite before these tests can be completed.
-
-Validate the end user devices can make a video call between each other by dynamically setting up a 5QI-1 and 5QI-2 bearer to transfer voice and video packets over RTP. Ensure the Call Setup Time is reasonable, the voice and video quality from both parties are clear and audible without one-way or intermittent muting and video freezing, through the duration of the call, especially during the handover process. Use the packet captures to validate there are no RTP packet drops or high RTP packet jitter which can cause voice muting, video freezing or video lag issues. Use the packet captures to ensure there are no out-of-sequence packets which can impact customer's video experience.
-
-The average range of values for the KPIs are included below for guidance. These values are applicable when the testing is performed in a controlled environment in good radio conditions without the interference of external factors which can impact the KPIs. For example: use of internet to connect to remote servers/hosts can add latency, jitter and reliability issues to the connection, thus impacting the KPIs. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure in the SUT.
-
-- CSSR – Call Setup Success Rate % -> 99%.
-- CST – Call Setup Time – < 2.5s
-- MOS Score – > 3.5
-- Mute Rate % – < 1%
-- One Way Call % - < 1%
-- RTP Packet Loss % - < 1%
-
-As a part of gathering data, ensure the minimum configuration parameters in Clause 4.3 are included in the test report. The following information should also be included in the test report to provide a comprehensive view of the test setup.
-
-UE side (real or emulated UE):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-31 Example Test Report for Video over NR – Inter O-CU Handover**
-
-| | Video over NR MO | Video over NR MT |
-|-------------------------|------------------|------------------|
-| Call Setup Success Rate | | |
-| Call Setup Time | | |
-| MOS Score | | |
-| Mute Rate % | | |
-| One Way Call % | | |
-
-| | Video over NR MO | Video over NR MT |
-|------------------------------------|------------------|------------------|
-| RTP Packet Loss % | | |
-| L1 DL Spectral efficiency [bps/Hz] | | |
-| UE RSRP [dBm] | | |
-| UE PDSCH SINR [dB] | | |
-| MIMO rank | | |
-| PDSCH MCS | | |
-| DL RB number | | |
-| UE CQI | | |
-| UE RSRQ | | |
-| UE PMI | | |
-| UE RSSI | | |
-| UE Buffer status | | |
-| UE Packet delay | | |
-| PDSCH BLER [%] | | |
-
-The end user video calling service experience can also be impacted by some of the features available (see Clause 7.8) on the SUT. The details of these features, along with any other features/functionality which can impact the end user's video calling service experience should be included in the test report to provide a comprehensive view of the testing.
-
-## 7.9 URLLC
-
-### 7.9.0 URLLC test introduction
-
-The 5G network has been built not just to support the data and voice use-cases of the past, but a wide variety of use-cases to support connectivity across a diverse set of verticals, such as industrial automation, health care, gaming etc. The 5G network was built with flexibility and efficiency with additional enhancements being added in every release to enable ultra-low latency or ultra-reliability to cater to a diverse set of use-cases such as: automotive applications, augment and virtual reality etc. Network slicing in 5G allows the separation of the network where services with different characteristics and requirements can be run on separate slices of the network. These enhancements in 5G, paired up with network slicing capability, allows a telecommunication service provider to support all the diverse set of use-cases using the same 5G network and different network slices.
-
-Ultra-Reliable Low Latency Communication (URLLC) is one such use case which allows service which require low end to end latency to be deployed. As this is a new concept, new services and use-cases are being created to use this slice of the network. The generic KPIs which will be monitored to assess the URLLC use cases are included below. As the URLLC use cases vary, the KPI used and the values for these KPIs also vary by use case. Not all KPIs are used for all use cases and similarly some KPIs are used only in specific use cases.
-
-- Reliability – This is the percentage of packets or messages sent which were successfully delivered to the end node.
-- End to End Latency – The time required to transfer a packet or message from the end user device to the application or vice versa.
-- Jitter – The variation of the end-to-end latency values measured in the network setup over the transmission of multiple packets or messages.
-- Position Service Accuracy – The distance between the location provided by the location service and the real location of the target object.
-
-- Position Service Latency – The time elapsed between the request to get location information to when the location information is available.
-- User experienced throughput – The network throughput as measured on the application layer.
-- Mean time between failures – The duration of time the service was available before a failure condition which causes the service to be unavailable.
-
-This clause provides the procedure to test the URLLC applications in a telecommunication network. URLLC refers to a diverse set of applications where the end-user device communicates to the application server over the 5G network. The use-case itself has stringent requirements for the end-to-end latency and reliability between the end-user device and application server. 5G has enhancements within the RAN and core to support these requirements for the URLLC use cases. The 5G RAN allows for lower downlink data to uplink Ack, thus reducing the latency on the air interface. Similarly, the 5G Core allows for the data plane anchor (UPF) to be deployed close to the end user device in the edge location along with the application server to eliminate part of the backhaul latency.
-
-Please see the below summary table of test cases and applicable technology.
-
-**Table 7-32: Augmented Reality Test Case summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|-------------------------|------------------|-----------------------|-----|----|
-| | | | LTE | NSA | SA |
-| Test ID | URLLC-Augmented Reality | | | | |
-| 7.9.1 | Augmented Reality | Service | N/A | N/A | Y |
-
-### 7.9.1 Augmented Reality
-
-This test scenario validates the end user’s augmented reality experience when using an AR device over the 5G network.
-
-#### 7.9.1.1 Test Description
-
-This clause uses Augmented Reality (AR) as an example application, where the end user device is an AR device which communicates with an image processing server acting as the application server. AR has a wide range of applications including gaming, augmented worker as a part of smart factory, remote maintenance, ad-hoc support from remote expert, control of heavy equipment, etc. AR is one use case where the AR device has a camera and continuously transmits images in real time to an application server, along with the position of the AR device. The application server in this use case would be an image processing server, which render the augmented image and transmits the augmented video stream back down to the AR device, that then displays the image on the AR device. The entire process of uploading the image from the AR device, to the processing on the application server, and the displaying of the augmented image on the AR device needs to occur within milliseconds, with high reliability, to ensure the end user has a realistic augmented reality experience.
-
-The 5G URLLC network slice does not have requirements on the protocol, or the method used to communicate between the end user device and the application server. The 5G network slice acts as a pipe to allow communication between these two end points, AR device and application server, with high data rate, high reliability and low latency requirements as dictated by the application. Optionally, depending on the AR use case two additional KPIs could also be monitored when audio-visual interaction is characterized by a human being interacting with entities or humans by relying on audio-visual feedback.
-
-- Motion to photon – The latency (measured time) between the physical movement of the user’s head and the updated image on the AR device.
-- Motion to audio – The latency (measured time) between the physical movement of the user’s head and the updated sound waves from the AR device’s speakers.
-
-#### 7.9.1.2 Test Setup
-
-The SUT as defined in Clause 4.1.0 is used to test the URLLC use case. A 5G SA Core would be required to support basic functionality to authenticate and register the end user device to establish a PDU session. An image processing server would act as an application server for this test scenario. The 5G core and application server may be a completely emulated, partially emulated or real non-emulated core and image processing server. An end user device would be an AR device for this test scenario, which may be a customized device, such as AR based eyeglass, or an AR based head mounted device or a generic handset which support AR or any AR end user device support this use case. For testing this use case, a real end user device or an emulated one may be used. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This may be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the Internet, the additional latency should be calculated and accounted for.
-
-The SUT shall have the correct configuration and software load. The SUT shall also be setup to run this testing in different radio conditions as outlined in Clause 4.6. The end user device shall be configured with the correct user credentials to be able to register and authenticate with the SUT and the 5G core. The 5G core may be distributed with the UPF deployed at the edge location along with the application server to support the stringent latency requirement of the AR use case. The end user device also shall be provisioned with the user credentials to register and set up the PDU session with the 5G core and to authenticate/communicate with the application server. The application server shall be configured and provisioned with all the necessary information, including relevant images and data to support the AR use case. The locations where the radio conditions are excellent, good, fair and poor shall be identified within the serving cell.
-
-All the elements in the network, such as the SUT, 5G core, and the application server should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the KPIs. Optionally, the network may have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. All these different components shall have connectivity with each other – the end user device shall be able to connect to SUT, SUT shall be connected to the 5G core which in turn shall have connectivity to the application server.
-
-#### 7.9.1.3 Test Methodology/Procedure
-
-Ensure the end user devices, SUT, 5G core and the application server have all been configured as outlined in Clause 7.9.1.2. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the end user device in excellent radio condition and ensure the device registers with the 5G core over SA by connecting over the SUT.
-- 2) Once the registration is complete, the end user device shall establish a PDU session over the URLLC network slice, followed by connection to the application server.
-- 3) Use the end user device to communicate with the application server for an AR session. Depending on the end user device, this could be done using a finger and/or hand to select the correct AR application, or using a button or touch activated system to select the correct AR application.
-- 4) Once the application has started, complete the designated task which could be playing a game or performing a pre-defined task on a machinery, troubleshooting etc.
-- 5) Repeat the test multiple times (> 10 times) and gather results.
-- 6) Repeat the above steps 1 through 5 for the good, fair and poor radio conditions.
-
-#### 7.9.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup to the URLLC network slice by the end user device without any errors over SUT. Also validate the end user device can connect to the application server for the AR session. This is a prerequisite before these tests can be validated.
-
-Validate the end user device can set up the AR session and perform the desired task eg: remote maintenance. Ensure there is no noticeable video freezing, jitter, or lag in the AR session for the end user. Use packet captures to validate there is no jitter or packet drops between the end user device and the application server. Use the packet captures to ensure there are no out-of-sequence packets which could impact the end user’s experience. Calculate the metrics, such as latency and throughput using the packet captures.
-
-The KPIs for an Augmented Reality session varies by the use-case type, the vertical that is being supported and even the product that is being used for testing. As there is no standard application layer protocol or method used for these use-cases, vendors have developed products which have been optimized using their own propriety mechanism(s). The specific values for these KPIs depends on the product used for testing and shall be provided by the product vendor. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure within the SUT.
-
-The KPIs for the URLLC session vary by use-case category, use-case type and even by the vendor products used for testing. The table below [34] gives a generic list of KPI values defined by use-case category. The specific values for these KPIs depends on the product used for testing and shall be provided by the product vendor.
-
-**Table 7-33 - URLLC KPIs**
-
-| Use case group | Use case example | e2e latency | jitter | round trip time | e2e reliability | network reliability | user experienced throughput | network throughput | availability | time synchronous accuracy | device/connection density |
-|--------------------------------------|----------------------------------------|----------------------------------------------|--------|---------------------------------------|------------------------|---------------------|------------------------------------|--------------------|--------------|---------------------------|---------------------------|
-| AR/VR | Augmented worker | 10ms | | | 99.9999% | | | | | | |
-| | VR view broadcast | | | <20ms | 99.999% | | 40 - 700Mbps | | | | 3000/km 2 |
-| Tactile interaction | Cloud Gaming | <7ms (uplink) | | | 99.999% | | 1 Gbps | | | | 3000/km 2 |
-| Energy | Differential protection | <15ms | <160us | | 99.999% | | 2.4Mbps | | | 10us | 10-100/km 2 |
-| | FISR | <25ms | | | | | 10 Mbps | | | | 10/km 2 |
-| | Fault location identification | 140ms | 2ms | | 99.9999% | | 100 Mbps | | | 5 us | 10/km 2 |
-| | fault mgmt. in distr. Power generation | <30ms | | | | 99.999% | 1Mbps | | 99.999% | | <2000/km 2 |
-| Factory of the future | Advanced industrial robotics | <2ms | | <30ms task planner; <1-5ms robot ctrl | 99.9999% to 99.999999% | | | | | | |
-| | AGV control | 5ms | | | 99.999% | | 100 kbps (downlink) 3-8Mbps uplink | | | | |
-| | Robot tooling | 1ms robotic motion ctrl; 1-10ms machine ctrl | <50% | | 99.9999% | | | | | | |
-| UAV | UTM connectivity | | | | 99.999% | | < 128 bps | | | | |
-| | Cmnd & Ctrl | <100ms | | | 99.999% | | | | | | |
-| | Payload | application dependent | | | | | | | | | |
-| Position measurement delivery | for AR in smart factory | <15ms | | | | | | | 99.9% | | |
-| | for inbound logistics in manufacturing | <10ms | | | | | | | 99.9% | | |
-
-The capability to capture data is dependent on the end user device’s capability. As a part of gathering data, it is recommended that minimum configuration parameters (see Clause 4.3) are included in the test report. The following information is also recommended to be included in the test report to provide a comprehensive view of the test setup.
-
-End user device (real or emulated AR device):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-34 Example Test Report for URLLC Testing**
-
-| URLLC KPIs | Excellent
(cell centre) | Good | Fair | Poor
(cell edge) |
-|------------------------------------|----------------------------|------|------|---------------------|
-| Reliability | | | | |
-| End to End Latency | | | | |
-| User Experienced Throughput | | | | |
-| Motion-to-Photon latency | | | | |
-| Motion-to-sound delay | | | | |
-| HARQ Retransmission | | | | |
-| DL/UL Latency – User Plane | | | | |
-| DL/UL Latency – Control Plane | | | | |
-| L1 DL throughput [Mbps] | | | | |
-| L1 DL Spectral efficiency [bps/Hz] | | | | |
-| L3 DL PDCP throughput [Mbps] | | | | |
-| Application DL throughput [Mbps] | | | | |
-| UE RSRP [dBm] | | | | |
-| UE RSRQ | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| MIMO rank | | | | |
-| PDSCH MCS | | | | |
-| CQI | | | | |
-| PMI | | | | |
-| RSSI | | | | |
-| Packet delay | | | | |
-| PDSCH BLER [%] | | | | |
-
-## 7.10 mMTC
-
-### 7.10.0 mMTC test introduction
-
-The 5G network also supports a wide set of use cases which allow machine type devices to communicate with the network to realise the Internet of Things use cases. These use cases fall under the category mMTC – massive Machine Type Communication. There are a diverse set of use cases under this category which supports a range of verticals including security, healthcare, remote control, metering, smart city, etc. The 5G network has enhanced the RAN and the core to support the mMTC requirements. Some of these enhancements include supporting large numbers of mMTC devices by improving coverage and density of devices. Enhancements also include reducing the overhead for small intermittent data transmission, thus ensuring low energy usage, and extending the battery life of the mMTC devices.
-
-Network slicing in 5G allows for a telecommunication service provider to support the diverse set of mMTC use cases by dedicating a separate slice of the network for these use cases. The 3GPP has also defined a massive Machine Type Communication (mMTC) as a slice which is used to support the use case to support very large number of small devices (million to billions) in an efficient way to ensure optimal energy utilization. This clause of the document includes scenarios to test service(s) which use the mMTC slice.
-
-Please see the below summary table of test cases and applicable technology.
-
-**Table 7-35: mMTC-Sensors Test Case Selection summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|--------------|------------------|-----------------------|-----|----|
-| | | | LTE | NSA | SA |
-| Test ID | mMTC-Sensors | | | | |
-| 7.10.1 | Sensors | Service | N/A | N/A | Y |
-
-### 7.10.1 Sensors
-
-This test scenario validates the working of sensors over an mMTC slice on a 5G network.
-
-##### 7.10.1.1 Test Description
-
-This clause provides the procedure to test the mMTC applications in a telecommunication network. mMTC comprises a diverse set of use cases supported across various verticals. Most of the mMTC use cases include an end user equipment which communicates with an application server over the 5G network. The end user device varies based on the use case, from a sensor which measure temperature, humidity, or weight, etc.; to a gauge which measures usage of electricity, or water, etc/; to a monitoring device which measure and report vital statistics. These end user devices collect data and update the application server periodically. The application server collects the data, stores it, analyses it, and can also perform additional tasks if needed, based on the outcome of the analysis, eg: turn off equipment when the temperature is high, etc.
-
-This clause is using sensors to perform mMTC testing. The test case includes deploying 5G sensors in the field to collect data and upload it to an application server. The sensors could vary based on the use case needed. These sensors could be air humidity sensor, temperature sensor, and soil moisture sensor used in conjunction to identify the need to irrigate a farm. These sensors could also be used to identify gas leaks to alert the authorities, or turn off gas lines. These sensors could also be light/image sensors which can be used to identify if a parking spot is occupied. There are numerous sensors which support a varied set of use cases, but this test case has been intentionally left generic without specifying the type of sensor that will be used for testing.
-
-The 5G mMTC network slice does not have requirements on the protocol, or the method used to communicate between the end user device and the application server. The 5G network slice acts as a pipe to allow communication between these two end points, the sensors and application server, with the low energy utilization and the ability to support massive number of such sensors to connect.
-
-#### 7.10.1.2 Test Setup
-
-The SUT as defined in Clause 4.1.0 is used to test the mMTC use case. A 5G SA core shall be required to support basic functionality to authenticate and register the end user device(s) to establish a PDU session. An application server which has the capability to collect data from different end user device(s)/sensor(s) which will be used for testing. The 5G core and application server may be a completely emulated, partially emulated or real non-emulated core. The end user device(s) in this scenario may be a single or a group of sensors which can communicate over 5G. For the testing of this use case, either real end user device(s) or emulated devices which emulate the different sensor(s) may be used. The test setup shall include tools which can collect traces on the elements and/or packet captures of communication between the elements. This may be a built-in capability of the emulated/non-emulated network elements or an external tool. Optionally, if some of the network elements are located remotely either in a cloud or on the Internet, the additional latency should be calculated and accounted for.
-
-The SUT shall have the correct configuration and software load. The SUT shall also be setup to run this testing in different radio conditions as outlined in Clause 4.6. The end user device shall be configured with the correct user credentials to be able to register and authenticate with the O-RAN system and the 5G core. The end user device also shall be provisioned with the user credentials to register and set up the PDU session with the 5G core and authenticate/communicate with the application server. The application server shall be configured and provisioned with all the necessary information to connect to the different sensors and the values. The locations where the radio conditions are excellent, good, fair and poor shall be identified within the serving cell.
-
-All the elements in the network, such as the SUT, 5G core and the application server should have the ability to capture traces to validate the successful execution of the test cases. The end user devices should have the capability to capture traces/packets to calculate the KPIs. Optionally, the network may have network taps deployed in various legs of the network to get packet captures to validate successful execution of the test cases. All these different components shall have connectivity with each other – the end user device shall be able to connect to SUT, SUT shall be connected to the 5G core which in turn shall have connectivity to the application server.
-
-#### 7.10.1.3 Test Methodology/Procedure
-
-Ensure the end user devices, SUT, 5G core and the application server have all been configured as outlined in Clause 7.10.1.2. All traces and packet captures shall be enabled for the duration of the testing to ensure all communication between network elements can be captured and validated.
-
-- 1) Power on the end user device(s) in excellent radio condition and ensure the device registers with the 5G core over SA by connecting over the SUT. Depending on the type of mMTC device this could be done by pushing the power button on the end user device or could be by connecting the end user device to a battery or power source.
-- 2) Once the registration is complete, the end user device(s) shall establish a PDU session over the mMTC network slice, followed by connection to the application server.
-- 3) Based on the type of mMTC device, additional steps may be required the first time the device is connected to the network, to enable the device to register with the application server. This could include adding the end user device to the application server using a unique ID or/and unique security code etc.
-- 4) Validate the end user device can communicate with the application server periodically and update the sensor data.
-- 5) Let the test run for long enough duration of time so that the end user device(s) can upload enough data to the application server.
-- 6) Repeat the above steps 1 through 5 for the good, fair and poor radio conditions.
-
-#### 7.10.1.4 Test Expectation (expected results)
-
-As a pre-validation, use the traces to validate a successful registration and PDU session setup to the mMTC network slice by the end user devices without any errors over SUT. Also validate the end user devices can connect to the application server. This is a prerequisite before these tests can be validated.
-
-Validate the end user devices can connect to the application server and update the sensor data periodically. Validate the application server can receive the data from the sensors, process it and take the necessary action – updating charts and report,
-
-triggering secondary actions, etc. Use packet captures to validate there are no packet drops between the end user device and the application server. Calculate the metrics, such as the latency and throughput using the packet captures.
-
-The KPIs for the mMTC session vary by use-case category, use-case type, and even by the vendor products used for testing. As there is no standard application layer protocol or method used for these use-cases, vendors have developed products which have been optimized using their own propriety mechanism(s). The specific values for these KPIs depends on the product used for testing and shall be provided by the product vendor. As there are multiple variables which can impact the testing in this scenario, a KPI outcome outside the range does not necessarily point to a failure within the SUT.
-
-The capability to capture data is dependent on the end user device’s capability. As a part of gathering data, it is recommended that minimum configuration parameters (see Clause 4.3) are included in the test report. The following information is also recommended to be included in the test report to provide a comprehensive view of the test setup.
-
-End user device (real or emulated sensors):
-
-- Radio parameters such as RSRP, RSRQ, PDSCH SINR (average sample per second)
-- PDSCH BLER, PDSCH MCS, MIMO rank (number of layers) (average sample per second)
-- Downlink transmission mode
-- Channel utilization, i.e. Number of allocated/occupied downlink PRBs and Number of allocated/occupied slots (average sample per second)
-
-**Table 7-36 Example Test Report for mMTC Testing**
-
-| MMTC KPIs | Excellent | Good | Fair | Poor |
-|---------------------|---------------|------|------|-------------|
-| | (cell centre) | | | (cell edge) |
-| RACH Success Rate | | | | |
-| Paging Success Rate | | | | |
-| UE RSRP [dBm] | | | | |
-| UE RSRQ | | | | |
-| UE PDSCH SINR [dB] | | | | |
-| CQI | | | | |
-| Packet delay | | | | |
-| Buffer Status | | | | |
-| DRX Sleep Time | | | | |
-
-# 8 Load and stress tests
-
-## 8.0 Load and stress tests introduction
-
-This clause describes the tests evaluating and assessing the load and stress tests of the radio access network from a network end-to-end perspective. The focus of the testing is on the tolerability of the SUT under load based on 3GPP and O-RAN specifications.
-
-The SUT shall have an ability to handle the various traffic patterns and loads which could happen in a real field deployment. The load and stress tests are used to evaluate the tolerability of SUT against loading and traffic in a laboratory setting. These tests may uncover problems that are difficult to observe and correct in the field. Load and stress tests in addition to Functional
-
-testing thereby help ensure the final quality of the SUT. It leads to improve the overall quality of the system, which in turn improve the user experience.
-
-The tests also cover special calling features, such as placing an Emergency Call.
-
-Please see below summary table of test cases and applicable technology.
-
-**Table 8-1: Load and Stress Tests summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|-----------|----------------------------------------------|------------------|-----------------------|-----|----|
-| | | | LTE | NSA | SA |
-| TEST ID | Load and Stress Tests | Load and Stress | | | |
-| 8.1 | Simultaneous RRC_CONNECTED UEs | Load and Stress | Y | Y | Y |
-| 8.2 | UE State Transition Rate Testing | Load and Stress | Y | Y | Y |
-| 8.3 | Traffic Load Testing | Load and Stress | Y | N/A | Y |
-| 8.4 | Traffic Model Testing | Load and Stress | Y | Y | Y |
-| 8.5 | Long hours stability Testing | Load and Stress | Y | Y | Y |
-| 8.6 | Multi-cell Testing | Load and Stress | Y | Y | Y |
-| 8.7 | Emergency call | Load and Stress | Y | Y | Y |
-| 8.8 | ETWS (Earthquake and Tsunami Warning System) | Load and Stress | Y | Y | Y |
-| 8.9 | MPS Call | Load and Stress | Y | Y | Y |
-| 8.10 | Simultaneous RRC_CONNECTED UEs Stability | Load and Stress | Y | Y | Y |
-
-## 8.1 Simultaneous RRC\_CONNECTED UEs
-
-### 8.1.1 Test description and applicability
-
-The purpose of this test is to connect multiple UEs to the SUT and measure the maximum number of UEs that can be simultaneously maintained in RRC\_CONNECTED state. By connecting multiple UEs at the same time, a basic SUT capacity is verified. This test is valid with either LTE or 5G NSA/SA. The test procedure is to stack the number of connected UEs to the SUT one by one and check the maximum number of simultaneous connected UEs. To perform this test, the connected UEs transmit a minimum size of U-Plane packet periodically such as ping to keep the RRC\_CONNECTED state. The transmit interval of the packets shall be shorter than RRC inactivity timer value in SUT. Figure 8-1 illustrates how the test works.
-
-
-
-Figure 8-1: Simultaneous RRC\_CONNECTED UEs. A diagram showing the timeline of multiple User Equipment (UE) connections. The y-axis represents the number of UEs (0 to 1,200). The x-axis represents time. Five UEs are shown making 'Call attempt' and entering 'RRC\_CONNECTED' state. A vertical blue line marks the 'Number of Maximum connected UEs' at 1,000. A red 'Failure' arrow points to the fifth UE's connection. All UEs eventually reach 'Release' state. A bracket indicates 'Call interval' between attempts and 'Connection holding time' for the duration of the connected state. A detailed view on the right shows the sequence of 'Call attempt', 'RRC\_CONNECTED', 'Release', and a 'Failure' for the fifth UE.
-
-Figure 8-1 Simultaneous RRC\_CONNECTED UEs
-
-### 8.1.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-Since this test scenario requires a large number of UE connections, it is recommended to use equipment that emulates a large number of UEs.
-
-This test is aimed at C-Plane (i.e., RRC, PDCP and RLC) capacity benchmarking, where a maximum capacity load shall be applied in accordance with Clause 4.1.1.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 8.1.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA/SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA/SA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools.
-- 5) "Power ON" the UEs one by one, connect them to the LTE or 5G NSA/SA cell, and confirm that they are in the RRC\_CONNECTED state normally. The UE in RRC\_CONNECTED state, to keep their RRC connection, periodically sends some data packets like Ping. The connection holding time shall be at least 3 minutes in Figure 8-1
-
-to be sufficient for the test. Increase the number of UEs until the newly powered UE fails to connect to LTE or 5G NSA/SA cell.
-
-- a) Start with a number of 100 UEs and further increase the number of UEs in increments of 100, until a newly powered on UE fails to connect. Connect the UEs sequentially at a reasonable rate; the recommended rate is 10 UEs per second.
- - b) From the last increment, where all UEs connected successfully, repeat the process of increasing the number of UEs in increments of 10, until a newly powered on UE fails to connect. Connect the UEs sequentially at the same rate as before.
- - c) From the last increment, where all UEs connected successfully, repeat the process of increasing the number of UEs in increments of 1, until a newly powered on UE fails to connect. Connect the UEs sequentially at the same rate as before.
-- 6) If all newly powered UEs successfully "Power ON" during one of the UE number increments in step 5, the Uu with optional additional OpenFH and/or F1 interface and test equipment (see Clause 4.1.1) should be used to add more UEs until a newly powered UE fails to connect
- - 7) Lost connections shall be re-established automatically to maximize number of RRC Connected UEs.
- - 8) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behavior such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements.
-
-### 8.1.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- KPIs mentioned in Table 8-2
-- SUT load/capacity/performance related KPIs (e.g., CPU and MEMORY utilization) if any
-
-Validate the successful procedures from the collected logs. Check the maximum number of UE connections. For the UE(s) which call loss has occurred in this test more than a certain percentage (e.g., 2%), the validity of the cause of the call loss shall be confirmed.
-
-**Table 8-2 Maximum Number of simultaneous RRC\_CONNECTED UEs**
-
-| | Maximum Number of simultaneous RRC_CONNECTED UEs |
-|---------|--------------------------------------------------|
-| LTE | |
-| NR(NSA) | |
-| NR(SA) | |
-
-## 8.2 UE State Transition Rate Testing
-
-### 8.2.1 Test description and applicability
-
-The purpose of this test is to benchmark the number of UE state transitions that can be processed by the control plane per unit time by connecting multiple UEs with various state transitions to an SUT.
-
-As shown in Figure 8-2, an incrementally increasing number of UEs are attached during each period of ‘X seconds’. UE traffic shall repeatedly perform UE state transitions (transition RRC\_IDLE to/from RRC\_CONNECTED) over the ‘X seconds’
-
-duration of the test. After each ‘X seconds’, the UE powers shall be off. In the first interval of X seconds 100 UEs should be attached sequentially and keep on performing UE state transitions for the rest of the interval. The recommended rate for the UEs to attach is 10 UEs per second. When the interval ends all UEs should detach. In the following intervals of X seconds this behaviour is replicated with an increasing number of UEs. The number of UEs shall increase by 100 for each following interval until a failure at connect occurs. When a failure to connect occurs the number of UEs shall increase by 10 UEs, from the last number of UEs which could connect without problem, by each following interval of X seconds until a failure to connect occurs. When a failure to connect occurs the number of UEs shall increase by 1 UE, from the last number of UEs which could connect without problem, by each following interval of X seconds until a failure to connect occurs. By connecting multiple UEs at the same time, the basic SUT control plane processing throughput is verified. This test is valid with either LTE or 5G NSA/SA.
-
-The value of X is determined by the following formula, with I being the RRC Inactivity timer in seconds of the SUT and R being the maximum number of simultaneous RRC\_CONNECTED UEs as determined by the result of test case 8.1:
-
-$$X = 10 \times I + [(R/10)]$$
-
-Note: The formula ensures that 5 state transitions take place by including 10 times the RRC Inactivity timer of the SUT. For the 5 state transitions the ping interval also should be 2 times I. The second part of the formula (R/10) ensures that there is enough time in each interval of X seconds to connect the maximum number of UEs to the SUT using the recommended rate of 10 UEs per second.
-
-The test procedure is to gradually increase the number of UEs connected to the SUT and check the maximum number of simultaneously connected UEs as they perform state transition. In order to transition the RRC\_CONNECTED state and the RRC\_IDLE state of the UE alternately and continuously, the UEs shall periodically transmit a minimum size of U-Plane packet such as a Ping. The transmit interval of the packets shall be longer than RRC inactivity timer value in SUT. By repeating state transitions by many UEs, test a limit of SUT processing capacity. In addition, by repeating the call generation and call release, it can be confirmed that there are no problems such as processing delays and memory release leaks.
-
-
-
-Figure 8-2 Benchmark of UE State Transition: A graph showing UE count over time. The Y-axis is labeled 'UE s' with values 100, 200, 300, 400, 500. The X-axis is labeled 'Time' and divided into four 'X Seconds' intervals. In the first interval, 100 UEs are shown. In the second, 200 UEs are shown, with an 'off' label above them. In the third, 300 UEs are shown, also with an 'off' label. In the fourth, 400 UEs are shown, with an 'off' label and a red box highlighting a group of UEs transitioning between states.
-
-Figure 8-2 Benchmark of UE State Transition
-
-### 8.2.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-Since this test scenario requires a large number of UE connections, it is recommended to use equipment that emulates a large number of UEs.
-
-This test is primarily C-Plane (i.e., RRC, PDCP and RLC) capacity benchmarking, where a maximum capacity load shall be applied in accordance with Clause 4.1.1.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 8.2.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA/SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA/SA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools.
-- 5) Sequentially “Power ON” the current number of UEs at a reasonable rate such as 10 UEs per second, starting with 100 UEs, to attach to the LTE or 5G NSA/SA cell. Observe the state transitions of each UE by checking by the state of receiving control plane messages.
-- 6) After an interval of ‘X seconds’ all UEs are then “Powered off”. It shall be checked whether there are any UEs that have failed to make the RRC state transition at the SUT.
-- 7) Run steps 5 and 6 again with an increased number of UEs. Each interval of ‘X seconds’ the number of UEs shall increase by 100 UEs until a failure to connect occurs. At this point during the next ‘X seconds’ -interval the previously working number of UEs shall be used. In each following interval of ‘X seconds’ the number of UEs should increase by 10 UEs until a failure to connect occurs. At this point during the next ‘X seconds’ -interval the previously working number of UEs is used. In each following interval of ‘X seconds’ the number of UEs shall be increased by 1 UE until a failure to connect occurs, at which point the test cases moves on to step 8.
-- 8) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behavior such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements.
-
-### 8.2.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- KPIs mentioned in Table 8-3
-- SUT load/capacity/performance related KPIs (e.g., CPU and MEMORY utilization) if any
-
-Validate the successful procedures from the collected logs. Check the rate of UE state transition that can be processed per unit time. For the UE(s) in which call loss has occurred in a X seconds test more than a certain percentage (e.g., 2%), the validity of the cause of the call loss shall be confirmed.
-
-**Table 8-3 Maximum Rate of UE State Transition**
-
-| | Maximum Rate of UE State Transition
(per second) | Number of UEs |
-|----------|-----------------------------------------------------|---------------|
-| LTE | | |
-| NR (NSA) | | |
-
-| | Maximum Rate of UE State Transition (per second) | Number of UEs |
-|---------|--------------------------------------------------|---------------|
-| NR (SA) | | |
-
-## 8.3 Traffic Load Testing
-
-### 8.3.1 Test description and applicability
-
-The purpose of this test is to check the stability of the SUT under load, with a large number of UEs sending and receiving user data. By connecting a large number of UEs at the same time, the SUT processing capacity and stability are verified. The maximum cell throughput is discussed in Clause 6 and is out of scope of this test. This test is valid with either LTE or 5G SA.
-
-The test procedure is to connect X UEs per second to the SUT with UDP download/upload traffic until N UEs are connected. Then disconnect X UEs per second and reconnect X new UEs per second to the SUT with UDP download/upload traffic. Continue disconnecting and connecting UEs near the maximum number of UEs to verify a stability of SUT. It is recommended that the total UDP traffic be less than the maximum cell throughput, as maximum cell throughput is out of scope for this test.
-
-The values of X and N are determined by the result of test case 8.1, i.e., the maximum number of simultaneous RRC\_CONNECTED UEs (denoted as R), and the following equations:
-
-$$X = \begin{cases} 1, & R \leq 60 \\ 10, & 60 < R < 600 \\ 25, & R \geq 600 \end{cases}$$
-
-$$N = \lfloor 0.9 * R \rfloor$$
-
-### 8.3.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-Since this test scenario requires a large number of UE connections, it is recommended to use equipment that emulates a large number of UEs.
-
-The performance of the SUT 3GPP stack components in all of the O-RU, O-DU, and O-CU sub-nodes shall be measured while all sub-nodes are under high load, where additional load may be applied in accordance with Clause 4.1.1.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G SA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 8.3.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G SA) in Clause 4.6.
-
-- 3) The End-to-end setup shall be operational for LTE or 5G SA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools.
-- 5) Power on X UEs per second to access the SUT by signalling, initiate UDP upload/download for each UE after UEs get access. In this step and later steps, lost connections shall be re-established automatically to maintain number of RRC Connected UEs.
-- 6) Continue Step 5 until total UEs reach maximum active number of UEs N per cell.
-- 7) Release X UEs per second then add X UEs per second to access the SUT and initiate UDP upload/download for each new access UE.
-- 8) Repeat Step 7 for at least 5 minutes and record the KPI values, RRC access success rate, and Packet Error Rate.
-- 9) Release all UEs, add X UEs per second to access the SUT and initiate UDP upload/download for each new access UE until total UEs reach maximum active number of UEs N per cell. Keep testing for at least 5 minutes. Record KPI values and packet error rate.
-- 10) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behavior such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements.
-
-### 8.3.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- N (maximum active number of UEs per cell), X (UEs per second)
-- KPIs mentioned in Table 8-4 and Table 8-5
-- SUT load/capacity/performance related KPIs (e.g., CPU and MEMORY utilization) if any
-
-Validate the successful procedures from the collected logs. Check the rate of UE state transition that can be processed per unit time. For the UE(s) in which call loss has occurred, the validity of the cause of the call loss shall be confirmed.
-
-**Table 8-4 RRC Access Success Rate**
-
-| | RRC Access Success Rate |
-|---------|-------------------------|
-| LTE | |
-| NR (SA) | |
-
-**Table 8-5 Packet Error Rate**
-
-| | Packet Error Rate | |
-|---------|-------------------|----------|
-| | Uplink | Downlink |
-| LTE | | |
-| NR (SA) | | |
-
-## 8.4 Traffic Model Testing
-
-### 8.4.1 Test description and applicability
-
-The purpose of this test is to check the performance under varying load for the SUT by generating various UE behavior such as Attach/Detach, Registration/Deregistration, Data upload/download, and Mobility based on the traffic model to load the SUT. Traffic models can vary depending on factors such as geographic characteristics of the target area, UE type, number of UEs, UE mobility, time of day, and so on. It is important to consider the maximum number of UEs and the behavior that is expected in the field and develop the appropriate traffic model. This test is valid for either LTE or 5G NSA/SA.
-
-The test procedure is to cause various UE behavior such as Attach/Detach, Registration/Deregistration, Data upload/download, and Mobility to the SUT. Repeat various scenarios based on the traffic model. By processing complex combinations of behavior, the processing capacity of the SUT is confirmed. Review the KPIs for each scenario to see if there are any issues that depend on a particular scenario.
-
-#### 8.4.1.1 Traffic model
-
-The traffic model is a model of the set of scenarios that an SUT is expected to undergo in the field. The test items in Clause 5 and 7 can be part of the traffic model scenario as they are or by simplifying them. Each scenario may be repeated continuously at a certain frequency, or many may be executed simultaneously. The pattern of possible scenarios as shown in Table 8-6, may be different depending on the characteristics of deployment area in which the SUT is deployed and can be categorized into several typical types. It is necessary to have SUT capabilities that are appropriate for the deployment area. See Table 8-6 for examples of typical traffic model types.
-
-**Table 8-6 Example of typical traffic model types**
-
-| No. | Traffic Model Type | Major Characteristics |
-|-----|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 1 | Indoor Hotspot | - The number of UEs may be very large, not much fluctuation in the number of UEs (less handover).
- High traffic volume in data transmission and reception.
|
-| 2 | Dense Urban | - The number of UEs is very large.
- High traffic volume in data transmission and reception.
- High in mobility.
- Less active at night
|
-| 3 | Office area | - The number of UEs is large.
- High traffic volume in data transmission and reception.
- High in mobility. Slower speed.
- Less active at night
|
-| 4 | Residential area | - The number of UEs is small.
- Data traffic volume is low during daytime, may peaks at night in area where Wi-Fi is not widespread.
- Low in mobility
- Somewhat active during daytime
|
-| 5 | Rural | - The number of UEs is very small.
- Low traffic volume in data.
- Low in mobility.
|
-| 6 | High Speed
(Train Station.
Along the railroad tracks.) | - The number of UEs may be temporarily concentrated in large numbers. Burst when a train arrives or departs, or when a train passes by.
- As a train passes, many UEs pass at high speed at the same time.
|
-
-The scenarios included in each traffic model type and the frequency (per UE per hour) should be appropriately determined considering the characteristics of that traffic model type.
-
-In this testing, one or more traffic models can be used to evaluate the capacity, stability and load durability of the SUT.
-
-Table 8-7 shows an example of traffic model. Traffic model defines a large number of UEs and scenarios, and this model can present traffic observed in real field.
-
-**Table 8-7 Example of Traffic Model**
-
-| Total number of UEs in a cell | | 1,000 | | | (The numbers are just example) | | |
-|-------------------------------|----------------------|------------------|--------|-------|--------------------------------|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| No | Scenario (baseline) | RAT | | | Number of UEs | Attempts (per UE per hour) | Description |
-| | | LTE | 5G NSA | 5G SA | | | |
-| 1 | Attach | ○ | ○ | N/A | 50 | 0.50 | Power ON |
-| 2 | Detach | ○ | ○ | N/A | 50 | 0.50 | Power OFF |
-| 3 | Tracking area update | ○ | ○ | N/A | 100 | 1.00 | |
-| 4 | Registration | N/A | N/A | ○ | 50 | 0.50 | Power ON |
-| 5 | Deregistration | N/A | N/A | ○ | 50 | 0.50 | Power OFF |
-| 6 | Paging | ○ | ○ | ○ | 200 | 1.00 | Total of paging in this model. |
-| 7 | Data upload/download | Stationary | ○ | ○ | 100 | 1.00 | One RRC_CONNECTED period is defined as "1 attempt". At least RRC_CONNECTED period and avg. DL/UL bit rate shall be specified. If mobility is involved, one hand over per attempt assumed, mobility type and when to move shall be specified. |
-| | | With Mobility *) | | | 5 | 0.50 | |
-| Additional scenario if any | | | | | | | |
-| 8 | Web Browsing | Stationary | ○ | ○ | 120 | 2.00 | At least hold time, RRC_CONNECTED period/interval/number of times per call, and avg. DL/UL Mbytes per RRC_CONNECTED period shall be specified. If mobility is involved, one hand over per attempt assumed, mobility type and when to move shall be specified. |
-| | | With Mobility *) | | | 6 | 0.50 | |
-| 9 | File upload/download | Stationary | ○ | ○ | 30 | 1.50 | At least file size, upload/download and hold time shall be specified. If mobility is involved, one hand over per attempt assumed, mobility type and when to move shall be specified. |
-| | | With Mobility *) | | | 2 | 0.50 | |
-| 10 | Voice Service | Stationary | ○ | ○ | 80 | 0.20 | 50% of calls Mobile Terminated, 50% of calls Mobile Originated assumed. At least avg. DL/UL bit rate and avg. hold time shall be specified. If mobility is involved, one hand over per attempt assumed, |
-| | | With Mobility *) | | | 4 | 0.50 | |
-
-| Total number of UEs in a cell | | | 1,000 | | | (The numbers are just example) | | |
-|-------------------------------|---------------------|------------------|--------|-------|---------------|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|
-| No | Scenario (baseline) | RAT | | | Number of UEs | Attempts (per UE per hour) | Description | |
-| | | LTE | 5G NSA | 5G SA | | | | |
-| | | | | | | | | mobility type and when to move shall be specified. |
-| 11 | Video Streaming | Stationary | ○ | ○ | 40 | 1.00 | At least avg. DL/UL bit rate and avg. hold time shall be specified. With mobility, one handover per one call attempt. If mobility is involved, one hand over per attempt assumed, mobility type and when to move shall be specified. | |
-| | | With Mobility *) | ○ | ○ | 2 | 0.50 | | |
-
-\*) e.g., Intra-cell handover. Other mobilities can be included if multiple cells are configured.
-
-The performance of the SUT shall be measured while all SUT components are under high load. To achieve this, the test results in the previous clauses 8.1 through 8.3 may be helpful .
-
-### 8.4.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-When inter-cell mobility is included in the traffic model, the target/source cells and UE behavior/sequence should be simulated by the UE emulator and Core emulator without using additional cells.
-
-Since this test scenario requires a large number of UE connections, it is recommended to use equipment that emulates a large number of UEs.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator/fading generator inserted between the antenna connectors (if available) of the SUT and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 8.4.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA and SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT’s Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA/SA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools.
-- 5) Start the operation of each UE according to the traffic model.
-
-- 6) Check KPIs for each scenario included in the traffic model during continuous operation (several tens of minutes to several hours).
-- 7) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behavior such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements.
-
-### 8.4.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- Traffic model
-- KPIs mentioned in Table 8-8
-- SUT load/capacity/performance related KPIs (e.g., CPU and MEMORY utilization) if any
-
-If a scenario in the Traffic Model is the same as the scenario described in Clause 5 and 7, it is recommended to select and evaluate some of the corresponding KPIs described in Clause 5 and 7.
-
-Validate the successful procedures from the collected logs. It is desirable that the test duration shall be more than several tens of minutes to several hours. Check the completion rate of each scenario and the adequacy of the completion rate for each scenario shall be confirmed. For the UE(s) in which call loss has occurred, the validity of the cause of the call loss shall be confirmed.
-
-**Table 8-8 KPIs in traffic model scenario (example)**
-
-| | | RAT | | | Success Rate (%) | Optional KPI if any |
-|----------------------------|----------------------|---------------|--------|-------|------------------|-----------------------------------------|
-| No. | Scenario(baseline) | LTE | 5G NSA | 5G SA | | |
-| 1 | Attach | ○ | ○ | N/A | | e.g., SgNB addition Success rate in NSA |
-| 2 | Detach | ○ | ○ | N/A | | |
-| 3 | Tracking area update | ○ | ○ | N/A | | |
-| 4 | Registration | N/A | N/A | ○ | | |
-| 5 | Deregistration | N/A | N/A | ○ | | |
-| 6 | Paging | ○ | ○ | ○ | | |
-| 7 | Data upload/download | Stationary | ○ | ○ | ○ | e.g., Avg. UL/DL throughput |
-| | | With Mobility | | | | e.g., Avg. UL/DL throughput |
-| Additional scenario if any | | | | | | |
-| 8 | Web Browsing | Stationary | ○ | ○ | ○ | e.g., Avg. UL/DL throughput |
-| | | With Mobility | ○ | ○ | ○ | e.g., Avg. UL/DL throughput |
-| 9 | File upload/download | Stationary | ○ | ○ | ○ | e.g., Avg. UL/DL throughput |
-| | | With Mobility | ○ | ○ | ○ | e.g., Avg. UL/DL throughput |
-| 10 | Voice Service | Stationary | ○ | ○ | ○ | e.g., Packet loss rate |
-| | | With Mobility | ○ | ○ | ○ | e.g., Packet loss rate |
-
-| | | | RAT | | | Success Rate (%) | Optional KPI if any |
-|-----|--------------------|---------------|-----|--------|-------|------------------|-----------------------------|
-| No. | Scenario(baseline) | | LTE | 5G NSA | 5G SA | | |
-| 11 | Video Streaming | Stationary | ○ | ○ | ○ | ○ | e.g., Avg. UL/DL throughput |
-| | | With Mobility | ○ | ○ | ○ | ○ | e.g., Avg. UL/DL throughput |
-
-## 8.5 Long hours stability Testing
-
-### 8.5.1 Test description and applicability
-
-The purpose of this test is to conduct a load test using the traffic model described in Clause 8.4.1.1 for a long period (e.g., 24 to 48 hours) to confirm the continuous operation for a long period of time. This test is valid with either LTE or 5G NSA and SA. The test procedure is to cause various UE behavior such as Attach/Detach, Registration/Deregistration, and Mobility based on the traffic model to the SUT and maintains its performance for a long time. Verify the KPIs for each scenario by repeating call generation and call release for various traffic.
-
-### 8.5.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-Since this test scenario requires a large number of UE connections, it is recommended to use equipment that emulates a large number of UEs.
-
-The extended length performance and stability of the SUT shall be measured while all SUT components are under high load. To achieve this, it may be required to apply additional traffic in accordance with Clause 4.1.1.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator inserted between the antenna connectors (if available) of the SUT and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 8.5.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA and SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other RF cells are powered off.
-- 2) If during execution of Clause 8.3.3 (Traffic Load Testing) or Clause 8.4.3 (Traffic Model Testing) incremental traffic was applied using the optional OpenFH and/or F1 interface and test equipment (see Clause 4.1.1) in addition to the traffic being applied at the RF interface, the same level of traffic should be applied again using the optional OpenFH and/or F1 interface and test equipment to ensure O-DU and O-CU exposed to adequate “base load” before execution of Step 6.
-- 3) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT’s Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) in Clause 4.6.
-- 4) The End-to-end setup shall be operational for LTE or 5G NSA/SA as applicable for the test scenario, and there should not be any connectivity issues.
-
-- 5) Required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools (optional).
-- 6) Start the operation of each UE according to the traffic model. Keep the operation for a long period of several tens of hours.
-- 7) Monitor KPIs for each scenario included in the traffic model during this test. A scenario is considered successful if the KPIs for each scenario is equivalent to the traffic model testing case. if not, it is a failure.
-- 8) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behavior such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements (optional).
-
-### 8.5.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- Traffic Model
-- KPIs mentioned in Table 8-9, Table 8-8.
-- SUT load/capacity/performance related KPIs (e.g., CPU and MEMORY utilization) if any
-
-Validate the successful procedures from the collected logs. Normally this test should be a minimum of 12 hours with 60 hours as a recommended maximum. Check the completion rate of each scenario and the adequacy of the completion rate for each scenario shall be confirmed. For the UE(s) in which call loss has occurred, the validity of the cause of the call loss shall be confirmed.
-
-**Table 8-9 Successfully tested hours**
-
-| | Successfully tested hours (hours) |
-|---------|-----------------------------------|
-| LTE | |
-| NR(NSA) | |
-| NR (SA) | |
-
-## 8.6 Multi-cell Testing
-
-### 8.6.1 Test description and applicability
-
-The purpose of this test is to benchmark the SUT's processing capacity by applying a load to some or all of its cells simultaneously based on the traffic model. Inter-cell interference is out of scope, so the DUT cells shall be configured there is no inter-cell interference. This test is valid with either LTE or 5G NSA and SA. The test procedure is to cause various UE behavior such as Attach/Detach, Registration/Deregistration, and Mobility based on the Traffic Model for some or all of the Cells in the SUT. Verify the KPIs for each scenario in each cell by repeating call generation and call release for various traffic (scenarios). This test is a multi-cell test of Clause 8.4 and is intended to increase the load on SUT. In this testing, various mobilities can be included among DUT cells.
-
-The performance of the SUT shall be measured while all SUT components are under high load. To achieve this, it may be required to apply additional traffic in accordance with Clause 4.1.1.
-
-### 8.6.2 Test setup and configuration
-
-The test setup is multiple cells scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-Since this test scenario requires a large number of UE connections, it is recommended to use equipment that emulates a large number of UEs.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator inserted between the antenna connectors (if available) of the SUT and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 8.6.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA and SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The target cells under test are activated and unloaded. All other cells are powered off.
-- 2) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA/SA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools.
-- 5) Start the operation of each UE according to the traffic model for all target cells.
-- 6) Check KPIs for each scenario included in the traffic model. A scenario is considered successful if the KPIs for each scenario is equivalent to the single-cell case. If not, it is a failure.
-- 7) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behavior such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements.
-
-### 8.6.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- Traffic Model
-- KPIs mentioned in Table 8-10, Table 8-8
-- SUT load/capacity/performance related KPIs (e.g., CPU and MEMORY utilization) if any
-
-Validate the successful procedures from the collected logs. The number of cells to be communicated is preferably 2 cells or more. Check the KPIs of each scenario and the adequacy of the completion rate for each scenario shall be confirmed. For the UE(s) in which call loss has occurred, the validity of the cause of the call loss shall be confirmed.
-
-**Table 8-10 Successfully tested number of Cells**
-
-| | Successfully tested number of Cells |
-|---------|-------------------------------------|
-| LTE | |
-| NR(NSA) | |
-| NR(SA) | |
-
-## 8.7 Emergency call
-
-### 8.7.1 Test description and applicability
-
-The purpose of this test is to ensure that emergency calls, such as 911/112, are preferentially established even if the SUT is overloaded. This test is valid with either LTE or 5G NSA and SA. The test procedure is to further increase the heavy traffic model to load the SUT, creating an overload condition where some behavior of the UE, such as data upload/download, fails. Verify that emergency calls, such as 911/112, can communicate correctly in such a situation.
-
-The Emergency Call performance of the SUT shall be measured while all SUT components are under high load, where a maximum capacity load shall be applied in accordance with Clause 4.1.1.
-
-### 8.7.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-Since this test scenario requires a large amount of non-emergency traffics to overload the SUT, so it is recommended to run the test with equipment that emulates a large amount of non-emergency traffic.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator inserted between the antenna connectors (if available) of the SUT and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 8.7.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA and SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA/SA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools.
-- 5) Start the operation of each UE according to the traffic model.
-- 6) Review the KPIs for each scenario in the traffic model to ensure that the KPIs are degraded due to overload. The degraded KPIs to be reviewed shall include the non-emergency call success rate degraded over 0.1%. If there is no
-
-degradation of the KPI, increase the traffic in accordance with Clause 4.1.1 until there is degradation of the KPI (until it becomes overloaded).
-
-NOTE: For the SUT conducting this test, it is expected that the non-emergency call success rate is 100.0% when there is no degradation due to overload.
-
-- 7) Make multiple emergency calls (100 times suggested) such as 911/112 to confirm if the call can be established.
-- 8) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behavior such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements.
-
-### 8.7.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- Traffic Model and related KPIs
-- KPIs mentioned in Table 8-11
-- SUT load/capacity/performance related KPIs (e.g., CPU and MEMORY utilization) if any
-
-Validate the successful procedures from the collected logs. Confirm the emergency call communication.
-
-**Table 8-11 Emergency Call Success Rate**
-
-| | Emergency Call Success Rate |
-|---------|-----------------------------|
-| LTE | |
-| NR(NSA) | |
-| NR(SA) | |
-
-## 8.8 ETWS (Earthquake and Tsunami Warning System)
-
-### 8.8.1 Test description and applicability
-
-The purpose of this test is to verify that the ETWS notification is successful even if the SUT is overloaded. This test is valid with either LTE or 5G NSA and SA. The test procedure is to further increase the heavy traffic model to load the SUT, creating an overload condition where some behavior of the UE, such as data upload/download, fails. Verify that the ETWS Primary and Secondary notifications can communicate correctly under these conditions.
-
-The ETWS performance of the SUT shall be measured while all SUT components are under high load, where a maximum capacity load shall be applied in accordance with Clause 4.1.1.
-
-### 8.8.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-Since this test scenario requires a large amount of non-emergency traffics to overload the SUT, so it is recommended to run the test with equipment that emulates a large amount of non-emergency traffics.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator inserted between the antenna connectors (if available) of the SUT and the UE, or appropriately emulated using a UE emulator. The test
-
-environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 8.8.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA and SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA/SA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools.
-- 5) Start the operation of each UE according to the traffic model.
-- 6) Review the KPIs for each scenario in the traffic model to ensure that the KPIs are degraded due to overload. If there is no degradation of the KPI, increase the traffic in accordance with Clause 4.1.1 until there is degradation of the KPI (until it becomes overloaded).
-- 7) Confirm the ETWS Primary and Secondary notifications communication multiple times (100 times suggested).
-- 8) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behavior such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements.
-
-### 8.8.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- Traffic Model and related KPIs
-- KPIs mentioned in Table 8-12
-- SUT load/capacity/performance related KPIs (e.g., CPU and MEMORY utilization) if any
-
-Validate the successful procedures from the collected logs. Make sure that the ETWS function works correctly and confirm that the ETWS notification is sent to the UE.
-
-**Table 8-12 ETWS Notification Success Rate**
-
-| | ETWS Notification Success Rate | |
-|-----|--------------------------------|-----------|
-| | Primary | Secondary |
-| LTE | | |
-| NR | | |
-
-## 8.9 MPS call
-
-### 8.9.1 Test description and applicability
-
-The purpose of this test is to ensure that Multimedia Priority Service (MPS) calls are preferentially established even if the SUT is overloaded. This test is valid with either LTE or 5G NSA and SA. The test procedure is to apply heavy traffic loading the SUT, creating an overload condition where some behavior of the non-MPS-subscribed UEs fail. Verify that MPS-subscribed UEs can obtain connectivity and establish priority Voice or Video IMS calls (via \*272 in NA) in such a situation.
-
-The MPS Call performance of the SUT shall be measured while all SUT components are under high load, where a maximum capacity load shall be applied in accordance with Clause 4.1.1.
-
-### 8.9.2 Test setup and configuration
-
-The test setup is a single cell scenario (i.e., isolated cell without any inter-cell interference – see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-This test scenario requires a large amount of non-MPS traffic to overload the SUT, so it is recommended to run the test with equipment that emulates a large amount of ordinary traffic.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator inserted between the antenna connectors (if available) of the SUT and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) as defined in Clause 4.6) for the UEs, but the minimum coupling loss (see Clause 4.6) shall not be exceeded. Designated MPS-subscribed UEs shall be configured with AccessIdentity=1 (5GC), or with AC=14 (EPC)
-
-### 8.9.3 Test procedure
-
-The test steps below are applicable for either LTE or 5G NSA and SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA/SA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Required performance data (incl. the signalling and control data) as specified in the “Test requirements” clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools.
-- 5) Start the operation of each ordinary UE according to the traffic model.
-- 6) Review the KPIs for each scenario in the traffic model to ensure that the KPIs are degraded due to overload. If there is no degradation of the KPI, increase the traffic in accordance with Clause 4.1.1 until there is degradation of the KPI (until it becomes overloaded).
-- 7) Activate an ordinary Voice UE. Make and release repeated voice calls (100 times suggested). Determine from logs whether the ordinary call is established.
-- 8) Activate an MPS-subscribed UE. Make and release repeated MPS voice calls (100 times suggested). Record from logs the number of times the MPS call is correctly established, showing RRC establishment cause ‘mps-PriorityAccess’ (NR), or RRC establishment cause ‘highPriorityAccess’ (E-UTRA).’
-
-- 9) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behavior such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements.
-
-Repeat the above Test, omitting Step 7, with Step 8 utilizing N MPS-subscribed UEs making Voice calls. The value N shall be gradually increased to determine an upper limit on the number of supported MPS calls, appropriate for the SUT
-
-Repeat the above Test with Step 7 utilizing an ordinary UE making a Video call, and Step 8 utilizing 1 MPS-subscribed UE making a Video call.
-
-Repeat the above Test, omitting Step 7, with Step 8 utilizing N MPS-subscribed UEs making Video calls. The value N shall be gradually increased to determine an upper limit on the number of supported MPS calls, appropriate for the SUT.
-
-### 8.9.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- Radio parameters such as RSRP, RSRQ
-- Traffic Model and related KPIs
-- KPIs mentioned in Tables 8-13 and 8-14
-- SUT load/capacity/performance related KPIs (e.g., CPU and MEMORY utilization) if any
-
-Validate the successful procedures from the collected logs. Confirm the MPS call communication.
-
-**Table 8-13 MPS Voice Call Results**
-
-| | MPS Voice Call Results | | | |
-|---------------------|----------------------------|-----------------------|---------|-----------------------|
-| | 1 Ordinary UE Success Rate | 1 MPS UE Success Rate | N Value | N MPS UE Success Rate |
-| LTE (E-UTRA/EPC) | | | | |
-| 5G SA (NR/5GC) | | | | |
-| 5G NSA (E-UTRA/5GC) | | | | |
-
-**Table 8-14 MPS Video Call Results**
-
-| | MPS Video Call Results | | | |
-|---------------------|----------------------------|-----------------------|---------|-----------------------|
-| | 1 Ordinary UE Success Rate | 1 MPS UE Success Rate | N Value | N MPS UE Success Rate |
-| LTE (E-UTRA/EPC) | | | | |
-| 5G SA (NR/5GC) | | | | |
-| 5G NSA (E-UTRA/5GC) | | | | |
-
-## 8.10 Simultaneous RRC\_CONNECTED UEs Stability
-
-### 8.10.1 Test description and applicability
-
-The purpose of this test is to verify the stability while connected at the number of UEs (e.g. the maximum number of UEs that O-CU-CP can accommodate) that can be simultaneously maintained in RRC\_CONNECTED state. This test is valid with either LTE or 5G NSA/SA. The test procedure is to stack the number of simultaneously connected UEs to the SUT and maintain the state. To perform this test, the connected UEs transmit a minimum size of U-Plane packet periodically such as ping to keep the RRC\_CONNECTED state. The transmit interval of the packets shall be shorter than RRC inactivity timer value in SUT.
-
-### 8.10.2 Test setup and configuration
-
-The test setup is either a single cell scenario or multiple cells scenario without any inter-cell interference (see Clause 4.7) with multiple UEs placed under excellent radio conditions (see Clause 4.6).
-
-Since this test scenario requires a large number of UE connections, it is recommended to use equipment that emulates a large number of UEs. Especially when measuring the capacity of the O-CU-CP, since many O-RUs and O-DUs may be required, it is recommended to connect an O-DU emulator and/or O-RU emulator using F1 and/or Open FH as shown in Figure 4-3.
-
-This test is aimed at C-Plane (i.e., RRC, PDCP and RLC) capacity benchmarking, where a maximum capacity load might be applied in accordance with Clause 4.1.1.
-
-**Test configuration:** The test configuration is not specified. The utilized test configuration (connection diagram between SUT and test equipment, parameters) shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a variable attenuator inserted between the antenna connectors (if available) of the O-RU and the UE, or appropriately emulated using a UE emulator. The test environment shall be setup to achieve excellent radio conditions (LTE RSRP (for LTE) or 5G SS-RSRP (for 5G NSA/SA) as defined in Clause 4.6) for the UE, but the minimum coupling loss (see Clause 4.6) shall not be exceeded.
-
-### 8.10.3 Test procedure
-
-The test steps below are applicable for LTE or 5G NSA/SA:
-
-- 1) The test setup is configured according to the test configuration. The test configuration shall be recorded in the test report (incl. the number of cells and UEs). The serving cell under test is activated and unloaded. All other cells are powered off.
-- 2) The UEs are placed under excellent radio conditions (Cell centre close to radiated SUT's Antenna) as defined by LTE RSRP (for LTE) or 5G SS-RSRP in Clause 4.6.
-- 3) The End-to-end setup shall be operational for LTE or 5G NSA/SA as applicable for the test scenario, and there should not be any connectivity issues.
-- 4) Required performance data (incl. the signalling and control data) as specified in the "Test requirements" clause below shall be measured and captured at the UE(s) and SUT side using logging/measurement tools.
-- 5) "Power ON" the X UEs per second continuously, connect them to the LTE or 5G NSA/SA cell, and confirm that the N UEs are in the RRC\_CONNECTED state normally. The UE in RRC\_CONNECTED state, to keep their RRC connection, periodically sends some data packets like Ping.
-- 6) Maintain the state in Step 5 for T (at least 30) minutes.
-- 7) Stop and save the test logs. Check the log to make sure that the test runs successfully and that no unexpected behaviour such as unexpected call release is recorded. The logs shall be captured and kept for test result reference and measurements.
-
-### 8.10.4 Test requirements (expected results)
-
-In addition to the common minimum set of configuration parameters (see Clause 4.3), the following metrics and counters shall be captured and reported in the test report for performance assessment.
-
-- X, the connection rate of UEs
-- N, the total number of UEs
-- T, the test duration
-- KPIs mentioned in Table 8-15
-
-**Table 8-15: The rate of UEs that remained connected without reconnection**
-
-| | The rate of UEs that remained connected without reconnection |
-|---------|--------------------------------------------------------------|
-| LTE | |
-| NR(NSA) | |
-| NR(SA) | |
-
-# 9 RIC-enabled end-to-end use case test
-
-## 9.0 RIC-enabled end-to-end use case test introduction
-
-This clause describes tests for evaluating and assessing the **performance of a radio access network with Non-RT RIC and Near-RT RIC optimisations from a network end-to-end perspective**. The focus of the testing is either on the end-user performance with user specific optimisations by the Non-RT RIC and Near-RT RIC or on system level performance with system specific optimisations.
-
-The test setup and test methodology applicable to all the RIC-enabled end-to-end use case tests is described in Clause 9.1, followed by the various test cases including their test description and procedures for each use case. At the beginning of each use case clause, system level, cell level and UE level test configurations and KPIs involved in defining the test scenario and measuring the performance related to the use case testing are discussed. Following it, exact parameter values and KPIs to be measured are defined on a per test case basis.
-
-The following RIC-enabled use case tests are defined in this clause:
-
-- Traffic steering with connected mode mobility control
-- Network energy saving carrier and cell switch off/on using Non-RT RIC
-
-Please see below summary table of test cases and applicable technology.
-
-**Table 9-1: RIC-Enabled end-to-end use case tests summary**
-
-| Test case | | Functional group | Applicable technology | | |
-|----------------|----------------------------------------------------------------------------|---------------------------|-----------------------|-----|----|
-| | | | LTE | NSA | SA |
-| TEST ID | RIC-Enabled End-to-end Use Case | | | | |
-| 9.2 | Traffic steering with connected mode mobility control | Traffic Steering Use Case | N/A | N/A | Y |
-| 9.3 | Network Energy Saving with Carrier and Cell switch off/on using Non-RT RIC | Network Energy Saving | N/A | N/A | Y |
-
-## 9.1 Test Setup and Methodology
-
-
-
-Figure 9-1: Illustration of test setup for RIC enabled use case E2E testing. The diagram shows the SUT (System Under Test) containing the SMO, Non-Real-Time RIC, Near-Real-Time RIC, gNB-DU, gNB-CU-CP, and gNB-CU-UP. The SUT is connected to the 5G Core, which is further connected to an Application Server and an IMS Core. The gNB-DU is connected to an O-RU, which is connected to a UE. The SMO and Non-Real-Time RIC are connected via the O1 interface. The Non-Real-Time RIC and Near-Real-Time RIC are connected via the A1 interface. The Near-Real-Time RIC is connected to the gNB-DU, gNB-CU-CP, and gNB-CU-UP via the E2 interface. The gNB-DU and gNB-CU-CP are connected via the F1 interface. The gNB-CU-UP is connected to the 5G Core via the Ng interface. The gNB-DU is connected to the O-RU via the O-FH interface. The O-RU is connected to the UE.
-
-**Figure 9-1: Illustration of test setup for RIC enabled use case E2E testing**
-
-The purpose of these tests is to validate the O-RAN system's E2E performance for all the various RIC-enabled use cases in different network deployment scenarios [36-38]. To achieve this, multiple sets of **test configuration** parameters are defined for system level, cell level and UE level configurations. In keeping with the spirit of the end-to-end test focus on the O-RAN system as SUT, the detailed ORAN protocol conformance on the various O-RAN internal interfaces as specified in [36-38] will not be verified, and instead, system-level performance according to the objectives of the use case is the primary test focus.
-
-There are no **passing criteria** defined for these performance-focused tests. This is due to the diversity of vendor-specific RRM and MAC layer scheduler implementations in the O-RAN system which also depend on specific network deployment scenarios, making it difficult to specify minimum performance requirements.
-
-The performance of the system with Non-RT RIC and Near-RT optimisations shall be benchmarked through **analysis** of KPI measurement results. The performance gain with Non-RT RIC and Near-RT optimisation is evaluated by **comparing** the test result with RIC optimisation enabled versus that with it disabled.
-
-## 9.2 Traffic steering with connected mode mobility control
-
-### 9.2.0 Traffic steering use case test introduction
-
-The purpose of this test is to validate the O-RAN system's E2E functionalities and evaluate system performance for the Traffic Steering (TS) use case. The O-RAN traffic steering use case specification can be found in Clause 3.5 of [36], with the use case requirements from a non-RT RIC standpoint specified in Clause 3.1 of [37] and near-RT RIC standpoint in Clause 3.1 of [38].
-
-The traffic steering optimization can be achieved through connected mode mobility control or idle mode mobility control through the Near-RT RIC [38], Clause 3.1. In this version of the test specification, only the connected mode mobility control is addressed while idle mode mobility control is FFS.
-
-All the elements in the network, including the O-RAN system, 5G core and the application servers shall have the ability to capture traces to validate the successful execution of the test cases. The end user device shall have the capability to capture traces/packets to calculate the KPIs related to the RIC enabled use cases.
-
-### 9.2.1 Test Configuration
-
-##### 9.2.1.1 System Level Configuration
-
-The following system configuration parameters shall be configured and recorded in the test report:
-
-- Node configuration: mapping of cells to O-RUs, mapping of O-RUs to O-DUs and O-DUs to O-CU-CP/O-CU-UP, and configuration of basic RAN parameters over O1.
-
-- Traffic Steering mode: TS mode 0, TS mode 1 or TS mode 2 [38]
-- KPI optimisation policies: e.g., bit rate guarantee, QoS guarantee, maximum cell throughput and maximum system throughput etc.
-
-##### 9.2.1.2 Cell Level Configuration
-
-
-
-The diagram illustrates four cell sites, each represented by a large circle with a central base station icon. Each site has smaller circles representing small cells (hotspots) within its coverage area. A legend on the right shows four shaded squares labeled Band 1 (lightest) to Band 4 (darkest). The top-left site has one small cell on Band 3. The top-right site has one small cell on Band 2. The bottom-left site has three small cells on Bands 1, 2, and 3. The bottom-right site has three small cells on Bands 2, 3, and 4. Vertical ellipses between the sites indicate additional cell sites.
-
-Illustration of cell topologies showing four cell sites with varying numbers of small cells (hotspots) and their associated frequency bands (Band 1 to Band 4).
-
-Figure 9-2: Illustration of cell topologies
-
-In SA, the test setup consists of multiple 5G cells, each one associated with a certain O-DU and O-CU connected to a 5G core network. To evaluate system performance, the example parameters listed in Table 9-2 can be configured for different cell deployment scenarios. The network can have macro cells as a coverage layer and small cells at different locations for capacity boosting. Each cell site can provide service access on multiple frequency bands.
-
-Table 9-2 Example cell topology configurations
-
-| Item No. | Categories | Parameters |
-|----------|-------------------------------|-------------------------------------------------------------------------------------------|
-| 1 | Macro Cell deployment pattern | Inter-site distance
Cell radius
Cell location
Frequency bands |
-| 2 | Small Cell deployment pattern | Inter-site distance
Cell location
Cell radius
Frequency bands |
-| 3 | Inter-cell interference | Clause 3.7 |
-| 5 | Deployment Environment | Urban Macro
Urban Micro
Rural Macro
Indoor |
-| 6 | Antenna | Tx power, antenna height, tilt, azimuth, radiation pattern and number of antenna elements |
-| 7 | Network configurations | Carrier frequency
Duplexing mode
Bandwidth
Numerology |
-
-#### 9.2.1.3 UE Level Configuration
-
-The test environment shall have multiple UEs, with active traffic, moving across multiple cells. Locations where the radio conditions are excellent, good, fair, and poor need to be configured for each cell. UEs shall be placed into these different radio conditions.
-
-The UEs may be distributed in the geographical distribution scenarios as defined below (see Figure 9-3):
-
-- a) **uniform distribution:** UEs are placed with a spatial separation randomly selected following a uniform probability distribution.
-- b) **non-uniform distribution:** the UEs are placed with a spatial separation randomly selected following a certain distribution such that the UEs tend to be grouped in clusters. UE density at the small cell hotspot area may be higher than UE density in wider macro cell coverage area. The UEs in the cluster experience similar radio conditions.
-
-As illustrated in Figure 9-4, UE mobility trajectory may be a predefined **deterministic path** or may be based on **random walk** model following certain geographical distribution profiles (uniform or non-uniform distribution) defined above. UEs of different **speed categories** can be configured in the test with the speed profile as defined in Clause 4.5. UE mobility speed may increase and decrease from time to time around the typical value specified for each speed category within an interval defined by the minimum and maximum speed configuration. The location distribution, mobility trajectory, mobility class configurations shall be recorded in the test report along with the KPI measurement results defined in Clause 9.2.2.1 for a group of UEs of interest that is monitored for performance evaluation.
-
-
-
-The figure shows two diagrams of a cell coverage area represented by concentric ellipses. In diagram (a), labeled 'uniform', several UE icons are scattered across the entire area. In diagram (b), labeled 'non-uniform', the UE icons are clustered together within the inner ellipse, which represents a hotspot area.
-
-Figure 9-3: Illustration of UE distribution pattern (a) uniform (b) non-uniform
-
-Figure 9-3: Illustration of UE distribution pattern (a) uniform (b) non-uniform
-
-
-
-The figure shows two diagrams of a cell coverage area. In diagram (a), labeled 'deterministic route', a single UE icon is shown with a straight line and arrow indicating a direct path from the outer edge to the center. In diagram (b), labeled 'random walk', a single UE icon is shown with a highly irregular, looping line representing a random movement path within the cell.
-
-Figure 9-4: Illustration of UE trajectory pattern (a) deterministic route (b) random walk
-
-Figure 9-4: Illustration of UE trajectory pattern (a) deterministic route (b) random walk
-
-The following service-related parameters may be configured on a per UE per QoS flow basis as illustrated by the examples shown in Table 9-3 for the group of UEs of interest that is monitored for performance evaluation. Another group of UEs may be configured to apply background traffic load to each cell to create low, medium, and high load conditions for different service types as required. The traffic load condition for both groups may vary with time around the typical value within an interval defined by the minimum and maximum load variation configuration. The service-related configurations including cell load conditions shall be recorded in the test report.
-
-- User traffic type
-- Traffic target load
-- 5QI
-- S-NSSAI
-
-**Table 9-3: Example of UE service configuration for three UEs [37]**
-
-| UE Identifier | UE Id=1, S-NSSAI =1 | UE Id=2, S-NSSAI =2 | UE Id=3, S-NSSAI =3 |
-|---------------|-----------------------------------|----------------------------------------------------------|-----------------------------------------------------------------|
-| User Traffic | 5QI=1: Voice
5QI=8: FTP, Email | 5QI=1: Voice
5QI=8: Email
5QI=83: Advanced Driving | 5QI=1: Voice
5QI=8: Progressive Video
5QI=8: File sharing |
-
-The test should be repeated using various mobility and traffic conditions to sufficiently evaluate the E2E system performance with Non-RT RIC and Near-RT RIC optimization based on AI/ML technology, compensating for performance uncertainties of AI/ML models.
-
-#### 9.2.1.4 Expected Results and KPIs
-
-The values of the system level KPIs and end user KPIs for each test run both with and without Traffic-Steering enabled shall be included in the test report along with the test configuration parameters as defined Clause 9.2.2 to provide a comprehensive view of the test setup. The test results shall be recorded at a constant time interval that is short enough to identify features of interest in the test analysis where the value of the time interval shall be set appropriately for the UE mobility class configured.
-
-There are no passing criteria defined for this test due to the diversity of vendor-specific RRM and MAC layer scheduler implementations in the O-RAN system. The performance of the system with Non-RT RIC and Near-RT optimisations shall be benchmarked through analysis of KPI measurement results. The performance gain with Non-RT RIC and Near-RT optimisation is evaluated by comparing the test result with RIC optimisation enabled versus that with it disabled.
-
-The following statistical KPI measurements should be included in the test report with time stamps:
-
-Cell level KPIs (for cells in performance monitoring group):
-
-- Distribution/average of DL total PRB usage per cell
-- Distribution/average of UL total PRB usage per cell
-- Distribution/average of DL throughput per cell per QoS class
-- Distribution/average of UL throughput per cell per QoS class
-- Distribution/average of DL delay between NG-RAN and UE per cell per QoS class
-- Distribution/average of UL delay between NG-RAN and UE per cell per QoS class
-- Distribution/average of delay DL air-interface per cell per QoS class
-
-End user KPIs (for UEs in performance monitoring group):
-
-- Distribution/average of DL Total PRB Usage per UE
-- Distribution/average of UL Total PRB Usage per UE
-- Distribution/average of DL UE throughput per UE per QoS class
-- Distribution/average of UL UE throughput per UE per QoS class
-- Distribution/average of DL delay between NG-RAN and UE per UE per QoS class
-- Distribution/average of UL delay between NG-RAN and UE per UE per QoS class
-- Distribution/average of delay DL air-interface per UE per QoS class
-- Distribution/average of RSRP, RSRQ, PDSCH SINR per UE
-- Wideband CQI and MCS distribution in PDSCH per UE
-- Wideband CQI and MCS distribution in PUSCH per UE
-
-Optionally, the following instantaneous KPI measurements may be attached to the report (as appropriate) along with timestamps and UE geolocation information to provide further details in the test analysis.
-
-Cell level KPIs (for cells in performance monitoring group):
-
-- DL total PRB usage per cell
-- UL total PRB usage per cell
-- DL throughput per cell per QoS class
-- UL throughput per cell per QoS class
-- DL delay between NG-RAN and UE per cell per QoS class
-- UL delay between NG-RAN and UE per cell per QoS class
-- Delay DL air-interface per cell per QoS class
-
-End user KPIs (for UEs in performance monitoring group):
-
-- DL Total PRB Usage per UE
-- UL Total PRB Usage per UE
-- DL UE throughput per UE per QoS class (IP)
-- UL UE throughput per UE per QoS class (IP)
-- DL delay between NG-RAN and UE per UE per QoS class
-- UL delay between NG-RAN and UE per UE per QoS class
-- Delay DL air-interface per UE per QoS class
-- RSRP, RSRQ, PDSCH SINR per UE
-
-The corresponding definitions of the KPIs above can be found in 3GPP TS 28.552 [35], Clause 5.1.
-
-KPIs related to service Quality-of-Experience (QoE):
-
-- Call drop rate
-- Relative Jitter for voice traffic
-- DL RTP Error Rate for voice traffic
-- UL RTP Error Rate for voice traffic
-- MOS value for voice traffic
-- MOS value for video traffic
-- FTP download/upload throughput
-- Average DL/UL IP throughput
-- Average DL/UL IP latency
-
-### 9.2.2 RIC-TS1 – Traffic Steering (Connected Mode Mobility) Test Case
-
-##### 9.2.2.1 Test Description and Applicability
-
-The purpose of this test is to validate the O-RAN system's E2E performance for the Traffic Steering use case in a minimum viable network deployment scenario with two macro cells operating at low-band and mid-band respectively. In the test 3 groups of UEs with different mobility classes (high, low, and stationary) and running different services are configured. UEs in the first group run Voice (5QI=1) service and UEs in the second and third UE groups run MBB (5QI=9) service. All UEs stay in RRC connected state. The Non-RT and Near RT RIC are informed of the requirements and characteristics of the services as well as the mobility class of each UE. The RIC entities aim to steer the traffic to the most appropriate cells through Connected Mode mobility control to the guarantee QoS requirements for the service of each UE, maximize service continuity, and meanwhile maximize the overall system throughput for MBB service.
-
-The test applies to SA (Standalone) mode operation only in this version of the test specification.
-
-##### 9.2.2.2 System Level Configuration
-
-The following system configuration parameters should be configured and recorded in the test report:
-
-##### **Node Configuration (O-RU, O-DU, and O-CU-CP/O-CU-UP)**
-
-The node configuration of the SUT (O-RU, O-DU and O-CU-CP/O-CU-UP) is not specified. The utilized test configuration (parameters) shall be recorded in the test report.
-
-##### **Traffic Steering Mode**
-
-Optimization in Near-RT RIC can be done with A1 policy guidance from Non-RT RIC (TS Mode 2) or without the guidance (TS mode 1) [38]. The performance gain with TS Mode 1 or 2 optimization can be compared against TS Mode 0 where Non-RT RIC and Near-RT RIC assisted optimisation is disabled. The exact TS Mode configured for the test is not specified. The utilized configuration (parameters) shall be recorded in the test report.
-
-##### **KPI Optimization Policy**
-
-Guarantee QoS requirement for the service of each UE as defined in [39], Table 5.7.4-1, maximize service continuity, meanwhile maximize the system throughput and service experience for MBB (5QI=9) service.
-
-#### 9.2.2.3 Cell Level Configuration
-
-
-
-Illustration of cell topologies showing two overlapping circular coverage areas, Cell A (inner, smaller) and Cell B (outer, larger), on a grid background. The diagram includes a legend at the bottom with icons for various network elements like antennas, base stations, and user equipment.
-
-Figure 9-5: Illustration of cell topologies
-
-As illustrated in Figure 9-5, the UEs are in an area covered by two cells on different frequency bands identified as Cell A and Cell B respectively. Cell B is the macro cell operating at low band with the best coverage. Cell A is macro cell operating at mid-band providing higher capacity than Cell B but less coverage. The configuration parameters for each cell are shown in Table 9-4.
-
-Table 9-4 Cell configuration profile
-
-| Item No. | Categories | Parameters | Value |
-|----------|-------------------------------|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
-| 1 | Macro Cell deployment pattern | Inter-site distance | NA |
-| | | Cell radius | Cell A: typical urban macro cell range lower than Cell B, e.g., 2.5km
Cell B: typical urban macro cell range higher than Cell A, e.g., 5km |
-| | | Cell position | As shown in Figure 10-5 |
-| | | Number of sectors per cell | 3 |
-| | | Sector start/stop angle (degree) | Sector 1: e.g., 0-119
Sector 2: e.g., 120-239
Sector 3: e.g., 239-359 |
-| | | Frequency bands | Cell A: e.g., mid band, n77
Cell B: e.g., low band, n8 |
-| 2 | Small Cell deployment pattern | Inter-site distance | NA |
-| | | Cell radius | NA |
-| | | Cell position | NA |
-| | | Number of sectors per cell | NA |
-| | | Sector start/stop angle (degree) | NA |
-| | | Frequency bands | NA |
-| 3 | Inter-cell interference | Clause 3.7 | Apply inter-cell interference according to Clause 3.7 |
-| 5 | Deployment Environment | Urban Macro | Cell A, Cell B |
-| | | Urban Micro | NA |
-
-| Item No. | Categories | Parameters | Value |
-|----------|------------------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | Rural Macro | NA |
-| | | Indoor | NA |
-| 6 | Antenna | Tx power, antenna height, tilt, azimuth, radiation pattern and number of antenna elements | Typical configurations meeting the cell sectors and cell radius requirements defined above.
MIMO antenna configurations:
Cell A: e.g., 4TX, 4RX
Cell B: e.g., 2TX, 2RX |
-| 7 | Network configurations | Carrier frequency | Not specified |
-| | | Bandwidth | Cell A: e.g., 100 MHz
Cell B: e.g., 20 MHz |
-| | | Numerology | Cell A: e.g., 1
Cell B: e.g., 1 |
-
-#### 9.2.2.4 UE Level Configuration
-
-In this test case there are 3 groups of UEs defined. **Group 1** and **2** contain 10 UEs each that move within the area covered by the two frequency bands in a random walk pattern following a uniform geographical distribution as discussed in Clause 9.2.2.3. The mobility class for each group of UEs is defined in Table 9-5. Service-related parameters are configured on a per UE per QoS flow basis for the Group 1 and 2 UEs as defined in Table 9-5. **Group 3** contains 10 stationary UEs located at the position shown in Figure 9-6 applying background traffic load to each cell. The number of stationary UEs placed in each cell and the MBB traffic throughput of each UE is configured to create the low, medium, and high load conditions defined in Table 9-6. The stationary UEs stay on the cells defined without handover to other cells to sustain the defined load conditions.
-
-
-
-The figure shows a top-down view of two overlapping circular cells, Cell A and Cell B, on a grid. Cell A is the inner circle, and Cell B is the outer circle. Ten User Equipment (UE) icons are placed at specific locations:
-
-
-- UE0 is at the center of Cell A.
-- UE1 is at the bottom of Cell A.
-- UE2 is at the top of Cell A.
-- UE3 is at the top of Cell B.
-- UE4 is at the bottom of Cell B.
-- UE5 is at the bottom of Cell B.
-- UE6 is at the top of Cell B.
-- UE7 is at the top of Cell B.
-- UE8 is at the bottom of Cell B.
-- UE9 is at the bottom of Cell B.
-
- A legend at the bottom right shows various UE icons and symbols.
-
-Illustration of stationary UE positions on a grid with two cells, Cell A and Cell B, and various UE icons labeled UEs 0 through 9.
-
-Figure 9-6: Illustration of stationary UE positions
-
-**Table 9-5 UE configuration profile**
-
-| | | | |
-|------------------|-----------------------------------------|-----------------------------------------|-----------------------------------------|
-| UE Identifier | Group 1, UE Id=1-10, S-NSSAI=1 | Group 2, UE Id=21-30, S-NSSAI=1 | Group 3, UE Id=41-50, S-NSSAI=1 |
-| User Traffic | 5QI=1: Voice | 5QI=9: Video, FTP | 5QI=9: FTP |
-| Mobility Class | 50% Low mobility
50% High mobility | 50% Low mobility
50% High mobility | Stationary |
-| Frequency Band | low band and mid-band, e.g., n8 and n77 | low band and mid-band, e.g., n8 and n77 | low band and mid-band, e.g., n8 and n77 |
-| Bandwidth | DL:20MHz, 100MHz
UL:20MHz, 100MHz | DL:20MHz, 100MHz
UL:20MHz, 100MHz | DL:20MHz, 100MHz
UL:20MHz, 100MHz |
-| Max. MIMO Layers | DL:4, UL:2 | DL:4, UL:2 | DL:4, UL:2 |
-
-**Table 9-6 Stationary UE service configuration profile**
-
-| | | |
-|-----------------------|-------------------|-----------------|
-| Cell | A | B |
-| No. of stationary UEs | 4 | 6 |
-| Traffic Load | Medium, e.g., 50% | High, e.g., 90% |
-
-#### **9.2.2.5 Initial Condition**
-
-- 1) The End-to-end setup shall be 5G SA, operational, and there shall be no connectivity issues.
-- 2) The test setup is configured according to the test configuration.
-
-#### **9.2.2.6 Test procedure**
-
-- 1) Disable traffic steering optimization by Near-RT RIC and Non-RT RIC (TS Mode 0 [38]).
-- 2) Power on the end user devices and ensure they register with the 5G core for data, video, or voice service over SA by connecting over the SUT.
-- 3) Once the registration is complete, the end user devices establish PDU sessions with the 5G core.
-- 4) Once the PDU sessions have been setup, the end user devices with voice or video traffic register with the IMS core to support Voice-over-NR or Video-over-NR service.
-- 5) Take appropriate action to enable the traffic according to the traffic configuration profile as discussed in Clause 9.2.3.4.
-- 6) Once the traffic has started, move the devices according to the mobility patterns and mobility classes configured (Clause 9.2.3.4).
-- 7) Observe the policies and commands from RIC over E2, O1 and A1 interfaces, capture traces over the interfaces (as required) for validating successful test execution.
-- 8) Keep the test running for 10 minutes, measure and record the KPIs as defined in Clause 9.2.3.7.
-- 9) Take appropriate action to reset the network and traffic conditions to its initial state at before Step 3.
-- 10) Enable the traffic steering optimisation from Near-RT and Non-RT RIC (TS Mode 1 or TS Mode 2 [38]), repeat Step 4-10.
-- 11) Analyse the KPI measurement results. Evaluate the performance gain with Non-RT RIC and Near-RT optimisation enabled versus that with it disabled.
-
-#### 9.2.2.7 Expected Result
-
-The exact optimization behaviors from Non-RT RIC and Near-RT RIC are not specified due to the diversity of vendor-specific RRM and MAC layer scheduler implementations in the O-RAN system making it impossible to specify a standardized behaviour pattern. However, behaviors similar to the example below shall be observed from the trace information captured from the emulated UEs.
-
-- 1) For UEs in Group 1, voice traffic (5QI=1) should preferably reside on Cell B to minimize inter-cell handovers for service continuity.
-- 2) For UEs in Group 2, the MBB traffic with (5QI=9) should preferably reside on Cell A if the radio and cell load condition on Cell A gives higher throughput and user experience for MBB service than Cell B.
-
-Serving cell and frequency band change for each UE in UE Group 1 and 2 can be observed from the trace information captured from the emulated UEs in order to confirm the Traffic Steering optimization behaviors from the Non-RT RIC and Near-RT RIC as discussed above.
-
-The performance of the system with Non-RT RIC and Near-RT optimisation shall be benchmarked through analysis of KPI measurement results as discussed in Clause 9.2.2.4. The performance gain with Non-RT RIC and Near-RT optimisation is evaluated by comparing the test result with RIC optimisation enabled versus that with it is disabled. The number of UEs meeting the QoS requirement for voice service (5QI=1) and MBB service (5QI=9), count of service drops, and the total system throughput and service experience for MBB service with Non-RT RIC and Near-RT RIC optimisation in Step 11 (Clause 9.2.3.6) shall outperform the case without the optimisation in Step 1-8 (Clause 9.2.3.6).
-
-The following statistical KPI measurements should be included in the test report:
-
-System level KPIs:
-
-- Number of UEs meeting the QoS requirement for voices service (5QI=1)
-- Number of UEs meeting the QoS requirement for MBB service (5QI=9)
-- Average system DL PDCP throughput
-- Average system UL PDCP throughput
-
-Cell level KPIs (for cells in performance monitoring group) [35]:
-
-- Average DL throughput per cell
-- Average UL throughput per cell
-- Average DL delay between NG-RAN and UE per cell
-- Average UL delay between NG-RAN and UE per cell
-- DL Cell PDCP SDU Data Volume
-- UL Cell PDCP SDU Data Volume
-
-End user KPIs (for UEs in performance monitoring group) [35]:
-
-- Average DL UE throughput per UE
-- Average UL UE throughput per UE
-- Average DL delay between NG-RAN and UE per UE
-- Average UL delay between NG-RAN and UE per UE
-
-KPIs related to user experience for Voice service:
-
-- MOS Score – Mean Opinion Score for the voice call. This needs to be measured on both ends of the Voice call – mobile originated and mobile terminated.
-- Mute Rate % – This is the percentage of calls which were muted in both directions (calls with RTP loss of > 3-4s in both directions are considered muted call). This needs to be measured on both ends of the Voice call – mobile originated and mobile terminated and counted only once per call.
-- One Way Calls % – This is the percentage of calls which were muted in any one direction (calls with RTP loss of > 3-4s in one direction only are considered one-way calls). This needs to be monitored on both ends of the Voice call – mobile originated and mobile terminated and counted only once per call.
-- RTP Packet Loss % - Number of RTP packets which were dropped/lost in uplink/downlink direction as a percentage of total packets. This needs to be measured on both ends of the Voice call – mobile originated and mobile terminated.
-
-KPIs related to user experience for Video service:
-
-- Video start time or Time to load first video frame – Time from when the video was selected to play to when the video starts playing in seconds.
-- Video MOS score – MOS score for the video streaming session as defined by ITU P1203.3.
-
-KPIs related to user experience for FTP service:
-
-- Download throughput – This is the average application layer throughput to download the file in kbps.
-- Upload throughput – This is the average application layer throughput to upload the file in kbps.
-- Time taken to Download file – This is the time taken to download the file in seconds.
-- Time taken to Upload file – This is the time taken to upload the file in seconds.
-
-## 9.3 Network Energy Saving with Carrier and Cell switch off/on using Non-RT RIC
-
-### 9.3.1 Functional test
-
-#### 9.3.1.1 Test Description and Applicability
-
-The purpose of this test is E2E functional validation of O-RAN system (see Clause 9.3.1.2) to support Network Energy Saving feature/use case with Carrier and cell switch off/on [36][46] using a minimum viable network deployment scenario with two overlapping cells/carriers. The E2E functional validation focuses on messaging between E2 nodes and SMO/Non-RT RIC utilizing the O1/M-plane interface and switching off/on behavior of the cell(s) under test. The cells/carriers operate as overlay coverage cell (low frequency band) and capacity cell (high frequency band) respectively. Figure 9-7 shows two cell topology options, one with two macro cells and another with macro and small cells. When the traffic load is low, energy saving can be achieved by switching off the entire capacity cell without impairing the network experiences. The switch off/on decision is made by the Non-RT RIC (deployment option 1) [36][46].
-
-For the sake of simplicity, the AI/ML model training phase [36][46] is not considered and may be added in a later version of the specification.
-
-
-
-Figure 9-7: Minimum viable network deployment scenarios for functional validation of Network energy saving with Carrier and cell switch off/on using Non-RT RIC. The diagram shows two scenarios. The left scenario shows a 'coverage cell' (large sector) and a 'capacity cell' (smaller sector) within the coverage area. 'UE group 1' is shown outside the capacity cell, and 'UE group 2' is shown inside the capacity cell. The right scenario shows a 'coverage cell' (large sector) and a 'capacity cell' (smaller sector) within the coverage area. 'UE group 1' is shown outside the capacity cell, and 'UE group 2' is shown inside the capacity cell. Both scenarios illustrate the placement of User Equipment (UE) groups relative to capacity and coverage cells.
-
-Figure 9-7: Minimum viable network deployment scenarios for functional validation of Network energy saving with Carrier and cell switch off/on using Non-RT RIC.
-
-#### 9.3.1.2 Test setup and configuration
-
-The test setup is shown in Figure 9-8. The System under test (SUT) is comprised of one or multiple O-RU(s), E2 nodes (such as O-DU, O-CU-CP, O-CU-UP), Non-RT RIC, SMO and Energy saving rApp [10][36]. E2 nodes are connected via O1 interface to SMO/Non-RT RIC. In case of hybrid mode, O-RU is connected via Open Fronthaul M-plane interface to SMO directly. The specific configuration and deployment are not defined and unified, but it shall be recorded in the test report. The energy consumption/efficiency can be affected by the specific configuration and deployment. Note that the test results are valid only for this specific configuration and deployment.
-
-The real or emulated UEs generate the traffic load to trigger the carrier/cell switch off/on decision. The 5G NR Standalone Architecture (Option 2) is considered in this test case with real or emulated 5G Core and Application Server. Later version of the specification may add also support of other architectures (see Clause 4.0).
-
-The Non-RT RIC/rApp should be configured to trigger the cell and carrier switch off/on according to used traffic model. The E2E functional validation focuses on messaging between E2 nodes and SMO/Non-RT RIC utilizing the O1/M-plane interface and switching off/on behavior of the cell(s) under test.
-
-
-
-Figure 9-8: Test setup diagram. The diagram shows the System Under Test (SUT) enclosed in a dashed orange box. Inside the SUT, there is an SMO and a Non-RT RIC + Energy saving rApp. The SMO is connected to the Non-RT RIC via an O1 interface. The Non-RT RIC is connected to the O-DU via an O1 interface. The O-DU is connected to the O-CU-CP via an F1-c interface and to the O-CU-UP via an F1-u interface. The O-CU-CP is connected to the 5GC via an Ng-c interface, and the O-CU-UP is connected to the 5GC via an Ng-u interface. The O-RU is connected to the O-DU via an OpenFH interface. The O-RU is also connected to the SMO via an OpenFH M-plane (hybrid mode) interface. The UE is connected to the O-RU via a Uu interface.
-
-**Figure 9-8: Test setup for E2E functional validation of Network energy saving with Carrier and cell switch off/on using Non-RT RIC (deployment option 1 in [36][46])**
-
-As illustrated in Figure 9-7, stationary test UEs are distributed and attached in coverage or capacity cells to generate the required traffic load in downlink and uplink directions. The test UEs of group 2 are in coverage of both coverage and capacity cells while the test UEs of group 1 are only in coverage of coverage cell. The test UEs of group 1 are attached/served in coverage cell while the test UEs of group 2 are attached/served in capacity cell. If the capacity cell is to be switched off, the test UEs of group 2 (that are still attached/served by capacity cell) shall be offloaded to coverage cell.
-
-### 9.3.1.3 Test Procedure
-
-- 1) The test setup is operational and configured according to the Clause 9.3.1.2. The test configuration shall be recorded in the test report. Coverage and capacity cells are activated and operational.
-- 2) A total of four stationary UEs are power on and distributed as follows: 2 UEs in group1 (in coverage of coverage cell and attached in coverage cell) and 2 UEs in group 2 (in coverage of both coverage and capacity cells and attached in capacity cell) – see Figure 9-7.
-- 3) The deployment and configuration (parameters) of coverage and capacity cells and distribution and position of test UEs are not changed during the whole test.
-- 4) Network energy saving feature with Carrier and cell switch off/on energy is enabled (ESfeature ON).
-- 5) The test UEs start downlink and uplink full-buffer data transmission (UDP or TCP) to achieve the maximum cell throughput (100%) in capacity cell (UEs of group 2) and 20% of the maximum cell throughput in coverage cell (UEs of group 1) in both downlink and uplink directions. The data transmission of UEs of group 1 remains constant during the whole test.
-- 6) Start tracing the messages over O1/M-plane interface and collecting the other required data/KPIs specified in Clause 9.3.1.4. The traces can be captured over the interfaces or collected from logfiles at nodes for validating successful execution.
-- 7) The downlink and uplink data transmission of UEs of group 2 is reduced to trigger the carrier/cell switch off/on decision when the capacity cell is switched off and UEs of group 2 are handover to coverage cell. Now, all test UEs are served by coverage cell.
-- 8) The downlink and uplink data transmission of UEs of group 2 is stopped.
-- 9) The downlink and uplink data transmission of UEs of group 2 is increased to trigger the carrier/cell switch off/on decision when the capacity cell is switched on and UEs of group 2 are handover to capacity cell. Now, the UEs of group 1 are served by coverage cell while the UEs of group 1 are served by capacity cell.
-- 10) Stop all tracing and logging of messages and data.
-
-#### 9.3.1.4 Test requirements (Expected Results)
-
-The exact optimization behavior of Non-RT RIC/rApp is not specified due to the diversity of vendor specific energy saving implementations making it impossible to specify a standardized behavior pattern. However, the behavior like the example below shall be observed during the test [36][46]:
-
-- 1) As the load in capacity cell is decreasing, the carrier/cell switch off/on decision is made, and appropriate operations to switch off capacity cell need to be taken in SMO/Non-RT RIC/rApp, E2 Node(s) and O-RU(s). If the capacity cell is to be switched off, the test UEs of group 2 shall be handover to the coverage cell. No UE drop is observed during these steps. The SMO/Non-RT RIC/rApp is notified by E2 Node(s) and O-RU(s) that the capacity cell switch off has been completed.
-- 2) As the load in coverage cell is increasing, the carrier/cell switch off/on decision is made, and appropriate operations to switch on capacity cell need to be taken in SMO/Non-RT RIC/rApp, E2 Node(s) and O-RU(s). If the capacity cell is to be switched on, the test UEs of group 2 shall be handover to the capacity cell. No UE drop is observed during
-
-these steps. The SMO/Non-RT RIC/rApp is notified by E2 Node(s) and O-RU(s) that the capacity cell switch on has been completed.
-
-Messages over O1 and M-plane interfaces between SMO/Non-RT RIC and O-CU-CP/O-CU-UP/O-DU/O-RU should be observed and recorded.
-
-### 9.3.2 Performance test
-
-##### 9.3.2.1 Test Description and Applicability
-
-The purpose of this test is to provide an indication of E2E performance of O-RAN system supporting Network Energy Saving feature/use case with Carrier and cell switch off/on [36][46] using a minimum viable network deployment scenario with two overlapping cells/carriers. This test provides indicative energy efficiency gain of Carrier and cell switch off/on feature by measuring the energy consumption of O-RAN system with the feature on and off using a traffic model. The cells/carriers operate as overlay coverage cell (low frequency band) and capacity cell (high frequency band) respectively. Figure 9-7 shows two cell topology options, one with two macro cells and another with macro and small cells. When the traffic load is low, energy saving can be achieved by switching off the entire capacity cell without impairing the network experiences. The switch off/on decision is made by the Non-RT RIC (deployment option 1) [36][46].
-
-For the sake of simplicity, the AI/ML model training phase [36][46] is not considered and may be added in a later version of the specification.
-
-##### 9.3.2.2 Test setup and configuration
-
-The test setup is shown in Figure 9-9. The System under test (SUT) is comprised of one or multiple O-RU(s), E2 nodes (such as O-DU, O-CU-CP, O-CU-UP), Non-RT RIC, SMO and Energy saving rApp [10][36]. E2 nodes are connected via O1 interface to SMO/Non-RT RIC. In case of hybrid mode, O-RU is connected via Open Fronthaul M-plane interface to SMO directly. The specific configuration and deployment are not defined and unified, but it shall be recorded in the test report. The energy consumption/efficiency can be affected by the specific configuration and deployment. Note that the test results are valid only for this specific configuration and deployment.
-
-The real or emulated UEs generate the traffic load to trigger the carrier/cell switch off/on decision. The 5G Standalone Architecture (Option 2) is considered in this test case with real or emulated 5G Core and Application Server. Later version of this specification may add also support of other architectures (see Clause 4.0).
-
-The Non-RT RIC/rApp should be configured to trigger the cell and carrier switch off/on according to used traffic model.
-
-
-
-Figure 9-9: Test setup for E2E performance testing of Network energy saving with Carrier and cell switch off/on using Non-RT RIC. The diagram shows a UE connected to an O-RU, which is part of a System Under Test (SUT). The SUT includes an O-DU, O-CU-CP, O-CU-UP, and O-Cloud. The O-RU is connected to the O-DU via an OpenFH interface. The O-DU is connected to the O-CU-CP via an F1-c interface and to the O-CU-UP via an F1-u interface. The O-CU-CP is connected to the O-CU-UP via an E1 interface. The O-CU-CP is connected to the 5GC via an Ng-c interface, and the O-CU-UP is connected to the 5GC via an Ng-u interface. The SMO (Service Management and Orchestration) is connected to the O-RU via an OpenFH M-plane (hybrid mode) interface. The SMO contains a Non-RT RIC + Energy saving rApp. The Non-RT RIC is connected to the O-DU, O-CU-CP, and O-CU-UP via O1 interfaces. An Energy meter is connected to the O-RU and the O-Cloud.
-
-**Figure 9-9: Test setup for E2E performance testing of Network energy saving with Carrier and cell switch off/on using Non-RT RIC (deployment option 1 in [36][46]) assuming typical deployment of O-RU as PNF and O-DU, O-CU-CP/O-CU-UP as VNF/CNF in O-Cloud.**
-
-As illustrated in Figure 9-7, stationary test UEs are distributed and attached in coverage or capacity cells to generate the required traffic load in downlink and uplink directions. The test UEs of group 2 are in coverage of both coverage and capacity cells while the test UEs of group 1 are only in coverage of coverage cell. The test UEs of group 1 are attached/served in coverage cell while the test UEs of group 2 are attached/served in capacity cell. If the capacity cell is to be switched off, the test UEs of group 2 (that are still attached/served by capacity cell) shall be offloaded to coverage cell.
-
-The energy consumption can be measured by energy meter or reported energy consumption values via O1/M-plane interfaces can be used.
-
-##### 9.3.2.3 Test Procedure
-
-The tester can choose one or more traffic models. Later version of the specification may add additional traffic models.
-
-##### 9.3.2.3.1 Basic traffic model
-
-Quick test that provides a basic insight to E2E performance.
-
-- 1) The test setup is operational and configured according to the Clause 9.3.2.2. The test configuration shall be recorded in the test report. Coverage and capacity cells are activated and operational.
-- 2) Test UEs are powered on and distributed in coverage and capacity cells. The exact number of UEs is not defined, but the number of UEs shall be sufficient to generate required cell throughput in both downlink and uplink directions (see Step 5).
-- 3) The deployment and configuration (parameters) of coverage and capacity cells and distribution and position of test UEs are not changed during the whole test.
-- 4) Network energy saving feature with Carrier and cell switch off/on is disabled ( $ES_{feature}$ OFF).
-- 5) The test UEs start downlink and uplink full-buffer data transmission (UDP or TCP) to achieve the maximum cell throughput (100%) in capacity cell (UEs of group 2) and 20% of the maximum cell throughput in coverage cell (UEs of group 1) in both downlink and uplink directions. The data transmission of UEs of group 1 remains constant during the whole test.
-- 6) Start measuring the energy consumption (EC) of SUT (O-RU(s), O-DU(s), O-CU-CP(s), O-CU-UP(s)) and collecting the other required data/KPIs specified in Clause 9.3.2.4.
-
-- 7) After 15 mins, the total downlink and uplink data transmission of UEs of group 2 (capacity cell throughput) is reduced by 10% (of the maximum cell throughput).
-- 8) Step 7 is repeated until the total downlink and uplink data transmission of UEs of group 2 is reduced to 0. In case of ESfeature ON, when the carrier/cell switch off/on decision is triggered, UEs of group 2 are handover from capacity to coverage cell and capacity cell is switched off.
-- 9) After 15 mins, the total downlink and uplink data transmission of UEs of group 2 (capacity cell throughput) is increased by 10% (of the maximum cell throughput).
-- 10) Step 9 is repeated until the maximum cell throughput (100%) of capacity cell is reached. In case of ESfeature ON, when the carrier/cell switch off/on decision is triggered, the capacity cell is switched on and UEs of group 2 are handover from coverage cell to capacity cell.
-- 11) Stop measuring the energy consumption and collecting the data/KPIs. Record all collected data.
-- 12) All test UEs stop downlink and uplink data transmission.
-- 13) Steps 5 to 12 are repeated for enabled Network energy saving feature with Carrier and cell switch off/on (ESfeature ON).
-
-###### 9.3.2.3.1 ETSI-based traffic model
-
-Complex traffic model but provides more realistic results/data.
-
-**Table 9-7: Traffic Model Parameters.**
-
-| Radio Condition | Good | | | Fair | | | Poor | | |
-|------------------------------|--------|--------|--------|------|-----|-----|--------|--------|--------|
-| % of UEs per pathloss | 15% | | | 70% | | | 15% | | |
-| File size [kByte] | 0.1 | 1 | 250 | 0.1 | 1 | 250 | 0.1 | 1 | 250 |
-| % of file distribution | 44% | 28% | 28% | 50% | 25% | 25% | 50% | 25% | 25% |
-| Inter arrival time [ms] | 4 | 20 | 200 | 4 | 20 | 200 | 4 | 20 | 200 |
-| % of UEs per path files size | 33.33% | 33.33% | 33.33% | 50% | 25% | 25% | 33.33% | 33.33% | 33.33% |
-
-- 1) The test setup is operational and configured according to the Clause 9.3.2.2. The test configuration shall be recorded in the test report. Coverage and capacity cells are activated and operational.
-- 2) The deployment and configuration (parameters) of coverage and capacity cells and distribution and position of test UEs are not changed during the whole test.
-- 3) Network energy saving feature with **Carrier and cell switch off/on is disabled (ESfeature OFF)**.
-- 4) Attach UEs of group 1 to coverage cell sequentially and start downlink and uplink data transmission (UDP or TCP) according to the traffic model defined in Table 9-7. The explanation of the parameters in the table is defined in Clause 3.3.3 of [45] while the definition of radio conditions can be found in Clause 4.6.
-- 5) Attach UEs of group 2 to capacity cell sequentially and start downlink and uplink data transmission according to the traffic model defined in Table 9-7 considering only good radio condition, which means that all UEs in capacity cell are in good radio condition.
-- 6) Monitor the PRB (Physical Resource Block) utilization in capacity and coverage cells until the average PRB utilization reaches 70%. Record the number of attached UEs of group 1 (in coverage cell) as X, and the number of attached UEs of group 2 (in capacity cell) as Y. If PRB utilization cannot reach 70%, inter arrival time in the traffic model can be decreased to achieve a higher PRB utilization.
-- 7) Start measuring of energy consumption of SUT (O-RU(s), O-DU(s), O-CU-CP(s), O-CU-UP(s)), and collecting the other required data/KPIs specified in Clause 9.3.2.4. If O-DU, O-CU-CP/O-CU-UP are deployed as VNF or CNF, mean vCPU usage of involved virtual instance and all virtual instances running on the same NFVI shall be measured (see Clause 9.3.2.4).
-
-- 8) Continue downlink and uplink data transmission according to traffic model defined in Table 9-7 with X UEs in coverage cell and Y UEs in capacity cell for 5 minutes.
-- 9) Detach the UEs of group 1 and group 2 sequentially so that all UEs are detached after 30 minutes. No UE is attached in coverage and capacity cells.
-- 10) Start attaching UEs of group 1 to coverage cell, UEs of group 2 to capacity cell and start downlink and uplink data transmission according to the traffic model defined in Table 9-7. Attach rate for UE group 1 and group 2 shall ensure that after 30 minutes X UEs of group 1 and Y UEs of group 2 are attached.
-- 11) Continue running downlink and uplink data according to traffic model as defined in Table 9-7 with X UEs attached in coverage cell and Y UEs attached in capacity cell for 5 minutes.
-- 12) Stop measuring the energy consumption of SUT and collecting the data/KPIs.
-- 13) All test UEs stop downlink and uplink data transmission.
-- 14) Network energy saving feature with **Carrier and cell switch off/on is enabled (ESfeature ON)**.
-- 15) Attach X UEs of group 1 to coverage cell and Y UEs of group 2 to capacity cell and start downlink and uplink data transmission according to the traffic model defined in Table 9-7.
-- 16) Steps 7 to 13 are repeated for enabled Network energy saving feature with Carrier and cell switch off/on.
-
-#### 9.3.2.4 Test requirements (Expected Results)
-
-In addition to deployment and test configuration (parameters), the following metrics and counters should be collected and reported for the performance assessment.
-
-- Total data volume [Mbits] transmitted in downlink direction during the test period of ESfeature ON and ESfeature OFF. The application data transmitted from application server to UEs.
-- Total data volume [Mbits] transmitted in uplink direction during the test period of ESfeature ON and ESfeature OFF. The application data transmitted from UEs to application server.
-- Total energy consumption [kWh] of SUT, incl. individual energy consumption of all measured components of SUT, during the test period of ESfeature ON and ESfeature OFF
-
-The following figures shall be also included in the test report:
-
-- Downlink PDCP throughput of coverage and capacity cells during the test period of ESfeature ON vs Time of test period (average sample per second)
-- Downlink PDCP throughput of coverage and capacity cells during the test period of ESfeature OFF vs Time of test period (average sample per second)
-- Uplink PDCP throughput of coverage and capacity cells during the test period of ESfeature ON vs Time of test period (average sample per second)
-- Uplink PDCP throughput of coverage and capacity cells during the test period of ESfeature OFF vs Time of test period (average sample per second)
-- Energy consumption of SUT during the test period of ESfeature ON vs Time of test period (average sample per 10 seconds)
-- Energy consumption of SUT during the test period of ESfeature OFF vs Time duration (average sample per 10 seconds)
-- Number of RRC connected UEs in coverage and capacity cells during the test period of ESfeature ON vs Time duration (average sample per 10 seconds)
-- Number of RRC connected UEs in coverage and capacity cells during the test period of ESfeature OFF vs Time duration (average sample per 10 seconds)
-
-##### Gain of Network energy saving feature with Carrier and cell switch off/on
-
-In case of PNF (typically O-RU), the energy consumption ( $EC_{PNF}$ ) is measured by an energy meter and obtained according to Clause 5.1.1.19.3 of [35].
-
-In case of VNF or CNF (typically O-DU, O-CU-CP/O-CU-UP), according to Clause 6.7.3.1.4 of [44], the energy consumption (EC) of virtual instance is estimated as a proportion of the energy consumption of the O-Cloud on which the virtual instance runs. This proportion is obtained by dividing the mean vCPU usage ( $VCpuUsageMean$ ) of the virtual instance, by the sum of the vCPU mean usage of all virtual instances running on the O-Cloud.
-
-$$EC_{virtual\_instance,estimated}[kWh] = \frac{VCpuUsageMean_{virtual\_instance,measured}}{\sum_{virtual\_instances} VCpuUsageMean_{virtual\_instance,measured}} * EC_{O-Cloud,measured}$$
-
-To minimize the impact of other virtual instances that share the O-Cloud with virtual instance(s) involved in testing, the other virtual instances should be disabled (i.e. only involved virtual instances use O-Cloud) or their vCPU usage should be constant during whole test.
-
-The energy consumption of SUT ( $EC_{SUT}$ ) is obtained as the sum of measured energy consumption of PNFs (typically O-RU) and the sum of estimated energy consumption of all involved virtual instances (typically O-DU, O-CU-CP, O-CU-UP).
-
-$$EC_{SUT}[kWh] = \sum_{PNFs} EC_{PNF,measured} + \sum_{virtual\_instances} EC_{virtual\_instance,estimated}$$
-
-The energy efficiency (EE) [36] is obtained by dividing the total volume of data transmitted in downlink and uplink directions in capacity and coverage cells by the energy consumption of SUT during the test period. The energy efficiency is calculated for disabled and enabled Network energy saving feature with Carrier and cell switch off/on as follows:
-
-$$EE_{ES_{featureON}} = \frac{TotalDataVolume [Mbits]}{EC_{SUT} [kWh]}$$
-
-The gain of Network energy saving feature with Carrier and cell switch off/on is obtained by dividing energy efficiency of SUT with enabled Network energy saving feature by energy efficiency of SUT with disabled Network energy saving feature.
-
-$$Gain_{ES_{feature}} = \frac{EE_{ES_{featureON}}}{EE_{ES_{featureOFF}}}$$
-
-# 10 Profile-based Performance Tests
-
-## 10.1 Introduction
-
-This clause describes the tests which can be used to evaluate the performance of radio access network from the network end-to-end perspective (see clause 4.1).
-
-The focus of the testing is on evaluating the RAN performance with complex test scenarios through the test configuration of the number of UEs (sufficiently high number), radio channel impairments (channel models), mobility profiles, mixed end users' services and application traffic.
-
-The tests defined in Clause 10.4 are designed to follow a **test configuration profile-based approach** as such test configuration profile parameters values (see Clause 10.2 - such as number of UEs and UEs distribution among other parameter values) defines the scope of tests. The scope of tests can therefore be easily extended to support different test scenarios by specifying different test configuration profiles - not needing to always create new tests, i.e. the same test can be used for scenarios with single UE, multiple UEs, stationary UEs, mobile UEs, downlink data traffic, uplink data traffic, voice traffic, etc.
-
-The test configuration profile(s) shall be defined and recorded as part of the test report.
-
-## 10.2 Test Configuration Profile
-
-Table 10.2-1 lists the test configuration profile parameters.
-
-**Table 10.2-1: Test Configuration Profile Parameters**
-
-| Item No. | Parameters | Sub parameters | Comments / Justification |
-|---------------------------------|---------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 1. Network Configuration | | | |
-| 1a | Deployment Scenario | - | Refer to clause 4.3 “Deployment scenario” for the information which are required to be specified.
Refer to Table 8-6 for an example listing of typical traffic model types |
-| 1b | Cell Configuration | Number of Cells (NumCells) | Number of Cells – 1 or more Cells - For each Cell, specify the Cell Id and Cell Configuration, Neighbour cell configuration and CA related configuration.
Cell Id - unique number which identifies the Cell within this Configuration Profile. This is not needing to be specified as the 3GPP Cell Identifier.
Cell Configuration Parameters - refer to clause 4.3 “Cell configuration parameters of each cell”.
Neighbour Cell Ids - list of Cell Ids of neighbour cells.
Cell Ids for possible SCell - list of Cell Ids of the cells that can be configured as SCell.
Example 1 – Neighbour Cell Ids (The cells with “Cell Id = 1” and “Cell Id = 2” are neighbour cells. The cells with “Cell Id = 2” and “Cell Id = 3” are neighbour cells.) - Neighbour Cell Ids of the Cell with “Cell Id = 1” is “2”.
- Neighbour Cell Ids of the Cell with “Cell Id = 2” is “1 and 3”.
- Neighbour Cell Ids of the Cell with “Cell Id = 3” is “2”.
|
-| | | Cell Configuration for Each Cell 1..< NumCells > | |
-| | | > Cell Id | |
-| | | > Cell Configuration Parameters | |
-| | | > Neighbour Cell Ids | |
-| | | > Cell Ids for possible SCell | |
-| 2. UE Configuration | | | |
-| 2a | Number of UEs | NumUes | Total number of UEs in all the Cells |
-| 2b | Number of UE Groups | NumUeGroups | Number of UE Groups – defines 1 or more UE Groups as each UE group will be uniquely identified by a UE Group Id.
The “Total number of UEs” maybe distributed to 1 or more UE Groups specified by the “Number of UE Groups”. |
-| | | UE Group Configuration Parameters 1..< NumUeGroups> | |
-| | | > UE Group Id | |
-| | | > Number of UEs (NumUesinGroup) | |
-
-| Item No. | Parameters | Sub parameters | Comments / Justification |
-|------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | > CapabilityOfCA | UE Group Id - unique number which identifies the UE Group within this Configuration Profile.
NumUesinGroup - Specify the number of UEs in each of the UE Groups as either a ratio of total number of UEs “NumUes” or an absolute number.
CapabilityOfCA - information if the UE group has CA capability of a certain carrier/band combination.
Example 1 – CA scenario (80% UEs with n1 and n79 CA capability)
Number of UE Groups – 2
- • NumUesinGroup in group A is 80% of NumUes.
- • NumUesinGroup in group B is 20% of NumUes.
- • CapabilityOfCA of Groups A is CA_n1-n79.
- • CapabilityOfCA of Groups B is None.
|
-| 2c | UEs Distribution | Uniform or Non-uniform | UEs may be distributed in a uniform or non-uniform manner inside a cell.
This parameter is used to specify the UEs distribution common for all the cells.
Non-uniform distribution (with clusters) uses same random seed for the UEs distribution to achieve repeatability.
|
-| 2d | Registration Rate | - | Number of UEs to perform registration per minute and within the minute the specified number of UEs are evenly distributed in performing its registration procedure.
Example – “Registration Rate = 120 UEs/minute” will result in one UE performing registration every 500ms.
|
-| 3. Radio Conditions Configuration | | | |
-| 3a | Radio Conditions and UE Placement
Refer to Section 4.6 | Radio Conditions Configuration Parameters
1..< NumUeGroups>
> UE Group Id
> Stationary or Mobility
> Cell Id(s) and associated Radio Condition(s)
> Mobility Profile (required for UE Group(s) which are configured for Mobility) | For each UE Group, specify
- • UE Group Id
- • Stationary or Mobility
- • Cell Id(s) and associated Radio Condition(s)
- • Mobility Profile (required for UE Group(s) which are configured for Mobility)
UE Group Id - unique number which identifies the UE Group within this Test Configuration Profile per defined in item 2(b).
Stationary or Mobility – Specify if the group of UEs is to be supporting stationary or mobility scenarios.
Cell Id(s) and associated Radio Condition(s) -
- • For UE Group(s) configured with Stationary profile – specify only 1 Cell Id and the Radio Condition associated with the Cell Id.
- • For UE Group(s) configured with Mobility profile – specify a list of Cell Ids and the Radio Condition associated with each of the Cell Ids in this list.
Refer to Table 4-2 for RSRP and SINR thresholds for the various radio conditions.
|
-
-| Item No. | Parameters | Sub parameters | Comments / Justification |
-|------------------------------------|--------------|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | | Mobility Profile - configured mainly through the varying speed and radio conditions. Refer to Section 4.5 “Mobility Classes for speed”.
For simplification purpose, further sophisticated / complex mobility and channel modelling is not considered.
Example 1 – Single Cell Scenario
Number of UE Groups – 5
- • NumUesinGroup in each group is 20% of NumUes. All UEs are in the same cell.
- • Groups A, B, C, D are configured as Stationary UEs, each configured with different Radio Conditions.
- ○ A: Excellent (Cell Center)
- ○ B: Good
- ○ C: Fair
- ○ D: Poor (Cell Edge)
- • Group E is configured as UEs supporting Mobility moving through different Radio Conditions within the same Cell with the configured Mobility Profile.
- ○ E: Excellent (Cell Center) -> Good -> Fair -> Poor (Cell Edge) -> Fair -> Good -> Excellent (Cell Center) ->, ...
Example 2 – Multi-Cells Scenario
Number of UE Groups – 5
- • NumUesinGroup in each group is 20% of NumUes.
- • Group A and B are configured as Stationary UEs located in Cell 1, each configured with different Radio Conditions.
- ○ A: Excellent (Cell Center)
- ○ B: Good
- • Group C and D are configured as Stationary UEs located in Cell 2, each configured with different Radio Conditions.
- ○ C: Fair
- ○ D: Poor (Cell Edge)
- • Group E is configured as Mobility UEs starting in Cell 1 and moving back and forth between Cell 2 and Cell 1.
- ○ E: Cell 1 Excellent (Cell Center) -> Cell 1 Good -> Cell 1 Fair -> Cell 1 Poor (Cell Edge) -> Cell 2 Poor (Cell Edge) -> Cell 2 Fair, Cell 2 Good, Cell 2 Excellent (Cell Center) -> Cell 2 Good ->, Cell 2 Fair -> Cell 2 Poor (Cell Edge) -> Cell 1 Poor (Cell Edge) ->, ...
|
-| 3b | Fading Model | TDL Channel Model | Specify the Fading model for all UE Groups with mobility simulated.
References can be made to 3GPP TS 38.141-2 Section J.2.1.
|
-| 4. UE Traffic Configuration | | | |
-| 4a | UE Traffic | UE Traffic Configuration Parameters
1..< NumUeGroups> | For each UE Group, specify - • UE Group Id
- • Number of Traffic Profiles in UE Group
- • Number of UEs in Each Traffic Profile
- • Traffic Patterns in Each Traffic Profile
- • Number of Traffic Types in Each Traffic Profile
|
-| | | > UE Group Id | |
-| | | > Number of Traffic Profiles in UE Group | |
-
-| Item No. | Parameters | Sub parameters | Comments / Justification |
-|----------|------------|-------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | 1.. | - List of Traffic Type(s) in Each Traffic Profile
|
-| | | >> Number of UEs in Traffic Profile | The following listed parameters are applicable if “Traffic Patterns in Traffic Profile” is defined as “Pre-defined”. |
-| | | >> Traffic Patterns in Traffic Profile | - Traffic Session Active Duration
- Traffic Session Idle Duration
|
-| | | >> Number of Traffic Types in Traffic Profile
1.. | For each of the UE Group specify |
-| | | >>> Traffic Type | - UE Group Id - unique number which identifies the UE Group within this Configuration Profile per defined in item 2(b).
- Number of Traffic Profiles in UE Group – specifies the number of traffic profiles to be configured for this UE group.
|
-| | | Applicable if “Traffic Patterns in Traffic Profile” is defined as “Pre-defined”.
>>> Traffic Session Active Duration | For each of the Traffic Profile in the UE Group specify |
-| | | Applicable if “Traffic Patterns in Traffic Profile” is defined as “Pre-defined”.
>>> Traffic Session Idle Duration | - Number of UEs in Each Traffic Profile – expressed either as absolute number of UEs or percentage of UEs within the specific Group (identified by the “UE Group Id”) which will be assigned to the specified “Traffic Profile”.
- Traffic Patterns in Each Traffic Profile – “Pre-defined” and “Randomized” options.
- Number of Traffic Types in Traffic Profile – specify the number of Traffic Type(s) to be configured as part of this Traffic Profile.
For each of the Traffic Type in the Traffic Profile specify
- Traffic Type which can be specified include
- Bi-Directional Full-buffer TCP / UDP data transmission (see clause 4.4) from the application server Sections 6.6.3, 6.6.4
- Uplink Full-buffer TCP / UDP data transmission
- Downlink Full-buffer TCP / UDP data transmission
- Voice Service – Voice over NR (VoNR) Section 7.5.1
- Video Service – Video over NR (ViNR) Section 7.8.1.
- Traffic Session Active Duration (seconds) defines when the UE(s) is/are active with the configured Traffic Type - Starting from the time when either the UE is registered to the network or when the last “Traffic Session Idle Duration” expired.
- Traffic Session Idle Duration (seconds) defines when the UE(s) is/are Idle - Starting from the time when the last “Traffic Session Active Duration” expired.
If more than one “Traffic Type” is defined in the “Traffic Profile”, each of the defined “Traffic Type” will be active in the 1st to last defined order.
Example – Traffic Profile defines
- Number of Traffic Types in Traffic Profile - 3
- (1): Traffic Type = VoNR; Traffic Session Active Duration = 90 seconds; Traffic Session Idle Duration = 15 seconds
- (2): Traffic Type = ViNR; Traffic Session Active Duration = 60 seconds; Traffic Session Idle Duration = 10 seconds
|
-
-| Item No. | Parameters | Sub parameters | Comments / Justification |
-|--------------------------------------------------|---------------|------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | | - • (3): Traffic Type = Downlink Full-buffer TCP; Traffic Session Active Duration = 30 seconds; Traffic Session Idle Duration = 5 seconds
After the UEs are registered to the network, VoNR traffic will be active for 90 seconds, idle for 15 seconds, ViNR traffic will be active for 60 seconds, idle for 10 seconds, TCP traffic will be active for 30 seconds, idle for 5 seconds, after which these UEs will continue these traffic patterns in the same sequence.
For UE sessions with “Traffic Type” specified for Bi-Directional Full-buffer UDP throughput test, the ratio between UL and DL traffic depends on the configured TDD DL:UL ratio.
For UE sessions with “Traffic Type” specified for TCP, the percentage of time when UE is transmitting TCP data in the uplink (UL) and receiving TCP data in the downlink (DL) when UE is receiving TCP data traffic transfer percentage are needing to be specified. e.g. UL is 25% and DL is 75% of the Call duration specified for TCP traffic transfer.
|
-| | | Applicable if “Traffic Patterns in Traffic Profile” is defined as “Randomized”.
> NumSequences | - • NumSequences – Number of pseudo random sequences: This variable can be set to define generate number of pseudo random sequences.
For a sample reference test scenario, see Annex B.
|
-| | | Applicable if “Traffic Patterns in Traffic Profile” is defined as “Randomized”.
> NumCycles | - • NumCycles: This variable can be set to determine how many cycles to test. It impacts the duration of the test.
For a sample reference test scenario, see Annex B.
|
-| | | Applicable if “Traffic Patterns in Traffic Profile” is defined as “Randomized”.
>>> P(UE Traffic) | - • P(UE Traffic) - Probability of UE Traffic: This variable can be set to assign probability of a specific traffic to be assigned in a cycle within a sequence.
For a sample reference test scenario, see Annex B.
|
-| | | Applicable if “Traffic Patterns in Traffic Profile” is defined as “Randomized”.
> Seed | - • Seed - Seed value for Pseudo random generation: This value can be used to allow for repeatability in the sequence generation.
For a sample reference test scenario, see Annex B.
|
-| 5. General Configuration | | | |
-| 5a | Test Duration | | Duration from the time when the test has started till when the test is stopped. |
-| 6. Applicable Measurements, KPIs and logs | | | |
-
-| Item No. | Parameters | Sub parameters | Comments / Justification |
-|----------|----------------------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------|
-| 6a | Applicable Measurements, KPIs and logs | | List of all applicable and relevant measurements, KPIs and log (list of “Item No.” from Table 10.3-1) that shall be collected. |
-
-Where applicable, references are made to existing parameters, measurements and KPIs which are already specified in this document.
-
-## 10.3 Measurements, KPIs and Logs
-
-Table 10.3-1 lists all the Measurements, KPIs and logs that can be collected.
-
-**Table 10.3-1: Measurements, KPIs and logs**
-
-| Item No. | Measurements/ KPIs | Comments / Justification |
-|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | Per Cell measurements/KPIs | Instructions
Provide minimum, maximum and average for: - all the users in the cell (1 measurement per KPI)
- per radio condition
for the duration of the test |
-| 1.1 | - RACH Success Rate, Attempts
- Registration Success Rate, Attempts
- Deregistration Success Rate, Attempts
| |
-| 1.2 | - Handover Success Rate, Attempts
| |
-| 1.3 | - SCell Addition Success Rate, Attempts
- SCell Release Success Rate, Attempts
| |
-| 1.4 | - Transmitted UL L1 Throughput [Mbps]
- Transmitted UL Application Throughput [Mbps]
- UL L1 Spectral Efficiency [bps/Hz]
| |
-| 1.5 | - Received DL L1 Throughput [Mbps]
- Received DL Application Throughput [Mbps]
- DL L1 Spectral Efficiency [bps/Hz]
| |
-| 1.6 | | |
-| 1.7 | | |
-| | Per UE Group measurements/KPIs
Per UE Group” and “Per User” Measurements, KPIs and Logs can be gathered from the Test UEs and/or UE Emulator | Instructions
Provide minimum, maximum and average for: - UE Groups per radio condition
for the duration of the test. |
-| 2.1 | | |
-| 2.2 | - PDSCH MCS
- PDSCH SINR [dB]
- PDSCH BLER [%]
- PDSCH MIMO rank
| |
-| 2.3 | - PUSCH transmit power [dBm]
- PUSCH MCS
- PUSCH BLER [%]
- PUSCH MIMO rank
| |
-| 2.4 | - Transmitted UL L1 Throughput [Mbps]
- Transmitted UL Application Throughput [Mbps]
| |
-| 2.5 | - Received DL L1 Throughput [Mbps]
- Received DL Application Throughput [Mbps]
| |
-| 2.4 | | |
-| 2.5 | | |
-
-## 10.4 Test Cases
-
-### 10.4.1 Single Cell
-
-#### 10.4.1.1 Test description and applicability
-
-The purpose of this test is to evaluate the performance of the SUT in a single cell scenario.
-
-#### 10.4.1.2 Test setup and configuration
-
-The test configuration (parameters and parameter values) is specified as part of the Test Profile (see Table 10.2-1) and shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a fading generator inserted between the antenna connectors (if available) of the O-RU and the UE or appropriately emulated using a UE emulator. It is recommended to use a UE emulator to properly distribute the UEs inside a cell according to selected distribution scenario. The minimum coupling loss (see clause 4.6) shall not be exceeded. The UEs shall be placed inside an RF shielded box or RF shielded room if the UEs are not connected via cables.
-
-#### 10.4.1.3 Test procedure
-
-- 1) The test setup is configured according to the Test Configuration Profile parameters values specified in Table 10.2-1. Configuration of the deployment environment is specified in Table 10.2-1 Item No. 1a and 1b. The test configuration shall be recorded in the test report. The serving cell under test is activated and unloaded. All other cells are turned off.
-- 2) The real or emulated UEs are
- - a) Configured according to the Number of UEs (NumUes) and Number of UE Groups (NumUeGroups) specified in Table 10.2-1 Item No. 2a and 2b respectively.
- - b) Placed inside a serving cell according to the UE distribution specified in Table 10.2-1 Item No. 2c and UEs placement specified in Table 10.2-1 Item No. 3a
- - c) Operating in the radio conditions as specified in Table 10.2-1 Item No. 3a including the specified mobility profile.
- - d) Applying fading models as specified in Table 10.2-1 Item No. 3b
- - e) Powered on and registered to the network as specified in Table 10.2-1 Item No. 2d
- - f) Performing services as specified in Table 10.2-1 Item No. 4a
-- 3) All the required performance data (including the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at the UEs, SUT and Application server using logging/measurement tools.
-- 4) The test is stopped after the test duration specified in Table 10.2-1 Item No. 5a.
-- 5) The capture of log data is stopped.
-
-#### 10.4.1.4 Test requirements (expected results)
-
-The following listed information shall be recorded and reported for assessment.
-
-- 1) Common minimum set of configuration parameters (see clause 4.3)
-- 2) Test Configuration Profile parameters and associated values applied for testing (listed in Table 10.2-1)
-- 3) The applicable and relevant Measurements, KPIs and logs as specified in Table 10.2-1 Item No. 6a
-
-### 10.4.2 Multiple Cells
-
-#### 10.4.2.1 Test description and applicability
-
-The purpose of this test is to evaluate the performance of the SUT in multiple cells scenario.
-
-#### 10.4.2.2 Test setup and configuration
-
-The test configuration (parameters and parameter values) is specified as part of the Test Profile (see Table 10.2-1) and shall be recorded in the test report.
-
-**Laboratory setup:** The radio conditions experienced by the UE can be modified using a fading generator inserted between the antenna connectors (if available) of the O-RU and the UE or appropriately emulated using a UE emulator. It is recommended to use a UE emulator to properly distribute the UEs inside cells according to selected distribution scenario. The minimum coupling loss (see clause 4.6) shall not be exceeded. The UEs shall be placed inside an RF shielded box or RF shielded room if the UEs are not connected via cables.
-
-#### 10.4.2.3 Test procedure
-
-- 1) The test setup is configured according to the Test Configuration Profile parameters values specified in Table 10.2-1. Configuration of the deployment environment is specified in Table 10.2-1 Item No. 1a, and 1b. The test configuration shall be recorded in the test report. The serving cells under test are activated and unloaded. All other cells are turned off.
-- 2) The real or emulated UEs are
- - a) Configured according to the Number of UEs (NumUes) and Number of UE Groups (NumUeGroups) specified in Table 10.2-1 Item No. 2a and 2b respectively.
- - b) Placed inside a serving cell according to the UE distribution specified in Table 10.2-1 Item No. 2c and UEs placement specified in Table 10.2-1 Item No. 3a.
- - c) Operating in the radio conditions as specified in Table 10.2-1 Item No. 3a including the specified mobility profile.
- - d) Applying fading models as specified in Table 10.2-1 Item No. 3b.
- - e) Powered on and registered to the network as specified in Table 10.2-1 Item No. 2d.
- - f) Performing services as specified in Table 10.2-1 Item No. 4a.
-- 3) All the required performance data (including the signalling and control data) as specified in the following “Test requirements” clause is measured and captured at the UEs, SUT and Application server using logging/measurement tools.
-- 4) The test is stopped after the test duration specified in Table 10.2-1 Item No. 5a.
-- 5) The capture of log data is stopped.
-
-#### 10.4.2.4 Test requirements (expected results)
-
-The following listed information shall be recorded and reported for assessment.
-
-- 1) Common minimum set of configuration parameters (see clause 4.3)
-- 2) Test Configuration Profile parameters and associated values applied for testing (listed in Table 10.2-1)
-- 3) The applicable and relevant Measurements, KPIs and logs as specified in Table 10.2-1 Item No. 6a
-
-# Annex A (normative): Template of test report
-
-The test report template provided in this annex is intended for general use in reporting E2E test results. This template is not intended for use in obtaining any O-RAN Certificate or O-RAN Badge. For more details on the process and procedures for use in seeking an O-RAN E2E Badge and for the test report templates to be used for this purpose, see [42].
-
-## A. GENERAL INFORMATION
-
-| | |
-|-----------------------------------------------------------------------|-----------------------|
-| A1 Name of test campaign | |
-| A2 Version of the report – reference ID | A3 Date(s) of testing |
-| A4 Contact person (tester) – incl. Name, Organization, E-mail address | |
-| A4 Test location (lab) – incl. the address | |
-| A5 Description of test campaign, summary of test results, conclusions | |
-
-List of tests - details of each test can be found in Clause E.
-
-| Test No. | Test name | Test status [ PASS / FAIL / - ] |
-|----------|-----------|---------------------------------|
-| 01 | | |
-| 02 | | |
-| 03 | | |
-
-## B. TEST AND MEASUREMENT EQUIPMENT AND TOOLS
-
-| # | Equipment or tool | Type | Manufacture | Version (HW/SW) | Notes# |
-|----|-------------------|------|-------------|-----------------|--------|
-| 01 | | | | | |
-| 02 | | | | | |
-| 03 | | | | | |
-
-# Specific details such as frequency range, date of last calibration, Type and version of Operating System at end-user device/application server, etc.
-
-## **C. SYSTEM UNDER TEST**
-
-| | |
-|------------------------------------------------------------|---------------------------------------------------------------|
-| C1 Total number of DUTs included in SUT | C2 Deployment architecture (indoor/outdoor, micro/pico/macro) |
-| C3 Deployment scenario – block diagram – connection scheme | |
-
-### **DUT 1#**
-
-| | | | | |
-|--------------------------------------------------------|------------------|---------------------------|--|--|
-| C3 Type | C4 Serial Number | C5 Supplier (manufacture) | | |
-| C6 SW version | C7 HW version | | | |
-| C8 Interface/IOT profile(s) if applied | | | | |
-| C9 Description incl. parameters, setting/configuration | | | | |
-
-# If SUT contains more DUTs, please copy the table.
-
-## **D. TEST CONFIGURATION**
-
-| Cell# 1 | | |
-|----------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------|
-| D1 Downlink/Uplink Carrier Frequency (MHz) and EARFCN/NR-ARFCN | D2 (Aggregated) Channel bandwidth (MHz) | D3 Transmission bandwidth configuration (number of Physical Resource Blocks) |
-| D4 Subcarrier spacing (SCS) | D5 Carrier prefix (CP) | D6 Duplex mode (FDD, TDD) |
-| TDD configuration parameters for 4G LTE | | |
-| D8 Uplink-downlink configuration | D9 Special subframe configuration | |
-
-| | | |
-|-------------------------------------------------------------------------|--------------------------------------------------------------------|----------------------------------------------------------------------|
-| | | |
-| TDD configuration parameters for 5G NR | | |
-| D10 slot configuration period (parameter dl-UL-TransmissionPeriodicity) | D11 number of slots with only downlink symbols (nrofDownlinkSlots) | D12 number of downlink symbols within the slot (nrofDownlinkSymbols) |
-| D13 number of slots with only uplink symbols (nrofUplinkSlots) | D14 number of uplink symbols within the slot (nrofUplinkSymbols) | |
-| SUT | UE | |
-| D15 Number of supported MIMO layers at SUT | D16 Number of supported MIMO layers at UE | |
-| D17 Antenna configuration - number of Tx/Rx at SUT | D18 Antenna configuration - number of Tx/Rx at UE | |
-| D19 Antenna gain at SUT | | |
-| D20 Transmit power at antenna connectors at SUT | | |
-
-#1 If the cells have different parameters, please copy the table.
-
-## **E. TEST RESULTS**
-
-| | |
-|-------------------------------------------------------------------------------------------------------------------------|------------------------------------|
-| E1 Test No. | E2 Test name |
-| E3 Date(s) of test execution | E4 Reference to test specification |
-| E5 Utilized test and measurement equipment and tools, incl. the specific setting/configuration – reference to Section B | |
-| E6 Test setup – connection/block diagram – deployment scenario (dense urban/urban/rural, LOS/NLOS/nLOS) | |
-| E7 Test procedure – describe differences in comparison with the test procedure defined in test spec. – limitations | |
-| E8 Test results – measured KPIs – incl. attachment of raw log file(s) | |
-
-| |
-|-----------------------------------------------------------------------------------------------------------------|
-| |
-| E9 Notes, incl. observed issues with the solutions |
-| E10 Conclusions – pass/fail – assessment of measured KPIs (in comparison with the expected KPIs) – gap analysis |
-
-# Annex B (informative): Example of Pseudo Random Sequence Generation for UE Activity
-
-This is a sample method to create a consistent and repeatable UE activity configuration test profile for a single O-RU. The goal is to create a traffic scenario that spans the test duration with a variety of UE activities that simulates a real-life traffic model.
-
-The use of pseudo random sequences to configure UE activities would make the test scenario appears random but is actually repeatable, thereby ensuring consistent results across test iterations or platforms.
-
-To generate the required pseudo random traffic sequences, Table 10.2-1 lists all the variables that need to be set at the time of the test execution.
-
-The sample reference test scenario consists of the following configuration:
-
-- NumUes = 500.
-- NumRadioConditions = 5.
- - Excellent
- - Good
- - Fair
- - Poor
- - Mobile – cycling between the first 4 radio conditions
-- NumSequences = 4.
-- NumUeGroups = 20.
-- Number of UEs per subgroup: $NumUes / NumUeGroups = 25$ .
-
-To evaluate the network performance under the test scenario conditions defined above, the UEs are required to run a sequence of operations. This sequence of operations is arranged as follows:
-
-- 1) Registration period for the UE.
-- 2) Wait time between registration and first UE activity.
-- 3) Multiple cycles [NumCycles] of UE traffic activity.
-- 4) Deregistration period for the UE.
-
-A pictorial depiction of this sequence is described in Figure B-1.
-
-
-
-Figure B-1: Example of UE sequence of operations. The diagram shows a horizontal sequence of colored boxes representing UE states: 'Reg' (pink), 'Wait' (orange), 'Cycle #1' (purple), 'Cycle #2' (purple), 'Cycle #3' (purple), followed by three dots, then 'Cycle #N' (purple), 'Wait' (orange), and 'DeReg' (pink).
-
-**Figure B-1. Example of UE sequence of operations.**
-
-Each cycle is composed of an activity that the UE performs followed by an Idle/Wait time. Each UE activity has a certain probability of occurring and a specific configuration.
-
-UE activities and Idle/Wait time configurations:
-
-- 1) Data traffic
- - P(Data) = 70%
- - UDP/TCP
- - Traffic Session Active = 90 seconds
- - Downlink = 75% of the session duration (67.5s)
- - Uplink = 25% of the session duration (22.5s).
-- 2) VoNR traffic
- - P(VoNR) = 20%
- - Traffic Session Active = 60 seconds
-- 3) ViNR traffic
- - P(ViNR) = 10%
- - Traffic Session Active = 60 seconds
-- 4) Idle/Wait time between UE activities:
- - Minimum Traffic Session Idle Duration = 2 seconds.
- - Maximum Traffic Session Idle Duration = 30 seconds.
- - Randomized: continuous uniform distribution
-
-The assignation of each activity for each UE at each cycle is determined randomly before the execution of the test. To help with consistency and repeatability between tests, the sequence generation shall accept seeds so that a sequence operation can be reproduced again.
-
-A sample method to generate the pseudo random activity sequence generation for each UE is as follows:
-
-- Set a registration period for each UE as the first activity, e.g. Registration Rate.
-- Generate a random number following a continuous uniform distribution with range of values [2, 30].
- - Assign the generated value as the duration of the Idle/Wait time duration.
- - Add this Idle/Wait time after the Registration of the UE is achieved.
-- If Traffic Patterns in Traffic Profile is set as Pre-defined, Select an initial value to determine the sequence of random numbers, e.g. Seed.
-- The use of any particular pseudo random number generator (PRNG) is not specified here as most common algorithms would produce the necessary uniform distribution sequences needed
-- For each UE traffic activity cycle:
- - Generate a random number following a continuous uniform distribution with range of values [1, 100]
-
-- If generated number is [1,70], assign UE traffic activity as Data
-- If generated number is [71,90], assign UE traffic activity as VoNR
-- If generated number is [91,100], assign UE traffic activity as ViNR
-- Generate a random number following a continuous uniform distribution with range of values [2, 30].
- - Assign the generated value as the duration of the Idle/Wait time duration.
- - Add this Idle/Wait time after the completion of the UE activity assigned for this cycle.
-- To achieve a target test duration (Test Duration) of approximately 2 hours, generate 100 UE traffic cycles [NumCycles = 100].
-- Set a deregistration period after the completion of the last cycle of the sequence.
-
-The resulting sample sequence of UE traffic activity is depicted on Figure B-2.
-
-
-
-Figure B-2: Example of a UE traffic activity sequence. The sequence shows a series of colored blocks representing different activities: Reg (Registration, pink), Wait (Idle/Wait, orange), ViNR (Voice over New Radio, purple), Data (Data traffic, blue), VoNR (Voice over NR, green), and DeReg (Deregistration, red). The sequence starts with Reg, followed by Wait, ViNR, Wait, Data, Wait, VoNR, Wait, then three dots indicating more cycles, then Wait, VoNR, Wait, and finally DeReg.
-
-**Figure B-2. Example of a UE traffic activity sequence**
-
-For the rest of the UEs, the same method to generate UE sequence of operation shall be followed with the conditions that:
-
-- Each UE under the same UE sequence shall use the same pseudo random activity sequence, e.g. the assigned traffic activities for each cycle are the same for all the UEs within the same sequence and radio condition.
-- Each UE under the same UE sequence shall have a different wait time between each activity. Each wait time can be generated using a number following a continuous uniform distribution with range of values [2, 30] in seconds.
-- At the beginning of the test, all 500 UEs follow a Registration Rate of 2 registrations per second.
-
-The combined test scenario created with the different pseudo random sequences coupled with a staggered sequence start time result in the overall UE traffic activity pattern for the test case as depicted on Figure B-3.
-
-
-
-Figure B-3: Example of UEs traffic activity sequences for the test case. This diagram shows the traffic activity sequences for multiple UEs over time. The UEs are grouped into three User Groups: User Group 20 (Mobility Pattern 4) containing UE #500 and UE #476; User Group 2 (Excellent Pattern 2) containing UE #50 and UE #26; and User Group 1 (Excellent Pattern 1) containing UE #25 and UE #1. Each UE's sequence is shown as a horizontal bar with colored blocks: Reg (pink), Wait (orange), Traffic (blue), and DeReg (red). The sequences are staggered in time. The x-axis is labeled 'Time' and has markers for 'Registration', 'Cycle 1', 'Cycle 2', 'Cycle 3', 'Cycle n', and 'Deregistration'.
-
-**Figure B-3. Example of UEs traffic activity sequences for the test case**
-
-# Annex C (informative): Change history/Change request (history)
-
-| Date | Revision | Description |
-|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 03/10/2021 | 01.00 | Initial version |
-| 07/18/2021 | 02.00 | Added some functional, performance, URLLC and mMTC services, and load and stress tests |
-| 03/31/2022 | 03.00 | New clause 9 with RIC-enabled use case tests.
New Traffic steering use case test |
-| 08/02/2022 | 04.00 | Added summary tables, alignment on report templates, minor corrections |
-| 11/17/2023 | 05.00 | Changes to comply with ODR in preparation for ETSI PAS
Removed Security Test clause and moved it to WG11 Security Test specification |
-| 03/22/2024 | 06.00 | Tests 5.12 and 5.13, update of terminology from “inter-RAT” to “inter-System” in accordance with referenced 3GPP 38.300 [44]
Tests 5.7 and 5.8, correction of Msg Flow and Expected results
New load and stress test 8.9 “MPS Call” added
New RIC-enable end-to-end use case test 9.3 “Network Energy Saving with Carrier and Cell switch off/on using Non-RT RIC” added |
-| 03/21/2025 | 07.00 | TS template alignment and 3GPP terminology alignment |
-| 07/18/2025 | 08.00 | New Clause 10 added (profile-based performance test), Annex A Test Report Template update to reflect profile-based performance testing, Updates to Clause 6.9, Clause 4.1.0 (core performance), Clauses 8.2 and 8.3, and other editorial updates. |
-| 11/26/2025 | 09.00 | Added new clauses 6.15 on User Plane Latency Tests and 8.10 Simultaneous RRC Connected UEs stability, updated 10.4 and added informative Annex B to include randomized traffic patterns, and various minor corrections. |
\ No newline at end of file
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/03703ee0fb20f67f19e3eb7c97a4b1e4_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/03703ee0fb20f67f19e3eb7c97a4b1e4_img.jpg
deleted file mode 100644
index de1cf94de2f35f7c00803a369e605384d3afe92d..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/03703ee0fb20f67f19e3eb7c97a4b1e4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3c981c6afbeccda6347b7e686a4065bf7d899ad150cb369e89a3c9a140c9ace7
-size 42075
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/068e6688fd646417399f8e6e50b85816_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/068e6688fd646417399f8e6e50b85816_img.jpg
deleted file mode 100644
index 6ffcb296db94b9ff609f4ba8b3637fe8551a2443..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/068e6688fd646417399f8e6e50b85816_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:36b2068e7ae8072b8837e26ed12712e8a6fb036fa690bbf04573880b6a1aa7b2
-size 9477
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/07bf92e869a2102e532783b036547f26_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/07bf92e869a2102e532783b036547f26_img.jpg
deleted file mode 100644
index 91675423603674220829bb169e0e60a322f35361..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/07bf92e869a2102e532783b036547f26_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:b5c91c7f5d5a8f9c3579891c0f5d47a427d178b72e5a0f999cc96fe842b0ca4e
-size 101081
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0b8f0df92a831a94cdac664d8b05f0ec_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0b8f0df92a831a94cdac664d8b05f0ec_img.jpg
deleted file mode 100644
index a7325598fdc7637d1f006d8e2cc7655d32b02237..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0b8f0df92a831a94cdac664d8b05f0ec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:7d09732c4b7133954716e92b2e18038d6c3489bc572781621a847b1453803fce
-size 41237
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg
deleted file mode 100644
index 0ad036ab3e4ef408a30da34f585645545350a446..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:78ed8ef1541d9e53ecc01f3baf14143aaef9a2657f0e776677c5780d8fb79b1e
-size 33026
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/10f4e3a2f3c016555ee12a5b556ba834_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/10f4e3a2f3c016555ee12a5b556ba834_img.jpg
deleted file mode 100644
index b1e37a4097d58caab495c9b8a99e20ee0ad8fbc6..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/10f4e3a2f3c016555ee12a5b556ba834_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:eb73f85193b7c24506aa0975f77a23c47f71f09fa2a1338cde2d9638688cd9ca
-size 68543
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/16d5f9c016e78737423c11d4fba9ae25_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/16d5f9c016e78737423c11d4fba9ae25_img.jpg
deleted file mode 100644
index 35063420eb78b0e9911980d6eaa831003b790c11..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/16d5f9c016e78737423c11d4fba9ae25_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:bb0a93d95d56df15c652dfc1db0af642cdeb0f38b4f762b771ddf7d697479746
-size 25277
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1baaba7a6e54e77197475726c871067d_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1baaba7a6e54e77197475726c871067d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1baf92180f2964741688e8215d7183da_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1baf92180f2964741688e8215d7183da_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1baf92180f2964741688e8215d7183da_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/22af211207188ebc64d7b60ca052b367_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/22af211207188ebc64d7b60ca052b367_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2427b810c52b62eddbd06f403f165ce7_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2427b810c52b62eddbd06f403f165ce7_img.jpg
deleted file mode 100644
index e7873a8439303e820965b76cd797b8b8952be914..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2427b810c52b62eddbd06f403f165ce7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:30becd0f86436f9d443c44b81677b702fa703d99cb3f8f6f325e00f6918afd9d
-size 27325
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg
deleted file mode 100644
index bfa0b60eb44c27817c2152756b8edec7bf09b9e6..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c4f41ba327b5909f57c1bdc7fe9aff4a4fbec7246138b583f63e865632c1c4b3
-size 4510
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg
deleted file mode 100644
index 17a7982f52f88776ec7b8badaca68d9a3d0fd737..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3a023edc65be85746c6b4a97c26710e43194aeb882db34c7e8d218d659299e72
-size 4523
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/29640f9496773db15b016e35bb17d5b8_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/29640f9496773db15b016e35bb17d5b8_img.jpg
deleted file mode 100644
index 5dc32ee2692a69bde43a752696fe1e421a2e2211..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/29640f9496773db15b016e35bb17d5b8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:fd9e98764336f3ce19c2227d229635551cb99a260bdc17ba6deabc35e6028de9
-size 11303
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2a185522b492253375ed16f0c515c230_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2a185522b492253375ed16f0c515c230_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2cdc3be3de33b97cdd52a0805b399419_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2cdc3be3de33b97cdd52a0805b399419_img.jpg
deleted file mode 100644
index ec3c314a93c62255d2fdde98f21914c551b1ecdb..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2cdc3be3de33b97cdd52a0805b399419_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:8ab34bd2acb03579ec992717a7b94dabf90ef7e1fa3c357cb6e0011b71c3ccf3
-size 51623
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2eea01382188b70064fa2818361d89f1_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/2eea01382188b70064fa2818361d89f1_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/318db222fae24a59c370fa6471d541b8_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/318db222fae24a59c370fa6471d541b8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/35437f160e157760713aa85be471c3f3_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/35437f160e157760713aa85be471c3f3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/37d5d6957e175201847002c556b5a29d_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/37d5d6957e175201847002c556b5a29d_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/37d5d6957e175201847002c556b5a29d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/3b89d812329a65ab156184a40524adf0_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/3b89d812329a65ab156184a40524adf0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/43b05bd1b6ee31fba18d3eb683903504_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/43b05bd1b6ee31fba18d3eb683903504_img.jpg
deleted file mode 100644
index 17b5c8c3efba4a43bfb6de1d0ce68bd8af877b29..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/43b05bd1b6ee31fba18d3eb683903504_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:b88f74be0f52fa4cd3d927ca856dcdc86dc27a4057be97ddbcea6411892120ef
-size 11450
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4a04896dfb569893fba50729314024f5_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4a04896dfb569893fba50729314024f5_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4c4a5bb88d303bdd784fcae1ddb08539_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4c4a5bb88d303bdd784fcae1ddb08539_img.jpg
deleted file mode 100644
index f25127125952beae6e7a02049e7b1554d64d49f4..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4c4a5bb88d303bdd784fcae1ddb08539_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4f7497cdf977f4686a59eecaafe7f443f5b4f24b7bba62dceb991e5fd0ce6203
-size 33499
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/5009e30a55479d3941af523871208f9d_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/5009e30a55479d3941af523871208f9d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg
deleted file mode 100644
index 41376671057aa7fa9f34e7ec2d3125aab9fc4848..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:fd0896eeaab08b6bf4a8ed8f7623a19ff0359fe94c02e6e018537ee45dbcb08b
-size 4554
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/568031aac86c633aab96b734dba3835e_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/568031aac86c633aab96b734dba3835e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/59368942873b0c35eef79a7a985025dc_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/59368942873b0c35eef79a7a985025dc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/5ae3023386ee15fae372871afce28865_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/5ae3023386ee15fae372871afce28865_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6588b1c7f14069d96744b473ad663248_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6588b1c7f14069d96744b473ad663248_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/66e89867f97592fd4bfab0e4f2b2054f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/66e89867f97592fd4bfab0e4f2b2054f_img.jpg
deleted file mode 100644
index ab6516c658decb5105d70d6018bdfd97062def74..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/66e89867f97592fd4bfab0e4f2b2054f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:6a75fdd361563880db899ee18b3fe3185cc395d3a7742a2d568d3f0ec6ccd7f9
-size 23073
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6b26e27af9601d90852f430c44907bad_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6b26e27af9601d90852f430c44907bad_img.jpg
deleted file mode 100644
index 0715e28335f8241157aafa5197d87806c97b1a1f..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6b26e27af9601d90852f430c44907bad_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:7e5aa41170a74519acfd094b485041ff1316c892efdc5a3efb82639c13c15f3f
-size 192089
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6ca05954842b17f14dfd52f26b9d43d2_img.jpg
deleted file mode 100644
index 7bf6dbb670227454ccd73163ad7fa2486b3f8e11..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6ca05954842b17f14dfd52f26b9d43d2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:44f4df6ba671d51e470c2cbc3a18e6cde3dad40d36d8c3bb84ba88b083e25d95
-size 36283
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
deleted file mode 100644
index 0e5b02a53ea60c1e67418a7b7184ac93fe8f038c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:936af21e44322d5197816c7da40db1bbb8b7a683881812dda70f4a3a5c4e8414
-size 4509
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/834fb96b114b8fdc001625e1ae28e8b1_img.jpg
deleted file mode 100644
index 0cb845d88613903d262536a7b3c3411cd2b3bd9d..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/834fb96b114b8fdc001625e1ae28e8b1_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:9d6a557101e3de16fcc5151b983542d7e37d41be48cca2ff867a00a80d54f823
-size 28253
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/854df8ad60507803253274673f9062cf_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/854df8ad60507803253274673f9062cf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8b4befaffc5166da571069410e207aea_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8b4befaffc5166da571069410e207aea_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg
deleted file mode 100644
index 41376671057aa7fa9f34e7ec2d3125aab9fc4848..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:fd0896eeaab08b6bf4a8ed8f7623a19ff0359fe94c02e6e018537ee45dbcb08b
-size 4554
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
deleted file mode 100644
index bfa0b60eb44c27817c2152756b8edec7bf09b9e6..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c4f41ba327b5909f57c1bdc7fe9aff4a4fbec7246138b583f63e865632c1c4b3
-size 4510
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg
deleted file mode 100644
index bfa0b60eb44c27817c2152756b8edec7bf09b9e6..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c4f41ba327b5909f57c1bdc7fe9aff4a4fbec7246138b583f63e865632c1c4b3
-size 4510
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg
deleted file mode 100644
index 41376671057aa7fa9f34e7ec2d3125aab9fc4848..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:fd0896eeaab08b6bf4a8ed8f7623a19ff0359fe94c02e6e018537ee45dbcb08b
-size 4554
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg
deleted file mode 100644
index cc68075c077fc452bcb293e8d204e7cdaeb124fa..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a5cfc41a8e8e65703471ac2b32706ffb0beb60b6c8fe75749e671e742d195167
-size 4595
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg
deleted file mode 100644
index 8bc522d8a8f253cef3b1ca1f088565d3e8b66403..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e717b71116eb9fb3c1ca00cdbc007f3b00cb09caeadffbcdcc18ec77bbf42df3
-size 22482
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg
deleted file mode 100644
index 95e845dff93accb1c60d4bf24b30168876ca71d3..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:bf28164ef278f410194af390e5788b9a326eb66247301d67ebe5a4d99294e61f
-size 110376
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a97518a839da75f8379c578562b01bc2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a97518a839da75f8379c578562b01bc2_img.jpg
deleted file mode 100644
index 277c4aded809ab8ab1cb7ecb5f06b088bde851e1..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a97518a839da75f8379c578562b01bc2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e41af4a56a00218eb3000ddb9bd69af9840a04e5b622770a26262478d638f079
-size 38825
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/aad0bf105da453377b319a03d9074beb_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/aad0bf105da453377b319a03d9074beb_img.jpg
deleted file mode 100644
index 16f27fc0f3af59716c032fd0f60893ded4f06ecc..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/aad0bf105da453377b319a03d9074beb_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:11be727a7a2689790aa6e5fc51efa81149cbbfcf27b4e37e30af592cc69c7dcc
-size 30442
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/aef4390a4629604196222b9ed006a786_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/aef4390a4629604196222b9ed006a786_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b2e5ca10383692a39c97d8b9929bcd6d_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b2e5ca10383692a39c97d8b9929bcd6d_img.jpg
deleted file mode 100644
index 6b8fe662d5d2d6442d237cf666deb5dcad64c25f..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b2e5ca10383692a39c97d8b9929bcd6d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:91c56fd60c6e42f7e2b477b0a737a12b4d4775fe7a80b254bb79ef9c61551f76
-size 85287
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/bb9f586190c7197099d25db7df9050af_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/bb9f586190c7197099d25db7df9050af_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
deleted file mode 100644
index d4e067ff04a2347855457ab49d06e669d9edb8cb..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c2fc2621e8206d24427b56bcb2398fc0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2af4f2eefd1d80b2d2383c4cb0cbfb480ace120a68b77a8bcb50353c05f6e18
-size 40643
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c68466afb0a12ea87dc7cf27b72fcd20_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c68466afb0a12ea87dc7cf27b72fcd20_img.jpg
deleted file mode 100644
index 969c2413126d89b355f21bf55ba62fb38a135e42..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/c68466afb0a12ea87dc7cf27b72fcd20_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4c83862b828ee8de46b7cbd65b2e0ac902c8284989efd21aeed5992b4e555e52
-size 35156
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg
deleted file mode 100644
index 125c52c3ec45a666b3edb42441e1073b2fb88647..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:57fd7f9d3355aa164c98502e750a4a18c130f839706ecf0265a3f0b5cdd9775e
-size 39963
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
deleted file mode 100644
index f744f58b703759b03eb6085368644ffde9db67a1..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:251c75ebaa835bbab9c3427c9013a663a1d3b3911d540f228bf695a23424403d
-size 53011
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg
deleted file mode 100644
index 2ead7e3a828de9dd11ffcc797586c57e5816307e..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a13870579104db3e12c848be0d567366ff9d2df8f8584a519348fefe02796d9b
-size 66954
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d35a80e3faed208324083399568c7461_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d35a80e3faed208324083399568c7461_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg
deleted file mode 100644
index bfa0b60eb44c27817c2152756b8edec7bf09b9e6..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c4f41ba327b5909f57c1bdc7fe9aff4a4fbec7246138b583f63e865632c1c4b3
-size 4510
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/df061c76cc6b43c8454b267631d4a585_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/df061c76cc6b43c8454b267631d4a585_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/df061c76cc6b43c8454b267631d4a585_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg
deleted file mode 100644
index ed38da39d84b1fa82fd5b140d4015c7b5660b439..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2866588046f7ff6d3a257895d93f31b4e7cdc6e946dcbaffb9b884e3ca2e37f9
-size 117312
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg
deleted file mode 100644
index 9fd6f512868cc356dbb3191c85f6297a83e355b2..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:8c30401e9c8ff8e679d645687562db57f11291ce1025f1e85e5f504b69de19d3
-size 38861
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg
deleted file mode 100644
index 0e5b02a53ea60c1e67418a7b7184ac93fe8f038c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:936af21e44322d5197816c7da40db1bbb8b7a683881812dda70f4a3a5c4e8414
-size 4509
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg
deleted file mode 100644
index f57b9023b656385f897dc1702ab8df73b8c09dc0..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:6d91f433c99630216d8e7ac6a9edf9c10bb1ba768c612ca7d9f3e791d06396c2
-size 22788
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f1fbb1287d999c7034742de35bdab836_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f1fbb1287d999c7034742de35bdab836_img.jpg
deleted file mode 100644
index 9fd363eec3161280346ebaf19de0dd331611d3fc..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f1fbb1287d999c7034742de35bdab836_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:b5f47101c543287cdf8736e6056b2fda354d7cbfc78e745fe43c0d11012de201
-size 28051
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f2ea0f64a770b22b902820457d262265_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f2ea0f64a770b22b902820457d262265_img.jpg
deleted file mode 100644
index a021242237ce8e9096d610f38831e427558bbd56..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f2ea0f64a770b22b902820457d262265_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2d208581ecb014d7aca9536b2dd8db95522514944b81d74a050b68f41bd716db
-size 28562
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f6442d68601dfecfe5f7f8a70449a2f7_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f6442d68601dfecfe5f7f8a70449a2f7_img.jpg
deleted file mode 100644
index 8c43ac21069f204c7201a4cd9cf5dd717419396a..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f6442d68601dfecfe5f7f8a70449a2f7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:f0ce47808e0c4bc265be79ae56c830067056591164d4543c708b11def359a2bf
-size 47894
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f74adaa1840504407cd4272995426f82_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f74adaa1840504407cd4272995426f82_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f9802d8871078af5421372727c628e2a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f9802d8871078af5421372727c628e2a_img.jpg
deleted file mode 100644
index 4821228607e10dc0797716c2214ed8ea6dc77c4d..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f9802d8871078af5421372727c628e2a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:52e2a27208c591203e2816c60e74976cf184651870ce2fd4494342706740c5b8
-size 48831
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg
deleted file mode 100644
index 5753f1b539c0b7a792a1f4764e5a828f5d17de6c..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3be4408d29304abcad7479f890a731655ff7beb6d9fa1a080df596537023234f
-size 4578
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/fac227c65a311c313325216dcf59591f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/fac227c65a311c313325216dcf59591f_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/fac227c65a311c313325216dcf59591f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/facce731b2dbfae43a8609231a700be1_img.jpg
deleted file mode 100644
index 3f5a3722bd47fe783f845042823d0471987b8eb8..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/facce731b2dbfae43a8609231a700be1_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:af8404ba7db84e45e2abab861eebd91f4e601aaaedd005d2ba5bfd638d0b41d4
-size 4552
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/fbee1b51966e04afd72119133d952535_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/fbee1b51966e04afd72119133d952535_img.jpg
deleted file mode 100644
index de50d0a0cf2bec473e4ab494e0aaeb92d4219783..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/fbee1b51966e04afd72119133d952535_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:670aedb94e8c2b1cac15a88c21c471ecd5d7ca775c0d54a923319ffde7def695
-size 4490
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
deleted file mode 100644
index 0baf79e98504beeb0d1d9ad4ea4ce6dcd4f09520..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:0b6be8920a743215027442c039fb9ff791908fe642d82488345ce87ca8702ef9
-size 4564
diff --git a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg
deleted file mode 100644
index 117758879a93028ce75b475d41f0ced252220fd5..0000000000000000000000000000000000000000
--- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a2a133c64b05db9aa6f76fe4a5b698fce7a93baf3af31e684f21a339b44757e6
-size 4489
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/doc.md b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/doc.md
deleted file mode 100644
index b5c1f89e8a00764787f8f666f8b4ab476ac5746d..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/doc.md
+++ /dev/null
@@ -1,1763 +0,0 @@
-
-
-# --- **O-RAN Work Group 1 (Use Cases and Overall Architecture)****Communication and Computing Integrated Networks**
-
-Copyright © 2026 by the O-RAN ALLIANCE e.V.
-
-The copying or incorporation into any other work of part or all of the material available in this document in any form without the prior written permission of O-RAN ALLIANCE e.V. is prohibited, save that you may print or download extracts of the material of this document for your personal use, or copy the material of this document for the purpose of sending to individual third parties for their information provided that you acknowledge O-RAN ALLIANCE as the source of the material and that you inform the third party that these conditions apply to them and that they must comply with them.
-
-O-RAN ALLIANCE e.V., Buschkauler Weg 27, 53347 Alfter, Germany
-Register of Associations, Bonn VR 11238, VAT ID DE321720189
-
-# Contents
-
-- Foreword..... 4
-- Modal verbs terminology ..... 4
-- 1 Scope ..... 5
-- 2 References ..... 5
- - 2.1 Normative references ..... 5
- - 2.2 Informative references ..... 5
-- 3 Definition of terms, symbols and abbreviations ..... 6
- - 3.1 Terms ..... 6
- - 3.2 Symbols ..... 6
- - 3.3 Abbreviations ..... 7
-- 4 General Concept..... 7
- - 4.1 The convergence of communication and computing in current industry landscape ..... 7
- - 4.1.1 Network Function Virtualization (NFV) in ETSI..... 7
- - 4.1.2 Multi-Access Edge Computing (MEC) in ETSI..... 8
- - 4.1.3 Edge Computing in 3GPP ..... 8
- - 4.1.4 Coordination of computing and networking in IMT-2020 and beyond in ITU-T ..... 8
- - 4.1.5 Computing aware traffic steering in IETF ..... 9
- - 4.2 Communication capabilities supported by O-RAN ..... 9
- - 4.3 Computing capabilities in O-RAN ..... 9
- - 4.4 The convergence of communication and computing in O-RAN ..... 10
-- 5 Scenarios and Use Cases..... 10
- - 5.1 Use Case 1: Multi aspect handover optimization ..... 10
- - 5.1.1 Background Information ..... 10
- - 5.1.2 Motivation ..... 11
- - 5.1.3 Proposed Solution ..... 12
- - 5.1.4 Benefits of O-RAN Architecture ..... 12
- - 5.2 Use Case 2: Radio Edge Computing Resource Information Exposure ..... 13
- - 5.2.1 Background Information ..... 13
- - 5.2.2 Motivation ..... 13
- - 5.2.3 Proposed Solution ..... 13
- - 5.2.4 Benefits of O-RAN Architecture ..... 15
- - 5.3 Use Case 3: O-RAN and Mobile Devices collaborative AI/ML inference ..... 15
- - 5.3.1 Background Information ..... 15
- - 5.3.2 Motivation ..... 16
- - 5.3.3 Proposed Solution #1 ..... 17
- - 5.3.4 Proposed Solution #2 ..... 18
- - 5.3.5 Benefits of O-RAN Architecture ..... 19
- - 5.4 Use Case 4: XR rendering collaboration ..... 19
- - 5.4.1 Background Information ..... 19
- - 5.4.2 Motivation ..... 20
- - 5.4.3 Proposed Solution ..... 22
- - 5.4.4 Benefits of O-RAN Architecture ..... 23
- - 5.5 Use Case 5: Computing Resource Scheduling in V2X Communications ..... 23
- - 5.5.1 Background Information ..... 23
- - 5.5.2 Motivation ..... 24
- - 5.5.3 Proposed Solution ..... 24
- - 5.5.4 Benefits of O-RAN Architecture ..... 25
- - 5.6 Use case 6: Exposure of performance information to assist computing resource scheduling ..... 25
- - 5.6.1 Background Information ..... 25
- - 5.6.2 Motivation ..... 26
- - 5.6.3 Proposed Solution ..... 26
- - 5.6.3.1 Performance information reporting triggers redeployment of a computing task ..... 26
- - 5.6.3.2 Performance information reporting triggers to scale a computing task ..... 30
- - 5.6.4 Benefits of O-RAN Architecture ..... 32
-- 6 Key Issues ..... 33
-
-- 6.1 Key Issue #1: Joint Communication and Computing Optimization.....33
-- 6.2 Key Issue #2: O-RAN computing service provision.....33
-- 6.3 Key Issue #3: O-RAN integrated communication and computing service provision..... 33
-- 6.4 Key Issue #4: Edge application orchestration in O-RAN..... 34
-- 7 Potential Solutions..... 34
- - 7.1 Solution #1: O1 configurations for multi-aspect handover optimization.....34
- - 7.1.1 Key Issue Mapping.....34
- - 7.1.2 Description.....34
- - 7.1.3 Procedures.....34
- - 7.1.4 Impacts on entities, services and interfaces.....36
- - 7.2 Solution #2: Computing information exposure via Y1 interface..... 37
- - 7.2.1 Key Issue Mapping.....37
- - 7.2.2 Description.....37
- - 7.2.3 Procedures.....37
- - 7.2.4 Impacts on entities, services and interfaces.....38
- - 7.3 Solution #3: Computing Service Provisioning.....38
- - 7.3.1 Key Issue Mapping.....38
- - 7.3.2 Description.....38
- - 7.3.3 Procedures.....38
- - 7.3.3.1 Computing service registration and discovery.....38
- - 7.3.3.2 Computing service consumption.....39
- - 7.3.4 Impacts on entities, services and interfaces.....41
- - 7.4 Solution #4: Integrated communication & computing service provisioning via SMO.....41
- - 7.4.1 Key Issue Mapping.....41
- - 7.4.2 Description.....41
- - 7.4.3 Procedures.....41
- - 7.4.4 Impacts on entities, services and interfaces.....43
- - 7.5 Solution #5: Edge application orchestration on O-Cloud via SMO.....43
- - 7.5.1 Key Issue Mapping.....43
- - 7.5.2 Description.....44
- - 7.5.3 Procedures.....44
- - 7.5.4 Impacts on entities, services and interfaces.....45
-- 8 Analysis on the Potential Architecture Impacts.....46
-- 9 Deployment Scenarios..... 46
- - 9.1 Scenario A: Local O-Cloud for private networks.....46
- - 9.2 Scenario B: Device Edge Cloud and local O-Cloud for private networks..... 47
- - 9.3 Scenario C: O-Cloud coordination with global orchestrator.....47
-- 10 Potential Requirements.....48
-- 11 Conclusion and Recommendations..... 48
-- Annex: Change history/Change request (history)..... 49**
-
-# Foreword
-
-This Technical Report (TR) has been produced by WG1 of the O-RAN ALLIANCE.
-
-The content of the present document is subject to continuing work within O-RAN and may change following formal O-RAN approval. Should the O-RAN ALLIANCE modify the contents of the present document, it will be re-released by O-RAN with an identifying change of version date and an increase in version number as follows:
-
-version xx.yy.zz
-
-where:
-
-- xx: the first digit-group is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have xx=01). Always 2 digits with leading zero if needed.
-- yy: the second digit-group is incremented when editorial only changes have been incorporated in the document. Always 2 digits with leading zero if needed.
-- zz: the third digit-group included only in working versions of the document indicating incremental changes during the editing process. External versions never include the third digit-group. Always 2 digits with leading zero if needed.
-
-## Modal verbs terminology
-
-In the present document "**shall**", "**shall not**", "**should**", "**should not**", "**may**", "**need not**", "**will**", "**will not**", "**can**" and "**cannot**" are to be interpreted as described in clause 3.2 of the O-RAN Drafting Rules (Verbal forms for the expression of provisions).
-
-"**must**" and "**must not**" are **NOT** allowed in O-RAN deliverables except when used in direct citation.
-
-# 1 Scope
-
-The present document provides a technical report for integrated communication and computing in O-RAN. The use cases are studied and potential requirements are identified.
-
-# 2 References
-
-## 2.1 Normative references
-
-Not applicable.
-
-## 2.2 Informative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are not necessary for the application of the present document, but they assist the user with regard to a particular subject area.
-
-- [i.1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
-- [i.2] Chih-Lin I, Guanding Yu, Shuangfeng Han, Geoffrey Ye Li, "Green and Software-defined Wireless Networks: From Theory to Practice", Cambridge University Press, 2019.
-- [i.3] ETSI White Paper No. 54, Evolving NFV towards the next decade, May, 2023.
-- [i.4] ETSI GS MEC 003: "Multi-access Edge Computing (MEC); Framework and Reference Architecture".
-- [i.5] ITU-T Y.IMT2020-CNC-req, Recommendation, Requirements of coordination of computing and networking for IMT-2020 and beyond.
-- [i.6] ITU-T Y.IMT2020-QoS-CNC-req, Recommendation, QoS assurance-related requirements and framework for coordination of computing and networking supported by IMT-2020 and beyond.
-- [i.7] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description".
-- [i.8] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
-- [i.9] 3GPP TS 23.501: "System architecture for the 5G System (5GS); Stage 2".
-- [i.10] 3GPP TS 28.538: "Management and orchestration; Edge Computing Management (ECM)".
-- [i.11] Draft-ietf-cats-usecases-requirements-00, Computing-Aware Traffic Steering (CATS) Problem Statement, Use Cases, and Requirements, July 2023.
-- [i.12] 3GPP TR 26.928: "Extended Reality (XR) in 5G"
-- [i.13] 3GPP TR 38.885: "Study on NR Vehicle-to-Everything (V2X)"
-- [i.14] O-RAN.WG1.TS.Use-Cases-Detailed-Specification: "Use Cases Detailed Specification".
-- [i.15] O-RAN.WG6.TS.CADS: "Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN".
-- [i.16] ITU-R, "Framework and overall objectives of the future development of imt for 2030 and beyond," Recommendation ITU, 2023.
-- [i.17] X. Zhou et al., "A surface defect detection framework for glass bottle bottom using visual attention model and wavelet transform," IEEE Trans. Ind. Informat., vol. 16, no. 4, pp. 2189–2201, Apr. 2020.
-
-- [i.18] J. Luo, Z. Yang, S. Li, and Y. Wu, "FPCB surface defect detection: A decoupled two-stage object detection framework," *IEEE Trans. Instrum. Meas.*, vol. 70, pp. 1–11, 2021.
-- [i.19] 3GPP TR 22.874: "Study on traffic characteristics and performance requirements for AI/ML model transfer in 5GS ;" Dec. 2021.
-- [i.20] N. Li, X. Li, Y. Yan, Q. Sun, Y. Han and K. Cheng, "Joint Communication and Computing Resource Optimization for Collaborative AI Inference in Mobile Networks," *2023 IEEE 98th Vehicular Technology Conference (VTC2023-Fall)*, Hong Kong, Hong Kong, 2023, pp. 1-5, doi: 10.1109/VTC2023-Fall60731.2023.10333702.
-- [i.21] Gapeyenko M, Petrov V, Paris S, et al. Standardization of Extended Reality (XR) over 5G and 5G-Advanced 3GPP New Radio[J]. *IEEE Network*, 2023, 37(4): 22-28.
-- [i.22] Huang Y, Li N, Sun Q, et al. Communication and Computing Integrated RAN: A New Paradigm Shift for Mobile Network[J]. *IEEE Network*, 2024.
-- [i.23] 3GPP TR 38.838: "Study on XR (Extended Reality) Evaluations for NR (Release 17)".
-- [i.24] 3GPP TR 22.261: "Service requirements for the 5G system; Stage 1".
-- [i.25] 3GPP TR 26.928: "Extended Reality (XR) in 5G".
-- [i.26] 3GPP TR 23.748: "Study on enhancement of support for Edge Computing in 5G Core network (5GC)".
-- [i.27] 3GPP TR 23.758: "Study on application architecture for enabling Edge Applications".
-- [i.28] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
-- [i.29] .
-- [i.30] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios", Mar. 2022.
-- [i.31] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "Non-RT RIC Architecture".
-- [i.32] O-RAN.WG1.TR.SMO-INT: "SMO Intents-driven Management".
-- [i.33] O-RAN.WG1.TR.Decoupled-SMO-Architecture: "Decoupled SMO Architecture".
-- [i.34] O-RAN.WG10.TS.OAM-Architecture: "Operations and Maintenance Architecture".
-- [i.35] ETSI GS NFV-IFA 011. Management and Orchestration; VNF Descriptor and Packaging Specification.
-- [i.36] ETSI GS NFV-IFA 008. Management and Orchestration; Ve-Vnfm reference point -Interface and Information Model Specification.
-- [i.37] O-RAN.WG3.TS.Y1TD, "Y1 interface: Type Definitions".
-- [i.38] O-RAN.WG3.TS.Y1GAP: "Y1 interface: General Aspects and Principles".
-- [i.39] O-RAN.WG6.TS.O-Cloud Notification API: "O-Cloud Notification API Specification for Event Consumers".
-- [i.40] O-RAN.WG6.TS.ORCH-USE-CASES: "Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN".
-
-# --- 3 Definition of terms, symbols and abbreviations
-
-## 3.1 Terms
-
-For the purposes of the present document, the terms given in 3GPP TR 21.905 [i.1] and O-RAN.WG1.TS.OAD [i.7] apply.
-
-## 3.2 Symbols
-
-For the purposes of the present document, the symbols given in 3GPP TR 21.905 [i.1] and O-RAN.WG1.TS.OAD [i.7] apply.
-
-## 3.3 Abbreviations
-
-For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [i.1], O-RAN.WG1.TS.OAD [i.7] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [i.1].
-
-| | |
-|-------------|-------------------------------------------------|
-| CCIN | Communication and Computing Integrated Networks |
-| MEC | Multi-Access Edge Computing |
-| NFV | Network Function Virtualization |
-| Near-RT RIC | Near-Real-Time RAN Intelligent Controller |
-| O-Cloud | O-RAN Cloud |
-| O-CU-CP | O-RAN Central Unit – Control Plane. |
-| O-CU-UP | O-RAN Central Unit – User Plane |
-| O-DU | O-RAN Distributed Unit |
-| XR | Extended Reality |
-
-# --- 4 General Concept
-
-## 4.1 The convergence of communication and computing in current industry landscape
-
-The past decades witnessed the convergence of communication and computing trends in mobile network. Great efforts were made and good momentum were achieved. C-RAN featured by centralization, cooperative, clean and cloud were first proposed in 2009, which depicts the vision of software based virtualized RAN [i.1]. The concept of Network Function Virtualization (NFV) was initiated from 2012. It introduced the information technology (IT) to enable the network transformation from the traditional physical hardware network into a new software based virtualized network [i.2]. This further steers up the pace for the convergence of communication and computing in RAN. Multiple-access edge computing (MEC), which enables compute-intensive applications for mobile devices and access to cloud computing service at the edge of communication networks, had attracted great attention [i.3]. The virtualized/cloudification RAN infrastructure can server as perfect edge computing platform. Thanks to the well-developed IT tools/frameworks, such as the containers, Kubernetes, the general-purpose hardware infrastructure could be easily and dynamically shared by the RAN functionality and the edge applications, providing the converged capabilities of mobile communication and computing. Edge computing was also incorporated into 5G system in 3GPP since Release 15. However, the communication and computing services offered by the existing design, such as NFV and MEC, were designed separately and developed independently. To fulfill the gap, the coordination of computing and networking is proposed in the context of IMT-2020 and beyond, and provides network enhancements based on the functional architecture of IMT-2020, to achieve the computing and network joint optimization based on the awareness, control and management over computing resources [i.4] [i.5]. Besides the above, IETF initiated a new working group on computing aware traffic steering to study how the network edge can steer traffic between clients of a service and sites offering the services, considering the integrated network and compute resource status [i.10]. This clause provides an overview of the related efforts in various standard developing organizations.
-
-### 4.1.1 Network Function Virtualization (NFV) in ETSI
-
-Network function virtualization is the one of the key pillars that accelerating the convergence of communication and computing in mobile networks. By adopting the cutting-edge IT technologies, the network functionalities are realized based on the general-purpose servers, which can be flexibly deployed on distributed cloud infrastructure. This revolutionized the way mobile communication networks are developed, deployed and operated. Series of NFV specifications are released by ETSI ISG NFV, from the concept, architecture, a set of interoperable implementation solutions, operational matters. Additional support for containerized VNFs and more cloud native deployment and automation are also specified in recent years. Regarding the further evolution, the requirements from telecom service providers, including: 1) unified network management; 2) user of latest cloud-native IT, automation and Artificial Intelligence (AI) open source software; 3) multi-vendor interoperability and migration among different nodes, are being considered as the key drivers [i.3].
-
-It is worth mentioning that the NFV work is more focusing on the network virtualization to offer the RAN services in IT manner with automation. It lays a good reference framework for RAN virtualization. But the dedicated requirements for RAN virtualization are not fully considered. This is further studied and specified in O-RAN. How computing services would be extended and how to provide the integrated communication and computing services based on the telecom cloud infrastructure for the both computing and communication intensive emerging services, such as metaverse, XR and AI, are not investigated.
-
-### 4.1.2 Multi-Access Edge Computing (MEC) in ETSI
-
-ETSI Industry Specifications Group (ISG) MEC defines the specifications relevant to the edge computing, where the specification is access agnostic and is not confined to mobile communications. ETSI ISG MEC specifies an open and standardized IT service environment that enables application to be deployed at the network edge close to edge user [i.4]. A common edge application enablement framework for multiple network technologies is developed with MEC service APIs. More specifically, network related service APIs are specified to provide added value to the edge application enabling the network aware service optimization. For example, radio network information (3GPP access), WLAN information, UE identity service APIs, V2X information service, etc., are specified. The MEC service APIs mostly focus on the how the MEC applications can be enabled and the orchestration and management of the MEC platform and the application. How the network would interact with the MEC functionalities and how the information required for network related service APIs can be obtained from the network is not fully investigated. To fill the gap, Y1 interfaces is introduced in O-RAN so that MEC can obtain the RAN analytics information via the Y1 interface [i.7]. However, the joint consideration of the edge service continuity and the communication service continuity, the unified orchestration and management of the mobile network and edge computing required for the operators are not yet investigated.
-
-In summary, MEC as another key pillar of the convergence of communication and computing, are now separately designed, deployed and operated on top of the mobile network. Thus, the dynamic coordination of the mobile network and application processing is not supported to ensure the end-to-end service QoS.
-
-### 4.1.3 Edge Computing in 3GPP
-
-3GPP edge computing work defines the 5G access specific interactions and interfaces as a complement part of the ETSI MEC work. The overall framework generally consists of five layers, i.e., application layer, edge enabler layer, edge hosting environment, edge management layer and 3GPP transport layer [i.8]. 3GPP develops specifications for the edge enabler layer, 3GPP transport layer, edge management layer, and some part of application layer (relevant to enabling of edge capabilities to the applications).
-
-In the transport layer, 5G supports to select/reselect user plane functions to steer/route traffic locally and connect to the local area data network in selected regions. It also supports Edge Application Server Discovery Function (EADSF), which enables the discovery of the IP address(es) of the EASs for the edge application [i.9].
-
-Regarding the management layer, different business roles involved in edge computing and the mobile network, and their relationship are also discussed along with the edge computing management specification [i.10]. Generally, PLMN operator is responsible for the 3GPP transport layer and deployment of the 5G network functions, edge computing service provider (ECSP) is responsible for the deployment of edge data network that contain edge enabler client (EEC) in the UE and edge enabler server (EES), and application service provider (ASP) is responsible for the creation of edge application servers (EASs) and application clients (ACs). The management system framework for edge computing defined in 3GPP consists of the PLMN management system and the ECSP management system. The two systems can interact with ETSI Network Function Virtualization Management and Orchestration (MANO) to perform lifecycle management functions.
-
-The edge enabler layer provides edge capability related Application Programming Interfaces (APIs) for the application developers [i.8]. With the well-defined services and APIs, the application developers can locate and connect to the most suitable edge application server, and to explore the service optimization leveraging the potential network information provided by underlying 3GPP network.
-
-Similar to the MEC work in ETSI, the joint optimization of network and computing resources are not yet considered to guarantee the end-to-end service quality that depends on both the computing and communication process.
-
-### 4.1.4 Coordination of computing and networking in IMT-2020 and beyond in ITU-T
-
-The requirements, framework and QoS assurance related requirement and framework for the coordination of computing and networking in IMT-2020 and beyond are studied in ITU-T [i.5] [i.6]. The coordination of computing and networking is defined as the coordination of utilization, control and management of computing, storage and networking resources. It provides the capability to jointly schedule the computing, storage and networking resources, and is expected to enhance the QoS support for IMT-2020 networks and beyond. The coordination of computing and networking is envisioned for the resource layer, control layer, service layer, and management and orchestration layer.
-
-The general requirements identified in the draft recommendations [i.5] includes: awareness of networking, computing and storage resources; joint scheduling of resources; unified management of resources; AI/ML integration; unified standard
-
-interfaces for resources; support resource transaction services so that the resource users can order computing services; energy saving and security and privacy related requirements.
-
-The high level QoS assurance mechanisms investigated for the coordination of computing and networking in IMT-2020 and beyond in [i.6] includes:
-
-- Perception of computing and networking status
-- Perception of service requirements
-- Mapping among service, computing and network requirements
-- Joint scheduling of computing and networking
-- Unified management and orchestration of computing and networking
-
-### 4.1.5 Computing aware traffic steering in IETF
-
-IETF initiated computing aware traffic steering working group in Mar. 2023. The main motivation is to study how to integrate both network and compute conditions in the optimization function that informs the steering applied by the network edge nodes with the desire to operate that function on nodes within the service provider's network, logically separated from service operation. The main motivation is the performance experienced by clients will depend on both network metrics such as bandwidth and latency, and compute metrics such as processing, storage capabilities, and capacity. For some services, especially, the XR and autonomous vehicles assisted by the network, it is desired to optimize network edge node traffic steering based on the awareness of both the communication and computing related metrics.
-
-The use cases and requirements for the computing aware traffic steering are studied in [i.11]. Four typical use cases, namely, computing-aware AR/VR, computing-aware intelligent transportation, computing-aware digital twin and computing-aware SD-WAN are discussed considering a distributed computing scenario. The requirements to support computing aware traffic steering are also identified:
-
-- Support dynamic and effective selection among multiple service instances
-- Support agreement on metric representation of both the compute capability related metrics and network metrics
-- Support flexible use of network and computing metrics for service instance selection
-- Support session and service continuity
-- Preserve communication confidentiality.
-
-## 4.2 Communication capabilities supported by O-RAN
-
-O-RAN is committed to evolving radio access networks with its core principles being intelligence and openness. The overall O-RAN architecture is specified in [i.7], where the key elements including the service management and orchestration framework, O-RAN network functions and O-Cloud are described. In general, the O-RAN architecture supports the 4G and 5G RAN communication services. With the hierarchical RAN intelligent controllers, namely Non-RIC and Near-RT RIC introduced in O-RAN, various AI/ML empowered RAN optimization use cases are explored in [i.14], offering improved RAN performance, user experiences, network resource utilization efficiency and energy efficiency.
-
-## 4.3 Computing capabilities in O-RAN
-
-Diversified 5G services call for new level of agility in RAN deployment and scaling. RAN cloudification emerges as a promising solution and offers innovation paradigm. O-RAN architecture adopts the RAN cloudification design. O-Cloud is defined as a cloud computing platform comprising a collection of physical infrastructure nodes that meet O-RAN requirements to host the relevant O-RAN NFs (i.e., Near-RT RIC, O-CU-CP, O-CU-UP, and O-DU) [i.7].
-
-O-Cloud platform hardware includes compute, network and storage components and may also include hardware accelerators for improving the computing efficiency by offloading the most computation-intensive or timing-intensive tasks in the radio protocol stack. O-Cloud platform software consists of cloud platform runtime, cloud platform management and virtual machine (VM)/container management and orchestration. The cloud platform runtime includes the hypervisor/container runtime, accelerator driver, network driver and precision time protocol to host the RAN functions. The cloud platform management is responsible for the life cycle management, high availability, fault management and configuration of the cloud infrastructure.
-
-The VM/container management and orchestration are typically implemented with OpenStack for VM deployments and Kubernetes (K8s) for container deployment. The cloud architecture and deployments scenarios for O-RAN virtualized RAN are described in [i.15].
-
-The cloudification in O-RAN greatly improves the RAN deployment flexibility, and transforms O-RAN into a native and cost-effective edge computing platform. Thus, edge application services can be deployed on the existing O-Cloud infrastructure along with the O-RAN functions. This lays the foundation of "beyond communication" service provision, offering the opportunities for RAN to provide the integrated communication and computing services.
-
-## 4.4 The convergence of communication and computing in O-RAN
-
-The CCIN is a network which could provide not only traditional RAN services such as connection and mobility control but also applications services by leveraging the communication and computing resources in an integrated manner. The goal of CCIN is to provide the beyond-connection services and bring new values to operators. A CCIN network has the following features.
-
-1. Sharable resources. Resources include not only the communication resources such as the radio bearers, the TTL, the frequency etc. but also those of computing resources including various hardware from CPU, GPU to switches, storage and so on. Thanks to the cloud technology, such resources could be scheduled and allocated for different usage, i.e. communication and computing on demand. For example, in the daytime, the computing power of the CPU should be used to process the radio stack for 5G coverage. While at night when the traffic volume drops, the CPU is then freed from the 5G computing and changed for AI model training.
-2. Holistic orchestration of communication and computing resources. The resources of CCIN should be scheduled and orchestrated in a holistic way. The CCIN itself should be capable of scheduling and allocating the communication and computing resources for different workloads. In addition, the CCIN should also be able to expose such resources and status to external in collaboration with the other network functions, e.g. core networks. A global orchestrator should be aware of the resources, orchestrate them together with the functions and services in a holistic way to optimize the system performance, efficiency and/or user experience.
-3. Integrated service provisioning. The CCIN could provide services externally and the services could be of different types. It could be in the very basic format of computing capability in the unit of Floating-point Operation Per Second (FLOP). It could be further provided in a more abstract yet user-sensible way. For example, the services could be the capability of training certain type of AI models with certain number of parameters. Eventually, such service provisioning would bring the beyond-connection value to operators.
-
-NOTE: If and how O-RAN addresses this topic of integrated service provisioning is for further study.
-
-In essence, CCIN features the integration of communication and computing. There could be several levels of integration. On the first level, the computing functions simply co-locate with the communication functions on the same hardware platform, i.e. the COTS servers. There is little interaction in between except that the user-plane local break-out by means of User-plane Function (UPF) could be implemented for local processing. On the second level, interaction between the communication and application services is enabled to provide RAN and application mutually aware optimization. On this level, the interaction is mainly via an established interface or Application Program Interface (API). For the third and the last level of integration in CCIN, the communication and computing relate to each other in a symbiotic way, i.e., they are jointly scheduled in a real-time way, managed and orchestrated in a holistic manner. With the orchestrator, the computing resources could be scaled in and out in a much more dynamic way with smaller granularity as the workload changes with the applications than the second level.
-
-# --- 5 Scenarios and Use Cases
-
-## 5.1 Use Case 1: Multi aspect handover optimization
-
-### 5.1.1 Background Information
-
-Communication and Computing Integrated Networks enables the collaboration of communication network and computing. It is an approach of softening the boundaries between the cloud computing and networking, such that their resources can be utilized in the most efficient way. This allows the applications to leverage on such convergence of compute and network resources. Cloud based RAN solutions can play an important role in the Communication and Computing Integrated Networks with its potential to share some of its vacant computing resources as the edge computing platform. New age applications based on XR
-
-(see 3GPP TR 26.928 [i.12], clause 4.1.1), V2X (see 3GPP TR 38.885 [i.13]) can benefit from Communication and Computing Integrated Networks but they require application mobility in addition to posing stringent requirements on both communication and computing. New network architecture for Communication and Computing Integrated Networks needs to address these application requirements.
-
-The types of computing resources required for different applications can be diverse based on the nature of the applications. However, the computing resources available in different entities might be of different computing resource type than what is required for specific applications. It is also possible that capabilities of a computing resource type required for specific applications is different even if an entity supports required computing resource type. Computing resource types referred here could be but not limited to the support for Graphical Processing Unit, Neural Processing Unit, Deep Processing Unit, etc. An example illustration of the cloud based joint RAN + Computing entity used in Communication and Computing Integrated Networks (CCIN) is given below in the Figure 5.1.1-1.
-
-
-
-Figure 5.1.1-1: Example illustration of cloud based joint RAN + Computing entity. The diagram shows three user equipment (UE) icons at the top, each connected to a central cloud-based RAN entity via a radio tower icon. Inside the cloud, there are two stacked boxes labeled 'O-CU' and 'O-DU'. To the right of these is a yellow box labeled 'apps' and 'MEC'. Below these components is a horizontal bar with labels 'NPU', 'DPU', 'GPU', and '...'. A dashed line connects the 'apps' and 'MEC' box to a text box on the right that reads: 'Cloud Resources in a RAN deployment that could be shared with other computing applications'.
-
-**Figure 5.1.1-1: Example illustration of cloud based joint RAN + Computing entity.**
-
-### 5.1.2 Motivation
-
-In a Communication and Computing Integrated Networks, the idea is to use the vacant computing resources from the cloud-based RAN (e.g., if the network load is low), to perform some edge computing related tasks so that cloud resources are used efficiently. In particular, leveraging the proximity of the cloud-based RAN entities to the end users/devices is a key factor to address low latency requirements of the tasks/applications. But in order to take advantage of this opportunity the following needs to be considered:
-
-- If the vacant resources match the task requirements in terms of the type of the computing resource and related capabilities.
-- If the amount of vacant resources of required type/capability suffices the task requirements
-- If the nodes are within the proximity required to support the continuity of the service and service latency requirements of the applications.
-
-In the use case of UE handover especially in the scenario where the UE needs to run applications with high computing and low latency requirements such as XR based applications the above stated challenges are more prominent. Thus, in such use case it is desirable that system considers the aspects of computing capability and availability of cloud-based RAN entities while supporting the mobility of UE and applications in it.
-
-In particular, it is important to create the awareness in a cloud-based RAN entity of the information regarding the computing capability and availability of other cloud-based RAN entities in the proximity and use these multiple aspects as part of the UE handover decisions. Proximity here means that coverage area of the cells served by source cloud-based RAN entity has some overlap with the coverage area of the cells served by target cloud-based RAN entity.
-
-
-
-Figure 5.1.2-1: Example illustration of multi aspect handover. The diagram shows a central Blue Node 1 with a red 'XR' label, surrounded by four other nodes: Yellow Node 3, Green Node 4, Pink Node 2, and Blue Node 1. Each node is represented by a colored cloud containing icons for a GPU and a CPU. The nodes are interconnected by lines, and a red arrow points from the central Blue Node 1 to the Green Node 4.
-
-Figure 5.1.2-1: Example illustration of multi aspect handover
-
-### 5.1.3 Proposed Solution
-
-In order to address aforementioned use case and related challenges it is proposed extend the Communication and Computing Integrated Networks framework. Such extensions comprise introduction of proximal computing table which stores the information on the compute capabilities of cloud-based RAN entities and its usage in UE handover decisions. This helps the handover of the UE to a target cloud-based RAN entity in the proximity with computing resource types of relevant capabilities and availability required for the applications in that UE. The proximal computing table can be of following types:
-
-1. Proximal Computing Capability Table which is a neighbor relation table indicative of computing resource types and/or capability of compute resource types of the target cloud-based RAN entities in the proximity of the source cloud-based Radio entity. Examples for resource types referred here are GPU, NPU, DPU, AI accelerator, etc. Examples for the capability of resource types referred here are supported types of AI algorithms, supported number of Ray Tracing Cores, etc.
-2. Proximal Computing Availability Table which is a neighbor relation table indicative of current availability of computing resource types of the target cloud-based RAN entities in the proximity of the source cloud-based RAN entity. This may comprise a predicted availability of the computing resource types for predetermined time periods.
-
-Proposed solution consists of rApp, SMO/Non-RT RIC Framework, Near-RT RIC, E2 nodes and O-Cloud. rApp retrieves CM data, PM data, location data of different cloud-based RAN entities and capability of computing resource types, load/availability of computing resource types in different cloud-based RAN entities. rApp derives Proximal Computing Capability Table for each cloud-based RAN entity based on the proximity analysis of different cloud-based RAN entities in the neighborhood and the capability analysis of computing resource types in different cloud-based RAN entities within the proximity. Proximity analysis uses different data including but not limited to PM data and location data. Similarly, rApp derives Proximal Computing Availability table for a cloud-based RAN entity based on the load/availability analysis of the computing resource types in different target entities in the corresponding Proximal Computing Capability table. rApp may rely on AI/ML model-based load/availability pattern analysis of the computing resource types, this includes prediction of available vacant resources at specific time window in a specific day e.g., during which time window it is expected to have the most vacant resources, with which confidence that can be determined and exposed etc.
-
-rApp creates different O1 based configurations including policies for multi-aspect handover optimization based on the Proximal Computing Capability Table and Availability Table at one or more near-RT RIC instances. Near-RT RIC will then use E2 control or E2 policy to ensure the UE handover to most optimum target cloud-based Radio entity.
-
-### 5.1.4 Benefits of O-RAN Architecture
-
-O-RAN architecture allows rApp based use cases to build intelligence based on both traditional RAN network data available over O1 interface as well as cloud-based computing capability data available over O2 interface. In addition, E2 control or E2 policies facilitates the finer control of UE level handover decisions in E2 nodes. In summary, O-RAN architecture provides necessary ingredients to facilitate multi aspect handover optimization.
-
-## 5.2 Use Case 2: Radio Edge Computing Resource Information Exposure
-
-### 5.2.1 Background Information
-
-AI/ML processing for network intelligence and automation evolution, as well as new 5G edge applications supporting e.g., immersive Virtual Reality (VR), autonomous driving, and intelligent internet of things (IoT), etc. put an unprecedented demand on the edge computing resources. The O-Cloud architecture of O-RAN and the spatial and temporal tidal effects of RAN communication services offer great opportunities for sharing underutilized computing resources in the RAN infrastructure. This helps to improve the resource utilization efficiency and reduce operators' investment on the edge computing infrastructure.
-
-### 5.2.2 Motivation
-
-The main objective is to provide radio edge computing resource information exposure service based on O-RAN architecture and its open interface. In O-RAN, SMO is a great candidate to provide radio edge computing resource information exposure service to the service consumers for perceiving unused computing resources in the O-Cloud infrastructure. The service consumers might be other orchestrators, e.g., central cloud orchestrator, edge cloud orchestrator, radio edge cloud orchestrator, device edge cloud orchestrator etc. The orchestrators could request computing resource information for multi-cloud collaboration, such as task migration between multiple clouds or edge intelligence. The service consumers could also be other 3rd applications, e.g., vertical customers, VR consumers etc., which could request computing resource information for application deployment using shared computing resources in a secured way.
-
-### 5.2.3 Proposed Solution
-
-Entities/resources involved in the use case:
-
-- 1) SMO:
- - a) Support collects and analysis computing related resources from O-Cloud.
- - b) Support provides radio edge computing resource information service, send the radio computing information for managed O-Cloud related computing resources to the service consumer, e.g., Orchestrator/Application Server.
-- 2) O-Cloud:
- - a) Support computing related inventory and updated resources report with required granularity to SMO over O2 interface.
-- 3) Radio Edge Computing Resource Information Exposure Service Consumer:
- - a) Request/subscribe radio edge computing resource information from SMO.
- - b) The service consumer might be Orchestrator/Application Server.
-
-The whole procedure is presented in Table 5.2.3-1, illustrated by Figure. 5.2.3-1.
-
-**Table 5.2.3-1: Radio Edge Computing Resource Information Exposure**
-
-| Use Case Step | Description of the Step |
-|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Goal | Radio Edge Computing Resource Information Exposure |
-| Actors and Roles | SMO, O-Cloud, orchestrator/application server |
-| Assumptions | - - All relevant functions and components are instantiated.
- - O2 interface connectivity is established with SMO.
|
-| Pre-conditions | - - SMO and O-Cloud are instantiated with O2 interface connectivity being established between them.
Editor's Note: Security related procedure is FFS. |
-| Begins when | Orchestrators or application servers want to request/subscribe Radio Edge Computing Resource information. |
-| Step 1 (M) | Orchestrators or application servers, e.g., RAN service computing center, send Radio Edge Computing Resource information request to SMO for initial or updated computing resource information. |
-| Step 2 (M) | SMO requests or subscribes the measurement data from O-Cloud, and receives computing related resources information from O-Cloud through response or periodic notifications. |
-| Step 3 (O) | Alternatively, SMO could use AI/ML or other methods to perform computing related resource data statistics and analysis. |
-| Step 4 (M) | SMO send Radio Edge Computing Resource information response, including the RAN side computing related information managed by SMO. |
-| Ends when | Orchestrators or application servers get the response. |
-| Post Conditions | N/A |
-
-```
-
-@startuml
-Skin rose
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-Box "Service Consumer" #lightcyan
- Participant "Orchestrator/Application Server" as app
-End box
-Box "Service Management and Orchestration" #gold
- Participant "SMO" as smo
-End box
-Box "O-Cloud Platform" #lightseagreen
- Participant ims as "IMS/DMS"
-End box
-
-app -> smo : 1 Radio Edge Computing Resource Information Request
-smo -> ims: 2.1 <> Data Collection Request/Subscribe
-ims -> smo: 2.2 <> Data Collection Response/Notify
-smo -> smo: 3 Data analysis
-smo -> app: 4 Radio Edge Computing Resource Information Response
-@enduml
-
-```
-
-
-
-```
-
-sequenceDiagram
- participant Service Consumer as Service Consumer
- participant Service Management and Orchestration as Service Management and Orchestration
- participant O-Cloud Platform as O-Cloud Platform
- Note left of Service Consumer: Orchestrator/Application Server
- Note right of Service Management and Orchestration: SMO
- Note right of O-Cloud Platform: IMS/DMS
- Service Consumer->>Service Management and Orchestration: 1 Radio Edge Computing Resource Information Request
- Service Management and Orchestration->>O-Cloud Platform: 2.1 <> Data Collection Request/Subscribe
- O-Cloud Platform-->>Service Management and Orchestration: 2.2 <> Data Collection Response/Notify
- Service Management and Orchestration->>Service Management and Orchestration: 3 Data analysis
- Service Management and Orchestration-->>Service Consumer: 4 Radio Edge Computing Resource Information Response
- Note left of Service Consumer: Orchestrator/Application Server
- Note right of Service Management and Orchestration: SMO
- Note right of O-Cloud Platform: IMS/DMS
-
-```
-
-Sequence diagram illustrating the Radio Edge Computing Resource Information Exposure process. It shows three lifelines: Service Consumer (Orchestrator/Application Server), Service Management and Orchestration (SMO), and O-Cloud Platform (IMS/DMS). The sequence of messages is: 1. Request from Service Consumer to SMO; 2.1. Data Collection Request/Subscribe from SMO to IMS/DMS; 2.2. Data Collection Response/Notify from IMS/DMS to SMO; 3. Data analysis within SMO; 4. Response from SMO to Service Consumer.
-
-**Figure 5.2.3- 1: Radio Edge Computing Resource Information Exposure**
-
-Required data:
-
-Computing related resource data are expected to be retrieved by SMO from O-Cloud for radio computing related data statistics, analysis and information exposure, including total, allocated, reserved, and available:
-
-- 1) CPU number for O-Cloud, cluster, or node
-- 2) vCPU number for O-Cloud, cluster, or node
-
-Exposed data:
-
-- 1) Radio Edge Computing Resource information exposed by SMO includes but is not limited to,
-- 2) Total capacity of computing or number of computing resources
-- 3) Allocated capacity of computing or number of computing resources
-- 4) Reserved capacity of computing or number of computing resources
-- 5) Available capacity of computing or number of computing resources
-- 6) Other computing related information
- - a) Computing resource identifier, e.g., Cloud identifier, Node identifier
- - b) Computing resource location,
- - c) vCPU number, etc.
-
-### 5.2.4 Benefits of O-RAN Architecture
-
-The proposed solution supports an effective way to expose the radio edge computing resource information to the service consumer, such as other orchestrators or applications. It requires features provided by the O-RAN architecture to collect the radio computing related data, alternatively supports statistics, analysis, and expose by SMO.
-
-## 5.3 Use Case 3: O-RAN and Mobile Devices collaborative AI/ML inference
-
-### 5.3.1 Background Information
-
-Integrated artificial intelligence (AI) and communication has been identified as crucial elements for IMT-2030 by ITU-R [i.16]. AI/ML-based applications are increasingly demanding in terms of computation, memory, and power consumption. However, mobile devices typically have limited energy, computing capability, and memory resources, making it challenging to run complete AI/ML inference. There is a growing need to offload AI/ML inference from mobile devices to the central cloud or edge computing platform to support the mobile AI/ML inference application through collaborative computing.
-
-For example, [i.17] and [i.18] give a manufacturing scenario that utilizes AI/ML technologies for analyzing image data in a product defect detection application. The product's image is initially captured by a sensor such as a camera and then it can be transmitted to the edge server equipped with an AI/ML model for identifying and classifying the potential defects in the product by analyzing the image data. Subsequently, the inference result is communicated to the console's actuator (e.g. a classifier), which directs the product to different processes based on the result. The AI/ML model can also be split between the mobile devices and the edge computing platform considering the radio transmission status and the mobile devices' computing capabilities. In several use cases of split AI/ML operation between AI/ML endpoints studied in 3GPP TR22.874 [i.19], the AI/ML endpoints at the end user side can be mobile devices, robotics, cameras, etc., and the AI/ML endpoints on the network side can be AI/ML edge servers, cloud servers, application servers, etc. When the performance of the AI/ML inference task decreases (e.g., the inference end-to-end latency increases and/or the inference accuracy decreases), service experience downgrades, or mobile device's computing capability cannot support current AI/ML inference computation, the AI/ML model split point between the AI/ML endpoints and the AI/ML exit point can be dynamically optimized by adjusting the computing workload of the AI/ML endpoints and the communication volume between AI/ML endpoints to ensure service quality. Taking ResNet18 as an example, Figure 5.3.1-1 shows the framework of the AI/ML model [i.20] and Table 5.3.1-1 shows data size of the intermediate outcomes and computation load for the split point inference of the ResNet18 model. The data size of AI/ML model intermediate outcomes need to be transmitted from mobile device to network side, computation load offloaded as well as the accuracy of the various AI/ML exit point are summarized in the following table.
-
-
-
-Diagram of the multi-branch ResNet-18 model architecture. It shows a vertical flow of layers starting from 'Image' input through '18 layers ResNet', '7\*7 conv, 64, /2', and 'maxpool, /2'. The main path continues with several '3\*3 conv' blocks. Three exit points are shown: 'Exit 1' branches off after the first '3\*3 conv, 64' block (with preceding '1\*1 conv, 128, /2'), 'Exit 2' branches off after the first '3\*3 conv, 256' block (with preceding '1\*1 conv, 256, /2'), and 'Exit 3' branches off after the first '3\*3 conv, 512' block (with preceding '1\*1 conv, 512, /2'). Each exit point consists of 'conv', 'conv', and 'FC' layers. The main path concludes with 'avgpool' and 'FC(512, 1000)' leading to 'softmax'.
-
-Figure 5.3.1-1: The framework of the multi-branch ResNet-18 model
-
-Table 5.3.1-1 Data size and computation load of ResNet18
-
-| Layer ID | Type | Data size (bit) | Computation load (FLOPs) | Accuracy of exit point |
-|------------|----------|-----------------|--------------------------|------------------------|
-| 1 | conv1 | 25690112 | 118013952 | |
-| | maxpool | 6422528 | 7225344 | |
-| 2 | conv2-1 | 6422528 | 115605504 | |
-| 3 | conv2-2 | 6422528 | 115605504 | |
-| 4 | conv2-3 | 6422528 | 115605504 | |
-| 5 (Exit1) | conv2-4 | 6422528 | 115605504 | 63.91% |
-| 6 | conv3-1 | 3211264 | 57802752 | |
-| 7 | conv3-2 | 3211264 | 115605504 | |
-| 8 | conv3-3 | 3211264 | 115605504 | |
-| 9 (Exit2) | conv3-4 | 3211264 | 115605504 | 65.36% |
-| 10 | conv4-1 | 1605632 | 57802752 | |
-| 11 | conv4-2 | 1605632 | 115605504 | |
-| 12 | conv4-3 | 1605632 | 115605504 | |
-| 13 (Exit3) | conv4-4 | 1605632 | 115605504 | 67.64% |
-| 14 | conv5-1 | 802816 | 57802752 | |
-| 15 | conv5-2 | 802816 | 115605504 | |
-| 16 | conv5-3 | 802816 | 115605504 | |
-| 17 | conv5-4 | 802816 | 115605504 | |
-| | avg pool | 16384 | 1229312 | |
-| 18 (Exit4) | fc | 32000 | 1023000 | 68.96% |
-
-### 5.3.2 Motivation
-
-The performance of the application AI/ML inference can be evaluated by two primary metrics: end-to-end application AI/ML inference latency and inference accuracy. The end-to-end latency in collaborative AI inference involving mobile devices and cloud/edge server generally comprises four key components: the inference computation latency on the mobile device, the transmission latency for AI/ML model intermediate outcomes from the mobile devices to the network, the inference computing latency within the edge/cloud server, and the transmission latency for the inference outcomes from the network to the mobile device. Figure 5.3.2-1 illustrates the end-to-end inference latency for collaborative AI inference between mobile devices and
-
-edge/cloud server, with the total inference latency represented as the sum of T1, T2, T3, and T4. The end-to-end latency of collaborative AI/ML inference is subject to multiple determinants. Latency T1 is influenced by both the complexity of the AI/ML model deployed on the mobile device and the device's computing capability. It is worth noting that the AI/ML model inference accuracy usually increases with the AI/ML model complexity. Latency T2 depends on the data size of the AI/ML model intermediate outputs, the radio interface and backhaul connection conditions. Latency T3 is contingent upon the complexity of the AI/ML model deployed on the edge/cloud server and the computing capability of the server. Meanwhile, latency T4 hinges on the data size of the inference result, the radio interface and backhaul connection conditions. The above analysis of the impact on latency T1~T4 indicates that the end-to-end latency of collaborative AI inference highly depends on both the communication and computational capabilities of the mobile device and the network. To assure the end-to-end collaborative AI inference performance, the joint communication and computing resources optimization is desired.
-
-The objective of this use case is to investigate how O-RAN architecture could be leveraged to support the collaborative AI/ML inference between the mobile device and the network.
-
-
-
-Diagram of AI/ML collaborative inference between mobile device and edge/cloud server. The diagram shows a mobile device on the left with 'Model layer 1 to 10 are computed at mobile device' and 'computing latency: T1'. An 'Input' is processed through a neural network icon. An arrow labeled 'AI/ML model intermediate outcomes transmission latency: T2' points to the right. On the right, an 'edge/cloud server' has 'Model layer 11 to output are computed at edge/cloud server' and 'computing latency: T3'. It produces an 'Inference result'. An arrow labeled 'AI inference result transmission latency: T4' points back to the mobile device. Below the devices, an O-RAN architecture stack is shown: O-CU/O-DU, xApp, RIC, and RAN Edge Application (e.g., UPF) on top of a Hypervisor(VM/Container) and Infrastructure. Mobile devices (phone, robot, car, laptop) are connected to the O-RAN base station. A note states 'NOTE: the CN is out of O-RAN scope'.
-
-**Figure 5.3.2-1: The AI/ML collaborative inference between mobile device and edge/cloud server**
-
-### 5.3.3 Proposed Solution #1
-
-O-RAN could provide both the edge computing capabilities and the communication assurance for the collaborative AI inference scenarios. This also helps to facilitate the joint communication and computing resource optimization to ensure the end-to-end performance.
-
-Firstly, in O-RAN system, O-Cloud infrastructure can provide high-quality computing resources for mobile device and network AI/ML collaborative inference. Idle O-Cloud resources can be leveraged to the deploy the AI/ML application. Compared with the collaborative AI inference between mobile device and central cloud server, AI/ML collaborative inference between mobile devices and O-Cloud is beneficial for reducing the transmission latency of AI/ML model intermediate outcomes and inference result. This also helps to potentially reduce the cost required for additional edge/cloud server deployment. To efficiently utilize the O-Cloud computing capabilities for the edge AI/ML applications, SMO could serve as an intermediary interface that translates external communication and computing requests into O-RAN internal operations. In detail, SMO could expose the computing services or integrated communication and computing services offered by O-RAN to the external entities or consumers so that external customers are able to convey their communication requirements and computing requirements. For example, in the AI/ML inference request, requirements such as computing resource requirements for AI/ML applications, end-to-end inference latency and accuracy requirements, service duration, and the number of served mobile devices, etc., could be provided to the SMO. With the service request input, SMO can orchestrate communication and computing resources to fulfill the service requirements. To enable the deployment of the edge applications (e.g., AI/ML application) on the O-Cloud from the external request, a new edge application orchestrator, i.e., RAN Edge Application Orchestrator (REAO), responsible for the edge application life cycle management, can be introduced in SMO or the existing mechanism could be reused. It can further consume the O-Cloud Deployment Management Service (DMS) to execute the deployment operation on O-Cloud.
-
-Secondly, Non-RT RIC and Near-RT RIC can further enable the intelligent service assurance and network performance improvement. These capabilities can be applied to collaborative AI inference, facilitating the joint communication and computing resources optimization. For example, Non-RT RIC may predict the trajectory of mobile devices, then proactively
-
-optimize communication resources at the target BS and assist to deploy AI/ML applications in advance at the target O-Cloud, etc. Near-RT RIC is capable to gather detailed information at both the UE level and the cell level. With these data and the policies received from Non-RT RIC, Near-RT RIC can help to assure the communication performance in near real-time for AI/ML inference application.
-
-Furthermore, O-RAN can provide RAN information including communication and computing information to network side AI/ML endpoints (which could be deployed at O-Cloud, edge or cloud servers). For example, Near-RT RIC can expose mobile device throughput, network congestion condition, radio interface latency, available computing resources, etc. via Y1 interface. This information can be used by the application to optimize the AI/ML model split and exit decisions in adaptation to the network connection conditions and computing status (e.g., mobile devices' computing capabilities, power status, etc.). The optimized decision from application may be further notified to mobile devices and SMO and enforced by them.
-
-Figure 5.3.3-1 shows how O-RAN support the collaborative AI inference application, such as industrial quality inspection, in the production line scenario.
-
-
-
-Diagram of AI/ML collaborative inference between mobile device and O-RAN. The diagram shows an 'External consumer' (e.g., Production Control Center) at the top, an 'SMO' (Service Management and Orchestration) block in the middle containing 'Non-RT RIC', and an 'O-Cloud' block at the bottom containing 'CU/DU', 'RAN', and 'Near RT RIC'. Below the O-Cloud are several mobile devices. Arrows indicate the flow of information: 1. Y1: communication and computing information exposure from O-Cloud to External consumer. 2. Communication and computing service request from External consumer to SMO. 3.a and 3.b: AI/ML application split part deployment (split part 1 at layers 1-10 on the device, split part 2 at layer 11-output on the O-Cloud). 4. A1: service assurance policy from SMO to O-Cloud. 5. E2: mobile device information collection from O-Cloud to devices. A note states 'NOTE: the CN is out of O-RAN scope'.
-
-Figure 5.3.3-1: The AI/ML collaborative inference between mobile device and O-RAN
-
-### 5.3.4 Proposed Solution #2
-
-This solution aims to incorporate comprehensive management of CCIN consumers' AI/ML inference applications, specifically regarding the life-cycle management of collaborative AI/ML inference tasks by SMO.
-
-To enable O-RAN to dynamically select an AI/ML model partitioning and exit point that is suitable for the current communication and computing resource condition, and to deploy the selected AI/ML model, CCIN consumers could provide SMO with a set of certain types of AI/ML models at possible partitioning and exit points. This allows the SMO to ascertain the uplink bandwidth and computing resource requirements of the AI/ML models within the set, thereby enabling the selection of partitioning of AI/ML models based on deployment strategies generated by the Non-RT RIC.
-
-Additionally, CCIN consumers could provide performance requirements for the AI/ML collaborative inference task, such as end-to-end latency of AI/ML inference, the area required to be covered, etc. This enables the Non-RT RIC to generate AI/ML model deployment strategies that comply with these performance metrics based on the status of communication and computing resources.
-
-Since mobile device and O-Cloud AI/ML collaborative inference involves not only adjustments to the AI/ML models deployed on the O-Cloud side but also adjustments on the mobile device side, the AI/ML models deployed on mobile device are always intended to compute collaboratively with those on O-Cloud. If the O-Cloud deploys AI/ML inference model from the (n+1)-th
-
-layer to the output layer, then the mobile device side needs to deploy the AI/ML model for layers 1 to (n). Consequently, O-RAN needs to communicate the decision on the O-Cloud side AI/ML model selection to CCIN consumers, enabling them to inform the mobile device side about the AI/ML model that need to be deployed.
-
-Figure 5.3.4-1 illustrates an example of O-RAN implementing AI/ML collaborative inference computing task between mobile device and O-Cloud. Herein, CCIN consumers notify the SMO of the AI/ML models (For instance, a set of AI/ML models that categorized with different AI/ML model partitioning and exit points.) and the performance requirements for the mobile device and O-Cloud AI/ML collaborative inference (such as end-to-end latency of AI/ML inference, the area desired to be covered, etc.) through the consumption of CCIN service. The Non-RT RIC, based on current communication and computational resources, generates AI/ML model deployment strategy and notifies the CCIN consumers. CCIN consumers then complete the deployment of AI/ML model on the mobile device side, while the SMO (for example, REAO within the SMO that deploys edge applications) completes the deployment of AI/ML model on O-Cloud. By monitoring of the AI/ML collaborative computing task, the Non-RT RIC can collect the communication status of the mobile device from the Near-RT RIC and generate AI/ML model adjustment strategy based on the current communication and computing status of the mobile device and the O-Cloud. The AI/ML model adjustment strategies are also communicated to CCIN consumers to update the AI/ML model on the mobile device side.
-
-
-
-Diagram of AI/ML inference application selection and deployment performed by O-RAN. The diagram shows interactions between an External consumer (e.g., Production Control Center), SMO (Non-RT RIC), O-Cloud (CU/DU, CN, Near RT RIC), and mobile devices. The process involves: 1. Communication and computing capability exposure from SMO to consumer; 2. Service request from consumer to SMO; 3.a. AI/ML model split part 1 deployment to devices; 3.b. AI/ML model split part 2 selection and deployment to O-Cloud; 4. Service assurance policy from SMO to O-Cloud; 5. Mobile device information collection from O-Cloud to SMO. A note indicates the CN is out of O-RAN scope.
-
-Figure 5.3.4-1: AI/ML inference application selection and deployment performed by O-RAN
-
-### 5.3.5 Benefits of O-RAN Architecture
-
-The O-RAN system presents several advantages in the collaborative AI/ML inference scenario. First, the idle computing resources of O-Cloud can be shared with AI/ML inference applications. Furthermore, Non-RT RIC and Near-RT RIC empowers joint communication and computing resources optimization to ensure the collaborative AI/ML inference end-to-end latency and accuracy performance.
-
-## 5.4 Use Case 4: XR rendering collaboration
-
-### 5.4.1 Background Information
-
-As a disruptive technology that brings new interactive experience, eXtended Reality (XR) has attracted considerable attention from content providers, mobile network operators, vertical industry customers, and so on. By design, a unique feature of XR is a new device form factor replacing or complementing handheld smartphones with wearable head-mounted displays or smart glasses. New devices (i.e., glasses or head mounted displays) impose strict requirements on user equipment (UE) power
-
-consumption, performance, and heat dissipation. Consequently, XR devices cannot do all the computations (i.e., Figure 5.4.1-1(1)) but require assistance from other nodes [i.21].
-
-XR applications often require high-quality visuals and real-time interactions, which can be demanding in terms of latency and bandwidth requirements. Figure 5.4.1-1 illustrates the collaboration between different types of computing nodes and XR devices, where blue lines represent communication latency and orange lines represent the processing in computing nodes. On the one hand, RAN computing, brings rendering and computing service closer to users, allowing for ultra-low communication latency and reliability assurance for XR applications. On the other hand, RAN computing capability is weaker than cloud computing, which may cause the larger computing delay [i.22]. In order to provide users with immersive experience and ensure real-time interaction, the delay of interaction must be small enough, which puts forward new requirements for both radio network and computing resources.
-
-
-
-Figure 5.4.1-1: Collaboration between different types of computing nodes and XR devices. The diagram shows four scenarios (1-4) illustrating the flow of data and processing between XR devices, RAN computing, Edge Computing, and Center Cloud Computing. A top blue arrow indicates 'Increased communication latency' from left to right. A bottom orange arrow indicates 'Strengthened computing capability' from left to right. Scenario (1) shows only XR devices. Scenario (2) shows XR devices connected to RAN computing. Scenario (3) shows XR devices connected to RAN computing, which is connected to Edge Computing. Scenario (4) shows XR devices connected to RAN computing, which is connected to Edge Computing, which is connected to Center Cloud Computing.
-
-**Figure 5.4.1-1: Collaboration between different types of computing nodes and XR devices**
-
-3GPP TR 38.838 [i.23] defines the evaluation methodology for XR studies in Release-17, including the modeling of XR applications, simulation scenarios, traffic models, KPIs, and simulation parameters. 3GPP TR 22.261 [i.24] defines the Cloud/Edge/Split Rendering as an additional high data rate and low latency service and provides corresponding requirements on the 5G system. In addition to the conversational service category, Interactive (Streaming), Passive Streaming, Download, and Split Compute/Rendering are identified as new delivery categories in 3GPP TR 26.928 [i.25], which also introduces different distributed computing architectures for XR. 3GPP TR 23.748 [i.26] defines the necessary modifications to 5G system architecture to enhance Edge Computing. Specifically, this study is investigating mechanisms to discover connectivity to available Edge Computing resources (e.g. using DNS), mobility improvements for both UE consuming Edge Computing services and for Edge Application Servers, and for network capability exposure towards the Edge Application Server. In addition, in 3GPP TR 23.758 [i.27] and 3GPP TS 23.558 [i.28] a new set of application layer interfaces for Edge Computing are identified that may potentially be useful for integration of Edge Computing. Specifically, the interfaces will enable application-layer discovery of Edge Application Servers, capability exposure towards the Edge Application Server, and procedures for onboarding, registration, and lifecycle management of Edge Applications.
-
-### 5.4.2 Motivation
-
-Figure 5.4.2-1 shows the XR rendering collaboration between RAN and XR devices. In this type of service, the terminal collects holographic information such as the user’s geographic location, orientation, manipulation, and five-senses through sensors. With the help of a high-speed and stable radio network, the information is transmitted to the RAN edge computing platform and the cloud through the uplink. Then, the RAN edge or cloud rendering server invokes computing resources to render the screen in real time, and the processed holographic information will be transmitted to the user’s terminal device through the downlink after being encoded and compressed. Finally, the terminal device restores the above information to the user.
-
-
-
-Diagram showing XR device sending holographic information to RAN computing, which then sends processed holographic information back. A 'processing' loop is shown on the RAN computing side.
-
-**Figure 5.4.2-1: XR rendering collaboration between RAN and XR devices**
-
-However, there are two major limitations with existing computation offloading approaches.
-
-Firstly, there is a lack of alignment between communication and computing decisions. Although computing is brought closer to the RAN, the existing architecture still manages communication and computing separately, resulting in sub-optimal performance. 3GPP TR 22.261 [i.22] defines motion-to-photon latency in the range of 7ms to 15ms while maintaining the required resolution of up to 8k giving user data rate of up to 1Gbit/s. Assuming the service requirements for motion-to-photon latency is 10ms, three RAN computing nodes with different bandwidth load and computing load can be chosen as the server, as shown in Figure 5.4.2-2. If choosing the computing node based on the best computing delay it will be the node 1, the E2E delay is 13ms. If choosing the computing node based on the best communication latency it will be the node 2, the E2E delay is 14ms. If choosing the computing node based on both of the status it will be the node 3, the E2E delay is 10ms and meets the service requirements. To ensure E2E delay without resource wastage of both radio network and computing resources, it is essential to align the decisions of communication and computing.
-
-
-
-| Node | Communication Delay (ms) | Computing Delay (ms) | Total E2E Delay (ms) |
-|------|--------------------------|----------------------|----------------------|
-| 1 | 9 | 4 | 13 |
-| 2 | 4 | 10 | 14 |
-| 3 | 5 | 5 | 10 |
-
-Figure 5.4.2-2: Comparison of three RAN computing nodes. Node 1: 9ms communication, 4ms computing, total 13ms. Node 2: 4ms communication, 10ms computing, total 14ms. Node 3: 5ms communication, 5ms computing, total 10ms. Each node has a bar chart showing its communication (blue) and computing (orange) load.
-
-**Figure 5.4.2-2: RAN computing nodes with different bandwidth load and computing load**
-
-Secondly, there is a lack of united orchestration among multiple users in adapting to resource-limited edge environments. An adaptive design focusing on a single-user offloading pipeline can be duplicated for multiple users, but this can lead to poor resource efficiency. Figure 5.4.2-3 shows the situation that XR devices are associated with the closest BS. Without united orchestration among multiple users, some RAN nodes may become overloaded while others are underutilized, resulting in inefficient resource allocation. To address this issue, it is necessary to coordinate the decisions of multiple users holistically.
-
-NOTE: Without specification, the "resource" mentioned above refers to the available communication and computing capabilities within RAN.
-
-
-
-Figure 5.4.2-3: Lack of united orchestration among multiple users in adapting to resource-limited edge environments. The diagram shows two scenarios. The top scenario, labeled 'heavy load', shows a central 'RAN computing' node connected to three 'XR device' units. A bar chart next to the RAN node shows a high level of 'communication' (blue) and 'computing' (orange) resources being used. The bottom scenario, labeled 'Normal load', shows a similar setup but with a lower level of resource usage in the bar chart. The legend indicates that blue represents 'communication' and orange represents 'computing'.
-
-**Figure 5.4.2-3: Lack of united orchestration among multiple users in adapting to resource-limited edge environments**
-
-Therefore, a joint design approach is required for computing node selection, computing resource allocation, and radio resource optimization. Leveraging modern AI technologies, computational tasks or resources can be automatically scheduled and orchestrated along with the optimization of communication resources. This integrated approach enables more efficient utilization of computing resources, thereby reducing wastage in redundant hardware capital expenditures (CAPEX) and operating expenses (OPEX).
-
-### 5.4.3 Proposed Solution
-
-As shown in Figure 5.4.3-1, XR rendering collaboration over SMO consists of the following steps:
-
-- 0) Application awareness: External consumer collects the XR service requirements and application status from the XR devices and XR edge applications.
-- 1) Capability exposure: communication and computing capabilities within RAN are exposed by SMO (1a) or via Y1 (1b) interface to external consumer. For example, levels of E2E delay can be provided for XR rendering tasks.
-- 2) Analysis and decision for service request: external consumer analyzes the XR service requirements and the capabilities within RAN, and then determines the service request for capabilities in O-RAN.
-- 3) Service request: external consumer requests communication and computing service in O-RAN.
-- 4) Optimization and decision analysis: potentially utilize AI/ML models to analyze the service request and determine the resource demand and policy for XR rendering assurance in O-RAN.
-- 5) Execution:
- - 5a) Deploy or scale the cloud resources of E2 nodes (i.e., O-CU, O-DU) via O2 interface.
- - 5b) Reconfigure the E2 nodes via the O1 interface to guarantee radio transmission for XR rendering (e.g., cell-level spectrum allocation).
- - 5c) Create A1 policy for XR rendering assurance.
- - 5d) Deploy or scale the cloud resources of XR edge applications on the O-Cloud platform.
- - 5e) (Out of O-RAN scope) Deploy XR applications on UE or notify UE the default XR edge application and/or the default communication node.
-
-NOTE1: Step 5a. to 5d. can be freely combined or skipped to guarantee the XR rendering assurance, depending on the specific requirements of the XR service.
-
-NOTE2: External consumers could be global orchestrator or the edge enabler server in 3GPP [i.28].
-
-
-
-Figure 5.4.3-1: XR rendering collaboration over SMO. This diagram illustrates the interaction between various O-RAN components for XR rendering. At the top, the Service management & Orchestration Framework (SMO) contains a Non-RT RIC with '4. Optimization and decision analysis'. It connects to an External consumer via '1a. Capability exposure' and '3. Service request'. The External consumer performs '2. Analysis and decision for service request' and sends '5e. Execution on UE' to XR devices. Below the SMO is the Near-RT RIC, which contains 'E2 control/ policy for XR rendering assurance'. It connects to the O-Cloud via 'O1' and 'A1' interfaces. The Near-RT RIC also connects to E2 Nodes via 'E2' and 'Y1' interfaces. The E2 Nodes provide 'E2 report for XR application' and receive '5a. Deploy or scale the E2 nodes', '5b. Reconfigure the E2 nodes', and '5c. A1 Policy for XR rendering assurance' from the SMO. The Near-RT RIC also connects to XR edge Applications\* via '1b. Capability exposure'. The XR edge Applications\* perform 'XR rendering collaboration' with XR devices. The XR devices send '0. Application awareness' to the External consumer. A legend indicates: orange lines for 'existed in O-RAN', green lines for 'potential enhancement in O-RAN', and blue lines for 'out of O-RAN scope'. A note states: 'XR edge application can share the infrastructure resources provided for O-RAN NFs'.
-
-Figure 5.4.3-1: XR rendering collaboration over SMO
-
-### 5.4.4 Benefits of O-RAN Architecture
-
-O-Cloud in O-RAN provides the necessary computing, storage, and communication resources to host and execute the virtualized functions and applications required for O-RAN operations. O-Cloud can extend its capabilities to the network edge, reducing latency and improves the performance of XR applications by processing data closer to the source.
-
-O-RAN’s open interfaces and AI/ML based architecture will enable the challenging mechanisms of XR rendering collaboration to be implemented. For example, Near-RT RIC collects rich data on radio conditions and computing capabilities in RAN, as well as information on XR applications. By training AI models with these data, the performance of XR rendering collaboration tasks can be significantly enhanced with jointly optimizing computing node selection, computing resource allocation and radio resource optimization.
-
-The purpose of this use case is to perform distributed rendering of co-orchestration of communication resources and computing resources in O-RAN to improve the experience of XR users.
-
-## 5.5 Use Case 5: Computing Resource Scheduling in V2X Communications
-
-### 5.5.1 Background Information
-
-It is expected that there will be approximately 8 million autonomous or semi-autonomous vehicles on the road by 2025 [i.29]. As an enabling technology, Vehicle-to-Everything (V2X) communication is pivotal in paving the way for the Intelligent Traffic System and autonomous vehicles by facilitating the exchange of crucial information among vehicles, infrastructure, and pedestrians. This exchange encompasses critical data, including real-time updates on traffic conditions, impending road hazards, and precise speed limits, to improve decision-making and prevent accidents.
-
-Within the realm of V2X communications, the intersection is one of the most challenging scenarios. The various ways of transportation (e.g. vehicles, pedestrians) coupled with densely constructed buildings contributes to the complexity of traffic conditions, resulting in a large amount of data gathered from diverse sources for comprehensive sensing and collision avoidance. As shown in Figure 5.5.1-1, Vehicle 1 travels straight through the intersection, while Vehicle 2 maintains a safe distance behind Vehicle 1, intending to turn left. During the drive, there are several risks.
-
-- Vehicle 1 risks colliding with Vehicle 3.
-- Vehicle 1 or Vehicle 3 risks colliding with the pedestrian 2 (if he suddenly rushes from behind Building 2 and turns left). However, either Vehicle 1 or Vehicle 3 cannot sense the pedestrian timely due to the blocking by Building 2.
-- Vehicle 2 risks colliding with other vehicles and pedestrian (e.g., Vehicle 3 and pedestrian 1). Due to the blocking by Vehicle 1 and Building 1, Vehicle 2 is unable to accurately sense traffic conditions ahead and to the left in real-time
-
-and should obtain information by exchanging information with other vehicles or infrastructures, which may result in high latency and high risk of collision.
-
-
-
-Figure 5.5.1-1: An illustration of the potential collisions at intersections. The diagram shows a four-way intersection with two buildings (Building 1 and Building 2) on opposite sides. A central radio tower is positioned at the intersection. Three vehicles (Vehicle 1, Vehicle 2, and Vehicle 3) and two pedestrians (Pedestrian 1 and Pedestrian 2) are shown approaching the intersection from different directions. Yellow starburst icons labeled 'risk' are placed at the intersection point, indicating potential collision points for the vehicles and pedestrians.
-
-**Figure 5.5.1-1: An illustration of the potential collisions at intersections**
-
-In collision warning scenarios, the latency requirement for data collection and computing are in few milliseconds (e.g., the maximum end-to-end latency for cooperative collision avoidance in the advanced driving scenario is 10ms.) [i.30], so that the results and warns can be fed back to vehicles and pedestrians in timely manner. To fulfill the strict latency demand, it is essential to process these tasks in one or several optimal computing nodes, e.g., the central cloud, edge cloud, radio edge cloud, device edge cloud etc. Since the end-to-end latency is limited by the computing latency and network latency, the optimal offloading choice cannot be found by either optimize the network or computing resource. Hence, joint optimization of network and computing resource is needed. For example, the road status sensing data from Vehicle 1, Vehicle 3 and Pedestrian 2 must be communicated and processed and the result fed back within milliseconds to avoid the collision between them.
-
-To reduce network latency, it is desirable to process the data locally in vehicles. However, the computing resources of vehicles may be limited, which may not satisfy the task requirements in terms of computing resources and capabilities and could also lead to high computing latency. Therefore, it may be desired to offload all or part of the data processing to the best edge server (e.g., the server completes data processing with the lowest latency, lowest energy consumption.) through joint optimization of network and computing resources. However, since the task requirements on computing resources (e.g., the required type of computing resources) are diverse and the availability of computing resources is dynamic, it is of great importance to enable joint communication and computing resources optimization. What is worse, there are other data to be processed, such as navigation requests from other vehicles, requests for entertainment-related services from passengers, etc., which also consume limited computing and communication resources and increase the difficulties.
-
-### 5.5.2 Motivation
-
-The main objective is to enable joint communication and computing resources optimization for V2X communications. In O-RAN, the global information on communication and computing resources is available over O1 and O2 interface, thus facilitating the joint communication and computing resources optimization. With the above global information, resource scheduling policies for both communication and computing can be developed in Non-RT RIC (e.g., policies in terms of CPU frequency, bandwidth and power, etc.), and communication optimization policies can be enforced by Near-RT RIC based on the near real-time UE level information (e.g., real-time link quality). In addition, the vacant computing resources in O-Cloud can provide edge computing services in case of low network load, which further facilitates the low-latency computing in V2X communications.
-
-### 5.5.3 Proposed Solution
-
-O-RAN can provide edge computing capabilities and communication assurance for computing in V2X. The vacant O-Cloud resources and collaboration between Non-RT RIC and Near-RT RIC facilitate on-demand resource allocation adjustments and joint optimization of communication and computing resource scheduling to ensure end-to-end performance.
-
-Fig. 5.5.3-1 illustrates how O-RAN can facilitate computing in V2X communications, where the O-Cloud is used as the computing entity in O-RAN.
-
-
-
-Diagram illustrating O-RAN assisted computing in V2X communications. The diagram shows the flow of information and requests between external consumers, the SMO, Non-RT RIC, Near-RT RIC, O-CU/O-DU, and the Infrastructure (O-Cloud). External consumers send service requests (2) and receive capability exposures (3). The SMO receives information exposures (4) from the Non-RT RIC and sends service assurance policies (5) to the Near-RT RIC. The Non-RT RIC receives data collection (1) from the Near-RT RIC and O-CU/O-DU. The Near-RT RIC receives device information collection (E2) from the O-CU/O-DU and sends communication and computing information exposures (Y1) to the edge/cloud server. The O-Cloud contains the Hypervisor (VM/Container) and the Infrastructure.
-
-**Figure 5.5.3-1: An illustration of O-RAN assisted computing in V2X communications**
-
-First, SMO retrieves data from Near-RT RIC, E2 nodes, O-Cloud, and/or edge/cloud servers to get the communication and computing resources information, which mainly includes but is not limited to information about available computing resources (e.g., resource type, CPU/GPU frequency and storage) and communication resources (e.g., network load, available bandwidth, link quality). The mentioned information of O-Cloud can be retrieved over the O2 interface, while the communication resource information can be obtained via the O1 interface from O-CU and O-DU. Also, the related information of external edge/cloud servers can be retrieved through the information exposure between external edge/cloud servers and SMO.
-
-Next, SMO exposes the computing services or integrated communication computing services provided by O-RAN to external entities, e.g., vehicles, pedestrians and other third-party consumers, so that external customers can send their service requests. The service request information can include but is not limited to data size, required computing resource type, latency deadline of the contained tasks.
-
-NOTE: The security related consideration is for further study.
-
-Then, Non-RT RIC trains the AI model to generate policies based on task requirements and available computing and communication resources. The policies mainly include but are not limited to task offloading strategies and/or the joint resource allocation/adjustment strategies of O-CUs/DUs (e.g., offload tasks to one of the O-DUs and allocate CPU frequency and bandwidth to these tasks based on non-real-time information), where the communication resources allocation/adjustment strategies can be further enforced and sent from Near-RT RIC to O-CUs/DUs (e.g., RAN optimization policies based on near real-time link quality).
-
-### 5.5.4 Benefits of O-RAN Architecture
-
-The O-RAN system presents several advantages in joint communication and computing resources optimization for V2X scenarios with a large amount of data to be processed in low latency. The vacant O-Cloud-based computing resources can be shared with edge applications. In addition, the Non-RT RIC can perform joint communication and computing resources optimization, and Near-RT RIC facilitates the RAN behaviour optimization based on the information obtained through E2 interface. In summary, O-RAN architecture provides necessary ingredients to facilitate computing for V2X scenarios.
-
-## 5.6 Use case 6: Exposure of performance information to assist computing resource scheduling
-
-### 5.6.1 Background Information
-
-Computing task performance information are used to monitor the loading conditions of virtual compute resources of computing tasks that include computing task memory usage, CPU occupancy rate, data throughput etc...
-
-ETSI NFV defines the use case of performance managements and performance metrics. Monitoring parameters associated with the compute related measurements and of interest for a VNF can be declared in the VNFD (see ETSI GS NFV-IFA 011 [i.35]). The measurements can be used as the triggers to the scale VNF operation (see clause 7.2.4 in ETSI GS NFV-IFA 008 [i.36]).
-
-The Kubernetes (K8s) API server provides supervision data about the Kubernetes objects, such as pods, processes and components use this information to track whether pods are being launched and maintained as expected. These cluster state metrics can also provide a high-level view of cluster and its state.
-
-### 5.6.2 Motivation
-
-In CCIN, computing resource orchestrator should continuously supervise the performance of running computing tasks. Reporting of running computing tasks performance information will assist the computing resource orchestrator to make decision on deploying a computing task to a new cloud node or triggering to scale a computing task.
-
-And this can also help the computing resource orchestrator to measure computing task's actual resource usage, which helps for evaluating the adequacy of a candidate cloud node to execute the computing task during mobility.
-
-### 5.6.3 Proposed Solution
-
-#### 5.6.3.1 Performance information reporting triggers redeployment of a computing task
-
-When a VNF/App is successfully deployed on an O-Cloud node, SMO collects the performance information of this VNF/App and computing resource information from Cloud Nodes distributed in various geographical locations on the O-Cloud through the O1 or O2 interface. If current O-Cloud node's performance does not meet the requirements of the VNF/App, computing resource orchestrator may trigger SMO to redeploy the VNF/App via the O2 interface.
-
-As shown in Figure 5.6.3.1-1, Node1 and Node2 provide computing resource at the edge cloud for UEs, and the coverage scope of cell shows as green in the figure. Through performance information reporting, when the orchestrators find that Node1 does not meet the computing resource requirements, the network may configure Node2 to serve the UE.
-
-
-
-Diagram of computing task orchestration based on performance information. At the top, External Clients connect to an SMO. The SMO is connected to an O-Cloud area (green oval) containing Near-RT RIC 1, E2 Nodes (CU DU), O-Cloud Node 1 (with VNF), O-Cloud Node 2, O-RU, and UE. Connections are shown between SMO and Near-RT RIC 1 (O1), Near-RT RIC 1 and E2 Nodes (E2), E2 Nodes and O-Cloud Node 1 (O2), E2 Nodes and O-Cloud Node 2 (O2), E2 Nodes and O-RU (Open RAN), and O-RU and UE. Performance information flow is indicated by dashed lines from O-Cloud Node 1 and O-Cloud Node 2 back to the SMO.
-
-Figure 5.6.3.1-1: Computing task orchestration based on performance information
-
-Entities/resources involved in the use case:
-
-- 1) SMO:
- - a) Support for collecting and analyzing VNF/App performance information from O-Cloud.
- - b) Support for redeployment or scale-in/scale-out VNF/App via O2.
-- 2) O-Cloud:
- - a) Support for computing related inventory and updated VNF/App performance information with required granularity to SMO over O2 interface.
- - b) Support for deploying of a VNF/App or scaling a VNF/App
-
-##### 3) Orchestrator/Application Server:
-
-- a) Request/subscribe VNF/App performance/computing information from SMO.
-- b) Response for deploy/scale VNF/App on O-Cloud.
-
-The whole procedure is presented in Table 5.6.3.1-1, illustrated by Figure. 5.6.3.1-2.
-
-**Table 5.6.3.1-1: Performance information reporting triggers redeployment of a computing task**
-
-| Use Case Step | Description of the Step |
-|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Goal | Performance information reporting assist redeployment of a computing task |
-| Actors and Roles | SMO, O-Cloud, orchestrators from other clouds/application server |
-| Assumptions | All relevant functions and components are instantiated.
O2 interface connectivity is established with SMO. |
-| Pre-conditions | SMO and O-Cloud are instantiated with O2 interface connectivity being established between them. |
-| Begins when | Orchestrators external to the O-Cloud want to subscribe VNFs/Apps performance information of O-Cloud. |
-| Step 1 (M) | Orchestrators external to the O-Cloud send VNFs/Apps performance information subscription to SMO. |
-| Step 2 (M) | SMO subscribe VNFs/Apps performance information from O-Cloud Nodes. |
-| Step 3 (M) | SMO response for VNFs/Apps performance information subscription to orchestrators external to the O-Cloud. |
-| Step 4 (L) | SMO collect VNF/App performance information via O2/O1 interface and send the notification to indicate VNF/App performance information to orchestrators external to the O-Cloud. |
-| Step 5 (M) | Performance can not fulfill the requirement, orchestrators external to the O-Cloud requests SMO to redeploy the VNF/App or App to cloud node2. SMO deploy VNF/App on node2 and VNF/App route switch from node1 to node2. |
-| Step 6 (L) | SMO terminate VNF/App on node1. |
-| Step 7 (M) | SMO response of redeployment of VNF/App success to orchestrators form other clouds or application servers. |
-| Ends when | Orchestrators form other clouds or application servers get the response. |
-| Post Conditions | N/A |
-
-```
-
-@startuml
-Skin rose
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-Box "Orchestrator" #lightcyan
- Participant "Orchestrator" as client
-End box
-
-Box SMO #gold
- Participant "SMO" as smo
-End box
-
-Box O_Cloud Node #lightseagreen
- Participant "IMS/DMS" as ims #orange
- Participant "Node 1" as ocloud1
- Participant "Node 2...Node N" as ocloud2
-End box
-
-autonumber 1
-|||
-
-activate ocloud1
-== VNF/Apps performance Subscription ==
-client ->smo : Subscription of VNF/App performance information\n report periodic
-or event trigger
-autonumber 2.1
-
-```
-
-```
-
-smo ->ims : Subscription of VNF/App performance information\n report periodic
-or event trigger
-smo <-ims : Response of VNF/App performance information
-autonumber 3
-client <-smo : Response of VNF/App performance information
-
-loop performance data accumulation
-autonumber 4.1
-ims <-> ocloud1: <> or <> VNF/App performance Information
-ims <-> ocloud2: <> or <> VNF/App performance Information
-ims -> smo: <> or <> VNF/App performance Information
-client <- smo: Notifications to indicatee VNF/App performance
-end
-
- Performance cant fulfill the resource requirement, deploy the VNF/App or App to other
-Cloud Node
-
-autonumber 5.1
-client -> smo: Request to change the cloud node to o-Cloud node 2
-loop for each NF need to be deployed on o-Cloud node 2
-alt ETSI
-note over smo, ocloud2:ETSI o-cloud Instantiate VNF/Apps refer to WG6 O2DMS ETSI IF 2.4.2.1
-else K8s (Kubernetes)
-note over smo, ocloud2: K8s (Kubernetes) o-cloud Instantiate NF deployment refer to WG6 O2DMS
-Kubernetes IF 3.1.2
-end
-ocloud2<->ocloud1:Swtich service route to ocloud2
-deactivate ocloud1
-activate ocloud2
-end
-
-
- Swtich service route to ocloud2 and terminate VNF/App instance on ocloud2
-autonumber 6.1
-
-loop for each VNF/Apps
-
-ims <- smo: Request to terminate the VNF/App
-
-alt ETSI
-note over ims, ocloud1:ETSI o-cloud terminate VNF/Apps
-else K8s (Kubernetes)
-note over ims, ocloud1: K8s (Kubernetes) o-cloud terminate
-end
-
-ims -> smo: Response to indicate the result of VNF/App termination
-end
-
-
-autonumber 7
-client <-smo :Response to indicate VNF/App node changing success
-deactivate ocloud2
-
-@enduml
-
-```
-
-
-
-```
-
-sequenceDiagram
- participant Orchestrator
- participant SMO
- participant IMS/DMS
- participant O_Cloud Node as O_Cloud Node (Node 1, Node 2...Node N)
-
- Note right of IMS/DMS: VNF/Apps performance Subscription
- Orchestrator->>SMO: 1 Subscription of VNF/App performance information (report periodic or event trigger)
- SMO->>IMS/DMS: 2.1 Subscription of VNF/App performance information (report periodic or event trigger)
- IMS/DMS-->>SMO: 2.2 Response of VNF/App performance information
- SMO-->>Orchestrator: 3 Response of VNF/App performance information
-
- loop performance data accumulation
- IMS/DMS->>Node 1: 4.1 or VNF/App performance Information
- Node 1->>Node 2...Node N: 4.2 or VNF/App performance Information
- Node 2...Node N-->>IMS/DMS: 4.3 or VNF/App performance Information
- IMS/DMS-->>Orchestrator: 4.4 Notifications to indicatee VNF/App performance
- end
-
- Note right of SMO: Performance cant fulfill the resource requirement, deploy the VNF/App or App to other Cloud Node
- Orchestrator->>SMO: 5.1 Request to change the cloud node to o-Cloud node 2
-
- loop for each NF need to be deployed on o-Cloud node 2
- alt ETSI: ETSI o-cloud Instantiate VNF/Apps refer to WG6 O2DMS ETSI IF 2.4.2.1
- alt K8s (Kubernetes) : K8s (Kubernetes) o-cloud Instantiate NF deployment refer to WG6 O2DMS Kubernetes IF 3.1.2
- end
-
- Note right of Node 1: 5.2 Switch service route to ocoud2
- Note right of SMO: Switch service route to ocoud2 and terminate VNF/App instance on ocoud2
-
- loop for each VNF/Apps
- SMO->>IMS/DMS: 6.1 Request to terminate the VNF/App
- alt ETSI: ETSI o-cloud terminate VNF/Apps
- alt K8s (Kubernetes) : K8s (Kubernetes) o-cloud terminate
- end
-
- IMS/DMS-->>SMO: 6.2 Response to indicate the result of VNF/App termination
- SMO-->>Orchestrator: 7 Response to indicate VNF/App node changing success
-
-```
-
-Sequence diagram showing performance information reporting triggers redeployment of a computing task. Lifelines: Orchestrator, SMO, IMS/DMS, O\_Cloud Node (Node 1, Node 2...Node N).
-
-**Table 5.6.3.2-2: Performance information reporting triggers redeployment of a computing task**
-
-Required data:
-
-Some computing task performance information that proposed to be exposed is list as below:
-
-##### 1) K8s
-
-- K8S pod status:
- - Pending
- - Running
- - Succussed
- - Failed
- - unknown
-- K8S Node, Pod, containers usage:
- - Memory requests: Total memory requests (bytes) of a pod
- - Memory limits Total memory limits (bytes) of a pod
-
-- Allocatable memory Total allocatable memory (bytes) of the node
-- Memory utilization Total memory in use on a node or pod
-- CPU requests Total CPU requests (cores) of a pod
-- CPU limits Total CPU limits (cores) of a pod
-- Allocatable CPU total allocatable CPU (cores) of the node
-- CPU utilization total CPU in use on a node or pod
-- Disk utilization total disk space used on a node
-
-##### 2) ETSI
-
-- ETSI VNF performance:
- - Average virtual CPU usage
- - Average virtual memory usage
- - Average virtual disk usage
- - Input data size (byte)
- - Output data size (byte)
- - Number of input packets
- - Number of output packets
-
-#### 5.6.3.2 Performance information reporting triggers to scale a computing task
-
-The orchestrators external to the O-Cloud who responsible for computing resource orchestration can also be triggered to perform Scale-In and Scale-Out by performance information reporting so as to make full use of computing resources.
-
-The whole procedure is presented in Table 5.6.3.2-1, illustrated by Figure. 5.6.3.2-1.
-
-**Table 5.6.3.2-1: Performance information reporting triggers to scale a computing task**
-
-| Use Case Step | Description of the Step |
-|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Goal | Performance information reporting assist scale-in/scale-out of a computing task |
-| Actors and Roles | SMO, O-Cloud, orchestrators from other clouds/application server |
-| Assumptions | - - All relevant functions and components are instantiated.
- - O2 interface connectivity is established with SMO.
|
-| Pre-conditions | - - SMO and O-Cloud are instantiated with O2 interface connectivity being established between them.
|
-| Begins when | Orchestrators form other clouds or application servers send subscribe VNFs/Apps performance information of O-Cloud. |
-| Step 1 (M) | Orchestrators external to the O-Cloud send VNFs/Apps performance information subscription to SMO. |
-| Step 2 (M) | SMO subscribe VNFs/Apps performance information from O-Cloud Nodes. |
-| Step 3 (M) | SMO response for VNFs/Apps performance information subscription to orchestrators external to the O-Cloud. |
-| Step 4 (L) | SMO collect VNF/App performance information via O2/O1 interface and send the notification to indicate VNF/App performance information to orchestrators form other clouds or application servers. |
-| Step 5 (M) | Resource can not fulfill the requirement (Scale out) or less resource is needed (Scale in), orchestrators form other clouds or application servers' triggers scale action. |
-| Step 6 (L) | SMO scale VNF/App via O2 interface. |
-| Step 7 (M) | SMO send response of VNF/App scale-out/Scale-in complete. |
-| Ends when | Orchestrators form other clouds or application servers get the response. |
-| Post Conditions | N/A |
-
-```
-
-@startuml
-Skin rose
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-Box "Orchestrator" #lightcyan
- Participant "Orchestrator" as client
-End box
-
-Box SMO #gold
- Participant "SMO" as smo
-End box
-
-Box O_Cloud Node #lightseagreen
- Participant "IMS/DMS" as ims #orange
- Participant "Node 1" as ocloud1
-End box
-autonumber 1
-
-activate ocloud1
-== VNFs/Apps performance Subscription ==
-client ->smo : Subscription of VNF/App performance information\n report periodic
-or event trigger
-autonumber 2.1
-smo ->ims : Subscription of VNF/App performance information\n report periodic
-or event trigger
-smo <-ims : Response of VNF/App performance information
-autonumber 3
-client <-smo : Response of VNF/App performance information
-|||
-loop performance data accumulation
-autonumber 4.1
- ims <-> ocloud1: <> or <> VNF/App performance Information
- ims -> smo: <> or <> VNF/App performance Information
- client <- smo: Notifications to indicatee VNF/App performance
-end
-
-```
-
-```
-
-|||
-== Resource can not fulfill the requirement(Scale out) or less resource is needed(Scale in) ==
-|||
-autonumber 5
-client -> smo: Request to scale-out/scale-in VNF/App
-loop for each NF need to be scale-out/scale-in on o-Cloud node
-autonumber 6.1
-smo ->ims : Request to scale-out/scale-in VNF/App
-note over ims, ocloud1: scale-out/scale-in VNF/App
-smo <-ims : Reponse VNF/App scale-out/scale-in complete
-end
-autonumber 7
-client <- smo:Reponse VNF/App scale-out/scale-in complete
-
-|||
-@enduml
-
-```
-
-
-
-The sequence diagram illustrates the interaction for performance reporting and scaling. Lifelines: Orchestrator, SMO, IMS/DMS, and Node 1 (part of O\_Cloud Node).
- 1. Subscription: Orchestrator sends a 'Subscription of VNF/App performance information' (1) to SMO. SMO then sends a similar subscription (2.1) to IMS/DMS. IMS/DMS responds (2.2) and SMO responds (3) to the Orchestrator.
- 2. Loop [performance data accumulation]: Node 1 sends '«O2» or «O1» VNF/App performance Information' (4.1) to IMS/DMS. IMS/DMS sends it (4.2) to SMO, which then sends 'Notifications to indicatee VNF/App performance' (4.3) to the Orchestrator.
- 3. Scaling Trigger: A note indicates 'Resource can not fulfill the requirement(Scale out) or less resource is needed(Scale in)'. Orchestrator sends 'Request to scale-out/scale-in VNF/App' (5) to SMO.
- 4. Loop [for each NF need to be scale-out/scale-in on o-Cloud node]: SMO sends 'Request to scale-out/scale-in VNF/App' (6.1) to IMS/DMS. A note 'scale-out/scale-in VNF/App' is shown. IMS/DMS responds (6.2) and SMO sends 'Reponse VNF/App scale-out/scale-in complete' (7) to the Orchestrator.
-
-Sequence diagram showing performance information reporting and scaling triggers between Orchestrator, SMO, IMS/DMS, and Node 1.
-
-Figure 5.6.3.2-1: Performance information reporting triggers to scale a computing task
-
-Required data:
-
-Same as clause 5.6.3.1.
-
-### 5.6.4 Benefits of O-RAN Architecture
-
-By providing computing task performance information to orchestrators external to the O-Cloud, orchestrators and application servers can redeploy or adjust computing tasks in O-Cloud. O-Cloud's edge computing resources can be fully and accurately
-
-scheduled. In that way, edge computing vertical businesses (e.g. XR, AI/ML, V2X, vertical industries) can be effectively supported by computing resource services.
-
-# --- 6 Key Issues
-
-## 6.1 Key Issue #1: Joint Communication and Computing Optimization
-
-Use cases 3, 4, and 5 have a common requirements on the joint communication and computing optimization. Use case 1 investigates the computing aware handover optimization. Use case 3 discusses how to expose the communication and computing status to the external entities (e.g., multi-cloud orchestrator, applications) to enable the RAN aware application optimization.
-
-In this key issue, the following points need to be studied:
-
-- How to enhance the mobility management to ensure the connection & service continuity taking both the communication and computing resource status into consideration?
-- What information needs to be exposed by O-RAN to external entities?
-- Which entity in O-RAN will do the exposure?
-- What's the mechanism (including the security mechanism) to support the information exposure?
-
-## 6.2 Key Issue #2: O-RAN computing service provision
-
-Use cases 3, 4 and 5 have a common requirement of exposing vacant O-RAN computing capabilities. The radio edge computing capability offered by O-RAN can be discovered by the O-RAN external consumers such as the multi-cloud orchestration or the application servers. The external consumers can monitor the O-RAN computing capability as well as other necessary information to decide whether to request edge application offloading to the O-RAN system.
-
-In this key issue, the following mechanisms need to be studied:
-
-- How an external consumer requests or subscribes to O-RAN system for providing the O-RAN computing capabilities?
-- How O-RAN system provides/updates the O-RAN computing capabilities to the external consumer?
-- How an external consumer requests or subscribes to O-RAN system for offloading the computing tasks to O-RAN system?
-
-## 6.3 Key Issue #3: O-RAN integrated communication and computing service provision
-
-Use Cases 3, 4 and 5 in Clause 5 expect O-RAN to provide integrated communication and computing services towards the external consumers (e.g., a multi-cloud orchestrator). Currently, SMO intent driven management was studied in [i.32], where RAN management intent and RAN performance assurance intents were investigated. However, they are all focusing on RAN communication services provision. While key issue 1 targets the O-RAN computing service provision. Key issue 3 is built on key issue 2 and the RAN service provision studied in [i.32] [i.33] [i.34], trying to investigate the integrated communication and computing service provision.
-
-In this key issue, the following mechanisms need to be studied:
-
-- How to describe or model the integrated communication and computing service profile?
-- How an external consumer requests or subscribes to the O-RAN system for integrated communication and computing services?
-- How does O-RAN system jointly orchestrate the communication and computing resources to fulfill the service request?
-
-## 6.4 Key Issue #4: Edge application orchestration in O-RAN
-
-As stated in use cases 3, 4 and 5, the vacant computing resources from the cloud-based RAN can be leveraged to offload edge computing applications or tasks so that radio cloud resources can be efficiently utilized. To achieve this vision and facilitate the computing service provision, integrated communication and computing services provision discussed in key issue 2 and 3, the edge application lifecycle management, including deployment, termination, upgrade, scale-in and out, etc., needs to be considered within O-RAN.
-
-In this key issue, the following mechanism needs to be studied:
-
-- How to deploy, manage and orchestrate the edge applications running on the O-Cloud?
-- How the edge application orchestration functionality interacts with the SMO services (SMOS) studied in [i.33], such as the RAN analytics SMOS, service orchestration SMOS, service assurance SMOS, to facilitate the joint communication and computing orchestration?
-
-# 7 Potential Solutions
-
-## 7.1 Solution #1: O1 configurations for multi-aspect handover optimization
-
-### 7.1.1 Key Issue Mapping
-
-This solution is for Key Issue #1: Joint Communication and Computing Optimization, specifically to enhance mobility management to ensure connection and service continuity, taking both communication and computing resource status into consideration.
-
-### 7.1.2 Description
-
-The solution is based on the clause 5.1 Use Case 1: Multi aspect handover optimization. It is built based on the existing capabilities of different interfaces such as R1 interface, O1 interface, O2 interface, etc. and introduces new O1 based configurations in Near-RT RIC to support multi-aspect handover optimization in a Communication and Computing Integrated Networks.
-
-This solution consists of rApp, SMO/Non-RT RIC Framework, near-RT RIC, E2 nodes, and O-Cloud. rApp uses the R1 interface to retrieve different input data, such as CM data, PM data, location data of different cloud-based RAN entities, supported types of computing resources, capabilities of computing resource types, and load/availability of computing resources in different cloud-based RAN entities. rApp then executes relevant algorithms to derive the proximal computing capability table and availability table for each cloud-based RAN entity. rApp uses this information to create different O1 based configurations for multi-aspect handover optimization using R1 services provided by SMO/Non-RT RIC Framework, which then creates the O1 based configurations at one or more near-RT RIC instances over O1. Near-RT RIC will then use E2 control or E2 policy to ensure the UE handover to the optimum target cloud-based Radio entity.
-
-### 7.1.3 Procedures
-
-Figure 7.1.3-1 depicts the procedure summarizing the solution.
-
-```
-@startuml
-Skin rose
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-skinparam lifelineStrategy solid
-skinparam wrapWidth 300
-autonumber
-
-box #lightseagreen
- participant "O-Cloud(s)" as OCLOUDS
-endbox
-```
-
-```
-box #gold
- participant "rApp" as rApp
- Participant "SMO / Non-RT RIC Framework" as nonRTRICFramework
-endbox
-
-box "O-RAN Nodes" #lightpink
- Participant "Near-RT RIC" as NearRTRIC
- Participant "E2-Node(s)" as RANNodes
-endbox
-
-group O1 Data Collection
- rApp -> nonRTRICFramework : <> Data collection request
- nonRTRICFramework -> RANNodes : <> Data collection request
- RANNodes -> nonRTRICFramework : <> Data Collection
- nonRTRICFramework -> rApp : <> Data Collection
-end
-
-group O2 Data Collection
- rApp -> nonRTRICFramework : <> Data collection request
- nonRTRICFramework -> OCLOUDS : <> Data collection request
- OCLOUDS -> nonRTRICFramework : <> Data Collection
- nonRTRICFramework -> rApp : <> Data Collection
-end
-
-group Data Analysis and Inference
- rApp -> rApp : Create Proximal Computing Capability Table and Availability table for
- each O-Cloud based RAN nodes and prepare related O1 configurations for multi-aspect handover
- optimization.
-end
-
-group Policy Creation
- rApp -> nonRTRICFramework : <> Create O1 configurations for multi-aspect handover
- optimization
- nonRTRICFramework -> NearRTRIC : <> Create O1 configurations
- NearRTRIC -> RANNodes : <> E2 control or E2 policies for multi-aspect handover
- optimization
-end
-
-@enduml
-```
-
-
-
-Sequence diagram showing O1 configurations for multi-aspect handover optimization. The diagram involves O-Cloud(s), rApp, SMO / Non-RT RIC Framework, Near-RT RIC, and E2-Node(s). It is divided into four phases: O1 Data Collection, O2 Data Collection, Data Analysis and Inference, and Policy Creation. The sequence of messages is as follows: 1. rApp to SMO: <> Data collection request; 2. SMO to E2-Node(s): <> Data collection request; 3. E2-Node(s) to SMO: <> Data Collection; 4. SMO to rApp: <> Data Collection; 5. rApp to SMO: <> Data collection request; 6. SMO to rApp: <> Data collection request; 7. rApp to SMO: <> Data Collection; 8. SMO to rApp: <> Data Collection; 9. rApp to SMO: Create Proximal Computing Capability Table and Availability table for each O-Cloud based RAN nodes and prepare related O1 configurations for multi-aspect handover optimization; 10. rApp to SMO: <> Create O1 configurations for multi-aspect handover optimization; 11. SMO to Near-RT RIC: <> Create O1 configurations; 12. Near-RT RIC to E2-Node(s): <> E2 control or E2 policies for multi-aspect handover optimization.
-
-Figure 7.1.3- 1: O1 configurations for multi-aspect handover optimization
-
-### 7.1.4 Impacts on entities, services and interfaces
-
-SMO/Non-RT RIC Framework:
-
-- Collects necessary CM/PM data from different cloud-based RAN entities over O1 interface. Collects supported types of computing resources, capabilities of computing resource types, and load/availability of computing resources in different cloud-based RAN entities over O2 interface.
-- Provides CM data, PM data, supported types of computing resources, capabilities of computing resource types, and load/availability of computing resources of different cloud-based RAN entities to rApp over R1 interface.
-- Provides O1 configurations to Near-RT RIC via O1 interface based on the request from rApp.
-
-rApp:
-
-- Retrieves necessary C/PM data related to different cloud-based RAN entities from SMO/Non-RT RIC Framework.
-- Retrieves supported types of computing resources, capabilities of computing resource types, and load/availability of computing resources in different cloud-based RAN entities from SMO/Non-RT RIC Framework.
-- Derives the Proximal Computing Capability Table and Availability Table for each cloud-based RAN entity, use this information to create related O1 configurations to support multi-aspect handover optimization in Near-RT RIC.
-
-Near-RT RIC:
-
-- Performs multi-aspect handover optimization based on the O1 configurations received.
-- Sends E2 control or E2 policy messages to E2 nodes (O-CU) related to multi-aspect handover optimization.
-
-E2 node:
-
-- Supports CM data read requests from SMO over O1 interface. Collect and Report PM data to SMO over O1 interface.
-- Supports UE handover related control and/or policy enforcement from near-RT RIC over E2 interface.
-
-O-Cloud:
-
-- Supports data requests related to supported types of computing resources, capabilities of computing resource types, and load/availability of computing resources of different cloud-based RAN entities to SMO over O2 interface.
-
-## 7.2 Solution #2: Computing information exposure via Y1 interface
-
-### 7.2.1 Key Issue Mapping
-
-This solution is for KI #1 Joint Communication and Computing Optimization.
-
-### 7.2.2 Description
-
-The solution aims to optimize joint communication and computing resources within O-RAN, particularly for use cases 3, 4, and 5. Building upon the existing capabilities of the Y1 interface, which is well-defined in the Y1 Type Definitions (Y1TD) and currently facilitates the exposure of communication information [i.37], this solution aims to extend the interface's functionality to include the exposure of computing information to external entities.
-
-The implementation of this solution involves defining the data structures and formats for computing information on the Y1 interface without needing to change the protocols or the procedures [i.38]. Besides, since Y1 Termination communicates with Y1 consumers via Y1 interface and exposes RAN analytics information service(s) from Near-RT RIC, Near-RT RIC need to obtain computing information from other O-RAN entities.
-
-The solution proposes that Near-RT RIC utilizes the O-Cloud Notification APIs to obtain computing information [i.39], which may be computing resources (containing physical and logical resources) or status (e.g., CPU load, network load, and storage consumption) information.
-
-### 7.2.3 Procedures
-
-Figure 7.2.3-1 depicts the procedure summarizing the solution.
-
-```
-@startuml
-Skin rose
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-Participant "External entities" as entities
-Participant "Near-RT RIC" as near
-Participant "O-Cloud" as ocloud
-
-entities -> near: 1 <> Subscribe/ Request computing information
-near -> ocloud: 2 Subscribe/ Request computing information via O-Cloud Notification APIs
-ocloud -> near: 3 Response/ Notify
-near -> entities: 4 <> Response/ Notify
-
-@enduml
-```
-
-
-
-```
-sequenceDiagram
- participant External entities
- participant Near-RT RIC
- participant O-Cloud
- Note left of External entities: 1 <> Subscribe/ Request computing information
- External entities->>Near-RT RIC: 1 <> Subscribe/ Request computing information
- Note right of Near-RT RIC: 2 Subscribe/ Request computing information via O-Cloud Notification APIs
- Near-RT RIC->>O-Cloud: 2 Subscribe/ Request computing information via O-Cloud Notification APIs
- Note right of O-Cloud: 3 Response/ Notify
- O-Cloud->>Near-RT RIC: 3 Response/ Notify
- Note right of Near-RT RIC: 4 <> Response/ Notify
- Near-RT RIC->>External entities: 4 <> Response/ Notify
-```
-
-Sequence diagram showing the interaction between External entities, Near-RT RIC, and O-Cloud for computing information exposure via Y1 interface. The steps are: 1. External entities send a Y1 Subscribe/ Request computing information to Near-RT RIC. 2. Near-RT RIC sends a Subscribe/ Request computing information via O-Cloud Notification APIs to O-Cloud. 3. O-Cloud sends a Response/ Notify to Near-RT RIC. 4. Near-RT RIC sends a Y1 Response/ Notify to External entities.
-
-Figure 7.2.3- 1: Computing Information Exposure via Y1 interface
-
-1. External entities subscribe or request computing information from Near-RT RIC via Y1 interface.
-2. Near-RT RIC subscribes or requests computing information via O-Cloud Notification APIs.
-
-3. Near-RT RIC receives response or notifications from O-Cloud.
-4. External entities receive response or notifications from Near-RT RIC via Y1 interface.
-
-### 7.2.4 Impacts on entities, services and interfaces
-
-Near-RT RIC:
-
-- Supports for receiving computing information subscription or request from external entities.
-- Supports the management of computing information processing workflows before exposure.
-- Supports subscription or request to O-Cloud via O-Cloud Notification APIs.
-- Supports computing information exposure on the Y1 interface.
-
-O-Cloud:
-
-- Supports for receiving computing information subscription or request from Near-RT RIC.
-
-External entities:
-
-- Supports subscription or request to Near-RT RIC via Y1 interface.
-
-## 7.3 Solution #3: Computing Service Provisioning
-
-### 7.3.1 Key Issue Mapping
-
-The solution is for Key Issue #2: O-RAN computing service provision.
-
-### 7.3.2 Description
-
-In clause 5, the use cases 2 to 5 describes the consumers consuming low latency communication and computing services provided by O-RAN via SMO. To facilitate the provisioning of computing services across diverse application scenarios, it is essential to develop a unified service provisioning approach for the SMO. An unified service provisioning approach of SMO will not only expedite O-RAN's ability to cater to varied business contexts and eliminate the complexity of designing different service delivery methods for different scenarios.
-
-Document [i.31] gives an Service Based Architecture (SBA) of Non-RT RIC, and the logical function Service Management and Exposure (SME) has been defined for Non-RT RIC internal services management, and exposes service to externals, therefore, utilizing SME to provide computing service to externals consumers is a feasible solution.
-
-This solution proposes to use SME to provide computing services externally. As a prerequisite for offering computing service, computing service firstly needs to be registered with the SME, e.g., RAN edge application orchestrator (REAO) registers computing service to SME. The SME offers service exposure to support external consumers discover computing service. External consumers obtain computing service API information through service discovery and consume computing service with the API.
-
-### 7.3.3 Procedures
-
-Figures 7.3.3-1 to 7.3.3-2 illustrate the process that summarizes the solution, wherein REAO serves as the computing service producer capable of registering and deregistering computing services with SME.
-
-#### 7.3.3.1 Computing service registration and discovery
-
-In the computing service registration procedure, REAO registers computing service to SME. The registered service could be exposed to external consumers.
-
-SME needs to provide a service discovery mechanism to enable external consumers to discover the computing service. SME can provide the service API information to external consumers through the service discovery. The service API information may contain the URI, IP address and Port, protocol, protocol number and data format, etc. for consumer consuming the service.
-
-The whole procedure is presented in Table 7.3.3-1, illustrated by Figure. 7.3.3-1.
-
-**Table 7.3.3-1: Computing service registration and service discovery**
-
-| Use Case Stage | Evolution / Specification |
-|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Goal | Computing service is registered with the SME and exposed to external consumers. Consumers can retrieve the computing service API through service discovery. |
-| Actors and Roles | SME, REAO, computing service consumers. |
-| Assumptions | The REAO inside SMO produces computing service. |
-| Step 1 (M) | REAO registers computing services with the SME. The computing service API information may include the URI, IP address, port, protocol, protocol number, data format, etc. |
-| Step 2 (M) | SME feeds the computing service registration result, e.g., successful or failure back to REAO |
-| Step 3 (M) | Computing service consumers interacts with SME for the computing service discovery. |
-| Step 4 (M) | SME feeds the computing service discovery back with service discovery result (e.g., successful, failure), service API, etc. |
-
-```
-
-@startuml
-skinparam sequenceArrowThickness 2
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-
-collections "Computing service consumer" as Consumers #LightCyan
-
-box "Service Management and Orchestration" #Gold
- Participant "SME" as SME #LightGray
- Collections "REAO" as REAO #LightGray
-end box
-
-Autonumber 1
-group "Computing service registration"
- REAO -> SME: Computing service registration request
- SME -> REAO: Computing service registration response
-end
-group "Computing service discovery"
- Consumers -> SME: Computing service discovery request
- SME -> Consumers: Computing service discovery response
-end
-
-@enduml
-
-```
-
-
-
-```
-
-sequenceDiagram
- participant Consumer as Computing service consumer
- subgraph SMO [Service Management and Orchestration]
- participant SME
- participant REAO
- end
- Note right of REAO: "Computing service registration"
- REAO->>SME: 1 Computing service registration request
- SME-->>REAO: 2 Computing service registration response
- Note left of SME: "Computing service discovery"
- Consumer->>SME: 3 Computing service discovery request
- SME-->>Consumer: 4 Computing service discovery response
-
-```
-
-Sequence diagram showing Computing Service Registration and Discovery. The diagram features a 'Computing service consumer' lifeline and a 'Service Management and Orchestration' box containing 'SME' and 'REAO' lifelines. The 'Computing service registration' sequence shows REAO sending a request to SME and SME returning a response. The 'Computing service discovery' sequence shows the consumer sending a request to SME and SME returning a response.
-
-**Figure 7.3.3- 1: Computing Service Registration and Discovery**
-
-#### 7.3.3.2 Computing service consumption
-
-In the computing service consumption procedure, consumers consume the computing service with the API retrieved from the service discovery procedure. The consumer provides the service requirements (e.g., required computing resource type, computing resource quantity, e2e latency, image URL, etc.) with in the computing service request, REAO allocates computing resources according to the requirements, deploys the workload and provides the consumer service endpoint information.
-
-The whole procedure is presented in Table 7.3.3-2, illustrated by Figure. 7.3.3-2.
-
-**Table 7.3.3-2: Computing service consumption**
-
-| Use Case Stage | Evolution / Specification |
-|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Goal | REAO deploys workloads on the O-Cloud based on user requirements, enabling users to access workloads. |
-| Actors and Roles | REAO, O-Cloud, computing service consumers. |
-| Assumptions | The REAO inside SMO produces computing service. |
-| Step 1 (M) | Consumers request computing service to REAO. Computing service requirement may include computing resource type (e.g., CPU, GPU, etc.), computing resource quantity, e2e latency, image URL, etc. |
-| Step 2 (M) | REAO feeds consumer back with a response to the received computing service request. |
-| Step 3 (M) | REAO deploys the workload on O-Cloud according to the computing requirements. |
-| Step 4 (M) | Once the workload deployed, REAO notifies consumer with the service availability and service entry point. |
-| Step 5 (M) | Consumer accesses the deployed workload. |
-
-```
-
-@startuml
-skinparam sequenceArrowThickness 2
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-
-collections "Computing service consumer" as Consumers #LightCyan
-
-box "Service Management and Orchestration" #Gold
- Participant "REAO" as REAO #LightGray
-end box
-
-box "O-Cloud" #DarkCyan
- Collections "WorkLoad" as WLoad
-end box
-
-Autonumber 1
-
-group "Computing service request"
- Consumers -> REAO: Computing service request
- REAO -> Consumers: Computing service response
-end
-
-group "Workload deployment"
- REAO <-> WLoad** : "Workload deployment"
-end
-
-REAO -> Consumers: Notification, contains e.g., \n service endpoint, service availability, etc.
-Consumers <--> WLoad: Service serving
-
-@enduml
-
-```
-
-
-
-```
-
-sequenceDiagram
- participant Consumer as Computing service consumer
- participant SMO as Service Management and Orchestration
- Note right of SMO: REAO
- participant OCloud as O-Cloud
- Note right of OCloud: WorkLoad
-
- Consumer->>REAO: 1 Computing service request
- REAO-->>Consumer: 2 Computing service response
- Note right of SMO: "Workload deployment"
- REAO->>WorkLoad: 3 "Workload deployment"
- REAO-->>Consumer: 4 Notification, contains e.g., service endpoint, service availability, etc.
- WorkLoad-->>Consumer: 5 Service serving
- Note right of SMO: REAO
- Note right of OCloud: WorkLoad
-
-```
-
-Sequence diagram illustrating Computing Service Consumption. The diagram shows interactions between a Computing service consumer, Service Management and Orchestration (SMO) containing REAO, and O-Cloud containing WorkLoad. The sequence includes: 1. Computing service request from consumer to REAO; 2. Computing service response from REAO to consumer; 3. Workload deployment from REAO to WorkLoad; 4. Notification (service endpoint, availability, etc.) from REAO to consumer; 5. Service serving from WorkLoad to consumer.
-
-Figure 7.3.3- 2: Computing Service Consumption
-
-### 7.3.4 Impacts on entities, services and interfaces
-
-SMO functionality:
-
-- Introduces new functionality or reuse such as NFO to provide computing service.
-- SME functions:
- - Support SMOS producer e.g., computing service producer REAO registering computing service to SME.
- - Support SMOS producer e.g., computing service producer REAO deregistering computing service from SME.
- - Support SMOS producer e.g., computing service producer REAO updating computing service to SME.
- - Support computing service exposure to external consumers.
- - Support external consumers to discover computing service.
-
-New service provided by SMO:
-
-- computing service.
-
-## 7.4 Solution #4: Integrated communication & computing service provisioning via SMO
-
-### 7.4.1 Key Issue Mapping
-
-This solution is for KI #3 O-RAN integrated communication and computing service provision.
-
-### 7.4.2 Description
-
-The solution aims to provide integrated communication and computing services towards the external consumers (e.g., a multi-cloud orchestrator) with O-RAN, particularly for use cases AI, XR, and V2X. Based on the existing research of SMO-enabled RAN communication service provisioning and its capability in retrieving the communication and computing resources information, this solution aims to extend the SMO's function to provide integrated communication and computing services.
-
-This solution involves illustrating the procedure of integrated communication and computing service request, as well as the orchestration of joint communication and computing resources within O-RAN.
-
-### 7.4.3 Procedures
-
-The whole procedure is presented in Table 7.4.3-1, illustrated by Figure. 7.4.3-1.
-
-**Table 7.4.3-1: Integrated communication & computing service provision via SMO**
-
-| Use Case Stage | Evolution / Specification |
-|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Goal | Provide integrated communication and computing service via SMO |
-| Actors and Roles | SMO, Near-RT RIC, O-Cloud, O-CU, O-DU |
-| Assumptions | All relevant functions and components are instantiated. |
-| Step 1-3 (M) | SMO exposes the integrated communication and computing service, and consumers send requests to SMO, where the service request includes but not limited to following information:
Service profile ID
Maximum number of UEs
Coverage for communication part of communication and computing services provided by RAN
Location of UE
Service end-to-end latency requirements
UE mobility level, UE trajectory
Overall uplink/downlink throughput requirements
Uplink/downlink throughput requirements per UE
Computing resource requirement
Storage resource requirement |
-| Step 4-5 (M) | SMO retrieves communication and computing information via O1 and O2 interfaces and performs joint communication and computing resource optimization via AI/ML inference. |
-| Step 6-8 (M) | SMO sends the workload deployment policy (e.g., the assigned endpoint) and/or computing resource optimization policy to O-Cloud via the O2 interface; O-Cloud performs workload deployment and resource assignment based on the policy.
SMO sends the communication resource optimization policy to Near-RT RIC via A1 interface, and Near-RT RIC send the policy to the E2 node. Also, Near-RT RIC can perform further communication optimization. E2 node allocates the communication (e.g., bandwidth) for services. |
-| Step 9 (M) | SMO sends notifications (e.g., service availability) to the consumer. The consumer establishes connection with the assigned endpoint and sends service load to the endpoint. |
-| Step 10 (M) | SMO evaluates the performance (e.g., network performance, QoS of service), updates AI/ML model and /or policy accordingly. |
-
-```
-
-@startuml
-skin rose
-skinparam defaultFontSize 12
-Autonumber
-
-Participant "Service consumer" as consumer
-Participant "SMO" as SMO
-Participant "Near RT-RIC" as RIC
-Participant "O-Cloud" as cloud
-Participant "E2 nodes" as e2
-
-group service exposure
-consumer->>SMO: service discovery request
-consumer<<-SMO: service discovery response
-end
-
-consumer->>SMO: service request
-
-group Joint communication and computing resource optimization
-SMO<<-cloud: Computing resource information
-SMO<<-e2: Communication resource information
-ref over SMO
-AI/ML inference
-end ref
-SMO->>cloud: Workload offload policy and/or computing resource optimization policy
-SMO->>RIC: Communication resource optimization policy
-RIC->>e2: Communication resource optimization policy
-end
-
-```
-
-```
-
-consumer<-SMO:Notifications (e.g., service availability)
-group Performance monitoring
-ref over SMO,RIC,cloud, e2
- Performance monitoring and evaluation
-end ref
-SMO->SMO: AI/ML model or policy update
-end
-@enduml
-
-```
-
-
-
-Sequence diagram showing interactions between Service consumer, SMO, Near RT-RIC, O-Cloud, and E2 nodes. The diagram includes three main interaction blocks: 'service exposure', 'joint communication and computing resource optimization', and 'Performance monitoring'. The 'service exposure' block involves a service discovery request and response, followed by a service request. The 'joint communication and computing resource optimization' block involves resource information exchange and policy updates, with an 'AI/ML inference' sub-block. The 'Performance monitoring' block involves performance monitoring and evaluation, leading to an AI/ML model or policy update. Notifications are sent from the SMO to the Service consumer.
-
-Figure 7.4.3- 1: Integrated communication and computing service via SMO
-
-### 7.4.4 Impacts on entities, services and interfaces
-
-SMO:
-
-- Supports integrated communication and computing service exposure.
-- Supports receiving integrated communication and computing service requests from external entities.
-- Supports joint optimization of communication and computing resources.
-- Manages communication and computing information.
-
-New service provided by SMO:
-
-- Integrated communication and computing service.
-
-## 7.5 Solution #5: Edge application orchestration on O-Cloud via SMO
-
-### 7.5.1 Key Issue Mapping
-
-This solution is for Key Issue #4: Edge application orchestration in O-RAN, specifically to deploy, manage and orchestrate edge applications running on O-Cloud and enable their orchestration functionality to interact with SMO services (SMOS), leveraging O-Cloud's edge computing resources as an ideal provider for such deployments under the 3GPP edge computing framework.
-
-### 7.5.2 Description
-
-3GPP edge computing enables operator and 3rd party services to be hosted close to the UE's access point of attachment, to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network [i.8].
-
-O-RAN distributed telecommunication network with O-Cloud computing resource is an ideal provider for edge application resource deployment. SMO and O-Cloud have already provided services to manage O-Cloud infrastructure and NF deployments for O-RAN internal clients via the O2 interface [i.40]. Leveraging the edge cloud resource in O-Cloud for 3GPP edge computing could be a potential solution. With the adaptation of 3GPP edge computing framework, O-Cloud can provide computing resource for edge application to serve UE in cell's coverage as illustrated in the figure below.
-
-
-
-Diagram showing the deployment of edge computing NFs on O-Cloud. A Client connects to an SMO via services for application & VNF deployment. The SMO connects to a Near-RT RIC 1 via an A1 interface. The Near-RT RIC 1 connects to E2 Nodes (CU DU) via an E2 interface. The E2 Nodes connect to an O-RU via Open FH (C/U Plane, M Plane) interfaces. The O-RU connects to a UE. The O-Cloud, containing EAS, UPF, EES, and ECS, is connected to the E2 Nodes via an O2 interface. The entire setup is within Cell 1.
-
-Figure 7.5.2-1: Deploy Edge Computing NFs on O-Cloud
-
-### 7.5.3 Procedures
-
-Based on computing scheduling or performance management needs, SMO can periodically/event-based report O-Cloud computing information to provide service consumers with computing information subscription services. When the edge application service is initiated, the PLMN operator and the application provider can deploy the edge UPF and edge computing resources on the O-Cloud near the base station in service as needed.
-
-```
-@startuml
-Skin rose
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-Box "Client" #lightcyan
-Participant "client" as client
-End box
-```
-
-```
-
-Box SMO #gold
- Participant "SMO" as smo
-End box
-
-Box O_Cloud #lightseagreen
- Participant "IMS/DMS" as ims #orange
-End box
-
-autonumber 1
-== Computing Resource Information Subscription ==
-opt
-note over smo, ims:1 Refer to WG6.ORCH-USE-CASES 3.8 Performance Use Cases
-end
-|||
-
-== PDU session establishment, Client deploy Local UPF & Edge Computing NFs on O-Cloud ==
-|||
-
-note over client, ims:2 Refer to WG6.ORCH-USE-CASES 3.2.1 Instantiate Network Function
-
-|||
-@enduml
-
-```
-
-
-
-The diagram illustrates a sequence of interactions between three participants: Client (light blue), SMO (yellow), and O\_Cloud (teal). The sequence starts with the Client sending a 'Computing Resource Information Subscription' message to the O\_Cloud. An 'opt' block labeled '1 Refer to WG6.ORCH-USE-CASES 3.8 Performance Use Cases' is shown. Next, the Client sends a 'PDU session establishment, Client deploy Local UPF & Edge Computing NFs on O-Cloud' message to the SMO. A note labeled '2 Refer to WG6.ORCH-USE-CASES 3.2.1 Instantiate Network Function' is shown. The sequence ends with the Client, SMO, and O\_Cloud participants still active.
-
-Sequence diagram showing the interaction between Client, SMO, and O\_Cloud for deploying edge computing NFs. The diagram includes two main message flows: 'Computing Resource Information Subscription' and 'PDU session establishment, Client deploy Local UPF & Edge Computing NFs on O-Cloud'. The first flow includes an optional step (opt) with a note referring to WG6.ORCH-USE-CASES 3.8 Performance Use Cases. The second flow includes a note referring to WG6.ORCH-USE-CASES 3.2.1 Instantiate Network Function.
-
-Figure 7.5.3-1: Deploy Edge Computing NFs
-
-The steps are as follows:
-
-- Step1 (Optional): The client sends a subscription request to subscribe computing resource information from an O-Cloud. O-Cloud will feedback notification reports based on the subscription with a subscription filter.
-- Step2: The client sends the deployment request to SMO to deploy L-UPF & edge computing NFs on O-Cloud. After the NF(s) have been instantiated as NF deployment(s) on the O-Cloud and configured by the SMO, SMO sends a response of the result of VNF deployment to the client.
-
-### 7.5.4 Impacts on entities, services and interfaces
-
-Given that O-RAN can support the services for 3GPP edge computing, the further investigations are needed in the following works:
-
-1. Expose SMO services which necessary for Applications and VNFs, e.g. NS lifecycle management, NS performance management, fault management, VNF package management, NFVI capacity information, policy management, etc..
-2. Enhance the SMO to support the deployment, management and orchestration of applications running on the O-Cloud.
-
-# --- 8 Analysis on the Potential Architecture Impacts
-
-Based on the use cases study and potential solutions discussed above, the following potential impacts are identified for the O-RAN architecture.
-
-## Potential SMO Impact
-
-- Exposure of the O-RAN computing resource information
-- Exposure of the Computing services, and integrated communication and computing services
-- New functionality or enhancement on existing SMO functionality to enable the deployment, management and orchestration of the applications running on the O-Cloud
-- New functionality or enhancement on existing SMO functionality to facilitate the joint communication and computing orchestration
-
-## Potential Near-RT RIC Impact
-
-- Exposure of the O-RAN communication and computing information
-- New functionality or enhancement on existing functionality to facilitate the computing aware handover optimization
-
-## Potential O-Cloud Impact
-
-- Orchestration and management of the application deployment's life cycle
-- Management of the heterogeneous hardware infrastructure for diversified applications, e.g., AI, XR rendering
-
-## Potential Impacts on rApps
-
-- Derive proximal computing availability for O-RAN entity based on the load/availability analysis of the computing resource types
-
-## Potential O1 Impact
-
-- O1 configurations for handover based on the proximal computing capability and availability
-
-# --- 9 Deployment Scenarios
-
-## 9.1 Scenario A: Local O-Cloud for private networks
-
-In this scenario, the Near-RT RIC, O-CU, O-DU functions, and edge applications are all deployed on the same local O-Cloud platform as shown in Figure 9.1-1. This scenario support deployments in the industry private networks, where the edge applications, e.g., industry vision detection application can be deployed together with the 5G network to reduce the service latency and the transport bandwidth from the edge to the central cloud. In this scenario, the mobile network operator can provide the entire enterprise 5G network and edge solution. The mobile operator can choose to partner with one or more industry-specific edge application/platform provider, to deliver the end-to-end services including the 5G connection and the edge cloud capabilities. In this case, the mobile network operator can run the O-RAN NFs as well as the edge applications on
-
-its own infrastructure, i.e., O-Cloud. The O-RAN network functions and the edge applications are managed and orchestrated by the SMO. The application service provides (ASPs) may consume the services provided by SMO to orchestrate and manage the edge applications.
-
-
-
-Figure 9.1-1: Deployment Scenario A. A block diagram showing the network architecture. At the top, an ASP connects to an SMO. The SMO connects to a Near-RT RIC via an O2 interface. The Near-RT RIC connects to an O-CU via an E2 interface. The O-CU connects to an O-DU via an F1 interface. The O-DU connects to an O-RU via an Open Fronthaul interface. The O-RU is connected to the outside world. The Near-RT RIC, O-CU, O-DU, and O-Cloud Platform are all part of the O-Cloud Platform. The O-Cloud Platform also contains a Local UPF and Edge Applications. The Local UPF connects to the Edge Applications. The SMO also has a connection to the Edge Applications via the O2 interface.
-
-Figure 9.1-1: Deployment Scenario A
-
-NOTE: UPF is out of O-RAN Scope.
-
-## 9.2 Scenario B: Device Edge Cloud and local O-Cloud for private networks
-
-In this scenario, similar to scenario A, the Near-RT RIC, O-CU, O-DU functions, and edge applications are all deployed on the same local O-Cloud platform. Furthermore, the 5G industry gateway is introduced and serves as device edge cloud. The mobile operator can choose to partner with one or more industry-specific edge application/platform, device edge application provider, to deliver the end-to-end services including the 5G connection, the edge cloud capabilities and the device edge cloud capabilities. The SMO can be extended to also manage and orchestrate the device edge cloud and the device edge applications compared to scenario A. The deployment scenario is shown in Figure 9.2-1.
-
-
-
-Figure 9.2-1: Deployment Scenario B. This diagram is similar to Figure 9.1-1 but includes a 5G Industry Gateway. The 5G Industry Gateway, which contains 'Device Edge Applications' and a 'Device Edge Cloud', connects to an O-RU via a Uu interface. The O-RU then connects to the O-DU via an Open Fronthaul interface. The rest of the architecture (ASP, SMO, Near-RT RIC, O-CU, O-DU, O-Cloud Platform, Local UPF, Edge Applications) remains the same as in Scenario A.
-
-Figure 9.2-1: Deployment Scenario B
-
-## 9.3 Scenario C: O-Cloud coordination with global orchestrator
-
-In this scenario, the Near-RT RIC network function is deployed on a regional cloud platform, While the O-CU and O-DU functions are deployed on an edge cloud platform that in a different location of the Near-RT RIC. Near-RT RIC can control multiple O-CUs and O-DUs and is centralized for RAN optimization based on a more global view. The deployment scenario is shown in Figure 9.3-1. SMO can manage and orchestrate the cloud infrastructure that holds both the Near-RT RIC, O-CU and O-DU. Moreover, the computing capability of the infrastructure can be exposed by SMO to the global orchestrator. So, the global orchestrator can request to deploy the edge applications on the O-Cloud platform as needed.
-
-
-
-The diagram illustrates Deployment Scenario C. At the top, a 'Global Orchestrator' is connected to an 'SMO' (Service Management and Orchestration) block. The 'SMO' is connected to a 'Near-RT RIC' (Radio Intelligent Controller) via an 'O2' interface. The 'Near-RT RIC' is connected to an 'O-CU' (Central Unit) and an 'O-DU' (Distributed Unit) via 'E2' interfaces. The 'O-CU' and 'O-DU' are connected to an 'O-RU' (Radio Unit) via an 'Open Fronthaul' interface. The 'O-CU' and 'O-DU' are also connected to an 'O-Cloud Platform'. The 'Near-RT RIC' is connected to a 'Local UPF' (User Plane Function) and 'Edge Applications' via a 'Y1' interface. The 'Local UPF' and 'Edge Applications' are connected to another 'O-Cloud Platform'. This second 'O-Cloud Platform' is connected to 'Central Cloud & Applications' via an 'O2' interface.
-
-Deployment Scenario C diagram showing the architecture of O-RAN components including Global Orchestrator, SMO, Near-RT RIC, O-CU, O-DU, O-RU, Local UPF, Edge Applications, and Central Cloud & Applications.
-
-Figure 9.3 -1: Deployment Scenario C
-
-# 10 Potential Requirements
-
-| | Description |
-|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| REQ-SMO-01 | The SMO should support the capability to expose O-RAN computing resource information to authorized SMO services consumers. |
-| REQ-SMO-02 | The SMO should expose the RAN computing services to authorized SMO services consumers. |
-| REQ-SMO-03 | The SMO should expose the RAN integrated communication and computing services to authorized SMO services consumers. |
-| REQ-SMO-04 | The SMO should provide discoverability of the RAN computing capabilities offered by the SMO to authorized SMO services consumers. |
-| REQ-SMO-05 | The SMO should provide discoverability of the RAN integrated communication and computing capabilities offered by the SMO to authorized SMO services consumers. |
-| REQ-SMO-06 | The SMO should support the capabilities to jointly orchestrate the communication and computing resources of the O-Cloud and functionalities running over the O-Cloud . |
-| REQ-SMO-07 | The SMO should support the capabilities to deploy, manage and orchestrate the applications running on the O-Cloud. |
-| REQ-RIC-01 | The Near-RT RIC should support the capability to expose the O-RAN communication and computing analytics information. |
-| REQ-RIC-02 | The Near-RT RIC should support the computing aware handover optimization. |
-| REQ-OCloud-01 | The O-Cloud should support the orchestration and management of the application deployment's life cycle. |
-| REQ-OCloud-02 | The O-Cloud should support the management of heterogeneous hardware infrastructure for diversified applications, e.g., AI, XR rendering. |
-| REQ-O1-01 | The O1 interface should support the capability of transferring the O1 configurations for handover proximal computing capability and availability. |
-| REQ-HRD-01 | The hardware reference design for O-RAN should support heterogeneous computing for O-RAN network functions and diversified applications, e.g., edge AI, XR rendering. |
-
-# 11 Conclusion and Recommendations
-
-This Technical Report presents the use cases for integrated communication and computing in O-RAN. The potential solutions are also studied for the identified use cases and key issues.
-
-It is recommended to continue the study and specify the well identified use cases, the necessary architecture requirements and enhancements during normative work.
-
-# Annex: Change history/Change request (history)
-
-| Date | Revision | Description |
-|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 2025.12.02 | 02.00 | Version incremented for TSC. |
-| 2025.12.02 | 01.00.02 | Editorial changes according to the review comments during WG1 poll. |
-| 2025.10.17 | 01.00.01 | Implemented CR
CICT-2024.06.05-WG1-UCTG-CCIN-CR-0002-TR-Deploy Edge Computing on O-RAN Cloud-v6.docx
and editorial corrections. |
-| 2024.07.28 | 01.00 | Version incremented for TSC. |
-| 2024.07.28 | 00.00.10 | Editorial changes according to the review comments during WG1 poll. |
-| 2024.07.12 | 00.00.09 | Implemented CRs
- CMCC-2024.07.04-WG1-UCTG-CR-0027-Potential Requirements for CCIN-v01.docx
- CMCC-2024.07.04-WG1-UCTG-CR-0028-Add Conclusion and Recommendations for CCIN-v02.docx
Remove the optional Executive summary, introduction and the blank Annex A, Annex B |
-| 2024.07.11 | 00.00.08 | Implemented CRs
- CMCC-2024.04.26-WG1-UCTG-CR-0019-Potential solution for CCIN TR key issue 1-v03.docx
- CMCC-2024.04.17-ORAN-UCTG-CR-0020-addPotentialSolutionforKeyIssue2_v02.docx
- CMCC-2024.04.01-ORAN-UCTG-CR-0021UseCase-AddProposedSolution4MobileDeviceandRANAIInferenceCollaboration_v02.docx
- CMCC-2024.05.30-WG1-UCTG-CR-0022-Potential solution 3 for CCIN TR-v03.docx
- CMCC-2024.06.03-WG1-UCTG-CR-0023-Analysis on Potential Architecture Impacts of CCIN-v05.docx
- CMCC-2024.06.03-WG1-UCTG-CR-0024-Deployment Scenarios for CCIN-v02.docx
- CMCC-2024.06.03-WG1-UCTG-CR-0025-Potential Requirements for CCIN-v03.docx
Editorial corrections |
-| 2024.06.18 | 00.00.07 | Implemented CR
NOK-2024-06-09-WG1-UCTG-CR-0067-CCIN TR-Solution based on multi-aspect-handover-optimization-v02.docx |
-| 2024.06.04 | 00.00.06 | Implemented CR
CICT-2024.04.18-WG1-UCTG-CCIN-CR-0001-TR-Exposure of Performance information-v02.docx |
-| 2024.05.06 | 00.00.05 | Implemented CRs
- CMCC-2024.03.21-WG1-UCTG-CR-0015-add key issue 1 for CCIN TR clause 6-v02.docx
- CMCC-2024.03.21-WG1-UCTG-CR-0016-add key issue 2 for CCIN TR clause 6-v02.docx
- CMCC-2024.03.21-WG1-UCTG-CR-0017-add key issue 3 for CCIN TR clause 6-v02.docx
- CMCC-2024.03.21-WG1-UCTG-CR-0018-add key issue 4 for CCIN TR clause 6-v02.docx |
-| 2024.03.30 | 00.00.04 | Implemented CRs
- CMCC-2023.10.11-ORAN-UCTG-CR-0008UseCase-MobileDeviceandRANAIInferenceCollaboration_v04.docx
- CMCC-2024.01.18-WG1-UCTG-CR-0010-CCIN-add XR rendering collaboration use case for clause 5_v04.docx
- CMCC-2024.03.21-WG1-UCTG-CR-0011-CCIN- add V2X communications use case for clause 5_v06.docx |
-| 2024.03.21 | 00.00.03 | Implemented CRs
- CMCC-2024.02.13-WG1-UCTG-CR-0012-add O-RAN related work for CCIN TR clause 4.2-v01.docx
- CMCC-2024.02.13-WG1-UCTG-CR-0013-add O-RAN related work for CCIN TR clause 4.3-v01.docx
- CMCC-2024.03.07-ORAN-UCTG-CR-0014 CCIN phases and general challenges v3.docx |
-| 2024.02.13 | 00.00.02 | Implemented CRs |
-
-| | | |
-|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | apply the latest TR template O-RAN.WGn.descriptor.0-v02.00-TR-template
Editorial corrections
|
-| 2023.07.17 | 00.00.01 | Initial TR skeleton |
\ No newline at end of file
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/042733dc5e8e7f5f30b60adba3266cde_img.jpg
deleted file mode 100644
index 44837c3755911f6c639444886f727fc96ba8a77a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/042733dc5e8e7f5f30b60adba3266cde_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c76d6cd4a595819865837a86a4be10b60c56996340140db8f657feae73eec9d5
-size 22354
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
deleted file mode 100644
index 851948de3e4cf8db14183a86417bd57d7af282b8..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:df71020959de269282efac0702522a08e33d03c86fd8f29521af6a6c57166ad4
-size 4501
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/0c80c383f76034e117adf5e5eaadaaf3_img.jpg
deleted file mode 100644
index bba9e555249524e9456f7400751cb9c98644d86e..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/0c80c383f76034e117adf5e5eaadaaf3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:d32694ea97ed5ebdb2a42d4262362ac89f8a8868e9097e0d8b188286eeeb71ba
-size 58819
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
deleted file mode 100644
index 0b6896fb0be620d08fe1c93a2a1bb0aa5e6ec33e..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:0b4f087ef61703713ff6484020d0ba2db96f23b282623b00af4cad57ddf7482c
-size 54341
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/10781f43062bf3e9601a1e086710556c_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/10781f43062bf3e9601a1e086710556c_img.jpg
deleted file mode 100644
index 6798adb6ae5c13c07e323a2cdaaae165876987f5..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/10781f43062bf3e9601a1e086710556c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:18e414011104b5b7ce53abbee64baf2ff14837f1572c15b00607b86f4fe99dd5
-size 75551
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg
deleted file mode 100644
index 87202f8be749923c068d6f24ceeaff1caec60537..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:0d9c2725b1ac8238d6858423836c20f629a3e74601a74f1712d8b903267b6f8a
-size 104359
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
deleted file mode 100644
index 2f0502ceb5c65e795e5edaa961cc49d977189c34..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:24130c43b1f793a392bc7067511efd834a70cee80a3e26f2f4d9a71d259c8e87
-size 4512
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg
deleted file mode 100644
index 34c7ee24471861e6726adf42c8fa2305b5d54c4c..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ab43e6a3f885ec17183cb3a3ac1c6463696d6b100fa2d45c6c00f4e29120fa69
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg
deleted file mode 100644
index 057f7e7056463a13e26c42c4e41be5802951373b..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:92e3bf6f0c86b5f14209f0521305e713255ded7682d640ba78e57962ca4c704c
-size 4585
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg
deleted file mode 100644
index cd43600ce150ea843c1e739f13d1932db494c980..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:8ffce077466a1be594f44fb9e6841bbc37b7655c2e34e2384c23418653cd3f03
-size 63172
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg
deleted file mode 100644
index 2a1a0edfd9b93f6e595d4dc55642499ac459d584..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:5e0153d379b7b2cdde59b79a1aaa7276a10cbf0949be4961ef51dede2d5902e4
-size 32748
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
deleted file mode 100644
index 9c03c14f6381f565a95911fc858c1fad4f549523..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:7320e7d8ed618e22e8d2a31804b8566359bcd760defc36e4156066078cf3e71a
-size 4480
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
deleted file mode 100644
index 9c8dd2f0b70711024eea95cb4b4cdcde6aac6518..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:fe7db8bc2a107a3512a09f07021bff84daa2699c6795f89d0e8a9ee27c0a7805
-size 4609
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg
deleted file mode 100644
index 851948de3e4cf8db14183a86417bd57d7af282b8..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:df71020959de269282efac0702522a08e33d03c86fd8f29521af6a6c57166ad4
-size 4501
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8269648391c59363ea61243864a2adf7_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8269648391c59363ea61243864a2adf7_img.jpg
deleted file mode 100644
index 899f396e4c4237640be542f7a66372c736b6ccfe..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8269648391c59363ea61243864a2adf7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:86906f6b4e83ebff5c36b4a7996b4feb135f845f5dd3b0d7724a8e0bddae3cac
-size 90200
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg
deleted file mode 100644
index 9c8dd2f0b70711024eea95cb4b4cdcde6aac6518..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:fe7db8bc2a107a3512a09f07021bff84daa2699c6795f89d0e8a9ee27c0a7805
-size 4609
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg
deleted file mode 100644
index 2c4a9782a9af3b1da97bb0db70ec3964aa00b90a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:719e90101943d91d628e1712092d998668c8f4600277d0daa97e80df86d548c2
-size 4517
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
deleted file mode 100644
index 2c4a9782a9af3b1da97bb0db70ec3964aa00b90a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:719e90101943d91d628e1712092d998668c8f4600277d0daa97e80df86d548c2
-size 4517
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg
deleted file mode 100644
index 34c7ee24471861e6726adf42c8fa2305b5d54c4c..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ab43e6a3f885ec17183cb3a3ac1c6463696d6b100fa2d45c6c00f4e29120fa69
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
deleted file mode 100644
index 2c4a9782a9af3b1da97bb0db70ec3964aa00b90a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:719e90101943d91d628e1712092d998668c8f4600277d0daa97e80df86d548c2
-size 4517
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8e80de0cac529b2c3775d677c5203133_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8e80de0cac529b2c3775d677c5203133_img.jpg
deleted file mode 100644
index 87fa3df82d7359e72829b9bcfa2c8c6ae805cfd3..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/8e80de0cac529b2c3775d677c5203133_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:39fdc6620e5d6075396c557a01f3c9b647cacd534287c7cec0f8ee7920aa22f5
-size 93437
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/95e259e8cb3519025066052af263f8c0_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/95e259e8cb3519025066052af263f8c0_img.jpg
deleted file mode 100644
index 8a7c33e7742907319903f47b84f53d5ff60f5c90..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/95e259e8cb3519025066052af263f8c0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:24d5bc2c07ced78f9595ea8f83c1365b49393e92bc76570d4e4cb4ae7b15163b
-size 53678
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/96bfe678265c45ada94af2d97be9d002_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/96bfe678265c45ada94af2d97be9d002_img.jpg
deleted file mode 100644
index 7f2ec08c882dd0f1763f6cfd9432d35045da4c11..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/96bfe678265c45ada94af2d97be9d002_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4a4102fbc44a2ac5999a6a2150d44c4fd171276b6fe130a1e4cfc652a960dcbd
-size 33096
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/9cd90f495b95ad2116ff780248c26d95_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/9cd90f495b95ad2116ff780248c26d95_img.jpg
deleted file mode 100644
index 925b694f6e36cfc0bb63ecfd65cdb38bbbd24b4b..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/9cd90f495b95ad2116ff780248c26d95_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:5e6dc6c79b64898c9d798d2bfd3abf2b63d323fa217f9ec5e8584149c5c04471
-size 62376
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/a26e142d3df5bef41a84a9dd099d7825_img.jpg
deleted file mode 100644
index 24749000495cfe61cf941933e119079a7f5f943f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/a26e142d3df5bef41a84a9dd099d7825_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:7c1cb09c437ac40d32607274463a476b1f182a9377101344024849ab50eafdf1
-size 44531
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/a3083eec2a883ee8327b3c24174df6a9_img.jpg
deleted file mode 100644
index 65aa7358533bb992f408428748fba0553720f4f0..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/a3083eec2a883ee8327b3c24174df6a9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:688bed3df92e636b4cd45efd1e68a4d21c50eb3bc98ef11dad31285345a35271
-size 18908
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
deleted file mode 100644
index 6728fa177e230eb90b5357f60e74440c9bfd8c95..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:06d30a74823d22c7a1af631dc6c35ba6ae9e7a209d5427b46b6b9567a62e752a
-size 23277
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/b58cedaf15ad4f0edee5621820865ccc_img.jpg
deleted file mode 100644
index 9a32176fa00eb6cbfad18e16daeb493cfd0c8ab9..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/b58cedaf15ad4f0edee5621820865ccc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:dab14aa3a3399af8f68e1a8e519e17e0ef4e6ef4c061848e946ab67a68000b53
-size 49247
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/bd4617f25d15430eb78c2d6d75a99dde_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/bd4617f25d15430eb78c2d6d75a99dde_img.jpg
deleted file mode 100644
index f65ba0cc47efcb3c990d9d7ea484bab0b0562ab3..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/bd4617f25d15430eb78c2d6d75a99dde_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:252e04ee88371bf13717b34c1d244d63ffa07224b4aa0b6f217a593808fa69f4
-size 30237
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
deleted file mode 100644
index 8968dcbaefa00cfc3b0431dd032105e586d1cea0..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:43bcd28b9b01a756e82fa66af0ab34e66fcd686d30cb4b4be9a40bfe9c88c4c9
-size 20253
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg
deleted file mode 100644
index 34c7ee24471861e6726adf42c8fa2305b5d54c4c..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ab43e6a3f885ec17183cb3a3ac1c6463696d6b100fa2d45c6c00f4e29120fa69
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
deleted file mode 100644
index 5c2fe57a95b552796038dcdea478647dced31426..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4c2481d302c2b86f3746fce63e1d7d044e3a38593926b0fbad38444eeef8845d
-size 13903
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg
deleted file mode 100644
index d1d4e77ae8bb1c48359ae7fb053fec348edd450d..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:54b635b19f28176e22d62b3bd44f064a615c130448a2deac766be5fe497eb891
-size 25895
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg
deleted file mode 100644
index 34c7ee24471861e6726adf42c8fa2305b5d54c4c..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ab43e6a3f885ec17183cb3a3ac1c6463696d6b100fa2d45c6c00f4e29120fa69
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
deleted file mode 100644
index ba0e3d3a6ec61f294d10b623e33938cc7c7b3a80..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:7a2b46860ec2e67cf0c5eef36fbd8bd73d66915851cba0905a6dd230cff1bb64
-size 32443
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg
deleted file mode 100644
index 9f50ec1dd8294e5be9b5c550349c5b0607c33348..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a0421b1e78df9142a3692c859b674e7ee063a6dcb021aa8a3ba4138ca3c4d72b
-size 73093
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg
deleted file mode 100644
index 6dfcdfa7c7264459f7f9da2dfee320c8310e2dac..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:6169a91bb59ef05add5b1a7e9b84f7ff94dbe2e80199055bc93fedc0b70732bc
-size 156966
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
deleted file mode 100644
index 9a811bcf580b498ecf6cd9a285b2e8460d937b7a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:bb61a7c1791dfd334c00c0bd233d842fa46c8cedb22890947a8f8ec137d5d0d8
-size 55795
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg
deleted file mode 100644
index bcf488b349ff6749de0e128b31cb4627a824b416..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:45be48e0b3040763e8bd21e8fc28e9b60051712d0f7b980cefe8298a94468d6b
-size 124238
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg
deleted file mode 100644
index 34c7ee24471861e6726adf42c8fa2305b5d54c4c..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ab43e6a3f885ec17183cb3a3ac1c6463696d6b100fa2d45c6c00f4e29120fa69
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
deleted file mode 100644
index 2c4a9782a9af3b1da97bb0db70ec3964aa00b90a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:719e90101943d91d628e1712092d998668c8f4600277d0daa97e80df86d548c2
-size 4517
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
deleted file mode 100644
index 2740162d16f08089e069d66efc6f4b99eea7bf31..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:51929046562b35d8b7db0661c7dee23ce2a852ca65bed8abfb6642b035ca5dc7
-size 4582
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
deleted file mode 100644
index ec276610821d8eb61ca41b23567be854dcac8897..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:96252833bc060acfacb5872254f932230ab6c996ebf159530267567c7a02f0d0
-size 4559
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/ec3647789b5c38fb686f2a0833324e79_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/ec3647789b5c38fb686f2a0833324e79_img.jpg
deleted file mode 100644
index 070f780f8515d074bab5814686cc8cc1482f1375..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/ec3647789b5c38fb686f2a0833324e79_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:5d6049ce518e6c1d404731c783009b5428c656980654f4875c6b92d0e8a8f9c9
-size 27563
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/f1fbb1287d999c7034742de35bdab836_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/f1fbb1287d999c7034742de35bdab836_img.jpg
deleted file mode 100644
index 515bf76145aaecd5d56389b50b586ddda24329ee..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/f1fbb1287d999c7034742de35bdab836_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:6e45a99b3a1c136940c49ab687d3f89b26f57166bd5df8c34335cb73f757c965
-size 25170
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg
deleted file mode 100644
index 34c7ee24471861e6726adf42c8fa2305b5d54c4c..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ab43e6a3f885ec17183cb3a3ac1c6463696d6b100fa2d45c6c00f4e29120fa69
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
deleted file mode 100644
index be65e41140a7268775811014dcd16323eb56ea87..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.CCIN-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:880f2196dd95c352c5dafaec18230ae58eb591819ebbd7f38c3ab0432e65c847
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/doc.md b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/doc.md
deleted file mode 100644
index 800a1cd7627ed93fffe5a4f16b72275c15725590..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/doc.md
+++ /dev/null
@@ -1,1049 +0,0 @@
-
-
-# --- **O-RAN Work Group 1 (Use Cases and Overall Architecture)****RIC Enabling NTN Deployments**
-
-Copyright © 2026 by the O-RAN ALLIANCE e.V.
-
-The copying or incorporation into any other work of part or all of the material available in this document in any form without the prior written permission of O-RAN ALLIANCE e.V. is prohibited, save that you may print or download extracts of the material of this document for your personal use, or copy the material of this document for the purpose of sending to individual third parties for their information provided that you acknowledge O-RAN ALLIANCE as the source of the material and that you inform the third party that these conditions apply to them and that they must comply with them.
-
-O-RAN ALLIANCE e.V., Buschkauler Weg 27, 53347 Alfter, Germany
-Register of Associations, Bonn VR 11238, VAT ID DE321720189
-
-# Contents
-
-- List of figures.....3
-- List of tables .....3
-- Foreword.....4
-- Modal verbs terminology.....4
-- Introduction .....4
-- 1 Scope .....6
-- 2 References .....6
- - 2.1 Normative references .....6
- - 2.2 Informative references.....6
-- 3 Definition of terms, symbols and abbreviations .....6
- - 3.1 Terms.....6
- - 3.2 Symbols.....6
- - 3.3 Abbreviations .....6
-- 4 NTN development status in standard organizations .....7
- - 4.1 3GPP .....7
- - 4.1.1 Overview .....7
- - 4.1.2 R17/R18/R19 work items for NTN.....8
- - 4.2 O-RAN .....8
- - 4.2.1 Overview .....8
- - 4.2.2 Study and work items for NTN.....8
-- 5 Key NTN use cases analysis in O-RAN enabled by RIC .....9
- - 5.1 Use Case Group 1: TN and NTN interworking and cooperation.....9
- - 5.1.1 Overview .....9
- - 5.1.2 Use Case 1-1: TN-NTN Coverage Information Sharing.....9
- - 5.1.3 Use Case 1-2: TN-NTN Mobility and Service Continuity.....10
- - 5.1.4 Use Case 1-3: Request of NTN coverage for Disaster Response.....12
- - 5.1.5 Use Case Group 1: Summary, Proposed Solution, Benefits and Impact to the O-RAN Architecture .....13
- - 5.2 Use Case Group 2: Intra-NTN Mobility Use Cases .....16
- - 5.2.1 Overview .....16
- - 5.2.2 Use Case 2-1: Connected mode NTN inter-gNB handover (HO) due to Satellite mobility.....17
- - 5.2.3 Use Case 2-2: NTN QoS-based inter-cell traffic steering and load balancing.....23
- - 5.2.4 Use Case 2-3: NTN Time-based and Distance-based Conditional Handover (CHO).....27
- - 5.2.5 Use Case 2-4: NTN Idle mode cell re-selection.....33
- - 5.2.6 Use Case 2-5: NTN UE Location-aware Connected Mode Handover and Inter-cell Traffic Steering and Load-balancing .....33
-- 6 Summary and Conclusion .....37
-- Annex: Change history/Change request (history).....38
-
-## --- List of figures
-
-| | |
-|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|
-| Figure 5.1.5.3-1: Topology of inter-operator scenario..... | 15 |
-| Figure 5.1.5.3-2: Topology of single operator scenario ..... | 16 |
-| Figure 5.2.2.1-1: Example network scenario with 4 satellites from a Walker Delta formation (left) and snapshot of the moment where HO opportunity is available with 4 satellites in view (right)..... | 17 |
-| Figure 5.2.2.3-1: UML chart of NTN handover management..... | 22 |
-| Figure 5.2.3.3-1 UML flow chart of use case of NTN QoS-based resource optimization and traffic steering ..... | 26 |
-| Figure 5.2.4.3.1-1: EMC inter-satellite handover scenario..... | 28 |
-| Figure 5.2.4.3.1-2: EFC inter-satellite handover scenario..... | 29 |
-| Figure 5.2.4.3.2-3: EFC inter-beam handover scenario ..... | 30 |
-| Figure 5.2.6.3-1 UML flow chart of use case of NTN UE Location-aware Connected Mode Handover and Inter-cell Traffic Steering and Load-balancing..... | 36 |
-
-# --- List of tables
-
-| | |
-|-------------------------------------------------------------------------------------|----|
-| Table 5.2.2.3-1: NTN handover management..... | 20 |
-| Table 5.2.3.3-1: NTN QoS-based inter-cell traffic steering and load balancing ..... | 24 |
-| Table 5.2.6.3-1: NTN UE-location-aware handover management..... | 34 |
-
-# Foreword
-
-This Technical Report (TR) has been produced by WG1 of the O-RAN ALLIANCE.
-
-The content of the present document is subject to continuing work within O-RAN and may change following formal O-RAN approval. Should the O-RAN ALLIANCE modify the contents of the present document, it will be re-released by O-RAN with an identifying change of version date and an increase in version number as follows:
-
-version xx.yy.zz
-
-where:
-
-- xx: the first digit-group is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have xx=01). Always 2 digits with leading zero if needed.
-- yy: the second digit-group is incremented when editorial only changes have been incorporated in the document. Always 2 digits with leading zero if needed.
-- zz: the third digit-group included only in working versions of the document indicating incremental changes during the editing process. External versions never include the third digit-group. Always 2 digits with leading zero if needed.
-
-## Modal verbs terminology
-
-In the present document "**shall**", "**shall not**", "**should**", "**should not**", "**may**", "**need not**", "**will**", "**will not**", "**can**" and "**cannot**" are to be interpreted as described in clause 3.2 of the O-RAN Drafting Rules (Verbal forms for the expression of provisions).
-
-"**must**" and "**must not**" are **NOT** allowed in O-RAN deliverables except when used in direct citation.
-
-# Introduction
-
-Support for Non-Terrestrial Networks (NTN) has been introduced in the 3GPP specifications starting from Release 17. Release 18 has been recently completed, with further enhancements in development as part of Release 19 and expected in the upcoming Release 20.
-
-NTN has gained substantial momentum in the telecommunication industry, with the first services in support of IoT and direct-to-device messaging launched, and more deployments including NR-NTN upcoming. NTN presents an emerging opportunity for Open RAN and there are multiple research/development projects and evaluations in progress focusing on NTN implementation leveraging Open RAN technologies. Non-Terrestrial Networks, in particular NGSO constellations, dynamic GSO, as well as hybrid multi-orbit constellations, present complex architectural, control, radio resource management, mobility and orchestration challenges which could be addressed by Open RAN technologies.
-
-The O-RAN ALLIANCE is currently developing specifications for O-RAN RIC-enabled optimization and autonomous management of terrestrial networks. Standardization of O-RAN RIC-enabled optimization and autonomous management for NTN and converged NTN+TN interworking deployment scenarios is essential for the NTN operator constellation planning and architectural phases, as a key enabler for their commercial success.
-
-This intelligent management of the RAN and its operation is naturally addressed by the Non- and Near-RT RICs. However, while there are many use cases documented for their employment in terrestrial 5G networks, moving the network functions into space brings in a whole new set of challenges and constraints, and opens up completely different novel implementation approaches for the existing O-RAN use cases (such as TS and QoS optimization), as well as a new host of use cases that are specific to NTN. For example to account for the new control signaling features introduced for NTN in 3GPP Releases 17 and 18 (such as SIB19 and timer/distance-based CHO), as well as to address challenges unique to NTNs.
-
-This technical report investigates use cases applicable to NTN and presents a gap analysis on possible impacts to WG2 and WG3 specifications of the O-RAN ALLIANCE, in preparation for normative work in WG2 and WG3. Two main groups of use cases are identified:
-
-- **Use Case Group #1:** How the TN and NTN segments will intelligently cooperate and provide a seamless experience to the users as they traverse between TN and NTN, and vice-versa, while making sure that the available spectral resources are optimally utilized.
-- **Use Case Group #2:** Once in the NTN segment, how are the users and their traffic flows going to be intelligently managed by the SNOs such that they are assuring the types of services being sold while accounting for temporospatial variations in motion of the space and aerial assets, weather, spectrum availability, onboard power and hardware constraints, different terminal classes, fast mobility, Line of Sight (LoS), QoS, etc.
-
-# 1 Scope
-
-The present document specifies a technical report on RIC enabling NTN deployments use cases.
-
-# 2 References
-
-## 2.1 Normative references
-
-Not applicable.
-
-## 2.2 Informative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are not necessary for the application of the present document, but they assist the user with regard to a particular subject area.
-
-[i.1] Non-Terrestrial Networks (NTN)
-
-NOTE: Available at:
-
-[i.2] 3GPP TR 38.821: "Solutions for NR to support Non-Terrestrial Networks (NTN)"
-
-# 3 Definition of terms, symbols and abbreviations
-
-## 3.1 Terms
-
-Void
-
-## 3.2 Symbols
-
-Void
-
-## 3.3 Abbreviations
-
-For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply:
-
-| | |
-|-----|---------------------------|
-| CHO | Conditional Handover |
-| EFC | Earth Fixed Cell |
-| EMC | Earth Moving Cell |
-| FDD | Frequency Division Duplex |
-| FR1 | Frequency Range 1 |
-| GSO | Non-Geostationary Orbit |
-| HO | Handover |
-
-| | |
-|---------|-----------------------------------------------|
-| IoT-NTN | Internet of Things Non-Terrestrial Networking |
-| ISL | Inter-Satellite Link |
-| KPI | Key Performance Indicator |
-| LEO | Low Earth Orbit |
-| LoS | Line of Sight |
-| NB-IoT | Narrow Band Internet of Things |
-| NR-NTN | New Radio Non-Terrestrial Networking |
-| NTN | Non-Terrestrial Network |
-| NGSO | Non-Geostationary Orbit |
-| OTA | Over-The-Air |
-| PCI | Physical Cell Identity |
-| QEFC | Quasi-Earth-Fixed Cell |
-| RIC | Radio Intelligent Controller |
-| SMTC | SSB Measurement Timing Configuration |
-| SNO | Satellite Network Operator |
-| SSB | Synchronization Signal Block |
-| TDD | Time Division Duplex |
-| TN | Terrestrial Network |
-| UAV | Unmanned Aerial Vehicle |
-| UE | User Equipment |
-| UML | Unified Modeling Language |
-
-# 4 NTN development status in standard organizations
-
-## 4.1 3GPP
-
-### 4.1.1 Overview
-
-Non-Terrestrial Networks (NTN) are a significant focus within the 3GPP standards, particularly for integrating satellite into 5G and beyond. Here's a summary of the current development status:
-
-1. Release 15 and 16: Study phase on scenarios, use cases, channel models and impact of NTN to the 5G System, as well as solutions for 5G New Radio (NR) support for Non-Terrestrial Networks.
-2. Release 17 and 18: These releases introduced NTN with a transparent (bent-pipe) architecture, where satellites act as radio repeaters without on-board processing capabilities. This approach was chosen for its simplicity and early deployment potential. Both NR-NTN and IoT-NTN are supported. Release 18 introduced support for NR NTN above 10 GHz, such as broadband in Ka band.
-3. Release 19: This release marks a major milestone with the introduction of a regenerative payload architecture. In this scenario, a complete gNB (Next Generation Node B) is placed on the satellite, allowing for greater integration and flexibility, and opening up new constellation topologies and use cases). This architecture supports packet processing directly on the satellite, enabling features like improved mobility management.
-4. Release 20: The next release is currently in the planning phase and a 3GPP RAN workshop in RAN#106 (12/2024) discussed potential NTN features for Rel-20. The initial work plan for Rel-20 was decided in RAN#108 (06/2025).
-
-**Technological Challenges:** The development of NTN involves unique challenges such as high Doppler shifts, longer propagation delays, and larger cell sizes due to the high altitudes of satellites. Enhanced beam management and regulatory considerations are also crucial. Most of these challenges are already covered by Rel-17 and 18.
-
-**Future Prospects:** The ongoing work aims to further integrate NTN with terrestrial networks, enhancing global coverage and resilience. The regenerative payload architecture is expected to support advanced functionalities like "store and forward," which allows satellites to store data temporarily and forward it when connectivity is restored, and also UE-satellite-UE communication with reduced latency.
-
-### 4.1.2 R17/R18/R19 work items for NTN
-
-Release 17:
-
-1. Transparent payload architecture with FDD systems.
-2. Adaptation to physical and access layer aspects, radio access network, system architecture, radio resource management, and RF requirements.
-3. Support for NTN-NR (5G New Radio (NR)) based satellite access in FR1 bands for handheld devices.
-4. Support for NTN-IoT (NB-IoT and eMTC) based satellite access for massive IoT and handheld messaging use cases.
-
-Release 18:
-
-1. Enhancements for NR-NTN and IoT-NTN, especially the time and location based conditional handover (CHO) for mobility enhancements.
-2. Enablers for NR based satellite access in bands above 10 GHz (including introduction of Ka-band, see 3GPP TS 38.108 and 38.101-5).
-3. Support for fixed and moving platforms (e.g., aircraft, vessels, UAVs) and building-mounted devices.
-
-Release 19
-
-1. Downlink Coverage Enhancements with CD-SSB periodicity relaxation and enhanced beam-hopping support
-2. Uplink capacity enhancements.
-3. Support for a non-terrestrial network architecture with 5G system functions on board the NTN vehicle (regenerative payloads), including the possibility for inter-satellite links (ISL).
-4. Use of RedCap devices within FR1 NTN.
-5. Store & Forward (S&F) operation based on regenerative payload to support non-complete constellations.
-6. Specification of Ku-band for NTN operations
-7. Support for half duplex operation in TDD and FDD scenarios for IoT-NTN
-8. New L- and S- frequency band definitions
-9. Over-The-Air (OTA) antenna requirements and performance framework for NTN
-
-## 4.2 O-RAN
-
-### 4.2.1 Overview
-
-To the group's best knowledge, no approved contributions or normative work on NTN exist so far in O-RAN ALLIANCE, but there have been some requests for the definition of new WIs and research areas in nGRG.
-
-### 4.2.2 Study and work items for NTN
-
-The following proposals have been submitted so far:
-
-1. New feature work for NTN deployments enabled by RIC.
-2. Study on open TN-NTN architecture based on O-RAN
-3. Research for requirements on O-RAN based satellite clustering for NTN in nGRG
-4. Work for regenerative NTN support in O-RAN in WG1 UCTG
-
-# 5 Key NTN use cases analysis in O-RAN enabled by RIC
-
-## 5.1 Use Case Group 1: TN and NTN interworking and cooperation
-
-### 5.1.1 Overview
-
-In most cases, these NTN networks and services are not anticipated to be completely standalone offerings, but rather intended at least in part as a complement to Terrestrial Networks, for example to provide coverage extension in white spots and hard to reach areas, 3D coverage at altitude, or a layer of resiliency. In fact, the ability for NTN to eliminate or alleviate coverage gaps in the Terrestrial Network was one of the key motivations for the introduction of NTN in 3GPP since the beginning.
-
-Based on the current market trends, it appears NTN deployment motivations will in most cases fall into one of the following categories:
-
-- Existing Satellite Network Operators (SNOs) who are looking to serve the NTN market in addition to or in evolution of their existing non-3GPP satellite services.
-- New entrant SNOs who are seeking to uniquely provide NTN services.
-- Mobile Network Operators (MNOs) who are seeking to extend their network via NTN.
-- New entrant MNOs who are seeking provide homogenous TN and NTN coverage
-
-Therefore, it is expected that many MNOs may seek to extend their own Terrestrial Network services via NTN, however the current market trends indicate that they will likely not seek to deploy and operate their own satellites, but rather form agreements with one or multiple NTN SNOs, who will provide coverage over areas of interest on behalf of their partner MNOs.
-
-For this to be achieved, the MNO's and SNO's networks will need to interact and coordinate with one another at some level. The required degree of interaction and information sharing required between the two operator domains will depend on the requirements of the specific use case and on the depth of integration between the two segments. This interaction is essential in order to for example make the NTN network aware of where the boundaries of the terrestrial network exist, share handover preparation information, reselection targets, etc. and conversely make the terrestrial network aware of when an NTN is available to its users.
-
-The following clauses describe some of the use cases that fall within the category of TN and NTN interworking and cooperation and that have been grouped under Use Case Group 1 (UCG#1).
-
-### 5.1.2 Use Case 1-1: TN-NTN Coverage Information Sharing
-
-#### 5.1.2.1 Use Case Description
-
-In order for an MNO and their partner SNO(s) to be able to support efficient complementary coverage via NTN, the TN network may need to be aware of the available NTN coverage footprint, and vice versa. This can include current coverage (i.e. already active) as well as potential coverage (i.e. not yet active, but possible), and will need to include some details of the coverage to be provided (e.g. applicable NTN cells, their configuration and corresponding serving satellite ephemeris).
-
-Depending on a number of operational factors and system constraints, such as feeder link availability, power and radio resource availability of the satellites forming the NTN constellation, the active cells, allocated resources (and thus capacity), as well as the specific coverage areas that an NTN operator chooses to serve or not serve may change over time. In addition, due to orbital precession, the specific satellite(s) serving a given cell coverage area on the ground at any point of time (e.g. in a scenario with Earth-fixed or quasi-Earth-fixed Cells) also change over time. Thus there is a need for the NTN segment to be able to communicate this information to the TN segment, such that the TN segment can be aware of which NTN cells are available or might become available in the future, as well as update the information being broadcast in SIB19/SIB31 messages in terrestrial edge cells.
-
-Likewise, in the reverse direction, an NTN operator may normally not be aware of the footprint, topology, configuration or even presence of terrestrial networks within the coverage of an NTN, unless this information has been separately sourced or disclosed by the MNO. Whilst some of this information can be shared at network planning by the TN MNO to the NTN SNO,
-
-the TN MNO network is expected to evolve over time, potentially also dynamically via the introduction of network energy saving (NES) techniques, and thus may need to be updated at runtime.
-
-In scenarios where the NTN coverage may totally or partially overlap with the TN coverage or its edge, by having awareness of the TN footprint or of its edge, the NTN operator may be able to selectively deactivate NTN coverage in overlapping areas, in order to save system power, capacity, or to enable coverage in other locations. In scenarios with no overlap (e.g. due to TN spectrum reuse in space), the NTN operator may need to adjust the NTN coverage edge to match as closely as possible the TN coverage edge, at least for certain frequencies.
-
-#### 5.1.2.2 Problem statement and challenges
-
-In order to fulfil the requirements of these scenarios, the TN and NTN segments would need to have a method of exchanging at least the minimum necessary information on their respective coverage footprints, required to fulfil complementary coverage functionalities. The current 3GPP- and O-RAN-specified interfaces between operator domains, such as the roaming interfaces and other interfaces at the Core network and RAN level (e.g. Xn), do not support sharing of this type of information.
-
-Sharing of neighbor cell information, including neighbor relationships, and other coverage related information within a single network domain (e.g. within a TN or an NTN) is typically expected at least in part to be addressed by interfaces such as X2/Xn. However, in the interaction between TN and NTN this is either not sufficient (e.g. due to lack of the necessary primitives), or outright not possible, such as in the scenario where SNO and MNO, with both networks assumed to be aligned with 3GPP and O-RAN architecture, are two distinct operator domains, where inter-operator Xn is currently not contemplated (or implemented) and presents potential feasibility issues. In addition, both the TN footprint, topology and configuration, as well as the NTN footprint, topology and configuration, are expected to be continuously evolving and dynamic in nature, especially as operators (MNOs and SNOs alike) increasingly target maximization of energy and deployment efficiencies. Therefore, traditional manual or static mechanisms of sharing this information are not going to be fit for purpose, and there is instead a need for automated mechanisms that can dynamically provide updates on the changes to the coverage in a timely manner (order of seconds at least), as soon as they happen. It is also important that this sharing of information is performed securely and with a fine-grained level of control on the type and amount of information that is respectively shared, at any given instant of time.
-
-Therefore, there is a gap and an identified need for a secure, programmatic and reactive mechanism for TN and NTN networks in different operator domains to interface and interact, for the purpose of selectively sharing coverage related information.
-
-### 5.1.3 Use Case 1-2: TN-NTN Mobility and Service Continuity
-
-#### 5.1.3.1 Use Case Description
-
-This use case covers the support for mobility and service continuity between a terrestrial network (TN) and a Non-Terrestrial Network (NTN). One of the key value propositions for Non-Terrestrial Networks is to enable complementary coverage for terrestrial networks, and to help MNOs fulfil coverage gaps. As such, enabling or facilitating mobility and service continuity between the TN and the NTN and vice-versa is a key requirement.
-
-Whilst 3GPP defines the procedures at RAN level for TN-NTN idle and connected mode mobility and stipulates the need for sharing of coverage and satellite assistance information (e.g. Ephemeris), the 3GPP specifications do not explicitly address how this information is shared, and further how these procedures are coordinated when the TN and NTN are in different operator domains. This use case thus describes the requirements, expected procedure and possible solution to address these remaining aspects in respect to TN-NTN mobility and service continuity.
-
-In order to be able to support TN-NTN mobility, the TN RAN needs to be aware of the NTN coverage footprint, and specifically which satellite(s) are or will be serving a given coverage area at any point in time, and which are or may be the applicable neighbor NTN cells, with their respective configurations. In 3GPP NTN Rel-17+ systems, some of this information, alongside other details such as Ephemeris of the satellites, is expected as per the 3GPP specifications to be delivered via SIB19 or SIB31 into the TN cells bordering or overlapping with the NTN coverage area. However, in order for the information to be delivered to the TN cells, the terrestrial network has to first be aware of the information in the first place. This information may in many cases need to come from an external source to the MNO network (e.g. an SNO network). In addition, there may be another scenario in which an MNO may wish to provide
-
-Additionally, when it comes to evaluating the candidate handover or reselection opportunities to an NTN cell from a TN cell, there may be a subset of satellites which are better suited as target candidates, and there is a need to study how the O-RAN RIC/SMO architecture might be leveraged in optimizing the selection, for example by tailoring the SMTC list and the *NTN-*
-
-*NeighCellConfigList* provided in SIB19 to include only the satellite candidates that actually make for good handover or reselection targets, in some cases based on the specific UE service requirements on RAN and line-of-sight (LoS) conditions.
-
-#### 5.1.3.2 Problem statement and challenges
-
-Whilst 3GPP specifies mechanisms for TN-NTN mobility and service continuity, many of the capabilities and information exchanges required to implement said mobility, and to more in general facilitate the seamless interworking between TN and NTN are currently not addressed by 3GPP specifications, and could on the other hand be effectively addressed by O-RAN.
-
-In order to support mobility from TN to NTN, the TN network must be aware at least of the following information, and their applicability in time:
-
-- Satellite assistance information (e.g. Ephemeris) of the target NTN systems, satellites and cells available for handover or reselection
-- Cell topology and availability of the NTN cells neighboring or overlapping the TN coverage edge, that could be candidate target cells for measurement, reselection or handover
-- Cell configuration of the NTN cells neighboring or overlapping the TN coverage edge, necessary for measurement configurations, reselection policy configuration and handover triggering
-
-In addition, the network-initiated Connected Mode handovers must also be explicitly triggered by the network, which must be able to:
-
-- Request measurements to the target NTN network, to identify HO cell candidates
-- Request HO triggering to the target gNB
-
-In a terrestrial network scenario or an intra-operator TN-NTN scenario, many of these capabilities are or can be enabled by the X2/Xn interface. However, X2/Xn may not be feasible in an inter-domain/inter-operator environment.
-
-In addition, given that between two operators, the network topology might be partially or completely obfuscated, there is no way for the Source gNB to even identify which target gNB endpoint (e.g. gNB-CU) to address the measurement and handover requests, as the X2/Xn interface exists between individual eNBs/gNBs.
-
-Thus, there would be no mechanisms for signaling of neighbour relationships, including for measurement configurations. Furthermore, the TN may not even be aware of the neighbour NTN cells (esp. for candidate cells that are not active, in systems deploying selective coverage and/or beam hopping).
-
-Therefore, these challenges arise with this scenario and the lack of a suitable interface, for example:
-
-- No awareness by the TN of the target NTN cell configuration (e.g. frequencies, PCI, etc) required to configure measurements, HO triggers, Reselection policies.
-- No awareness of the gNB topology in the target network (either TN or NTN), and thus no awareness of which gNB to even establish an Xn connection or trigger an HO request or measurement request.
-- With 3GPP NTN R17+, the TN might not be aware of Satellite Ephemeris (SIB19/SIB31 content), required by the UE to perform UL pre-compensation
-- The NTN coverage may not be active (or may be configured with insufficient duty cycle/capacity) in the target area that the UEs are about to move to (satellite coverage is limited and must be selective)
-- The NTN may not have any awareness of incoming load, QoS requirements or UE capabilities
-- In 3GPP R19 NTN, SSB Periodicity could be relaxed (e.g. up to 160ms). This can impact UE sync performance/reliability and may need specific SMTC configuration for measurement before TN to NTN handover
-- UE capability signaling is very heavy. Forcing the NTN to perform UE capability exchange from scratch may have adverse impact on NTN capacity
-- Letting the UE/network declare RLF and Detach the UE, would lead to a network selection/access from scratch, which creates service interruption and unnecessary signalling load.
-- The NTN network may not be aware of which (or any) UE in TN are about to be handed over (or reselect to) NTN
-
-- In the reverse direction (NTN to TN), no awareness by the NTN of the target TN cell configuration (e.g. frequencies, PCI, etc) required to configure measurements, HO triggers, Reselection policies
-
-### 5.1.4 Use Case 1-3: Request of NTN coverage for Disaster Response
-
-#### 5.1.4.1 Use Case Description
-
-In some cases a Terrestrial MNO might wish to explicitly request NTN coverage in a given area, either to fulfil a coverage gap, or to respond to a total or partial outage of the terrestrial network, such as in a disaster scenario. This same capability could also be used simply to request the NTN to allocate additional capacity in a given area, in order to respond to an expected or witnessed increase in demand.
-
-Scenario 1) TN MNO1 identifies a coverage gap in its coverage, or is interested in providing additional coverage overlay, and thus requests NTN coverage to specific target geographical area to NTN SNO1.
-
-Scenario 2) TN MNO1 already has active NTN coverage by NTN SNO1 in a given target geographical area, but identifies a need to allocate additional capacity (e.g. due to an upcoming event).
-
-Scenario 3) During a disaster scenario (e.g. a hurricane), cell towers of TN MNO1 in a given area are affected by an outage (e.g. power outage) and are thus unavailable. TN MNO1 requests NTN coverage (in dedicated or shared spectrum) to the affected target geographical area to NTN SNO1.
-
-The scenarios from 1 to 3 are applicable also when an MNO has a commercial relationship or wishes to establish a commercial relationship with more than one NTN SNO partner.
-
-In addition to the basic coverage or capacity request, a TN MNO may wish to communicate additional information to their NTN SNO partner, for example:
-
-- Expected load or last-known load
-- Required capacity
-- QoS information and/or Slice policies for specific services that may be required (e.g. public safety, emergency messaging and/or calling)
-- List of UEs for prioritization/QoS policy
-- Pre-sharing of UE capabilities mapped to explicit list of UEs
-- Interference thresholds and coverage edge contours or other constraints (e.g. to prevent interference, in case of terrestrial spectrum reuse)
-- Desired cell configuration parameters
-- In case of terrestrial spectrum reuse or other form of spectrum lease, information on the spectrum available for deployment and any configuration requirements.
-
-#### 5.1.4.1 Problem Statement
-
-Current methods for an MNO to request NTN coverage from an SNO are entirely reliant on traditional office IT communication (e.g. emails, meetings), and require extensive discussions and pre-agreements not only at the commercial level, but also at the technical level, as a pre-requisite.
-
-With current methods, derivation of technical parameters for requests of either complementary coverage or capacity rely on extensive offline simulations performed by both parties respectively. These simulations are usually based on abstracted knowledge of the network, and relatively limited advance knowledge of the respective systems, also due to confidentiality constraints. From these simulations and plans, a notional NTN network plan is usually derived and agreed by both parties, via extensive discussion. In some cases, the simulations used to derive the plan may not even be fully reflective of the up-to-date conditions of the network (mostly because they are generated not from the live network, but from offline system-level simulator toolsets), nor of the real-world practical conditions in which the system will operate.
-
-In addition, any subsequent update usually needs to go through a similar formal cycle of discussions, simulations, agreements and formal approvals, de-facto preventing the enactment of any reactivity to changing requirements or events in responsive timeframes. In some cases, due to the relatively “static” nature of the plan and of the need to pre-plan in advance, often with a high level of detail, this can also lead to inflexibility in any regulatory filings submitted, where exact static values may be specified or filed for, and thus require an update to the regulatory filings in case some parameters are altered or optimized.
-
-As a consequence, the resulting plan exhibits a few unfortunate byproducts:
-
-- 1) **Staleness:** The NTN network plan derived is relatively static and represents a snapshot of the respective systems at a given moment of time, which may become stale over time, due to being unable to automatically reflect any subsequent changes or optimizations in either the MNO terrestrial network coverage, or the SNO's NTN coverage.
-- 2) **Immutability and lack of reactivity:** Changes in the NTN network plan are difficult and slow to introduce, and not only it cannot easily accommodate either changes in the actual respective network topologies, capabilities and plans, but it is also unable to be adapted in responsive time frames, to react to changing or unforeseen needs by either SNO or MNO, such as need to provide Disaster Coverage in response to an outage, spikes in demand or other time-sensitive events.
-- 3) **Poor accuracy:** Due to the simulation environments used to derive the technical parameters of the plan, and due to issues with confidentiality, the plan may not reflect the accurate and up-to-date state, capabilities or parameters of the live network, reducing the accuracy of representation. Its accuracy also to the physical live environment and its interaction with terrain, weather and other factors is also very limited.
-- 4) **Conservativeness and sub-optimality:** Due to the above issues, the plans are usually defined with relatively (sometimes extremely) conservative margins, in order to avoid, or at least reduce, any risks of disruption to user experience. Inevitably, this also results in significant sub-optimality.
-
-These issues could be resolved via a form of automated and programmatic mechanism, enabling the exchange of requests (as well as advertisements of availability) for coverage and capacity between different entities, such as for example between one MNO and one or more SNOs to provide NTN coverage and capacity in reaction to changing demand or to an unforeseen even, such as a disaster scenario.
-
-There are currently no existing interfaces, APIs or otherwise programmatic and/or automated mechanisms to support either static, semi-static or let alone dynamic requests for coverage and/or capacity between different operator entities within either the 3GPP or the O-RAN specifications. Such requirements and concepts have been raised and discussed from time to time, at least within 3GPP in the context of NTN, but have never so far been introduced. In particular, there is currently no satisfactory mechanism to satisfy certain mission-critical use cases for the public good, such as respond to the need to supply Disaster Coverage via NTN in response to total or partial outages to parts or totality of an MNO's terrestrial network within meaningfully responsive timeframes from the occurrence of an event (e.g. seconds or at most minutes).
-
-### 5.1.5 Use Case Group 1: Summary, Proposed Solution, Benefits and Impact to the O-RAN Architecture
-
-#### 5.1.5.1 Summary of Gap Analysis
-
-The previous clauses describe a number of use cases that involve interaction between the TN and NTN networks and summarize the current gaps and required interactions. Due to the commonalities between the different use cases, it was decided to address possible solutions in a single, common clause. The following clause thus analyzes possible common solutions to address the aforementioned use cases. From analyzing the different use cases in Group 1, we can also summarize a list of requirements that a possible solution must be able to fulfil.
-
-In all the previously discussed use cases of Group 1, it is assumed that the TN and NTN segments could be either part of the same operator domain or, more typically, part of two different and independent operator domains. It is also possible that, within a single operator domain, the operator may choose to maintain domain separation between the TN and NTN segments. Any new solution(s) must be capable of addressing all such cases.
-
-In addition, the solution should not be limited to a one-to-one relationship between TN and NTN segments, but should also enable one-to-many relationships, for example to support the case where an MNO may have multiple SNO partners, and vice-versa the case where an SNO may have multiple MNO partners/customers, but also the case where multiple separate TN and NTN segments exist within a single operator, as separate administrative domains.
-
-The key requirements for the solution can thus be summarized as follows:
-
-- 1) Allow interaction between TN and NTN segments in the same operator, assigned to a single administrative domain
-- 2) Allow interaction between TN and NTN segments in the same operator, assigned to multiple separate administrative domains
-- 3) Allow interaction between TN and NTN segments in different operators and independent operator administrative domains
-
-- 4) Allow interaction between one TN segment and multiple NTN segments (in the same or different operator domains)
-- 5) Allow interaction between one NTN segment and multiple TN segments (in the same or different operator domains)
-- 6) Allow sharing of NTN radio cell coverage information from the NTN to the TN
-- 7) Allow sharing of TN radio cell coverage information from the TN to the NTN
-- 8) Allow sharing of cell configuration between the TN and NTN
-- 9) Allow sharing of NTN satellite assistance information with the TN (e.g. in the form of satellite Ephemeris for SIB19/SIB31)
-- 10) Allow secure sharing of information between different operator trust domains
-- 11) Allow dynamically-selective sharing of information across TN and NTN based on respective operator's control
-- 12) Allow advertisement of network capabilities
-- 13) Allow requesting of NTN coverage to one or more target locations in 3D space and time
-- 14) Allow requesting of NTN capacity to one or more existing target NTN coverage areas
-- 15) Allow sharing of load information between networks
-- 16) Allow sharing of UE capability information between networks
-- 17) Allow sharing of QoS and Slice policy information between networks, including for specific UE to be prioritized (e.g. list of UEs)
-- 18) Allow sharing of information necessary to configuration of measurements for mobility between TN and NTN (in both directions)
-- 19) Allow triggering of measurements from the partner network (TN or NTN), e.g. in preparation for a mobility event
-- 20) Allow triggering of mobility events for Idle and Connected mode mobility between TN and NTN (in both directions)
-- 21) Allow sharing of acknowledgements and status information for previously advertised or requested capabilities
-
-The requirements described above cannot be presently satisfied by any existing interface, architectural element or procedure in the current 3GPP or O-RAN Architecture, at least for the case where the TN and NTN segment are operated by different entities (e.g. different operators) or part of different administrative domains.
-
-The O-RAN architecture and RIC/SMO complex, however, do offer a unique framework for management of radio coverage in an operator domain, to complement the 3GPP specification and address challenges not addressed by 3GPP, and are either already capable, or are expected to be capable (e.g. in the case of NTN) of accessing the required information in the respective operator networks. They therefore offer a unique opportunity to introduce a viable solution for TN-NTN radio network coverage level inter-working and cooperation, if a suitable mechanism to enable communication between the TN and NTN domains can be identified.
-
-#### 5.1.5.2 Proposed Solution: New TN-NTN Interface
-
-In order to satisfy the requirements outlined above, for the scenario in which the TN and NTN segments are operated by different operators, an MNO and an SNO respectively, or under otherwise different administrative domains, a potential proposed solution is the introduction of a new and novel O-RAN interface or API between the two operator domains that is suitably designed to cross the inter-operator domain trust boundary.
-
-If we assume that both the TN and NTN are respectively adopting the O-RAN architecture and thus both have their own respective Near/Non-RT RIC and SMO deployments, the new interface could be designed to exist between the MNO's and SNO's respective Near/Non-RT RICs or SMOs, facilitating different levels of information sharing. Such capability and interface are not currently specified or contemplated by the O-RAN Architecture and Specifications, and therefore it is identified as a gap. Overall, this cross-operator mode of operation and interaction was not envisaged by 3GPP or the O-RAN Alliance previously and would require investigation into how the O-RAN architecture may need to evolve, potentially with the specification of one or more new interfaces.
-
-After several discussions on at which layer should this new interface exist, and considerations for various candidate options, it seems that the most likely suitable approach may be to specify this interface between the Non-RT RICs or SMOs. However, the possibility of supporting a new interface between the Near-RT RICs could also be considered and should be further studied if the requirements for use cases demand it.
-
-#### 5.1.5.3 Impact to the O-RAN Architecture
-
-This clause of the Technical Report outlines different architecture options for TN-NTN interworking depending on whether the two segments are operated by the same or a different operator (or different administrative entities within the same operator), and considers as a solution the specification of at least a new interface between an NTN Non-RT RIC or SMO and a TN Non-RT RIC or SMO, at least for the case where TN and NTN segment are operated by different entities.
-
-The impact can thus be summarized as follows:
-
-- **Case 1 (TN and NTN operated by different entities):** Introduction of a new East/West API interface or service between Non-RT RICs or SMOs of the two operators.
-- **Case 2 (TN and NTN operated by the same entity):** Reuse of the existing A1 interface reference point and augmentation of the A1 and the RIC/SMO layer with procedures and information relating to TN-NTN information sharing.
-
-For the scenario in which the TN and NTN segment are operated by different operators, an MNO and an SNO respectively, or part of different administrative domains, a potential proposed solution is to introduce a new East/West API interface or service between the SNO's NTN Non-RT RIC and the MNO's TN Non-RT RIC. Via such interface, the TN Non-RT RIC and the NTN Non-RT RIC could exchange information regarding the respective coverage areas as well as other information as required for mobility and service continuity procedures.
-
-Figure 5.1.5.3-1, below, depicts the aforementioned topology in an inter-operator scenario, which sees separate TN and NTN network segments operated by different operators (e.g. an MNO and an SNO respectively), and highlights the potential new interface reference point between Non-RT RICs of the two operators. It is important to note that today some control and management functions may still be supported outside of the O-RAN architecture framework as they are not currently covered by any O-RAN function and are opaque to the O-RAN architecture. These have been represented in the figure below as “Non-O-RAN NTN Functions” and are currently outside of the scope of O-RAN and of this Technical Report. Similarly then, the interface between the Non-O-RAN NTN Functions and NTN gNB is currently a bespoke interface, which is also outside of the scope of O-RAN and of this Technical Report.
-
-
-
-Topology diagram of inter-operator scenario showing NTN and TN network segments. The NTN segment (left) includes NTN SMO (with NTN O&M and NTN Non-RT RIC), Non-O-RAN NTN Functions, NTN Near-RT RIC, and NTN gNB (with Gateways/Satellites and gNB functions). The TN segment (right) includes TN SMO, TN Near-RT RIC, and TN RAN. Interfaces shown include A1, E2, Xn, and a new I/F between NTN Non-RT RIC and TN SMO. Annotations include 'O1 with new satellite YANG models', 'Currently Proprietary I/F', and 'E2 with NTN enhancement'. A legend indicates SNO (Satellite Network Operator) and MNO (Mobile Network Operator).
-
-**Figure 5.1.5.3-1: Topology of inter-operator scenario**
-
-For the case in which the TN and NTN segment are operated by the same operating entity, the existing architecture and interfaces could be reused, whereby a single Non-RT RIC and SMO may exist and assume the responsibility of managing both the TN and NTN segments of the network.
-
-The existing mechanisms of interaction between the Non-RT RIC and the Near-RT RIC via the A1 interface could in principle thus be reused, with the assumption that the operator’s Non-RT RIC would have multiple A1 interface associations with one or more TN Near-RT RICs, as well as one or more NTN Near-RT RICs. The common Non-RT RIC could then supply information to both the TN and NTN Near-RT RICs in the shape of A1 policies or enrichment information, with appropriate extensions to the standardized data types, yet to be determined.
-
-Figure 5.1.5.3-2, below, depicts the aforementioned topology where both TN and NTN segments are operated by the same operator (e.g. either an MNO with an NTN component, or an SNO with a TN component). The topology of both TN and NTN segments follows the existing O-RAN architecture and reuses the existing O-RAN interfaces, such as the A1 reference point. Similarly to the inter-operator case, it is expected that today some control and management functions may still be supported outside of the O-RAN architecture framework as they are not currently covered by any O-RAN function and are opaque to the O-RAN architecture. These have been represented in the figure below as “Non-O-RAN NTN Functions” and are currently outside of the scope of O-RAN and of this Technical Report. Similarly then, the interface between the Non-O-RAN NTN Functions and NTN gNB is currently a bespoke interface, which is also outside of the scope of O-RAN and of this Technical Report.
-
-
-
-Topology diagram of a single operator scenario showing the interaction between TN and NTN segments. At the top, a blue box labeled 'TN/NTN SMO' contains 'TN/NTN O&M' and 'TN/NTN Non-RT RIC'. Below this, the 'TN/NTN Non-RT RIC' connects via A1 interfaces to two green boxes: 'NTN Near-RT RIC' and 'TN Near-RT RIC'. The 'NTN Near-RT RIC' connects via an 'E2 with NTN enhancement' interface to a green box labeled 'NTN gNB', which contains 'Gateways/Satellites' and 'gNB functions'. The 'TN Near-RT RIC' connects via an 'E2' interface to a green box labeled 'TN RAN'. A dashed line labeled 'Xn' connects the 'NTN gNB' and 'TN RAN'. On the left, a grey box labeled 'Non-O-RAN NTN Functions' is connected to the 'NTN gNB' via a 'Currently Proprietary I/F'. This box is also associated with 'O1 with new satellite YANG models'. On the right, an 'O1' interface is shown connecting the 'TN RAN'.
-
-Figure 5.1.5.3-2: Topology of single operator scenario
-
-#### 5.1.5.4 Benefits
-
-There are several benefits to this new proposed interaction, some of which have been captured in the Use Cases of the Use Case Group 1, and include the enablement of TN to NTN and NTN to TN mobility and service continuity scenarios, such as reselection and handover between the TN and the NTN and vice-versa, the enablement of the ability to request NTN coverage in a number of operator scenarios, as well as opportunities for higher levels of optimization, for example in how coverage is provided between the TN and NTN segment, and in ensuring truly complementary and mutually-beneficial and optimal coverage between the TN and NTN segments.
-
-## 5.2 Use Case Group 2: Intra-NTN Mobility Use Cases
-
-### 5.2.1 Overview
-
-This clause describes use cases applicable within the NTN, in particular, use cases related to aspects of mobility and intra-system service continuity. Mobility events in an NTN constellation may be driven by a number of factors and impairments that are specific to NTNs, in addition to typical UE mobility requirements, such as satellite (i.e. network node) mobility as well as delay and Doppler, spectrum and power constraints and others such as line-of-sight. The following are some examples of key mobility scenarios that can be expected in an NTN system:
-
-- Feeder link management (e.g. switching, load balancing, etc)
-- Satellite mobility
-- Satellite load balancing and selection
-- UE Mobility
-- Inter-satellite Link (ISL) mobility
-
-3GPP Releases 17, 18 and 19 introduced new procedures specifically to address NR-NTN and IoT NTN mobility management, that are designed to take into account such NTN-specific impairments and influencing factors. However, whilst the procedures are specified in detail in the 3GPP specification, their actual implementation and the full implications from a network architecture and implementation are not stipulated and are instead left up to operator and/or vendor implementation choice.
-
-This chapter analyses a number of mobility use cases that fall in the categories listed above and that leverage existing 3GPP procedures as of Release 18, within the context of the O-RAN architecture as a possible implementation, in a bid to efficiently allocate the limited resources of the NTN system whilst maintaining and maximizing fulfilment of user service requirements.
-
-Lastly, an initial assessment of the possible impact of the introduction of such use cases to the O-RAN architecture and specifications is made.
-
-### 5.2.2 Use Case 2-1: Connected mode NTN inter-gNB handover (HO) due to Satellite mobility
-
-#### 5.2.2.1 Use Case Description
-
-This use case covers the use of an NTN near-RT RIC and xApps to optimize the implementation of inter-satellite inter-gNB Connected Mode Handover (HO) within an NTN Non-Geostationary Orbit (NGSO) constellation, exemplified by a Low Earth Orbit (LEO) constellation, driven by satellite mobility. This use case is in principle formulated in a way that is largely agnostic of the NTN gNB architecture (e.g. Transparent vs Regenerative). In this scenario, users are assumed to be practically stationary or slow moving (e.g. handheld), and the mobility events are driven by satellite motion. This scenario use case description assumes Earth-fixed cells (EFC) or quasi-Earth-fixed cells (QEFC), but is applicable also to Earth-moving cells (EMC).
-
-Many upcoming 5G NTN constellations will be deployed in Low Earth Orbit, where a significant number of satellites are needed in order to achieve ubiquitous global coverage. LEO constellations are highly-mobile and their network configuration is continuously changing, and as such UEs may experience frequent handovers from one satellite to the next.
-
-In addition, in dense constellations, multiple candidate satellites may be able to serve a given coverage area, introducing the need for the network to select the appropriate target satellite to serve the incoming users. This could be influenced by a number of factors, such as feeder link availability, expected satellite visibility period, maximum number of concurrent beams, on-board power limitations, UE TX power and antenna gain, line of sight, spectrum constraints and more.
-
-
-
-Figure 5.2.2.1-1: Two side-by-side images of Earth showing satellite orbital trajectories in cyan. The left image shows four satellites (labeled 12, 11, 31, 21) with their projected paths. The right image shows a similar view with four satellites in view, illustrating a handover opportunity.
-
-**Figure 5.2.2.1-1: Example network scenario with 4 satellites from a Walker Delta formation (left) and snapshot of the moment where HO opportunity is available with 4 satellites in view (right)**
-
-The example scenario in Figure 5.2.2.1-1 shows part of an NTN LEO Walker Delta constellation with four satellites in view, two of which co-planar and two cross-planar. The projected satellite orbital trajectories are shown in cyan. As a simplifying
-
-assumption, each satellite is associated with a single feeder link (shown in dotted green) to a given gateway (represented by red dots associated to the green dotted lines) and a single gNB broadcasting a single PCI. Feeder link mobility is thus not considered for the sake of simplicity. This allows this use case to focus on user link mobility, and makes the scenario applicable to both Transparent and Regenerative architectures.
-
-Co-planar satellites are numbered with the same most-significant digit, whereas cross-planar satellites are assigned a different most-significant digit. The current scenario assumes that the associated satellites project a beam which is fixed to the satellite and is sweeping the Earth beneath. This eliminates the need for a system to be present which will intelligently control a steerable beam antenna that would direct energy towards a particular Earth-fixed direction, as well as maintain things like beam hopping schedules. However, in most future 5G NTN constellations, steerable beam antennas would be a key component, and their management and scheduling would have to be coordinated with the management of the 5G NTN RAN in order to achieve truly optimized operations.
-
-At the beginning of the scenario, a UE located in Spain is currently served by satellite 11, which forms the user link to the UE (in yellow) and is supported by a feeder link (in green) to a ground station in central Italy. As shown by the orbital trajectory, in some time, satellite 11 will be approaching the end of its viable service time for the target UE (e.g. due to low elevation, scan angle or link budget). Simultaneously, the remaining three satellites 12, 21 and 31 will approach the UE coverage area and become eligible to place a beam (and a cell) in the UE's location, and they therefore offer potentially viable candidate handover opportunities. Figure 5.2.2.1-3 shows the possible candidate satellites and UE service links at the instant in which all satellites are in principle eligible to serve the coverage area.
-
-An NTN Near-RT RIC and an associated NTN xApp could be tasked with taking all the various factors into account and driving the decision of which of the 3 available candidate handover satellites should start serving the UE once its currently serving satellite becomes unsuitable.
-
-In addition, the previously mentioned power and spectrum constraints present a further optimization opportunity to the network and NTN xApp: for example one of the available satellites could deliver the requested level of service to the UE while consuming fewer resources than another satellite. Lastly, in a scenario with several UEs in a given coverage area, the NTN Near-RT RIC and NTN xApp must make a handover decision that accounts for the requirements and conditions of all the users in the coverage area, which may create the need for trade-off decisions.
-
-#### 5.2.2.2 Problem statement and challenges
-
-The first part of the problem statement is relatively trivial. In order to support NR NTN scenarios aligned with 3GPP Release 17 and above, the NTN xApp must be able to configure the required NTN-specific measurement configurations, as well as the necessary handover triggers.
-
-In Release 17, a new SSB Measurement Timing Configuration (SMTC) specific to NR NTN, namely SMTC4 (*SSB-MTC4List-r17*), has been introduced. In addition, the NTN cells must be able to broadcast Satellite Assistance information, in particular Satellite Ephemeris, in the form of SIB19, containing serving and neighbor satellite and cell information. Furthermore, in order to trigger a HO, the gNB must be able to include specific SIB19 content in the HO triggers.
-
-This implicitly requires the NTN Near-RT RIC and xApp(s) to be aware of the constellation Ephemeris, the serving and target satellite timing information, as well have the ability to deliver the necessary configurations to the O-CU/DU.
-
-The second aspect of the problem is related to coordination of the HO across multiple satellites (and cells, potentially gNBs), in order to hand the UE over to the best satellite.
-
-Several criteria and KPIs may be taken into account to select the best target satellite, and, depending on the service requirements set by the SNO, the NTN RIC may have to either privilege one or more specific KPIs at the expense of others, or to perform a multi-constraint evaluation by ensuring adequate and balanced satisfaction of several different KPIs at once.
-
-In terrestrial networks, assessment of handover opportunities is almost entirely focused on KPIs affecting the user link, and would typically be driven by UEs measuring the SSBs of relevant neighbour cells, and then the gNB or Near-RT RIC monitoring for SMTC-configured measurement events and reports where the quality of a neighbour cell signal would exceed that of the serving cell signal by some threshold, such as is the case in the A3 event. Measurement reporting, based on SSBs but also CSI-RS, is also very important for channel estimation in terrestrial networks to aid link adaptation, primarily due to urban deployments where the various channel state and effects of multi-path propagation are highly and frequently variable and difficult to predict, except perhaps at the cell edge. In NTN deployments, on the other hand, limited multipath effects due to focus on outdoor environments, and the predictable movement of the satellite in the sky coupled with accurate weather forecast data make it such that the user link channel state by itself is much more steady and predictable, driven mostly by satellite motion, and can thus be
-
-quite reliably modelled and estimated. The overall link and HO candidate selection is, however, on the other hand, affected by a number of other factors, many of which are completely opaque to the gNB and cannot be addressed with measurements.
-
-Some examples include:
-
-- Ability to sustain the link vector for the duration of the satellite pass (or UE call flow) - influenced by a number of factors including feeder link availability
-- Available on-board battery power
-- Overall network load balancing goals
-- Cleanest channel, and thus best achievable MCS
-- Feeder link availability - e.g. due to weather or other system constraints such as antenna field of regard and LoS to the satellite.
-- Line of sight (LoS) on the user link (but not only)
-
-Feeder link availability is a particularly interesting example as it is chiefly important in transparent NTN deployments where, even in cases where the user link is in FR1, the NR-Uu waveform has to traverse also the feeder link between the satellite and the ground station, which often utilises higher frequencies (e.g. Ku-, Ka-, Q- or V-band) that are notably susceptible to attenuation due to weather effects, and which makes it such that the feeder link directly impacts the NR-Uu user link radio interface. The feeder link behavior and impacts are not specified in 3GPP; this effectively makes it opaque to the gNB and its internal processes. In addition, due to the dynamic nature of the system and of the external effects (e.g. weather) that might intervene, the impact to the NR-Uu user link introduced by the feeder link might not be completely known in advance by any of the individual gNBs at the moment of handover, due to the fact that a feeder link might not even have been established yet.
-
-Continuous satellite movement also makes it such that the channel quality is, albeit predictably, always continually and steadily changing, driven effectively by satellite motion, unlike in terrestrial networks. Not only might the different satellites and their respective feeder and user link vectors, propagating through variable weather and atmospheric conditions, result in varying channel qualities and therefore attainable MCS regimes, but they can also result in varying viable service times before either the user link or the service link becomes unsustainable, due to factors such as Line-of-Sight (LoS) or minimum elevation angles due to field-of-view (FoV) and obstructions.
-
-Thus, serving or neighbour cell signal measurements prior to the handover can by themselves be at least partially misleading in NTN, since they do not indicate much about either the end-to-end channel quality including the feeder link and the satellite itself (e.g. on transparent systems), past and future channel state evolution throughout the satellite pass, or future vectors between each satellite and the UEs being served, or expected to be served in the future (e.g. impacted by LoS effects, such as mountain ranges which might block LoS from a given area and UEs or feeder links to a given satellite at any future point of the service pass). For example, for Satellite 31 in Figure 5.2.2.1-1, a feeder link is formed with a ground station in the Azores. As the satellite propagates due North-East, it may witness its current ground station fall out of the feeder link view before the UE falls out of the user link view, thus requiring a feeder link handover. While feeder link is not a 3GPP-specified element of the network, mobility procedures associated with it may still require intervention from the RAN, and, depending on network implementation, may potentially result in an L3 Handover as well for the UE, leading to potential service discontinuity and signaling overhead.
-
-Furthermore, since the NTN link is often more constrained compared to a terrestrial link, an excessive reliance on user link signalling and UE measurement reports may create significant overhead on the link, negatively affecting user throughput and system capacity.
-
-This introduces the need for intervention, and opportunity for optimization, from an external control plane that has awareness of the satellite constellation, its sub-components and its evolution, and is thus capable of predicting the behaviour of both the user links and their channel state across multiple satellites throughout their motion, as well as the impact of components of the system that are outside of the scope of any individual gNB, such, in this example, other gNBs, other satellites or NTN service nodes, or any of the gateway feeder links. In addition, to account for events in the future impacting links that have not come into existence yet, there might be a need for the NTN control plane to be able to be spatially-aware, in addition to it being temporally-aware, to propagate predict where the NTN service nodes (e.g. satellites, but not only) might be at any future point in time and which links they might be able to form.
-
-#### 5.2.2.3 Proposed Solution
-
-A possible solution could be leveraging the NTN RIC, either as a combination of the Near-RT and the Non-RT RIC, or via the Near-RT RIC alone, with the introduction of a new control loop provided by one or more NTN xApp(s). Such xApps would leverage the holistic view of the satellite network provided by the NTN RIC, combined with predictive capabilities, to produce handover decisions which take into account multiple concurring factors, as well as reducing the reliance on signal measurements and reporting.
-
-The NTN RIC and xApp(s)/rApps are configured with a digital twin of the NTN network, including, not only the 3GPP RAN segment, but also the NTN ground and space segments (e.g. the gateways, the feeder links, the satellites, etc) via which the NTN service is delivered, even though some of these elements are presently not within the scope or control of the existing O-RAN reference framework.
-
-It is assumed that the NTN RIC may be capable of predicting NTN network node state, motion, trajectory (e.g. orbit) and behaviour in time and space. It is also assumed that the NTN RIC may be able to ingest external data sources, such as, but not limited to, weather data, to predict impact of external events on the active or candidate links, in order to aid the control loop affecting handover decisions.
-
-By knowing the predictable orbital movement of the candidate satellites , their association with ground stations and feeder links, the relatively static position (compared to the satellites) of UE or groups of UE in a given target coverage area (e.g. cell or cell portion) and the impact of weather effects, an NTN xApp could drive the decision of which satellite to hand over the UE to by modelling the candidate link vectors which could be formed and sustained until the need for the next handover, and aiming to choose the one that satisfies the appropriate combination of constraints. The use of prediction can be considered a supplement to, not a replacement of the evaluation of UE measurement reports.
-
-**Table 5.2.2.3-1: NTN handover management**
-
-| Use Case Stage | Detailed Information |
-|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Goal | Find best handover candidate satellites/cells for a UE to address impact of satellite motion and constellation evolution, while considering a number of diverse constraints and dependencies not directly visible through measurements, and trigger a Connected Mode Handover (HO). |
-| Actors and Roles | NTN xApp, Near-RT RIC, E2 Nodes, UE. |
-| Assumptions | All relevant functions and components are instantiated. The NTN RIC is aware of the state and motion of the constellation and is capable of predicting its evolution in time and space. |
-| Pre-conditions | E2 interface connectivity is established, UE is in active RRC Connected Mode state to a given serving satellite (e.g. Satellite 11) |
-| Step 1 (M) | NTN Handover Optimization xApp/Near-RT RIC subscribes to UE information change and message copy of UE mobility from E2 Nodes to understand the state of the network and the UEs within it. |
-| Step 2 (M) | NTN Handover Optimization xApp/Near-RT RIC requests to the E2 Nodes for the UEs to perform measurements of both serving and visible candidate target cells across satellites, and configure in the E2 Nodes UE information change and message copy of UE mobility to be reported back to the NTN Handover Optimization xApp /Near-RT RIC. |
-| Step 3 (M) | E2 Nodes configure target measurements to UEs and UEs perform measurements and monitor for configured measurement events, upon which they signal a measurement report to the serving NTN E2 Node |
-| Step 4 (M) | NTN E2 Nodes forward the measurement report to NTN Handover Optimization xApp/Near-RT RIC |
-| Step 5 (M) | xApp with digital twin analyses the currently employed Ground Station and transparent LEO satellite to derive the remaining service time before a handover must occur. It also evaluates the candidate handover opportunities via available neighbouring satellites and feeder links to model the link performances attainable during the service times that they could respectively offer to the UE, and compares them with the results of the measurement reports.
Its output is a selection of the neighbour satellite/cell which is best positioned to serve the UEs in the target coverage area.
|
-| Step 6 (M) | NTN Handover Optimization xApp/Near-RT RIC signals to NTN E2 Node to establish the correct handover control to the target UEs, to the selected target satellites, including the correct SIB19 contents (e.g. Ephemeris) for the respective target satellites to be included in the HO request message by the E2 Node. |
-
-| | |
-|------------|---------------------------------------------------------------------------------------------------------------|
-| Step 7 (M) | NTN E2 Node implements RRC Connected Mode handover as specified by NTN Handover Optimization xApp/Near-RT RIC |
-|------------|---------------------------------------------------------------------------------------------------------------|
-
-```
-
-@startuml handover optimization
-title NTN Handover Optimization Use Case
-Skin rose
-skinparam sequenceMessageAlign left
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-box "NTN Segment" #cyan
-participant "NTN HO Optimization xApp/Near-RT RIC" as xappnearrtric
-participant "NTN E2 Nodes" as e2nodes
-end box
-
-autonumber
-
-group #White NTN Handover Optimization xApp/Near-RT RIC collect RAN metrics
-xappnearrtric -> e2nodes: Subscribe to UE information change and message copy of measurement reports
-e2nodes -> xappnearrtric: Report UE information change and message copy of measurements events
-end group
-
-group #White NTN Handover Optimization xApp/Near-RT RIC establish signal measurement and reporting config for candidate handover opportunities
-xappnearrtric -> e2nodes: Set up signal measurement and reporting configuration per-UE/per-cell
-note over e2nodes: Configure measurement control for candidate serving satellites/cells and\nUE report measurement result of candidate serving satellites/cells to E2 nodes
-e2nodes -> xappnearrtric: Report the measurement result
-end group
-
-note over xappnearrtric
-xApp with digital twin analyses the currently employed Ground Station and transparent LEO satellite to derive the remaining service time before a handover must occur. It also evaluates the candidate handover opportunities via available neighbouring satellites and feeder links to model the link performances attainable during the service times that they could respectively offer to the UE, and compares them with the results of the measurement reports. Its output is a selection of the neighbour satellite/cell which is best positioned to serve the UEs in the target coverage area.
-end note
-
-note over xappnearrtric : xApp derives decision to handover\nUE to Neighboring X LEO, served\nby Neighboring X gNB/NTN GW
-
-xappnearrtric -> e2nodes: Per-UE network-initiated HO configuration, inclusive of SIB19 satellite assistance information
-note over e2nodes: Network initiated handover
-
-@enduml
-
-```
-
-
-
-UML sequence diagram titled 'NTN Handover Optimization Use Case'. It shows the interaction between 'NTN HO Optimization xApp/Near-RT RIC' and 'NTN E2 Nodes'. The sequence includes: 1. RIC collects RAN metrics from E2 nodes; 2. E2 nodes report UE information and measurement events; 3. RIC establishes signal measurement and reporting config for candidate handover opportunities; 4. E2 nodes report measurement results; 5. RIC sends per-UE network-initiated HO configuration (including SIB19 satellite assistance) to E2 nodes, leading to a network-initiated handover. Callouts explain that the xApp uses a digital twin to analyze ground station and LEO satellite data to predict service time and optimize handover candidates, and that the final decision is to handover the UE to a neighboring X LEO served by a neighboring X gNB/NTN GW.
-
-Figure 5.2.2.3-1: UML chart of NTN handover management
-
-#### 5.2.2.4 Benefits
-
-The first and main benefit is the introduction of support of Release 17+ NR NTN network-controlled Handover (HO) from RRC Connected Mode, including support for NTN-specific satellite assistance information in the HO request/trigger, which is presently not supported by the O-RAN specifications.
-
-The second benefit, achieved by the introduction of an NTN RIC (Near/Non-RT RIC) that is aware of the dynamic topology, physics and evolution of the constellation, and is capable of predicting its behaviour, is a potentially significant reduction of the signalling overhead, as well as a reduction of the potential for handover failures or sub-optimal handovers, leading to an improved service experience, as well as overall improved efficiency of the network by reduction of the resources consumed to support a mobility event.
-
-#### 5.2.2.5 Impact on O-RAN WGs
-
-The use case brings an intelligent NTN handover management approach to O-RAN, which also utilizes information that is not natively exposed by the O-RAN interfaces (information owing to the non-3GPP components of an NTN constellation, and the constellation’s own dynamic evolution.
-
-There is a need to support the configuration of the previously described new measurement configurations specific to NR NTN introduced in Release 17, such as the new SSB Measurement Timing Configuration (SMTC) or SMTC4 (*SSB-MTC4List-r17*). In addition, the NTN cells must be able to broadcast Satellite Assistance information, in particular Satellite Ephemeris, in the form of SIB19, containing serving and neighbor satellite and cell information. Furthermore, in order to trigger a HO, the gNB must be able to include specific SIB19 content in the HO triggers.
-
-These could be implemented by extending the existing support for measConfig and configuration of HO that is found in E2 Service Model RAN Control, as well as investigating new mechanisms either via E2 or O1 to deliver SIB19 information to gNB from the RIC/SMO.
-
-### 5.2.3 Use Case 2-2: NTN QoS-based inter-cell traffic steering and load balancing
-
-#### 5.2.3.1 Use Case description
-
-This use case covers the use of an NTN RIC, specifically a Near-RT RIC and xApp(s) to support the implementation of traffic steering and load balancing for administrative and network optimization reasons in an NTN network supporting NR NTN with satellite access via Release 17 and above. This use case is similar to the Traffic Steering Use Case described in the O-RAN Alliance WG1 Use Cases Analysis Report, however it focuses on Non-Terrestrial Networks (NTN) with satellite access and includes Load Balancing, as well as explicit awareness of orbits, orbital dynamics, cell load and QoS.
-
-The current O-RAN use case definitions on Traffic Steering and QoS-aware scheduling do not take into account issues specific to NTN deployments, satellite or otherwise.
-
-This use case's applicability is not limited to a specific orbit, and is instead applicable to any GSO or NGSO orbit, including but not limited to GEO, MEO and LEO. This use case can also apply to multi-orbit scenarios (e.g. GEO + LEO, GEO + MEO, etc), where different orbit types are specified in 3GPP as different RAT types. The scope of inter-RAT Traffic Steering and Load Balancing for this use case is presently focused on 5G NR RAT types where the RAT type is used to differentiate the NTN orbit.
-
-#### 5.2.3.2 Problem statement and challenges
-
-It is well understood that in terrestrial cellular networks, imbalances in the traffic load across different cells, or differences in their available bandwidth and QoS capabilities, can lead to network hotspots, network congestion, suboptimal spectrum utilization and negative impact on the user experience due to for example increased latency.
-
-It is also understood that networks may provide access to users with diverse profiles, as well as support different types of services and their associated requirements.
-
-This challenge is tackled in the terrestrial domain by the RICs evaluating the QoS targets of the various DRBs/UEs as well as the current resource utilization in the network to determine whether there are sufficient resources allocated in the correct locations to meet the QoS requirements of users.
-
-In NTN deployments, particularly those in Low Earth Orbit (LEO), the inherent movement of satellites means that components of the RAN, the air interface and even its transport might no longer traverse deterministic fibre optic connections, but rather wireless links between various space and ground assets of the NTN network which are likely to have time- and space-variant properties, such as high mobility, bandwidth constraints, high, variable or diverse delay, as well as potentially low reliability.
-
-Even in 3GPP Release 17/18 specifications, which mostly focus on transparent/bent-pipe architectures, even though the entire RAN and the interconnections between its associated RAN Network Functions are placed on Earth, the NR Uu air interface has to traverse at least one transparent satellite hop via a radio feeder and user link, which can induce a series of time-variant impairments and latencies that impact the network's (and a RIC's and xApp's) ability to appropriately steer and load balance traffic in sync with the RAN scheduler.
-
-It is also worth noting that traffic steering methodologies have been devised to achieve intelligent mapping of UEs to cells with an assumption that the cells might be at worst macro and micro cells, or more typically closely adjacent and similar tier cells. In the NTN context, on the other hand, the scenarios might involve networks with multiple orbits, where UEs in a given region could be split between GSO and NGSO segments, as well as within NGSO networks where different types of UEs in the same cell could be best served by different NGSO satellites depending on their specific connectivity requirements (e.g. eMBB vs URLLC) as well as the dynamic state of the network. This diversity of access layers may create significant differences in the latency, mobility, capacity, coverage area as well as several other factors.
-
-Lastly, in terrestrial macro mobile networks, UEs with specialized characteristics and vertical-specific QoS requirements might be a comparatively small minority as opposed to eMBB smartphone users, at least in a given area of the network or band group. In NTN, on the other hand, this diversity is expected to be quite significant, both in terms of a mix of handheld (e.g. smartphone) and non-handheld UE (e.g. automotive, CPE, UAV, etc) even within the same cell, frequency band and RAT.
-
-This makes it such that a number of aspects introduced by the nature of NTN systems, and that will be impacting the ability of the RIC to perform accurate traffic steering and load-balancing, are not yet accounted for in the O-RAN specifications, and thus require further analysis.
-
-#### 5.2.3.3 Proposed Solution
-
-5G NTN aims to primarily serve UEs in rural outdoors environments where limited LoS obstruction on the ground, limited multipath effects and the predictable movement of the satellite in the sky coupled with accurate weather forecast data means that the channel quality can be more reliably modelled and estimated. Such a capability would allow an xApp/rApp solution to not only rely on instantaneous signal measurements, but also to perform modelling of the user and feeder link channel qualities as their link vectors change due to the orbital movement of the satellite. Additionally, by having access to information about the Satellite Transport Network such as the possible or currently employed antenna configurations onboard the satellites and the scheduled feeder link handovers, an xApp/rApp solution could obtain this cognisance of the downstream impacts of steering specific types of traffic and services in different ways.
-
-For example, upon handover opportunities for a specific UE which are “forced” such as those that occur because the current serving satellite is dropping below the horizon, the xApp/rApp could perform channel modelling and predictions on the array of potential user and feeder link vector pairs which could be employed for that UE during the viable service time of that user-feeder link pair (i.e. prior to the next necessary user or feeder link handover). From this, it could derive which handover opportunity for a given UE/group of UEs would result in a service time during which the highest attainable spectral efficiency would be achieved on the user/feeder link pair, which would be the criterion on the basis of which DRBs and associated UEs with eMBB type of QoS flow targets would be managed. In parallel, for those UEs which are requesting a URLLC type of service, the xApp/rApp would also take into account any associated packet delay budget requirements which would have to be enforced, while also attempting to evaluate which of the candidate handover opportunities could deliver service the longest before either a user or feeder link handover would require temporary service disruption.
-
-In cases of significant congestion, the xApp/rApp would prioritise those UEs and QoS targets which are regarded as being of highest priority, and would use other measures such as those defined in the existing QoS-based resource optimisation use case in WG3 UCR to find alternate solutions for those UEs whose QoS targets cannot be met in the current network state. To support the kinds of Conditional Handovers which are crucial for NTN mobility, as was highlighted in Use Case 2-3 in Clause 5.2.4, the current interface specification(s) would need to be extended. Lastly, if only a subset of potential satellites are relevant handover candidates for a UE consuming a specific type of service, the xApp/rApp solution would aim to decrease the overall power consumption and signaling overhead on behalf of the UE and RAN by constraining the SIB19 contents (e.g. ntn-NeighCellConfigList) and SMTC4 configuration to only produce Measurement Reports for those satellites which are determined to be relevant.
-
-Subsequently, one of the handover capabilities defined in Use Case 2-3 in Clause 5.2.4 could be used to facilitate the handovers.
-
-**Table 5.2.3.3-1: NTN QoS-based inter-cell traffic steering and load balancing**
-
-| Use Case Stage | Evolution / Specification | <> Related use |
-|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
-| Goal | Find best candidate serving satellites/cells to best meet QoS requirements for a variety of UEs while utilizing the least amount of radio resources in the network | |
-| Actors and Roles | Non-RT RIC, NTN QoS-aware Traffic Steering and Load Balancing rApp, Near-RT RIC, NTN QoS-aware Traffic Steering and Load Balancing xApp, E2 Nodes. | |
-| Assumptions | All relevant functions and components are instantiated. UE is already in the NTN segment and served by the NTN network.
The NTN RIC is aware of the state and motion of the constellation and is capable of predicting its evolution in time and space. | |
-| Pre-conditions | A1/E2 interface connectivity is established, QoS xApp has access to live source of global weather data | |
-| Begins when | Operator specified trigger condition or event is satisfied. | |
-| Step 1 (M) | Non-RT RIC sends the QoS optimization policy for UEs to Near-RT RIC via A1 interface. | |
-| Step 2 (M) | NTN QoS Optimization xApp/Near-RT RIC subscribes to performance metrics, UE information change and message event of | |
-
-| | | |
-|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
-| | UE mobility from E2 Nodes to understand the state of the network and location of UEs within it. | |
-| Step 3 (M) | NTN E2 Nodes report performance metrics, UE information change and message event of UE mobility to NTN QoS Optimization xApp /Near-RT RIC. | |
-| Step 4 (M) | NTN QoS Optimization xApp/Near-RT RIC performs analysis of collected information and determine the candidate serving satellites/cells with its digital twin or AI/ML model. | |
-| Step 5 (O) | NTN QoS Optimization xApp/Near-RT RIC signals to NTN E2 Nodes to establish signal measurement and reporting in UEs for candidate handover opportunities | |
-| Step 6 (O) | E2 nodes configures measurement control to UEs and UEs perform measurements and monitor for configured measurement events, upon which they signal a measurement report to the serving NTN E2 Node | |
-| Step 7 (O) | NTN E2 Nodes forward the measurement report to NTN QoS Optimization xApp/Near-RT RIC | |
-| Step 8 (M) | NTN QoS Optimization xApp/Near-RT RIC performs analysis of collected updated information and make the decision of handover to target serving satellites/cells with its digital twin or AI/ML model. | |
-| Step 9 (M) | NTN QoS Optimization xApp/Near-RT RIC signals to NTN E2 Node to establish the correct handover control to the target UE | |
-| Step 10 (M) | NTN E2 Nodes configure measurement control to UE for current serving satellite/cell. | |
-| Step 11 (M) | NTN QoS Optimization xApp/Near-RT RIC continuously signals to Non-RT RIC feedback on enforcement status of defined QoS requirements | |
-
-```
-
-@startuml qos optimization
-title NTN QoS Optimization Use Case
-Skin rose
-skinparam sequenceMessageAlign left
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-box "SMO Framework" #gold
-participant "Non-RT RIC" as nonrtric
-end box
-
-box "NTN Segment" #cyan
-participant "NTN QoS Optimization xApp/Near-RT RIC" as xappnearrtric
-participant "NTN E2 Nodes" as e2nodes
-end box
-
-autonumber
-
-nonrtric -> xappnearrtric : Non-RT RIC sends the QoS optimization policy for UEs.
-
-group #White NTN QoS Optimization xApp/Near-RT RIC collect UE information
-xappnearrtric -> e2nodes: Subscribe to cell performance metrics, UE information change and message event of UE mobility
-
-```
-
-```
-
-e2nodes -> xappnearrric: Report cell performance metrics, UE information change and message
-event of UE mobility
-end group
-note over xappnearrric: Perform analysis according to current cell-level resource usage, \nper-
-DRB QoS requirements and future-looking and weather-dependent \nlink budget analysis to derive
-candidate per-UE handover opportunities
-
-group #White NTN QoS Optimization xApp/Near-RT RIC establish signal measurement and reporting
-for candidate handover opportunities
-xappnearrric -> e2nodes: Set up signal measurement and reporting configuration per-UE/per-
-cell
-note over e2nodes: Configure measurement control for candidate serving satellites/cells and \nUE
-report measurement result of candidate serving satellites/cells to E2 nodes
-e2nodes -> xappnearrric: Report the measurement result
-end group
-
-note over xappnearrric : Take into account measurement reports to derive target handover
-occasion
-xappnearrric -> e2nodes: Per-UE network-initiated handover or CHO configuration
-note over e2nodes: Network initiated handover
-xappnearrric -> nonrric: QoS policy feedback
-
-@enduml
-
-```
-
-
-
-UML sequence diagram titled 'NTN QoS Optimization Use Case'. It shows interactions between SMO Framework (Non-RT RIC), NTN Segment (NTN QoS Optimization xApp/Near-RT RIC), and NTN E2 Nodes. The sequence includes: 1. Non-RT RIC sends QoS optimization policy; 2. xApp subscribes to metrics; 3. E2 nodes report metrics; 4. xApp establishes measurement configuration; 5. E2 nodes report results; 6. xApp initiates handover; 7. xApp sends policy feedback. Callouts explain the analysis and configuration steps.
-
-Figure 5.2.3.3-1 UML flow chart of use case of NTN QoS-based resource optimization and traffic steering
-
-Sample required data:
-
-1. QoS Optimization policy
- - a. Guaranteed Flow Bit Rate (GFBR)
- - b. Maximum Flow Bit Rate (MFBR)
- - c. Priority Level
- - d. Packet Delay Budget (PDB)
-2. Metrics and information reporting
- - a. Performance metrics
- - i. Average DL/UL UE throughput
- - ii. Mean DL/UL PRB used for data traffic
- - iii. Packet Delay
- - iv. DL Synchronization Signal based Reference Signal Received Power (SS-RSRP)
- - v. DL Synchronization Signal based Signal to Noise and Interference Ratio (SS-SINR)
- - b. UE information changes
- - i. UE ID
- - ii. UE RRC state
-
-#### 5.2.3.4 Benefits
-
-Employing limited network resources to communicate information is naturally at the centre of mobile networks, and especially critical for NTN. By leveraging access to network telemetry as well as employing accurate models of the behaviour of the system components and channel(s) to produce prediction-based data-driven decisions, the adoption of an O-RAN RIC and xApp-driven NTN control plane would lead to overall increase in efficiency of the system, lower spectral and power usage in the network, both from the aspect of achieving higher MCS on link vectors, as well as exhausting fewer resources.
-
-This is expected to also lead to a higher overall rate of satisfied QoS and QoE requirements by increasing the number of fulfilled service targets with the same amount of resources, in turn improving the overall commercial viability of the SNO's NTN operations.
-
-#### 5.2.3.5 Impact on O-RAN WGs
-
-The use case brings forth an NTN-specific angle and approach to Traffic Steering and QoS-based optimization use cases which were already addressed for terrestrial networks in WG2 and WG3. While the 5G QoS framework has not changed significantly for NTN, there is a need to support the configuration of NTN-specific network-controlled HO for traffic-steering and load-balancing purposes. For the SIB19 component, an opportunity exists for an xApp/rApp to update the relevant RAN nodes with some of the contents of the System Information Block 19 (e.g. Satellite Assistance Information and Ephemeris, neighbor satellite and cell configurations, k\_offset, etc) which it ought to broadcast in the cell or unicast to specific users during HO command.
-
-### 5.2.4 Use Case 2-3: NTN Time-based and Distance-based Conditional Handover (CHO)
-
-#### 5.2.4.1 Use Case Description
-
-This use case covers the support of the new Time-based and Distance-based Connected Mode Conditional Handovers (CHO) introduced in 3GPP for NR NTN since Release 18.
-
-The handover end-to-end call flow requires a sequence of signaling exchanges between the UE, its serving cell and a target neighboring cell to take place in order for the full procedure to be successful. In an event where the UE loses connectivity to its serving cell before it has received the required instructions to join the target cell, this could inhibit it from successfully undergoing a handover in RRC Connected Mode. Such an event is largely avoided in terrestrial networks by tailoring the signal measurement event on the serving cell to be triggered before its signal becomes too weak, but can become more likely to occur in 5G NTN constellations where the physical mobility of the satellites could mean that one which is currently delivering a cell to a specific location on the ground would all of a sudden become unable or ineligible to continue doing so, interrupting the procedure. This risk is only made higher by the increased control plane latencies witnessed in NTN networks, especially in transparent NTN systems where the RTT could be quite long, and when coupled with any additional processing time on the UE and RAN it might leave the UE(s) with insufficient time to receive the command to initiate the Random Access procedure prior to losing connectivity to the serving cell.
-
-To account for such events, 3GPP has extended the capabilities of the Conditional Handover (CHO) with support for Time-based and distance-based CHO configurations in the UE, in which its serving cell can preauthorize the UE to initiate the handover to a neighbor cell under conditions which are precomputed, and which provide the UE(s) with sufficient opportunity to undergo a successful handover, while not attempting it either before the neighboring cell becomes available or unnecessarily early, the latter of which would increase the frequency of handovers which are a costly procedure. This functionality is particularly relevant in NTN because the difference in signal strength owed to the UE being located at the cell center versus the cell edge is not as pronounced as it would be in terrestrial networks, as discussed in Use Case 2-1 in Clause 5.2.2, and is an insufficient trigger to determine the necessity for a handover to take place. The Time-based and Distance-based triggers on the other hand do not account for what could be a potentially ephemeral drop in signal quality of the serving cell as more traditional signal measurement triggers might, but rather communicate that there is a hard limitation to the currently serving cell's ability to sustain service to the UE. By applying this configuration to all UEs in a cell, significant reductions in signaling overhead can be achieved compared to the regular handover scenario.
-
-The Time-based and Distance-based CHO, introduced in 3GPP Release 17 as *condEventT1* and *condEventD1* in 3GPP TS 38.331 [1], have their applicability in both Earth-Moving Cell (EMC), and Earth Fixed Cell and quasi-Earth Fixed Cell (both addressed as EFC hereafter) applications, as discussed below.
-
-#### 5.2.4.3 Problem Statement and challenges
-
-##### 5.2.4.3.1 Time-based CHO
-
-Accounting for Earth-Moving Cell based systems first, NTN constellations in NGSO employing the EMC configuration include satellites which project beams onto the Earth which are fixed to the body of the satellite itself, and are effectively sweeping over the Earth underneath. Even though the individual beams can be hundreds of kilometers in diameter, the high orbital velocity of a satellite that is for instance in LEO would mean that a UE would enter into the coverage of a single beam and exit it within the order to seconds (depending on factors like satellite elevation angle, angular beam width, satellite altitude, etc.).
-
-This is exemplified in the Figure 5.2.4.3.1-6 below, showing a simplified representation of UE (orange point) mobility between cells illuminated by two NTN LEO satellites (blue and green points), applicable to both Transparent and Regenerative architectures, employing Earth-Moving Cells.
-
-
-
-Figure 5.2.4.3.1-1: EMC inter-satellite handover scenario. The figure consists of three sequential satellite images of the Earth, showing the movement of a User Equipment (UE) represented by an orange dot. The UE is initially covered by a cell (PCI 3) from a blue satellite. As the satellite moves, the UE moves into the coverage area of a green satellite, which provides a new cell (PCI 10). The handover occurs between these two cells. The figure illustrates the inter-satellite handover scenario where the UE moves from one satellite's coverage to another's.
-
-**Figure 5.2.4.3.1-1: EMC inter-satellite handover scenario**
-
-In the first instance, the handovers occur between cells illuminated by the same satellite, exemplified as the blue satellite in Figure 5.2.4.3.1-1. In a Regenerative architecture, these would most often involve cells which belong to the same onboard gNB and would constitute intra-gNB handovers. In Transparent architectures, the same could be the case (successive cells belong to same gNB on the ground), or the satellite could be connected via multiple feeder links to different gateways and gNBs, in which case successive beams could carry cells delivered by different gNBs and would therefore constitute an inter-gNB handover. Nevertheless, eventually the UE would be covered by one of the “outer” beams of a single satellite after which there is no further beam arriving from the same satellite. In this event, there needs to be another satellite coming either in succession in the same orbital plane or from another crossing orbital plane (the green satellite in the same Figure) which can resume service to the UE with a new beam and cell. Again, depending on the architecture employed, this could either lead to an intra- or inter-gNB handover. As discussed before, signal measurement-based handover mechanisms would be insufficient to drive this type of mobility. Because of the frequency of handovers and the potential high number of UEs on the ground, significant signaling overheads would be generated as the UEs are being swept by different beams and cells. Time-based CHO was introduced in 3GPP to address exactly this.
-
-Even if the satellites in the NTN constellation are capable of beam steering, allowing them to illuminate and track Earth-Fixed Cells, there is still a fundamental limitation whereby a satellite in LEO would eventually fall beneath the minimum elevation angle, causing it to stop illuminating a 5G cell over the EFC, and the EFC would need to be handed over to a 5G cell served via a subsequent satellite. The two satellites could provide overlapping service with their respective cells for a short period of time during the handover of the EFC from one to the other, but they need not to, and the coverage can even be discontinuous in time as long as the associated timers (e.g. T304, T310) do not expire before the UEs in the EFC connect to the subsequent cell, causing RLF. This type of handover of entire EFCs (and constituent UEs) is applicable to Transparent architectures where different gNBs on the ground deliver successive cells via different gateways and satellites, where the same gNB delivers successive cells via different gateways and satellites, as well as in cases where two different gNBs via different gateways form feeder links with the same Transparent satellite that illuminates both of the successive cells onto the same EFC. It is also applicable to Regenerative architectures where the gNB is placed onboard the satellite, and the two gNBs/satellites deliver successive cells to the same EFC.
-
-The Figure 5.2.4.3.1-2 below showcases a simplified view of the above scenarios from the point of view of the satellite user links (omitting gateways and feeder links), whereby the orange UE is initially served by a cell delivered via the blue satellite (PCI 3). As the blue satellite is progressing along its orbit due North-East, it is nearing the moment where it will no longer be capable of illuminating and tracking the EFC in which the orange UE is located. At the same time, the red LEO satellite is
-
-coming into view, moving due South-East, and can resume the service to the EFC. It would deploy a new cell on top of the EFC (PCI 13), either with overlapped or discontinuous service.
-
-
-
-Figure 5.2.4.3.1-2: EFC inter-satellite handover scenario. The figure consists of three sequential satellite images of the Earth showing the movement of a satellite beam. In the first image, a blue hexagonal coverage area labeled 'PCI 3' is shown. In the second image, the beam has moved, and a new red hexagonal coverage area labeled 'PCI 13' is appearing, overlapping with the previous one. In the third image, the beam is fully on the new cell labeled 'PCI 13'.
-
-**Figure 5.2.4.3.1-2: EFC inter-satellite handover scenario**
-
-Yet again, the need for a handover is not driven by variable signal quality by serving and candidate neighboring cells, but either by a hard limitation to the serving cell's ability to sustain service to the EFC in question, or a higher layer decision by an NTN optimization xApp to redirect the blue satellite's beam and power resources to provide coverage onto another EFC, even if the blue satellite could sustain coverage to the original EFC for a longer period of time. While UEs in EFCs would nominally undergo handovers less frequently compared to UEs in EMCs, risks owing to the reliability of just-in-time control plane signaling delivery and overall impacts on signaling overhead can be mitigated through the employment of Time-based CHO to drive handovers, where the exact moment of handover can be precomputed and delivered ahead of time to the NTN gNB, who would signal it to the UEs in the EFC in question.
-
-##### 5.2.4.3.2 Distance-based CHO
-
-While the ephemeral nature of satellite coverage over a given region defines the time bounds between which UEs in the region in question can be served, there are also other determinants which might cause a UE to exit coverage of one cell or beam, and necessitate a handover to another cell or beam, if present. One of these determinants is spatial in nature; namely, a UE's physical location with respect to the spatial coverage footprint of a satellite beam via which the serving cell is illuminated will determine if the UE can continue to be served by that cell. By the same logic, a UE's physical location with respect to that of a neighboring beam and cell will determine if the UE can be handed over to that cell.
-
-Focusing on EMC-based systems first, this determinant can be exemplified by reusing Figure 5.2.4.3.1-1. With considerations on whether the architecture is Transparent or Regenerative being equal to the Time-based CHO EMC case, the coverage beams of NGSO satellites for which the EMC scenario applies are often approximated using hexagons, but their illumination footprints are in practice more circular in nature, with overlapping coverage towards the circular beams' edges. Therefore, the footprint area can be nominally defined using the circular footprint's center and radius (this holds true best when satellites are directly at zenith over a coverage region; at lower elevation angles the beam footprint illuminates the Earth's surface at an angle, causing the effective footprint to be more oval). Focusing on Figure 5.2.4.3.1-1, the orange UE is initially inside the satellite beam and cell with PCI 3. As the blue satellite traverses overhead along its orbital path, at one point the orange UE, even if stationary, will find itself more than the radius distance away from the moving center of the cell with PCI 3 (implicitly exiting its coverage), and less than the radius distance away from the moving center of the neighboring cell with PCI 4 (implicitly entering its coverage). With the expected slight overlap of the beams, there is a short period of time during which the UE can be expected to be in coverage of both cells. As was the case with Time-based CHO, relying on signal measurements from the serving and neighboring cell(s) to drive such mobility cases is insufficient, and the legacy handover procedure can be expected to meaningfully contribute to signalling overhead and reduce the robustness of the handover procedure in an NTN scenario. For this purpose, the Distance-based CHO mechanism was extended in 3GPP Release 18 to support EMC cases.
-
-The Distance-based CHO mechanism was in fact originally introduced in 3GPP Release 17 in support of EFC-based systems. In contrast to EMC, satellite beams and cells are fixed to the Earth and so, while their footprints can still be approximated as circles with a center and radius, the footprints' centers are stationary. Nevertheless, the UEs themselves could be moving, and with them their distance from the serving and neighboring cell centers could be changing. At one point, a UE will have moved outside the effective coverage of its currently serving cell, and into that of another neighboring cell, if present, leading to a handover event.
-
-Taking Figure 5.2.4.3.2-3 as an example scenario, the orange UE is initially located inside the blue cell with PCI 6. After some time, due to the UE's mobility, it will have travelled due North and crossed over into the coverage of the blue cell with PCI 3. At this point, the UE becomes closer to the center of the cell with PCI 3 than to that of the cell with PCI 6. Similar to the explanation for EFC in Time-based CHO scenarios, the blue satellite could either be Regenerative and the handover between two blue cells would be an intra-gNB handover, or the blue satellite could be Transparent, potentially forming one or more feeder links to one or more gNBs, depending on which the handover could be intra- or inter-gNB.
-
-
-
-Figure 5.2.4.3.2-3: EFC inter-beam handover scenario. The figure consists of three sequential maps of Spain showing the movement of an orange UE (User Equipment) across different satellite coverage areas. The coverage areas are represented by colored hexagons: blue (PCI 1-7) and green (PCI 8-14). In the first map, the UE is in the blue cell with PCI 6. In the second map, it has moved north into the blue cell with PCI 3. In the third map, it is closer to the center of the PCI 3 cell. Dashed lines indicate the orbital paths of the satellites.
-
-**Figure 5.2.4.3.2-3: EFC inter-beam handover scenario**
-
-Once in the blue cell with PCI 6, after some time the orange UE might move Eastwards towards the area which is covered by the green cell with PCI 12, coming from the green satellite. Once more, the overall architecture at play would influence what type of handover this is. If the blue and green satellites are Regenerative, this would be an inter-gNB handover while if they are Transparent, the same could be the case or both might even be connected via feeder links to the same gNB, implying an intra-gNB handover.
-
-The current E2SM-RC [2] specification does not presently support Time-based and Distance-based measurement and Conditional Handover events (e.g. *condEventT1*, *condEventD1* and *condEventD2* in TS 38.331[1]) required for the Near-RT RIC to implement the new NTN-specific Time-based and Distance-based Conditional Handover (CHO) procedures introduced by 3GPP in Release 17 and Release 18.
-
-As described previously, this can lead to a high signaling load, especially in Earth-Moving Cells (EMC) systems, whenever the satellite exits the coverage area and all the UEs within the cell need to be handed over. For high-speed UEs (e.g. aircraft, fast UAV), due to the signal profile in an NTN cell, this could lead to the call being dropped in case the traditional HO procedure cannot be sufficiently responsive as the UE reaches the cell edge, causing it to hit Radio Link Failure (RLF).
-
-#### 5.2.4.4 Proposed Solution
-
-##### 5.2.4.4.1 Time-based CHO
-
-Addressing the EMC case first, whether the system is Transparent or Regenerative, 3GPP has not provisioned or accounted for the NTN gNBs to have the ability to keep track of which satellites, and by proxy which EMC cells, are valid neighboring candidates for handover in a continuously evolving system such as an NGSO NTN constellation. This is exemplified in the simplified Figure 5.2.4.3.1-6 but would be even more pronounced in a denser deployment, as it would be in a real constellation.
-
-The blue satellite in the Figure, orbiting due North-East along its orbit, is the one which is initially serving the orange UE via the cell with PCI 3. Following 3GPP Release 17, the NTN gNB, as prompted by the NTN xApp via the E2 interface, can instruct the UE with GNSS capabilities to record coarse location information (with ~2 km accuracy) and report it to the NTN gNB [1], who subsequently uses the E2 interface to deliver it to the NTN Near-RT RIC and the NTN xApp. By knowing the coarse coordinates of the UE as well as using the digital twin to derive the coverage footprints of the individual cells/beams delivered by the blue satellite, the NTN xApp can compute the remaining service time of the cell with PCI 3 after which the UE needs to be handed over to the cell with PCI 4, and subsequently to the cell with PCI 5. These derived remaining service times and handover target cells are UE-specific even within the same cell (e.g. PCI 3) as the relative location of different UEs within the same cell would define their mobility opportunities. For instance, if the UE in Figure 5.2.4.3.1-6 was instead in the North-West corner of the cell with PCI 3 in the initial view, its target handover cell would instead be the cell with PCI 1, and the handover would need to occur sooner due to the shape of the beam and cell with PCI 3.
-
-The NTN xApp would instruct the NTN gNB delivering the cell with PCI 3 to configure the orange UE with the T1 CHO (*condEventT1* [1]) conditions that would signal to it the time interval during which it ought to attempt to connect to the cell that is subsequent to it, the one with PCI 4, as well as with appropriate SIB19 parameters to be broadcast that would contain the *ntn-Config-r17* of all of the neighboring cells, itself containing the *epochTime-r17* and *ephemerisInfo-r17* of the blue satellite, among other parameters. Taking the cell with PCI 3 from the above Figure as an example, its neighboring cells would be cells with PCI 1, PCI 4 and PCI 6.
-
-After some time, the orange UE enters the trailing beam/cell of the blue satellite (PCI 5) after which it needs to be handed over to a cell illuminated by another satellite, in this instance the green one (first cell being one with PCI 14). The NTN Near-RT RIC and NTN xApp would yet again combine coarse UE location information and digital twin modelling of the NTN constellation to produce the T1 CHO (*condEventT1*) and SIB19 parameters which aid the handover from blue cell with PCI 5 to the green cell with PCI 14. This could be coupled with another condition, such as one that is dependent on the signal quality of the neighboring cell exceeding some nominal value to ensure that the handover stands a greater chance of success (e.g. *condEventA3*, *condEventA4*, *condEventA5*) for which the SMTC4 configuration defined for NTN is employed (or otherwise can be used to pre-synchronize with the neighboring SS/PBCH transmissions). Furthermore, the overlapping coverage from multiple satellites also necessitates close coordination of which frequencies are employed by which cell in order to avoid interference, and the question of which are permitted to be employed is in many cases dependent on the region of the Earth that is being illuminated. Therefore, there is a further need for a higher order NTN control function, such as an NTN Near-RT RIC and constituent NTN xApp(s), to drive this functionality.
-
-As for the EFC case, in good time prior to the scheduled discontinuation of coverage to the EFC by the blue cell with PCI 3, the NTN Near-RT RIC and NTN xApp would instruct via the E2 interface the NTN gNB to configure the UEs in the cell with the appropriate T1 CHO (*condEventT1*) configuration, potentially in conjunction with signal measurement-based CHO configurations (e.g. *condEventA3*, *condEventA4*, *condEventA5*). As was the case in the EMC instance, the NTN xApp will infer, if not decide itself, through the NTN digital twin and forward-looking scheduling that it will be the red satellite which will deploy a particular cell (PCI 13) at a particular moment over that EFC in order to continue providing service, and will have therefore provisioned the T1 CHO configurations in good time prior to the handover occasion taking place, taking into account any dependency on signaling delays induced by the RTT influenced by the orbital regime and Transparent vs. Regenerative nature of the constellation. Likewise, this will need to be accompanied with the updated SIB19 containing the *ntn-Config-r17* which will indicate to the UE crucial information about the cell with PCI 13 and the red satellite, such as its ephemeris information, enabling the UE to synchronize with it.
-
-In the event that there is a significant number of UEs in the blue cell with PCI 3, their handing over to the red cell with PCI 13 during the potential overlap period should be managed carefully in order to reduce the chances of preamble collisions, contention resolution delays, etc. Since the two satellite beams and cells in question are intended to cover the same EFC, the relative location of different UEs within the EFC would not play as much of a role as it did in the EMC case, as all of the UEs would be affected by the withdrawal of the blue cell with PCI 3 and illumination of the red cell with PCI 13 in the same manner and time (there is an edge case where this need not be true; if the elevation angles of the blue and red satellites cause their beam footprints and therefore cell coverages on top of the EFC at the moment of handover to be of different shapes, excluding certain UEs). In this respect, the same T1 CHO parameters could be configured for all of the UEs within the same cell. Nevertheless, in order to balance the RA load onto the red cell with PCI 13, the NTN Near-RT RIC and NTN xApp(s) can theoretically alter the duration of any overlap or discontinuity of service to the EFC (T310 timer for RLF in UEs starts as blue cell shuts off – UEs must perform RA to the red cell prior to expiry to avoid exiting RRC Connected Mode) as well as tune the per-UE group RACH-Config and T1 CHO parameters to better distribute their RA across the red cell's RACH occasions.
-
-##### 5.2.4.4.1 Distance-based CHO
-
-Focusing again on the EMC case first, and with respect to the scenario in Figure 5.2.4.3.1-6, the UE is initially served by the blue satellite via the beam and cell with PCI 3. It requires a mechanism by which to evaluate its distance from the moving locations which represent its current serving cell and a candidate neighboring cell in an EMC system. In 3GPP Release 18, a new CHO configuration was introduced, called D2 CHO (*condEventD2* [1]), for this purpose. This allows the NTN xApp, by proxy of the E2 interface to the NTN gNB, to specify two distances, *distanceThreshFromReference1-r18* and *distanceThreshFromReference2-r18* alongside a hysteresis distance, to a UE in a cell. The UE is expected to use its GNSS capabilities to ascertain its location, but it also needs the two moving locations to measure and compare its distance to.
-
-At the same time, the NTN xApp can use the E2 interface to deliver to the NTN gNB the parameters which it is supposed to broadcast to UEs in cell with PCI 3 as part of SIB19. Other than including crucial parameters such as *epochTime-r17* and *ephemerisInfo-r17* which are found in the *ntn-Config-r17*, starting from 3GPP Release 18 the SIB19 is also supposed to also include a field called *movingReferenceLocation-r18*. This is supposed to signal to the UEs a serving cell-specific reference location which they are supposed to measure their distance to, and compare it to the *distanceThreshFromReference1-r17* value
-
-provided via the D2 CHO configuration. Nominally this location can be regarded as representing the moving cell center, but strictly speaking need not be, and it is up to the NTN xApp to define what this is going to represent. The *movingReferenceLocation-r18* is in its definition a static point on the ground, timestamped to the *epochTime-r17* from the *ntn-Config-r17*, and the UE is expected to combine this with the *ephemerisInfo-r17* to propagate the satellite's orbital trajectory in the immediate future and ascertain how the *movingReferenceLocation-r18* would move along with the satellite, before it receives the subsequent SIB19 broadcast with the network-updated *movingReferenceLocation-r18*.
-
-The other reference location, the distance to which the UE is measuring using its GNSS-derived coordinates and comparing to the *distanceThreshFromReference2-r17* value provided via the D2 CHO configuration, is delivered inside the *measObjectNR*, namely in the *ntn-NeighbourCellInfo-r18* field, for a specific candidate neighboring cell. Within this field, the neighboring cell's *epochTime-r17*, *ephemerisInfo-r17*, and *referenceLocation-r17* are specified, where the latter is a static location which indicates the reference location at *epochTime-r17*, which the UE can use alongside the *ephemerisInfo-r17* to propagate the satellite's orbital trajectory in the immediate future and ascertain how the *referenceLocation-r17* would move along with the satellite, as was the case with *movingReferenceLocation-r18*.
-
-Once the distance to the *movingReferenceLocation-r18* of the serving cell exceeds the *distanceThreshFromReference1-r17*, and simultaneously the distance to the *referenceLocation-r17* of a neighboring candidate cell drops below the *distanceThreshFromReference2-r17* (taking into account hysteresis in both cases), the UE regards itself as having satisfied the conditions for the D2 CHO, and attempts to join the neighboring cell. Nominally, the NTN xApp does not need to know the coarse location of the UEs in a cell to supply them with the D2 CHO parameters, making the D2 CHO configuration common to all UEs in the cell. Referring to the scenario in Figure 5.2.4.3.1-6, if the UE were to be initially located inside the blue cell with PCI 4, it would be supplied with D2 CHO configurations only for the neighboring blue cells which could at some point in the future (no farther than the *TimeToTrigger* in the D2 CHO config) illuminate the current footprint of the cell with PCI 4. These would be the cells with PCIs 2, 5 and 7, but not the ones with PCIs 1, 3 and 6, since those wouldn't be valid handover candidates due to the movement of the blue satellite. Then, if the serving and various neighboring cell reference locations were tied to the cell centers, the distances supplied in the D2 CHO config would relate to the serving and neighboring cells' radii.
-
-Moving on to EFC-based systems next, and taking the scenario from Figure 5.2.4.3.2-2 as reference, the orange UE is initially located within the blue cell with PCI 6. The NTN xApp is aware of the overall EFC topology of the network, and can infer the cells which are neighbors to the cell with PCI 6. In the simplified example in the Figure, these are the blue cells with PCIs 3, 4, 7 and the green cell with PCI 12. In this instance, the cell centers are not influenced by the movement of the blue and green satellites, but are instead fixed on the ground. For supporting mobility cases where the UE's relative proximity to these reference locations is driven by the mobility of the UE itself, 3GPP introduced in Release 17 support for D1 CHO (*condEventD1* [1]). Within it, the two reference locations (*referenceLocation1-r17* and *referenceLocation2-r17*) and the distance thresholds to the two reference locations (*distanceThreshFromReference1-r17* and *distanceThreshFromReference2-r17*) are defined right in the D1 CHO configuration, and are common for all UEs in the cell. Referring again to the starting position of the orange UE, it receives a D1 CHO configuration for each of the neighboring cells. After some time, the UE moves due North sufficiently such that its distance from the center of the serving cell with PCI 6 (*referenceLocation1-r17*) exceeds the configured *distanceThreshFromReference1-r17*, while its proximity to the center of the neighboring cell with PCI 3 (*referenceLocation2-r17*) drops below the configured *distanceThreshFromReference2-r17*, taking into account hysteresis for both distances. At that point, the D1 CHO configuration for cell with PCI 3 is triggered, and the orange UE attempts to join it, where upon success it becomes configured with the D1 CHO configurations for the new set of neighboring cells (blue cells with PCIs 1, 4 and 6 and green cells with PCIs 9 and 12). The triggering condition could again be coupled with another condition, such as one that is dependent on the signal quality of the neighboring cell exceeding some nominal value to ensure that the handover stands a greater chance of success (e.g. *condEventA3*, *condEventA4*, *condEventA5*) for which the SMTTC4 configuration defined for NTN is employed (or otherwise can be used to pre-synchronize with the neighboring SS/PBCH transmissions). Yet again, after some time, the orange UE moves, this time Eastwards into the coverage footprint of the green cell with PCI 12. Here, the same conditional measurement procedure takes place, and the orange UE eventually joins the cell with PCI 12.
-
-#### 5.2.4.5 Benefits
-
-This would enable the new NTN-specific Time-based and Distance-based Conditional Handover (CHO) procedures introduced by 3GPP in Release 17 and further refined in Release 18. These types of handovers were created specifically for their potential for reduction of the signaling overhead in a cell, by adding flexibility to when the network can trigger UE handovers, allowing the control signaling to be spread over time or sent during low-traffic intervals, in turn improving the user experience and smoothness of mobility. This is especially important for NTN systems with Earth-Moving Cells (EMC) and for fast-moving UEs.
-
-#### 5.2.4.6 Impact on O-RAN WGs
-
-The support for the above solutions would require the introduction of support in the O-RAN E2 interface for the new NTN-specific Time-based and Distance-based Conditional Handover (CHO) procedures introduced by 3GPP in Release 17 and further refined in Release 18 (*condEventT1*, *condEventD1*, and *condEventD2*), with their corresponding new measurement events (*eventD1* and *eventD2*), as defined in TS 38.331 [1]. These would be further augmented by the NTN xApp being able to use the E2 interface to further:
-
-- specify SIB19 parameters to be broadcast by a cell,
-- specify SMTC4 (*SSB-MTC4List-r17*) parameters,
-- specify the *ntn-NeighbourCellInfo-r18* information sent via the *measObjectNR*,
-- configure recording of coarse-grained information about the UEs' GNSS-derived location,
-- subscribe to reports of coarse-grained information about the UEs' GNSS-derived location
-
-The above changes are anticipated to be best hosted in the O-RAN E2SM-RC [2] specification. Further to changes to the E2 interface, an Near-RT RIC optimized for hosting xApps purpose built for NTN optimizations is expected to be required to also expose to the xApps access to an NTN digital twin which the xApps can query to obtain the dynamic and evolving nature of the NTN constellation, including non-3GPP assets such as ground stations and the satellite buses themselves. In addition, such a Near-RT RIC could be required also to expose to the xApps an updated dataset of nowcast and forecast global weather data, which the xApps could be used to calculate prospective radio link conditions if different configurations of the NTN constellation were employed to deliver connectivity to the ground.
-
-### 5.2.5 Use Case 2-4: NTN Idle mode cell re-selection
-
-#### 5.2.5.1 Use Case Description
-
-Void.
-
-#### 5.2.5.3 Problem Statement and challenges
-
-Void.
-
-#### 5.2.5.4 Proposed Solution
-
-Void.
-
-#### 5.2.5.5 Benefits
-
-Void.
-
-#### 5.2.5.6 Impact on O-RAN WGs
-
-Void.
-
-### 5.2.6 Use Case 2-5: NTN UE Location-aware Connected Mode Handover and Inter-cell Traffic Steering and Load-balancing
-
-#### 5.2.6.1 Use Case description
-
-This use case describes leveraging of knowledge of UE location (coarse or fine) by the NTN network to aid mobility (e.g. HOs), as well as other network control procedures such as inter-cell Traffic Steering and Load Balancing.
-
-#### 5.2.6.2 Problem statement and challenges
-
-Normally, in a mobile network it is assumed that handover decisions are taken without awareness of the UE’s location in the network. This is typically sufficient in terrestrial networks because the cells, even macro cells, are in general reasonably small and, in MIMO and other beamforming systems, the spatial granularity of the UE positions within the cell is within the resolution of a single gNB beam in the beamforming matrix. As the number of UE per cell densifies, a typical solution is to aim for ever larger MIMO arrays, thus increasing the spatial resolution (e.g. Massive MIMO).
-
-In addition, heavy multipath environments typical of terrestrial urban networks help the MIMO system by creating very distinct channel transfer functions between each user and the network.
-
-This however is mostly not true for NTN, where each NTN node (e.g. a satellite) should be seen as a single large multi-beam MIMO array, and where each NTN beam is expected to cover a very large geographic area (e.g. several km, 10s or even 100s of km) and thus several UEs or groups of UEs. This has also the collateral effect of creating very large overlap areas between beams/cells, which, coupled with a typically “flat” cell signal distribution per-beam, makes it such that the cell boundaries are more complicated to establish. In addition, the NTN node motion makes it such that, as the NTN node, such as a satellite, flies over the service area, the signal level and quality will naturally vary quite significantly even as seen by a stationary UE.
-
-This creates a number of gaps and problems, such as:
-
-1. Inability of the network to precisely assess when a UE is approaching edge of cell (e.g. due to satellite mobility in EMC scenarios, or UE mobility in all other cases), which can make it difficult to assess whether a UE is about to require handover to an adjacent beam/cell.
-2. Ambiguity in assessing the UE mobility and the signal reporting state across multiple beams/cells, as a UE may report a signal drop even when stationary, due to satellite movement, which can lead to ping-pong effects by making the network wrongly think that a UE is approaching the threshold at which it can be better served by an adjacent cell, beam or NTN node.
-3. Inability of the network of discerning in which portions of the NTN beam (and thus potentially cell) UE are located or clustered, which may force a worst-case resource assignment, and may make it impossible (or very difficult) for the network to assess whether some UE could be offloaded to an adjacent cell/beam or NTN mode (e.g. satellite) to smooth cell load.
-
-All of the above knowledge gaps can create problems and inefficiencies with both mobility, as well as resource assignment and traffic load-balancing at the network level. In all such cases, knowledge of UE locations or clustering, at least at coarse-grained level, by the NTN network, can significantly improve mobility reliability and resource management decisions.
-
-Whilst some of the procedures are technically available since at least Release 16, new NTN-specific procedures have been introduced in Rel-18, and moreover there may be gaps in the O-RAN specifications to prevent full leveraging of existing solutions. Therefore the exact O-RAN specification gaps need to be further investigated.
-
-#### 5.2.6.3 Proposed Solution
-
-Several mechanisms are available for the network to become aware of UE locations, at either coarse- or fine-grained degree.
-
-For example, once the UE is in RRC\_CONNECTED mode and AS security has been established, the network can request the UE to report its GNSS-derived location information, either coarse or fine-grained, through location management procedures either directly to the gNB, or via the Core Network (e.g. LMF).
-
-**Table 5.2.6.3-1: NTN UE-location-aware handover management**
-
-| Use Case Stage | Detailed Information |
-|------------------|---------------------------------------------------------------------------------------------------------------------------|
-| Goal | Find best handover candidate satellites/cells for a UE while utilizing the least amount of radio resources in the network |
-| Actors and Roles | NTN xApp, Near-RT RIC, E2 Nodes, UE. |
-| Assumptions | All relevant functions and components are instantiated. |
-| Pre-conditions | E2 interface connectivity is established, NTN xApp has access to live source of global weather data |
-
-| | |
-|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Step 1 (M) | NTN Handover Optimization xApp/Near-RT RIC subscribes to UE GNSS, UE information change and message copy of UE mobility from E2 Nodes to understand state of the network and location of UEs within it. |
-| Step 2 (M) | NTN E2 Nodes report UE GNSS, UE information change and message copy of UE mobility to NTN QoS Optimization xApp /Near-RT RIC. |
-| Step 3 (M) | E2 Nodes configure measurement control to UEs and UEs perform measurements and monitor for configured measurement events, upon which they signal a measurement report to the serving NTN E2 Node |
-| Step 4 (M) | NTN E2 Nodes forward the measurement report to NTN Handover Optimization xApp/Near-RT RIC |
-| Step 5 (M) | xApp with digital twin analyses the currently employed Ground Station and transparent LEO satellite to derive the remaining service time before a handover must occur. It also evaluates the candidate handover opportunities via available neighbouring satellites and the feeder links they form with Ground Stations that host NTN gNBs to model the link budgets attainable during the service times that they could respectively offer to the UE, and in doing so it selects the neighbouring satellite/cell which is best positioned. |
-| Step 6 (M) | NTN Handover Optimization xApp/Near-RT RIC signals to NTN E2 Node to establish the correct handover control to the target UE |
-| Step 7 (M) | NTN E2 Node implements RRC Connected Mode handover as specified by NTN Handover Optimization xApp/Near-RT RIC |
-
-```
-
-@startuml handover optimization
-title NTN Handover Optimization Use Case
-Skin rose
-skinparam sequenceMessageAlign left
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-box "NTN Segment" #cyan
-participant "NTN HO Optimization xApp/Near-RT RIC" as xappnearrrtric
-participant "NTN E2 Nodes" as e2nodes
-end box
-
-autonumber
-
-group #White NTN Handover Optimization xApp/Near-RT RIC collect RAN metrics
-xappnearrrtric -> e2nodes: Subscribe to UE GNSS, UE information change and message copy of measurement reports
-e2nodes -> xappnearrrtric: Report UE GNSS, UE information change and message copy of measurements events
-end group
-
-group #White NTN Handover Optimization xApp/Near-RT RIC establish signal measurement and reporting config for candidate handover opportunities
-xappnearrrtric -> e2nodes: Set up signal measurement and reporting configuration per-UE/per-cell
-note over e2nodes: Configure measurement control for candidate serving satellites/cells and\nUE report measurement result of candidate serving satellites/cells to E2 nodes
-e2nodes -> xappnearrrtric: Report the measurement result
-end group
-
-note over xappnearrrtric
-xApp with digital twin analyses the currently employed Ground Station and transparent LEO satellite to derive the remaining service time before a handover must occur.
-
-```
-
-```
-
-It also evaluates the candidate handover opportunities
-via available neighbouring satellites and the feeder
-links they form with Ground Stations that host NTN gNBs
-to model the link budgets attainable during the service
-times that they could respectively offer to the UE, and
-in doing so it selects the neighbouring satellite/cell
-which is best positioned.
-end note
-
-note over xappnearrrtric : xApp derives decision to handover\nUE to Neighboring X LEO, served\nnby
-Neighboring X gNB/NTN GW
-
-xappnearrrtric -> e2nodes: Per-UE network-initiated handover or CHO configuration
-note over e2nodes: Network initiated handover
-
-@enduml
-
-```
-
-
-
-UML sequence diagram titled 'NTN Handover Optimization Use Case'. The diagram shows interactions between 'NTN HO Optimization xApp/Near-RT RIC' and 'NTN E2 Nodes'. The sequence includes: 1. Subscription to UE GNSS and measurement reports; 2. Reporting of GNSS and measurement events; 3. Establishment of measurement configuration; 4. Reporting of measurement results; 5. Network-initiated handover or CHO configuration. Callouts explain that the xApp uses a digital twin to analyze Ground Stations and LEO satellites to determine optimal handover candidates based on link budgets and service times.
-
-**Figure 5.2.6.3-1 UML flow chart of use case of NTN UE Location-aware Connected Mode Handover and Inter-cell Traffic Steering and Load-balancing**
-
-#### 5.2.6.4 Benefits
-
-Additionally, the ability for the network to retrieve coarse GNSS location from the UE can help the NTN xApp augment its ability to assess the candidate link vectors for a particular UE.
-
-#### 5.2.6.5 Impact on O-RAN WGs
-
-The current O-RAN E2 specification already supports retrieval of UE location, however, for NTN, there is also a need to enable retrieval of the new parameter for Coarse UE Location introduced in Rel-17 and 18.
-
-# --- 6 Summary and Conclusion
-
-Void
-
-# Annex: Change history/Change request (history)
-
-| Date | Revision | Description |
-|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 2024.12.12 | 00.00.03 | Initial TR skeleton |
-| 2025.02.24 | 00.00.04 | - Add introduction and NTN development status in standard organizations
- The following CRs have been implemented:
- KEY, AAL - CR 0001 – Introduction - v2
- KEY, AAL, FRN – CR 0002 - NTN development status in standard organizations - v3
|
-| 2025.06.17 | 00.00.05 | - Introduction of initial Use Case Group 2 set
- The following CRs have been implemented:
- AAL, KEY, RAD – CR 0004 - Introduction of Use Case Group 2 - v0.6_NOK_AAL
|
-| 2025.06.18 | 00.00.06 | - Update clause 1-3 and change history
- introduction of Use Case Group 1, the following CRs have been implemented:
- KEY, AAL – CR 0005 - fix clause 1-3 and change history - v3
- AAL, KEY, RMI, MTR – CR 0003 - Introduction of Use Case Group 1- v0.12_AtMeeting
|
-| 2025.06.30 | 00.00.08 | - Updates to the overall TR
- Corrections to image references after first round of comments.
|
-| 2025.07.09 | 00.00.09 | Editorial and formatting for first release |
-| 2025.07.21 | 00.00.10 | - Implementation of voting round editorial comments
- Addition of CR references to the Change history/Change request (history)
|
-| 2025.07.22 | 01.00 | First formal release |
-| 2025.10.17 | 01.00.01 | - Merge CRs for update of use case group 2 as below:
- AAL, KEY, RAD CR-0005
- AAL, KEY CR-0007
- Fixed figure and table index
|
-| 2025.12.02 | 01.00.02 | - Fix figure and table index and address comments in review
|
-| 2025.12.02 | 02.00 | November train 2025 release |
\ No newline at end of file
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/031bd5c072298c549b99e157de88dfbf_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/031bd5c072298c549b99e157de88dfbf_img.jpg
deleted file mode 100644
index 2589f806d700e637eda63d49b2a1f626323c5e63..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/031bd5c072298c549b99e157de88dfbf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:69859b5b50dab8a5a1b74b64d360446b09dada7be97c7f5361d3b2005d4eb182
-size 83358
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
deleted file mode 100644
index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:79608603c3aa9e126495e2659c247dca745e88ba92d5a4759353b5984132c6f9
-size 4505
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg
deleted file mode 100644
index 49b24ea246a7fce35493cfff7ea6e65536601038..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e07cfb8ce0148f9eed97ed0599cb221b242368e635c11c0cae003512d5f2c89b
-size 69298
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
deleted file mode 100644
index 48cd6cfd9c032028ecea17ac6d538f30bac4d582..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:292d6ac1952660b7ba8f4f37ebc0c91b47ec10150df069f1c076acb93831329c
-size 148360
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg
deleted file mode 100644
index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e651e0bddb05f1e829f9f354306f4087bedfa5b6246ea795fafd57b8ced34090
-size 4555
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/39ca823ef41ba00da416ecc099940770_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/39ca823ef41ba00da416ecc099940770_img.jpg
deleted file mode 100644
index 9274343b6483be1d6ace841b51ab2d0256859726..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/39ca823ef41ba00da416ecc099940770_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:948a7cbea397dea122b02c95df55244316bfbf355b1eb0d2e1edef1cde514d30
-size 81355
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg
deleted file mode 100644
index 6134992ce9c5d512e70c1e2ff37d9530ef08bf5d..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:29c293be93061ac43373e0b12fce4fa52bb5d92014cdb5cb7d6a095b5c12b421
-size 4518
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/4a04896dfb569893fba50729314024f5_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/4a04896dfb569893fba50729314024f5_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
deleted file mode 100644
index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4f6d08444a1dddff6009753a3442a2f3b4f55c9e91148537a2e5ff7d08c3c4ed
-size 4533
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/5ae3023386ee15fae372871afce28865_img.jpg
deleted file mode 100644
index 6a69c912b93b852487847aaabc8e3d63616636f7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/5ae3023386ee15fae372871afce28865_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:d8c8ea95f7110d60340c07156aac78589dd81598e05be6a695a028106dcbdc3c
-size 4604
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg
deleted file mode 100644
index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4f6d08444a1dddff6009753a3442a2f3b4f55c9e91148537a2e5ff7d08c3c4ed
-size 4533
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
deleted file mode 100644
index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e651e0bddb05f1e829f9f354306f4087bedfa5b6246ea795fafd57b8ced34090
-size 4555
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg
deleted file mode 100644
index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e651e0bddb05f1e829f9f354306f4087bedfa5b6246ea795fafd57b8ced34090
-size 4555
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg
deleted file mode 100644
index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e651e0bddb05f1e829f9f354306f4087bedfa5b6246ea795fafd57b8ced34090
-size 4555
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg
deleted file mode 100644
index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4f6d08444a1dddff6009753a3442a2f3b4f55c9e91148537a2e5ff7d08c3c4ed
-size 4533
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg
deleted file mode 100644
index 2f54633a796f0d866754433c73dd79178cd34273..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:8c1006a64108d9a01cc0c5ef18fe356c8a4320f30cf6cf41c451f437b3cfe4a7
-size 4487
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
deleted file mode 100644
index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e651e0bddb05f1e829f9f354306f4087bedfa5b6246ea795fafd57b8ced34090
-size 4555
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
deleted file mode 100644
index 2f54633a796f0d866754433c73dd79178cd34273..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:8c1006a64108d9a01cc0c5ef18fe356c8a4320f30cf6cf41c451f437b3cfe4a7
-size 4487
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg
deleted file mode 100644
index 6077ca558e90c6c459cfa343620c4ceb7ff8a401..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:f517d296ce32f7486f48d9f5948af2f7eeaeea1b8f6f83b1ede5eeda55c1bda1
-size 101152
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a11a74eff5bf35900dc491470141e2e9_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a11a74eff5bf35900dc491470141e2e9_img.jpg
deleted file mode 100644
index 76f74b5e81517ed1bb0b28d187a3ba9b0a0cac8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a11a74eff5bf35900dc491470141e2e9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e41f3e6e4acb138a5cf6cb0f43ad407fb30c2f7175179bc705354bdd702ed1ba
-size 77120
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg
deleted file mode 100644
index 6134992ce9c5d512e70c1e2ff37d9530ef08bf5d..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:29c293be93061ac43373e0b12fce4fa52bb5d92014cdb5cb7d6a095b5c12b421
-size 4518
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a7c51c18111139f9aca2805114108565_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a7c51c18111139f9aca2805114108565_img.jpg
deleted file mode 100644
index 17d31d46bbc8ec34ceb9a2bd8e55c4102e15fa2f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/a7c51c18111139f9aca2805114108565_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3e46cf780c8559dd3eb57f44e5b324991a18882af807913951d14b237064649f
-size 59627
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg
deleted file mode 100644
index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e651e0bddb05f1e829f9f354306f4087bedfa5b6246ea795fafd57b8ced34090
-size 4555
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/bc453b6a6e6a96bdafd56edb6ea9d14b_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/bc453b6a6e6a96bdafd56edb6ea9d14b_img.jpg
deleted file mode 100644
index 843b6d7f5981773bc7b52adf8ce05e9e2851e344..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/bc453b6a6e6a96bdafd56edb6ea9d14b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:6ca9d395645a523940926fdbe4a41702e621ddcf82e2171023841b973c7f5494
-size 71798
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg
deleted file mode 100644
index 6134992ce9c5d512e70c1e2ff37d9530ef08bf5d..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:29c293be93061ac43373e0b12fce4fa52bb5d92014cdb5cb7d6a095b5c12b421
-size 4518
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
deleted file mode 100644
index c895ed27903711c5751fb690f0d0461b18975f93..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e608300f3b005772337331b0a9839a2a8c8308aaa843083f215a521642ba2338
-size 140504
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg
deleted file mode 100644
index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e651e0bddb05f1e829f9f354306f4087bedfa5b6246ea795fafd57b8ced34090
-size 4555
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg
deleted file mode 100644
index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4f6d08444a1dddff6009753a3442a2f3b4f55c9e91148537a2e5ff7d08c3c4ed
-size 4533
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
deleted file mode 100644
index 8ddaf6adc8b455f7d3cc8be540360bcbe788965b..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:856b926582c17242d0d3330f3547066f6f55440ba2cc6d780eaf04a0a2942571
-size 4541
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg
deleted file mode 100644
index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3d049c554b2900c22bc8803d3ad701ed99b61b673f86f779540c0831fb079907
-size 4520
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg
deleted file mode 100644
index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:79608603c3aa9e126495e2659c247dca745e88ba92d5a4759353b5984132c6f9
-size 4505
diff --git a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
deleted file mode 100644
index e8b9624631d343de15dc1c23522e08f9b2eb85d7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.RIC4NTN-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:36e34a1f7ef32e27fabbe6f9cde08fe510152296131578ca747a79434b59946c
-size 4542
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/doc.md b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/doc.md
deleted file mode 100644
index 934ab71b5c52dea85ff7d76c74afe9ce1282c7e9..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/doc.md
+++ /dev/null
@@ -1,2793 +0,0 @@
-
-
-# --- **O-RAN Work Group 1 (Use Cases and Overall Architecture)**
-
-## **Use Cases Analysis Report**
-
-Copyright © 2026 by the O-RAN ALLIANCE e.V.
-
-The copying or incorporation into any other work of part or all of the material available in this document in any form without the prior written permission of O-RAN ALLIANCE e.V. is prohibited, save that you may print or download extracts of the material of this document for your personal use, or copy the material of this document for the purpose of sending to individual third parties for their information provided that you acknowledge O-RAN ALLIANCE as the source of the material and that you inform the third party that these conditions apply to them and that they must comply with them.
-
-# Contents
-
-Foreword 5
-
-Modal verbs terminology 5
-
-Introduction 5
-
-- 1 Scope 6
-- 2 References 6
- - 2.1 Normative references 6
- - 2.2 Informative references 6
-- 3 Definition of terms, symbols and abbreviations 8
- - 3.1 Terms 8
- - 3.2 Symbols 9
- - 3.3 Abbreviations 9
-- 4 Use cases 10
- - 4.1 Context-based dynamic HO management for V2X 10
- - 4.1.1 Background information 10
- - 4.1.2 Motivation 10
- - 4.1.3 Proposed solution 11
- - 4.1.4 Benefits of O-RAN architecture 11
- - 4.1.5 Notes 11
- - 4.2 Flight path based dynamic UAV radio resource allocation 12
- - 4.2.1 Background information 12
- - 4.2.2 Motivation 12
- - 4.2.3 Proposed solution 12
- - 4.2.4 Benefits of O-RAN architecture 13
- - 4.3 Radio resource allocation for UAV application scenario 13
- - 4.3.1 Background information 13
- - 4.3.2 Motivation 14
- - 4.3.3 Proposed solution 14
- - 4.3.4 Benefits of O-RAN architecture 15
- - 4.4 QoE optimization 15
- - 4.4.1 Background information 15
- - 4.4.2 Motivation 16
- - 4.4.3 Proposed solution 16
- - 4.4.4 Benefits of O-RAN architecture 21
- - 4.5 Traffic steering 21
- - 4.5.1 Background information 21
- - 4.5.2 Motivation 22
- - 4.5.3 Proposed solution 22
- - 4.5.4 Benefits of O-RAN architecture 23
- - 4.6 Massive MIMO optimization 23
- - 4.6.1 Background information 23
- - 4.6.2 Motivation 23
- - 4.6.3 Proposed solution 23
- - 4.6.4 Benefits of O-RAN architecture 27
- - 4.7 RAN sharing 28
- - 4.7.1 Background information 28
- - 4.7.2 Motivation 28
- - 4.7.3 Proposed solution 29
- - 4.7.4 Benefits of O-RAN architecture 30
- - 4.8 QoS based resource optimization 30
- - 4.8.1 Background information 30
- - 4.8.2 Motivation 31
- - 4.8.3 Proposed solution 31
- - 4.8.4 Benefits of O-RAN architecture 32
- - 4.9 RAN slice SLA assurance 32
-
-| | | |
-|--------|----------------------------------------------------|----|
-| 4.9.1 | Background information | 32 |
-| 4.9.2 | Motivation | 32 |
-| 4.9.3 | Proposed solution | 32 |
-| 4.9.4 | Benefits of O-RAN architecture | 33 |
-| 4.10 | Multi-vendor slices | 33 |
-| 4.10.1 | Background information | 33 |
-| 4.10.2 | Motivation | 33 |
-| 4.10.3 | Proposed solution | 34 |
-| 4.10.4 | Benefits of O-RAN architecture | 35 |
-| 4.11 | Dynamic spectrum sharing (DSS) | 36 |
-| 4.11.1 | Background information | 36 |
-| 4.11.2 | Motivation | 36 |
-| 4.11.3 | Proposed solution | 36 |
-| 4.11.4 | Benefits of O-RAN architecture | 37 |
-| 4.12 | NSSI resource allocation optimization | 38 |
-| 4.12.1 | Background information | 38 |
-| 4.12.2 | Motivation | 38 |
-| 4.12.3 | Proposed solution | 38 |
-| 4.12.4 | Benefits of O-RAN architecture | 39 |
-| 4.13 | Local indoor positioning in RAN | 39 |
-| 4.13.1 | Background information | 39 |
-| 4.13.2 | Motivation | 40 |
-| 4.13.3 | Proposed solution | 40 |
-| 4.13.4 | Benefits of O-RAN architecture | 40 |
-| 4.14 | Massive SU/MU-MIMO grouping optimization | 41 |
-| 4.14.1 | Background information | 41 |
-| 4.14.2 | Motivation | 41 |
-| 4.14.3 | Proposed solution | 41 |
-| 4.14.4 | Benefits of O-RAN architecture | 43 |
-| 4.15 | O-RAN signalling storm protection | 43 |
-| 4.15.1 | Background information | 43 |
-| 4.15.2 | Motivation | 43 |
-| 4.15.3 | Proposed solution | 44 |
-| 4.15.4 | Benefits of O-RAN architecture | 45 |
-| 4.16 | Congestion prediction and management | 45 |
-| 4.16.1 | Background information | 45 |
-| 4.16.2 | Motivation | 45 |
-| 4.16.3 | Proposed solution | 46 |
-| 4.16.4 | Benefits of O-RAN architecture | 47 |
-| 4.17 | Industrial IoT optimization | 47 |
-| 4.17.1 | Background information | 47 |
-| 4.17.2 | Motivation | 48 |
-| 4.17.3 | Proposed solution | 48 |
-| 4.17.4 | Benefits of O-RAN architecture | 50 |
-| 4.18 | BBU pooling to achieve RAN elasticity | 50 |
-| 4.18.1 | Background information | 50 |
-| 4.18.2 | Motivation | 50 |
-| 4.18.3 | Proposed solution | 50 |
-| 4.18.4 | Benefits of O-RAN architecture | 51 |
-| 4.19 | Integrated SON function within the O-RAN framework | 52 |
-| 4.19.1 | Background information | 52 |
-| 4.19.2 | Motivation | 53 |
-| 4.19.3 | Proposed solution | 53 |
-| 4.19.4 | Benefits of O-RAN architecture | 55 |
-| 4.20 | Shared O-RU | 55 |
-| 4.20.1 | Background information | 55 |
-| 4.20.2 | Motivation | 55 |
-| 4.20.3 | Proposed solution | 56 |
-| 4.20.4 | Benefits of O-RAN architecture | 59 |
-| 4.21 | Network energy saving | 59 |
-| 4.21.1 | Background information | 59 |
-
-4.21.2 Motivation..... 60
-
-4.21.3 Proposed solution ..... 60
-
-4.21.4 Benefits of O-RAN architecture..... 66
-
-4.22 MU-MIMO optimization ..... 66
-
-4.22.1 Background information ..... 66
-
-4.22.2 Motivation..... 66
-
-4.22.3 Proposed solution ..... 66
-
-4.22.4 Benefits of O-RAN architecture..... 66
-
-4.23 Sharing Non-RT RIC data with the core..... 67
-
-4.23.1 Background information ..... 67
-
-4.23.2 Motivation..... 68
-
-4.23.3 Proposed solution ..... 68
-
-4.23.4 Benefits of O-RAN architecture..... 78
-
-4.24 Industrial vision SLA assurance ..... 78
-
-4.24.1 Background information ..... 78
-
-4.24.2 Motivation..... 78
-
-4.24.3 Proposed solution ..... 79
-
-4.24.4 Benefits of O-RAN architecture..... 80
-
-4.25 Void ..... 80
-
-4.26 Interference detection, prediction and optimization..... 81
-
-4.26.1 Background information ..... 81
-
-4.26.2 Motivation..... 81
-
-4.26.3 Proposed solution ..... 82
-
-4.26.4 Benefits of O-RAN architecture..... 87
-
-4.27 Communication and computing integrated networks ..... 87
-
-4.27.1 Background information ..... 87
-
-4.27.2 Motivation..... 87
-
-4.27.3 Proposed solution ..... 88
-
-4.27.4 Benefits of O-RAN architecture..... 92
-
-4.28 RAN intent-driven management services ..... 92
-
-Annex: Change history/Change request (history).....93
-
-# Foreword
-
-This Technical Report (TR) has been produced by WG1 of the O-RAN ALLIANCE.
-
-The content of the present document is subject to continuing work within O-RAN and may change following formal O-RAN approval. Should the O-RAN ALLIANCE modify the contents of the present document, it will be re-released by O-RAN with an identifying change of version date and an increase in version number as follows:
-
-version xx.yy.zz
-
-where:
-
-- xx: the first digit-group is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have xx=01). Always 2 digits with leading zero if needed.
-- yy: the second digit-group is incremented when editorial only changes have been incorporated in the document. Always 2 digits with leading zero if needed.
-- zz: the third digit-group included only in working versions of the document indicating incremental changes during the editing process. External versions never include the third digit-group. Always 2 digits with leading zero if needed.
-
-## Modal verbs terminology
-
-In the present document "**shall**", "**shall not**", "**should**", "**should not**", "**may**", "**need not**", "**will**", "**will not**", "**can**" and "**cannot**" are to be interpreted as described in clause 3.2 of the O-RAN Drafting Rules (Verbal forms for the expression of provisions).
-
-"**must**" and "**must not**" are **NOT** allowed in O-RAN deliverables except when used in direct citation.
-
-# Introduction
-
-This document provides O-RAN WG1 high level use case descriptions. Any multi-WG use case defined in O-RAN is expected to be documented in this report. If the use case is to be studied further, it will be covered in O-RAN WG1 detailed use case specification next, and then in relevant WGs.
-
-# 1 Scope
-
-The present document specifies potential O-RAN use cases as defined by O-RAN WG1 UCTG (Use Case Task Group). The use cases are described at a very high level, emphasizing how the use is enabled by O-RAN architecture along with basic input data expectations and resulting actions. These high level use cases are prioritized within O-RAN, and selected use cases are further detailed in O-RAN WG1 UCTG and relevant O-RAN WGs to define the requirements for O-RAN components and their interfaces.
-
-# 2 References
-
-## 2.1 Normative references
-
-Not applicable.
-
-## 2.2 Informative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are not necessary for the application of the present document, but they assist the user with regard to a particular subject area.
-
-- [i.1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”
-- [i.2] 3GPP TR 38.802: "Study on New Radio Access Technology; Physical Layer Aspects"
-- [i.3] 3GPP TR 38.889: “Study on NR-based access to unlicensed spectrum”
-- [i.4] 3GPP TS 38.401: “NG-RAN; Architecture description”
-- [i.5] ETSI EN 302 637-2: “Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service”, Release 1, November 2010
-- [i.6] GSMA Future Networks: “Infrastructure Sharing: An Overview”, June 2019
-- [i.7] GSMA NG.116: “Generic Network Slice Template”, Version 2.0, October 2019
-- [i.8] López-Pérez, David, et al. "A Survey on 5G Radio Access Network Energy Efficiency: Massive MIMO, Lean Carrier Design, Sleep Modes, and Machine Learning", IEEE Communications Surveys & Tutorials (2022)
-- [i.9] 3GPP TS 22.261: “Service requirements for the 5G system; Stage 1”
-- [i.10] 3GPP TS 23.285: “Architecture enhancements for V2X services”
-- [i.11] 3GPP TS 23.501: “System architecture for the 5G System (5GS); Stage 2”
-- [i.12] 3GPP TS 26.247: “Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)”
-- [i.13] 3GPP TS 28.310: “Management and orchestration; Energy efficiency of 5G”
-
-- [i.14] 3GPP TS 28.313: “Management and orchestration; Self-Organizing Networks (SON) for 5G networks”
-- [i.15] 3GPP TS 28.530: “Management and orchestration; Concepts, use cases and requirements”
-- [i.16] 3GPP TS 28.541: “Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3”
-- [i.17] 3GPP TS 28.552: “Management and orchestration; 5G performance measurements”
-- [i.18] 3GPP TS 36.300: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2”
-- [i.19] 3GPP TR 36.902: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Self-configuring and self-optimizing network (SON) use cases and solutions”
-- [i.20] 3GPP TS 37.340: “Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage 2”
-- [i.21] 3GPP TS 38.331: “NR; Radio Resource Control (RRC) protocol specification”
-- [i.22] O-RAN WG6: “Orchestration Use Cases and Requirements for O-RAN Virtualized RAN”
-- [i.23] 3GPP TS 29.520: “5G System; Network Data Analytics Services; Stage 3”
-- [i.24] 3GPP TS 23.288: “Architecture enhancements for 5G System (5GS) to support network data analytics services”
-- [i.25] 3GPP TS 29.510: “5G System; Network Function Repository Services, Stage 3”
-- [i.26] 3GPP TS 23.502: “Procedures for the 5G System (5GS); Stage 2”
-- [i.27] 3GPP TS 28.550: “Management and orchestration; Performance assurance”
-- [i.28] 3GPP TS 28.532: “Management and orchestration; Generic management services”
-- [i.29] O-RAN R1 interface: “General Aspects and Principles”
-- [i.30] O-RAN.WG1.OAD: “O-RAN Architecture Description”
-- [i.31] O-RAN.WG2.Non-RT-RIC-ARCH-TS: “Non-RT RIC: Functional Architecture”
-- [i.32] Void
-- [i.33] Void
-- [i.34] Void
-- [i.35] Void
-- [i.36] Void
-- [i.37] Void
-- [i.38] Void
-- [i.39] Void
-- [i.40] Void
-- [i.41] 3GPP TS 28.104: “Management and orchestration; Management Data Analytics (MDA)”
-- [i.42] O-RAN WG3: “E2 Service Model (E2SM) Cell Configuration and Control”
-- [i.43] 3GPP TS 36.331: “Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification”
-
-- [i.44] Chih-Lin I, Guanding Yu, Shuangfeng Han, Geoffrey Ye Li, “Green and Software-defined Wireless Networks: From Theory to Practice”, Cambridge University Press, 2019
-- [i.45] ETSI White Paper No. 54, “Evolving NFV towards the next decade”, May, 2023
-- [i.46] ETSI GS MEC 003: “Multi-access Edge Computing (MEC); Framework and Reference Architecture”
-- [i.47] ITU-T Y.IMT2020-CNC-req, Recommendation, “Requirements of coordination of computing and networking for IMT-2020 and beyond”
-- [i.48] 3GPP TS 28.538: “Management and orchestration; Edge Computing Management (ECM)”
-
-# --- 3 Definition of terms, symbols and abbreviations
-
-## 3.1 Terms
-
-For the purposes of the present document, the terms and definitions [given in [i.1] and the following] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in [i.1].
-
-**A1:** Interface between Non-RT RIC and Near-RT RIC to enable policy-driven guidance of Near-RT RIC applications/functions, and support AI/ML workflow.
-
-**A1 policy:** Type of declarative policies expressed using formal statements that enable the Non-RT RIC function in the SMO to guide the Near-RT RIC function, and hence the RAN, towards better fulfilment of the RAN intent.
-
-**A1 enrichment information:** Information utilized by Near-RT RIC that is collected or derived at SMO/Non-RT RIC either from non-network data sources or from network functions themselves.
-
-**E2:** Interface connecting the Near-RT RIC and one or more O-CU-CPs, one or more O-CU-UPs, and one or more O-DUs.
-
-**E2 node:** A logical node terminating E2 interface. In the present document, O-RAN nodes terminating E2 interface are:
-
-- for NR access: O-CU-CP, O-CU-UP, O-DU or any combination.
-- for E-UTRA access: O-eNB.
-
-**FCAPS:** Fault, Configuration, Accounting, Performance, Security.
-
-**Intents:** A declarative policy to steer or guide the behavior of RAN functions, allowing the RAN function to calculate the optimal result to achieve stated objective.
-
-**Near-RT RIC:** O-RAN Near-Real-Time RAN Intelligent Controller: A logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained data collection and actions over E2 interface.
-
-**Non-RT RIC:** O-RAN Non-Real-Time RAN Intelligent Controller: A logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in Near-RT RIC.
-
-**O-CU:** O-RAN Central Unit: A logical node hosting O-CU-CP and O-CU-UP.
-
-**O-CU-CP:** O-RAN Central Unit – Control Plane: A logical node hosting the RRC and the control plane part of the PDCP protocol.
-
-**O-CU-UP:** O-RAN Central Unit – User Plane: A logical node hosting the user plane part of the PDCP protocol and the SDAP protocol.
-
-**O-DU:** O-RAN Distributed Unit: A logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.
-
-**O-RU:** O-RAN Radio Unit: A logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP's "TRP" or "RRH" but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction).
-
-**O1:** Interface between management entities (NMS/EMS/MANO) and O-RAN managed elements, for operation and management, by which FCAPS management, software management, file management can be achieved.
-
-**RAN:** Generally referred as Radio Access Network. In terms of this document, any component below Near-RT RIC per O-RAN architecture, including O-CU/O-DU/O-RU.
-
-## 3.2 Symbols
-
-Void
-
-## 3.3 Abbreviations
-
-For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in [i.1].
-
-| | |
-|-------|----------------------------------------------------|
-| AI/ML | Artificial Intelligence/Machine Learning |
-| ASM | Advanced Sleep Mode |
-| DCCF | Data Collection Coordination and Delivery Function |
-| EC | Energy Consumption |
-| EE | Energy Efficiency |
-| eNB | eNodeB (applies to LTE) |
-| ES | Energy Saving |
-| gNB | gNodeB (applies to NR) |
-| KPI | Key Performance Indicator |
-| KQI | Key Quality Indicator |
-| MFAF | Messaging Framework Adaptor Function |
-| MIMO | Multiple Input, Multiple Output |
-| NRF | Network Repository Function |
-| NWDAF | NetWork Data Analytics Function |
-| PRB | Physical Resource Block |
-| QoE | Quality of Experience |
-| RAT | Radio Access Technology |
-| RIC | O-RAN RAN Intelligent Controller |
-
-| | |
-|------|-----------------------------------------|
-| SINR | Signal-to-Interference-plus-Noise Ratio |
-| SSB | Synchronization Signal Block |
-| UAV | Unmanned Aerial Vehicle |
-| V2X | Vehicle to Everything |
-| VM | Virtual Machine |
-| SMO | Service Management and Orchestration |
-| UDM | Unified Data Management |
-
-# --- 4 Use cases
-
-## 4.1 Context-based dynamic HO management for V2X
-
-### 4.1.1 Background information
-
-V2X communication allows for numerous potential benefits such as increasing the overall road safety, reducing emissions, and saving time. Part of the V2X architecture is the V2X UE (SIM + device attached to vehicle) which communicates with the V2X Application Server (V2X AS). The exchanged information comprises Cooperative Awareness Messages (CAMs) from UE to V2X AS [i.5], radio cell IDs, connection IDs, and basic radio measurements (RSRP, RSRQ etc.).
-
-### 4.1.2 Motivation
-
-As vehicles traverse along a highway, due to their high speed and the heterogeneous natural environment V2X UE-s are handed over frequently, at times in a suboptimal way, which can cause handover (HO) anomalies: e.g., short stay, ping-pong, and wrong cell. Such suboptimal HO sequences substantially impair the functionality of V2X applications. Since HO sequences are mainly determined by the Neighbour Relation Tables (NRTs), maintained by the xNBs, there is hardly room for UE-level customization.
-
-This UC aims to present a method to avoid and/or resolve problematic HO scenarios by using past navigation and radio statistics in order to customize HO sequences on a UE level. To this end, the AI/ML functionality that is enabled by the Near-RT RIC is employed.
-
-### 4.1.3 Proposed solution
-
-**A1:** Policy, Enrichment Data, Trained Model, Training Information.
-
-**Enrichment Data:** CAMs, DENMs, navigation data, geo data (position, velocity, direction)
-
-**E2 Report:** HO source+ target cell, HO complete/failure, failure cause, radio cell ID, connection ID, RSRP/RSRQ measurements.
-
-**E2 Policy:** set UE-NRT.
-
-
-
-```
-
-graph TD
- V2X[V2X APP Server] -- ENRICHMENT DATA --> NonRT[Non-RT RIC]
- subgraph NonRT [Non-RT RIC]
- LTA[Long-term analytics]
- end
- subgraph NearRT [Near RT RIC]
- RTO[Real-time optimization]
- end
- gNB[gNB]
-
- NonRT -- "A1: ENRICHMENT DATA" --> NearRT
- NearRT -- "A1: POLICY + TRAINED MODEL TRAINING INFO" --> NonRT
- NearRT -- "E2: REPORT" --> gNB
- gNB -- "E2: POLICY" --> NearRT
-
-```
-
-Diagram of Dynamic handover management for V2X use case. The diagram shows three main components: V2X APP Server, Non-RT RIC, and Near RT RIC, all connected to a gNB. The V2X APP Server sends ENRICHMENT DATA to the Non-RT RIC. The Non-RT RIC contains a 'Long-term analytics' block. The Non-RT RIC and Near RT RIC are connected by two interfaces: A1 (ENRICHMENT DATA and POLICY + TRAINED MODEL TRAINING INFO) and E2 (REPORT and POLICY). The Near RT RIC contains a 'Real-time optimization' block. The Near RT RIC sends E2: REPORT to the gNB and receives E2: POLICY from the gNB.
-
-**Figure 4.1.3-1: Dynamic handover management for V2X use case**
-
-In order to prevent anomalous HO sequences causing performance degradation for the V2Xs, an xApp can be built with two main functionalities as shown in figure 4.1.3-1. Applying long-term analytics by using AI/ML algorithms is the first function expected from the xApp. As it is suggested by O-RAN framework, non-real-time intelligent management of RAN functions are deployed in the Non-RT RIC. V2X AS maintains the UE-based HO events and mobility data which are shared with Non-RT RIC over O1 interface. Hence, Non-RT RIC can identify causes of HO anomalies and discover optimal HO sequences. Finally, a data base is maintained to keep track of resolutions to anomalies based on these feedbacks. The other function of the xApp is performing real-time optimization which is offered by trained ML model on the Near-RT RIC. Near-RT RIC will monitor UE specific real-time mobility context based on V2X data. Deployed ML model is used to detect/predict unexpected HO events and generate desired HO sequence which can eliminate/avoid HO anomaly. Finally, Near-RT RIC is expected to create and update UE-specific NRTs to improve performance of the V2X users.
-
-The xNB is assumed to host, besides the default NRT, also UE-specific NRTs (UE-NRTs) for V2X (and potentially other types of) users. If the UE-NRT for a specific V2X user exists, it is used. If not, the default NRT remains valid.
-
-The input samples for handover profiling can come from the V2X AS and the xNB:
-
-- CAMs, navigation data, geo data (position, velocity, direction),
-- Radio cell ID, connection ID, basic radio measurements (RSRP, RSRQ etc.),
-- Handover event (source and target cell IDs),
-- Handover success / error codes.
-
-The long-term analytics function and the real-time optimization function can be thought of as ML training and ML inference, respectively.
-
-### 4.1.4 Benefits of O-RAN architecture
-
-The long-term optimization function can jointly process UE level radio and navigation data. Both the analysis and the prediction functions can employ a range of AI/ML methods, whose availability is facilitated by the O-RAN architecture.
-
-### 4.1.5 Notes
-
-An option for associating the data coming from the gNB and that coming from the V2X AS can be achieved by the ECGI+C-RNTI [i.10][i.18]. The ECGI uniquely identifies the cell, while the C-RNTI uniquely identifies a UE within a cell. The ECGI+C-RNTI pair constitutes a globally unique UE identifier.
-
-## 4.2 Flight path based dynamic UAV radio resource allocation
-
-### 4.2.1 Background information
-
-This use case provides the background, motivation, and requirements for the support the use case of flight path based dynamic UAV radio resource allocation, allowing operators to adjust radio resource allocation policies through the O-RAN architecture, reducing unnecessary handover and improving radio resource utilization.
-
-### 4.2.2 Motivation
-
-The field trials' results show that the coverage for low altitude is good and can provide various services for terrestrial UEs with good performance. However, since the site along the flight is mainly for terrestrial UEs, the altitude of the UAV is always not within the main lobe of the ground station antenna. And the side lobes give rise to the phenomenon of scattered cell associations particularly noticeable in the sky. The cell association pattern on the ground is ideally contiguous area where the best cell is most often the one closest to the UE. As the UE move up in height, the antenna side lobes start to be visible, and there is a possibility of the best cell no longer being the closest one. The cell association pattern in this particular scenario becomes fragmented especially at the height of 300m and above. Hence, at higher altitudes, several challenges that lead to a different radio environment are:
-
-- LOS propagation/uplink interference
-- Poor KPI caused by antenna side lobes for base stations
-- Sudden drop in signal strength
-
-These challenges directly impact on the mobility performance of the drone and the service experience of the user. Hence, we would like to support the use case of flight path based dynamic UAV radio resource allocation to resolve the above issues.
-
-### 4.2.3 Proposed solution
-
-To manage resource allocation of UAVs based on flight path, Non-RT RIC retrieves necessary aerial vehicles related metrics from network level measurement reports. Moreover, flight path information of aerial vehicle, climate information, flight forbidden/limitation area information and space load information are received from an application, e.g., UTM (Unmanned Traffic Management) for constructing/training relevant AI/ML model. For example, this could be UL/DL interference from/to aerial vehicles, the detection of aerial vehicle UEs, and available radio resource (e.g., frequency, cell, beam, BWP, numerology) prediction. The Near-RT RIC supports deployment and execution of AI/ML model from Non-RT RIC. Based on this, Near-RT RIC can perform the radio resource allocation for UAVs considering the radio channel condition, flight path information and other application information with on-demand coverage. Moreover, aerial vehicles performance reports should be sent to Non-RT RIC for evaluation and optimization of the ML model.
-
-The architectural context of the flight path based dynamic UAV radio resource allocation use case is shown in figure 4.2.3-1.
-
-
-
-Diagram of O-RAN architecture for UAV radio resource allocation. A UTM (Unmanned Traffic Management) cloud icon is connected via a dashed line to a 'Non-Real Time RIC' block. This block is connected vertically to a 'Near-Real Time RIC' block. Below this, a dashed box contains 'CU-CP' and 'CU-UP' blocks connected by an 'E1' interface. The 'Near-Real Time RIC' connects to both CU blocks via 'E2' interfaces. Both CU blocks connect down to a 'DU' block via 'F1' interfaces. The 'DU' block is connected to a UAV icon via a 'Uu' interface and also features a red radio tower icon.
-
-**Figure 4.2.3-1: Use case of flight path based dynamic UAV radio resource allocation**
-
-### 4.2.4 Benefits of O-RAN architecture
-
-An effective functional module, retrieving the application information, performing machine learning and training is not provided by current gNB/eNB architecture. Though, the O-RAN architecture components can collect both the acquired application information and radio environment information and execute AI/ML models based on received information. The flight path based dynamic UAV radio resource allocation mechanism can be supported by the RIC function modules, i.e. Non-RT RIC and Near-RT RIC. Therefore, we provide the description of O-RAN support use case for flight path based dynamic UAV radio resource.
-
-## 4.3 Radio resource allocation for UAV application scenario
-
-### 4.3.1 Background information
-
-As shown in figure 4.3.1-1, this scenario refers to a rotor UAV flying at low altitude and low speed and carrying cameras, sensors and other devices mounted. The operation terminal uses the 5.8 GHz frequency band remote control the UAV for border/forest inspection, high voltage/base station inspection, field mapping, pollution sampling, and HD live broadcast.
-
-At the same time, the UAV control mobile station and the UAV anti-weapon combination provide the UAV control, fight against illegal UAV and other services to ensure low-altitude safety in special areas.
-
-The UAV operation terminal, the anti-UAV weapon, and the UAV control mobile station are connected with the UAV control vehicle using 5G network. UAV control vehicle deploys network equipment, including O-CU, O-DU, the Non-RT RIC, the Near-RT RIC function modules and application server (in this use case, it is an edge computing service platform) to provide reliable network services through 5G networks.
-
-
-
-The diagram illustrates a UAV control vehicle application scenario. At the top, two UAVs (UAV 1 and UAV 2) are shown. UAV 1 is connected to an 'Operation terminal 1' and UAV 2 to 'Operation terminal 2'. Above them, a box contains icons for a 'Camera', 'Gas detector', and 'searchlight'. Below the UAVs, there are three ground-based entities: 'Anti-UAV Weapon', 'Illegal UAV' (with labels 'Fight against illegal UAV' and 'Identify illegal UAV'), and 'Mobile control station'. On the right, a 'UAV Control Vehicle' is shown, which is equipped with a '5G gNB'. Dashed green lines labeled '5G network transmission' connect the UAVs, operation terminals, Anti-UAV Weapon, Illegal UAV, Mobile control station, and the 5G gNB on the control vehicle to a central point, indicating a networked environment.
-
-Diagram of UAV control vehicle application scenario showing various UAVs and ground stations connected to a central 5G gNB via 5G network transmissions.
-
-**Figure 4.3.1-1: UAV control vehicle application scenario**
-
-### 4.3.2 Motivation
-
-UAV terminal access is a new scenario of 5G networks. It has a large amount of high real-time data that is more suitable for local processing. For the existing radio resource allocation strategy, there is no solution for such uplink high-rate data transmission.
-
-In this use case, UAV control vehicle is required to provide reliable network services through 5G networks. The data of the UAV terminal interacting with the network includes control data and application data, and the control data includes navigation commands, configuration changes, flight status data reporting, etc. Control data requires low latency and low bandwidth requirements. The application data includes 4K high-definition video data, which has obvious uplink and downlink service asymmetry, and the uplink has high requirements on network bandwidth.
-
-The UAV control vehicle deploys edge computing services that application services and content are placed on the edge instead of core network so that local processing of video and control information can be managed. At the same time, real-time data services can be provided to third-party applications through a video server.
-
-### 4.3.3 Proposed solution
-
-As shown in figure 4.3.3-1, this use case involves two options of network architecture. Option A is that O-CU, O-DU and Near-RT RIC are deployed on the control vehicle, Non-RT RIC and core network are deployed on the central cloud. The control vehicle is connected to core network and Non-RT RIC via fiber optics. Option B is a private network, all modules, including the gNB, Near-RT RIC, Non-RT RIC and the necessary core network function modules, are deployed in the control vehicle.
-
-In both deployment options, radio resource allocation for UAV application use case requires some of the basic functionalities of the O-RAN components. Non-RT RIC should retrieve UE-level radio resource requirements from application server to generate UE based radio resource allocation policies. In this scenario, Near-RT RIC should support execution and interpretation of retrieved policies to create configuration parameters to be applied on the E2 nodes. In addition to UE-specific radio resource adjustment with respect to received parameters, E2 nodes should provide information about UE registration or UE status change to Near-RT RIC so that it can be transferred to application server. As it is stated in previous clause, UAV terminals require low latency and high throughput in the uplink direction. For this reason, application server is needed to receive user plane data from UAV terminals.
-
-
-
-Figure 4.3.3-1: Network architecture for UAV control vehicle application scenario. The diagram shows two options, Option A and Option B, for a UAV control vehicle. Both options show a vehicle containing a 5G gNB, O-DU, O-CU, Near-RT RIC, and an Application Server (Edge computing Service Platform). The Non-RT RIC is connected to the Service Management & Orchestration Framework. The Application Server is connected to a Video server, which in turn connects to VR, AI, and Video components. In Option A, the Application Server is connected to the Near-RT RIC. In Option B, the Application Server is connected to the Non-RT RIC.
-
-**Figure 4.3.3-1: Network architecture for UAV control vehicle application scenario**
-
-### 4.3.4 Benefits of O-RAN architecture
-
-The 5G network supports real-time high-definition video transmission and remote low-latency control of UAV, and finally provides various industry services such as inspection, security, surveying, and mapping.
-
-In the UAV control vehicle application scenario, there are a small amount of control data interaction requirements between the terminal and the network interaction, as well as the large bandwidth requirements for uploading HD video.
-
-The service asymmetry raises new requirements for resource allocation of the gNB. At the same time, the existing network operation and maintenance management platform (OSS system) can only optimize the parameters of a specific group of UEs, but not for individual users. Therefore, under the O-RAN architecture, the radio resource requirements for different terminals are sent to the gNB for execution by means of the Near-RT RIC function module.
-
-The UAV control vehicle has flexible layout features. In this use case, the application service and content are deployed on the edge computing platform instead of the core network; the Non-RT RIC function module is used to schedule radio resources instead of the core network's QoS mechanism. In this way, the load and overhead of the core network can be reduced, and the forwarding and processing time in data transmission can be reduced, and the delay can be reduced.
-
-## 4.4 QoE optimization
-
-### 4.4.1 Background information
-
-Highly demanding 5G native applications like cloud VR and industrial automation are both bandwidth consuming and latency sensitive. Demanding contemporary 4G and 5G applications like online multiplayer gaming and connected vehicles are today often handled in a best effort way with low or no application specific optimization. These traffic-intensive and highly interactive applications are not well served by current semi-static QoS framework which does not efficiently satisfy diversified QoE requirements. These requirements can vary during an application lifetime, especially taking into account potentially significant fluctuation of radio transmission capability and applications with dynamic performance requirements. It is expected that QoE estimation/prediction from application level can help deal with such uncertainty and improve the efficiency of radio resources, and eventually improve user experience and yield a more efficient use of RAN resources. Furthermore, an increased set of mobile applications with varying QoE demands will
-
-increasingly become unmanageable if semi-static profiles are “preloaded” into the relevant RAN nodes without a more automated closed-loop approach. RAN performance exposure to an external application are also envisioned to be helpful for the application to improve the user experience.
-
-### 4.4.2 Motivation
-
-The main objective is to ensure QoE optimization be supported within the O-RAN architecture and its open interfaces in a way that allows per-user, slice or 5QI flow modification of RAN behavior, features, scheduling procedures and other configuration based on user application requirements or other input. This includes:
-
-1. A user-centric QoE policy approach. Input from external systems, such as user applications, can be used to set or request specific RAN behavior automatically and without preloading of static configuration data and QoS profiles into E2 Nodes. Feedback is provided to these systems on the acceptance of the request.
-2. A user-centric QoE update and feedback approach. During a user or application session lifetime, a closed-loop including the user application or other external input can provide enriched performance targets to the RAN, varying the targeted performance in response to these external factors. Feedback is provided to the requesting source on the RAN performance for measurement against an SLA or for the application itself to take action to improve the user QoE.
-3. Using AI / ML approaches embedded in the RAN. Multi-dimensional data, e.g., user traffic data, QoE measurements, network measurement report, can be acquired and processed via ML algorithms to support traffic recognition, QoE prediction, QoS enforcement decisions. ML models can be trained offline and model inference will be executed in a real-time manner.
-4. Radio performance analytics and exposure. Based on the data analysis and ML algorithms, Near-RT RIC provides either statistics or predictions on the cell level or UE level, e.g., traffic rate, latency, packet loss rate. Furthermore, Near-RT RIC can expose the real time RAN analytics information to the external applications, and helps external applications to execute logic control, e.g., TCP sending window adjustment, video coding rate selection to improve the user QoE.
-
-The use case focus is a general solution that supports any specific QoE use case (e.g., cloud VR, video, gaming, connected vehicles, etc.).
-
-### 4.4.3 Proposed solution
-
-Traditional technologies involve manual configuration of RAN parameters for the congested cells to improve QoE of the network users. This can include per-site or per-cell parameter modification to target congested cells, or deployment of network-wide configurations to create application or user specific handling policies. The O-RAN architecture facilitates QoE optimization in a real-time way with proactive closed-loop network optimization, both within the RAN and including input from external applications. This will improve the way congested cells are detected and automatically allocate resources based on the end user experience, whose demands can change over time.
-
-The proposed solution consists of O-RAN components, Non-RT RIC, Near-RT RIC and E2 nodes, empowered with machine learning algorithms and user, slice or 5QI flow-centric feature and QoS modification interfaces. The solution introduces a “user RAN policy”, hosted at the Non-RT RIC (3.4.3.2) or Near-RT RIC (3.4.3.3). The user RAN policy will be instantiated as an rApp or xApp which will apply the operator’s desired QoE configuration for specific user, slice or 5QI flow types on the network in response to requests from external systems or in response to UE mobility, and provide feedback and reporting mechanisms, including SLA information, to external systems which are hosting the user application(s). The solution also includes exposing per-user or per-cell radio performance analytics information to external applications, and the application can optimize user QoE based on the RAN analytics information.
-
-#### 4.4.3.1 User-centric QoE connection policy
-
-
-
-```
-
-graph TD
- subgraph SMO
- subgraph Non-RT_RIC
- UE_RAN_Policy[UE RAN Policy]
- end
- end
-
- subgraph Near-RT_RIC
- RAN_RRM_Optimisation[RAN RRM Optimisation]
- end
-
- subgraph RAN
- CU-UP[CU-UP]
- CU-CP[CU-CP]
- O-DU/RU[O-DU/RU]
- end
-
- subgraph UE
- User_Application[User Application]
- end
-
- subgraph External_App_API[External App / API]
- end
-
- External_App_API -- "Application / slicing request" --> Non-RT_RIC
- Non-RT_RIC -- "Request Response" --> External_App_API
-
- Non-RT_RIC -- "O1: Node configuration" --> Near-RT_RIC
- Non-RT_RIC -- "A1: User-centric QoE Connection policy" --> RAN_RRM_Optimisation
- RAN_RRM_Optimisation -- "A1: RAN User State / policy request" --> Non-RT_RIC
-
- RAN_RRM_Optimisation -- "E2" --> CU-CP
- CU-CP -- "RAN User State" --> RAN_RRM_Optimisation
-
- CU-UP --> O-DU/RU
- CU-CP --> O-DU/RU
- O-DU/RU -- "Radio Resources" --> User_Application
-
-```
-
-Diagram illustrating the QoE connection policy application concept. It shows the flow of information between the SMO (containing Non-RT RIC), Near-RT RIC, RAN (CU-UP, CU-CP, O-DU/RU), and UE (containing User Application).
-
-**Figure 4.4.3.1-1: QoE connection policy application concept**
-
-This solution is expected to be invoked in response to changes in the applications being delivered to a UE, updates in the intended use-case handling behavior by an operator, implementation of a new network slice within the network, or mobility of a UE to a node which requires an update of the relevant handling policy.
-
-The concept of QoE connection policy application is shown in figure 4.4.3.1-1.
-
-The Non-RT RIC hosts a RAN QoE connection policy configuration which can be modified by operators to apply RAN connection level behaviors to a network slice, 5QI flow per device, specific user types or specific user ID(s).
-
-The Non-RT RIC will use the O1 interface to activate and configure the features of a particular QoE connection policy as they are needed across the network, while the A1 interface is used to request policy updates from the Non-RT RIC by specific network nodes (policy request) and by the Non-RT RIC to communicate the performance handling features that apply to a specific user, slice or 5QI flow (user-centric QoE connection policy).
-
-For example, in response to an A1 interface policy request: The O1 interface is first used to implement or update a constellation of carrier aggregation configuration, traffic steering, mobility, power control or scheduling priority or other behaviors (e.g. DRX) as a constellation of features which can be referred to by a feature activation policy index. The A1 interface is then used to indicate the users or flows this set of features is to be applied to.
-
-E2 nodes provide updated RAN user state information with sufficient granularity to the Near-RT RIC to trigger policy requests as needed.
-
-#### 4.4.3.2 User-centric QoE performance policy, Non-RT RIC
-
-
-
-The diagram illustrates two feedback loops for QoE performance policy application in the Non-RT RIC. Both loops share a common architecture: SMO (containing Non-RT RIC with UE RAN Policy), Near-RT RIC (containing RAN RRM Optimisation), RAN (containing CU-UP, CU-CP, and O-DU/RU), and UE (containing User Application).
-Loop (a) "Feedback loop with external application" shows feedback from the User Application to an External (App/API), which then feeds into the SMO via the Interface via SMO / BSS.
-Loop (b) "Feedback loop with RAN QoE handler" shows feedback from the User Application to a QoE Handler within the UE, which then feeds into the RAN and subsequently the SMO via a QoE Handler in the SMO.
-Both loops involve the exchange of "User performance targets", "RAN performance feedback & app guidance" via SMO/BSS, "User-centric performance policy" via A1 interface, and "Node/User-centric performance policy" via E2 interface. Near-RT PM and RAN User State are reported back from RAN to Near-RT RIC and SMO.
-
-Figure 4.4.3.2-1: QoE performance policy application concept, Non-RT RIC version. The diagram shows two feedback loops: (a) Feedback loop with external application and (b) Feedback loop with RAN QoE handler.
-
-**Figure 4.4.3.2-1: QoE performance policy application concept, Non-RT RIC version**
-
-This solution is expected to be invoked in response to changes in the user experience which could happen at any time during the lifetime of an application or session. This will typically operate as a continuous closed-loop including feedback from the user application(s).
-
-The concept of QoE performance policy application, Non-RT RIC version is shown in figure 4.4.3.2-1.
-
-In (a), the Non-RT RIC hosts a RAN QoE performance policy configuration which accepts input from external systems (user application or via other SMO/BSS functions) that provide closed-loop feedback on the user experience. This will be translated into a user-centric performance policy which is communicated via the A1 interface towards the Near-RT RIC which in turn, enforces these policies on the set of E2 nodes which currently host UEs of the type configured in the performance policy. For example, this policy would include specific latency, bitrate, and jitter targets which are used in conjunction with the connection policy described at 4.4.3.1 to determine how a specific user is handled in real time.
-
-An alternative, optional approach is shown at (b), which instead uses application layer measurement reporting from the UE to the RAN as defined in [i.43] (*MeasReportAppLayer* RRC Container) and [i.12] for LTE and in [i.21] (*MeasurementReportAppLayer* RRC Container) and [i.12] for NR. This approach is complementary to (a) and will be limited to those user applications with access to UE AT interfaces or appropriate middleware, and so is not universally applicable. The *MeasReportAppLayer* is forwarded from the RAN to a QoE handling node (outside of the O-RAN architecture) and provides input to the Non-RT RIC analogous to the external system but with reduced latency.
-
-E2 nodes provide updated user state information with sufficient granularity to allow for the distribution of connection policy, and PMs with required granularity to SMO to report on performance KPIs given the performance policy targets. This is then used to determine if an agreed performance target or SLA has been met, or alternatively, to indicate the RAN performance to an external application which can itself take action to improve the user QoE.
-
-#### 4.4.3.3 User-centric QoE performance policy, Near-RT RIC
-
-
-
-The diagram illustrates two variants of the QoE performance policy application concept for the Near-RT RIC.
-
-**(a) Feedback loop with external application:** This variant shows the flow of information between the Near-RT RIC, RAN, and an external application. The Near-RT RIC contains the UE RAN Policy and RAN RRM Optimisation. The RAN contains the CU-UP, CU-CP, and O-DU/RU. The UE contains the User Application. The flow is as follows:
-
-
-- The UE RAN Policy sends *User-centric performance policy* to the RAN RRM Optimisation.
-- The RAN RRM Optimisation sends *Node/User-centric performance policy* to the CU-UP and CU-CP.
-- The CU-UP and CU-CP send *Radio Resources* to the O-DU/RU.
-- The O-DU/RU sends *Radio Resources* to the UE.
-- The User Application sends *App performance feedback* to the External (App / API).
-- The External (App / API) sends *RAN performance feedback & App guidance* to the UE RAN Policy via the Interface FFS.
-- The UE RAN Policy also sends *User performance targets* to the Interface FFS.
-- The RAN RRM Optimisation sends *Near-RT PM and RAN User State* to the External (App / API).
-
-**(b) Feedback loop with RAN QoE handler:** This variant shows the flow of information between the Near-RT RIC, RAN, and a QoE Handler. The Near-RT RIC contains the UE RAN Policy and RAN RRM Optimisation. The RAN contains the CU-UP, CU-CP, and O-DU/RU. The UE contains the QoE Handler and the User Application. The flow is as follows:
-
-
-- The UE RAN Policy sends *User-centric performance policy* to the RAN RRM Optimisation.
-- The RAN RRM Optimisation sends *Node/User-centric performance policy* to the CU-UP and CU-CP.
-- The CU-UP and CU-CP send *Radio Resources* to the O-DU/RU.
-- The O-DU/RU sends *Radio Resources* to the UE.
-- The User Application sends *Application Layer Measurement Report* to the QoE Handler.
-- The QoE Handler sends *App performance feedback* to the UE RAN Policy via the Interface FFS.
-- The UE RAN Policy also sends *User performance targets* to the Interface FFS.
-- The RAN RRM Optimisation sends *Near-RT PM and RAN User State* to the External (App / API).
-
-Figure 4.4.3.3-1: QoE performance policy application concept, Near-RT RIC version. The diagram shows two variants: (a) Feedback loop with external application and (b) Feedback loop with RAN QoE handler. Both variants show the flow of information between the Near-RT RIC, RAN (CU-UP, CU-CP, O-DU/RU), and UE (User Application).
-
-Figure 4.4.3.3-1: QoE performance policy application concept, Near-RT RIC version
-
-This solution has the same set of usage patterns as described at 4.4.3.2, except the RAN QoE performance policy configuration is moved to the Near-RT RIC. This solution is only expected to be necessary to support QoE input from edge-hosted applications co-located with the Near-RT RIC or CU-UP nodes.
-
-The concept of QoE performance policy application, Near-RT RIC version is shown in figure 4.4.3.3-1.
-
-In (a), the edge hosted external app provides input to the Near-RT RIC. The specific interface used is not defined here and can be vendor specific or part of a future O-RAN release. In the (b) variant, which instead uses application layer measurement reporting [i.21][i.12], the QoE handler is also implemented at the edge location, with *MeasReportAppLayer* RRC containers forwarded for handling and then providing input to the Near-RT RIC rather than relying on the external app.
-
-#### 4.4.3.4 AI/ML QoE enhancements
-
-The concept of AI/ML QoE enhancements is shown in figure 4.4.3.4-1.
-
-
-
-```
-
-graph TD
- subgraph SMO
- subgraph Non-RT_RIC
- MT[Model Training]
- end
- end
- subgraph Near-RT_RIC
- AM[AI/ML Model]
- end
- subgraph RAN
- CUUP[CU-UP]
- CUCP[CU-CP]
- ODURU[O-DU/RU]
- end
- subgraph UE
- UA[User Application]
- end
-
- MT -- "A1/O1" --> AM
- MT -- "AI / ML Model parameters" --> AM
- AM -- "E2" --> CUCP
- AM -- "RAN QoE Tuning" --> CUCP
- CUCP -- "Near-RT PM" --> MT
- ODURU -- "Non-RT PM" --> MT
- ODURU -- "Radio Resources" --> UA
-
-```
-
-This diagram illustrates the AI/ML QoE enhancements concept. It shows a vertical stack of network components: SMO (containing Non-RT RIC), Near-RT RIC, RAN (containing CU-UP, CU-CP, and O-DU/RU), and UE (containing User Application).
-Key interactions include:
-
-- Model Training:** Occurs within the Non-RT RIC, with data flow from the RAN and UE back to the SMO via the **Non-RT PM** interface.
-- AI/ML Model:** Located in the Near-RT RIC, it receives **AI/ML Model parameters** from the Non-RT RIC and interacts with the RAN via the **E2** interface for **RAN QoE Tuning**.
-- Radio Resources:** The RAN provides these to the UE.
-
-AI/ML QoE enhancements concept diagram
-
-Figure 4.4.3.4-1: AI/ML QoE enhancements concept
-
-The Non-RT RIC will construct AI/ML models trained with data retrieved from SMO, network level measurements and policies to be sent Near-RT RIC for managing RAN parameters. The ML model will be deployed in the Near-RT RIC to assist QoE optimization such as making predictions on application/traffic types, QoE and available bandwidth.
-
-To achieve all these functions, E2 nodes should provide the PMs with required granularity to SMO over O1 and to the Near-RT RIC over E2. Also, RRM behaviour updates should be allowed by E2 nodes through E2 to support QoS enforcement.
-
-#### 4.4.3.5 Radio performance analytics
-
-
-
-```
-
-graph LR
- subgraph SMO_Non-RT_RIC
- RDC1[RAN data collection]
- RPPrApp[Radio performance prediction rApp AI/ML Model Training]
- end
- subgraph Near-RT_RIC
- RDC2[RAN data collection]
- RPPxApp[Radio performance prediction xApp AI/ML Model Inference]
- end
- subgraph RAN_Layer
- RAN[RAN]
- end
- subgraph UE_Layer
- UE[UE]
- end
-
- LNEF[Local NEF]
- ExtApp[External App]
-
- RAN -- "O1" --> RDC1
- RAN -- "E2" --> RDC2
- RPPrApp -- "A1" --> RPPxApp
- RPPxApp -.-> LNEF
- LNEF -- "N33" --> ExtApp
- UE --- RAN
-
-```
-
-This diagram shows the exposure of radio performance analytics. The stack includes SMO(Non-RT RIC), Near-RT RIC, RAN, and UE.
-Key components and flows:
-
-- SMO(Non-RT RIC):** Contains 'RAN data collection' (connected to the RAN via **O1**) and 'Radio performance prediction rApp (AI/ML Model Training)' (connected to the Near-RT RIC via **A1**).
-- Near-RT RIC:** Contains 'RAN data collection' (connected to the RAN via **E2**) and 'Radio performance prediction xApp (AI/ML Model Inference)'.
-- Local NEF:** Receives data from the Near-RT RIC and exposes it to an **External App** via the **N33** interface.
-- Legend:** A dashed blue arrow indicates the path to 'expose radio performance through local NEF to external applications'.
-
-Radio performance analytics information exposure, through local NEF diagram
-
-Figure 4.4.3.5-1: Radio performance analytics information exposure, through local NEF
-
-
-
-```
-
-graph TD
- subgraph SMO [SMO (Non-RT RIC)]
- RDC1[RAN data collection]
- RPPrApp[Radio performance prediction rApp
-(AI/ML Model Training)]
- end
-
- subgraph NearRT [Near-RT RIC]
- RDC2[RAN data collection]
- RPPxApp[Radio performance prediction xApp
-(AI/ML Model Inference)]
- end
-
- subgraph MECServer [MEC App Server]
- MECApp[MEC App]
- end
-
- RAN[RAN]
- UE[UE]
-
- SMO -- O1 --> NearRT
- SMO -- A1 --> NearRT
- NearRT -- E2 --> RAN
- RAN -- O1 --> SMO
- RAN --- UE
- RPPxApp -.-> MECApp
- MECApp -.-> UE
-
- style MECApp fill:#fff,stroke:#333,stroke-width:1px
- style RDC1 fill:#fff,stroke:#333,stroke-width:1px
- style RPPrApp fill:#fff,stroke:#333,stroke-width:1px
- style RDC2 fill:#fff,stroke:#333,stroke-width:1px
- style RPPxApp fill:#fff,stroke:#333,stroke-width:1px
-
-```
-
-Diagram showing radio performance analytics information exposure through MEC. The diagram illustrates the flow of data from the UE through the RAN, Near-RT RIC, and SMO(Non-RT RIC) to the MEC App Server. The SMO contains RAN data collection and radio performance prediction rApp (AI/ML Model Training). The Near-RT RIC contains RAN data collection and radio performance prediction xApp (AI/ML Model Inference). The MEC App Server contains the MEC App. Arrows indicate data flow: O1 from SMO to Near-RT RIC, A1 from SMO to Near-RT RIC, E2 from Near-RT RIC to RAN, O1 from RAN to SMO, and a dashed arrow from the MEC App to the UE labeled 'expose radio performance to the applications in MEC App server'.
-
-**Figure 4.4.3.5-2: Radio performance analytics information exposure, through MEC**
-
-This solution is expected to be invoked when the external application requests for RAN performance from Near-RT RIC. In response to application requests, Near-RT RIC subscribes measurements through E2 interface and runs radio performance prediction model to generate predicted performance for a specific UE or cell.
-
-As shown in figure 4.4.3.5-1, Near-RT RIC exposes radio performance prediction information through local NEF (defined in 3GPP) to external apps. As shown in figure 4.4.3.5-2, Near-RT RIC exposes radio performance prediction information directly to MEC app deployed in MEC app server (defined in ETSI MEC).
-
-External application receives radio performance prediction information and executes logic control based on the service and user requirements, e.g., for 4K/8K/VR videos, application could execute TCP sending window adjustment, video coding rate selection to improve user experience.
-
-### 4.4.4 Benefits of O-RAN architecture
-
-The proposed solution to support a real-time QoE optimization for any specific use e.g., cloud VR, video. It requires features provided by O-RAN architecture to orchestrate these requirements via interoperable A1/O1/E2 interfaces and including input from external systems and user applications. Retrieving measurement metrics, AI/ML training and executing the AI/ML model in near-real-time are also offered by the O-RAN architecture.
-
-## 4.5 Traffic steering
-
-### 4.5.1 Background information
-
-5G systems will support many different combinations of access technologies namely, LTE (licensed band), NR (licensed band), NR-U (unlicensed band), Wi-Fi (unlicensed band), (see TR 38.889 [i.3]). Several different multi-access deployment scenarios are possible with 5GC to support wide variety of applications and satisfy the spectrum requirements of different service providers.
-
-- Carrier aggregation between licensed band NR (primary cell) and NR-U (secondary cell)
-- Dual connectivity between licensed band NR (primary cell) and NR-U (secondary cell)
-- Dual connectivity between licensed band LTE (primary cell) and NR-U (secondary cell)
-- Dual connectivity between licensed band NR (primary cell) and Wi-Fi (secondary cell)
-
-NOTE: The scenario of dual connectivity between NR and Wi-Fi is not defined in the present document.
-
-The traffic steering use case allows, using the A1 interface, flexibly configure the desired optimization policies and utilize the appropriate performance criteria to proactively manage user traffic across different access technologies. A1 interface can also provide the enrichment information, e.g., radio fingerprint information based on the data analytics of the historical RAN data
-
-### 4.5.2 Motivation
-
-Imbalances in the traffic load across cells of different access technologies, or variances in their available bandwidth and QoS attributes, can give rise to situations with suboptimal spectrum utilization and negative impact on the user experience. The 3GPP Self-Organizing Network (SON) function Mobility Load Balancing (MLB) is the legacy approach to improve the user experience by balancing the load through optimization of the handover triggers and handover decisions using load information shared between neighbouring cells. Normally all users are treated equally in this respect. In addition, the statistical characteristics of the radio network information have not been fully exploited and utilized to enhance the network and user experience performance.
-
-### 4.5.3 Proposed solution
-
-#### 4.5.3.1 Policy-based traffic management optimization
-
-Impairments of the user experience due to local load imbalances across cells, or due to variances in their available bandwidth offered, are example scenarios addressed by traffic management policies over the A1 interface. The traffic management policy allows allocating cells in order of priority to individual users, for the control plane and user plane respectively. A traffic management policy could be issued for any reason, e.g. reasons not known to the RAN.
-
-The Non-RT RIC monitors the user experience by UE level performance measurements and the resource utilization on cell level. The Non-RT RIC assesses the observed performance vs. the expected service level requirements. If the requirements are breached the Non-RT RIC locates the cell where the breach is detected and assesses the local load or bandwidth conditions in the associated cells. It can desire to relocate one or more users to other cells e.g., in order to increase their available radio resources, offer increased bandwidth, desire to off-load a certain cell to improve conditions for the remaining users, or for any other reason.
-
-Further in a multi-access system, apart from selecting the appropriate access technology to steer the traffic, there is a need to switch the traffic across different access technologies based on changes in radio environment and application requirements and even split the traffic across multiple access technologies to satisfy performance requirements. The different types of traffic and frequency bands in a commercial network can require appropriate bearer selection (Master Cell Group (MCG) bearer, Secondary Cell Group (SCG) bearer, split bearer) and bearer type change for achieving load balancing, low latency and best in class throughput in a multi-access scenario with 5GC networks., (see TS 37.340 [i.20]).
-
-The Non-RT RIC creates corresponding traffic management policies directed to identify UEs expressing the priority order of cells to be allocated to each one for their control planes and user planes respectively. The policies are sent over the A1 interface to the Near-RT RIC, who uses the policies when enforcing the radio resource control.
-
-#### 4.5.3.2 Enrichment information-based traffic steering optimization
-
-The current traffic management solutions are usually implemented by relocating users among cells, which highly depends on the Measurement Report (MR) from the UE feedback. The statistical characteristics of the radio network and the UE behaviors information have not been fully exploited and utilized to enhance the network and user experience performance.
-
-The enrichment information can be utilized to optimize traffic management performance. The enrichment data could include network radio fingerprint information, UE trajectory information (e.g., way points in cell-level or beam-level), UE mobility profile (e.g., stationary, horizontal, vertical speed), UE service type (e.g., delay sensitivity or bit error rate sensitive), traffic pattern (e.g., average UL/DL packet size, periodicity). With the assistance of the enrichment information provided by Non-RT RIC, Near-RT RIC can efficiently derive optimized solutions.
-
-For example, Non-RT RIC can derive the radio fingerprint enrichment information via the data statistical analysis of historical measurement results. The radio fingerprint information captures the mapping relationship of the intra-frequency measurement results and the inter-frequency measurements. Then Non-RT RIC can deliver it to Near-RT RIC to help it predict the inter-frequency measurement, reduce the unnecessary inter-frequency measurement, accelerate the process of traffic optimization and improve the network system performance and user experience.
-
-### 4.5.4 Benefits of O-RAN architecture
-
-The use case explores the opportunity with the policy based A1 interface allowing to address specific users to obtain an intent driven by e.g. UE specific service level requirements.
-
-## 4.6 Massive MIMO optimization
-
-### 4.6.1 Background information
-
-Massive MIMO is seen as one of the key technologies for 5G. Due to the multi-antenna transmission and reception, this technology can inherently provide diversity and improve capacity by targeting high gain antenna beams towards one or multiple subscribers, thus improving the receive power levels and spatially filtering the interference from neighboring subscribers and transmission points. In addition, a spatial multiplexing operations regime can improve the network capacity by transferring multiple data streams towards/from one or different subscribers utilizing a spatial re-use of the scarce time/frequency resource blocks. Further advantages include the controlling of electromagnetic (EM) emissions or advanced network management technologies like beam shaping, beam-based load balancing, optimized beam mobility, adaptive cell coverage areas, especially in highly dense urban 3D environments and mobile subscribers. In order to further optimize networks, e.g., maximize spectral efficiency, optimize coverage, or maximize cell capacity, fully digital beamforming (BF) methods are to be employed for below 6 GHz frequency wireless telecommunications. Grid of Beams (GoB) is a BF method which aims at selectively covering regions of interest with a suitable subset of radio beams (chosen from a dictionary of possible beams). Beam-based mobility robustness optimization is a BF method enhancing beam specific mobility performance e.g., by adding beam specific individual offsets. Mobility robustness optimization is a well-known SON concept [i.19]. First supporting measurements have been specified in LTE in Release 9 [i.18].
-
-### 4.6.2 Motivation
-
-The massive MIMO BF optimization use case aims at proactively and continuously improving cell and/or user-centric coverage, capacity and mobility performance in a massive MIMO deployment area by adapting beam configurations (e.g., number of beams, beam boresights, vertical beam widths, horizontal beam widths, beam black lists/white lists, beam mobility thresholds) in a multi-cell, possibly multi-vendor, deployment scenario to non-real time (e.g., 3D construction, 3D terrain topology, network, weather seasons, intra-day cell splitting/merging/shaping, traffic distribution, beam conflicts) and near-real time (e.g., moving users/hotspots, changing traffic distribution, crowd source data) changes. The high number of configuration parameters per array antenna, the amount of available measurement input data, the complexity, pro-activeness as well as non- and near-real time requirements suggest the application of machine learning techniques of input data analytics as well as use case decision generation.
-
-The objective of this use case is to allow the operator to flexibly configure massive MIMO system parameters by means of policies, configuration or machine learning techniques, according to objectives defined by the operator.
-
-### 4.6.3 Proposed solution
-
-- 1) The performance of BF is strongly dependent on the choice of the beam pattern.
-Traditional GoB solutions do not take contextual/per-site information into account and operate with a narrow set of manually predefined beam patterns. Contextual/per-site information is, among others, comprised of cell geometry
-
-and other cell parameters, antenna array parameters, real-time or long-term (e.g., seasonal) traffic patterns, real-time or long-term user mobility patterns etc. One goal of this use case is to demonstrate that by taking contextual/per-site information into account, GoB/mMIMO BF can enhance the network performance by allowing the operator to perform extensive BF customization and optimization.
-
-- 2) A key factor in multi-user (MU) mMIMO is the management of Beam Failures (BFAs). In order to prevent connectivity and user experience degradation, two AI/ML based beam mobility optimization solutions are proposed.
-
-In this use case three optimization loops for mMIMO BF are proposed (see figure 4.6.3-1):
-
-- 1) An outer, Non-RT loop massive MIMO GoB beam forming optimization
-- 2) An inner, Near-RT loop massive MIMO beam-based mobility robustness optimization
-- 3) An inner, Near-RT loop massive MIMO beam selection optimization
-
-The two optimization loops can be implemented and deployed either individually or jointly in a nested fashion.
-
-
-
-The diagram illustrates a nested control loop architecture. At the top is a box labeled 'Non-RT RIC/SMO' containing 'GoB Beam Forming Opt.'. Below it is a box labeled 'Near-RT RIC' containing 'Beam Mobility Optimization'. At the bottom is a box labeled 'mMIMO BS'.
-
-There are two feedback loops represented by arrows:
-1. An outer loop: An arrow goes from 'mMIMO BS' up to 'Non-RT RIC/SMO', and another arrow goes from 'Non-RT RIC/SMO' back down to 'mMIMO BS'.
-2. An inner loop: An arrow goes from 'mMIMO BS' up to 'Near-RT RIC', and another arrow goes from 'Near-RT RIC' back down to 'mMIMO BS'.
-
-Diagram of Non-RT and Near-RT optimization loops.
-
-Figure 4.6.3-1: Non-RT and Near-RT optimization loops
-
-#### 4.6.3.1 Non-RT massive MIMO GoB beam forming optimization
-
-The concept of Non-RT Beam Forming (BF) optimization is shown in figure 4.6.3.1-1.
-
-
-
-The diagram shows a hierarchical control structure.
-- At the top is a box 'Non-RT RIC/SMO' containing 'Model training & BF Optimization' with a circular arrow indicating an internal process.
-- Below it is a semi-transparent box 'Near-RT RIC'.
-- At the bottom are three 'mMIMO BS' units, each emitting multiple beams (represented by blue fan shapes).
-
-Control flows are indicated by vertical arrows on the left:
-- A downward arrow labeled 'BF configuration' originates from the 'Non-RT RIC/SMO' and points towards the 'mMIMO BS' units.
-- An upward arrow labeled 'Data collection' originates from the 'mMIMO BS' units and points towards the 'Non-RT RIC/SMO'.
-- Thin lines connect the 'Non-RT RIC/SMO' through the 'Near-RT RIC' layer to each of the three 'mMIMO BS' units.
-
-Diagram of Non-RT Beam Forming (BF) optimization architecture.
-
-Figure 4.6.3.1-1: Non-RT Beam Forming (BF) optimization
-
-Non-RT RIC hosts an application with long-term analytics function (=ML training, Non-RT RIC), whose task is to collect, process and analyse antenna array parameters, cell performance KPIs, UE mobility/spatial density data, traffic density data, interference data and BF gain/beam RSRP and MDT measurement data.
-
-The input data for BF optimization training and inference can be comprised of [i.2] antenna timing advance and angle-of-arrival measurements (for positioning estimation unless derived from another entity), aggregated & preprocessed beam-based reference signal measurements (average) traffic density measurements (across the respective mMIMO spatial grid) with associated positioning information, CSI measurements or, power headroom reports (PHRs), neighboring cells' beams/interference information and beam RSRPs/gains as well as cell performance measurements such as handover and beam failure statistics.
-
-The output of the BF optimization inference can be optimized BF configuration, number of beams, beam elevation, beam horizontal & vertical widths and power allocation of beams.
-
-The long-term analytics function and the BF optimization function can be thought of as ML training and ML inference, respectively.
-
-Operator objectives can include desired coverage, defined in terms of the cell geometry (SSB beams), cell capacity requirements (CSI-RS beams), per UE cell edge throughput and traffic density weighted average RSRP and BF gain requirements. (E.g., the operator might wish to implement the strategy to cover low-density areas with wide beams and high-density areas with narrow beams.)
-
-#### 4.6.3.2 Near-RT massive MIMO beam-based Mobility Robustness Optimization (bMRO)
-
-The concept of Near-RT beam-based mobility robustness optimization is shown in figure 4.6.3.2-1.
-
-Near-RT RIC hosts an xApp with BF optimization function (=ML inference, Near-RT RIC), whose task is to monitor UE/traffic density measurements, UE positioning information, beam-based mobility and beam failure KPIs and select/deploy optimized mMIMO BF parameters to E2 nodes.
-
-The Near-RT RIC can host an xApp to optimize inter-cell beam mobility such as a beam-based mobility robustness optimization. In this case the Near-RT RIC might for instance configure beam individual offsets for inter-cell mobility decisions.
-
-The Near-RT bMRO function can run individually, without the Non-RT BF optimization. However, it can be deployed in a nested fashion within a Non-RT BF optimization loop. In that case, upon change of the GoB configuration, the Near-RT bMRO function is reset or reconfigured. There are several options for coordinating the outer and the inner loops such as:
-
-- 1) The outer loop's output comes from a finite set of configurations, and to each configuration the inner loop employs a trained model.
-- 2) The inner loop employs a reinforcement or adaptive learning technique which is reset upon change of the GoB configuration, or, depending on implementation, adapted to it.
-
-
-
-```
-
-graph TD
- UE[UE: +3dBm, -4dBm] -- Data collection --> NonRT[Non-RT RIC/SMO: Model training]
- NonRT -- Model deployment --> NearRT[Near-RT RIC: Model inference]
- NearRT -- BS configuration --> BS1[mMIMO BS]
- NearRT -- BS configuration --> BS2[mMIMO BS]
- NearRT -- BS configuration --> BS3[mMIMO BS]
- BS1 -- Measurement report --> NearRT
- BS2 -- Measurement report --> NearRT
- BS3 -- Measurement report --> NearRT
- NearRT -- Model inference --> BS1
- NearRT -- Model inference --> BS2
- NearRT -- Model inference --> BS3
-
-```
-
-Diagram of Near-RT beam-based mobility robustness optimization architecture. It shows a hierarchy from Non-RT RIC/SMO (Model training) to Near-RT RIC (Model inference) to multiple mMIMO BS units. Data collection from a UE (with +3dBm and -4dBm signal levels) is sent to the Non-RT RIC. Model deployment and BS configuration are sent from the Non-RT RIC to the Near-RT RIC. Measurement reports are sent from the mMIMO BS units to the Near-RT RIC.
-
-**Figure 4.6.3.2-1: Near-RT beam-based mobility robustness optimization**
-
-Non-RT RIC hosts an application with long-term analytics function (=ML training, Non-RT RIC), whose task is to collect and analyse underlying GoB configuration, if GoB configuration exists, beam mobility and failure statistics, L1/L2 RSRP values, potential source-target beam pairs.
-
-Near-RT RIC hosts an xApp with bMRO optimization function (=ML inference, Near-RT RIC), whose task is to monitor potential source-target beam pairs and optimize beam mobility for scheduling by managing user-beam pairing.
-
-The input data for beam mobility robustness optimization training and inference can be comprised of [i.2] per-user measurements (e.g., RSRP, SINR, etc.), handover failure statistics (e.g., overall HO failures, too early or too late or HO to wrong cell), such as number of BFAs, times of BFAs, BFA rate etc., per-user potential source-target beam pairs and neighbouring cells' beams/interference information.
-
-The output of the bMRO optimization function can be [i.19] adjusted offsets for candidate source-target beam pairs for beam mobility.
-
-The long-term analytics function and the bMRO function can be thought of as ML training and ML inference, respectively.
-
-Operator objectives can include minimization of BFA rate for a group of users (e.g., high-mobility users).
-
-#### 4.6.3.3 Near-RT massive MIMO Beam Selection Optimization (BSO)
-
-The concept of Near-RT Beam Selection Optimized (BSO) function is shown in figure 4.6.3.3-1.
-
-Near-RT RIC hosts an xApp with BF optimization function (=ML inference, Near-RT RIC), whose task is to monitor UE/traffic density measurements, UE positioning information, beam-based mobility, and beam failure KPIs and select/deploy optimized mMIMO BF parameters to E2 nodes.
-
-The Near-RT RIC can host an xApp to optimize intra-cell beam mobility. In this case the Near-RT RIC might for instance configure parameters for intra-cell beam switching decisions.
-
-The Near-RT BSO function can run individually, without the Non-RT BF optimization. However, it can be deployed in a nested fashion within a Non-RT BF optimization loop. In that case, upon change of the GoB configuration, the Near-RT BSO function is reset or reconfigured. There are several options for coordinating the outer and the inner loops such as:
-
-- 1) The outer loop's output comes from a finite set of configurations, and to each configuration the inner loop employs a trained model.
-- 2) The inner loop employs a reinforcement or adaptive learning technique which is reset upon change of the GoB configuration, or, depending on implementation, adapted to it.
-
-
-
-The diagram illustrates the O-RAN architecture for the Near-RT Beam Selection Optimized (BSO) function. At the top, a box labeled "Non-RT RIC/SMO" contains a circular arrow labeled "Model training". Below it, a box labeled "Near-RT RIC" contains a circular arrow labeled "Model inference". At the bottom, three boxes represent "mMIMO BS".
-
-Data flows are indicated by arrows:
-
-- "Data collection" points from the mMIMO BS level up to the Non-RT RIC/SMO.
-- "Model deployment" points from the Non-RT RIC/SMO down to the Near-RT RIC.
-- "Measurement report" points from the Near-RT RIC up to the Non-RT RIC/SMO.
-- "BS configuration" points from the Near-RT RIC down to the mMIMO BSs.
-
-On the left, a graphic shows a mobile device (UE) receiving beams from a base station. Signal levels are marked as "+3dBm" for a red beam and "-4dBm" for a green beam.
-
-Diagram of Near-RT Beam Selection Optimized (BSO) function architecture
-
-**Figure 4.6.3.3-1: Near-RT Beam Selection Optimized (BSO) function**
-
-Non-RT RIC hosts an application with long-term analytics function (=ML training, Non-RT RIC), whose task is to collect and analyse underlying GoB configuration, if GoB configuration exists, beam mobility and failure statistics, L1/L2 RSRP values, potential source-target beam pairs.
-
-Near-RT RIC hosts an xApp with BSO function (=ML inference, Near-RT RIC), whose task is to monitor potential source-target beam pairs, and to optimize beam mobility for scheduling by managing user-beam pairing.
-
-The input data for BSO training and inference can be comprised of per-user measurements (e.g. RSRP, SINR etc.), beam failure statistics, per-user potential source-target beam pairs and neighbouring cells' beams/interference information.
-
-The output of the BSO optimization function can be adjusted offsets for candidate source-target beam pairs for beam mobility.
-
-The long-term analytics function and the BSO function can be thought of as ML training and ML inference, respectively.
-
-Operator objectives can include minimization of BFA rate for a group of users (e.g., high-mobility users).
-
-### 4.6.4 Benefits of O-RAN architecture
-
-The advantages the O-RAN architecture provides to this use case include the chance to apply and combine both, non- and near real-time analytics, machine-learning, and decision making for various sub-tasks of this use case for a cell-centric and /or user (group) centric point of view. The Non-RT RIC oversees by definition the long-term traffic-, coverage-, and interference situation etc., in a whole cluster of cells. O-RAN interfaces such as O1, A1, and E2 will support necessary data, policy, and configuration exchanges between the architectural elements. By taking contextual information and past failure statistics into account, mMIMO BF can be much more customized and thus achieve purposeful operator desires/requirements. Optimized mMIMO BF depends on the collection, processing, and the analysis of both non-real-time and real-time cell-/UE-level data, which is facilitated by the O-RAN architecture.
-
-## 4.7 RAN sharing
-
-### 4.7.1 Background information
-
-One of the main challenges for network operators is to deploy a massive number of services, while providing different Quality of Service (QoS) requirements and keeping reasonable the level of investment in the network. Network sharing is envisioned as an efficient and sustainable way to accelerate the deployment of 5G, while taking advantage of a common pool of physical infrastructures and resources, made available for two or more partner operators.
-
-Besides, regulatory requirements often force operators to provide coverage in not business attractive areas, causing profitability issues. To this end, RAN sharing is seen as a promising solution that can reduce network costs, increase network capacity and coverage, while enhancing customer satisfaction. Accordingly, the open and multi-vendor nature of the O-RAN architecture can accelerate the introduction and development of RAN sharing solutions, by enhancing the deployment of Virtual Network Functions (VNF) on commodity shared hardware, while taking into account diverse QoS requirements.
-
-Among the different RAN sharing models that have been experimented so far, a special focus is put here on the evaluation of the compatibility of the “geographical split” RAN sharing model with the O-RAN architecture. In such a model, a coverage area is split between two or more operators; each operator manages the RAN in a specific area, while offering access to its RAN resources to its operator partners. Two main configurations have been used worldwide [i.6] Multi-Operator Core Network (MOCN) and Multi-Operator RAN (MORAN). In MOCN, both the RAN infrastructure and carriers are pooled. Even though this model enables further cost saving, especially in rural areas due to a lower number of carriers, it requires the presence of a regulatory entity that takes care of the allocation of different parts of the shared spectrum between operators. Conversely, in MORAN, each operator utilizes a separate carrier, while getting more freedom and independency on the control of the radio resources. MORAN is the most widely used sharing configuration as it can provide appropriate independency to each sharing partner operator, while maximizing the benefits of sharing in terms of CAPEX and OPEX.
-
-Besides, the O-RAN architecture can provide new opportunities for implementing this RAN sharing model in a more efficient way, thanks to its multi-vendor interfaces and abstraction control provided by the RIC (RAN Intelligent Controller). Accordingly, O-RAN can accelerate the deployment of 3GPP-based solutions by providing more flexibility in the management of the shared resources.
-
-### 4.7.2 Motivation
-
-3GPP has specified RAN sharing procedures for 5G in [i.11][i.2] and analysed RAN sharing scenarios for aggregated and disaggregated architectures [i.4]. Two options are discussed in 3GPP: 1) both gNB-CU and gNB-DU are shared or 2) only the gNB-DU is shared, with possibility to have a different gNB-CU for each operator.
-
-However, 3GPP does not cover the analysis of RAN sharing scenarios with LLS functional split (i.e., in O-RAN case; O-DU/O-RU), while the coordination between HLS functional split (i.e., in O-RAN case O-CU and O-DU) belonging to different operators is left to implementation (not standardized).
-
-In this context, O-RAN can be seen as the ideal enabler of the 3GPP RAN sharing model by providing the required coordination between the shared network nodes and management layer.
-
-To this end, the SMO/O-Cloud can enable the coordination of multiple O-CU-CP, O-CU-UP and O-DU, while opening the road for diverse RAN sharing scenarios.
-
-Moreover, O-RAN can accelerate the deployment of 5G RAN sharing solutions by taking advantage of the open fronthaul split. This can enable different multi-supplier configurations of O-DUs and O-RUs, while providing more flexibility to the sorts of configurations that the operators sharing the same RAN can deploy.
-
-### 4.7.3 Proposed solution
-
-The logic architecture of the proposed MORAN use case is given in figure 4.7.3-1. It is assumed that two operators, denoted as operator A and operator B, share the same RAN infrastructure, while keeping the core network independent.
-
-Specifically, operator A owns the site A and shares the PHY layer (LOW) with operator B (Shared O-RU shown in figure 4.7.3-1). Indeed, multiple PLMN IDs are broadcasted [i.6], while each operator operates in a different carrier.
-
-Moreover, site A hosts VNF instances of operator B in a shared O-DU and O-CU site. Specifically, the computing resources of the site A are shared among multiple VNFs, belonging to the operator A and B respectively. Each VNF represents a logic implementation of the O-DU and O-CU functionalities and should be controlled by each partner operator in an independent manner.
-
-While operator A can directly control its VNFs, operator B needs to control its VNFs in a remote manner. The challenge here is to enable operator B to control resources in an infrastructure that is owned by another operator. Accordingly, it is assumed that operator B can monitor and control the remoted resources via the RIC node of site B. Note that in the proposed architecture, the RIC are not shared and kept independent at the site A and B respectively.
-
-Such a scenario presents a set of implementation challenges:
-
-- A common interface is needed to control and coordinate the usage of shared resources.
-- An orchestrator has to be able to communicate effectively with the shared nodes regardless of the manufacturer or vendor of the used hardware devices.
-
-
-
-Figure 4.7.3-1: MORAN use case in O-RAN. The diagram illustrates the architectural layout between Site A (Operator A) and Site B (Operator B). Site A contains a Service Management & Orchestration Framework with an NMS Sharing APP, connected via A1 to an NRT-RIC, which connects via E2 to an nRT-RIC. Below this are VNFs for both Operator A and Operator B (O-CU-CP, O-CU-UP, O-DU) running on shared computing resources. These connect to a Shared O-RU via Open FH. Site B has a similar SMO and RIC structure. A 'Remote E2' interface connects Site B's nRT-RIC to the VNFs in Site A. An 'O1/O2 + SLA (Remote)' interface connects the SMOs of both sites. A legend identifies Site Operator A (orange outline), Site Operator B (blue outline), IT Infrastructure shared in Site A (light orange fill), IT Infrastructure shared in Site B (light blue fill), Network function specific to A (dark orange fill), and Network function specific to B (dark blue fill).
-
-**Figure 4.7.3-1: MORAN use case in O-RAN**
-
-To this end, this use case proposes to enable operator B to remote control the O-CU and O-DU VNFs via a “remote E2 interface”, giving it the freedom to implement and configure its RIC policies in an autonomous manner.
-
-Besides, it is assumed that operator A instantiates all the network nodes in site A, including the VNFs of operator B, via the O2 interface, while the management and orchestration is provided by Service & Orchestration Framework. To better orchestrate the shared resources, the Service & Orchestration Framework of site A should interact with the one of operator B. This interaction can be enabled as follows:
-
-- by designing a new interface between the Service & Orchestration Framework of the two sites (RAN sharing orchestration interface in figure 4.7.3-1)
-- by enabling the operator B to directly orchestrate its VNFs deployed in site A via “remote O1 & O2” interfaces.
-
-Regarding the control plane, it is assumed that operator A can control only the shared physical resources, while operator B can handle only the virtual resources that belong to it.
-
-The “remote E2” interface should provide secure access to operator’s A site, while from the operator B RIC perspective, the O-DU and O-CU VNFs hosted at site A should be controlled in a transparent manner as in non-shared scenario.
-
-Finally, this use case proposes an extension of the E2 interface in order to support the remote control of shared resources, while taking account security aspects related to the risk of: i) offering to an external actor the possibility to have access to the resources of the hosting RAN infrastructure, and ii) enabling an external actor to orchestrate the resources of the partner operator.
-
-### 4.7.4 Benefits of O-RAN architecture
-
-The proposed MORAN sharing architecture shown in figure 4.7.3-1 lets operators to configure shared network resources independently from configuration and operating strategies of the other sharing operators. Accordingly, this architecture enables the RIC of the operator B to monitor the radio state of the customers served by the partner operator’s site, facilitating the optimization of the radio allocation process and the remote configuration of QoS parameters. Moreover, this approach can favour the deployment of slicing scenarios facilitating the differentiation of services running on the shared RAN.
-
-## 4.8 QoS based resource optimization
-
-### 4.8.1 Background information
-
-QoS based resource optimization can be used when the network has been configured to provide some kind of preferential QoS for certain users. One such scenario can be related to when the network has been configured to support e2e slices. In this case, the network has functionality that ensures resource isolation between slices as well as functionality to monitor that slice Service Level Specifications (SLS) are fulfilled.
-
-In RAN, it is the scheduler that ensures that Physical Resource Block (PRB) resources are isolated between slices in the best possible way and also that the PRB resources are used in an optimal way to best fulfill the SLS for different slices. The desired default RAN behavior for slices is configured over O1. For example, the ratio of physical resources (PRBs) reserved for a slice is configured at slice creation (instantiation) over O1. Also, QoS can be configured to guide the RAN scheduler how to (in real-time) allocate PRB resources to different users to best fulfill the SLS of a specific slice. In the NR NRM this is described by the resource partition attribute.
-
-Instantiation of a RAN sub-slice will be prepared by rigorous planning to understand to what extent deployed RAN resources will be able to support RAN sub-slice SLS. Part of this procedure is to configure RAN functionality according to above. With this, a default behavior of RAN is obtained that will be able to fulfill slice SLSs for most situations. However, even through rigorous planning, there will be times and places where the RAN resources are not enough to fulfill SLS given the default configuration. To understand how often (and where) this happens, the performance of a RAN slice will continuously be monitored by SMO. When SMO detects a situation when RAN SLS cannot be fulfilled, Non-RT RIC can use A1 policies to improve the situation. To understand how to utilize A1 policies and how to resolve the situation, the Non-RT RIC will use additional information available in SMO.
-
-### 4.8.2 Motivation
-
-To motivate the use case an example with an emergency service as a slice tenant is used. For this example, it is understood (at slice instantiation) that 50% of the PRBs in an area can be enough to support the emergency traffic under normal circumstances. Therefore, the ratio of PRBs for the emergency users is configured to 50% as default behavior for the pre-defined group of users belonging to the emergency slice. Also, QoS is also configured in CN and RAN so that video cameras of emergency users get a minimum bitrate of 500 kbps.
-
-Now, suppose a large fire is ongoing and emergency users are on duty. Some of the personnel capture the fire on video on site. The video streams are available to the emergency control command. Because of the high traffic demand in the area from several emergency users (belonging to the same slice), the resources available for the emergency slice is not enough to support all the traffic. In this situation, the operator has several possibilities to mitigate the situation. Depending on SLAs towards the emergency slice compared to SLAs for other slices, the operator could reconfigure the amount of PRB reserved to emergency slice at the expense of other slices. However, there is always a risk that emergency video quality is not good enough irrespective if all resources are used for emergency users. It might be that no video shows sufficient resolution due to resource limitations around the emergency site.
-
-In this situation, the emergency control command decides, based on the video content, to focus on a selected video stream to improve the resolution. The emergency control system gives the information about which users to up- and down-prioritized to the e2e slice assurance function (through e.g., an Edge API) of the mobile network to increase bandwidth for selected video stream(s). Given this additional information, the Non-RT RIC can influence how RAN resources are allocated to different users through a QoS target statement in an A1 policy. By good usage of the A1 policy, the emergency control command can ensure that dynamically defined group of UEs provides the video resolution that is needed.
-
-The use case can be summarized as per below:
-
-- A fire draws a lot of emergency personnel to an area.
-- Because of this RAN resources becomes congested which affects the video quality for all video feeds in the area.
-- The emergency control command have 5 active video feeds and selects one video feed which is of specific interest.
-- The emergency control command requests higher resolution of a selected feed, while demoting the other.
-- With this information, the Non-RT RIC will evaluate how to ensure higher bandwidth for the feed selected by emergency control command (and lower for other feeds).
-- The Non-RT RIC updates the policy for the associated UEs in the associated Near-RT RIC over the A1 interface.
-- Near-RT RIC enforce the modified QoS target for the associated UEs over the E2 interface to fulfill the request.
-- The emergency control command experiences a higher resolution of the selected video feed.
-
-### 4.8.3 Proposed solution
-
-The main functions of the O-RAN components are utilized to support an improved QoS based resource optimization. QoS based resource optimization use case deploys O-CU, O-DU, the Non-RT RIC and the Near-RT RIC function modules. To achieve intelligent resource optimization, Non-RT RIC should provide policies to Near-RT RIC which are used to drive QoS based resource optimization at the RAN level. Non-RT RIC should monitor QoS related metrics from network and SMO functions. O-CU and O-DU components should provide UE performance metrics with the configured granularity to SMO via O1. In addition to performance metrics retrieved from network elements, external information sources might also be utilized to solve the problem of allocation limited RAN resources. For example, external server could provide Non-RAN data about priorities of the UEs to SMO. Finally, the E2 nodes should execute QoS enforcement decisions received from Near-RT RIC which are expected to influence RRM behaviour.
-
-### 4.8.4 Benefits of O-RAN architecture
-
-The main features of O-RAN architecture are pointed by the proposed solution which aims to offer more advanced QoS based resource optimization.
-
-## 4.9 RAN slice SLA assurance
-
-### 4.9.1 Background information
-
-The 3GPP standards architected a sliceable 5G infrastructure which allows creation and management of customized networks to meet specific service requirements that can be demanded by future applications, services and business verticals. Such a flexible architecture needs different requirements to be specified in terms of functionality, performance and group of users which can greatly vary from one service to the other. The 5G standardization efforts have gone into defining specific slices and their Service Level Agreements (SLAs) based on application/service type [i.11]. Since network slicing is conceived to be an end-to-end feature that includes the core network, the transport network and the radio access network (RAN), these requirements should be met at any slice subnet during the life-time of a network slice [i.15], especially in RAN side. Exemplary slice performance requirements are defined in terms of throughput, energy efficiency, latency and reliability at a high level in SDOs such as 3GPP [i.9] and GSMA [i.7]. These requirements are defined as a reference for SLA/contractual agreements for each slice, which individually need proper handling in NG-RAN.
-
-Although network slicing support is started to be defined with 3GPP Release 15, slice assurance mechanisms in RAN needs to be further addressed to achieve deployable network slicing in an open RAN environment. It is necessary to assure the SLAs by dynamically controlling slice configurations based on slice specific performance information. Existing RAN performance measurements [i.17] and information model definitions [i.16] are not enough to support RAN slice SLA assurance use cases. This use case is intended to clarify necessary mechanisms and parameters for RAN slice SLA assurance.
-
-### 4.9.2 Motivation
-
-In the 5G era, network slicing is a prominent feature which provides end-to-end connectivity and data processing tailored to specific business requirements. These requirements include customizable network capabilities such as the support of very high data rates, traffic densities, service availability and very low latency. According to 5G standardization efforts, the 5G system can support the needs of the business through the specification of several service needs such as data rate, traffic capacity, user density, latency, reliability, and availability. These capabilities are always provided based on a Service Level Agreement (SLA) between the mobile operator and the business customer, which brought up interest for mechanisms to ensure slice SLAs and prevent its possible violations. O-RAN's open interfaces and AI/ML based architecture will enable such challenging mechanisms to be implemented and help pave the way for operators to realize the opportunities of network slicing in an efficient manner.
-
-### 4.9.3 Proposed solution
-
-As shown in figure 4.9.3-1, RAN slice SLA assurance scenario involves Non-RT RIC, Near-RT RIC, E2 nodes and SMO interaction. The scenario starts with the retrieval of RAN specific slice SLA/requirements (possibly within SMO or from NSSMF depending on operator deployment options). Based on slice specific performance measurements from E2 nodes, Non-RT RIC and Near-RT RIC can fine-tune RAN behavior aligned with O-RAN architectural roles to assure RAN slice SLAs dynamically. Non-RT RIC monitors long-term trends and patterns for RAN slice subnets' performance and employs AI/ML methods to perform corrective actions through SMO (e.g., reconfiguration via O1) or via creation of A1 policies. Non-RT RIC can also construct/train relevant AI/ML models that will be deployed at Near-RT RIC. A1 policies possibly include scope identifiers (e.g., S-NSSAI) and statements such as KPI targets. On the other hand, Near-RT RIC enables
-
-optimized RAN actions through execution of deployed AI/ML models in near-real-time by considering both O1 configuration (e.g., static RRM policies) and received A1 policies, as well as received slice specific E2 measurements.
-
-
-
-The diagram illustrates the Slice SLA assurance architecture. At the top is the **Service, Management & Orchestration Framework** (orange box) containing an **AI/ML** block. Below it is the **Non-Real Time RIC** (green box). In the center is the **Near-RT RIC** (blue box) containing an **ML model**. At the bottom are the **E2 Nodes** (grey box). The interfaces and their associated functions are:
-
-- O1 Interface:**
- - From Framework to Non-RT RIC: Long term monitoring of RAN slice subnets performance, Retrieval of target RAN slice SLA/requirements, Non-RT O1 re-configuration / A1 policies for slice assurance.
- - From Non-RT RIC to Near-RT RIC: Default/static/non-rt configuration, Counters/KPIs from near-RT RIC and E2 nodes.
-- A1 Interface:**
- - From Non-RT RIC to Near-RT RIC: A1 POLICY (Dynamic & optimized), Policies for dynamic slice SLA assurance.
-- E2 Interface:**
- - From Near-RT RIC to E2 Nodes: E2 REPORT (Fine-grained statistics), E2 CONTROL/POLICY (Slice assurance actions, Slice resource allocation/prioritization).
- - From E2 Nodes to Near-RT RIC: Near real-time monitoring of RAN slice subnets performance, Optimized RAN (E2) actions to achieve RAN slice SLA based on O1 config, A1 policy, and E2 observations.
-
-Figure 4.9.3-1: Slice SLA assurance diagram showing the interaction between Service, Management & Orchestration Framework, Non-Real Time RIC, Near-RT RIC, and E2 Nodes via O1, A1, and E2 interfaces.
-
-Figure 4.9.3-1: Slice SLA assurance
-
-### 4.9.4 Benefits of O-RAN architecture
-
-Current standardization efforts focus on defining business and system requirements, slice management functionalities and procedures, and possible RRM policies on shared resources without specifying how such a flexible envisioned system can be addressed within 5G RAN. Considering the dynamic nature of RAN, providing desired levels of service quality for each RAN slice is a challenging topic that requires further investigation and standardization efforts for a multi-vendor open RAN environment. O-RAN’s open interfaces combined with its AI/ML based innovative architecture can enable such RAN SLA assurance mechanisms, which could potentially change the way network operators do their business and also enable new business models. For example, O-RAN architecture and interfaces can enable operators to manage spectrum resource allocation across slices more efficiently and dynamically in response to usage patterns, thereby allowing more efficient use of spectrum resources.
-
-## 4.10 Multi-vendor slices
-
-### 4.10.1 Background information
-
-This use case enables multiple slices with functions provided by multi-vendors, such as slice #1, composed of DU(s) and CU(s), provided by vendor A and slice #2, composed of DU(s) and CU(s), provided by vendor B.
-
-### 4.10.2 Motivation
-
-When providing multiple slices, it is assumed that suitable vO-DU/scheduler and vO-CU treat each slice respectively. A vendor who provides vO-DU and vO-CU function can have a strength of a customized scheduler for a certain service. With accomplishment of multi-vendor circumstances, following benefits can be expected:
-
-- 1) **More flexible and time to market deployment**
-Operators can maximize options to choose suitable vO-DU/scheduler and vO-CU to offer various slices. For example, some vendors can have a strength of a scheduler for eMBB service and the other can have a strength of scheduler for URLLC service. Or, vendor A can provide vO-DU/scheduler and vO-CU suitable for URLLC earlier than vendor B, therefore operators can choose vO-DU and vO-CU functions from vendor A to meet their service requirements.
-
-Also, when an operator wants to add a new service/slice, new functions from a new vendor can be introduced with less consideration for existing vendors if multi-vendor circumstance was realized. This can help expand vendor's business opportunities rapidly.
-
-- 2) Flexible deployment when sharing RAN equipment among operators
-When operators want to share RAN equipment and resources, RAN vendors and their placement of each RAN functions can be different. If multi-vendor circumstance was introduced, then it can relax restrictions among operators to share RAN equipment and resources. This can help expanded opportunities for reaching agreements of RAN sharing among operators. With expansion of RAN sharing, operators CAPEX and OPEX can be optimized, helping with additional investment opportunities.
-- 3) Reducing supply chain risk
-If an existing vendor providing a certain pair of vO-DU and vO-CU functions withdraws of the market due to business reasons, operators can deploy new vO-DU and vO-CU functions alternatively from other vendors under this multi-vendor circumstance. This can reduce a risk for operators' business continuity.
-
-### 4.10.3 Proposed solution
-
-#### 4.10.3.1 Multi-vendor slices
-
-An architecture for multi-vendor slices use case is given in figure 4.10.3.1-1. There are multiple slices with which have vO-DU and vO-CU functions associating respectively. As shown in figure 4.10.3.1-1, slice-1 is composed of vO-DU(s) and vO-CU(s) provided by vendor B, and slice-2 is composed of vO-DU(s) and vO-CU-UP(s) provided by vendor C. Each vO-DU/scheduler and vO-CU functions treat one slice as an example. O-RU provided by vendor A is shared between two vO-DU(s) supplied by two different vendors, vendor B and C. The case of vO-DU and vO-CU from different vendors in a slice is not defined in the present document.
-
-
-
-```
-
-graph LR
- subgraph "Vendor A"
- ORU[O-RU]
- end
- subgraph "Vendor B (Slice #1: eMBB)"
- VODUB[vO-DU]
- subgraph "O-Cloud B"
- VOCUUPB[vO-CU-UP]
- VOCUCPB[vO-CU-CP]
- end
- end
- subgraph "Vendor C (Slice #2: URLLC)"
- VODUC[vO-DU]
- subgraph "O-Cloud C"
- VOCUUPC[vO-CU-UP]
- VOCUCPC[vO-CU-CP]
- end
- end
- CORE[5G Core]
-
- ORU -- FH --> VODUB
- ORU -- FH --> VODUC
- VODUB -- F1-C/F1-U --> VOCUUPB
- VODUB -- F1-C --> VOCUCPB
- VOCUUPB -- E1 --- VOCUCPB
- VODUC -- F1-C/F1-U --> VOCUUPC
- VODUC -- F1-C --> VOCUCPC
- VOCUUPC -- E1 --- VOCUCPC
- VOCUUPB -- NG-U --> CORE
- VOCUCPB -- NG-C --> CORE
- VOCUUPC -- NG-U --> CORE
- VOCUCPC -- NG-C --> CORE
-
-```
-
-Figure 4.10.3.1-1: Multi-vendor slices use case diagram. It shows an O-RU (Vendor A) connecting via FH to two separate vO-DUs. One vO-DU (Vendor B) connects to vO-CU-UP and vO-CU-CP (Vendor B) within an O-Cloud, leading to Slice #1: eMBB in the 5G Core. The second vO-DU (Vendor C) connects to vO-CU-UP and vO-CU-CP (Vendor C) within another O-Cloud, leading to Slice #2: URLLC in the 5G Core. A legend identifies Vendor A as yellow, Vendor B as blue, and Vendor C as green.
-
-Figure 4.10.3.1-1: Multi-vendor slices use case
-
-#### 4.10.3.2 RAN sharing
-
-An additional application of multi-vendor slices use case is RAN sharing where, operator A has a pair of vO-DU and vO-CU from vendor A, and operator B has a different pair of vO-DU and vO-CU from vendor B, and O-RU is shared among these two operators (see figure 4.10.3.2-1).
-
-As mentioned in clause 4.10.2, through RAN sharing, CAPEX and OPEX are expected to be reduced. Savings achieved by RAN sharing can then be invested again for additional expansions of RAN sharing area.
-
-This use case considers single slice in each operator and multiple slices in each operator is not defined in the present document.
-
-
-
-Figure 4.10.3.2-1: RAN sharing use case diagram. It shows an O-RU connected via FH to two operators: Operator A (Hosting) and Operator B. Operator A (Vendor A, blue) has a vO-DU connected via F1-C/F1-U to a vO-CU-UP and vO-CU-CP, which connect to a Core via NG-U and NG-C. Operator B (Vendor B, yellow) has a vO-DU connected via E1 and F1-C to a vO-CU-UP and vO-CU-CP, which connect to a Core via NG-U. Both operators share a Common PF and HW.
-
-Figure 4.10.3.2-1: RAN sharing use case
-
-To realise multi-vendor slices, some coordination between vO-DU/vO-CUs will be required since radio resource should be assigned properly and without any conflicts. Depending on different service goals and the potential impact on O-RAN architecture, a required coordination scheme needs to be determined. The possible cases are:
-
-- 1) Loose coordination through O1/A1 interface (case 1 shown in figure 4.10.3.2-2)
-- 2) Moderate coordination through E2/X2/F1 interface (case 2 shown in figure 4.10.3.2-2)
-- 3) Tight coordination through a new interface between vO-DUs (case 3 shown in figure 4.10.3.2-2)
-
-
-
-Figure 4.10.3.2-2: Multi-vendor slices coordination scheme options diagram. It shows three coordination levels: loose, moderate, and tight. Each level shows an SMO (Service Management & Orchestration Framework) with Non-RT RIC and Near-RT RIC connected via A1. The Near-RT RIC connects via E2 to Shared Computing Resources containing VNF A (Vendor A, blue) and VNF B (Vendor B, green). Each VNF has an O-CU and O-DU connected via F1. The O-DUs connect to an O-RU. In the 'loose' case, coordination is via O1/A1. In the 'moderate' case, coordination is via an X2 interface between O-CUs. In the 'tight' case, coordination is via a 'New IF' between O-DUs.
-
-Figure 4.10.3.2-2: Multi-vendor slices coordination scheme options
-
-In case 1, a resource allocation between slices or vO-DU/vO-CUs is provisioned through O1/A1 interface and each pair of vO-DU and vO-CU will allocate radio resources to each customer within radio resources allocated by Near-RT RIC and/or Non-RT RIC.
-
-In case 2, a resource allocation can be negotiated between slices or vO-DU/vO-CUs through E2, X2 and F1 after provisioned through O1/A1 interface.
-
-If a more adaptive radio resource allocation is needed (case 3), a more frequent negotiation would be required. This can potentially be achieved via an interface or API extension between vO-DU(s).
-
-### 4.10.4 Benefits of O-RAN architecture
-
-The proposed multi-vendor slices approach will not only enable operators to utilize different vendor's strengths for particular service/slice type but also provide opportunities for additional RAN sharing use cases. The coordination needed between different vendors CU(s)/DU(s) can be realized through O-RAN architecture where Near-RT RIC and Non-RT RIC can coordinate CU(s)/DU(s) to efficiently allocate and use resources across these multi-vendor slices.
-
-## 4.11 Dynamic spectrum sharing (DSS)
-
-### 4.11.1 Background information
-
-As we transition from 4G to 5G, the spectral resources used for 5G deployment is a key consideration and this situation varies from one operator to another. Though, new C-band resources between 3-6 GHz and mmWave bands have been acquired by operators, these bands suffer from great propagation and penetration loss, limiting their coverage to users in proximity of the cell site, this is compelling particularly on the UL where the UE device is power constrained. This mandates the requirement of 5G deployment on lower bands (i.e., below 2GHz), which are widely used in existing 4G LTE deployments. Operating on lower bands along with non-standalone mode of 5G deployment helps to cover large geography, enables seamless mobility between 4G and 5G while being sensitive to overall cost of deployment. In addition, DSS offers the advantage of dynamically sharing the available spectrum adapting to the changing work loads of 4G and 5G network.
-
-### 4.11.2 Motivation
-
-DSS is compelling considering the need for operators to dynamically share already deployed spectral resources between LTE and NR devices without degrading the QoE of the current 4G subscribers while offering the same level of coverage to support NR devices, with the consideration that they will be rolled out in an incremental manner. The objective of this use case is to propose DSS in the context of the O-RAN architecture, specifically to realize it as an application in the RIC framework. This would particularly benefit vRAN implementations when the 4G/5G CU/DU are from different vendors and one could leverage RAN data over ORAN's framework for traffic prediction, resource management and control functions. Towards this, we identify the intelligent control functions which can be realized as a DSS application to augment the L2/L1 control functions defined as part of LTE-NR coexistence in Rel-15/16.
-
-### 4.11.3 Proposed solution
-
-The architectural context for the proposed solution is shown in figure 4.11.3-1, where DSS enables 4G and 5G UEs to operate over the same spectrum identified as X (typically low band), while 5G itself could operate on new bands Y (typically high band) not used by current 4G deployment. In a typical setting, Y would offer higher capacity, low latency and smaller coverage, while X would be used to offer reasonable capacity along with larger coverage. 3GPP specifications offers DSS support over X2/Xn interface to enable dynamic sharing of spectrum resource, in addition to L2/L1 adaptation for 5G-NR to co-exist with LTE subscriber.
-
-When DSS is enabled in the SA mode, 5G UE would be capable of operating on lower LTE bands (below 2GHz), C and mmWave bands and requires connectivity only to the gNBs. The sharing of the LTE bands between LTE and 5G data channels are achieved by both 4G scheduler and 5G scheduler, assisted by the coordination function, complimented by the RIC, between them.
-
-For 5G NSA mode, the 5G UE is required to have dual connectivity capability and be able to connect to eNBs on LTE bands for control plane requirements and user plane connectivity towards the LTE and/or 5G depending on deployment requirements. In the scenario where gNB only operates on 5G C or mmWave bands, the sharing of the LTE frequency band between 4G and 5G UEs can be solely fulfilled by eNB MAC scheduler, as the two devices are indistinguishable from L2/L1 perspective. While, if the gNB is required to operate on lower LTE bands as well, then spectral sharing needs to be coordinated between the LTE and 5G schedulers.
-
-The use case proposes to conduct DSS related policy, configuration, resource management and control functions using the Non-RT and Near-RT functions over open interfaces proposed by ORAN.
-
-An abstracted view of how DSS application can be realized using the Non-RT and Near-RT RIC components is shown in figure 4.11.3-2. The DSS over RIC can be realized as multiple applications considering its multiple optimization and operational objectives. One possible logical breakdown is as a resource management application (DSS-app) managing the shared spectrum resource adapting to dynamic 4G and 5G specific workload requirements in various local contexts,
-
-and another application (RAT-app) to configure, control and monitor DSS rules in the CU/DU corresponding to the LTE and 5G cells. The DSS-app engineers to translate the global DSS objectives such as workload requirements for a region and time-of-day to spectrum sharing policies such as max/min bandwidth threshold at a local level (e.g., central office). The RAT-app then translates the DSS-app’s resource policies to RAT specific configuration and control actions communicating with the respective CU/DU instances.
-
-
-
-This diagram illustrates the RIC-based DSS architecture. At the top, the SMO (Service Management and Orchestration) contains a nonRT-RIC with an R-APP(DSS). Below it, the nRT-RIC contains an X-APP(DSS). The nRT-RIC is connected to the SMO via the O1 interface and to the CU+DU (LTE) via the A1 interface. The CU+DU (LTE) is connected to the CU+DU (5G) via the X2/Xn interface. Both CU+DU units are connected to the RAN (Radio Access Network) via the E2 interface. The RAN includes NG-eNodeB/eNB and gNodeB units. The NG-eNodeB/eNB is connected to the CU+DU (LTE) and the gNodeB is connected to the CU+DU (5G). The RAN is also connected to the EPC/NGCore. The RAN serves three types of UEs: UE-4G, UE-4G+5G, and UE-5G. The RAN is shown with two spectrum pools: Spectrum X and Spectrum X+Y. The X2/Xn interface is also shown between the CU+DU (LTE) and the CU+DU (5G).
-
-Figure 4.11.3-1: RIC-based DSS architecture
-
-Figure 4.11.3-1: RIC-based DSS architecture
-
-
-
-This diagram shows a realization of the RIC-based DSS architecture. The SMO at the top contains a NonRT RIC with a DSS-App and RAT-App-4G/5G, located in a Regional Cloud. Below the SMO is the NearRT RIC with a DSS-App and RAT-App-4G/5G, located in a Central Office. The NearRT RIC is connected to the SMO via the O1 interface and to the RAN via the A1 interface. The RAN contains (CU/DU) 4G and (CU/DU) 5G units, which are connected to the NearRT RIC via the E2 interface. The RAN serves 4G/5G UEs. The NonRT RIC is connected to the NearRT RIC via the O1 interface. The NearRT RIC is connected to the RAN via the E2 interface.
-
-Figure 4.11.3-2: RIC-based DSS realization
-
-Figure 4.11.3-2: RIC-based DSS realization
-
-The main goal of the Non-RT DSS-App is to provide long-term policy or intent as a scheduling guidance to 4G and 5G scheduler considering business, user, spatial and temporal workload factors and the main functionality of Non-RT RAT-App is to translate the global DSS policies from Non-RT DSS-App to RAT specific policies to the RAT-App in the Near-RT RIC over A1.
-
-The main functionalities of the Near-RT DSS-App include policy translation between Non-RT DSS-App to RAT specific configuration to the Near-RT RAT-App. Furthermore, it is actively involved in closed-loop decision using the KPIs from the RAN adapting to the needs of the 4G and 5G cells. The main functionality of Near-RT RAT-App is to perform RAT specific configuration, control and data subscription over E2 interface with RAN (CU/DU components).
-
-### 4.11.4 Benefits of O-RAN architecture
-
-Using RIC based implementation of DSS benefits from using the non-real-time and near-real-time data from the RAN to influence the 4G/5G MAC scheduler’s near and long-term resource management policies and scheduler configuration. This is in addition to the value driven from control over open interfaces and using third party DSS applications. This is in contrast to synchronizing the 4G and 5G schedulers using closed resource management functions. Some scenarios where we foresee the advantage of a RIC based DSS include:
-
-- 1) DSS over RIC allows policy driven resource management between the 4G and 5G schedulers, aided by predictive intelligence. Furthermore, DSS requires synchronizing the MAC schedulers to avoid scheduling interference. However, the granularity of synchronization depends on the nature of workload. While workloads that are bursty in nature can require close to per-TTI synchronization, predictable workload could be handled without trading-off significant efficiency with coarser TTI synchronization. The latter would be workloads DSS over RIC would be suitable for, which would also be in line with Near-RT RIC’s operational requirement of 10ms-1s control loop latency.
-- 2) DSS over RIC can also improve resource management efficiency over multiple 4G/5G spectrum sharing cells. In this scenario, the RIC could use the global data spanning distributed cell sites, aided with predictive models to share the spectral resources dynamically. For example, data on predictive LTE or 5G user mobility can be used to predict the bandwidth requirement in adjacent 4G and 5G cells. This bandwidth decision can be then coordinated in advance across multiple distributed 4G/5G cells.
-
-- 3) DSS over RIC can also be useful when the 4G/5G cells can only overlap over the cell edge, in which case UE related information such as RSRP/RSRQ, PDCP throughput can be used by the Near-RT RIC to identify the set of overlapping cells along with the projected workload. This information is then used to slice the shared resource among the cell edge users to avoid interference by the respective schedulers while optimizing resources for the cell center users.
-
-## 4.12 NSSI resource allocation optimization
-
-### 4.12.1 Background information
-
-5G networks are becoming increasingly complex with the densification of millimeter wave small cells, and various new services, such as eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low Latency Communications), and mMTC (massive Machine Type Communications) that are characterized by high speed high data volume, low speed ultra-low latency, and infrequent transmitting low data volume from huge number of emerging smart devices, respectively. It is a challenging task for 5G networks to allocate resources dynamically and efficiently among multiple network nodes to support various services.
-
-### 4.12.2 Motivation
-
-eMBB, URLLC, and mMTC services in 5G are typically realized as NSI(s) (Network Slice Instance(s)) and the resources allocated to NSSI (Network Slice Subnet Instance) to support the O-RAN nodes can be optimized according to the service requirements. As the new 5G services have different characteristics, the network traffic tends to be sporadic, where there can be different usage pattern in terms of time, location, UE distribution, and types of applications. For example, most IoT sensor applications can run during off-peak hours or weekends. Special events, such as sport games, concerts, can cause traffic demand to shoot up at certain times and locations. Therefore, NSSI resource allocation optimization function trains the AI/ML model, based on the huge volume of performance data collected over days, weeks, months from O-RAN nodes. It then uses the AI/ML model to predict the traffic demand patterns of 5G networks in different times and locations for each network slice subnet, and automatically re-allocates the network resources ahead of the network issues surfaced.
-
-The resource quota policies associated with RAN NFs (E2 nodes) included in the respective NSSIs enable 5G network providers to optimize or prioritize the utilization of the RAN resources across slices and supports the flexibility to share resources optimally across critical service slices during resource surplus or scarcity. For example, an NSSI allocated for premium service can receive a major share of the resources compared to a slice allocated for a standard/best-effort service. Another such example is the scenario of additional resource allocation for emergency services. An important consideration here is that the NSSI resource quota policies focus on maximization of resource utilization across the NSSIs. The resource quota policies can be used as a constraint for resource allocation that defines the range of resources that can be allocated per slice. One use case for applying such a constraint is the analysis and decision based on history of resource allocation failure that can be reflected in the RAN node measurements. Here resource quota policy can be provisioned to control the minimum, maximum and dedicated resources that need to be allocated based on the historical pattern.
-
-### 4.12.3 Proposed solution
-
-The NSSI resource allocation optimization on the Non-RT RIC is shown in figure 4.12.3-1, and can consist of the following steps:
-
-- 1) Monitoring: monitor the radio network(s) by collecting data via the O1 interface, including performance measurements (that are measured per S-NSSAI (TS 28.552 [i.17])) such as mean DL PRB used for data traffic, mean UL PRB used for data traffic, average DL UE throughput in gNB, average UL UE throughput in gNB, number of PDU sessions requested to setup, number of PDU sessions successfully setup, distribution of UL UE throughput in gNB, etc.
-- 2) Analysis & decision:
-
-- 2a. Utilize AI/ML models to analyse the measurements and predict the future traffic demand, including the RRMPolicyRatio IOC limits, for each NSSI for a given time and location.
-- 2b. Determine the actions needed to add or reduce the resources (e.g., capacity, VNF resources, slice subnet attributes (TS 28.541 [i.16]), etc.) for the RAN NFs (E2 nodes) included in the respective NSSI at the given time, and location.
-- 3) Execution: execute the following actions to reallocate the NSSI resources:
- - 3a. Re-configure the NSSI attributes, including RRMPolicyRatio IOCs (TS 28.541 [i.16]) via the OAM functions in SMO which uses O1 interface to configure the E2 nodes.
- - 3b. Update the cloud resources via the O2 interface.
-
-
-
-The diagram illustrates the architecture for NSSI resource allocation optimization. At the top is the "Service management & Orchestration Framework" containing the "Non-RT RIC". Inside the Non-RT RIC is a block for "NSSI Resource Allocation Optimization" which performs "2. analysis & decision". To its left is the "O-Cloud M&O" block. Below the SMO is the "Near-RT RIC" and a set of "Network functions" enclosed in a dashed box. The network functions include "O-CU-UP", "O-CU-CP", "O-DU", and "O-RU". At the very bottom is the "O-Cloud".
-
-Key interactions and interfaces shown:
-
-- 1. monitoring**: An arrow from the Network Functions to the Non-RT RIC.
-- 2. analysis & decision**: Internal process within the Non-RT RIC.
-- 3.a. execution**: An arrow from the Non-RT RIC to the Network Functions via the **O1** interface.
-- 3.b. execution**: An arrow from the O-Cloud M&O to the O-Cloud via the **O2** interface.
-- A1 interface**: Connects Non-RT RIC to Near-RT RIC.
-- E2 interface**: Connects Near-RT RIC to O-CU-UP, O-CU-CP, and O-DU.
-- F1-U / F1-C interfaces**: Connect O-CU-UP/CP to O-DU.
-- Open Fronthaul interface**: Connects O-DU to O-RU.
-
-Diagram illustrating the realization of NSSI resource allocation optimization over Non-Real Time RIC.
-
-Figure 4.12.3-1: The realization of NSSI resource allocation optimization over Non-Real Time RIC
-
-### 4.12.4 Benefits of O-RAN architecture
-
-This use case is based on the retrieval and analysis of long term performance data captured from RAN nodes and the generation of AI/ML models for re-allocation of network resources based on the prediction of traffic demand patterns of 5G networks, which is made possible by O-RAN’s AI/ML based architecture.
-
-## 4.13 Local indoor positioning in RAN
-
-### 4.13.1 Background information
-
-Cellular network-based positioning is an important technology for 5G vertical industries, individuals and operators, especially in local indoor scenarios. For instance, mall can provide value-added services, such as local indoor navigation and shop recommendation by leverage real-time indoor positioning. Industrial manufacturing field should send real-time safe warning to remind operators keep away from the dangerous area which would also need real-time indoor positioning.
-
-NR positioning is introduced by 3GPP Rel.16. The Location Management Function (LMF) resides in core network acts as a location server. LTE Positioning Protocol (LPP) is reused for the UE measurements and NR Positioning Protocol “a” (NRPPa) based on LPPa is used for the gNB measurements [i.18]. The NR Positioning Protocol A (NRPPa) PDUs carry
-
-E-CID, OTDOA are routed between eNB/gNB and the LMF via AMF. The AMF routes the NRPPa PDUs transparently based on a routing ID corresponding to the involved LMF over NG-C interface without knowledge of the involved NRPPa transaction. This long route messages between eNB/gNB and centralized LMF can suffer network jitters and leads to un-real-time UE location results. For some local indoor scenario, e.g., mall and industrial manufacturing, it would be better to directly deploy the positioning function in the RAN side and expose UE location to local applications.
-
-### 4.13.2 Motivation
-
-For local indoor scenarios, the positioning function inside RAN is envisioned to be a promising solution. It not only reduces the latency of positioning but also can reuse the edge cloud infrastructure in RAN. In the context of O-RAN architecture, the positioning function can be deployed as a positioning xApp in the Near-RT RIC. The positioning xApp computes the UE location and optional velocity based on the positioning measurement obtained via the E2 interface.
-
-One example is that distributed indoor small base station in the operator's domain can provide UE positioning service by adding Near-RT RIC with positioning xApp. The positioning related information report from small base station to the positioning xApp inside Near-RT RIC can be measured based on the uplink SRS information. By leveraging multi-point positioning, field strength positioning and other positioning algorithms, positioning xApp inside Near-RT RIC can conduct a real-time position of UE.
-
-### 4.13.3 Proposed solution
-
-Cellular network based positioning procedure mainly includes two main steps: 1) positioning measurements reports; and 2) position computation and optional velocity estimation based on the measurements. The local indoor positioning in RAN use case mainly involves the Near-RT RIC, E2 nodes and potentially Non-RT RIC in the O-RAN architecture. To enable the local indoor positioning in RAN, Near-RT RIC should be able to discover the location measurement capability of the E2 nodes and subscribe the positioning measurements based on the chosen positioning algorithm and positioning QoS requirements.
-
-Non-RT RIC can also be leveraged to provide the AI/ML model if machine learning based algorithm is selected for the positioning. In this case, Non-RT RIC trains the AI/ML position model based on the historical positioning measurements (e.g., RSSI) and the labeled user location (e.g., by manual or by Minimal Drive Test (MDT)). Then, the trained positioning AI/ML model can be deployed to Near-RT RIC for real-time positioning inference.
-
-The E2 nodes are expected to provide positioning measurements to Near-RT RIC as required. The measurements report can be periodical, or event driven based on Near-RT RIC subscription. Near-RT RIC can also adjust the corresponding positioning measurement configurations in E2 nodes to assure the measure requirement. What kind of positioning measurements need to be reported from E2 node depend on the subscription request from positioning xApp in Near-RT RIC. For instance, the positioning measurements can include E-CID, OTDOA, UTDOA, TOA, RSSI, RSRQ and RRU antenna ID if it is the indoor system. The report granularity is expected in the order of 10-100 ms.
-
-The positioning xApp in Near-RT RIC can pass the positioning results to the SMO for further exposure. Furthermore, Near-RT RIC can also expose the positioning results to edge application nearby in a secure manner (via API gateway with firewall).
-
-### 4.13.4 Benefits of O-RAN architecture
-
-By enabling the local indoor positioning xApp in Near-RT RIC, it helps to reduce the latency of positioning in local indoor scenarios. Moreover, Near-RT RIC covers multiple E2 nodes, it can track UE location in case of mobility within certain areas.
-
-## 4.14 Massive SU/MU-MIMO grouping optimization
-
-### 4.14.1 Background information
-
-The massive MIMO is one of the key technologies for 4G and 5G. Due to the multi-antenna transmission and reception, this technology can inherently provide diversity and improve capacity by targeting high gain antenna beams towards one or multiple subscribers, thus improving the receive power levels and spatially filtering the interference from neighboring subscribers and transmission points. The case that only one subscriber is served by a given physical resource block of a massive MIMO cell in a transmission interval is called Single-User MIMO (SU-MIMO). While the case that multiple subscribers are served by a given physical resource block of a massive MIMO cell in a transmission interval is called Multi-User MIMO (MU-MIMO).
-
-In the commercial deployment, the massive MIMO eNB/gNB support both SU-MIMO and MU-MIMO transmission. The SU-MIMO and MU-MIMO are targeting for different scenarios and can achieve different spectral efficiency. Some subscribers can be stationary, some subscribers can be pedestrian, and some subscribers can be moving at a high speed. The performance of MU-MIMO is very susceptible to subscriber's moving speed, while the performance of SU-MIMO is relatively robust to subscriber's moving speed. Additionally, some subscribers can have VoLTE or VoNR traffic, some subscribers can have download/FTP traffic, and some subscribers can have YouTube-like traffic. The performance of MU-MIMO considerably reduces in the low traffic volume scenario, while the performance of SU-MIMO is relatively robust to low traffic scenarios.
-
-The spectral efficiency of SU-MIMO and MU-MIMO differ from each other. The spectral efficiency of MU-MIMO can be several times of spectral efficiency of SU-MIMO. Furthermore, SU-MIMO and MU-MIMO have different requirement for C-DRX, SRS, and other RRC configurations. These RRC configurations can be optimized based on scenario information.
-
-### 4.14.2 Motivation
-
-The massive SU/MU-MIMO grouping optimization use case aims at proactively and continuously improving cell and/or user-centric transmission efficiency and reliability in a massive MIMO deployment area by adapting appropriate transmission methods (e.g., SU-MIMO, MU-MIMO) for each user. The massiveness of available measurement input data, the complexity, pro-activeness as well as near-real time requirement suggest the application of machine learning techniques of input data analytics as well as use case decision generation.
-
-The objective of this use case is to allow the operator and vendor to optimize SU/MU-MIMO transmission by means of policies, configuration, or machine learning techniques, according to objectives defined by the operator.
-
-### 4.14.3 Proposed solution
-
-#### 4.14.3.1 Solution 1
-
-Non-RT RIC inference solution is shown in figure 4.14.3.1-1. In this solution, Non-RT RIC is for SU/MU-MIMO grouping decision.
-
-The SMO should collect the necessary configurations, performance indicators, measurement reports data from RAN nodes triggered by Non-RT RIC if required, and Non-RT RIC should retrieve user enrichment information (e.g., GPS information, traffic information) from the application server. When the optimization objective fails, it triggers the AI/ML model re-training, data analytics and optimization in Non-RT RIC.
-
-The Non-RT RIC should enable to retrieve necessary configurations, performance indicators, measurement reports and other information (e.g., user GPS information, traffic information) for the purpose of constructing/training relevant AI/ML models. The Non-RT RIC should use the trained AI/ML model to decide the UE list for SU-MIMO group and MU-
-
-MIMO group by inferring the mobility, traffic model of each user. Additionally, Non-RT RIC should also decide RRC configuration for SU-MIMO group and MU-MIMO group, such as SRS and C-DRX configuration, etc.
-
-The Near-RT RIC should be able to retrieve SU/MU-MIMO grouping, and related RRC configurations from Non-RT RIC (if it configures over A1). Moreover, it can send the configurations to E2 nodes by policy.
-
-The RAN nodes should send proper RRC configuration accordingly for UE in both SU-MIMO and MU-MIMO groups, do SU-MIMO scheduling for UE in SU-MIMO group, and do SU-MIMO or MU-MIMO scheduling for UE in MU-MIMO group dynamically. The RAN nodes should collect and report the performance measurement to SMO related to SU-MIMO and MU-MIMO spectral efficiency. For example, average layer, rank, and throughput for SU-MIMO and MU-MIMO.
-
-
-
-Diagram of Solution 1: Non-RT RIC centered SU/MU-MIMO grouping. The diagram shows three main components: SMO (top), Near-RT RIC (middle), and E2 Nodes (bottom). The SMO contains a Non-RT RIC and an AI/ML block. The Non-RT RIC is connected to an App Server via an External EI/F interface. The AI/ML block is connected to the Non-RT RIC. The Non-RT RIC is connected to the Near-RT RIC via an A1 interface. The Near-RT RIC contains an xApp block. The xApp block is connected to the E2 Nodes via an E2 interface. The E2 Nodes contain an O-DU block, which in turn contains a MAC Scheduling block. Arrows indicate the flow of information: from the App Server to the SMO, from the SMO to the Near-RT RIC, from the Near-RT RIC to the E2 Nodes, and from the E2 Nodes back to the SMO.
-
-Figure 4.14.3.1-1: Solution 1: Non-RT RIC centered SU/MU-MIMO grouping
-
-#### 4.14.3.2 Solution 2
-
-Near-RT RIC inference solution is shown in figure 4.14.3.2-1. This solution is Near-RT RIC centered SU/MU-MIMO grouping decision. Another alternative is that the Near-RT RIC just provides the mobility and the traffic model prediction result over E2 interface. The E2 node makes final decision on SU/MU-MIMO grouping.
-
-The SMO should collect the necessary configurations, performance indicators, measurement reports data from RAN nodes triggered by Non-RT RIC if required, and Non-RT RIC should retrieve user enrichment information (e.g., GPS information, traffic information) from the application server when the optimization objective fails, and it triggers the AI/ML model re-training, data analytics and optimization in Non-RT RIC.
-
-The Non-RT RIC should enable the operators to retrieve necessary configurations, performance indicators, measurement reports and other information (e.g., user GPS information, traffic information) for the purpose of constructing/training relevant AI/ML models. The Non-RT RIC should send enrichment information to Near-RT RIC by A1-EI I/F. The Near-RT RIC supports deployment and execution of AI/ML model from Non-RT RIC. The Near-RT RIC does ML inference to decide the UE list for SU-MIMO group and MU-MIMO group by inferring the mobility, the traffic model of each user. Additionally, Near-RT RIC should decide RRC configuration for SU-MIMO group and MU-MIMO group, such as SRS and C-DRX configuration, etc.
-
-The Near-RT RIC should be able to send the configurations to E2 nodes by policy.
-
-E2 nodes should send proper RRC configuration accordingly for UE in both SU-MIMO and MU-MIMO groups, do SU-MIMO scheduling for UE in SU-MIMO group, and do SU-MIMO or MU-MIMO scheduling for UE in MU-MIMO group dynamically. E2 nodes should collect and report performance measurement to SMO related to SU-MIMO and MU-MIMO spectral efficiency. For example, average layer, rank, and throughput for SU-MIMO and MU-MIMO. An E2 node can also decide on the SU/MU-MIMO grouping; the E2 nodes should retrieve the mobility and the traffic model prediction
-
-result over the E2. E2 nodes should support the advanced MAC scheduling algorithms that decide to do SU-MIMO or MU-MIMO transmission for each user considering the user mobility and traffic model prediction.
-
-
-
-Diagram of Solution 2: Near-RT RIC centered SU/MU-MIMO grouping. The diagram shows three stacked boxes representing architectural layers. The top box is 'SMO Model training' containing 'Non-RT RIC' and 'AI/ML', connected to an 'App Server' via 'External EI/F'. The middle box is 'Near-RT RIC' containing 'xApp' and 'AI/ML' (with 'ML Inference'), connected to the SMO via 'A1' and to the bottom box via 'E2'. The bottom box is 'E2 Nodes' containing 'O-DU' and 'MAC Scheduling'. An 'O1' interface line connects the SMO and Near-RT RIC to the E2 Nodes.
-
-Figure 4.14.3.2-1: Solution 2: Near-RT RIC centered SU/MU-MIMO grouping
-
-### 4.14.4 Benefits of O-RAN architecture
-
-The advantages the O-RAN architecture provides to massive MIMO SU/MU-MIMO grouping optimization use case include the ability to apply and combine both, non- and near real-time analytics, machine-learning, and decision making for various sub-tasks of this use case for a cell-centric and /or user (group) centric point of view. The Non-RT RIC supports long-term AI/ML training based on enrichment information. O-RAN interfaces such as O1, A1, and E2 has support for necessary data, policy, and configuration exchanges between the architectural elements. These advantages motivate massive MIMO SU/MU-MIMO grouping optimization to run on O-RAN based RAN implementations.
-
-## 4.15 O-RAN signalling storm protection
-
-### 4.15.1 Background information
-
-Society is increasingly dependent on network connectivity at any time and in any place and increasing diversity of device types ranging from complex devices such as smart phone to very simple and low-cost IoT devices are connecting to the network. The sheer number of connected devices, as well as the wide range of device types, makes the mobility network subject to accidental or intentional attacks that can disrupt the regular usage of the network. Given that life-critical applications are moving to wireless networks, such network disruptions are not only an inconvenience but can have impact on life and health of individuals. The O-RAN architecture offers an opportunity to address such security challenges in customizable and creative ways by utilizing the Near-Real-Time RIC xApps and Non-Real-Time RIC rApps.
-
-### 4.15.2 Motivation
-
-The main defense mechanism against attacks coming from the devices toward the network is based on configuration of the devices themselves and trust that the devices will indeed comply to restrictions defined by mobility standards. One such defense mechanism is the back-off timer that restricts the number of repeated device registrations, thus preventing devices from overloading the network with attaches. If this trust is breached there are no other options for defending the network rather than rejecting (denying service) randomly to both benign and malicious devices, a state which is equivalent to DDoS. Unfortunately, even today the network has few hundreds of device types that accidentally breach this trust and allow devices to aggressively attach to the network in a rate of few thousand times per hour (the maximum allowed number by standard is less than 20 attaches per hour). An attacker that finds a way to manipulate a large set of these
-
-vulnerable devices remotely can cause an attach storm that would lead to a long outage of large parts of the network. Furthermore, this attacker can continue this attack over many hours, each time picking few thousand of devices from a large pool of millions of devices available; the network carrier will not be able to stop this attack without intelligent and fine-grained controls to act against a certain patterns of behaviour. The good news is that detecting these aggressive devices is possible as their behaviour is very different from the other devices in the network. What the network really needs is to apply dynamic restriction over these devices to prevent them from overloading the control plane of the network. This restriction should be smart enough to still allow benign devices to register to the network without interruption. Having smart security control at the RAN can stop such attack and without overloading deeper parts of the network in the core.
-
-### 4.15.3 Proposed solution
-
-In order to protect the network from such UE originated signaling storms, an xApp can be built with two main functionalities: a DDoS detection capability and a DDoS mitigation capability. The DDoS detection capability has two parts: the near-real-time detection, which takes place in a RIC xApp and a non-real time detection, which takes place at the SMO and relies on enrichment data originated in external system (e.g., 5G core or OAM system) (see figure 4.15.3-1). The reason for this functionality split is that some detection logic relies on information that is available only at the core (such as IMSI, IMEI, device types, PLMN, etc.), while for other detection logic, the information available at the RAN will suffice. It is assumed that the Near-Real-Time RIC DDoS detection xApp provides a faster response with coarse grained aggressive device detection while the 5G core detection results computed by the SMO rApp provide slower response with finer grained aggressive device detection. It is noted that for some attack scenarios the xApp can perform the detection without the help of external information coming from the Non-Real-Time RIC. The DDoS mitigation xApp can implement an E2 INSERT-CONTROL control loop where the xApp can decide for each attach request if it should be accepted or rejected, or it can update an appropriate E2 POLICY when a UE is determined to be suspect. An exemplary E2 POLICY in this use case can allow suspected UEs to be blocked completely or throttled at a given rate at the E2 node.
-
-
-
-Diagram of RIC DDoS capability for 5G stand alone setup. The diagram shows a flow from 5G Core / OAM down to gNB and then to User Equipment (UE). The 5G Core / OAM sends 'Enrichment Information' to the Non-RT RIC/SMO. The Non-RT RIC/SMO contains a 'DDoS Detection rApp' which outputs '3b. A1 (e.g. List of misbehaving UE "GUTI"s)'. This is an optional component. The Near-RT RIC contains 'DDoS Detection xApp' and 'DDoS Mitigation xApp'. The gNB sends '1. REG. RQST.' to the UE and receives '5. REG. ACC/REJ' from the UE. The gNB also sends '2. E2 (ACCESS RQST)' to the Near-RT RIC. The Near-RT RIC performs '3a. RAN Detect' and sends '4a. E2 (INSERT-CONTROL)' and '4B. E2 (POLICY)' back to the gNB. A dashed box labeled 'Identifiers' lists 'C-RNTI, 5G-GUTI, Signal parameters, location'.
-
-Figure 4.15.3-1: RIC DDoS capability for 5G stand alone setup
-
-The detection algorithms should detect abnormal activity of high volume of control plane messages originating from a set of devices. The detection algorithm can change based on the network environment (metro, rural, enterprise, etc.) as well as dynamic usage trends and available devices. The output of the detection algorithm can also be of different levels of quality, depending on the attack type, in some cases the detection algorithm will produce list of specific devices while in other cases, it would only point to problematic geographic locations, specific gNBs or cell towers where the attack seems to be originated. Generally speaking, a detection algorithm should track registration behavior of individual devices and alert in the case that a threshold is exceeded for a given time threshold (e.g., one minute). The thresholds per tracking
-
-unit (i.e., cell site, gNB, AMF group, etc.) should be calculated dynamically based on normal behavior of the tracking unit. The learning of the normal behavior can be achieved using ML algorithm over time.
-
-An important concern regarding the detection report quality is the identifiers lifetime. Identifiers of network elements such as a gNB or cell tower are considered persistent over long periods of time. When considering device or subscriber related identifiers their life span depends on where they are collected. Specifically, equipment identifier (such as IMEI) or subscriber identifier (such as IMSI) are only visible at the network core and are not available at the RAN. Some RAN identifiers change upon every network attach and are allocated randomly (for example C-RNTI), while others persist longer such as the 5G TMSI. The available identifiers in the detection report depends on the nature of the attack: location, number of devices used, exploited vulnerability type and more. For example, if an aggressive device uses an RRC connection re-establishment procedure, the C-RNTI remains the same over the numerous connection attempts, while in the case of RRC connection establishment procedure there is a fresh randomly selected C-RNTI for each attempt. There are detection techniques to identify an aggressive UE that don't rely solely on its identifiers, rather on signal parameters such as signal quality or timing advance, which can in turn, help build a unique fingerprint of the aggressive device. An important disclaimer is that not all attack scenarios can be prevented. Specifically, in the case where the modem or chipset itself are compromised and communication parameters can be faked by the attacker, the detection methods mentioned above could be avoided.
-
-The mitigation functionality should support a set of actions, depending on the policy applied. These actions can be applied to a single UE, or a set of UEs that apply to a certain criterion. The criteria can be a location, a cell tower or a gNB. A UE set can be defined in a custom manner to include a list of UEs, where the criteria is based on considerations external to RIC, such as UE reputation, vendor, or vulnerability type. The actions applied to a single UE or set of UE should include (but not be limited to) rejecting attach requests, throttling attach requests (attach rate should not exceed a certain threshold), handover a set of devices to a different radio or applying a different slice to set.
-
-### 4.15.4 Benefits of O-RAN architecture
-
-The O-RAN architecture allows applying protection to the network at the edge, thus minimizing the effect of these signaling storm DDoS attacks on network resources.
-
-The combination of near-real-time logic at the Near-Real-Time RIC for fast detection, with slower scale analysis and input from the Non-Real-Time RIC and SMO provides a good mixture between quick reaction and advanced detection schemes. Lighter detection processes can be applied as xApps while more advanced heavy processing ML analytics can run externally and send input to RIC over the A1 interface.
-
-## 4.16 Congestion prediction and management
-
-### 4.16.1 Background information
-
-This use case provides a proactive approach to congestion handling in the base station by analysing the radio resource utilization and taking timely corrective action so as to mitigate any potential congestion in the system.
-
-### 4.16.2 Motivation
-
-Large-scale commercial cellular networks have many problems - like cell congestions leading to RLF (Radio Link Failure, etc.), handover failure, poor data rates etc. Network congestion is a crucial problem for the telecom operators as it affects the Quality of Service (QoS) of the users directly. An operator has many solutions like offload (across carriers, Wi-Fi, etc.) or antenna techniques (cell split, higher order MIMO, etc.) to handle congestion. However, the congestion patterns in the network are not fully understood and mitigation is done post facto at the expense of the prolonged user experience degradation. The congestion mitigation is critical for operators to retain their subscribers for operator and individual user
-
-experience. With 5G, the congestion needs to be handled to as to best utilize the radio resources. Today operators do not have a well-defined mechanism to predict congestion. The main objective of this use case is to use the embedded intelligence of O-RAN to predict the congestion ahead of time, so that operators can keep the cell congestion mitigation solution in place before the congestion is predicted to happen.
-
-### 4.16.3 Proposed solution
-
-CPM (Congestion Prediction & Management) architecture is proposed to detect and mitigate congestion pro-actively. In the CPM architecture, E2 node statistics [counters] are collected by the data collector of SMO. This is done over the O1 interface. The pre-processing of data is also done in the same place. Pre-processing includes adding VNF/cell names/numbers and ids to the data and converting counters into KPI using KPI logic. After preprocessing data is shared with Non-RT RIC deployed in the SMO using a data sharing entity. Non-RT RIC will invoke the corresponding training model/application in an AI server inside SMO (it can be placed outside SMO also). The data cleaning and training will happen and the predicted KPIs will be sent back to CPM rApp in Non-RT RIC. Machine learning models can be used to learn and predict the future traffic for the next hour/day/month. The prediction window can be configured by operators as per the available data and its periodicity. CPM rApp in Non-RT RIC will form the inference. Inference logic to define cell congestion can be like:
-
-1. The average user-perceived IP throughput < P Mbps
-2. DL PRB utilization > Q%
-3. Average RRC user > R
-
-The inference will contain the cell ids, information about whether the cell is congested or not, time stamp of cell congestion and predicted KPI value (to decide the congestion intensity). As per the CPM rApp information in Non-RT RIC, there are two options to mitigate cell congestion as follows:
-
-**Option a:** CPM rApp in Non-RT RIC transfers the inference to the CPM xApp in Near-RT RIC through A1 interface. Near-RT RIC can decide the mitigation solutions as per the inference. Mitigation solutions can include
-
-1. Switching to dual connectivity mode
-2. Debarring of user access
-3. Load sharing
-
-These solutions can be controlled over E2 interface.
-
-**Option b:** Non-RT RIC can also directly help to mitigate the congestion with the help of O1 interface. Some of the mitigation solutions can be
-
-1. Splitting a cell (assuming hardware support available)
-2. Add more carriers
-3. Switching to higher order MIMO
-4. Switching some of the users to Wi-Fi
-
-Finally, the E2 nodes feedback can be sent to Non-RT RIC through O1 interface. The proposed CPM solution is shown in figure 4.16.3-1 in detail.
-
-NOTE: There can be more mitigation solutions apart from the one provided in steps 6a and 6b (see figure 4.16.3-1). Choosing the mitigation solution is up to the operator to decide as per the congestion intensity (specified in the inference).
-
-
-
-The diagram illustrates the proposed congestion prediction management solution. At the top, a box labeled 'Can be On-Premise / Private Cloud / Public Cloud' contains 'Data Cleaning + Model Training' and an 'AI Server'. This is connected to the 'SMO Framework' via a blue arrow labeled '3'. The SMO Framework contains 'Non-Real Time RIC' with 'CPM rAPP', 'rAPP 2', and 'rAPP 3', as well as 'Data Collectors' and a 'Data Sharing Entity'. Below the SMO Framework is the 'Near-RT RAN Intelligent Controller (RIC)' with 'CPM xAPP' and 'xAPP'. A 'Statistics Collection' box (labeled '1') with counters for Cell-Id, PRB, RRC UE, and IP Throughput is connected to the RIC. The RIC connects to the 'O-CU-CP Container' and 'O-CU-UP Container' via 'O1' and 'E2' interfaces. The CU containers are connected to the 'O-DU (Container)' via 'F1-c' and 'F1-u' interfaces. The O-DU is connected to the 'O-RU (PNF)' via a '7-2x/ Ethernet' interface. Yellow circles with numbers 1-6a and 6b indicate key interaction points. A table on the left defines the 'RIC Use case' for 'Network Intelligence' as 'Congestion Prediction and Mitigation (CPM)'.
-
-| RIC Use case | |
-|----------------------|--------------------------------------------|
-| Network Intelligence | Congestion Prediction and Mitigation (CPM) |
-
-Proposed congestion prediction management solution diagram showing the flow of data and control between various O-RAN components including SMO Framework, RIC, CU, DU, and RU.
-
-Figure 4.16.3-1: Proposed congestion prediction management solution
-
-### 4.16.4 Benefits of O-RAN architecture
-
-All the main O-RAN components can leverage from proposed CPM use case. It predicts congestion before its occurrence so that an operator can configure the cell and prevent the degradation of QoS of a cell. AI server in SMO can be utilized for model training of KPIs. Similar models can be used to predict KPIs for other use cases as well. Non-RT RIC can be utilized to prepare inference based on predicted KPIs and congestion logic. These inference can be helpful for operators to choose on what solutions can be applied for a give congestion severity. CPM utilize Near-RT RIC for configuring a cell well before the congestion based on the inference and infrastructure dynamics.
-
-## 4.17 Industrial IoT optimization
-
-### 4.17.1 Background information
-
-In 3GPP Industrial Internet of Thing (IIoT) item, new scenarios with high reliability (i.e., $10^{-5}$ ~ $10^{-6}$ ) have been considered including factory automation, transport industry. To satisfy these scenarios requirements, several key features as below have been supported for IIoT in 5G system, such as data duplication and multi-connectivity enhancement (PDCP duplication, PDU session duplication, QoS flow duplication), time sensitive networking (Ethernet Header Compression (EHC), accurate reference timing provisioning, QoS and scheduling enhancements) and different prioritized transmission multiplexing.
-
-Based on O-RAN architecture some of these features can be optimized, e.g., PDCP duplication, EHC, and different prioritized transmission multiplexing. For PDCP duplication, up to 4 RLC entities/legs can be supported. RRC signaling is used for initial configurations. And MAC CE is used for dynamic control. According to 3GPP specifications definition, PDCP duplication can only be applicable for NR. For EHC, PDCP entities associated with DRBs can be configured by RRC to use EHC. Each PDCP entity carrying user plane data can be configured to use EHC. Every PDCP entity uses at most one EHC compressor instance and at most one EHC decompressor instance. For different prioritized transmission multiplexing, the lower priority transmission can be cancelled and preempted by the higher priority transmissions. RRC signaling is used for the related configurations.
-
-
-
-Non-RT RIC should be able to retrieve network data (network load, performance metrics, QoS flow 5QI, etc.) and external service information from SMO. The external enrichment information such as service type, traffic period, duration, packet size, KPI requirements can be provided by MEC server, APP server or industrial control platform, etc., to SMO. Non-RT RIC should be able to retrieve configured policy from SMO, e.g., cell edge user reliability KPI target, ethernet header compression efficiency. Additionally, Non-RT RIC should be able to deploy and update AI/ML model from SMO. Non-RT RIC should use AI/ML model to infer and decide related IIoT key techniques configurations, such as whether the QoS flow should map to DRB supporting duplication and EHC, whether high priority traffic can preempt transmission resource by cancelling the low priority traffic transmission.
-
-Near-RT RIC should be able to retrieve IIoT related configurations from Non-RT RIC (if it configures over A1). Near-RT RIC should be able to send the configurations to E2 nodes by policy.
-
-E2 node (O-CU, O-DU) should provide UE measurement report, performance metrics, etc., to SMO through O1 interface. E2 node should enforce E2 control policy or O1 configuration, if O1 configuration per UE can be supported.
-
-#### 4.17.3.2 Near-RT RIC solution of IIoT optimization
-
-The architecture of Near-RT RIC solution of IIoT optimization use case is given in figure 4.17.3.2-1.
-
-
-
-```
-
-graph TD
- ESI[External Enrichment Information] --> SMO
- subgraph SMO
- NonRT[Non-RT RIC
-Model training]
- end
- NonRT -- A1 --> NearRT[Near-RT RIC
-AI/ML]
- NearRT -- E2 --> E2Node[E2 Node]
- SMO -- O1 --> E2Node
-
-```
-
-Architecture diagram of Near-RT RIC solution of IIoT optimization use case. The diagram shows a stack of components: External Enrichment Information (orange box) pointing to SMO (light blue box). Inside SMO is Non-RT RIC (blue box) with Model training (yellow box). Non-RT RIC is connected to Near-RT RIC (blue box) via A1 interface. Near-RT RIC has AI/ML (yellow box). Near-RT RIC is connected to E2 Node (green box) via E2 interface. There is also an O1 interface connecting SMO and E2 Node.
-
-**Figure 4.17.3.2-1: Architecture of Near-RT RIC solution of IIoT optimization use case**
-
-Non-RT RIC should be able to retrieve network data (network load, performance metrics, QoS flow 5QI, etc.) and external service information from SMO. The external enrichment information such as service type, traffic period, duration, packet size, KPI requirements can be provided by MEC server, APP server or industrial control platform, etc., to SMO. Non-RT RIC should be able to train AI/ML model for Near-RT RIC. Additionally, Non-RT RIC should be able to evaluate the collected data and A1 policy feedback, if required, and generate or update the appropriate optimization policy, such as reliability targets, and sends it to the Near-RT RIC via A1 interface.
-
-Near-RT RIC should be able to deploy or update AI/ML model via O1 interface. Near-RT RIC should be able to receive an A1 policy from the Non-RT RIC and initiate the corresponding optimization procedure. Additionally, Near-RT RIC should be able to evaluate the performance data from the E2 nodes and monitor whether the performance is out of KPI targets which are indicated in the A1 policy. E.g., cell edge user performance cannot meet the A1 policy. Based on service estimation, i.e., service characteristics, and channel quality estimation, and A1 policy, the Near-RT RIC should infer and make decision of PDCP duplication on/off, RLC entity selection and high priority traffic preemption. Then, Near-RT RIC can generate new E2 policies or modify the existing ones to send them to the E2 nodes. If required, Near-RT RIC should send report to Non-RT RIC for evaluation and optimization.
-
-E2 node (O-CU, O-DU) should provide network metrics, etc., to SMO through O1 interface. E2 node should provide UE measurement report, performance metrics, and cell resource utility to Near-RT RIC through E2 interface. Additionally, E2 node should enforce E2 control policy.
-
-### 4.17.4 Benefits of O-RAN architecture
-
-The benefits of O-RAN architecture for IIoT use case include the ability to use external enrichment information provided by MEC server, APPs server, or industrial control platform to SMO. Based on the external service information and RAN information, AI/ML method is introduced to help generating IIoT key techniques strategies to improve performance of system and users. For SDAP sub-layer, it can provide semi-static QoS flow to DRB mapping rules. For PDCP and RLC sub-layer, semi-static EHC on/off configuration, semi-static or dynamic PDCP duplication activate/deactivate decision and RLC entities dynamic control/selection decision can be provided. For MAC and PHY, it can provide semi-static and dynamic PI and CI configurations when different prioritized transmissions are multiplexed. Besides, multi-E2 node coordination will be beneficial based on O-RAN architecture.
-
-## 4.18 BBU pooling to achieve RAN elasticity
-
-### 4.18.1 Background information
-
-Driving cost efficiency by improving the elasticity of workloads is one of the principal goals of cloudification. This use case presents BBU pooling as an opportunity to achieve RAN elasticity. O-RAN CADs describes multiple deployment options for the O-RAN cloudified NFs, which allows for different variants of centralization of these resources in the edge and regional clouds. In particular, cloudified BBUs can be deployed on a common hardware pool, centralized at the same cloud location. This centralization opens up the opportunity for O-RUs to be flexibly mapped to BBUs, thereby enabling RAN elasticity, while potentially lowering the costs in the long term.
-
-### 4.18.2 Motivation
-
-Pooling of BBU resources provides many benefits like having to maintain only a single large, controlled environment for many cell sites, better resiliency and agility to deal with unexpected failures and increases in demands, and allowing capacity to be added incrementally and assigned to cell sites as needed resulting in better overall utilization. More importantly, BBU pooling provides significant statistical multiplexing benefits due to better resource consolidation. The total resources required from the shared pool will be less than total resources required across distributed locations, because the peak of the sum of the traffic will generally be lower than the sum of the individual cell site traffic peaks. BBU pooling enables more aggressive capacity dimensioning based on different percentiles of resource consumption rather than for the peak consumption. This proposal addresses the scenarios where both O-CUs and O-DUs can be pooled, but for simplicity the following clauses focus on the description of O-DU pooling.
-
-### 4.18.3 Proposed solution
-
-A high-level depiction of approaches to O-DU pooling is shown in figure 4.18.3-1. The O-DU resources for multiple cell sites are pooled at a single centralized location or the *O-DU pool*. The Cloud Access Switch (CAS) at the O-DU pool aggregates traffic from the multiple front haul gateways and routes it to the appropriate O-DU blade based on the load balancing requirement. For the O-DU pooling use case, it is assumed that an open front haul exists with O-RAN defined 7-2x split. Based on the association between O-RUs and O-DUs, and the granularity at which the traffic is assigned from the O-RUs to the O-DUs, we define the following classes of O-DU pooling.
-
-- 1) **Class 0 pooling:** A scenario where an O-RU is assigned to a single specific O-DU statically, and the traffic from the O-RU is not split into subsets that could be assigned to different O-DUs. This is the same as simple centralization as defined in CADs V2.0. With class 0 pooling, re-assigning an O-RU to connect to a different O-DU would require significant “hands on” activity, and is performed very infrequently during specific maintenance windows.
-- 2) **Class 1 pooling:** A scenario where *n* O-RUs are initially assigned to a single O-DU during a specific period of time, but the O-RUs can be re-assigned to different O-DU at any point of time via orchestration procedures with the help
-
-of SMO. This automated re-assignment can be triggered outside maintenance windows, based on various performance criterion or for load balancing. Like with class 0 pooling, the traffic from the O-RU is not split into subsets that could be assigned to different O-DUs.
-
-- 3) **Class 2 pooling:** A scenario where n O-RUs are assigned to m O-DUs, and subsets of traffic from one O-RU are dynamically distributed (and load-balanced) across the O-DU resources within the O-DU pool using a cluster aware scheduler.
-
-
-
-Diagram illustrating Class 1 and Class 2 O-DU pooling architectures. Class 1 shows O-RUs connected to a Cloud Access Switch, which is connected to an O-DU Pool (O-DU blade 1, 2, 3) managed by an SMO. Class 2 shows O-RUs connected to a Cloud Access Switch, which is connected to an O-DU Pool (O-DU blade 1, 2, ..., k) managed by a Cluster aware Scheduler. Both diagrams show 'Option 7.2x split' at the switch.
-
-Figure 4.18.3-1: O-DU pooling
-
-With all classes of O-DU pooling, the total resources required from the shared pool will be less than total resources required across distributed locations, because the peak of the sum of the traffic will generally be lower than the sum of the individual cell site traffic peaks. In particular, class 1 and class 2 O-DU pooling enables more aggressive capacity dimensioning based on different percentiles of resource consumption rather than for the peak consumption. However, the key distinction between the classes of pooling is the granularity at which traffic can be load balanced across the O-DUs, which provides different statistical multiplexing benefits. While class 0 pooling provides a one-time statistical multiplexing gains at the time of initial deployment due to the centralization, class 1 pooling allows further load balancing benefits due to the automated and flexible re-mapping of O-RUs to the O-DUs periodically. However, the re-assignment of O-RUs needs to be performed during maintenance windows (or via hitless migration) to minimize service interruptions. Finally, class 1 pooling enables better handling of hot spots, and more efficient management of traffic loads and maintenance/upgrades.
-
-On the other hand, class 2 pooling dynamically assigns subsets of traffic to the O-DU resources in the shared O-DU pool. Hence, if some cell sites experience light traffic demand, while others experience high traffic demand, then subsets of traffic can be routed to O-DU resources in the shared pool such that the traffic is optimally consolidated among the O-DU resources needed to meet the performance requirements, leading to significant statistical multiplexing benefits. At one extreme, class 2 pooling allows each O-DU in the O-DU pool to have similar load (once the optimal number of blades have been predicted for a given time period), if each UE flow or each slot processing can be mapped to the least-busy blade for the duration of that flow. In addition, there is no service interruption as with class 1 pooling. Class 2 pooling could also be performed with more coarse-grained distribution of traffic subsets to the O-DUs. For example, traffic could be mapped to the least-utilized blade on a per UE basis or on a per-carrier basis within a TRP.
-
-### 4.18.4 Benefits of O-RAN architecture
-
-As described in clause 4.18.3, both class 1 and class 2 pooling are enabled by the O-RAN open fronthaul with LLS (option 7-2x split). Further, for class 1 pooling, O-RAN architecture standardizes the SMO functions needed to enable pooled BBUs including:
-
-- Management of O-DU & O-RU (registration/de-registration of O-RU to O-DU, registration of RU locations to SMO).
-
-- Orchestration features via O1/O2 interfaces and procedures for remapping O-RUs from one O-DU to another O-DU, implementing the orchestration control loops provided by the Non-RT RIC, hitless draining of cell traffic from one O-DU to another O-DU.
-- Monitoring performance/fault metrics to determine DU load and KPIs.
-
-Class 2 pooling is relatively less explored in the industry, aiming to provide fine-grained load scheduling across the O-DUs in the pool. For class 2 pooling, O-RAN architecture helps with:
-
-- Affinity of control and downlink data, supported by cluster aware scheduler.
-- Affinity between control and uplink data, supported by the cloud access switch or in the O-RU.
-- Configuration of the O-DU to support a wider range of sectors through the cluster aware scheduler.
-- Monitoring performance/fault metrics to determine DU load and KPIs.
-- Triggers for the scale-in/scale-out workflows in the SMO that manages the O-DU pool.
-- Fine-grained load balancing functions through the RIC that standardizes the role of CU-CP high.
-
-## 4.19 Integrated SON function within the O-RAN framework
-
-### 4.19.1 Background information
-
-Self-Organizing Network (SON) functionalities for 5G (3GPP TS 28.313 [i.14]) reduces the cost of running a mobile network by providing automated configuration, optimization, protection and healing functions and thus eliminating manual configuration of network elements right from initial deployment through the network operation. SON also helps better network performance and customer experience and can significantly improve OPEX-to-revenue ratio and help in realizing avoidable CAPEX.
-
-SON is an automation technology that enables the network to set itself up and self-manage resources and configuration to achieve optimal performance. The SON functions are handled by SON algorithms either individually or in groups. SON algorithms monitor the network(s) by collecting management data including MDAS (Management Data Analytics Service) data and subsequently analyse the data to determine if there are issues in the network(s) and what needs to be resolved.
-
-3GPP SON specification TS 28.313 [i.14] specifies the concepts, use cases, requirements, and procedures for the SON functionality. Based on the location of the SON algorithm, the implementation of SON solution is termed as
-
-- Centralized SON (C-SON - where the SON algorithms are executed in the 3GPP management system)
-- Distributed SON (D-SON - where the SON algorithms are executed in the network function layer) and
-- Hybrid SON (where the SON algorithm execution is spread across the network function layers and the management layers).
-
-Since the interfaces between various entities hosting the SON algorithms are not standardized, there can be interoperability issues in multi-vendor network deployments. This is further explained in detail in clause 4.19.2.
-
-### 4.19.2 Motivation
-
-The objective of this use case is to enable the realization of SON functions in the O-RAN architecture framework i.e., as rApps, xApps or as management entity functions through open interfaces in a way that inter vendor interoperability issues can be addressed.
-
-The following SON functions are of interest for operators for this use case definition:
-
-- Initial PCI allocation, conflict resolution and ANR (Automatic Neighbor Relations)
-- Mobility Load Balancing (MLB) and Mobility Robustness Optimization (MRO)
-- RACH optimization
-- Energy savings
-- Coverage and capacity optimization
-
-When the SON algorithms are realized in a centralized location, as a C-SON variant, the interface between C-SON and the RAN nodes, being proprietary, demands the operator to choose the same vendor for both SON solution and the RAN nodes. When the SON algorithms are realized in distributed fashion, as a D-SON variant, the interface between D-SON and the RAN nodes could be proprietary and internal to vendor's design. The performance of such vendor specific SON solutions affect KPIs as typical 5G deployments are expected to be multi-vendor based.
-
-When operators use management entities like NMS, EMS from a different vendor and RAN nodes (gNB-CUs, gNB-DUs) from different vendors, the following issues are observed:
-
-- D-SON implementations in different gNB-CU vendors cannot interoperate though they communicate each other via open Xn interface.
-- C-SON can be realized as either collocated with management entities (e.g., EMS/NMS) or as a standalone entity. Integrating the C-SON as a standalone entity with RAN nodes could lead to interoperability issues due to vendor specific interfaces.
-
-Integrating third party SON solutions partially leads to degradation of the overall operator KPIs. Non interoperable SON/RRM implementations have been seen to significantly impact the overall network performance. Even with operator assisted vendor and integrated third-party SON Solutions, it is difficult to deterministically quantify/confirm the output performance mainly due to the nature of multi-vendor implementations.
-
-The nature of band allocations in different geographic regions have led to some operators to consider using these new bands along with LTE bands for 5G network deployment. Large-scale deployment of small cells in urban areas is required to accommodate large traffic especially with smaller millimeter wave band cells (i.e., cell ISD of 100~200 meters). Therefore, the acquisition, deployment, and operation of ultra-dense cells become more important. This will force operators to explore small-sized and low weight base stations where multi-vendor interoperability of end-to-end system and realization of SON technology becomes necessary.
-
-### 4.19.3 Proposed solution
-
-The general SON functional solution in the O-RAN architecture is shown in figure 4.19.3-1. The SON algorithms are realized as rApps or as xApps or as a combination thereof through open interfaces in a way that inter vendor interoperability issues can be addressed. The A1 and E2 and optionally O1 interfaces will be used for the realization of the SON functions.
-
-
-
-Diagram of SON functions in O-RAN architecture. At the top is 'Service, Management & Orchestration' containing 'SON functions. Management Entity' and 'SON functions. Non-RT RIC' (with an 'ML Model.'). Below is 'Near-RT RIC' with 'SON functions.'. At the bottom is 'E2 Node.' connected to 'O-RU' via 'Open Fronthaul.' The 'Management Entity' connects to 'Near-RT RIC' via 'O1' and to 'E2 Node.' via 'A1'. The 'Non-RT RIC' connects to 'Near-RT RIC' via 'A1' and to 'E2 Node.' via 'E2'. Callouts explain: 'Time insensitive SON functions implemented within the management entity.' (pointing to Management Entity), 'Time insensitive SON functions implemented within the Non-RT RIC through rApps.' (pointing to Non-RT RIC), 'Enhanced O1 interface to support all the SON functions.' (pointing to O1), 'Time sensitive SON functions implemented within the Near-RT RIC through xApps.' (pointing to Near-RT RIC), 'Enhanced A1 interface to support all the SON functions/Profiles.' (pointing to A1), and 'Enhanced E2 interface to support all the SON functions.' (pointing to E2).
-
-**Figure 4.19.3-1: SON functions**
-
-As shown in figure 4.19.3-1, time insensitive SON functions like initial PCI, initial ANR, and energy saving can be implemented either at Non-RT RIC using separate rApp or in the management entities like EMS, NMS or at the SMO. A group of such functionalities can also be combined and executed in an rApp. The SON function related information can be exchanged either directly via O1 interface or via A1 & E2 interfaces. The dynamic or time sensitive SON functions will be realized in the xApps of RT-RIC. The actual SON algorithm implementation within xApps/rApps/management entities are implementation specific and it is out of scope of the current proposal, and the SON functions provide the derived SON configurations to the associated E2 nodes via E2 interface (in case of xApps).
-
-This approach helps provide a framework for the realization of the following SON functions within the existing O-RAN architecture. As an illustrative example, consider the PCI allocation SON function:
-
-When an operator wants to deploy a cell, the location for the E2 node/O-RU deployment is identified. As part of the plug-and-play functionality, the E2 node first establishes the link with the management entity via the O1 interface, to get the FCAPS configurations. Before the E2 node becomes operational, it needs the initial PCI allocated. At this stage as the E2 node will not be able to establish any link with the Near-RT RIC, there should be some SON functions within the SMO that can derive the initial SON configurations. Within the SMO, the SON functions can be realized either as rApps or through SON functions within the management entities. The initial PCI SON function should be equipped to get the location information of the E2 node being deployed. This can be provided by the E2 node itself across the O1 interface or an application can directly provide the location information to the management entity. The management entity can internally share it with the initial PCI function rApp. The initial PCI rApp can use this location information [azimuth, elevation, altitude, etc.,] to derive the possible neighbor nodes already deployed in and around the current node's location and the associated PCIs of these neighbors. The rApp can then derive a mutually exclusive PCI for the current node being deployed. This derived PCI acts as an initial PCI for the E2 node being deployed. This allocated PCI will be shared to the management entity internally and which in turn forwards to the node via the O1 interface. The E2 node will be operational with this initial PCI. Similarly, the initial PCI SON function can also be implemented within the management entity itself. In this case it can access the node's location information within the management entity database and the rest of the functionalities defined above for rApp case follows.
-
-When an E2 node becomes operational, there can be race conditions with other E2 nodes becoming operational resulting in a PCI conflict. To detect and correct such PCI conflicts during the lifetime of a deployed node, there can be a dynamic PCI SON functions, which could reside at the Near-RT RIC level as such PCI conflicts that needs to be detected and corrected at the earliest.
-
-### 4.19.4 Benefits of O-RAN architecture
-
-The functional entities of the current O-RAN architecture can be reused to realize SON functions to operators. The O-RAN specified interfaces such as O1, E2 and A1 interfaces will also be reused with appropriate modifications to enable the SON functions.
-
-By using the O-RAN framework, third-party SON algorithms (realized as an rApp, xApp or as a management entity function) can be easily integrated to achieve optimal performance, across a multi-vendor deployment scenario.
-
-## 4.20 Shared O-RU
-
-### 4.20.1 Background information
-
-The existing fronthaul specifications include role-based access control capabilities to restrict permissions to certain sections of an O-RU's configuration based on privileges as well as supporting parallel management interfaces for realizing hybrid fronthaul deployments. However, the current lower layer split architecture is constrained by having an O-RU node operate with a single O-DU node. This limits the ability of fronthaul system to be used to deliver enhanced use cases where multiple O-DU nodes can be used to enhance the capabilities offered using O-RAN's open fronthaul specifications.
-
-### 4.20.2 Motivation
-
-Already defined use cases, including RAN sharing as defined in clause 4.7 and multi-vendor slices as defined in clause 4.10 describe use cases where a common O-RU is operated with a plurality of O-DUs. More generically, deployments of a common O-RU node with multiple O-DU nodes offers the ability to support enhanced capabilities when using O-RAN's lower layer split, including:
-
-- Enhanced scalability and/or enhanced availability and/or enable access-specific node deployments in fronthaul systems, where multiple O-DU nodes are deployed by a single operator and connected to a Shared O-RU.
-- Enhanced sharing capabilities where multiple O-DU nodes are deployed by different operators and connected to a common Shared O-RU node.
-
-For single operator deployments, the decomposition of the RAN into O-RU and O-DU functional components based on interoperable O-RAN defined interfaces enables new approaches to the delivery of enhanced systems whereby multiple O-DU nodes can be deployed in different configurations, including:
-
-- “active/standby configuration” to support increased availability,
-- “horizontal configuration” by adding more O-DU nodes to (or removing nodes from) an O-RAN system to enable scale in/out,
-- “access-centric configuration” to support combined LTE and NR deployments, where one or more O-DU nodes are used to deliver LTE functionality and one or more other O-DU nodes are used to deliver NR functionality,
-- configuration supporting a case to add new O-DU provided from a different vendor, migrating to O-DU with providing slices. Radio resource is allocated among O-DUs/slices dynamically. Single O-CU will cover multiple O-DUs per UE.
-
-As described elsewhere in this document, RAN sharing is envisioned as an efficient and sustainable way to reduce the network deployment costs, while increasing network capacity and coverage. Accordingly, the open and multi-vendor nature of the O-RAN architecture can accelerate the introduction and development of RAN sharing solutions.
-
-For multi-operator deployments, the decomposition of the RAN into O-RU and O-DU functional components based on interoperable O-RAN defined interfaces leads to new options for RAN sharing:
-
-- Shared O-RU, where a common O-RU node is shared and dedicated O-RU resources (e.g., spectrum, transmit power, etc.) and dedicated O-DU node is used by each sharing operator.
-- Shared O-RU, where a common O-RU is shared and dedicated O-DU node is used by each sharing operator and O-RU resources are dynamically shared between sharing operators.
-
-Whilst there are a variety of RAN sharing deployment models, a key motivation of this use case is to enable O-RAN based architectures to be able to support Shared O-RU based RAN sharing. In the conventional radio node-based sharing, a “host” operator makes available a shared radio node as part of distributed antenna system (DAS) that can be partitioned between one or more mobile operators. The host operator then integrates with the RAN equipment of the one or more Mobile Operators (MNOs), where the interface between DAS radio node and RAN equipment can re-use an attenuated Uu interface. Translating this into the O-RAN architecture, the host operator is responsible for operating the Shared O-RU that can integrate with the O-DUs of one or more mobile operators. Hereafter such a host operator is referred to as a Shared Resource Operator – Host (SRO-H) and the mobile operators operating the O-DUs are referred to as Shared Resource Operator - Tenants (SRO-T). The SRO-H can operate its own O-DU and O-CU functionalities, in which case the O-RU is shared between the SRO-H and SRO-T(s). Alternatively, the host can operate the O-RU as a neutral-host, in which case the O-RU is shared between the SRO-Ts. Hereafter such a host operator is referred to as a Shared Resource Operator - Neutral Host (SRO-NH).
-
-When such RAN sharing is coupled with established open fronthaul specified shared cell functionality, where multiple O-RU nodes are used to support a common cell, then it is evident that there is an opportunity for the O-RAN ecosystem to be re-applied to address the distributed antenna system market; a market that is estimated to have a global revenue of over USD 19 Bn by 2025 according to Market Data Forecast ().
-
-### 4.20.3 Proposed solution
-
-#### 4.20.3.1 Static allocation of resources between O-DU nodes
-
-##### 4.20.3.1.1 Introduction
-
-The initial phase of the proposed solution is to enhance the current open fronthaul architecture to enable a common O-RU node to operate with multiple O-DU nodes with the limitation that resources are statically allocated to separate O-DU nodes.
-
-##### 4.20.3.1.2 Single operator use case
-
-The single operator use cases are shown in figure 4.20.3.1.2-1, for either hybrid or hierarchical open fronthaul deployments. Because resources are statically allocated, co-ordination of O-RU resources is performed by the operator’s SMO. In this figure, two set of O-CU and O-DU are described but single O-CU can also cover multiple O-DUs per one UE.
-
-
-
-Figure 4.20.3.1.2-1: Single operator solution for hybrid and hierarchical open fronthaul deployments. The diagram shows two side-by-side network architectures. Both start with an SMO at the top, which coordinates O-RU resources for O-DU#1 and O-DU#2 via O1 interfaces. Below the SMO, each architecture has an O-CU-UP and O-CU-CP connected to a Near-RT RIC via E2 interfaces. The Near-RT RIC is connected to the O-DUs via E2 interfaces. In the left architecture (Hybrid), the O-DUs are connected to the O-RU via Open FH M-Plane (hybrid-odu) and Open FH CUS-Plane. In the right architecture (Hierarchical), the O-DUs are connected to the O-RU via Open FH M-Plane (sudo) and Open FH CUS-Plane. Both architectures show Carriers connected to the O-RU.
-
-**Figure 4.20.3.1.2-1: Single operator solution for hybrid and hierarchical open fronthaul deployments**
-
-In the case of active/standby operation, the SMO is responsible for configuring identical carrier configurations on separate O-DU nodes. The data model of the O-RU is enhanced with capabilities to associate the fronthaul transport flows associated with an active O-DU node, which necessarily includes the O-DU node’s CU-plane transport endpoint, with the corresponding fronthaul transport flows associated with a standby O-DU node. The operation of the stand-by O-DU node is enhanced such that carrier configuration of the O-RU is omitted, which is instead performed only by the active O-DU node. The stand-by O-DU node subscribes to receive supervision notifications from the O-RU. The switchover from active to stand-by O-DU node can be initiated by the SMO, e.g., enabling operation of a planned procedure to de-commission the active O-DU node. Alternatively, the switchover from active to stand-by O-DU node can be initiated automatically whereby the standby O-DU node becomes aware that the active O-DU has become non-operational which triggers the switchover procedure.
-
-In the case of scale in/scale out operation, the SMO statically partitions O-RU resources between a set of candidate O-DU nodes. The SMO oversees the definition and reporting of long-term traffic metrics in a whole cluster of cells that can be served by the candidate O-DUs, e.g., using the Non-RT RIC. The SMO uses the O1 interface to either i) activate and configure or ii) de-activate and de-commission candidate O-DU nodes in response to varying traffic load.
-
-In the case of “access-centric configuration” to support combined LTE and NR deployments, the SMO statically partitions O-RU resources between LTE and NR carriers. The SMO uses the O1 interface to configure one or more O-DU nodes for each of the respective radio technologies, e.g., including associated DSS aspects such as MBSFN configuration, subframe masks and rate matching configurations.
-
-##### 4.20.3.1.3 Multi-operator use case
-
-The multi-operator use cases are shown in figure 4.20.3.1.3-1, where (a) shows the deployment with hierarchical open fronthaul, (b) shows the deployment with hybrid open fronthaul and (c) shows the deployment with neutral host. In all three cases an SRO-H enters into an agreement with one or more SRO-Ts to offer access to the resources of a Shared O-RU. The sharing agreement covers off those aspects of the O-RU’s resources which are available to the SRO-T and which can be used in the SRO-T’s configuration. In all cases, the SRO-H is responsible for configuring the common aspects of the Shared O-RU.
-
-
-
-The diagram illustrates three multi-operator solutions for open fronthaul deployments, labeled (a), (b), and (c). Each solution shows the interaction between multiple operators' SMOs (SRO-H, SRO-T, SRO-NH), O-CU-UP, O-CU-CP, O-DUs, and a shared O-RU with carriers.
-
-- (a) Hybrid O-DU:** Shows two operators. The first operator's SRO-H SMO connects to a Hybrid O-DU, which is connected to an O-RU. The second operator's SRO-T SMO connects to an SRO-T O-DU, which is also connected to the O-RU. Sharing agreements are shown between the SRO-H SMO and the SRO-T SMO.
-- (b) Hierarchical O-DU:** Shows two operators. The first operator's SRO-H SMO connects to a Hierarchical O-DU, which is connected to an O-RU. The second operator's SRO-T SMO connects to an SRO-T O-DU, which is also connected to the O-RU. Sharing agreements are shown between the SRO-H SMO and the SRO-T SMO.
-- (c) Multiple O-DUs:** Shows three operators. The first operator's SRO-NH SMO connects to an SRO-T#1 O-DU, which is connected to an O-RU. The second operator's SRO-T#1 SMO connects to an SRO-T#1 O-DU, which is also connected to the O-RU. The third operator's SRO-T#2 SMO connects to an SRO-T#2 O-DU, which is also connected to the O-RU. Sharing agreements are shown between the SRO-NH SMO and the SRO-T#1 SMO, and between the SRO-T#1 SMO and the SRO-T#2 SMO.
-
-Figure 4.20.3.1.3-1: Multi-operator solution for open fronthaul deployments. The diagram shows three scenarios: (a) Hybrid O-DU, (b) Hierarchical O-DU, and (c) Multiple O-DUs connected to a single O-RU. Each scenario illustrates the interaction between SMOs (SRO-H, SRO-T, SRO-NH), O-CU-UP, O-CU-CP, O-DUs, and the O-RU with carriers. Sharing agreements are shown between different operators' SMOs.
-
-Figure 4.20.3.1.3-1: Multi-operator solution for open fronthaul deployments
-
-The Shared O-RU is enhanced with additional role-based access control capabilities to restrict the ability of an SRO-T from accessing the configuration of the Shared O-RU associated with resources to which it has not been authorized, e.g., those resources that have been allocated to a second SRO-T. Furthermore, the Shared O-RU's enhanced role-based access control capabilities restrict the ability of an SRO-T from receiving performance management information to that which is associated with its authorized set of Shared O-RU resources. Additional capabilities are defined to support supervision of the communications link between the Shared O-RU and an SRO-T, with an alarm indication able to indicate to the SRO-H that the communications to the SRO-T have been interrupted. Unlike in conventional O-RU operation, the loss of supervision to an SRO-T O-DU does not result in the O-RU ceasing all radio transmissions and performing an autonomous reset. Instead, only those carriers associated with the SRO-T O-DU are disabled.
-
-The SRO-H is able to validate that the SRO configuration adheres to the specifics of the sharing agreement between the parties. The SMO of the SRO-H can configure to be notified of modifications to the O-RU's configuration datastore. These notifications can be used to confirm that the sharing agreement is being adhered to. Any remedial action required, e.g., if the SRO-T configuration is not in compliance with the sharing agreement, is handled between the SRO-H and the SRO-T.
-
-#### 4.20.3.2 Dynamic allocation of resources between O-DU nodes
-
-##### 4.20.3.2.1 Introduction
-
-This phase of the proposed solution is to enhance the current open fronthaul architecture to enable a common O-RU node to operate with multiple O-DU nodes with the limitation that resources are dynamically allocated to separate O-DU nodes.
-
-##### 4.20.3.2.2 Single operator use case
-
-The single operator use cases are shown in figure 4.20.3.2.2-1 (shows only hybrid model), for either hybrid or hierarchical open fronthaul deployments. Because resources are dynamically allocated, co-ordination of O-RU resources is performed by the Near RT-RIC or M-plane based on demand and performance for slices. To keep improving frequency efficiency with providing slices concurrently, radio resource allocation will be expected frame by frame or in seconds. A single O-CU will cover multiple O-DUs per UE.
-
-
-
-Figure 4.20.3.2.2-1: Single operator solution for hybrid open fronthaul deployments migrating to vO-DU. The diagram shows two states of an O-RAN architecture. On the left, an SMO (Co-ordination of O-RU for O-DU#1 and O-DU #2) is connected to an O-CU and a Near-RT RIC. The O-CU is connected to a Hybrid O-DU#1, which is connected to an O-RU (Carrier). The Near-RT RIC is connected to the O-CU and the Hybrid O-DU#1. The Hybrid O-DU#1 has an Open FH M-Plane (hybrid-odu) and an Open FH CUS-Plane. The O-RU has an Open FH M-Plane (sudo). On the right, the architecture has migrated to a vO-DU. The SMO is now connected to an O-CU and a Near-RT RIC. The O-CU is connected to a Hybrid O-DU#1, which is connected to an O-RU (Carrier). The Near-RT RIC is connected to the O-CU and the Hybrid O-DU#1. The Hybrid O-DU#1 has an Open FH M-Plane (hybrid-odu) and an Open FH CUS-Plane. The O-RU has an Open FH M-Plane (sudo). A second Hybrid O-DU#2 is shown, connected to the O-CU and the Near-RT RIC. The Hybrid O-DU#2 has an Open FH M-Plane (hybrid-odu) and an Open FH CUS-Plane. The O-RU has an Open FH M-Plane (sudo).
-
-Figure 4.20.3.2.2-1: Single operator solution for hybrid open fronthaul deployments migrating to vO-DU
-
-### 4.20.4 Benefits of O-RAN architecture
-
-The proposed single operator Shared O-RU architectures shown in figure 4.20.3.1.2-1 let operators use the open fronthaul to enable a common O-RU node to operate with a plurality of O-DU nodes. Such a capability can be used to deliver enhanced deployment scenarios where multiple O-DU nodes are used to increase the resilience or scalability of the O-RAN fronthaul architecture. The proposed access-centric approach allows operators to utilize different O-DU vendor's strengths for a particular radio technology, enabling a Shared O-RU node configured for DSS to operate with an LTE O-DU node from vendor#1 and an NR O-DU node from vendor#2.
-
-The proposed multi-operator Shared O-RU architectures shown in figure 4.20.3.1.3-1 let operators use the open fronthaul to enable a single O-RU node to be shared between multiple different operators. The architecture allows shared resource operators to configure Shared O-RU resources independently from configuration and operating strategies of the other shared resource operators while preventing one shared resource operator from gaining insight into the configuration and operational status of Shared O-RU resources allocated to a second shared resource operator. Moreover, the architecture enables the SRO-H to operate as an independent neutral host provider.
-
-NOTE:
-
-Use cases where resources are dynamically allocated to separate O-DU nodes for multi-operator use case are not defined in the present document.
-
-## 4.21 Network energy saving
-
-### 4.21.1 Background information
-
-Energy Consumption (EC) of RAN is an important topic for network operators, especially for 5G network. RAN Energy Saving (ES) depends on rigorous planning and configuration. Due to the varying nature of traffic load and to user mobility, the optimization of EC of the RAN is complex and can be applied to different network layers and in different time scales. There is a risk that RAN equipment consumes much energy while serving low traffic, or even no traffic at all.
-
-Different ES features are investigated in industry, some of which are deployed in operational networks. Examples are deep sleep mode (e.g., shut down of a base station of a given technology), carrier shut down, and RF channels' switch off/on). More recently, short time scales ES mechanisms have been proposed, at symbol-, subframe- and frame-levels, known as Advanced Sleep Modes (ASM).
-
-O-RU is responsible for a major part of the mobile network EC. EC of VNFs have not yet been standardized in Release 17 of 3GPP and can be only estimated, e.g., based on mean vCPU usage of the underlying VMs. EC measurements will
-
-be further addressed in release 18. In O-RAN O-Cloud, the only feature with relation to ES is scale in/out that is mentioned in the use case document [i.22]. Sub-use cases involving scale-in/scale-out processes, workload placement or HW processors' sleep modes are not defined in the present document.
-
-### 4.21.2 Motivation
-
-ES for legacy and 5G networks can be carried out using manual configuration or SON functions. 3GPP defines both centralized and distributed ES features [i.13], which are mainly targeting intra- or inter-RAT cell on/off switching. The motivation of the ES use case is to leverage on O-RAN AI/ML services and open interfaces in order to introduce optimized ES and EE solutions involving switching off/on of different network components at different time scale. Will be considered off/on switching solutions supported by 3GPP configurations or supported by propriety implementations that require additional standardization.
-
-### 4.21.3 Proposed solution
-
-The ES use cases is divided into three sub-use cases, according to the time scale of the control and the controlled system involved:
-
-1. Carrier and cell switch off/on ES. Time scale: non-real-time for both control and controlled system. The feature aims at reducing O-CU/DU/RU power consumption by switching off/on one or more carriers or a cell of a given technology. AI/ML assisted solutions in the Non-RT RIC can be used to control the traffic load of the carriers and the cell, and to automatically decide when to switch off/on one or more carriers or a cell using O1 and/or open fronthaul M-plane parameter configurations. Off/on switching is accompanied with adequate traffic steering, guided by policies, to ensure service continuity and quality of service. Carrier switch off/on has two modes of operation: (i) hibernate mode in which the radio's power amplifiers remain with minimum current draw, and (ii) complete switch off.
-2. RF channel switch off/on ES. Time scale: non- or near-real-time are possible for both control and controlled system. This feature aims at reducing power consumption of O-RU with massive MIMO deployment by switching off/on certain RF channels [i.8]. Using AI/ML assisted solutions, rApp or xApp will trigger switching off/on certain RF channels, based on traffic information such as load, user location and mobility. As example, one can switch off 32 out of 64 RF channels in digital beamforming architecture or reduce the number of layers and/or number of multi-user scheduled UEs in a hybrid beamforming architecture. The O-RU reconfiguration can be performed using the open fronthaul M-plane from E2 node or SMO.
-3. Advanced sleep mode ES. Time scale for control: near-real-time. Time scale for the controlled system: real-time and near-real-time. This feature is expected to reduce power consumption by partially switching off O-RU components. The impact of ASMs on O-DU and O-CU EC is not defined in the present document. Using multi-dimensional data, e.g., traffic load, user service type, energy efficiency measurements, etc., the Near-RT RIC can configure cell parameters, such as the SSB periodicity needed for the operation of ASMs.
-4. External power source coordination-based energy saving. Time scale for control: non-real-time is possible for both control and controlled system. The feature aims to enable the SMO framework to utilize the energy source and supply information to switch the energy source and use them as inputs for preparing energy saving policy or configuration changes in a deployment where the NF node (O-RU, O-DU, and O-CU) is powered by renewable energy sources. Using AI/ML assisted solutions, rApp will prepare the energy saving policy or an intent to trigger the activation of an appropriate energy saving method in NF node depending on the energy source and supply information.
-5. PA power optimization ES. Time scale for control: near-real-time and non-real-time. Time scale for the controlled system: real-time, near-real-time, and non-real-time. This feature is expected to reduce O-RU power consumption by optimizing its PA parameters based on the maximum output power configured by the O-DU. The impact of PA power optimization on O-DU and O-RU EC is not defined in the present document. Using multi-dimensional data, e.g., traffic load, user service type, energy efficiency measurements, etc., the Non-RT RIC and Near-RT RIC can configure cell parameters, such as the O-RU maximum output power per carrier, cell coverage and capacity.
-
-#### 4.21.3.1 ES sub-use case 1: Carrier and cell switch off/on
-
-The carrier and cell switch off/on is a non-real-time sub-use case where the Non-RT RIC is in charge of configuring E2 nodes. This ES feature can be invoked in response to changes in traffic load or change in the cell/carrier off/on switching policy. The Non-RT RIC will use the O1 interface to configure the parameters of the O-CU/O-DU and will use the open fronthaul M-plane from the SMO to configure O-RU switch off/on, after triggering handovers to move users to other cells/carriers. The O1 interface is also used to collect traffic information per cell and per carrier to the SMO as input to the Non-RT RIC. rApps hosting AI/ML assisted solutions can be used to achieve optimized ES configurations, such as the switching time that can provide optimal desired tradeoff between ES and users' QoS.
-
-The concept of carrier and cell switch off/on ES sub-use case is given in figure 4.21.3.1-1.
-
-
-
-The diagram illustrates the architecture for the ES sub-use case 1: Carrier and cell switch off/on. At the top is the **Service, Management & Orchestration (SMO)** block, which contains an **ML model** and the **Non-Real Time RIC**. Below the SMO is the **Near-RT RIC**, connected via the **A1** interface. Below the Near-RT RIC is the **E2 Node**, connected via the **E2** interface. At the bottom is the **O-RU**, connected to the E2 Node via the **Open fronthaul M-plane**. The SMO is also connected to the E2 Node via the **O1** interface. The O1 interface is used for traffic steering configuration, carrier and cell switch off/on parameter configuration, and traffic information from the E2 Node. The Open fronthaul M-plane is used for carrier and cell switch off/on parameter configuration. The Non-RT RIC is responsible for collecting cell traffic information, steering traffic before or after cell/carrier switching off or on, and configuring carrier and cell switch off/on and traffic steering. The O1 interface is also used to collect traffic information per cell and per carrier to the SMO as input to the Non-RT RIC.
-
-Diagram of Carrier and cell switch off/on ES sub-use case architecture showing Service, Management & Orchestration (SMO) with Non-Real Time RIC (containing ML model), Near-RT RIC, E2 Node, and O-RU. It details the O1 and Open fronthaul M-plane interfaces and their respective functions for traffic steering and carrier/cell switching configuration.
-
-Figure 4.21.3.1-1: Carrier and cell switch off/on ES sub-use case
-
-#### 4.21.3.2 EE/ES sub-use case 2: RF channel switch off/on
-
-The first implementation of this sub-use case is non-real-time. This solution is expected to reduce power consumption by switching off certain RF channels of O-RU with massive MIMO deployment. Based on data collected from E2 nodes and O-RU, the solution will automatically switch off/on certain RF channels and configure the massive MIMO system to minimize the impact on users' QoS.
-
-The concept of RF channel switch off/on ES sub-use case: Non-real-time implementation is given in figure 4.21.3.2-1.
-
-
-
-Figure 4.21.3.2-1: RF channel switch off/on ES sub-use case: Non-real time implementation. This diagram shows a vertical stack of network components: Service, Management & Orchestration (SMO) at the top, followed by a Non-RT RIC (containing an ML model), a Near-RT RIC, an E2 Node, and an O-RU at the bottom. The Non-RT RIC is connected to the SMO and the Near-RT RIC via the A1 interface. The Near-RT RIC is connected to the E2 Node via the E2 interface. The E2 Node is connected to the O-RU via the Open fronthaul M-plane. The O-RU is also connected to the Non-RT RIC via the Open fronthaul M-plane. Callouts provide details: 'Non-RT RIC' collects cell traffic load, users' QoS, UE speed and UE location data, and configures the massive-MIMO system. 'O1' collects traffic load, users' QoS, UE speed and UE location data from the E2 Node and configures users' QoS. 'Open FH M-plane' on the right is used for massive MIMO system reconfiguration.
-
-**Figure 4.21.3.2-1: RF channel switch off/on ES sub-use case: Non-real time implementation**
-
-The second implementation of this sub-use case is near-real-time. As in the non-real-time implementation, this solution is expected to reduce EC by switching off certain RF channels of O-RU with massive MIMO.
-
-The AI/ML training host in the SMO/Non-RT RIC will train AI/ML model based on data collected from applications and/or O1 interface such as cell traffic, users' QoS, users' speed or geolocation data. The Near-RT RIC uses the trained model to select the off/on switching time and to infer the configuration of the massive MIMO system based on information from E2 and open fronthaul M-plane interfaces.
-
-The concept of RF channel switch off/on ES sub-use case: Near-real-time implementation is given in figure 4.21.3.2-2.
-
-
-
-Figure 4.21.3.2-2: RF channel switch off/on ES sub-use case: Near-real-time implementation. This diagram shows a similar vertical stack: Service, Management & Orchestration Framework (SMO) at the top, a Non-RT RIC, a Near-RT RIC (containing an ML model), an E2 Node, and an O-RU at the bottom. The Non-RT RIC is connected to the SMO and the Near-RT RIC via the A1 interface. The Near-RT RIC is connected to the E2 Node via the E2 interface. The E2 Node is connected to the O-RU via the Open fronthaul M-plane. Callouts provide details: 'Non-RT RIC' trains the AI/ML model with data information from the O1 interface. 'A1' is used for ML model deployment. 'O1' collects traffic load, users' QoS, UE speed and UE location data from the E2 node. 'Near-RT RIC' collects traffic load, users' QoS, UE speed, UE location data and optimizes the RF channel configuration. 'E2' collects traffic load, users' QoS, UE speed and UE location data, and sends the massive MIMO configuration to the E2 node. 'E2 node' performs massive MIMO system reconfiguration via the open FH M-plane.
-
-**Figure 4.21.3.2-2: RF channel switch off/on ES sub-use case: Near-real-time implementation**
-
-#### 4.21.3.3 ES sub-use case 3: Advanced sleep modes
-
-ASMs are used to reduce EC by partially and automatically switching off O-RU components, at a duration of a symbol (ASM1), a slot (ASM2) and a frame (ASM3). The deeper (longer) is the sleep mode level, the longer is its wake-up time. The impact of ASMs on O-DU and O-CU is not defined in the present document.
-
-The aim of this sub-use case is to maximize the ASMs duration (and the corresponding ES) in which O-RU components are switched-off, taking into account user QoS constraints in terms of latency. To this end, ASM activation policy can be set (e.g., the order and number of ASMs in each level), and system configurations can be applied (such as setting the SSB periodicity; compress data transmissions in particular slots and empty the remaining ones that are put “into sleep state”; reduce the synchronization signals’ transmissions and the opportunities for random access and paging).
-
-The ASM activation policy and configurations can be derived using AI/ML models, aiming at achieving optimal tradeoffs between ES and QoS. The AI/ML training host in the SMO/Non-RT RIC will train an AI/ML model based on measurements such as traffic load and latency, on service information and will derive optimal system configuration (e.g., SSB periodicity, ASM sleep level and sleep duration). The Near-RT RIC will request the AI/ML model from A1 interface that, once deployed and activated, will optimize ES by setting ASM policies and system configurations via E2 and open fronthaul M-plane interfaces.
-
-The concept of advance sleep mode ES sub-use case is given in figure 4.21.3.3-1.
-
-
-
-The diagram illustrates the architecture and data flow for the advance sleep mode ES sub-use case. At the top is the **Service, Management & Orchestration** block, which contains the **Non-RT RIC**. Below it is the **ML model** block, which contains the **Near-RT RIC**. Below that is the **E2 Node**, and at the bottom is the **O-RU**. The **Non-RT RIC** and **ML model** are connected via an **A1** interface. The **Non-RT RIC** and **Near-RT RIC** are connected via an **O1** interface. The **Near-RT RIC** and **E2 Node** are connected via an **E2** interface. The **E2 Node** and **O-RU** are connected via an **Open fronthaul M-plane** interface. Various callouts provide details:
-
-
-- Non-RT RIC**: Trains AI/ML model with data from O1.
-- A1**: ML model deployment.
-- Near-RT RIC**: Collects traffic load, users' QoS, and system configuration information; infers ASM activation policy and system configurations.
-- O1**: Collects traffic load, users' QoS, and system configuration information from E2 node.
-- E2**: ASM activation policy and system configurations; Traffic information including traffic load and users' QoS.
-- E2 node**: configures ASM and system parameters; Sends ASM and system parameters to O-RU via open FH M-plane.
-
-Diagram of Advance sleep mode ES sub-use case showing interactions between Service, Management & Orchestration, Non-RT RIC, ML model, Near-RT RIC, E2 Node, and O-RU.
-
-Figure 4.21.3.3-1: Advance sleep mode ES sub-use case
-
-#### 4.21.3.4 ES sub-use case 4: External power source coordination-based energy saving
-
-External power source coordination-based energy saving is for SMO framework to get the energy source and supply information (either by operator input or available to SMO framework from external producers or exposed via O-RU, where the energy supplier control panel provides the energy source and supply information to the O-RU through a vendor specific implementation). Then the SMO framework may utilize its appropriate SMOS(s) to use those data to optionally switch the energy source and to configure appropriate energy saving method in O-RU based on the energy source and supply information. For example, when O-RU power source switched from grid supply to either battery or solar power (or any other renewable energy source) with limited energy supply. The SMO framework may utilize an appropriate SMOS(s) to analyse energy sources and their supply information like capacity and then activate the appropriate energy saving in O-RU to prolong its services. The concept of external power coordination-based energy saving sub-use case is given in figure 4.21.3.4-1.
-
-
-
-**Service, Management & Orchestration**
-
-**RAN NF OAM SMOS**
-
-**AI/ML Model Non-Real Time RIC**
-
-**O1**
-
-**O-DU Node**
-
-**Open FH M-Plane**
-
-**O-RU Node**
-
-**SMO**
-
-- Operator configures energy source and supply information to appropriate SMOS of SMO framework or RAN NF SMOS collects the energy source and supply information from energy supplier control panel.
-- Generate optimization Controls or policy for O-RU energy saving based on energy source and supply information.
-
-**NF (O-DU) Node**
-
-- Execute policies and apply the configuration changes from SMO framework (RAN NF OAM SMOS) via O1 interface.
-- Configure appropriate energy saving features in O-RU and forward the energy source switching command (if it receives from SMO) to energy supplier control panel through O-RU.
-- Provide traffic and O&M data and forward the energy source and supply information (if it receives through O-RU from energy supplier control panel) to SMO framework.
-
-**Non-RT RIC**
-
-- Consume NF data
-- Train & Deploy AI/ML Model to generate policies based on O1 data
-- Generate policies for NF Nodes based on priority, load & energy consumption.
-
-**O-RU Node**
-
-- Apply the energy saving methods configured by O-DU based on SMO provided policy or configuration changes.
-- If O-RU has a capability to receive the energy supply source and supply information from the energy supplier control panel, it will forward to SMO through O-DU.
-- Forward the energy source switching command that it receives from the SMO through the O-DU, to the energy supplier control panel.
-
-Diagram of External power source coordination-based energy saving - Non-RT RIC and O1 based solution. The diagram shows a hierarchy: Service, Management & Orchestration (top) containing RAN NF OAM SMOS and AI/ML Model Non-Real Time RIC; O1 interface; O-DU Node; Open FH M-Plane; O-RU Node. Callout boxes detail the functions of SMO, NF (O-DU) Node, Non-RT RIC, and O-RU Node.
-
-**Figure 4.21.3.4-1: External power source coordination-based energy saving - Non-RT RIC and O1 based solution**
-
-#### 4.21.3.5 ES sub-use case 5: PA power optimization-based energy saving
-
-Power amplifier optimization (maximum output power control) based energy saving is for SMO framework to collect the network data and KPIs from various network functions, such as O-DU and O-RU. By leveraging this information, the SMO framework may use an appropriate SMOS(s) to dynamically prepare the policies or configuration changes and provide them to the O-DU. Once the conditions mentioned in that policy satisfied or based on configuration changes, the O-DU configures the maximum output power in O-RU, where this power value may be determined by O-DU according to the traffic scheduling requirements. The O-RU optimizes the power amplifier operating region according to the maximum output power configured by O-DU. This could result in O-RU energy saving as the power amplifier is a major power consuming component of O-RU.
-
-The concept of PA power optimization-based energy saving sub-use case driven by Non-RT RIC is given in figure 4.21.3.5-1.
-
-
-
-**Service, Management & Orchestration**
-
-**RAN NF OAM SMOS**
-
-**AI/ML Model Non-Real Time RIC**
-
-**O1**
-
-**O-DU Node**
-
-**Open FH M-Plane**
-
-**O-RU Node**
-
-**SMO Framework**
-Generate optimization Controls or policy for O-RU energy saving by optimizing the PA according to the traffic requirements.
-
-**NF Node (O-DU)**
-1) Execute policies and/or apply the configuration changes from RAN NF OAM SMOS via O1 interface.
-2) Execute Policies/Controls to mobilize & prioritize traffic.
-3) Provide Traffic data for Non-RT RIC/Near RT RIC.
-4) Limit/control the output power of O-RU based on traffic KPIs and energy consumption.
-
-**Non-RT RIC**
-1) Consume NF data
-2) Train & Deploy AI/ML Model to generate policies based on O1 data
-3) Generate policies for NF Nodes based on priority, load & energy consumption.
-
-**O-RU Node**
-1) Apply the maximum output power configured by O-DU based on SMO provided policy or configuration changes.
-2) Adjust the PA operating region according to the maximum output power configured by the O-DU.
-
-Architecture diagram for PA power optimization-based energy saving using Non-RT RIC and O1 interface. The diagram shows Service, Management & Orchestration at the top containing RAN NF OAM SMOS and AI/ML Model Non-Real Time RIC. Below are O-DU Node and O-RU Node connected via Open FH M-Plane. Various callouts explain the roles of SMO Framework, NF Node (O-DU), and Non-RT RIC.
-
-Figure 4.21.3.5-1: PA power optimization-based energy saving - Non-RT RIC and O1 based solution
-
-The concept of PA power optimization-based energy saving sub-use case driven by Near-RT RIC is given in figure 4.21.3.5-2.
-
-
-
-**Service, Management & Orchestration**
-
-**AI/ML Model Non-Real Time RIC**
-
-**RAN NF OAM SMOS**
-
-**A1**
-
-**AI/ML Model Near-RT RIC**
-
-**Open FH M-Plane**
-
-**E2**
-
-**O-DU (E2) Node**
-
-**O-RU Node**
-
-**Non-RT RIC**
-1) Consume NF data
-2) Train & Deploy AI/ML Model to generate A1 policies based on O1 data
-3) Generate A1 policies for Near-RT RIC based on priority, load, and energy consumption.
-
-**SMO Framework**
-Generate optimization Controls or policy for O-RU energy saving by optimizing the PA according to the traffic requirements.
-
-**NF (E2) Node (O-DU)**
-1) Execute policies or apply the configuration changes from near-RT RIC via E2 interface.
-2) Execute Policies/Controls to mobilize & prioritize traffic.
-3) Provide Traffic data for Non-RT RIC/Near RT RIC
-4) Limit/control the output power of O-RU based on traffic KPIs and energy consumption.
-
-**Near-RT RIC**
-1) Consume NF data.
-2) Train & Deploy AI/ML Model to generate E2 policies and configuration changes based on E2 data.
-3) Provide E2 policies or configuration changes for O-DU based on priority, traffic load & energy consumption.
-
-**O-RU Node**
-1) Apply the maximum output power configured by O-DU based on SMO provided policy or configuration changes.
-2) Adjust the PA operating region according to the maximum output power configured by the O-DU.
-
-Architecture diagram for PA power optimization-based energy saving using Near-RT RIC and E2 interface. The diagram shows Service, Management & Orchestration at the top containing AI/ML Model Non-Real Time RIC and RAN NF OAM SMOS. Below is an AI/ML Model Near-RT RIC connected via A1 interface. Further down are O-DU (E2) Node and O-RU Node connected via Open FH M-Plane and E2 interface. Various callouts explain the roles of Non-RT RIC, Near-RT RIC, NF (E2) Node (O-DU), and O-RU Node.
-
-Figure 4.21.3.5-2: PA power optimization-based energy saving - Near-RT RIC and E2 based solution
-
-### 4.21.4 Benefits of O-RAN architecture
-
-The proposed solutions will support the AI/ML assisted solutions at both Non-RT RIC and Near-RT RIC as inference hosts, to efficiently optimize ES and EE at different time scales. The ES solutions will leverage on O-RAN open interfaces to support the use case in a multi-vendor disaggregated RAN.
-
-## 4.22 MU-MIMO optimization
-
-### 4.22.1 Background information
-
-MU-MIMO is one of the key technologies available for increasing UE and cell capacities using existing time/frequency resources. The use of multiple antennas enables the pointing of beams to multiple UEs with each beam spatially filtering the interference from the other beams. This has the potential to provide higher total cell capacity when there are N eNB/gNB antennas.
-
-In a commercial deployment, some subscribers can be stationary, some can be pedestrian moving slowly, and some can be moving at high speed. Traditional MU-MIMO solutions are very sensitive to subscriber mobility and as a result the capacity gains achieved with multiple antennas is limited.
-
-New beamforming solutions are emerging that support MU-MIMO with less time sensitivity allowing them to be implemented in the Near-RT RIC. These solutions are applicable to both downlink and uplink data channels and both TDD and FDD, and can provide high user and cell performance for subscribers moving wide range of speeds.
-
-### 4.22.2 Motivation
-
-The MU-MIMO optimization use case aims at enabling new spatial multiplexing and precoding solutions that have the potential for increasing user and overall cell capacity in a massive MIMO deployment area by selecting appropriate users over time and frequency resources, and for each selection of users recommending the applicable precoding coefficients and Modulation and Coding Schemes (MCS) for most efficient resource usage.
-
-### 4.22.3 Proposed solution
-
-The use case proposes to have the MU-MIMO optimization function as an application in the Near-RT RIC. The application collects information from the E2 nodes and sends control messages to the E2 nodes using the E2 interface.
-
-The main functionalities of the Near-RT RIC application include collecting UE state from the O-CU, configuring the O-CU/O-DU to report RRC parameters and UL/DL traffic and channel information, using the reported channel and traffic information to select the best UEs to be spatially multiplexed, calculating for each selection the applicable frequency/time resources, the MCS, and the beamforming coefficients for best MU-MIMO performance, and sending the recommended UEs selections, applicable resources, MCS, and beamforming coefficients to the O-DU over E2 interface.
-
-The E2 nodes (O-CU/O-DU) provide RRC parameters and UL/DL traffic and channel information to the Near-RT RIC and the O-DU can use the information received from the Near-RT RIC to schedule MU-MIMO transmissions, while still handling time critical events separately.
-
-### 4.22.4 Benefits of O-RAN architecture
-
-Using a RIC-based implementation of MU-MIMO can benefit from using the near-real-time data from the E2 nodes to influence how the 4G/5G MAC scheduler assigns the near-term resources and how the PHY forms the MU-MIMO beams for achieving improved per subscriber and overall cell throughput performance in certain deployment scenarios. Using the RIC-based implementation to support this use case, where the Near-RT RIC enables near-real-time control and
-
-optimization of services and resources in multiple O-CUs/O-DUs, also opens the door for future expansion of the MU-MIMO to supporting CoMP covering both ICIC and joint multi sites MU-MIMO.
-
-## 4.23 Sharing Non-RT RIC data with the core
-
-### 4.23.1 Background information
-
-As networks have become more and more complicated, the need has arisen for complex analytics, being available in close to real time, so as to facilitate automated network “control loops” through entities such as the Non-RT RIC and the Near-RT RIC. The need for such analytics is not, however, restricted to the RAN but also exists in the 5G core. Thus, 3GPP has defined the NWDAF function in the 3GPP 5GC architecture [i.23].
-
-The NWDAF uses standard interfaces to deliver analytics to other 5G core network functions, which use those analytics to optimize their network processing. This is a similar pattern that we see with the Non-RT RIC, which uses a standard interface (i.e., A1-EI) to deliver analytics to 5G RAN network functions (i.e., Near-RT RIC instances), which use those analytics to optimize network processing.
-
-3GPP defines a plethora of optional functionality that an NWDAF can provide, but fundamental to the NWDAF is a functionality 3GPP defines as the Analytics Logical Function (AnLF). AnLF is the basic ability, perhaps using AIML, to produce analytics information content useful to 5GC NFs, which includes determining what source data content is necessary to do so. It is this AnLF functionality that the NWDAF function holds in common with the Non-RT RIC.
-
-So that any 5G core NF can semantically interpret the analytic content produced by any NWDAF, 3GPP has defined the specific “analytics Ids” associated with each NWDAF-producible analytic type, as well as the data structures associated with each analytic Id. It is worth noting that O-RAN has resisted similarly defining the data structures into which all rApp analytics should be carried so as to allow for innovation.
-
-rApps can produce analytics for multiple data consumers, such as other rApps, Near-RT RIC/xApps, general external entities (e.g., an Application Function, AF). In such a multi-consumer environment, it is a good architectural practice to avoid coupling of the data producer with the data consumer, in fact even hiding from the producer the identity of its data consumers or even whether the data consumers are single or multiple. This is, in fact, how the R1 DME is defined. In keeping with this principle, rApps will likely structure the information content of instance data they publish over R1 in a manner that is “generally useful” and not tailored to any particular data consumer. Some data consumers will be able to accept these “generally useful” data structures as is. Such might be the case, for example, for an external Application Function (AF). However, as described above, this is not the case with the 5G core NFs.
-
-One common pattern that will be used in various solution proposals builds on an internal functionality of the Non-RT RIC, background on which will be described here. As per [i.29], an rApp data producer should “one-time” register its output via DME services. If that rApp also intends to make its data also available via A1-EI, that rApp should also “one-time” register that same analytic output as an A1-EI type ([i.29], clause 5.3.3.2). Because A1-EI defines some standard data structures, presumably this A1-EI registration would also include the information necessary for the A1-related function to determine how to map any “generally useful” information content into these A1-EI data structures.
-
-3GPP has also defined that the 5G core NFs would use the NRF discover which specific analytics types (analytics Ids) are available and the service endpoint through which to obtain instances of that analytic. In addition, 3GPP has defined an optional capability through which the 5G core NF can leverage the UDM to discover available UE-level analytics and the service endpoint through which to obtain instances of such analytics for a given UE.
-
-### 4.23.2 Motivation
-
-There exist use cases such that the Non-RT RIC will produce, as a by-product of its normal function, analytics that would be useful to the core. For these purposes an analytic would be considered to be of 'useful interest' to a 5G core NF if that analytic corresponds in its semantic content to an 'output analytic' described in 3GPP TS 23.288 [i.24].
-
-For example, it would be within the scope of the Non-RT RIC to produce analytics related to UE mobility and QoS sustainability (e.g., traffic steering and congestion prediction and management). The semantic content of these could reasonably correspond to that described in the "output analytic" structures of the UE mobility and QoS sustainability analytics types appropriate to an NWDAF (see [i.23], clause 4.2.1.1). The same could be said of other NWDAF analytics types as well (e.g., slice load level, network performance, etc.)
-
-Given that some Non-RT RIC generated analytics would be directly useful to 5GC network functions, rather than implementing such an analytic twice, assuming that such an analytic is implemented via an rApp in the Non-RT RIC, there should be a mechanism whereby such an analytic can be shared with the core.
-
-### 4.23.3 Proposed solution
-
-Several possible solutions can be envisioned, which are treated below. A "fundamental challenge" that each solution should address is where the mapping takes place of the analytic information content from the "generally useful" structure that the rApp publishes across R1 for multiple consumers to the very specific data structures required by 5G core. The various options explored differ not only on the answer to this fundamental challenge, but also on whether the AnLF functionality is replicated in the functional architecture (i.e., in both the Non-RT RIC function and the NWDAF function) or shared, in the mechanism for whether and how to update the NRF/UDM, etc.
-
-We will explore two options whereby the SMO/Non-RT RIC can perform the role of a 5GC NWDAF, without a separate intervening NWDAF function, and then we will explore two options whereby the SMO/Non-RT RIC interact with a separate intervening NWDAF function.
-
-#### 4.23.3.1 SMO/Non-RT RIC direct to 5GC consumer with façade of an NWDAF
-
-This option 1 approach follows the pattern defined in [i.24], clauses 6.1.1 and 6.1.2. In this approach, the SMO/Non-RT RIC exposes the analytic directly to the consuming 5GC NF, performing the role of and presenting the façade of an NWDAF relative to that network function. Thus, in this option the AnLF functionality is not duplicated but exists only in the Non-RT RIC.
-
-Regarding the "fundamental challenge", in this option 1 the SMO/Non-RT RIC is responsible for mapping the analytic information content from the "generally useful" data structures published across R1 into the specific data structures expected by [i.24]. The mechanism for how to do this mapping extends the established pattern defined in [i.29] for rApp registration of A1-EI types. Specifically, option 1 would require an rApp that intends to make its data also available to 5G core NFs to also "one-time" register its R1 data type as a [i.24] analytic Id. This subsequent registration would also include the information necessary to map the "generally useful" information content into the data structures expected by [i.24]. The entity that would perform this mapping during subsequent runtime analytics exposure process will be described generically in this document as the "NWDAF façade" of the SMO/Non-RT RIC.
-
-In this option the 5GC NF discovers the correct "NWDAF" instance of interest through the UDM (for UE-related analytics) and the NRF (for non-UE related analytics). Accordingly, the SMO/Non-RT RIC, in the role of an NWDAF:
-
-1. Should register with the NRF for the capabilities that it supports (see [i.26], clause 5.2.7.1 and [i.25], clause 6.1.6.2.45).
-2. Can optionally register with the UDM for the UEs that it is serving or collecting data for, and for the related analytics ID(s) ([i.24], clause 6.1C.2).
-
-##### Observations:
-
-1. The process through which a new analytics type would be introduced would likely entail:
-
-- a. One or more rApp being loaded onto the Non-RT RIC capable of generating the desired analytic content in the "generally useful" structures, communicating to the NWDAF façade how to subsequently render that content into the NWDAF structures (see [i.24], clauses 6.6 and following).
- - b. The NWDAF façade of the SMO/Non-RT RIC registering that new analytics Id with the NRF and optionally UDM (per UE) as being available for consumption.
- - c. A new feature being loaded on a 5GC NF type capable of utilizing a particular NWDAF analytics Id, and which uses the NRF and optionally UDM (per UE) to determine that the SMO/Non-RT RIC is the entity from which to consume that specific analytics Id (perhaps with further discrimination based on TAC or NF mapping; [i.11], clause 6.3.19).
-2. The Non-RT RIC is within the SMO, where "M" is "management". If the SMO/Non-RT RIC presents itself to the 5GC NFs as an NWDAF, it is taking the role of a network function. The implications of this will be explored in the Detailed Specification.
-3. Similar to option 2, a DCCF/MFAF could be among the analytics consumer "5GC NFs". Because of that, the real differentiator between option 1 and option 2 is in which entity, if any, registers new analytics Ids with the NRF and optionally UDM.
-4. If there is a desire for 5GC NFs to also be able to access historical SMO/Non-RT RIC analytics, then the NWDAF façade would also need to support the optional Nnwdaf\_DataManagement Subscribe/Notify services.
-5. The NWDAF specification (see [i.24]) lists many other functionalities that an NWDAF can optionally support, such as supporting an external ADRF, providing training services to other 5GC NFs, aggregation and transfer of analytics, etc. Thus, other optional interfaces of the NWDAF (e.g., Nnwdaf\_DataManagement, Nnwdaf\_ModelProvision and Nnwdaf\_ModelInfo) are not considered. Because the SMO/Non-RT RIC does not support such functionality at this time nor are they critical to the topic of sharing data between RAN and core, this assumes that the NWDAF façade to the 5GC would be that of an NWDAF instance that does not support this optional functionality.
-
-##### Benefits of this approach:
-
-1. No duplication of AnLF functionality between the SMO/Non-RT RIC and a separate NWDAF, resulting in less cost and management complexity for a carrier/operator.
-2. No changes to the 3GPP defined interfaces, and no new interfaces need to be defined.
-3. This option addresses the "fundamental challenge" by following an established pattern used for delivery of rApp analytics to the Near-RT RIC via A1-EI.
-4. No configuration changes needed (outside of SMO/Non-RT RIC) with each new analytics type being exposed to the 5GC NFs. Rather, the 5GC knows that the source of that analytic type is the SMO/Non-RT RIC through dynamic NRF updates.
-
-##### Negatives of this approach:
-
-While it is not truly a negative, it is worth pointing out that this option does require support for new interfaces that are unlike any functionality that is currently associated with the SMO/Non-RT RIC, specifically the interfaces for SMO/Non-RT RIC to interact with the 5GC NRF and UDM to register its analytics types. However, such functionality can be generically useful for support of other external data consumers.
-
-The approach taken by option 1 is shown in figure 4.23.3.1-1 below:
-
-
-
-```
-
- graph TD
- SMO[SMO/Non-RT RIC] -- "Nudm_UECM_Registration" --> UDM[UDM]
- SMO -- "Nnrf_NFManagement" --> NRF[NRF]
- UDM -- "Register NWDAF" --> UDM
- NRF -- "Register NWDAF" --> NRF
- UDM -- "Discover NWDAF" --> AnyNF[Any 5GC NF]
- NRF -- "Discover NWDAF" --> AnyNF
- AnyNF -- "Nnrf_NFDiscovery" --> SMO
- SMO -- "Request" --> NWDAF[NWDAF]
- NWDAF -- "Deliver" --> AnyNF
- SMO -- "A1-EI" --> NearRT[Near-RT RIC]
- AnyNF -- "Nnwdaf_AnalyticsSubscription (Subscribe)" --> NWDAF
- AnyNF -- "Nnwdaf_AnalyticsInfo (Request)" --> NWDAF
- NWDAF -- "Nnwdaf_AnalyticsSubscription (Notify)" --> AnyNF
- NWDAF -- "Nnwdaf_AnalyticsInfo (Response)" --> AnyNF
-
-```
-
-Diagram showing the interaction between SMO/Non-RT RIC, UDM, NRF, and Any 5GC NF via an NWDAF façade. The SMO/Non-RT RIC registers with UDM and NRF, discovers NWDAF, and sends requests to Any 5GC NF. The NWDAF façade handles these requests and delivers responses. The SMO/Non-RT RIC also connects to the Near-RT RIC via an A1-EI interface.
-
-**Figure 4.23.3.1-1: SMO/Non-RT RIC direct to 5GC consumer with façade of an NWDAF**
-
-#### 4.23.3.2 SMO/Non-RT RIC to DCCF/MFAF with façade of an NWDAF
-
-This option 2 approach follows the pattern defined in [i.24], clause 6.1.4.2. In this approach, the SMO/Non-RT RIC shares its analytics with a DCCF/MFAF, which in turn makes those analytics available to requesting 5GC NFs. Thus, in this option the AnLF functionality is not duplicated but exists only in the Non-RT RIC.
-
-Regarding the "fundamental challenge", this option 2 approach also gives the SMO/Non-RT RIC responsibility for mapping the analytic information content from the "generally useful" data structures published across R1 into the specific data structures expected by [i.24]. The mechanism for how to do this is that described in option 1, with the separate rApp data registration event for 5G core NF data sharing.
-
-Because in this option the SMO/Non-RT RIC performs the AnLF and data mapping function, the SMO/Non-RT RIC will present the façade of an NWDAF relative to the DCCF/MFAF, leveraging the [i.24] NWDAF services for data subscription and delivery. The DCCF/MFAF is responsible for receiving analytics requests from 5GC NFs, forwarding the corresponding request to the NWDAF façade of the SMO/Non-RT RIC, receiving from the SMO/Non-RT RIC the associated analytics information, and returning the same to the requesting 5GC NFs.
-
-On the surface this option 2 can appear similar, from an SMO/Non-RT RIC perspective, to option 1 in that, in both cases, the SMO/Non-RT RIC presents the façade of an NWDAF towards the 5G core, in this case a 5G core DCCF/MFAF. However, in this option 2 approach a simplification of the SMO/Non-RT RIC functionality is achieved by eliminating the ability of 5GC NFs to discover NWDAF instances via the NRF and UDM. Rather, in this option 2 approach, the 5GC NFs can only discover via the NRF the DCCF/MFAF instances, which they would do through standard means ([i.11], clause 6.3.19). Neither does the DCCF/MFAF discover NWDAF façade instances, but rather option 2 assumes that the DCCF/MFAF knows how to reach the various NWDAF façade instances through local configuration.
-
-NOTE: See [i.11], clause 6.3.13: "The NF consumers should utilize the NRF to discover NWDAF instance(s) unless NWDAF information is available by other means, e.g., locally configured on NF consumers." In this case, the DCCF/MFAF is the sole "NF consumer".
-
-##### Observations:
-
-1. The process through which a new analytics type would be introduced would likely entail:
- - a. One or more rApp being loaded onto the Non-RT RIC capable of generating the desired analytic content in the "generally useful" structures, communicating to the NWDAF façade how to subsequently render that content into the NWDAF structures (see [i.24], clauses 6.6 and following).
-
-- b. Configure the DCCF with a mapping from analytics Id to the source NWDAF instance.
- - c. A new feature being loaded on a 5GC NF type capable of utilizing a particular NWDAF analytics Id, and which uses the NRF and optionally UDM (per UE) to determine that the SMO/Non-RT RIC is the entity from which to consume that specific analytics Id (perhaps with further discrimination based on TAC or NF mapping; [i.11], clause 6.3.19).
-- 2. The Non-RT RIC is within the SMO, where “M” is “management”. If the SMO/Non-RT RIC presents itself to the 5GC NFs as an NWDAF, it is taking the role of a network function. The implications of this will be explored in the Detailed Specification.
-- 3. If there is a desire for the DCCF/MFAF to also be able to access and share historical SMO/Non-RT RIC analytics, then the NWDAF façade would also need to support the optional Nnwdaf\_DataManagement Subscribe/Notify services.
-- 4. The NWDAF specification (see [i.24]) lists many other functionalities that an NWDAF can optionally support, such as supporting an external ADRF, providing training services to other 5GC NFs, aggregation and transfer of analytics, etc. Thus, other optional interfaces of the NWDAF (e.g., Nnwdaf\_DataManagement, Nnwdaf\_ModelProvision and Nnwdaf\_ModelInfo) are not considered. Because the SMO/Non-RT RIC does not support such functionality at this time nor are they critical to the topic of sharing data between RAN and core, this assumes that the NWDAF façade to the 5GC would be that of an NWDAF instance that does not support this optional functionality.
-- 5. Because in both option 2 and option 1 the SMO/Non-RT RIC assumes the façade of an NWDAF instance relative to the 5GC, option 2 can be viewed as an interim deployment step that can be seamlessly evolved to an option 1 approach.
-
-##### Benefits of this approach:
-
-- 1. No duplication of AnLF functionality between the SMO/Non-RT RIC and a separate NWDAF, resulting in less cost and management complexity for a carrier/operator.
-- 2. No changes to the 3GPP defined interfaces, and no new interfaces need to be defined.
-- 3. This option addresses the "fundamental challenge" by following an established pattern used for delivery of rApp analytics to the Near-RT RIC via A1-EI.
-- 4. Simplification, over option 1, of the functionality of the NWDAF façade of the SMO/Non-RT RIC, eliminating the NRF and UDM registration interfaces assumed in option 1.
-
-##### Negatives of this approach:
-
-- 1. The practical cost of this simplification over that of option 1 is perhaps the elimination of some deployment options for SMO/Non-RT RIC instances that present an NWDAF façade, in order to avoid adding practical complexity to the DCCF/MFAF configuration. For example:
- - a. In this option approach it is unlikely that a carrier would want to deploy many, many instances of SMO/Non-RT RIC, distinguished both by analytics type and by geographical area of service (e.g., TAC and/or NF mapping), because that would significantly increase the complexity of the DCCF/MFAF configuration for distinguishing between these instances. Rather, because the 5GC NF’s ability to discover a DCCF/MFAF instance would likely be limited to a TAC or NF mapping ([i.11], clause 6.3.19), perhaps a simple one-to-many mapping between DCCF/MFAF instance and NWDAF façade would be more manageable through DCCF/MFAF configuration, the granularity of this mapping also likely being at the TAC or NF level.
- - b. In this option approach there is no update of the UDM to indicate when UE-level analytics are being collected, so there is no ability for the 5GC NFs to leverage the UDM to determine the source for UE-level analytics. (However, as per observation #5, option 2 does provide a seamless path to overcome this negative over time.)
-- 2. Configuration changes need to be made in the DCCF/MFAF with each new analytic type being exposed to the 5GC NFs, so that the DCCF/MFAF knows that the source of that analytic is the SMO/Non-RT RIC.
-
-The approach of option 2 is shown in figure 4.23.3.2-1 below:
-
-
-
-The diagram illustrates the interaction flow for SMO/Non-RT RIC to DCCF/MFAF. At the top, the SMO/Non-RT RIC (containing an NWDAF icon) and the DCCF/MFAF are shown. Above them, the NRF is shown with 'Register DCCF' and 'Discover DCCF' messages. Below the SMO/Non-RT RIC, the Near-RT RIC is shown, connected via an 'A1-EI' interface. The main interaction sequence is: 1. Any 5GC NF sends a 'Request' to DCCF/MFAF; 2. DCCF/MFAF sends a 'Request' to SMO/Non-RT RIC; 3. SMO/Non-RT RIC sends a 'Deliver' to DCCF/MFAF; 4. DCCF/MFAF sends a 'Deliver' to Any 5GC NF. Dashed lines represent subscription and notification messages: *Ndpcf\_DataManagement (Subscribe)*, *Ndpcf\_DataManagement\_Fetch (Request)*, *Ndpcf\_DataManagement (Notify)*, *Ndpcf\_DataManagement\_Fetch (Response)*, *Nnwdaf\_AnalyticsSubscription (Subscribe)*, *Nnwdaf\_AnalyticsInfo (Request)*, *Nnwdaf\_AnalyticsSubscription (Notify)*, and *Nnwdaf\_AnalyticsInfo (Response)*.
-
-Sequence diagram showing interactions between SMO/Non-RT RIC, NWDAF, DCCF/MFAF, NRF, Any 5GC NF, and Near-RT RIC. The diagram includes numbered steps 1-4 and various message exchanges like Register DCCF, Discover DCCF, Request, Deliver, and A1-EI. Dashed lines represent subscription and notification messages between the RIC and the NWDAF.
-
-Figure 4.23.3.2-1: SMO/Non-RT RIC to DCCF/MFAF
-
-#### 4.23.3.3 SMO/Non-RT RIC to separate NWDAF with façade of OA&M
-
-This option 3 approach follows the pattern defined in [i.24], clause 6.2.3.2. In this approach, the SMO/Non-RT RIC shares its analytics with a separate NWDAF, which in turn makes those analytics available to requesting 5GC NFs. Thus, in this option the AnLF functionality is duplicated in both the Non-RT RIC function and the NWDAF function.
-
-There are multiple sub-options regarding how to approach the "fundamental challenge". These are described in "observations" below.
-
-In this option 3 approach, the SMO/Non-RT RIC performs the role and presents the façade of an OAM system relative to the NWDAF (see [i.28]). In this option the separate NWDAF performs its normal functionality: receiving analytics requests from 5GC NFs, determining the source data that should be collected in order to fulfill that analytics request, using that source data to construct the analytics response, and forwarding the resultant analytics response to the requesting 5GC NF.
-
-##### Observations:
-
-1. The OAM interface presented as a façade towards the NWDAF [i.28] follows the SA5 approach whereby content is specified via Network Resource Models (NRMs) which define certain standardized attributes (e.g., PLMN ID, S-NSSAI, etc.). There is also the provision for vendor-specific extensions which, of course, would not be standardized. In order for the separate NWDAF to understand the semantic content of the information being sent from the OAM façade, the SMO/Non-RT RIC will need to either map its analytics content into these standard NRM structures or map that content into the extensions. Approaches for addressing the "fundamental challenge" include:
- - a. SMO/Non-RT RIC maps the "generally useful" data structures into the existing [i.28] standardized NRM attributes, with each rApp using data type registration to communicate to the OAM façade its own mapping into these standardized NRM attributes. However, given that the standard NRM attributes were defined by 3GPP independent of the NWDAF data structures, finding such a mapping is expected to be challenging at best, and hence is not considered a viable path forward.
- - b. SMO/Non-RT RIC maps the "generally useful" data structures into a set of new [i.28] standardized NRM attributes, with each rApp using data type registration to communicate to the OAM façade its own mapping into these standardized NRM attributes. This would require O-RAN to negotiate with 3GPP changes to [i.28] to define the new NRMs, and changes to [i.24] for the NWDAF to know how
-
-to generically map these NRM structures into the structures expected by [i.24]. For a variation on this approach, see item “e” below.
-
-- c. SMO/Non-RT RIC maps the "generally useful" data structures into a set of rApp-by-rApp defined [i.28] vendor extensions, with each rApp using data type registration to communicate to the OAM façade its own mapping into these one-off vendor extensions. With this approach, for each new analytic produced by an rApp, a negotiation would take place between the rApp vendor and the separate NWDAF vendor on how to encode its specific analytic information content into the extensions supported by [i.28]. This approach results in additional complexity which can stifle innovation and is thus not considered a viable path forward.
- - d. SMO/Non-RT RIC maps the "generally useful" data structures into a set of O-RAN defined [i.28] vendor extensions, with each rApp using data type registration to communicate to the OAM façade its own mapping into this set of O-RAN defined extensions. This would require O-RAN to negotiate with 3GPP changes to [i.28] and to [i.24] to define a standard set of [i.28] data structures into which the SMO/Non-RT RIC can map "generally useful" data structures, and the [i.24] mapping required for the NWDAF to derive the [i.24] data structures. This would, in effect, be negotiating an entirely new interface between O-RAN and 3GPP, a significant effort. A more practical variation of this approach can be found in item “e” below.
- - e. SMO/Non-RT RIC maps the "generally useful" data structures into the structures defined in [i.24], with each rApp using data type registration to communicate to the OAM façade its own mapping into this set of O-RAN defined extensions. The OAM façade would wrap those structures into the extensions supported by [i.28]. This would require modifications to [i.28] to define the standard method for wrapping these data structures, as well as a change to [i.24] such that an NWDAF would expect to find [i.24] data structures embedded in a [i.28] interface. Note that this approach has the SMO/Non-RT RIC performing some limited NWDAF functionality in that it knows how to map its analytics output into [i.24] data structures. Of the available approaches listed, this seems to be the more viable path forward.
-2. The analysis above related to the runtime exchange of instance data between the SMO/Non-RT RIC, however the NWDAF is also responsible for registering with the NRF the analytics types that it supports (see [i.26], clause 5.2.7.1 and [i.25], clause 6.1.6.2.45). It can also optionally register with the UDM its capability to produce an analytics ID for a specific UE. To do this, the separate NWDAF would need to discover the capabilities of the SMO/Non-RT RIC. Options include:
- - a. The SMO/Non-RT RIC could present the façade of an NWDAF towards the separate NWDAF, that separate NWDAF acting as an aggregation NWDAF (see [i.24], clause 6.1A). However, this approach conflicts with the fundamental premise of this option: that SMO/Non-RT RIC presents an OAM façade to the separate NWDAF. In addition, from an SMO/Non-RT RIC perspective this approach would be no different than option 1 and so will not be further considered.
- - b. A new interface being negotiated between O-RAN and 3GPP for automatically communicating to an NWDAF the capabilities of an OAM entity. This would be a significant effort.
- - c. Similar to option 2, leveraging the capability of [i.11], clause 6.3.13, such that the separate NWDAF knows how to reach the various NWDAF façade instances through local configuration. This seems like the only viable path forward.
- 3. Given the above, the process through which a new analytics type would be introduced assuming the most viable paths forward as described above:
- - a. One or more rApp being loaded onto the Non-RT RIC that are capable of generating the desired analytic content.
- - b. Configure the separate NWDAF with a mapping from analytics Id to the source OAM instance so that it can register that analytics Id with the NRF (and optionally, UDM).
- - c. A new feature being loaded on a 5GC NF type that requires access to a particular NWDAF analytics Id, and which uses the NRF and optionally UDM (per UE) to determine that the separate NWDAF entity is that from which to consume that specific analytics Id (perhaps with further discrimination based on TAC or NF mapping; [i.11], clause 6.3.19).
-
-*Benefits of this approach (assuming the most viable path forward):*
-
-1. Separate NWDAF determines SMO/Non-RT RIC instance for its source analytics, avoiding the need for new interfaces for SMO/Non-RT RIC to interact with the 5GC NRF and UDM. (Of course, see negative below as to how the NWDAF would discover new analytics types supported in the SMO/Non-RT RIC so as to register them.)
-2. This option addresses the "fundamental challenge" by following an established pattern used for delivery of rApp analytics to the Near-RT RIC via A1-EI.
-
-##### *Negatives of this approach (assuming the most viable path forward):*
-
-1. Duplication of AnLF functionality in both the SMO/Non-RT RIC and the separate NWDAF, resulting in less cost and management complexity for a carrier/operator.
-2. In addition, the NWDAF AnLF function as envisioned by 3GPP is capable of performing complex trending and AI/ML functionalities to process raw source data into the desired analytics output. In this option 3 approach, however, the NWDAF's role is only of adaptation and reformatting of the analytics from the SMO/Non-RT RIC for presentation to the 5GC NF. With this option, a service provider would be using its likely complex NWDAF function to perform what is essentially a data adaptation function.
-3. As per observation #1e above, this option requires changes to two separate 3GPP interface specifications: [i.25] and [i.24]. Note that other alternatives were also explored in #1 above, however each of those alternatives also involved either changes to existing or defining entirely new 3GPP interfaces entailing even more effort, or else requiring per analytic custom coding in the NWDAF stifling innovation in the Non-RT RIC, both alternatives seeming less palatable than this documented negative.
-4. Configuration changes need to be made in the separate NWDAF with each new analytic type being exposed to the 5GC NFs, so that the NWDAF knows that the source of that analytic is the SMO/Non-RT RIC.
-5. The practical cost of the simplification taken in observation "2c" is perhaps the elimination of some deployment options for SMO/Non-RT RIC instances in order to avoid adding practical complexity to the DCCF/MFAF configuration. For example:
- - a. In this option approach it is unlikely that a carrier would want to deploy many, many instances of SMO/Non-RT RIC, distinguished both by Analytics type and by geographical area of service (e.g., TAC and/or NF mapping), because that would significantly increase the complexity of the DCCF/MFAF configuration for distinguishing between these instances. Rather, because the 5GC NF's ability to discover a DCCF/MFAF instance would likely be limited to a TAC or NF mapping ([i.11], clause 6.3.19), perhaps a simple one-to-many mapping between DCCF/MFAF instance and NWDAF façade would be more manageable through DCCF/MFAF configuration, the granularity of this mapping also likely being at the TAC or NF level.
- - b. In this option approach there is no ability for the 5GC NFs to leverage the UDM to determine the source for UE-level analytics. In addition, unlike option 2, because the SMO/Non-RT RIC presents the façade of an OAM endpoint, there is no seamless path to overcome this negative.
-
-This approach is shown in figure 4.23.3.3-1 below:
-
-
-
-Diagram showing the interaction between SMO/Non-RT RIC, NWDAF, and Any 5GC NF. The SMO/Non-RT RIC (with OAM facade) sends a 'Request' (2) to the NWDAF and receives a 'Deliver' (3). The NWDAF sends a 'Request' (1) to 'Any 5GC NF' and receives a 'Deliver' (4). The NWDAF also registers with UDM and NRF, and discovers NWDAF from NRF. A dashed line indicates 'Generic performance assurance and fault supervision management services' between the SMO/Non-RT RIC and the NWDAF. An 'A1-EI' interface connects the SMO/Non-RT RIC to the Near-RT RIC. Service messages include Nnwdaf\_AnalyticsSubscription (Subscribe/Notify) and Nnwdaf\_AnalyticsInfo (Request/Response).
-
-Figure 4.23.3.3-1: SMO/Non-RT RIC to separate NWDAF with façade of OA&M
-
-#### 4.23.3.4 SMO/Non-RT RIC to separate NWDAF with façade of RAN NF
-
-This option 4 approach also follows the pattern defined in [i.24], clause 6.2.3.2. In this approach, the SMO/Non-RT RIC shares its analytics with a separate NWDAF, which in turn makes those analytics available to requesting 5GC NFs. Thus, in this option the AnLF functionality is duplicated in both the Non-RT RIC function and the NWDAF function.
-
-There are multiple sub-options regarding how to approach the "fundamental challenge" (in fact the same that were presented in option 3). These are addressed below.
-
-In the option 4 approach, the SMO/Non-RT RIC performs the role and presents the façade of a RAN NF providing performance management OAM relative to the NWDAF ([i.27], clause 5.1.1). In this option the separate NWDAF performs its normal functionality: receiving analytics requests from 5GC NFs, determining the source data that should be collected in order to fulfill that analytics request, using that source data to construct the analytics response, and forwarding the resultant analytics response to the requesting 5GC NF.
-
-##### Observations:
-
-1. Similar to option 3, the RAN NF interface presented as a façade towards the NWDAF [i.27] follows the SA5 approach whereby content is specified via Network Resource Models (NRMs) which define certain standardized attributes (e.g., PLMN ID, S-NSSAI, etc.). There is also the provision for vendor-specific extensions which, of course, would not be standardized. In order for the separate NWDAF to understand the semantic content of the information being sent from the RAN NF façade, either the SMO/Non-RT RIC will need to either map its analytics content into these standard NRM structures (see [i.24], clauses 6.2 and following), or map that content into vendor-specific extensions. The options and the viability assessment for addressing the "fundamental challenge" would be basically the same as that of option 3.
-2. The options and viability assessment thereof for the separate NWDAF discovering the analytics capabilities of the SMO/Non-RT RIC would be basically the same as that of option 3.
-3. The process through which a new analytics type would be introduced would be the same as that described in option 3.
-
-##### Benefits of this approach:
-
-1. Separate NWDAF determines SMO/Non-RT RIC instance for its source analytics, avoiding the need for new interfaces for SMO/Non-RT RIC to interact with the 5GC NRF and UDM. (Of course, the NWDAF should support interfaces to the NRF and UDM to register new analytics types that are supported in the SMO/Non-RT RIC.)
-2. This option follows the same basic rApp-to-framework pattern already established for delivery of rApp analytics to the Near-RT RIC via A1-EI.
-3. The same interface to the NWDAF can be leveraged by both the Non-RT and Near-RT RICs.
-
-##### Negatives of this approach:
-
-1. This approach shares the same negative as option 3 list item #1.
-2. This approach shares the same negative as option 3 list item #2.
-3. This approach shares the same negative as option 3 list item #3, substituting occurrences of reference [i.28] with reference [i.27] as appropriate.
-4. This approach shares the same negative as option 3 list item #4.
-5. This approach shares the same negative as option 3 list item #5.
-
-This approach is shown in figure 4.23.3.4-1 below:
-
-
-
-Diagram of SMO/Non-RT RIC to separate NWDAF with façade of RAN NF. The diagram shows the SMO/Non-RT RIC (containing NWDAF sub-case and RAN NF) interacting with the NWDAF, UDM, NRF, and Any 5GC NF. The RAN NF acts as a façade for the NWDAF sub-case. The NWDAF interacts with the UDM and NRF for registration and discovery. The NWDAF also interacts with Any 5GC NF for requests and deliveries. The SMO/Non-RT RIC also interacts with the Near-RT RIC via the A1-EI interface. The diagram includes numbered steps 1-4 and labels for messages like 'Register NWDAF', 'Discover NWDAF', 'Request', 'Deliver', and 'NF PM Services'.
-
-Figure 4.23.3.4-1: SMO/Non-RT RIC to separate NWDAF with façade of RAN NF
-
-#### 4.23.3.5 SMO/Non-RT RIC to external NWDAF with façade of 3GPP MDA
-
-This option 5 is a variation of option 3 hence it follows the pattern defined in [i.24], clause 6.2.3.2 but leverages the 3GPP MDA specification in [i.41], instead of OAM as in option 3. Similar to option 3, the SMO/Non-RT RIC performs the role, and presents the façade of, a 3GPP management service towards the NWDAF except that in option 5 this is an MDA service (see [i.24] and [i.41]). Same as in option 3, the external NWDAF performs its normal functionality: receiving analytics requests from 5GC NFs, determining the source data that should be collected in order to fulfill that analytics request, requesting the analytics from the target MDA service source data to construct the analytics response, and forwarding the resultant analytics response to the requesting 5GC NF.
-
-##### Observations:
-
-1. The main difference with option 3 is that option 5 uses 3GPP MDA façade instead of OAM:
-
-- a. MDA service exposed to the NWDAF [i.28] follows the 3GPP SA5 approach whereby content is specified in the MDA specification [i.41]. There is also the provision for vendor-specific extensions which, of course, would not be standardized. As per [i.28], the NWDAF understands the 3GPP MDA semantic content [i.41], so the SMO/Non-RT RIC can reuse the existing 3GPP MDA analytics data types. In addition, O-RAN can define new RAN analytics data types as needed, as extensions to the 3GPP MDA data types.
-2. Approach for addressing the "fundamental challenge" include:
- - a. SMO/Non-RT RIC can reuse the existing [i.41] standardized MDA data types, with each rApp using data type registration to communicate to the MDA façade its own mapping into these standardized 3GPP MDA attributes. There are two possible alternatives:
- - i. O-RAN defines its own RAN analytics data types as per the vendor-extension mechanism enabled in 3GPP MDA, where O-RAN defines its extensions. The NWDAF [i.24] will need to understand the O-RAN standardized extensions; or
- - ii. O-RAN to request 3GPP SA5 to define a dedicated O-RAN data type extension in [i.41], to enable O-RAN to define its contents/structure.
- - b. SMO/Non-RT RIC maps the data structures into a set of O-RAN defined vendor extensions [i.28], [i.41]], with each rApp using data type registration with DME to communicate the supported set of O-RAN defined RAN analytics extensions.
- - c. In case of rApps which do not produce RAN analytics types in a standardized format (3GPP MDA, O-RAN), then the rApps are expected to provide their own mappings into the standardized set of RAN analytics data types. The rApps use data type registration with DME to communicate this mapping so that they can be discoverable for consumption. The MDA façade would wrap those structures into the extensions supported by [i.24], [i.41]], or specified in O-RAN.
- 3. Same as for option 3 - the NWDAF is responsible for registering with the NRF the analytics types that it supports, to enable discovery by 5GC NFs (see [i.26], clause 5.2.7.1 and [i.25], clause 6.1.6.2.45.). It can also optionally register with the UDM its capability to produce an analytics ID for a specific UE. To do this, the external NWDAF would need to discover the RAN analytics capabilities of the MDA service produced by the SMO/Non-RT RIC. Options include:
- - a. Same as in option 3, leveraging the capability of [i.11], clause 6.3.13, such that the external NWDAF knows how to reach the various MDA façade instances through local configuration.
- - b. NWDAF can discover the RAN analytics service/s of the SMO/Non-RT RIC via SME service discovery mechanisms, and it can discover the supported RAN analytics data types via DME. That implies that NWDAF has the ability to consume the SME and DME services, and this is an impact to [i.24].
- 4. Given the above, the process through which a new analytics type would be introduced assuming the most viable paths forward as described above:
- - a. One or more rApp being loaded onto the Non-RT RIC that are capable of generating the desired RAN analytic content.
- - b. Configure the external NWDAF with a mapping from analytics Id to the source MDA instance so that it can register that analytics Id with the NRF (and optionally, UDM) on behalf of the SMO/Non-RT RIC.
- - c. A new feature being loaded on a 5GC NF type that requires access to a particular NWDAF analytics Id, and which uses the NRF and optionally UDM (per UE) to determine that the external NWDAF entity is that from which to consume that specific Analytics Id (perhaps with further discrimination based on TAC or NF mapping; [i.11], clause 6.3.19).
-
-##### Benefits of this approach (assuming the most viable path forward):
-
-1. External NWDAF determines SMO/Non-RT RIC instance for its source analytics using the NWDAF consumption of MDA services as described in [i.24], avoiding the need for new interfaces for SMO/Non-RT RIC to interact with the 5GC NRF and UDM.
-2. It offers a single/common solution to provide both the RAN analytics data, such as the UE location predictions described in this use case, as well as RAN management data analytics.
-3. New RAN analytics can be flexibly added in Non-RT RIC as needed, via e.g., rApps.
-
-4. Dynamic service and data discovery by NWDAF: the MDA service and the data types produced by the SMO/Non-RT RIC can be discovered using the service discovery via SME, and respectively the data discovery via DME.
-
-##### *Negatives of this approach (assuming the most viable path forward):*
-
-1. If a dynamic discovery of the MDA service and RAN analytics types supported by the SMO/Non-RT RIC is desired, then NWDAF needs to be capable to consume the SME and DME services. This is an impact to [i.24].
-2. If the static method is used, then configuration changes need to be made in the external NWDAF with each new analytic type being exposed to the 5GC NFs, so that the NWDAF knows that the MDA source of that analytic is the SMO/Non-RT RIC.
-
-NOTE: As the static/configuration approach is the one provided in 3GPP [i.24], this is a common negative in most options, as in all cases there is some level of configuration needed in NWDAF to recognize different sources of data.
-
-### 4.23.4 Benefits of O-RAN architecture
-
-The Non-RT RIC will be capable of generating analytics that have general usefulness to the core as well. Thus, it is beneficial to overall efficiency that such analytics produced by the Non-RT RIC can be shared with the core, rather than requiring a separate NWDAF to also generate them. Even more so, there are some analytics that the RAN is in a better position to generate than the core, such as UE mobility predictions. This is true irrespective of which specific solution approach is used to enable such sharing.
-
-## 4.24 Industrial vision SLA assurance
-
-### 4.24.1 Background information
-
-Industrial vision is an image recognition technology used for automatic inspection, work piece processing and assembly automation, as well as the monitoring and control of production process by using machines to replace human eyes for various measurements and judgments. The main feature of industrial vision system is that it needs to collect the images of the products tested or processed in the area with dense production lines, and then transmit them to the vision server for detection and feedback the results.
-
-### 4.24.2 Motivation
-
-5G pre-scheduling technology can greatly reduce the transmission delay and improve the transmission reliability. However, the traditional static pre-scheduling mechanism does not fully consider the actual industrial production line uplink transmission characteristics. Regardless of whether the terminal has uplink transmission data, it always allocates air interface resources according to the existing configuration, resulting in a large waste of resources, and a significant decline in the actual bearable traffic of the cell, which is difficult to deploy commercially.
-
-Therefore, the commercial pre-scheduling mechanism generally adopts a dynamic pre-scheduling fashion, in which scheduling start time can be dynamically adjusted according to the actual business characteristics. In order to realize dynamic pre-scheduling, the network side needs to perceive the arrival of uplink transmission data on the terminal side, prepare uplink air interface resources for this terminal in advance, and configure the pre-scheduling adaptively.
-
-O-RAN based architecture will enable such adaptive pre-scheduling parameters configuration to be implemented and help to realize the high efficiency of industrial vision.
-
-### 4.24.3 Proposed solution
-
-Industrial vision use case mainly involves the Non-RT RIC, Near-RT RIC, E2 nodes in the O-RAN architecture, and industrial vision server (MES), industrial camera in the production system. The data transmission to Non-RT RIC approach includes, but not limited to, below method: non-RAN data about production line/camera information and data transmission information is transmitted to Non-RT RIC as enrichment information [i.30], [i.31].
-
-NOTE: The enrichment information mentioned above can be also obtained from the 5G core network.
-
-With enrichment information from industry server application server, base station can sync the camera data uplink resource allocation with work piece arrival time through dynamic pre-scheduling, as shown in figure 4.24.3-1.
-
-
-
-Figure 4.24.3-1: Industrial vision SLA assurance overview. This diagram shows the architecture of an industrial vision system. It is divided into two domains: the OT domain (left) and the CT domain (right), separated by a dashed line representing the 5G transmission. In the OT domain, an 'Edge Computer Room' contains an 'Industrial Vision Application Server' and 'MES'. Below it, a 'Production Line' includes an 'Industrial Camera', 'Material Returning Equipment', and a 'PLC'. Data from the camera and PLC flows into the 5G transmission. In the CT domain, the 5G transmission connects to a '5G CPE', which is connected to a 'gNB'. The 'gNB' is connected to a 'Near-RT RIC', which is connected to a 'Non-RT RIC'. A 'UPF' is also shown in the CT domain, connected to the 'Non-RT RIC' and the '5G transmission'.
-
-Figure 4.24.3-1: Industrial vision SLA assurance overview
-
-In order to realize the adaptive configuration of pre-scheduling process, the Near-RT RIC needs to adaptively calculate three pre-scheduling parameters matching with the industrial vision periodical business characteristics, including pre-scheduling data size, pre-scheduling period and pre-scheduling start time, so as to configure the E2 node via E2 control/policy service with those pre-scheduling parameters.
-
-
-
-Figure 4.24.3-2: Industrial vision dynamic pre-scheduling. This diagram illustrates the iterative process of dynamic pre-scheduling. A horizontal timeline at the top shows four stages of resource allocation: 'allocated too early', 'allocated slightly early', 'allocated perfectly', and 'allocated slightly late'. Below this, a graph shows 'uplink resource' on the y-axis and 'time' on the x-axis. It depicts 'camera data' being transmitted in bursts. The process is numbered: 1. 'Based on Enrichment Information, RIC configures pre-scheduling data size, period and initial start time'; 2. 'With pre-schedule utilization report from E2 and delay info from EI, RIC could evaluate how good the sync is'; 3. 'RIC adjusts the start time iteratively'; 4. 'RIC stops adjusting when transmission performance data (e.g. pre-schedule utilization) becomes stable in reasonable range'.
-
-Figure 4.24.3-2: Industrial vision dynamic pre-scheduling
-
-The dynamic pre-scheduling workflow is shown in figure 4.24.3-2. At the start-up stage of production line, pre-scheduling data size and pre-scheduling period are calculated by the Near-RT RIC based on production line speed and configured industrial camera attributes, such as image color, pixel, etc. These production line data can be imported as enrichment information to the Non-RT RIC, and then delivered to the Near-RT RIC. Then, the Near-RT RIC decides an initial pre-scheduling start time, which can be absolute time or relative time depending on the Near-RT RIC's capability to synchronize time with E2 nodes. The pre-scheduling start time is the time at which the first pre-scheduling of the whole iterative process should start.
-
-The Near-RT RIC then configures the E2 node via E2 control/policy service with pre-scheduling data size, pre-scheduling period and pre-scheduling start time parameters. Note that the configured parameters mentioned above only serve as scheduling recommendations to E2 nodes. Actual PRB scheduling depends on many other factors not captured by this use case. E2 node might for instance supersede Near-RT RIC’s recommendation in case high priority delay critical data needs to be scheduled.
-
-After initial configuration, the Near-RT RIC adaptively adjusts the pre-scheduling start time based on the service data transmission information, including pre-scheduling time-domain resource utilization and image data transmission delay related enrichment information. The pre-scheduling time-domain resource utilization is to be provided by E2 node, but it is currently not defined in the E2 interface specification, and it can be defined as the ratio of the time-domain resource of the data to be scheduled to the total pre-scheduled time-domain resource. The image data transmission delay related enrichment information is provided to the Non-RT RIC by industrial vision server (MES) which hosts industrial vision application, and is then delivered to the Near-RT RIC.
-
-The initial pre-scheduling starting time can be set to $T=0$ , and then iteratively adjusted based on the service data transmission information, as shown in figure 4.24.3-3, until the service data transmission information converges to a reasonable range.
-
-
-
-The figure illustrates the iterative adjustment of the pre-scheduling starting time. The x-axis represents 'Time' and the y-axis represents 'Pre-scheduling cycle'. The timeline starts with an 'Initial Pre-scheduling starting time' at $T=0$ . Service data transmission is shown as orange blocks, and pre-scheduling resource utilization is shown as light orange blocks. The diagram shows three adjustments: 'First adjustment' at $T=t$ , 'Second adjustment' at $T=2t$ , and 'Third adjustment' at $T=2t+t'$ . The 'Data transmission time in one service period' is indicated by a bracket on the first service data block. The legend identifies 'Service Data' as orange and 'Pre-scheduling Resource' as light orange.
-
-Figure 4.24.3-3: Pre-scheduling starting time adjustment illustration. A line graph with Time on the x-axis and Pre-scheduling cycle on the y-axis. It shows orange blocks for Service Data and light orange blocks for Pre-scheduling Resource. The pre-scheduling resource blocks are iteratively shifted to align with the service data blocks through a series of adjustments: First adjustment at T=t, Second adjustment at T=2t, and Third adjustment at T=2t+t'.
-
-**Figure 4.24.3-3: Pre-scheduling starting time adjustment illustration**
-
-### 4.24.4 Benefits of O-RAN architecture
-
-Near-RT RIC based recommendation of pre-scheduling configuration towards the E2 node might reduce the latency and improve the timing accuracy of image data transmission and might reduce scheduling related uplink signal overhead. The proposed solution to support industrial vision business assurance requires features provided by O-RAN architecture to satisfy the requirements via interoperable E2 interfaces and including input from external systems and external applications.
-
-## 4.25 Void
-
-## 4.26 Interference detection, prediction and optimization
-
-### 4.26.1 Background information
-
-LTE and 5G network are deployed based on co-frequency networking due to limited radio resources, which leads to co-frequency interference becoming the bottleneck of network performance. Heterogeneous networks as well as ultra-dense networks make inter-cell interference more complex. As a result, how to detect and/or predict, and then optimize interference is of great importance for wireless networks. Current research mainly focuses on a class of interference optimization solutions called Inter-Cell Interference Coordination (ICIC), which include static ICIC and dynamic ICIC, assuming that inter-cell interference is available via detection and/or prediction. The principle of ICIC is to restrict the use of radio resources in individual cells in an inter-cell coordination manner, including restricting which time-frequency resources are available, or limiting their transmitting power on certain time-frequency resources. The principle of ICIC is to divide all cells in the network in several categories, then divides the UE to Cell Edge User (CEU) as well as Cell Center User (CCU), and schedule CEU to edge radio resources.
-
-Such ICIC solutions suffer from the following limitations:
-
-- The radio resources are allocated statically or in non-real time, and do not support dynamic adjustment, which causes low radio resource utilization.
-- ICIC depends on specific ideal cell networking structure, and the performance of interference optimization algorithm is poor for complex networking structure.
-- The radio resource allocation is based on cell level, and do not support UE level or UE group level.
-- The measurement data is used for post-interference analysis and optimization, in a non-real-time manner.
-
-Besides, current research may mainly focus on interference optimization, based on the assumption that inter-cell interference is available via detection and/or prediction. In fact, interference detection and prediction is not less important than interference optimization. On the one hand, interference detection and/or prediction with high accuracy contributes to accurate and efficient interference optimization. On the other hand, interference detection and/or prediction can be utilized to optimize other transmission configurations, e.g., Modulation and Coding Scheme (MCS), not limited to radio resources allocation.
-
-In addition to LTE and 5G interference, there are other non-3GPP types of interference experienced in a 5G network including internal RF interference, such as passive intermodulation, and external RF interference, such as ducting, that need to be detected and optimized. To support effective interference optimization, there is a need to identify the source of the interference in terms of interference type and geographical location.
-
-Thanks to the open interface and intelligent functionalities provided by the O-RAN architecture, multi-cell-based collaborative real-time interference detection, prediction and interference optimization schemes can be realized. Multi-dimensional data, e.g., network level measurement data, can be acquired and used for interference detection, interference prediction, interference relationships construction, and interference optimization in real time. Interference relationship construction can further take QoS related metrics into analysis to facilitate UE service assurance through interference management. Based on the AI policy as well as interference relationships, Near-RT RIC ensures optimal radio resource allocation for UE or UE group or RAN slice through E2 interface towards RAN for interference optimization. In addition, based on the history interference detection, Near-RT RIC can predict interference for future data transmissions and thus facilitates MCS optimization to adapt to fluctuating interference.
-
-### 4.26.2 Motivation
-
-The main objective is to ensure interference optimization to be supported within the O-RAN architecture and its open interfaces in a way that allows UE or UE group or RAN slice or cell level modification of RAN behavior, features, scheduling, resource allocation procedures and other configuration based on user QoS requirements or other multi-dimensional data. This includes:
-
-1. Interference detection. Near-RT RIC helps UE(s) to achieve UE-level interference detection by optimally configuring the reference signal resource allocation and information transmission strategy for the serving cell and its intra-frequency neighboring cells. Near RT RIC helps UL interference detection, classification and locating by leveraging the measurements of the interference levels and interference patterns at PRBs and mMIMO beams. Based on the A1 policy (interference detection related policy) developed by the Non-RT RIC, Near-RT RIC generates and sends the E2 control or policy, such as allocated resource(s) of the reference signal, information transmission strategy to indicate UE for channel measurement, channel estimation and interference measurement as well as PRBs and mMIMO beams to be monitored. Interference detection, classification and locating results can be used as a trigger condition for interference optimization or exposed to other xApps.
-2. Interference relationships construction. Interference optimization is assisted by interference relationships, e.g., interference graph, which are used to describe the potential interference relationships between UEs or UE groups or RAN slices or PRBs or mMIMO beams in a multi-cell coverage area. Interference relationships are constructed by Near-RT RIC. Multi-dimensional data, e.g., QoS related metrics from SMO and network level measurement reported by RAN through E2 interface can be used for Near-RT RIC to construct interference relationships.
-3. Interference optimization. Near-RT RIC achieves interference optimization by optimally allocating radio resources to UEs or UE groups or RAN slices or cells or PRBs or mMIMO beams based on the interference relationship between UEs or UE groups or RAN slices or cells or PRBs or mMIMO beams as described in the interference relationship. Near-RT RIC receives the interference optimization related policy through A1 interface and the measurement data through E2 interface, and then the Near-RT RIC formulates an interference optimization policy for the serving cell and its intra-frequency neighboring cells based on the interference relationship, including radio resource allocation.
-4. Above interference optimization flow can be locally applied even in Non-RT RIC by closed loop control via O1 interface for long-term traffic trends. The optimization by Near-RT RIC is fast loop optimization, while the optimization by Non-RT RIC is slow loop optimization. Appropriate approaches can be selected depending on traffic trends or use cases.
-5. Interference prediction. In many cases, there is a time delay between the measurement and use of the channel, so that in time the channel information obtained at the moment of the reference signal measurement is accurate, and at the moment of use the channel information is outdated. Taking uplink transmission as an example, the transmission configuration (e.g., RB allocation and MCS) for PUSCH is indicated in the Downlink Control Information (DCI), which is sent by gNB ahead of K2 slots before PUSCH transmission. The transmission configuration is determined by gNB, based on the latest estimated channel quality, e.g., SINR, via channel measurement. Due to the fluctuation of wireless links, the channel quality may have changed dramatically from the moment of channel measurement to the moment of PUSCH transmission, leading to performance degradation. In this way, predicting future interference in data transmission for uplink transmission configuration optimization, such as MCS optimization, maximises the transmission efficiency of the wireless link while ensuring reliability.
-
-### 4.26.3 Proposed solution
-
-#### 4.26.3.1 Fast loop optimization
-
-The concept of interference detection and optimization use case for fast loop control is given in figure 4.26.3.1-1.
-
-
-
-Diagram of Interference detection and optimization use case for fast loop control. The diagram shows a hierarchy: Service Orchestration & Management (top) contains Non-RT RIC with 'Interference Detection and Optimization related Policy'. This connects via 'Parameters and policy update' to Near-RT RIC. Near-RT RIC contains 'Interference Detection and Optimization xApp' which includes 'Interference Detection' (Reference signal resource allocation, Information transmission strategy configuring), 'Interference Relationships Construction', and 'Interference Optimization: Multi-Cell Radio Resource Allocation'. Below this is the Near-RT RIC Platform. At the bottom, a CU/DU/gNB is connected to the platform via an E2 interface and is linked to four User Equipment (UE) units.
-
-Figure 4.26.3.1-1: Interference detection and optimization use case for fast loop control
-
-The interference detection and optimization application includes interference detection, classification and locating, interference relationships construction, as well as interference optimization, which are deployed in Near-RT RIC.
-
-In the process of implementing interference detection and optimization, Non-RT RIC generates interference detection and optimization-related policy and sends the policy to Near-RT RIC via A1 interface. Interference detection and optimization-related policy includes reference signal type, measurement report configuration, neighborhood list of serving cell, interference detection execution period, threshold for performing interference optimization, etc.
-
-The Near-RT RIC receives interference detection and optimization policies from the Non-RT RIC and obtains the necessary interference-related measurements from the network-level measurement reports via the E2 interface for interference relationships graph construction, e.g., interference graph, and interference optimization-related E2 control or policy generation. The Near-RT RIC sends control or policies via the E2 interface to the RAN for interference optimization, and also sends Non-RT RIC with interference optimization performance reports for evaluation and optimization. One of the examples in resource allocation control is that Near-RT RIC separates resources between aggressor and victim cells for per-slice interference (as specified in [i.42], clause 9.3.16). Other examples of resource allocation control for cell resources include Tx power, PRB blanking, carrier aggregation, and beam management including beam forming and beam muting.
-
-The base station supports the reporting of network status and UE measurement data based on the policies developed by Near-RT RIC and sends them to Near-RT RIC via E2 interface with the required granularity. At the same time, the base station supports the execution of interference optimization policies based on E2 messages to achieve, e.g., resource allocation for the UE (or UE group or RAN slice).
-
-UEs support network interference detection based on the reference signal configuration and report the result to RAN. RAN supports uplink interference detection, classification and locating based on the interference levels and interference patterns of PRBs as well as mMIMO beams/interference.
-
-##### 4.26.3.1.1 Interference detection
-
-The Near-RT RIC generates an interference detection policy (E2 policy) based on the interference detection related policy (A1 policy) sent by the Non-RT RIC. The interference detection policy includes:
-
-- 1) allocated resource(s) of the reference signal for the gNB(s);
-- 2) information transmission strategy configured for the intra-frequency cells adjacent to the cells corresponding to the gNB(s);
-- 3) detection profile for interference levels and interference patterns of PRBs where detection profile contains the criteria for engaging the E2 service;
-- 4) detection profile for mMIMO beams/interference where detection profile contains the criteria for engaging the E2 service.
-
-Based on the reference signal resource configuration and information transmission strategy configuration for the serving cell and intra-frequency neighboring cells, the UE can perform real-time interference detection. Based on detection profile for interference levels and interference patterns of PRBs as well as detection profile for mMIMO beams/interference, RAN can perform near-RT interference detection, classification and locating.
-
-##### 4.26.3.1.2 Interference relationships construction
-
-Near-RT RIC constructs interference relationships, e.g., interference graph, between UEs and UE groups and RAN slice based on the received QoS related metrics from SMO and network level measurement from RAN. Near-RT RIC uses interference relationships graph for interference optimization. Near-RT RIC constructs interference relationships based on the scheduled resources of PRBs of the serving cell and its intra-frequency neighboring cells as well as parameters of mMIMO beams.
-
-##### 4.26.3.1.3 Interference optimization
-
-When the interference detection result meets the interference optimization conditions (e.g., the interference value detected by UE is greater than the interference optimization threshold, the interference level and interference pattern of PRBs meet criteria in the detection profile or the mMIMO beams/interference meet the criteria in the detection profile), the interference optimization formulates an interference optimization policy based on the latest interference relationships and selects appropriate time and frequency domain for radio resources for DL or UL transmission in the service cell and its intra-frequency neighboring cells in order to achieve multi-cell radio resource coordination or active interference avoidance, and thus achieve interference optimization.
-
-#### 4.26.3.2 Slow loop optimization
-
-The concept of interference detection and optimization use case for slow loop control is given in figure 4.26.3.2-1.
-
-
-
-Diagram of Interference Detection and Optimization architecture. At the top, 'Service Management & Orchestration' contains a 'Non-RT RIC' block. Inside 'Non-RT RIC' is an 'Interference Detection and Optimization rApp' block, which contains an 'Interference Optimization' sub-block described as 'Multi-cell radio resource allocation for long-term traffic trends'. Below the rApp is a 'Non-RT RIC Platform' block. Two large orange arrows point between the rApp and the platform. Below the platform, an 'O1' interface connects to a central 'E2 nodes' block. Four 'UE' (User Equipment) blocks are connected to the 'E2 nodes' block via dashed blue arrows.
-
-Figure 4.26.3.2-1: Interference detection and optimization use case for slow loop control
-
-The interference detection and optimization application includes interference detection, interference relationships construction, and interference optimization, which are deployed in Non-RT RIC.
-
-In the process of implementing interference detection and optimization, Non-RT RIC generates interference detection and optimization-related policy and sends control based on the policy to E2 nodes via O1 interface. The control information includes appropriate time and frequency domain resources in the service cell and its intra-frequency neighboring cells.
-
-The base station supports the reporting of network status based on the policies developed by control information from Non-RT RIC and sends them to Non-RT RIC via O1 interface with the required granularity. At the same time, the base station supports the execution of interference optimization policies based on the control information to achieve resource allocation for the UE (or UE group or RAN slice).
-
-UEs support network interference detection based on the reference signal configuration and report the result to RAN.
-
-##### 4.26.3.2.1 Interference detection and optimization
-
-When the interference detection result meets the interference optimization conditions (the interference value detected by UE is greater than the interference optimization threshold), the interference optimization formulates an interference optimization policy based on the latest interference relationships and selects appropriate time and frequency domain resources in the service cell and its intra-frequency neighboring cells in order to achieve multi-cell radio resource coordination or active interference avoidance, and thus achieve interference optimization.
-
-#### 4.26.3.3 Interference prediction for MCS optimization
-
-The concept of the interference prediction for MCS optimization is given in figure 4.26.3.3-1.
-
-
-
-The diagram illustrates the architecture for interference prediction for MCS optimization, organized into three horizontal layers:
-
-- Service Management& Orchestration (Top Layer):** Contains a box for **Non-RT RIC**. Inside this box is a sub-box labeled **Interference Prediction for MCS optimization Policy**. This layer connects to the middle layer via the **A1** interface.
-- Near-RT RIC (Middle Layer):** Contains a box for **Interference Prediction xApp**. Inside this box are two sub-boxes: **Data Collection** and **AI/ML model inference**. Below the xApp is a box for the **Near-RT RIC Platform**. Upward and downward arrows connect the xApp and the platform. This layer connects to the bottom layer via the **E2** interface.
-- E2 Nodes (Bottom Layer):** Contains a box for **MCS optimization**.
-
-Diagram of Interference prediction for MCS optimization architecture
-
-**Figure 4.26.3.3-1: Interference prediction for MCS optimization**
-
-In the process of implementing interference prediction for MCS optimization, Non-RT RIC generates interference prediction related policy and sends the policy to Near-RT RIC via A1 interface. Interference prediction for MCS optimization related policy includes neighborhood list of serving cell, prediction granularities and prediction steps, etc.
-
-The Near-RT RIC receives interference prediction for MCS optimization policies from the Non-RT RIC and obtains the necessary data required for interference prediction from the reports via the E2 interface for interference prediction related E2 control or policy generation.
-
-Assuming the AI/ML model training using the training data set is on Non-RT RIC or on Near-RT RIC, the trained AI/ML model will be deployed in the Near-RT RIC used for the AI/ML model inference.
-
-The Near-RT RIC sends control or policies with the predicted uplink interference to the E2 node via the E2 interface for MCS optimization, and also sends interference prediction-based MCS optimization performance to Non-RT RIC for evaluation and optimization.
-
-The E2 nodes support the reporting of interference prediction related data based on the subscriptions from Near-RT RIC, and send them to Near-RT RIC via E2 interface with the required granularity. At the same time, the E2 node supports the execution of MCS optimization based on E2 control or policy from Near-RT RIC.
-
-##### 4.26.3.3.1 Interference prediction
-
-Prediction interference for future data transmission in advance, is based on history interference and relevant features from neighboring cells.
-
-Different prediction granularities are available, e.g., wideband, RB group, and RB for frequency domain, and TTI, frame for time domain.
-
-##### 4.26.3.3.2 MCS optimization
-
-Adjust MCS based on the predicted interference for future data transmission. The method of adjusting the MCS could be realized by replacing the outdated interference with the predicted interference when estimate the channel quality (e.g., SINR), or adjusting the target BLER\ACK adjustment step\initial MCS using the predicted interference value, to maximize the transmission efficiency while ensuring the reliability.
-
-### 4.26.4 Benefits of O-RAN architecture
-
-The proposed solution to support a real-time interference detection, prediction and optimization for co-frequency networking. It requires features provided by O-RAN architecture to orchestrate these requirements via interoperable O1 or A1/E2 interfaces. Retrieving measurement metrics in near-real-time are offered by the O-RAN architecture for interference detection, interference prediction, interference relationships construction, and interference optimization.
-
-## 4.27 Communication and computing integrated networks
-
-### 4.27.1 Background information
-
-With the development of 5G and future networks, the integration of communication and computing has become a critical trend in network architecture. Traditional communication networks have focused primarily on data transmission and connectivity, while modern network applications increasingly require substantial computational resources. Examples of these applications include Artificial Intelligence (AI), Augmented Reality (AR), Virtual Reality (VR), autonomous driving, and Industrial Internet of Things (IIoT). These applications not only require high-speed, low-latency communication but also significant computing capabilities for real-time data processing and inference.
-
-The past decades witnessed the convergence of communication and computing trends in mobile network. Great efforts were made and good momentum were achieved. C-RAN featured by centralization, cooperative, clean and cloud were first proposed in 2009, which depicts the vision of software based virtualized RAN [i.1]. The concept of Network Function Virtualization (NFV) was initiated from 2012. It introduced the Information Technology (IT) to enable the network transformation from the traditional physical hardware network into a new software based virtualized network [i.44]. This further steers up the pace for the convergence of communication and computing in RAN. Multiple-access Edge Computing (MEC), which enables compute-intensive applications for mobile devices and access to cloud computing service at the edge of communication networks, had attracted great attention [i.45]. The virtualized/cloudification RAN infrastructure can serve as perfect edge computing platform. Thanks to the well-developed IT tools/frameworks, such as the containers, kubernetes, the general-purpose hardware infrastructure could be easily and dynamically shared by the RAN functionality and the edge applications, providing the converged capabilities of mobile communication and computing. Edge computing was also incorporated into 5G system in 3GPP since Release 15. However, the communication and computing services offered by the existing design, such as NFV and MEC, were designed separately and developed independently. To fulfill the gap, the coordination of computing and networking is proposed in the context of IMT-2020 and beyond, and provides network enhancements based on the functional architecture of IMT-2020, to achieve the computing and network joint optimization based on the awareness, control and management over computing resources [i.46], [i.47]. Besides the above, IETF initiated a new working group on computing aware traffic steering to study how the network edge can steer traffic between clients of a service and sites offering the services, considering the integrated network and compute resource status [i.48].
-
-### 4.27.2 Motivation
-
-The evolution of mobile networks toward deep integration of communication and computing is essential to support emerging applications like XR, real-time industrial control, and V2X. These services require tight coordination between computational processing and radio transmission. In this context, the timeliness of computational results directly depends on communication reliability, while radio resource availability is dynamically constrained by computing load variations.
-
-Current O-RAN architectures exhibit two fundamental limitations that prevent optimal joint optimization of system efficiency and service quality.
-
-On the one hand, the lack of unified modeling and orchestration for communication and computing resources hinders the system's ability to coordinate decisions across domains. Existing architectures maintain separate management planes for communication and computing resources, thereby preventing global optimization across domains. First, service degradation becomes unavoidable when radio-centric optimization directs traffic towards nodes with inadequate compute resources. For instance, access-related decisions such as handover or slice association may guide services toward cells with favorable radio conditions yet severely overloaded compute nodes. In scenarios such as frame-based XR rendering, this can lead to rendering latency exceeding the acceptable perceptual threshold, despite strong signal quality. Moreover, idle computing capacity within the RAN, which is subject to spatial and temporal tidal effects in mobile traffic, remains underutilized. Without a mechanism for real-time compute resource sharing, unused capacity cannot be reallocated to support adjacent AI inference or industrial tasks, resulting in low infrastructure return on investment.
-
-On the other hand, the lack of standardized mechanisms for exposing computing resource status limits the ability of external entities to coordinate services based on comprehensive system information. Although O-RAN defines interfaces for managing communication functions, it does not establish mechanisms for external entities (such as edge computing orchestrators or third-party applications) to discover and utilize RAN computing capabilities. The decision-making under incomplete information would impair the effectiveness of higher-level orchestration. For example, in distributed AI inference or collaborative V2X control, external platforms may need to schedule or offload tasks based on the network and compute state. In the absence of explicit exposure mechanisms, such platforms must rely on indirect estimation or static assumptions. Consequently, edge computing platforms cannot effectively offload computational tasks to nodes, leading to degraded service performance.
-
-The objective of this use case is to extend the O-RAN architecture to facilitate both internal joint optimization of communication and computing resources, as well as standardized exposure of computing capabilities to external systems. The O-RAN ALLIANCE focuses on promoting the openness and intelligence of RAN, and its architecture provides a solid foundation for this integration. O-RAN's cloud-based architecture (O-Cloud) supports the virtualization of multiple network functions, including RAN functions and edge computing applications. Additionally, O-RAN's intelligent capabilities—enabled by the Non-RT RIC and Near-RT RIC—allow for the dynamic optimization and management of both communication and computing resources. This flexibility enables O-RAN to meet the requirements of various application scenarios and network conditions, making it an ideal platform for realizing the CCIN vision.
-
-### 4.27.3 Proposed solution
-
-The CCIN use cases are divided into several sub-use cases to analysis requirements for different scenarios.
-
-#### 4.27.3.1 Sub-use case 1: Multi aspect handover optimization
-
-In scenarios where UE needs to handover between cloud-based RAN nodes while running applications with high computing and low latency requirements, the solution involves storing the compute capabilities of cloud-based RAN nodes such as O-CU and using this information in UE handover decisions. It leverages rApp to retrieve data from different cloud-based RAN nodes and derive the proximal computing capability and availability information. rApp then creates O1/A1-based configurations for multi-aspect handover optimization at Near-RT RIC instances, which use E2 control or E2 policies to ensure the UE handover to the optimal target cloud-based node.
-
-#### 4.27.3.2 Sub-use case 2: RAN edge computing resource information exposure
-
-When external entities such as orchestrators or application servers need to access unused computing resources in the O-Cloud infrastructure, the solution proposes that SMO collects and analyses computing-related resources from O-Cloud and provides a radio edge computing resource information service to service consumers such as orchestrators or application servers. It involves SMO requesting or subscribing to measurement data from O-Cloud and sending the radio computing information for managed O-Cloud related computing resources to the service consumer. This enables effective exposure of radio edge computing resource information to service consumers.
-
-#### 4.27.3.3 Sub-use case 3: O-RAN and mobile devices collaborative AI/ML inference
-
-For scenarios where mobile devices need to offload AI/ML inference tasks to the network due to limited computing resources, O-RAN can provide edge computing capabilities and communication assurance for collaborative AI inference scenarios. SMO could translate external communication and computing requests into O-RAN internal operations, orchestrating communication and computing resources to fulfill service requirements. Non-RT RIC and Near-RT RIC enable intelligent service assurance and network performance improvement, jointly optimizing communication and computing resources to ensure end-to-end performance. O-RAN can also provide RAN information including communication and computing information to network-side AI/ML endpoints, helping optimize AI/ML model split and exit decisions.
-
-Figure 4.27.3.3-1 shows how O-RAN support the collaborative AI inference application, such as industrial quality inspection, in the production line scenario.
-
-
-
-Diagram of AI/ML collaborative inference between mobile device and O-RAN. The diagram shows an 'External consumer' (e.g., Production Control Center) at the top, an 'SMO' (Service Management and Orchestration) block in the middle containing 'Non-RT RIC', and an 'O-Cloud' block at the bottom containing 'CU/DU', 'RAN', 'CN(e.g., UPF)', and 'Near RT RIC'. Below the O-Cloud are mobile devices. Arrows indicate five numbered interactions: 1. Capability exposure from SMO to External consumer; 2. Service request from External consumer to SMO; 3. Application deployment (split part 1) from External consumer to O-Cloud and (split part 2, layer 11-output) from SMO to O-Cloud; 4. Service assurance policy from SMO to O-Cloud; 5. Mobile device information collection from O-Cloud to SMO. A note states 'NOTE: the CN is out of O-RAN scope'.
-
-Figure 4.27.3.3-1: The AI/ML collaborative inference between mobile device and O-RAN
-
-To go a step further, in cases where there is a need for dynamic management of collaborative AI/ML inference tasks between mobile devices and the network, the solution focuses on the life-cycle management of collaborative AI/ML inference tasks by SMO. CCIN consumers provide SMO with a set of AI/ML models and performance requirements. Non-RT RIC generates AI/ML model deployment strategies based on current communication and computational resources. SMO deploys the selected AI/ML model on O-Cloud, while consumers deploy the corresponding model on mobile devices. Near-RT RIC monitors the AI/ML collaborative computing task and generates adjustment strategies based on current communication and computing status, updating the AI/ML model on mobile devices.
-
-Figure 4.27.3.3-2 illustrates an example of O-RAN implementing AI/ML collaborative inference computing task between mobile device and O-Cloud.
-
-
-
-
-
-Figure 4.27.3.4-1: XR rendering collaboration over SMO. This diagram shows the interaction between a Service management & Orchestration Framework (SMO), an External consumer, XR edge Applications, XR devices, and the O-Cloud. The SMO contains a Non-RT RIC (with optimization and decision analysis) and a Near-RT RIC (with E2 control policy for XR rendering assurance). The Near-RT RIC is connected to E2 Nodes (with E2 report for XR application). The O-Cloud is connected to the E2 Nodes. The External consumer sends a service request to the Non-RT RIC and receives capability exposure. The Non-RT RIC sends a service request to the External consumer. The External consumer sends application awareness to the Near-RT RIC. The Near-RT RIC sends capability exposure to the XR edge Applications. The XR edge Applications send XR rendering collaboration to the XR devices. The XR devices send execution on UE to the External consumer. The SMO also sends O1, O2, and A1 messages to the E2 Nodes. The O-Cloud sends 5d. Deploy or scale the XR applications to the Near-RT RIC. A legend indicates that orange lines represent existing O-RAN components, green lines represent potential enhancements, and blue lines represent out-of-scope components. Notes indicate that XR edge applications can share infrastructure resources provided for O-RAN NFs.
-
-Figure 4.27.3.4-1: XR rendering collaboration over SMO
-
-#### 4.27.3.5 Sub-use case 5: Joint communication and computing optimization for V2X communications
-
-In V2X communication scenarios, especially at intersections where large amounts of data need to be processed with low latency, O-RAN can provide edge computing capabilities and communication assurance for computing in V2X. The vacant O-Cloud resources and collaboration between Non-RT RIC and Near-RT RIC facilitate on-demand resource allocation adjustments and joint optimization of communication and computing resource scheduling to ensure end-to-end performance.
-
-Figure 4.27.3.5-1 illustrates how O-RAN can facilitate computing in V2X communications, where the O-Cloud is used as the computing entity in O-RAN.
-
-
-
-Figure 4.27.3.5-1: An illustration of O-RAN assisted computing in V2X communications. This diagram shows the interaction between external consumers, the SMO, the Non-RT RIC, the Near-RT RIC, the O-Cloud, and an edge/cloud server. The external consumers send a communication and computing service request to the SMO and receive a communication and computing capability exposure. The SMO sends a communication and computing information exposure to the edge/cloud server. The Non-RT RIC sends an A1: service assurance policy or AI model to the Near-RT RIC. The Near-RT RIC sends data collection and E2: Device information collection to the O-Cloud. The O-Cloud sends data collection to the Near-RT RIC. The Near-RT RIC sends Y1: Communication and computing information exposure to the edge/cloud server. The O-Cloud contains a Hypervisor(VM/Container) and xApp. The legend indicates that orange lines represent existing O-RAN components, green lines represent potential enhancements, and blue lines represent out-of-scope components.
-
-Figure 4.27.3.5-1: An illustration of O-RAN assisted computing in V2X communications
-
-#### 4.27.3.6 Sub-use case 6: Exposure of performance information to assist computing resource scheduling
-
-In scenarios where the performance of a VNF/App deployed on an O-Cloud node does not meet requirements, the solution involves SMO collecting the performance information of VNF/Apps deployed on O-Cloud nodes through the O1 or O2 interface. It monitors the performance of these tasks and makes decisions to redeploy them based on this information. If the current node's performance does not meet the requirements of the VNF/App, the orchestrator can request SMO to redeploy the VNF/App to another node with better performance. This ensures that the computing task is executed on a node that can meet its performance requirements, optimizing resource utilization and task performance.
-
-When there is a need to adjust the scale of a computing task based on performance demands, the solution focuses on scaling the task up or down. The orchestrator subscribes to VNF/App performance information from SMO. When the performance information indicates a need for scaling (either scale out or scale in), the orchestrator triggers the corresponding action. SMO then scales the VNF/App via the O2 interface and notifies the orchestrator of the completion. This allows for dynamic adjustment of computing resources to meet the current demands, improving resource efficiency and task execution.
-
-### 4.27.4 Benefits of O-RAN architecture
-
-O-RAN architecture offers several significant advantages for the realization of CCIN. First, its open interfaces enable seamless integration and interoperability between communication and computing resource management systems. Furthermore, the AI-driven optimization capabilities of the Non-RT RIC and Near-RT RIC allow for data-driven decision-making and real-time adjustments to resource allocation, ensuring that both communication and computing resources are utilized effectively to meet application demands. Additionally, O-RAN's O-Cloud platform extends the RAN's capabilities, transforming it into an edge computing infrastructure. This enables localized data processing, reducing transmission latency and enhancing the responsiveness of time-sensitive applications, such as XR, autonomous driving, and AI inference, ultimately improving the overall performance and user experience.
-
-## 4.28 RAN intent-driven management services
-
-Void
-
-# Annex: Change history/Change request (history)
-
-| Date | Revision | Description |
-|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 2019.07.07 | 01.00.00 | Draft template |
-| 2019.08.28 | 01.00.01 | Addition of O-RAN IPR notes
Addition of CRs:
- CR-INSUR--Resource allocation strategy use case in UAV application scenario-20190815
- ORAN-WG1.UseCasesAnalysisReport_CR_NOK_DHO_20190815 |
-| 2019.09.20 | 01.00.02 | Addition of CR:
- ORAN-WG1.Netsia_QoE.UseCaseAnalysis_CR |
-| 2019.09.23 | 01.00.03 | Addition of CR:
- ORAN-WG1.Netsia_TrafficSteering.UseCaseAnalysis_CR |
-| 2019.09.26 | 01.00.04 | Addition of CR:
- O-RAN-WG1.UseCaseAnalysisINSUR -clean.docx |
-| 2019.09.26 | 01.00.05 | Addition of CR:
- ORAN-WG1.UseCasesAnalysisReport_CR_Amdocs_3DMIMO |
-| 2019.09.26 | 01.00.06 | Editorial updates to make use case sections as consistent as possible |
-| 2019.09.27 | 01.00.07 | Addition of CRs:
- ORAN-WG1.UseCasesAnalysisReport_CR_ORANGE_RAN_Sharing Sep 27.docx
- ORAN-WG1.UseCasesAnalysisReport_CR_Amdocs_3DMIMO
Editorial updates |
-| 2019.09.28 | 01.00.08 | Updates merged from
- O-RAN-WG1.UseCaseAnalysisINSUR -0927 |
-| 2019.10.17 | 01.00.09 | Updated 3D MIMO use case diagram 3.6.3-2 to reflect O1 CM interface rather than A1/E2 towards O-CU-CP
Updates merged from:
- ORAN-WG1.Correction on UAV_UseCasesAnalysisReport_CMCC_CR v1 |
-| 2019.10.17 | 01.00 | Final version 01.00 |
-| 2019.11.16 | 02.00.01 | Initial version of v2.0
Document version number update to v02.00.01 |
-| 2019.12.08 | 02.00.02 | Initial version of v2.0
- Editorial updates and corrections based on the comments received for v1.0 |
-| 2019.12.10 | 02.00.03 | Addition of new use case (Slice SLA Assurance):
- O-RAN_WG1_2019.11.27-Netsia_KDDI_ATT_TEF_UCTG_CR_UCAR_Slice_Assurance |
-| 2019.12.22 | 02.00.04 | Addition of new use case (QoS Based Resource Optimization):
- ORAN-WG1.Use Cases Analysis Report_QoS_based_resource_optimization |
-| 2020.01.14 | 02.00.05 | Addition of CR:
- ORAN-WG1.UseCasesAnalysisReport_CR_Traffic_Steering_Ericsson_2020.01.08 |
-| 2020.01.17 | 02.00.06 | Addition of CR:
- ORAN-WG1.Netsia_CR_ImprovementsForUCAnalysisReport_2020_01_16 |
-
-| | | |
-|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 2020.01.29 | 02.00.07 | Addition of CR:
- ORAN-WG1-CMCC-UseCasesAnalysisReport_CR_Traffic_Steering_2020.01.20 |
-| 2020.02.12 | 02.00.08 | Addition of CR:
- ORAN-WG1.UCTG_UseCaseAnalysisReport_CR_MassiveMIMO_Amdocs_clean+TIM_V2 |
-| 2020.02.23 | 02.00.09 | Editorial updates, including references |
-| 2020.03.01 | 02.00.10 | Editorial updates, fixing table of contents issues, spec naming corrections |
-| 2020.03.11 | 02.00.11 | Updates to various sections based on WG1 review/approval feedback |
-| 2020.03.11 | 02.00 | Final version 02.00 |
-| 2020.06.19 | 03.00.01 | Initial version of v3.0
Document version number update to v03.00.01 |
-| 2020.06.22 | 03.00.02 | Addition of CR:
- WG1_2020.02.17_KDDI-TEF-NET-ATT_UCTG_CR_MultiVendorSlice_r1 |
-| 2020.06.28 | 03.00.03 | Editorial updates to section 3.10 |
-| 2020.06.28 | 03.00.04 | Addition of CR:
- ORAN-WG1.UseCasesAnalysisReport_CR_NOK_ORANGE_complete_mMIMO_2020.03.25
Editorial updates for this CR (to merge with existing use case) |
-| 2020.06.29 | 03.00.05 | Addition of CRs:
- ORAN-WG1.UseCasesAnalysisReport_CR_NOK_ORANGE_complete_mMIMO_2020.06.29
- STL.AO-2020.05.07-WG1-CR-0000-DSS-v01 |
-| 2020.06.30 | 03.00.06 | Addition of CR:
- INT-2020.05.01-WG1-D-CR-NSSI-Rsrc-Opt-UC
Editorial updates for this CR and mMIMO use case |
-| 2020.06.30 | 03.00.07 | Addition of CR:
- ORAN-WG1 UseCasesAnalysisReport_CR_Local Positioning in RAN-CMCC-v2
Editorial updates for this CR |
-| 2020.07.01 | 03.00.08 | Addition of CR:
- INT-2020.06.30-WG1-D-CR-UseCasesAnalysisReport_MultiAccess_UC_v1 |
-| 2020.07.07 | 03.00.09 | Minor updates to section 3.10.3.1 to align the text description with the figure |
-| 2020.07.15 | 03.00.10 | Updates based on WG1 review comments (mainly editorial, correction of O1/O2 for RAN sharing use case, minor updates to Multi-vendor Slices use case including updated figure 3.10.3-3) |
-| 2020.07.16 | 03.00.11 | Getting the version ready to be published externally (removal of track changes/comments) |
-| 2020.07.16 | 03.00 | Final version 03.00 |
-| 2020.10.17 | 04.00.01 | Initial version of v4.0
Document version number update to v04.00.01 |
-| 2020.10.18 | 04.00.02 | Addition of CR:
- SAM.AO-2020.09.24-WG1-CR-0001-SU-MIMO and MU-MIMO_TM_prediction-v0.2 |
-| 2020.10.22 | 04.00.03 | Addition of CR:
- ATT-2020.08.13-WG1(UCTG)-Signaling_Storm_Protection_v1.03 |
-| 2020.10.28 | 04.00.04 | Addition of CR:
- SAM-2020.09.29-WG1(UCTG)-CR-0001-CongestionPredictionManagement-v01 |
-| 2020.11.01 | 04.00.05 | Addition of CR: |
-
-| | | |
-|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | - CTC-2020.09.23-WG1(UCTG)-UseCaseAnalysisReport_IIoT_Optimization_v03
Editorial updates, corrections |
-| 2020.11.02 | 04.00.06 | Updated Massive MIMO SU/MU-MIMO Optimization use case to remove the similar/redundant text in solution 2 |
-| 2020.11.02 | 04.00 | Final version 04.00 |
-| 2021.02.28 | 05.00.01 | Initial version of v5.0
Document version number update to v05.00.01 |
-| 2021.02.28 | 05.00.02 | Addition of CR:
- ATT-2020.10.07-WG1-CR-0001-Use Case Analysis Report BBU Pooling-v03 |
-| 2021.03.07 | 05.00.03 | Addition of CR:
- SAM.AO-2021.03.04-WG1-CR-0001-Naming-Change for Massive_MIMO_SU_MU-MIMO_Optimization |
-| 2021.03.07 | 05.00.04 | Addition of CR:
- NOK-2021.03.03-ORAN-CR-0001-UseCaseAnalysisReport_mMIMO_BF_Optimization |
-| 2021.03.13 | 05.00 | Final version 05.00 |
-| 2021.07.10 | 06.00.01 | Initial version of v6.0
Document version number update to v06.00.01 |
-| 2021.07.11 | 06.00.02 | Addition of CR:
- TEA-2021.02.24-WG1-CR-0001-Use-Case-Analysis-Report-QOE-Optimization-v03.1 |
-| 2021.07.19 | 06.00 | Final version 06.00 |
-| 2021.11.11 | 07.00.01 | Initial version of v7.0
Document version number update to v07.00.01 |
-| 2021.11.12 | 07.00.02 | Addition of relevant parts of CR:
- NC.AO-2021.07.20-WG1-CR-0001-NSSIResourceAllocationWithQuota-v04 |
-| 2021.11.12 | 07.00.03 | Correction of terminology used in NSSI optimization use case |
-| 2021.11.13 | 07.00.04 | Addition of relevant parts of CR:
- JIO-2021.10.21-ORAN-CR-0001-UseCasesAnalysisReport_ISRM-v02
Updates to this use case with additional comments from NC |
-| 2021.11.14 | 07.00.05 | Clean version for WG1 approval |
-| 2021.11.23 | 07.00.06 | Updates to address WG1 review comments, merge of minor updates to use case 19 "Integrated SON Function" per the review process |
-| 2021.11.23 | 07.00 | Final version 07.00 |
-| 2022.03.27 | 07.00.07 | Adopted new spec revision numbering per O-RAN Work Procedures
Initial version towards v08.00, starting with v07.00.07 per new revision numbering |
-| 2022.03.27 | 07.00.08 | Addition of CR:
- CIS-2022.01.09-WG1-C-UseCaseAnalysisReport-Shared ORU-v03 |
-| 2022.03.27 | 07.00.09 | Addition of CR:
- ORA.AO-2022.02.23-WG1-C-UseCaseAnalysisReport-Energy Saving-v02 |
-| 2022.03.27 | 07.00.10 | Addition of CR:
- CMCC-2022.1.13-WG1-CR-0001-UseCasesAnalysisReport-QOE-Optimization-v1.0 |
-| 2022.03.27 | 07.00.11 | Addition of CR:
- JNPR-2022.03.18-WG1-CR-0006-Scope-Correction-Of-Use-Case-Analysis-Report-v01 |
-
-| | | |
-|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 2022.03.27 | 07.00.12 | Changes accepted from v07.00.11
Baseline for WG1 approval |
-| 2022.04.04 | 07.00.13 | Addressing WG1 comments |
-| 2022.04.04 | 07.00.14 | All changes accepted from v07.00.13
Clean version for TSC approval |
-| 2022.04.04 | 08.00 | Final version 08.00 |
-| 2022.07.24 | 08.00.01 | Initial version towards v09.00, starting with v08.00.01 per O-RAN specification revision numbering process |
-| 2022.07.25 | 08.00.02 | Addition of CR:
- COT.AO-2022.02.09-WG1-CR-0001-UseCaseAnalysisReport-MU-MIMO-Optimization-v04 |
-| 2022.07.25 | 08.00.03 | Addition of CR:
- KDDI.AO-2022.04.21-WG1-CR-0000-UseCaseAnalysisReport-Shared_ORU_Ph2-v01
Per UCTG Shared O-RU subgroup discussions, updating use case #20 from “Lower Layer Multi Node Support” to “Shared O-RU” for consistency with the O-RAN Shared O-RU feature |
-| 2022.07.25 | 08.00.04 | Update of the document to comply with the new O-RAN Technical Spec template |
-| 2022.07.25 | 08.00.05 | All changes accepted, clean version for WG1 approval |
-| 2022.08.01 | 09.00 | Final version 09.00 |
-| 2022.11.10 | 09.00.01 | Initial version towards v10.00 starting with v09.00.01 per O-RAN specification revision numbering process
Addition of CR:
- ATT.AO-2022.05.11-ORAN-CR-0001- UseCaseAnalysisReport_CoreDataSharing - Rev 7 |
-| 2022.11.13 | 09.00.02 | Added O-RAN Release “R003” to document name, updated copyright to 2023 as the document will be published externally in 2023.
All changes accepted, clean version for WG1 approval |
-| 2022.11.18 | 10.00 | Final version 10.00 |
-| 2023.03.16 | 10.00.01 | Initial version towards v11.00, starting with v10.00.01 per O-RAN specification revision numbering process.
Update of the spec to latest O-RAN TS template except for splitting the references to formative and informative. This split is planned to be made in next release of the document |
-| 2023.03.16 | 10.00.02 | Addition of CR:
- CMCC-2022.12.15-WG1-CR-0002-UseCasesAnalysisReport-industrial vision-v5 |
-| 2023.03.16 | 10.00.03 | All changes accepted, clean version for WG1 approval |
-| 2023.03.24 | 10.00.04 | WG1 review comments are addressed, and approval is completed. Ready for TSC approval and publication. |
-| 2023.03.24 | 11.00 | Final version 11.00 |
-| 2023.05.04 | 11.00.01 | Initial version towards v12.00, starting with v11.00.01 per O-RAN specification revision numbering process.
Addition of CR:
- JNPR-2023.05.02-WG1-CR-0010-O-RAN-Use-Cases-Analysis-Report-ODR-References-Section-v01 |
-
-| | | |
-|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 2023.05.04 | 11.00.02 | Addition of CR:
- - JNPR-2023.05.02-WG1-CR-0011-O-RAN-Use-Cases-Analysis-Report-ODR-References-Section-v01
|
-| 2023.05.16 | 11.00.03 | Addition of CRs:
- - JNPR-2023.05.16-WG1-CR-0018-O-RAN-Use-Cases-Analysis-Report-References-Update-v01
- - JNPR-2023.05.16-WG1-CR-0019-O-RAN-Use-Cases-Analysis-Report-References-Correction-v01
|
-| 2023.06.06 | 11.00.04 | Addition of CR:
- - JNPR-2023.05.29-WG1-CR-0026-O-RAN-Use-Cases-Analysis-Report-ODR-Figures-References_Wording_Corrections-v01
|
-| 2023.06.12 | 11.00.05 | Addition of CR:
- - JNPR-2023.06.12-WG1-CR-0029-O-RAN-Use-Cases-Analysis-Report-ODR-References-Section-v01
|
-| 2023.06.12 | 11.00.06 | Addition of CR:
- - JNPR-2023.06.12-WG1-CR-0030-O-RAN-Use-Cases-Analysis-Report-ODR-References-Update-v01
|
-| 2023.06.13 | 11.00.07 | Addition of CR:
- - JNPR-2023.06.13-WG1-CR-0031-O-RAN-Use-Cases-Analysis-Report-ODR-Notes-v01
|
-| 2023.06.27 | 11.00.08 | Addition of CR:
- - JNPR-2023.06.27-WG1-CR-0035-O-RAN-Use-Cases-Analysis-Report-ODR-Modal-Verbs_Shall_Shall_not_Should_Should_not_Must_Must_not-v01
|
-| 2023.06.28 | 11.00.09 | Addition of CR:
- - JNPR-2023.06.28-WG1-CR-0037-O-RAN-Use-Cases-Analysis-Report-ODR-Modal-Verbs_Can_Cannot_May_Need_not-v01
|
-| 2023.07.19 | 11.00.10 | Addition of CR:
- - MITRE-2023-07-07-WG1-CR-0001-UseCaseAnalysisReport-RAN-Sharing-Via-Midhaul-v10
|
-| 2023.07.19 | 11.00.11 | Addition of CR:
- - ERI-2023.05.04-WG1-CR-0053-UseCasesAnalysisReport-UseCase23-new-option-v01
|
-| 2023.07.20 | 11.00.12 | - - Update of the spec to latest O-RAN TS template
- - Correction of font types and spacing across the spec per ODR requirements
- - Editorial corrections
|
-| 2023.07.20 | 11.00.13 | Clean version for WG1 approval |
-| 2023.07.27 | 11.00.14 | WG1 review comments are addressed, and approval is completed. |
-| 2023.07.27 | 11.00.15 | All changes accepted, clean version. |
-| 2023.07.27 | 12.00 | Final version 12.00 |
-| 2023.11.06 | 12.00.01 | Initial version towards v13.00, starting with v12.00.01 per O-RAN specification revision numbering process.
Addition of CR: |
-
-| | | |
-|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | - - CMCC-2022.04.20-WG1-CR-0003-UseCasesAnalysisReport-Interference-Optimization-v06
|
-| 2023.11.06 | 12.00.02 | Addition of CR: - - KDDI.AO-2023.10.11-WG1-CR-0003-AnalysisReport-Interference-Optimization-v02
|
-| 2023.11.06 | 12.00.03 | Clean version for WG1 approval |
-| 2023.11.16 | 12.00.04 | WG1 review comments are addressed, and approval is completed. |
-| 2023.11.16 | 12.00.05 | All changes accepted, clean version. |
-| 2023.11.16 | 13.00 | Final version 13.00 |
-| 2023.11.22 | 13.00.01 | Initial version towards v14.00, starting with v13.00.01 per O-RAN specification revision numbering process.
Addition of CR: - - JNPR-2023.11.22-WG1-CR-0046-O-RAN-Use-Cases-Analysis-Report-ODR-FFS-Concepts-v01
|
-| 2024.02.26 | 13.00.02 | Addition of CRs: - - JNPR-2024.01.16-WG1-CR-0050-O-RAN-Use-Cases-Analysis-Report-ODR-Clauses-v01
- - JNPR-2024.01.16-WG1-CR-0052-O-RAN-Use-Cases-Analysis-Report-ODR-Figures-Numbering_Capital_Letters_Editorial_Changes-v01
|
-| 2024.03.21 | 13.00.03 | Clean version for WG1 approval |
-| 2024.03.31 | 13.00.04 | WG1 review comments are addressed, and approval is completed. |
-| 2024.03.31 | 13.00.05 | All changes accepted, clean version. |
-| 2024.03.31 | 14.00 | Final version 14.00 |
-| 2024.06.20 | 14.00.01 | Initial version towards v15.00, starting with v14.00.01 per O-RAN specification revision numbering process.
Addition of CR: - - JNPR-2024.05.10-WG1-CR-0055-O-RAN-Use-Cases-Analysis-Report-ODR-Capital_Letters-Editorial_Changes-Fixes-v02
|
-| 2024.06.20 | 14.00.02 | Addition of CR: - - MTR.AO-2024.04.18-WG1UCTG-CR0001-Use Case 26-public release -r7
|
-| 2024.06.28 | 14.00.03 | Addition of CRs: - - JNPR-2024.06.03-WG1-CR-0057-O-RAN-Use-Cases-Analysis-Report-ODR-References-v01.docx
- - JNPR-2024.06.04-WG1-CR-0058-O-RAN-Use-Cases-Analysis-Report-ODR-Footnotes-v01
|
-| 2024.07.05 | 14.00.04 | Clean version for WG1 approval |
-| 2024.07.18 | 14.00.05 | WG1 review comments are addressed, and approval is completed. |
-| 2024.07.18 | 14.00.06 | All changes accepted, clean version. |
-| 2024.07.18 | 15.00 | Final version 15.00 |
-| 2024.09.09 | 15.00.01 | Initial version towards v16.00, starting with v15.00.01 per O-RAN specification revision numbering process. |
-
-| | | |
-|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | Addition of CRs: - - CMCC-2024.06.06-WG1-UCTG-CR-0026-UseCasesAnalysisReport-Use Case 26-Interference-Prediction_v2
- - JNPR-2024.08.05-WG1-CR-0060-O-RAN-Use-Cases-Analysis-Report-ODR-References-Editorial_Change-v01
|
-| 2024.11.04 | 15.00.02 | Addition of CRs: - - JNPR-2024.10.14-WG1-CR-0066-O-RAN-Use-Cases-Analysis-Report-ETSI_PAS_Comments-v01
- - JNPR-2024.10.18-WG1-CR-0067-O-RAN-Use-Cases-Analysis-Report-ETSI_PAS_Comments-v02
- - JNPR-2024.10.22-WG1-CR-0068-O-RAN-Use-Cases-Analysis-Report-ETSI_PAS_Comments-v01
- - JNPR-2024.10.22-WG1-CR-0069-O-RAN-Use-Cases-Analysis-Report-ETSI_PAS_Comments-v02
- - DTAG-2024.09.24-WG1-CR-0004-Use case numbering-v03
|
-| 2024.11.15 | 15.00.03 | Updated copyright statement on the cover page and footer to 2025
Editorial changes to align to O-RAN TR template v02.01
Added 3GPP Release 18 related text to Informative References clause |
-| 2024.11.21 | 15.00.04 | Clean version for WG1 approval |
-| 2024.12.06 | 15.00.05 | WG1 review comments are addressed, and approval is completed. |
-| 2024.12.06 | 15.00.06 | All changes accepted, clean version. |
-| 2024.12.06 | 16.00 | Final version 16.00 |
-| 2025.01.13 | 16.00.01 | Initial version towards v17.00, starting with v16.00.01 per O-RAN specification revision numbering process.
Addition of CRs: - - JNPR-2024.12.10-WG1-CR-0087-O-RAN-Use-Cases-Analysis-Report-ETSI_PAS_Comments-v01
- - JNPR-2024.12.10-WG1-CR-0088-O-RAN-Use-Cases-Analysis-Report-ETSI_PAS_Comments-v01
|
-| 2025.02.21 | 16.00.02 | Addition of CR: - - MTR.AO-2024.12.09-WG1-CR0004-UCTG-Interference Classification-v2
|
-| 2025.02.25 | 16.00.03 | Addition of CRs: - - JNPR-2025.02.13-WG1-CR-0092-O-RAN-Use-Cases-Analysis-Report-Rel-18-Upgrade-v01
- - JNPR-2025.02.13-WG1-CR-0093-O-RAN-Use-Cases-Analysis-Report-Rel-18-Upgrade-26.247-v01
- - JNPR-2025.02.13-WG1-CR-0094-O-RAN-Use-Cases-Analysis-Report-Rel-18-Upgrade-28.552-v01
- - JNPR-2025.02.13-WG1-CR-0095-O-RAN-Use-Cases-Analysis-Report-Rel-18-Upgrade-38.331-v01
- - JNPR-2025.02.13-WG1-CR-0096-O-RAN-Use-Cases-Analysis-Report-Voiding-Unused-References-v01
|
-
-| | | |
-|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| | | - JNPR-2025.02.13-WG1-CR-0097-O-RAN-Use-Cases-Analysis-Report-Reference-Correction-Editorial-Correction-v01 |
-| 2025.03.20 | 16.00.04 | Editorial updates to align to O-RAN TR template v03.00 |
-| 2025.03.20 | 16.00.05 | Clean version for WG1 approval |
-| 2025.03.28 | 17.00 | Final version 17.00 |
-| 2025.06.19 | 17.00.01 | Initial version towards v18.00, starting with v17.00.01 per O-RAN specification revision numbering process.
Addition of CR:
- CMCC-2025.02.10-WG1-CR-0032-O-RAN-Use-Cases-Analysis-Report-CCIN-v02 |
-| 2025.07.08 | 17.00.02 | Editorial updates to align to O-RAN TR template v05 |
-| 2025.07.09 | 17.00.03 | Clean version for WG1 approval |
-| 2025.07.18 | 18.00 | Final version 18.00 |
-| 2025.10.15 | 18.00.01 | Initial version towards v19.00, starting with v18.00.01 per O-RAN specification revision numbering process.
Addition of CRs:
- RMI.AO-2025.08.05-WG1-UCTG-UCAR-CR-0035-NES-External_Power_Source_Coordination_based_ES-v01
- RMI.AO-2025.08.06-WG1-UCTG-UCAR-CR-0039-NES-PA_Power_Optimization_based_ES-v01 |
-| 2025.11.21 | 18.00.02 | Addition of clause 4.28 with void content as placeholder for RAN intent-driven management services use case |
-| 2025.11.21 | 18.00.03 | Clean version for WG1 approval |
-| 2025.12.02 | 18.00.04 | WG1 review comments are addressed, and approval is completed. |
-| 2025.12.02 | 18.00.05 | All changes accepted, clean version. |
-| 2025.12.02 | 19.00 | Final version 19.00 |
\ No newline at end of file
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/01832e59ebad7ada5e790de6f90cc9b6_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/01832e59ebad7ada5e790de6f90cc9b6_img.jpg
deleted file mode 100644
index 9eea8151e986b0ff241ea3e4d5bcff4552da6dc7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/01832e59ebad7ada5e790de6f90cc9b6_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4973b5355e9cd51abb51c52e59c5e9f288d1d5bde5af9bc00a3a09762cabe62f
-size 45312
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg
deleted file mode 100644
index 38b472b6cddf14d84f812d31de3ac3f62520e719..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:80d6bc9a65ada99dd8de375ccc68849d617f1d8a250d945ca2ceb49a48ce422d
-size 60526
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/0c80c383f76034e117adf5e5eaadaaf3_img.jpg
deleted file mode 100644
index cbfc89baef0e9705f29fbdcecc77ef871381c7df..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/0c80c383f76034e117adf5e5eaadaaf3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:34ff3c37d6f68e053d391f0acb6d127b37adca91354085a6f7e1ef4f05076d22
-size 50782
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/1baaba7a6e54e77197475726c871067d_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/1baaba7a6e54e77197475726c871067d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/22af211207188ebc64d7b60ca052b367_img.jpg
deleted file mode 100644
index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/22af211207188ebc64d7b60ca052b367_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:961edf29d7101c36a5633a34cb07127ddc8d42543983c969931296b3e82c0b66
-size 4449
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/24ca460ee3381aee781887e9e586ec67_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/24ca460ee3381aee781887e9e586ec67_img.jpg
deleted file mode 100644
index 05cd7f6ce9498607e88e778fe5ab024485b6aa5a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/24ca460ee3381aee781887e9e586ec67_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:5f88713ad731a62830a51ab63dae13343a39258415812d25f30ffd0ef13dfad4
-size 68099
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg
deleted file mode 100644
index 718aef5cb47ff5f5fec0695f4c6ccdacd23e376c..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:62a1d26e29a2923e500aaa5cb35aa9c8e02b8c870ffd17ad086c7feb9c93271f
-size 77104
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/2b60ebe01f77d22e53da1fbe73083b01_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/2b60ebe01f77d22e53da1fbe73083b01_img.jpg
deleted file mode 100644
index 1aaa4c5658b6aa977e61ff80804392d454fd668d..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/2b60ebe01f77d22e53da1fbe73083b01_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:5af430873cad8afa40f981466de676c10903d3719c00ca897d98ff0845318fa3
-size 83821
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg
deleted file mode 100644
index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:961edf29d7101c36a5633a34cb07127ddc8d42543983c969931296b3e82c0b66
-size 4449
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/318db222fae24a59c370fa6471d541b8_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/318db222fae24a59c370fa6471d541b8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/318f02285df33c4d38cdad30845972d4_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/318f02285df33c4d38cdad30845972d4_img.jpg
deleted file mode 100644
index d49616ede946fc35b1d4592a23c31cd75b761288..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/318f02285df33c4d38cdad30845972d4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ca94c84bab573ac5f4f511db27a92e47e352c33c3614ac5929f58c4c7c9b69a1
-size 25487
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg
deleted file mode 100644
index be03423ed1be86867bb70399e5e338c0f003b187..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:49692a24147551b600007be1413ad42660de6c97b8cc1b9082bbf0d1986a7b81
-size 68303
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg
deleted file mode 100644
index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:961edf29d7101c36a5633a34cb07127ddc8d42543983c969931296b3e82c0b66
-size 4449
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/37806e0fc150d857046ebc7e47893d7a_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/37806e0fc150d857046ebc7e47893d7a_img.jpg
deleted file mode 100644
index 2791ad6f1fef92f20f30fac0fede5183d41c26e8..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/37806e0fc150d857046ebc7e47893d7a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:9735b98a233925b27b8f3a51ab66898a523c296ef3f0fd7fb3e20b35b85652fd
-size 90612
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
deleted file mode 100644
index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:aab4538d061e8739f2dc9287f6e83ada04877c38622954edf19ae981273b0c90
-size 4494
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/3c99312f83459559d9a301148555d7b9_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/3c99312f83459559d9a301148555d7b9_img.jpg
deleted file mode 100644
index 7199e65cf298b04df007d77fc481078c51200a2c..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/3c99312f83459559d9a301148555d7b9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:9816374cef26fec7228b157663a58d2cd2c851ec07ff8510f858c83db56abc4e
-size 81130
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/3ce04f1c7128814978c6b34d654a25cc_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/3ce04f1c7128814978c6b34d654a25cc_img.jpg
deleted file mode 100644
index b466c706c3e38726705a0e9918e2aade72c900f0..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/3ce04f1c7128814978c6b34d654a25cc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:cf7a26fc6ccbb75848d68a4276aeebafd0f554a4c2a13ddf9a747fcb0cfbfc8c
-size 101572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg
deleted file mode 100644
index 887e190263e4d3a4a7c7e8c41e4def42d05de025..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:300a50c13b915ff54d5d8ab45ec0155be9061a37f8d19c46f1c3ea4f93390b1d
-size 98975
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4356776ca004ecba5d599667a155d7d4_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4356776ca004ecba5d599667a155d7d4_img.jpg
deleted file mode 100644
index b0dd021b1b380eae1c35a6be164b5eca7ffc867d..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4356776ca004ecba5d599667a155d7d4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:df6e657095e4fc17e37a51d0235b65a153cbf80928c6c229b023bbb46f48fccf
-size 94168
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg
deleted file mode 100644
index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:aab4538d061e8739f2dc9287f6e83ada04877c38622954edf19ae981273b0c90
-size 4494
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4a04896dfb569893fba50729314024f5_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4a04896dfb569893fba50729314024f5_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg
deleted file mode 100644
index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c797d9c161d9841238b9a350aa163fd2ec3524d0888718c851c106caa935addf
-size 4546
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
deleted file mode 100644
index 71ef8dcb9a0411db26165fc339f40c8fdcca3db0..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:6d6e59bf0d9aa5088289bcb8bf992fbe1727e7433ee668a7a1ca5476d422837f
-size 57369
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5009e30a55479d3941af523871208f9d_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5009e30a55479d3941af523871208f9d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg
deleted file mode 100644
index a8ab0495ccd15517eb64a85ae2cd1849d49c5bbc..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:b74563517f4d1406c30ff353be7ac4c0c5b2e1ba840cc6cfcc37b9aa1e2cd198
-size 24394
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg
deleted file mode 100644
index 9e5241224c7894ac2d10062a5129ca1ac93ff45d..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:897a38b1582a3186d2c03f78f003ea4c62824ded67ed653c848d5f830410762e
-size 138137
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5445597cceefaca1ac89e710fe339325_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5445597cceefaca1ac89e710fe339325_img.jpg
deleted file mode 100644
index 2d6d8220e44423d87486c53d6243fbf25f037b77..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5445597cceefaca1ac89e710fe339325_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:8ce7d7d20f680cf813531459cd72571324d82be9e306bc8d5aaba7fe3aa08375
-size 22248
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/59368942873b0c35eef79a7a985025dc_img.jpg
deleted file mode 100644
index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/59368942873b0c35eef79a7a985025dc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:aab4538d061e8739f2dc9287f6e83ada04877c38622954edf19ae981273b0c90
-size 4494
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg
deleted file mode 100644
index eb0409eb02efc6dde62be613dd3d8a448870d1a1..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:78ecc2b29aac102405938945e04ed971b822dbdab7afc0be78558922d3666f1c
-size 35239
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg
deleted file mode 100644
index 3082149b824ef06fe421cbfe4fcbfc83a5f08d3e..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3485e7be84727e4987e256c2dc112659e175a7ba92cc4866142d0c7c99c665e6
-size 67469
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg
deleted file mode 100644
index 4bd6736610fc3217eb8fcb5591f023841d0853ef..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:d6893628fbed31715898029e7b7624ffd558b9c826d2fd80c1f43654cb1c968c
-size 62785
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/6d2057d7e401741861ca63545a5d7d3b_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/6d2057d7e401741861ca63545a5d7d3b_img.jpg
deleted file mode 100644
index 75ffde559a9a6711a86416c83e878631fb983d7e..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/6d2057d7e401741861ca63545a5d7d3b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:fc888ddd156380d1e7057d3b30616b31523dbd5fd3df9042c9ae1559d7a06ad5
-size 69154
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg
deleted file mode 100644
index 986363f075eab27a8bb34168c80eaffc7770f67d..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:8fa12fd2cc7bee996360a02809feac57a2fe774a3fb4a65d2a455f70878fc6eb
-size 43746
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/742a5484e7dd016256ab99921bbd635d_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/742a5484e7dd016256ab99921bbd635d_img.jpg
deleted file mode 100644
index e48a38228aeb2a1992d4541b5bcdb48a663832ea..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/742a5484e7dd016256ab99921bbd635d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:68767701f6982818d5dd2ec2eee516e07eda7b6e99cf4808e7d68d05bb4b4561
-size 132002
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
deleted file mode 100644
index 7a8ed849997ecaa0ba9089ec2e7500b5ac46d028..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ab9d6492d9fd7e1013ce282d93fc78feb87aa33ac956e4c9b7a5696c49f47944
-size 35321
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
deleted file mode 100644
index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:aab4538d061e8739f2dc9287f6e83ada04877c38622954edf19ae981273b0c90
-size 4494
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8269648391c59363ea61243864a2adf7_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8269648391c59363ea61243864a2adf7_img.jpg
deleted file mode 100644
index 47dbddea5edd5421f5f73aaf298c503152590d14..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8269648391c59363ea61243864a2adf7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:21eedaa27dd513a44234036c20dd22e0709113ae6a53c23c72f1a9ddc8f116d1
-size 20583
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8307f6b04df072c9332f9987e034272c_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8307f6b04df072c9332f9987e034272c_img.jpg
deleted file mode 100644
index 21642561aac318753ccf51a3fe9a545cf1ca4d1a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8307f6b04df072c9332f9987e034272c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ffc4010efb0fde152412b8b2770f7810f568af3080a78990f2711ea932a07d64
-size 55948
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg
deleted file mode 100644
index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:aab4538d061e8739f2dc9287f6e83ada04877c38622954edf19ae981273b0c90
-size 4494
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/854df8ad60507803253274673f9062cf_img.jpg
deleted file mode 100644
index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/854df8ad60507803253274673f9062cf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c40dd0ad8bd0fafe07b620344f686375583942d8a34dd2fc56931f6f8824ee5c
-size 4504
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8658cfab6a458b4a80ab2e384c61ff89_img.jpg
deleted file mode 100644
index 61c9d3de203bfe8d5e2462d7528a6e38b1b8f99f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8658cfab6a458b4a80ab2e384c61ff89_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:78c759d5a5e2b29d8bfc02859edfbdace1d2c9f0d246c93b393191bf7eb01f42
-size 38814
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8b4befaffc5166da571069410e207aea_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8b4befaffc5166da571069410e207aea_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg
deleted file mode 100644
index 947044d8b6813cda7c33cdb51f8e3604b5585afb..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:7ea6073fe48a3967a15cdf8c7929f1d0c115c7b1f937c190c9be142fef7cedf5
-size 27361
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
deleted file mode 100644
index fdf1962c5e5756ecbf960269e7811edc51f4a3bd..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e24fd323223bd983a476c2ecb51c7207e06c8a77d51903c83df6681cfab919e9
-size 85391
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg
deleted file mode 100644
index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c797d9c161d9841238b9a350aa163fd2ec3524d0888718c851c106caa935addf
-size 4546
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/90183a52275501da5a0fd5c63d837009_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/90183a52275501da5a0fd5c63d837009_img.jpg
deleted file mode 100644
index e492d813b3e276dc6dfc4cb07752dda9d3c3ee52..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/90183a52275501da5a0fd5c63d837009_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:10d6acab1b5f95096e7dfa5a4869047c64b72e385cdefba1dae494f9311a0435
-size 70703
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg
deleted file mode 100644
index 072f3195e5a1c3d76b064d2a91f05a7f0d6c2fa8..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:3153b3fa7c370f2ea8c2bb6b711100deb44f3bd6c5fbcbf113db6c02d35f670d
-size 44292
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9156549264d36ead617a1dec7987f970_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9156549264d36ead617a1dec7987f970_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg
deleted file mode 100644
index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c797d9c161d9841238b9a350aa163fd2ec3524d0888718c851c106caa935addf
-size 4546
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg
deleted file mode 100644
index 1b5b9821e5adee9ba34400d908cb34d3bb2d1192..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:cd10ce48d51298da0abcd1ec5490361be4229e1466c52763d301db48d41ce994
-size 84887
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
deleted file mode 100644
index 07dcb2a0e8c079ac758e1638f93c756f5ddbd950..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:0dfd60a3e024f1736fd2db42c4ee9f47d64a27ab72221b1039e38c5d83bcd60f
-size 52337
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg
deleted file mode 100644
index c00f2ee410653c4f4db9d695c039abca984f49e3..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:7247560934db0028719a5c95686453ed182554289e0c4cb95d842295cc7d03a6
-size 34519
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg
deleted file mode 100644
index 1f5fe258e896ab3d2f5545d5f53fb94193d8070e..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e0b70058e1ee287f870e19bb2fb8bff920a45a7786e42d6bc7384040908f0940
-size 20269
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg
deleted file mode 100644
index 5ec5aa10ee34f0a612bd2ab7ce0b1c5f58f1db01..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4849057ed690b3e10396a323c92c9765bd3b27b6604761f264972f2019ba1fac
-size 17275
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg
deleted file mode 100644
index 4644c4ec42d678dc5b95da06db15ce344082714e..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:62423f5e5266f430e801e2e8e69e432a5bf9b8691b2fdfdc9f156313de8c397d
-size 73265
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg
deleted file mode 100644
index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c40dd0ad8bd0fafe07b620344f686375583942d8a34dd2fc56931f6f8824ee5c
-size 4504
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg
deleted file mode 100644
index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c797d9c161d9841238b9a350aa163fd2ec3524d0888718c851c106caa935addf
-size 4546
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg
deleted file mode 100644
index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c797d9c161d9841238b9a350aa163fd2ec3524d0888718c851c106caa935addf
-size 4546
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg
deleted file mode 100644
index 93590778a61a8b231084ed11a8b3b3674272ab20..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:8fa6d35001df10d9c6867e07f288798ac5ea439f16efbdeeecc64f81d68f88a7
-size 113241
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b1e7bb95fa1587d870de03df02477df4_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b1e7bb95fa1587d870de03df02477df4_img.jpg
deleted file mode 100644
index da4c4d4cc7fc74302776d3ccb6a0319c7909e133..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b1e7bb95fa1587d870de03df02477df4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:be2676950603c1367c4b3dad8ed3fcb2f05908b207fbcd22591b1e7378c6a021
-size 33110
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b2f5606b9c7184c1c6070a290080a3e3_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b2f5606b9c7184c1c6070a290080a3e3_img.jpg
deleted file mode 100644
index 471a06f9f66f347fde8ac396a1d6da2f4a746720..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b2f5606b9c7184c1c6070a290080a3e3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:83076530f0b661790d67e3ed84e63817dc403a994764796d584342e1ead5eecd
-size 33433
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b35ea3e304aad7d350a9902270413930_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b35ea3e304aad7d350a9902270413930_img.jpg
deleted file mode 100644
index c4f6917352f24979f24f93cae3a3d539007803bb..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b35ea3e304aad7d350a9902270413930_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:82113b7b1e3a6fb6a914c87b73595be38148da6a0325530e8d5411c867c0b7c0
-size 66246
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b5335262987c819d7f71ce40f99cb71b_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b5335262987c819d7f71ce40f99cb71b_img.jpg
deleted file mode 100644
index 304b32a66566f4be6d0137457220356b22c59aef..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/b5335262987c819d7f71ce40f99cb71b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:fd876246b2e52b8ec737dddb5fc48c74e494ca5fb3741187bed0cbff7f03ef6c
-size 68211
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/bb3063a33c89b248574f64b6d8dfc404_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/bb3063a33c89b248574f64b6d8dfc404_img.jpg
deleted file mode 100644
index 7cc89bb9e36f242debb57add4f61b161601641bd..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/bb3063a33c89b248574f64b6d8dfc404_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:f1025c4d36d95332ce37819a90f0ff382122ad1f4eb71cee3c86b4807f4cab88
-size 53138
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
deleted file mode 100644
index 83952ea0fda54a2b940c2719d0ae68d1c4e3943b..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:732119adba6c2249a3b3b17c2cb91d4f385e36099b4abd55b49d92bc0aed4088
-size 29916
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg
deleted file mode 100644
index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2980e7a8abce05796398f9a86319e5275baa01712b04436486f0cded3df672b7
-size 4549
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg
deleted file mode 100644
index bfb3802673ddf4aefbcb049bf702d65acc5bf5d0..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4b2df480b5fd5806d6d11a3378d04436f31b78fc0e19a68f566c46fd27545074
-size 71127
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg
deleted file mode 100644
index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c40dd0ad8bd0fafe07b620344f686375583942d8a34dd2fc56931f6f8824ee5c
-size 4504
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg
deleted file mode 100644
index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c40dd0ad8bd0fafe07b620344f686375583942d8a34dd2fc56931f6f8824ee5c
-size 4504
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg
deleted file mode 100644
index af123d217797b07794cd3c6caff958058eb552a0..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:484984828b0a048c76cdefcdc22c26dc081872cf68261bfa9cc5e841f7a0950e
-size 48753
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/dcf83796ccf494110638fbd4677b931d_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/dcf83796ccf494110638fbd4677b931d_img.jpg
deleted file mode 100644
index 503843d47570375a511daea7339d72295c865e55..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/dcf83796ccf494110638fbd4677b931d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:fa810ed72b0447327400d3869b6fa9a160c9807277fe92fe5e8710286a32318a
-size 63311
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e05122559f56af5699789b7118d8fe87_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e05122559f56af5699789b7118d8fe87_img.jpg
deleted file mode 100644
index 180a44c2684d8f602fa4898f660ef3f5c4912bdd..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e05122559f56af5699789b7118d8fe87_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:09ba3570a68f4f9f294ce0f5c2746c989643740286bb68c0c6ffcc43136f41fe
-size 19933
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg
deleted file mode 100644
index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:aab4538d061e8739f2dc9287f6e83ada04877c38622954edf19ae981273b0c90
-size 4494
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e636d7ccca0ad14c6b95201404324823_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e636d7ccca0ad14c6b95201404324823_img.jpg
deleted file mode 100644
index 6a3dd69cef90278eaad7ccc226b8d3810dcb42e2..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e636d7ccca0ad14c6b95201404324823_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:f2bc307215c12eff37a250625a285db77165edb774b7925be67b11184d3a12af
-size 28461
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e9b43ac020435f8121e8592f31afdc52_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e9b43ac020435f8121e8592f31afdc52_img.jpg
deleted file mode 100644
index 6f797f9c99a8f3f076d782cdadcc101088ee9790..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/e9b43ac020435f8121e8592f31afdc52_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2b0693be8a90d3a58e5e79129912a444d113cd9f1bb081545312f38887666207
-size 113723
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
deleted file mode 100644
index c03d7cab95ecabb83240815b821f4f94445aa96a..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ba58c1d10dfb31827788e8199ad8bf87d2aaca2921e88bf70b26fd142c0fa81e
-size 24074
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg
deleted file mode 100644
index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2980e7a8abce05796398f9a86319e5275baa01712b04436486f0cded3df672b7
-size 4549
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg
deleted file mode 100644
index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:765f6f0daf70f4260df1a3e909628a2cef741e50e35616364cec131c683f416f
-size 4464
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
deleted file mode 100644
index 584d07716bd85f6223b7d4faae9916103eb7aaf3..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:bd5b95329f9bf849816b9644516a1de64cb6466a139eac93ad29793bc6020060
-size 4590
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/fed4a04822c24fb22cca3a14f4ddae83_img.jpg
deleted file mode 100644
index f2438fe27246371d7a0ebb6ce11e7723df1cb491..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/fed4a04822c24fb22cca3a14f4ddae83_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:d0d105ee52ecbcf54158190d1a0e096b92eb97805a9e3b7f4b2eeb6db339b011
-size 55204
diff --git a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg
deleted file mode 100644
index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TR.Use-Cases-Analysis-Report-R005-v19.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2cfd318c513021a6ad8ee5bc43cd4e78dd5e062e226d7780e820d35f461665ca
-size 4572
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/doc.md b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/doc.md
deleted file mode 100644
index 89e116e4e27a9761177ca49b00a2f65c8fe8e953..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/doc.md
+++ /dev/null
@@ -1,1119 +0,0 @@
-
-
-# --- **O-RAN Work Group 1 (Use Cases and Overall Architecture)**
-
-## **O-RAN Architecture Description**
-
-Copyright © 2026 by the O-RAN ALLIANCE e.V.
-
-The copying or incorporation into any other work of part or all of the material available in this specification in any form without the prior written permission of O-RAN ALLIANCE e.V. is prohibited, save that you may print or download extracts of the material of this specification for your personal use, or copy the material of this specification for the purpose of sending to individual third parties for their information provided that you acknowledge O-RAN ALLIANCE as the source of the material and that you inform the third party that these conditions apply to them and that they must comply with them.
-
-O-RAN ALLIANCE e.V., Buschkauler Weg 27, 53347 Alfter, Germany
-
-Register of Associations, Bonn VR 11238, VAT ID DE321720189
-
-# Contents
-
-| | |
-|----------------------------------------------------------------------|----|
-| Foreword..... | 4 |
-| Modal verbs terminology ..... | 4 |
-| Introduction ..... | 4 |
-| 1 Scope..... | 5 |
-| 2 References ..... | 5 |
-| 2.1 Normative references ..... | 5 |
-| 2.2 Informative references ..... | 6 |
-| 3 Definition of terms, symbols and abbreviations ..... | 7 |
-| 3.1 Terms ..... | 7 |
-| 3.2 Symbols..... | 9 |
-| 3.3 Abbreviations..... | 9 |
-| 4 General O-RAN architecture principles..... | 12 |
-| 5 O-RAN architecture ..... | 12 |
-| 5.1 Overall architecture of O-RAN..... | 12 |
-| 5.2 O-RAN control loops..... | 14 |
-| 5.3 Description of O-RAN architecture elements..... | 15 |
-| 5.3.1 Service Management and Orchestration framework..... | 15 |
-| 5.3.2 Near-RT RIC..... | 18 |
-| 5.3.3 O-CU-CP..... | 18 |
-| 5.3.4 O-CU-UP..... | 19 |
-| 5.3.5 O-DU..... | 19 |
-| 5.3.6 O-RU..... | 19 |
-| 5.3.7 O-eNB..... | 19 |
-| 5.3.8 O-Cloud..... | 20 |
-| 5.4 Relevant interfaces in O-RAN architecture ..... | 20 |
-| 5.4.1 Introduction to relevant interfaces in O-RAN architecture..... | 20 |
-| 5.4.2 A1 interface ..... | 21 |
-| 5.4.3 O1 interface ..... | 22 |
-| 5.4.4 O2 interface ..... | 22 |
-| 5.4.5 E2 interface ..... | 22 |
-| 5.4.6 O-Cloud Notification interface..... | 22 |
-| 5.4.7 Open Fronthaul interface..... | 22 |
-| 5.4.8 E1 interface ..... | 22 |
-| 5.4.9 F1-c interface..... | 22 |
-| 5.4.10 F1-u interface ..... | 22 |
-| 5.4.11 NG-c interface ..... | 23 |
-| 5.4.12 NG-u interface..... | 23 |
-| 5.4.13 X2-c interface..... | 23 |
-| 5.4.14 X2-u interface..... | 23 |
-| 5.4.15 Xn-c interface..... | 23 |
-| 5.4.16 Xn-u interface..... | 23 |
-| 5.4.17 Uu interface ..... | 23 |
-| 5.4.18 CTI ..... | 23 |
-| 5.4.19 Y1 interface ..... | 23 |
-| 5.4.20 R1 interface ..... | 24 |
-| 5.4.21 Near-RT RIC APIs..... | 24 |
-| 5.4.22 D2 interface ..... | 24 |
-| 5.5 UE associated identifiers used in O-RAN ..... | 24 |
-| 5.6 O-RAN security architecture ..... | 25 |
-| 6 O-RAN Information Model (IM) principles ..... | 26 |
-
-**Annex (informative): Implementation options of O-RAN functions and nework elements..... 26**
-
-A.1 Shared cell..... 26
-
-A.2 FHGW function ..... 27
-
-A.3 Near-RT RIC..... 28
-
-A.4 Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, and O-RU..... 29
-
-A.5 Cooperative transport..... 33
-
-A.6 Inter O-DU Carrier Aggregation (CA) ..... 34
-
-**Annex (informative): Change history ..... 35**
-
-# --- Foreword
-
-This Technical Specification (TS) has been produced by WG1 of the O-RAN ALLIANCE.
-
-The content of the present document is subject to continuing work within O-RAN and may change following formal O-RAN approval. Should the O-RAN ALLIANCE modify the contents of the present document, it will be re-released by O-RAN with an identifying change of version date and an increase in version number as follows:
-
-version xx.yy.zz
-
-where:
-
-- xx: the first digit-group is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have xx=01). Always 2 digits with leading zero if needed.
-- yy: the second digit-group is incremented when editorial only changes have been incorporated in the document. Always 2 digits with leading zero if needed.
-- zz: the third digit-group included only in working versions of the document indicating incremental changes during the editing process. External versions never include the third digit-group. Always 2 digits with leading zero if needed.
-
-## --- Modal verbs terminology
-
-In the present document "**shall**", "**shall not**", "**should**", "**should not**", "**may**", "**need not**", "**will**", "**will not**", "**can**" and "**cannot**" are to be interpreted as described in clause 3.2 of the O-RAN Drafting Rules (Verbal forms for the expression of provisions).
-
-"**must**" and "**must not**" are **NOT** allowed in O-RAN deliverables except when used in direct citation.
-
-# --- Introduction
-
-O-RAN activities are guided by the following objectives as specified in O-RAN Whitepaper [i.5]:
-
-- Leading the industry towards open, interoperable interfaces, RAN virtualization, and big data and AI enabled RAN intelligence.
-- Maximizing the use of common-off-the-shelf hardware and merchant silicon and minimizing proprietary hardware.
-- Specifying APIs and interfaces, driving standards to adopt them as appropriate, and exploring open source where appropriate.
-- The O-RAN Architecture identifies the key functions and interfaces adopted in O-RAN.
-
-# 1 Scope
-
-This Technical Specification has been produced by the O-RAN ALLIANCE.
-
-The present document
-
-- specifies: the overall architecture of O-RAN.
-- describes: the O-RAN architecture elements and relevant interfaces that connect them.
-
-# 2 References
-
-## 2.1 Normative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are necessary for the application of the present document.
-
-- [1] 3GPP TS 23.501: "System Architecture for the 5G System (5GS); Stage 2".
-- [2] 3GPP TS 28.622: "Generic Network Resource Model (NRM); Stage 2".
-- [3] 3GPP TS 32.101: "Technical Specification Group Services and System Aspects; Telecommunication management; Principles and high level requirements".
-- [4] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture Description".
-- [5] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
-- [6] 3GPP TS 36.420: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 general aspects and principles".
-- [7] 3GPP TS 36.423: "LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)".
-- [8] 3GPP TS 38.300 "NR; NR and NG-RAN Overall Description; Stage 2".
-- [9] 3GPP TS 38.331: "5G; NR; Radio Resource Control (RRC); Protocol specification".
-- [10] 3GPP TS 38.401: "NG-RAN; Architecture description".
-- [11] 3GPP TS 38.413: "5G; NG-RAN; NG Application Protocol (NGAP)".
-- [12] 3GPP TS 38.420: "NG-RAN; Xn general aspects and principles".
-- [13] 3GPP TS 38.423: "5G; NG-RAN; Xn Application Protocol (XnAP)".
-- [14] 3GPP TS 38.460: "NG-RAN; E1 general aspects and principles".
-- [15] 3GPP TS 38.463: "5G; NG-RAN; E1 Application Protocol (E1AP)".
-- [16] 3GPP TS 38.470: "NG-RAN; F1 general aspects and principles".
-- [17] 3GPP TS 38.473: "5G; NG-RAN; F1 Application Protocol (F1AP)".
-- [18] O-RAN.WG2.TS.A1GAP: "O-RAN A1 interface: General Aspects and Principles" ("A1GAP").
-
-- [19] O-RAN.WG4.TS.CUS.0: "O-RAN Control, User and Synchronization Plane Specification" ("Open FH CUS-Plane").
-- [20] O-RAN.WG4.CTI-TCP.0: "O-RAN Cooperative Transport Interface; Transport Control Plane Specification" ("CTI Control").
-- [21] O-RAN.WG4.CTI-TMP.0: "O-RAN Cooperative Transport Interface; Transport Management Plane Specification" ("CTI Management").
-- [22] O-RAN.WG3.TS.E2GAP: "O-RAN E2 General Aspects and Principles (E2GAP)".
-- [23] O-RAN.WG7.IPC-HRD-Opt8.0: "O-RAN Hardware Reference Design Specification for Indoor Picocell (FR1) with Split Architecture Option 8".
-- [24] O-RAN.WG4.TS.MP-0: "O-RAN Management Plane Specification" ("Open FH M-Plane").
-- [25] O-RAN.WG3.TS.E2SM: "O-RAN E2 Service Model (E2SM)".
-- [26] O-RAN.WG3.TS.RICARCH: "O-RAN Near-RT RIC Architecture".
-- [27] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "O-RAN Non-RT RIC: Architecture".
-- [28] O-RAN.WG6.O-Cloud Notification API: "O-RAN O-Cloud Notification API Specification for Event Consumers".
-- [29] O-RAN.WG6.AAL-GAnP: "O-RAN Acceleration Abstraction Layer General Aspects and Principles" ("AALGAP").
-- [30] O-RAN.WG10.TS.Information Model and Data Models: "O-RAN Information Model and Data Models Specification & YANG Models".
-- [31] O-RAN.WG10.TS.O1-Interface: "O-RAN O1 Interface Specification" ("OAM Interface").
-- [32] O-RAN.WG11.TS.SecTestSpecs.0: "O-RAN Security Test Specifications".
-- [33] O-RAN.WG6.TS.O2-GA&P: "O-RAN O2 Interface General Aspects and Principles" ("O2GAP").
-- [34] O-RAN.WG10.TS.OAM-Architecture: "O-RAN Operations and Maintenance Architecture" ("OAM Architecture").
-- [35] O-RAN.WG2.TS.R1GAP: "O-RAN R1 Interface: General Aspects and Principles" ("R1GAP").
-- [36] O-RAN.WG11.TS.SecProtSpec.0: "O-RAN Security Protocols Specifications".
-- [37] O-RAN.WG11.TS.SRCS.0: "O-RAN Security Requirements and Control Specifications".
-- [38] O-RAN.WG1.TS.Use-Cases-Detailed-Specification: "O-RAN Use Cases Detailed Specification".
-- [39] O-RAN.WG3.TS.Y1GAP: "O-RAN Y1 interface: General Aspects and Principles" ("Y1GAP").
-- [40] O-RAN.WG5.TS.D2GAP: "O-RAN D2 Interface: General Aspects and Principles" ("D2GAP").
-- [41] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2".
-- [42] O-RAN.WG1.TS.SMOARCH: "SMO Architecture".
-
-## 2.2 Informative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are not necessary for the application of the present document, but they assist the user with regard to a particular subject area.
-
-- [i.1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
-- [i.2] 3GPP TR 38.801: "Study on new radio access technology: Radio access architecture and interfaces (Release 14)".
-- [i.3] O-RAN.WG6.CADS: "O-RAN Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN".
-- [i.4] O-RAN.WG11.TR.Threat-Modeling.0: "O-RAN Security Threat Modeling and Risk Assessment".
-- [i.5] O-RAN White Paper: "O-RAN: Towards an Open and Smart RAN", October 2018 ("O-RAN Whitepaper").
-- [i.6] Rose, S., Borchert, O., Mitchell, S., and Connelly, S., NIST SP 800-207: "Zero-Trust Architecture", U.S. NIST, August 2020, .
-- [i.7] Zero Trust Maturity Model, US DHS CISA, April 2023.
-
-# --- 3 Definition of terms, symbols and abbreviations
-
-## 3.1 Terms
-
-For the purposes of the present document, the terms given in 3GPP TR 21.905 [i.1] and the following apply:
-
-**E2 Node:** A logical node terminating E2 interface.
-
-**Managed Element:** The definition of a Managed Element (ME) is given in 3GPP TS 28.622 [2], clause 4.3.3.
-
-**Managed Function:** The definition of a Managed Function (MF) is given in 3GPP TS 28.622 [2], clause 4.3.4.
-
-**Near-Real-Time RAN Intelligent Controller:** An O-RAN Network Function (NF) comprised of the Near-RT RIC platform and Near-RT RIC Applications (xApps).
-
-**Near-RT RIC APIs:** A set of service-based interfaces that can be produced and consumed by the Near-RT RIC Platform and xApps.
-
-NOTE: Please refer to Near-RT RIC Architecture [26] for more information.
-
-**Near-RT RIC platform:** Platform supporting A1, E2, Y1 and O1 interfaces and providing a set of services via Near-RT RIC APIs needed for xApp functionality.
-
-**Non-Real-Time RAN Intelligent Controller:** A functionality within Service Management and Orchestration (SMO) comprised of the Non-RT RIC Framework and the Non-RT RIC Applications (rApps) that manages the content carried across the A1 interface.
-
-NOTE: Please refer to Non-RT RIC: Architecture [27] for more information.
-
-**Non-RT RIC Framework:** A functionality within the Non-RT RIC that logically terminates the A1 interface and provides support for rApps, including the R1 services through the R1 interface.
-
-**NMS:** A Network Management System for the O-RU as specified in Open FH M-Plane [24] to support legacy Open Fronthaul M-Plane deployments (prior to version 5 of Open FH M-Plane [24]).
-
-**O-Cloud:** Cloud platform that provides O-RAN standardized interfaces, hosting O-RAN defined software components.
-
-NOTE: Please refer to Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN [i.3] for more information.
-
-**O-eNB:** An O-RAN eNB as specified in 3GPP TS 36.401 [4] or O-RAN ng-eNB as specified in 3GPP TS 38.300 [8].
-
-NOTE: Please refer to clause 5.3.7 for more information.
-
-**O-RAN Central Unit – Control Plane:** A logical node hosting the RRC and the control plane part of the PDCP protocol.
-
-NOTE: Please refer to clause 5.3.3 for more information.
-
-**O-RAN Central Unit – User Plane:** A logical node hosting the user plane part of the PDCP protocol and the SDAP protocol.
-
-NOTE: Please refer to clause 5.3.4 for more information.
-
-**O-RAN Distributed Unit:** A logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.
-
-NOTE: Please refer to clause 5.3.5 for more information.
-
-**O-RAN Network Function:** A network function with O-RAN defined behaviors and interfaces, which can also inherit and/or extend defined behaviors and interfaces of a Network Function defined in 3GPP TS 23.501 [1].
-
-**O-RAN node:** Same as an O-RAN NF.
-
-**O-RAN Radio Unit:** A logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP's "TRP" or "RRH" but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction).
-
-NOTE: Please refer to clause 5.3.6 for more information.
-
-**O1:** Interface used by the SMO framework, as specified in clause 5.3.1, for operation and management of O-RAN NFs as specified in OAM Interface [31].
-
-**O2:** Interface between SMO framework as specified in clause 5.3.1 and the O-Cloud.
-
-NOTE: Please refer to O2GAP [33] for more information.
-
-**Open Fronthaul M-Plane:** Management interface controlling the O-RU, generally driven from the O-DU but in the case of the hybrid topology also driven from the SMO.
-
-NOTE: Please refer to Open FH M-Plane [24] for more details.
-
-**PCell O-DU:** O-DU where SpCell (Special Cell as defined in 3GPP TS 37.340 [41]) is configured for a particular UE for supporting inter O-DU carrier aggregation.
-
-**rApp:** Modular application that consumes and/or produces non real time management and automation services.
-
-**R1:** A service-based interface between the rApps and the R1 Termination via which R1 services can be produced and consumed.
-
-NOTE: Please refer to R1GAP [35] for more information.
-
-**R1 Services:** The SMOS capabilities available for consumption by rApps, and the capabilities produced by rApps, that are accessible via the R1 interface.
-
-**SCell O-DU:** O-DU where SCell (Secondary Cell as defined in 3GPP TS 37.340 [41]) is configured for a particular UE for supporting inter O-DU carrier aggregation.
-
-**SMO:** A Service Management and Orchestration framework (SMO framework).
-
-NOTE: Please refer to clause 5.3.1 for more details.
-
-**SMO External Interface:** The interface between the SMO and an SMO External System.
-
-**SMO External System:** A data source outside the O-RAN domain that provides data to the SMO.
-
-**SMO Functions (SMOFs):** Internal SMO entities which provide one or more SMO Services.
-
-NOTE: An SMO Function exposes standardized interfaces which enable interoperability between SMO Functions.
-
-**SMO Service (SMOS):** Standardized cohesive set of management, orchestration and automation capabilities offered by an SMO Function.
-
-**xApp:** An application consuming and/or producing Near-RT RIC services via the Near-RT RIC API to provide value added control of, or guidance to the E2 Nodes.
-
-**Y1:** An interface over which RAN analytics services are exposed by the Near-RT RIC to be consumed by Y1 consumers.
-
-**Y1 consumers:** A role played by entities within or outside of the PLMN trust domain that consumes the Y1 services produced by the Near-RT RIC.
-
-## 3.2 Symbols
-
-Void
-
-## 3.3 Abbreviations
-
-For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [i.1] and the following apply:
-
-| | |
-|---------|---------------------------------------------------------|
-| 4G | 4th Generation of mobile communications |
-| 5G | 5th Generation of mobile communications |
-| 3GPP | 3rd Generation Partnership Project |
-| 5GC | 5G Core |
-| 5GS | 5G System |
-| AAL | Accelerator Abstraction Layer |
-| API | Application Programming Interface |
-| AI | Artificial Intelligence |
-| AMF | Access and Mobility Functions |
-| CA | Carrier Aggregation |
-| CM | Configuration Management |
-| CMTS | Cable Modem Termination System |
-| CP | Control Plane |
-| CSP | Communications Service Provider |
-| CTI | Cooperative Transport Interface |
-| CUS | Control User Synchronization |
-| DC | Dual Connectivity |
-| DOCSIS | Data Over Cable Service Interface Specification |
-| DM | Data Model |
-| DME | Data Management and Exposure |
-| DTLS | Datagram Transport Layer Security |
-| E-UTRA | Evolved Universal Terrestrial Radio Access |
-| E-UTRAN | Evolved Universal Terrestrial Radio Access Network |
-| EN-DC | E-UTRAN New Radio – Dual Connectivity |
-| eNB | evolved Node B |
-| EPC | Evolved Packet Core |
-| FCAPS | Fault, Configuration, Accounting, Performance, Security |
-| FFT | Fast Fourier Transform |
-| FHGW | Fronthaul Gateway |
-| FHM | Fronthaul Multiplexer |
-| FM | Fault Management |
-| gNB | next generation Node B |
-
-| | |
-|-------------|------------------------------------------------|
-| gNB-CU | gNB Central Unit |
-| gNB-DU | gNB Distributed Unit |
-| GUAMI | Globally Unique AMF Identifier |
-| GUMMEI | Globally Unique MME Identifier |
-| HARQ | Hybrid Automatic Repeat Request |
-| ID | Identifier |
-| iFFT | inverse Fast Fourier Transform |
-| IM | Information Model |
-| IPSec | Internet Protocol Security |
-| LLS | Lower Layer Split |
-| LTE | Long Term Evolution |
-| MAC | Media Access Control |
-| ME | Managed Element |
-| MeNB | Master eNB |
-| MF | Managed Function |
-| ML | Machine Learning |
-| MME | Mobility Management Entity |
-| Near-RT RIC | Near-Real-Time RAN Intelligent Controller |
-| NETCONF | Network Configuration Protocol |
-| NF | Network Function |
-| NG | Next Generation |
-| NG-RAN | Next Generation RAN |
-| NGAP | Next Generation Application Protocol |
-| NIST | National Institute of Standards and Technology |
-| NMS | Network Management System |
-| Non-RT RIC | Non-Real-Time RAN Intelligent Controller |
-| NR | 5G New Radio |
-| O-Cloud | O-RAN Cloud |
-| O-CU-CP | O-RAN Central Unit – Control Plane. |
-| O-CU-UP | O-RAN Central Unit – User Plane |
-| O-DU | O-RAN Distributed Unit |
-| O-eNB | O-RAN eNB |
-| O-RU | O-RAN Radio Unit |
-| OAM | Operations, Administration and Maintenance |
-| OLT | Optical Line Terminal |
-| ONU | Optical Network Unit |
-| Open FH | Open Fronthaul |
-| PDCP | Packet Data Convergence Protocol |
-
-| | |
-|-------|-----------------------------------------------|
-| PHY | Physical layer |
-| PKI | Public Key Infrastructure |
-| PKIX | Public Key Infrastructure (X.509) |
-| PM | Performance Management |
-| PNF | Physical Network Function |
-| PON | Passive Optical Network |
-| PRACH | Physical Random Access Channel |
-| PTP | Precision Time Protocol |
-| RAN | Radio Access Network |
-| rApp | Non-RT RIC Application |
-| RIC | RAN Intelligent Controller |
-| RF | Radio Frequency |
-| RLC | Radio Link Control |
-| RRC | Radio Resource Control |
-| RRH | Remote Radio Head |
-| RRU | Remote Radio Unit |
-| RT | Real Time |
-| RU | Radio Unit |
-| SBA | Service Based Architecture |
-| SBOM | Software Bill of Materials |
-| SDAP | Service Data Adaptation Protocol |
-| SME | Service Management and Exposure |
-| SMO | Service Management and Orchestration |
-| SMOF | Service Management and Orchestration Function |
-| SMOS | Service Management and Orchestration Service |
-| SRB | Signalling Radio Bearer |
-| SSHv2 | Secure Shell 2.0 |
-| TLS | Transport Layer Security |
-| TN | Transport Node |
-| TR | Technical Report |
-| TRP | Transmission and Reception Point |
-| TS | Technical Specification |
-| TU | Transport Unit |
-| UE | User Equipment |
-| UL | Up Link |
-| UP | User Plane |
-| UPF | User Plane Function |
-| WG | Working Group |
-
-| | |
-|------|-------------------------|
-| xApp | Near-RT RIC Application |
-| X2AP | X2 Application Protocol |
-| XnAP | Xn Application Protocol |
-| ZTA | Zero Trust Architecture |
-
-# 4 General O-RAN architecture principles
-
-This clause contains the general O-RAN architecture principles as described below.
-
-- The O-RAN architecture, interface specifications, and terminology shall be consistent with 3GPP architecture, interface specifications, and terminology with additions to accommodate O-RAN specific features.
-- This document represents the O-RAN architecture at the time of its publication and may evolve as deemed appropriate by the O-RAN ALLIANCE.
-- The O-RAN architecture includes a logical representation of a Radio Access Network (RAN) which extends the 3GPP specified RAN and consists of logical NFs or logical nodes (as per 3GPP TS 38.300 [8] and TR 21.905 [i.1]).
-
-NOTE: Therefore, the terms O-RAN NFs as well as O-RAN nodes are used interchangeably to refer to some of the logical O-RAN entities, according to the context used in that particular statement. In any case, they always refer to a logical entity and not to a physical or cloudified instantiation of an O-RAN NF or an O-RAN node.
-
-# 5 O-RAN architecture
-
-## 5.1 Overall architecture of O-RAN
-
-Figure 5.1-1 below provides a high-level view of the O-RAN architecture. It shows that the interfaces – A1, O1, Open Fronthaul M-plane and O2 – connecting SMO (Service Management and Orchestration) framework to O-RAN Network Functions and to O-Cloud. As depicted in this figure, the O-Cloud includes the O-Cloud Notification interface as specified in O-Cloud Notification API Specification for Event Consumers [28] is available for the relevant O-RAN Network Functions (i.e., Near-RT RIC, O-CU-CP, O-CU-UP and O-DU) to receive O-Cloud related notifications.
-
-Figure 5.1-1 below also illustrates that the O-RAN Network Functions can be hosted on the O-Cloud or on customized hardware.
-
-All O-RAN NFs, except O-RU, are managed via the O1 interface to an authorized SMO framework.
-
-The O1 interface exposes management services for the O-RAN NFs that are managed individually or together, as specified in OAM Architecture[34].
-
-The Open Fronthaul M-plane interface, between SMO and O-RU, supports the O-RU management in hybrid mode, as specified in Open FH M-Plane [24].
-
-O-RAN NFs instantiated on the O-Cloud may utilize the APIs exposed by the Accelerator Abstraction Layer (AAL) defined in AALGAP [29].
-
-The Near-RT RIC O-RAN NF in figure below provides RAN analytics information services via the Y1 service interface as specified in Y1GAP [39]. These services can be consumed by Y1 consumers after mutual authentication and authorization by subscribing to or requesting the RAN analytics information via the Y1 service interface. Y1 consumers role can be played by entities which are within an PLMN trusted domain. Y1 consumers outside the PLMN trusted domain may use Y1 services in a secure manner via an exposure function, e.g., as in 3GPP TS 23.501 [1], clause 5.20. The framework for mutual authentication and authorization between Y1 consumers and the Near-RT RIC is not supported in the present document.
-
-
-
-The diagram illustrates the high-level architecture of O-RAN. At the top is the **Service Management and Orchestration framework** (SMO), which contains the **Non-RT RIC**. An **External system providing enrichment data to the SMO** is connected to the SMO. Below the SMO is the **Near-RT RIC**, which is part of the **O-RAN Network Functions**. The Near-RT RIC connects to the **O-Cloud** via the **O-Cloud Notification** interface. The O-Cloud is connected to the **O-RU**. The O-RU connects to the **5GC** via the **NG** interface. The O-RU also connects to the **Open Fronthaul M-Plane**, which is connected to the **Near-RT RIC**. The Near-RT RIC connects to the **Y1 consumers** via the **Y1** interface. The O-RAN defined interfaces are labeled as **O2** (between SMO and Near-RT RIC), **A1** (between SMO and Near-RT RIC), and **O1** (between SMO and O-RAN Network Functions). A legend indicates that purple lines represent O-RAN Defined Interfaces, orange lines represent 3GPP Defined Interfaces, and black lines represent Interfaces out of scope for O-RAN.
-
-High Level Architecture of O-RAN diagram showing Service Management and Orchestration framework, Non-RT RIC, Near-RT RIC, O-RAN Network Functions, O-Cloud, O-RU, Y1 consumers, and 5GC with various interfaces like O2, A1, O1, Open Fronthaul M-Plane, O-Cloud Notification, and NG.
-
-**Figure 5.1-1: High Level Architecture of O-RAN**
-
-Within the logical architecture of O-RAN, as shown in Figure 5.1-2 below, the radio side includes Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, and O-RU O-RAN NFs. The E2 interface connects O-eNB to Near-RT RIC. Although not shown in this figure, the O-eNB does support O-DU and O-RU O-RAN NFs with an Open Fronthaul interface between them. The Near-RT RIC, in the figure below, supports the Y1 service interface towards Y1 consumers. Y1 consumers, unlike the other network elements shown in this figure, does not denote a logical O-RAN function.
-
-As stated earlier, the management side includes SMO Framework containing a Non-RT-RIC function. The O-Cloud, on the other hand, is a cloud computing platform comprising a collection of physical infrastructure nodes that meet O-RAN requirements to host the relevant O-RAN NFs (such as Near-RT RIC, O-CU-CP, O-CU-UP, and O-DU etc.), the supporting software components (such as Operating System, Virtual Machine Monitor, Container Runtime, etc.) and the appropriate management and orchestration functions. The virtualization of O-RU is not supported in the present document.
-
-As shown in this figure, the O-RU provides the Open Fronthaul M-Plane interface to authorized O-DU in hierarchical mode, or to authorized O-DU and SMO in hybrid mode as specified in Open FH M-Plane [24] and OAM Architecture [34].
-
-NOTE: The LLS (O-DU to O-RU interface) specified in clauses 5.3.5 and 5.3.6 (Split Option 7-2x) is the Open Fronthaul interface described in the Open FH CUS-Plane [19]. Other LLS options specified in 3GPP TR 38.801 [i.2] may be considered for reference designs when the relevant interfaces are described in specifications created by related open industry initiatives (e.g., the Small Cell Forum for Split Option 6) or in O-RAN white-box hardware specifications (e.g., Split Option 8).
-
-As shown in Figure 5.1-2, O-DU provides D2 interface to connect with peer O-DU for supporting inter O-DU carrier aggregation. The D2 interface includes D2-u and D2-c services.
-
-
-
-Figure 5.1-2: Logical Architecture of O-RAN. This diagram shows the logical architecture of O-RAN. At the top is the Service Management and Orchestration framework, which contains the Non-Real Time RIC. Below it is the Near-Real Time RIC. To the left is the O-eNB. To the right are the O-CU-CP and O-CU-UP. Below the O-CU-CP and O-CU-UP is the O-DU. Below the O-DU is the O-RU. At the bottom is the O-Cloud. Interfaces are shown between these components: O1, O2, A1, Y1, E2, X2-c, X2-u, NG-u, Xn-c, NG-c, F1-c, F1-u, D2, Open FH M-Plane, and Open FH CUS-Plane. A legend indicates that solid lines represent 3GPP interfaces and green lines represent O-RAN interfaces.
-
-Figure 5.1-2: Logical Architecture of O-RAN
-
-The following figure shows the Uu interface between UE and O-RAN NFs as well as between UE and O-eNB. As shown in Figure 5.1-3 below, the dotted box denotes all the O-RAN NFs required to support the Uu interface for NR. The O-eNB, on the other hand, terminates the Uu interface for LTE. Please refer to clause 5.4.17 for more details.
-
-
-
-Figure 5.1-3: Uu interface for O-RAN Network Functions and O-eNB. This diagram shows the Uu interface for O-RAN Network Functions and O-eNB. It includes the Service Management and Orchestration framework, Non-Real Time RIC, Near-RT RIC, O-eNB, O-CU-CP, O-CU-UP, O-DU, O-RU, and O-Cloud. A dotted box encloses the O-CU-CP, O-CU-UP, O-DU, and O-RU, indicating they are required to support the Uu interface for NR. The O-eNB is shown outside the dotted box, terminating the Uu interface for LTE. Interfaces shown include O1, O2, A1, Y1, E2, X2-c, X2-u, NG-u, Xn-c, NG-c, F1-c, F1-u, D2, Open FH M-Plane, and Open FH CUS-Plane. A legend indicates that solid lines represent 3GPP interfaces and green lines represent O-RAN interfaces.
-
-Figure 5.1-3: Uu interface for O-RAN Network Functions and O-eNB
-
-## 5.2 O-RAN control loops
-
-The O-RAN architecture supports at least the following control loops involving different O-RAN functionalities:
-
-- Non-RT (Non-Real Time) control loops
-- Near-RT (Near-Real Time) control loops
-- RT (Real Time) control loops
-
-
-
-The diagram illustrates the O-RAN control loop hierarchy. At the top is the **Service Management and Orchestration framework** (SMO), which contains the **Non-RT RIC**. Below it is the **Near-RT RIC**, which connects to **O-eNB**, **O-CU-CP**, and **O-CU-UP**. The **O-CU-CP** connects to **O-DU**, which in turn connects to **O-RU** and **O-Cloud**. The **O-CU-UP** connects to various external interfaces: X2-c, X2-u, NG-u, Xn-c, NG-c, and F1-u. The **Open FH M-Plane** and **Open FH CUS-Plane** are also shown. A legend indicates that green lines represent O-RAN interfaces and black lines represent 3GPP interfaces. Control loops are categorized by timing: Non-RT (>= ~1 s), Near-RT (>= ~10 ms < ~1 s), and RT (< ~10 ms). The **Y1 consumers** block is also shown.
-
-Figure 5.2-1: O-RAN Control Loops diagram showing the hierarchy of control loops from Non-RT to RT across various O-RAN entities like SMO, RIC, O-eNB, O-CU-CP, O-CU-UP, O-DU, O-RU, and O-Cloud. It includes timing ranges and interface legends.
-
-Figure 5.2-1: O-RAN Control Loops
-
-As shown in Figure 5.2-1 above, the control loops are defined based on the controlling entity and the architecture shows the other logical entities with which the control loop host interacts.
-
-Control loops exist at various levels and run simultaneously. Depending on the use case, they may or may not interact with each other. The use cases for the Non-RT and Near-RT control loops and the interaction between the RICs for these use cases are fully defined by O-RAN Use Cases Detailed Specification [38]. The Use Cases Detailed Specification [38] also defines relevant interaction for the O-CU-CP and O-DU control loops, responsible for call control and mobility, radio scheduling, HARQ, beamforming etc. along with slower mechanisms involving SMO management interfaces.
-
-The timing of these control loops is use case dependent. Typical execution time for use cases involving the Non-RT control loops are 1 second or more; Near-RT control loops are in the order of 10 milliseconds or more; control loops in the E2 Nodes can operate below 10 milliseconds. (e.g., O-DU radio scheduling).
-
-For any specific use case, however, a stable solution would require the loop time in the Non-RT RIC and/or SMO management plane processes to be significantly longer than the loop time for the same use case in the control entities stated above.
-
-## 5.3 Description of O-RAN architecture elements
-
-### 5.3.1 Service Management and Orchestration framework
-
-#### 5.3.1.1 Service Management and Orchestration framework architecture principles
-
-Service Management and Orchestration (SMO) and Service Management and Orchestration framework (SMO framework) have been used interchangeably in this document.
-
-Service Based Architecture (SBA) introduces the roles of service producer and service consumer together with standardized service-based interfaces. These standardized service-based interfaces enable interoperability within the SMO. SBA is not
-
-concerned with the implementation, but it defines logical functions in their service producer and consumer roles. When properly applied the SBA approach can enable the following:
-
-- Validates produced services with consumer use cases.
-- Identifies service operations with their information model defining semantic behaviour.
-- Specifies the API and a data model for a syntactic interface.
-- Identifies common services that can be produced by a single producer such as those that are commonly used by multiple internal consumers (e.g., authentication, authorization, service registration and discovery, data management, etc.).
-
-A service-based SMO architecture is specified in SMO Architecture [42].
-
-#### 5.3.1.2 SMO Services (SMOSs)
-
-##### 5.3.1.2.1 Introduction to SMO Services
-
-In the O-RAN architecture, SMO is responsible for RAN domain management. Following the SBA principles above, the SMO Services produced by the SMO are defined. A SMOF implementation can produce and/or consume any combinations of one or more SMOSs, provided that the SMOF complies with the O-RAN specifications of the interfaces exposing the SMOSs.
-
-The definition of SMOFs is in general not in scope of the O-RAN specifications, as the interoperable functional behaviour of SMOFs is specified via the SMOS Producer/Consumer roles.
-
-The SMO Services produced by the SMO include those listed below.
-
-- RAN NF OAM SMOS
-- Network Functions Orchestration (NFO) SMOS
-- Federated O-Cloud Orchestration and Management (FOCOM) SMOS
-- Service Management and Exposure (SME) SMOS
-- Data Management and Exposure (DME) SMOS
-- Topology Exposure and Inventory Management (TE&IV) SMOS
-- RAN Analytics SMOS
-- Service and Slice Subnet Orchestration (SO) SMOS
-- Service and Slice Subnet Assurance (SA) SMOS
-- AI/ML workflow (AIMLWF) SMOS
-- rApp Management SMOS
-- AI Related SMOS
-- Software Package Onboarding SMOS
-- Policy Management and Information (PMI) SMOS
-
-A representative overview of the SMO architecture is provided in Figure 5.3.1.2.1-1 below. Descriptions of the capabilities of each SMOS, and a representation of the SMOSs in a service-based SMO architecture diagram, are provided in SMO Architecture [42]. SMO communication with other O-RAN architectural elements, with external service consumers and/or producers, and with external data consumers and/or producers, is also described in SMO Architecture [42].
-
-
-
-The diagram illustrates the Service Management and Orchestration (SMO) framework. At the top, a box labeled 'Service Management and Orchestration framework' contains a 'Non-RT RIC' box. Inside the 'Non-RT RIC' box, there is an 'rApps' box connected to an 'R1 Termination' box via an 'R1' interface. Below the 'Non-RT RIC' box, there is a horizontal line representing the SMO boundary. Below this line, on the left, is an 'SMOS Producer/Consumer' box. On the right, another 'SMOS Producer/Consumer' box is shown. The 'R1 Termination' box is connected to the 'SMOS Producer/Consumer' box on the right. The 'SMOS Producer/Consumer' box on the left is connected to the 'R1 Termination' box. A legend at the bottom indicates that a small circle represents 'Consumption of services' and a larger circle represents 'Production of services'.
-
-Service Management and Orchestration framework diagram showing the hierarchy of the SMO, Non-RT RIC, rApps, R1 Termination, and SMOS components with their service consumption and production relationships.
-
-Figure 5.3.1.2.1-1: SMO architecture overview
-
-##### 5.3.1.2.2 Service Management and Orchestration framework in the O-RAN architecture
-
-The SMO consumes services offered by other O-RAN architecture elements through four key southbound interfaces:
-
-- The A1 interface, which provides A1 policy management, A1 enrichment information and A1 ML model management between SMO and the Near-RT RIC to support RAN optimization.
-- The O1 interface, which provides SMO FCAPS support either directly or indirectly between the SMO and the O-RAN Network Functions.
-- In the hierarchical model, SMO FCAPS support information over O1 to the O-DU which uses the Open FH M-Plane interface to manage the O-RU.
-- In the hybrid model, SMO provides FCAPS support information over Open FH M-Plane interface between the SMO and the O-RU and over O1 to the O-DU which uses the Open FH M-Plane interface to manage the O-RU.
-- O2 interface between the SMO and the O-Cloud to provide O-Cloud resource management and workload management.
-
-##### 5.3.1.2.3 Non-RT RIC
-
-The Non-RT RIC supports intelligent RAN optimization control loops through rApps with intervals greater than 1 second.
-
-Non-RT RIC is the functionality internal to the SMO that supports intelligent RAN optimization by:
-
-- enabling the A1-Related SMOS to provide policy-based guidance over the A1 interface
-- enabling the A1-Related SMOS to provide enrichment information over the A1 interface
-- enabling the A1-Related SMOS to provide ML model management over the A1 interface
-- enabling RAN optimization actions through the RAN NF OAM SMOS over O1 and Open FH M-Plane interfaces, and the NFO and FOCOM SMOSs over O2 interface
-
-The rApps can be producers and/or consumers of R1 services, as shown in Figure 5.3.1.2.1-1. For more information on R1 services and the R1 interface refer to Non-RT RIC Architecture [27].
-
-##### **5.3.1.2.4 SMO capabilities extensions**
-
-As a flexible extension mechanism, the SMO allows delivery of aspects of RAN management and orchestration functionality via rApps.
-
-##### **5.3.1.2.5 Void**
-
-### **5.3.2 Near-RT RIC**
-
-Near-RT RIC is an O-RAN NF that enables near real-time control and optimization of services and resources of E2 Nodes via fine-grained data collection and actions over the E2 interface with control loops in the order of 10 ms-1s. The Near-RT RIC hosts one or more xApps that use E2 interface to collect near real-time information (e.g., on a UE basis or a Cell basis) and provide value added services. The Near-RT RIC control over the E2 Nodes is steered via the policies and the enrichment data provided via A1 from the Non-RT RIC. Based on the available data, the Near-RT RIC generates the RAN analytics information and exposes it via Y1 interface.
-
-The functional enhancement provided by the Near-RT RIC and the E2 Node is subject to the capability of the E2 Node exposed over the E2 interface by means of the E2SM [25], in order to support the use cases described in Use Cases Detailed Specification [38]. The E2 service model describes the functions in the E2 Node which may be controlled by the Near-RT RIC and the related procedures. For a function exposed in the E2SM [25], the Near-RT RIC may e.g., monitor, override, or control via policies the behavior of E2 Node.
-
-In the event of a Near-RT RIC failure, the E2 Node shall be able to provide services but there may be an impact to certain optimization capabilities that are provided by the Near-RT RIC.
-
-The Near-RT RIC is composed of a Near-RT RIC platform and one or more xApps as specified in Near-RT RIC Architecture [26] and their capabilities are exposed as services. Both the Near-RT RIC platform and an xApp can be a service producer and/or a service consumer, and these services can be accessed via the set of Near-RT RIC APIs as illustrated in Figure 5.3.2-1.
-
-
-
-The diagram illustrates the service-based representation of the Near-RT RIC architecture. At the top, three overlapping rectangular boxes represent 'xApps'. Below them is a horizontal line labeled 'Near-RT RIC API(s)'. Each xApp is connected to this API line by a vertical line that includes a small circle with a dot, representing a service interface. Below the API line, another vertical line with a similar service interface connects to a rectangular box at the bottom labeled 'Near-RT RIC platform'.
-
-Service-based representation of Near-RT RIC architecture showing xApps connected to a Near-RT RIC platform via Near-RT RIC API(s).
-
-**Figure 5.3.2-1: Service-based representation of Near-RT RIC as specified in Near-RT RIC Architecture [26]**
-
-### **5.3.3 O-CU-CP**
-
-The O-CU-CP terminates the NG-c, X2-c, Xn-c, F1-c, and E1 interfaces as well as the RRC and PDCP (for SRB) protocols towards the UE as specified in 3GPP TS 38.401 [10].
-
-The O-CU-CP terminates E2 interface to Near-RT RIC as specified in E2GAP [22].
-
-The O-CU-CP is managed via O1 interface by the SMO as specified in OAM Architecture [34].
-
-The O-CU-CP terminates NG-c interface to 5GC as specified in 3GPP TS 38.300 [8].
-
-The O-CU-CP terminates X2-c interface to O-eNB (in case O-eNB is an O-RAN eNB), eNB, or to en-gNB in EN-DC as specified in 3GPP TS 36.420 [6] and 3GPP TS 38.300 [8].
-
-The O-CU-CP terminates Xn-c to O-CU-UP, O-eNB (in case O-eNB is an O-RAN ng-eNB), gNB, or to ng-eNB as specified in 3GPP TS 38.300 [8] and 3GPP TS 38.420 [12].
-
-### 5.3.4 O-CU-UP
-
-The O-CU-UP terminates the NG-u, X2-u, S1-u, Xn-u, F1-u, and E1 interfaces as well as the PDCP and SDAP protocols towards the UE as specified in 3GPP TS 38.401 [10].
-
-The O-CU-UP terminates E2 interface to Near-RT RIC as specified in E2GAP [22].
-
-The O-CU-UP is managed via O1 interface by the SMO as specified in OAM Architecture [34].
-
-The O-CU-UP terminates NG-u interface to 5GC as specified in 3GPP TS 38.300 [8].
-
-The O-CU-UP terminates X2-u interface to O-eNB (in case O-eNB is an O-RAN eNB), eNB, or to en-gNB in EN-DC as specified in 3GPP TS 36.420 [6] and 3GPP TS 38.300 [8].
-
-The O-CU-UP terminates Xn-u to O-CU-UP, O-eNB (in case O-eNB is an O-RAN ng-eNB), gNB, or to ng-eNB as specified in 3GPP TS 38.300 [8] and 3GPP TS 38.420 [12].
-
-### 5.3.5 O-DU
-
-The O-DU is an O-RAN NF in the O-RAN Architecture. An O-DU, combined with one or more O-RU(s) connected to it, supports and is fully compatible with the functions of a gNB-DU as defined by 3GPP TS 38.401 [10].
-
-The O-DU may be implemented either by virtualized or non-virtualized methods.
-
-The O-DU terminates the E2 and the F1 interface (according to the principles described in clause 5.4.9), and the Open Fronthaul interface (also known as LLS interface as specified in Open FH CUS-Plane [19]) as well as the RLC, MAC, and High-PHY functions of the radio interface towards the UE.
-
-The O-DU is managed via O1 interface by the SMO as specified in OAM Architecture [34].
-
-The O-DU terminates the Open Fronthaul M-Plane interface, towards the O-RU, to support O-RU management either in hierarchical model or hybrid model, as specified in Open FH M-Plane [24].
-
-The O-DU terminates the D2 interface as specified in D2GAP [40] towards a peer O-DU, to support the inter O-DU NR carrier aggregation across O-DUs connected to same O-CU-CP.
-
-The O-DU may support CTI to a TN to control UL bandwidth allocation to TUs for UL LLS traffic on shared point-to-multipoint transport network (TN is a PON OLT or DOCSIS CMTS, TU is a PON ONU or DOCSIS Cable Modem). The CTI is specified in CTI Control [20] and CTI Management [21]. An informative overview of the CTI is shown in Annex A.
-
-### 5.3.6 O-RU
-
-The O-RU terminates the Open Fronthaul interface (also known as LLS interface as specified in Open FH CUS-Plane [19]) as well as Low-PHY functions of the radio interface towards the UE. This is deployed as a PNF.
-
-The O-RU terminates the Open Fronthaul M-Plane interface towards the O-DU and SMO as specified in Open FH M-Plane [24].
-
-### 5.3.7 O-eNB
-
-In case O-eNB is an O-RAN O-eNB, O-eNB terminates the S1, X2, O1 and E2 interfaces as well as the RRC, PDCP, RLC, MAC, and PHY layers of the LTE-Uu radio interface towards the UE as specified in 3GPP TS 36.401 [4]. In case O-eNB is an O-RAN ng-eNB, O-eNB terminates the NG, Xn, O1, and E2 interfaces as well as the RRC, SDAP, NR PDCP, RLC, MAC, and PHY layers of the LTE-Uu radio interface towards the UE as specified in 3GPP TS 38.401 [10].
-
-In case O-eNB is an O-RAN ng-eNB,
-
-- the O-eNB terminates E2 interface to Near-RT RIC as specified in E2GAP [22].
-- the O-eNB is managed via O1 interface by the SMO as specified in OAM Architecture [34].
-- the O-eNB terminates NG interface to 5GC as specified in 3GPP TS 38.300 [8].
-- the O-eNB terminates Xn interface to O-eNB, gNB, ng-eNB, or O-CU-CP/O-CU-UP as specified in 3GPP TS 38.300 [8] and 3GPP TS 38.420 [12].
-
-In case O-eNB is an O-RAN eNB,
-
-- the O-eNB terminates E2 interface to Near-RT RIC as specified in E2GAP [22].
-- the O-eNB is managed via O1 interface by the SMO as specified in OAM Architecture [34].
-- the O-eNB terminates S1 interface to EPC as specified in 3GPP TS 36.401 [4].
-- the O-eNB terminates X2 interface to O-eNB, eNB, en-gNB, or O-CU-CP/O-CU-UP as specified in 3GPP TS 36.401 [4] and 3GPP TS 38.420 [12].
-
-The O-eNB supports O-DU and O-RU O-RAN NFs with an Open Fronthaul interface between them as specified in Open FH CUS-Plane [19] and Open FH M-Plane [24].
-
-### 5.3.8 O-Cloud
-
-O-Cloud is a cloud computing platform comprising a collection of physical infrastructure nodes that meet O-RAN requirements to host the relevant O-RAN NFs (i.e., Near-RT RIC, O-CU-CP, O-CU-UP, and O-DU), the supporting software components (such as Operating System, Virtual Machine Monitor, Container Runtime, etc.), and the appropriate management and orchestration functions which satisfy the following criteria:
-
-- Exposes the O-RAN O2 interface for cloud and workload management to provide functions such as infrastructure discovery, registration, software lifecycle management, workload lifecycle management, fault management, performance management, and configuration management.
-- Exposes O-RAN AAL API towards the hosted O-RAN workloads for hardware accelerator management.
-- Exposes O-Cloud Notification interface towards the hosted O-RAN workloads in order to notify the workloads of critical notifications (e.g., PTP synchronization states).
-- The virtualization of the O-RU is not supported in the present document.
-
-## 5.4 Relevant interfaces in O-RAN architecture
-
-### 5.4.1 Introduction to relevant interfaces in O-RAN architecture
-
-The following interfaces are defined and maintained by O-RAN:
-
-- A1 interface
-- O1 interface
-- O2 interface
-- E2 interface
-- Y1 interface
-- O-Cloud Notification interface
-
-- Open Fronthaul interface
-- R1 interface
-- Near-RT RIC APIs
-- CTI (Cooperative Transport Interface)
-- D2 interface
-
-The following interfaces are defined and maintained by 3GPP, but seen also as part of the O-RAN architecture:
-
-- E1 interface
-- F1-c interface
-- F1-u interface
-- NG-c interface
-- NG-u interface
-- X2-c interface
-- X2-u interface
-- Xn-c interface
-- Xn-u interface
-- Uu interface
-
-Following clauses describe the termination points of O-RAN defined interfaces and 3GPP interfaces adopted by O-RAN.
-
-### 5.4.2 A1 interface
-
-A1 interface is between Non-RT RIC and the Near-RT RIC as specified in A1GAP [18].
-
-A1 is the interface between the Non-RT RIC in SMO and the Near-RT RIC function O-RAN NF. A1 interface supports three types of services as defined in A1GAP [18]:
-
-- Policy Management Service
-- Enrichment Information Service
-- ML Model Management Service
-
-A1 policies have the following characteristics compared to persistent configuration as specified in A1GAP [18] and Use Cases Detailed Specification [38]. A1 policies,
-
-- are not critical to traffic;
-- have temporary validity;
-- may handle individual UE or dynamically defined groups of UEs;
-- act within and take precedence over the configuration;
-- are non-persistent, i.e., do not survive a restart of the Near-RT RIC.
-
-### 5.4.3 O1 interface
-
-The O1 interface is used by SMO for the management of the O-RAN NFs as defined in OAM Architecture [34] and OAM Interface [31].
-
-### 5.4.4 O2 interface
-
-The O2 interface is between the SMO and O-Cloud as introduced in O2GAP [33]. The O2 interface provides two categories of services – O2 deployment management services (O2dms) and O2 infrastructure management services (O2ims).
-
-### 5.4.5 E2 interface
-
-E2 is a logical interface connecting the Near-RT RIC with an E2 Node as defined in E2GAP [22].
-
-- An E2 Node is connected to only one Near-RT RIC.
-- A Near-RT RIC can be connected to multiple E2 Nodes.
-
-The E2 interface is a control plane interface that provides support for Near-RT RIC Services using E2 Application Protocol and E2 Services Models as specified in E2GAP [22].
-
-### 5.4.6 O-Cloud Notification interface
-
-The O-Cloud Notification interface allows event consumer such as an O-DU deployed on O-Cloud to subscribe to events/status from the O-Cloud. The cloud infrastructure will provide event producer to enable cloud workloads to receive events/status that might be known only to the infrastructure.
-
-### 5.4.7 Open Fronthaul interface
-
-The Open FH (Fronthaul) interface is between O-DU and O-RU logical nodes as specified in Open FH CUS-Plane [19] and Open FH M-Plane [24]. The Open FH interface includes the CUS (Control User Synchronization) Plane and M (Management) Plane. In hybrid mode, the Open FH M-Plane interface connects the O-RU to the SMO for FCAPS functionality.
-
-### 5.4.8 E1 interface
-
-The E1 interface, as defined by 3GPP, is between the gNB-CU-CP and gNB-CU-UP logical nodes as specified in 3GPP TS 38.401[10] and 3GPP TS 38.460 [14]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted between the O-CU-CP and the O-CU-UP logical nodes.
-
-### 5.4.9 F1-c interface
-
-The F1-c interface, as defined by 3GPP, is between the gNB-CU-CP and gNB-DU logical nodes as specified in 3GPP TS 38.401 [10] and 3GPP TS 38.470 [16]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted between the O-CU-CP and the O-DU logical nodes, as well as for the definition of interoperability profile specifications.
-
-### 5.4.10 F1-u interface
-
-The F1-u interface, as defined by 3GPP, is between the gNB-CU-UP and gNB-DU logical nodes as specified in 3GPP TS 38.401 [10] and 3GPP TS 38.470 [16]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted between the O-CU-UP and the O-DU logical nodes, as well as for the definition of interoperability profile specifications.
-
-### 5.4.11 NG-c interface
-
-The NG-c interface, as defined by 3GPP, is between the gNB-CU-CP and the AMF in the 5GC as specified in 3GPP TS 38.300 [8]. It is also referred as N2 in 3GPP TS 38.300 [8]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted between the O-CU-CP and the 5GC.
-
-### 5.4.12 NG-u interface
-
-The NG-u interface, as defined by 3GPP, is between the gNB-CU-UP and the UPF in the 5GC as specified in 3GPP TS 38.300 [8]. It is also referred as N3 in 3GPP TS 38.300 [8]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted between the O-CU-UP and the 5GC.
-
-### 5.4.13 X2-c interface
-
-The X2-c interface is defined in 3GPP for transmitting control plane information between eNBs or between eNB and en-gNB in EN-DC as specified in 3GPP TS 36.420 [6] and 3GPP TS 38.300 [8]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted for the definition of interoperability profile specifications.
-
-### 5.4.14 X2-u interface
-
-The X2-u interface is defined in 3GPP for transmitting user plane information between eNBs or between eNB and en-gNB in EN-DC as specified in 3GPP TS 36.420 [6] and 3GPP TS 38.300 [8]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted for the definition of interoperability profile specifications.
-
-### 5.4.15 Xn-c interface
-
-The Xn-c interface is defined in 3GPP for transmitting control plane information between gNBs, ng-eNBs or between ng-eNB and gNB as specified in 3GPP TS 38.300 [8] and 3GPP TS 38.420 [12]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted for the definition of interoperability profile specifications.
-
-### 5.4.16 Xn-u interface
-
-The Xn-u interface is defined in 3GPP for transmitting user plane information between gNBs, ng-eNBs or between ng-eNB and gNB as specified in 3GPP TS 38.300 [8] and 3GPP TS 38.420 [12]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted for the definition of interoperability profile specifications.
-
-### 5.4.17 Uu interface
-
-The UE to eNB/gNB interface in 3GPP is denoted as the Uu interface. The Uu is a complete protocol stack from L1 to L3 and as such, seen as a whole, it terminates in the NG-RAN. If the NG-RAN is decomposed, different protocols terminate at different reference points and none of them has been defined by O-RAN. Since the Uu messages still flow from the UE to the intended eNB/gNB managed function, it is not shown in the O-RAN architecture as a separate interface to a specific managed function. For more information on the Uu interface between the UE and the NG-RAN, please refer to clauses 5.2 and 5.3 of 3GPP TS 38.401 [10].
-
-### 5.4.18 CTI
-
-Interface between the O-DU and TN to dynamically control bandwidth allocations to TUs when using a shared point-to-multipoint transport network. The CTI is specified in CTI Control [20] and CTI Management [21].
-
-### 5.4.19 Y1 interface
-
-Y1 service interface as specified in Y1GAP [39] allows the Y1 consumers to subscribe or request the RAN analytics information provided by Near-RT RIC.
-
-### 5.4.20 R1 interface
-
-The R1 interface is a service-based interface between the rApps and the Non-RT RIC framework via which R1 services can be produced and consumed as specified in Non-RT RIC Architecture [27].
-
-The producers of R1 services can be part of the Non-RT RIC and/or the SMO Framework. R1 services are specified in R1GAP [35].
-
-### 5.4.21 Near-RT RIC APIs
-
-The Near-RT RIC APIs are a set of service-based interfaces that can be produced and consumed by the Near-RT RIC Platform and xApps as specified in Near-RT RIC Architecture [26].
-
-### 5.4.22 D2 interface
-
-The D2 interface is between two O-DU nodes connected to the same O-CU-CP. O-CU-UP for both the O-DUs can be same or different. One O-DU can be connected to multiple O-DUs. D2 interface is used for supporting inter O-DU NR carrier aggregation across O-DUs. An O-DU can be a PCell O-DU for a particular UE and a SCell O-DU for another UE at the same time.
-
-## 5.5 UE associated identifiers used in O-RAN
-
-As described earlier (clauses 5.3.1 and 5.3.2), the Non-RT RIC and Near-RT RIC enable intelligent RAN optimization via A1, O1 and E2 interfaces respectively.
-
-To support intelligent RAN optimization, the Non-RT RIC with rApps and Near-RT RIC with xApps utilize the knowledge of different UE associated events reported by the O-RAN NFs (excluding O-RU) over E2 and O1 interfaces. Both the Non-RT RIC and Near-RT RIC may need to correlate different UE associated events reported by the O-RAN functions for the same UE. In order to facilitate this correlation task, the reporting O-RAN NF includes a set of UE associated identifiers with any report containing UE specific information.
-
-The Table 5.5-1 below shows the set of UE associated identifiers to be reported by any O-RAN NF (excluding O-RU) over O1 and E2 interfaces for any UE associated information.
-
-**Table 5.5-1: UE associate identifiers used in O-RAN**
-
-| UE associated identifier | Reference Specification | Comments |
-|--------------------------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| AMF UE NGAP ID | 3GPP TS 38.413 [11] | Reported by O-CU-CP and O-eNB for UEs connected to 5GC. |
-| GUAMI | 3GPP TS 38.413 [11] | Reported by O-CU-CP and O-eNB for UEs connected to 5GC. |
-| MME UE S1AP ID | 3GPP TS 36.413 [5] | Reported by O-eNB for UEs connected to EPC. |
-| GUMMEI | 3GPP TS 36.413 [5] | Reported by O-eNB for UEs connected to EPC. |
-| gNB-CU UE F1AP ID | 3GPP TS 38.473 [17] | Reported by O-CU-CP and O-DU. |
-| gNB-CU-CP UE E1AP ID | 3GPP TS 38.463 [15] | Reported by O-CU-CP and O-CU-UP. |
-| RAN UE ID | 3GPP TS 38.473 [17]
3GPP TS 38.463 [15] | Reported by O-CU-CP, O-CU-UP and O-DU when available/allocated. |
-| M-NG-RAN node UE XnAP ID | 3GPP TS 38.423 [13] | Identifier reported when the UE operates in DC with 5GC. Reported by O-CU-CP and O-eNB. |
-| Global NG-RAN Node ID | 3GPP TS 38.423 [13] | Identifier reported when the UE operates in DC with 5GC. Identifies the peer gNB/ng-eNB and is reported in conjunction with the M-NG-RAN node UE XnAP ID to ensure that the UE can be uniquely identified over Xn interface. Reported by O-eNB and O-CU-CP. |
-| MeNB UE X2AP ID | 3GPP TS 36.423 [7] | Identifier reported when the UE operate in DC with EPC. Reported by O-CU-CP and O-eNB. |
-| Global eNB ID | 3GPP TS 36.423 [7] | Identifier reported when the UE operate in DC with EPC. Identifies the peer eNB and is reported in conjunction with the MeNB UE X2AP ID to ensure that the UE can be uniquely identified over X2 interface. Reported by O-CU-CP and O-eNB. |
-| C-RNTI (Cell Radio Network Temporary Identifier) | 3GPP TS 38.331 [9] | Optionally reported by O-CU-CP, O-DU and O-eNB. |
-
-Additionally, the Non-RT RIC and Near-RT RIC may initiate messages towards the O-RAN NFs which are associated with specific UEs. In such cases, the Non-RT RIC and Near RT RIC may include one or more of the UE associated identifiers specified in the Table 5.5-1 above with any UE associated messages over A1 and E2 interface for identification of the UE in the O-RAN NFs.
-
-## 5.6 O-RAN security architecture
-
-The goals of the O-RAN ALLIANCE are to achieve a secure, open, and interoperable RAN. Building upon security advancements from the 3GPP and IETF standards development organizations, the O-RAN ALLIANCE specifies an O-RAN security architecture with the goal to enable 5G CSPs (Communication Service Provider) to deploy and operate O-RAN with the same, or higher level of confidence as a 3GPP-specified RAN. The O-RAN ALLIANCE is strengthening O-RAN's security posture by specifying security requirements and security controls that mitigate risk across its attack surface while pursuing the goals of a ZTA (Zero-Trust Architecture).
-
-The O-RAN security architecture is specified in the following two O-RAN Technical Specifications:
-
-- Security Protocols Specifications [36]
-- Security Requirements and Controls Specifications [37]
-
-The above TSs, Security Protocols Specifications [36] and Security Requirements and Controls Specifications [37], include specifications for configuration and cipher suites with use of the following security protocols on O-RAN interfaces to ensure confidentiality, integrity, availability, and authenticity: SSHv2 (Secure Shell 2.0), TLS 1.2 and 1.3, DTLS (Datagram Transport Layer Security) 1.2, IPsec (Internet Protocol Security), OAuth 2.0, CMPv2, IEEE 802.1X, and NETCONF (Network Configuration Protocol) over Secure Transport.
-
-O-RAN has also provided requirements for SBOM (Software Bill of Materials) in Security Requirements and Controls Specifications [37].
-
-The test cases to verify proper security implementation of O-RAN security architecture is specified in the O-RAN Technical Specification:
-
-- O-RAN Security Tests Specifications [32]
-
-The threats to the O-RAN architecture and the risk assessment are documented in the TR:
-
-- O-RAN Security Threat Modeling and Risk Assessment [i.4]
-
-The security threat modeling and risk analysis is used to derive the security requirements and security controls in the Security Requirements and Controls Specifications [37]. The O-RAN Security Threat Modeling and Risk Assessment [i.4] considers external and internal threats to achieve a ZTA. In addition, security analysis TRs are maintained for O-RAN NFs and features. These TRs help to drive the requirements in the O-RAN security specifications.
-
-NOTE: Internal and external threats are considered in a ZTA, as defined in NIST SP 800-207 [i.6]. Achieving a ZTA is an incremental process, as identified by the United States Department of Homeland Security's Cybersecurity and Infrastructure Security Agency in Zero Trust Maturity Model [i.7]. The O-RAN ALLIANCE is continuing to pursue a ZTA as the O-RAN architecture, threats, and controls evolve.
-
-# --- 6 O-RAN Information Model (IM) principles
-
-O-RAN shall align its Information Model (IM) with 3GPP to the extent possible. The additional O-RAN extensions to its IM and DMs (Data Model) are described in O-RAN Information Model and Data Models Specification [30].
-
-# --- Annex (informative): Implementation options of O-RAN functions and network elements
-
-## A.1 Shared cell
-
-Shared cell, as specified in Open FH CUS-Plane [19], is defined as the operation for the same cell by several O-RUs with one or multiple component carriers. It can be deployed in either FHM (Fronthaul Multiplexer) or Cascade mode as described below.
-
-In FHM mode, the shared cell may be realized by placing an FHM function between an O-DU and several O-RUs that may have one or multiple component carriers from these O-RUs. FHM function may be modelled as an O-RU with LLS Fronthaul support (same as normal O-RU) along with the copy and combine function (additional to normal O-RU), but without radio transmission/reception capability. The Figure A.1-1 below shows how each O-RU can be used for either operating in the same cell (Single Cell Scenario) or in different cells (Multiple Cells Scenario) by configuring the FHM function.
-
-
-
-Figure A.1-1: Shared cell deployment using FHM mode. The diagram is split into two parts: 'Single Cell Scenario' and 'Multiple Cell Scenario'. In both, an O-DU (red box) connects to an FHM (grey box) via an 'Open Fronthaul' interface. The FHM then connects to multiple O-RUs (red boxes) via 'Open Fronthaul' interfaces. In the Single Cell Scenario, the O-RUs are labeled #1, #2, #N-1, and #N, all grouped under 'Cell # 1'. In the Multiple Cell Scenario, the O-RUs are grouped into multiple cells: Cell # 1 (O-RUs #1, #2), Cell # M-1 (O-RUs #N-3, #N-2), and Cell # M (O-RUs #N-1, #N).
-
-**Figure A.1-1: Shared cell deployment using FHM mode**
-
-In Cascade mode, the shared cell is realized by several O-RUs cascaded in chain. In this case, one or more O-RUs are inserted between the O-DU and the O-RU. The O-RUs in the cascaded chain except for the last O-RU support Copy and Combine function. Figure A.1-2 below shows an implementation of Cascade mode shared cell.
-
-
-
-Figure A.1-2: Shared cell deployment using Cascade mode. An O-DU (red box) connects to a stack of O-RUs via 'Open Fronthaul' interfaces. The stack includes O-RU #1 (Cascade O-RU #1), O-RU #2 (Cascade O-RU #2), O-RU #N-1 (Cascade O-RU #N-1), and O-RU #N (normal O-RU / Cascade O-RU #N). All O-RUs are grouped under a single 'Single Cell' label at the bottom.
-
-**Figure A.1-2: Shared cell deployment using Cascade mode**
-
-The Cascade mode, as described above, is implemented within the O-RU.
-
-Please refer to Open FH CUS-Plane [19] for additional information.
-
-## A.2 FHGW function
-
-The FHGW (Fronthaul Gateway) function may be placed between the O-DU and RU/RRU (Radio Unit / Remote Radio Unit) with the following O-RAN specified interfaces:
-
-- The interface between O-DU and FHGW function is Open Fronthaul (Option 7-2x).
-- The interface between FHGW function and RU/RRU is subject to reference implementation developed by any relevant O-RAN WG (e.g., WG7) as described in Hardware Reference Design Specification for Indoor Picocell (FR1) with Split Architecture Option 8 [23].
-- The interface between FHGW function and RU/RRU does not support Open Fronthaul (Option 7-2x).
-- The FHGW function may be packaged with other functions (such as Ethernet switching) in a physical product, as considered within WG7.
-
-The Figure A.2-1 below depicts the deployment of the FHGW function using O-RAN specified interfaces.
-
-
-
-```
-
-graph TD
- ODU[O-DU] ---|Open Fronthaul| FHGW[FHGW]
- FHGW ---|A reference implementation by O-RAN (not an Open Fronthaul)| RU[RU/RRU]
- style ODU fill:#ff0000,color:white
- style FHGW fill:#808080,color:white
- style RU fill:#008000,color:white
-
-```
-
-Diagram showing the deployment of O-DU and RU/RRU using FHGW function. O-DU (red box) is connected to FHGW (grey box) via Open Fronthaul. FHGW is connected to RU/RRU (green box) via a reference implementation by O-RAN (not an Open Fronthaul).
-
-**Figure A.2-1: Deployment of O-DU and RU/RRU using FHGW function**
-
-## A.3 Near-RT RIC
-
-The Near-RT RIC can control multiple E2 Nodes or can control a single E2 Node. The following figures show two implementation options of Near-RT RIC.
-
-
-
-```
-
-graph TD
- subgraph SMO [Service Management and Orchestration framework]
- NRT[Non-Real Time RIC]
- end
- NRT ---|A1| NRT1[Near-RT RIC]
- NRT ---|A1| NRT2[Near-RT RIC]
- NRT ---|A1| NRT3[Near-RT RIC]
- NRT1 ---|E2| OCUCP1[O-CU-CP]
- NRT1 ---|E2| OCUUP1[O-CU-UP]
- NRT1 ---|E2| ODU1[O-DU]
- NRT2 ---|E2| OCUCP2[O-CU-CP]
- NRT2 ---|E2| OCUUP2[O-CU-UP]
- NRT2 ---|E2| ODU2[O-DU]
- NRT2 ---|E2| OENB2[O-eNB]
- NRT3 ---|E2| OENB3[O-eNB]
- style SMO fill:#6a5acd,color:white
- style NRT fill:#00ff00,color:white
- style NRT1 fill:#4a90e2,color:white
- style NRT2 fill:#4a90e2,color:white
- style NRT3 fill:#4a90e2,color:white
- style OCUCP1 fill:#ffcc00,color:white
- style OCUUP1 fill:#ffcc00,color:white
- style ODU1 fill:#ff0000,color:white
- style OCUCP2 fill:#ffcc00,color:white
- style OCUUP2 fill:#ffcc00,color:white
- style ODU2 fill:#ff0000,color:white
- style OENB2 fill:#6b8e23,color:white
- style OENB3 fill:#6b8e23,color:white
-
-```
-
-Type 1: Near-RT RIC only serving 5G Type 2: Near-RT RIC serving 5G and 4G Type 3: Near-RT RIC only serving 4G
-
-Diagram showing three types of Near-RT RIC configurations. All three types are connected to a Non-Real Time RIC via A1 interfaces. Type 1 (Near-RT RIC only serving 5G) connects to O-CU-CP, O-CU-UP, and O-DU via E2 interfaces. Type 2 (Near-RT RIC serving 5G and 4G) connects to O-CU-CP, O-CU-UP, O-DU, and O-eNB via E2 interfaces. Type 3 (Near-RT RIC only serving 4G) connects to O-eNB via E2 interfaces.
-
-**Figure A.3-1: Centralized Near-RT RIC Serving 4G and 5G Simultaneously**
-
-
-
-Diagram of Distributed Near-RT RIC architecture. At the top is the 'Service Management and Orchestration framework' containing a 'Non-Real Time RIC'. Below this are four 'Near-RT RIC' blocks connected via A1 interfaces. At the bottom are four radio units: 'O-CU-CP', 'O-CU-UP', 'O-DU', and 'O-eNB' connected via E2 interfaces to the Near-RT RICs. A callout indicates that the four Near-RT RIC blocks represent the implementation of one physical Near-RT RIC consisting of one or more logical Near-RT RICs.
-
-**Figure A.3-2: Distributed Near-RT RIC**
-
-## A.4 Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, and O-RU
-
-Although the O-RAN architecture specifies the O-RAN NFs Near-RT RIC, O-CU-CP, O-CU-UP, O-DU and O-RU as separate O-RAN architecture elements, it is possible in the implementation to aggregate some or all of these O-RAN NFs, and thus collapsing some of the internal interfaces, e.g., F1-c, F1-u, E1, and E2. At least the following implementation options are possible:
-
-- Disaggregated O-RAN NFs as per O-RAN architecture
-- Aggregate O-CU-CP and O-CU-UP
-- Aggregate O-CU-CP, O-CU-UP, and O-DU
-- Aggregate Near-RT RIC, O-CU-CP, and O-CU-UP
-- Aggregate O-CU-CP, O-CU-UP, O-DU, and O-RU
-- Aggregate O-DU and O-RU
-- Aggregate Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, and O-RU
-
-Aggregation of O-RAN NFs is supported by the O-RAN specified interfaces O1 and E2. For the O1 interface, the aggregated O-RAN NFs will be managed as separate Managed Functions belonging to a single Managed Element as specified in OAM Architecture [34]. For the E2 interface the aggregated O-RAN NFs can be exposed as part of the E2 Service Model towards the Near-RT RIC (see Annex A in E2GAP [22]).
-
-Please see the figures (i.e., Figure A.4-1 through Figure A.4-7) below.
-
-
-
-Figure A.4-1: Disaggregated O-RAN Network Functions. This diagram illustrates the O-RAN architecture with disaggregated components. At the top, the 'Service Management and Orchestration framework' contains the 'Non-Real Time RIC'. Below it is the 'Near-Real Time RIC', connected via the A1 interface. The Near-Real Time RIC connects to 'O-eNB', 'O-CU-CP', and 'O-CU-UP' via E2 interfaces. 'Y1 consumers' connect to the Near-Real Time RIC via the Y1 interface. The 'O-CU-CP' and 'O-CU-UP' connect to the 'O-DU' via F1-c and F1-u interfaces respectively. The 'O-DU' connects to the 'O-RU' via 'Open FH CUS-Plane' and 'Open FH M-Plane'. The 'O-RU' sits above the 'O-Cloud'. Green lines represent O-RAN interfaces (O1, O2, A1, E2, Y1, Open FH), and black lines represent 3GPP interfaces (X2-c, X2-u, NG-u, Xn-u, Xn-c, NG-c, E1, F1-c, F1-u).
-
-**Figure A.4-1: Disaggregated O-RAN Network Functions**
-
-
-
-Figure A.4-2: Aggregated O-CU-CP and O-CU-UP. This diagram shows a similar architecture to Figure A.4-1, but with the 'O-CU-CP' and 'O-CU-UP' enclosed in a dashed box to indicate aggregation. The connections and interfaces (O1, O2, A1, E2, Y1, F1, etc.) remain consistent with the disaggregated model, showing how aggregated units still interface with the SMO, RICs, and lower-level O-DU/O-RU components.
-
-**Figure A.4-2: Aggregated O-CU-CP and O-CU-UP**
-
-
-
-Figure A.4-3: Aggregated O-CU-CP, O-CU-UP, and O-DU. This diagram shows the O-RAN architecture where the O-CU-CP and O-CU-UP are aggregated into a single unit, and the O-DU is separate. The Service Management and Orchestration framework (SMO) contains a Non-Real Time RIC connected to an O-eNB via O2 and O1 interfaces, and to a Near-Real Time RIC via an A1 interface. The Near-Real Time RIC is connected to 'Y1 consumers' via a Y1 interface and to the O-CU-CP via an E2 interface. The O-CU-CP and O-CU-UP are connected to each other via an E1 interface. The O-CU-CP is connected to the O-DU via an F1-c interface, and the O-CU-UP is connected to the O-DU via an F1-u interface. The O-DU is connected to the O-RU via an Open FH CUS-Plane, and the O-RU is connected to the O-Cloud via an Open FH M-Plane. The O-RU is also connected to the O-eNB via an Open FH M-Plane. The O-CU-CP and O-CU-UP are connected to external networks via X2-c, X2-u, NG-u, Xn-c, Xn-u, and NG-c interfaces. A legend indicates that black lines represent 3GPP interfaces and green lines represent O-RAN interfaces.
-
-**Figure A.4-3: Aggregated O-CU-CP, O-CU-UP, and O-DU**
-
-
-
-Figure A.4-4: Aggregated Near-RT RIC, O-CU-CP, and O-CU-UP. This diagram shows the O-RAN architecture where the Near-Real Time RIC, O-CU-CP, and O-CU-UP are aggregated into a single unit. The Service Management and Orchestration framework (SMO) contains a Non-Real Time RIC connected to the aggregated unit via an A1 interface. The aggregated unit is connected to 'Y1 consumers' via a Y1 interface. The O-CU-CP and O-CU-UP are connected to each other via an E1 interface. The O-CU-CP is connected to the O-DU via an F1-c interface, and the O-CU-UP is connected to the O-DU via an F1-u interface. The O-DU is connected to the O-RU via an Open FH CUS-Plane, and the O-RU is connected to the O-Cloud via an Open FH M-Plane. The O-RU is also connected to the O-eNB via an Open FH M-Plane. The O-CU-CP and O-CU-UP are connected to external networks via X2-c, X2-u, NG-u, Xn-c, Xn-u, and NG-c interfaces. A legend indicates that black lines represent 3GPP interfaces and green lines represent O-RAN interfaces.
-
-**Figure A.4-4: Aggregated Near-RT RIC, O-CU-CP, and O-CU-UP**
-
-
-
-Figure A.4-5: Aggregated O-CU-CP, O-CU-UP, O-DU, and O-RU. This diagram shows the O-RAN architecture where the O-CU-CP, O-CU-UP, O-DU, and O-RU are aggregated into a single unit. The Service Management and Orchestration framework contains a Non-Real Time RIC connected to an O-eNB via O2 and O1 interfaces, and to a Near-Real Time RIC via an A1 interface. The Near-Real Time RIC is connected to Y1 consumers and to the aggregated unit via E2 interfaces. The aggregated unit (O-CU-CP, O-CU-UP, O-DU, O-RU) is connected to an O-Cloud via an E2 interface. The O-CU-CP and O-CU-UP are connected to external networks via X2-c, X2-u, NG-u, Xn-u, Xn-c, and NG-c interfaces. A legend indicates that black lines represent 3GPP interfaces and green lines represent O-RAN interfaces.
-
-**Figure A.4-5: Aggregated O-CU-CP, O-CU-UP, O-DU, and O-RU**
-
-
-
-Figure A.4-6: Aggregated O-DU and O-RU. This diagram shows the O-RAN architecture where the O-DU and O-RU are aggregated into a single unit. The Service Management and Orchestration framework contains a Non-Real Time RIC connected to an O-eNB via O2 and O1 interfaces, and to a Near-Real Time RIC via an A1 interface. The Near-Real Time RIC is connected to Y1 consumers and to the O-CU-CP and O-CU-UP via E2 interfaces. The O-CU-CP is connected to the O-CU-UP via an E1 interface. The O-CU-CP is connected to the aggregated O-DU/O-RU unit via F1-c, and the O-CU-UP is connected via F1-u. The aggregated unit is connected to an O-Cloud via an E2 interface. External interfaces include X2-c, X2-u, NG-u, Xn-u, Xn-c, and NG-c. A legend indicates that black lines represent 3GPP interfaces and green lines represent O-RAN interfaces.
-
-**Figure A.4-6: Aggregated O-DU and O-RU**
-
-
-
-The diagram illustrates the O-RAN architecture components and their interconnections. At the top is the **Service Management and Orchestration framework**, which contains the **Non-Real Time RIC**. Below it is the **Near-Real Time RIC**. The **Non-Real Time RIC** is connected to the **Near-Real Time RIC** via the **A1** interface. The **Near-Real Time RIC** is connected to **Y1 consumers** via the **Y1** interface. The **Non-Real Time RIC** is also connected to the **O-CU-CP** via the **O1** interface. The **O-CU-CP** and **O-CU-UP** are connected to each other via the **X2-c** and **X2-u** interfaces. The **O-CU-CP** is connected to the **O-DU** via the **NG-c** and **Xn-c** interfaces. The **O-CU-UP** is connected to the **O-DU** via the **NG-u** and **Xn-u** interfaces. The **O-DU** and **O-RU** are connected to each other via the **O2** interface. The **O-RU** is connected to the **O-Cloud** via the **O1** interface. A legend indicates that black lines represent **3GPP interfaces** and green lines represent **O-RAN interfaces**.
-
-Diagram of Aggregated Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, and O-RU architecture. The diagram shows a hierarchy of components: Service Management and Orchestration framework (top), Non-Real Time RIC, Near-Real Time RIC, O-CU-CP, O-CU-UP, O-DU, O-RU, and O-Cloud (bottom). Interfaces are labeled: O1, O2, A1, Y1, X2-c, X2-u, NG-u, Xn-u, Xn-c, NG-c. A legend indicates 3GPP interfaces (black lines) and O-RAN interfaces (green lines).
-
-Figure A.4-7: Aggregated Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, and O-RU
-
-## A.5 Cooperative transport
-
-To enhance the resource utilization and reduce the latency of UL LLS traffic when using a shared point-to-multipoint transport network requiring resource allocation (such as PON or DOCSIS), the O-RAN architecture supports a cooperative transport feature. The cooperative transport feature is based on the O-DU’s knowledge of the expected uplink LLS traffic from a given O-RU which is provided to the associated (PON or DOCSIS) TN in the transport network. This enables the TN to dynamically allocate the correct bandwidth over the shared transport network to the TU that is used by the O-RU. The CTI signaling is described in CTI Control [20]. To support the CTI, the O-DU is configured over the O1 interface with CTI client specific configuration as described in CTI Management [21]. When there are intermediate nodes between the O-DU and the TN, they will forward the CTI messages transparently but will not participate in CTI interactions.
-
-A simplified architecture of the CTI is shown in figure A.5-1 below. The SMO, O-DU and O1 interface shown in this figure are part of the O-RAN Architecture (please see clauses 5.3.1, 5.3.5, and 5.4.3, respectively), whereas the TN and Transport OAM, are the components of the transport network. For detailed specification and reference architecture, please see CTI Control [20] and CTI Management [21].
-
-
-
-```
-
-graph TD
- SM[Service Management and Orchestration framework] -- "O1 (including CTI client configuration)" --> OD[O-DU]
- OD -- "CTI" --> TN[TN]
- TN -- "OAM (including CTI server configuration)" --> TO[Transport OAM]
-
-```
-
-Simplified CTI Architecture diagram showing Service Management and Orchestration framework connected to O-DU via O1, O-DU connected to TN via CTI, and TN connected to Transport OAM via OAM.
-
-A.5-1: Simplified CTI Architecture
-
-## A.6 Inter O-DU Carrier Aggregation (CA)
-
-The D2 interface is used for supporting carrier aggregation across cells configured in the different O-DUs as specified in D2GAP [40]. In the present document, DL CA is supported by the D2 interface that includes D2-c and D2-u.
-
-
-
-```
-
-graph TD
- UC[U-CU-UP] -- E1 --> CC[O-CU-CP]
- UC -- F1-u --> OD1[O-DU1]
- UC -- F1-u --> OD2[O-DU2]
- UC -- F1-u --> ODn[O-DUn]
- CC -- F1-c --> OD1
- CC -- F1-c --> OD2
- CC -- F1-c --> ODn
- OD1 -- D2 --> OD2
- OD2 -- D2 --> ODn
- OD1 -- Open FH --> RU1[O-RU1]
- OD2 -- Open FH --> RU2[O-RU2]
- ODn -- Open FH --> RUn[O-RUn]
-
-```
-
-Inter O-DU CA diagram showing O-CU-UP and O-CU-CP connected to multiple O-DUs (O-DU1, O-DU2, O-DUn) via F1-u and F1-c interfaces. The O-DUs are interconnected via D2 interfaces and connected to O-RUs (O-RU1, O-RU2, O-RUn) via Open FH interfaces.
-
-A.6-1: Inter O-DU CA
-
-# Annex (informative): Change history
-
-| Date | Revision | Description |
-|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 2020.01.16 | 01.00 | - First version with an overall architecture of O-RAN.
- Describe O-RAN architecture elements and relevant interfaces.
|
-| 2020.10.30 | 02.00 | - Introduce new implementation options by bundling O-RAN logical functions.
- Clarify the O-RAN position that OFH (7-2x) is the interface between O-DU and O-RU.
- Add a new principle that architecture may evolve as deemed appropriate by the O-RAN community.
|
-| 2020.11.25 | 03.00 | - Introduce functional architecture of Non-RT RIC with description of rApps, R1 interface, and Non-RT RIC framework.
- Add implementation options of FHM and FHGW functions.
- Remove the optionality of SMO to support OFH M-Plane interface towards O-RU.
- Add definition of "Managed Application".
- Add 'legends' to the architecture figures.
|
-| 2021.03.18 | 04.00 | - Enhance O-RAN control loops by making their execution times and interactions dependent on use cases.
- Explain that the execution times of Non-RT and Near-RT control loops may overlap as dictated by use cases.
- Designate the O1 interface between SMO and O-RU as a topic for future study.
- Use two colors (i.e., green for O-RAN and black for 3GPP) for the logical interfaces in the architecture figures.
|
-| 2021.07.16 | 05.00 | - Elaborate the relationship between rApps, R1 interface, Non-RT RIC framework, and SMO framework within Non-RT RIC functional architecture.
- Introduce the concept of 'anchored' vs. 'non-anchored' functionality within SMO and Non-RT RIC frameworks.
- Provide a high-level view of 'functions' required to enable the capabilities of rApps.
- Add a CTI clause and an Annex clause containing a simple CTI implementation.
|
-| 2021.11.18 | 06.00 | - Clarify how R1 interface works between rApps and O-RAN logical functions.
- Extend the "OFH M-Plane" interface between SMO and O-RU.
- Add 'UE Associated Identifiers Used in O-RAN' clause for correlating UE identities.
- Introduce "O-Cloud Notification" interface between O-RAN functions and O-Cloud.
- Add "O-RAN Security Architecture" clause consisting of 'Threat Analysis', 'Attack Surfaces', and 'Security Protocols'.
|
-| 2022.10.21 | 07.00 | - Add the concept of SBA as part of the "SMO Architecture Principles" clause.
- Implement changes (i.e., new legal statement in cover page, revised foot note, and deletion of annex ZZZ) to be compliant with the new IPR policy of O-RAN ALLIANCE.
|
-| 2022.11.17 | 08.00 | - Introduce new Y1 interface for exposing RAN analytics information to internal and/or external functions.
- Remove all references to future work items (e.g., O1 interface between SMO and O-RU, planned security enhancements etc.) to align with the O-RAN drafting rules.
- Add C-RNTI to UE identifier so that it can be optionally reported by O-CU-CP, O-DU, and O-eNB.
|
-| 2023.03.25 | 09.00 | - Elucidate the role of Y1 consumers within or outside the PLMN trust domain.
- Clarify that the Y1 consumers box depicted in figures is not a logical O-RAN function.
- Add definitions of "Y1", "Y1 consumers", "SMO External Interface", "SMO External System", "SMOFs", and "SMOS".
- Enhance the description of O-DU to align it with the gNB-DU of 3GPP.
|
-
-| | | |
-|------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 2023.07.27 | 10.00 | - Eliminate terminology inconsistencies between O-RAN NF, O-RAN function, and O-RAN node.
- Clarify that "O-RAN NF" and "O-RAN node" can be used interchangeably to denote an O-RAN logical entity, according to the context being described.
- Add definition of "Cloudified NF".
- Update O-eNB clause to be consistent with the description of other O-RAN nodes.
|
-| 2023.11.21 | 11.00 | - Clarify that O-RAN NF has "O-RAN defined behaviors and interfaces" but "can also inherit and/or extend" a 3GPP Network Function.
- Remove "Cloudified NF" definition that addresses deployment aspects to keep the focus of this document on logical network view.
- Add R1 interface and Near-RT RIC APIs to "Relevant Interfaces in O-RAN Architecture" clause.
- Add text and figure to describe service-base representation of Near-RT architecture.
- Simplify "O-RAN Security Architecture" clause by removing informative content and referring to relevant WG11 specifications.
- Update relevant clauses to add testability, clarify that O-RAN does not conflict with 3GPP, and align with OAM architecture by representing O1 as a management service.
|
-| 2024.03.29 | 12.00 | - Revise the definitions of O-Cloud, Near-RT RIC, Near-RT RIC APIs, Near-RT RIC platform, xApp, Non-RT RIC, Non-RT RIC Framework, and rApp to align with ODR (O-RAN Drafting Rules).
- Move all TR references to "Informative Reference" clause.
- Add overlooked references and acronyms to their respective clauses.
- Change O1 related "shall" statements to "is" statements to be consistent with current "Architecture Description".
|
-| 2024.12.02 | 13.00 | - Add Release 18 as the default 3GPP reference.
- Include high-level concepts of Decoupled SMO TR.
- Remove RRM terminology to avoid potential conflict with 3GPP specifications.
- Clarify SMO southbound interfaces for FCAPS support in both hierarchical and hybrid models.
- Include the example of Non-RT RIC SMOF consisting of rApps and A1 related SMOSs.
- State that the O2 interface has deployment and infrastructure management services.
- Add "Non-RT RIC" sub-clause within clause "5.3.1 SMO (Service Management and Orchestration)".
|
-| 2025.03.30 | 14.00 | - Add D2 interface.
- Add a description of SMOS Communication and R1 services.
- Make editorial changes to align with ODR (O-RAN Document Drafting Rules).
|
-| 2025.07.25 | 15.00 | - Add definition of "R1 Services".
- Show "R1 interface" and "R1 Termination" in SBA representation of SMOSs.
- State "SMO" and "SMO framework" are used interchangeably. Change "Service Management and Orchestration Framework" to "Service Management and Orchestration framework".
- Add support for SMO consumption of external service/data producers.
- Remove "3GPP MDA MnS (3GPP TS 28.104)" from the "Figure 5.3.1.2.1-1: SMOSs in the SMO SBA representation".
- Correct "Service & Subnet Slice" to "Service and Slice Subnet" or "Service & Slice Subnet".
- Make editorial changes to align with the recent TS Template v05.
|
-| 2025.12.03 | 16.00 | - Add CTI in the list of O-RAN defined interfaces in clause 5.4.1.
- Replace "Figure 5.3.1.2.1-1: SMOSs in the SMO SBA representation" with "Figure 5.3.1.2.1-1: SMO architecture overview".
- Update text in clause 5.3.1 to align with the "SMO architecture overview" figure.
- Remove the content of clause 5.3.1.2.5 and mark it as "Void".
|
\ No newline at end of file
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
deleted file mode 100644
index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:002b1548d4392049bd12ac9da6616c6d5853ea2e756364a532eaae00261be2c5
-size 4525
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/124c6108c63173818afb8ed49521e22d_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/124c6108c63173818afb8ed49521e22d_img.jpg
deleted file mode 100644
index 855365f3d49d9fc6e6709f1e156d56530806a067..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/124c6108c63173818afb8ed49521e22d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2dc994cdb54c07c15b592ec311aef62c93f91ea9e9a827d3cf5703623118a90a
-size 23719
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg
deleted file mode 100644
index 1069ab9699c66beb502a41ad74c660fa16464510..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:f83b26d3364b8bec421c18601f193498de4794cefaa5de501159592f7dfa30f3
-size 78669
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg
deleted file mode 100644
index 37c8e5f40fa3e07d2ed2094c8e47f2f460db84b5..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c5a4313998579c1369db586bd96d34eeb9494449027c8cf73aba1b1fd04a4a82
-size 52249
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg
deleted file mode 100644
index 714716175862aaf3fad0624717fcfc76a2f75beb..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:2adb4cd6a427d882edc3303bde307cf606b84b74fcb96740f904a9223f4bcf98
-size 75007
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4a04896dfb569893fba50729314024f5_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4a04896dfb569893fba50729314024f5_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4af57aad638888edf2062306f8a54a6c_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4af57aad638888edf2062306f8a54a6c_img.jpg
deleted file mode 100644
index 72691974ff466764fded8d1ec095e145593607a1..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4af57aad638888edf2062306f8a54a6c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:f790d100adea5e9cadea6634d1b5b6c75ccad2e18f85c9a15142395eba85005a
-size 56046
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg
deleted file mode 100644
index c928a9b0962e435de5967f830bdd51ef9704e09b..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:7151b9e7481b830664b0bc8912c92af0145c09cc012c1183faaf637a11e820fb
-size 29609
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
deleted file mode 100644
index 6847c30fb1c1ab32b64cde9f652b8477b8482cec..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:bd7af424ae25e4b0dd40ad37bdb0e84c3407aaec36817ba80e6d7ecb3b151bb8
-size 73756
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4f148853ae68fdcf5e43f7604cab457d_img.jpg
deleted file mode 100644
index 4e5f9cc0319665266b280223338a9b8968a3f1a8..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4f148853ae68fdcf5e43f7604cab457d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:45408e97406a2f1a1af44440aadcf15310ccc20aa8653c2bd941b3893898a327
-size 84551
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
deleted file mode 100644
index 6e681bec610e4841f38a15e1188c43f7c0af61f9..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:8bd3ae1c7810b20dd0988d63c5bc560c36bcb9507a00ffb4c1550ee45e985c51
-size 82897
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
deleted file mode 100644
index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4041da71c3f65eef413dcad3172bba4a50fb3f8c94dfe0031d165cdb81b5f91a
-size 4518
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
deleted file mode 100644
index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4041da71c3f65eef413dcad3172bba4a50fb3f8c94dfe0031d165cdb81b5f91a
-size 4518
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg
deleted file mode 100644
index 8535118c0589833e5475b6d7853c1ac64bdc74e6..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:d74b98aa9269c476a1fd1a117f71514143898c29c64170d329806851def52120
-size 74306
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg
deleted file mode 100644
index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a55cf057add81bac5208e738578b06871feea626854066f7ee84fdb6fc13c319
-size 4529
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
deleted file mode 100644
index 7c25c335e360545c149230493c33833d0360fa14..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:70ff3f7616cf90ac5e0a3ab785ca97f352175498d10fdad53d34527b29ad6668
-size 81923
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg
deleted file mode 100644
index 735a88d275e993410c9905e7678db0b538737002..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:f95cde94f59320876f93b84de940ab87219a10aab2c20a779acfbdb38a4c6a50
-size 56482
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/a1890b9a9b85f13e67ed59bbad623659_img.jpg
deleted file mode 100644
index 2863933acdb6618f9bf6c7b7e1f5a9900033dc0c..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/a1890b9a9b85f13e67ed59bbad623659_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:dcc24ec1a6ebad05350095e913e3b0f4f2916cd175f6f1e245ec618723cb13f2
-size 37300
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/a26e142d3df5bef41a84a9dd099d7825_img.jpg
deleted file mode 100644
index 81e17216c9d36d187230c1b3520f534fee0a74fd..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/a26e142d3df5bef41a84a9dd099d7825_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:b79789198eb3cc2e44caedf4f6a3874b81c75a6d26e03ce95a073a96ce3a4d5d
-size 70301
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/c389468860cd886ab9c732473e959f0f_img.jpg
deleted file mode 100644
index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/c389468860cd886ab9c732473e959f0f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4041da71c3f65eef413dcad3172bba4a50fb3f8c94dfe0031d165cdb81b5f91a
-size 4518
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg
deleted file mode 100644
index 5aa98361f489fa4cc5154b6abe9d7c638c65d7a6..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:aea00e6c432261354c006fc45e9df7b713b5a924ef4ce5e5e0d9efc9238480ae
-size 29177
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg
deleted file mode 100644
index 59c6f3d16cc028c289c567f9c1172200444b5ac5..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:d2b868bc1515c6b7b6bb1605a8204f7b1468251703383e6c7896c9bf028592ef
-size 56670
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg
deleted file mode 100644
index 0d85b198d6577034b83b98a0e778b55d222a8a73..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:ebf06d56bc1d245199ec067807d8fb26e6f0cc8e6db26115d1c085d7dfba066a
-size 77103
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg
deleted file mode 100644
index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a55cf057add81bac5208e738578b06871feea626854066f7ee84fdb6fc13c319
-size 4529
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
deleted file mode 100644
index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:13907d04258e9271ee051eba8d6cedf72546d9bf8b92530dd8fa921314655d9f
-size 4491
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
deleted file mode 100644
index 2994d9f720d2a888914c7ec44aef224aa81387c7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:30a2c85b6a5ff062acae1fefa83f2beb0f02c919eb8b29f1efd398ab90b00272
-size 4486
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
deleted file mode 100644
index 2994d9f720d2a888914c7ec44aef224aa81387c7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:30a2c85b6a5ff062acae1fefa83f2beb0f02c919eb8b29f1efd398ab90b00272
-size 4486
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg
deleted file mode 100644
index f50b0c015e1d7b280d154423ba2170a07f8c69a0..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:170c1153acd61c556320bb6b4ff5c3ba194b1b6aeeaad70b50c4e663945f8cf9
-size 13883
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
deleted file mode 100644
index bd40fefc240a5594ab9537c5d4c6a82b735ccce2..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:25800f8b09c159ba1ab1540ab9e9e004b0bcc7bcc421f3d13a8da28b04ca5bb7
-size 52547
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg
deleted file mode 100644
index e7de92299dbebeb939a65301e3ad805aea8eaee8..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:aeb0007279221e6335d83f1346bdb14ca41dc7ad46a346c48c6e0c336b6feac1
-size 78001
diff --git a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
deleted file mode 100644
index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.OAD-R005-v16.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:bc3238cb8249e044e431352b85e73b297352925b914edc60af73d8011b6efe53
-size 4542
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/doc.md b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/doc.md
deleted file mode 100644
index 6e32f0722578234201aff3a67a60a30ff63ce3fb..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/doc.md
+++ /dev/null
@@ -1,391 +0,0 @@
-
-
-# --- **O-RAN Work Group 1 (Use Cases and Overall Architecture)****SMO Architecture**
-
-Copyright © 2026 by the O-RAN ALLIANCE e.V.
-
-The copying or incorporation into any other work of part or all of the material available in this specification in any form without the prior written permission of O-RAN ALLIANCE e.V. is prohibited, save that you may print or download extracts of the material of this specification for your personal use, or copy the material of this specification for the purpose of sending to individual third parties for their information provided that you acknowledge O-RAN ALLIANCE as the source of the material and that you inform the third party that these conditions apply to them and that they must comply with them.
-
-O-RAN ALLIANCE e.V., Buschkauler Weg 27, 53347 Alfter, Germany
-Register of Associations, Bonn VR 11238, VAT ID DE321720189
-
-# --- Contents
-
-| | |
-|-------------------------------------------------------------------------------------|-----------|
-| Foreword..... | 3 |
-| Modal verbs terminology ..... | 3 |
-| 1 Scope..... | 4 |
-| 2 References ..... | 4 |
-| 2.1 Normative references ..... | 4 |
-| 2.2 Informative references ..... | 4 |
-| 3 Definition of terms, symbols and abbreviations ..... | 5 |
-| 3.1 Terms ..... | 5 |
-| 3.2 Symbols..... | 5 |
-| 3.3 Abbreviations ..... | 5 |
-| 4 O-RAN SMO Architecture ..... | 5 |
-| 4.1 SMO Overview ..... | 5 |
-| 4.2 SMO Services (SMOS)..... | 6 |
-| 4.2.1 Introduction to SMO Services..... | 6 |
-| 4.2.2 Service Management and Exposure (SME) SMOS description..... | 6 |
-| 4.2.3 Data Management and Exposure (DME) SMOS description ..... | 7 |
-| 4.2.4 RAN NF OAM SMOS description ..... | 7 |
-| 4.2.5 Network Function Orchestrator SMOS description ..... | 8 |
-| 4.2.6 Federated O-Cloud Orchestration and Management (FOCOM) SMOS description ..... | 8 |
-| 4.2.7 Service and Slice Subnet Orchestration SMOS (SO SMOS) description ..... | 9 |
-| 4.2.8 Service and Slice Subnet Assurance SMOS (SA SMOS) description ..... | 9 |
-| 4.2.9 rApp Management SMOS description ..... | 10 |
-| 4.2.10 Topology Exposure and Inventory SMOS description ..... | 10 |
-| 4.2.11 Software Package Onboarding SMOS description ..... | 10 |
-| 4.2.12 AI Related SMOS description ..... | 11 |
-| 4.3 SMO in consumer role of southbound interfaces ..... | 11 |
-| 4.4 Northbound external exposure of SMO Services ..... | 11 |
-| 4.5 Extending the SMO services..... | 11 |
-| 4.6 SMO Functions ..... | 11 |
-| 4.6.1 Introduction ..... | 11 |
-| 4.6.2 Non-RT RIC SMOF..... | 12 |
-| 4.7 Intent-driven RAN management..... | 12 |
-| Annex (informative): Change history/Change request (history) ..... | 13 |
-
-# --- Foreword
-
-This Technical Specification (TS) has been produced by WG1 of the O-RAN ALLIANCE.
-
-The content of the present document is subject to continuing work within O-RAN and may change following formal O-RAN approval. Should the O-RAN ALLIANCE modify the contents of the present document, it will be re-released by O-RAN with an identifying change of version date and an increase in version number as follows:
-
-version xx.yy.zz
-
-where:
-
-- xx: the first digit-group is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have xx=01). Always 2 digits with leading zero if needed.
-- yy: the second digit-group is incremented when editorial only changes have been incorporated in the document. Always 2 digits with leading zero if needed.
-- zz: the third digit-group included only in working versions of the document indicating incremental changes during the editing process. External versions never include the third digit-group. Always 2 digits with leading zero if needed.
-
-## --- Modal verbs terminology
-
-In the present document "**shall**", "**shall not**", "**should**", "**should not**", "**may**", "**need not**", "**will**", "**will not**", "**can**" and "**cannot**" are to be interpreted as described in clause 3.2 of the O-RAN Drafting Rules (Verbal forms for the expression of provisions).
-
-"**must**" and "**must not**" are **NOT** allowed in O-RAN deliverables except when used in direct citation.
-
-# --- 1 Scope
-
-The present document specifies the SMO architecture based on the service-based-architecture principles described in [1] and provides the description of the SMO Services that are provided by the SMO.
-
-# --- 2 References
-
-## 2.1 Normative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are necessary for the application of the present document.
-
-- [1] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description"
-- [2] O-RAN.WG6.O2-GA&P: "O2 Interface General Aspects and Principles"
-- [3] O-RAN.WG6.ORCH-USE-CASES: "Cloudification and Orchestration Use Cases and Requirements"
-- [4] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "Non-RT RIC: Architecture"
-- [5] O-RAN.WG6.O2DMS-INTERFACE-ETSI-NFV-PROFILE: "O-RAN O2dms Interface Specification: Profile based on ETSI NFV Protocol and Data Models"
-- [6] O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE: "O-RAN O2dms Interface Specification: Kubernetes Native API Profile for Containerized NFs"
-- [7] O-RAN.WG10.TE&IV-UCR: "O-RAN Topology Exposure and Inventory Management Services Use Cases and Requirements"
-- [8] O-RAN.WG10.TS.OAM-Architecture: "O-RAN Operations and Maintenance Architecture"
-- [9] O-RAN.WG10.TS.OnboardingSMOSGAP: "O-RAN Onboarding SMOS General Aspects and Principles"
-- [10] O-RAN.WG2.TS.AIGAP: "O-RAN A1 interface: General Aspects and Principles"
-- [11] ETSI GS-NFV SOL 003: "RESTful protocols specification for the Or-Vnfm Reference Point"
-
-## 2.2 Informative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are not necessary for the application of the present document, but they assist the user with regard to a particular subject area.
-
-- [i.1] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "Non-RT RIC: Architecture"
-
-[i.2] 3GPP TS 28.312: "Intent driven management services for mobile networks"
-
-[i.3] TMF921: "Intent Management API User Guide v5.0.0"
-
-# --- 3 Definition of terms, symbols and abbreviations
-
-## 3.1 Terms
-
-For the purposes of the present document, the terms given in [1] and the following apply:
-
-**Intent:** formal specification of all requirements including goals and constraints given to a system.
-
-NOTE: This definition aligns with the definitions in 3GPP TS 28.312 [i.2], Clause 3.1 and in TMF921 [i.3].
-
-**RAN management intent owner:** An authorized SMO service consumer, responsible for formulating the RAN management Intents as per its own goals and requirements and consuming intent-based services.
-
-**RAN management intent handler:** An authorized SMO service producer which understands, can process and ensure fulfilment of RAN management Intents.
-
-## 3.2 Symbols
-
-Void.
-
-## 3.3 Abbreviations
-
-For the purposes of the present document, the abbreviations given in [1] and the following apply:
-
-| | |
-|------|-------------------------------|
-| RMIO | RAN management intent owner |
-| RMIH | RAN management intent handler |
-
-# --- 4 O-RAN SMO Architecture
-
-## 4.1 SMO Overview
-
-The SMO capabilities identified as SMOSs are represented in a service-based architecture in Figure 4.1-1 below. All the SMO Service producers represented in Figure 4.1-1 can also be SMOS consumers.
-
-Service Management and Orchestration (SMO) and Service Management and Orchestration framework (SMO framework) are used interchangeably in this document.
-
-NOTE: The SMOS interfaces and modelling are not specified in the present document.
-
-
-
-Figure 4.1-1: SMO capabilities represented as SMOSs in the SMO SBA approach. The diagram shows the Service Management and Orchestration framework connected to various network elements and external systems. At the top, external data consumers/producers and external service consumers/producers connect to the framework. The framework contains several SMOSs: Software Package Onboarding, Service & Slice Subnet Orchestration, Service & Slice Subnet Assurance, Topology & Inventory (TE&IV), AI/ML Workflow, Data Management and Exposure (DME), and Service Management and Exposure (SME). These are connected via SMOS Communication to Network Function Orchestrator (NFO), Federated O-Cloud Orchestration and Management (FOCOM), RAN NF QAM (e.g., CM, FM, PM, Tracing, Logging, etc.), RAN Analytics, and Policy Management and Information (PMI). An 'Example Non-RT RIC SMOF' contains rApps, R1, R1 termination, rApp Management, and A1 Related. The framework connects to O-Cloud via O2, to O-RU via Open FH M-plane and O1, and to Near-RT RIC via A1. Other O1 Nodes are also connected to the Near-RT RIC. A legend at the bottom defines symbols for SMO interfaces, external interfaces, service consumption/production, SMOS Producers, and SMOS Producers anchored in Non-RT RIC.
-
-**Figure 4.1-1: SMO capabilities represented as SMOSs in the SMO SBA approach**
-
-NOTE: The AI/ML Workflow, RAN Analytics and Policy Management and Information SMOSs shown in Figure 4.1-1 are not addressed in the current version of this specification.
-
-The SMOS Communication, shown in Figure 4.1-1, represents the logical support for communication between any SMOS Producer, SMOS Consumer, and rApps. Examples of SMOS Communication implementation include, but are not limited to, service mesh, API gateway, direct communication, and message bus. SMOS consumers and producers rely on the capabilities provided by SME for purposes such as service discovery and on the capabilities provided by DME for purposes such as data exposure.
-
-The R1 interface, shown in Figure 4.1-1, is a service-based interface. R1 termination, also shown in Figure 4.1-1, enables R1 service producers and R1 service consumers to exchange messages via the R1 interface.
-
-SME and DME support the exposure of SMO services, and/or data to authorized external services, and/or external data consumers, as represented in the SBA approach depicted in Figure 4.1-1.
-
-SME and DME support the SMO consumption of external services, and/or data from authorized external services, and/or external data producers, as represented in the SBA approach depicted in Figure 4.1-1.
-
-## 4.2 SMO Services (SMOS)
-
-### 4.2.1 Introduction to SMO Services
-
-A set of SMO Services (SMOSs), as defined in the O-RAN Architecture Description [1], is identified in the service-based SMO architecture shown in Figure 4.1-1 above. The capabilities provided by each SMOS are described in the following sub-chapters.
-
-### 4.2.2 Service Management and Exposure (SME) SMOS description
-
-The SME service is introduced in the Non-RT RIC Architecture specification [i.1] section 3.1. The SME services are applicable to any entities within the SMO that fulfil the roles of Service Producer and/or Service Consumer.
-
-In a service-based SMO architecture, the SME can be leveraged as a generic SMOS, handling service management and exposure for any SMOSs within SMO. The SME SMOS provides a set of common SMO capabilities that are needed for all SMO Services.
-
-The SME SMOS offers the following capabilities:
-
-- Service registration,
-- Service discovery,
-- Authentication and authorization to access a service,
-- Communication support (e.g. service mesh) between Service Producers and Service Consumers,
-- Bootstrap of new Service consumers and Service Producers (determination of the endpoints for the SME services) (optional),
-- Heartbeat of Service producers (optional).
-
-The role of one, or both, of Service Producer and Service Consumer can be assumed by any SMOF or rApp in the SMO. The services are registered individually. The Service Consumers can also be external to the SMO, for the services made discoverable and exposed also to the external SMO consumers.
-
-### 4.2.3 Data Management and Exposure (DME) SMOS description
-
-The DME SMOS provides capabilities that allow Data Consumers, as defined in the Non-RT RIC Architecture specification [i.1], to discover data types and to consume collected data, and allow Data Producers, as defined in the Non-RT RIC Architecture specification [i.1], to register data types and to produce data for collection. The DME services can handle any registered data types and expose them for discovery and consumption to Data Consumers. In the Non-RT RIC Architecture specification [i.1] clause 3.2, both the Data Producer and Data Consumer are restricted to refer only to rApps, because the scope of [i.1] is the R1 interface between rApps and the SMO/Non-RT RIC framework.
-
-This is extended in a decoupled service-based SMO architecture, where the DME SMOS can be leveraged as an enabler handling any SMOS data types, therefore any SMOF can also be a Data Producer and/or a Data Consumer which can benefit from using DME SMOS to register, produce, discover and consume data.
-
-The role of one, or both, of Data Producer and Data Consumer can be assumed by any SMOF and rApp (for the data types related to each SMOS and/or rApp) in the SMO. The SMO Data Consumers can also be external SMO consumers, for the data made discoverable and allowed to be exposed to the external SMO consumers.
-
-### 4.2.4 RAN NF OAM SMOS description
-
-The RAN NF OAM SMOS includes, but is not limited to, the following set of capabilities:
-
-- Provisioning Management, including bulk and basic synchronous and asynchronous configuration management CRUD (create, read, update, delete) operations, CM notifications and model exposure.
-- Fault Supervision Management, including alarm subscription, notification, clearing, acknowledgement, and query
-- Performance Management, including PM counter initiation and supervision
-- Trace Management, including trace initiation and supervision
-- Streaming Data Reporting, including stream collection and stream exposure.
-- File Data Reporting, including file collection and file exposure.
-- PNF software and hardware management.
-- NF Log data collection and exposure.
-
-RAN NF OAM capabilities are exposed to consumers via SME and DME.
-
-The RAN NF OAM capabilities also provide mechanisms to allow their service consumers to scope the target of their requests (e.g., to entire RAN, to specific areas, NFs, cells, etc.), allowing the request to be applied to either a single target or multiple targets at once.
-
-### 4.2.5 Network Function Orchestrator SMOS description
-
-The Network Function Orchestrator (NFO) SMOS includes capabilities for the orchestration of the NF Deployments that constitute the Cloudified NFs. This includes the initial deployment of the software and any subsequent lifecycle management actions necessary on the respective NF Deployments instances, such as healing, updates, scaling, software upgrades, termination, etc.
-
-The NFO SMOS leverages the NF Deployment management services provided by the O-Clouds, each exposing O2dms services over the O2 interface, for deployment and lifecycle management of NF Deployment instances.
-
-The NFO SMOS interacts with the DMS by means of specified O2dms profiles:
-
-- The ETSI NFV O2dms profile [5], which is based on the ETSI GS-NFV SOL 003 protocol specification [11]
-- The Kubernetes O2dms profile [6], which is based on the Kubernetes API protocol specification
-
-The NFO SMOS also provide capabilities for:
-
-- Monitoring the execution status of lifecycle operations/requests that the NFO has been requested to execute
-- Querying to understand which O-Cloud node cluster an NF Deployment is deployed on
-- Secure handling of sensitive NF Deployment configuration data
-
-NFO SMOS capabilities are exposed to consumers via SME and DME.
-
-NOTE: The capability of the NFO is introduced from a logical perspective in the O-RAN Working Group 6 O2 Interface General Aspects and Principles specification [2] and the use cases are described in the O-RAN WG6 Cloudification and Orchestration Use Cases and Requirements specification [3].
-
-### 4.2.6 Federated O-Cloud Orchestration and Management (FOCOM) SMOS description
-
-The Federated O-Cloud Orchestration and Management (FOCOM) SMOS includes capabilities for orchestration of cluster and infrastructure resources in one or several O-Clouds. It includes, but is not limited to, the following capabilities:
-
-- Querying and discovery of O-Cloud infrastructure inventory information such as O-Cloud Sites, physical and logical infrastructure resources, Node Clusters, Deployment Managers and O-Cloud Template information.
-- Subscription for notifications related to changes in O-Cloud infrastructure inventory information.
-- Provisioning (create, update, delete) of cluster and infrastructure resources in each O-Cloud.
-- Monitoring of cluster and infrastructure resources in each O-Cloud.
-
-The FOCOM SMOS exposes O-Cloud infrastructure inventory information that is acquired from the O-Cloud O2ims inventory service. The FOCOM SMOS enables the service consumer to subscribe for notifications related to particular O-Cloud resource types.
-
-FOCOM SMOS capabilities are exposed to consumers via SME and DME.
-
-NOTE: The functionality of FOCOM is introduced from a logical perspective in the O-RAN Working Group 6 O2 Interface General Aspects and Principles specification [2] and the use cases are described in the O-RAN WG6 Cloudification and Orchestration Use Cases and Requirements specification [3].
-
-### 4.2.7 Service and Slice Subnet Orchestration SMOS (SO SMOS) description
-
-The SO SMOS includes capabilities to perform the orchestration of a RAN service and/or slice subnet. This includes both the orchestration of the fulfilment of the RAN service or the RAN slice subnet, and orchestration support for the actuation of an assurance process. The behaviour of the SO SMOS is dependent on both the SO requests that it receives and the related artifacts to support the requests. The exact definition of the RAN service is defined by the operator using the SMO, it can be generally considered as a logical concept that represents the capability for the RAN within a certain geographic area, to provide UEs the ability to have voice and/or data connectivity to the core, with requested characteristics. This includes the RAN slice subnet. In order to execute on its responsibilities, the SO SMOS consumes other services including the RAN NF OAM SMOS for configuration, the FOCOM SMOS for infrastructure management requests, the NFO for deployment requests, as well as services produced by rApps, etc.
-
-The SO SMOS includes the following capabilities:
-
-- Oversees and automates the fulfillment of a service or a slice subnet order, received directly or via a higher-level orchestrator, according to the information contained in the service or a slice subnet order and the related artifacts, utilizing the services provided by SMOFs (such as SMOFs supporting RAN NF OAM SMOS for configuration, NFO SMOS for NF Deployment [2] LCM, etc.) and services produced by rApps.
-- Coordinates the orchestration of lifecycle and service or the slice subnet-related configuration for one or more RAN NFs (also including multiple NF Deployments), including taking the homing decision considering both the RAN service or the slice subnet, and application-level requirements as well as the non-functional requirements e.g., infrastructure capabilities needed as well as the transport networks used to interconnect the O-RAN NFs (and NF Deployments) and O-RUs when they are deployed over different sites in order to meet the connectivity requirements for the RAN service or the slice subnet. This can include generating the required configuration used when requesting (via the appropriate SMOS) the configuration of the RAN NFs.
-- Coordination of the NFs transport connectivity: based on requirements and objectives obtained on RAN NF connectivity it requests the suitable transport networks management domain to fulfil the requirements of the RAN service and/or slice subnet requirements.
-- Based on the infrastructure requirements of the O-RAN NF Deployments, it orchestrates the necessary management actions to the O-Cloud infrastructure, by coordinating with FOCOM SMOS producer for the needed O-Cloud management requests.
-
-SO SMOS capabilities are exposed to consumers via SME and DME.
-
-### 4.2.8 Service and Slice Subnet Assurance SMOS (SA SMOS) description
-
-The SA SMOS includes capabilities to ensure the required assurance for the RAN services and slice subnets. The behaviour of SA SMOS is dependent upon the related artifacts to support the request. It consumes the services provided by other SMOS Producers and can delegate responsibilities to rApps according to its configuration.
-
-The SA SMOS includes the following capabilities:
-
-- Assures the intended state (together with rApps and/or other SMOSs) of the RAN services and slice subnets.
-- It monitors/observes the data that is relevant (produced by other SMOS producers and/or services produced by rApps) to assessing the current RAN service, and/or RAN slice subnet characteristics against the service requirements.
-- In case the RAN service and/or RAN slice subnet requirements are not met, decisions are taken (together with rApps and/or other SMOSs) on a course of remedial actions.
-- The identified actions (e.g., configuration changes, scaling, changes of connectivity, etc.) are executed (by making requests to rApps and/or other SMOSs producers), as part of an open or closed automation loop.
-
-- In the case that the service or slice subnet requirements cannot be met, the service assurance will escalate to the operator and/or northbound systems.
-
-SA SMOS capabilities are exposed to consumers via SME and DME.
-
-### 4.2.9 rApp Management SMOS description
-
-The rApp management SMOS includes the following set of capabilities:
-
-- rApp lifecycle management, including rApp deployment, rApp upgrade and rApp termination.
-- rApp configuration management, which enables management of the rApp instance configuration settings.
-- rApp fault management, which enables an rApp instance to report faults that are related to the rApp itself or to its communication with other entities.
-- rApp performance management, which enables an rApp instance to report on the performance of the rApp itself or to its communication with other entities.
-- rApp logging, which enables an rApp instance to generate and report timestamped logs, including audit trail records of its configuration actions within the network.
-
-rApp management SMOS capabilities are exposed to consumers via SME and DME.
-
-NOTE 1: An rApp instance is a specific occurrence of an rApp as defined in [1].
-
-NOTE 2: rApp package on-boarding is a prerequisite for executing the capabilities of the rApp management SMOS. The rApp package on-boarding is not in scope of this SMOS.
-
-For further details see O-RAN TS: Non-RT RIC Architecture [4].
-
-### 4.2.10 Topology Exposure and Inventory SMOS description
-
-The Topology Exposure and Inventory (TE&IV) SMOS includes, but is not limited to, the following capabilities:
-
-- Creating, updating and deleting information about TE&IV resources and the relationships between them
-- Querying to obtain information about the TE&IV resources and the relationships between them, using filter criteria such as TE&IV resource types and/or geo-location data
-- Subscribing for notifications of changes to TE&IV resource information
-
-TE&IV resources include both RAN resources and O-Cloud resources. For further details see O-RAN TS: O-RAN Topology Exposure and Inventory Management Services Use Cases and Requirements [7].
-
-Topology Exposure and Inventory SMOS capabilities are exposed to consumers via SME and DME.
-
-### 4.2.11 Software Package Onboarding SMOS description
-
-The Software Package Onboarding SMOS includes, but is not limited to, the following capabilities:
-
-- Onboarding of software packages to the SMO
-- Validation of software packages to ensure that their format and contents can be understood by the SMO
-- Security verification of the software package contents
-- Extraction of artifacts contained in the software package and making them available to other SMOSs for consumption
-- Deletion of software packages from the SMO
-
-- Querying the list of onboarded software packages
-
-Software packages supported by the Software Package Onboarding SMOS include O-RAN NFs (as defined in the O-RAN Operations and Maintenance Architecture [8]), rApps and xApps.
-
-Software Package Onboarding SMOS capabilities are exposed to consumers via SME and DME.
-
-For further details see O-RAN TS: O-RAN Onboarding SMOS General Aspects and Principles [9].
-
-### 4.2.12 A1 Related SMOS description
-
-The A1 Related SMOS includes, but is not limited to, the following capabilities:
-
-- Support for management of A1 policies, including discovery of A1 policies and A1 policy types available in Near-RT RICs, as well as creation, querying, updating, and deletion of A1 policies, querying the enforcement status of A1 policies, and subscribing for event notifications related to A1 policies and A1 policy types.
-- Support for A1 Enrichment Information (EI), including registration and deregistration of EI types.
-- Support for discovering AI/ML model training capabilities exposed by Near-RT RICs, and requesting AI/ML model training and status of training jobs.
-
-The capabilities of the A1 Related SMOS are exposed to consumers via SME.
-
-For further details on the A1 interface see O-RAN TS: O-RAN A1 interface: General Aspects and Principles [10].
-
-## 4.3 SMO in consumer role of southbound interfaces
-
-The SMO consumes services offered by other O-RAN architecture elements through the following O-RAN defined southbound interfaces:
-
-- The O1 interface, for which the service consumer in the SMO is the RAN NF OAM SMOS Producer.
-- The Open Fronthaul M-Plane interface, for which the service consumer in the SMO in the hybrid model is the RAN NF OAM SMOS Producer.
-- The O2 interface, for which the service consumer in the SMO is the FOCOM SMOS Producer for O2ims services, and the NFO SMOS Producer for O2dms services.
-- The A1 interface, for which the service consumer in the SMO is the A1 Related SMOS Producer.
-
-## 4.4 Northbound external exposure of SMO Services
-
-Editor's Note: introduce the external northbound SMO exposure.
-
-## 4.5 Extending the SMO services
-
-Editor's Note: address how new services/capabilities can be added in the SMO.
-
-## 4.6 SMO Functions
-
-### 4.6.1 Introduction
-
-Editor's Note: introduce SMOFs as combos of one or more SMOS Producers.
-
-### 4.6.2 Non-RT RIC SMOF
-
-Editor's Note: clarify Non-RT RIC SMOF role within SMO.
-
-## 4.7 Intent-driven RAN management
-
-Intents describe desired objectives for RAN management (goals, requirements, and constraints) without specifying how to achieve them. In SMO, intent-driven RAN management services can be made accessible to authorized consumers. SMO intent capabilities are exposed by associated SMOS producers and by rApps.
-
-RMIO and RMIH refer to two distinct roles in intent-driven RAN management. An RMIO has objectives it needs the RAN network to meet. It is using intent to express these objectives and provide them to the respective service producers. Therefore, RMIOs are the sources of intent. If needed the RMIO can also modify or delete its intents.
-
-The role of a service producer that receives objectives through intents from one or multiple RMIOs and fulfils and assures these objectives is referred to as RMIH. Furthermore, an RMIH provides intent reports to RMIOs informing them about the fulfilment status details regarding their intent. RMIOs determines the properties of intent report sending. This includes, for example, the frequency of report sending and the content of the intent reports.
-
-Within SMO, suitable SMOS producers can assume the role of RMIH and/or RMIO and become producers and/or consumers of intent capabilities. Examples include SO and SA SMOS producer(s) and rApps.
-
-Multiple entities within the SMO can assume the RMIH role and produce intent capabilities. Individual RMIHs typically produce a unique subset of possible intent capabilities. They expose their capabilities through SME. Through the exposed RMIH intent capabilities, authorized RMIOs can discover a suitable RMIH for the objectives they want to provide with intent.
-
-A common mechanism for exposure of intent capabilities, the expression of objectives with intent, the life-cycle management of the intent, the subscription to intent reports, and the expression of intent reports is used across all SMOSs that specify intent capabilities. Within this common mechanism the specification of a SMOS can define SMOS-specific intent capabilities.
-
-External SMO service consumers can only act as RMIO. No use cases have been identified where an RMIO within the SMO would provide intent to an external RMIH.
-
-Figure 4.7-1 below shows the above-mentioned RMIO/RMIH placement options.
-
-
-
-Architecture diagram showing intent handling capabilities producer/consumer placement options within an SMO framework. It includes components like External data consumers, SMOS Producer/Consumer (RMIO), Data Management and Exposure (DME), Service Management and Exposure (SME), and an Example Non-RT RIC SMOF containing rApps and rApp Management. A legend at the bottom defines symbols for SMO External interface, service consumption/production, SMOS Producer, and SMOS Producer anchored in Non-RT RIC.
-
-Figure 4.7-1: Intent handling capabilities producer/consumer placement options example
-
-# Annex (informative): Change history/Change request (history)
-
-| Date | Revision | Description |
-|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 2025.07.28 | 01.00 | - First version. Includes a service-based SMO architecture diagram and descriptions of SMOSs (SMO Services) in the SMO.
- Describes SMOS Communications, R1 interface and R1 termination, and support for external service/data producers and/or consumers.
|
-| 2025.11.19 | 02.00 | - Adds an introduction to Intent-driven RAN management (clause 4.7)
- Updates the 'Introduction to SMO Services' in clause 4.2.1.
- Describes the SMO role as southbound interface consumer in clause 4.3
|
\ No newline at end of file
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
deleted file mode 100644
index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4041da71c3f65eef413dcad3172bba4a50fb3f8c94dfe0031d165cdb81b5f91a
-size 4518
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
deleted file mode 100644
index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4041da71c3f65eef413dcad3172bba4a50fb3f8c94dfe0031d165cdb81b5f91a
-size 4518
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
deleted file mode 100644
index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:4041da71c3f65eef413dcad3172bba4a50fb3f8c94dfe0031d165cdb81b5f91a
-size 4518
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/a7d78d22e465dea388b31d0739f9d0cd_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/a7d78d22e465dea388b31d0739f9d0cd_img.jpg
deleted file mode 100644
index 7a90f3629144246441bac585df6f37811295393b..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/a7d78d22e465dea388b31d0739f9d0cd_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:1efef2cf0d4f3c1009aa1556edebddde34a2229283d7b7ea78bf83175025680a
-size 122101
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
deleted file mode 100644
index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:a55cf057add81bac5208e738578b06871feea626854066f7ee84fdb6fc13c319
-size 4529
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
deleted file mode 100644
index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:e38483cbf6d1bdd04438a1570335a80b7de97cc9a175d47bbc542bb5456e4bb3
-size 4563
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
deleted file mode 100644
index 45ed1e5f61f869df0f884633f15da046e14c39e7..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:c63966b771ac5e988471c0e22d0aa67f8581c2c72d9600a55be7616d6b9a664f
-size 81697
diff --git a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
deleted file mode 100644
index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.SMO-ARCH-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:bc3238cb8249e044e431352b85e73b297352925b914edc60af73d8011b6efe53
-size 4542
diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/doc.md b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/doc.md
deleted file mode 100644
index d3bfa67a4161e033c66fc9e1a865dbcc582f0edf..0000000000000000000000000000000000000000
--- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/doc.md
+++ /dev/null
@@ -1,15966 +0,0 @@
-
-
-# --- **O-RAN Work Group 1 (Use Cases and Overall Architecture)**
-
-## **Use Cases Detailed Specification**
-
-Copyright © 2026 by the O-RAN ALLIANCE e.V.
-
-The copying or incorporation into any other work of part or all of the material available in this specification in any form without the prior written permission of O-RAN ALLIANCE e.V. is prohibited, save that you may print or download extracts of the material of this specification for your personal use, or copy the material of this specification for the purpose of sending to individual third parties for their information provided that you acknowledge O-RAN ALLIANCE as the source of the material and that you inform the third party that these conditions apply to them and that they must comply with them.
-
-O-RAN ALLIANCE e.V., Buschkaueler Weg 27, 53347 Alfter, Germany
-Register of Associations, Bonn VR 11238, VAT ID DE321720189
-
-# Contents
-
-| | |
-|-------------------------------------------------------------------|----|
-| Foreword..... | 5 |
-| Modal verbs terminology ..... | 5 |
-| Introduction ..... | 5 |
-| 1 Scope..... | 6 |
-| 2 References..... | 6 |
-| 2.1 Normative references..... | 6 |
-| 2.2 Informative references ..... | 8 |
-| 3 Definition of terms, symbols and abbreviations..... | 9 |
-| 3.1 Terms..... | 9 |
-| 3.2 Symbols ..... | 10 |
-| 3.3 Abbreviations..... | 10 |
-| 4 Use cases ..... | 11 |
-| 4.1 Context-based dynamic HO management for V2X ..... | 11 |
-| 4.1.1 Background and goal of the use case ..... | 12 |
-| 4.1.2 Entities/resources involved in the use case ..... | 12 |
-| 4.1.3 Solutions..... | 12 |
-| 4.1.4 Required data ..... | 16 |
-| 4.2 Flight path based dynamic UAV radio resource allocation ..... | 16 |
-| 4.2.1 Background and goal of the use case ..... | 16 |
-| 4.2.2 Entities/resources involved in the use case ..... | 17 |
-| 4.2.3 Solutions..... | 18 |
-| 4.2.4 Required data ..... | 20 |
-| 4.3 Radio resource allocation for UAV application scenario..... | 21 |
-| 4.3.1 Background and goal of the use case ..... | 21 |
-| 4.3.2 Entities/resources involved in the use case ..... | 22 |
-| 4.3.3 Solutions..... | 23 |
-| 4.3.4 Required data ..... | 25 |
-| 4.4 QoE optimization..... | 25 |
-| 4.4.1 Background and goal of the use case ..... | 25 |
-| 4.4.2 Entities/resources involved in the use case ..... | 26 |
-| 4.4.3 Solutions..... | 26 |
-| 4.4.4 Required data ..... | 35 |
-| 4.5 Traffic steering..... | 36 |
-| 4.5.1 Background and goal of the use case ..... | 36 |
-| 4.5.2 Entities/resources involved in the use case ..... | 37 |
-| 4.5.3 Solutions..... | 37 |
-| 4.5.4 Required data ..... | 46 |
-| 4.6 Massive MIMO optimization..... | 47 |
-| 4.6.1 Background and goal of the use case ..... | 47 |
-| 4.6.2 Entities/resources involved in the use case ..... | 48 |
-| 4.6.3 Solutions..... | 50 |
-| 4.6.4 Required data ..... | 61 |
-| 4.7 RAN sharing ..... | 64 |
-| 4.7.1 Background and goal of the use case ..... | 64 |
-| 4.7.2 Entities/resources involved in the use case ..... | 65 |
-| 4.7.3 Solutions..... | 66 |
-| 4.7.4 Required data ..... | 71 |
-| 4.8 QoS based resource optimization..... | 72 |
-| 4.8.1 Background and goal of the use case ..... | 72 |
-| 4.8.2 Entities/resources involved in the use case ..... | 72 |
-| 4.8.3 Solutions..... | 73 |
-| 4.8.4 Required data ..... | 76 |
-| 4.9 RAN slice SLA assurance..... | 76 |
-| 4.9.1 Background and goal of the use case ..... | 77 |
-
-- 4.9.2 Entities/resources involved in the use case ..... 77
-- 4.9.3 Solutions..... 77
-- 4.9.4 Required data ..... 88
-- 4.10 Multi-vendor slices ..... 91
- - 4.10.1 Background and goal of the use case ..... 91
- - 4.10.2 Entities/resources involved in the use case ..... 92
- - 4.10.3 Solutions..... 92
- - 4.10.4 Required data ..... 107
-- 4.11 Dynamic spectrum sharing (DSS) ..... 108
- - 4.11.1 Background and goal of the use case ..... 108
- - 4.11.2 Entities/resources involved in the use case ..... 110
- - 4.11.3 Solutions..... 110
- - 4.11.4 Required data ..... 114
-- 4.12 NSSI resource allocation optimization ..... 116
- - 4.12.1 Background and goal of the use case ..... 116
- - 4.12.2 Entities/resources involved in the use case ..... 118
- - 4.12.3 Solutions..... 118
- - 4.12.4 Required data ..... 121
-- 4.13 Local indoor positioning in RAN ..... 122
- - 4.13.1 Background and goal of the use case ..... 122
- - 4.13.2 Entities/resources involved in the use case ..... 122
- - 4.13.3 Solutions..... 123
- - 4.13.4 Required data ..... 125
-- 4.14 Massive SU/MU-MIMO grouping optimization ..... 126
-- 4.15 O-RAN signalling storm protection ..... 126
- - 4.15.1 Background and goal of the use case ..... 126
- - 4.15.2 Entities/resources involved in the use case ..... 127
- - 4.15.3 Solutions..... 127
- - 4.15.4 Required data ..... 138
-- 4.16 Congestion prediction and management ..... 138
-- 4.17 Industrial IoT optimization ..... 139
-- 4.18 BBU pooling to achieve RAN elasticity ..... 139
-- 4.19 Integrated SON function within the O-RAN framework ..... 139
- - 4.19.1 Background and goal of the use case. .... 139
- - 4.19.2 Entities/resources involved in the use case ..... 140
- - 4.19.3 Solutions..... 142
- - 4.19.4 Required data ..... 160
-- 4.20 Shared O-RU ..... 161
- - 4.20.1 Background and goal of the use case ..... 161
- - 4.20.2 Entity/resources involved in the use case..... 172
- - 4.20.3 Solution ..... 180
- - 4.20.4 Required data ..... 331
-- 4.21 Network energy saving ..... 333
- - 4.21.1 Background and goal of the use case ..... 333
- - 4.21.2 Entities/resources involved in the use case ..... 334
- - 4.21.3 Solutions..... 335
- - 4.21.4 Required data ..... 385
-- 4.22 MU-MIMO optimization ..... 404
- - 4.22.1 Background and goal of the use case ..... 404
- - 4.22.2 Entities/resources involved in the use case ..... 404
- - 4.22.3 Solutions..... 405
- - 4.22.4 Required data ..... 407
-- 4.23 Sharing Non-RT RIC data with the core..... 408
-- 4.24 Industrial vision SLA assurance ..... 408
- - 4.24.1 Background and goal of the use case ..... 408
- - 4.24.2 Entities/resources involved in the use case ..... 409
- - 4.24.3 Solutions..... 409
- - 4.24.4 Required data ..... 412
-- 4.25 Void ..... 413
-- 4.26 Interference detection, prediction and optimization..... 413
- - 4.26.1 Background and goal of the use case ..... 413
-
-| | | |
-|------------------------|------------------------------------------------------------|-----|
-| 4.26.2 | Entities/resources involved in the use case ..... | 413 |
-| 4.26.3 | Solutions..... | 414 |
-| 4.26.4 | Required data ..... | 431 |
-| 4.27 | Communication and computing integrated networks ..... | 432 |
-| 4.27.1 | Background and goal of the use case ..... | 432 |
-| 4.27.2 | Entities/resources involved in the use case ..... | 436 |
-| 4.27.3 | Solutions..... | 438 |
-| 4.27.4 | Required data ..... | 447 |
-| 4.28 | RAN intent-driven management services ..... | 450 |
-| 4.28.1 | Background and goal of the use case ..... | 450 |
-| 4.28.2 | Entities/resources involved in the use case ..... | 451 |
-| 4.28.3 | Solutions..... | 451 |
-| 4.28.4 | Required data ..... | 456 |
-| Annex A (informative): | Additional information ..... | 457 |
-| A.1 | Traffic steering use case A1 interface usage example ..... | 457 |
-| Annex (informative): | Change history/Change request (history) ..... | 459 |
-
-# Foreword
-
-This Technical Specification (TS) has been produced by WG1 of the O-RAN ALLIANCE.
-
-The content of the present document is subject to continuing work within O-RAN and may change following formal O-RAN approval. Should the O-RAN ALLIANCE modify the contents of the present document, it will be re-released by O-RAN with an identifying change of version date and an increase in version number as follows:
-
-version xx.yy.zz
-
-where:
-
-- xx: the first digit-group is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have xx=01). Always 2 digits with leading zero if needed.
-- yy: the second digit-group is incremented when editorial only changes have been incorporated in the document. Always 2 digits with leading zero if needed.
-- zz: the third digit-group included only in working versions of the document indicating incremental changes during the editing process. External versions never include the third digit-group. Always 2 digits with leading zero if needed.
-
-# Modal verbs terminology
-
-In the present document "**shall**", "**shall not**", "**should**", "**should not**", "**may**", "**need not**", "**will**", "**will not**", "**can**" and "**cannot**" are to be interpreted as described in clause 3.2 of the O-RAN Drafting Rules (Verbal forms for the expression of provisions).
-
-"**must**" and "**must not**" are **NOT** allowed in O-RAN deliverables except when used in direct citation.
-
-# Introduction
-
-This document provides O-RAN WG1 detailed use case descriptions. Any multi-WG use case defined in O-RAN is expected to be documented in “O-RAN WG1 Use Case Analysis Report” and if the use case is to be studied further, it will be covered in this document in detail, and then in relevant WGs.
-
-# 1 Scope
-
-The present document specifies the top-level use cases as defined by O-RAN WG1 UCTG (Use Case Task Group). For each use case, the document describes the motivation, resources, steps involved, and the data requirements. These top-level use cases are further detailed in relevant WGs along with the requirements for O-RAN components and their interfaces.
-
-# 2 References
-
-## 2.1 Normative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are necessary for the application of the present document.
-
-- [1] 3GPP TS 22.261: “Service requirements for the 5G system; Stage 1”
-- [2] 3GPP TS 23.501: “System architecture for the 5G System (5GS); Stage 2”
-- [3] Void
-- [4] 3GPP TS 28.530: “Management and orchestration; Concepts, use cases and requirements”
-- [5] 3GPP TS 28.541: “Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3”
-- [6] 3GPP TS 28.552: “Management and orchestration; 5G performance measurements”
-- [7] 3GPP TS 28.554: “Management and orchestration; 5G end to end Key Performance Indicators (KPI)”
-- [8] 3GPP TS 28.622: “Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)”
-- [9] 3GPP TS 28.624: “Telecommunication management; State management data definition Integration Reference Point (IRP); Requirements”
-- [10] 3GPP TS 28.625: “Telecommunication management; State Management Data Definition Integration Reference Point (IRP); Information Service (IS)”
-- [11] 3GPP TS 28.626: “Telecommunication management; State management data definition Integration Reference Point (IRP); Solution Set (SS) definitions”
-- [12] 3GPP TS 37.340: “Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage 2”
-- [13] 3GPP TS 38.211: “NR; Physical channels and modulation”
-- [14] 3GPP TS 38.213: “NR; Physical layer procedures for control”
-
-- [15] ETSI EN 302 637-2: “Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service”, Release 1, November 2010
-- [16] ETSI EN 302 637-3: “Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service”, Release 1, November 2014
-- [17] GSMA NG.116: “Generic Network Slice Template”, Version 2.0, October 2019
-- [18] ITU-T X.731: “Information technology - Open Systems Interconnection - Systems management: State management function”
-- [19] RFC 8348: “A YANG Data Model for Hardware Management”
-- [20] 3GPP TS 28.313: “Management and orchestration; Self-Organizing Networks (SON) for 5G networks”
-- [21] 3GPP TS 28.532: “Management and orchestration; Generic management services”
-- [22] 3GPP TS 23.502: “Procedures for the 5G System (5GS); Stage 2”
-- [23] ETSI GS NFV IFA013: “Management and Orchestration; Os-Ma-nfvo reference point - Interface and Information Model Specification”, v4.4.1, Release 4, March 2023
-- [24] ETSI GS NFV IFA008: “Management and Orchestration; Ve-Vnfm reference point - Interface and Information Model Specification”, v4.3.1, Release 4, May 2022
-- [25] O-RAN WG5.O-DU-O1: “O1 Interface specification for O-DU”, Version R003-V09, December 9, 2023
-- [26] O-RAN.WG6.ORCH-USE-CASES: “Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN”
-- [27] O-RAN.WG10.OAM-Architecture: “O-RAN Working Group 10, O-RAN Operations and Maintenance Architecture”
-- [28] O-RAN.WG4.MP: “O-RAN Working Group 4 (Open Fronthaul Interfaces WG), Management Plane Specification”
-- [29] O-RAN.WG4.CUS.0-v02.00: “O-RAN Fronthaul Working Group, Control, User and Synchronization Plane Specification”
-- [30] 3GPP TS 36.423: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP)”
-- [31] 3GPP TS 36.314: “Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 – Measurements”
-- [32] 3GPP TS 38.314: “NR; Layer 2 Measurements”
-- [33] 3GPP TS 32.425: “Telecommunication management; Performance Management (PM); Performance measurements; Evolved Universal Terrestrial Radio Access Network (E-UTRAN)”
-- [34] 3GPP TS 36.300: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2”
-- [35] 3GPP TS 23.401: “General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access”
-- [36] 3GPP TS 23.203: “Policy and charging control architecture”
-- [37] 3GPP TS 36.214: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements”
-
-- [38] 3GPP TS 36.331: “Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification”
-- [39] O-RAN.WG11.TS.Security-Requirements-Specification.0-R004-v11.00: “Security Requirements and Controls Specifications”
-- [40] 3GPP TS 28.623: “Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions”
-- [41] 3GPP TS 28.662: “Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)”
-- [42] O-RAN.WG6.TS.O-CLOUD-IM: “O-RAN Work Group 6 (Cloudification and Orchestration Workgroup), O-Cloud Information Model”
-- [43] 3GPP TS 28.310: “Management and orchestration; Energy efficiency of 5G”, V19.1.0 (2025-06)
-- [44] O-RAN.WG10.TS.O1-Interface: “O-RAN O1 Interface Specification”
-- [45] O-RAN.WG10.TS.O1NRM: “O1 Network Resource Model”
-- [46] O-RAN.WG3.TS.UCR-R004: “Use Cases and Requirements”
-- [47] O-RAN.WG3.TS.E2SM-CCC: “E2 Service Model (E2SM) Cell Configuration and Control”
-- [48] O-RAN.WG10.TS.O1PMeas: “O-RAN O1 Performance Measurements Specification”
-- [49] O-RAN.WG3.TS.E2SM-KPM: “E2 Service Model (E2SM) KPM”
-- [50] O-RAN.WG2.TS.Use-Case-Requirements-R004: “Non-RT RIC & A1/R1 interface: Use Cases and Requirements”
-- [51] O-RAN.WG4.TS.CUS.0-R004: “Control, User and Synchronization Plane Specification”
-- [52] 3GPP TS 28.558: “Management and orchestration; UE level measurements for 5G system”
-
-## 2.2 Informative references
-
-References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release 18, or the latest 3GPP release prior to Release 18 that includes that document.
-
-NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long-term validity.
-
-The following referenced documents are not necessary for the application of the present document, but they assist the user with regard to a particular subject area.
-
-- [i.1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”
-- [i.2] 3GPP TR 37.817: “Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Study on enhancement for Data Collection for NR and EN-DC”
-- [i.3] 3GPP TR 38.889: “Study on NR-based access to unlicensed spectrum”
-- [i.4] 3GPP TR 38.913: “Study on Scenarios and Requirements for Next Generation Access Technologies”
-- [i.5] ETSI ES 203 228: “Environmental Engineering (EE); Assessment of mobile network energy efficiency”, V1.3.1, October 2020
-- [i.6] Chih-Lin I, Guanding Yu, Shuangfeng Han, Geoffrey Ye Li, “Green and Software-defined Wireless Networks: From Theory to Practice”, Cambridge University Press, 2019
-
-- [i.7] ETSI White Paper No. 54, “Evolving NFV towards the next decade”, May, 2023
-- [i.8] ETSI GS MEC 003: “Multi-access Edge Computing (MEC); Framework and Reference Architecture”
-- [i.9] ITU-T Y.IMT2020-CNC-req, Recommendation, “Requirements of coordination of computing and networking for IMT-2020 and beyond”
-- [i.10] 3GPP TS 28.538: “Management and orchestration; Edge Computing Management (ECM)”
-- [i.11]
-- [i.12] 3GPP TS 22.186: “Enhancement of 3GPP support for V2X scenarios; Stage 1”
-- [i.13] 3GPP TR 26.928: “Extended Reality (XR) in 5G”
-- [i.14] 3GPP TR 38.885: “NR; Study on NR Vehicle-to-Everything (V2X)”
-- [i.15] 3GPP TS 28.312: “Management and orchestration; Intent driven management services for mobile networks”
-- [i.16] TMF921: “Intent Management API User Guide v5.0.0”
-
-# --- 3 Definition of terms, symbols and abbreviations
-
-## 3.1 Terms
-
-For the purposes of the present document, the terms and definitions [given in [i.1] and the following] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in [i.1].
-
-**A1:** Interface between Non-RT RIC and Near-RT RIC to enable policy-driven guidance of Near-RT RIC applications/functions, and support AI/ML workflow.
-
-**A1 policy:** Type of declarative policies expressed using formal statements that enable the Non-RT RIC function in the SMO to guide the Near-RT RIC function, and hence the RAN, towards better fulfilment of the RAN intent.
-
-**A1 enrichment information:** Information utilized by Near-RT RIC that is collected or derived at SMO/Non-RT RIC either from non-network data sources or from network functions themselves.
-
-**E2:** Interface connecting the Near-RT RIC and one or more O-CU-CPs, one or more O-CU-UPs, and one or more O-DUs.
-
-**E2 node:** A logical node terminating E2 interface. In the present document, O-RAN nodes terminating E2 interface are:
-
-- for NR access: O-CU-CP, O-CU-UP, O-DU or any combination.
-- for E-UTRA access: O-eNB.
-
-**FCAPS:** Fault, Configuration, Accounting, Performance, Security.
-
-**Intent:** Formal specification of all requirements including goals and constraints given to a system.
-
-NOTE: This definition aligns with the definitions in 3GPP TS 28.312 [i.15], clause 3.1. and TMF921 [i.16].
-
-**Intents:** A declarative policy to steer or guide the behavior of RAN functions, allowing the RAN function to calculate the optimal result to achieve stated objective.
-
-**Near-RT RIC:** O-RAN Near-Real-Time RAN Intelligent Controller: A logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained data collection and actions over E2 interface.
-
-**Non-RT RIC:** O-RAN Non-Real-Time RAN Intelligent Controller: A logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in Near-RT RIC.
-
-**O-CU:** O-RAN Central Unit: A logical node hosting O-CU-CP and O-CU-UP.
-
-**O-CU-CP:** O-RAN Central Unit – Control Plane: A logical node hosting the RRC and the control plane part of the PDCP protocol.
-
-**O-CU-UP:** O-RAN Central Unit – User Plane: A logical node hosting the user plane part of the PDCP protocol and the SDAP protocol.
-
-**O-DU:** O-RAN Distributed Unit: A logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.
-
-**O-RU:** O-RAN Radio Unit: A logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP's "TRP" or "RRH" but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction).
-
-**O1:** Interface between management entities (SMO/EMS/MANO) and O-RAN managed elements, for operation and management, by which FCAPS management, software management, file management can be achieved.
-
-**O2:** Interface between management entities and the O-Cloud for supporting O-RAN virtual network functions.
-
-**RAN:** Generally referred as Radio Access Network. In terms of this document, any component below Near-RT RIC per O-RAN architecture, including O-CU/O-DU/O-RU.
-
-**RAN management intent handler:** An authorized SMO service producer which understands, can process and ensure fulfilment of RAN management intents.
-
-**RAN management intent owner:** An authorized SMO service consumer, responsible for formulating the RAN management intents as per its own goals and requirements and consuming intent-based services.
-
-**Shared O-RU:** An O-RU that is able to be configured to operate with one or more O-DUs operated by one or more mobile network operators.
-
-## 3.2 Symbols
-
-Void
-
-## 3.3 Abbreviations
-
-For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in [i.1].
-
-| | |
-|-------|--------------------------------------------------|
-| AI/ML | Artificial Intelligence/Machine Learning |
-| AISG | Antenna Interface Standards Group |
-| CAM | Cooperative Awareness Message |
-| DENM | Decentralized Environmental Notification Message |
-| eNB | eNodeB (applies to LTE) |
-| gNB | gNodeB (applies to NR) |
-
-| | |
-|-------|-----------------------------------------|
-| KPI | Key Performance Indicator |
-| MIMO | Multiple Input, Multiple Output |
-| mTLS | Multiplexed Transport Layer Security |
-| NACM | NETCONF Access Control Model |
-| NRT | Neighbor Relation Table |
-| O-CU | O-RAN Central Unit |
-| O-DU | O-RAN Distributed Unit |
-| O-RU | O-RAN Radio Unit |
-| PRB | Physical Resource Block |
-| QoE | Quality of Experience |
-| RAN | Radio Access Network |
-| rApps | RAN Applications |
-| RIC | O-RAN RAN Intelligent Controller |
-| RMIH | RAN Management Intent Handler |
-| RMIO | RAN Management Intent Owner |
-| SA | Service and Slice Subnet Assurance |
-| SINR | Signal-to-Interference-plus-Noise Ratio |
-| SME | Service Management and Exposure |
-| SMO | Service Management and Orchestration |
-| SMOS | SMO Service |
-| SO | Service and Slice Subnet Orchestration |
-| TLS | Transport Layer Security |
-| UAV | Unmanned Aerial Vehicle |
-| V2X | Vehicle to Everything |
-
-# --- 4 Use cases
-
-## 4.1 Context-based dynamic HO management for V2X
-
-This use case provides the background, motivation, and requirements for the context-based dynamic HO management for V2X use case, allowing operators to adjust radio resource allocation policies through the O-RAN architecture, reducing latency and improving radio resource utilization.
-
-### 4.1.1 Background and goal of the use case
-
-V2X communication allows for numerous potential benefits such as increasing the overall road safety, reducing emissions, and saving time. Part of the V2X architecture is the V2X UE (SIM + device attached to vehicle) which communicates with the V2X Application Server (V2X AS). The exchanged information comprises Cooperative Awareness Messages (CAMs), (from UE to V2X AS) [15], radio cell IDs, connection IDs, and basic radio measurements (RSRP, RSPQ, etc.)
-
-As vehicles traverse along a highway, due to their high speed and the heterogeneous natural environment V2X UEs are handed over frequently, at times in a suboptimal way, which can cause handover (HO) anomalies: e.g., short stay, ping-pong, and remote cell. Such suboptimal HO sequences substantially impair the functionality of V2X applications. Since HO sequences are mainly determined by the Neighbour Relation Tables (NRTs), maintained by the xNBs, there is hardly room for UE-level customization.
-
-This UC aims to present a method to avoid and/or resolve problematic HO scenarios by using past navigation and radio statistics in order to customize HO sequences on a UE level. To this end, the AI/ML functionality that is enabled by the Near-RT RIC is employed.
-
-### 4.1.2 Entities/resources involved in the use case
-
-- 1) Non-RT RIC:
- - a) Retrieve necessary performance, configuration, and other data for constructing/training relevant AI/ML models that will be deployed in Near-RT RIC to assist in the V2X HO management function. For example, this could be a clustering algorithm that classifies traffic situations and radio conditions that (probably) do or do not lead to HO anomalies.
- - b) Support deployment and update of AI/ML models into Near-RT RIC xApp.
- - c) Support communication of intents and policies (system-level and UE-level) from Non-RT RIC to Near-RT RIC.
- - d) Support communication of non-RAN data to enrich control functions in Near-RT RIC (enrichment data).
-- 2) Near-RT RIC:
- - a) Support update of AI/ML models retrieved from Non-RT RIC.
- - b) Support interpretation and execution of intents and policies from Non-RT RIC.
- - c) Support necessary performance, configuration, and other data for defining and updating intents and policies for tuning relevant AI/ML models.
- - d) Support communication of configuration parameters to RAN.
-- 3) RAN:
- - a) Support data collection with required granularity to SMO over O1 interface.
- - b) Support near-real-time configuration-based optimization of HO parameters over E2 interface.
- - c) Report necessary performance, configuration, and other data for performing real-time V2X HO optimization in the Near-RT RIC over E2 interface.
-- 4) V2X application server:
- - a) Support data collection with required granularity from V2X UE over V1 interface.
- - b) Support communication of real-time traffic related data about V2X UE to Non-RT RIC as enrichment data.
-
-### 4.1.3 Solutions
-
-#### 4.1.3.1 Context-based dynamic handover management for V2X
-
-The context of the context-based dynamic handover management for V2X use case is captured in table 4.1.3.1-1.
-
-**Table 4.1.3.1-1: Context-based dynamic handover management for V2X**
-
-| Use Case Stage | Evolution / Specification | <> |
-|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
-| | | Related use |
-| Goal | Drive V2X UE HOs in RAN according to defined intents, policies, and configuration while enabling AI/ML-based solutions. | |
-| Actors and Roles | Non-RT RIC: RAN policy control function.
Near-RT RIC: RAN policy enforcement function.
RAN: Policy enforcement for configuration updates.
SMO: Termination point for O1 interface.
V2X AS: Termination point for V1 interface and enrichment data provider. | |
-| Assumptions | All relevant functions and components are instantiated.
A1, O1, E2 interface connectivity is established. | |
-| Pre-conditions | Network is operational.
SMO has established the data collection and sharing process, and Non-RT RIC has access to this data.
Non-RT RIC analyzes the historical data from RAN and V2X AS for training the relevant AI/ML models to be deployed or updated in the Near-RT RIC, as well as AI/ML models required for real-time optimization of configuration and policies. | |
-| Begins when | Operator specified trigger condition or event is detected. | |
-| Step 1 (M) | Non-RT RIC deploys/updates the AI/ML model in the Near-RT RIC via O1 or Non-RT RIC assigns/update the AI/ML model for the Near-RT RIC xApp via A1. | |
-| Step 2 (M) | Non-RT RIC communicates relevant policies/intents and enrichment data to the Near-RT RIC over the A1 interface. The enrichment data from the non-RAN data can include V2X UE location, trajectory, navigation information, GPS data, CAMs, DENMs. | |
-| Step 3 (M) | The Near-RT RIC receives the relevant info from the Non-RT RIC over the A1 interface and from the RAN over the E2 interface, interprets the policies and updates the AI/ML models. | |
-| Step 4 (M) | The Near-RT RIC infers optimal RAN configuration (UE-specific NRTs) according to the trained AI/ML models and communicates the result to the RAN over E2 interface. | |
-| Step 5 (M) | RAN deploys the configuration received from the Near-RT RIC over the E2 interface. | |
-| Step 4 | If required, Non-RT RIC can configure specific performance measurement data to be collected from RAN to assess the performance of the V2X HO management function in Near-RT RIC, or to assess the outcome of the applied policies and configuration. | |
-| Ends when | Operator specified trigger condition or event is satisfied. | |
-| Exceptions | None identified. | |
-| Post Conditions | Non-RT RIC monitors the performance of the V2X HO related function in Near-RT RIC by collecting and monitoring the relevant performance KPIs and counters from the RAN and the V2X AS. | |
-
-```
-
-@startuml
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-Autonumber
-
-Box "Service Management and Orchestration" #gold
- Participant SMO as "Orchestration"
- Boundary Collector
- Control CTRL as "Resource Controller"
- Database DL as "Data Lake"
- Participant NON as "Non-RT RIC"
- Collections MLTH as "ML Training Host(s)"
-end box
-
-Box "O-RAN" #lightpink
- Participant RIC as "Near-RT RIC"
- Participant OCU as "O-CU"
- Participant ODU as "O-DU"
-End box
-
-Box "External" #lightcyan
- Participant V2X as "V2X Application Server"
-End box
-
-ODU-> Collector : <> SMO data collection
-OCU-> Collector : <> SMO data collection
-RIC -> Collector : <> SMO data collection
-
-Hnote over NON
- Assume trained models are available in SMO
-Endhnote
-
-SMO -> NON : <> Deploy NonRT_Model1
-NON -> NON : Execute NonRT_Model1
-NON -> RIC : <> Traffic Steering Policy (create/update/delete)
-
-SMO -> RIC : <> Deploy NearRT_Model1
-SMO -> RIC : <> Deploy NearRT_Model2
-RIC -> ODU: <> Subscription request to initiate data collection
-ODU -> RIC : <> Model inference data collection
-RIC -> OCU: <> Subscription request to initiate data collection
-OCU -> RIC : <> Model inference data collection
-RIC -> NON : <> Subscription request to initiate data collection
-NON -> V2X : <> Subscription request to initiate data collection
-V2X -> NON : <> Model inference data collection
-NON -> RIC : <> Model inference data collection
-
-RIC -> ODU : <> Subscription Request:{Measurement report for UE}
-ODU -> RIC : <> Report:{Measurement report for UE}
-RIC -> OCU : <> Subscription Request:{Measurement report for UE}
-OCU -> RIC : <> Report:{Measurement report for UE}
-RIC -> NON : <> Subscription Request:{Measurement report for UE}
-NON -> V2X : <> Subscription Request:{Measurement report for UE}
-V2X -> NON : <> Report:{Measurement report for UE}
-NON -> RIC : <> Report:{Measurement report for UE}
-RIC -> RIC : Detect V2X UE
-
-RIC -> RIC : <> Monitor UE performance
-
-```
-
-```
-
-RIC -> RIC : Execute NearRT_Model1 to detect/predict anomalous HO situation
-Alt if HO anomaly score < threshold
- RIC -> RIC : Execute NearRT_Model2 to find substitute UE specific substitute NRTs
- RIC -> OCU : <> RICControlRequest, ControlmessageIE: {xNB, cell_iD, UE_ID_NRT, Action = deploy}
- OCU -> RIC : <> RICControlResponse: {successful/failure}
-End
-
-ODU-> Collector : <> SMO data collection
-OCU-> Collector : <> SMO data collection
-RIC -> Collector : <> SMO data collection
-
-SMO -> SMO: Update NearRT_model2
-SMO -> RIC : <> Deploy NearRT_Model2
-@enduml
-
-```
-
-The flow diagram of the context-based dynamic handover management for V2X use case is given in figure 4.1.3.1-1.
-
-
-
-The sequence diagram illustrates the context-based dynamic handover management for V2X use case. It is divided into three main lifelines: Service Management and Orchestration (SMO), O-RAN, and External (V2X Application Server).
-
-**Service Management and Orchestration (SMO) components:** Orchestration, Collector, Resource Controller, Data Lake, Non-RT RIC, ML Training Host(s).
-
-**O-RAN components:** Near-RT RIC, O-CU, O-DU.
-
-**External component:** V2X Application Server.
-
-**Sequence of interactions:**
-
-- SMO internal components (Collector, Resource Controller, Data Lake) send SMO data collection messages (1, 2, 3).
-- Orchestration sends a message to deploy NonRT\_Model1 (4).
-- Non-RT RIC executes NonRT\_Model1 (5).
-- Non-RT RIC sends a Traffic Steering Policy (create/update/delete) (6).
-- Orchestration sends messages to deploy NearRT\_Model1 (7) and NearRT\_Model2 (8).
-- Non-RT RIC sends subscription requests to initiate data collection (9, 10, 11, 12).
-- Non-RT RIC sends subscription requests to initiate data collection (13, 14, 15, 16).
-- Non-RT RIC sends subscription requests for measurement reports (17, 18, 19, 20).
-- Non-RT RIC sends subscription requests for measurement reports (21, 22, 23, 24).
-- Non-RT RIC detects V2X UE (25).
-- Non-RT RIC monitors UE performance (26).
-- Non-RT RIC executes NearRT\_Model1 to detect/predict anomalous HO situation (27).
-- An 'alt' block titled 'if HO anomaly score < threshold' contains:
- - Execute NearRT\_Model2 to find substitute UE specific substitute NRTs (28).
- - RIC sends a RICControlRequest (xNB, cell\_iD, UE\_ID\_NRT, Action = deploy) (29).
- - RIC receives a RICControlResponse (successful/failure) (30).
-- SMO internal components send SMO data collection messages (31, 32, 33).
-- Orchestration updates NearRT\_model2 (34).
-- Orchestration sends a message to deploy NearRT\_Model2 (35).
-
-Sequence diagram for context-based dynamic handover management for V2X use case. The diagram shows interactions between Service Management and Orchestration (SMO), O-RAN (Near-RT RIC, O-CU, O-DU), and External (V2X Application Server).
-
-Figure 4.1.3.1-1: Context-based dynamic handover management for V2X flow diagram
-
-### 4.1.4 Required data
-
-The measurement counters and KPIs (as defined by 3GPP) shall be appropriately aggregated by cell, QoS type, slice, etc.
-
-- 1) Measurement reports with RSRP/RSRQ/CQI information for serving and neighboring cells.
-- 2) UE connection and mobility/handover statistics with indication of successful and failed handovers and error codes etc.
-- 3) V2X related data: position, velocity, direction, navigation data, CAMs, DENMs as specified in ETSI EN 302 637-3 [16] and in [i.5].
-
-## 4.2 Flight path based dynamic UAV radio resource allocation
-
-This use case provides the background, motivation, and requirements for the support the use case of flight path based dynamic UAV radio resource allocation, allowing operators to adjust radio resource allocation policies through the O-RAN architecture, reducing unnecessary handover and improving radio resource utilization.
-
-### 4.2.1 Background and goal of the use case
-
-The field trials' results show that the coverage for low altitude is good and can provide various services for terrestrial UEs with good performance. However, since the site along the flight is mainly for terrestrial UEs, the altitude of the UAV is always not within the main lobe of the ground station antenna. And the side lobes give rise to the phenomenon of scattered cell associations particularly noticeable in the sky. The cell association pattern on the ground is ideally contiguous area where the best cell is most often the one closest to the UE. As the UE move up in height, the antenna side lobes start to be visible, and there is a possibility of the best cell no longer being the closest one. The cell association pattern in this particular scenario becomes fragmented especially at the height of 300m and above. Hence, at higher altitudes, several challenges that lead to a different radio environment are:
-
-- a) LOS propagation/uplink interference
-- b) Poor KPI caused by antenna side lobes for base stations
-- c) Sudden drop in signal strength
-
-These challenges directly impact on the mobility performance of the drone and the service experience of the user. Hence, we would like to support the use case of flight path based dynamic UAV radio resource allocation to resolve the above issues.
-
-Non-Real-Time RIC can retrieve necessary of aerial vehicles related measurement metrics from network based on UE's measurement report and SMO, and flight path information of aerial vehicle, climate information, flight forbidden/limitation area information and space load information etc. from application, e.g., UTM (Unmanned Traffic Management) for constructing/training relevant AI/ML model that will be deployed in RAN. For example, this could be UL/DL interference from/to aerial vehicles, the detection of aerial vehicle UEs, and available radio resource (e.g., frequency, cell, beam, BWP, numerology) prediction. And the Near-Real-Time RIC can support deployment and execution of AI/ML models from Non-RT RIC. Based on this, the Near-Real-Time RIC can perform the radio resource allocation for on-demand coverage for UAV considering the radio channel condition, flight path information and other application information.
-
-The architectural context of the flight path based dynamic UAV radio resource allocation use case is shown in figure 4.2.1-1.
-
-
-
-Diagram illustrating the use case of flight path based dynamic UAV radio resource allocation. The diagram shows a vertical stack of components: UTM (cloud icon) connected to Non-Real Time RIC, which is connected to Near-Real Time RIC. Below Near-Real Time RIC is a dashed box containing CU-CP and CU-UP, connected via E2 interfaces. Below this box is the DU, connected via F1 interfaces. A UAV (airplane icon) is shown at the bottom, connected to the DU via a Uu interface.
-
-**Figure 4.2.1-1: Use case of flight path based dynamic UAV radio resource allocation**
-
-Since there is no effective functional module in current eNB/gNB to retrieve the application information, perform machine learning and training based on both the acquired application information and radio environment information, and execute AI/ML models based on above information. And in the O-RAN architecture, the flight path based dynamic UAV radio resource allocation mechanism can be supported by the RIC function module, i.e., Non-Real-Time RIC and Near-Real-Time RIC. Therefore, we provide the description of O-RAN support use case for flight path based dynamic UAV radio resource.
-
-### 4.2.2 Entities/resources involved in the use case
-
-- 1) Non-RT RIC:
- - a) Retrieve necessary of O-RAN support for aerial vehicles related measurement metrics from network level measurement report and SMO (can acquire data from application) for constructing/training relevant AI/ML model that will be deployed in Near-RT RIC to assist in the O-RAN support for aerial vehicles function. For example, this could be UL/DL interference from/to aerial vehicles, the detection of aerial vehicle UEs, and available radio resource (e.g. frequency, cell, beam, BWP, numerology) prediction.
- - b) Training of potential ML models for O-RAN support for aerial vehicles, which can respectively autonomously control UL/DL interference from/to aerial vehicles, detect the UE of aerial vehicles, and predict available radio resource (e.g. frequency, cell, beam, BWP, numerology) for aerial vehicles.
- - c) Send policies/intents to Near-RT RIC to drive the O-RAN support for aerial vehicles at RAN level in terms of expected behavior.
-- 2) Near-RT RIC:
- - a) Support update of AI/ML models from Non-RT RIC.
- - b) Support execution of the AI/ML models from Non-RT RIC.
- - c) Support interpretation and execution of intents and policies from Non-RT RIC to derive O-RAN support for aerial vehicles at RAN level in terms of expected behavior.
- - d) Support perform the radio resource allocation for on-demand coverage for UAV considering the radio channel condition, flight path information and other application information via the AI/ML models from Non-RT RIC.
- - e) Sending aerial vehicles performance report to Non-RT RIC for evaluation and optimization.
-- 3) RAN:
- - a) Support data collection with UE performance report over O1 interface.
- - b) Support non-real-time optimization of radio resources allocation parameters over O1 interface.
-- 4) Application server:
-
-- a) Provide application information, e.g. flight path information of aerial vehicle, climate information, flight forbidden/limitation area information and space load information.
-
-### 4.2.3 Solutions
-
-#### 4.2.3.1 Flight path based dynamic UAV radio resource allocation
-
-The context of the flight path based dynamic UAV radio resource allocation use case is captured in table 4.2.3.1-1.
-
-**Table 4.2.3.1-1: Flight path based dynamic UAV radio resource allocation**
-
-| Use Case Stage | Evolution / Specification | <>
Related use |
-|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
-| Goal | In the O-RAN architecture, the flight path based dynamic UAV radio resource allocation mechanism can be supported, which can perform the radio resource allocation for on-demand coverage for UAV considering the radio channel condition, flight path information and other application information. | |
-| Actors and Roles | Non-RT RIC: RAN policy control function.
Near-RT RIC: RAN policy enforcement function.
RAN: Implementation of updated configuration parameters.
Application server: Generates RAN side UE-level policies. | |
-| Assumptions | All relevant functions and components are instantiated.
A1/O1 interface connectivity is established with Non-RT RIC. | |
-| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them.
A certificate is shared between Near-RT RIC and Non-RT RIC for model related data exchange.
E2 interface is established between Near-RT RIC and CU/DU. | |
-| Begins when | Operator specified trigger condition or event is detected. | |
-| Step 1 (M) | Application server sends the application data to Non-RT RIC. | |
-| Step 2 (M) | Non-RT RIC deploys/updates AI/ML models in the Near-RT RIC via O1 or Non-RT RIC assigns/update the AI/ML model for the Near-RT RIC xApp via A1. | |
-| Step 3 (M) | Non-RT RIC sends relevant policies/intents and enrichment data to the Near-RT RIC over the A1 interface. | |
-| Step 4 (M) | The Near-RT RIC receives the relevant info from the Non-RT RIC over the A1 interface and from the RAN over the E2 interface, interprets the policies and updates the AI/ML models.
And the Near-RT RIC converts policy to specific configuration parameter commands. | |
-| Step 5 (M) | RAN executes the command to modify the configuration parameters RAN executes the command to modify the configuration parameters. | |
-| Ends when | Operator specified trigger condition or event is satisfied. | |
-| Exceptions | None identified. | |
-
-| Use Case Stage | Evolution / Specification | <> |
-|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
-| | | Related use |
-| Post Conditions | Non-RT RIC collects relevant performance data from eNB/gNB, to observe the data transmission performance improvement brought by the wireless resource configuration optimization policy. | |
-
-```
-
-@startuml
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-Autonumber
-
-Box "Service Management and Orchestration" #gold
- Boundary Collector as collect
- Participant "Non-RT RIC" as non
-End box
-
-Box "O-RAN" #lightpink
- Participant near as "Near-RT RIC"
- Participant ran as "O-CU/O-DU"
-End box
-
-Box "External" #lightcyan
- Participant "Application Server" as app
-End box
-
-ran --> collect: <> Data collection
-collect--> non : Retrieval of data
-app --> non : Data retrieval of application data
-
-group ML workflow
- non -> non : Training of ML models
- non -> non : Deploy internal ML models
- non -> near : <> Deploy or update ML models
-end
-
-app --> non : Data retrieval of application data
-
-```
-
-```
-
-non -> near : <> Radio resource allocation/update policies/intents for UAV UE
-non -> near : <> Enrichment data
-near -> ran : <> Radio resource configuration update for UAV UE
-
-group Performance evaluation and optimization
- ran -> collect: <> Data collection
- collect-> non : Data retrieval of RAN and other data
- non -> non : Performance monitoring & evaluation
- non -> non : Model re-training/update
-end
-
-@enduml
-
-```
-
-The flow diagram of the flight path based dynamic UAV radio resource allocation use case is given in figure 4.2.3.1-1.
-
-
-
-The diagram illustrates the sequence of interactions for the flight path based dynamic UAV radio resource allocation use case. It features three main lifelines: Service Management and Orchestration (containing Collector and Non-RT RIC), O-RAN (containing Near-RT RIC and O-CU/O-DU), and External (containing Application Server). The process is divided into two main phases: ML workflow and Performance evaluation and optimization.
-
-**ML workflow:**
-
-- Collector sends <> Data collection to Non-RT RIC.
-- Non-RT RIC sends 2 Retrieval of data to Collector.
-- Non-RT RIC sends 3 Data retrieval of application data to Application Server.
-- Non-RT RIC performs 4 Training of ML models.
-- Non-RT RIC performs 5 Deploy internal ML models.
-- Non-RT RIC sends 6 <> Deploy or update ML models to Near-RT RIC.
-- Non-RT RIC sends 7 Data retrieval of application data to Application Server.
-- Non-RT RIC sends 8 <> Radio resource allocation/update policies/intents for UAV UE to Near-RT RIC.
-- Non-RT RIC sends 9 <> Enrichment data to Near-RT RIC.
-- Near-RT RIC sends 10 <> Radio resource configuration update for UAV UE to O-CU/O-DU.
-
-**Performance evaluation and optimization:**
-
-- Collector sends 11 <> Data collection to Non-RT RIC.
-- Non-RT RIC sends 12 Data retrieval of RAN and other data to Collector.
-- Non-RT RIC performs 13 Performance monitoring & evaluation.
-- Non-RT RIC performs 14 Model re-training/update.
-
-Sequence diagram showing the interaction between Service Management and Orchestration (Collector, Non-RT RIC), O-RAN (Near-RT RIC, O-CU/O-DU), and External (Application Server) for UAV radio resource allocation. The diagram is divided into two main groups: 'ML workflow' and 'Performance evaluation and optimization'. The ML workflow involves data collection, retrieval, model training, and deployment. The Performance evaluation group involves data collection, retrieval, monitoring, and model re-training.
-
-Figure 4.2.3.1-1: Use case of flight path based dynamic UAV radio resource allocation flow diagram
-
-### 4.2.4 Required data
-
-Multi-dimensional data are expected to be retrieved for AI/ML model training and policies generation.
-
-- 1) Network level measurement report, including:
- - a) UE level radio channel information, mobility related metrics
- - b) UE level location information
-
-- 2) Aerial vehicles related measurement metrics collected from SMO (can acquire data from application or network, e.g., flight path information of aerial vehicle, climate information, flight forbidden/limitation area information and space load information).
-
-## 4.3 Radio resource allocation for UAV application scenario
-
-This use case provides the background, motivation, and requirements for the UAV control vehicle use case, allowing operators to adjust radio resource allocation policies through the O-RAN architecture, reducing latency and improving radio resource utilization.
-
-### 4.3.1 Background and goal of the use case
-
-As shown in figure 4.3.1-1, this scenario refers to a rotor UAV flying at low altitude and low speed, and carrying cameras, sensors and other devices mounted. The operation terminals work in the 5.8GHz to remote control the UAV for border/forest inspection, high voltage/base station inspection, field mapping, pollution sampling, and HD live broadcast. At the same time, the UAV mobile control stations and the anti-UAV weapons jointly provide the service of fighting against illegal UAVs to ensure low-altitude safety in special areas. The UAV operation terminals, the anti-UAV weapons, and the UAV mobile control stations are connected with the UAV control vehicle using 5G network.
-
-
-
-The diagram illustrates the UAV control vehicle application scenario. At the top, two rotor UAVs (UAV 1 and UAV 2) are shown. UAV 1 is connected to 'Operation terminal 1' and UAV 2 is connected to 'Operation terminal 2'. Both terminals are connected via 5G network transmissions to a '5G gNB' located inside a 'UAV Control Vehicle'. Above the UAVs, a callout box shows three mounted devices: a 'Camera', a 'Gas detector', and a 'searchlight'. Below the UAVs, an 'Anti-UAV Weapon' is shown fighting against an 'Illegal UAV', and a 'Mobile control station' is shown identifying the 'Illegal UAV'. Both the Anti-UAV Weapon and the Mobile control station are also connected via 5G network transmissions to the '5G gNB' in the UAV Control Vehicle.
-
-Diagram of UAV control vehicle application scenario showing UAVs, operation terminals, anti-UAV weapons, mobile control stations, and a UAV control vehicle connected via 5G network transmissions to a 5G gNB.
-
-Figure 4.3.1-1: UAV control vehicle application scenario
-
-UAV control vehicle deploys network equipment, including O-CU, O-DU, the Non-RT RIC function modules and application server (in this use case it is an edge computing service platform) to provide reliable network services through 5G networks. The data transmitted over the network includes control data and application data. The control data includes navigation commands, configuration changes, flight status data reporting, etc. Control data requires low latency and low bandwidth requirements. The application data includes 4K high-definition video data, which has obvious uplink and downlink service asymmetry, and the uplink has high requirements on network bandwidth. The UAV control vehicle deploys edge computing services on the 5G gNB side to implement local processing of video and control information. At the same time, real-time data services can be provided with the third-party applications by a video server. The Near-RT RIC function module provides radio resource management functions of the gNB side.
-
-
-
-Figure 4.3.1-2: Network architecture for UAV control vehicle application scenario. The diagram shows two options, Option A and Option B, for the network architecture. Both options show a UAV Control Vehicle containing an O-CU, O-DU, and 5G gNB connected to a Near-RT RIC. The Near-RT RIC is connected to an Application Server (Edge Computing Service Platform) and a Non-RT RIC. The Non-RT RIC is connected to a Service Management & Orchestration Framework. The Service Management & Orchestration Framework is connected to a Video server, which is connected to VR, AI, and Video. In Option A, the Non-RT RIC and Service Management & Orchestration Framework are in the cloud, while in Option B, they are inside the vehicle.
-
-**Figure 4.3.1-2: Network architecture for UAV control vehicle application scenario**
-
-The 5G network supports real-time high-definition video transmission and remote low-latency control of UAV, and finally provides various industry services such as inspection, security, surveying, and mapping. In the UAV control vehicle application scenario, there are a small amount of control data interaction requirements between the terminal and the network interaction, as well as the large bandwidth requirements for uploading HD video.
-
-The service asymmetry raises new requirements for resource allocation of the gNB. At the same time, the existing network operation and maintenance management platform (OSS system) can only optimize the parameters of a specific group of UEs, but not individual users. In the O-RAN architecture, the radio resource requirements for different terminals are sent to the gNB for execution by means of the RIC function module.
-
-The UAV control vehicle has flexible layout features. In this use case, the application service and content are deployed on the edge computing platform instead of the core network; the RIC function module is used to schedule radio resources instead of the core network's QoS mechanism. In this way, the load and overhead of the core network can be reduced, the forwarding and processing time of data transmission can be reduced.
-
-As shown in figure 4.3.1-2, this scenario involves two options of network architecture. Option A is that gNB and Near-RT RIC are deployed on the control vehicle, Non-RT RIC and core network are deployed on the central cloud. The control vehicle is connected to the core network and Non-RT RIC via fiber optics. Option B is a private network, all the modules, including the gNB, Near-RT RIC, Non-RT RIC and the necessary core network function modules, are deployed in the control vehicle.
-
-### 4.3.2 Entities/resources involved in the use case
-
-- 1) Non-RT RIC:
- - a) Support sending resource allocation requirements to Near-RT RIC.
- - b) Support receiving UE-level radio resource adjustment requirements from the application server.
- - c) Support communication between Non-RT RIC and Near-RT RIC with UE-level policies.
-- 2) Near-RT RIC:
- - a) Support for receiving resource allocation requests from Non-RT RIC.
- - b) Support for the interpretation and execution of the resource allocation policies received from Non-RT RIC.
- - c) Support communication with RAN of configuration parameters.
-- 3) RAN:
- - a) Support resource allocation requests from the Near-RT RIC.
- - b) Support sending terminal registration information to RAN application server and Near-RT RIC.
-
-- c) Support non-real-time optimization of radio resources allocation parameters over O1 interface.
- - d) Support for adjustment of the resource configuration parameters for a specific UE.
-- 4) Application server:
-- a) Support receiving terminal registration information from E2 nodes via SMO.
- - b) Support collection of user plane data uploaded from RAN.
- - c) Support sending UE-level radio resource adjustment requirements to Non-RT RIC.
-
-### 4.3.3 Solutions
-
-#### 4.3.3.1 UAV control vehicle
-
-The context of the UAV control vehicle use case is captured in table 4.3.3.1-1.
-
-**Table 4.3.3.1-1: UAV control vehicle**
-
-| Use Case Stage | Evolution / Specification | <>
Related use |
-|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
-| Goal | In the UAV control vehicle scenario, the UE-level radio resource configuration optimization is achieved through the delivery of policies and configuration parameters. | |
-| Actors and Roles | Non-RT RIC: RAN policy control function.
Near-RT RIC: RAN policy enforcement function.
RAN: Implementation of updated configuration parameters.
Application server: Generates UE-level resource allocation requirements. | |
-| Assumptions | All relevant functions and components are instantiated.
A1/O1 interface connectivity is established with Non-RT RIC. | |
-| Pre-conditions | The Non-RT RIC sends an instruction through the interface, informing the RAN to allocate the default resource, and establish the cell.
The RAN notifies the Near-RT RIC and application server of the accessed terminal (UE) information. | |
-| Begins when | Operator specified trigger condition or event is detected. | |
-| Step 1 (M) | Application server sends requirements of radio resource allocation adjustment to Non-RT RIC.
This request can be sent at any time, or it can be sent at regular intervals. | |
-| Step 2 (M) | Non-RT RIC converts the requirements to resource adjustment policy and distributes the policy to the Near-RT RIC. | |
-| Step 3 (M) | Near-RT RIC converts policy to specific configuration parameter commands. | |
-| Step 4 (M) | RAN executes the command to modify the configuration parameters. | |
-| Step 5 (M) | The specified UE adjusts the uplink rate. | |
-| Ends when | Operator specified trigger condition or event is satisfied. | |
-| Exceptions | None identified. | |
-
-| Use Case Stage | Evolution / Specification | <>
Related use |
-|-----------------|--------------------------------------------------------------|-------------------------|
-| Post Conditions | The RAN operates using the newly deployed parameters/models. | |
-
-```
-
-@startuml
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-Autonumber
-
-Box "Service Management and Orchestration" #gold
- participant "Non-RT RIC" as non
-End box
-
-Box "O-RAN" #lightpink
- Participant near as "Near-RT RIC"
- Participant ran as "O-CU/O-DU"
-End box
-
-Box "External" #lightcyan
- Participant "Application Server" as app
-End box
-
-non->near: <> Resource allocation request
-near->ran: <> Resource allocation command
-ran->ran: Cell establishment
-ran->near: <> Terminal registration
-near->non: <>Terminal registration
-non->app: Terminal registration
-
-app->app: data analysis based on the retrieved user plane data from RAN
-
-group Policy of wireless resource configuration optimization
- app->non: Radio resource allocation requirement
- non->near: <> Radio resource allocation policy
- near->ran: <> Adjust configuration parameter command
-
-```
-
-```
-
-ran->ran: Adjust resource allocation
-
-end
-
-@enduml
-
-```
-
-The flow diagram of the UAV control vehicle use case is given in figure 4.3.3.1-1.
-
-
-
-```
-
-sequenceDiagram
- box "Service Management and Orchestration"
- participant NonRT as Non-RT RIC
- end
- box "O-RAN"
- participant NearRT as Near-RT RIC
- participant OCU as O-CU/O-DU
- end
- box "External"
- participant AS as Application Server
- end
-
- NonRT->>NearRT: 1 <> Resource allocation request
- NearRT->>OCU: 2 <> Resource allocation command
- OCU->>OCU: 3 Cell establishment
- OCU->>NearRT: 4 <> Terminal registration
- NearRT->>NonRT: 5 <> Terminal registration
- NonRT->>AS: 6 Terminal registration
- AS->>AS: 7 data analysis based on the retrieved user plane data from RAN
-
- rect rgb(255, 255, 255)
- Note over NonRT, OCU: Policy of wireless resource configuration optimization
- AS->>NearRT: 8 Radio resource allocation requirement
- NearRT->>NonRT: 9 <> Radio resource allocation policy
- NearRT->>OCU: 10 <> Adjust configuration parameter command
- OCU->>OCU: 11 Adjust resource allocation
- end
-
-```
-
-Sequence diagram for UAV control vehicle use case showing interactions between Service Management and Orchestration (Non-RT RIC), O-RAN (Near-RT RIC, O-CU/O-DU), and External (Application Server).
-
-Figure 4.3.3.1-1: UAV control vehicle
-
-### 4.3.4 Required data
-
-Multi-dimensional data are expected to be retrieved for policy generation and performance improvements brought by the policy:
-
-- 1) The number of terminals accessed, the identification information such as a UE ID that distinguishes each UAV connected with UAV the control vehicle, and the resource information assigned by default.
-- 2) UE-level radio resource allocation information, such as the number of PRB resources used in PDSCH/PUSCH scheduling.
-
-## 4.4 QoE optimization
-
-This use case provides the background and motivation for the O-RAN architecture to support real-time QoE optimization. Moreover, some high-level description and requirements over Non-RT RIC, A1 and E2 interfaces are introduced.
-
-### 4.4.1 Background and goal of the use case
-
-The highly demanding 5G native applications like cloud VR are both bandwidth consuming and latency sensitive. However, for such traffic-intensive and highly interactive applications, current semi-static QoS framework cannot efficiently satisfy diversified QoE requirements especially taking into account potentially significant fluctuation of radio transmission capability. It is expected that QoE estimation/prediction from application level can help deal with such uncertainty and improve the efficiency of radio resources, and eventually improve user experience. RAN analytics information as RAN service can be exposed to an external application or MEC. It is envisioned to be helpful for the application to improve the user experience.
-
-The main objective is to ensure QoE optimization be supported within the O-RAN architecture and its open interfaces. Multi-dimensional data, e.g., user traffic data, QoE measurements, network measurement report, can be acquired and processed via ML algorithms to support traffic recognition, QoE prediction, QoS enforcement decisions. ML models can be trained offline and model inference will be executed in a real-time manner. Focus should be on a general solution that would support any specific QoE use case (e.g., cloud VR, video, etc.).
-
-### 4.4.2 Entities/resources involved in the use case
-
-- 1) Non-RT RIC:
- - a) Retrieve necessary QoE related measurement metrics from network level measurement report and SMO (can acquire data from application) for constructing/training relevant AI/ML model that will be deployed in Near-RT RIC to assist in the QoE optimization function. For example, this could be application classification, QoE prediction, and available bandwidth prediction.
- - b) Training of potential ML models for predictive QoE optimization, which can respectively autonomously recognize traffic types, predict quality of experience, or predict available radio bandwidth.
- - c) Send policies/intents to Near-RT RIC to drive the QoE optimization at RAN level in terms of expected behavior.
-- 2) Near-RT RIC:
- - a) Support update of AI/ML models from Non-RT RIC.
- - b) Support execution of the AI/ML models from Non-RT RIC, e.g., application classification, QoE prediction, and available bandwidth prediction.
- - c) Support interpretation and execution of intents and policies from Non-RT RIC to derive the QoE optimization at RAN level in terms of expected behavior.
- - d) Sending QoE performance report to Non-RT RIC for evaluation and optimization.
-- 3) RAN:
- - a) Support network state and UE performance report with required granularity to SMO over O1 interface.
- - b) Support QoS enforcement based on messages from A1/E2, which are expected to influence RRM behavior.
-- 4) Application server/MEC:
- - a) Request/subscribe RAN analytics information from Near-RT RIC.
-
-### 4.4.3 Solutions
-
-#### 4.4.3.1 AI/ML model training and distribution
-
-The context of the model training and distribution is captured in table 4.4.3.1-1.
-
-**Table 4.4.3.1-1: Model training and distribution**
-
-| Use Case Stage | Evolution / Specification | <> |
-|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
-| | | Related use |
-| Goal | Model training and distribution | |
-| Actors and Roles | Non-RT RIC, Near-RT RIC, SMO, application server | |
-| Assumptions | All relevant functions and components are instantiated.
A1/O1 interface connectivity is established with Non-RT RIC. | |
-| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them.
A certificate is shared between Near-RT RIC and Non-RT RIC for model related data exchange.
Editor's note: Security related procedure is not defined in the present document. | |
-
-| Use Case Stage | Evolution / Specification | <> |
-|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
-| | | Related use |
-| Begins when | Operator specified trigger condition or event is detected. | |
-| Step 1 (M) | QoE related measurement metrics from SMO (can acquire data from application) and network level measurement report either for instantiating training of a new ML model or modifying existing ML model. | |
-| Step 2 (M) | Non-RT RIC does the model training, obtains QoE related models, and can deploy QoE policy model internally. An example of QoE-related models that can be used at the Near-RT RIC is provided as follows: - a) Application classification model (optional and can refer to 3rd party's existing functionality)
- b) QoE prediction model
- c) QoE policy model
- d) Available BW prediction model
| |
-| Step 3 (M) | Non-RT RIC deploys/updates the AI/ML model in the Near-RT RIC via O1 or Non-RT RIC assigns/update the AI/ML model for the Near-RT RIC xApp via A1. | |
-| Step 4 (M) | Near-RT RIC stores the received QoE related ML models in the ML model inference platform and based on requirements of ML models. | |
-| Step 5 (O) | If required, Non-RT RIC can configure specific performance measurement data to be collected from RAN to assess the performance of AI/ML models and update the AI/ML model in Near-RT RIC based on the performance evaluation and model retraining. | |
-| Ends when | Operator specified trigger condition or event is satisfied. | |
-| Exceptions | None identified. | |
-| Post Conditions | Near-RT RIC stores the received QoE related ML models in the ML model inference platform and execute the model for QoE optimization function in Near-RT RIC. | |
-
-```
-
-@startuml
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-Box "Service Management and Orchestration" #gold
- Boundary "Collector" as smo
- Participant "Non-RT RIC" as non
-End box
-
-Box "O-RAN" #lightpink
-
-```
-
-```
-Participant near as "Near-RT RIC"
-Participant ran as "O-CU/O-DU"
-End box
-
-Box "External" #lightcyan
- Participant "Application Server" as app
-End box
-
-ran --> smo : <> Data collection
-smo --> non : Retrieval of collected data
-app --> non : Data retrieval of application data
-
-group ML workflow
- non -> non : Training of ML models
- non -> non : Deploy internal ML models
- non -> near: <> Deploy AI/ML models
-end
-
-group Performance evaluation and optimization
- ran -> smo : <> Data collection
- smo -> non : Data retrieval of RAN
- non -> non : Performance monitoring & evaluation
- non -> non : Model re-training/update
- non -> near: <> or <> Update AI/ML models
-end
-
-@enduml
-```
-
-The flow diagram of the model training and distribution is given in figure 4.4.3.1-1.
-
-
-
-Sequence diagram showing Model training and distribution flow. Lifelines: Service Management and Orchestration (Collector, Non-RT RIC), O-RAN (Near-RT RIC, O-CU/O-DU), External (Application Server). The diagram is divided into two main sections: 'ML workflow' and 'Performance evaluation and optimization'. In the ML workflow, data is collected from O-RAN, retrieved by the Collector, and then used for training and deployment of ML models. In the Performance evaluation section, data is collected from O-RAN, retrieved by the Collector, and used for performance monitoring and model re-training. The bottom of the diagram shows a repeat of the lifelines and initial interactions.
-
-Figure 4.4.3.1-1: Model training and distribution flow diagram
-
-#### 4.4.3.2 Policy generation and performance evaluation
-
-The context of the policy generation and performance evaluation is captured in table 4.4.3.2-1.
-
-Table 4.4.3.2-1: Policy generation and performance evaluation
-
-| Use Case Stage | Evolution / Specification | <>
Related use |
-|------------------|-------------------------------------------------------------------------------------------------------------------------|-------------------------|
-| Goal | Policy generation and performance evaluation | |
-| Actors and Roles | Non-RT RIC, Near-RT RIC, SMO | |
-| Assumptions | All relevant functions and components are instantiated.
A1/O1 interface connectivity is established with Non-RT RIC. | |
-| Pre-conditions | QoE related models have been deployed in Non-RT RIC and Near-RT RIC respectively. | |
-| Begins when | The network operator/manager want to generate QoE policy or optimize QoE related AI/ML models. | |
-| Step 1 (M) | Non-RT RIC evaluates the collected data and generates the appropriate QoE optimization policy. | |
-| Step 2 (M) | Non-RT RIC sends the QoE optimization policy to Near-RT RIC via A1 interface. | |
-
-| Use Case Stage | Evolution / Specification | <> |
-|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
-| | | Related use |
-| Step 3 (M) | Near-RT RIC receives the policy from the Non-RT RIC over the A1 interface and from the RAN over the E2 interface. And the Near-RT RIC infers the QoE related AI/ML models and converts policy to specific E2 control or policy commands. | |
-| Step 4 (M) | Near-RT RIC sends the E2 control or policy commands towards RAN for QoE optimization. | |
-| Step 5 (M) | RAN enforces the received control or policy from the Near-RT RIC over the E2 interface. | |
-| Step 6 (O) | If required, Non-RT RIC can configure specific performance measurement data to be collected from RAN to assess the performance of the QoE optimization function in Near-RT RIC, or to assess the outcome of the applied A1 policies. And then update A1 policy and E2 control or policy. | |
-| Ends when | Operator specified trigger condition or event is satisfied. | |
-| Exceptions | None identified. | |
-| Post Conditions | Non-RT RIC monitors the performance of the QoE optimization related function in Near-RT RIC by collecting and monitoring the relevant performance KPIs and counters from RAN. | |
-
-```
-
-@startuml
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-Box "Service Management and Orchestration" #gold
- Boundary "Collector" as smo
- Participant "Non-RT RIC" as non
-End box
-Box "O-RAN" #lightpink
- Participant near as "Near-RT RIC"
- Participant ran as "O-CU/O-DU"
-End box
-
-ran --> smo : <> Data collection
-smo --> non : Data retrieval
-
-group A1 policies
- non -> non : Performance monitoring
- non -> non : QoE optimization policy generation
-
-```
-
-```
-non -> near : <> QoE optimization policy
-end
-
-group E2 control & Policy
- ran -> near: <> Data collection
- near -> near : ML model inference
- near -> near : E2 control or policy generation
- near -> ran: <> Control or policy message
-end
-
-group Performance evaluation and optimization
- ran -> smo: <> Data collection
- smo -> non: Data retrieval
- non -> non: Performance monitoring
- non -> non: Update A1 policy
- non -> near : <> policy update
- ran -> near : <> Data collection
- near -> near: Update E2 control or policy
- near -> ran: <> Control or policy update
-end
-
-@enduml
-```
-
-The flow diagram of the policy generation and performance evaluation is given in figure 4.4.3.2-1.
-
-
-
-The diagram illustrates the interaction between Service Management and Orchestration (SMO) and O-RAN components for policy generation and performance evaluation. The SMO contains a Collector and a Non-RT RIC. The O-RAN contains a Near-RT RIC and O-CU/O-DU. The process is divided into three main phases:
-
-- A1 policies:**
- - The Non-RT RIC sends a <> Data collection request to the Collector.
- - The Collector responds with Data retrieval.
- - Inside the A1 policies block, the Non-RT RIC performs Performance monitoring and QoE optimization policy generation.
- - The Non-RT RIC sends a <> QoE optimization policy message to the Near-RT RIC.
-- E2 control & Policy:**
- - The Near-RT RIC sends a <> Data collection request to the O-CU/O-DU.
- - The O-CU/O-DU performs ML model inference and E2 control or policy generation.
- - The O-CU/O-DU sends a <> Control or policy message to the Near-RT RIC.
-- Performance evaluation and optimization:**
- - The Non-RT RIC sends a <> Data collection request to the Collector.
- - The Collector responds with Data retrieval.
- - Inside the Performance evaluation and optimization block, the Non-RT RIC performs Performance monitoring and Update A1 policy.
- - The Non-RT RIC sends a <> policy update message to the Near-RT RIC.
- - The Near-RT RIC sends a <> Data collection request to the O-CU/O-DU.
- - The O-CU/O-DU performs Update E2 control or policy.
- - The O-CU/O-DU sends a <> Control or policy update message to the Near-RT RIC.
-
-Sequence diagram showing policy generation and performance evaluation flow between Service Management and Orchestration and O-RAN components (Non-RT RIC, Near-RT RIC, O-CU/O-DU).
-
-Figure 4.4.3.2-1: Policy generation and performance evaluation flow diagram
-
-#### 4.4.3.3 RAN performance analytics
-
-The context of the RAN performance analytics is captured in table 4.4.3.3-1.
-
-**Table 4.4.3.3-1: RAN performance analytics**
-
-| Use Case Stage | Evolution / Specification | <> |
-|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
-| | | Related use |
-| Goal | Expose RAN analytics information to external applications or MEC. | |
-| Actors and Roles | Non-RT RIC, Near-RT RIC, SMO, application server/MEC | |
-| Assumptions | All relevant functions and components are instantiated.
A1/O1 interface connectivity is established with Non-RT RIC. | |
-| Pre-conditions | QoE related models have been deployed in Non-RT RIC and Near-RT RIC respectively.
Editor's note: Security related procedure is not defined in the present document. | |
-| Begins when | The application server or MEC wants to request/subscribe RAN analytics information | |
-| Step 1 (M) | Application server or MEC sends RAN analytics information request to Near-RT RIC or subscribes RAN analytics information from Near-RT RIC to get periodic or event triggered RAN performance. | |
-| Step 2 (M) | Near-RT RIC receives the request or subscription from application server or MEC. Upon the request, the Near-RT RIC subscribes and receives the measurement data from O-CU/O-DU. Based on it, with QoE related AI/ML models, the Near-RT RIC infers the RAN analytics information, and exposes it to application server or MEC via the response or notification command. Such information, e.g., performance analytics could be used for QoE optimization. | |
-| Ends when | Application server gets response or sends subscription deletion toward the Near-RT RIC. | |
-| Exceptions | None identified. | |
-| Post Conditions | Application server executes logic control, e.g., TCP transmission window adjustment, video coding rate selection to improve QoE. | |
-
-```
-
-@startuml
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-skinparam defaultFontSize 12
-
-Box "Service Management and Orchestration" #gold
- Boundary "Collector" as smo
- Participant "Non-RT RIC" as non
-End box
-
-Box "O-RAN" #lightpink
-
-```
-
-```
-Participant near as "Near-RT RIC"
-Participant ran as "O-CU/O-DU"
-End box
-
-Box "External" #lightcyan
- Participant "Application Server" as app
-End box
-
-ran --> smo : <> Data collection
-smo --> non : Retrieval of collected data
-app --> non : Data retrieval of application data
-
-group ML workflow
- non -> non : Training of ML models
- non -> non : Deploy internal ML models
- non -> near: <> Deploy AI/ML models
-end
-
-group Performance evaluation and optimization
- ran -> smo : <> Data collection
- smo -> non : Data retrieval of RAN
- non -> non : Performance monitoring & evaluation
- non -> non : Model re-training/update
- non -> near: <> or <> Update AI/ML models
-end
-
-@enduml
-```
-
-The flow diagram of the RAN performance analytics is given in figure 4.4.3.3-1.
-
-
-
-The diagram illustrates the RAN performance analytics flow across three main domains:
-
-- Service Management and Orchestration (SMO):** Contains two instances of 'Collector' and 'Non-RT RIC' components. The top instance shows a 'Collector' connected to a 'Non-RT RIC'.
-- O-RAN:** Contains 'Near-RT RIC' and 'O-CU/O-DU' components. The flow starts with a 'RAN analytics information Request/Subscribe' from the 'Near-RT RIC' to the 'Application Server/MEC' in the External domain. This is followed by a sequence of messages: '<> RIC Subscription Request' from 'Near-RT RIC' to 'O-CU/O-DU', '<> RIC Subscription Response' from 'O-CU/O-DU' to 'Near-RT RIC', and '<> RIC Indication' from 'O-CU/O-DU' to 'Near-RT RIC'. Inside the 'Near-RT RIC', there are steps for 'Data analysis' and 'ML model inference'. Finally, a 'RAN analytics information Response/Notify' is sent from the 'Near-RT RIC' to the 'Application Server/MEC'.
-- External:** Contains 'Application Server/MEC' components. The bottom instance shows an 'Application Server/MEC' connected to a 'Collector' in the SMO domain.
-
-RAN performance analytics flow diagram showing interactions between Service Management and Orchestration, O-RAN (Near-RT RIC, O-CU/O-DU), and External (Application Server/MEC) components.
-
-Figure 4.4.3.3-1: RAN performance analytics flow diagram
-
-### 4.4.4 Required data
-
-Multi-dimensional data are expected to be retrieved by Non-RT RIC for AI/ML model training and policies/intents generation. Network level measurement data from O-CU/O-DU are also expected to report to Near-RT RIC for RAN analytics information inference.
-
-- 1) Network level measurement report, including:
- - a) UE level radio channel information, mobility related metrics, e.g., CQI, SINR, MCS
- - b) L2 measurement report related to traffic pattern, e.g., throughput, latency, packets per-second, inter frame arrival time
- - c) RAN protocol stack status: e.g., PDCP buffer status
- - d) Cell level information: e.g., DL/UL PRB occupation rate
-- 2) QoE related measurement metrics collected from SMO (can acquire data from application or network).
-- 3) User traffic data, which can be obtained via a proprietary interface from existing data collection equipment and is currently out of the scope of A1 or E2.
-
-#### **RAN analytics information:**
-
-RAN analytics information exposed by Near-RT RIC to application server includes but is not limited to:
-
-- 1) UE level information, e.g.:
- - a) Predicted RAN performance, e.g., maximum/average traffic rate, maximum/average latency, average packet loss rate
- - b) Prediction related information, e.g., confidence, validity period
-- 2) Cell level information.
-
-## 4.5 Traffic steering
-
-This use case provides the motivation, description, and requirements for traffic steering use case, allowing operators to specify different objectives for traffic management such as optimizing the network/UE performance, or achieving balanced cell load.
-
-### 4.5.1 Background and goal of the use case
-
-5G systems will support many different combinations of access technologies namely; LTE (licensed band), NR (licensed band), NR-U (unlicensed band), Wi-Fi (unlicensed band) [i.3]. Several different multi-access deployment scenarios are possible with 5GC to support wide variety of applications and satisfy the spectrum requirements of different service providers;
-
-- Carrier aggregation between licensed band NR (primary cell) and NR-U (secondary cell)
-- Dual connectivity between licensed band NR (primary cell) and NR-U (secondary cell)
-- Dual connectivity between licensed band LTE (primary cell) and NR-U (secondary cell)
-- Dual connectivity between licensed band NR (primary cell) and Wi-Fi (secondary cell)
-
-NOTE: The scenario of dual connectivity between NR and Wi-Fi is not defined in the present document.
-
-The rapid traffic growth and multiple frequency bands utilized in a commercial network make it challenging to steer the traffic in a balanced distribution. Further in a multi-access system there is need to switch the traffic across access technologies based on changes in radio environment and application requirements and even split the traffic across multiple access technologies to satisfy performance requirements. The different types of traffic and frequency bands in a commercial network make it challenging to handle the complex QoS aspects, bearer selection (Master Cell Group (MCG) bearer, Secondary Cell Group (SCG) bearer, split bearer), bearer type change for load balancing, achieving low latency and best in class throughput in a multi-access scenario with 5GC networks as specified in 3GPP TS 37.340 [12]. Typical controls are limited to adjusting the cell reselection and handover parameters; modifying load calculations and cell priorities; and are largely static in nature when selecting the type of bearers and QoS attributes.
-
-Further, the RRM (Radio Resource Management) features in the existing cellular network are all cell-centric. Even in different areas of within a cell, there are variations in radio environment, such as neighboring cell coverage, signal strength, interference status, etc. However, base stations based on traditional control strategies treat all UEs in a similar way and are usually focused on average cell-centric performance, rather than UE-centric.
-
-Such current solutions suffer from following limitations:
-
-- It is hard to adapt the RRM control to diversified scenarios including multi-access deployments and optimization objectives.
-- The traffic management strategy is usually passive, rarely taking advantage of capabilities to predict network and UE performance. The strategy needs to consider aspects of steering, switching, and splitting traffic across different access technologies in a multi-access scenario.
-- Non-optimal traffic management, with slow response time, due to various factors such as inability to select the right set of UEs for control action. This further results in non-optimal system and UE performance, such as suboptimal spectrum utilization, reduced throughput and increased handover failures.
-
-Based on the above reasons, the main objective of this use case is to allow operators to flexibly configure the desired optimization policies, utilize the right performance criteria, and leverage machine learning to enable intelligent and proactive traffic management.
-
-### 4.5.2 Entities/resources involved in the use case
-
-- 1) Non-RT RIC:
- - a) Retrieve necessary performance, configuration, and other data for defining and updating policies to guide the behavior of traffic management function in Near-RT RIC. For example, the policy could relate to specifying different optimization objectives to guide the carrier/band preferences at per-UE or group of UE granularity.
- - b) Support communication of policies to Near-RT RIC.
- - c) Support communication of measurement configuration parameters to RAN.
-- 2) Near-RT RIC:
- - a) Support interpretation and enforcement of policies from Non-RT RIC.
-- 3) E2 nodes:
- - a) Support data collection with required granularity to SMO over O1 interface.
-
-### 4.5.3 Solutions
-
-#### 4.5.3.1 Policy-based traffic steering
-
-The context of the traffic steering use case is captured in table 4.5.3.1-1.
-
-**Table 4.5.3.1-1: Traffic steering**
-
-| Use Case Stage | Evolution / Specification | <>
Related use |
-|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
-| Goal | Drive traffic management in RAN in accordance with defined intents, policies, and configuration. | |
-| Actors and Roles | Non-RT RIC: RAN policy control function.
Near-RT RIC: RAN policy enforcement function.
E2 nodes: Control plane and user plane functions.
SMO/Collection & Control: Termination point for O1 interface. | |
-| Assumptions | All relevant functions and components are instantiated.
A1 interface connectivity is established with Non-RT RIC.
O1 interface connectivity is established with SMO/ Collection & Control. | |
-| Pre-conditions | Network is operational.
SMO/ Collection & Control has established the data collection and sharing process, and Non-RT RIC has access to this data.
Non-RT RIC monitors the performance by collecting the relevant performance events and counters from E2 nodes via SMO/ Collection & Control. | |
-| Begins when | Operator specified trigger condition or event is detected. | |
-| Step 1 (O) | If required, Non-RT RIC configures additional, more specific, performance measurement data to be collected from E2 nodes to assess the performance. | |
-| Step 2 (M) | Non-RT RIC decides an action and communicates relevant policies to Near-RT RIC over A1. The example policies can include: - a) QoS targets
- b) Preferences on which cells to allocate control plane and user plane
| |
-
-| Use Case Stage | Evolution / Specification | <> |
-|-----------------|--------------------------------------------------------------------------------------------------------------------------|-------------|
-| | | Related use |
-| | c) Bearer handling aspects including bearer selection, bearer type change | |
-| Step 3 (M) | The Near-RT RIC receives the relevant info from Non-RT RIC over A1 interface, interprets the policies and enforces them. | |
-| Step 4 (M) | Non-RT RIC decides that conditions to continue the policy is no longer valid. | |
-| Ends when | Non-RT RIC deletes the policy. | |
-| Exceptions | None identified. | |
-| Post Conditions | Non-RT RIC monitors the performance by collecting the relevant performance events and counters from E2 nodes via SMO. | |
-
-```
-
-@startuml
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-Autonumber
-
-Box "Service Management and Orchestration" #gold
- participant "Collection & Control" as smo
- participant "Non-RT RIC" as non
-end box
-
-Box "O-RAN" #lightpink
- participant "Near-RT RIC" as near
- participant "E2 Nodes" as ran
-end box
-
-ran -> smo : <> Data collection
-smo -> non : Data retrieval
-
-non -> non : Performance monitoring and evaluation
-non -> non : Performance trigger for traffic steering
-
-group O1 Data collection
- non -> smo: Request additional measurements
- smo -> ran: <> PM measurement configuration
- ran -> smo : <> Data collection
-end group
-
-```
-
-```
-smo -> non : Data retrieval
-
-end
-
-non -> non : Decision of optimization action
-
-group A1 Policies
- non -> near : <> Traffic management policy create message
- near -> ran : <> Traffic management enforcement
-end
-
-ran -> smo : <> Data collection
-smo -> non : Data retrieval of RAN and non-RAN data
-non -> non : Performance monitoring and evaluation
-non -> non : Decision to remove policy
-group A1 Policies
- non -> near : <> Traffic management policy delete message
- near -> ran : <> Traffic management policy deletion
-end
-
-@enduml
-```
-
-The flow diagram of the traffic steering use case is given in figure 4.5.3.1-1.
-
-
-
-```
-
-sequenceDiagram
- participant CC as Collection & Control
- participant NRIC as Non-RT RIC
- participant NRIC as Near-RT RIC
- participant EN as E2 Nodes
-
- Note left of CC: Service Management and Orchestration
- Note right of EN: O-RAN
-
- Note left of CC: O1 Data collection
-
- Note left of NRIC: A1 Policies
-
- Note left of NRIC: A1 Policies
-
- CC->>NRIC: 1 <> Data collection
- NRIC-->>CC: 2 Data retrieval
- NRIC->>NRIC: 3 Performance monitoring and evaluation
- NRIC->>CC: 4 Performance trigger for traffic steering
-
- Note left of CC: O1 Data collection
- CC->>NRIC: 5 Request additional measurements
- NRIC->>EN: 6 <> PM measurement configuration
- CC->>NRIC: 7 <> Data collection
- NRIC-->>CC: 8 Data retrieval
-
- NRIC->>NRIC: 9 Decision of optimization action
-
- Note left of NRIC: A1 Policies
- NRIC->>NRIC: 10 <> Traffic management policy create message
- NRIC->>EN: 11 <> Traffic management enforcement
-
- CC->>NRIC: 12 <> Data collection
- NRIC-->>CC: 13 Data retrieval of RAN and non-RAN data
- NRIC->>NRIC: 14 Performance monitoring and evaluation
- NRIC->>NRIC: 15 Decision to remove policy
-
- Note left of NRIC: A1 Policies
- NRIC->>NRIC: 16 <> Traffic management policy delete message
- NRIC->>EN: 17 <> Traffic management policy deletion
-
-```
-
-Sequence diagram for Traffic steering use case flow. Lifelines: Collection & Control, Non-RT RIC, Near-RT RIC, E2 Nodes. The diagram shows interactions for data collection, performance monitoring, and traffic management policy creation and enforcement.
-
-Figure 4.5.3.1-1: Traffic steering use case flow diagram
-
-#### 4.5.3.2 Enrichment information based traffic steering
-
-In this variation, when the Near-RT detects cell congestion, it requests via A1-EI to Non-RT RIC analytics that can be used as additional information to assist in its efforts at alleviating that congestion.
-
-The context of the enrichment information-based traffic steering use case is captured in table 4.5.3.2-1.
-
-Table 4.5.3.2-1: Enrichment information-based traffic steering
-
-| Use Case Stage | Evolution / Specification | <>
Related use |
-|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
-| Goal | Drive traffic management in RAN in accordance with defined enrichment information and associated decision control. | |
-| Actors and Roles | - Non-RT RIC: RAN analytics and enrichment information framework.
- “UE location” rApp: Capable of calculating the geo-location of UEs with a prediction on the granularity of seconds time scale (e.g., based on timing advance and RRC measurements), aggregating and trending those over time to learn mobility patterns, and using these to predict a UE’s future location based on its recent location history.
| |
-
-| Use Case Stage | Evolution / Specification | <>
Related use |
-|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
-| | - • “Traffic steering” rApp: Determines set of UEs connected to requested cell and requests UE location rApp analytics, forwarding the same to the Near-RT RIC.
- • Near-RT RIC: Detects breaches in expected performance and requests enrichment information from Non-RT RIC to aid in mitigation efforts. Also performs RAN decision control based on network telemetry and the enrichment information provided by Non-RT RIC.
- • E2 nodes: Control plane and user plane RAN functions.
- • SMO/ Collection & Control: Termination point for O1 interface.
| |
-| Assumptions | - • All relevant functions and components are instantiated.
- • A1 interface connectivity is established between Near-RT RIC and Non-RT RIC.
- • O1 interface connectivity is established between RAN E2 nodes and SMO/ Collection & Control.
- • Near-RT RIC is capable of detecting a breach in cell performance and determine the usefulness of predictive data.
| |
-| Pre-conditions | - • Network is operational.
- • Network data collection pipelines have been engineered for necessary data volumes and Non-RT RIC has access to this data.
- • Both rApps have registered via R1 the data types that they produce and the data types they consume.
- • UE location rApp has been trained to recognize the UE mobility patterns in the local area such that, given a UE identifier, it can quickly determine whether that UE is or is not following a known mobility pattern.
- • Traffic steering rApp has subscribed to, and Non-RT RIC/SMO is collecting on its behalf, the relevant performance events and counters from E2 nodes via SMO/ Collection & Control.
| |
-| Begins when | Near-RT RIC detects a cell performance breach (e.g., due to UE capacity considerations) and determines it might be useful to have additional information from the Non-RT RIC regarding UE candidates for handover. | |
-| Step 1 (M) | Near-RT RIC requests of the Non-RT RIC the enrichment information corresponding to the UE_Traj_Pred R1 data type for the congested cell. | |
-| Step 2 (M) | Non-RT RIC leverages R1 to subscribe to UE_Traj_Pred data type from the traffic steering rApp. | |
-| Step 3 (M) | Traffic steering rApp subscribes to relevant network data for the cell in question. | |
-| Steps 4-8 (M) | Non-RT RIC/SMO interact with the O-RAN network to collect the requested network data and deliver to the traffic steering rApp. | |
-| Step 9 (M) | Traffic steering rApp determines from network data which UEs are connected to the cells in question. | |
-
-| Use Case Stage | Evolution / Specification | <> |
-|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
-| | | Related use |
-| Step 10 (M) | Traffic steering rApp leverages R1 to subscribe to UE location prediction data type (UeLocPred) for those UEs connected to the cells in question and that also meet other criteria known to the traffic steering rApp. | |
-| Step 11 (M) | Non-RT RIC leverages R1 to have UE location rApp produce the requested data type instances for the specified UEs. | |
-| Step 12 (M) | UE location rApp subscribes to relevant network data for the UEs in question. | |
-| Steps 13-17 (M) | Non-RT RIC/SMO interact with the O-RAN network to collect the requested network data and deliver to the UE location rApp. | |
-| Step 18 (M) | UE location rApp determines from network data, trended over time, the UE location prediction over a particular future time window (e.g., 10-30 seconds) for the UE along with a confidence value for that prediction. | |
-| Steps 19-20 (M) | UE location rApp leverages R1 to return the UeLocPred instances to the Non-RT RIC, which in turn delivers to the traffic steering rApp. | |
-| Step 21 (M) | Traffic steering rApp determines from UE location prediction analytics the predicted locations of the specified UEs within the next 10-30 seconds, maps those locations into a historical RF measurements map overlaying cell boundaries to physical geography, and determines the subset of UEs predicted to be leaving the oversubscribed cell within the next 10-30 seconds anyway, and hence which would perhaps be candidates for expedited handover. | |
-| Step 22 (M) | Traffic steering rApp leverages R1 to generate UE trajectory prediction (UE_Traj_Pred) data based on its analysis. | |
-| Step 23 (M) | Non-RT RIC leverages A1-EI to forward the UE trajectory prediction data to the Near-RT RIC as the corresponding A1 enrichment information type. | |
-| Step 24 (M) | The Near-RT RIC interprets the information content received across the A1-EI interface and determines whether and how to use that EI in its congestion mitigation activities. (As a further optimization, it can be useful for the Near-RT RIC to also understand what type of activity the UE is engaged in.) | |
-| Step 25 (M) | Near-RT RIC continues monitoring cell performance and decides that congestion has been resolved. | |
-| Step 26 (M) | Near-RT RIC requests the Non-RT RIC to discontinue UE_Traj_Pred data production for the target cell. | |
-| Step 27 (M) | Non-RT RIC leverages R1 to unsubscribe to UE_Traj_Pred data type from the traffic steering rApp. | |
-| Step 28 (M) | Traffic steering rApp leverages R1 to unsubscribe to the UE location prediction data type for the corresponding UEs. | |
-| Step 29 (M) | Non-RT RIC leverages R1 to unsubscribe to UeLocPred data type from the UE location rApp. | |
-| Steps 30-32 (M) | UeLocPred rApp unsubscribes to the relevant network data. | |
-| Ends when | UE location prediction rApp ceases to produce the UE location prediction data for the corresponding UEs and to collect the associated network data. | |
-| Exceptions | None identified. | |
-| Post Conditions | Near-RT RIC continues to monitor RAN performance. | |
-
-```
-@startuml
-
-skin rose
-skinparam ParticipantPadding 5
-skinparam BoxPadding 10
-Autonumber
-
-Box "Service Management and Orchestration" #gold
- participant "Collection & Control" as smo
-end box
-
-Box "Non-RT RIC" #yellow
- participant "Non-RT RC FW" as fw
- participant "Traffic Steering rApp" as tsrapp
- participant "UE Location rApp" as uerapp
-end box
-
-Box "O-RAN" #lightpink
- participant "Near-RT RIC" as near
- participant "E2 Nodes" as ran
-end box
-
-near -> fw : <> request UE_Traj_Pred
-fw -> tsrapp : <> request UE_Traj_Pred
-
-tsrapp -> fw : <> request network data
-
-group Optional - If no other rApp is collecting
- fw -> smo : internal
- smo -> ran : Request <> data
- ran -> smo : <> data collection
- smo -> fw : internal
-end
-
-fw -> tsrapp : <> data distribution
-```
-
-```
-tsrapp -> tsrapp : Determine UEs\nof interest
-
-tsrapp -> fw : <> request UeLocPred (UE list)
-fw -> uerapp : <> request UeLocPred (UE list)
-
-uerapp -> fw : <> request network data
-
-group Optional - If no other rApp is collecting
- fw -> smo : internal
- smo -> ran : request <> data
- ran -> smo : <> data collection
- smo -> fw : internal
-end
-
-fw -> uerapp : <> data distribution
-
-group Repeat per UE
- uerapp -> uerapp : Predict UE location
-end
-
-group Prediction could be returned per UE or by some grouping of UE
- uerapp -> fw : <> UeLocPred (UE list) data
- fw -> tsrapp : <> data distribution
-
- tsrapp -> tsrapp : analyze results
-
- tsrapp -> fw : <> UE_Traj_Pred (UE list) data
- fw -> near : <> UE_Traj_Pred data
-end
-
-near -> ran : <> congestion\nmitigation
-
-near -> near : Determine congestion cleared
-near -> fw : <> cease UE_Traj_Pred
-```
-
-```
-fw -> tsrapp : <> cease\UE_Traj_Pred
-tsrapp -> fw : <> cease\UELocPred
-fw -> uerapp : <> cease\nUELocPred
-
-uerapp -> fw : <> cease network data
-
-group Optional - If no other rApp is collecting
- fw -> smo : internal
- smo -> ran : cease <> data
-end
-
-@enduml
-```
-
-The flow diagram of the enrichment information-based traffic steering use case is given in figure 4.5.3.2-1.
-
-
-
-```
-
-sequenceDiagram
- participant SMO as Service Management and Orchestration
-Collection & Control
- participant FW as Non-RT RC FW
- participant TS as Traffic Steering rApp
- participant Loc as UE Location rApp
- participant NearRIC as Near-RT RIC
- participant E2 as E2 Nodes
-
- Note over FW, Loc: Non-RT RIC
- Note over NearRIC, E2: O-RAN
-
- TS->>FW: 1 <> request UE_Traj_Pred
- TS->>FW: 2 <> request UE_Traj_Pred
- TS->>FW: 3 <> request network data
-
- rect rgb(240, 240, 240)
- Note left of SMO: Optional - If no other rApp is collecting
- SMO->>SMO: 4 internal
- SMO->>E2: 5 Request <> data
- E2->>SMO: 6 <> data collection
- SMO->>SMO: 7 internal
- end
-
- FW->>TS: 8 <> data distribution
- TS->>TS: 9 Determine UEs of interest
- TS->>FW: 10 <> request UeLocPred (UE list)
- Loc->>FW: 11 <> request UeLocPred (UE list)
- Loc->>FW: 12 <> request network data
-
- rect rgb(240, 240, 240)
- Note left of SMO: Optional - If no other rApp is collecting
- SMO->>SMO: 13 internal
- SMO->>E2: 14 request <> data
- E2->>SMO: 15 <> data collection
- SMO->>SMO: 16 internal
- end
-
- FW->>Loc: 17 <> data distribution
-
- rect rgb(255, 255, 200)
- Note right of Loc: Repeat per UE
- Loc->>Loc: 18 Predict UE location
- end
-
- rect rgb(240, 240, 240)
- Note left of FW: Prediction could be returned per UE or by some grouping of UE
- Loc->>FW: 19 <> UeLocPred (UE list) data
- FW->>TS: 20 <> data distribution
- TS->>TS: 21 analyze results
- TS->>FW: 22 <> UE_Traj_Pred (UE list) data
- FW->>TS: 23 <> UE_Traj_Pred data
- end
-
- NearRIC->>E2: 24 <> congestion mitigation
- NearRIC->>NearRIC: 25 Determine congestion cleared
-
- TS->>FW: 26 <> cease UE_Traj_Pred
- TS->>FW: 27 <> cease UE_Traj_Pred
- TS->>FW: 28 <> cease UELocPred
- Loc->>FW: 29 <> cease UELocPred
- Loc->>FW: 30 <> cease network data
-
- rect rgb(240, 240, 240)
- Note left of SMO: Optional - If no other rApp is collecting
- SMO->>SMO: 31 internal
- SMO->>E2: 32 cease <